Skip to contentSkip to conversation

USB extension (repeater) cable

DISCUSSION Udo van den Heuvel 4 participants 6 messages Jan 19, 2007 – Jan 21, 2007 USB

lore
Share & tools
lore
#0 lore raw

Hello,

I just tried my shiny new usb extension cable (repeater):

Jan 19 16:01:17 epia kernel: usb 5-1: new high speed USB device using
ehci_hcd and address 60
Jan 19 16:01:17 epia kernel: usb 5-1: configuration #1 chosen from 1 choice
Jan 19 16:01:17 epia kernel: hub 5-1:1.0: USB hub found
Jan 19 16:01:17 epia kernel: hub 5-1:1.0: 4 ports detected
Jan 19 16:01:18 epia kernel: hub 5-1:1.0: Cannot enable port 1.  Maybe
the USB cable is bad?
Jan 19 16:01:22 epia last message repeated 3 times
Jan 19 16:01:23 epia kernel: hub 5-1:1.0: Cannot enable port 2.  Maybe
the USB cable is bad?
Jan 19 16:01:26 epia last message repeated 3 times
Jan 19 16:01:27 epia kernel: hub 5-1:1.0: Cannot enable port 3.  Maybe
the USB cable is bad?
Jan 19 16:01:31 epia last message repeated 3 times

The second cable does the same.
Of course we have just one port on this hub...
Any ideas?

#1 lore raw
Quoted 19 lines · Udo van den Heuvel

Hello,

I just tried my shiny new usb extension cable (repeater):

Jan 19 16:01:17 epia kernel: usb 5-1: new high speed USB device using
ehci_hcd and address 60
Jan 19 16:01:17 epia kernel: usb 5-1: configuration #1 chosen from 1 choice
Jan 19 16:01:17 epia kernel: hub 5-1:1.0: USB hub found
Jan 19 16:01:17 epia kernel: hub 5-1:1.0: 4 ports detected
Jan 19 16:01:18 epia kernel: hub 5-1:1.0: Cannot enable port 1.  Maybe
the USB cable is bad?
Jan 19 16:01:22 epia last message repeated 3 times
Jan 19 16:01:23 epia kernel: hub 5-1:1.0: Cannot enable port 2.  Maybe
the USB cable is bad?
Jan 19 16:01:26 epia last message repeated 3 times
Jan 19 16:01:27 epia kernel: hub 5-1:1.0: Cannot enable port 3.  Maybe
the USB cable is bad?
Jan 19 16:01:31 epia last message repeated 3 times
Quoted 3 lines

The second cable does the same.
Of course we have just one port on this hub...
Any ideas?

Perhaps the kernel is not lying and this cable really is bad? :)

Your hardware can not handle this device, there really is nothing that the kernel can do about this.

USB extension cables are horrible things, and usually violate the USB spec and do not always work, as you are finding out. Sorry about that.

good luck,

greg k-h

#2 lore raw
Quoted 24 lines · Greg KH
Quoted 19 lines · Udo van den Heuvel

Hello,

I just tried my shiny new usb extension cable (repeater):

Jan 19 16:01:17 epia kernel: usb 5-1: new high speed USB device using
ehci_hcd and address 60
Jan 19 16:01:17 epia kernel: usb 5-1: configuration #1 chosen from 1 choice
Jan 19 16:01:17 epia kernel: hub 5-1:1.0: USB hub found
Jan 19 16:01:17 epia kernel: hub 5-1:1.0: 4 ports detected
Jan 19 16:01:18 epia kernel: hub 5-1:1.0: Cannot enable port 1.  Maybe
the USB cable is bad?
Jan 19 16:01:22 epia last message repeated 3 times
Jan 19 16:01:23 epia kernel: hub 5-1:1.0: Cannot enable port 2.  Maybe
the USB cable is bad?
Jan 19 16:01:26 epia last message repeated 3 times
Jan 19 16:01:27 epia kernel: hub 5-1:1.0: Cannot enable port 3.  Maybe
the USB cable is bad?
Jan 19 16:01:31 epia last message repeated 3 times
Quoted 3 lines

The second cable does the same.
Of course we have just one port on this hub...
Any ideas?

Quoted 8 lines

Perhaps the kernel is not lying and this cable really is bad? :)

Your hardware can not handle this device, there really is nothing that the kernel can do about this.

USB extension cables are horrible things, and usually violate the USB spec and do not always work, as you are finding out. Sorry about that.

Actually, what it looks like is even simpler. The extension cable contains a four-port hub chip (which is the most common commodity chip) and haven't bothered changing the descriptor to tell the computer only one port is actually active. So only one port can be activated, and the others are stubbed out in some evil way. In that case, it should be noisy but harmless.

-hpa

