Once I run startx my keyboard flatout dies. It becomes completely unresponsive and even the Caps Lock, Num Lock, etc. lights stop working. It is a non-USB Type 6 keyboard. However, the mouse works fine. The screen is all black and I have the standard X cursor that moves around perfectly. Mouse buttons have no effect though. I'm not getting any kind of menus or anything. I have fluxbox installed, but now that I think of it I never did add that to xinit. My only option after running startx is to ssh into the box and reboot. I've tried killing X but it just makes the screen black without giving my tty's back, and the keyboard is still unresponsive (even to the three finger salute).
I just discovered this bug is linked to the X server's glx module. When I comment this module out, the server loads fine, and the keyboard works.
correction .... it's DRI ... I can load glx and GLcore both if I comment out DRI. It has something to do with the communication between DRI and glx
What hardware are you using? Can you attach your xorg.conf and Xorg.0.log? Does this happen if you use the DRI modules from (DRI) CVS?
reporter: ping. please provide more information about your setup so we can fix this.
Closing as WORKSFORME, due to the reporter not responding to request for information for > 2 months. Note that this type of issue has been a bug in the kernel's AGP driver in every case I've seen, and I've seen many. I'm tempted to NOTOURBUG bug 707 as well, but that would be more convincing if someone could find the issue with sis agp.
Created attachment 3352 [details] xorg.conf
I have exactly the same problem. I tried out the xorg dri modules but it did not help. I have attached my xorg.conf. If I enable the 'Load "glx"' line then startx results in a hard-locked machine with the radeon DRI kernel driver. If I use the xorg DRI drivers my screen is blank, but my keyboard responses and I can reboot the machine. Environment: - AMD64 - Radeon 9250 (rv280) - kernel 2.6.13
sven, you reopened this, but you didn't provide any information on your AGP setup (which as eric noted is often the problem), nor did you attach your X log. please provide more information and reopen this when you do.
I'm closing this bug due to the lack of activity. If the issue still persists, please reopen.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.