On Mon, 31 Jan 2005, Malcolm Apps wrote: > > > If I do "modprobe ohci_hcd" from the command line, lsusb gives me : > > > > > > Bus 002 Device 001: ID 0000:0000 > > > Bus 001 Device 001: ID 0000:0000 > > > > > > but nothing else. > > > > What shows up in the system log when you do the modprobe manually? > > > > Alan Stern > > > > This: > PCI: Found IRQ 11 for device 0000:00:01.2 > PCI: Sharing IRQ 11 with 0000:00:01.3 > ohci_hcd 0000:00:01.2: OHCI Host Controller > ohci_hcd 0000:00:01.2: irq 11, pci mem 11928000 > ohci_hcd 0000:00:01.2: new USB bus registered, assigned bus number 1 > hub 1-0:1.0: USB hub found > hub 1-0:1.0: 3 ports detected > PCI: Found IRQ 11 for device 0000:00:01.3 > PCI: Sharing IRQ 11 with 0000:00:01.2 > ohci_hcd 0000:00:01.3: OHCI Host Controller > ohci_hcd 0000:00:01.3: irq 11, pci mem 1192a000 > ohci_hcd 0000:00:01.3: new USB bus registered, assigned bus number 2 > hub 2-0:1.0: USB hub found > hub 2-0:1.0: 3 ports detected > usb 1-2: new full speed USB device using address 2 > hub 1-2:1.0: USB hub found > hub 1-2:1.0: 4 ports detected > usb 1-3: new full speed USB device using address 3 > drivers/usb/class/usblp.c: usblp0: USB Bidirectional printer dev 3 if 0 > alt 0 proto 2 vid 0x03F0 pid 0x8204 > usb 1-2.3: new full speed USB device using address 4
That certainly looks like everything is working. An external hub was detected, along with two other devices, one of which was a printer. They certainly will show up in /proc/bus/usb/devices; I don't know lsusb shows nothing. > After a bit of rummaging and playing I've come up with a solution that > I'm happy with because I can scan and print again. OTOH I'm not happy > because it's a bit of a hack and my SmartCard reader still isn't > accessible. Is it not detected at all? You can get more information by turning on USB verbose debugging in the kernel configuration and rebuilding the drivers. Also, is it plugged into one of your computer's ports or the external hub? Can you try plugging the reader into a different port? > The hack is to make sure the USB stuff's plugged in and do 'modprobe > ohci_hcd' in rc.local. That seems like a reasonable approach given that the normal mechanism for loading ohci-hcd decides to unload it a moment later. Alan Stern ------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