#3 lore raw
Quoted 20 lines · H. Peter Anvin
Quoted 19 lines · Greg KH
Quoted 18 lines · Udo van den Heuvel

I just tried my shiny new usb extension cable (repeater):

Jan 19 16:01:17 epia kernel: usb 5-1: new high speed USB device using
ehci_hcd and address 60
Jan 19 16:01:17 epia kernel: usb 5-1: configuration #1 chosen from 1
choice
Jan 19 16:01:17 epia kernel: hub 5-1:1.0: USB hub found
Jan 19 16:01:17 epia kernel: hub 5-1:1.0: 4 ports detected
Jan 19 16:01:18 epia kernel: hub 5-1:1.0: Cannot enable port 1.  Maybe
the USB cable is bad?
Jan 19 16:01:22 epia last message repeated 3 times
Jan 19 16:01:23 epia kernel: hub 5-1:1.0: Cannot enable port 2.  Maybe
the USB cable is bad?
Jan 19 16:01:26 epia last message repeated 3 times
Jan 19 16:01:27 epia kernel: hub 5-1:1.0: Cannot enable port 3.  Maybe
the USB cable is bad?
Jan 19 16:01:31 epia last message repeated 3 times

[...]

Quoted 6 lines

Actually, what it looks like is even simpler. The extension cable contains a four-port hub chip (which is the most common commodity chip) and haven't bothered changing the descriptor to tell the computer only one port is actually active. So only one port can be activated, and the others are stubbed out in some evil way. In that case, it should be noisy but harmless.

I will do some more testing then.
Is there a way to get rid of the messages?

#4 lore raw
Quoted 10 lines · Udo van den Heuvel
Quoted 7 lines

Actually, what it looks like is even simpler. The extension cable contains a four-port hub chip (which is the most common commodity chip) and haven't bothered changing the descriptor to tell the computer only one port is actually active. So only one port can be activated, and the others are stubbed out in some evil way. In that case, it should be noisy but harmless.

I will do some more testing then.
Is there a way to get rid of the messages?

No, but you don't have to care about them.

-hpa

#5 lore raw
In reply to Udo van den Heuvel
Quoted 31 lines · Udo van den Heuvel
Quoted 20 lines · H. Peter Anvin
Quoted 19 lines · Greg KH
Quoted 18 lines · Udo van den Heuvel

I just tried my shiny new usb extension cable (repeater):

Jan 19 16:01:17 epia kernel: usb 5-1: new high speed USB device using
ehci_hcd and address 60
Jan 19 16:01:17 epia kernel: usb 5-1: configuration #1 chosen from 1
choice
Jan 19 16:01:17 epia kernel: hub 5-1:1.0: USB hub found
Jan 19 16:01:17 epia kernel: hub 5-1:1.0: 4 ports detected
Jan 19 16:01:18 epia kernel: hub 5-1:1.0: Cannot enable port 1.  Maybe
the USB cable is bad?
Jan 19 16:01:22 epia last message repeated 3 times
Jan 19 16:01:23 epia kernel: hub 5-1:1.0: Cannot enable port 2.  Maybe
the USB cable is bad?
Jan 19 16:01:26 epia last message repeated 3 times
Jan 19 16:01:27 epia kernel: hub 5-1:1.0: Cannot enable port 3.  Maybe
the USB cable is bad?
Jan 19 16:01:31 epia last message repeated 3 times

[...]

Quoted 6 lines

Actually, what it looks like is even simpler. The extension cable contains a four-port hub chip (which is the most common commodity chip) and haven't bothered changing the descriptor to tell the computer only one port is actually active. So only one port can be activated, and the others are stubbed out in some evil way. In that case, it should be noisy but harmless.

Quoted 2 lines

I will do some more testing then.
Is there a way to get rid of the messages?

I am using the following patch (with 2.6.17) to shut up these messages with my repeater cable - found it on the linux-usb mailinglist some time ago when facing the same problem, but did not write down from who it is.

(Does not silence all log messages when usb debugging is enabled, but when it is disabled there is no endless log-stream anymore and the cable works)

I tried to fix the logging-change to the usb id, but the cable uses exactly the same chip and id as the two chips inside my 7port usb-hub.

drivers/usb/core/hub.c +2 -1
Index: linux/drivers/usb/core/hub.c
===================================================================
@@ -1496,7 +1496,8 @@
 
 		/* bomb out completely if something weird happened */
 		if ((portchange & USB_PORT_STAT_C_CONNECTION))
-			return -EINVAL;
+			//return -EINVAL;
+			return -ENOTCONN;
 
 		/* if we`ve finished resetting, then break out of the loop */
 		if (!(portstatus & USB_PORT_STAT_RESET) &&

c'ya
sven

Signature · 2 lines
The Internet treats censorship as a routing problem, and routes around it.
(John Gilmore on http://www.cygnus.com/~gnu/)