Date: Tue, 23 May 1995 20:09:25 -0400 (EDT) From: Peter Dufault <dufault@hda.com> To: iain@nwpeople.demon.co.uk Cc: bugs@FreeBSD.org Subject: Re: console lockup Message-ID: <199505240009.UAA25314@hda.com> In-Reply-To: <639@nwpeople.demon.co.uk> from "Iain Baird" at May 23, 95 11:27:15 pm
next in thread | previous in thread | raw e-mail | index | archive | help
Iain Baird writes: > The following problem has occurred several times with 2.0-9504120-SNAP > on Gateway 2000 4DX2-66V: > > FreeBSD boots successfully and presents the login prompt. > Typing then has no effect, nor can I use Alt-Fn to switch virtual > consoles. I can login to the system using telnet from a remote host. > wall(1) has no effect on the console, nor has shutdown(8), although > the system seems to shutdown correctly. > > The problem seems usually to occur immediately after power-on. > > I'm not too distressed about this, trying again usually sorts it. > > Hopefully the information will be useful to you. Let me know if > you want more details. The "Gateway keyboard" bug is back! This went away when we switched over to syscons. I have this motherboard, but I almost never bring my system down and so I don't know about this anymore. When you log in remotely over the network try this: 1. Hit a key on the keyboard; 2. Echo something to the console. If this is the same as the old bug the keyboard will then come to life. There has never been an adequate solution to this problem because (I think) no one really understands it. The usual redress is to read the Van Gilluwe book and then sprinkle delays around in the keyboard probe code. Peter -- Peter Dufault Real Time Machine Control and Simulation HD Associates, Inc. Voice: 508 433 6936 dufault@hda.com Fax: 508 433 5267
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199505240009.UAA25314>