Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Display resolution for console on boot-up

7 views
Skip to first unread message

zmdmw52

unread,
Aug 25, 2008, 12:09:10 PM8/25/08
to
Is there a way to adjust the display resolution of the DOS-like screen
(console) that appears after the appropriate entry in GRUB is
selected? (this is the screen with the scrolling commands).

Earlier it used to be 1440 X 900 (which is the default Monitor
Resolution), but now it is 768 X 680 (after re-install of openSUSE
11.0). I recall there was a line at the bottom stating VGA and then a
combination of alphabets & numbers, but don't remember what it exactly
was.

Tried configuring it from the Boot / GRUB options (there is an entry
for VGA/Monitor Res for Console, down at the bottom), but I do not
know what value to put there.

houghi

unread,
Aug 25, 2008, 12:42:11 PM8/25/08
to
zmdmw52 wrote:
> Tried configuring it from the Boot / GRUB options (there is an entry
> for VGA/Monitor Res for Console, down at the bottom), but I do not
> know what value to put there.

Start with vga=ask and you will be offerd possible settings.

houghi
--
Theologians can pursuade themselves of anything. Anyone who can worship
a trinity and insists that his religion is a monotheism can believe
anything -- just give him time to rationalize it.
Robert A. Heinlein, JOB: A Comedy of Justice

Chris

unread,
Aug 25, 2008, 12:42:21 PM8/25/08
to
zmdmw52 wrote:

Here's an article on openSUSE.org about the vga modes settings and how to
figure out what magic number you need :)

http://en.opensuse.org/SDB:Setting_up_Unsupported_Graphics_Cards_with_the_Framebuffer_Device_(GRUB)

--
Chris

Chris

unread,
Aug 25, 2008, 12:50:57 PM8/25/08
to
Chris wrote:

I forgot to mention, in the article you see the hex values for the modes.
vga= requires the base-10 number. I think you can use the hex value (0x317)
but I haven't tried it. I just used kalc to convert the hex to base-10. You
can use google too if you want:

http://www.google.ca/search?q=0x317+to+base+10

HTH,

--
Chris

zmdmw52

unread,
Aug 25, 2008, 1:20:55 PM8/25/08
to

> > Here's an article on openSUSE.org about the vga modes settings and how to
> > figure out what magic number you need :)
>
> http://en.opensuse.org/SDB:Setting_up_Unsupported_Graphics_Cards_with...)

Thanks, that helps a lot; will try it out.

> I forgot to mention, in the article you see the hex values for the modes.
> vga= requires the base-10 number. I think you can use the hex value (0x317)
> but I haven't tried it. I just used kalc to convert the hex to base-10. You
> can use google too if you want:
>
> http://www.google.ca/search?q=0x317+to+base+10

You are right, the last line was a hex number (something like 0x317);
which is why I could not remember it. Will try it out both ways (raw 3-
digit no [which, according to the article, should work] & hex number].

BTW, how do I convert XXX (raw no., .... if that is the correct word)
--> hex (hexadecimal) no?...doesn't matter, the Windows Calculator can
do it. Need to add a '0x' before the output displayed from dec -->
hex.


David Bolt

unread,
Aug 25, 2008, 1:36:50 PM8/25/08
to
On Mon, 25 Aug 2008, Chris wrote:-

>I forgot to mention, in the article you see the hex values for the modes.
>vga= requires the base-10 number.

No it doesn't. It accepts hex and decimal mode numbers.

>I think you can use the hex value (0x317)
>but I haven't tried it.

You can, and it works. I used to use 0x317 and 0x314 as the usual modes
when installing but now use their decimal equivalents, 791 or 788, as
it's 2 characters less typing.

>I just used kalc to convert the hex to base-10. You
>can use google too if you want:
>
>http://www.google.ca/search?q=0x317+to+base+10

Or you can use the page on wikipedia, which gives the mode numbers in
decimal:

<URL:http://en.wikipedia.org/wiki/VESA_BIOS_Extensions#Linux_video_mode_numbers>


Regards,
David Bolt

--
www.davjam.org/lifetype/ www.distributed.net: OGR@100Mnodes, RC5-72@15Mkeys
SUSE 10.1 32b | | openSUSE 10.3 32b | openSUSE 11.0 32b
| openSUSE 10.2 64b | openSUSE 10.3 64b | openSUSE 11.0 64b
RISC OS 3.6 | TOS 4.02 | openSUSE 10.3 PPC | RISC OS 3.11

J G Miller

unread,
Aug 25, 2008, 3:22:37 PM8/25/08
to
On Mon, 25 Aug 2008 16:42:21 +0000, Chris wrote:
> Here's an article on openSUSE.org about the vga modes settings and how
> to figure out what magic number you need :)
>
> http://en.opensuse.org/
SDB:Setting_up_Unsupported_Graphics_Cards_with_the_Framebuffer_Device_
(GRUB)

Disapointingly, on visiting this page, it says --

(There is currently no text in this page)


David Bolt

unread,
Aug 25, 2008, 5:59:15 PM8/25/08
to
On Mon, 25 Aug 2008, J G Miller wrote:-

You'll probably find that the link you went to didn't include the last
')' and so went to the empty page. If you add the ')' to the URL, you
should get there. Alternatively, I've wrapped the link in angled
brackets which should, and does locally, ensure the last bracket is
included.

<URL:http://en.opensuse.org/SDB:Setting_up_Unsupported_Graphics_Cards_with_the_Framebuffer_Device_(GRUB)>

houghi

unread,
Aug 26, 2008, 3:18:29 AM8/26/08
to
Chris wrote:
> I forgot to mention, in the article you see the hex values for the modes.
> vga= requires the base-10 number. I think you can use the hex value (0x317)
> but I haven't tried it. I just used kalc to convert the hex to base-10. You
> can use google too if you want:
>
> http://www.google.ca/search?q=0x317+to+base+10

Even how interesting this all is, I still think thatthe easiest way is
to do `vga=ask`. You will then see what is possible, try them out and if
you find one, use that in menu.lst (or via YaST) to set it fixed.

houghi
--
The whole principle [of censorship] is wrong. It's like demanding that
grown men live on skim milk because the baby can't have steak.
-- Robert A. Heinlein in "The Man Who Sold the Moon"

J G Miller

unread,
Aug 26, 2008, 10:04:13 AM8/26/08
to
On Mon, 25 Aug 2008 22:59:15 +0100, David Bolt wrote:
> You'll probably find that the link you went to didn't include the last
> ')' and so went to the empty page.
Thank you for pointing that out -- it was all of the (GRUB) at the end of
the URL which was not being picked up.

This is a useful reference page.

Thank you once again for providing the link.

0 new messages