From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1HjjhB-0002AX-JM for qemu-devel@nongnu.org; Thu, 03 May 2007 18:22:41 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1HjjhA-00028B-0O for qemu-devel@nongnu.org; Thu, 03 May 2007 18:22:41 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Hjjh9-00027e-Qx for qemu-devel@nongnu.org; Thu, 03 May 2007 18:22:39 -0400 Received: from nz-out-0506.google.com ([64.233.162.230]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Hjjaa-0002F0-6C for qemu-devel@nongnu.org; Thu, 03 May 2007 18:15:52 -0400 Received: by nz-out-0506.google.com with SMTP id i11so1761075nzi for ; Thu, 03 May 2007 15:15:51 -0700 (PDT) Message-ID: Date: Thu, 3 May 2007 18:15:51 -0400 From: kitambi@gmail.com Subject: Re: [Qemu-devel] Patch for SDL framebuffer console problem In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <200705021613.07542.rob@landley.net> Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Rob Landley Cc: qemu-devel@nongnu.org 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, kitambi@gmail.com 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 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 > > >