Hi,
We’ve attached a USB 3.0 hub from VIA Labs (VLI 威鋒電子股份有限公司) to an NVIDIA Jetson Orin. Whenever we connect a peripheral directly to the hub, it is detected but doesn’t establish a connection. We conducted an experiment using two USB drives: the first one connected directly to the hub was detected but not connected, while the second one connected to an intermediate hub was both detected and connected.
I know this seems complicated, this is the actual state:

Orin Nx → VIA Labs HUB → USB drive A: FAIL
Orin Nx → VIA Labs HUB → Intermediate HUB → USB drive B: SUCCESS

This is the lsusb -t command output:
`
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=tegra-xusb/4p, 10000M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 10000M
|__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/4p, 5000M
|__ Port 1: Dev 4, If 0, Class=Mass Storage, Driver=usb-storage, 5000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=tegra-xusb/4p, 480M
|__ Port 2: Dev 2, If 0, Class=Hub, Driver=hub/5p, 480M
|__ Port 1: Dev 6, If 0, Class=Mass Storage, Driver=usb-storage, 480M
|__ Port 2: Dev 4, If 0, Class=Hub, Driver=hub/4p, 480M
|__ Port 5: Dev 5, If 0, Class=, Driver=, 480M
`

This is dmesg:
`[ 1.577637] usbcore: registered new interface driver usbfs
[ 1.583134] usbcore: registered new interface driver hub
[ 1.588460] usbcore: registered new device driver usb
[ 4.316286] usbcore: registered new interface driver r8152
[ 4.321920] usbcore: registered new interface driver asix
[ 4.327474] usbcore: registered new interface driver ax88179_178a
[ 4.333738] usbcore: registered new interface driver cdc_ether
[ 4.339731] usbcore: registered new interface driver net1080
[ 4.345546] usbcore: registered new interface driver cdc_subset
[ 4.351631] usbcore: registered new interface driver zaurus
[ 4.357355] usbcore: registered new interface driver cdc_ncm
[ 4.363169] usbcore: registered new interface driver aqc111
[ 4.385712] tegra-xusb 3610000.xhci: Adding to iommu group 0
[ 4.392051] usbcore: registered new interface driver uas
[ 4.397530] usbcore: registered new interface driver usb-storage
[ 4.415689] usbcore: registered new interface driver xpad
[ 6.946574] usbcore: registered new interface driver usbhid
[ 6.952304] usbhid: USB HID core driver
[ 7.288681] usbcore: registered new interface driver snd-usb-audio
[ 8.292176] tegra-xusb 3610000.xhci: Firmware timestamp: 2021-12-01 05:27:10 UTC, Version: 80.03 release
[ 8.301925] tegra-xusb 3610000.xhci: xHCI Host Controller
[ 8.307492] tegra-xusb 3610000.xhci: new USB bus registered, assigned bus number 1
[ 8.316159] tegra-xusb 3610000.xhci: hcc params 0x0180ff05 hci version 0x120 quirks 0x0000000000050810
[ 8.325764] tegra-xusb 3610000.xhci: irq 222, io mem 0x03610000
[ 8.332217] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.10
[ 8.340717] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 8.348143] usb usb1: Product: xHCI Host Controller
[ 8.353148] usb usb1: Manufacturer: Linux 5.10.104-tegra xhci-hcd
[ 8.359404] usb usb1: SerialNumber: 3610000.xhci
[ 8.373170] tegra-xusb 3610000.xhci: xHCI Host Controller
[ 8.378722] tegra-xusb 3610000.xhci: new USB bus registered, assigned bus number 2
[ 8.386512] tegra-xusb 3610000.xhci: Host supports USB 3.1 Enhanced SuperSpeed
[ 8.394008] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.10
[ 8.402516] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 8.409927] usb usb2: Product: xHCI Host Controller
[ 8.414936] usb usb2: Manufacturer: Linux 5.10.104-tegra xhci-hcd
[ 8.421191] usb usb2: SerialNumber: 3610000.xhci
[ 8.634144] usb 1-2: new high-speed USB device number 2 using tegra-xusb
[ 8.792467] usb 1-2: New USB device found, idVendor=2109, idProduct=2822, bcdDevice= 0.30
[ 8.800891] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 8.808233] usb 1-2: Product: USB2.0 Hub
[ 8.813433] usb 1-2: Manufacturer: VIA Labs, Inc.
[ 8.922240] usb 2-1: new SuperSpeedPlus Gen 2 USB device number 2 using tegra-xusb
[ 8.957457] usb 2-1: New USB device found, idVendor=2109, idProduct=0822, bcdDevice= 0.30
[ 8.965898] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 8.973236] usb 2-1: Product: USB3.1 Hub
[ 8.978427] usb 2-1: Manufacturer: VIA Labs, Inc.
[ 9.550368] usb 1-2.1: new high-speed USB device number 3 using tegra-xusb
[ 14.722194] usb 1-2.1: device descriptor read/64, error -110
[ 18.251687] usb0: HOST MAC 12:c5:64:3c:20:d2
[ 18.251691] usb0: MAC 12:c5:64:3c:20:d3
[ 18.262625] l4tbr0: port 2(usb0) entered blocking state
[ 18.262638] l4tbr0: port 2(usb0) entered disabled state
[ 18.262773] device usb0 entered promiscuous mode
[ 24.958461] usb 2-1.2: new SuperSpeed Gen 1 USB device number 3 using tegra-xusb
[ 24.987100] usb 2-1.2: New USB device found, idVendor=05e3, idProduct=0620, bcdDevice=93.07
[ 24.987108] usb 2-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 24.987112] usb 2-1.2: Product: USB3.2 Hub
[ 24.987115] usb 2-1.2: Manufacturer: GenesysLogic
[ 25.114172] usb 1-2.2: new high-speed USB device number 4 using tegra-xusb
[ 25.268183] usb 1-2.2: New USB device found, idVendor=05e3, idProduct=0610, bcdDevice=93.07
[ 25.268192] usb 1-2.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 25.268196] usb 1-2.2: Product: USB2.1 Hub
[ 25.268199] usb 1-2.2: Manufacturer: GenesysLogic
[ 25.342805] usb 2-1.2.1: new SuperSpeed Gen 1 USB device number 4 using tegra-xusb
[ 25.365607] usb 2-1.2.1: LPM exit latency is zeroed, disabling LPM.
[ 25.369115] usb 2-1.2.1: New USB device found, idVendor=346d, idProduct=5678, bcdDevice= 2.00
[ 25.369122] usb 2-1.2.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 25.369126] usb 2-1.2.1: Product: Intenso Speed Line
[ 25.369129] usb 2-1.2.1: Manufacturer: Intenso
[ 25.369132] usb 2-1.2.1: SerialNumber: FC081A094C35E
[ 25.370496] usb-storage 2-1.2.1:1.0: USB Mass Storage device detected
[ 25.370824] scsi host0: usb-storage 2-1.2.1:1.0
[ 25.442157] usb 1-2.5: new high-speed USB device number 5 using tegra-xusb
[ 25.548301] usb 1-2.5: New USB device found, idVendor=2109, idProduct=8822, bcdDevice= 0.01
[ 25.548312] usb 1-2.5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 25.548317] usb 1-2.5: Product: USB Billboard Device
[ 25.548321] usb 1-2.5: Manufacturer: VIA Labs, Inc.
[ 25.548324] usb 1-2.5: SerialNumber: 0000000000000001
[ 25.830173] usb 1-2.1: new high-speed USB device number 6 using tegra-xusb
[ 27.283801] usb 1-2.1: New USB device found, idVendor=24a9, idProduct=205a, bcdDevice= 2.00
[ 27.283810] usb 1-2.1: New USB device strings: Mfr=2, Product=3, SerialNumber=4
[ 27.283812] usb 1-2.1: Product: Intenso Speed Line
[ 27.283814] usb 1-2.1: Manufacturer: Intenso
[ 27.283816] usb 1-2.1: SerialNumber: 46729111
[ 27.285322] usb-storage 1-2.1:1.0: USB Mass Storage device detected
[ 27.285789] scsi host1: usb-storage 1-2.1:1.0`

