Originally Posted by Antiarch View Post
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".

This seems to have worked for me. Currently running AIGLX at ~2300fps in glxgears and between 505 and 515 fps in fgl_glxgears.

Had a few issues getting it going, but i think that was related to XGL and my xorg.conf.

:D

01-31-2008, 08:33 AM

kmolazz

Worked for me too, 3D is working again :D Thanks!

03-18-2008, 04:40 PM

achyeboah

i dont have a BusID field at all - 1400X, Suse 10.3

hello!!! help!!!

i'm a novice, so this is really discouraging me. i'm using a dell inspiron 9400, mobility 1400X, opensuse 10.3, 64bit version. i should have a resolution of 1400x900, but dont get it. I don't have any 3D either. i downloaded the driver from http://ati.amd.com/support/drivers/l...64-radeon.html. i installed it, and BAM! it failed to get the graphical screen. Ctrl +Alt + F1 failed to get console too. i had to reboot with single option at GRUB prompt, and replace the xorg.conf file with a backup i made. that got me back my graphics, but still with a resolution of 1152x864. i tried did an uninstall of the fglrx driver, and reinstalled and it broke again. i get the error message
(EE) fglrx(0): Failed to initialize ASIC in kernel. etc,etc

however i DONT HAVE A BusID line in my xorg.conf file at all!

what do i do?

:confused::confused::confused::confused:

I hope i've provided enough information

05-25-2008, 05:34 PM

allartk

You are not alone. I've this issue with the 8.5 release on ubuntu hardy with a X1300 pcie.

This driver seems to be worse for my card every release.

I had no BusID in my xorg.conf, now i have but it doesn't make any difference. Someone has a clue to help me out?

edit: I can post the used xorg.conf in the evening (about 8 hours ) but I was a bit in a hurry this morning

05-28-2008, 05:57 PM

allartk

I switched to the OSS driver..

05-28-2008, 07:13 PM

bridgman

Not sure if this is relevant, but how much system memory do you have ? Wondering if this might be a low memory issue; looks like we're trying to grab 256MB during kernel driver initialization and failing.

05-28-2008, 10:08 PM

SheeEttin

Nah, probably not memory. I suspect a bad installation.

Start fresh with "sudo rm -rf /var/lib/dkms/fglrx", then install again. (You might consider first switching to the vesa driver and rebooting to the the fglrx modules 'n everything unloaded.)
I've written a script for Ubuntu types to assist in installation... You can get it here. (Excuse the messy post there, I have yet to clean it up.)

EDIT: Oh yeah, that'll install Catalyst 8.4 (the most recent being 8.5). If you want/need Catalyst 8.5, you can edit lines 69 and 72, replacing the "8-4-x86" with "8-5-x86". No other changes are necessary.

05-29-2008, 05:08 AM

allartk

Thanks for the answer, the errors are gone, but nothing is displayed. So I have a black screen.. The last rows in my Xorg.1.log are:

# xorg.conf (xorg X Window System server configuration file)
#
# This file was generated by dexconf, the Debian X Configuration tool, using
# values from the debconf database.
#
# Edit this file with caution, and see the xorg.conf manual page.
# (Type "man xorg.conf" at the shell prompt.)
#
# This file is automatically updated on xserver-xorg package upgrades *only*
# if it has not been modified since the last upgrade of the xserver-xorg
# package.
#
# If you have edited this file but would like it to be automatically updated
# again, run the following command:
# sudo dpkg-reconfigure -phigh xserver-xorg