[NTLUG:Discuss] KVM Switch and constant new mouse

Chris Cox cjcox at acm.org
Fri Jul 18 11:39:31 CDT 2003


Dennis Daupert wrote:
> I plugged in a new Iogear KVM switch, and it has changed life as I know it
> :-)
> I.E, works pretty well. Only thing, every time I boot up SuSE 8.1 he thinks
> he has
> detected a new mouse. I have a straightforward Logitech 3-button PS/2, but
> suse forgets, I guess, and asks me to configure the "new mouse" _every
> time_.
> This one should be an easy fix, I just haven't learned it yet.
> 
> The YaST "new hardware" detection function brings up a list of options, and
> the one that seems to work with this mouse is IntelliMouse Explorer (ps2)

One problem is the way the cheap KVMs handle switching... most don't
feed info to the mouse when switched away and Linux loses its mind
when you return (use the Ctrl-Alt-F1, Alt-F7 trick to restore mouse
behavior).  My guess is that the problem is semi related.  I just ignore
the SuSE 8.2 request if I know for certain that my mouse definition
is correct and in tact for the given config.  But that's assuming
a interactive desktop config....

However... things are a bit different in 8.1.  Best bet is to just
turn of hwscan using the Runlevel Editor in YaST.  This is what I
do for enterprise server deployments using SuSE 8.0/8.1/etc.





More information about the Discuss mailing list