From: "Richard Greenblott" <reggreen@ne.mediaone.net>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] Nvidia video driver
Date: Mon, 16 Apr 2001 22:03:10 -0400 [thread overview]
Message-ID: <001701c0c6e2$8d652ae0$1e8c1e42@ne.mediaone.net> (raw)
In-Reply-To: <15067.31564.353932.201731@nido.hilbert.space>
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.
----- Original Message -----
From: <paurea@dei.inf.uc3m.es>
Newsgroups: comp.os.plan9
Sent: Monday, April 16, 2001 7:23 PM
Subject: Re: [9fans] Nvidia video driver
> Richard Greenblott writes:
> > From: "Richard Greenblott" <reggreen@ne.mediaone.net>
> > Subject: Re: [9fans] Nvidia video driver
> > Date: Sun, 15 Apr 2001 23:11:34 -0400
> >
> > Hi:
> >
> > Thanks you for the binaries. But I still am having problems with my
> > Display driver.
> > When I boot it stops with and unknown controller "nvidia" error.
> >
> I had the same problem as you, and it was that I hadn't modified
> /sys/src/cmd/vga/data.c. The steps to follow are:
>
>
> I have:
> Copied the vganvidia.c supplied to /sys/src/9/pc
>
> Added vganvidia +cur to pcdisk
>
> Compiled 9pcdisk.gz
>
> Copied it to an installation disk.
>
>
> Copied the nvidia.c supplied to /sys/src/cmd/vga
>
> Added nvidia.$O\ to the mkfile of vga
>
> Added extern Ctlr nvidia; and
>
> extern Ctlr nvidiahwgc; to vgadb.h
>
> and extern Ctlr nvidia; to vga.h
>
> Compiled it. Installed it.
> An added an entry in vgadb for my
> card: (yours differs)
>
> ctlr 0xC0072 "Diamond Viper 550"
> ctlr nvidia
> ctlr nvidiahwgc
> link=vga
>
> add a pair of entries in the array in data.c
> similar to the ones of the other drivers.
> --
> /"\
> \ / ascii ribbon campaign - against html mail
> X - against ms attachments
> / \
>
next prev parent reply other threads:[~2001-04-17 2:03 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 [this message]
2001-04-17 8:48 ` Nicholas Waples
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='001701c0c6e2$8d652ae0$1e8c1e42@ne.mediaone.net' \
--to=reggreen@ne.mediaone.net \
--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).