On Sat, 9 Jul 2005, Dr.techn. Alexander K. Seewald wrote: > Hi, > > Is the GL811E supported by usb-storage? I'm using a 64bit AMD system > (MSI K8N) with ohci_hcd and ehci_hcd (ohci_hcd is tested, via a usblp > device; ehci_hcd is not yet tested since I don't have any other USB 2.0 > device)
Yes, the GL811E is supported. > The chip says GL811E and 0506MK8JG-04. It is an IDE-USB2.0 interface > chip. However, when I switch the HDD enclosure on, the hdd spins up, > but no entries at all appear in messages, dmesg or syslog. I've read > that there may be issues with the chip not recognizing certain > harddisks. I've tried two harddisks, but none of them work. It might > be an issue with ehci_hcd on nforce4. However, I get no errors > during startup: > ehci_hcd 0000:00:02.1: PCI device 10de:005b (nVidia Corporation) > ehci_hcd 0000:00:02.1: irq 21, pci mem 0xfebfe000 > ehci_hcd 0000:00:02.1: new USB bus registered, assigned bus number 2 > ehci_hcd 0000:00:02.1: park 0 > ehci_hcd 0000:00:02.1: USB 2.0 initialized, EHCI 1.00, driver 10 Dec 2004 > > Should I try the newest EHCI driver? Or is it likely that the > enclosure is completely broken, since even with USB debugging > activated no messages appear when I plug it in or remove it. > In /proc/bus/usb, I also see no new device (bus 002 shows just the > hub; 001 shows the hub and the usblp device (USB 1.1)) You can try using the enclosure after doing "rmmod ehci-hcd". If your OHCI controller is able to communicate with the enclosure then you'll know that the enclosure isn't completely broken and it is able to recognize the hard disk. It also never hurts to try using the newest drivers. > I've read somewhere that the GL811E is supported, although there are > problems with file transfer. But mine is not even recognized by the > system, so perhaps it is a different problem. This does not sound at all like the problems people used to have with file transfers. > If someone could point me in the right direction to investigate and > fix this problem, that would be nice. Is there a low-level interface > to USB, where I can check if there is any communication at all? A major part of the low-level interface is to turn on CONFIG_USB_DEBUG. If you still get no messages in the system log after plugging in the device, then some part of the hardware is broken: the controller, the cable, or the device. Alan Stern ------------------------------------------------------- This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual core and dual graphics technology at this free one hour event hosted by HP, AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar _______________________________________________ [email protected] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
