AMD USB 4 Weirdness, most devices only seen as USB 2

Support
, ,
1

The only device I own which is detected by xhci as USB 3 is an Intenso USB Stick with USB 3.1 Gen 1x1.
All other devices, including my phone, with USB 3.2 Gen 2 and USB-C to DisplayPort Adapters are only shown and attached as 480Mbps USB 2 devices.
Here is my system info:
inxi -Fazyv7:

System:
  Kernel: 6.2.9-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 12.2.1
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.2-x86_64
    root=UUID=9f41ad32-4a25-42a3-8c3b-edc54f2088c7 rw pci=realloc quiet
    apparmor=1 security=apparmor udev.log_priority=3
  Desktop: KDE Plasma v: 5.27.3 tk: Qt v: 5.15.8 wm: kwin_wayland vt: 2
    dm: SDDM Distro: Manjaro Linux base: Arch Linux
Machine:
  Type: Laptop System: ASUSTeK product: ROG Strix G713RS_G713RS v: 1.0
    serial: <superuser required>
  Mobo: ASUSTeK model: G713RS v: 1.0 serial: <superuser required>
    UEFI: American Megatrends LLC. v: G713RS.327 date: 02/16/2023
Battery:
  ID-1: BAT0 charge: 84.5 Wh (100.0%) condition: 84.5/90.0 Wh (93.9%)
    volts: 17.2 min: 15.9 model: AS3GWAF3KC GA50358 type: Unknown
    serial: <filter> status: full
Memory:
  RAM: total: 30.62 GiB used: 4.11 GiB (13.4%)
  RAM Report: permissions: Unable to run dmidecode. Root privileges required.
CPU:
  Info: model: AMD Ryzen 9 6900HX with Radeon Graphics bits: 64 type: MT MCP
    arch: Zen 3+ gen: 4 level: v3 note: check built: 2022 process: TSMC n6 (7nm)
    family: 0x19 (25) model-id: 0x44 (68) stepping: 1 microcode: 0xA404102
  Topology: cpus: 1x cores: 8 tpc: 2 threads: 16 smt: enabled cache:
    L1: 512 KiB desc: d-8x32 KiB; i-8x32 KiB L2: 4 MiB desc: 8x512 KiB L3: 16 MiB
    desc: 1x16 MiB
  Speed (MHz): avg: 2118 high: 3300 min/max: 1600/4934 boost: enabled
    scaling: driver: acpi-cpufreq governor: schedutil cores: 1: 1600 2: 3300
    3: 1600 4: 1600 5: 1600 6: 3300 7: 1397 8: 1600 9: 1600 10: 1600 11: 1600
    12: 1600 13: 3300 14: 3300 15: 1600 16: 3300 bogomips: 105440
  Flags: 3dnowprefetch abm adx aes aperfmperf apic arat avic avx avx2 bmi1
    bmi2 bpext cat_l3 cdp_l3 clflush clflushopt clwb clzero cmov cmp_legacy
    constant_tsc cpb cppc cpuid cqm cqm_llc cqm_mbm_local cqm_mbm_total
    cqm_occup_llc cr8_legacy cx16 cx8 de decodeassists erms extapic
    extd_apicid f16c flushbyasid fma fpu fsgsbase fsrm fxsr fxsr_opt ht
    hw_pstate ibpb ibrs ibs invpcid irperf lahf_lm lbrv lm mba mca mce
    misalignsse mmx mmxext monitor movbe msr mtrr mwaitx nonstop_tsc nopl npt
    nrip_save nx ospke osvw overflow_recov pae pat pausefilter pclmulqdq
    pdpe1gb perfctr_core perfctr_llc perfctr_nb pfthreshold pge pku pni popcnt
    pse pse36 rapl rdpid rdpru rdrand rdseed rdt_a rdtscp rep_good sep sha_ni
    skinit smap smca smep ssbd sse sse2 sse4_1 sse4_2 sse4a ssse3 stibp succor
    svm svm_lock syscall tce topoext tsc tsc_scale umip v_spec_ctrl
    v_vmsave_vmload vaes vgif vmcb_clean vme vmmcall vpclmulqdq wbnoinvd wdt
    x2apic xgetbv1 xsave xsavec xsaveerptr xsaveopt xsaves
  Vulnerabilities:
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: retbleed status: Not affected
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
    prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
    sanitization
  Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, IBRS_FW,
    STIBP: always-on, RSB filling, PBRSB-eIBRS: Not affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: NVIDIA GA104M [GeForce RTX 3080 Mobile / Max-Q 8GB/16GB]
    vendor: ASUSTeK driver: nvidia v: 530.41.03 alternate: nouveau,nvidia_drm
    non-free: 530.xx+ status: current (as of 2023-03) arch: Ampere code: GAxxx
    process: TSMC n7 (7nm) built: 2020-22 pcie: gen: 1 speed: 2.5 GT/s lanes: 8
    link-max: gen: 4 speed: 16 GT/s lanes: 16 ports: active: none off: HDMI-A-1
    empty: DP-6,eDP-2 bus-ID: 01:00.0 chip-ID: 10de:249c class-ID: 0300
  Device-2: AMD Rembrandt [Radeon 680M] vendor: ASUSTeK driver: amdgpu
    v: kernel arch: RDNA-2 code: Navi-2x process: TSMC n7 (7nm) built: 2020-22
    pcie: gen: 4 speed: 16 GT/s lanes: 16 ports: active: eDP-1 empty: DP-1,
    DP-2, DP-3, DP-4, DP-5 bus-ID: 06:00.0 chip-ID: 1002:1681 class-ID: 0300
    temp: 47.0 C
  Display: wayland server: X.org v: 1.21.1.8 with: Xwayland v: 23.1.1
    compositor: kwin_wayland driver: X: loaded: amdgpu,nvidia
    unloaded: modesetting,nouveau alternate: fbdev,nv,vesa dri: radeonsi
    gpu: nvidia,amdgpu d-rect: 4480x1440 display-ID: 0
  Monitor-1: HDMI-A-1 pos: right res: 1920x1080 size: N/A modes: N/A
  Monitor-2: eDP-1 pos: primary,left res: 2560x1440 size: N/A modes: N/A
  API: OpenGL v: 4.6 Mesa 23.0.1 renderer: AMD Radeon Graphics (rembrandt
    LLVM 15.0.7 DRM 3.49 6.2.9-1-MANJARO) direct-render: Yes
