help me diagnose why the X crushes...

itz2000 · 09-30-2006, 07:26 PM

What shall I do to diagnose what cause the crash?

thanks

lordtweety · 09-30-2006, 07:29 PM

X Crush? or perhaps crash?

chadl · 09-30-2006, 08:38 PM

I am assuming mean crash, as I have never seen the term crush used in that way before.

First, we will need more information then that. Is there some type of error message? Does it freeze?

If you do not see an error message, your best bet is to stop X, switch to a terminal, by pressing ctrl+alt+F1, and then run the command

Code:

startx >Errorlog.log 2>&1

and then after it crashes, post what is in Errorlog.log.

haertig · 09-30-2006, 10:36 PM

Quote:

Originally Posted by itz2000

What shall I do to diagnose what cause the crush?

If you're using Xorg, check it's logfile. That would be /var/log/Xorg.0.log on my system (a typical location). If you're using XFree, it's logfile would be /var/log/XFree86.0.log probably.

Inside those logfiles, looking for lines that begin with "(EE)" would be a good start. Those would be error lines.

Also check out your syslog for errors. On my system, this is /var/log/syslog, but the location can vary with different distros.

Try running "dmesg" as well (you'll need to page it's output with "pg" or "less" or "more" or whatever pager you prefer).

haertig · 09-30-2006, 10:42 PM

If the cause of your crash is not evident in the logfiles I mentioned above, the first shot-in-the-dark step I'd take would be to configure X to use the generic vesa video driver.

The will be a "Device" section in your X configuration file for your video card. Comment out the current "Driver" line there if it's not vesa, and add "Driver vesa" in it's place. Your X configuration file should be either /etc/X11/xorg.conf or /etc/X11/XF86Config-4 depending on if you're running Xorg or XFree.

itz2000 · 10-01-2006, 04:29 AM

it seems to happen when I try to switch languages, randomly...

dmesg shows nothing, so does /var/log/Xorg

blahhhh

Code:

[root@localhost log]# cat Xorg.0.log | grep EE
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(II) Loading extension MIT-SCREEN-SAVER
(EE) RADEON(0): [dri] RADEONDRIScreenInit failed because of a version mismatch.
(EE) RADEON(0): Setting pPriv->adjustment to 0
(EE) RADEON(0): Setting pPriv->adjustment to 0
(EE) RADEON(0): Setting pPriv->adjustment to 0
(EE) RADEON(0): Setting pPriv->adjustment to 0
[root@localhost log]# cat Xorg.0.log.old | grep EE
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(II) Loading extension MIT-SCREEN-SAVER
(EE) RADEON(0): [dri] RADEONDRIScreenInit failed because of a version mismatch.
(EE) RADEON(0): Setting pPriv->adjustment to 0
[root@localhost log]#

and no, it has nothing related to the radeon, cause if it did, it would have done this crash before...

chadl · 10-01-2006, 08:59 AM

Quote:

Originally Posted by itz2000

it seems to happen when I try to switch languages, randomly...

dmesg shows nothing, so does /var/log/Xorg

blahhhh

Code:

[root@localhost log]# cat Xorg.0.log | grep EE
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(II) Loading extension MIT-SCREEN-SAVER
(EE) RADEON(0): [dri] RADEONDRIScreenInit failed because of a version mismatch.
(EE) RADEON(0): Setting pPriv->adjustment to 0
(EE) RADEON(0): Setting pPriv->adjustment to 0
(EE) RADEON(0): Setting pPriv->adjustment to 0
(EE) RADEON(0): Setting pPriv->adjustment to 0
[root@localhost log]# cat Xorg.0.log.old | grep EE
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(II) Loading extension MIT-SCREEN-SAVER
(EE) RADEON(0): [dri] RADEONDRIScreenInit failed because of a version mismatch.
(EE) RADEON(0): Setting pPriv->adjustment to 0
[root@localhost log]#

and no, it has nothing related to the radeon, cause if it did, it would have done this crash before...

The error "RADEONDRIScreenInit failed because of a version mismatch." seems to indicate that some component was updated, while some component that it needs to work with was not.

Is there some language module that the ATI drivers are using that it would care about the version numbers on? That is the only thing that I can think of that would link changing the language and a version error with the ATI drivers.

I use an NVidia card, so I do not know much about the workings of ATI drivers, however.

haertig · 10-01-2006, 11:46 AM

Quote:

and no, it has nothing related to the radeon

I don't see how you can say this, given the log data you posted above.

The next step in my debugging would be to try that vesa driver. That is a diagnostic step to try and isolate the problem. If everything works with vesa, then you have an even bigger smoking gun pointing at your ATI video setup than before.

itz2000 · 10-02-2006, 01:00 PM

I figured out what cause is to crash (the sequence CTRL+ALT+BACKSPACE) but I don't know why!

I've looked everywhere but there's no such a shortcut configured to crash X.

:S

haertig · 10-02-2006, 01:24 PM

Quote:

Originally Posted by itz2000

I've looked everywhere but there's no such a shortcut configured to crash X.

I certainly hope you're joking with that statement. That is the standard shortcut to kill X! It's known as the "Ultimate Escape from X (tm)".