My vga16fb problem may be the same one from bug 538893 comment #1, at least in that the garbage I see in text mode seems to be influenced by what was on the screen in X. And yes, that's a different bug. Blacklisting vga16fb is not necessary as long as X works: I get a brief period of garbage between vga16fb and X kicking in, but X works just fine. It's viafb that is the real problem here, because X (xserver-xorg- video-openchrome) does not reset things back to a usable state.
-- [KM400] Black screen after boot, no text console possible https://bugs.launchpad.net/bugs/518623 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
