Comment 329 for bug 129910

Colin:

> it breaks suspend/resume

The suspend/remove issue is a bug in the proprietary X video drivers, not in vesafb. I'm sure that blacklisting the framebuffer seemed like the thing to do at the time.

> CD boot menu in Hardy no longer incites people . . . , which was probably why quite so many people were running into this bug.

That's a plausible explanation, but it's not what I'm seeing with my customers. I like the F4 feature very much because it's much easier to see what you're doing when setting up several machines a day. However, my sense is that few people ever use the F4. I have taught around 50 people how to install Ubuntu, and I tell them about F4 when I do. However, when they actually do the install themselves, they ignore it.

The reason people use the console is because it is useful for so many tasks, especially when fixing problems with video in X. They are accustomed to modern video resolutions, even in text mode, so they naturally expect the CLI to work with a decent resolution.

> Uploaded an initramfs-tools . . . . Bug is only partially fixed right now.

I think the solution Ben is driving towards is a reasonable compromise. It will get the framebuffer working for those who need or want it, but works around the suspend/remove problem in the X video driver.

I think I can speak for many on this thread: THANKS!!

Happy Trails,

Loye Young