You can observe this error message
[ 14.722194] usb 1-2.1: device descriptor read/64, error -110

PS: It is not possible to access directly the Orin USB ports as all of them are connected to the VIA Labs HUB.

Appreciate your help,
Ahmed

Not sure what we can tell you, since you don't tell us the version/distro of Linux you're using. And I know you say you can't plug directly into the Orin, but until you actually do that for diagnostic purposes, there's nothing more that can be found out. Could be as simple as that hub doesn't have enough power, or the hub is faulty. Test it by plugging directly into the Orin.

Be aware that usb sockets are current limited. Is your usb hub independently powered?

If not, attaching 1 x 2.5" disk uses all the power of a usb-3.0 port. Do not attach 2 disks to the same hub without at least 1.5A power supply. 3.5" drives need their own power supply & case. And 5.1V supply or suchlike for your new PSU is better than 5.0V as you'll lose power on the way to where it's used. Trust me, I've used that in fault finding.

The logs look pretty meaningless. My interpretation is that you have a couple of spinning rust drives. Spin-up on the motors takes 5x rated power initially, and ≤2x rated power for a few seconds. So your PC finds the drive, spins it up, loses the drive again... then finds it again when the dust settles and repeats the process.

Thank you for your fast responses!

Regarding the operating system details, the system runs on Ubuntu 20.04 with the aarch64 architecture.

