You are not logged in.
I recently swapped out my motherboard for a Gigabyte X870E Aorus Master with a 9950X3D.
Since I have done this, I am unable to get my Thunderbolt NVME drive to work. It worked on my Intel board, and does on my AMD laptop with the same kernel versions.
I have tried setting the kernel parameters to increase hot-plug bus size and memory to no avail. I've tried enabling/disable re-sizeable bar and IOMMU to no avail.
Within BIOS, the drive is seen and reported as a block device under NVME configuration. I am running the latest BIOS for the board.
journalctl
May 01 21:32:43 archlinux kernel: thunderbolt 0-3: new device found, vendor=0xb8 device=0x2464
May 01 21:32:43 archlinux kernel: thunderbolt 0-3: NewQ NQ-HS-01
May 01 21:32:43 archlinux boltd[976]: probing: started [1000]
May 01 21:32:43 archlinux boltd[976]: [0d3c4c17-a098-NQ-HS-01 ] parent is 86314c17-007f...
May 01 21:32:43 archlinux boltd[976]: [0d3c4c17-a098-NQ-HS-01 ] connected: connected (/sys/devices/pci0000:00/0000:00:02.2/0000:16:00.0/0000:17:03.0/0000:89:00.0/domain0/0-0/0-3)
May 01 21:32:43 archlinux boltd[976]: [0d3c4c17-a098-NQ-HS-01 ] auto-auth: authmode: enabled, policy: auto, iommu: no -> ok
May 01 21:32:43 archlinux boltd[976]: [0d3c4c17-a098-NQ-HS-01 ] auto-auth: security: user mode, key: no -> ok
May 01 21:32:43 archlinux boltd[976]: [0d3c4c17-a098-NQ-HS-01 ] authorize: authorization prepared for 'user' level
May 01 21:32:43 archlinux boltd[976]: [0d3c4c17-a098-NQ-HS-01 ] udev: device changed: authorizing -> authorizing
May 01 21:32:43 archlinux boltd[976]: [0d3c4c17-a098-NQ-HS-01 ] udev: device changed: authorizing -> authorizing
May 01 21:32:44 archlinux boltd[976]: [0d3c4c17-a098-NQ-HS-01 ] authorize: finished: ok (status: authorized, flags: 0)
May 01 21:32:44 archlinux boltd[976]: [0d3c4c17-a098-NQ-HS-01 ] auto-auth: authorization successful
May 01 21:32:44 archlinux boltd[976]: [0d3c4c17-a098-NQ-HS-01 ] udev: device changed: authorized -> authorized
May 01 21:32:44 archlinux kernel: pcieport 0000:17:01.0: pciehp: Slot(0-1): Card present
May 01 21:32:44 archlinux kernel: pcieport 0000:17:01.0: pciehp: Slot(0-1): Link Up
May 01 21:32:45 archlinux kernel: pci 0000:50:00.0: [1b21:2463] type 01 class 0x060400 PCIe Switch Upstream Port
May 01 21:32:45 archlinux kernel: pci 0000:50:00.0: PCI bridge to [bus 00]
May 01 21:32:45 archlinux kernel: pci 0000:50:00.0: bridge window [io 0x0000-0x0fff]
May 01 21:32:45 archlinux kernel: pci 0000:50:00.0: bridge window [mem 0x00000000-0x000fffff]
May 01 21:32:45 archlinux kernel: pci 0000:50:00.0: bridge window [mem 0x00000000-0x000fffff 64bit pref]
May 01 21:32:45 archlinux kernel: pci 0000:50:00.0: enabling Extended Tags
May 01 21:32:45 archlinux kernel: pci 0000:50:00.0: PME# supported from D0 D3hot D3cold
May 01 21:32:45 archlinux kernel: pci 0000:50:00.0: Adding to iommu group 28
May 01 21:32:45 archlinux kernel: pcieport 0000:17:01.0: ASPM: current common clock configuration is inconsistent, reconfiguring
May 01 21:32:45 archlinux kernel: pci 0000:50:00.0: bridge configuration invalid ([bus 00-00]), reconfiguring
May 01 21:32:45 archlinux kernel: pci 0000:51:00.0: [1b21:2463] type 01 class 0x060400 PCIe Switch Downstream Port
May 01 21:32:45 archlinux kernel: pci 0000:51:00.0: PCI bridge to [bus 00]
May 01 21:32:45 archlinux kernel: pci 0000:51:00.0: bridge window [io 0x0000-0x0fff]
May 01 21:32:45 archlinux kernel: pci 0000:51:00.0: bridge window [mem 0x00000000-0x000fffff]
May 01 21:32:45 archlinux kernel: pci 0000:51:00.0: bridge window [mem 0x00000000-0x000fffff 64bit pref]
May 01 21:32:45 archlinux kernel: pci 0000:51:00.0: enabling Extended Tags
May 01 21:32:45 archlinux kernel: pci 0000:51:00.0: PME# supported from D0 D3hot D3cold
May 01 21:32:45 archlinux kernel: pci 0000:51:00.0: Adding to iommu group 28
May 01 21:32:45 archlinux kernel: pci 0000:50:00.0: PCI bridge to [bus 51-87]
May 01 21:32:45 archlinux kernel: pci 0000:51:00.0: bridge configuration invalid ([bus 00-00]), reconfiguring
May 01 21:32:45 archlinux kernel: pci 0000:52:00.0: [144d:a808] type 00 class 0x010802 PCIe Endpoint
May 01 21:32:45 archlinux kernel: pci 0000:52:00.0: BAR 0 [mem 0x00000000-0x00003fff 64bit]
May 01 21:32:45 archlinux kernel: pci 0000:52:00.0: 2.000 Gb/s available PCIe bandwidth, limited by 2.5 GT/s PCIe x1 link at 0000:17:01.0 (capable of 31.504 Gb/s with 8.0 GT/s PCIe x4 link)
May 01 21:32:45 archlinux kernel: pci 0000:52:00.0: Adding to iommu group 28
May 01 21:32:45 archlinux kernel: pci 0000:51:00.0: PCI bridge to [bus 52-87]
May 01 21:32:45 archlinux kernel: pci_bus 0000:52: busn_res: [bus 52-87] end is updated to 52
May 01 21:32:45 archlinux kernel: pci_bus 0000:51: busn_res: [bus 51-87] end is updated to 52
May 01 21:32:45 archlinux kernel: pcieport 0000:17:01.0: Assigned bridge window [mem 0xb000000000-0xcfffffffff 64bit pref] to [bus 50-87] cannot fit 0x100000 required for 0000:51:00.0 bridging to [bus 52]
May 01 21:32:45 archlinux kernel: pci 0000:51:00.0: bridge window [mem 0x00000000-0x000fffff 64bit pref] to [bus 52] requires relaxed alignment rules
May 01 21:32:45 archlinux kernel: pcieport 0000:17:01.0: Assigned bridge window [mem 0xac000000-0xc3ffffff] to [bus 50-87] cannot fit 0x100000 required for 0000:51:00.0 bridging to [bus 52]
May 01 21:32:45 archlinux kernel: pci 0000:51:00.0: bridge window [mem 0x00000000-0x000fffff] to [bus 52] requires relaxed alignment rules
May 01 21:32:45 archlinux kernel: pcieport 0000:17:01.0: Assigned bridge window [mem 0xb000000000-0xcfffffffff 64bit pref] to [bus 50-87] cannot fit 0x100000 required for 0000:50:00.0 bridging to [bus 51-52]
May 01 21:32:45 archlinux kernel: pci 0000:50:00.0: bridge window [mem 0x00000000-0x000fffff 64bit pref] to [bus 51-52] requires relaxed alignment rules
May 01 21:32:45 archlinux kernel: pcieport 0000:17:01.0: Assigned bridge window [mem 0xac000000-0xc3ffffff] to [bus 50-87] cannot fit 0x100000 required for 0000:50:00.0 bridging to [bus 51-52]
May 01 21:32:45 archlinux kernel: pci 0000:50:00.0: bridge window [mem 0x00000000-0x000fffff] to [bus 51-52] requires relaxed alignment rules
May 01 21:32:45 archlinux kernel: pci 0000:50:00.0: bridge window [mem 0xac000000-0xc3ffffff]: assigned
May 01 21:32:45 archlinux kernel: pci 0000:50:00.0: bridge window [mem 0xb000000000-0xcfffffffff 64bit pref]: assigned
May 01 21:32:45 archlinux kernel: pci 0000:50:00.0: bridge window [io 0x7000-0x9fff]: assigned
May 01 21:32:45 archlinux kernel: pci 0000:51:00.0: bridge window [mem 0xac000000-0xc3ffffff]: assigned
May 01 21:32:45 archlinux kernel: pci 0000:51:00.0: bridge window [mem 0xb000000000-0xcfffffffff 64bit pref]: assigned
May 01 21:32:45 archlinux kernel: pci 0000:51:00.0: bridge window [io 0x7000-0x9fff]: assigned
May 01 21:32:45 archlinux kernel: pci 0000:52:00.0: BAR 0 [mem 0xac000000-0xac003fff 64bit]: assigned
May 01 21:32:45 archlinux kernel: pci 0000:51:00.0: PCI bridge to [bus 52]
May 01 21:32:45 archlinux kernel: pci 0000:51:00.0: bridge window [io 0x7000-0x9fff]
May 01 21:32:45 archlinux kernel: pci 0000:51:00.0: bridge window [mem 0xac000000-0xc3ffffff]
May 01 21:32:45 archlinux kernel: pci 0000:51:00.0: bridge window [mem 0xb000000000-0xcfffffffff 64bit pref]
May 01 21:32:45 archlinux kernel: pci 0000:50:00.0: PCI bridge to [bus 51-52]
May 01 21:32:45 archlinux kernel: pci 0000:50:00.0: bridge window [io 0x7000-0x9fff]
May 01 21:32:45 archlinux kernel: pci 0000:50:00.0: bridge window [mem 0xac000000-0xc3ffffff]
May 01 21:32:45 archlinux kernel: pci 0000:50:00.0: bridge window [mem 0xb000000000-0xcfffffffff 64bit pref]
May 01 21:32:45 archlinux kernel: pcieport 0000:17:01.0: PCI bridge to [bus 50-87]
May 01 21:32:45 archlinux kernel: pcieport 0000:17:01.0: bridge window [io 0x7000-0x9fff]
May 01 21:32:45 archlinux kernel: pcieport 0000:17:01.0: bridge window [mem 0xac000000-0xc3ffffff]
May 01 21:32:45 archlinux kernel: pcieport 0000:17:01.0: bridge window [mem 0xb000000000-0xcfffffffff 64bit pref]
May 01 21:32:45 archlinux kernel: pcieport 0000:50:00.0: enabling device (0000 -> 0003)
May 01 21:32:45 archlinux kernel: pcieport 0000:51:00.0: enabling device (0000 -> 0003)
May 01 21:32:45 archlinux kernel: nvme nvme2: pci function 0000:52:00.0
May 01 21:32:45 archlinux kernel: nvme 0000:52:00.0: enabling device (0000 -> 0002)
May 01 21:32:47 archlinux boltd[976]: probing: timeout, done: [2816306] (2000000)lspci (shows the two drives that are on the Motherboard, as well as the Thunderbolt drive, but Thunderbolt drive has no driver in use)
02:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller S4LV008[Pascal] (prog-if 02 [NVM Express])
Kernel driver in use: nvme
Kernel modules: nvme
03:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller S4LV008[Pascal] (prog-if 02 [NVM Express])
Kernel driver in use: nvme
Kernel modules: nvme
52:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983 (prog-if 02 [NVM Express])
Kernel modules: nvmeboltctl list
● NewQ NQ-HS-01
├─ type: peripheral
├─ name: NQ-HS-01
├─ vendor: NewQ
├─ uuid: 0d3c4c17-a098-a7b4-ffff-ffffffffffff
├─ generation: USB4
├─ status: authorized
│ ├─ domain: 86314c17-007f-9405-ffff-ffffffffffff
│ ├─ rx speed: 40 Gb/s = 2 lanes * 20 Gb/s
│ ├─ tx speed: 40 Gb/s = 2 lanes * 20 Gb/s
│ └─ authflags: none
├─ authorized: Fri 02 May 2025 03:30:47 AM UTC
├─ connected: Fri 02 May 2025 03:30:45 AM UTC
└─ stored: Thu 01 May 2025 07:30:18 AM UTC
├─ policy: auto
└─ key: nolsblk not showing the 3 NVME (nvme2 is missing) drives
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
zram0 253:0 0 4G 0 disk [SWAP]
nvme0n1 259:0 0 1.8T 0 disk
├─nvme0n1p1 259:2 0 1G 0 part /boot
└─nvme0n1p2 259:3 0 1.8T 0 part /
nvme1n1 259:1 0 1.8T 0 disk
├─nvme1n1p1 259:4 0 100M 0 part
├─nvme1n1p2 259:5 0 16M 0 part
├─nvme1n1p3 259:6 0 1.8T 0 part
└─nvme1n1p4 259:7 0 522M 0 partuname -a
Linux archlinux 6.14.4-arch1-2 #1 SMP PREEMPT_DYNAMIC Tue, 29 Apr 2025 09:23:13 +0000 x86_64 GNU/LinuxLast edited by jslay (2025-05-02 03:50:58)
Offline
Issue still persists with 6.15.3
Last edited by jslay (2025-06-24 07:32:29)
Offline
I've got the same issue using an ACASIS TB501Pro. I've got an ASUS X870-I which uses the ASM4242 for the usb4 controller, and I'm using the 6.18.9 kernel
lspci definitely picks up the device:
0e:04.0 PCI bridge: Intel Corporation JHL9480 Thunderbolt 5 80/120G Bridge [Barlow Ridge Hub 80G 2023] (rev 85)
Subsystem: Device 2222:1111
Kernel driver in use: pcieport
Kernel modules: shpchpAnd boltctl shows the device as authorised:
● ACASIS TB501Pro
├─ type: peripheral
├─ name: TB501Pro
├─ vendor: ACASIS
├─ uuid: e4ec8780-006e-7b71-ffff-ffffffffffff
├─ generation: USB4
├─ status: authorized
│ ├─ domain: d6a34c17-007f-14de-ffff-ffffffffffff
│ ├─ rx speed: 40 Gb/s = 2 lanes * 20 Gb/s
│ ├─ tx speed: 40 Gb/s = 2 lanes * 20 Gb/s
│ └─ authflags: none
├─ authorized: Wed 18 Feb 2026 07:18:41
├─ connected: Wed 18 Feb 2026 07:18:41
└─ stored: Wed 18 Feb 2026 06:32:13
├─ policy: auto
└─ key: noI've plugged in a Samsung 970 EVO 512GB nvme drive into the acasis ssd enclosure, and the kernel output shows that nvme is picking it up:
[ 1574.722779] nvme nvme2: pci function 0000:0f:00.0
[ 1574.722790] nvme 0000:0f:00.0: enabling device (0000 -> 0002)Last edited by roryhealy (2026-02-18 07:33:22)
Offline