fglrx 9.3.1

[nico80]

I can't seem to start X after updating xorg-x11-drv-fglrx to 9.3.1 (Fedora 10, ATI Radeon HD3470)

Anyone else has a similar problem?

[ShivaS]

Any error message (check /var/log/Xorg* log files )?

[nico80]

Sorry, my bad, I should have been a bit more precise.

No error messages at all.
The problem, though, is that the mouse cursor shows up and then hangs there (have to reset the computer...) so maybe there is an error but is not being logged (?)

Changing driver to ati or radeon solves the problem (but i get no 3D acceleration).
Haven't tried to downgrade the package yet. I will try tonight.

[Firewing1]

What do you mean by 9.3.1? ATI's only released 9.3 and 9.4 (beta)...

Can you pastebin your /etc/X11/xorg.conf and /var/log/Xorg.0.log files?

[nico80]

Hmmmm... it's actually 9.3-1

This guy here:
xorg-x11-drv-fglrx-libs-9.3-1.fc10.i386

EDIT: my xorg.conf

Section "ServerLayout"
Identifier "single head configuration"
Screen 0 "Screen0" 0 0
Option "AIGLX" "on"
EndSection

Section "Module"
Load "dri"
Load "glx"
EndSection

Section "ServerFlags"
Option "AIGLX" "on"
EndSection

Section "Device"
Identifier "ATI Radeon HD 3470"
Driver "fglrx"
Option "OpenGLOverlay" "off"
Option "VideoOverlay" "on"
Option "XAANoOffscreenPixmaps" "on"
EndSection

Section "Screen"
Identifier "Screen0"
Device "ATI Radeon HD 3470"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection

Section "DRI"
Mode 0666
EndSection

Section "Extensions"
Option "Composite" "Enable"
Option "RENDER" "Enable"
EndSection

[Firewing1]

Ah, okay so that's the 9.3 driver then. The -1 is the RPM release that's bumped at RPM Fusion if things change in the packaging but not at the driver level.

Can you post a pastebin link to your xorg.conf file? I have the feeling I know what's wrong (modulepaths)...
Edit: Saw your edit, thanks :p

[paladin_zero]

I can't seem to start X after updating xorg-x11-drv-fglrx to 9.3.1 (Fedora 10, ATI Radeon HD3470)

Anyone else has a similar problem?

Yes, I have the same problem. I did a yum update this morning, rebooted, and now when X tries to start, it fails and the computer crashes and reboots. This is with fglrx-9..3-1 and the 2.6.27.21-170.2.56 kernel. I tried booting with an old kernel, and then when it gets to X I get a blank screen, computer doesnt respond to ctrl-alt-del or ctrl-alt-bksp. Any advice on a workaround, or how I can get back a working desktop would be *greatly appreciated*, I'm in an aweful predicament without this computer.

[paladin_zero]

