Can't access USB Memory Card reader

rhauff · 11-23-2003, 10:35 PM

I'm trying to use a Trendnet USB 2.0 6-in-1 card reader/writer, the mfg. says it is kernel 2.4.0 compatible. I am running Mandrake 9.2, kernel 2.4.23 and think I have all the appropriate kernel options and modules. I don't have any /dev/sd devices when I plug it in however. Here is a piece of dmesg:

Initializing USB Mass Storage driver...
usb.c: registered new driver usb-storage
USB Mass Storage support registered.
hub.c: new USB device 00:10.3-6, assigned address 4
usb.c: USB device not responding, giving up (error=-71)
hub.c: new USB device 00:10.3-6, assigned address 5
usb.c: USB device not responding, giving up (error=-71)
usb-uhci.c: $Revision: 1.275 $ time 08:51:56 Nov 22 2003
usb-uhci.c: High bandwidth mode enabled
usb-uhci.c: USB UHCI at I/O 0xdc00, IRQ 21
usb-uhci.c: Detected 2 ports
usb.c: new USB bus registered, assigned bus number 2
hub.c: USB hub found
hub.c: 2 ports detected
usb-uhci.c: USB UHCI at I/O 0xe000, IRQ 21
usb-uhci.c: Detected 2 ports
usb.c: new USB bus registered, assigned bus number 3
hub.c: USB hub found
hub.c: 2 ports detected
usb-uhci.c: USB UHCI at I/O 0xe400, IRQ 21
usb-uhci.c: Detected 2 ports
usb.c: new USB bus registered, assigned bus number 4
hub.c: USB hub found
hub.c: 2 ports detected
usb-uhci.c: v1.275:USB Universal Host Controller Interface driver
hub.c: new USB device 00:10.3-6, assigned address 6
usb.c: USB device not responding, giving up (error=-71)
hub.c: new USB device 00:10.3-6, assigned address 7
usb.c: USB device not responding, giving up (error=-71)

Any ideas?
Thanks
Roland

rhauff · 12-05-2003, 08:10 AM

I guess I'll reply to my own. After LOTS of searching and testing, I found the ehci module has problems with the VIA KT400 chipset, doing "rmmod ehci-hcd" removes the USB 2.0 module and allows devices to run at USB 1.1 speed, whichI can live with.
I am just hoping ehci gets upgraded to play nice with VIA, cause there are lot's of their chipsets out there. Also I've seen that the APIC settings in BIOS or disabling either in BIOS or kernel boot string should fix the problem, but I had no luck.
Roland