From owner-freebsd-current Thu Jan 27 13:43:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 3EB88154D5 for ; Thu, 27 Jan 2000 13:43:53 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id QAA20638; Thu, 27 Jan 2000 16:43:46 -0500 (EST) (envelope-from wollman) Date: Thu, 27 Jan 2000 16:43:46 -0500 (EST) From: Garrett Wollman Message-Id: <200001272143.QAA20638@khavrinen.lcs.mit.edu> To: "Jordan K. Hubbard" Cc: Bill Fenner , current@FreeBSD.ORG Subject: Re: Problems installing FreeBSD 4.0 20000125-CURRENT In-Reply-To: <45272.949008490@zippy.cdrom.com> References: <200001271856.KAA09456@windsor.research.att.com> <45272.949008490@zippy.cdrom.com> 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. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message