TIP: Click on subject to list as thread! ANSI
echo: os2hardware-l
to: Eddy Thilleman
from: Kris Steenhaut
date: 1999-08-30 14:28:22
subject: Matrox drivers?

Hello Eddy,
donderdag 26 augustus 1999 11.15, Eddy Thilleman wrote to Kris Steenhaut:

 ET> Hi Kris,

 ET> 19 Aug 99, Kris Steenhaut of 2:292/8125.11 wrote to Mike Roark:

 KS>> more detailed survey about the Matrox problems was mailed by
 KS>> Daniela Engert.

 ET> Could you email that to me? Or post it here if it's not too long.

It's in the readme Danis506.add beta 7:


++++ Knip.....Begin van het bestand y:1.1 .....++++
If there is a PCI EIDE controller in your system, and you happen to
have a Matrox video board, then the boot process might just stop at a
certain point or fail with a trap 8. This is due to a horribly nasty
behaviour of the Matrox driver wich scans all ports with addresses Cx0yh
(x = 0..F, y = 0..3) at initialization of the base video handler even if
these addresses are not assigned to the video board. I wouldn't call it
playing by the rules beating the bush and looking if some sort of MGA
drops out of it.

If any other PCI device gets assigned addresses matching the above pattern,
*anything* can happen. To work around this problem, I have added a new
option /MGAFIX which detects EIDE hardware with addresses affected by that,
and tries to push them away a little by reprogramming the address decoders
so that they are no longer potential scan targets.

++++ Knip.....Einde van het bestand y:1.1 .....++++


On my system here, the /MGAFIX trick doesn't work, btw.

And I do have the "anything could happen" feature. ((-:


    Groeten uit Gent,
    Regards/2

      Kris

--- GoldED/2 3.0.1  FMail/2 1.48/g
* Origin: From Flanders Fields (2:292/8125.11)

SOURCE: echoes via The OS/2 BBS

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.