Re: [gentoo-amd64] Re: I took the plunge with kde

[Dmitri Pogosyan]

Sorry guys for duplicated messages, something is off in my mailer.

The tool to find the VESA codes for the modes your card supports
is vbespy from the bottom of

http://en.wikipedia.org/wiki/VESA_BIOS_Extensions

run it as

./vbetest 2> /dev/null

Note that the codes for non-standard VESA modes can vary from card to card.
For example on my laptop mode 361 is 1440x900x8, while on desktop 
the same code refers to 1680x1050x32.

You need to convert the VESA codes vbetest reports to kernel codes passed
as vga=.   The rule is to add 512 and optionally convert to hex.

i.e 361+512=873 (decimal)=0x369 hex


> > On 09/05/2009 02:43 PM, Paul Stear wrote:
> > > By the way does anybody know how to use a smaller font for the boot up
screen?
> >
> > What monitor do you have?  If it's a TFT, use its native resolution in
> > the kernel parameters.  Though some widescreen resolutions aren't
> > supported by some graphics cards' VESA BIOSes, sadly.
>
> actually, most of them are. I happily run with vesafb 1440x900x16 laptop
> display (vga=0x36a) and 1680x1050x32 monitor (kernel parameter  vga=0x369 )
> I had a tool that detects all VESA modes your card supports, but somehow
> can't recall what was its name.
>
> >
> > Another solution is to change the kernel font (in the kernel
> > configuration, somewhere in the console framebuffer settings) and
> > console font (/etc/conf.d/consolefont) since the kernel font will be
> > replaced after the kernel has booted an init is run.
>
> --
> Dmitri Pogosyan            Department of Physics
> Professor                  University of Alberta
> tel [phone]         11322 - 89 Avenue
> fax [phone]         Edmonton, AB, T6G 2G7, CANADA



--
Dmitri Pogosyan            Department of Physics
Professor                  University of Alberta
tel [phone]         11322 - 89 Avenue
fax [phone]         Edmonton, AB, T6G 2G7, CANADA