Thunderbolt Drives disappearing after update

My thunderbolt-connected drives don't show up after updating. I've got a Dr460nized KDE install that's been stable for over a year now, and I just noticed that the drives don't show up in KDE Partion Manger, or anywhere else. The device is Trusted and Connected, but the drives don't show.

I've used the latest LXQT and KDE Dr460nized isos to test, both connect the drives on a fresh install, but after updating, they do not show up again. The dock is still listed as Trusted and Authorized; Connected. But no drives connected show up. So it's not a hardware issue, it's got to be software.

plasma-thunderbolt and bolt do not get updated, they are current at time of install. Something else is happening. The archwiki's thunderbolt page says Installation of the package [linux-zen-e820-patched] which integrates this patch solves the bug. But that fails to build for me on KDE and LXQT (not to mention that it's 4 GiB?!) with an error about the keyring.

Anyone have any idea what could be causing this? Is it something in the Zen kernel? Anyone else have this issue? Just knowing it's not just me would make me feel better lol. I don't really need the drive space, just chasing bugs.

System:
  Kernel: 5.19.10-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
    root=UUID=a963ccdd-1ea3-40f7-963f-70c06d9e408f rw [email protected]
    quiet quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0
    loglevel=3
  Desktop: LXQt v: 1.1.0 tk: Qt v: 5.15.6 info: cairo-dock, lxqt-panel
    wm: kwin_x11 vt: 1 dm: SDDM Distro: Garuda Linux base: Arch Linux
Machine:
  Type: Desktop Mobo: Micro-Star model: MS-1T11 v: REV:1.0
    serial: <superuser required> UEFI: American Megatrends v: E1T11IMS.10F
    date: 01/15/2018
CPU:
  Info: model: Intel Core i7-6700K bits: 64 type: MT MCP arch: Skylake-S
    gen: core 6 level: v3 built: 2015 process: Intel 14nm family: 6
    model-id: 0x5E (94) stepping: 3 microcode: 0xF0
  Topology: cpus: 1x cores: 4 tpc: 2 threads: 8 smt: enabled cache:
    L1: 256 KiB desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB desc: 4x256 KiB
    L3: 8 MiB desc: 1x8 MiB
  Speed (MHz): avg: 1674 high: 4000 min/max: 800/4200 scaling:
    driver: intel_pstate governor: powersave cores: 1: 900 2: 900 3: 4000
    4: 900 5: 899 6: 900 7: 900 8: 4000 bogomips: 63999
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT
    vulnerable
  Type: mds mitigation: Clear CPU buffers; SMT vulnerable
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data mitigation: Clear CPU buffers; SMT vulnerable
  Type: retbleed mitigation: IBRS
  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: IBRS, IBPB: conditional, RSB filling,
    PBRSB-eIBRS: Not affected
  Type: srbds mitigation: Microcode
  Type: tsx_async_abort mitigation: TSX disabled
