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.
Announcement
Collapse
No announcement yet.
Problem with 8.01: "Failed to initialize ASIC in kernel"
Collapse
X
-
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
Comment
-
Version mismatch?
Hi Carlos,
Originally posted by kmolazz View PostI don't have the "failed to initialize ASIC in Kernel" error any more,
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
Comment
-
...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
regards,
Carlos
Comment
-
File a Trouble Ticket!
Hello,
I just filed a trouble-ticket with the AMD/ATI customer support here:
http://support.ati.com/ics/support/d...94&task=ticket
You may want to try that, too - might be the only way to get AMD's attention...
Cheers,
knutbert
Comment
-
No Laptop support from ATI/AMD...
Originally posted by knutbert View PostI just filed a trouble-ticket with the AMD/ATI customer support here:
http://support.ati.com/ics/support/d...94&task=ticket
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.
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...Last edited by knutbert; 28 January 2008, 06:45 PM.
Comment
-
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".
Code:# /.../ # SaX generated X11 config file # Created on: 2007-10-25T03:55:29-0400. # # Version: 8.1 # Contact: Marcus Schaefer <[email protected]>, 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
Comment
-
Back in business!
Hi Antiarch,
Originally posted by Antiarch View PostThe 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".
Thanks for passing the news around, Antiarch! And thanks to sndirsch for providing the workaround!
You are my heroes-of-the-day!
Cheers,
knutbert
Comment
Comment