Hey, I am looking to build a DIY external GPU solution, to attach to a Laptop running EOS via Thunderbolt 4.
Does someone here have experience using an eGPU on EndeavourOS? Any tips? Do’s and Dont’s? Gotcha’s?
I’m also interested in hearing what kind of eGPU setups you have 
Well it is a hit and miss, but that is not individual to EndeavourOS more Linux in general and that not many have a setup like this, it’s niche.
Out of experience I can say, it works on x11 very fine, if you install egpu-switcher.
On Wayland though… In my experience I get flickering on the second monitor completely. But it seems I am the only one on the entire internet that has this issue no matter what distro I install.
I believe the reason for that is that if I use the egpu I technically have 3 GPUs (intel+nvidia+nvidia) and Wayland just can’t handle it. Likely everyone with only integrated graphics and an eGPU doesn’t have this issue. So it will just work out of the box once the drivers are installed as it should be for Wayland.
So you should be fine, depending on what you go for.
Beside the insights @Mellow has provided,
I guess the Arch Wiki on external GPUs should cover the basics that would apply to EndeovourOS as well.
So there is an internal Nvidia GPU and a Nvidia eGPU. Hmm. How about disconnecting the internal GPU and then trying out with the eGPU?
It is a laptop, i cant physically disconnect it.
I had this back and forward with the garuda team around a year ago. because the problem appeared with an update (i believe it was somewhere around the kde 6.0 release). status before it was just poor performance, like 10 fps and 3-5 seconds delay on the monitor and after the update the performance was as it should be but with flickering and graphical glitches all over the place.
it wasnt kdes fault as it happens also with gnome as we tested it, and just disableing the dGPU doesnt do it either bc for 1 it would hinder my workflow and 2 doesnt fix the underlying problem and 3 doesnt fix the problem anyway.
Long story short, we figured out it is likely a wayland issue (they explained it to me in detail what the issue is but im too dumb to explain it myself even if i understand it.. somewhat) and probably noone except the wayland team can fix it, as whatever they tried to fix performance wise at around that time, created a new problem (that they probably may or may not be aware of)
If it is a forum post or a bug post, can you please share the link?
most of the chat went into DMs over time (esp after it auto closed). that one guy that was there to help me in the forum post started to DM me instead of posting in there, trying all sorts of things and then some other guy (probably asked by the one who originally helped me) also messaged me explaining it to me what the issue very likely is. (think it even was some kind of dev but i didnt ask)
but uh yeah this is the original post
(dont judge me too hard, i was even more clueless about stuff back then than i am today)