9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: simona@fspdc.uchicago.edu, 9fans@cse.psu.edu
Subject: Re: [9fans] Matrox Millenium oddities
Date: Fri,  9 Jun 2000 10:15:12 -0400	[thread overview]
Message-ID: <200006091415.KAA24520@cse.psu.edu> (raw)

[-- Attachment #1: Type: text/plain, Size: 237 bytes --]

Someone else just got a Millennium 2064W
going in 640x480x8 mode by first downloading
a flash BIOS upgrade from Matrox and then
using 0xC001E="IBM COMPATIBLE MATROX/MILLENNIUM VGA/VBE"
in their vgadb.

You might try that.

Russ

[-- Attachment #2: Type: message/rfc822, Size: 3328 bytes --]

From: Simon Allaway <simona@fspdc.uchicago.edu>
To: 9fans@cse.psu.edu
Subject: [9fans] Matrox Millenium oddities
Date: Fri, 9 Jun 2000 08:38:31 GMT
Message-ID: <393FEF00.49DB85DC@fspdc.uchicago.edu>

I have a test machine that's using a reasonably old Matrox Millenium
video card. I can see fromvgadb that the MGA chipset is supported, but
using version 2164W. The card I have has 2064W stamped on it.

So, I tried editing vgadb:

ctlr
        0xC002D="MATROX/MILLENNIUM  VGA/VBE BIOS (V2.2 )"       #
Millennium
        0xC002D="MATROX/MISTRAL  VGA/VBE BIOS (V1."             #
Millennium II
        link=vga
        ctlr=mga2064w linear=1
        hwgc=mga2064whwgc

This cause aux/vga to hang.

The result of aux/vga -pv :

aux/vga: controller not in /lib/vgadb
0xC0000 55 AA 40 EB 7B 22 72 03 C0 04 00 19 2E 3E 3A 19
U.@.{"r......>:.
0xC0010 44 19 FF FF 00 00 00 00 60 00 00 00 00 20 49 42  D.......`....
IB
0xC0020 4D 20 43 4F 4D 50 41 54 49 42 4C 45 20 4D 41 54  M COMPATIBLE
MAT
0xC0030 52 4F 58 2F 4D 49 4C 4C 45 4E 4E 49 55 4D 20 20  ROX/MILLENNIUM
0xC0040 56 47 41 2F 56 42 45 20 42 49 4F 53 20 28 56 32  VGA/VBE BIOS
(V2
0xC0050 2E 32 20 29 00 87 DB 87 DB 87 DB 87 DB 87 DB 90  .2
)............
0xC0060 50 43 49 52 2B 10 19 05 00 00 18 00 00 00 00 03
PCIR+...........
0xC0070 40 00 00 00 00 80 00 00 38 33 38 2D 31 32 00 FF
@.......838-12..
0xC0080 E8 0D 61 8B D8 E8 9E 61 74 22 8C C8 3D 00 C0 74
...a....at"..=..t
0xC0090 1B B0 04 2E A2 02 00 33 C0 33 F6 B9 FF 07 2E 02
........3.3......
0xC00A0 04 46 E2 FA F6 D8 2E 88 04 33 C0 CB 55 33 C0 8E
..F.......3..U3..
0xC00B0 D8 8E C0 E8 6D 63 E8 2D 67 53 B0 40 E8 2B 00 5B
.....mc.-gS.@.+.[
0xC00C0 E8 B1 67 FC BA D4 03 E8 17 33 B8 00 A0 8E C0 BF
...g......3......
0xC00D0 00 20 B9 00 C0 33 C0 F3 AA 8E C0 E8 09 33 B8 03  .
....3.......3..
0xC00E0 00 CD 10 E8 4C 02 5D 33 C0 CB FA C7 06 08 01 65
.....L.]3.......e
0xC00F0 F0 C7 06 0A 01 00 F0 C7 06 40 00 60 19 8C 0E 42
..........@.`...B

Have I missed something obvious?

Thanks in advance.

Simon

             reply	other threads:[~2000-06-09 14:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-06-09 14:15 Russ Cox [this message]
2000-06-09 14:52 ` Roman V. Shaposhnick
2000-06-09 16:19 ` Brian Wheeler
2000-06-12  9:57   ` Sim IJskes
  -- strict thread matches above, loose matches on Subject: below --
2000-06-09 16:42 Russ Cox
2000-06-12 10:08 ` Douglas A. Gwyn
2000-06-09 15:09 Russ Cox
2000-06-09  8:38 Simon Allaway

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=200006091415.KAA24520@cse.psu.edu \
    --to=rsc@plan9.bell-labs.com \
    --cc=9fans@cse.psu.edu \
    --cc=simona@fspdc.uchicago.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).