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.

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!

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?

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

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

Comment

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.

Comment

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!