If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

The driver has lots of problems with Xserver 1.4. Usually it starts, but AIGLX does not work and the first 3d app (except glxgears) hangs. Maybe ATI should compile it against Xserver 1.4 direct instead of using the same binary like for 1.3.

No Laptop support from ATI/AMD...

The first one was just an automatically generated email I suppose everybody gets who files a ticket about Catalyst drivers and Linux.

Upon responding that the general information provided (nothing I hadn't seen before) did not solve my problem, I got an email from a CSR. So someone's actually processing these tickets!

Unfortunately this second email also does not address in any way the specific problem I described in detail.
It's just the same old collection of links to the well-known FAQs on the AMD pages.

And then - yes, yes, of course I expected it - there's this:

Since the equipment manufacturer that uses AMD technology in their mobile (laptop/notebook) products has many other implementations that might affect the general performance of the equipment, we redirect our customer to contact the equipment manufacturer for technical service.

Now that's what I call a cheap excuse!

I just hope this is only the official version and they are internally looking into the problem...

Regards,
knutbert

P.S.: Caught myself the other day checking out prices of my laptops Nvidia-counterpart on ebay...

The good news is there's a simple work around for it. Find the Device section in your xorg.conf (Section "Device") and look for a line that starts with BusID. In quotes will be something like "1:0:0" (there will be different numbers depending on your card) Before that string of numbers, add "PCI:", to make it look like this: "PCI:1:0:0".

I was getting the same ASIC problem on the Radeon X1950Pro in my desktop with the 8.01 drivers on OpenSuSE 10.3. Commenting out the BusID line should work as well. You have Dieter Jurzitza to thank for tracking down the bug. I'm just passing on the good word after doing a Google search on the issue. I've got 3D acceleration and Compiz is working just fine.

Back in business!

Hi Antiarch,

Originally Posted by Antiarch

The good news is there's a simple work around for it. Find the Device section in your xorg.conf (Section "Device") and look for a line that starts with BusID. In quotes will be something like "1:0:0" (there will be different numbers depending on your card) Before that string of numbers, add "PCI:", to make it look like this: "PCI:1:0:0".

what can I say, this solved the issue completely for me - 3D and Compiz are working fine!

Thanks for passing the news around, Antiarch! And thanks to sndirsch for providing the workaround!