Comment 235 for bug 129910

<rant>
The statement in /etc/modprobe.d/blacklist-framebuffers to the effect that all framebuffer drivers suck is extremely bizarre, because GFXBOOT that the install CD uses loads the framebuffer to install the system and does it damn near flawlessly.

As a sanity check, when I boot from the install disk, press F4, select the best resolution that works for my card/monitor, I get great resolution in the consoles. If it works during installation (which often must use lowest common denominator), it damn sure should work when the system is fully installed.

If the kernel framebuffer is so bad, somebody needs to change the install script for xserver-xorg, because it recommends the framebuffer ("Enabling this option is the safe bet . . . ."). If you don't believe me, try "dpkg-reconfigure xserver-xorg". (Now that I think of it, I've wasted a lot of time trying to get X to work correctly by enabling the framebuffer when it's blacklisted.) If the framebuffer works for the GUI, I for the life of me can't see why it won't work in text mode.

By the way, it's pretty damn arrogant to blacklist every driver out of hand and leave a flame in the configuration file about how bad they are. The framebuffer has been around for at least 8 years that I know of, and it works great for the rest of the world. The guys upstream writing the fb drivers for the kernel are some of the best software engineers in the world, with many years of experience, and these days they get their information straight from the manufacturers. Whoever wrote the flame in the blacklist file should consider that perhaps the problem is NOT in the framebuffer driver but instead somwhere between the keyboard and the chair.
</rant>

Happy trails,

Loye Young
Isaac & Young Computer Company
Laredo, Texas
http://www.iycc.biz