Juste les carte faites par ATI, pas les

Voici les mails parlant de ca sur la ml:
From: Roman Stepanov <roman@visquez.com>
Subject: [Dri-devel] Re: New ATI FireGL drivers announced
To: Alexander Stohr <AlexanderS@ati.com>
Cc: dri-devel@lists.sourceforge.net
Date: 2002年11月22日 15:02:31 +0300

Hi, Alexander!
[ snip ]

At first I attempted to set up SuSE's xfglrx package to get 3D acceleration
for my Gigabyte AP64D board (actually it is a R200 QL with 64 Mb DDR RAM).
After generating XF86Config and typing startx in command prompt X server
failed to start. I found in system logs that 2D driver refused to
work with third party boards. It's nearly impossible to buy "build by ATI"
board in Moscow, so I was forced to apply my assembly skills to modify board
vendor id in 2D driver (fglrx_drv.o). After replacing ATI's id (0x1002) with
Gigabyte (0x1458) I was able to start XFree but I saw my text consoles
(vga=791) broken. Next thing I've tried is to start Tux Racer game. After 2
minutes of pretty smooth gameplay it hung and my box locked up completely.
I decided it's enough to uninstall this package and I started to look around
for any alternative driver. I've downloaded official ATI driver version
2.4.0 and tried to install it. After install script built kernel drm modules
installation stopped because depmod complained about unresolved symbols in
module fglrx.o That was my last attempt to use official ATI drivers :(

Now I have installed driver from dri trunk, it works pretty well, but I have
very slow gameplay with Loki's Rune. Maybe today I will try to install
official ATI driver again, this time version 2.4.3. I hope it finally going
to work.

******** FIN du premier mail ********
Reponse:
From: Alexander Stohr <AlexanderS@ati.com>
Subject: RE: [Dri-devel] Re: New ATI FireGL drivers announced
To: Roman Stepanov <roman@visquez.com>
Cc: dri-devel@lists.sourceforge.net
Date: 2002年11月22日 13:43:31 +0100

[snip]
for completeness its: R200/RV250/R300/some-Mobility
[snip les quotes qui parle du drivers qui se lance pas]
That's Intentional. On the list you can find several references to
problems with the multiple OEM BIOS variants even with the DRI drivers.
Since this must be considered as third party software and hardware,
you should consider calling the respective vendor for support.
(Having a broken BIOS checksum is the least problem in that area...)
[snip quotes qui parlent du changement du code hexa]
This might be a BIOS problem. Current drivers are using the
XFre86 Int10 module for doing mode switches. Thanks for another
reason for not letting that drivers run on third party boards.
[snip]

Stability of a specifc grafics board is mainly due to its
clock rate, its RAM bus interface clock an signal quality
plus misc power supply parameters (mainboard abilities to
drive that board, PCB design to ensure the voltage does not
drop critical in any operation thermal and electrical condtion).

I know that ATI is ensuring this for the "Built by ATI" boards
with much effort, but i have no idea how intense those third
party vendors do that. The second unknown thing is your hosting
PC system. You should verify it with a secondary operating system.

[snip]
> Now I have installed driver from dri trunk, it works pretty
> well, but I have very slow gameplay with Loki's Rune.

Thats the best and only drivers that should use for your adapter.

> Maybe today I will try to install official ATI driver again,
> this time version 2.4.3. I hope it finally going to work.

What you were doing is "unsupported" and "not recommended".
This is meaning that it is on your own risk if you do it.
Maybe there are legal reasons why you shouldn't be allowed
to do that, but i dont know this myselves.

-Alex.
*** fin ***

Desolé si c'est super long, ya bien qq1 qui me mettra a -1 pour caché ca des yeux de ceux qui ne veulent pas voir ca!