Problem with USB 2.0 - Revision history

Djwgates: /* Solutions */

2011-01-15T19:41:40Z

‎Solutions

2010-08-10T23:08:38Z

‎See Also: link to T42 USB ports not working

2010-07-20T05:30:11Z

‎Models affected

2010-07-20T01:00:44Z

‎Models affected: fix layout

2010-07-20T00:58:57Z

Add section with the models we have reports of fried USB2.0 ports for

2009-08-30T21:35:27Z

‎removing ehci_hcd

2009-04-20T20:01:19Z

‎removing ehci_hcd

2009-04-20T19:58:07Z

‎disabling ehci_hcd

2009-04-20T19:53:51Z

better document solutions

2009-01-31T23:11:19Z

‎Mechanical Damage to Mainboard

@@ Line 39: / Line 39: @@
 ==Solutions==
 This seems to be a hardware problem with the USB controller on Intel's chip or related electronics. Sending the laptop in for service may help.
 If the Linux kernel refuses to register the USB device, you can try removing or disabling the ehci_hcd part. Doing this means that USB devices will run at USB 1.1 speeds, which is supported by pretty much every USB device for backwards compatibility. This is not a problem for USB Keyboards and Mice as they are typically USB 1.1 anyway, but for USB storage devices it can slow things down dramatically.

← Older revision		Revision as of 23:08, 10 August 2010
Line 66:		Line 66:
	== See Also ==		== See Also ==
	[http://forums.cnet.com/5208-7586_102-0.html?forumID=68&threadID=151816 IBM X40 USB Problem] (fried USB on multiple {{X40}}s)		[http://forums.cnet.com/5208-7586_102-0.html?forumID=68&threadID=151816 IBM X40 USB Problem] (fried USB on multiple {{X40}}s)
		+
		+	[http://www.oneafrikan.com/2006/03/03/ibm-t42p-thinkpad-usb-ports-not-working/ T42 USB ports not working]

@@ Line 16: / Line 16: @@
 ====Models affected====
-* {{T40}}, {{T41}}, {{T42}}
+* {{T40}}, {{T40p}}, {{T41}}, {{T41p}}, {{T42}}, {{T42p}}
 * {{X40}}

@@ Line 16: / Line 16: @@
 ====Models affected====
-{T40}
+* {{T40}}, {{T41}}, {{T42}}
-{T41}
+* {{X40}}
 ===Mechanical Damage to Mainboard===

@@ Line 14: / Line 14: @@
 there is a (small) risk that when plugging in or removing a USB device causes damage to the chip. Usually, the first symptom is broken USB 2.0, behaving in exactly the way you described (ie, works under Windows, but only after some waiting and as if it was connected to a USB 1.1 controller, not a USB 2.0 one, and not at all under Linux unless you unload the USB 2.0 driver). This tends to lead to a completely dead chipset a short time later, so better get it serviced NOW.
 }}
 ===Mechanical Damage to Mainboard===

@@ Line 44: / Line 44: @@
 To rebuilt your initrd on a Red Hat/Fedora system, run the following command
-  mkinitrd /boot/initrd-$(uname -r).img $(uname -r)
+  mkinitrd -f /boot/initrd-$(uname -r).img $(uname -r)
 ===disabling ehci_hcd===

@@ Line 43: / Line 43: @@
 Or alternatively to prevent the module from ever loading, add {{path|ehci_hcd}} to {{path|/etc/modprobe.d/blacklist.conf}} (or {{path|/etc/modprobe.d/blacklist}}). But note that adding it to the blacklist file might not be enough by itself as most distributions load the ehci_hcd module already during initrd, as such you might need to rebuild your initrd after adding it to the blacklist for it to have effect.
-To rebuilt your inird on a Red Hat/Fedora system, run the following command
+To rebuilt your initrd on a Red Hat/Fedora system, run the following command
   mkinitrd /boot/initrd-$(uname -r).img $(uname -r)
 ===disabling ehci_hcd===
 If your distribution (like Fedora 11) instead compiled the ehci_hcd support directly into the kernel, you cannot unload or blacklist it.

@@ Line 51: / Line 51: @@
   lspci|grep -i ehci
-On a ThinkPad T41 this returns
+On a ThinkPad {{T41}} this returns
 :1d.7 USB Controller: Intel Corporation 82801DB/DBM (ICH4/ICH4-M) USB2 EHCI Controller (rev 01)

@@ Line 36: / Line 36: @@
 This seems to be a hardware problem with the USB controller on Intel's chip or related electronics. Sending the laptop in for service may help.
-If the Linux kernel refuses to register the USB device, "modprobe -r ehci_hcd" may help. This disables USB 2.0 functionality for the session.
+If the Linux kernel refuses to register the USB device, you can try removing or disabling the ehci_hcd part. Doing this means that USB devices will run at USB 1.1 speeds, which is supported by pretty much every USB device for backwards compatibility. This is not a problem for USB Keyboards and Mice as they are typically USB 1.1 anyway, but for USB storage devices it can slow things down dramatically.
-Unloading ehci_hcd as per above confirmed to work on T41 running Ubuntu Edgy. Also worked on a T40 running Debian Lenny.
+Or alternatively to prevent the module from ever loading, add {{path|ehci_hcd}} to {{path|/etc/modprobe.d/blacklist.conf}} (or {{path|/etc/modprobe.d/blacklist}}). But note that adding it to the blacklist file might not be enough by itself as most distributions load the ehci_hcd module already during initrd, as such you might need to rebuild your initrd after adding it to the blacklist for it to have effect.
 == See Also ==
 [http://forums.cnet.com/5208-7586_102-0.html?forumID=68&threadID=151816 IBM X40 USB Problem] (fried USB on multiple {{X40}}s)

@@ Line 28: / Line 28: @@
 hub 4-0:1.0: unable to enumerate USB device on port 4<br />
 }}
-Flexing the right palmrest area up will temporarily make the USB 2.0 recognizable again. Tightening the screws on the bottom and front edge of the laptop may also the problem.
+Flexing the right palmrest area up will temporarily make the USB 2.0 recognizable again. Tightening the screws on the bottom and front edge of the laptop may also fix the problem.