Comment 322 for bug 129910

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.