[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: usb drive nolonger registers on one pc, still registers on another



On Tue, Dec 14, 2010 at 10:48:32AM -0500, Thomas H. George wrote:
> On Tue, Dec 14, 2010 at 12:29:34PM +0000, Camaleón wrote:
> > On Mon, 13 Dec 2010 17:16:21 -0500, Thomas H. George wrote:
> > 
> > > A Toshiba usb hard drive previously registered with no difficulty on one
> > > computer but still registers with no difficulty on a seconcd computer.
> > > Both computers are using the Linux 2.6.32-5-amd64 stock kernel but the
> > > one with the problem was just updated and the one with no problem was
> > > updated last August.
> > > 
> > > By failing to register I mean that when connected I get a continuing
> > > series of messages like this:
> > > 
> > > 
> > > Dec 13 16:54:21 dragon kernel: [ 3212.860525] usb 1-2: new high speed USB device using ehci_hcd and address 44 
> > > Dec 13 16:54:21 dragon kernel: [ 3213.008537] hub 1-0:1.0: unable to enumerate USB device on port 2 
> > 
> > (...)
> > 
> > > Has something changed in the kernel?  Or perhaps in some other software
> > > as in each case the update was a full dist-upgrade?
> > 
> > You mean the USB hard disk is working properly but logs that output or 
> > you get the errors and the disk is not detected at all?
> 
> The device is detected, that is the led on the device flashes repeatedly
> as the system tries to assign a device number and fails.
> > 
> > You can make a quick test: run " dmesg | grep [euo]hci" in both computers to 
> > check what USB module is in charge of the disk. There are some devices that 
> > play better with old "[uo]hci" stack and have problems when using the new one.
> > 
> Very interesting.  The older system finds only ehci entries in dmesg.
> The newer system finds both ohci and echi entries and, more
> importantly, issues a warning that ohci controller is being loaded
> before the ehci controller.  I don't know how to change this.  I checked
> /etc/udev but found no rules regarding usb controllers.
> 
> Here is the dmesg output for the newer system:
> 
> 
> [    0.778844] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
> [    0.778899] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
> [    0.778936] Warning! ehci_hcd should always be loaded before uhci_hcd and ohci_hcd, not after
  .
  .
  .

Edited /etc/usb_modeswitch.conf to enable mode switching.  Now the ehci
controller is loaded before the ohci controller.  This does not solve
the problems.

> > 
> These final entries for the low speed USB device may relate to
> Cyberpower ups.  The NUT usbd does not always find the Cyperpower driver
> on bootup.  Left to its own devices it will repeadedly try and fail
> again.  Issuing the upsdrvctl -D start command two or three times
> corrects the situation.  I hope correcting the order of loading the usb
> controllers will correct all the problems.
> 
> Tom
> > 
> > -- 
> > To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org 
> > with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
> > Archive: [🔎] pan.2010.12.14.12.29.31@gmail.com">http://lists.debian.org/[🔎] pan.2010.12.14.12.29.31@gmail.com
> > 
> > 
> 
> 
> -- 
> To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org 
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
> Archive: [🔎] 20101214154832.GA14917@tomgeorge.info">http://lists.debian.org/[🔎] 20101214154832.GA14917@tomgeorge.info
> 
> 


Reply to: