I move my notebook around my office. Sometimes I am using the internal pointers, sometimes a USB mouse, and sometimes a USB keyboard/mouse adapter that is plugged into a kvm (actually two of them).
With one of these USB k/m adapters, when I plug in, the system fails to recognize the mouse (but no problem with the keyboard). The 2 adapters are the same brand/model (Aten), but the KVMs are different Aten masterviews.
Of course I would like to figure out why this is happening and get it to stop,
but meanwhile is there a way to restart the mouse services.
On Thu, 2006-09-07 at 16:55 -0400, Robert Moskowitz wrote:
I meant to mention that possibility. I don't know much about usb. I know there's 2(?) drivers that need loading? Not sure, uhci_hcd ehci_hcd?
It *used* to be, long ago and far away, that we could just rmmod stuff and then start up a service needing the modules. I wouldn't know if that's save in today's environ or not.
<snip sig stuff>
HTH -- Bill
On Thu, 2006-09-07 at 17:37 -0400, Robert Moskowitz wrote:
Wouldn't be there. These are device drivers. *If* they're loadable modules (I think they are), they can be inserted by the initrd process or may be mandated in the /etc/modprobe.conf file.
If you do "lsmod" you'll see them *if* they are modules. There's also a command that I like "modinfo". Gives basic info. There's some params, IIRC. "Man modinfo" 'cause I'll be darned if I remember them! :-(
<snip>
Test on one of your non-critical machines? rmmod <the name of a module> and it will either remove it or tell you something is using it, IIRC. That might give you enough boost on the old learning curve to address the current problem without resorting to Windows SOP.
HTH -- Bill
On Thu, 2006-09-07 at 18:56 -0400, Robert Moskowitz wrote:
*If* something, such as a mouse driver depended on them, normally a modprobe.conf (is USB special? Does it need definition in modprobe.conf? Yes, see below) might exist that showed that relationship. So, after you removed the usb drivers, if you did a restart on the mouse or kb or whatever, it would cause the modules to be reloaded via modprobe.conf entries. I don't use mouse/keyboard there, but mine has this.
alias usb-controller ehci-hcd alias usb-controller1 uhci-hcd
So if i did a mount, e.g. of my usb drive, that should cause the usb modules to be automatically loaded.
So, restart your mouse on the test machine and if your fortunate, the modprobe will occur, based on the node's "memory" that your mouse is usb, to load those modules.
I suppose I can do the remove and install to act as a remove? And then which one? Are they interdepent or what?
I'm not that familiar. IIRC, if one depended on the other, that would be in modprobe. But that could be elsewhere now? It's been a long time. Maybe they are independent. Like maybe one's a block driver and the other a character or something? I have never even read up on them.
HTH -- Bill
William L. Maltby wrote:
Well I did a
modprobe -rv ehci-hcd modprobe -rv ohci-hcd
The USB keyboard stopped working after I removed ohci-hcd.
I unplugged and replugged the USB M/K adapter and nothing happene. No mouse, no keyboard (of course notebook mouse/pointer continued to work). Then I did a:
modprobe -v ohci-hcd
And the usb keyboard started up, but not the mouse.
gpm restart did nothing.
Well, it is time to move my notebook. Next local only has a usb mouse, no kvm, no external keyboard...
Robert Moskowitz spake the following on 9/7/2006 5:53 PM:
Wouldn't it be more prudent to just use the keyboard/mouse that is built into the laptop? I know it doesn't solve your problem, but it makes it easier to work without the distraction of things not working.
William L. Maltby wrote:
Oh! Bill!!
[summer@bilby ~]$ file /etc/rc.d/init.d/* | (head;tail) /etc/rc.d/init.d/FreeWnn: Bourne shell script text executable /etc/rc.d/init.d/NetworkManager: Bourne shell script text executable
Robert Moskowitz wrote:
For within X, I don't think so.
I have a USB KVM, and I have had problems when switching, the KVM seemed to hang and needed its power cycled.
That involves unplugging all USB connectors to hosts that have power to the motherboard, and replugging them.
Fortunately, it seems to have settled down, it's a fairly tedious way to swap KV & M.