[opensuse] restoring X setup after doom3 locks up
On my 10.3 system, doom3 will occasionally lock up, meaning I have to kill it to get my system back. I switch to a virtual console and kill the doom3 process, but when I return to KDE, my previous resolution etc. hast not been not restored and I have no mouse. I presume this is due to doom3 being killed and therefore not exiting and properly. How can I manually restore whatever the X settings were before I started doom3? thanks Per -- Per Jessen, Zürich (-3.0°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tuesday 05 January 2010 17:37:28 Per Jessen wrote:
On my 10.3 system, doom3 will occasionally lock up, meaning I have to kill it to get my system back. I switch to a virtual console and kill the doom3 process, but when I return to KDE, my previous resolution etc. hast not been not restored and I have no mouse. I presume this is due to doom3 being killed and therefore not exiting and properly. How can I manually restore whatever the X settings were before I started doom3?
xrandr --auto is the simplest way I can think of. Will -- Will Stephenson, openSUSE Team SUSE LINUX Products GmbH - Nürnberg - AG Nürnberg - HRB 16746 - GF: Markus Rex -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Will Stephenson wrote:
On Tuesday 05 January 2010 17:37:28 Per Jessen wrote:
On my 10.3 system, doom3 will occasionally lock up, meaning I have to kill it to get my system back. I switch to a virtual console and kill the doom3 process, but when I return to KDE, my previous resolution etc. hast not been not restored and I have no mouse. I presume this is due to doom3 being killed and therefore not exiting and properly. How can I manually restore whatever the X settings were before I started doom3?
xrandr --auto is the simplest way I can think of.
Will
Will that keep my X session running? I.e. with whatever open windows etc I had? That's the important bit. I guess I'll try xrandr next time. /Per -- Per Jessen, Zürich (-2.4°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wednesday 06 January 2010 08:44:13 Per Jessen wrote:
Will Stephenson wrote:
On Tuesday 05 January 2010 17:37:28 Per Jessen wrote:
On my 10.3 system, doom3 will occasionally lock up, meaning I have to kill it to get my system back. I switch to a virtual console and kill the doom3 process, but when I return to KDE, my previous resolution etc. hast not been not restored and I have no mouse. I presume this is due to doom3 being killed and therefore not exiting and properly. How can I manually restore whatever the X settings were before I started doom3?
xrandr --auto is the simplest way I can think of.
Will
Will that keep my X session running? I.e. with whatever open windows etc I had? That's the important bit. I guess I'll try xrandr next time.
Yes, it just tells X to reset its resolution on the default output back to defaults. Will -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Per Jessen wrote:
On my 10.3 system, doom3 will occasionally lock up, meaning I have to kill it to get my system back. I switch to a virtual console and kill the doom3 process, but when I return to KDE, my previous resolution etc. hast not been not restored and I have no mouse. I presume this is due to doom3 being killed and therefore not exiting and properly. How can I manually restore whatever the X settings were before I started doom3?
thanks Per
Per, Just ctrl+alt+f1 and 'ps axf' kill what you can identify as doom related and then ctrl+alt+f7. If no joy, then ctrl+alt+f1 and 'rcxdm stop' look for any hung X processes with 'ps ax | grep X' and kill any remaining. Then rcxdm start and it will throw you back to the greeter where you can start a new session. (ATI fglrx driver by chance?) Which graphics kernel module are you using. Some behave better than others.... -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
David C. Rankin wrote:
Per Jessen wrote:
On my 10.3 system, doom3 will occasionally lock up, meaning I have to kill it to get my system back. I switch to a virtual console and kill the doom3 process, but when I return to KDE, my previous resolution etc. hast not been not restored and I have no mouse. I presume this is due to doom3 being killed and therefore not exiting and properly. How can I manually restore whatever the X settings were before I started doom3?
Per,
Just ctrl+alt+f1 and 'ps axf' kill what you can identify as doom related and then ctrl+alt+f7.
Hi David exactly what I do now, but it doesn't restore the X config.
If no joy, then ctrl+alt+f1 and 'rcxdm stop' look for any hung X processes with 'ps ax | grep X' and kill any remaining. Then rcxdm start and it will throw you back to the greeter where you can start a new session. (ATI fglrx driver by chance?)
Yep, but I don't want a new session, that's the main issue. I want my old session back with all the open windows etc. The graphics card is an ATI Radeon X1650. /Per -- Per Jessen, Zürich (-1.5°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Per Jessen wrote:
If no joy, then ctrl+alt+f1 and 'rcxdm stop' look for any hung X processes with 'ps ax | grep X' and kill any remaining. Then rcxdm start and it will throw you back to the greeter where you can start a new session. (ATI fglrx driver by chance?)
Yep, but I don't want a new session, that's the main issue. I want my old session back with all the open windows etc.
The graphics card is an ATI Radeon X1650.
/Per
Umm, Dunno how to break this to you, but more than likely you are not going to get your old X session back -- "ever". Why? The fglrx driver is notorious for not completely unloading, with some hardware (9600 - 9800 cards) nothing short of a 'power off restart' will unload the remaining driver fragments. My GUESS is that when doom flips the resolution from your normal res to the framebuffer res it uses, with pieces of the driver for your native res as well as the framebuffer loaded. If doom crashes and does NOT go through its process of closing the framebuffer and restoring your normal res --> your hosed for that session. With the 1650, you should be fine starting a new session without having to do a power-off shutdown. ( I believe X1200+ no longer requires the power-off shutdown to clear the driver fragments). The only other tidbit I have is to make sure you are using the fglrx 8.532 driver (from the 8-9 driver package). It seems to be the best from a performance/stability standpoint. From 8-10 through 9-3 the fglrx driver included support for the 2400+ series cards that really screwed performance for the 1850 and earlier cards. If you are happy with your current driver - keep it. If you want to try the 8-9 (8.532) driver, the package is still available on the ati site under the 'previous drivers' page. -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
David C. Rankin wrote:
Per Jessen wrote:
If no joy, then ctrl+alt+f1 and 'rcxdm stop' look for any hung X processes with 'ps ax | grep X' and kill any remaining. Then rcxdm start and it will throw you back to the greeter where you can start a new session. (ATI fglrx driver by chance?)
Yep, but I don't want a new session, that's the main issue. I want my old session back with all the open windows etc.
The graphics card is an ATI Radeon X1650.
Dunno how to break this to you, but more than likely you are not going to get your old X session back -- "ever".
Well, 9 times of out 10 it works fine. I.e. doom3 exits normal, and my regular X session is back. I'm pretty certain it's a some rare race-condition somewhere.
Why? The fglrx driver is notorious for not completely unloading, with some hardware (9600 - 9800 cards) nothing short of a 'power off restart' will unload the remaining driver fragments.
Hmm, with the most recent driver, I have had more situations where I've had to to a cold start - with the previous one, I could just restart X.
My GUESS is that when doom flips the resolution from your normal res to the framebuffer res it uses, with pieces of the driver for your native res as well as the framebuffer loaded.
Yeah, something like that, I'm sure.
With the 1650, you should be fine starting a new session without having to do a power-off shutdown. ( I believe X1200+ no longer requires the power-off shutdown to clear the driver fragments).
I have not yet had to power off, but it's becoming increasingly annoying having to restart everything after such a crash. knode doesn't take it too well either.
The only other tidbit I have is to make sure you are using the fglrx 8.532 driver (from the 8-9 driver package). It seems to be the best from a performance/stability standpoint. From 8-10 through 9-3 the fglrx driver included support for the 2400+ series cards that really screwed performance for the 1850 and earlier cards. If you are happy with your current driver - keep it.
I think I'm on 8.593 right now. I had the same problem with previous drivers too though. Whatever I've got installed now will usually leave little black areas on my screen when I exit doom3, but I barely notice that. /Per -- Per Jessen, Zürich (-2.5°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 06/01/10 21:12, Per Jessen wrote:
Well, 9 times of out 10 it works fine. I.e. doom3 exits normal, and my regular X session is back. I'm pretty certain it's a some rare race-condition somewhere.
I think I'm on 8.593 right now. I had the same problem with previous drivers too though. Whatever I've got installed now will usually leave little black areas on my screen when I exit doom3, but I barely notice that.
/Per
Why not start doom3 in it's own X server so that it doesn't interfere if it crashes? Something like xinit doom3 $* -- :1 Haven't tried it with recent Xorg versions but that was what I used to do with my problematic games. You should be able to Ctrl-Alt-F7 back to the desktop if something goes wrong. Regards, Tejas -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (4)
-
David C. Rankin -
Per Jessen -
Tejas Guruswamy -
Will Stephenson