9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
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	[thread overview]
Message-ID: <2479282393cac7dbc85ee9dc2b22d590@plan9.bell-labs.com> (raw)
In-Reply-To: <ee0a291e865e2f470f4e538089d909aa@granite.cias.osakafu-u.ac.jp>

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.



  reply	other threads:[~2003-04-15 15:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-15  7:25 okamoto
2003-04-15  8:34 ` okamoto
2003-04-15  9:59   ` okamoto
2003-04-15 15:23     ` Russ Cox [this message]
2003-04-16  0:50       ` okamoto
2003-04-16  1:36         ` okamoto

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=2479282393cac7dbc85ee9dc2b22d590@plan9.bell-labs.com \
    --to=rsc@plan9.bell-labs.com \
    --cc=9fans@cse.psu.edu \
    /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).