Graphics:
  Device-1: Intel HD Graphics 530 vendor: Micro-Star MSI driver: i915
    v: kernel arch: Gen-9 process: Intel 14n built: 2015-16 ports: active: none
    empty: DP-1,DP-2 bus-ID: 00:02.0 chip-ID: 8086:1912 class-ID: 0380
  Device-2: NVIDIA GP104M [GeForce GTX 1070 Mobile] vendor: Micro-Star MSI
    driver: nvidia v: 515.76 alternate: nouveau,nvidia_drm non-free: 515.xx+
    status: current (as of 2022-08) arch: Pascal code: GP10x
    process: TSMC 16nm built: 2016-21 pcie: gen: 3 speed: 8 GT/s lanes: 8
    link-max: lanes: 16 bus-ID: 01:00.0 chip-ID: 10de:1ba1 class-ID: 0300
  Display: x11 server: X.Org v: 21.1.4 with: Xwayland v: 22.1.3
    compositor: kwin_x11 driver: X: loaded: modesetting,nvidia
    unloaded: nouveau alternate: fbdev,intel,nv,vesa gpu: i915,nvidia
    display-ID: :0 screens: 1
  Screen-1: 0 s-res: 5120x1440 s-dpi: 108 s-size: 1204x342mm (47.40x13.46")
    s-diag: 1252mm (49.28")
  Monitor-1: DP-2 pos: primary,left res: 2560x1440 hz: 60 dpi: 109
    size: 597x336mm (23.5x13.23") diag: 685mm (26.97") modes: N/A
  Monitor-2: HDMI-0 pos: primary,right res: 2560x1440 hz: 60 dpi: 109
    size: 598x336mm (23.54x13.23") diag: 686mm (27.01") modes: N/A
  Message: Unable to show GL data. Required tool glxinfo missing.
Audio:
  Device-1: Intel 100 Series/C230 Series Family HD Audio
    vendor: Micro-Star MSI driver: snd_hda_intel bus-ID: 1-13.1:4 v: kernel
    bus-ID: 00:1f.3 chip-ID: 046d:0a78 class-ID: 0300 chip-ID: 8086:a170
    class-ID: 0403 serial: <filter>
  Device-2: NVIDIA GP104 High Definition Audio vendor: Micro-Star MSI
    driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 8
    link-max: lanes: 16 bus-ID: 01:00.1 chip-ID: 10de:10f0 class-ID: 0403
  Device-3: Logitech G560 Gaming Speaker type: USB
    driver: hid-generic,snd-usb-audio,usbhid
  Sound Server-1: ALSA v: k5.19.10-zen1-1-zen running: yes
  Sound Server-2: PulseAudio v: 16.1 running: no
  Sound Server-3: PipeWire v: 0.3.58 running: yes
Network:
  Device-1: Qualcomm Atheros Killer E2400 Gigabit Ethernet
    vendor: Micro-Star MSI driver: alx v: kernel pcie: gen: 1 speed: 2.5 GT/s
    lanes: 1 port: c000 bus-ID: 70:00.0 chip-ID: 1969:e0a1 class-ID: 0200
  IF: enp112s0 state: down mac: <filter>
  Device-2: Qualcomm Atheros Killer E2400 Gigabit Ethernet
    vendor: Micro-Star MSI driver: alx v: kernel pcie: gen: 1 speed: 2.5 GT/s
    lanes: 1 port: b000 bus-ID: 71:00.0 chip-ID: 1969:e0a1 class-ID: 0200
  IF: enp113s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  Device-3: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter
    vendor: Rivet Networks Killer Wireless-n/a/ac 1535 driver: ath10k_pci
    v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 bus-ID: 72:00.0
    chip-ID: 168c:003e class-ID: 0280
  IF: wlp114s0 state: down mac: <filter>
Bluetooth:
  Device-1: Qualcomm Atheros QCA61x4 Bluetooth 4.0 type: USB driver: btusb
    v: 0.8 bus-ID: 1-8:2 chip-ID: 0cf3:e300 class-ID: e001
  Report: bt-adapter ID: hci0 rfk-id: 0 state: up address: <filter>
Drives:
  Local Storage: total: 6.71 TiB used: 595.03 GiB (8.7%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung
    model: MZVPV256HDGL-00000 size: 238.47 GiB block-size: physical: 512 B
    logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter>
    rev: BXW7300Q temp: 37.9 C scheme: GPT
  ID-2: /dev/sda maj-min: 8:0 vendor: HGST (Hitachi) model: HTS721010A9E630
    size: 931.51 GiB block-size: physical: 4096 B logical: 512 B
    speed: 6.0 Gb/s type: HDD rpm: 7200 serial: <filter> rev: A3U0
    scheme: GPT
  ID-3: /dev/sdb maj-min: 8:16 type: USB vendor: Samsung model: PSSD T7
    size: 931.51 GiB block-size: physical: 512 B logical: 512 B type: SSD
    serial: <filter> scheme: GPT
  SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
  ID-4: /dev/sdc maj-min: 8:32 type: USB vendor: Seagate
    model: BUP Portable size: 4.55 TiB block-size: physical: 4096 B
    logical: 512 B type: N/A serial: <filter> rev: 0004 scheme: GPT
  ID-5: /dev/sdd maj-min: 8:48 type: USB vendor: SanDisk model: Ultra USB
    3.0 size: 115.69 GiB block-size: physical: 512 B logical: 512 B type: N/A
    serial: <filter> rev: 1.00 scheme: MBR
  SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
  ID-1: / raw-size: 896.82 GiB size: 896.82 GiB (100.00%) used: 11.85 GiB
    (1.3%) fs: btrfs dev: /dev/sdb2 maj-min: 8:18
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%) used: 608 KiB
    (0.2%) fs: vfat dev: /dev/sdb1 maj-min: 8:17
  ID-3: /home raw-size: 896.82 GiB size: 896.82 GiB (100.00%) used: 11.85
    GiB (1.3%) fs: btrfs dev: /dev/sdb2 maj-min: 8:18
  ID-4: /var/log raw-size: 896.82 GiB size: 896.82 GiB (100.00%) used: 11.85
    GiB (1.3%) fs: btrfs dev: /dev/sdb2 maj-min: 8:18
  ID-5: /var/tmp raw-size: 896.82 GiB size: 896.82 GiB (100.00%) used: 11.85
    GiB (1.3%) fs: btrfs dev: /dev/sdb2 maj-min: 8:18
Swap:
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: zram size: 31.26 GiB used: 0 KiB (0.0%) priority: 100
    dev: /dev/zram0
  ID-2: swap-2 type: partition size: 34.39 GiB used: 0 KiB (0.0%)
    priority: -2 dev: /dev/sdb3 maj-min: 8:19
Sensors:
  System Temperatures: cpu: 46.0 C pch: 63.0 C mobo: N/A gpu: nvidia
    temp: 55 C
  Fan Speeds (RPM): N/A
Info:
  Processes: 285 Uptime: 5m wakeups: 0 Memory: 31.27 GiB used: 2.86 GiB
  (9.2%) Init: systemd v: 251 default: graphical tool: systemctl Compilers:
  gcc: 12.2.0 Packages: pm: pacman pkgs: 1204 libs: 317 tools: octopi,paru
  Shell: Bash v: 5.1.16 running-in: qterminal inxi: 3.3.21
Garuda (2.6.7-1):
  System install date:     2022-09-24
  Last full system update: 2022-09-24
  Is partially upgraded:   No
  Relevant software:       NetworkManager
  Windows dual boot:       Probably (Run as root to verify)
  Snapshots:               Snapper
  Failed units:

It sounds like it could be a kernel issue. I read the comment you mentioned in the ArchWiki; the patch submitted to the kernel looks like it is from March, and the linked Bugzilla is all the way from February 2020 so it seems kind of odd that this would just start happening to you now.

In any case, testing the patched kernel I think is a good starting point.

I gave this a shot and ran into presumably the same error. gpg --recv-keys 3B94A80E50A477C7 wasn't good enough; I ended up needing to specify the keyserver as well like so:

gpg --keyserver 'hkps://keys.openpgp.org' --receive-keys  3B94A80E50A477C7

After that I was able to get it to build. Don't forget the headers! :wink:

Try some other kernels too, like linux, linux-mainline, and linux-lts and see if you have any different results.

7 Likes

Yep, it must be an issue with the Zen kernel. Not sure how far back it goes (although it works on linux-zen 5.19.7.zen2-1 which ships in the September iso, but it must have broken somewhere between there and 5.19.10 which is current). I did try some other kernels. linux-xanmod-anbox didn't work, but linux-lts did.

I'll try the keyserver specification tomorrow and add if that works, just for future searches. Thank you for the help!

This is fixed in linux-zen-5.19.11

1 Like

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.