[Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)

[Richard George]

The default behavior using the vga=... parameter on Gusty is to break
the virtual consoles while producing no error message to the user.

I understand that it makes sense to start the booting process with the
lowest common denominator driver for reliability reasons,

however I think if the system finds itself booting with a vga=.... and
all framebuffer modules blacklisted, which default configuration, the
system should produce a meaningful error message and gracefully ignore
the vga=... option, rather than the current behavior which is to display
a black screen without offering any explanation to the user as to what's
going on. Maybe that's not practical to implement, but the current
system is not intuitive.

-- 
Blank ttys when using vesafb (vga=xxx)
https://bugs.launchpad.net/bugs/129910
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to initramfs-tools in ubuntu.