On Sun, 30 Dec 2001, Chris Johnson wrote: > Ours is also connected to a KVM switch, and that switch uses the scroll lock > key to bring up a menu of machines it's connected to (I've never seen it, but > that's how it was described to me). Someone else suggested that maybe scroll > lock was on on the first virtual terminal, causing the console to block. This > seems likely to be the cause of the problem, and I'll have someone check it out > when the office opens back up after the holiday. >
Yes, Belkin KVM switches listen for the Scroll lock key to be pressed twice in a row, then the up, down, left, or right arrow keys will determine which adjacent computer to switch to. It is possible to get them stuck. If a person presses Scroll lock once, the switch doesn't do anything, the computer behaves normally and does whatever Scroll lock is supposed to do. It he or she presses Scroll Lock twice in a row, though, the KVM switch makes a beep, and waits for one of the arrow keys to be pressed. Unless I'm mistaken, it disreguards any other input at that time. Just before it does that, it sends a second Scroll Lock signal to the current computer, to return it to its old Scroll Lock state. Apart from the arrow keys, a person can also switch computers by pressing the appropriate button on the KVM switch, of course. If it turns out that the KVM switch is at fault, just let me say that you're not the only one to accidently put the switch in this limbo state. Chris Wilmes To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message