I don't see message of hotplug getting invoked by the kernel, like;
Nov 2 21:12:18 antonia kernel: hub.c: connect-debounce failed, port 1
disabled
Nov 2 21:12:23 antonia kernel: hub.c: new USB device 00:1d.0-1, assigned
address 2
Nov 2 21:12:23 antonia kernel: usb.c: USB device 2 (vend/prod 0x781/0x2)
is not claimed by any active driver.
Nov 2 21:12:26 antonia /etc/hotplug/usb.agent: Setup usb-storage for USB
product 781/2/9
Oh yeah, I don't have that drive connected right now. I can see, though, that hotplugging is failing so it's a safe bet that that device would go undetected.
However, let me try to restart hotplugging this evening with the device attached to make sure I have a complete test and complete output.
Question? If I have a NEC ATAPI drive in a USB/IEEE1394 enclosure, what will be the vendor and product info? That of the drive or that of the enclosure?
Thanks!
On Sun, 2 Nov 2003, Michael George wrote:On Sat, Nov 01, 2003 at 05:43:24PM -0800, Stephen J. Gowdy wrote:Yes, that is the file I presume I need to put a new entry into so that
when I plug this device in, the system knows to load the usb-storage
module.
No, that file is generated automatically.
Okay, that makes sense.
I've no idea what an 8.2Pro is. Can you try reading the documentation
at
linux-hotplug.sf.net?
Yes, and the info at linux-usb, but I'm not finding any references to
creating entries in that file.
You shouldn't add entries to that file. If you device is a usb-storage
device then it should already have a class level entry that matches it.
I can look at /usr/share/usb.ids to see what is there and find the
proper match_flags to use and then plug in the device and see what
/var/log/messages gives me as identifiers for the drive/enclosure, but
I don't know for sure if the modules.usbmap might be generated by the
kernel build and maybe I should make the entries elsewhere.
Yes, /etc/hotplug/usb.usermap. But you shouldn't need that...
Since the device does work once the usb-storage module is loaded, I
just need to know the correct process for having this "unknown" device
become "known"...
Are you sure hotplug is installed and your kernel has that option enabled?
hotplug is installed, it is configured in the kernel, and I thought it was
running, but it was not.
I tried to restart it and it would stop and give me: Nov 2 21:53:36 brutus kernel: usb.c: deregistering driver usbscanner
in /var/log/messages. Normal.
On the start, though, I would get:
Nov 2 21:53:50 brutus /etc/hotplug/usb.rc[6518]: loaded HCD: usb-uhci
Nov 2 21:53:50 brutus kernel: uhci.c: USB Universal Host Controller Interface
driver v1.1
Nov 2 21:53:51 brutus kernel: usb.c: registered new driver usbscanner
Nov 2 21:53:51 brutus kernel: scanner.c: USB scanner device (0x04b8/0x0110)
now attached to scanner0
Nov 2 21:53:51 brutus kernel: scanner.c: 0.4.10:USB Scanner Driver
Nov 2 21:53:51 brutus insmod: Using
/lib/modules/2.4.20-athlon/kernel/drivers/usb/scanner.o
Nov 2 21:53:51 brutus insmod: Symbol version prefix ''
Nov 2 21:53:55 brutus kernel: mice: PS/2 mouse device common for all mice
which looks innocuous, but on the commandline from issuing the start I got a
fail. Perhaps this is something that is best run at system start time? But I
would guess that it is dying at system start, too. It's been over 65 days
since a reboot, and at the time I didn't care if I could hotplug. As long as
the scanner would work (which isn't hotplugged) I was happy.
Actually, though, I use a KVM and a USB keybaord, so I am hotplugging that all
the time. Though sometimes it seems to get confused and I have to manually
rmmod and modprobe the usb-uhci module to get the keyboard recognized again.
Something about the device not accepting the id it's given...
Hmm, maybe the problems are related...
On Thu, 30 Oct 2003, Michael George wrote:
I just got an NEC 1300A CD-RW/DV�RW drive in a USB enclosure.
When I plug the device into a USB port and power it up, the system says:
Oct 30 14:00:26 brutus kernel: hub.c: new USB device 00:04.3-2.1,
assigned
address 3
Oct 30 14:00:26 brutus kernel: usb.c: USB device 3 (vend/prod
0x402/0x5621) is
not claimed by any active driver.
Oct 30 14:00:26 brutus kernel: usb-uhci.c: interrupt, status 2, frame#
278
Oct 30 14:00:26 brutus kernel: hub.c: usb_hub_port_status (2) failed
(err =
-84)
So it doesn't know what driver to load. If I manually do modprobe usb-storage
the drive is recognized and mounted right away. But shouldn't the
system
(8.2Pro kernel 2.4.20) automatically know that it's a storage device?
I figure there needs to be an entry in usb.distmap in /etc/hotplug,
but
I
can't find any info about how to construct an entry for a device
that's
not
already present in the file.
Where can I find that info?
-Michael
------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