Upon reviewing the datasheet of the VIA Labs Hub, it appears to possess ample power capabilities. It can provide up to 10A.

You can check the hardware schematics here https://forums.developer.nvidia.com/...tom-dtb/229398.


I appreciate your help!

Ahmed

I ask again: A simple yes or no will suffice. I looked at the drawing. No power supply components were shown. And at issue is not power available, but voltage dropped while the power gets out to the extremities.

Are the disks 2.5" or 3.5"? That matters because external 3.5" disks need their own independent power supply. The 3.5" disks want a 12V line also, which the external case psu supplies. Straight answer please.

If you plug each disk into a usb3 port, does it behave itself? Have you fsck'd the disks recently? Why not do it when you're testing them individually.

If the disks work, both the disk and the port are OK. If you put a hub in and things go AWOL, there's your answer. How many usb devices have you connected anyhow?

1 members found this post helpful.

No thank you...we're not going to chase down schematics and read data sheets for a device. You were asked simply if the powered hub was plugged in or not...you did not answer. And you first said it was a VIA Labs hub, and now you post a link to the nVidia developer site????

And you were also given a suggestion of plugging whatever device you have directly into the Orin for troubleshooting purposes...did you do that??? Until you start eliminating things and answering questions, there isn't going to be much we can help with.

Hello again,

Sorry for my inappropriate response, the problem is annoying and not repeatable.
What I meant about USB drive is just a simple USB stick (not 2.5" or 3.5" disk).

The HUB is not independently powered, it shares the power supply with other components.

So, I conducted an experiment with two USB sticks (not disks). Please note that I tested them with my laptop and they work perfectly.
First, I just inserted one USB stick, this is the `dmesg` that I got:

