Thunderbolt dock authorized, but not working

Hi,

recently my thunderbolt-3-dock stopped working.
I am not sure, what the main cause could be. Meanwhile there was a bios update, which could be a good cause-candidate btw.

I connected, authorized (boltctl) and removed the device multiple times, tested different thunderbolt-security settings, but nothing worked.
Only the external display is working, connected over displayport.

In Windows the dock still works as expected.

Is there some kind of another "reset" I could try, to make it work again?

System:    Host: luke-pc Kernel: 5.7.0-3-MANJARO x86_64 bits: 64 compiler: gcc v: 10.1.0 Desktop: i3 4.18.1 
           Distro: Manjaro Linux 
Machine:   Type: Laptop System: Schenker product: XMG FUSION 15 (XFU15L19) v: Late 2019 serial: <root required> 
           Mobo: Intel model: LAPQC71A v: K54899-303 serial: <root required> UEFI: Intel v: QCCFL357.0114.2020.0401.1544 
           date: 04/01/2020 
Battery:   ID-1: BAT0 charge: 62.6 Wh condition: 93.5/93.5 Wh (100%) model: standard status: Charging 
CPU:       Topology: 6-Core model: Intel Core i7-9750H bits: 64 type: MT MCP arch: Kaby Lake rev: A L2 cache: 12.0 MiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 62431 
           Speed: 800 MHz min/max: 800/4500 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800 8: 800 
           9: 800 10: 801 11: 800 12: 800 
Graphics:  Device-1: Intel UHD Graphics 630 driver: i915 v: kernel bus ID: 00:02.0 
           Device-2: NVIDIA TU116M [GeForce GTX 1660 Ti Mobile] vendor: Intel driver: N/A bus ID: 01:00.0 
           Display: x11 server: X.Org 1.20.8 driver: intel resolution: 1920x1080~144Hz 
           OpenGL: renderer: Mesa Intel UHD Graphics 630 (CFL GT2) v: 4.6 Mesa 20.0.7 direct render: Yes 
Audio:     Device-1: Intel Cannon Lake PCH cAVS driver: snd_hda_intel v: kernel bus ID: 00:1f.3 
           Sound Server: ALSA v: k5.7.0-3-MANJARO 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Intel driver: r8169 v: kernel port: 3000 
           bus ID: 3d:00.0 
           IF: enp61s0 state: up speed: 1000 Mbps duplex: full mac: b0:25:aa:33:16:bd 
           Device-2: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel port: 3000 bus ID: 3e:00.0 
           IF: wlp62s0 state: up mac: 94:e6:f7:a4:27:57 
           IF-ID-1: lxdbr0 state: down mac: 9a:eb:a7:67:25:91 
Drives:    Local Storage: total: 894.25 GiB used: 351.68 GiB (39.3%) 
           ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 970 EVO Plus 500GB size: 465.76 GiB 
           ID-2: /dev/nvme1n1 vendor: Corsair model: Force MP510 size: 894.25 GiB 
Partition: ID-1: / size: 457.16 GiB used: 89.72 GiB (19.6%) fs: ext4 dev: /dev/nvme0n1p2 
Sensors:   System Temperatures: cpu: 64.0 C mobo: 47.0 C 
           Fan Speeds (RPM): N/A 
Info:      Processes: 291 Uptime: 11m Memory: 15.49 GiB used: 1.98 GiB (12.8%) Init: systemd Compilers: gcc: 10.1.0 Shell: zsh 
           v: 5.8 inxi: 3.0.37 

So it turns out, that it is got something to do with the latest BIOS update (114).
But no one knows, what exactly causes the issue.

Can you maybe take a look at the output of dmesg and see anything thunderbolt related after you try to connect/configure/etc. the device? If you run dmesg -w, you can see the kernel message buffer in real time, so that way it might be easier to know which messages appeared when you did something.

Sorry, I encountered your comment only now...
The output of dmesg, when connecting/disconnecting the thunderbolt dock is just this:

[18898.693324] pcieport 0000:00:1b.0: EDR: ACPI event 0x2 received
[18939.945435] pcieport 0000:00:1b.0: EDR: ACPI event 0x2 received

And does the device appear anywhere in the settings after you connect it?

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

Forum kindly sponsored by