topic title: can't mount external hd (unable to enumerate usb device)
Posts: 44
Johnn
Joined: 16 Feb 2013
#1
I'm getting a lot of this messages:

Code: Select all

[534646.693520] hub 1-1:1.0: unable to enumerate USB device on port 3
[534646.949437] hub 1-1:1.0: unable to enumerate USB device on port 3
[534647.205321] hub 1-1:1.0: unable to enumerate USB device on port 3
[534647.461274] hub 1-1:1.0: unable to enumerate USB device on port 3
And usually to solve this I whould do:

echo -n"0000:00:1a.0" > /sys/bus/pci/drivers/ehci_hcd/unbind

And then I whould be able to mount it, but there is no 0000:00:1a.0, only 0000:00:1d.0 and that one disables all my usb ports :\

Any way to solve this? The last distribution that I got this old hard drive working was like ubuntu 9.10, and then ubuntu started to not being able to mount it aswell..

Don't bother asking me if the hard drive is broken, because it's not.. it's just old, I tested it today on a window$ machine.

Thanks in advance.
Posts: 1,308
BitJam
Joined: 31 Aug 2009
#2
Do you have a /sys/bus/pci/drivers/ohci_hcd/ directory? If so, what are the contents?

There are four different
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"https://en.wikipedia.org/wiki/Host_controller_interface_%28USB,_Firewire%29"
linktext was:"*hci_hcd drivers"
====================================
:

ohci: usb 1.1
ehci: usb 2.0
uhci: proprietary, incompatible with ohci
xhci: supposed to be faster and better

On the antiX I'm running, all four are compiled in. Maybe there is a different ^hci_hcd/ directory where you need to do the unbind trick. You want to get your old drive to use ohci.

If this doesn't work the only other thing I know to try is to ask anti very kindly if he would be willing to try making a kernel that has ehci_hcd compiled as a module. I think the unbind trick is pretty much the equivalent of this (except perhaps for when it happens). Also, this could require us to make other changes in order to ensure we use the faster ehci on systems that boot from a USB stick.

I'd certainly like to see the contents of the other *hci_hcd/ directories before asking anti for a new kernel.
Posts: 44
Johnn
Joined: 16 Feb 2013
#3
BitJam wrote:Do you have a /sys/bus/pci/drivers/ohci_hcd/ directory? If so, what are the contents?

There are four different
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"https://en.wikipedia.org/wiki/Host_controller_interface_%28USB,_Firewire%29"
linktext was:"*hci_hcd drivers"
====================================
:

ohci: usb 1.1
ehci: usb 2.0
uhci: proprietary, incompatible with ohci
xhci: supposed to be faster and better

On the antiX I'm running, all four are compiled in. Maybe there is a different ^hci_hcd/ directory where you need to do the unbind trick. You want to get your old drive to use ohci.

If this doesn't work the only other thing I know to try is to ask anti very kindly if he would be willing to try making a kernel that has ehci_hcd compiled as a module. I think the unbind trick is pretty much the equivalent of this (except perhaps for when it happens). Also, this could require us to make other changes in order to ensure we use the faster ehci on systems that boot from a USB stick.

I'd certainly like to see the contents of the other *hci_hcd/ directories before asking anti for a new kernel.

I've:

Code: Select all

0000:00:1d.0  bind  module  new_id  remove_id  uevent  unbind
Thanks for replying.
Posts: 44
Johnn
Joined: 16 Feb 2013
#4
BitJam wrote:Do you have a /sys/bus/pci/drivers/ohci_hcd/ directory? If so, what are the contents?

There are four different
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"https://en.wikipedia.org/wiki/Host_controller_interface_%28USB,_Firewire%29"
linktext was:"*hci_hcd drivers"
====================================
:

ohci: usb 1.1
ehci: usb 2.0
uhci: proprietary, incompatible with ohci
xhci: supposed to be faster and better

On the antiX I'm running, all four are compiled in. Maybe there is a different ^hci_hcd/ directory where you need to do the unbind trick. You want to get your old drive to use ohci.

If this doesn't work the only other thing I know to try is to ask anti very kindly if he would be willing to try making a kernel that has ehci_hcd compiled as a module. I think the unbind trick is pretty much the equivalent of this (except perhaps for when it happens). Also, this could require us to make other changes in order to ensure we use the faster ehci on systems that boot from a USB stick.

I'd certainly like to see the contents of the other *hci_hcd/ directories before asking anti for a new kernel.

Code: Select all

/sys/bus/pci/drivers/ohci_hcd:
bind  new_id  remove_id  uevent  unbind

/sys/bus/pci/drivers/uhci_hcd:
bind  module  new_id  remove_id  uevent  unbind

/sys/bus/pci/drivers/xhci_hcd:
0000:05:00.0  bind  module  new_id  remove_id  uevent  unbind
hummm... so weird, kernel 3.6 works fine with the HD because it has the ehci_hcd folder and I can unbind, but this one I'm finding it hard to.

EDT: Thank you for helping me, I hope you guys don't need to change the kernel :\