I have an Asus A7V8x motherboard, and I am running 2.4.27-1-k7 (the latest Debian).

12 Mbs USB devices work.

When I plug in any high speed (480 Mbs) USB 2.0 device, I get the following messages in syslog:

Sep 12 08:25:53 bagpipes kernel: hub.c: new USB device 00:10.3-5, assigned address 19
Sep 12 08:25:53 bagpipes kernel: usb.c: USB device not responding, giving up (error=-71)


I've tried both a flash USB Mass Storage (UMS, Fujifilm) device and an iRiver mp3 IFP-790 player. Other devices, e.g. a Bluetooth device, were caught by hotplug and loaded the right module e.g, the Bluetooth bluez module.

I have noticed, if I'm fast enough to hit lsusb, that there's a transient time when the device is almost recognized... it shows up on lsusb and then goes off the list.

By way of experiment, I tried unloading the ehci-hcd module from the kernel and then everything worked as expected: the uhci driver caught the insert from hotplug, the usb-storage module loaded to catch the Fuji drive, and placed it on the /dev/scsi chain (didn't create a /dev/sd* drive, but that's a separate question about configuration).

The conclusion I get is that either there's a config issue I'm not catching a or mobo support issue with the ehci-hcd driver.

Are these known issues? The A7V8X uses the VIA chipset, the 8232 IIRC, and I thought VIA was supported at this point.

I've also tried 2.6.8-1-k7, by the way. I didn't attempt to unload ehci-hcd to see what happens, but I could not load any 2.0 devices.

Any suggestions or comments?

--
Moshe Yudkowsky



-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 13. Go here: http://sf.net/ppc_contest.php
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-users

Reply via email to