Date: Wed, 22 May 1996 00:09:33 -0700 (PDT) From: Jake Hamby <jehamby@lightside.com> To: Michael Smith <msmith@atrad.adelaide.edu.au> Cc: joerg_wunsch@uriah.heep.sax.de, freebsd-current@freebsd.org Subject: Re: bad keyboard reset routine? Message-ID: <Pine.GSO.3.92.960522000626.408A-100000@hamby1> In-Reply-To: <199605220517.OAA02201@genesis.atrad.adelaide.edu.au>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 22 May 1996, Michael Smith wrote: > > As Jordan K. Hubbard wrote: > > > > > Thanks for reminding me.. I also meant to mention that I've been > > > getting: > > > > > > scprobe: keyboard RESET failed (result = 0xfa) > > > > Interesting. :-) > > > > I vote for killing scprobe()'s keyboard reset attempt entirely. It's > > of no real use. > > Given that it will have reset on power-up, and the BIOS will have reset > it again at least twice. It might be nice to make it an option depending > on a 'flags' setting just in case someone needs it. I too get that message. Good to hear that it's not serious. In which case it should not be printed as a "failure". Reminds me of an unusual bug in Solaris/x86 2.5 on my system where whenever you "touch /reconfigure" and reboot (or equivalently, "boot -r" which rebuilds the /dev directory and reprobes the hardware), the keyboard is completely frozen. The first few times I needed to do this, I just waited till the disk activity stopped then punched the Reset button! Finally I realized if you unplugged and replugged the keyboard cable it came back to life. Odd! :-) ------------------------------------------------------------------------------ |Jake Hamby| Ask me about Unix, FreeBSD, Solaris, The Tick, Motif, or NT, eh?| ------------------------------------------------------------------------------ "Hi, can I interest you in buying some meat over the phone?" -Lotus commercial
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.3.92.960522000626.408A-100000>