Comment 26 for bug 86666

Adding vga=792 to my kernel stops the panic and I get the splash.

Unfortunately at the end of the boot when loading kdm it stuck but I believe
this has more to do with the fglrx driver that I am trying to get
configured. Strangely when I leave splash off and do not set vga X starts
fine. I will have to try a few more boots and look at the logs to determine
if they are linked.

Thanks for the info. Hope this can be fixed prior to final release.

On 13/03/07, Timo Jyrinki <email address hidden> wrote:
>
> Also working vga=786 (640x480 / 24-bit, with the little fault this time
> that the progress bar is not correctly centered).
>
> Now also tested 769 (640x480/8-bit), 775 (1280x1024/8-bit), 784
> (640x480/15-bit), 791 (1024x768/16-bit), 789 (800x600/24-bit), 792
> (1024x768/24-bit) and 795 (1280x1024/24-bit), and aside from the
> centerization issue of the progress bar, all work. So setting any of
> these vga=NNN settings seems to correct this for me.
>
> I answered the usplash.conf issue earlier already, ie. it was set at the
> default xres=1024 / yres=768. Regardless of what I put there, the
> usplash hangs without setting some vga= -thing.
>
> Are the developers sure this is not related to any of the hacks that
> were made during late Ubuntu 6.10 development on the amd64 platform that
> resulted with that low-resolution, grey thing from the past on the amd64
> platform? Could it be by default eg. forcing 640x400 that was at some
> point discussed, is it the thing causing problems, or what?
>
> (saved the text, booted one more time). Answering to myself: no, also
> vga=768 works, which is 640x400/8-bit. So using any vga=NNN parameter
> fixes the issue, but by default Feisty crashes hard each and every time.
>
> --
> Feisty crashes after grub if usplash enabled (amd64)
> https://launchpad.net/bugs/86666
>