On Wed, Sep 06, 2006 at 09:08:21AM +0100, Jenny Hopkins wrote:
And whilst I'm on the subject of posting solved problems: I posted a while ago about a mouse problem with a set of eight debian boxes running from a Belkin KVM, and Wayne pointed me in the direction of the firmware of those particular KVM models. I set our hardwarey bloke on to the task and he was sent a few different firmware changes to make. He did this and reported the changes, none of which solved the problem, and finally Belkin requested we send the switch back to them for tests. They promised to send a reply-addressed box for this. Two weeks later, still no box, and since several weeks had gone by before that with these eight production-essential machines out of action, we had to shrug and order a known-to-work DLink KVM. This was a great shame, as the Belkin was an easier to use design in that you could select the channel required at the press of a button, whereas the DLink you have to tab round. Also because i was pretty pleased that Belkin were being so supportive and helpful and then disappointed they couldn't even post a box. So the solution was that we didn't solve it but bypassed the problem.
I must say that I've never had a lot of success with KVM switches from the mouse point of view. I have a Belkin switch that I occasionally use (instead of Cygwin/X on my Win2k machine) to switch between Win2k and a Slackware Linux system. Over the years systems have changed but the mouse switching has never worked reliably (different systems, different KVM switches).
I just have two mice and use the KVM for only the keyboard and video.