I didnt see anything out of the ordinary in the Xorg log, but I found this in dmesg, with the old kernel (I can't ssh in with the current kernel to inspect the logs):

Pid: 2995, comm: X Tainted: P (2.6.27.19-170.2.35.fc10.i686.PAE #1) emp
ty
EIP: 0060:[<f8b38306>] EFLAGS: 00003246 CPU: 1
EIP is at fill_gal_mapping_info+0x96/0x230 [fglrx]
EAX: 00000064 EBX: 00000000 ECX: 00000000 EDX: f1c68894
ESI: 00000000 EDI: f8c1eba0 EBP: 00000187 ESP: f1c689a0
DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068
Process X (pid: 2995, ti=f1c68000 task=f3018000 task.ti=f1c68000)
Stack: f8c15cea f8c1eba0 00000187 f8b38169 00000000 f2545bfc f372c138 f1c68a30
f2545c00 00000000 00001000 f8b36028 f2545c00 f1c68a30 00000028 00000232
00000000 f8c1f560 00000000 0000000f 00000000 0000000f 01000000 00000000
Call Trace:
[<f8b38169>] ? __mc_heap_insert_locked+0x79/0xd0 [fglrx]
[<f8b36028>] ? __mc_heap_map_to_gart_space+0x228/0x4b0 [fglrx]
[<f8b13bec>] ? drm_alloc+0x15c/0x1d0 [fglrx]
[<f8b3561a>] ? mc_heap_add_reserved_range+0x20a/0x350 [fglrx]
[<f8b30285>] ? __gart_init+0x375/0x8d0 [fglrx]
[<f8c03b45>] ? amdPcsCommand+0x145/0x620 [fglrx]
[<f8b2ff10>] ? __gart_init+0x0/0x8d0 [fglrx]
[<f8b2d7c4>] ? gal_init+0xd4/0x190 [fglrx]
[<f8b345ee>] ? mc_heap_init+0x12e/0x280 [fglrx]
[<f8b21d4f>] ? firegl_init_pcie+0x14f/0x4d0 [fglrx]
[<c04fede1>] ? avc_has_perm+0x39/0x43
[<c04fbe6c>] ? security_capable+0xc/0xe
[<f8b21c00>] ? firegl_init_pcie+0x0/0x4d0 [fglrx]
[<f8b1c94d>] ? firegl_ioctl+0x22d/0x2b0 [fglrx]
[<f8b126e9>] ? ip_firegl_ioctl+0xd/0xf [fglrx]
[<c04a2868>] ? vfs_ioctl+0x50/0x69
[<c04a2abc>] ? do_vfs_ioctl+0x23b/0x247
[<c0500700>] ? selinux_file_ioctl+0x35/0x38
[<c04a2b08>] ? sys_ioctl+0x40/0x5c
[<c0408b8b>] ? sysenter_do_call+0x12/0x34
=======================
Code: 24 8b 6c 24 28 83 c4 2c c3 b9 81 01 00 00 89 4c 24 08 8d 76 00 c7 04 24 ea
5c c1 f8 bf a0 eb c1 f8 89 7c 24 04 e8 7c ac fd ff cc <eb> c8 8b 77 34 31 db 89
74 24 18 8b 6e 18 31 f6 8b 55 0c 8b 45
EIP: [<f8b38306>] fill_gal_mapping_info+0x96/0x230 [fglrx] SS:ESP 0068:f1c689a0
---[ end trace 132e5011acc4fa9a ]---
[fglrx:firegl_release] *ERROR* device busy: 1 0
[fglrx] release failed with code -EBUSY

[Firewing1]

Aha, yup it's the modulepaths. Was xorg-x11-server-Xorg updated at the same time? It's been reported that one of the Xorg updates removes modulepaths from the xorg.conf, but unfortunately this breaks fglrx...
Section "ServerLayout"
Identifier "single head configuration"
Screen 0 "Screen0" 0 0
Option "AIGLX" "on"
EndSection

Section "Module"
Load "dri"
Load "glx"
EndSection

Section "ServerFlags"
Option "AIGLX" "on"
EndSection

Section "Device"
Identifier "ATI Radeon HD 3470"
Driver "fglrx"
Option "OpenGLOverlay" "off"
Option "VideoOverlay" "on"
Option "XAANoOffscreenPixmaps" "on"
EndSection

Section "Screen"
Identifier "Screen0"
Device "ATI Radeon HD 3470"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection

Section "DRI"
Mode 0666
EndSection

Section "Extensions"
Option "Composite" "Enable"
Option "RENDER" "Enable"
EndSection
The sections in red can be removed completely, Xorg should be autoconfiguring this. But back to the original problem... To re-add the module paths, just run:
fglrx-config-display disable
fglrx-config-display enable

[paladin_zero]

Aha, yup it's the modulepaths.

[...]

To re-add the module paths, just run:
fglrx-config-display disable
fglrx-config-display enable

Thank you very much, that solved the problem here.

[nico80]

also solved the problem here. Cheers :)

[axle_foley00]

Thanks, it solved the problem for me also. :)

[gbeagle]

That fixed my problem with starting X but now whenever I try to open anything that uses opengl it throws the following error


X Error of failed request: BadRequest (invalid request code or no such operation)
Major opcode of failed request: 155 (GLX)
Minor opcode of failed request: 19 (X_GLXQueryServerString)
Serial number of failed request: 12
Current serial number in output stream: 12


also
xdpyinfo | grep DRI
returns nothing

