From: "Keith Nash" <k.j.nash@usa.net>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] ATI Xpert98 "OEM" Edition - doesn't work with Plan9
Date: Wed, 7 Feb 2001 21:24:28 +0000 [thread overview]
Message-ID: <003d01c0914c$5b796bc0$0100a8c0@r4hvy> (raw)
In-Reply-To: <200102071706.MAA32735@smtp4.fas.harvard.edu>
Thanks for the help - the installation is now one step forward. It tries to
switch to graphics, but then produces garbage. My monitor (a Dell M770,
Hsync 30-69 kHz, Vsync 48-160Hz) just says "Signal Out Of Range". I haven't
got a 'scope so I can't examine the signals. I notice that in the default
PLAN9.INI, the monitor is selected as "multisync75". In case this is the
problem, I tried changing this to "micron-17FGx", since the frequency range
for this monitor is stated in VGADB to lie within the range of my M770. No
difference. Any suggestions?
Best wishes,
Keith.
----- Original Message -----
From: Russ Cox <rsc@plan9.bell-labs.com>
To: <9fans@cse.psu.edu>; <k.j.nash@usa.net>
Sent: Wednesday, February 07, 2001 5:06 PM
Subject: Re: [9fans] ATI Xpert98 "OEM" Edition - doesn't work with Plan9
> The Xpert98 should work; hopefully all that's
> wrong is the recognition of the card for what it is.
>
> After making the boot disk, edit a:\vgadb
> and look for the section with all the Mach64
> entries.
>
> Add the marked line (without the >>>)
>
> 0xC0000-0xC0200="MACH64GB"
> 0xC0000-0xC0200="MACH64GM"
> >>> 0xC0000-0xC0200="MACH64GR"
> 0xC0000-0xC0200="MACH64GZ"
>
> and try booting again.
>
> Russ
>
next prev parent reply other threads:[~2001-02-07 21:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-07 17:06 Russ Cox
2001-02-07 21:24 ` Keith Nash [this message]
2001-02-08 0:40 ` [9fans] ATI Xpert98 "OEM" Edition Keith Nash
2001-02-08 9:43 ` Douglas A. Gwyn
-- strict thread matches above, loose matches on Subject: below --
2001-02-09 18:28 [9fans] ATI Xpert98 "OEM" Edition - doesn't work with Plan9 Russ Cox
2001-02-12 10:24 ` Douglas A. Gwyn
2001-02-07 20:11 forsyth
2001-02-07 9:55 Keith Nash
2001-02-08 9:42 ` 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='003d01c0914c$5b796bc0$0100a8c0@r4hvy' \
--to=k.j.nash@usa.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).