X Window Manager Crashes

symatic · 03-02-2008, 11:24 PM

Quote:

symatic, I hope by saying that the VertRefrsh setting is the "same thing" you merely mean that you must provide the correct values and not that they are equivalent to the HorizSync values, because they shouldn't be the same.

I could have been more specific in my detail.

HorizSync 24-82 <--place your monitors values here
VertRefrsh 55-77 <--place you monitors values here

You will also need this for DRI/3D rendering to work:

Code:

Section "DRI"
	Mode         0666
EndSection

Also had this line to your fstab:

Code:

tmpfs	/dev/shm    tmpfs  defaults    0   0

then

Code:

mount tmpfs

You will have to restart X for this to take affect. Once you are back in X fire up a console and type

Code:

fglrxinfo

Should say something like OpenGL: ATI technologies...

I'm not sure if this will fix your problems, but this will allow you to set up the ati driver a bit better. Possible the opengl scrrensavers were locking up your system. But we'll see when you post your logs.

dlinux · 03-03-2008, 02:23 AM

Im having a similar problem(with Intel integrated graphics card).Whenever my screen saver starts,the screen goes black and back again a couple of times and then i have to reboot.What's strange is that it didn't happen with KDE, now im using Xfce and it crashes in both KDE and Xfce!

Im using the 2.6.24.3 linux kernel.

ps: This i some of my Xorg.0.log:

Quote:

(II) intel(0): Not using default mode "640x350" (vrefresh out of range)
(II) intel(0): Not using default mode "640x400" (vrefresh out of range)
(II) intel(0): Not using default mode "720x400" (vrefresh out of range)
(II) intel(0): Not using default mode "640x480" (vrefresh out of range)
(II) intel(0): Not using default mode "640x480" (vrefresh out of range)
(II) intel(0): Not using default mode "640x480" (vrefresh out of range)
(II) intel(0): Not using default mode "800x600" (vrefresh out of range)
(II) intel(0): Not using default mode "800x600" (vrefresh out of range)
(II) intel(0): Not using default mode "800x600" (vrefresh out of range)
(II) intel(0): Not using default mode "800x600" (vrefresh out of range)
(II) intel(0): Not using default mode "1024x768" (vrefresh out of range)
(II) intel(0): Not using default mode "1024x768" (vrefresh out of range)
(II) intel(0): Not using default mode "1024x768" (vrefresh out of range)
(II) intel(0): Not using default mode "1152x864" (vrefresh out of range)
(II) intel(0): Not using default mode "1280x960" (hsync out of range)
(II) intel(0): Not using default mode "1280x960" (vrefresh out of range)
(II) intel(0): Not using default mode "1280x1024" (hsync out of range)
(II) intel(0): Not using default mode "1280x1024" (vrefresh out of range)
(II) intel(0): Not using default mode "1280x1024" (vrefresh out of range)
(II) intel(0): Not using default mode "1600x1200" (hsync out of range)
(II) intel(0): Not using default mode "1600x1200" (vrefresh out of range)
(II) intel(0): Not using default mode "1600x1200" (vrefresh out of range)
(II) intel(0): Not using default mode "1600x1200" (vrefresh out of range)
(II) intel(0): Not using default mode "1600x1200" (vrefresh out of range)
(II) intel(0): Not using default mode "1792x1344" (hsync out of range)
(II) intel(0): Not using default mode "1792x1344" (vrefresh out of range)
(II) intel(0): Not using default mode "1856x1392" (hsync out of range)
(II) intel(0): Not using default mode "1856x1392" (vrefresh out of range)
(II) intel(0): Not using default mode "1920x1440" (hsync out of range)
(II) intel(0): Not using default mode "1920x1440" (vrefresh out of range)
(II) intel(0): Not using default mode "832x624" (vrefresh out of range)
(II) intel(0): Not using default mode "1152x768" (vrefresh out of range)
(II) intel(0): Not using default mode "1400x1050" (hsync out of range)
(II) intel(0): Not using default mode "1400x1050" (vrefresh out of range)
(II) intel(0): Not using default mode "1600x1024" (hsync out of range)
(II) intel(0): Not using default mode "1920x1440" (vrefresh out of range)
(II) intel(0): Not using default mode "2048x1536" (hsync out of range)
(II) intel(0): Not using default mode "2048x1536" (vrefresh out of range)
(II) intel(0): Not using default mode "2048x1536" (vrefresh out of range)

jnedobity · 03-03-2008, 11:48 AM

Quote:

Originally Posted by dlinux

Im having a similar problem(with Intel integrated graphics card).Whenever my screen saver starts,the screen goes black and back again a couple of times and then i have to reboot.What's strange is that it didn't happen with KDE, now im using Xfce and it crashes in both KDE and Xfce!

Im using the 2.6.24.3 linux kernel.

ps: This i some of my Xorg.0.log:

Not to sound like an ass but you should pm the first guy that responded to my first post. I think he may know more about the intel chipsets.

okay done, lets continue.

Okay since I can not post the log files

I have archived them (for easy downloading) and have uploaded them to one of my websites. Please note that they will only be there for a short time before I remove them, Approx a Week at the most.

A link to where you can get them -> http://jonweb.vlexo.net/Public/Xorg_Logs.zip approx 26k or so

orasis · 03-03-2008, 08:42 PM

I have the same thing happening over here, well close. What happens here is that if I start 'gmplayer' or 'kmplayer' the Xserver crashes right back to console. - I disabled frame buffer (thinking that perhaps fb could be causinh some problems since... it has been known to on my machine on other distro's) but to no avail, same issue - crash crash crash :|

I'm also using an ATI/Radeon card.

Right now I am compiling the Gxine/Xine program and we'll see what happens.. if it continues to crash I think something is up with Slack12 and certain radeons/ati chips. - Since nothing like this happened with Slack 11.