- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- bad behavior of KVM console's touch pad
Operating System - Linux
1752565
Members
5422
Online
108788
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-12-2007 09:58 PM
тАО12-12-2007 09:58 PM
bad behavior of KVM console's touch pad
Hello,
I have 4 servers HP proliant DL380G5 on which i have installed linux red hat 4. the servers are managed via a unique console related to a KVM switch.
when I have installed the KVM for the first time, the mouse (touch pad ) of the console did not work at all, then , i have disconnected the KVM switch and I have attached the console directly to one of the servers, and so, the mouse is working very well.
when i have reconnected the KVM switch back , the mouse moved , so it is working now, but its behavior is very strange, and very bad, i dont know how to explain it, but it is moving down when trying to move left for exemple, it makes right clicks without doing it myself...
Could anyone help me resolving this issue?
Thanks a lot and Best regards
Samer
I have 4 servers HP proliant DL380G5 on which i have installed linux red hat 4. the servers are managed via a unique console related to a KVM switch.
when I have installed the KVM for the first time, the mouse (touch pad ) of the console did not work at all, then , i have disconnected the KVM switch and I have attached the console directly to one of the servers, and so, the mouse is working very well.
when i have reconnected the KVM switch back , the mouse moved , so it is working now, but its behavior is very strange, and very bad, i dont know how to explain it, but it is moving down when trying to move left for exemple, it makes right clicks without doing it myself...
Could anyone help me resolving this issue?
Thanks a lot and Best regards
Samer
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-13-2007 05:07 AM
тАО12-13-2007 05:07 AM
Re: bad behavior of KVM console's touch pad
Shalom,
Try connecting if possible a normal mouse to the KVM.
Its pretty common that Linux won't use certain mouse types via KVM. Laser mice don't work via KVM, but regular ball mice do.
Eventually the OS will catch up.
SEP
Try connecting if possible a normal mouse to the KVM.
Its pretty common that Linux won't use certain mouse types via KVM. Laser mice don't work via KVM, but regular ball mice do.
Eventually the OS will catch up.
SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-13-2007 07:29 AM
тАО12-13-2007 07:29 AM
Re: bad behavior of KVM console's touch pad
The protocol between the touchpad and the server has got out of sync, probably because the KVM switch cuts the power to the mouse when switching it from one server to another.
With Linux, you can usually recover from this fairly easily. If you're using the X Window System GUI, press Ctrl-Alt-F1 to switch to text-mode virtual console. Move the mouse, then press Ctrl-Alt-F7 to switch back to the GUI.
If you are not using the GUI or the procedure above won't help, restart the "gpm" process. Switch to text mode first if necessary (as above).
sh /etc/init.d/gpm restart
With most Microsoft OSs, the only way to recover from this state is to reboot the server! (as far as I know :-)
With newer kernels, there are some parameters that might help, but I'm not sure whether they're implemented in Linux kernel 2.6.9 (RHEL 4's kernel version) or not.
As RHEL 4 has the psmouse driver compiled in the kernel and not as a separate module, the parameters must be specified as kernel boot parameters:
psmouse.resetafter=2
Makes the mouse driver to automatically reset the mouse after receiving 2 "bad" packets from the mouse.
and/or
psmouse.resync_time=120
Forces the mouse to be reset after the mouse has been idle for 120 seconds.
MK
With Linux, you can usually recover from this fairly easily. If you're using the X Window System GUI, press Ctrl-Alt-F1 to switch to text-mode virtual console. Move the mouse, then press Ctrl-Alt-F7 to switch back to the GUI.
If you are not using the GUI or the procedure above won't help, restart the "gpm" process. Switch to text mode first if necessary (as above).
sh /etc/init.d/gpm restart
With most Microsoft OSs, the only way to recover from this state is to reboot the server! (as far as I know :-)
With newer kernels, there are some parameters that might help, but I'm not sure whether they're implemented in Linux kernel 2.6.9 (RHEL 4's kernel version) or not.
As RHEL 4 has the psmouse driver compiled in the kernel and not as a separate module, the parameters must be specified as kernel boot parameters:
psmouse.resetafter=2
Makes the mouse driver to automatically reset the mouse after receiving 2 "bad" packets from the mouse.
and/or
psmouse.resync_time=120
Forces the mouse to be reset after the mouse has been idle for 120 seconds.
MK
MK
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP