From owner-freebsd-bugs Mon Feb 10 02:45:09 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id CAA24740 for bugs-outgoing; Mon, 10 Feb 1997 02:45:09 -0800 (PST) Received: from bugs.us.dell.com (bugs.us.dell.com [143.166.169.147]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id CAA24735 for ; Mon, 10 Feb 1997 02:45:04 -0800 (PST) Received: from ant.us.dell.com (ant.us.dell.com [198.64.66.34]) by bugs.us.dell.com (8.6.12/8.6.12) with SMTP id EAA08296; Mon, 10 Feb 1997 04:44:28 -0600 Message-Id: <3.0.1.32.19970210044426.006a265c@bugs.us.dell.com> X-Sender: tony@bugs.us.dell.com X-Mailer: Windows Eudora Light Version 3.0.1 beta 12 (32) Date: Mon, 10 Feb 1997 04:44:26 -0600 To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) From: Tony Overfield Subject: Re: Stuck! 2.2 Gamma won't go. Cc: bugs@freebsd.org In-Reply-To: References: <3.0.1.32.19970209182035.006a34a8@bugs.us.dell.com> <3.0.1.32.19970209182035.006a34a8@bugs.us.dell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >NB: you can manually start that program as XF86Setup. Since the >low-level routines work (the LEDs are driven by the Xserver, not by >the kernel driver), you could at least finally kill the Xserver with >Ctrl-Alt-BkSpc if all else fails. This does work. Apparently, I managed to kill it off some other way before, because when I got out of the X server, the keyboard was still dead. I had my text-mode console screen back, but no keys would work, and Alt-F1, etc. would just beep. (time passes ...) Ok, now I know what I did. While X was running, I got back to the text console and pressed Ctrl-C. That seems to be a really bad thing to do. I won't do that any more. >Can you toggle the consoles with Ctrl-Alt-F1 (for example)? Yes. Thanks. So that's what I "one million monkeyed" into my keyboard to get it to switch before. I had been pushing Alt-F1 with no luck. Only *now* do I remember reading about that. ;-) >You really can't move around with the TAB key? Sometimes I can. Hmm, I wonder .... (more time passes ...) Bad case: 1. Start XF86Setup. 2. At the XFree86 "Oval" screen, move the PS/2 mouse. It will move erratically. 3. Stop moving the mouse. 4. Press TAB repeatedly. It works fine. 5. TAB to "Mouse" button and press space bar (or enter). 6. Press space bar (or enter) again to "Dismiss" help text. 7. At this point TAB, Alt-H, '?', etc. will *not* work. Ctrl-Alt-F1, and Ctrl-Alt-Backspace *will* work. The mouse will behave erratically if you move it. Good case (well, better): 1. Start XF86Setup. 2. At the XFree86 "Oval" screen, do *not* move the PS/2 mouse. 3. Press TAB repeatedly. It works fine. 4. TAB to "Mouse" button and press space bar (or enter). 5. Press space bar (or enter) again to "Dismiss" help text. 6. At this point TAB, Alt-H, '?', 'p', etc. *will* work. The mouse will behave erratically if you move it. Once the mouse has been moved, the keyboard will die after you, for example, call up help and dismiss it, but apparently not otherwise. I think this contains some usable clues. Well, I'm past that stumbling block. I now know how to avoid this, and we'll probably all forget about it until someone else finds this one. Thanks, Joerg. With your suggestions I was able to repeat the experiments much more quickly. - Tony