fix: disable evdi

[castrojo]

No description provided.

[MilesEdwards]

Hey @castrojo, @p5,

I wanted to discuss this change as it's impacted day-to-day development.

Lesson learned: I will switch to a custom image to avoid this. Still, Bluefin's goal is to provide a seamless 'pick up and code' experience, but the EVDI module is regularly added and removed on a whim.

Would it be possible to commit to one of the following approaches for better consistency:

1. Keep evdi baked in; users can remove/disable where unnecessary
   or
2. Skip evdi: require users to add it themselves as needed

I'm partial to option 1, given it's easier to turn off a service

[MilesEdwards]

@castrojo, able to share context? This PR was tagged as a fix, so was there some issue on your system caused by evdi, or an upcoming conflict?

[m2Giles]

Most of the back and forth you see is that the kmod breaks often. To not prevent builds we disable evdi.

Where things get tricky is that you cannot do an rpm-install for the kmod at run time. So if you want it you need to make a custom image. Displaylink is used in a ton of docks so we would like to include this for hardware enablement.

But yes overall it is a frustrating situation that this kmod breaks a lot. It has even more bizarre behavior as well.

[castrojo]

Yeah sorry, not intentional on our part. Feels like we turn this thing on half of people's docks break, we turn it off the other half of people's docks break. And then the module may or may not build at that time. Additionally there's CPU usage issues depending on the dock being used, etc.

I personally do not own one of these so we are dependent on what people report. It might make sense for us to just explicitly say we don't support these. I cannot believe vendors sell this as a product. :-/