scanner not autoloading, and wlan card

scanner not autoloading, and wlan card

[David Cougle]

I have

hotplug-2002_04_01-6

and a usb scanner, but even though I have this in modules.conf...
alias char-major-180,48 scanner


it still will not load the scanner module when i use xsane or whatever.
also, I have a usb printer, hp960cse, that does not seem to autoload either.
it's /dev/usb/lp0

hotplug seems to find most other items, but not these two, and even though i 
have this

# usb module         match_flags idVendor idProduct bcdDevice_lo 
bcdDevice_hi bDeviceClass bDeviceSubClass bDeviceProtocol bInterfaceClass 
bInterfaceSubClass bInterfaceProtocol driver_info
wusb11  0x0003 0x066b 0x2212 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
prism2usb  0x0003 0x066b 0x2212 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00

and i have something called wusb11 in usb/ dir to execute on plugging it in
is that how it goes?
how do i find out if it's correct for usb.usermap?
is the first part the script it executes in usb/?


_________________________________________________________________
Chat with friends online, try MSN Messenger: http://messenger.msn.com


_______________________________________________________________

Sponsored by:
ThinkGeek at http://www.ThinkGeek.com/
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

Re: scanner not autoloading, and wlan card

[David Brownell]

> also, I have a usb printer, hp960cse, that does not seem to autoload 
> either.
> it's /dev/usb/lp0
> 
> hotplug seems to find most other items, but not these two,

USB hotplug is driven by data found in the USB device and interface
descriptors.  It's quite possible that the drivers in your kernel don't
happen to know about your scanner and/or printer devices.

You didn't say what kernel you're using ... does 2.4.19-pre10 fail
in that way?  If so, send the relevant /proc/bus/usb/devices info to
the maintainers of the "printer" and "scanner" drivers.


 > 	and even
> though i have this
> 
> # usb module         match_flags idVendor idProduct bcdDevice_lo 
> bcdDevice_hi bDeviceClass bDeviceSubClass bDeviceProtocol 
> bInterfaceClass bInterfaceSubClass bInterfaceProtocol driver_info
> wusb11  0x0003 0x066b 0x2212 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
> prism2usb  0x0003 0x066b 0x2212 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 
> 0x00
> 
> and i have something called wusb11 in usb/ dir to execute on plugging it in
> is that how it goes?
> how do i find out if it's correct for usb.usermap?

There are some suggestions on the linux-hotplug.sf.net website about
how to debug problems in driver hotplugging:

     http://linux-hotplug.sourceforge.net/?selectedÞbug

If this is the "prism2usb" driver I found out about recently, that
driver doesn't yet know about hotplugging.  It needs to include a
MODULE_DEVICE_TABLE and use it correctly, then "depmod" will find it
and list it in /lib/modules/$(uname -r)/modules.usbmap and it'll just
hotplug normally.


> is the first part the script it executes in usb/?

The first field is the name of the logical driver, which may also have
a usermode setup script ... if there's an executable of that name in
/etc/hotplug/usb it should run that when a device associated with that
kernel driver gets hotplugge.  You should be able to just name your
script "prism2usb" and install it, without needing to make any entries
in "usb.handmap" ... that file should mostly be needed for drivers that
only use "usbfs" and have no other kernel code.

- Dave



_______________________________________________________________

Sponsored by:
ThinkGeek at http://www.ThinkGeek.com/
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel