linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Valdis.Kletnieks@vt.edu
To: "David St.Clair" <dstclair@cs.wcu.edu>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.0-test1 Vesa fb and Nvidia
Date: Wed, 16 Jul 2003 16:33:29 -0400	[thread overview]
Message-ID: <200307162033.h6GKXTup002619@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Wed, 16 Jul 2003 16:13:16 EDT." <1058386396.3710.4.camel@localhost>

[-- Attachment #1: Type: text/plain, Size: 973 bytes --]

On Wed, 16 Jul 2003 16:13:16 EDT, "David St.Clair" <dstclair@cs.wcu.edu>  said:
> I don't know if this is a hardware specific bug or I just don't have
> something configured right.

2.6.0-test1-mm1, Dell C840 laptop with a Geforce4 440Go.

I do *NOT* have 'CONFIG_FB_VGA16' set, but *do* have 'CONFIG_VIDEO_VESA'.

With this, 'vga=794' gets me a small font and a penguin on boot,
the NVidia binary driver works fine under X  after the minion.de patch,
switching back and forth works well, and life is generally good.

Mode 792 is in the VESA bios mode range: from Documentation/svga.txt:

   0x0200 to 0x08ff - VESA BIOS modes. The ID is a VESA mode ID increased by
        0x0100. All VESA modes should be autodetected and shown on the menu.
....
   CONFIG_VIDEO_VESA - enables autodetection of VESA modes. If it doesn't work
on your machine (or displays a "Error: Scanning of VESA modes failed" message),
you can switch it off and report as a bug.

Try turning that on?


[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]

  reply	other threads:[~2003-07-16 20:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-16 20:13 2.6.0-test1 Vesa fb and Nvidia David St.Clair
2003-07-16 20:33 ` Valdis.Kletnieks [this message]
2003-07-16 21:31   ` David St.Clair
2003-07-17 18:03 ` James Simmons
2003-07-17 18:30   ` David St.Clair

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=200307162033.h6GKXTup002619@turing-police.cc.vt.edu \
    --to=valdis.kletnieks@vt.edu \
    --cc=dstclair@cs.wcu.edu \
    --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;
as well as URLs for NNTP newsgroup(s).