You can also try the binary drivers to see if that fixes things (I'm using the latest ATI drivers, and they've been really fast and stable). Additionally, if you use Xinerama, DRI won't work and should automatically be disabled. Also, keep in mind if you've got DRI enabled in the kernel, well, I've had a lot of problems with that and the framebuffer support in the kernel doing similar things. Jason /--------------------------------------|---------------------------\ | Jason McIntosh | CELL: 573-424-7612 | | Webmaster, thinker, programmer, etc. | WORK: 573-884-3865 | |------------------------------------------------------------------| |"How should I know if it works? That's what beta testers are | |for. I only coded it." | |(Attributed to Linus Torvalds, somewhere in a posting) | \--------------------------------------|---------------------------/
On May 1, 2007, at 10:26 AM, George Robb wrote: I'm using the generic ati driver none of the fancy binary drivers. Good call on the DRI and GLX disable. I've not attempted that yet.
George
On May 1, 2007, at 10:20 AM, McIntosh Jason wrote:
I'd check to see which driver you're using, whether DRI is enabled, etc. I've seen X with the kernel hooks through DRI kill a machine before ;) It's the same problem with windows to get accelerated graphics. SO, you can try disabling a lot of the low level modules, or instead of using say the ati/nvidia drivers, use the open source drivers. Just a few thoughts ;) Jason
/--------------------------------------|---------------------------\ | Jason McIntosh | CELL: 573-424-7612 | | Webmaster, thinker, programmer, etc. | WORK: 573-884-3865 | |------------------------------------------------------------------| |"How should I know if it works? That's what beta testers are | |for. I only coded it." | |(Attributed to Linus Torvalds, somewhere in a posting) | \--------------------------------------|---------------------------/
On May 1, 2007, at 10:17 AM, George Robb wrote:
It helps for a sanity check ;) It just amazes me that the crash is knocking out the keyboard.
Thanks for the input!
George
On May 1, 2007, at 10:12 AM, Dave McBride wrote:
I had problems with essentially the same symptoms, but in older versions of X (pre-FC era). Different versions, different distros, same problem. It seemed to manifest itself in the first release of a version upgrade, but I never tried to prove it empirically.
I also never found out why it happened. I was able to work around the problem by swearing a lot, then upgrading, downgrading, or just switching distros. In each case, I wiped the OS and started fresh. Mind you, this was on my own, home computer where my only real expenses were aggravation and wasted time.
Sorry it isn't much help, Dave
George Robb wrote: Hi MLUG- Has anyone had experience with FC4 (Ya, ya.. I know old school...) that crashes X so hard that the keyboard no longer responds to status LEDs (num lock, caps lock, etc...) or even ctrl-alt-del. Ctrl-Shift-Alt-Backspace won't even kill X. The monitor goes out of sync (no signal) and the keyboard becomes a paperweight. A work around was to edit the inittab to keep things in runlevel 3 but, for this particular user a GUI is a must. I nuked xorg.conf and had the system build a new one with X -configure. even X -config xorg.conf.new crashes the system. If I ssh in the system reveals that X is at 99.7% cpu and has no desire to chill out. A kill -15 bounces off and a kill -9 brings things back to normal of course with no X. Anyone else seen this before? Thanks, George _______________________________________________ members mailing list
_______________________________________________ members mailing list
_______________________________________________ members mailing list
_______________________________________________ members mailing list
_______________________________________________ members mailing list
|
Home | FAQ | Server | Presentations | Mailing Lists/Archives | Member Tools | Links | Sponsors | Contact