Problems With OEM ATI Cards And ATI's Linux Driver
Doug Bostrom writes "Over at FlightGear.org, Andy Ross describes how ATI's new Linux drivers only seem to work with "official" ATI cards (made by ATI), why that does not make sense, and a possible fix that unfortunately would mean booting Windows, if only for a few minutes."
According to the message posted, the utility used to reflash the BIOS runs in DOS, not Windows, and will work in FreeDOS
There are a few possible explanations for this rather odd driver situation...
I know this is rumor-mongering, but I can't help but notice that the *Windows* drivers dont' perform such a check, and neither do the Linux Retail drivers...
Consider this: Microsoft or some other party requests unofficially that ATi *not* support Linux in its OEM hardware, just for the sake of not having OEM desktop vidcard support for Linux...this could explain things like the OEM/Retail check that occurs in Linux, but not Windows. Interesting stuff..I want to see what ATI's reaction on this is.
------- "From bored to fanboy in 3.8 asian girls" ----------
This is probably a very good argument for non-binary, truly open-source drivers...
/* affect != effect */ void affect(int *thing,int effect) { *thing += effect; }
I've been hearing about bad ATI drivers since the days of the 80386. I've had some severe problems with ATI drivers myself, and needed to call ATI tech support. My impression is that the company should not allow receptionists to write drivers when they are not answering phones.
My answer: For business use, buy Matrox.
Nvidia drivers for linux are really good but So are Matrox's. Matrox write some bitchen drivers like Nvidia but unlike Nvidia they GPL the whole thing. Getting all the windows functionality in linux for both my GF4 and G400 cards is perfectly easy. I advise buying from those two companies for linux. Matrox cards though old are very nice because they are cheap and they have good linux duel head support.
unzip; strip; touch; finger; mount; fsck; more; yes; unmount; sleep
They are not drivers for the ATI Card itself, they are drivers for the ATI CHIPSET.
ATI makes cards with its own Chipset but they also let other companies (such as Sapphire) makes their own boards with ATI GPU's, and they are supposed to use the same drivers.
Incase anyone is wondering, Sapphires cards are way cheaper and sometimes (in the 8500's case) they outperform ati's own cards.
RTA -F(polite)
He didn't have windows/dos/fat partitions at all. he downloaded freedos and used a ramdrive to flash his videocard's bios. thats all that was wrong. the ATI driver checks to make sure the videocard is an ATI card. It should just check for an ATI chipset. Sounds like a problem ATI will pacth in the next release.
I have an Excalibur (ATI 9000 Pro based card), and have to run through a series of installs
to stop the video card locking up my Win2K system. The original drivers seem to be buggy.
When it is working fine (like now), it is a damned fine graphics card, its just such a
bitch to get going.
http://jesus.everdense.com/
Open. Closed.
Presuming you already have Linux installed, you should look in the various /usr/doc/whatever
directories belonging to the XFree86 stuff (there
will probably be a whole load of different packages
required for X, I don't know about Redhat/Mandrake
as I use Debian) and look for a file like README.DRI,
which might be gzipped (it is for me). The file also
tells you how to make sure that X will try to use
OpenGL (not difficult, may already be done for you!)
Alternatively, the actual DRI webpages are more up to date, and more thorough about which versions of cards they support - look for the "status" page for a start!
Configuring stuff, heh, I forget! If you have X set up to use your card, and tell it to use OpenGL, it will know whether your card can do it or not, and will try to load the appropriate kernel module. In my case, using a G400 card, it doesn't manage this, as it wants to have the agpgart module installed before the mga module, but doesn't realise to do this, so when my machine's booted, I normally modprobe the agpgart module myself, and then the mga module, and then the OpenGL works fine. Really, I should set up the modules.conf files to do this automatically, but I can't be bothered.
Bear in mind, that the mga module is only right for using G400/G200 cards, and the other cards would want other kernel modules! Also, those other kernel modules might not have those same requirements. In short, your mileage may vary.
But to return to the point in hand: If you don't want to be downloading binary-only drivers, then nVidia based cards are NOT what you want; they have no opensource 3d drivers at all that I know of. Some of the ATi cards are supported out of the box (I don't know how well!!) and some are only supported by ATi's driver so far, the one in the article.
Be careful! New moon tonight.
Sure, buy a crap card (LE means it didn't pass the "non LE" test, it's underclocked).
/.
Then flash it with an ATI firmware. FYI the GPU & RAM clock speed are... in the firmware.
That means his card is "overclocked" an probably instable as well, else they wouldn't sell it a LE.
Then, test some drivers, and make a flame report about it, and then get it posted on
So, instead of encouraring the company to make competitive drivers (binary, not binary, who cares: we want drivers THIS YEAR) lets do the contrary and flame them.
If you look at this comment as coming from someone who might not have a Windows partition/licence, then it's simply an honest expression of a disappointment in a technical restriction they can't overcome either costlessly or legally.
That said.
I have been in the computer game for a long time and have been threw every component and its manufacturer under the sun.
ATI gets a bad rap because it sold a buncha crappy cards with crappy drivers a while back. But they hired the Apple PR team to pimp them and a lotta people bought these cards and got screwed. The ads were better than the actual performance.
NVIDIA came along with a couple of nice 16 meg cards that worked well with Open GL and Direct X, and were fairly cheap.
ATI retaliates and does the Original Radeon. Pretty much junk except for the 3d performance. But ATI had been a traditionally OEM supplier anyway. Not a lot of experience for the high end commercial product. Remember the day of 3d cards? You would see STB and VooDoo, and that was about it.
The Geforce is a great product, sold a helluva lot, did the job become popular. But ATI revamped and started with the 8500, cleaned its driver act up and their cards kick ass.
I have an 8500 64 meg I grabbed from NewEGg and am perfectly happy with it, all 3d games in windows and it works well in Linux. My other box has a geforce 3 and it works well two. Though for web stuff, 2d, the ATI hands it its ass.
Problem with most people is they buy the bargain basement, OEM, close out, and it doesn't work to expectations. Well, GEE, musta been a reason for the closeout sale for all that white box shit. Oh yeah, paid 74 bucks 2 months ago for the 8500, tv out and all.
AS for those drivers from ATI, there are for ATI cards. In the day there were many problems with NVIDIAs reference drivers not working with third party manufacturers.
I understand we are all cheap computer people, and we conserve where we can. Between pricewatch and EBAY. But I learned a long time ago. Spend that extra 20 dollars for the retail CPU, get the 3 year warranty. Get that name brand motherboard. Cause it never fails, you buy something cheap and it burns out and you gotta buy again.
I think ATI and NVIDIA are par with each other and I am glad. Good competition. I understand the loyalty to NVIDIA, they were the reigning champions. ATI is kicking ass too. IT is better for all of us. And as for you guys who bought that 64 meg 20 dollar Radeon 7000(cause it said 64 meg) sorry dudes, shoulda ponied up some more cash/
Puto
The Revolution Will Not Be Televised
so why do their windows drivers work with "powered by" hardware?
I've been in touch with tech support at the OEM for my Radeon 9000 Pro, Power Color. They are not happy with the situation and the pressure is on for ATI to get a fix out ASAP. Latest email estimated sometime next week for drivers that work on all of the OEM cards.
I also get the impression that this was not a conspiracy. The drivers use the INT10 support in the card's video BIOS. The OEM video BIOS's vary slightly from card to card depending on what features they implemented (2 DAC vs 1, etc). The driver needs to be adjusted for each of the various BIOS. That's why flashing the ATI BIOS works. ATI just made it work on their cards first and will be filling in support for OEM cards ASAP.
WTF are you smoking. Whatever it is, you should stop posting to slashdot while under the influence.
The boards the drivers don't work with are boards built by 3rd party board manufacturers, using chips that ATI sold to them. (ie not reverse engineered, not stolen, not illegal or immoral in any way) These boards, while not made by ATI themselves, are as legal and sanctioned as the ones made by ATI. They are not jerry-ridded, hacked or downscaled in any way. In fact, ATI lets these manufacturers use the logo "powered by ATI". If any manufacturer was making cards that ATI was not happy with, ATI would simply refuse to sell the Radeon chipsets to them.
This driver incomaptibility is a silly restriction, probably due to a rushed release schedual or poor foresight from the driver writers. It could be simply because the driver has not been tested with "powered by ATI" hardware yet. I expect that this will be fixed.
A mindset more graphics cards companies should adopt.
3D graphics cards are really powerful computers
True, but they are not general purpose computers. They are designed to do one thing only - perform operations relevant to rendering 3D scenes. More than that, in fact - they are built to accelerate Direct3D and OpenGL operations specifically. Modifying the drivers might well allow you to do other cool things, but you'd almost certainly be better off doing those things with a normal CPU.
Other than that, while I sympathise with your sentiments, and to some extent agree with them, we don't really have much choice. The only fully working Linux drivers for modern graphics cards are closed source. By "fully working", I mean with complete, stable, fast suppot for all of the card's features. I'm pragmatic; if I've spent £200 on a new card, I want it to work properly. If that means using a close-source driver, so be it.
Finally, you seem not to realise that it isn't always up to the card/chipset manufacturers to open their driver source. NVidia, for example, is under NDA with several third parties over technology used in their cards and drivers. That means that they can't open the source to their drivers.
It's official. Most of you are morons.
Instead of all the jumping-through-hoops to build a bootable DOS floppy etc., why aren't the hardware manufacturers starting to build Linux-based tools?
The GPL'd FreeDOS project deserves kudos for providing legacy support alright, but Linux also provides additional reliability (no lockups during BIOS flashing...), choices between CLI or various GUIs, continued cutting-edge development of the environment with support for USB, FireWire or whatever media peripherals might be available and even support for hardware platforms other than x86 (e.g. Mac peripherals have BIOSes as well), to mention some advantages off the top of my head.
Since hardware manufacturers can't continue relying on DOS much longer now that MS is pulling the plug, the obvious choice for boot-time tools is really the freely-distributable Linux. It would be a tragedy for everyone but Microsoft if Windows became the successor of DOS as the *required* hardware maintenance platform.
Should invading one's peaceful neighbours be opposed, or rewarded with trade deals?
Here's a thread where people asked the same question on running 'powered by' cards and it contains a link that we found which seems to solve the problem. (Requires hex editing a file and the 'powered by' restriction is gone)
h re adid=33648944&perpage=20&pagenumber=4
http://www.rage3d.com/board/showthread.php?s=&t
I've got a OEM 9000 PRO from ATi and it refused to work initially:
/usr/X11R6/lib/modules/drivers/fglrx_drv.o
(--) fglrx(0): Chipset: "Radeon RV250 If" (Chipset = 0x4966)
(--) fglrx(0): (PciSubVendor = 0x148c, PciSubDevice = 0x2039)
(--) fglrx(0): board vendor info: third party grafics adapter - NOT original ATI
(--) fglrx(0): Linear framebuffer (phys) at 0xd8000000
(--) fglrx(0): MMIO registers at 0xe9000000
(--) fglrx(0): ChipRevID = 0x00
(--) fglrx(0): VideoRAM: 131072 kByte (64-bit DDR SDRAM)
(EE) fglrx(0): board/chipset is not supported by this driver (third party board)
I quickly came to the conclusion that the ATi drivers don't like non-ATi cards. I did a bit of searching and I found a solution - I did not find this myself!
Install and configure the drivers as per normal. Also, I suggest you download "hexedit" from freshmeat.net as you'll need it. You'll then need to hexedit this file:
To let it accept non-ATi boards, hexedit the file at offset 0x626e and alter "74 44" to "90 90" and save changes and away you go. Since making this change only, my 9000 PRO now works fine under RH 8.
This means no Vesa drivers! It means no more 60Hz screen refreshes! It means for GL acceleration. Run "glxinfo" for some information on the status of OpenGL and maybe "glx_gears" to actually test it. It should run very quickly.
Enjoy!