From owner-freebsd-current Fri Aug 13 21:54:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 352C914FCE for ; Fri, 13 Aug 1999 21:54:44 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id WAA29185; Fri, 13 Aug 1999 22:54:54 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id WAA13749; Fri, 13 Aug 1999 22:55:03 -0600 (MDT) Message-Id: <199908140455.WAA13749@harmony.village.org> To: Mike Smith Subject: Re: Problems with 4.0 keyboard input! Cc: "Ron Klinkien" , freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Fri, 13 Aug 1999 21:43:22 PDT." <199908140443.VAA00388@dingo.cdrom.com> References: <199908140443.VAA00388@dingo.cdrom.com> Date: Fri, 13 Aug 1999 22:55:03 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199908140443.VAA00388@dingo.cdrom.com> Mike Smith writes: : It's not the boot blocks doing anything explicit; they just use the BIOS. I have noticed that boot[12] doesn't seem to have this problem. However, after /boot/loader has been loaded, I see this problem from time to time. I don't know what is going on, I'm just reporting what I've seen.... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message