From owner-freebsd-current Thu Jan 27 21:27:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id BA8E715C4B for ; Thu, 27 Jan 2000 21:27:46 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id VAA80024; Thu, 27 Jan 2000 21:27:16 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <200001280527.VAA80024@gndrsh.dnsmgr.net> Subject: Re: Problems installing FreeBSD 4.0 20000125-CURRENT In-Reply-To: <200001272143.QAA20638@khavrinen.lcs.mit.edu> from Garrett Wollman at "Jan 27, 2000 04:43:46 pm" To: wollman@khavrinen.lcs.mit.edu (Garrett Wollman) Date: Thu, 27 Jan 2000 21:27:16 -0800 (PST) Cc: jkh@zippy.cdrom.com (Jordan K. Hubbard), fenner@research.att.com (Bill Fenner), current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > < said: > > >> 3. On the first reboot after installing, the keyboard was in a funny > >> state. > > > Urk, can't reproduce it. I need a reproducible sequence of operations > > before we'll have any hope of tackling this one. > > >> Control-alt-del definitely didn't work, so I had to power off and > >> reboot. This hasn't repeated itself. > > > Same here. > > I have on a number of occasions had my laptop boot with a > non-functional keyboard. Sometimes the keyboard is just locked; other > times it generates garbage. Never managed to isolate the > circumstances in which this happened (but it didn't happen with a > kernel from last September or there-abouts). Haven't had it happen on > a desktop or server yet. I have seen this on numerious occasion, but have never tracked it down to any one specific thing. All on desktop and servers, but thats only because we don't do laptops. I have not seen it in quite some time (about a month), so I am thinking it has probably been unknowingly fixed someplace. I'll keep an eye out for it. -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message