From owner-freebsd-stable Sun Feb 4 2:38:46 2001 Delivered-To: freebsd-stable@freebsd.org Received: from jason.argos.org (a1-3b044.neo.rr.com [24.93.181.44]) by hub.freebsd.org (Postfix) with ESMTP id 974F137B401 for ; Sun, 4 Feb 2001 02:38:29 -0800 (PST) Received: from localhost (mike@localhost) by jason.argos.org (8.10.1/8.10.1) with ESMTP id f14ARok24998; Sun, 4 Feb 2001 05:27:50 -0500 Date: Sun, 4 Feb 2001 05:27:50 -0500 (EST) From: Mike Nowlin To: Jesper Skriver Cc: Robert , freebsd-stable@FreeBSD.ORG Subject: Re: uh oh - after 4 -> 4.2 cvsup, no keyboard. any ideas? In-Reply-To: <20010204112503.E71706@skriver.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > anyway, now - although the system boots fine, I only have keyboard up to > > where I can interrupt the boot. At that state - pre-boot I suppose - I have > > keyboard. If I then do the full boot, I have no keyboard. A mouse sure? but > > a dead keyboard. Now this is pretty useless :-) > > > > So I wondered if anyone had any good ideas how I can get in and get my > > keyboard back - and maybe even what I should be fixing anyway? > > Get in via telnet/ssh given they are enabled. Get creative! Log in with cut & paste via your mouse and the boot message output on the screen! :) Have you tried a different keyboard? I've run across a few that get confused with various OS's at times - they work just fine, but go brain-dead during various init sequences... Or maybe pulling the plug on the kbd and putting it back in after boot - you sometimes have to do this a few times for the kbd to init correctly - hit Caps Lock a few times until the LED starts blinking. mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message