newbie questions on hotplug with IBM X20
<!doctype html public "-//w3c//dtd html 4.0 transitional//en"> <html>
I recently upgraded my IBM X20 notebook to Red Hat Linux 7.2 and would like to use a couple of serial
<br>devices that work fine when the computer is booted into WIN2K. <p>1) When a Targus PAUM003 USB mouse is plugged in, the following is printed /var/log/messages:
<br>
<blockquote>Dec 12 13:38:25 mike-laptop kernel: hub.c: USB new device connect on bus1/1, assigned device number 2
<br>Dec 12 13:38:25 mike-laptop kernel: hub.c: USB hub found <br>Dec 12 13:38:25 mike-laptop kernel: hub.c: 2 ports detected <br>Dec 12 13:38:25 mike-laptop /etc/hotplug/usb.agent: ... no drivers for USB product 451/2036/101 <br>Dec 12 13:38:26 mike-laptop kernel: hub.c: USB new device connect on bus1/1/2, assigned device number 3 <br>Dec 12 13:38:26 mike-laptop kernel: input0: USB HID v1.00 Mouse [KYE Genius USB Wheel Mouse] on usb1:3.0 <br>Dec 12 13:38:26 mike-laptop /etc/hotplug/usb.agent: ... can't load
module mousedev</blockquote>
What needs to do next in order to use this mouse from Linux? <p>2) When a USC-2000 USB serial converter is plugged in, the following is printed in /var/log/messages:
<blockquote>Dec 12 13:42:35 mike-laptop kernel: hub.c: USB new device connect on bus1/1, assigned device number 4
<br>Dec 12 13:42:35 mike-laptop kernel: hub.c: USB hub found <br>Dec 12 13:42:35 mike-laptop kernel: hub.c: 2 ports detected <br>Dec 12 13:42:35 mike-laptop kernel: hub.c: USB new device connect on bus1/1/2, assigned device number 5 <br>Dec 12 13:42:35 mike-laptop kernel: usb.c: USB device 5 (vend/prod 0x67b/0x2303) is not claimed by any active driver. <br>Dec 12 13:42:35 mike-laptop /etc/hotplug/usb.agent: ... no drivers for USB product 451/2036/101 <br>Dec 12 13:42:35 mike-laptop /etc/hotplug/usb.agent: ... no drivers
for USB product 67b/2303/200
<br> </blockquote>
What needs to do next in order to use this USB to serial converter? <p>Thanks for your help,
<br>Michael</html>
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
[email protected]
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
Sorry I can't quote your email, but it was sent in html format, which is not a nice thing to send to mailing lists.
Anyway, it sounds like these are general Linux USB questions, and the Linux USB Guide and FAQ should answer them:
http://www.linux-usb.org/
thanks,
greg k-h
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
[email protected]
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
Quoted 5 lines
1) When a Targus PAUM003 USB mouse is plugged in,
the following is printed/var/log/messages: ...Dec 12 13:38:26 mike-laptop /etc/hotplug/usb.agent: ... can't load module mousedevWhat needs to do next in order to use this mouse from Linux?
Did you verify that you can't use it? If "mousedev" is statically linked into your kernel, you should be able to use it already. I often get that message when I connect a USB mouse; it's still usable
So far as I know, there's no standard way for the hotplug scripts to tell when the reason a module can't be loaded is that it's been statically linked. "lsmod" only shows the dynamically linked modules, not the statically linked ones, and "modprobe" fails when it can't be dynamically linked, even if the module is already statically linked.
- Dave
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
[email protected]
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
David Brownell wrote:
<snip>
Quoted 3 lines
So far as I know, there's no standard way for the hotplug scripts to tell when the reason a module can't be loaded is that it's been statically linked. "lsmod" only shows the
<snip>
For the USB case, parse /proc/bus/usb/drivers?
Maybe we can come up with equivalent for other hotplug systems during 2.5? The work on conversion to driverfs and other gucci vfs things could probably be expanded to other subsystems.
Brad
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
[email protected]
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
Quoted 5 lines
Quoted 3 lines
So far as I know, there's no standard way for the hotplug scripts to tell when the reason a module can't be loaded is that it's been statically linked. "lsmod" only shows ...
For the USB case, parse
/proc/bus/usb/drivers?
That one wasn't a "usb" driver, it's an "input subsystem" driver.
An early USB-only version of the hotplug scripts did look at the /proc/bus/usb/drivers file, and knew how to work around the fact that some driver and module names don't match. (One that comes to mind is "keyboard" vs "usbkbd".) The current version doesn't ... maybe because after converting to use the "modules.usbmap" file, it wasn't usually an issue. (The "mousedev" module in question uses "usb.handmap" to work around the "no input hotplug" issue.)
Quoted 2 lines
Maybe we can come up with equivalent for other hotplug systems during 2.5?
I'd rather see a generic solution that's not specific to drivers, myself. It's not the sort of thing every driver subsystem should need to re-invent, IMO.
- Dave
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
[email protected]
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel