From: jmk@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] nvidia problems
Date: Wed, 23 Jul 2003 19:53:56 -0400 [thread overview]
Message-ID: <5ca3fbd9eb4e3acfb26fe90f76505b61@plan9.bell-labs.com> (raw)
In-Reply-To: <3F1F1B8D.1040300@Princeton.EDU>
[-- Attachment #1: Type: text/plain, Size: 217 bytes --]
yes, that was my conclusion too and i've sent him a patched
aux/vga to try.
in the pci listing he gave, all but the 3com ethernet have an
nvidia vid. i didn't know nvidia made anything other than graphics
chips.
[-- Attachment #2: Type: message/rfc822, Size: 3206 bytes --]
From: Martin Harriss <martin@Princeton.EDU>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] nvidia problems
Date: Wed, 23 Jul 2003 19:34:37 -0400
Message-ID: <3F1F1B8D.1040300@Princeton.EDU>
Seen this before with an S3 video card. The system that it was
installed in also had an S3 sound card (unsupported by plan 9, but in
the machine for use by Windows.) Plan 9 confused the sound card with an
S3 video card. I posted a fix and the good folks at the Labs put it in
the distribution. If you look in the S3 driver code it should be
obvious what to do.
Martin
Martin Althoff wrote:
> Oops, big typo...
>
>
>>pcirouting: Southbridge 10DE/01E0 not found
>>and then later ignoring that.
>>The same DID as the TNT2...
>
> should read:
> same _assumed_ DID (01E0).
> The matching (first) VID (10DE) seems to trip hunt for a vga card.
>
>
next prev parent reply other threads:[~2003-07-23 23:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-23 15:54 david presotto
2003-07-23 15:33 ` jmk
2003-07-23 21:08 ` Re[2]: " Martin Althoff
2003-07-23 21:16 ` Re[3]: " Martin Althoff
2003-07-23 23:34 ` Martin Harriss
2003-07-23 23:53 ` jmk [this message]
2003-07-23 21:23 ` Re[2]: " jmk
2003-07-23 21:25 ` jmk
2003-07-24 8:42 ` Ram'on Garc'ia Fern'andez
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=5ca3fbd9eb4e3acfb26fe90f76505b61@plan9.bell-labs.com \
--to=jmk@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).