eGPU authorized, but not recognized - Ubuntu 20.04
The egpu does seem to be authorized and is listed in the thunderbolt manager, but I just can't seem to get it to be recognized. Has anyone else run into a similar issue?
$ apt install nvidia-driver-440 Reading package lists... Done Building dependency tree Reading state information... Done nvidia-driver-440 is already the newest version (440.100-0ubuntu0.20.04.1). 0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.
$ nvidia-smi NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running.
$ lspci | grep VGA 00:02.0 VGA compatible controller: Intel Corporation Iris Plus Graphics G7 (rev 07)
$ boltctl list ● GIGABYTE GV-N1080IXEB-8GD ├─ type: peripheral ├─ name: GV-N1080IXEB-8GD ├─ vendor: GIGABYTE ├─ uuid: 00d361f8-5ac1-ed00-ffff-ffffffffffff ├─ status: authorized │ ├─ domain: c0c7910c-17e1-8680-ffff-ffffffffffff │ └─ authflags: none ├─ authorized: Thu 23 Jul 2020 05:05:18 AM UTC ├─ connected: Thu 23 Jul 2020 05:05:18 AM UTC └─ stored: Wed 22 Jul 2020 08:10:45 PM UTC ├─ policy: iommu └─ key: no
anything useful in the dmesg output related to thunderbolt nvidia or any errors for pci ?
What BIOS settings do you have related to thunderbolt? If I recall when I was trying to get my setup working I also saw the stored policy set to iommu and i couldnt get it to work. As soon as changed the setting I was able to authorize and enroll.
Try forgetting the device and re-enrolling it if you just added the hpbussizes pci addresses may have changed causing issues too.
So forgetting it, then reauthorizing and enrolling did not work, but I found something that sort of worked.
I currently have Ubuntu dualbooted with Windows, with Windows recognizing it most of the time. When Windows didn't recognize it, unplugging the power to the egpu (not thunderbolt), waiting for a few seconds, then connecting again got it to work.
Installing Ubuntu fresh did recognize it when plugged in from boot.
Things that broke it (or at least I think that broke it, could easily be wrong):
- slimbookbattery - under any power saving setting, it broke it. Turning it off allowed it to be recognized again on a clean boot)
- leaving thunderbolt plugged in when shutting down and powering back up with it still connected
Another big thing I noticed was that sometimes it did get recognized and fully worked after removing the power from the egpu (in my case, aorus gaming box) before boot and waiting for like 10-20s. Disconnecting thunderbolt was not enough to get it to work. This is most likely unrelated to the actual underlying problem, but it seems to work. Also, probably mentioned before, but the egpu is not hot pluggable.
Current bug I'm dealing with is when leaving thunderbolt connected when powered off, then powering back on still connected. Ubuntu hangs after spitting out:
/dev/nvme0..: clean. nnn/nnn files , nnn/nnn blocks
Sometimes I see this after the line:
[nnn] Bluetooth: ...: Failed to send Intel_write_DDC (-22)
The first is a file system checker, so I disabled that in /etc/fstab. That only got rid of the lines being printed, but still would get the Bluetooth error. This is most likely not the underlying issue though. I got it to work again after going into windows, connecting the egpu (after unplugging for a few seconds, was not recognized), then powering off, unplugging again for 10s, connect thunderbolt and power, boot to Ubuntu. Again, I'm not too sure why that worked or if it's something unrelated.