Re: [9fans] GeForece4 MX (Inno3D Tornedo)

[okamoto@granite.cias.osakafu-u.ac.jp]

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

I have two kinds of Nvidia cards, one is GeForece2 MX200(32MB), and
the other is GeForece4 MX(64MB), the latter of which was the card I
reported problem and solution.   For Geforece2 cards we have no
problem up to 1600x1200x32 to run with your new driver, which
recognizes the nvidia cards automatically.   In the case of our GeForce4
card, I think the problem was caused by the bug of the card itself.

Kenji

[-- Attachment #2: Type: message/rfc822, Size: 2866 bytes --]

From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] GeForece4 MX (Inno3D Tornedo)
Date: Tue, 15 Apr 2003 11:23:28 -0400
Message-ID: <2479282393cac7dbc85ee9dc2b22d590@plan9.bell-labs.com>

Do you have a bigger monitor?  I'd be interested to know
if the higher resolution modes work at all for you.

I tried a 0x0181 card recently and just could not get
it to do anything >= 1280x1024.  I made the clock
frequency change, but that wasn't enough.  It was as
though the "I am a mode < 1280 pixels wide" bit (0x04
in CRT 0x1A) was set, even though it was very clearly not set:
I could run in 1268x1024 just fine, but pushing it up to 1280
broke things.  Modes like 1600x1200 just gave completely
blank screens.

I traced through the VGA BIOS initializing the card
and still couldn't figure out what was going on in the
1280x1024 case.  The BIOS did not give 1600x1200 as a
mode option, though 1400x1050 was (and didn't shed any
light on the subject).  This was all in digital mode.

Finally I rewrote the driver to be almost exactly like
the XFree86 driver (even closer than the current one)
and then nothing worked, presumably because of some
bugs I introduced but didn't track down.  At this point
a week had gone by, and I gave up, threw out all the code
I'd changed, and just used VMware.  So much for Nvidia's
great backwards compatibility.

Sigh.