Re: X kills console

Wakko Warner (wakko@animx.eu.org)
Fri, 22 Oct 1999 17:09:46 -0400


> Run savetextmode (an svgalib utility) before starting X. After killing X,
> run textmode as root from a virtual console (I find chvt handy to get back
> to a virual console).

I assume it saves to a file, right? I didn't know about this in svgalib.
If it saves to a file, I assume I could copy the saved from another machine
and load it on the one that's not working. Same video hw and mobo. I
really don't care if it crashes trying this (just prefer it not, but either
way I'd have to reboot)

> > When I have to kill -9 X, is there anyway (w/o rebooting, the
> > box has been
> > up for 73 days on 2.2.10 SMP) to get the console back the way
> > it was after
> > the machine boots? I've upgraded the kernel to 2.2.13 but
> > don't see a need
> > to reboot (the console isn't that big of a deal, but would
> > like to fix it).
> >
> > I'm sure someone else has been in this situation where the console is
> > completely messed up and would like to have it back w/o booting.
> >
> > --
> > Lab tests show that use of micro$oft causes cancer in lab animals
> >
> > -
> > To unsubscribe from this list: send the line "unsubscribe
> > linux-kernel" in
> > the body of a message to majordomo@vger.rutgers.edu
> > Please read the FAQ at http://www.tux.org/lkml/
> >

-- 
 Lab tests show that use of micro$oft causes cancer in lab animals

- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/