Problem with 8.01: "Failed to initialize ASIC in kernel"

[knutbert]

***** This issue has been solved by means of a workaround - see below! ****

Hello,

since version 8-01 aka 8.452 I am experiencing this disturbing 'failed to initialize ASIC' error that I have not seen in previous versions:

(II) Module fglrxdrm: vendor="FireGL - ATI Technologies Inc."
compiled for 7.1.0, module version = 8.45.4
ABI class: X.Org Server Extension, version 0.3
(II) fglrx(0): Using adapter: 1:0:0.
(EE) fglrx(0): Failed to initialize ASIC in kernel.
(--) fglrx(0): VideoRAM: 262144 kByte, Type: DDR3
(II) fglrx(0): PCIE card detected
(WW) fglrx(0): board is an unknown third party board, chipset is supported

Additionally or maybe consequently (?) the system has trouble with the PCIe memory:

(**) fglrx(0): ATI GART size: 256 MB
(EE) fglrx(0): [pcie] Failed to gather memory of size 262144Kb for PCIe. Error (-1014)

And I finally end up without 3D support: :(

(EE) fglrx(0): atiddxDriScreenInit failed, GPS not been initialized.
(WW) fglrx(0): ***********************************************
(WW) fglrx(0): * DRI initialization failed! *
(WW) fglrx(0): * (maybe driver kernel module missing or bad) *
(WW) fglrx(0): * 2D acceleraton available (MMIO) *
(WW) fglrx(0): * no 3D acceleration available *
(WW) fglrx(0): ********************************************* *


EDIT: In the syslog the errors look like this:


kernel: [fglrx] Maximum main memory to use for locked dma buffers: 928 MBytes.
kernel: [fglrx] ASYNCIO init succeed!
kernel: [fglrx] PAT is enabled successfully!
kernel: [fglrx] module loaded - fglrx 8.45.4 [Jan 16 2008] on minor 0
kernel: [fglrx:firegl_cail_init] *ERROR* CAIL: CAILEarlyASICInit failed, error 1
kernel: [fglrx:firegl_init_asic] *ERROR* Failed to initialize ASIC.
kernel: [fglrx:drm_vmalloc] *ERROR* [mempages] Allocating 0 bytes
kernel: [fglrx:firegl_init_pcie] *ERROR* failed to alloc pagelist of size 00


I have not seen any of these errors in version 7-12 aka 8.443.

Any ideas on what the problem is or how to fix it?

System: OpenSUSE 10.2 (32-bit) / kernel 2.6.24-rc7 / Xorg 7.3 (Xserver 1.4)
Graphics: ATI Mobility Radeon X1900.

EDIT:
* Checked with kernels 2.6.23 and 2.6.22: same errors - so it's not a kernel 2.6.24 issue!
* Re-checked with fglrx 8.443 (just to be sure): no errors here
==> something is very different with fglrx 8.452 as opposed to earlier versions!

EDIT:
Looks like I'm not the only one experiencing these problems:
http://ati.cchtml.com/show_bug.cgi?id=987

EDIT:
There's another report of this bug here (http://phoronix.com/forums/showpost.php?p=23027&postcount=140).

So far there are two reports with a Mobility X1400 and mine with the Mobility X1900.
Do we see a pattern forming here? Both the X1400 and the X1900 are a bit different from the rest of the X1xxx series...

EDIT:
We now have 5 confirmed reports of the "failed to initilize ASIC" error. The chips involved are the X1900, X1400 (twice), X300 and X700 (all of them Mobility Radeon). Interestingly all of these systems were running openSUSE 10.2/10.3 with X.org 7.3 (xserver 1.4).

While from first three reports it looked like it was an issue specific to the X1900 and X1400 adapters, there are now two people with a X1400 reporting they are not seeing the ASIC bug (lucky you!). They are both running Gutsy with X.org 7.2 (xserver 1.3) though!

So is that the new common denominator?
Xorg 7.3 or OpenSUSE 10.2 / 10.3 or the combination?

EDIT:
Antiarch posted a workaround for this issue:
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".

Such a faulty(?) "BusID" entry is generated by SaX2, the openSuSE X-setup-tool.
So we were on the right track... :D

Thanks to Antiarch and sndirsch for spreading / providing the workaround! :):):):):):):)