cat /var/log/Xorg.0.log | grep dri
X.Org XInput driver : 2.1
(II) "dri" will be loaded. This was enabled by default and also specified in the config file.
(II) LoadModule: "dri"
(II) Loading /usr/lib/xorg/modules/extensions/fglrx//libdri.so
(II) Module dri: vendor="X.Org Foundation"
(II) Loading /usr/lib/xorg/modules/drivers//fglrx_drv.so
(WW) This ATI Proprietary Linux Driver does not guarantee support of video driver ABI higher than 2.0
(WW) Video driver ABI version of the X server is 4.1
(II) AMD Video driver is running on a device belonging to a group targeted for this release
(II) AMD Video driver is signed
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: node name is /dev/dri/card1
drmOpenDevice: node name is /dev/dri/card2
drmOpenDevice: node name is /dev/dri/card3
drmOpenDevice: node name is /dev/dri/card4
drmOpenDevice: node name is /dev/dri/card5
drmOpenDevice: node name is /dev/dri/card6
drmOpenDevice: node name is /dev/dri/card7
drmOpenDevice: node name is /dev/dri/card8
drmOpenDevice: node name is /dev/dri/card9
drmOpenDevice: node name is /dev/dri/card10
drmOpenDevice: node name is /dev/dri/card11
drmOpenDevice: node name is /dev/dri/card12
drmOpenDevice: node name is /dev/dri/card13
drmOpenDevice: node name is /dev/dri/card14
(II) fglrx(0): board/chipset is supported by this driver (original ATI board)
(II) fglrx(0): 1. 520/560MHz @ 0Hz [enable load balancing, overdrive]
(II) fglrx(0): 2. 419/560MHz @ 0Hz [enable load balancing, overdrive]
(II) fglrx(0): 3. 527/560MHz @ 0Hz [overclocked, enable load balancing, overdrive]
(==) fglrx(0): OpenGL ClientDriverName: "fglrx_dri.so"
(WW) fglrx(0): No DRM connection for driver fglrx.
(II) fglrx(0): driver needs X.org 1.4.x.y with x.y >= 99.906
(WW) fglrx(0): * (maybe driver kernel module missing or bad) *
ABI class: X.Org XInput driver, version 2.1


so obviously the dri module isn't loading properly. If I boot into the previous version of the kernel the 9.3 drivers are working fine.

[Hypernix]

Hello,

I'm sure the trick previously described helped, but I had to do more tweaking to stop X from crashing and freezing my computer. :p

So what I did is comment out the line "DefaultDepth 24" in the Screen section. This causes X to fail to start complaining that the fglrx driver does not support 8 bit color. Then uncomment the line and X will start in 24 bit color with a fully functionnal fglrx driver.

I have no idea why it's behaving like this. This trick needs to be done every time the computer is restarted. So booting in run level 5 is not an option anymore :(

Hypernix

PS:

Here's my xorg.conf (I had a lot more stuff in there before with fglrx 9.2, but this now works for me with dual head screens)

Section "Files"
ModulePath "/usr/lib64/xorg/modules/extensions/fglrx"
ModulePath "/usr/lib64/xorg/modules"
EndSection

Section "Module"
EndSection

Section "ServerFlags"
Option "AIGLX" "on"
# Option "Xinerama" "off"
EndSection

Section "Device"
Identifier "Videocard0"
Driver "fglrx"
VendorName "Videocard Vendor"
BoardName "ATI Technologies Inc RV530LE [Radeon X1650 PRO]"
Option "OpenGLOverlay" "off"
Option "VideoOverlay" "on"
# BusID "PCI:2:0:0"
EndSection

Section "Screen"
Identifier "Screen0"
Device "Videocard0"
Monitor "Monitor0"
DefaultDepth 24
SubSection "Display"

# Modes "1280x1024"
# Depth 24
Viewport 0 0
EndSubSection
EndSection

Section "Extensions"
Option "Composite" "Enable"
EndSection

[Muspellsson]

Firewing1, thanks! I have this problem, and your tip solved it

[andro76]

Firewing, this solution works just fine. I temporarily changed to the vesa driver, but now I'v changed back to fglrx. Thanx...

[ildg]

Thanks to this thread.
I have the same problem and it took me a whole day to try and try to reinstall fedora10 again.

