From: "Dmitri Pogosyan" <pogosyan@phys.ualberta.ca>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Re: I took the plunge with kde
Date: Sat, 5 Sep 2009 17:10:14 -0600 [thread overview]
Message-ID: <200909052310.n85NAEw27373@webmail.phys.ualberta.ca> (raw)
> 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, but may have non-standard codes.
I run laptop 1440x900x16 (vga=0x36a) and desktop monitor at 1680x1050x32
(vga=0x369).
vbespy from the bottom of
http://en.wikipedia.org/wiki/VESA_BIOS_Extensions
allows the detection of supported VESA modes on your card.
Be careful to convert VESA mode codes reported by vbespy to kernel codes
that vga= parameter takes. Transformation is to add 512, and, optionally
convert to hex.
i.e for me vbespy reports 1680x1050 (8,8,8) vesa mode as 361 (decimal). Kernel
mode is 361+512=873=0x369 in hex
>
> 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 1-780-492-2150 11322 - 89 Avenue
fax 1-780-492-0714 Edmonton, AB, T6G 2G7, CANADA
next reply other threads:[~2009-09-05 23:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-05 23:10 Dmitri Pogosyan [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-09-05 23:26 [gentoo-amd64] Re: I took the plunge with kde Dmitri Pogosyan
2009-09-05 22:57 Dmitri Pogosyan
2009-09-05 22:46 Dmitri Pogosyan
2009-09-05 11:43 [gentoo-amd64] " Paul Stear
2009-09-05 20:23 ` [gentoo-amd64] " Nikos Chantziaras
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=200909052310.n85NAEw27373@webmail.phys.ualberta.ca \
--to=pogosyan@phys.ualberta.ca \
--cc=gentoo-amd64@lists.gentoo.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