eGPU always shows as disconnected about egpu-switcher

[hertg]

Thanks for submitting all the information.

Have you tried re-running the setup? Maybe the card is connected to another PCI BUS ID than it was when you initially ran the setup. Can you post the outputs of the following commands?

This will output your egpu-switcher configuration (ie. at which PCI BUS ID egpu-switcher will look for your eGPU):

cat /etc/egpu-switcher/egpu-switcher.conf

This is the exact command egpu-switcher uses for egpu detection internally:

lspci -d ::0300 && lspci -d ::0302

[Sandvich]

Seems right:

❯ cat /etc/egpu-switcher/egpu-switcher.conf
external_driver=amdgpu
external_gpu=48:0:0
internal_driver=
internal_gpu=
❯ lspci -d ::0300 && lspci -d ::0302
00:02.0 VGA compatible controller: Intel Corporation Iris Plus Graphics G7 (rev 07)
2e:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Hawaii XT / Grenada XT [Radeon R9 290X/390X] (rev 80)

Also, I rebooted, so have a picture of the UEFI too :)

I've just rerun the setup, so I'll reboot now and see if it worked.

[Sandvich]

That got it! I did a little bit of digging and it looks like it was to do with the order that I plugged things in - I have both a dock and the enclosure, and if I plug in the enclosure first it seems to cause this issue.
Thanks!

[hertg]

❯ cat /etc/egpu-switcher/egpu-switcher.conf
external_driver=amdgpu
external_gpu=48:0:0
internal_driver=
internal_gpu=
❯ lspci -d ::0300 && lspci -d ::0302
00:02.0 VGA compatible controller: Intel Corporation Iris Plus Graphics G7 (rev 07)
2e:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Hawaii XT / Grenada XT [Radeon R9 290X/390X] (rev 80)

yes, you might have swapped the Thunderbolt 3 port where you connected those.

2e:00.0 VGA compatible... if you have a closer look here 2e in HEX is 46 in DEC, but egpu-switcher was set up to search at BUS ID 48 :)

This will be addresses in the future, so that the PCI BUS ID no longer matters for egpu-switcher to detect your eGPU. For the time being, if you run into the problem again, just try re-running the setup.