But I've found a new problem, akmod 9.31 makes glxgears become much slower than the akmod 9.3. Does someone got the same problem?

[Firewing1]

Thanks to this thread.
I have the same problem and it took me a whole day to try and try to reinstall fedora10 again.

But I've found a new problem, akmod 9.31 makes glxgears become much slower than the akmod 9.3. Does someone got the same problem?
Can you provide the RPM package versions? I'm not sure what you mean by 9.31 and 9.3... The first RPM packaged release of 9.3 is versioned as 9.3-1.

BTW - I've submitted a new build (xorg-x11-drv-fglrx-9.3-2) that should fix this issue. It will be in rpmfusion-nonfree-updates-testing soon.

[ildg]

Can you provide the RPM package versions? I'm not sure what you mean by 9.31 and 9.3... The first RPM packaged release of 9.3 is versioned as 9.3-1.

BTW - I've submitted a new build (xorg-x11-drv-fglrx-9.3-2) that should fix this issue. It will be in rpmfusion-nonfree-updates-testing soon.

Thank you, Firewing1:)

It's akmod-fglrx-9.3-1.fc10.i686 now.

I remembered very very well that the previous version of akmod-fglrx(maybe 9.2, since you said 9.31 is the first release of 9.3) is perfect on my computer, because the video playback is the smoothest ever to me.

I use fedora since 2006. My video card is radeon x1300. I can't remember how many times I reinstalled fedora due to updating ati video driver.

I suffered a lot from ati driver, but every time I see it getting better and better, I feel it worth it.

With previous of akmod-fglrx, I got over 1400 fps with glxgears. But with 9.3-1, I got only 900 fps.

I want to move back, but I can't find the old akmod-fglrx:mad:

Thank you, again.

[Firewing1]

Do you notice decreased performance in games/OpenGL applications? glxgears isn't a benchmark - as long as the animation is smooth, things are working normally. You can double-check by running:
glxinfo | grep -i direct
This should return "Yes".

[ildg]

Do you notice decreased performance in games/OpenGL applications? glxgears isn't a benchmark - as long as the animation is smooth, things are working normally. You can double-check by running:
glxinfo | grep -i direct
This should return "Yes".

$ glxinfo | grep -i direct
direct rendering: Yes

The first thing to do after installing fglrx is to run "glxinfo | grep -i direct". It's yes.

glxgears result is not a benchmark, but as I remember, everytime I successfully update the driver, the result will be a little higher.

I seldom play any 3d games under linux, but every day I will play some movies, the playback can tell me if the driver is OK or not.

But now I can't try it since the usb disk will not be automatically mounted anymore. This is another problem.;)

[Arith]

I've had similar problems. Since updating I've had shoddy 3d experiences. I had opened a thread (which honestly is a ghost town, so here I am here). Admittedly I was going by glxgears (not knowing that is not a reliable benchmark).

$ glxinfo | grep -i direct
direct rendering: Yes

Is my result, however glxgears does stutter ever so slightly, and if I try games such as open arena or urban terror.. they work.. but degraded 3d performance compared to pre-update. Urban terror has some serious input lag since as well.

I've tried all the suggestions listed in this thread with no change.

[Firewing1]

Can you pastebin the full output of "glxinfo"? Maybe it's using mesa's rendering instead of fglrx's...

[Arith]

Forgive me, I fear I may have been wasting people's time here. For the longest time I was going by glxgears as a benchmark.. somewhere down the line, I may have fixed it. I just tried urban terror again, and I'm pulling a solid 55-65fps with no noticable lag at all.

None the less, here is my output just in case;
http://pastebin.com/m71e1f58

From the looks of it, I don't think it's using mesa.

I have yet to look for myself, but do you know of a decent benchmarking tool that I can go by?

Thanks again, and sorry about that.

[ddotb]

Hello mates,

I have a similar problem, but when I run the test for direct rendering, I get the following:

$ glxinfo | grep -i direct
direct rendering: No (If you want to find out why, try setting LIBGL_DEBUG=verbose)

Can anyone tell me how I enable direct rendering???

Thanks

[Firewing1]

None the less, here is my output just in case;
http://pastebin.com/m71e1f58

From the looks of it, I don't think it's using mesa.

I have yet to look for myself, but do you know of a decent benchmarking tool that I can go by?

