© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
a60fb26
(Get the code!)
Hmm, no plymouthd isn't starting quite early enough in Noble:
2.799s - plymouthd starts
4.080s - first show-splash attempt (rejected because DRM hasn't started yet)
5.290s - found /dev/dri/card0
5.364s - showing splash screen
What this means is that any attempt to fix the bug in plymouthd itself (I was planning with FBIOPUT_CON2FBMAP) would be unreliable because plymouthd has started too late to dodge those early console messages.