From: Nicholas Waples <nickw@pobox.com>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] Nvidia video driver
Date: Tue, 17 Apr 2001 18:48:19 +1000 [thread overview]
Message-ID: <Pine.LNX.4.31.0104171811370.603-100000@localhost> (raw)
In-Reply-To: <001701c0c6e2$8d652ae0$1e8c1e42@ne.mediaone.net>
On Mon, 16 Apr 2001, Richard Greenblott wrote:
> Ok. I still can not get this to work...
> One problem I have is that I can not rebuild software for Plan9 until I can
> load Plan9 (catch 22).
> I don't have a Plan9 system to build from...
>
> I have copied 9PCFLOP to the floppy and modified Vgadb on the same floppy as
> stated in my last posting.
> Is there anything else I can do? paurea@dei.inf.uc3m.es did say he had to
> rebuild the software to make it work.
> Is the posted files at http://members.optusnet.com.au/~nwaples/ Ok to use or
> do I need to rebuild them for my Video Board?
>
> Sorry for sounding like a broken record.....
>
> Thanks for any help you can give...
>
> Rick G.
>
Well, as a test to make sure it all worked, I did it from scratch myself.
What i did was -
- download and create the floppy from main plan9 site
- modified vgadb on the floppy to add entry for my nvidia video card.
There was already an entry for nvidia cards (though it doesnt
seem to have been built in the kernel yet), so I just added the entry
for my card
diff /tmp/vgadb vgadb
300a301
> 0xC0072="Diamond Viper V550" # NVIDIA TNT
The nvidia section now looks like
ctlr
0xC00A2="NVIDIA TNT2 Model 64 BIOS V2.05.13 " # NVIDIA TNT Model 64
0xC0072="Diamond Viper V550" # NVIDIA TNT
link=vga
ctlr=nvidia linear=1
hwgc=nvidiahwgc
- downloaded 9pcflop.gz from
http://members.optusnet.com.au/~nwaples/binaries/ , and replaced the
one on the boot floppy with this.
After this it all worked for me.
The error message you saw,
sequencer->enter on
sequencer->leave on
dbctlr: unknown controller "nvidia" ctlr
would happen if the driver wasnt built into the kernel. That shouldnt
happen with the kernel I built.
I even uploaded the floppy image I used (nvidia.9fd) if you still cant
get it to work.
Nick.
next prev parent reply other threads:[~2001-04-17 8:48 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-31 3:37 jmk
2001-03-31 12:25 ` Richard Greenblott
2001-04-02 17:37 ` Nicholas Waples
2001-04-04 17:04 ` Richard Greenblott
2001-04-11 7:42 ` Nicholas Waples
2001-04-12 2:53 ` Richard Greenblott
2001-04-12 3:38 ` Nicholas Waples
2001-04-16 3:11 ` Richard Greenblott
2001-04-16 23:07 ` paurea
2001-04-17 2:03 ` Richard Greenblott
2001-04-17 8:48 ` Nicholas Waples [this message]
2001-04-18 16:55 ` Richard Greenblott
2001-04-23 9:53 ` Richard Greenblott
-- strict thread matches above, loose matches on Subject: below --
2001-04-24 13:37 jmk
2001-04-23 14:25 jmk
2001-04-24 9:01 ` Richard Greenblott
2001-04-24 9:02 ` Douglas A. Gwyn
2001-04-18 17:07 jmk
2001-04-16 3:18 rsc
2001-04-05 3:56 Russ Cox
2001-04-05 3:46 okamoto
2001-04-02 17:25 nemo
2001-04-02 10:06 paurea
2001-03-31 2:20 Nicholas Waples
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=Pine.LNX.4.31.0104171811370.603-100000@localhost \
--to=nickw@pobox.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).