mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Giuseppe Bilotta <bilotta78@hotpop.com>
To: linux-kernel@vger.kernel.org
Subject: Framebuffer with nVidia GeForce 2 Go on Dell Inspiron 8200
Date: Wed, 10 Mar 2004 23:38:02 +0000 (UTC)	[thread overview]
Message-ID: <c2o8sp$h3j$1@sea.gmane.org> (raw)

Date: Thu, 11 Mar 2004 00:37:58 +0100
Message-ID: <MPG.1ab9c538eb2f9b69989681@news.gmane.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-15"
Content-Transfer-Encoding: 7bit
X-Newsreader: MicroPlanet Gravity v2.60

Hello,

I have recently started to migrate to Linux on my DELL laptop; 
everything is going pretty smoothly, but one thing I can't seem to 
enable is the framebuffer to take advantage, in console, of the high 
resolution my video card and monitor can afford.

The video card is an nVidia GeForce 2 Go, on a Dell Inspiron 8200, 
and the monitor is their UXGA monitor (1600x1200). The system BIOS is 
version A11, which means the video card BIOS is up to version 
3.11.01.44.D1.

The system I'm running is a Debian testing/unstable updated every two 
or three days.

I tried the following things with the kernels 2.4.22, 2.6.0, 2.6.1, 
2.6.2, 2.6.3 (self-compiled) more or less always with the same 
results:

1. The vga framebuffer works. I can even bring the monitor to 800x600 
in tweaked VGA mode.

2. The VESA framebuffer does not work. Apparently, the card is not 
detected as VESA-compatible. (I'm not 100% sure about this --how can 
I check if this is indeed the case?)

3. The Riva framebuffer doesn't work either. It detects the video 
card all right, understands that I'm running on a laptop and thus 
with an LCD monitor, but as soon as I "touch" it (be it even just 
with a fbset -i to find the information), the screen goes blank or 
has some very funny graphical effects (fade to black in the middle, 
etc). The system doesn't lock up (I can still blind-type and reset 
it), but I can't use it.

Does anybody know what could be wrong?


The only thing which I can think of is that even Windows drivers have 
problems with this particular setup; the only documentation I could 
find on the matter is here

http://www.laptopvideo2go.com/

(Go to "Dell laptop owners")

HTH,

-- 
Giuseppe "Oblomov" Bilotta

Can't you see
It all makes perfect sense
Expressed in dollar and cents
Pounds shillings and pence
                  (Roger Waters)


             reply	other threads:[~2004-03-10 23:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-10 23:38 Giuseppe Bilotta [this message]
2004-03-11  1:14 ` James Simmons
2004-03-11 10:51   ` Giuseppe Bilotta
2004-03-15 21:56     ` Giuseppe Bilotta
2004-03-17 22:03       ` James Simmons
2004-03-17 22:46         ` Giuseppe Bilotta
2004-03-17 23:06           ` James Simmons
2004-03-17 23:25             ` Giuseppe Bilotta
2004-06-20 17:55         ` Giuseppe Bilotta

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='c2o8sp$h3j$1@sea.gmane.org' \
    --to=bilotta78@hotpop.com \
    --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

all inboxes | Powered by JetHome®