From: Denis Vlasenko <vda@ilport.com.ua>
To: Asfand Yar Qazi <ay0106@qazi.f2s.com>
Subject: Re: Kernel 'vga=' parameter wierdness
Date: Wed, 22 Feb 2006 11:30:13 +0200
User-Agent: KMail/1.8.2
Cc: linux-kernel@vger.kernel.org
References: <43FC1624.8090607@qazi.f2s.com>
In-Reply-To: <43FC1624.8090607@qazi.f2s.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200602221130.13872.vda@ilport.com.ua>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 948
Lines: 27

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.

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