From owner-freebsd-current Fri May 24 06:45:57 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id GAA04356 for current-outgoing; Fri, 24 May 1996 06:45:57 -0700 (PDT) Received: from melbourne.DIALix.oz.au (melbourne.DIALix.oz.au [192.203.228.98]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id GAA04344 for ; Fri, 24 May 1996 06:45:53 -0700 (PDT) Received: (from seeuucp@localhost) by melbourne.DIALix.oz.au (sendmail) with UUCP id XAA04207 for freebsd-current@freebsd.org; Fri, 24 May 1996 23:45:43 +1000 (EST) Received: (from mark@localhost) by putte.seeware.DIALix.oz.au (8.7.5/8.7.3) id WAA08621; Fri, 24 May 1996 22:46:08 +1000 (EST) Date: Fri, 24 May 1996 22:46:08 +1000 (EST) Message-Id: <199605241246.WAA08621@putte.seeware.DIALix.oz.au> X-Newsreader: knews 0.9.6 References: <199605220552.PAA11944@godzilla.zeta.org.au> <5306.832756715@time.cdrom.com> From: mark@seeware.DIALix.oz.au (Mark Hannon) Subject: Re: bad keyboard reset routine? X-Original-Newsgroups: freebsd.current In-Reply-To: <5306.832756715@time.cdrom.com> To: freebsd-current@freebsd.org Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article <5306.832756715@time.cdrom.com>, jkh@time.cdrom.com (Jordan K. Hubbard) writes: >> It is used to set the keyboard to a known state. E.g., it blows away the >> BIOS defaults for the keyboard repeat and delay rates (RAD), and it turns > >Can we kill the error message then since so many keyboards seem to >exhibit this problem? :-) > > Jordan Unfortunately since this error message started showing up my keyboard also stopped working! Running -stable a few days old. /mark -- +-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-+ | Mark Hannon,| FreeBSD - Free Unix for your PC| mark@seeware.DIALix.oz.au| | Melbourne, | PGP key available by fingering | epamha@epa.ericsson.se | | Australia | seeware@melbourne.DIALix.oz.au | | +-=-=-=-=-=-=-+-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-+