I tried various combinations of fixing this problem before I wrote a
patch.  The keyboard is somehow trashed and/or disabled when qemu
crashes in this manner.  The methods I tried to fix it were:
1. "reset" - never works
2. log in remotely and reboot - always works
3. log in remotely and try various combinations of "vga_reset" and
"fbset 800x600-56" - always works after I figured out the right order
to run the commands in.

In the end, I couldn't find any acceptable solutions without a patch,
since this is a laptop and I don't always have it connected to a
network so I can bail myself out.  I apologize for the duplicate
message too, I accidently sent the last email without finishing it.

On 5/3/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
I did, of course, try this first.  The keyboard doesn't work after
qemu crashes.  The ways I tried to fix this were:
1. "reset" (didn't work)
2. log in remotely and reboot (always works)
3. log in remotely and try "vga_reset", and "fbset 800x600-56" (the normal
mode

On 5/2/07, Rob Landley <[EMAIL PROTECTED]> wrote:
> On Tuesday 24 April 2007 2:23 am, Kitambi Leo wrote:
> > I've been using qemu using the Linux framebuffer console, on a machine
> > that's a bit too slow to support X.  There have been more than a few
> snags,
> > but perhaps the most irritating one was that if qemu crashed (and
received
> a
> > SIGSEGV), it would leave the console in an unusable state.  This would
> > require me to log into the machine via ssh and reboot it remotely.
>
> Type "reset" and hit enter when this happens.
>
> Rob
>



Reply via email to