From owner-freebsd-current Fri Aug 13 22:10:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles530.castles.com [208.214.165.94]) by hub.freebsd.org (Postfix) with ESMTP id ED76E15054 for ; Fri, 13 Aug 1999 22:10:37 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id WAA00566; Fri, 13 Aug 1999 22:05:31 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199908140505.WAA00566@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Warner Losh Cc: Mike Smith , "Ron Klinkien" , freebsd-current@FreeBSD.ORG Subject: Re: Problems with 4.0 keyboard input! In-reply-to: Your message of "Fri, 13 Aug 1999 22:55:03 MDT." <199908140455.WAA13749@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 13 Aug 1999 22:05:31 -0700 From: Mike Smith 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.... *mumble* We're seeing a few cases where BIOS code in the boot path isn't working too well (or at all) when run in vm86 mode. 8( -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message