Installed packages plymouth and libplymouth4 from cosmic-proposed.
e.g: Get:1 http://archive.ubuntu.com/ubuntu cosmic-proposed/main i386 plymouth i386 0.9.3-1ubuntu10.1
To test the fix I verified plymouth and drm-modules are not present at initramfs.
This causes intel drm to be initiated after startup of plymouth and previously caused the problem.
Verified at plymouth:debug log, that fb driver first was loaded and later replaced by drm-driver.
Problem was solved now!
Remark: the default delivered initramfs hook /usr/share/initramfs-tools/hooks/plymouth still contains the line:
OPTION=FRAMEBUFFER
At my PC the variable FRAMEBUFFER is not set by any file at /usr/share/initramfs-tools/conf-hooks.d, causing plymouth and drm-files not loaded at initramfs. This gives an annoying late appearing of the plymouth-screen at startup.
Installed packages plymouth and libplymouth4 from cosmic-proposed. archive. ubuntu. com/ubuntu cosmic- proposed/ main i386 plymouth i386 0.9.3-1ubuntu10.1
e.g: Get:1 http://
To test the fix I verified plymouth and drm-modules are not present at initramfs.
This causes intel drm to be initiated after startup of plymouth and previously caused the problem.
Verified at plymouth:debug log, that fb driver first was loaded and later replaced by drm-driver.
Problem was solved now!
Remark: the default delivered initramfs hook /usr/share/ initramfs- tools/hooks/ plymouth still contains the line: initramfs- tools/conf- hooks.d, causing plymouth and drm-files not loaded at initramfs. This gives an annoying late appearing of the plymouth-screen at startup.
OPTION=FRAMEBUFFER
At my PC the variable FRAMEBUFFER is not set by any file at /usr/share/