From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: linux-kernel@vger.kernel.org
Subject: Re: vesafb doesn't work in 240t10?
Date: Thu, 2 Nov 2000 11:35:23 +0100 [thread overview]
Message-ID: <20001102113522.B14851@lug-owl.de> (raw)
In-Reply-To: <Pine.LNX.4.02.10011021050140.10126-100000@prins.externet.hu> <3A01408D.6DBE85F9@mandrakesoft.com>
In-Reply-To: <3A01408D.6DBE85F9@mandrakesoft.com>; from jgarzik@mandrakesoft.com on Thu, Nov 02, 2000 at 05:23:09AM -0500
[-- Attachment #1: Type: text/plain, Size: 690 bytes --]
On Thu, Nov 02, 2000 at 05:23:09AM -0500, Jeff Garzik wrote:
> Narancs 1 wrote:
> > I used to start vesafb like this:
> > /etc/lilo.conf:
> > vga=317
> vga takes a decimal number, but the number in vesafb.txt is
> hexidecimal. Let us convert 0x317 to decimal:
> So, use "vga=791" in your lilo.conf.
lilo accepts hex values as well, AFAIK, so lets do:
vga = 0x317
MfG, JBG
--
Fehler eingestehen, Größe zeigen: Nehmt die Rechtschreibreform zurück!!!
/* Jan-Benedict Glaw <jbglaw@lug-owl.de> -- +49-177-5601720 */
keyID=0x8399E1BB fingerprint=250D 3BCF 7127 0D8C A444 A961 1DBD 5E75 8399 E1BB
"insmod vi.o and there we go..." (Alexander Viro on linux-kernel)
[-- Attachment #2: Type: application/pgp-signature, Size: 240 bytes --]
next prev parent reply other threads:[~2000-11-02 10:35 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
2000-11-02 10:35 ` Jan-Benedict Glaw [this message]
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=20001102113522.B14851@lug-owl.de \
--to=jbglaw@lug-owl.de \
--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