Thanks again, and sorry about that.
Yup, your renderer and vendor strings are "ATI" instead of "SGI" or "Mesa" so it's working as expected. I haven't really looked into benchmarking GPU performance so I can't offer much advice there, although you may want to look into phoronix-test-suite as the benchmarks done on Phoronix are all done on the phoronix-test-suite software.
Hello mates,

I have a similar problem, but when I run the test for direct rendering, I get the following:

$ glxinfo | grep -i direct
direct rendering: No (If you want to find out why, try setting LIBGL_DEBUG=verbose)

Can anyone tell me how I enable direct rendering???

Thanks
We need a bit more information - please pastebin your xorg.conf.

[ddotb]

Here is my output of xorg.cof:

# Xorg configuration created by system-config-display

Section "ServerLayout"
Identifier "single head configuration"
Screen 0 "Screen0" 0 0
InputDevice "Keyboard0" "CoreKeyboard"
EndSection

Section "InputDevice"
# keyboard added by rhpxl
Identifier "Keyboard0"
Driver "kbd"
Option "XkbModel" "pc105+inet"
Option "XkbLayout" "us"
EndSection

Section "Device"
Identifier "Videocard0"
Driver "intel"
EndSection

Section "Screen"
Identifier "Screen0"
Device "Videocard0"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection

[Firewing1]

Section "Device"
Identifier "Videocard0"
Driver "intel"
EndSection
What graphics hardware do you have? The fglrx driver is only compatible with ATI graphic cards, HD 2000 series and up. If you have other hardware, start another thread.

[ddotb]

ok thanks for the heads up

[AndyW]

I upgraded to xorg-x11-drv-fglrx 9.3 a few days ago (together with kernel 2.6.27.21 and a load of other package updates using yum) and had the problem with Fedora freezing as soon as the graphics display loaded. I tried fglrx-config-display diable / enable but still couldn't get anywhere.

In the end I removed all *fglrx* packages and reinstalled them following Leigh123's FC10 instructions. Now, when the X server tries to start it flashes through a load of display modes before gving up and dumping me at a flashing cursor. All I can do is Ctrl-Alt-F4 to get to a tty session.

These are the packages I have installed:
akmod-fglrx.x86_64 9.3-1.fc10
kmod-fglrx-2.6.27.21-170.2.56.fc10.x86_64.x86_64
xorg-x11-drv-fglrx.x86_64 9.3-2.fc10
xorg-x11-drv-fglrx-libs.i386 9.3-2.fc10
xorg-x11-drv-fglrx-libs.x86_64 9.3-2.fc10
This is my xorg.conf file:
# Xorg configuration created by livna-config-display

Section "ServerLayout"
Identifier "Default Layout"
Screen 0 "Screen0" 0 0
InputDevice "Keyboard0" "CoreKeyboard"
EndSection

Section "Files"
ModulePath "/usr/lib64/xorg/modules/extensions/fglrx"
ModulePath "/usr/lib64/xorg/modules"
EndSection

Section "ServerFlags"
Option "AIGLX" "on"
EndSection

Section "InputDevice"

# keyboard added by rhpxl
Identifier "Keyboard0"
Driver "kbd"
Option "XkbModel" "pc105"
Option "XkbLayout" "gb"
EndSection

Section "Device"
Identifier "Videocard0"
Driver "fglrx"
Option "OpenGLOverlay" "off"
Option "VideoOverlay" "on"
EndSection

Section "Screen"
Identifier "Screen0"
Device "Videocard0"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection

Section "Extensions"
Option "Composite" "Enable"
EndSection

