[Bug 107441] Black or broken VT when loading i915.ko "late"

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=107441

--- Comment #21 from Jan-Marek Glogowski <glogow at fbihome.de> ---
Created attachment 141167
  --> https://bugs.freedesktop.org/attachment.cgi?id=141167&action=edit
initramfs-tools hook to remove i915.ko module

(In reply to Maarten Lankhorst from comment #19)
> Plymouth is loaded before i915 in the rootfs case?

There was a public holiday here in Bavaria / Germany, so sorry for the delay…

Yup. On Ubuntu / Debian plymouthd is started via an initramfs-tools script
(/usr/share/initramfs-tools/scripts/init-premount/plymouth), so you get a nice
splash screen for cryptsetup.

AFAIK that splash doesn't work without a DRM device, so if I kick the i915.ko
module from the initramfs, I get no splash but still plymouthd is started (hook
script goes to /etc/initramfs-tools/hooks/)

I updated my system, and now I always end up with black screen (still Ubuntu
16.04 with a kernel 4.18).

In the "early case" I get the splash until some point. Then I can manually
change the VT from 1 => 2 => 1 and it re-appears.

In the late case, now all VTs are black.

I both cases 'plymouth --quit' quits plymouthd and restores the VTs, which
would normally happen anyway, as I disabled that services to see the splash
after boot.

All this might be a user space problem. Probably some timing changed due to the
new packages. Normally a systemd service would stop plymouth, which I changed
to /bin/true for the testing.

If you have any other idea for me to test, feel free to ask me.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20180817/241f41db/attachment.html>