Re: [9fans] Matrox Millenium oddities

Re: [9fans] Matrox Millenium oddities

[Russ Cox]

[-- 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

Re: [9fans] Matrox Millenium oddities

[Roman V. Shaposhnick]

On Fri, Jun 09, 2000 at 10:15:12AM -0400, Russ Cox wrote:
> Someone else just got a Millennium 2064W

  And what about Millennium G400 ? Any chances ?

Thanks,
Roman.

Re: [9fans] Matrox Millenium oddities

[Brian Wheeler]

In article <200006091415.KAA24520@cse.psu.edu>,
	rsc@plan9.bell-labs.com (Russ Cox) writes:
> This is a multi-part message in MIME format.
> --upas-hwhpkkwubdqxidhpdpnsohvvza
> Content-Disposition: inline
> Content-Type: text/plain; charset="US-ASCII"
> Content-Transfer-Encoding: 7bit
>
> 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

Maybe this is a dumb question...I editted the floppy vgadb file
(I had the Matrox Millenium 2.3 version instead of 2.5) and when plan9 comes
up from the hard disk, the vgadb on the disk doesn't have my changes and
aux/vga fails...

Did I miss something very obvious?  I'm pretty new to plan9...

Brian Wheeler
bdwheele@indiana.edu


>
> --upas-hwhpkkwubdqxidhpdpnsohvvza
> Content-Type: message/rfc822
> Content-Disposition: inline
>
> Received: from plan9.cs.bell-labs.com ([135.104.9.2]) by plan9; Fri Jun  9 05:05:11 EDT 2000
> Received: from cse.psu.edu ([130.203.3.50]) by plan9; Fri Jun  9 05:05:10 EDT 2000
> Received: from localhost (majordom@localhost)
> 	by cse.psu.edu (8.8.8/8.8.8) with SMTP id EAA18247;
> 	Fri, 9 Jun 2000 04:46:32 -0400 (EDT)
> Received: by claven.cse.psu.edu (bulk_mailer v1.5); Fri, 9 Jun 2000 04:46:06 -0400
> Received: (from majordom@localhost)
> 	by cse.psu.edu (8.8.8/8.8.8) id EAA18209
> 	for 9fans-outgoing; Fri, 9 Jun 2000 04:46:00 -0400 (EDT)
> X-Authentication-Warning: claven.cse.psu.edu: majordom set sender to owner-9fans using -f
> Received: from mercury.bath.ac.uk (mercury.bath.ac.uk [138.38.32.81])
> 	by cse.psu.edu (8.8.8/8.8.8) with ESMTP id EAA18204
> 	for <9fans@cse.psu.edu>; Fri, 9 Jun 2000 04:45:55 -0400 (EDT)
> Received: from news by mercury.bath.ac.uk with local (Exim 3.12 #1)
> 	id 130KJP-0004vv-00
> 	for 9fans@cse.psu.edu; Fri, 09 Jun 2000 09:38:43 +0100
> Received: from GATEWAY by bath.ac.uk with netnews
> 	for 9fans@cse.psu.edu (9fans@cse.psu.edu)
> To: 9fans@cse.psu.edu
> Date: Fri, 9 Jun 2000 08:38:31 GMT
> From: Simon Allaway <simona@fspdc.uchicago.edu>
> Message-ID: <393FEF00.49DB85DC@fspdc.uchicago.edu>
> Organization: The University of Chicago
> Content-Type: text/plain; charset=us-ascii
> Content-Transfer-Encoding: 7bit
> Subject: [9fans] Matrox Millenium oddities
> Sender: owner-9fans@cse.psu.edu
> Reply-To: 9fans@cse.psu.edu
> Precedence: bulk
>
> 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
> --upas-hwhpkkwubdqxidhpdpnsohvvza--

Re: [9fans] Matrox Millenium oddities

[Sim IJskes]

Brian Wheeler wrote:

> Maybe this is a dumb question...I editted the floppy vgadb file
> (I had the Matrox Millenium 2.3 version instead of 2.5) and when plan9 comes
> up from the hard disk, the vgadb on the disk doesn't have my changes and
> aux/vga fails...
>
> Did I miss something very obvious?  I'm pretty new to plan9...
>
> Brian Wheeler
> bdwheele@indiana.edu

What you could do:

put floppy in drive A and type the following
a: (to mount /n/a:)
mv /lib/vgadb /lib/vgadb.orig
cp /n/a:/vgadb /lib

and then start rio again (or reboot, after 'disk/kfscmd halt')

Gr. Sim

Re: [9fans] Matrox Millenium oddities

[Douglas A. Gwyn]

Russ Cox wrote:
> After booting the installation and
> rio fails, put the floppy back and type
>         a:
>         disk/kfscmd allow
>         cp /n/a:/vgadb /lib/vgadb
>         disk/kfscmd disallow
>         disk/kfscmd halt
> and then reboot the system.

When I was doing stuff like that, disk/kfscmd was inoperative,
so unless something has changed, your best bet might be to

cp /n/a:/vgadb /tmp
bind -b /tmp /lib	# causes /tmp/vgadb to become /lib/vgadb
vga -l 800x600x8

or incantations to that effect.

Re: [9fans] Matrox Millenium oddities

[Russ Cox]

That's a good point.  Currently, if you
edit vgadb to get yourself booted,
you'll have to copy it over from the
floppy yourself once you're installed.

After booting the installation and
rio fails, put the floppy back and type
	a:
	disk/kfscmd allow
	cp /n/a:/vgadb /lib/vgadb
	disk/kfscmd disallow
	disk/kfscmd halt
and then reboot the system.

Rebooting isn't strictly necessary
(you run run the rest of /rc/bin/termrc
by hand) but it's the surest way to test that
it will work the next time.

We'll try to have the install program do
that automatically sometime soon.

Russ

Re: [9fans] Matrox Millenium oddities

[Russ Cox]

  And what about Millennium G400 ? Any chances ?

Not without some work, unfortunately.
I tried to bring up a Millennium G200 a
couple days ago with no luck.

Russ

[9fans] Matrox Millenium oddities

[Simon Allaway]

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