Seiichi Ariga wrote: > When my X stopped, I did rlogin from other computer > and killed almost everything except processes like > init, those k* things and internet related damons. > But I couldn't erase my stopped screen or go back > to terminal. So I had to reboot my system.
Yep. > Now, I have two questions, (1) how can I get back to > normal terminal when X server stops and screen doesn't > update even after X was killed? (2) How can I avoid > this mesa error? Can't help you with step 1. Step 2, this isn't mesa's error. I'm pretty sure it's nVidia's glx (and also possiblly vendor specific...my tnt2ultra gave me trouble until I disabled AGP Bus Turbo Mode on my Ali board; see the docs that come with Nvidia's latest GLX driver) To avoid it, I highly recommend installing X4.0 with the latest drivers from nvidia. (sounds like you're using 3.x series..i could be wrong though?) They fixed some of those kind of annoying bugs. Fast ConfigureNotify events don't freeze it up anymore, so resizing a GL context in E with the opaque method is safe (this may have been my turbo mode setting though). Also, if...when the nvidia drivers do crash X, it drops you to the console correctly instead locking the framebuffer. An alternative would be to use GDM. You'd still lose the consoles, but at least a new login would appear so that you can continue in X. Or a last alternative would be to startx through the rlogin. The framebuffer will still lock after crash, but now just startx again from the rlogin to get X back. HTH, -- ( Mike Brownlow | http://wsmake.org/~mike/ | http://wsmake.org/ ) ( "A scorner seeketh wisdom, and findeth it not: but knowledge ) ( is easy unto him that understandeth." Proverbs 14:6 )
