Slashdot Mirror


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."

12 of 248 comments (clear)

  1. Summary is wrong by awptic · · Score: 5, Informative

    According to the message posted, the utility used to reflash the BIOS runs in DOS, not Windows, and will work in FreeDOS

  2. Re:Luckily... by packeteer · · Score: 4, Informative

    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
  3. Re:Not everyone has *dual boot by Niadh · · Score: 5, Informative

    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.

  4. Re:Why not patch the drivers instead? by ActiveSX · · Score: 4, Informative
  5. Re:Why not patch the drivers instead? by benwb · · Score: 3, Informative

    Yes, you were mistaken. ATI's drivers are not open source. The GATOS project is open source and provides drivers for ATI's cards, but is not affiliated with ATI.

  6. Re:Advice please help by Tomble · · Score: 5, Informative
    Anonymous coward asked:
    Which card will work hardware accelerated out of the box on latest Mandrake or Redhat?
    Er, well AFAICT, you can't get hardware 3d acceleration on Linux without at least configuring it a little bit, but if you mean "What cards won't I need to download extra drivers for to get hardware accelearated 3d", then the answer would be roughly MGA G400, maybe G200, Radeon models up to 7500 (I think) as these are done by the free DRI drivers, and most of the more recent 3dfx based cards.

    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.
  7. Built by ATI vs Powered by ATI by Lhadatt · · Score: 3, Informative

    There is a difference between "Built by ATI" and "Powered by ATI". The problem you're seeing with OEM and non-ATI manufactured cards (aka "Powered by ATI") is in the BIOS -- the driver expects an official ATI BIOS (which would be a on "Built by ATI" card) and doesn't see it, so it won't work. The "Powered by" cards use reference drivers which aren't tweaked to any particular iteration of the card. "Built by" drivers won't install on non-ATI cards.

    Solutions: Flash the BIOS as some have been suggesting, or buy an official card. Or just yell at ATI enough until they release a reference driver.

    --
    -----------
    POiT!
  8. Re:Luckily... by Blkdeath · · Score: 3, Informative
    You have _GOT_ to be kidding...... First off nVidia is Microsoft's bitch, they dont do SHIT from within Linux,
    Incidentally, this video depicts a somewhat different story.
    --
    BD Phone Home!

    Shameless plug. Like you weren't expecting it.

  9. Re:Luckily... by Cryptnotic · · Score: 3, Informative

    I don't know how much Matrox helped with getting the Linux/XFree86/GDI drivers written. I'm fairly sure it was mostly thanks to hackers who reverse engineered the Windows drivers.

    --
    My other first post is car post.
  10. OEM's not happy by jonsmirl · · Score: 5, Informative

    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.

  11. Another workaround (without Windows) by Lev_Arris · · Score: 4, Informative

    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)

    http://www.rage3d.com/board/showthread.php?s=&th re adid=33648944&perpage=20&pagenumber=4

  12. How to get the ATi drivers working with ANY card. by Wiz · · Score: 5, Informative

    I've got a OEM 9000 PRO from ATi and it refused to work initially:

    (--) 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: /usr/X11R6/lib/modules/drivers/fglrx_drv.o

    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!