`
[73109.199359] usb 2-1.2: USB disconnect, device number 3
[73113.132300] usb 2-1.2: new SuperSpeed Gen 1 USB device number 4 using tegra-xusb
[73113.158795] usb 2-1.2: New USB device found, idVendor=24a9, idProduct=205a, bcdDevice= 1.10
[73113.158807] usb 2-1.2: New USB device strings: Mfr=2, Product=3, SerialNumber=4
[73113.158812] usb 2-1.2: Product: Intenso Speed Line
[73113.158815] usb 2-1.2: Manufacturer: Intenso
[73113.158817] usb 2-1.2: SerialNumber: 46729111
[73113.162880] usb-storage 2-1.2:1.0: USB Mass Storage device detected
[73113.163109] scsi host0: usb-storage 2-1.2:1.0
[73114.189353] scsi 0:0:0:0: Direct-Access Intenso Speed Line PQ: 0 ANSI: 6
[73114.200032] sd 0:0:0:0: [sda] 122880000 512-byte logical blocks: (62.9 GB/58.6 GiB)
[73114.208182] sd 0:0:0:0: [sda] Write Protect is off
[73114.213202] sd 0:0:0:0: [sda] Mode Sense: 23 00 00 00
[73114.213401] sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[73114.273589] sd 0:0:0:0: [sda] Attached SCSI removable disk
`

PS: I got just one partition (sda1).

Secondly, I removed the first USB stick and connected the 2nd one, this is the `dmesg` I got:
`
[74536.635083] usb 1-2.4: new high-speed USB device number 5 using tegra-xusb
[74536.788275] usb 1-2.4: New USB device found, idVendor=abcd, idProduct=1234, bcdDevice= 1.00
[74536.788286] usb 1-2.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[74536.788292] usb 1-2.4: Product: UDisk
[74536.788295] usb 1-2.4: Manufacturer: General
[74536.788298] usb 1-2.4: SerialNumber: Љ
[74536.789804] usb-storage 1-2.4:1.0: USB Mass Storage device detected
[74536.790071] scsi host1: usb-storage 1-2.4:1.0
[74537.812796] scsi 1:0:0:0: Direct-Access General UDisk 5.00 PQ: 0 ANSI: 2
[74537.821999] sd 1:0:0:0: [sdb] 985088 512-byte logical blocks: (504 MB/481 MiB)
[74537.829698] sd 1:0:0:0: [sdb] Write Protect is on
[74537.834570] sd 1:0:0:0: [sdb] Mode Sense: 0b 00 80 08
[74537.834756] sd 1:0:0:0: [sdb] No Caching mode page found
[74537.840258] sd 1:0:0:0: [sdb] Assuming drive cache: write through
[74537.868523] sdb:
[74537.869660] sd 1:0:0:0: [sdb] Attached SCSI removable disk
`

I cannot access this device.

This is `lsusb -t -v` command output just in case
`/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=tegra-xusb/4p, 10000M
ID 1d6b:0003 Linux Foundation 3.0 root hub
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 10000M
ID 2109:0822 VIA Labs, Inc.
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=tegra-xusb/4p, 480M
ID 1d6b:0002 Linux Foundation 2.0 root hub
|__ Port 2: Dev 2, If 0, Class=Hub, Driver=hub/5p, 480M
ID 2109:2822 VIA Labs, Inc.
|__ Port 4: Dev 5, If 0, Class=Mass Storage, Driver=usb-storage, 480M
ID abcd:1234 Unknown
|__ Port 5: Dev 3, If 0, Class=, Driver=, 480M
ID 2109:8822 VIA Labs, Inc.`


Thank you!

The only oddity I see there is that things usually output a size, and a partition list if there's a partition table like this one in my dmesg snippet In your dmesg extracts, disk sda is 64GB and appears unformatted. sdb is tiny, to judge by the size. It's years since anything that small was made. But you say they work perfectly. So the question becomes: What exactly were you plugging them into?

I'd like to compare the 'dmesg |tail' output from the usb disks

1. inserted into the laptop with no hub in sight.
2. Inserted into the hub.

I'll also mention that I shudder to see Via LABS on anything. They made a dreadful reputation, folded and were bought over in the 2000s. The name is a liability, not an asset. Seeing a usb.id of abcd:1234 is underwhelming. It's obviously a placeholder for a real usb.id. They never bothered to fill it in! I'm also sceptical of 2822 & 8822 and speculate that 2822 is the correct version because it's continuing their range of hub numbers. Brace yourself for similar hardware performance.

If putting the hub in the way interferes with disk performance, the hub is the problem. It may be non-standard, knowing Via.

1 members found this post helpful.