From: James S. <jsi...@ac...> - 2000-03-11 03:00:20
|
> >If the X driver or some svgalib application dropped out without > >resetting the fb mode correctly, then the local ttys became "lost" and > >unviewable. (Any way out of this?) svgalib is particular nasty to > >use with the console fb. Never ever use libsvga with fbdev. Both hit the hardware at the same time and for low end hardware this locks the card or even damages it. As for the X problem I have a patch that saves the console mode before opening /dev/fb. If X dies then /dev/fb is closed which then restores the video mode back to normal. Also fbdev drivers should be check all modes before actually setting them so you can't set insane modes. > I've heard that the sysRq key is supposed to help. compile in "magic sysRq > key" support in the kernel, then press Alt-SysRq-{some letter which i > forgot}. Alt-SysRq-K > i never got it working, cause i haven't had the problem and the > sysRq key at the same time, but *tell me if you get it working* I would very > much like to have the procedure for this figured out. If you still set a insane mode often the fbdev drivers are not written well enough to check the mode. This leaves the console in a undefine state. Even the magic keys can't save you. > >I have been particular vulnerable to this > >since I've been using banshee and voodoo3 cards for quite a while and > >their drivers are vastly improving and still not 100% stable. I've > >also been meaning to have a good look at ggi, but too much to do and > >so little time... GGI take advantage of video hardware in any environment. Its preety neat. I use Mesa-GGI so I can run OpenGL on the console with fbdev of course. "Look it's a text editor, no it's a OS, no it's Emacs" James Simmons ____/| fbdev/gfx developer \ o.O| http://www.linux-fbdev.org =(_)= http://linuxgfx.sourceforge.net U |