Comment 6 for bug 428519

I have an update on this issue:
After some more attempts to get grub2 to work I finally gave up and downgraded to grub legacy.
However I still have the same problem!!!
This problem is NOT related to grub (grub legacy or grub2) it's the kernel in karmic!

Both grub versions correctly set the graphics mode you choose, however karmic does not send it's output there!
That's why there are sooo many posts saying that they have a blank screen for a while.
Then during boot, karmic switches the console back to it's own text mode and you can suddenly see all the output from the boot process.

This is somewhat similar to previous versions of Ubuntu.
In jaunty the console output from the kernel boot does NOT go the graphical screen set by grub, until during boot it encounters this: (as seen in dmesg)
[ 6.750050] pci 0000:00:08.0: Boot video device
(I guess this is where the kernel has initialized PCI and is now able to use that to send console output there?)
After this point all the rest of the boot output for the console is displayed in the graphical screen set by grub.
However jaunty does not try to set it's own text mode the way karmic does.

So this bug should not be filed against grub2 but somewhere else, although I don't know where.