KVM-switch problem no scroll-lock key
Hi,
I have a laptop and a desktop. On the laptop W2k is installed. On the desktop I have Linux Redhat 9. They are both connected to a KVM-switch (Keyboard, Video, Mouse) , that switches between the two pc's using the key [scroll][scroll][arrow up] or [arrow down]. The problem I am having, is that once I am in Redhat 9, scroll lock does not seem to work, or (is perhaps for some function I don't know about). So once I am in Linux I cannot switch back to my laptop. Does anyone has a similar problem? Or does anyone know how I can use the scroll lock key. When I hit this key (the led is not going on...). Thanks. |
|
Newstar 2-port KVM switch
Thanks,
Mine is a Newstar 2-port KVM-switch. It is not listed in the url you mentioned. I am afraid I should have bought a KVM-switch with a real physical switch in stead of some hot keys. Hope the real good ones aren't expensive. |
Check if you are using a PS/2 -> USB converter
All of my KVM problems went away when I noticed that the actual mouse I was using was connected to the
KVM through one of those PS/2 (round plug) to USB (rectangle plug) converters. I found another mouse that didn't need the converter, but still has the wheel and everything works great. For me the IMPS/2 didn't matter and getting rid of the scroll wheel in XF86Config didn't help but getting that converter out of the way made everything work like magic. Drake42 |
Solution!
I ran into the same issue using a USB KVM switch with CentOS 5.0. This thread discusses using xmodmap to resolve the issue:
http://www.linuxquestions.org/questi...t-work-536178/ Happy scroll locking! (-: |
Please look at the date of the original post: 2004.
|
Duly noted. 5 years later people are still having the same issue (-:
|
Quote:
|
Quote:
xmodmap -e 'add mod3 = Scroll_Lock' the light comes on, but the keypress function apparently gets swallowed by something. <scroll_lock><scroll_lock> (the manual with the switch says EVERY OS including linux can use this) works fine as long as both machines are running console-only, but that's not what's needed. How could such a basic problem remain unsolved for so long? |
All times are GMT -5. The time now is 06:06 PM. |