MLUG: Re: [MLUG] hard X crash that kills keyboard
Re: [MLUG] hard X crash that kills keyboard
Email address obfuscation in effect -- please click here to turn it off.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Well, the cheese I think is normal, isn't it?  i.e. no background so it displays that?  Try starting xterm along with it, see if that gets you something.  Does that X -config /myconfig cause the CPU and keyboard failure, where you can't kill X?  If not, it does sound like something with the default X startup is at issue.  Otherwise, I'd guess DRI or some other thing loading with X.
Jason

/--------------------------------------|---------------------------\
| Jason McIntosh                       | CELL: 573-424-7612        |
| Webmaster, thinker, programmer, etc. | WORK: 573-884-3865        |
| http://mcintosh.poetshome.com/blog/  |                           |
|------------------------------------------------------------------|
|"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 12:07 PM, George Robb wrote:

Any attempt to run X causes cheese.   e.g.  X -config /root/xorg.conf.new  Which should just bring up a grey screen with an X cursor.

Just another odd one to chalk up as "hmmm"

George

On May 1, 2007, at 10:36 AM, McIntosh Jason wrote:

Just another random thought... is X starting something perhaps that's taking the CPU time?  i.e. gconf/bonobo or similar?  You could try starting a super super simple system of X, i.e. run X with just an xterm.
Jason

/--------------------------------------|---------------------------\
| Jason McIntosh                       | CELL: 573-424-7612        |
| Webmaster, thinker, programmer, etc. | WORK: 573-884-3865        |
| http://mcintosh.poetshome.com/blog/  |                           |
|------------------------------------------------------------------|
|"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:29 AM, George Robb wrote:

xorg.0.log has a (WW) warnings about video bios (no current access to machine at the moment).  A ton of (II) about memory addresses and video modes and normal info.  No (EE) errors at all.

George




On May 1, 2007, at 10:21 AM, Scott Hussey wrote:

Does the xorg.log tell you anything interesting when you SSH in?

On 5/1/07, George Robb <EMAIL:PROTECTED> 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



-- 
Scott Hussey

_______________________________________________
members mailing list


_______________________________________________
members mailing list

_______________________________________________
members mailing list


_______________________________________________
members mailing list

_______________________________________________
members mailing list
EMAIL:PROTECTED
http://mlug.missouri.edu/mailman/listinfo/members