OPINIONATED OMARCHY
TROUBLESHOOTING CORPUS
790
RECORDS
790
AUDITED
0
UNCHECKED
2388
SOURCES
LIVE
display-monitors medium occasional DISPUTE

Fix a USB4 or Thunderbolt monitor reporting No signal after a reboot

omarchyarchendeavouroscachyoshyprlandwaylanddesktoplaptopdock
CORRECTED An auditor found the fix wrong or incomplete and rewrote it.
AUDIT NOTE

The technical content is accurate and matches the Arch Thunderbolt wiki exactly. The udev rule ACTION=="add", SUBSYSTEM=="thunderbolt", ATTR{authorized}=="0", ATTR{authorized}="1" is that page's verbatim 99-removable.rules example, and the force_power path with GUID 86CCFD48-205E-4A77-9C48-2021CBEDE341 is its verbatim example too. sudo pacman -S bolt is correctly a plain -S with no -Sy partial-upgrade hazard, boltctl list is right, and the connector re-probe loop plus hyprctl reload is consistent with the other records. basecamp/omarchy#374 exists ('Problems with Display Port over USB4 (BeeLink SER9)'). What is missing is a warning: steps 1 and 2 together, dropping BIOS Thunderbolt security to none AND blanket auto-authorizing every device that is ever plugged in, remove Thunderbolt's DMA-attack protection entirely. That is a real security downgrade being handed to a user as a copy-paste, and it needs to be stated. udevadm control --reload also needs a trigger to affect already-present devices.

The cause above was not rewritten and may still contain the error described. The fix below is the corrected version.
RISK

Setting the Thunderbolt security level to none or auto-authorizing every device removes the protection against DMA attacks from a malicious plugged-in device. Do not do this on a machine that gets plugged into untrusted docks or cables.

Symptom

A monitor connected over USB4/Thunderbolt DP-Alt-Mode works perfectly once you are in the session, but after a reboot the screen reports 'No signal' on the Thunderbolt input from the bootloader menu onwards. The only way back is to plug in the native DisplayPort or HDMI cable, get a picture, then replug the USB4 cable.

Cause

The Thunderbolt tunnel is not established before the OS takes over the display: the device is not pre-boot authorized, and the DP tunnel only comes up once the Thunderbolt stack is loaded and the device is authorized in Linux. Until then the connector reports nothing.

Fix

  1. In firmware/BIOS, enable Thunderbolt pre-boot support. Prefer security level dponly (tunnels DisplayPort only, no PCIe/DMA) over none. dponly is enough to get a picture at the boot menu and keeps DMA protection. This is what makes the boot menu appear on the USB4 input.
  1. Auto-authorize Thunderbolt devices in Linux so the tunnel comes up without a prompt:

> **Security warning:** this authorizes *every* Thunderbolt device the moment it is plugged in, including one plugged in while the machine is unattended. Combined with a BIOS security level of none it removes Thunderbolt's DMA-attack protection. On a laptop that leaves your sight, prefer enrolling your dock once with boltctl enroll <uuid> instead of the blanket rule below.


sudo pacman -S bolt
boltctl list                       # find your dock's UUID
sudo boltctl enroll <uuid>         # trust just this dock, persistently

If you accept the risk and want everything auto-authorized:


sudo tee /etc/udev/rules.d/99-removable.rules <<'EOF'
ACTION=="add", SUBSYSTEM=="thunderbolt", ATTR{authorized}=="0", ATTR{authorized}="1"
EOF
sudo udevadm control --reload
sudo udevadm trigger --subsystem-match=thunderbolt
  1. If the tunnel is up but the connector is stale, force a re-probe:

for c in /sys/class/drm/card*-DP-*; do
  [ -e "$c/status" ] || continue
  echo off | sudo tee $c/status; sleep 1
  echo on | sudo tee $c/status; echo detect | sudo tee $c/status
done
hyprctl reload
  1. If your controller powers itself down, force it on (Dell/Intel WMI only, and the attribute is absent on machines that do not expose it):

echo 1 | sudo tee /sys/bus/wmi/devices/86CCFD48-205E-4A77-9C48-2021CBEDE341/force_power

Verify

Reboot with only the USB4 cable attached: the bootloader menu and then the Hyprland session both appear on that input, and hyprctl monitors shows the native mode.

Sources

usb4-displayport-no-signal-after-reboot