Re: Framebuffer console not restored correctly after X server abort
On Mon, 18 Apr 2005 22:54:43 +0200 Francois Lucas <[EMAIL PROTECTED]> wrote: > The config is an quad Ultra 80 running sid with debian 2.6 SMP kernel > and a creator3D. Unfortunately, if the sunffb closedown function isn't called the color key in the framebuffer pixels is not restored to what the kernel was using resulting in the behavior you see. This should only really happen if the Xserver takes an unrecoverrable fault from which it cannot call the sunffb shutdown routines. You'll need to debug the Xserver sources to try and fix this. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Framebuffer console not restored correctly after X server abort
Hi, all! When I tried to get DRI working, I made a few (lots in fact :-) ) tries involving starting and stopping gdm. I found that when the xserver aborts violently (complaining about no screen founds and things like that), frequently the framebuffered console is not restored correctly (the screen can become written black on green - ugly - or darkdarkdark blue on black - unreadable-). Is there a way to workaround that whitout rebooting the machine (POST is slow ;-) ) The config is an quad Ultra 80 running sid with debian 2.6 SMP kernel and a creator3D. NB: 1/ Before switching to grey X screen when launching gdm, the console becomes "normal" again (white on black) but when I quit, it goes back bad. 2/ The problem doesn't seem to occur on 2.4 debian kernel. -- F.
