PDA

View Full Version : GLXBadContext after F7 to F8 upgrade



sceotend
12th November 2007, 06:14 AM
Upgraded to F8 this weekend, from F7 (which was working all nice with compiz-fusion and everything). While fglrx (Livna) appears to be working for X Windows, GLX isn't working at all.

I'm running an ATI Radeon X1900XTX video card in my system.



$ glxinfo
name of display: :0.0
X Error of failed request: GLXBadContext
Major opcode of failed request: 143 (GLX)
Minor opcode of failed request: 5 (X_GLXMakeCurrent)
Serial number of failed request: 16
Current serial number in output stream: 16


Same with fglrxinfo...



$ fglrxinfo
X Error of failed request: GLXBadContext
Major opcode of failed request: 143 (GLX)
Minor opcode of failed request: 5 (X_GLXMakeCurrent)
Serial number of failed request: 16
Current serial number in output stream: 16


No significant errors nor warnings in the Xorg.0.log file... (pretty much exactly the same output I had with F7 working fine).



$ grep EE /var/log/Xorg.0.log
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(II) Loading extension MIT-SCREEN-SAVER

$ grep WW /var/log/Xorg.0.log
grep WW /var/log/Xorg.0.log
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(WW) The core pointer device wasn't specified explicitly in the layout.
(WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
(WW) fglrx: No matching Device section for instance (BusID PCI:5:0:1) found
(WW) fglrx(0): Only one display is connnected,so single mode is enabled
(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
(WW) <default pointer>: No Device specified, looking for one...


My xorg.conf has the usual entries for making AIGLX work (at least they worked with F7, and the X server works in F8, but without glx functioning). I have played with the various Device options tossed about the forums to no effect.



# Xorg configuration created by livna-config-display

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

Section "Files"

EndSection

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

Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
Option "XkbModel" "pc105"
Option "XkbLayout" "us"
EndSection

Section "Monitor"
Identifier "Monitor0"
ModelName "Dell 2407WFP (Digital)"
HorizSync 30.0 - 83.0
VertRefresh 56.0 - 76.0
ModeLine "1920x1200" 154.0 1920 1968 2000 2080 1200 1203 1209 1235 -hsync +vsync
Option "dpms"
EndSection

Section "Device"
Identifier "Videocard0"
Driver "fglrx"
EndSection

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

Section "DRI"
Mode 0666
EndSection


I have the livna kmod-fglrx modules updated to match the kernel...



$ rpm -qa | grep kernel
kernel-doc-2.6.23.1-49.fc8
kernel-devel-2.6.23.1-49.fc8
kernel-headers-2.6.23.1-49.fc8
kernel-2.6.23.1-49.fc8

$ rpm -qa | grep fglrx
xorg-x11-drv-fglrx-8.42.3-7.lvn8.1
kmod-fglrx-2.6.23.1-49.fc8-8.42.3-8.lvn8
kmod-fglrx-8.42.3-8.lvn8


One thing I am seeing is that the xorg-x11-drv-fglrx package is 8.42.3-7, while the kmod-fglrx package for the kernel is 8.42.3-8, both from Livna. I can't get yum to perform an update for the xorg-x11-drv-fglrx package at this time (nothing newer available apparently). Could this be the problem and an update is pending? ;-) Erasing and reinstalling the packages has had no effect (with reboots in between).

Once glxinfo and fglrxinfo work, I expect the compiz-fusion-0.6.99.i386 (with updates added afterwards) will work as expected.

Anyone have any ideas? Any other outputs I need to post? ;-)

I don't want to have to wait until ATI releases an 2.6.23 compatible driver, since the Livna one has worked great in F7 with my setup.

sceotend
15th November 2007, 02:34 AM
Okay, while I don't know exactly what I did to fix the above problem, its fixed.

I had found some problems with video playback, in anything I tried, and several package reinstalls and reboots later, things are suddenly working. Except compiz-fusion.

After much reading, research, and fiddling, the common conclusion appears to be a problem in the 8.42.3 driver (even patched) with the 2.6.23 kernel. Oh well, been here before - waiting for ATI to release a fixed driver.

zietbukuel
21st November 2007, 03:19 AM
Can you please post yor new configuration? I'm having the same problem with ati-drivers. Thank you. :)

bino
14th December 2007, 11:00 AM
Would be nice indeed, same issue here.

phoxis
3rd January 2008, 12:56 PM
I am not having the provlem which you have shown in the glxinfo output everything is fine direct rendering is enabled
Celestia is running smoothly with opengl but ......... when i run wine like
winecfg or wine notepad or wine <anything> it shows the exact problem

X Error of failed request: GLXBadContext
Major opcode of failed request: 143 (GLX)
Minor opcode of failed request: 5 (X_GLXMakeCurrent)
Serial number of failed request: 18


and i have installed cedega
and it fails to find any opengl or direct3d devices.
my amdcccle (ati catalyst control centre) says i have for 128mb or video ram , where the 128mb is my shared memory (i.e the graphics apurture) i have also integrated 512MB ram
I have Biostar TA690G AM2 motherboard with ATI Radeon Xpress 1250 Graphics
AMD Athlon64 X2 4400+ Processor