Audio:
  Device-1: NVIDIA GA104 High Definition Audio vendor: ASUSTeK
    driver: snd_hda_intel v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 8
    link-max: gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 01:00.1
    chip-ID: 10de:228b class-ID: 0403
  Device-2: AMD ACP/ACP3X/ACP6x Audio Coprocessor vendor: ASUSTeK
    driver: snd_pci_acp6x v: kernel alternate: snd_pci_acp3x, snd_rn_pci_acp3x,
    snd_pci_acp5x, snd_acp_pci, snd_rpl_pci_acp6x, snd_pci_ps,
    snd_sof_amd_renoir, snd_sof_amd_rembrandt pcie: gen: 4 speed: 16 GT/s
    lanes: 16 bus-ID: 06:00.5 chip-ID: 1022:15e2 class-ID: 0480
  Device-3: AMD Family 17h/19h HD Audio vendor: ASUSTeK driver: snd_hda_intel
    v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 06:00.6
    chip-ID: 1022:15e3 class-ID: 0403
  API: ALSA v: k6.2.9-1-MANJARO status: kernel-api with: aoss
    type: oss-emulator tools: alsamixer,amixer
  Server-1: JACK v: 1.9.22 status: off tools: N/A
  Server-2: PipeWire v: 0.3.67 status: off with: pipewire-media-session
    status: active tools: pw-cli
  Server-3: PulseAudio v: 16.1 status: active with: pulseaudio-jack
    type: module tools: pacat,pactl
Network:
  Device-1: MEDIATEK MT7922 802.11ax PCI Express Wireless Network Adapter
    vendor: Foxconn driver: mt7921e v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 1
    bus-ID: 03:00.0 chip-ID: 14c3:0616 class-ID: 0280
  IF: wlo1 state: up mac: <filter>
  IP v4: <filter> type: dynamic noprefixroute scope: global
    broadcast: <filter>
  IP v6: <filter> type: dynamic noprefixroute scope: global
  IP v6: <filter> type: noprefixroute scope: link
  Device-2: Realtek RTL8125 2.5GbE vendor: ASUSTeK driver: r8169 v: kernel
    pcie: gen: 2 speed: 5 GT/s lanes: 1 port: e000 bus-ID: 04:00.0
    chip-ID: 10ec:8125 class-ID: 0200
  IF: enp4s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  IP v4: <filter> type: dynamic noprefixroute scope: global
    broadcast: <filter>
  IP v6: <filter> type: dynamic noprefixroute scope: global
  IP v6: <filter> type: noprefixroute scope: link
  WAN IP: <filter>
Bluetooth:
  Message: No bluetooth data found.
Logical:
  Message: No logical block device data found.
RAID:
  Message: No RAID data found.