This is what looks to be the relevant section at the end of the Xorg.log file:
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 14, (OK)
drmOpenByBusid: Searching for BusID PCI:1:0:0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 14, (OK)
drmOpenByBusid: drmOpenMinor returns 14
drmOpenByBusid: drmGetBusid reports PCI:1:0:0
(WW) AIGLX: 3D driver claims to not support visual 0x23
(WW) AIGLX: 3D driver claims to not support visual 0x24
(WW) AIGLX: 3D driver claims to not support visual 0x25
(WW) AIGLX: 3D driver claims to not support visual 0x26
(WW) AIGLX: 3D driver claims to not support visual 0x27
(WW) AIGLX: 3D driver claims to not support visual 0x28
(WW) AIGLX: 3D driver claims to not support visual 0x29
(WW) AIGLX: 3D driver claims to not support visual 0x2a
(WW) AIGLX: 3D driver claims to not support visual 0x2b
(WW) AIGLX: 3D driver claims to not support visual 0x2c
(WW) AIGLX: 3D driver claims to not support visual 0x2d
(WW) AIGLX: 3D driver claims to not support visual 0x2e
(WW) AIGLX: 3D driver claims to not support visual 0x2f
(WW) AIGLX: 3D driver claims to not support visual 0x30
(WW) AIGLX: 3D driver claims to not support visual 0x31
(WW) AIGLX: 3D driver claims to not support visual 0x32
(WW) AIGLX: 3D driver claims to not support visual 0x33
(WW) AIGLX: 3D driver claims to not support visual 0x34
(WW) AIGLX: 3D driver claims to not support visual 0x35
(WW) AIGLX: 3D driver claims to not support visual 0x36
(WW) AIGLX: 3D driver claims to not support visual 0x37
(WW) AIGLX: 3D driver claims to not support visual 0x38
(WW) AIGLX: 3D driver claims to not support visual 0x39
(WW) AIGLX: 3D driver claims to not support visual 0x3a
(WW) AIGLX: 3D driver claims to not support visual 0x3b
(WW) AIGLX: 3D driver claims to not support visual 0x3c
(WW) AIGLX: 3D driver claims to not support visual 0x3d
(WW) AIGLX: 3D driver claims to not support visual 0x3e
(WW) AIGLX: 3D driver claims to not support visual 0x3f
(WW) AIGLX: 3D driver claims to not support visual 0x40
(WW) AIGLX: 3D driver claims to not support visual 0x41
(WW) AIGLX: 3D driver claims to not support visual 0x42
(WW) AIGLX: 3D driver claims to not support visual 0x43
(WW) AIGLX: 3D driver claims to not support visual 0x44
(WW) AIGLX: 3D driver claims to not support visual 0x45
(WW) AIGLX: 3D driver claims to not support visual 0x46
(WW) AIGLX: 3D driver claims to not support visual 0x47
(WW) AIGLX: 3D driver claims to not support visual 0x48
(WW) AIGLX: 3D driver claims to not support visual 0x49
(WW) AIGLX: 3D driver claims to not support visual 0x4a
(WW) AIGLX: 3D driver claims to not support visual 0x4b
(WW) AIGLX: 3D driver claims to not support visual 0x4c
(WW) AIGLX: 3D driver claims to not support visual 0x4d
(WW) AIGLX: 3D driver claims to not support visual 0x4e
(WW) AIGLX: 3D driver claims to not support visual 0x4f
(WW) AIGLX: 3D driver claims to not support visual 0x50
(WW) AIGLX: 3D driver claims to not support visual 0x51
(WW) AIGLX: 3D driver claims to not support visual 0x52
(WW) AIGLX: 3D driver claims to not support visual 0x53
(WW) AIGLX: 3D driver claims to not support visual 0x54
(WW) AIGLX: 3D driver claims to not support visual 0x55
(WW) AIGLX: 3D driver claims to not support visual 0x56
(WW) AIGLX: 3D driver claims to not support visual 0x57
(WW) AIGLX: 3D driver claims to not support visual 0x58
(WW) AIGLX: 3D driver claims to not support visual 0x59
(WW) AIGLX: 3D driver claims to not support visual 0x5a
(WW) AIGLX: 3D driver claims to not support visual 0x5b
(WW) AIGLX: 3D driver claims to not support visual 0x5c
(WW) AIGLX: 3D driver claims to not support visual 0x5d
(WW) AIGLX: 3D driver claims to not support visual 0x5e
(WW) AIGLX: 3D driver claims to not support visual 0x5f
(WW) AIGLX: 3D driver claims to not support visual 0x60
(WW) AIGLX: 3D driver claims to not support visual 0x61
(WW) AIGLX: 3D driver claims to not support visual 0x62
(WW) AIGLX: 3D driver claims to not support visual 0x63
(WW) AIGLX: 3D driver claims to not support visual 0x64
(WW) AIGLX: 3D driver claims to not support visual 0x65
(WW) AIGLX: 3D driver claims to not support visual 0x66
(WW) AIGLX: 3D driver claims to not support visual 0x67
(WW) AIGLX: 3D driver claims to not support visual 0x68
(WW) AIGLX: 3D driver claims to not support visual 0x69
(WW) AIGLX: 3D driver claims to not support visual 0x6a
(WW) AIGLX: 3D driver claims to not support visual 0x6b
(WW) AIGLX: 3D driver claims to not support visual 0x6c
(WW) AIGLX: 3D driver claims to not support visual 0x6d
(WW) AIGLX: 3D driver claims to not support visual 0x6e
(WW) AIGLX: 3D driver claims to not support visual 0x6f
(WW) AIGLX: 3D driver claims to not support visual 0x70
(WW) AIGLX: 3D driver claims to not support visual 0x71
(WW) AIGLX: 3D driver claims to not support visual 0x72
(II) AIGLX: Loaded and initialized /usr/lib64/dri/fglrx_dri.so
(II) GLX: Initialized DRI GL provider for screen 0
(II) fglrx(0): Enable the clock gating!
(II) fglrx(0): Restoring recent mode: 1280x1024@60Hz

