- 1 Installer Issues
- 2 X Server Related Issues
- 2.1 X Server freeze upon lockscreen/lid-close when Intel iGPU selected
- 2.2 No XVideo support on 690G integrated graphic chipset
- 2.3 System lockup on logout or switch to virtual consoles
- 2.4 BigDesktop (Dual screen) doesn't work after GDM login screen
- 2.5 Computer Freezes while using fglrx (UMA and SIDEPORT)
- 2.6 Graphical Anomalies
- 2.7 OpenGL framebuffer Corruption
- 2.8 Blank Screen with Xorg 1.3.0
- 2.9 Radeon GPU fan is very loud / constantly works
- 2.10 System freezes after logout with GDM, KDM or XDM
- 2.11 System freezes at startup of Fedora 7 or RHEL 5.3 after installing the driver
- 2.12 System lockup on logout with catalyst 8.01 
- 2.13 Intermittent Freezes/Lockups due to AGPv3 running at 8x
- 2.14 _ZN17SegmentMapManager13deleteMappingEP9CMMClient+0x3f/0x170
- 2.15 [SOLVED] System freeze / Catalyst 11-9 / "unable to handle kernel NULL pointer dereference at ..."
- 2.16 An Example of a working Xorg.conf
- 2.17 Sticky mouse cursor
- 2.18 [SOLVED] RadeonHD6670 & Catalyst 13.4 : X server crash ( segmentation fault after __driCreateNewScreen in fglrx_dri.so ) / KMS working
- 3 aticonfig Issues
- 4 AMD installer script completes, fglrx X driver loads, fglrxinfo reports error
- 5 X fails - fglrx module not found
- 6 References
When the installer fails to produce results, check the directory where the ati catalyst installer has been placed. If it contains international characters or spaces, weird errors will arise. (The issue has been reported to ATI some time ago, but even in the newest releases they seem to like to prefer to conserve the bug)
February 15, 2013 - Catalyst 13.1 Install on Ubuntu 10.04 (lucid)
Had much the same problems as the poster below, but found another fix:
dh_install: fglrx missing files (arch/#SRCOTHERARCH#/etc/OpenCL/vendors/*.icd), aborting
1. Extract files from the installer:
sh amd-driver-installer-catalyst-13.1-linux-x86.x86_64.run --extract amd
2. Edit the packages/Ubuntu/dists/lucid/rules file as follows:
The following line had to be appended after line 69: SRC_other_arch := x86_64 and the following line had to be appended after line 151: -e "s|#SRCOTHERARCH#|$(SRC_other_arch)|g" \
3. Create package:
sudo ./ati-installer.sh 9.012 --buildpkg Ubuntu/lucid
January 22, 2013 - Catalyst 13.1 Install on Ubuntu 11.04 (natty)
Just wanted to document my problems with this install and the workaround I came up with.
1. I got the installer from AMD (amd-driver-installer-catalyst-13.1-linux-x86.x86_64.run) and attempted this:
sh amd-driver-installer-catalyst-13.1-linux-x86.x86_64.run --buildpkg Ubuntu/natty
This failed with:
dh_install: fglrx missing files (arch/#SRCOTHERARCH#/etc/OpenCL/vendors/*.icd), aborting make: *** [binary-arch] Error 2 dpkg-buildpackage: error: debian/rules binary gave error exit status 2
That '#SRCOTHERARCH#' looked a bit suspicious. I found a directory arch/x86_64/etc/OpenCL/vendors with an "icd" file in it. I guessed that was what the installer was looking for.
2. I then extracted the files from the installer:
sh amd-driver-installer-catalyst-13.1-linux-x86.x86_64.run --extract amd
3. Create sym link for the "#SRCOTHERARCH#" directory that the installer is expecting to find:
cd amd/arch ln -sf x86_64 '#SRCOTHERARCH#'
4. Back up to the installer directory and retried the "buildpkg" step - this time it worked and created the three deb package files. I was then able to continue with the install as normal.
X Server Related Issues
This "free sharing" of information seems too good to be true. Like communism.
X Server freeze upon lockscreen/lid-close when Intel iGPU selected
On a Haswell system with an Intel HD 4400 as the integrated card in a hybrid system X freezes (moveable mouse cursor but either black screen or frozen image of desktop at time of freeze) often when the user locks the screen (inactivity or otherwise) or closes the lid. The desktop (in 13.10 at least) can be recovered by switching to a tty and back( e.g. ctrl+alt+fn1, followed by ctl+alt+fn7). In 12.04 I needed to restart completely from tty.
This bug occurs because pxpress loads the intel driver with the "AccelMethod" "UXA" option. You can verify this is the cause by using a minimal (Intel only) `xorg.conf` (even before fglrx drivers are installed) with just
Section "Device" Identifier "Intel Graphics" Driver "intel" Option "AccelMethod" "UXA" # (mode fglrx uses) I can see the bug # Option "AccelMethod" "SNA" #(default) no bug! EndSection
and you should reproduce the bug with a few attempts at closing lid/locking screen. Whereas with the change to ` Option "AccelMethod" "SNA"` there is no bug anymore ("SNA" is the default anyway).
How to fix
Create (or edit) the DRI config file `~/.drirc` containing
<device screen="0" driver="dri2"> <application name="Default"> <option name="vblank_mode" value="0"/> </application> </device>
This turns off "vsync" for the Intel card (the mode that attempts to make your gfx card sync its framerate with that of the display to avoid tearing, rather than racing ahead at its intrinsic higher framerate).
Now even when pxpress loads the intel driver in "UXA" mode, the bug should not be reproducible.
It would be a better solution if it were possible to tell pxpress to load intel driver with SNA mode directly.
No XVideo support on 690G integrated graphic chipset
- Upgrade your BIOS if you get random flicker lines and black screen with a 690G chip.
- Motherboard using the 690G IGP chipset don't have XVideo support. When you execute the "xvinfo" command you get "no adaptors present". This is the case by using the 8.39.4 FGLRX driver and whenever the "sudo aticonfig --overlay-type=Xv" command or the "sudo aticonfig --overlay-type=opengl" was used. ATI seem to know this as there list TVtime as an application unable to run on a 690G chip.
- XVideo works with 8-1 release (version 8.45.4). You need to change the defaults in /etc/ati/amdpcsdb (created by amdcccle, loaded by X on start, and saved on exit). With X shutdown, set VideoOverlay=Son, OpenGLOverlay=Soff, and Textured2D=STrue. (Don't use aticonfig or xorg.conf to set these. At this time, aticonfig and amdccle don't change these settings, and /etc/ati/amdpcsdb seems to override xorg.conf) (Verified on Asus M2A-VM with BIOS 1501)
- With 8-3 release (8.47.1), to get XVideo working I added Option "TexturedVideo" "true" to the xorg.conf file. It wasn't necessary to edit the /etc/ati/amdpcsdb file as described in the paragraph above; the open GL overlay can be active and it will still work.
System lockup on logout or switch to virtual consoles
If your system locks up after you logout or when you try to switch to a virtual console, this might be an instance of this bug. It is likely that the problem only occurs for users with an Xorg version of at least 7.0. Probably it only affects users of DVI.
There is a workaround: Use a standard D-Sub VGA connector instead of the DVI connector.
This workaround was posted as a comment to another related bug: see here.
Unfortunately "D-sub" users (like me) have the same problem.
BigDesktop (Dual screen) doesn't work after GDM login screen
This can occur on Ubuntu Feisty Fawn & Gutsy.
System > Prefrences > Screen Resolution
Select the resolution that is a combination of both screen resolutions wide and your height.
If X crashes during login, go to a virtual console using Ctrl+Alt+F1, log in,
sudo vim /etc/X11/xorg.conf, and comment out the line which looks like the following:
Option "DesktopSetup" "something"
Computer Freezes while using fglrx (UMA and SIDEPORT)
If after choosing fglrx as your driver in either xorg.conf or xfree86.conf files, the computer freezes and becomes unresponsive while trying to start X this may be the solution.
Some ATI cards have the ability to run in three modes: UMA, SIDEPORT, or a combination of both. UMA mode is that one in which the video card does not use its dedicated memory, but rather uses and shares the system memory. On the other hand, SIDEPORT mode is the one in which the card uses its own dedicated memory. And finally, the third mode is a combination of the previous modes in which the card uses both the system memory and its dedicated memory.
If your computer hangs, this settings may be where the solution lies. If your computer hangs, try using either UMA by itself or a combination of both. However, if you choose the combination, make sure that the UMA one is at least 128MB. In my case, I have SIDEPORT 128MB and 128MB UMA. If I choose any less for UMA, it does not work. This is definetly not an attractive solution since it compromises your systems performance. Hopefully, this will be solved very soon.
On some systems, the BIOS screen may not offer a choice of UMA or SIDEPORT. In this case, you can try turning the amount of RAM dedicated to the video card down, from 128Mb to 64Mb for example.
On some ACER laptops (at least the TimelineX), this means that you need to set display adapter mode to DISCRETE in BIOS.
This was experienced with an ATI Radeon X1600 Pro 512mb:
After following instructions for both Method 1 and Method 2, whenever the Composite Extension is disabled, the display would be almost unusable, but the fglrxinfo command would display the correct information. If the Composite Extension is re-enabled the display would be usable, but fglrxinfo would report using mesa drivers.
To resolve the problem it maybe needed to lower the AGP Aperture setting in my BIOS to 128mb (or lower worked too). The AGP Aperture was initially set to 256mb. After setting the AGP Aperture to 128mb, everything worked perfectly; the Composite Extension is disabled, fglrxinfo reports the correct drivers, and direct rendering is enabled. Some systems may require setting the AGP Aperture to the highest setting (256mb or 512mb).
There's been a bug report regarding anomalies in Firefox as well.
OpenGL framebuffer Corruption
This problem has been experienced on Thinkpads (T60p) with an ATI MOBILITY FireGL V5250 running driver versions 7.12, 8.01 and 8.02. Whenever any OpenGL application is rendered, the rendered output appears "scrambled" and unreadable. This problem is not very well documented and both glxgears and fgl_glxgears display this anomaly when testing.
When Anti-Aliasing is forced, the problem resides.
A solution (tested with 8.02 on Ubuntu Gutsy) to this problem is to open the ATI/AMD Catalyst Control Center and expand the item labeled '3D' in the options tree on the left-hand side of the window. From there, select "Anti-Aliasing" and check the box which reads: "Override application setting". Apply the settings and close the control center.
For an example of this anomaly, please see this image
This solution not work on acer laptop with ATI Mobility Radeon HD 2400 XT. kepfeltoltes.hu/view/080302/atisux_www.kepfeltoltes.hu_.jpg
Blank Screen with Xorg 1.3.0
If you happen to get a blank screen on X startup and you find lines similar to those in your Xorg.log:
2: /usr/lib64/xorg/modules/drivers//fglrx_drv.so(swlDalHelperValidateModeFromDAL 0x549) [...] 3: /usr/lib64/xorg/modules/drivers//fglrx_drv.so [...] 4: /usr/lib64/xorg/modules/drivers//fglrx_drv.so(atiddxPreInit 0x8b3) [...]
Then you're probably using the ati-drivers with Xorg-1.3.0. If that's the case the only solution (known to me) is to use a version < 1.3.0.
Edit: I got the same problem after using the --add-pairmode argument of aticonfig (using Xorg 1.3.0). My ati mobility x300 seemes to try sending the monitor signal to the vga output (even if no monitor is connected to it). After pressing [Fn]+[F8(CRT/LCD)] the monitor signal sometimes returnes to the internal laptop monitor. By switching to a console or shutting down the X-server, the card switches back to vga...
My solution: overwriting the file /etc/ati/amdpcsdb with /etc/ati/amdpcsdb.default (sudo cp /etc/ati/amdpcsdb.default /etc/ati/amdpcsdb) and restore the xorg.conf (since Xorg replaces /etc/X11/xorg.conf with a failsafe config file). Then reboot the system: fglrx should now work fine again with Xorg-1.3.0 .
Radeon GPU fan is very loud / constantly works
- See bug 499 for additional information.
It seems fglrx has a bug with all X800/X850 cards causing them to heat up excessively even when not in 3D mode. This behaviour will cause the cards' fans to function on full blast continuously. There is no known fix as of driver 8.31.05 or previous. Open source "radeon" driver does not exhibit this problem.
My Ati 1650GT has the same problem.It was normal when I enter ubuntu for 1 or 2minutes,and than ,the fan became crazy..No doubt it's because the temp~
It happens too with Radeon X1800 GTO and Radeon X1900 GT.
Possible solution (at least using a Mobility Radeon X1600):
To find out which powerstates your Radeon supports try:
If you use GDM, which is the default Login Manager on Ubuntu, modify
sudo gedit /etc/gdm/gdm.conf
If you use KDM, which is the default Login Manager on Kubuntu, add to the [X-:*-Core] section the following
sudo kate /etc/kde3/kdm/kdmrc
if you use xdm, add the following to
sudo gedit /etc/X11/xdm/xdm-config
System freezes at startup of Fedora 7 or RHEL 5.3 after installing the driver
Turn off the Redhat Graphical boot from grub config:
Edit the grub config file located at /boot/grub/grub.conf and remove the 'rhgb' from the kernel line in order to disable the Redhat Graphical boot.
This also works for Red Hat Enterprise Linux 5.3.
To solve this issue you need to disable atieventsd. On ubuntu you can run:
sudo /usr/sbin/update-rc.d -f atieventsd remove
Intermittent Freezes/Lockups due to AGPv3 running at 8x
Try forcing X to set AGP Speed to 4x
Option "AGPv3Mask" "0x00000002"
((Would be nice to put down WHERE to change this, not just to change this. The same applies to just about every hint shown above.))
+ You add it to the "Device" section for your graphics card in /etc/X11/xorg.conf.
Great hammer of Thor, that is powerfully helpufl!
UPDATE: The problem I have reported here is no more reproducible with the fglrx revision 11.03 (ati-driver-installer-11-3-x86.x86_64.run) within two months of testing. Many thanks to the guys that fixed this !
Strange name for a bug but this is what your kernel might say if your screen freeze completely while using two sessions and switching between them. The bug is more likely to occur while doing the session switch, but can also occur in a later moment. I have observed it while starting a new application, or while doing a simple page scrolling. Anyway, in case of this bug the graphic is completely unusable as well as the console switching, but the OS and non graphic application continue to work. A reboot it the only way I know to bring back the screen to normal operations. Then your /var/log/kernel.log might contain something like this:
Dec 16 07:22:13 cube kernel: [1178220.704151] BUG: unable to handle kernel NULL pointer dereference at 00000000000001c0 Dec 16 07:22:13 cube kernel: [1178220.704168] IP: [<ffffffffa030ef0f>] _ZN17SegmentMapManager13deleteMappingEP9CMMClient+0x3f/0x170 [fglrx] Dec 16 07:22:13 cube kernel: [1178220.704319] PGD 171a1b067 PUD 1b5376067 PMD 0 Dec 16 07:22:13 cube kernel: [1178220.704330] Oops: 0000 [#1] SMP Dec 16 07:22:13 cube kernel: [1178220.704337] last sysfs file: /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq Dec 16 07:22:13 cube kernel: [1178220.704346] CPU 1 Dec 16 07:22:13 cube kernel: [1178220.704351] Modules linked in: cramfs ext2 iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 iptable_filter ip_tables x_tables fglrx(P) ftdi_sio usbserial ext3 jbd mbcache btrfs nls_utf8 zlib_deflate nls_cp437 crc32c vfat fat libcrc32c radeon ttm drm_kms_helper drm i2c_algo_bit ppdev lp sco bridge stp bnep rfcomm l2cap crc16 powernow_k8 cpufreq_stats cpufreq_powersave cpufreq_conservative cpufreq_userspace binfmt_misc fuse loop snd_hda_codec_atihdmi snd_hda_codec_realtek snd_usb_audio snd _hda_intel snd_hda_codec snd_pcm_oss snd_mixer_oss snd_pcm snd_usb_lib snd_hwdep snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq snd_timer snd_seq_device sd_mod btusb crc_t10dif usblp asus_atk0110 bluetooth snd parport_pc i2c_piix4 parport psmouse rfkill button k8tem p i2c_core shpchp serio_raw processor pcspkr evdev soundcore pci_hotplug edac_core snd_page_alloc edac_mce_amd usbhid hid nfs lockd fscache nfs_acl auth_rpcgss sunrpc usb_storage ata_generic ahci firewire_ohci fi Dec 16 07:22:13 cube kernel: rewire_core crc_itu_t sky2 thermal thermal_sys pata_atiixp libata ohci_hcd ehci_hcd scsi_mod usbcore nls_base [last unloaded: fglrx] Dec 16 07:22:13 cube kernel: [1178220.704516] Pid: 7344, comm: Xorg Tainted: P W 2.6.32-5-amd64 #1 System Product Name Dec 16 07:22:13 cube kernel: [1178220.704516] RIP: 0010:[<ffffffffa030ef0f>] [<ffffffffa030ef0f>] _ZN17SegmentMapManager13deleteMappingEP9CMMClient+0x3f/0x170 [fglrx] Dec 16 07:22:13 cube kernel: [1178220.704516] RSP: 0018:ffff88003e91bc38 EFLAGS: 00010292 Dec 16 07:22:13 cube kernel: [1178220.704516] RAX: 0000000000000000 RBX: ffffc9001236f620 RCX: 00000000000006b0 Dec 16 07:22:13 cube kernel: [1178220.704516] RDX: 0000000000000000 RSI: ffffc90012398e00 RDI: 0000000000000140 Dec 16 07:22:13 cube kernel: [1178220.704516] RBP: ffffc90012398e00 R08: ffff88020b560008 R09: ffffc9001237b620 Dec 16 07:22:13 cube kernel: [1178220.704516] R10: 00000000000006bc R11: 0000000000000001 R12: ffff88003e91bc58 Dec 16 07:22:13 cube kernel: [1178220.704516] R13: 00000000000001c0 R14: ffffc90012398e00 R15: 0000000000000140 Dec 16 07:22:13 cube kernel: [1178220.704516] FS: 00007f52b107d700(0000) GS:ffff880008480000(0000) knlGS:00000000f75858d0 Dec 16 07:22:13 cube kernel: [1178220.704516] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Dec 16 07:22:13 cube kernel: [1178220.704516] CR2: 00000000000001c0 CR3: 00000001712a7000 CR4: 00000000000006e0 Dec 16 07:22:13 cube kernel: [1178220.704516] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Dec 16 07:22:13 cube kernel: [1178220.704516] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 Dec 16 07:22:13 cube kernel: [1178220.704516] Process Xorg (pid: 7344, threadinfo ffff88003e91a000, task ffff88020bf5a350) Dec 16 07:22:13 cube kernel: [1178220.704516] Stack: Dec 16 07:22:13 cube kernel: [1178220.704516] 000000001238c660 ffffffffa0389489 0000000000000100 0000000000000148 Dec 16 07:22:13 cube kernel: [1178220.704516] <0> 0000000000000000 0000000000000000 000002af00000068 ffffffffa038c6e7 Dec 16 07:22:13 cube kernel: [1178220.704516] <0> 00000000000001c0 000000000019330c 00007f52ab7a2000 ffffc9001236f620 Dec 16 07:22:13 cube kernel: [1178220.704516] Call Trace: Dec 16 07:22:13 cube kernel: [1178220.704516] [<ffffffffa0311680>] ? _ZN3MSF9free_surfEP9CMMDriverP10CMMSurface+0x50/0xe0 [fglrx] Dec 16 07:22:13 cube kernel: [1178220.704516] [<ffffffffa030d391>] ? CMMFreeSurface+0x131/0x1b0 [fglrx] Dec 16 07:22:13 cube kernel: [1178220.704516] [<ffffffffa031d24c>] ? _Z8uCWDDEQCmjjPvjS_+0x68c/0xf00 [fglrx] Dec 16 07:22:13 cube kernel: [1178220.704516] [<ffffffffa02d2114>] ? firegl_cmmqs_CWDDE_32+0x334/0x440 [fglrx] Dec 16 07:22:13 cube kernel: [1178220.704516] [<ffffffffa02d0ba0>] ? firegl_cmmqs_CWDDE32+0x70/0x100 [fglrx] Dec 16 07:22:13 cube kernel: [1178220.704516] [<ffffffffa02d0b30>] ? firegl_cmmqs_CWDDE32+0x0/0x100 [fglrx] Dec 16 07:22:13 cube kernel: [1178220.704516] [<ffffffffa02b0b5a>] ? firegl_ioctl+0x1ea/0x250 [fglrx] Dec 16 07:22:13 cube kernel: [1178220.704516] [<ffffffff810fa4c7>] ? vfs_ioctl+0x56/0x6c Dec 16 07:22:13 cube kernel: [1178220.704516] [<ffffffff810fa9e0>] ? do_vfs_ioctl+0x48d/0x4cb Dec 16 07:22:13 cube kernel: [1178220.704516] [<ffffffff812fd946>] ? do_page_fault+0x2e0/0x2fc Dec 16 07:22:13 cube kernel: [1178220.704516] [<ffffffff810faa6f>] ? sys_ioctl+0x51/0x70 Dec 16 07:22:13 cube kernel: [1178220.704516] [<ffffffff81010b42>] ? system_call_fastpath+0x16/0x1b Dec 16 07:22:13 cube kernel: [1178220.704516] Code: 4c 8d 64 24 20 c7 44 24 04 00 00 00 00 4c 8d af 80 00 00 00 48 c7 44 24 20 00 00 00 00 48 c7 44 24 28 00 00 00 00 4c 89 6c 24 40 <49> 8b 5d 00 31 c0 48 85 db 48 89 5c 24 30 74 04 48 8b 43 30 49 Dec 16 07:22:13 cube kernel: [1178220.704516] RIP [<ffffffffa030ef0f>] _ZN17SegmentMapManager13deleteMappingEP9CMMClient+0x3f/0x170 [fglrx] Dec 16 07:22:13 cube kernel: [1178220.704516] RSP <ffff88003e91bc38> Dec 16 07:22:13 cube kernel: [1178220.704516] CR2: 00000000000001c0 Dec 16 07:22:13 cube kernel: [1178220.705883] ---[ end trace c9192c1a2722dc89 ]---
As fglrx source is closed, it will b difficult to catch this bug without AMD internal resource. If someone from AMD read this: please catch this bug. It is there from a least the last couple of monthly driver and really make my machine unable to do the work it was intended to do. I first see this bug using a Debian Lenny AMD64 with a old kernel. I recently upgraded to Debian Squeeze AMD64 with his last kernel, but the bug is exactly the same.
[SOLVED] System freeze / Catalyst 11-9 / "unable to handle kernel NULL pointer dereference at ..."
Similar to previous section, mouse and keyboard unresponsive afer a ramdomly amount of time.
Linux Debian Squeeze + sid fglrx packages Desktop Motherboaord ASUS P5KPL - 4GB RAM Intel E8500 3.16GHz ACPI DISABLED
X.Org X Server 1.7.7 Release Date: 2010-05-04 X Protocol Version 11, Revision 0 Build Operating System: Linux 2.6.37-trunk-amd64 x86_64 Debian Current Operating System: Linux Joelle 2.6.32- #1 SMP Sat Oct 8 21:03:45 CEST 2011 x86_64 xorg-server 2:1.7.7-13 Current version of pixman: 0.16.4Section "Device"
Section "Device" Identifier "RADEON HD2600 - fglrx" Driver "fglrx" BusID "PCI:2:0:0" #Option "SWCursor" "true" Option "TexturedVideo" "on" Option "TexturedVideoSync" "true" Option "VideoOverlay" "on" Option "OpenGLOverlay" "off" # ATI #Option "AccelMethod" "EXA" #Option "AGPMode" "4" #Option "EnablePageFlip" "true" #Option "DDCMode" # NOTUSED Option "RenderAccel" "true" #Option "SubPixelOrder" "NONE" #Option "ColorTiling" "false" #Option "backingstore" "true" #---- # NOTUSED Option "XAANoOffscreenPixmaps" "true" # NOTUSED Option "AddARGBGLXVisuals" "true" # NOTUSEDOption "AllowGLXWithComposite" "true" EndSection
Vendor: ATI Technologies Inc Device: RV630 [Radeon HD 2600 Series] SVendor: PC Partner Limited SDevice: Device e410
BIOS_CREATION_DATE="09/05/07 21:52" BIOS_MSG="11X-1E410ASA-001 RV630 GDDR2 128BIT 256MB 600E/500M" BIOS_KIT_VERSION="BK-ATI VER010.059.000.003.000000" BIOS_PN="113-B1E41QIM-X01"
Date 09/05/07 21:52 Version 010.059.000.003.000000 Part Number 113-B1E41QIM-X01
Type DDR2 Clock 500 MHz Size 256 MB Bandwidth 16.0 GBytes/s
Graphics Capability PCI Express Maximum Setting x16 Core Clock 600 MHz
Catalyst version 10.9 Driver Packaging Version 8.771-100825a-104565C-ATI 2D Driver Version 8.89.4 Catalyst Control Center Version 2.13 RandR Version 1.3
OpenGL Provider Advanced Micro Devices, Inc. OpenGL Renderer ATI Radeon HD 2600 Pro OpenGL Version 3.3.11079 Compatibilty Profile COntext
BUG trace in syslog
Oct 8 23:17:33 Joelle kernel: [ 3922.443571] BUG: unable to handle kernel NULL pointer dereference at 0000000000000008 Oct 8 23:17:33 Joelle kernel: [ 3922.443576] IP: [<ffffffffa024b8d1>] _ZN20CMMHeap_SystemMemory8pushPoolEP7CMMPool+0x11/0x40 [fglrx] Oct 8 23:17:33 Joelle kernel: [ 3922.443623] PGD 37736067 PUD 5cfd6067 PMD 0 Oct 8 23:17:33 Joelle kernel: [ 3922.443626] Oops: 0002 [#1] SMP Oct 8 23:17:33 Joelle kernel: [ 3922.443628] last sysfs file: /sys/devices/pci0000:00/0000:00:1f.1/host0/target0:0:0/0:0:0:0/block/sda/uevent Oct 8 23:17:33 Joelle kernel: [ 3922.443631] CPU 1 Oct 8 23:17:33 Joelle kernel: [ 3922.443632] Modules linked in: binfmt_misc fuse coretemp w83627ehf hwmon_vid drm loop snd_hda_codec_atihdmi snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep snd_pcm_oss snd_mixer_oss snd_pcm snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq snd_timer snd_seq_device snd i2c_i801 soundcore snd_page_alloc i2c_core pcspkr fglrx(P) rng_core evdev psmouse serio_raw ext3 jbd mbcache dm_mod sd_mod crc_t10dif ata_generic uhci_hcd ata_piix libata ehci_hcd scsi_mod usbcore nls_base [last unloaded: scsi_wait_scan] Oct 8 23:17:33 Joelle kernel: [ 3922.443656] Pid: 1521, comm: Xorg Tainted: P 2.6.32- #1 System Product Name Oct 8 23:17:33 Joelle kernel: [ 3922.443657] RIP: 0010:[<ffffffffa024b8d1>] [<ffffffffa024b8d1>] _ZN20CMMHeap_SystemMemory8pushPoolEP7CMMPool+0x11/0x40 [fglrx] Oct 8 23:17:33 Joelle kernel: [ 3922.443686] RSP: 0018:ffff8800370bb970 EFLAGS: 00010297 Oct 8 23:17:33 Joelle kernel: [ 3922.443687] RAX: ffff880037638008 RBX: ffffc9000144a150 RCX: 0000000000000000 Oct 8 23:17:33 Joelle kernel: [ 3922.443689] RDX: 0000000000000000 RSI: ffffc9000144a018 RDI: ffff880037638de8 Oct 8 23:17:33 Joelle kernel: [ 3922.443690] RBP: 0000000000000002 R08: ffffffffa0278bb0 R09: ffff880037638008 Oct 8 23:17:33 Joelle kernel: [ 3922.443692] R10: ffffc9000144a090 R11: ffff880037638008 R12: ffff880037638de8 Oct 8 23:17:33 Joelle kernel: [ 3922.443693] R13: 0000000000000040 R14: 0000000000000000 R15: 0000000000000000 Oct 8 23:17:33 Joelle kernel: [ 3922.443695] FS: 00007fb0e561d700(0000) GS:ffff880001700000(0000) knlGS:0000000000000000 Oct 8 23:17:33 Joelle kernel: [ 3922.443697] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Oct 8 23:17:33 Joelle kernel: [ 3922.443698] CR2: 0000000000000008 CR3: 000000003776b000 CR4: 00000000000006e0 Oct 8 23:17:33 Joelle kernel: [ 3922.443700] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Oct 8 23:17:33 Joelle kernel: [ 3922.443702] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 Oct 8 23:17:33 Joelle kernel: [ 3922.443704] Process Xorg (pid: 1521, threadinfo ffff8800370ba000, task ffff8800377d3100) Oct 8 23:17:33 Joelle kernel: [ 3922.443705] Stack: Oct 8 23:17:33 Joelle kernel: [ 3922.443706] ffffffffa024b2f6 0000000000000000 ffff880037638de8 ffff880037638e78 Oct 8 23:17:33 Joelle kernel: [ 3922.443709] <0> 0000000000000200 0000000000000000 ffffffffa01e45d5 0000000000080000 Oct 8 23:17:33 Joelle kernel: [ 3922.443711] <0> ffff880037638de8 ffffffffa0278bb0 ffffffffa01e4938 0000000000000000 Oct 8 23:17:33 Joelle kernel: [ 3922.443714] Call Trace: Oct 8 23:17:33 Joelle kernel: [ 3922.443743] [<ffffffffa024b2f6>] ? _ZN7CMMHeap15createPoolSpaceI21CMMPoolAsicAccessibleEEbj+0xb6/0xc0 [fglrx] Oct 8 23:17:33 Joelle kernel: [ 3922.443788] [<ffffffffa01e45d5>] ? _ZN20CMMHeap_SystemMemory10obtainPoolEv+0x85/0xc0 [fglrx] Oct 8 23:17:33 Joelle kernel: [ 3922.443831] [<ffffffffa01e4938>] ? _ZN16CMMHeap_PAGEABLE10expandHeapEm+0x18/0xb0 [fglrx] Oct 8 23:17:33 Joelle kernel: [ 3922.443860] [<ffffffffa024b0ea>] ? _ZN7CMMHeap10expandHeapEmRmPv+0xa/0x10 [fglrx] Oct 8 23:17:33 Joelle kernel: [ 3922.443904] [<ffffffffa01e32ed>] ? _ZN7CMMHeap21allocateMorePoolSpaceEmPv+0x8d/0x1b0 [fglrx] Oct 8 23:17:33 Joelle kernel: [ 3922.443947] [<ffffffffa01e1cbe>] ? _ZN14CMMHeapManager13allocPageableEjR14CMM_ALLOCATION+0xbe/0x100 [fglrx] Oct 8 23:17:33 Joelle kernel: [ 3922.443992] [<ffffffffa020a1f1>] ? AddrComputeSurfaceInfo+0x31/0x50 [fglrx] Oct 8 23:17:33 Joelle kernel: [ 3922.444036] [<ffffffffa01ebc57>] ? _ZN9CMMObjectnwEmP8CMM_CORE+0x37/0x70 [fglrx] Oct 8 23:17:33 Joelle kernel: [ 3922.444080] [<ffffffffa01ef7a2>] ? _ZN8MSF_CORE21get_surface_structureEv+0xc2/0xe0 [fglrx] Oct 8 23:17:33 Joelle kernel: [ 3922.444122] [<ffffffffa01da40f>] ? _ZN3MSF11create_surfEP9CMMClientP9CMMDriverPvRA4_K14CMM_ALLOCATIONP16MSF_SURF_ATTRIBS+0x1f/0x1c0 [fglrx] Oct 8 23:17:33 Joelle kernel: [ 3922.444164] [<ffffffffa01dbaf3>] ? _ZN3MSF21handle_shared_surfaceEP9CMMClientP9CMMDriverP10CMMSurfaceP16MSF_SURF_ATTRIBSP15_CMM_RETURNCODE+0x113/0x280 [fglrx] Oct 8 23:17:33 Joelle kernel: [ 3922.444206] [<ffffffffa01d61aa>] ? CMMAllocSurface_WA+0x62a/0xab0 [fglrx] Oct 8 23:17:33 Joelle kernel: [ 3922.444235] [<ffffffffa018a522>] ? firegl_trace+0x72/0x1e0 [fglrx] Oct 8 23:17:33 Joelle kernel: [ 3922.444278] [<ffffffffa01e7219>] ? _Z8uCWDDEQCmjjPvjS_+0xb59/0x10c0 [fglrx] Oct 8 23:17:33 Joelle kernel: [ 3922.444307] [<ffffffffa018ca32>] ? firegl_cmmqs_CWDDE_32+0x332/0x440 [fglrx] Oct 8 23:17:33 Joelle kernel: [ 3922.444336] [<ffffffffa018b360>] ? firegl_cmmqs_CWDDE32+0x70/0x100 [fglrx] Oct 8 23:17:33 Joelle kernel: [ 3922.444365] [<ffffffffa018b2f0>] ? firegl_cmmqs_CWDDE32+0x0/0x100 [fglrx] Oct 8 23:17:33 Joelle kernel: [ 3922.444389] [<ffffffffa0169fd8>] ? firegl_ioctl+0x1e8/0x250 [fglrx] Oct 8 23:17:33 Joelle kernel: [ 3922.444412] [<ffffffffa0160c75>] ? ip_firegl_unlocked_ioctl+0x9/0xd [fglrx] Oct 8 23:17:33 Joelle kernel: [ 3922.444417] [<ffffffff810e34d8>] ? vfs_ioctl+0x19/0x83 Oct 8 23:17:33 Joelle kernel: [ 3922.444419] [<ffffffff810e3a22>] ? do_vfs_ioctl+0x46e/0x4b2 Oct 8 23:17:33 Joelle kernel: [ 3922.444422] [<ffffffff810d8216>] ? vfs_read+0xc7/0xfc Oct 8 23:17:33 Joelle kernel: [ 3922.444424] [<ffffffff810e3aa2>] ? sys_ioctl+0x3c/0x5c Oct 8 23:17:33 Joelle kernel: [ 3922.444428] [<ffffffff8100ba6b>] ? system_call_fastpath+0x16/0x1b Oct 8 23:17:33 Joelle kernel: [ 3922.444429] Code: 00 00 00 00 00 00 00 00 00 00 48 8d 47 60 c3 00 00 00 00 00 00 00 00 00 00 00 31 c9 48 8b 97 90 00 00 00 83 7e 18 02 48 0f 44 ce <48> 89 51 08 ff 87 98 00 00 00 48 89 8f 90 00 00 00 c3 00 00 00 Oct 8 23:17:33 Joelle kernel: [ 3922.444449] RIP [<ffffffffa024b8d1>] _ZN20CMMHeap_SystemMemory8pushPoolEP7CMMPool+0x11/0x40 [fglrx] Oct 8 23:17:33 Joelle kernel: [ 3922.444477] RSP <ffff8800370bb970> Oct 8 23:17:33 Joelle kernel: [ 3922.444478] CR2: 0000000000000008 Oct 8 23:17:33 Joelle kernel: [ 3922.444480] ---[ end trace dbbddd5ad13ce08c ]---
Tried : Installed a more recent kernel ( 18.104.22.168 ) , Removed sid fglrx package, and installed a previous version "ati-driver-installer-11-6-x86.x86_64.run" downloaded from ADM site -> bug still present
Trying now "ati-driver-installer-10-9-x86.x86_64.run"
Solved ! New ATI drivers conflict with kms. So you have to disable kms ( for example append "nomodeset" on your kernel boot line )
An Example of a working Xorg.conf
Lots of trial and error changing Options to get Compiz-Fusion running under Mandriva 2008-2010. X Server 1.6.5 (Sadly, the 'drak' tools that come with Mandriva to configure are worthless.)
In this instance it was chosen to remove packaged drivers and install from .bin file from AMD/ATI.
Most Options were added per 'aticonfig -f --initial ... ...'. And the rest were added as needed. Constantly checking '/var/log/Xorg.0.log' for errors and warnings.
Section "ServerLayout" Identifier "aticonfig Layout" Screen 0 "aticonfig-Screen-0" 0 0 # The extra zeros are necessary for some reason Option "AIGLX" EndSection Section "Files" EndSection Section "Module" Load "dbe" Load "v4l" Load "extmod" Load "type1" Load "freetype" Load "glx" Load "dri" EndSection Section "Monitor" Identifier "aticonfig-Monitor-0" Option "VendorName" "Hewlett-Packard" Option "ModelName" "HP D2845 Ergo 1600 21-inch Display" HorizSync 31.5-95.0 VertRefresh 50.0-160.0 Option "DPMS" "true" EndSection Section "Device" Identifier "aticonfig-Device-0" Driver "fglrx" BusID "PCI:1:0:0" Option "UseFastTLS" "2" Option "Textured2D" "on" Option "TexturedXrender" "off" Option "BackingStore" "on" Option "VideoOverlay" "off" Option "OpenGLOverlay" "off" 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 "Extensions" Option "Composite" "on" Option "RENDER" "on" # essential for proper window border rendering Option "DAMAGE" "on" # compiz-fusion calls for explicitly EndSection
Open for scrutiny and testing.
Sticky mouse cursor
Some users reported that the mouse cursor gets stuck when the mouse is moved to the lower right corner. At least in several versions of Ubuntu using Gnome desktop and starting with Catalyst 11.4.
That seems to be solved when adding ""load "dri"" to "Section Module" of xorg.conf.
[SOLVED] RadeonHD6670 & Catalyst 13.4 : X server crash ( segmentation fault after __driCreateNewScreen in fglrx_dri.so ) / KMS working
Linux Debian Wheezy + AMD installer Kernel 3.2.46 #1 SMP Wed Aug 21 11:01:42 CEST 2013 x86_64 GNU/Linux ACPI disabled AMD TURKS firmwares included Desktop Motherboaord ASUS P5KPL - 4GB RAM Intel E8500 3.16GHz
BUG trace in syslog
(...) ukiDynamicMajor: found major device number 252 [ 304.303] ukiDynamicMajor: found major device number 252 [ 304.303] ukiOpenByBusid: Searching for BusID PCI:2:0:0 [ 304.303] ukiOpenDevice: node name is /dev/ati/card0 [ 304.303] ukiOpenDevice: open result is 12, (OK) [ 304.303] ukiOpenByBusid: ukiOpenMinor returns 12 [ 304.303] ukiOpenByBusid: ukiGetBusid reports PCI:2:0:0 [ 304.346] [ 304.346] Backtrace: [ 304.346] 0: /usr/bin/Xorg (xorg_backtrace+0x36) [0x7faadd5d1d06] [ 304.346] 1: /usr/bin/Xorg (0x7faadd453000+0x182859) [0x7faadd5d5859] [ 304.346] 2: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7faadc77b000+0xf030) [0x7faadc78a030] [ 304.346] 3: /lib/x86_64-linux-gnu/libc.so.6 (0x7faadb484000+0x11fc45) [0x7faadb5a3c45] [ 304.346] 4: /usr/lib/dri/fglrx_dri.so (__driCreateNewScreen_20050727+0x56) [0x7faad542e0c6] [ 304.346] 5: /usr/lib/xorg/modules/extensions/libglx.so (0x7faad9d4c000+0x1e0ea) [0x7faad9d6a0ea] [ 304.346] 6: /usr/lib/xorg/modules/extensions/libglx.so (0x7faad9d4c000+0x1fb05) [0x7faad9d6bb05] [ 304.346] 7: /usr/bin/Xorg (InitExtensions+0x99) [0x7faadd510889] [ 304.346] 8: /usr/bin/Xorg (0x7faadd453000+0x41d42) [0x7faadd494d42] [ 304.346] 9: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xfd) [0x7faadb4a2ead] [ 304.346] 10: /usr/bin/Xorg (0x7faadd453000+0x4219d) [0x7faadd49519d] [ 304.346] [ 304.346] Segmentation fault at address 0x7fff00000014 [ 304.346] Fatal server error: [ 304.346] Caught signal 11 (Segmentation fault). Server aborting
The solution is : downgrade AMD driver.
I could these AMD driver working:
AMD Catalyst installer (legacy) 13.1 ( installer says version 8.97.2 ) AMD Catalyst installer (non-legacy) 13.1 ( installer says version 9.012 )
-> both seems to be the same, kernel module version reported in Xorg.0.log is always 8.97.2 !
They both sticks "AMD Unsupported hardware" in the low-right corner of my monitor ( which can be removed easily ).
Seems that from version 13.4, the software was deeply modified, that make it buggy.
KMS works well ( module radeon.ko ). I have frame buffer kernel module ( radeonfb.ko ) built but I didnt try for instant to load it simultaneously with KMS.
If you get the message ‘‘aticonfig: No supported adapters detected’’, you might have a card not officially supported by the fglrx driver but that might still work when forcing the driver to load. See Ubuntu#Unsupported_adapter.
X server dies at start, possibly with error segmentation fault at address 0x8
- aticonfig can mess up the fglrx config in /etc/ati/amdpcsdb, try overwriting with /etc/ati/amdpcsdb.default
"VideoOverlay" "on" "OpenGLOverlay" "off" "UseInternalAGPGART" "yes" (10/2011, on cat-11.9, ATI 6300 aka 9803)
AMD installer script completes, fglrx X driver loads, fglrxinfo reports error
Xorg.log reports 2d/3d acceleration disabled, DRI disabled and uki errors related to /proc/ati files. AMD control panel works.
This can happen if there is a problem w/ the AMD installer compiling the fglrx.ko kernel module. The installation completes anyway with the fglrx Xorg driver in place. As per 22.214.171.124 and the 12.1 AMD driver there was a compile error in/usr/src/fglrx-8.93/firegl_public.c, due to TS_USEDFPU macro not being defined. Other compile-time errors will produce a similar problem. Check the contents of /usr/share/ati/fglrx-install.log, note if there was a compile error. If so, re-running the AMD installer will not fix the problem since the compile error will just recur. Likewise, patching the bug ie
and then reinstalling won't help either since the installer re-extracts the source from the archive. To fix, apply whatever fix is required to the sourcecode that the installer leaves in /usr/src/fglrx-xxx and use dkms to compile and install the driver.
dkms add fglrx/8.93 /usr/src/fglrx-8.93
dkms build fglrx/8.93
dkms install fglrx/8.93
Apply fixes to the fglrx source and repeat the dkms build step until the build completes, then install & reboot. Check lsmod output to see if fglrx.ko is loaded, confirm DRI and proc stuff in Xorg.log is working.
In the 126.96.36.199 w/ 12.1 bug case, the fix is to add the TS_USEDFPU ifdef in firegl_public.c as below;
void ATI_API_CALL KCL_fpu_begin(void)
preempt_disable(); if (__thread_has_fpu(current)) __save_init_fpu(current);
struct thread_info *cur_task = current_thread_info(); preempt_disable(); if (cur_task->status & TS_USEDFPU) __save_init_fpu(cur_task->task);
X fails - fglrx module not found
Using the latest Catalyst driver (14.501 9 Dec 2014) Xorg log complains that fglrx module not found. (on Debian)
Modprobe shows that fglrx module is loaded.
Explanation: xorg is looking in /usr/lib/xorg/modules and /usr/lib but drivers and libs were installed in /usr/lib64/xorg/modules and /usr/lib64
Solution: make appropriate symlinks from /usr/lib64/xorg/modules to /usr/lib/xorg/modules and from /usr/lib64 to /usr/lib
- http://ati.cchtml.com/show_bug.cgi?id=239 Going back to gdm/kdm/xdm hardlocks after running X session
- http://www.phoronix.com/forums/showthread.php?t=7448&page=5 System lockup on logout with catalyst 8.01
|Distribution Neutral Steps|