9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Douglas A. Gwyn" <gwyn@arl.army.mil>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] ATI Xpert98 "OEM" Edition - doesn't work with Plan9
Date: Thu,  8 Feb 2001 09:42:12 +0000	[thread overview]
Message-ID: <3A81995A.83A9D856@arl.army.mil> (raw)
In-Reply-To: <003b01c090ec$0d7dbe40$0100a8c0@r4hvy>

Keith Nash wrote:
> I have obtained an ATI Xpert 98 "OEM" card.  Like the real Xpert 98 it uses
> the Rage XL chipset and has 8Mb of RAM.

According to ATI's Web site before its recent restructuring,
there are actually a couple of different chipsets (XL vs. LT PRO)
used for products named "Xpert 98".

> 0xC0080  CB 90 90 0D 0A 41 54 49 20 52 41 47 45 20 53 44   .....ATI RAGE SD
> 0xC0090  52 41 4D 20 42 49 4F 53 20 50 2F 4E 20 31 31 33   RAM BIOS P/N 113
> Is there any way to get this card to work with Plan9?

Yes, the Plan 9 installation guide (troubleshooting section)
should explain how to do this.  Basically, edit vgadb to
add another entry that matches a unique portion of the BIOS,
e.g. at C0085 "ATI RAGE SDRAM".  Then it might either work or
"sort of" work, the latter case consisting of bad framing in
Rio (multiple panes, tearing, or something of the sort), in
which case the MACH64 driver needs to be hacked to use
different timing.  (Probably easier to get somebody in the US
to ship you a retail Xpert 98.)  Don't forget there are two
vgadb files, one on the floppy and one in /n/9fat (use Plan 9
command "9fat:" before trying to edit the latter); once you
have the system running you need to also fix up the /n/9fat
version and reboot.


  reply	other threads:[~2001-02-08  9:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-07  9:55 Keith Nash
2001-02-08  9:42 ` Douglas A. Gwyn [this message]
2001-02-07 17:06 Russ Cox
2001-02-07 21:24 ` Keith Nash
2001-02-07 20:11 forsyth
2001-02-09 18:28 Russ Cox
2001-02-12 10:24 ` Douglas A. Gwyn

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=3A81995A.83A9D856@arl.army.mil \
    --to=gwyn@arl.army.mil \
    --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).