https://bugzilla.suse.com/show_bug.cgi?id=1232727 https://bugzilla.suse.com/show_bug.cgi?id=1232727#c13 --- Comment #13 from Fabian Vogt <fvogt@suse.com> --- (In reply to Fabian Vogt from comment #12)

There are three issues with this approach:

1. A bug in the code: ID_PATH does not start with platform-simple-framebuffer, but it's in the middle, e.g. ID_PATH=pci-0000:00:01.0-platform-simple-framebuffer.0 2. For platforms where only the simpledrm driver is available there is an arbitrary timeout (8s by default) until plymouth tries to display anything. 3. For platforms where the simpledrm driver is available but not supposed to be used (because a native one will be loaded), it might still break if the native driver doesn't take over within that arbitrary timeout.

IMO the correct way here is: Fix 1. To avoid 2 + 3, add a list of platform device IDs which require simpledrmfb and only use simpledrmfb for those. That's essentially what plymouth-only_use_fb_for_cirrus_bochs.patch did, just ported over from fb0 to simpledrm devices. For now we can see how far we get with just removing the patch and relying on issue 1 preventing issue 2. -- You are receiving this mail because: You are on the CC list for the bug.