From: David Brownell <david-b@pacbell.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: scanner not autoloading, and wlan card
Date: Sun, 16 Jun 2002 23:30:11 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-102427015615330@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-102426501212566@msgid-missing>
> 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
prev parent reply other threads:[~2002-06-16 23:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-16 22:02 scanner not autoloading, and wlan card David Cougle
2002-06-16 23:30 ` David Brownell [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=marc-linux-hotplug-102427015615330@msgid-missing \
--to=david-b@pacbell.net \
--cc=linux-hotplug@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).