Cheers,
knutbert

[knutbert]

Hello,

is anyone else experiencing this ASIC bug?
If so please post, so we can narrow down the "boundary conditions".

Also: If you've got a Mobility X1900 or Mobility X1400 and you don't get this error, please let us know.

Any information is appreciated! :)

Regards,
knutbert

[mweiss38]

Hello,

is anyone else experiencing this ASIC bug?
If so please post, so we can narrow down the "boundary conditions".

Also: If you've got a Mobility X1900 or Mobility X1400 and you don't get this error, please let us know.

Any information is appreciated! :)

Regards,
knutbert

I see the same error on a Dell Inspiron 6000 with a Radeon Mobility X300, 128MB, PCIE, 1920x1200 screen.

Standard openSUSE 10.3 with all security updates.
Can provide more detailed info if necessary.

mweiss38

[SheeEttin]

Radeon X1600 here, 512 MB memory, PCIe, Catalyst 8.10, Kubuntu Gutsy, stock kernel 2.6.22-14. I get the "failed to gather memory" and "GPS not been initialized", but not the ASIC bug.

$ grep -E "[WE]{2}" /var/log/Xorg.0.log
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
(II) Loading extension MIT-SCREEN-SAVER
(WW) fglrx: No matching Device section for instance (BusID PCI:1:0:1) found
(WW) fglrx(0): board is an unknown third party board, chipset is supported
(II) fglrx(0): POWERplay version 3. 1 power state available:
(EE) fglrx(0): [pcie] Failed to gather memory of size 262144Kb for PCIe. Error (-1000)
(EE) fglrx(0): atiddxDriScreenInit failed, GPS not been initialized.
(WW) fglrx(0): ***********************************************
(WW) fglrx(0): * DRI initialization failed! *
(WW) fglrx(0): * (maybe driver kernel module missing or bad) *
(WW) fglrx(0): * 2D acceleraton available (MMIO) *
(WW) fglrx(0): * no 3D acceleration available *
(WW) fglrx(0): ********************************************* *
(WW) fglrx(0): Textured Video not supported without DRI enabled.
(WW) fglrx(0): Video Overlay not supported on AVIVO based graphics cards. For XVideo support use Option "TexturedVideo".
(EE) AIGLX: Screen 0 is not DRI capable

Full Xorg.0.log (http://paste.biz/paste-2971.html), xorg.conf (http://paste.biz/paste-2972.html).
Any ideas?

EDIT: Or is this pulling in a different direction?

EDIT: Rebooting fixed it. Maybe I should've done that in the first place. :P

[oyvind]

<snip>

Also: If you've got a Mobility X1900 or Mobility X1400 and you don't get this error, please let us know.

Any information is appreciated! :)
<snip>

I have an X1400 mobile on a Lenovo Thinkpad Z61m laptop. I don't experience this error (never seen such an error with any fglrx version).

[knutbert]

I have an X1400 mobile on a Lenovo Thinkpad Z61m laptop. I don't experience this error (never seen such an error with any fglrx version).

Thanks for sharing the information!
So apparently it is not a per se problem with the Mobility X1400. :)

To narrow down things a bit:
What distro / xserver-version / kernel version are you running?

Regards,
knutbert

[oyvind]

Thanks for sharing the information!
So apparently it is not a per se problem with the Mobility X1400. :)

To narrow down things a bit:
What distro / xserver-version / kernel version are you running?

Regards,
knutbert

Sure, no prob. I'm running Ubuntu 7.10 Gutsy 32bit, X server 1.3.0, Xorg 7.2 and kernel 2.6.22-14-generic SMP (standard Ubuntu).

[hmangalam]

Hi All,

When using 8.24.4 driver direct from ATI, on a dist-upgrade from feisty to gutsy, using kernel 2.6.22-14-generic on a thinkpad T60/X1400, the login screen comes up fine, but when I try to log on, the screen goes black then drops me back to the graphical login screen. When going to console login and running startx, X will come up briefly (can see the X cursor on the grey background), but then it dies back to the console. When that happens, the screen reports some XKEYBOARD/xkbcomp errors (which explicitly say they aren't fatal), but those are the only errors showing up. I'm not really getting any errors now, except for the ones mentioned below.



The log has given me a number of errors, none of which appear to be fatal, but clearly something is.

Currently, the warnings or errors from X are as follows:

(WW) The directory "/usr/share/X11/fonts/misc" does not exist.
(WW) The directory "/usr/share/X11/fonts/100dpi" does not exist.
(WW) The directory "/usr/share/X11/fonts/75dpi" does not exist.
(WW) The directory "/usr/share/X11/fonts/Type1" does not exist.
(WW) `fonts.dir' not found (or not valid) in "/var/lib/defoma/fontconfig.d/a".
(WW) Including the default font path /usr/share/fonts/X11/misc,/usr/share/fonts/X11/cyrillic,/usr/share/fonts/X11/100dpi/:unscaled,/usr/share/fonts/X11/75dpi/:unscaled,/usr/share/fonts/X11/Type1,/usr/share/fonts/X11/100dpi,/usr/share/fonts/X11/75dpi,/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType.
(WW) fglrx(0): GetVBEMode failed
(WW) fglrx(0): board is an unknown third party board, chipset is supported
(WW) fglrx(0): Only one display is connnected,so single mode is enabled
(WW) fglrx(0): Option "UseFBDev" is not used
(WW) fglrx(0): Option "VendorName" is not used
(WW) fglrx(0): Option "ModelName" is not used

so no Errors and the warnings do not seem to be all that horrible.

Some errors in the past dealt with not being able to load 'glcore' and 'font1' modules, but I've commented those out without complaint.

syslog gives me the following fglrx-related errs

[fglrx:firegl_free_mutex] *ERROR* mutex id 0x20000008 not found in mutex list
[fglrx:firegl_init_pcie] *ERROR* Invalid GART type 0.
[fglrx:firegl_init_pcie] *ERROR* Invalid GART type 0.

but then on rerunning startx, I only get these in a repeating fglrx message block:

[fglrx] PCIe has already been initialized. Reinitializing ...
[fglrx] Reserve Block - 0 offset = 0X7ffb000 length = 0X5000
[fglrx] Reserve Block - 1 offset = 0X0 length = 0X1000000
[fglrx] Reserve Block - 2 offset = 0X7fbb000 length = 0X40000
[fglrx] interrupt source 10000000 successfully enabled
[fglrx] enable ID = 0x00000008
[fglrx] Receive enable interrupt message with irqEnableMask: 10000000
[fglrx] interrupt source 10000000 successfully disabled!
[fglrx] enable ID = 0x00000000
[fglrx] Receive disable interrupt message with irqEnableMask: 10000000; dwIRQEnableId:

[kmolazz]

I also have the problem described in the first post.
X700 mobile
OpenSuse 10.3 (32bit)
2.6.22.13-0.3 kernel
Xorg 7.3

[knutbert]

Hello,

first of all I'd like to thank everybody who reported their experiences! :)

Let me briefly summarize the findings so far:

ASIC-Bug:
We have 5 confirmed reports of the "failed to initilize ASIC" error. The chips involved are the X1900, X1400 (twice), X300 and X700 (all of them Mobility Radeon). Interestingly all of these systems were running openSUSE 10.2/10.3 with X.org 7.3 (xserver 1.4).

Working systems:
While from first three reports it looked like it was an issue specific to the X1900 and X1400 adapters, there are now two people with a X1400 reporting they are not seeing the ASIC bug (lucky you!). They are both running Gutsy with X.org 7.2 (xserver 1.3) though!

So is that the new common denominator?
Xorg 7.3 or OpenSUSE 10.2 / 10.3 or the combination?

Please keep on posting your experiences! I have a feeling we can track this issue down! :cool:

Regards,
knutbert

[Kano]

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.

[combatdoc]

Just to add more complete data to the bug report I filed on bugzilla.
Dell e1705 (1GB RAM for now)
ATI Mobility x1400
Xorg version 7.2
Kernel 2.6.22.13-0.3-default #1 SMP
Gnome 2.20
Compiz 0.6.9

[kmolazz]

I tried installing the drivers again. Removed the old drivers, started with a new xorg.conf (mine was a mess, had references to both fglrx and radeon), and deleted all *fglx* files i could find.

I don't have the "failed to initialize ASIC in Kernel" error any more, but i do have this:
(EE) fglrx(0): [pcie] Failed to gather memory of size 262144Kb for PCIe. Error (-1014)
(EE) fglrx(0): atiddxDriScreenInit failed, GPS not been initialized.
(WW) fglrx(0): ***********************************************
(WW) fglrx(0): * DRI initialization failed! *
(WW) fglrx(0): * (maybe driver kernel module missing or bad) *
(WW) fglrx(0): * 2D acceleraton available (MMIO) *
(WW) fglrx(0): * no 3D acceleration available *
(WW) fglrx(0): ********************************************* *

Whenever i try to run a 3D app i get kicked out of kde (X?).
Sorry for the few details but my linux skills are very basic.
regards,
Carlos

[knutbert]

Hi Carlos,

I don't have the "failed to initialize ASIC in Kernel" error any more,

Uninstall/Reinstall can be a bit tricky at times... So just to rule out a simple explanation for your errors: Is the right kernel module being loaded?

On the other hand the "ASIC-error" you've seen before might have been due to a driver / kernel-module version mismatch that you cleared by reinstalling...

You can easily check with "dmesg | grep fglrx" and compare the version number with that reported in Xorg.0.log.

Cheers,
knutbert

[kmolazz]

...oh crap... i was looking at the sax2 log file.
I still have the ASIC error in the Xorg log:

(EE) fglrx(0): Failed to initialize ASIC in kernel.
(EE) fglrx(0): === [swlDalHelperAddCustomizeMode] === CWDDEDI_DisplayGetSetModeTimingOverride failed: 2
(EE) fglrx(0): [pcie] Failed to gather memory of size 262144Kb for PCIe. Error (-1014)
(EE) fglrx(0): atiddxDriScreenInit failed, GPS not been initialized.
(WW) fglrx(0): ***********************************************
(WW) fglrx(0): * DRI initialization failed! *
(WW) fglrx(0): * (maybe driver kernel module missing or bad) *
(WW) fglrx(0): * 2D acceleraton available (MMIO) *
(WW) fglrx(0): * no 3D acceleration available *
(WW) fglrx(0): ********************************************* *


The fglrx versions are the same. And i also got errors with dmesg:
[fglrx:firegl_cail_init] *ERROR* CAIL: CAILEarlyASICInit failed, error 1
[fglrx:firegl_init_asic] *ERROR* Failed to initialize ASIC.
[fglrx:drm_vmalloc] *ERROR* [mempages] Allocating 0 bytes
[fglrx:firegl_init_pcie] *ERROR* failed to alloc pagelist of size 00
[fglrx:firegl_cail_init] *ERROR* CAIL: CAILEarlyASICInit failed, error 1
[fglrx:firegl_init_asic] *ERROR* Failed to initialize ASIC.
[fglrx:drm_vmalloc] *ERROR* [mempages] Allocating 0 bytes
[fglrx:firegl_init_pcie] *ERROR* failed to alloc pagelist of size 00

bummer :confused:

regards,
Carlos

[knutbert]

Hello,

I just filed a trouble-ticket with the AMD/ATI customer support here:
http://support.ati.com/ics/support/default.asp?deptID=894&task=ticket

You may want to try that, too - might be the only way to get AMD's attention... ;)

Cheers,
knutbert

[Osado]

Hello

No ASIC error here (but having the same issues about 3D stated by Kano some posts up).
Dell Inspiron 6400, ATI Mobility X1400, Mandriva Cooker (Xorg 1.4), kernel 2.6.24-rc8.

Regards

[knutbert]

I just filed a trouble-ticket with the AMD/ATI customer support here:
http://support.ati.com/ics/support/default.asp?deptID=894&task=ticket


Meanwhile I got two responses from ATI:

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

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... :o

[Antiarch]

For those of you using OpenSuSE 10.2/10.3 and most likely had your xorg.conf generated by SaX2...

The short of it is there's a regression in the 8.01 driver. http://ati.cchtml.com/show_bug.cgi?id=998

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

# /.../
# SaX generated X11 config file
# Created on: 2007-10-25T03:55:29-0400.
#
# Version: 8.1
# Contact: Marcus Schaefer <sax@suse.de>, 2005
# Contact: SaX-User list <https://lists.berlios.de/mailman/listinfo/sax-users>
#
# Automatically generated by [SaX2] (8.1)
# PLEASE DO NOT EDIT THIS FILE!
#

Section "ServerLayout"
Identifier "Layout[all]"
Screen "Screen[0]" 0 0
InputDevice "Keyboard[0]" "CoreKeyboard"
InputDevice "Mouse[1]" "CorePointer"
EndSection

Section "Files"
InputDevices "/dev/gpmdata"
InputDevices "/dev/input/mice"
FontPath "/usr/share/fonts/misc:unscaled"
FontPath "/usr/share/fonts/local"
FontPath "/usr/share/fonts/75dpi:unscaled"
FontPath "/usr/share/fonts/100dpi:unscaled"
FontPath "/usr/share/fonts/Type1"
FontPath "/usr/share/fonts/URW"
FontPath "/usr/share/fonts/Speedo"
FontPath "/usr/share/fonts/PEX"
FontPath "/usr/share/fonts/cyrillic"
FontPath "/usr/share/fonts/latin2/misc:unscaled"
FontPath "/usr/share/fonts/latin2/75dpi:unscaled"
FontPath "/usr/share/fonts/latin2/100dpi:unscaled"
FontPath "/usr/share/fonts/latin2/Type1"
FontPath "/usr/share/fonts/latin7/75dpi:unscaled"
FontPath "/usr/share/fonts/baekmuk:unscaled"
FontPath "/usr/share/fonts/japanese:unscaled"
FontPath "/usr/share/fonts/kwintv"
FontPath "/usr/share/fonts/truetype"
FontPath "/usr/share/fonts/uni:unscaled"
FontPath "/usr/share/fonts/CID"
FontPath "/usr/share/fonts/ucs/misc:unscaled"
FontPath "/usr/share/fonts/ucs/75dpi:unscaled"
FontPath "/usr/share/fonts/ucs/100dpi:unscaled"
FontPath "/usr/share/fonts/hellas/misc:unscaled"
FontPath "/usr/share/fonts/hellas/75dpi:unscaled"
FontPath "/usr/share/fonts/hellas/100dpi:unscaled"
FontPath "/usr/share/fonts/hellas/Type1"
FontPath "/usr/share/fonts/misc/sgi:unscaled"
FontPath "/usr/share/fonts/xtest"
FontPath "/opt/kde3/share/fonts"
EndSection

Section "Module"
Load "dbe"
Load "type1"
Load "freetype"
Load "extmod"
Load "glx"
Load "dri"
EndSection

Section "ServerFlags"
Option "AllowMouseOpenFail" "on"
Option "IgnoreABI" "on"
Option "AIGLX" "true"
EndSection

Section "InputDevice"
Identifier "Keyboard[0]"
Driver "kbd"
Option "Protocol" "Standard"
Option "XkbLayout" "us"
Option "XkbModel" "microsoftpro"
Option "XkbRules" "xfree86"
EndSection

Section "InputDevice"
Identifier "Mouse[1]"
Driver "evdev"
Option "Buttons" "20"
Option "InputFashion" "Mouse"
Option "Name" "Logitech USB Gaming Mouse"
Option "Protocol" "event"
Option "SendCoreEvents" "on"
Option "Vendor" "Sysp"
Option "ZAxisMapping" "4 5"
EndSection

Section "Modes"
Identifier "Modes[0]"
EndSection

Section "Monitor"
Identifier "Monitor[0]"
VendorName "HSD"
ModelName "HANNS.G HX191"
UseModes "Modes[0]"
DisplaySize 376 301
HorizSync 30.0 - 80.0
VertRefresh 43.0 - 75.0
Option "CalcAlgorithm" "XServerPool"
Option "DPMS"
EndSection

Section "Device"

#Option "NoDDC"
Identifier "Device[0]"
Driver "fglrx"
VendorName "VESA"
BoardName "Framebuffer Graphics"
Option "UseInternalAGPGART" "no"
Option "no_accel" "no"
Option "no_dri" "no"
Option "mtrr" "off"
Option "ScreenOverlap" "0"
Option "GammaCorrectionI" "0x00000000"
Option "GammaCorrectionII" "0x00000000"
Option "Capabilities" "0x00000000"
Option "CapabilitiesEx" "0x00000000"
Option "VideoOverlay" "on"
Option "OpenGLOverlay" "off"
Option "CenterMode" "off"
Option "PseudoColorVisuals" "off"
Option "Stereo" "off"
Option "StereoSyncEnable" "1"
Option "FSAAEnable" "off"
Option "FSAAScale" "0"
Option "FSAADisableGamma" "no"
Option "FSAACustomizeMSPos" "no"
Option "FSAAMSPosX0" "0.000000"
Option "FSAAMSPosY0" "0.000000"
Option "FSAAMSPosX1" "0.000000"
Option "FSAAMSPosY1" "0.000000"
Option "FSAAMSPosX2" "0.000000"
Option "FSAAMSPosY2" "0.000000"
Option "FSAAMSPosX3" "0.000000"
Option "FSAAMSPosY3" "0.000000"
Option "FSAAMSPosX4" "0.000000"
Option "FSAAMSPosY4" "0.000000"
Option "FSAAMSPosX5" "0.000000"
Option "FSAAMSPosY5" "0.000000"
Option "UseFastTLS" "0"
Option "BlockSignalsOnLock" "on"
Option "ForceGenericCPU" "no"
Option "KernelModuleParm" "locked-userpages=0"
Option "XAANoOffscreenPixmaps" "true"
BusID "PCI:1:0:0"
EndSection

Section "Screen"
Identifier "Screen[0]"
Device "Device[0]"
Monitor "Monitor[0]"
DefaultDepth 24
SubSection "Display"
Depth 15
Modes "1280x1024" "1280x960" "1152x864" "1024x768" "800x600"
EndSubSection
SubSection "Display"
Depth 16
Modes "1280x1024" "1280x960" "1152x864" "1024x768" "800x600"
EndSubSection
SubSection "Display"
Depth 24
Modes "1280x1024" "1280x960" "1152x864" "1024x768" "800x600"
EndSubSection
SubSection "Display"
Depth 8
Modes "1280x1024" "1280x960" "1152x864" "1024x768" "800x600"
EndSubSection
EndSection

Section "DRI"
Group "video"
Mode 0660
EndSection

Section "Extensions"
Option "Composite" "true"
Option "DAMAGE" "true"
EndSection

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. :cool:

[knutbert]

Hi 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!

You are my heroes-of-the-day! :D:D:D:D:D:D:D:D

Cheers,
knutbert

[combatdoc]

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

[kmolazz]

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

[achyeboah]

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/linux64/linux64-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

[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?

[bridgman]

allartk, what errors are you getting in the X log ?

[allartk]

Here the warnings and error from my Xorg.0.log


$ grep '(EE)\|(WW)' Xorg.0.log
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
(WW) fglrx: No matching Device section for instance (BusID PCI:1:0:1) found
(WW) fglrx: No matching Device section for instance (BusID PCI:1:0:1) found
(EE) fglrx(0): Failed to initialize ASIC in kernel.
(WW) fglrx(0): board is an unknown third party board, chipset is supported
(WW) fglrx(0): Only one display is connnected,so single mode is enabled
(EE) fglrx(0): [pcie] Failed to gather memory of size 261120Kb for PCIe. Error (-1007)
(EE) fglrx(0): atiddxDriScreenInit failed, GPS not been initialized.
(WW) fglrx(0): ***********************************************
(WW) fglrx(0): * DRI initialization failed! *
(WW) fglrx(0): * (maybe driver kernel module missing or bad) *
(WW) fglrx(0): * 2D acceleraton available (MMIO) *
(WW) fglrx(0): * no 3D acceleration available *
(WW) fglrx(0): ********************************************* *
(WW) fglrx(0): Textured Video not supported without DRI enabled.
(WW) fglrx(0): Option "VendorName" is not used
(WW) fglrx(0): Option "ModelName" is not used
(EE) fglrx(0): firegl_SetSuspendResumeState FAILED -1003.


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

[allartk]

I switched to the OSS driver..

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

[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 (http://kubuntuforums.net/forums/index.php?topic=3082777.0). (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.

[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:
(**) Configured Mouse: always reports core events
(**) Option "Device" "/dev/input/mice"
(**) Option "Emulate3Buttons" "true"
(**) Configured Mouse: Emulate3Buttons, Emulate3Timeout: 50
(**) Option "ZAxisMapping" "4 5"
(**) Configured Mouse: ZAxisMapping: buttons 4 and 5
(**) Configured Mouse: Buttons: 9
(**) Configured Mouse: Sensitivity: 1
(II) evaluating device (Configured Mouse)
(II) XINPUT: Adding extended input device "Configured Mouse" (type: MOUSE)
(II) evaluating device (Generic Keyboard)
(II) XINPUT: Adding extended input device "Generic Keyboard" (type: KEYBOARD)
(II) Configured Mouse: ps2EnableDataReporting: succeeded
(II) AIGLX: Suspending AIGLX clients for VT switch

my xorg.conf is

# 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

Section "ServerLayout"

# Uncomment if you have a wacom tablet
# InputDevice "stylus" "SendCoreEvents"
# InputDevice "cursor" "SendCoreEvents"
# InputDevice "eraser" "SendCoreEvents"
Identifier "Default Layout"
Screen 0 "aticonfig-Screen[0]" 0 0
InputDevice "Generic Keyboard"
InputDevice "Configured Mouse"
# Option "AIGLX" "false"
EndSection

Section "Files"
EndSection

Section "Module"
# Load "glx"
# Load "GLcore"
# Load "dri"
# Load "v4l"
EndSection

Section "InputDevice"
Identifier "Generic Keyboard"
Driver "kbd"
Option "CoreKeyboard"
Option "XkbRules" "xorg"
Option "XkbModel" "pc105"
Option "XkbLayout" "us"
EndSection

Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ImPS/2"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "true"
EndSection

Section "InputDevice"
Identifier "stylus"
Driver "wacom"
Option "Device" "/dev/input/wacom"
Option "Type" "stylus"
Option "ForceDevice" "ISDV4"# Tablet PC ONLY
EndSection

Section "InputDevice"
Identifier "eraser"
Driver "wacom"
Option "Device" "/dev/input/wacom"
Option "Type" "eraser"
Option "ForceDevice" "ISDV4"# Tablet PC ONLY
EndSection

Section "InputDevice"
Identifier "cursor"
Driver "wacom"
Option "Device" "/dev/input/wacom"
Option "Type" "cursor"
Option "ForceDevice" "ISDV4"# Tablet PC ONLY
EndSection

Section "Monitor"
Identifier "aticonfig-Monitor[0]"
Option "VendorName" "ATI Proprietary Driver"
Option "ModelName" "Generic Autodetecting Monitor"
Option "DPMS" "true"
EndSection

Section "Device"
Identifier "aticonfig-Device[0]"
# Driver "ati"
BusID "PCI:1:0:0"
Driver "fglrx"
# Option "AccelMethod" "EXA"
Option "NoDRI"
# Option "TexturedVideoSync" "on"
# Option "TexturedVideo" "on"
# Option "OpenGLOverlay" "off"
# Option "VideoOverlay" "off"
# Option "XaaNoOffscreenPixmaps" "1"
EndSection

Section "Screen"
Identifier "aticonfig-Screen[0]"
Device "aticonfig-Device[0]"
Monitor "aticonfig-Monitor[0]"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection

Section "DRI"
Mode 0666
EndSection

Section "Extensions"
Option "Composite" "Disable"
EndSection

nodri en no composite is for testing..

But for now i will stay at the OSS driver with 3d. (the former fglrx had also problems on my system, that is why I gave it a try).

[SheeEttin]

The last line in your xorg log is caused by switching to another terminal.
After getting the black screen, try switching to and from a terminal (e.g. Ctrl+Alt+F1).

[allartk]

The last line in your xorg log is caused by switching to another terminal.
After getting the black screen, try switching to and from a terminal (e.g. Ctrl+Alt+F1).

Thanks for the post, but I did that myself top copy the log file of that session to my home direcory (and edit xorg.conf to use the OSS driver to get again something on my screen and post on the forum).

[SheeEttin]

Hmm.
Well, why don't you back up your current xorg.conf somewhere and start a new one with "sudo dpkg-reconfigure xserver-xorg". When you finish that, either edit the new xorg.conf to use fglrx or "sudo aticonfig --initial". See how that works.
(Oh, and post the whole log at some pastebin service so I/we can take a look at it.)

By the way, when you say "OSS driver", you mean the ati/radeon driver, correct?