Hi @mikeone, there are eight troubleshooting steps as follows:
- Check the Status of Thunderbolt Devices
Use the boltctl command to list the Thunderbolt devices and their status:
run boltctlin your terminal
- Check Thunderbolt and USB4 Details
Run boltctl list to see detailed information about connected Thunderbolt devices:
bash
2. Check Thunderbolt and USB4 Details
Run boltctl list to see detailed information about connected Thunderbolt devices:
run boltctl list in your terminal.
3. Monitor Thunderbolt Events
You can monitor events related to Thunderbolt devices using boltd. This can help you see real-time events when you connect or disconnect devices:
run boltd --monitor in your terminal.
- Show Thunderbolt Security Level
To check the current security level of Thunderbolt devices, run:
run boltctl show in your terminal.
5. Authorize Thunderbolt Devices
If you have any unauthorized devices, you can authorize them using:
run boltctl authorize [device-uuid] in your terminal. Replace [device-uuid] with the actual UUID of the device you want to authorize.
- Check Kernel Logs for Thunderbolt/USB4 Errors
Use dmesg to filter out Thunderbolt-related messages:
run dmesg | grep -i thunderbolt in your terminal.
7. Check Detailed Information of Thunderbolt Devices
You can use lspci to get detailed information about the Thunderbolt controller and connected devices:
run lspci | grep -i thunderbolt in your terminal.
- Verify IOMMU Groups
Check the IOMMU groups to ensure proper device isolation and passthrough:
run find /sys/kernel/iommu_groups/ -type l in your terminal.
By running these commands, you should be able to gather more detailed information about the status and configuration of your Thunderbolt and USB4 devices. Let me know if you encounter any specific messages or issues that need further analysis!
I have decoded the demessage you included in your last post. Based on the dmesg output, it seems there are issues with both the USB4 and Thunderbolt controllers, as indicated by the errors for 0000:8c:00.0 and 0000:8d:00.0. The error code -110 typically indicates a timeout issue, suggesting the hardware may not be initializing correctly. Here are several steps you can take to further diagnose and potentially resolve these issues.
First, verify the USB4 and Thunderbolt settings in your BIOS/UEFI to ensure they are correctly configured. Enter the BIOS/UEFI setup during boot, check for settings related to USB4, Thunderbolt, and IOMMU, and make sure they are enabled. Look for any USB/Thunderbolt-related firmware updates or specific settings that need to be enabled for proper operation.
Next, make sure your motherboard’s BIOS/UEFI and Thunderbolt firmware are up to date. Visit the ASUS support website for your motherboard model, download, and install the latest BIOS/UEFI firmware updates. If available, update the Thunderbolt firmware as well.
Ensure you have the necessary kernel parameters set for proper initialization of USB4 and Thunderbolt. Edit the GRUB configuration file at /etc/default/grub and add intel_iommu=on iommu=pt to GRUB_CMDLINE_LINUX_DEFAULT. Then, update GRUB by running update-grub and reboot the system to apply the changes.
Check that the controllers are seated properly in their PCIe slots, as sometimes reseating the card can help resolve initialization issues. Consider testing with a different kernel version to see if the issue persists. Install a newer kernel, if available, using sudo apt-get install linux-image-generic, then reboot and select the new kernel from the GRUB menu.
Use boltctl to gather more information about the Thunderbolt device by running boltctl list and boltctl show. Monitor Thunderbolt events with boltd --monitor to see real-time events and logs related to Thunderbolt devices. Verify the Thunderbolt controller state with lspci -vvv -s 8d:00.0 to get detailed information about the controller.
If the issue persists after these steps, consider reaching out to ASUS support for further assistance. There may be a hardware-specific issue or a need for a firmware update that they can provide.
