Page 1 of 3 123 LastLast
Results 1 to 10 of 33

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

Hybrid View

  1. #1
    Join Date
    Jan 2008
    Posts
    27

    Exclamation [Solved] Problem with 8.01: "Failed to initialize ASIC in kernel"

    ***** 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:

    Code:
    (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:

    Code:
    (**) 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:

    Code:
    (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:

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

    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:
    Quote 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".
    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!

    Cheers,
    knutbert
    Last edited by knutbert; 01-30-2008 at 04:28 PM.

  2. #2
    Join Date
    Jan 2008
    Posts
    27

    Exclamation

    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

  3. #3
    Join Date
    Jan 2008
    Posts
    6

    Default

    Quote Originally Posted by knutbert View Post
    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

  4. #4
    Join Date
    Aug 2007
    Location
    Norway
    Posts
    146

    Default

    Quote Originally Posted by knutbert View Post
    <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).

  5. #5
    Join Date
    Jan 2008
    Posts
    27

    Default

    Quote Originally Posted by oyvind View Post
    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

  6. #6
    Join Date
    Aug 2007
    Location
    Norway
    Posts
    146

    Default

    Quote Originally Posted by knutbert View Post
    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).

  7. #7
    Join Date
    Mar 2007
    Posts
    48

    Default

    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.

    Code:
    $ 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, xorg.conf.
    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
    Last edited by SheeEttin; 01-21-2008 at 11:18 AM.

  8. #8
    Join Date
    Jan 2008
    Posts
    1

    Default momentary X, then gone w/ 8.45.4 / Gutsy / x1400

    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:

  9. #9
    Join Date
    Oct 2007
    Posts
    31

    Default

    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

  10. #10
    Join Date
    Jan 2008
    Posts
    27

    Exclamation Current summary

    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!

    Regards,
    knutbert
    Last edited by knutbert; 01-22-2008 at 04:59 PM.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •