You are not logged in.
When booting Arch with a thunderbolt device attached the system goes to a black screen after the boot loader. I cant access the system without hard powering off the device, unplugging the dock, and then booting.
When the system is up and I connect the dock it falls back to USB C compatibility and boltctl gives no output. The dock seems to work perfectly fine after that. dmesg also gives the following error which explains no boltctl output:
thunderbolt: probe of 0000:00:0d.2 failed with error -110I think the error is occurring during the Kernel process since blacklisting the thunderbolt module didn't seem to help. My system also runs on an encrypted zfs root meaning journaling wont occur until after the password is entered which I cannot do.
I'm not really sure where to go from here, especially since I'm not sure how to get logs during the black screen.
Remove landlock from AppArmor lsm kernel parameter fixed boot issue.
The thunderbolt error still occurs but it is a separate issue related to the kernel and my hardware.
System76 Oryx pro 8
WD19TB Dock
Disconnecting everything from the dock and booting.
Update Dock Firmware: fwupdmgr had an update which I applied but didn't help.
Different Thunderbolt Device: Tried booting with an Aorus eGPU attached which lead to the same issue.
Booting lts kernel: Same issue but when the dock is attached after boot the dock runs in thunderbolt mode. There are no errors for thunderbolt in dmesg and boltctl gives an output.
Blacklisting thunderbolt module: It seemed to allow a reboot but it was a fluke as the same issue occurred after rebooting again and even doing a full power cycle. No errors in dmesg of course.
Booting another linux distribution: Booting Pop_OS! gave no errors, booted without issue, and boltctl gave an output. It had no issues which leads me to believe it's an arch specific issue.
Enter Bios: Entering bios activated the keyboard and mouse attached to the dock which I found a bit odd. Once I chose the boot the dock turned off and black screened.
Last edited by echo-84 (2022-01-05 05:18:58)
Offline
Also worth trying: Boot from an Arch install medium.
Offline
Also worth trying: Boot from an Arch install medium.
That boots with the dock attached tho it still has an error about thunderbolt which is due to the kernel. Pop_OS! and the lts kernel work with thunderbolt due to changes made for ACPI 6.4 _OSC not being applied. Pop_OS's kernel has a patch to revert the change (5.13: Fix TBT #61) while lts doesn't have the update yet.
This explains the thunderbolt error but doesn't explain why it wont boot on my install.
In the meantime I'll try a "fresh" zfs boot environment. If it boots, it should help narrow down what's causing the issue.
Last edited by echo-84 (2022-01-04 09:14:00)
Offline
I managed to get it to boot with the dock attacked by removing landlock from AppArmor lsm kernel parameters.
After compiling Pop_OS!'s kernel and still seeing the issue I realized I had kernel parameters related to AppArmor enabled. Looking at Pop's kernel config I found the AppArmor line and the parameter's they used. Comparing the differences, Arch had landlock and bpf while Pop had integrity. Landlock was the only one out of those that made since so I disabled it and it worked. It seems to be a hardware specific issue because I tried it on another computer with the same AppArmor parameters and it didn't have an issue.
The thunderbolt error still occurs but it is a separate issue related to the kernel and hardware.
My best guess would be that both these issues have something to do with how the bios/firmware handles thunderbolt in the Oryx Pro.
Offline