Backtrace:
0: /usr/bin/X(xorg_backtrace+0x26) [0x4e7c96]
1: /usr/bin/X(xf86SigHandler+0x39) [0x47a6a9]
2: /lib64/libc.so.6 [0x329a232f90]
3: /usr/bin/X(dixLookupPrivate+0x4) [0x42d5a4]
4: /usr/bin/X(xf86SetViewport+0x31) [0x476d41]
5: /usr/bin/X(ProcessInputEvents+0x51) [0x47af41]
6: /usr/bin/X(UpdateCurrentTime+0x46) [0x446b06]
7: /usr/bin/X(RRTellChanged+0x3d) [0x51dddd]
8: /usr/bin/X(xf86SetSingleMode+0x171) [0x4a2701]
9: /usr/lib64/xorg/modules/drivers//fglrx_drv.so(atiddxSwitchMode+0x74) [0x7fd281074fd4]
10: /usr/bin/X [0x4ac2ce]
11: /usr/bin/X [0x48207d]
12: /usr/bin/X(xf86SwitchMode+0xea) [0x476e5a]
13: /usr/lib64/xorg/modules/drivers//fglrx_drv.so [0x7fd28107da84]
14: /usr/lib64/xorg/modules/drivers//fglrx_drv.so [0x7fd28107c825]
15: /usr/bin/X [0x4a18f1]
16: /usr/bin/X(main+0x2e4) [0x42cbd4]
17: /lib64/libc.so.6(__libc_start_main+0xe6) [0x329a21e576]
18: /usr/bin/X [0x42c129]

Fatal server error:
Caught signal 11. Server aborting

(II) AIGLX: Suspending AIGLX clients for VT switch

This guy appears to have exactly the same issue as me: http://forums.fedoraforum.org/showpost.php?p=1195967&postcount=3256. The only info I could find on AIGLX: Suspending AIGLX clients for VT switch suggested disabling atieventsd, which I have done to no avail.

fglrx had been working fine for a few months up until now. Any suggestions? Do I have to completely reinstall Fedora, or can I downgrade fglrx to a more trouble-free version?

[rick10]

I have the same problem here. I have tried re-installing the drivers several times and no luck. I just backup the /etc/X11/xorg.conf and delete it. That way I can run the generic driver until we get a fix.

[Ravnos]

I have the same problem here, maybe it is a problem with the 64 bit version ? Downgrading was not an option, since the 9.2 drivers were not available in the rpmfusion repo. I will try the testing package later.

[Firewing1]

Can you pastebin your xorg.conf? Have you tried the instructions posted on pages 1/2 of the thread?

[Ravnos]

Can you pastebin your xorg.conf? Have you tried the instructions posted on pages 1/2 of the thread?

Yep, I tried with no luck. Things were fine with the 9.2 driver, now I'm using the radeon driver until I find time to try something else, I don't have the xorg.conf I was using before but It seemed fine ... no errors in Xorg.0.log either, it simply crashes :(