You are not logged in.

Pages: 1

#1 2019-10-21 15:26:01

ezacaria
Member
Registered: 2007-12-10
Posts: 113

USB 3.1 hub not working with extension cable

I bought one StarTech USB 3.1 bus-powered hub to extend my PCIe 3.1 controller.

When I plug the hub straight to the card, everything seems to be working normally. The problem starts when I use a 1-meter USB-C extension cable to be able to put the hub on my desk (the hub's cable is only 25cm long).

The cable is also new, and I trying to decide if there is any workaround to the problem, or if I should get another one.

The extension cable is a Belker CSC-TCE1 1-m cable. The packaging says that this should work as a "USB 3.1 Gen1 Type C Extension Cable" and I thought this could do to plug the hub.

The hub itself is recognised without problems when using the extension cable. The output of dmesg shows the same as when plugged directly to the USB PCIe card:

[Mon Oct 21 16:44:09 2019] usb 2-2: new high-speed USB device number 5 using xhci_hcd
[Mon Oct 21 16:44:09 2019] usb 2-2: New USB device found, idVendor=2109, idProduct=2820, bcdDevice= b.a3
[Mon Oct 21 16:44:09 2019] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[Mon Oct 21 16:44:09 2019] usb 2-2: Product: USB2.0 Hub
[Mon Oct 21 16:44:09 2019] usb 2-2: Manufacturer: VIA Labs, Inc.
[Mon Oct 21 16:44:09 2019] hub 2-2:1.0: USB hub found
[Mon Oct 21 16:44:09 2019] hub 2-2:1.0: 4 ports detected
[Mon Oct 21 16:44:09 2019] usb 3-2: new SuperSpeed Gen 1 USB device number 10 using xhci_hcd
[Mon Oct 21 16:44:09 2019] usb 3-2: New USB device found, idVendor=2109, idProduct=8820, bcdDevice= b.a3
[Mon Oct 21 16:44:09 2019] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[Mon Oct 21 16:44:09 2019] usb 3-2: Product: USB3.1 Hub
[Mon Oct 21 16:44:09 2019] usb 3-2: Manufacturer: VIA Labs, Inc.
[Mon Oct 21 16:44:09 2019] hub 3-2:1.0: USB hub found
[Mon Oct 21 16:44:09 2019] hub 3-2:1.0: 4 ports detected

But unlike the case of pluggin the hub to the PCIe card, whenever I use the extension cable there is no transfer to any USB drive connected to the hub.

When connected via the extension cable, dmesg shows:

[Mon Oct 21 16:46:12 2019] sd 11:0:0:0: [sdi] tag#0 data cmplt err -71 uas-tag 1 inflight: CMD 
[Mon Oct 21 16:46:12 2019] sd 11:0:0:0: [sdi] tag#0 CDB: Write(10) 2a 00 09 a3 ef 80 00 01 80 00
[Mon Oct 21 16:46:12 2019] xhci_hcd 0000:07:00.0: WARN Event TRB for slot 14 ep 3 with no TDs queued?
[Mon Oct 21 16:46:43 2019] sd 11:0:0:0: [sdi] tag#5 uas_eh_abort_handler 0 uas-tag 6 inflight: CMD OUT 
[Mon Oct 21 16:46:43 2019] sd 11:0:0:0: [sdi] tag#5 CDB: Write(10) 2a 00 0b 22 e8 68 00 04 00 00
[Mon Oct 21 16:46:43 2019] xhci_hcd 0000:07:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
[Mon Oct 21 16:46:43 2019] sd 11:0:0:0: [sdi] tag#4 uas_eh_abort_handler 0 uas-tag 5 inflight: CMD OUT 
[Mon Oct 21 16:46:43 2019] sd 11:0:0:0: [sdi] tag#4 CDB: Write(10) 2a 00 0b 22 e4 68 00 04 00 00
...

I even plugged the hub's cable rotated to the extension (as in the instructions for USB2 devices), but there is no difference.

Did I actually miss something and bought the wrong cable type? Could anyone suggest a good extension (1m) cable for USB 3.1 (10gbps) for the purpose of transferring data to/from disk enclosures?
Or is 1-m+25cm (from the hub's cable) too much for the 10gbps link?

I just updated the system today, the kernel is "5.3.7-arch1-1-ARCH"

Thanks!

Offline

#2 2019-10-24 12:10:49

ezacaria
Member
Registered: 2007-12-10
Posts: 113

Re: USB 3.1 hub not working with extension cable

I made some further diagnostics:

Plugging the hub directly to the PCIe card, I can use USB disk drives via my existing, old, 1.5m USB 3.0 extension cable without problems. However, this strategy would mean having more of those extension cables (one per hub port) and is a no-go, since it would get quite messy.

Then, I can plug the new cable (CSC-TCE1) to the PCIe card, with the USB drive attached to the far end. Data transfer works fine.

Thus, I find it difficult to understand that the hub will not do data transfer, when there is only a single drive attached to it (the hub being connected to the CSC-TCE1 cable). So far, both cable and hub work individually, but not together sad

Anyways, I will try next to use a reduced speed (USB 3.1 gen 1) cable to connect the hub.

Offline

#3 2019-10-25 10:53:05

Lone_Wolf
Administrator
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 15,102

Re: USB 3.1 hub not working with extension cable

to extend my PCIe 3.1 controller.

When I plug the hub straight to the card,

Are you using ports from an PCIe extension card or from your motherboard ?
Please post brand & model and type of them.
lspci -kvv , lsusb -tv could also be useful.

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

Offline

#4 2019-10-25 12:00:11

ezacaria
Member
Registered: 2007-12-10
Posts: 113

Re: USB 3.1 hub not working with extension cable

Yes, I have this PCIe USB card, which I would like to extend in terms of port number and availability (hence the hub plus the extension cable).

The motherboard is an ASUS RAMPAGE IV EXTREME, BIOS version 4701 (according to hwinfo).
The card is an Inateck 2-port PCIe card (I do not think I ever had a model for the card itself), it was supposed to be 3.1 gen 2 (up to 10gbps) compatible.

Here's what lspci says about the USB card, the USB chipset being ASM1142:

07:00.0 USB controller: ASMedia Technology Inc. ASM1142 USB 3.1 Host Controller (prog-if 30 [XHCI])
	Subsystem: ASMedia Technology Inc. ASM1142 USB 3.1 Host Controller
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 41
	Region 0: Memory at fb800000 (64-bit, non-prefetchable) [size=32K]
	Capabilities: [50] MSI: Enable- Count=1/8 Maskable- 64bit+
		Address: 0000000000000000  Data: 0000
	Capabilities: [68] MSI-X: Enable+ Count=8 Masked-
		Vector table: BAR=0 offset=00002000
		PBA: BAR=0 offset=00002080
	Capabilities: [78] Power Management version 3
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=55mA PME(D0-,D1-,D2-,D3hot+,D3cold+)
		Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [80] Express (v2) Endpoint, MSI 00
		DevCap:	MaxPayload 512 bytes, PhantFunc 0, Latency L0s <64ns, L1 <2us
			ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset- SlotPowerLimit 25.000W
		DevCtl:	CorrErr- NonFatalErr- FatalErr- UnsupReq-
			RlxdOrd- ExtTag+ PhantFunc- AuxPwr- NoSnoop+
			MaxPayload 256 bytes, MaxReadReq 512 bytes
		DevSta:	CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr+ TransPend-
		LnkCap:	Port #1, Speed 5GT/s, Width x2, ASPM L1, Exit Latency L1 unlimited
			ClockPM- Surprise- LLActRep- BwNot- ASPMOptComp+
		LnkCtl:	ASPM Disabled; RCB 64 bytes Disabled- CommClk+
			ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
		LnkSta:	Speed 5GT/s (ok), Width x2 (ok)
			TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
		DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR+, OBFF Not Supported
			 AtomicOpsCap: 32bit- 64bit- 128bitCAS-
		DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled
			 AtomicOpsCtl: ReqEn-
		LnkCtl2: Target Link Speed: 5GT/s, EnterCompliance- SpeedDis-
			 Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
			 Compliance De-emphasis: -6dB
		LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete-, EqualizationPhase1-
			 EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest-
	Capabilities: [100 v1] Virtual Channel
		Caps:	LPEVC=0 RefClk=100ns PATEntryBits=1
		Arb:	Fixed- WRR32- WRR64- WRR128-
		Ctrl:	ArbSelect=Fixed
		Status:	InProgress-
		VC0:	Caps:	PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
			Arb:	Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256-
			Ctrl:	Enable+ ID=0 ArbSelect=Fixed TC/VC=01
			Status:	NegoPending- InProgress-
	Capabilities: [200 v1] Advanced Error Reporting
		UESta:	DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
		UEMsk:	DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
		UESvrt:	DLP+ SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP+ ECRC- UnsupReq- ACSViol-
		CESta:	RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr-
		CEMsk:	RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr+
		AERCap:	First Error Pointer: 00, ECRCGenCap- ECRCGenEn- ECRCChkCap- ECRCChkEn-
			MultHdrRecCap- MultHdrRecEn- TLPPfxPres- HdrLogCap-
		HeaderLog: 00000000 00000000 00000000 00000000
	Capabilities: [280 v1] Secondary PCI Express <?>
	Capabilities: [300 v1] Latency Tolerance Reporting
		Max snoop latency: 0ns
		Max no snoop latency: 0ns
	Kernel driver in use: xhci_hcd
	Kernel modules: xhci_pci

And when the hub is plugged straight to the card, with one USB 3.0 stick attached, lsusb tells:

/:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 10000M
    ID 1d6b:0003 Linux Foundation 3.0 root hub
    |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/4p, 5000M
        ID 2109:8820 VIA Labs, Inc. 
        |__ Port 4: Dev 4, If 0, Class=Mass Storage, Driver=usb-storage, 5000M
            ID 8564:1000 Transcend Information, Inc. JetFlash
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M
    ID 1d6b:0002 Linux Foundation 2.0 root hub
    |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/4p, 480M
        ID 2109:2820 VIA Labs, Inc.

And same thing when the hub plus the stick are attached to the extension cable.

Thanks!

Offline

#5 2019-10-25 13:16:49

ezacaria
Member
Registered: 2007-12-10
Posts: 113

Re: USB 3.1 hub not working with extension cable

Maybe I missed the point, so I checked the output of those commands again. But I could not see anything related to error counters or anything that could indicate what went wrong when connected via the extension cable and trying to write data to the stick.

Offline

#6 2019-10-26 14:42:57

ezacaria
Member
Registered: 2007-12-10
Posts: 113

Re: USB 3.1 hub not working with extension cable

I tried a different cable. This is a DeLock 85533 ("DeLock USB3.1 Gen1 USB-C extension").

The M2+USB enclosure works when plugged on the hub via the new extension cable, but the USB stick went to some device resets until it finally transfered data. While I am not jumping out of joy with the general impression of the whole setup, it may be that this can be useful once I learn what works and what does not tongue

If I find the time I will try a different hub, which is from Inateck (same company that sells the PCIe USB card) - maybe that combination will work better.

Offline

#7 2019-10-27 10:20:11

ezacaria
Member
Registered: 2007-12-10
Posts: 113

Re: USB 3.1 hub not working with extension cable

The Inateck Hub indeed seems to work better.

Summarising, the HW is as follows:

  1. StarTech hub: idVendor=2109, idProduct=8820, bcdDevice= b.a3. This is shown as "Product: USB3.1 Hub"

  2. Inatech hub: idVendor=2109, idProduct=0817, bcdDevice= 3.84. This is shown as "Product: USB3.0 Hub"

  3. USB-C extension cable 1 (Belker): CSC-TCE1

  4. USB-C extension cable 2 (DeLock): 85533

With following preliminary results:

Extension cable  |USB-C Hub  |Limited-testing result                  |Obs
--------------------------------------------------------------------------------------------------------------------------------------------------------
Belker           |StarTech   |No data transfer                        |Hub is recognised but data transfer fails
DeLock           |StarTech   |Data transfer OK, some hiccups overall  |Mostly issues with a USB 3.0 stick taking a while from plugging to working
DeLock           |Inateck    |Data transfer OK, some hiccups          |Problems may relate to the USB 2.0 part. Usage with a windows10 laptop seems OK
Belker           |Inateck    |Data transfer OK                        |So far, this seems a usable, working combination

For my purposes, the Inateck hub+Belker tuple cable works "well enough" for everyday situations, I get read speeds around 3 to 3.4 gbps and writing not too far below (depending on the device). If I really should need to push close to 5gbps, then I can always connect the enclosure directly on the other port, or disconnect the hub and plug the disk directly to the extension cable. In the end, it seems that I will leave the DeLock+StarTech hub for those rare cases when I need them on a w10 laptop.

By the way, it is a pity that our BBCode does not support the table tag sad

Offline

Pages: 1

Board footer

Powered by FluxBB