Page 1 of 1
MX-19.4 Thunderbolt Drive not recognized
Posted: Fri Nov 03, 2023 6:13 pm
by woodyb12
My system stats:
Code: Select all
System: Kernel: 5.10.0-5mx-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0
parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.0-5mx-amd64
root=UUID=<filter> ro quiet splash
Desktop: Xfce 4.14.2 tk: Gtk 3.24.5 info: xfce4-panel wm: xfwm 4.14.0 vt: 7
dm: LightDM 1.26.0 Distro: MX-19.4_x64 patito feo March 31 2021
base: Debian GNU/Linux 10 (buster)
Machine: Type: Desktop Mobo: ASRock model: X570 Phantom Gaming-ITX/TB3 serial: <filter>
BIOS: American Megatrends v: P2.80 date: 11/30/2020
CPU: Info: 8-Core model: AMD Ryzen 7 3700X bits: 64 type: MT MCP arch: Zen 2
family: 17 (23) model-id: 71 (113) stepping: 0 microcode: 8701021 cache: L2: 4 MiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
bogomips: 115197
Speed: 3260 MHz min/max: 2200/3600 MHz boost: enabled Core speeds (MHz): 1: 3260
2: 2106 3: 4163 4: 2780 5: 1866 6: 1864 7: 2800 8: 1866 9: 4169 10: 2783 11: 1870
12: 1866 13: 2808 14: 1867 15: 3254 16: 2120
Vulnerabilities: Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: spec_store_bypass
mitigation: Speculative Store Bypass disabled via prctl and seccomp
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2
mitigation: Full AMD retpoline, IBPB: conditional, STIBP: conditional, RSB filling
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics: Device-1: AMD Cape Verde PRO [Radeon HD 7750/8740 / R7 250E] vendor: VISIONTEK
driver: radeon v: kernel alternate: amdgpu bus-ID: 2a:00.0 chip-ID: 1002:683f
class-ID: 0300
Display: x11 server: X.Org 1.20.4 compositor: xfwm4 v: 4.14.0 driver:
loaded: ati,modesetting,radeon unloaded: fbdev,vesa display-ID: :0.0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.0x11.2")
s-diag: 582mm (22.9")
Monitor-1: DisplayPort-0 res: 1920x1080 hz: 60 dpi: 61 size: 800x450mm (31.5x17.7")
diag: 918mm (36.1")
OpenGL: renderer: AMD VERDE (DRM 2.50.0 5.10.0-5mx-amd64 LLVM 7.0.1)
v: 4.5 Mesa 18.3.6 direct render: Yes
Audio: Device-1: AMD Cape Verde/Pitcairn HDMI Audio [Radeon HD 7700/7800 Series]
vendor: VISIONTEK Oland/Hainan/Cape driver: snd_hda_intel v: kernel bus-ID: 2a:00.1
chip-ID: 1002:aab0 class-ID: 0403
Device-2: AMD Starship/Matisse HD Audio vendor: ASRock driver: snd_hda_intel
v: kernel bus-ID: 2c:00.4 chip-ID: 1022:1487 class-ID: 0403
Sound Server-1: ALSA v: k5.10.0-5mx-amd64 running: yes
Sound Server-2: PulseAudio v: 12.2 running: yes
Network: Device-1: Intel driver: iwlwifi v: kernel modules: wl port: N/A bus-ID: 25:00.0
chip-ID: 8086:2723 class-ID: 0280
IF: wlan0 state: up mac: <filter>
Device-2: Intel I211 Gigabit Network vendor: ASRock driver: igb v: kernel port: e000
bus-ID: 26:00.0 chip-ID: 8086:1539 class-ID: 0200
IF: eth0 state: down mac: <filter>
Bluetooth: Device-1: Intel type: USB driver: btusb v: 0.8 bus-ID: 5-2:2 chip-ID: 8087:0029
class-ID: e001
Report: hciconfig ID: hci0 rfk-id: 1 state: up address: <filter>
Info: acl-mtu: 1021:4 sco-mtu: 96:6 link-policy: rswitch sniff
link-mode: slave accept service-classes: rendering, capturing, object transfer
Drives: Local Storage: total: 465.76 GiB used: 90.94 GiB (19.5%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Sabrent model: Rocket 4.0 500GB
size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s lanes: 4
type: SSD serial: <filter> rev: RKT401.3 temp: 65.8 C scheme: GPT
Partition: ID-1: / raw-size: 32.1 GiB size: 31.34 GiB (97.65%) used: 13.5 GiB (43.1%) fs: ext4
dev: /dev/nvme0n1p2 maj-min: 259:1
ID-2: /home raw-size: 361.66 GiB size: 354.92 GiB (98.14%) used: 77.44 GiB (21.8%)
fs: ext4 dev: /dev/nvme0n1p3 maj-min: 259:2
Swap: Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: partition size: 72 GiB used: 0 KiB (0.0%) priority: -2
dev: /dev/nvme0n1p4 maj-min: 259:3
Sensors: System Temperatures: cpu: 74.1 C mobo: N/A gpu: radeon temp: 71.0 C
Fan Speeds (RPM): N/A
Repos: Packages: note: see --pkg apt: 2372 lib: 1225 flatpak: 0
No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
1: deb http://deb.debian.org/debian buster-updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://deb.debian.org/debian buster main contrib non-free
2: deb http://deb.debian.org/debian-security buster/updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/google-chrome.list
1: deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/ buster main non-free
No active apt repos in: /etc/apt/sources.list.d/various.list
Info: Processes: 366 Uptime: 9m wakeups: 1 Memory: 62.8 GiB used: 3.79 GiB (6.0%)
Init: SysVinit v: 2.93 runlevel: 5 default: 5 tool: systemctl Compilers: gcc: 8.3.0
alt: 8 Shell: quick-system-in default: Bash v: 5.0.3 running-in: quick-system-in
inxi: 3.3.06
I just received my Ankmax SSD enclosure [Thunderbolt 4/3] and installed a[n] SSD into it and it is not showing up in File Manager. I have tried to set the BIOS (at least temporarily to no security) to see if that
might be a problem. Not the problem. Then I enabled IOMMU, and that doesn't solve anything either. What else should I do?
Re: MX-19.4 Thunderbolt Drive not recognized
Posted: Sat Nov 04, 2023 12:54 pm
by CharlesV
I believe that kernel will allow thunderbolt, have you added thunderbolt drivers? ( bolt and thunderbolt-tools as I recall)
Re: MX-19.4 Thunderbolt Drive not recognized
Posted: Sun Nov 05, 2023 3:05 am
by woodyb12
@CharlesV So, how do I know if they are loaded? And if they are not; How to?? I just did an lsmod and I see 2 NVMe modules nvme-core and nvme.
I got it to work! But I still can't boot from the drive. Am I missing something? ( like maybe grub-update or something?)
Re: MX-19.4 Thunderbolt Drive not recognized
Posted: Sun Nov 05, 2023 9:28 am
by woodyb12
I just discovered a[n] MX tool called "CHroot-rescue" and it found my external drive with MX-21 Wildflower installed. So; what do I do next? How do I update the Grub thingy? (or just update the grub menu on my"internal" MX-19 O.S?).
Re: MX-19.4 Thunderbolt Drive not recognized
Posted: Sun Nov 05, 2023 11:31 am
by CharlesV
If you have an existing MX load on it, AND there is a grub on it too, then al lyou need to do is to tell your bios to boot from it. And as long as you bios understands how to reach that drive, you should be off and going.
if your trying to integrate that drive in to your existing grub, then there is a method, however I am not the one to attempt to lead you through that one.
Re: MX-19.4 Thunderbolt Drive not recognized
Posted: Tue Nov 07, 2023 5:38 pm
by woodyb12
I have just received my OWC Thunderbolt dock today. I wanted to see if that would help with my problem; However, it just causes more problems. While using Thunderbolt devices in Linux is supported, nothing seems to have changed. No devices appear to attach. So, I abused google and found a couple articles:
https://christian.kellner.me/2017/12/14 ... -gnulinux/ and another:
https://wiki.archlinux.org/title/Thunderbolt. So; then I went into mxpi and found two packages: "bolt" and "thunderbolt-tools".
I just don't know how to use them.
Still need help!
Re: MX-19.4 Thunderbolt Drive not recognized
Posted: Tue Nov 07, 2023 5:53 pm
by CharlesV
So, with the drive directly connected to the computer, reboot and go into your bios. Do you see an option to boot from that device? If so.. choose that and see if it boots.
If no choice for booting onto that usb drive, then make sure you see the drive in the bios.
And does an lsusb show the drive when it is connected ?
Re: MX-19.4 Thunderbolt Drive not recognized
Posted: Tue Nov 07, 2023 6:02 pm
by woodyb12
Code: Select all
woody@Lil-Monstr:~
$ lsusb
Bus 008 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 002: ID 8087:0029 Intel Corp.
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 002: ID 0bc2:3343 Seagate RSS LLC
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 003: ID 062a:650a MosArt Semiconductor Corp.
Bus 003 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
this is what lsusb outputs.
Re: MX-19.4 Thunderbolt Drive not recognized
Posted: Tue Nov 07, 2023 6:10 pm
by CharlesV
Am I correct in that I do not see that Ankmax ssd controller connected ?
Re: MX-19.4 Thunderbolt Drive not recognized
Posted: Tue Nov 07, 2023 6:37 pm
by woodyb12
lspci command output:
Code: Select all
woody@Lil-Monstr:~
$ lspci
00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Root Complex
00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
00:01.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge
00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
00:03.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge
00:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
00:05.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
00:07.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
00:07.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B]
00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B]
00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 61)
00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51)
00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 0
00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 1
00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 2
00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 3
00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 4
00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 5
00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 6
00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 7
01:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 57ad
02:01.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 57a3
02:02.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 57a3
02:04.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 57a3
02:05.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 57a3
02:08.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 57a4
02:09.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 57a4
02:0a.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 57a4
03:00.0 Non-Volatile memory controller: Phison Electronics Corporation Device 5016 (rev 01)
04:00.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 2C 2018] (rev 06)
05:00.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 2C 2018] (rev 06)
05:01.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 2C 2018] (rev 06)
05:02.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 2C 2018] (rev 06)
06:00.0 System peripheral: Intel Corporation JHL7540 Thunderbolt 3 NHI [Titan Ridge 2C 2018] (rev 06)
08:00.0 USB controller: Intel Corporation JHL7540 Thunderbolt 3 USB Controller [Titan Ridge 2C 2018] (rev 06)
25:00.0 Network controller: Intel Corporation Device 2723 (rev 1a)
26:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network Connection (rev 03)
27:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP
27:00.1 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller
27:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller
28:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51)
29:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51)
2a:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde PRO [Radeon HD 7750/8740 / R7 250E]
2a:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde/Pitcairn HDMI Audio [Radeon HD 7700/7800 Series]
2b:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Function
2c:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP
2c:00.1 Encryption controller: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Cryptographic Coprocessor PSPCPP
2c:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller
2c:00.4 Audio device: Advanced Micro Devices, Inc. [AMD] Starship/Matisse HD Audio Controller
Looks like everything is registered. I can't see the SSD in file explorer, much less boot from it.
Re: MX-19.4 Thunderbolt Drive not recognized
Posted: Tue Nov 07, 2023 6:41 pm
by woodyb12
How are people supposed to "authorize" a thunderbolt connection for something like an SSD if there is "no dialog" to respond to????
Re: MX-19.4 Thunderbolt Drive not recognized
Posted: Tue Nov 07, 2023 6:48 pm
by CharlesV
What model # is that Ankmax SSD enclosure ? Unless I am not reading this right, it looks like you have a Thunderbolt 4 device in a Thunderbolt 3 bridge ?
Re: MX-19.4 Thunderbolt Drive not recognized
Posted: Wed Nov 08, 2023 9:41 pm
by woodyb12
Hello again Ladies and Gentlemen! I recently discovered a program called "boltctl." I typed "thunderbolt" into the mxpi and got two results. The other was a program that Intel (obliviously) stopped maintaining a long time ago. But it's similar to "boltctl." I have some output that I would like for you all to see:
Code: Select all
woody@Lil-Monstr:~
$ boltctl list -a
● ASRock X570 Phantom Gaming-ITX/TB3
├─ type: host
├─ name: X570 Phantom Gaming-ITX/TB3
├─ vendor: ASRock
├─ uuid: c6030000-0082-840e-03e7-403fcae34901
├─ status: authorized
│ ├─ domain: c6030000-0082-840e-03e7-403fcae34901
│ └─ authflags: nokey
├─ authorized: Thu 09 Nov 2023 01:56:36 AM UTC
├─ connected: Thu 09 Nov 2023 01:56:36 AM UTC
└─ stored: no
● Other World Computing Thunderbolt Hub
├─ type: peripheral
├─ name: Thunderbolt Hub
├─ vendor: Other World Computing
├─ uuid: 0093f808-c403-8780-ffff-ffffffffffff
├─ status: connected
│ ├─ domain: c6030000-0082-840e-03e7-403fcae34901
│ └─ authflags: none
├─ connected: Thu 09 Nov 2023 01:56:36 AM UTC
└─ stored: no
woody@Lil-Monstr:~
$ boltctl authorize 0093f808-c403-8780-ffff-ffffffffffff
woody@Lil-Monstr:~
$ boltctl monitor 0093f808-c403-8780-ffff-ffffffffffff
Bolt Version : 0.7
Daemon API : 1
Client API : 1
Security Level: secure
Auth Mode : enabled
Ready
Probing started
DeviceAdded: /org/freedesktop/bolt/devices/00d78148_33a7_2500_ffff_ffffffffffff
Probing done
[0093f808-c403-8780-ffff-ffffffffffff] Thunderbolt Hub | storetime -> 1699495580
[0093f808-c403-8780-ffff-ffffffffffff] Thunderbolt Hub | key -> BOLT_KEY_MISSING
[0093f808-c403-8780-ffff-ffffffffffff] Thunderbolt Hub | policy -> BOLT_POLICY_AUTO
[0093f808-c403-8780-ffff-ffffffffffff] Thunderbolt Hub | stored -> TRUE
But wait! There's more:
Code: Select all
woody@Lil-Monstr:~
$ boltctl enroll 0093f808-c403-8780-ffff-ffffffffffff
● Other World Computing Thunderbolt Hub
├─ type: peripheral
├─ name: Thunderbolt Hub
├─ vendor: Other World Computing
├─ uuid: 0093f808-c403-8780-ffff-ffffffffffff
├─ dbus path: /org/freedesktop/bolt/devices/0093f808_c403_8780_ffff_ffffffffffff
├─ status: authorized
│ ├─ domain: c6030000-0082-840e-03e7-403fcae34901
│ ├─ parent: c6030000-0082-840e-03e7-403fcae34901
│ ├─ syspath: /sys/devices/pci0000:00/0000:00:01.2/0000:01:00.0/0000:02:02.0/0000:04:00.0/0000:05:00.0/0000:06:00.0/domain0/0-0/0-1
│ └─ authflags: none
├─ authorized: Thu 09 Nov 2023 02:03:21 AM UTC
├─ connected: Thu 09 Nov 2023 01:56:36 AM UTC
└─ stored: Thu 09 Nov 2023 02:06:20 AM UTC
├─ policy: auto
└─ key: no
woody@Lil-Monstr:~
$ boltctl power 0093f808-c403-8780-ffff-ffffffffffff
acquired power guard (7)
^C
woody@Lil-Monstr:~
$ boltctl info 0093f808-c403-8780-ffff-ffffffffffff
● Other World Computing Thunderbolt Hub
├─ type: peripheral
├─ name: Thunderbolt Hub
├─ vendor: Other World Computing
├─ uuid: 0093f808-c403-8780-ffff-ffffffffffff
├─ dbus path: /org/freedesktop/bolt/devices/0093f808_c403_8780_ffff_ffffffffffff
├─ status: authorized
│ ├─ domain: c6030000-0082-840e-03e7-403fcae34901
│ ├─ parent: c6030000-0082-840e-03e7-403fcae34901
│ ├─ syspath: /sys/devices/pci0000:00/0000:00:01.2/0000:01:00.0/0000:02:02.0/0000:04:00.0/0000:05:00.0/0000:06:00.0/domain0/0-0/0-1
│ └─ authflags: none
├─ authorized: Thu 09 Nov 2023 02:03:21 AM UTC
├─ connected: Thu 09 Nov 2023 01:56:36 AM UTC
└─ stored: Thu 09 Nov 2023 02:06:20 AM UTC
├─ policy: auto
└─ key: no
woody@Lil-Monstr:~
$
And just one more for the road:
Code: Select all
woody@Lil-Monstr:~
$ boltctl list
● Ankmax UC4M2
├─ type: peripheral
├─ name: UC4M2
├─ vendor: Ankmax
├─ uuid: 00d78148-33a7-2500-ffff-ffffffffffff
├─ status: connected
│ ├─ domain: c6030000-0082-840e-03e7-403fcae34901
│ └─ authflags: none
├─ connected: Wed 08 Nov 2023 04:08:12 PM UTC
└─ stored: no
woody@Lil-Monstr:~
$ boltctl enroll 00d78148-33a7-2500-ffff-ffffffffffff
● Ankmax UC4M2
├─ type: peripheral
├─ name: UC4M2
├─ vendor: Ankmax
├─ uuid: 00d78148-33a7-2500-ffff-ffffffffffff
├─ dbus path: /org/freedesktop/bolt/devices/00d78148_33a7_2500_ffff_ffffffffffff
├─ status: authorized
│ ├─ domain: c6030000-0082-840e-03e7-403fcae34901
│ ├─ parent: c6030000-0082-840e-03e7-403fcae34901
│ ├─ syspath: /sys/devices/pci0000:00/0000:00:01.2/0000:01:00.0/0000:02:02.0/0000:04:00.0/0000:05:00.0/0000:06:00.0/domain0/0-0/0-1
│ └─ authflags: none
├─ authorized: Wed 08 Nov 2023 04:12:04 PM UTC
├─ connected: Wed 08 Nov 2023 04:08:12 PM UTC
└─ stored: Wed 08 Nov 2023 04:12:04 PM UTC
├─ policy: auto
└─ key: no
woody@Lil-Monstr:~
$ boltctl authorize 00d78148-33a7-2500-ffff-ffffffffffff
woody@Lil-Monstr:~
$ boltctl domain
boltctl: error: Invalid command: domain
Try "boltctl --help" for more information.
woody@Lil-Monstr:~
$ boltctl domains
● domain0 c6030000-0082-840e-03e7-403fcae34901
├─ bootacl: 1/16
│ └─[0] 00d78148-33a7-2500-ffff-ffffffffffff
└─ security: user
woody@Lil-Monstr:~
$ boltctl monitor
Bolt Version : 0.7
Daemon API : 1
Client API : 1
Security Level: user
Auth Mode : enabled
Ready
^C
woody@Lil-Monstr:~
$ boltctl power
acquired power guard (7)
^C
woody@Lil-Monstr:~
$ boltctl config --describe
boltctl: error: Invalid command: config
Try "boltctl --help" for more information.
woody@Lil-Monstr:~
$ boltctl --describe
boltctl: error: Unknown option --describe
Try "boltctl --help" for more information.
woody@Lil-Monstr:~
$ boltctl list -a
● ASRock X570 Phantom Gaming-ITX/TB3
├─ type: host
├─ name: X570 Phantom Gaming-ITX/TB3
├─ vendor: ASRock
├─ uuid: c6030000-0082-840e-03e7-403fcae34901
├─ status: authorized
│ ├─ domain: c6030000-0082-840e-03e7-403fcae34901
│ └─ authflags: none
├─ authorized: Wed 08 Nov 2023 10:56:56 AM UTC
├─ connected: Wed 08 Nov 2023 10:56:56 AM UTC
└─ stored: no
● Ankmax UC4M2
├─ type: peripheral
├─ name: UC4M2
├─ vendor: Ankmax
├─ uuid: 00d78148-33a7-2500-ffff-ffffffffffff
├─ status: authorized
│ ├─ domain: c6030000-0082-840e-03e7-403fcae34901
│ └─ authflags: none
├─ authorized: Wed 08 Nov 2023 04:12:04 PM UTC
├─ connected: Wed 08 Nov 2023 04:08:12 PM UTC
└─ stored: Wed 08 Nov 2023 04:12:04 PM UTC
├─ policy: auto
└─ key: no
woody@Lil-Monstr:~
$ boltctl monitor
Bolt Version : 0.7
Daemon API : 1
Client API : 1
Security Level: user
Auth Mode : enabled
Ready
[00d78148-33a7-2500-ffff-ffffffffffff] UC4M2 | status -> BOLT_STATUS_DISCONNECTED
[00d78148-33a7-2500-ffff-ffffffffffff] UC4M2 | domain ->
[00d78148-33a7-2500-ffff-ffffffffffff] UC4M2 | syspath ->
[00d78148-33a7-2500-ffff-ffffffffffff] UC4M2 | parent ->
Probing started
[00d78148-33a7-2500-ffff-ffffffffffff] UC4M2 | authtime -> 0
[00d78148-33a7-2500-ffff-ffffffffffff] UC4M2 | conntime -> 1699460605
[00d78148-33a7-2500-ffff-ffffffffffff] UC4M2 | authflags -> BOLT_AUTH_NONE
[00d78148-33a7-2500-ffff-ffffffffffff] UC4M2 | status -> BOLT_STATUS_CONNECTED
[00d78148-33a7-2500-ffff-ffffffffffff] UC4M2 | domain -> c6030000-0082-840e-03e7-403fcae34901
[00d78148-33a7-2500-ffff-ffffffffffff] UC4M2 | syspath -> /sys/devices/pci0000:00/0000:00:01.2/0000:01:00.0/0000:02:02.0/0000:04:00.0/0000:05:00.0/0000:06:00.0/domain0/0-0/0-1
[00d78148-33a7-2500-ffff-ffffffffffff] UC4M2 | parent -> c6030000-0082-840e-03e7-403fcae34901
[00d78148-33a7-2500-ffff-ffffffffffff] UC4M2 | status -> BOLT_STATUS_AUTHORIZING
[00d78148-33a7-2500-ffff-ffffffffffff] UC4M2 | status -> BOLT_STATUS_AUTHORIZED
[00d78148-33a7-2500-ffff-ffffffffffff] UC4M2 | authtime -> 1699460606
Probing done
---------------------------------------------------
This is a beautiful discovery!!
But I still can't see, or, access my SSD.
Any ideas? Where do I go from here??
I just went to the Debian website and found the (meager) docs on "thunderbolt-tools." I have some more output files for everyone to view:
Code: Select all
woody@Lil-Monstr:~
$ tbtadm topology
Controller 0
├─ Details:
│ ├─ Name: X570 Phantom Gaming-ITX/TB3, ASRock
│ └─ Security level: SL2 (secure)
│
└─ Thunderbolt Hub, Other World Computing
├─ Details:
│ ├─ Route-string: 0-1
│ ├─ Authorized: Yes
│ ├─ In ACL: Yes
│ └─ UUID: 0093f808-c403-8780-ffff-ffffffffffff
│
└─ UC4M2, Ankmax
└─ Details:
├─ Route-string: 0-501
├─ Authorized: Yes
├─ In ACL: Yes
└─ UUID: 00d78148-33a7-2500-ffff-ffffffffffff
Next:
woody@Lil-Monstr:~
$ tbtadm acl
0093f808-c403-8780-ffff-ffffffffffff Other World Computing Thunderbolt Hub connected
00d78148-33a7-2500-ffff-ffffffffffff Ankmax UC4M2 connected
One more:
woody@Lil-Monstr:~
$ tbtadm approve-all
Found domain "/sys/bus/thunderbolt/devices/domain0"
Found child "/sys/bus/thunderbolt/devices/domain0/0-0/0-1"
Authorizing "/sys/bus/thunderbolt/devices/domain0/0-0/0-1"
Already authorized
Found child "/sys/bus/thunderbolt/devices/domain0/0-0/0-1/0-501"
Authorizing "/sys/bus/thunderbolt/devices/domain0/0-0/0-1/0-501"
Already authorized
I still can't access my SSDs!!
Re: MX-19.4 Thunderbolt Drive not recognized
Posted: Sat Nov 11, 2023 9:13 pm
by woodyb12
Calling all Dolphins! I got a new thunderbolt dock. This time it is a TB3 Dock. It was working [partially] and I got to messing with the "boltctl" and "tbtadmin" utilities and lost connection with all of the Dock. I have been working on this issue for some time now with not much relief. There is not very much documentation on the net. But I may be "looking for Love in all the wrong places!"
You can follow the effort that I have put into this problem by looking at my post(s). I am doing everything I possibly can. I have been to product support sites; as well as e-mail and phone calls. No one can say that I haven't put in some effort! Please help. I really need these SSDs to sort through a "lot" of documents and personal stuff. So I need these fast storage devices.
Thanks for everything everybody. I do love this community.
Re: MX-19.4 Thunderbolt Drive not recognized
Posted: Sun Nov 12, 2023 8:31 am
by woodyb12
Here are some more stats from my new CalDigit Thunderbolt 3 Dock!
Code: Select all
Saturday Night 11-11-2023 @ 11:59p.m.
woody@Lil-Monstr:~
$ tbtadm topology
Controller 0
├─ Details:
│ ├─ Name: X570 Phantom Gaming-ITX/TB3, ASRock
│ └─ Security level: SL1 (user)
│
└─ TS3 Plus, CalDigit, Inc.
├─ Details:
│ ├─ Route-string: 0-1
│ ├─ Authorized: Yes
│ ├─ In ACL: Yes
│ └─ UUID: 00292a5c-46d4-3d00-ffff-ffffffffffff
│
└─ UC4M2, Ankmax
└─ Details:
├─ Route-string: 0-301
├─ Authorized: Yes
├─ In ACL: Yes
└─ UUID: 00d78148-33a7-2500-ffff-ffffffffffff
woody@Lil-Monstr:~
$ boltctl info 00292a5c-46d4-3d00-ffff-ffffffffffff
● CalDigit, Inc. TS3 Plus
├─ type: peripheral
├─ name: TS3 Plus
├─ vendor: CalDigit, Inc.
├─ uuid: 00292a5c-46d4-3d00-ffff-ffffffffffff
├─ dbus path: /org/freedesktop/bolt/devices/00292a5c_46d4_3d00_ffff_ffffffffffff
├─ status: authorized
│ ├─ domain: c6030000-0082-840e-03e7-403fcae34901
│ ├─ parent: c6030000-0082-840e-03e7-403fcae34901
│ ├─ syspath: /sys/devices/pci0000:00/0000:00:01.2/0000:01:00.0/0000:02:02.0/0000:04:00.0/0000:05:00.0/0000:06:00.0/domain0/0-0/0-1
│ └─ authflags: none
├─ authorized: Sun 12 Nov 2023 03:35:28 AM UTC
├─ connected: Sun 12 Nov 2023 03:35:28 AM UTC
└─ stored: Sun 12 Nov 2023 04:02:57 AM UTC
├─ policy: auto
└─ key: no
woody@Lil-Monstr:~
$ boltctl info 00d78148-33a7-2500-ffff-ffffffffffff
● Ankmax UC4M2
├─ type: peripheral
├─ name: UC4M2
├─ vendor: Ankmax
├─ uuid: 00d78148-33a7-2500-ffff-ffffffffffff
├─ dbus path: /org/freedesktop/bolt/devices/00d78148_33a7_2500_ffff_ffffffffffff
├─ status: authorized
│ ├─ domain: c6030000-0082-840e-03e7-403fcae34901
│ ├─ parent: 00292a5c-46d4-3d00-ffff-ffffffffffff
│ ├─ syspath: /sys/devices/pci0000:00/0000:00:01.2/0000:01:00.0/0000:02:02.0/0000:04:00.0/0000:05:00.0/0000:06:00.0/domain0/0-0/0-1/0-301
│ └─ authflags: none
├─ authorized: Sun 12 Nov 2023 03:57:26 AM UTC
├─ connected: Sun 12 Nov 2023 03:57:26 AM UTC
└─ stored: Sat 11 Nov 2023 04:53:09 PM UTC
├─ policy: auto
└─ key: no
I am going to ask what may appear to some as a "weird" question: If I could somehow use a BSD package; or, in the alternative, a Darwin (Mac) package in Linux -- to solve this problem? It's hard for me to imagine that @Dolphin and @Anticapitolista haven't researched this already. Now, I
know that person(s) can use Linux stuff in BSD(Free), but, I don't know if the "reverse " is true. I also
know that Apple(Mac) is "based" on BSD(Darwin). I know that Linux and BSD are
both "POSIX" compliant....etc., and I
know that Microsoft and Apple are given "preference" from manufacturer(s) of
EVERYTHING hardware related in the "Computer" world; but, that has only made those of us who choose the "Freedom" of Open-Source software to be more determined to show that "ours" IS a Better World!
I also believe that if we(Together) can solve this problem [And I am very confident that I am not the only one who finds this s*it confusing] this would be a "Great Advancement"; not just for MX-Brand, but, for the entire Linux community.
So! Please take me "seriously." I may be a "hillbilly," but that doesn't make me "stupid!"
Check out this video; it explains the difficulty of Thunderbolt :
Code: Select all
https://papers.freebsd.org/2020/bsdcan/long-thunderbolt_on_freebsd/
This guy is very smart, and even he is still trying to figure some things out! So! I know this isn't an "easy" subject! Thanks all!
Se also:
Code: Select all
https://people.freebsd.org/~scottl/
Re: MX-19.4 Thunderbolt Drive not recognized
Posted: Sun Nov 12, 2023 11:32 am
by CharlesV
That is probably about the perfect way to brick your system.
Again, What model # is that Ankmax SSD enclosure ?
And have you tried the enclosure OUT of a dock?
Re: MX-19.4 Thunderbolt Drive not recognized
Posted: Sun Nov 12, 2023 11:57 am
by woodyb12
Here is the Model: Ankmax UC4M2. It was working without [and with] the dock when I first got the CalDigit Dock. But the other SSD was not. It is also an [different] Ankmax enclosure. It was working without the Dock; However I couldn't get them both to work at the same time. The other enclosure is a model UC31M2. Got them both on Amazon. Now neither one of them work with or without the Dock. I just now received [in the mail] a USB-A to USB-C type cable and the Ankmax UC31M2 works (without the Dock of course!). But nothing is working on the Dock!
Re: MX-19.4 Thunderbolt Drive not recognized
Posted: Sun Nov 12, 2023 12:06 pm
by CharlesV
So both units will work, just not at the same time?
THAT may be a complication of your bios and the thunderbolt port. I have seen this on USB-C a few times now where it will work with one high speed device, but not two.
Re: MX-19.4 Thunderbolt Drive not recognized
Posted: Sun Nov 12, 2023 12:14 pm
by woodyb12
I got the UC31M2 to work on the machine(USB 3.2-2 port) with a new cable (USB 3.2-2 USB-A to USB-C cable. But nothing works on the Dock! Hah! I just got the other enclosure to work with the same cable! [ I just got this cable today from Amazon!]. Do you suppose that these are NOT Thunderbolt enclosures?? Even though the UC4M2 enclosure shows up in the "boltctl" and the "tbtadm" programs both recognized it and not the other?? I suspected that the UC31M2 might be USB-3.2-2!
Re: MX-19.4 Thunderbolt Drive not recognized
Posted: Sun Nov 12, 2023 12:24 pm
by CharlesV
Very possible... and NOT all cables are the same quality either! It is possible there is a problem with a cable too.
Re: MX-19.4 Thunderbolt Drive not recognized
Posted: Sun Nov 12, 2023 12:29 pm
by woodyb12
Well! I have tried other TB3 cables, with no luck. Besides, if it were the cables, how would the commands recognize the devices?? Both the Dock AND the Enclosure??
Re: MX-19.4 Thunderbolt Drive not recognized
Posted: Sun Nov 12, 2023 12:32 pm
by CharlesV
true -
Edited Well.. MAYBE true... it is possible that the cable would allow recognition but not data passing at a rate that would support the device. I have seen several usb cables like this - several phones come to mind immediately. The phones shipped with cables that would power the device - and the computer would SEE the device, but no data was able to be passed through those cables.
Re: MX-19.4 Thunderbolt Drive not recognized
Posted: Sun Nov 12, 2023 12:35 pm
by woodyb12
Do the "commands" under tbtadm and boltctl affect the Dock itself? Or just the Kernel module? I ask because I know that Dock makers issue "updates" for their Docks; but I don't know if they are hardware or software updates.
Re: MX-19.4 Thunderbolt Drive not recognized
Posted: Sun Nov 12, 2023 12:37 pm
by CharlesV
I would assume the kernel / os, but I dont really know that.
Re: MX-19.4 Thunderbolt Drive not recognized
Posted: Sun Nov 12, 2023 12:56 pm
by woodyb12
Is there a way to reinstall the Kernel module without rebooting or compiling( I don't know how to compile a Letter, much less a Kernel module!
While doing research to try to figure this problem out I came across some skimpy info about how these Docks use IOMMU. Do I need to set IOMMU in the BIOS?
Re: MX-19.4 Thunderbolt Drive not recognized
Posted: Sun Nov 12, 2023 1:06 pm
by woodyb12
Thunderbolt technology should not be this difficult! It is supposed to be similar in function to the USB specification. Plug and Play! Albeit; with authentication.
Re: MX-19.4 Thunderbolt Drive not recognized
Posted: Sun Nov 12, 2023 1:35 pm
by CharlesV
woodyb12 wrote: ↑Sun Nov 12, 2023 12:56 pm
Is there a way to reinstall the Kernel module without rebooting or compiling( I don't know how to compile a Letter, much less a Kernel module!
While doing research to try to figure this problem out I came across some skimpy info about how these Docks use IOMMU. Do I need to set IOMMU in the BIOS?
No, I do not believe you should have too. And you need to be very wary when you are looking at internet articles... There are many people that say how to do something, and really do not know. (There are many that do too.. but you have to be careful.)
The fact that you can see and work with ONE unit at a time, is a serious clue - it IS working... so something else is happening here when a second unit it connected.
Re: MX-19.4 Thunderbolt Drive not recognized
Posted: Sun Nov 12, 2023 1:52 pm
by woodyb12
The Dock worked once. But not with both drives. The Dock never recognized Thumb Drives, SD cards, or anything else; except once I got the UC4M2 Ankmax enclosure to work. But that was it!
Also, I don't just "do" what is suggested to me from users. I am very "paranoid" about that. I realize that there are many people (who are honest and wish to be helpful) who are "well meaning", but who have very little experience with REAL technology issues. I can usually tell them apart. I have gotten both of the SSD enclosures to work directly from the machines' USB 3.2 Gen-2 port. But I am in great need of multiple port(s) SSD's for organizing a huge backlog of files. I am considering this item from Amazon:
https://www.amazon.com/dp/B0C6L2BG6T/?c ... lig_dp_it.. What do you think?
I have an OWC (Thunderbolt-4) Dock with the same issues; but, I got this Dock (Thunderbolt-3 ) because I thought it was just that the Thunderbolt-3 on my computer was "incompatible" with the Thunderbolt-4 Dock. I guess I was wrong about that!!
Re: MX-19.4 Thunderbolt Drive not recognized
Posted: Sun Nov 12, 2023 2:01 pm
by CharlesV
Excellent on being cautious. I always hate to say that, but unfortunately caution is required ;-/
I prefer Anker Dock's actually, had VERY good luck with them. There are a few that are more driven for HDMI use, etc, but some have some are geared more for multiple connections. I will try to find the one I have used in the past, but not sure I have used one for thunderbolt connections - except for on a mac.
Re: MX-19.4 Thunderbolt Drive not recognized
Posted: Sun Nov 12, 2023 2:04 pm
by woodyb12
I like Anker products too! But I didn't see anything I thought I could use for what I needed. I buy (almost) exclusively @ Amazon. Have been a "Prime Member" since 2016. It has perks that I have come to depend on! Like ALL of my electronics covered by one insurance plan, free returns,etc.
Re: MX-19.4 Thunderbolt Drive not recognized
Posted: Sun Nov 12, 2023 2:12 pm
by woodyb12
I can even go to Amazon and get "invoices" for products I bought in 2016! Ha! Isn't that something?? I love Amazon as much as I love the MX community! You guys (and I'm sure there are Gals too!) are the best Linux people I've ever met! I mean that too! I have been using Linux since around 1986 (off and on); and believe me when I tell you; the linux community then was very harsh with "newbies!"
Re: MX-19.4 Thunderbolt Drive not recognized
Posted: Sun Nov 12, 2023 2:37 pm
by CharlesV
Ya, amazon is awesome. I really hope the DOJ and others dont mess it up ;-/
And I agree with your take on the MX forum too. I started playing with linux around 1992 ish, and as I attempted to use it a few years later I was pretty turned off by the harsh attitudes and various problem peeps in forums. I pretty much stopped using forums in 2010, just gave up on the lack of good people and bad advise. Honestly, this forum, the Mint forum and the xfce forum are all I am ever really on - everything else is a search and spot check. (and I pretty much never go into windows forums - even though support many windows users.)
Re: MX-19.4 Thunderbolt Drive not recognized
Posted: Sun Nov 12, 2023 3:11 pm
by CharlesV
A few more thoughts on this ...
Your bios is quite old and you may want to read through some release notes or just head for a newer version. (10/26/23 was their last update for your mobo. )
https://pg.asrock.com/mb/AMD/X570%20Pha ... x.asp#BIOS
You also may want to do some reading here:
https://www.kernel.org/doc/html/v4.15/a ... rbolt.html
And last, you are on a 5.10 kernel, and while everything I can find says it supports Thunderbolt... you may just want to try a newer kernel. (Also .. it might be smart to head for a mx21 or mx23 load too. ) And, personally... I would add ahs and get the very latest linux firmware on board too.
Re: MX-19.4 Thunderbolt Drive not recognized
Posted: Sun Nov 12, 2023 5:07 pm
by woodyb12
I updated my BIOS; That's why (I think) the TB-3 Dock worked at all after I did that. I did read the article you referenced above; didn't have much information useful to me. And the last thing:
I have no clue how to upgrade to MX-23 and keep all of my files, programs, and settings. So! Unless you want to babysit me through that stuff; Not Happening!
Re: MX-19.4 Thunderbolt Drive not recognized [Solved]
Posted: Sun Nov 12, 2023 5:15 pm
by CharlesV
There are some methods to reduce the pain, but it will some work to do it and no guarantee it will help this particular issue either. ( Might be worth building a stick of mx23 and trying it though.)
Re: MX-19.4 Thunderbolt Drive not recognized
Posted: Sun Nov 12, 2023 7:39 pm
by woodyb12
I have many versions of MX-Linux! I plan on trying several different versions of different Distributions. But I tend to prefer Debian based systems. But, I don't want to have to give up everything I've worked hard to achieve with this version of MX! All the programs I've installed to accomplish the things "I" want to do. I would almost rather eat sh!t--I mean "straight out O the Toilet!"
I will just try a few Distros and if I find one that works well with this Dock; I will use that on a thumb drive and move my files around that way!
So! I guess I will close this thread and mark it as "solved!" Thanks for your help @CharlesV!