public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Narancs 1 <narancs1@externet.hu>
Cc: kraxel@goldbach.in-berlin.de, linux-kernel@vger.kernel.org
Subject: Re: vesafb doesn't work in 240t10?
Date: Thu, 02 Nov 2000 05:23:09 -0500	[thread overview]
Message-ID: <3A01408D.6DBE85F9@mandrakesoft.com> (raw)
In-Reply-To: <Pine.LNX.4.02.10011021050140.10126-100000@prins.externet.hu>

Narancs 1 wrote:
> I used to start vesafb like this:
> /etc/lilo.conf:
> vga=317

> I want to start the kernel in 1024x768 16 bit
> How to do it?
> I've read Doc*/fb/vesafb.txt

vga takes a decimal number, but the number in vesafb.txt is
hexidecimal.  Let us convert 0x317 to decimal:

[jgarzik@rum linux_2_4]$ perl -e 'printf "%d\n", 0x317;'
791

So, use "vga=791" in your lilo.conf.

-- 
Jeff Garzik             | Dinner is ready when
Building 1024           | the smoke alarm goes off.
MandrakeSoft            |	-/usr/games/fortune
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2000-11-02 10:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-02  9:54 vesafb doesn't work in 240t10? Narancs 1
2000-11-02 10:23 ` Jeff Garzik [this message]
2000-11-02 10:35   ` Jan-Benedict Glaw
2000-11-02 10:38   ` Nick Holloway
2000-11-02 10:38   ` Brett
2000-11-02 14:15     ` Narancs 1
2000-11-02 14:25       ` Alan Cox
2000-11-02 16:20         ` so vesafb doesn't work in i815 Narancs 1
2000-11-02 16:27           ` Andre Hedrick
2000-11-02 17:51           ` Alan Cox
2000-11-03  8:00             ` Narancs 1
2000-11-03 13:13               ` Alan Cox
2000-11-03  7:32       ` vesafb doesn't work in 240t10? James Simmons

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=3A01408D.6DBE85F9@mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --cc=kraxel@goldbach.in-berlin.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=narancs1@externet.hu \
    /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