Date: Wed, 9 Apr 1997 06:41:58 -0400 (EDT) From: Thomas David Rivers <ponds!rivers@dg-rtp.dg.com> To: ponds!time.cdrom.com!jkh, ponds!lakes.water.net!rivers Cc: ponds!freebsd.org!hackers Subject: Re: Some significant (daresay serious) problems with 2.2.1 install & keyboard Message-ID: <199704091041.GAA08473@lakes.water.net>
next in thread | raw e-mail | index | archive | help
> >> However, there were some circumstances that might make this easier >> to reproduce for a diagnosis. >> >> I was trying to scroll-lock on the device probes to ensure I had >> entered everything correctly in the CLI (the port for ep0 needed to >> change from the value in the GENERIC kernel); but instead of pressing >> [Pause] - I had pressed [Scroll Lock]. This, of course, did not > >I think that falls under "PLIBCAK*" and I will therefore consider this >bug report closed. :-) > > Jordan > >* Problem Lies In Between Chair And Keyboard. :) > Hmmm... I wouldn't think so. You see; 1) on one more modern machine I was able to cause the problem. 2) On an older machine, I don't have to do anything to cause the problem - it's "just there." 3) In no circumstance (in my opinion) should the system installation do "strange things" with the keyboard. So what if you accidently press Scroll-lock; why does that cause the wrong key values? [note that pressing scroll-lock again doesn't fix the problem]; Now, if this was NUM-LOCK, and I had said the digits don't work; then we could close it, but that's not what's going on. - Dave Rivers -
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199704091041.GAA08473>