[gutsy] 2.6.22 kernel option vga=xxx does not work

Not so, vesafb is built into the kernel now.

Built-in or not, vga=XXX fails with this kernel, which, as the original reporter mentioned, leaves someone without a console after a dist-upgrade. This needs to be fixed ASAP, as the console often is the only way to rescue a system, especially in the case of a server.

Yes, so. It doesn't support vga=XXX as expected. Reopening.

Hum. Further tests show that I can get it working *IF* I specify the VGA option with a hex value. For example, I had my systems originally set with 'vga=792' -- which, we know already, does not work. Now, by bootting with 'vga=0x31a' I did get my FB console.

So. It would be nice if this was documented -- if indeed, this is how it should work.

I was using vga=0x31B in Feisty, but it no longer works in Gutsy. I don't think it has to do with being represented in hex value.

Related bug:
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/129910

Hi, could you test if the fix described in bug 129910 works in your case as well. If it does please mark this as a duplicate of 129910. Thanks.

Yes, adding 'fbcon' to the initramfs modules list fixes it for me.

did not work with me, at 2.6.22-11. Will now try previous kernel levels to see what happens.

The fix works for me, as well, but hggdh is the original reporter. If it doesn't work for him, it must not be the same bug.

it is now the same bug :-)

it works now, as long as I pass the vga= in hex.

marked as duplicate of bug 129910

Got no luck with the workaround here.
using vga=0x318

maddler@aubergine [4|~/thunderbird-maddler] $ uname -a
Linux aubergine 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686 GNU/Linux

01:00.0 VGA compatible controller: nVidia Corporation G70 [GeForce Go 7600] (rev a1)

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!