Re: Kernel 'vga=' parameter wierdness

[Asfand Yar Qazi]

Denis Vlasenko wrote:
> On Wednesday 22 February 2006 09:43, Asfand Yar Qazi wrote:
>
> > 'Scuse my noobness, but when I supply the following parameter to the arguments 
> >  of my kernel through GRUB, I get an 'undefined mode' error:
> >
> > vga=0164
> >
> > But then, when the prompt comes up asking me which mode I want I type in:
> >
> > 0164
> >
> > and I get the required mode!
>
>
> vga parameter is not passed to kernel itself, it is parsed by bootloader.
> Previously, booploaders had bugs versus vga=NN specified in hex and/or octal.
> Try entering decimal value.

OK, will try that.  decimal of octal(0164) = decimal(116)

> > What's happening?  On 2.4 kernel, I used to boot with vga=0x0a (which is the 
> > same mode as 0164) and it would boot fine.  Not anymore...
>
>
> 0x0a != 0164, that's for sure
> --
> vda


OK, allow me to explain:

When the modes come up on screen, they are numbered (0, 1, 2, ... a, b, etc.) 
 This is what the 'a' refers to.  Hey, it worked through LILO on 2.4 kernels.

Before I type in scan, the number for the 132x60 mode is actually 030C.  After 
I've typed in 'scan', then it comes up as 0164.  If I enter 0164 BEFORE I type 
in 'scan' at the vid mode, it still works.  But not if I give it as argument 
to GRUB.  As I said, will try giving decimal equivalent (116) as argument to GRUB.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/