> This is the critical part of the log. So plymouth can't find a
> /dev/dri/card0 *or* a /dev/fb0 when it needs to. You haven't altered
> the start condition of /etc/init/plymouth-splash.conf or anything, have
> you?
No, the file got autoaupdated - the last time in 2010-04-08 with this change:
diff --git a/init/plymouth-splash.conf b/init/plymouth-splash.conf
index 8c87d21..730da40 100644
--- a/init/plymouth-splash.conf
+++ b/init/plymouth-splash.conf
@@ -15,11 +15,6 @@ description "Userspace bootsplash"
start on (started plymouth
and (graphics-device-added PRIMARY_DEVICE_FOR_DISPLAY=1
or drm-device-added PRIMARY_DEVICE_FOR_DISPLAY=1
- or stopped udevtrigger
- or (runlevel [016]
- and (stopped gdm
- or stopped kdm
- or stopped xdm
- or stopped lxdm))))
+ or stopped udevtrigger))
-exec /bin/plymouth --show-splash
+exec /bin/plymouth show-splash
> Or changed the way that the nouveau kernel driver is loaded ?
Not that I'm aware of.
> The call to start the splash screen isn't supposed to happen until the first
> graphics device has shown up.
Well, it was working for some days, but then broke again. maybe 14 days
ago?!
--
http://daniel.hahler.de/
--
No graphic splash using nouveau driver (although framebuffer is used after
boot/shutdown)
https://bugs.launchpad.net/bugs/551108
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