Drives:
  Local Storage: total: 2.81 TiB used: 1.37 TiB (48.8%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Lexar model: SSD NM710 2TB
    size: 1.82 TiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
    lanes: 4 type: SSD serial: <filter> rev: 8212 temp: 33.9 C scheme: GPT
  ID-2: /dev/nvme1n1 maj-min: 259:7 vendor: Micron model: 2450 MTFDKBA1T0TFK
    size: 953.87 GiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
    lanes: 4 type: SSD serial: <filter> rev: V5MA010 temp: 28.9 C scheme: GPT
  ID-3: /dev/sda maj-min: 8:0 type: USB vendor: Intenso model: Ultra Line
    size: 58.59 GiB block-size: physical: 512 B logical: 512 B type: N/A
    serial: <filter> scheme: MBR
  SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
  Message: No optical or floppy data found.
Partition:
  ID-1: / raw-size: 953.57 GiB size: 937.53 GiB (98.32%)
    used: 724.59 GiB (77.3%) fs: ext4 dev: /dev/nvme1n1p2 maj-min: 259:9
    label: N/A uuid: 9f41ad32-4a25-42a3-8c3b-edc54f2088c7
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
    used: 292 KiB (0.1%) fs: vfat dev: /dev/nvme1n1p1 maj-min: 259:8
    label: NO_LABEL uuid: BE37-2D25
  ID-3: /data raw-size: 1.69 TiB size: 1.67 TiB (98.37%)
    used: 677.52 GiB (39.7%) fs: ext4 dev: /dev/nvme0n1p6 maj-min: 259:6
    label: M\xc3\xb6hrchen uuid: ba7e380f-e90f-44b1-8ab2-b13ca0fc5f28
Swap:
  Alert: No swap data was found.
Unmounted:
  ID-1: /dev/nvme0n1p1 maj-min: 259:1 size: 100 MiB fs: vfat label: N/A
    uuid: 9E53-9D17
  ID-2: /dev/nvme0n1p2 maj-min: 259:2 size: 16 MiB fs: <superuser required>
    label: N/A uuid: N/A
  ID-3: /dev/nvme0n1p3 maj-min: 259:3 size: 126.65 GiB fs: ntfs label: N/A
    uuid: 1A1E540A1E53DD77
  ID-4: /dev/nvme0n1p4 maj-min: 259:4 size: 660 MiB fs: ntfs label: N/A
    uuid: DE8089C88089A81B
  ID-5: /dev/nvme0n1p5 maj-min: 259:5 size: 604 MiB fs: <superuser required>
    label: N/A uuid: N/A
  ID-6: /dev/sda1 maj-min: 8:1 size: 58.59 GiB fs: exfat label: INTENSO
    uuid: 0010-4800
USB:
  Hub-1: 1-0:1 info: Hi-speed hub with single TT ports: 4 rev: 2.0
    speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900
  Device-1: 1-3:2 info: ASUSTek N-KEY Device type: Keyboard
    driver: asus,usbhid interfaces: 1 rev: 2.0 speed: 12 Mb/s power: 100mA
    chip-ID: 0b05:19b6 class-ID: 0301
  Hub-2: 2-0:1 info: Super-speed hub ports: 2 rev: 3.1 speed: 10 Gb/s
    chip-ID: 1d6b:0003 class-ID: 0900
  Hub-3: 3-0:1 info: Hi-speed hub with single TT ports: 3 rev: 2.0
    speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900
  Device-1: 3-2:2 info: HP Logitech M-UAL-96 Mouse type: Mouse
    driver: hid-generic,usbhid interfaces: 1 rev: 2.0 speed: 1.5 Mb/s power: 98mA
    chip-ID: 03f0:2c24 class-ID: 0301
  Hub-4: 4-0:1 info: Hi-speed hub with single TT ports: 1 rev: 2.0
    speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900
  Hub-5: 5-0:1 info: Hi-speed hub with single TT ports: 1 rev: 2.0
    speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900
  Device-1: 5-1:2 info: Google Nexus/Pixel Device (MTP + debug)
    type: Still Imaging driver: N/A interfaces: 2 rev: 2.1 speed: 480 Mb/s
    power: 500mA chip-ID: 18d1:4ee2 class-ID: 0601 serial: <filter>
  Hub-6: 6-0:1 info: Hi-speed hub with single TT ports: 1 rev: 2.0
    speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900
  Hub-7: 7-0:1 info: Super-speed hub ports: 2 rev: 3.1 speed: 10 Gb/s
    chip-ID: 1d6b:0003 class-ID: 0900
  Device-1: 7-1:2 info: IS918 Intenso Ultra Line type: Mass Storage
    driver: usb-storage interfaces: 1 rev: 3.2 speed: 5 Gb/s power: 304mA
    chip-ID: 24a9:205a class-ID: 0806 serial: <filter>
  Hub-8: 8-0:1 info: Super-speed hub ports: 1 rev: 3.1 speed: 10 Gb/s
    chip-ID: 1d6b:0003 class-ID: 0900
  Hub-9: 9-0:1 info: Linux Foundation 3.0 root hub ports: N/A rev: 3.0
    speed: 5 Gb/s chip-ID: 1d6b:0003 class-ID: 0900
  Hub-10: 10-0:1 info: Super-speed hub ports: 1 rev: 3.1 speed: 10 Gb/s
    chip-ID: 1d6b:0003 class-ID: 0900
Sensors:
  System Temperatures: cpu: 52.2 C mobo: N/A gpu: amdgpu temp: 48.0 C
  Fan Speeds (RPM): cpu: 0
Info:
  Processes: 408 Uptime: 13m wakeups: 5 Init: systemd v: 252 default: graphical
  tool: systemctl Compilers: gcc: 12.2.1 alt: 11 clang: 15.0.7 Packages:
  pm: pacman pkgs: 1922 libs: 504 tools: pamac,yay pm: flatpak pkgs: 0
  Shell: Zsh v: 5.9 default: Bash v: 5.1.16 running-in: konsole inxi: 3.3.26
2

can you report

sudo lsusb -vt

have you try with this option “iommu=pt” ?

3

lsusb -vt

/:  Bus 10.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 10000M
    ID 1d6b:0003 Linux Foundation 3.0 root hub
/:  Bus 09.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/0p, 5000M
    ID 1d6b:0003 Linux Foundation 3.0 root hub
/:  Bus 08.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 10000M
    ID 1d6b:0003 Linux Foundation 3.0 root hub
/:  Bus 07.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 10000M
    ID 1d6b:0003 Linux Foundation 3.0 root hub
/:  Bus 06.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 10000M
    ID 1d6b:0003 Linux Foundation 3.0 root hub
/:  Bus 05.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M
    ID 1d6b:0002 Linux Foundation 2.0 root hub
/:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/3p, 480M
    ID 1d6b:0002 Linux Foundation 2.0 root hub
    |__ Port 1: Dev 8, If 0, Class=Vendor Specific Class, Driver=, 480M
        ID 18d1:d00d Google Inc. Xiaomi Mi/Redmi 2 (fastboot)
    |__ Port 2: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
        ID 03f0:2c24 HP, Inc Logitech M-UAL-96 Mouse
/:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M
    ID 1d6b:0002 Linux Foundation 2.0 root hub
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M
    ID 1d6b:0002 Linux Foundation 2.0 root hub
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M
    ID 1d6b:0002 Linux Foundation 2.0 root hub
    |__ Port 3: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
        ID 0b05:19b6 ASUSTek Computer, Inc.

And yes, I’ve tried iommu, disabling svm, disabling msi, and bios mass storage driver.

4

Here is another lsusb -vt with the 3.2 Gen 1x1 Stick and 3.2 Gen 2 Phone, and a USB 2 Mouse attached.

/:  Bus 10.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 10000M
    ID 1d6b:0003 Linux Foundation 3.0 root hub
/:  Bus 09.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/0p, 5000M
    ID 1d6b:0003 Linux Foundation 3.0 root hub
/:  Bus 08.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 10000M
    ID 1d6b:0003 Linux Foundation 3.0 root hub
/:  Bus 07.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 10000M
    ID 1d6b:0003 Linux Foundation 3.0 root hub
    |__ Port 1: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 5000M
        ID 24a9:205a  
/:  Bus 06.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 10000M
    ID 1d6b:0003 Linux Foundation 3.0 root hub
/:  Bus 05.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M
    ID 1d6b:0002 Linux Foundation 2.0 root hub
/:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M
    ID 1d6b:0002 Linux Foundation 2.0 root hub
    |__ Port 1: Dev 2, If 0, Class=Vendor Specific Class, Driver=, 480M
        ID 18d1:4ee7 Google Inc. Nexus/Pixel Device (charging + debug)
/:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/3p, 480M
    ID 1d6b:0002 Linux Foundation 2.0 root hub
    |__ Port 2: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
        ID 03f0:2c24 HP, Inc Logitech M-UAL-96 Mouse
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M
    ID 1d6b:0002 Linux Foundation 2.0 root hub
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M
    ID 1d6b:0002 Linux Foundation 2.0 root hub
    |__ Port 3: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
        ID 0b05:19b6 ASUSTek Computer, Inc.
5

inxi -FJaz is made for usb debugging issues, but seems to not be registering as an option. That’s the --usb trigger, -J is shortcut for --usb.

USB 2/3 issues are often caused by the system’s way of creating hubs, I know my system does that, basically as soon as you plugin a usb 2 device into an existing hub (which inxi -Jaz shows fairly clearly in terms of which hub owns which hub or device) it transforms the entire chain to usb 2, that’s by the usb spec, it’s not a bug, it’s a feature. For a long time I thought my motherboard vendor had lied and made the usb 3 bus usb 2, not realizing that usb 2 and 3 are so different that they basically have to create a virtual usb 2 hub to handle usb 2 devices when plugged into a usb 3 hub.

That appears to be what is happening in your case. This is not at all intuititive, nor is it at all common knowledge, I didn’t know it until I tracked down the real specs and docs for usb 2 and 3.

There’s also a very common misperception that the connector type has anything to do with the usb speed, it does not, except that certain types were commonly found with usb 2 only, and don’t support usb 3, like microusb, but others do support usb 3, like usb a (as long as it’s usb 3 type, aka the blue ends). USB c is a type of connector, it’s not a speed rating, it supports usb 2 and 3, and maybe 1.1, I forget, probably also 1.0 and 1.1 since it can be converted to usb type a connector, like a c to a cable. Most usb c devices I have are usb 2 speed rated, but they could be usb 3 as long as the usb c cable is a usb 3 type, which they can easily not be (check the usb a connector color, if blue, it’s usb 3 capable, if not, it’s usb 2 only.

It’s useful to not confuse those things, for example my phone has a usb c connector, but is is a usb 2 device.

There’s also an issue that sometimes because of the fairly virtual way the hubs route usb 2 when it’s a 3 hub, it can trigger issues, so in a sense, it’s best to plug usb 2 devices into usb 2 hubs, and usb 3 into usb 3 hubs, which will avoid I think in most cases that virtual usb 2 hub appearing in the usb 3 hub which is confusing.

Let me illustrate this with 2 samples, the first has a usb 2 flash drive attached to a usb 3 port, the second has a usb 3 flash drive attached to the same exact port:

pinxi -Jx
USB:
  [pseudo parent hub]  Hub-1: 1-0:1 info: Hi-speed hub with single TT ports: 14 rev: 2.0**
  Device-1: 1-4:2 info: Wacom ET-0405A [Graphire2 (4x5)] type: Mouse
    driver: usbhid,wacom rev: 1.1
  [child device] Device-2: 1-8:91 info: Verbatim STORE N GO type: Mass Storage**
    driver: usb-storage rev: 2.0**
  Device-3: 1-9:3 info: Tangtop HID Keyboard type: Keyboard,Mouse
    driver: hid-generic,usbhid rev: 1.1
  Device-4: 1-10:4 info: Microsoft Natural Keyboard Elite type: Keyboard
    driver: hid-generic,usbhid rev: 1.0
  [actual parent hub] Hub-2: 2-0:1 info: Super-speed hub ports: 8 rev: 3.1
  Hub-3: 3-0:1 info: Hi-speed hub with single TT ports: 2 rev: 2.0
  Hub-4: 4-0:1 info: Super-speed hub ports: 2 rev: 3.1
  Hub-5: 5-0:1 info: Hi-speed hub with single TT ports: 4 rev: 2.0
  Device-1: 5-4:3 info: American Power Conversion Uninterruptible Supply
    type: HID driver: hid-generic,usbhid rev: 1.1
  Hub-6: 6-0:1 info: Super-speed hub ports: 4 rev: 3.0
  Hub-7: 6-1:2 info: VIA Labs USB3.0 Hub ports: 4 rev: 3.2
  Hub-8: 6-1.3:3 info: VIA Labs USB3.0 Hub ports: 4 rev: 3.2

next the usb 3, same physical port:

pinxi -Jx
USB:
  Hub-1: 1-0:1 info: Hi-speed hub with single TT ports: 14 rev: 2.0
  Device-1: 1-4:2 info: Wacom ET-0405A [Graphire2 (4x5)] type: Mouse
    driver: usbhid,wacom rev: 1.1
  Device-2: 1-9:3 info: Tangtop HID Keyboard type: Keyboard,Mouse
    driver: hid-generic,usbhid rev: 1.1
  Device-3: 1-10:4 info: Microsoft Natural Keyboard Elite type: Keyboard
    driver: hid-generic,usbhid rev: 1.0
  [parent hub] Hub-2: 2-0:1 info: Super-speed hub ports: 8 rev: 3.1**
  [child device]Device-1: 2-8:4 info: SanDisk Ultra type: Mass Storage driver: usb-storage**
    rev: 3.0**
  Hub-3: 3-0:1 info: Hi-speed hub with single TT ports: 2 rev: 2.0
  Hub-4: 4-0:1 info: Super-speed hub ports: 2 rev: 3.1
  Hub-5: 5-0:1 info: Hi-speed hub with single TT ports: 4 rev: 2.0
  Device-1: 5-4:3 info: American Power Conversion Uninterruptible Supply
    type: HID driver: hid-generic,usbhid rev: 1.1
  Hub-6: 6-0:1 info: Super-speed hub ports: 4 rev: 3.0
  Hub-7: 6-1:2 info: VIA Labs USB3.0 Hub ports: 4 rev: 3.2
  Hub-8: 6-1.3:3 info: VIA Labs USB3.0 Hub ports: 4 rev: 3.2

then I plug the usb 2 and 3 device into the two ports of this hub:

pinxi -Jx
USB:
 [fake parent hub] Hub-1: 1-0:1 info: Hi-speed hub with single TT ports: 14 rev: 2.0
  Device-1: 1-4:2 info: Wacom ET-0405A [Graphire2 (4x5)] type: Mouse
    driver: usbhid,wacom rev: 1.1
  [usb 2 device on port of Hub-2]Device-2: 1-7:92 info: Verbatim STORE N GO type: Mass Storage
    driver: usb-storage rev: 2.0
  Device-3: 1-9:3 info: Tangtop HID Keyboard type: Keyboard,Mouse
    driver: hid-generic,usbhid rev: 1.1
  Device-4: 1-10:4 info: Microsoft Natural Keyboard Elite type: Keyboard
    driver: hid-generic,usbhid rev: 1.0
  [true usb 3.1 parent]Hub-2: 2-0:1 info: Super-speed hub ports: 8 rev: 3.1
  [child of usb 3 hub]Device-1: 2-8:4 info: SanDisk Ultra type: Mass Storage driver: usb-storage
    rev: 3.0
  Hub-3: 3-0:1 info: Hi-speed hub with single TT ports: 2 rev: 2.0
  Hub-4: 4-0:1 info: Super-speed hub ports: 2 rev: 3.1
  Hub-5: 5-0:1 info: Hi-speed hub with single TT ports: 4 rev: 2.0
  Device-1: 5-4:3 info: American Power Conversion Uninterruptible Supply
    type: HID driver: hid-generic,usbhid rev: 1.1
  Hub-6: 6-0:1 info: Super-speed hub ports: 4 rev: 3.0
  Hub-7: 6-1:2 info: VIA Labs USB3.0 Hub ports: 4 rev: 3.2
  Hub-8: 6-1.3:3 info: VIA Labs USB3.0 Hub ports: 4 rev: 3.2

As you can see, now the usb 3 parent hub is the parent of the usb 3 stick, and the pseudo usb 2 hub is the apparent parent of the usb 2 stick, but they are running on the same hub, that goes with one cable to the motherboard if I remember right. So that usb 2 signal is basically routed to a real usb 2 hub up the chain, I think, maybe, and the real usb 3 hub does not try to run it.

This is what the inxi -Jx feature is for, by the way, making this stuff clear, that’s how I discovered this usb 2/3 behavior in terms of creating a virtual usb 2 connection to another usb 2 hub within the actual usb 3 hub…

Now you know.

I don’t know the actual mechanism the kernel uses to make these changes in apparent parent hubs, but I know that is what happens. I don’t remember if it happens inside the usb 3 chip, or if it happens outside it, but it’s part of the spec basically, it’s not wrong behavior, it’s how they maintained backwards compatibility to 1.0, 1.1, and 2.0, despite 3 and 4 being radically different technologies.

I think the best way to think of it is that a usb 3 hub actually cannot do usb 2, so it has to resort to this sort of hardware/firmware/software hack to make the connection viable.

The easiest way to determine what your devices true usb revision number/speeds are is to just plug them in one by one to a usb 3 port or hub, and use inxi -Jx to determine what is actually happening each time. Remove them one at a time, so there is only one device attached to the hub at a time. It’s harder to know what the motherboard actually considers a hub, you can do a test there too by having no usb devices attached, then plugging in a usb 3 device to each port on the system, whenever it shows a 3.x hub with a 3 x device, you know that’s a true usb 3 port, or usb 4 if that is out yet. I believe 3 and 4 do not have this backward issue with eachother like they do with 1.0,1.1, and 2.

But don’t confused a USB C connector with USB 2, 3, or 4, they have no necessary connection.

6

Thanks for your detailed and insightful explanation.
However, in my specific case, I believe there is actually something wrong based on the fact that my displayport adapter, and other USB C (not 2.0, but actually 3.2 Gen 2 rated) devices either don’t show up, only show USB 2 billboard devices, or work at a way slower than advertised speed.

7

I’m back at my PC now and did some additional research.
The phone, which only registers on the 480Mbps (USB 2)
root hub, is rated at 10Gbps, as stated on Google’s website.

My ASUS ROG G17 Laptop’s APU has dedicated PCIe Lanes for USB 4 support:
lspci -nnk|grep USB:

06:00.3 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Rembrandt USB4 XHCI controller #3 [1022:161d]
06:00.4 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Rembrandt USB4 XHCI controller #4 [1022:161e]
07:00.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Rembrandt USB4 XHCI controller #8 [1022:161f]
07:00.3 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Rembrandt USB4 XHCI controller #5 [1022:15d6]
07:00.4 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Rembrandt USB4 XHCI controller #6 [1022:15d7]

while ASUS themselves rate the rear USB-C Ports for 3.2 Gen 2
speeds and the one closest to the HDMI port has a DisplayPort logo,
and a lightning bolt, definitely not Thunderbolt, but signaling
power delivery capability.

Based on all this, and on the fact that my phone actually
fast charges on that port, I’d say there’s actually something
wrong with how the xhci_hcd driver handles these ports,
especially so, because USB-C to DisplayPort Adapters utilizing
DP Alt Mode don’t cause my Display Configuration to change
(Wayland and Xorg) and connected monitors don’t even
show up as permanently disabled, while the HDMI port worked
out of the box, thanks to the brilliant hybrid graphics drivers.

8 
USB:
  Hub-1: 1-0:1 info: Hi-speed hub with single TT ports: 4 rev: 2.0
    speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900
  Device-1: 1-3:2 info: ASUSTek N-KEY Device type: Keyboard
    driver: asus,usbhid interfaces: 1 rev: 2.0 speed: 12 Mb/s power: 100mA
    chip-ID: 0b05:19b6 class-ID: 0301
  Hub-2: 2-0:1 info: Hi-speed hub with single TT ports: 1 rev: 2.0
    speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900
  Device-1: 2-1:2 info: IS918 Intenso Ultra Line type: Mass Storage
    driver: usb-storage interfaces: 1 rev: 2.1 speed: 480 Mb/s power: 200mA
    chip-ID: 24a9:205a class-ID: 0806 serial: <filter>
  Hub-3: 3-0:1 info: Hi-speed hub with single TT ports: 3 rev: 2.0
    speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900
  Device-1: 3-1:4 info: SINO WEALTH Gaming KB type: Keyboard,HID
    driver: hid-generic,usbhid interfaces: 2 rev: 1.1 speed: 12 Mb/s
    power: 500mA chip-ID: 258a:003a class-ID: 0300
  Device-2: 3-2:2 info: HP Logitech M-UAL-96 Mouse type: Mouse
    driver: hid-generic,usbhid interfaces: 1 rev: 2.0 speed: 1.5 Mb/s
    power: 98mA chip-ID: 03f0:2c24 class-ID: 0301
  Hub-4: 4-0:1 info: Hi-speed hub with single TT ports: 1 rev: 2.0
    speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900
  Device-1: 4-1:4 info: Google Nexus/Pixel Device (MTP + debug)
    type: Still Imaging driver: N/A interfaces: 2 rev: 2.1 speed: 480 Mb/s
    power: 500mA chip-ID: 18d1:4ee2 class-ID: 0601 serial: <filter>
  Hub-5: 5-0:1 info: Hi-speed hub with single TT ports: 1 rev: 2.0
    speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900
  Hub-6: 6-0:1 info: Super-speed hub ports: 2 rev: 3.1 speed: 10 Gb/s
    chip-ID: 1d6b:0003 class-ID: 0900
  Hub-7: 7-0:1 info: Super-speed hub ports: 2 rev: 3.1 speed: 10 Gb/s
    chip-ID: 1d6b:0003 class-ID: 0900
  Hub-8: 8-0:1 info: Super-speed hub ports: 1 rev: 3.1 speed: 10 Gb/s
    chip-ID: 1d6b:0003 class-ID: 0900
  Hub-9: 9-0:1 info: Linux Foundation 3.0 root hub ports: N/A rev: 3.0
    speed: 5 Gb/s chip-ID: 1d6b:0003 class-ID: 0900
  Hub-10: 10-0:1 info: Super-speed hub ports: 1 rev: 3.1 speed: 10 Gb/s
    chip-ID: 1d6b:0003 class-ID: 0900
9

My experience with true high speed usb 3 and above is that the cables start to matter a LOT. I’ve always been somewhat cavalier about cables for usb, but I’ve noticed that there is far less forgiveness for cable weakness in usb 3. I’ve never seen usb 4 personally, good to know it’s shipping.

It could be a driver issue given how new usb 4 is relatively speaking.

that’s a good overview, one thing that caught my eye is this:

USB4 specifies tunneling of:

USB 3.2 (“Enhanced Superspeed”) Tunneling
DisplayPort 1.4a-based Tunneling
PCI Express (PCIe)-based Tunneling
USB4 also requires support of DisplayPort Alternate Mode. That means, DP can be sent via USB4 tunneling or by DP Alternate Mode.[15]

DisplayPort Alt Mode 2.0: USB 4 supports DisplayPort 2.0 over its alternative mode. DisplayPort 2.0 can support 8K resolution at 60 Hz with HDR10 color and can use up to 80 Gbit/s which is the same amount available to USB data, but just unidirectional.[16]

Legacy USB (1–2) is always supported using the dedicated wires in the USB-C connector.

Which answers the question of how the usb 2 hub issue happens, it’s physical wiring, at least on usb c connectors, which then take the usb data to a usb 2 hub, I think.

This is a guess, since it can be one of several things, but if the cable is faulty, and is treated as a usb 2 connection, that would then maybe send the displayport data to somewhere it doesn’t belong. This is a guess however. That is, if the cable is being treated as usb 2 because it’s not a true or working usb 3 compliant cable, this might then split the signal and send what it believes is a usb 2 item to a usb 2 hub, which does not know about display port. Not sure about this though.

I would make sure you are using a known good cable there before anything else, and also of course search for usb 4 linux driver issues for your specific hardware. This is very new tech, and it often takes a while to roll out the full support, and usb 4 2.0, awkward naming, just was spec’ed in 2022.

It’s also possible that usb 4 is ‘seen’ internally differently, particularly if it’s going over the pcie bus directly.

I would not deduce anything from the device charging over the cable, that’s a simple wire connection, which probably always works until the cable is totally failed, that probably simply means that the wire from the connector is not broken at any point.

I’d have to get a usb 4 pcie card to test this stuff completely, as of yet I’ve never seen a dataset from a true native pcie run usb 4 system.

Note that the inxi usd data comes from the internal usb bus data, mainly from /sys, so would in theory include all usb devices and hubs, but that’s not certain.

I don’t know how the wiring would work in this case, for example, is the usb 2 data tunneled through the pcie connection? It must be at some point, unless it’s split out before that point.

The tests I indicated above are still useful, for example, insert a usb 2 device via usb c into the two usb c female connectors. Does the device now appear? if so, note the hub bus ID it is on. then stick a real usb 3 device in, does it now appear?

This type of testing is fairly tedious, and I know in my case, I didn’t do it for a year or so, assuming there was a defect with my mobo, when it was all by design, and I was simply not understanding the stuff.

I wish there were some way to truly test continuity in usb cables, but I dont’ know of any beyond hoping you have a known good one, and then doing the tests to pinpoint the cause of the issue.

I’ll check back in this thread because this may be an issue inxi can deal with, but I can’t know until I really get usb 4 test data to determine if it’s working or not, or if htere is a new variant that is not handled.

Your initial lsusb also shows the same thing however, and the hub should be appearing as a usb 4 hub, but there are only 3.0 and 3.1 from what I can see from the speeds.

There’s also another possible situation, which is that the hub chip is dead or dying. I had that issue with an entire production run of usb 3 controller cards, I think I had 5 die after only a few gigabytes of data transfer, it was a global usb 3 chip issue. You can probably determine this if no devices register, and if the hub fails to show, but that could also be a driver issue.

However, note that your initial issue description corresponds almost verbatim to what I am talking about, devices being transferred to a usb 2 bus, then showing up as owned by that usb 2 hub. This could be a hardware problem, but I’ve also seen cases where a single usb 2 device plugged in made the entire thing become usb 2, though I believe that might be a hardware issue.

I generally don’t recommend random bios/uefi flashing and updating, but you might give a thought to making sure you have the latest uefi/bios for your hardware because this could well be a firmware issue.

10

Yeah, in anticipation of hardware and firmware issues, I updated the UEFI and got a second USB-C to DisplayPort cable…
So that sadly rules out any low-level issues I could fix.

11

This is the “Cable Matters USB-C to 8K DisplayPort Adapter”:

Hub-4: 4-0:1 info: Hi-speed hub with single TT ports: 1 rev: 2.0
    speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900
  Device-1: 4-1:7 info: Realtek billboard type: Billboard driver: N/A
    interfaces: 1 rev: 2.0 speed: 12 Mb/s power: 500mA chip-ID: 0bda:5452
    class-ID: 1100 serial: <filter>

And this is the “Anker 518 USB-C Adapter”:

Hub-4: 4-0:1 info: Hi-speed hub with single TT ports: 1 rev: 2.0
    speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900
  Device-1: 4-1:8 info: Fresco Logic Generic Billboard Device
    type: Billboard driver: N/A interfaces: 1 rev: 2.0 speed: 12 Mb/s
    chip-ID: 1d5c:7102 class-ID: 1100

The “billboard” device in these is supposed to communicate connection errors and such to the system, but I don’t know in what way that’s implemented in Linux.

12

It was rapid charging, which means even Power Delivery is working on the port.

13

Maybe that’s an issue too, as lspci -nnk clearly showed USB4 XHCI Controllers, and ASUS also rates them for 3.2 Gen 2, and these speeds would also be needed for a stable DisplayPort 1.4 connection.

14

As noted, power is a wire, basically. If I understand it right. That would be I think the last thing to fail in this chain.

More interesting is that your two devices are reporting 12 Mb/s, aka, usb 1.1 speeds. Those speeds come from /sys by the way, that’s what the kernel is seeing at that moment.

Check for uefi updates on the vendor website, yours is almost new, but see if there has been a fix released recently, if so, that might be related to this issue, this could well be a firmware issue on the mobo.

It’s very hard to pin down issues like this, as I noted, I was looking right at the data on my system for a year before I finally realized what it meant.

What is your actual phone, the data above shows the clearly wrong redmi 2 string, which is 10 years old, so that’s not the real phone ID. A newer pixel I assume?

If all your true usb 3 devices are showing as very slow usb 2 or even 1.1 speeds, and if there is no cable involved in most cases, that suggests maybe firmware issue to me, or possibly driver issue, or even worst case the usb 4 pcie bus is failed and everything is being shunted to the usb 2/1.1/1 bus.

15

Sorry for the confusion, the Redmi ID came for my Huawei P30 lite, which is only USB 2, afaik.
My current phone is a Google Pixel 7, sorry for the confusion.
Here is inxi -FJaz with a USB 3.2 Gen 1 Stick, and the Google Pixel connected:

USB:
  Hub-1: 1-0:1 info: Hi-speed hub with single TT ports: 4 rev: 2.0 speed: 480 Mb/s
    chip-ID: 1d6b:0002 class-ID: 0900
  Device-1: 1-3:2 info: ASUSTek N-KEY Device type: Keyboard driver: asus,usbhid interfaces: 1
    rev: 2.0 speed: 12 Mb/s power: 100mA chip-ID: 0b05:19b6 class-ID: 0301
  Hub-2: 2-0:1 info: Hi-speed hub with single TT ports: 1 rev: 2.0 speed: 480 Mb/s
    chip-ID: 1d6b:0002 class-ID: 0900
  Hub-3: 3-0:1 info: Hi-speed hub with single TT ports: 3 rev: 2.0 speed: 480 Mb/s
    chip-ID: 1d6b:0002 class-ID: 0900
  Hub-4: 4-0:1 info: Hi-speed hub with single TT ports: 1 rev: 2.0 speed: 480 Mb/s
    chip-ID: 1d6b:0002 class-ID: 0900
  Device-1: 4-1:9 info: Google Nexus/Pixel Device (charging + debug) type: <vendor specific>
    driver: N/A interfaces: 1 rev: 2.1 speed: 480 Mb/s power: 500mA chip-ID: 18d1:4ee7
    class-ID: 0000 serial: <filter>
  Hub-5: 5-0:1 info: Hi-speed hub with single TT ports: 1 rev: 2.0 speed: 480 Mb/s
    chip-ID: 1d6b:0002 class-ID: 0900
  Hub-6: 6-0:1 info: Super-speed hub ports: 2 rev: 3.1 speed: 10 Gb/s chip-ID: 1d6b:0003
    class-ID: 0900
  Hub-7: 7-0:1 info: Super-speed hub ports: 2 rev: 3.1 speed: 10 Gb/s chip-ID: 1d6b:0003
    class-ID: 0900
  Device-1: 7-2:3 info: IS918 Intenso Ultra Line type: Mass Storage driver: usb-storage
    interfaces: 1 rev: 3.2 speed: 5 Gb/s power: 304mA chip-ID: 24a9:205a class-ID: 0806
    serial: <filter>
  Hub-8: 8-0:1 info: Super-speed hub ports: 1 rev: 3.1 speed: 10 Gb/s chip-ID: 1d6b:0003
    class-ID: 0900
  Hub-9: 9-0:1 info: Linux Foundation 3.0 root hub ports: N/A rev: 3.0 speed: 5 Gb/s
    chip-ID: 1d6b:0003 class-ID: 0900
  Hub-10: 10-0:1 info: Super-speed hub ports: 1 rev: 3.1 speed: 10 Gb/s chip-ID: 1d6b:0003
    class-ID: 0900

The other device is just the laptop’s keyboard.
Despite just 500mA power being reported, the phone is actually fast charging, so that might be wrong too.

16

I wouldn’t put much meaning into the power item, that could be a simple current draw for the port, not the actual electrical current running through it when charging, that is, 500ma might be what it takes to run that connection, and isn’t related at all to the power going through the power line, that’s my guess. I don’t know what that number refers to, or where the kernel gets it from.

In other words, I believe the say 500ma refers not the power going through the power wire/s, but to the power required to maintain the usb connection itself.

As an aside, testing this, when I connected my usb 2 phone to a usb 3 hub it did not show up at all, but when I connected it to a usb 2 hub, it did. I had read that there can be issues with running some usb 2 devices through a usb 3 hub.

I confirmed this with the same cable, first to a usb 3 mobo > usb 3 external hub, then with usb 2 hub to phone, then mobo usb 3 header to ports, and only the true usb 2 hub connection worked. That shows how delicate this can be, really in an objective sense, usb 2 and 3/4 aren’t the same tech, only the interfaces are the same from what I can see, and that can lead to issues.

However, demonstrating my point re power charging is just a wire, in all cases, the phone was charging, so this is more about how usb 2 and 3 gets routed.

I checked the asus website, and don’t see any new uefi past march 1, which is probably your 2-26 version I’d guess, since the packaging date probably comes before th release date.

There’s also oddities that creep in with how the kernel gets this data by the way, sometimes the speed/rev report are the actual current live speeds, and sometimes they are the rated max speed, for example, sometimes if you plug a 3.2 device into a 3.1 hub, it will show as 3.2 speed, even though it’s actually only able to run at 3.1 speed, but sometimes it shows as the modified speed, the actual real speed that is. This is not consistent from my recollection.

The best test is to have a true simple usb 4 device, like a flash drive, with no cable, and insert it into the usb c connected usb 4 port, and see if the usb 4 hub suddenly springs into existence, or if it stays at 3. Or worst, if it drops to usb 2 speed and appears under a usb 2 hub, at which point I’d start suspecting hardware/firmware issues.

17

Yeah, sadly the only USB4 device I have is the CableMatters Adapter, and its billboard is USB 2 again, so that’s not the best test case.
And yeah, I have the newest BIOS from the ASUS website.

18

Its’ an interesting problem don’t give up, but keep in mind sometimes behaviors that appear to be inexplicable can be hardware issues, but they can also be firmware issues or kernel driver issues, very hard to diagnose, but you are running fairly cutting edge hardware there and it’s possible you’re experiencing teething pains somewhere in the stack, but sadly also entirely possible you are looking at a hardware issue, which annoyingly is very hard to distinguish from firmware/kernel driver issues.

I was fairly burned by a global usb 3 chip glitch that had filled entire production runs of at least some usb 3 controller card makers, in my case, the vendor was actually very awesome and kept sending me new cards, until I basically just gave up and suggested they had a bad run of usb 3 chips since they all failed in basically the same way. So I suspect that it’s a chip issue but that’s not at all a given, and the pcie usb 4 chips are going to be totally new, different series, so highly unlikely to be that same issue, which I think hit me around 2021 or so.

I’d start looking for other reports online of usb 4 issues with that laptop/chipset.

19

I want to point this out since I just noticed it.

Reproduce that, and note when the intenso shows as attached to a usb 2 hub with usb 2 speed (that’s an example by the way of the two ways the kernel reports the device speed, or hub attached to hub speed, either the actual current speed, OR the max device speed, in your case, its’ reporting the possible speed at the moment).

In other words, insert the device into the port that reports it as as usb 2 speed, then into the port that reports it as usb 3 speed. This should tell you a lot, unless the usb 2 port is actually just a usb port, and the usb 3 speed reporting port is a standard usb 3.

Hub-2: 2-0:1 info: Hi-speed hub with single TT ports: 1 rev: 2.0
    speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900
  Device-1: 2-1:2 info: IS918 Intenso Ultra Line type: Mass Storage
    driver: usb-storage interfaces: 1 rev: 2.1 speed: 480 Mb/s power: 200mA
    chip-ID: 24a9:205a class-ID: 0806 serial: <filter>


Hub-7: 7-0:1 info: Super-speed hub ports: 2 rev: 3.1 speed: 10 Gb/s chip-ID: 1d6b:0003
    class-ID: 0900
  Device-1: 7-2:3 info: IS918 Intenso Ultra Line type: Mass Storage driver: usb-storage
    interfaces: 1 rev: 3.2 speed: 5 Gb/s power: 304mA chip-ID: 24a9:205a class-ID: 0806
    serial: <filter>

In the usb 4 specs, I note for example that usb 4 only works over usb c connectors, and that the intenso appears to use a male usb a type connector, rated at usb 3 speed. There may be some mapping to legacy usb types if any type A to type C connector adapters are used, that would require empirical data to determine.

20

The top one is actually the stick connected to one of the USB-C ports using a C-to-A adapter which probably doesn’t meet 3.0 spec, even electrically.