Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
I have run into an interesting problem. An X application caused my X server to crash. This left the video totally frozen. I was able to partially get out of this situation by logging into my machine from another through ssh. I killed the offending process but things did not return to normal. The video was still frozen on my machine. So I tried starting X from the remote terminal. X came up and ran normally.
This is where I am stuck. Now when I try to switch back to a virtual console it does not switch to a text mode. All that changes is a black area appears in the upper left corner of the screen. I have discovered that that black area is showing what is on the virtual console. It does not show text. I believe it is the graphical representation of the virtual terminals text buffer in memory.
I have blindly tried logging in on a virtual terminal and entering 'reset', and 'echo [ctrl+v][esc]c'. These have no effect. I am sure a reboot would fix this but I am interested in a more elegant solution. Mainly because I am trying to see how long I can keep the system running without rebooting it.
For now I will try to make due with a "graphics mode" only environment. Though, I don't know how long I can hold out. If anyone has any tricks, please let me know.
Im frequently suffering from the same problem.. I fix it the same way you do, and sometimes starting a new X and shutting it down restores the VT:s back in order.. What kinda video hardware and X versions are you running? It would be nice to be able to narrow this problem down and some day find a cure.. d:
yeah, I was a tad suprised too to find out it actually has a driver.. it claims to be mainly for the onboard soundcard and ethernet, but since I dont use the sound and the ethernet works fine out of the box, I havnt installed the driver..
Could be just that its a tad buggy.. Getting weird errors from it upon boot.. *sigh*
Guess itll never be solved..