From: Asfand Yar Qazi <ay0106@qazi.f2s.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Kernel 'vga=' parameter wierdness
Date: Wed, 22 Feb 2006 12:21:30 +0000 [thread overview]
Message-ID: <43FC574A.4000100@qazi.f2s.com> (raw)
In-Reply-To: <mj+md-20060222.121130.6225.albireo@ucw.cz>
Martin Mares wrote:
> Hello!
>
>
>>OK, will try that. decimal of octal(0164) = decimal(116)
>
>
> This won't work -- the mode numbers are hexadecimal, not octal.
> Use 356 (decimal).
You're right. I thought '0164' was octal - 0 prefix.
>
>
>>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.
>
>
> Beware, these menu item numbers are _not_ meant to be stable across
> kernel upgrades. Better use the "long" mode numbers like 0164 or 030c.
Yep, I realise that now :-)
>
>
>>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.
>
>
> You can also try giving 0x164 to GRUB.
I'll try that as well.
>
> Have a nice fortnight
err... you too :-)
next prev parent reply other threads:[~2006-02-22 12:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-22 7:43 Asfand Yar Qazi
2006-02-22 9:30 ` Denis Vlasenko
2006-02-22 12:10 ` Asfand Yar Qazi
2006-02-22 12:13 ` Martin Mares
2006-02-22 12:21 ` Asfand Yar Qazi [this message]
2006-02-24 7:32 ` Jan Engelhardt
2006-02-24 10:11 ` Martin Mares
2006-02-24 18:09 ` Jan Engelhardt
2006-02-24 18:13 ` Martin Mares
2006-02-24 18:18 ` Jan Engelhardt
2006-02-24 18:26 ` Martin Mares
[not found] <5IWVb-7UA-11@gated-at.bofh.it>
[not found] ` <5IYDF-20s-3@gated-at.bofh.it>
[not found] ` <5J0Z7-5we-13@gated-at.bofh.it>
[not found] ` <5J18z-5HB-21@gated-at.bofh.it>
[not found] ` <5J1iu-5TF-27@gated-at.bofh.it>
2006-02-22 13:20 ` Asfand Yar Qazi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=43FC574A.4000100@qazi.f2s.com \
--to=ay0106@qazi.f2s.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®