Before you get the wrong idea, I already know about having to update the kernel and mesa drivers and Linux firmware. The problem is, before finding out about all that, I tried to update the drivers normally and was testing using elden ring, which had been giving me a white screen, but for some reason this time purple pixels went everywhere on my screen and the computer froze. After a bit I force shut down my PC, and when I tried to reboot it neither the motherboard display port slot or the GPU slot worked. After a bit this seemed to resolve, but now when I plug in the cable to my gpu everything gets very sluggish just on the desktop. In mission center it says the clock speed is 0-2 megahertz and is drawing next to no power. I updated my motherboard bios, I updated the kernel to 6.14, I updated the mesa drivers to 25, and reinstalled the amdgpu firmware. Still the same as before. Did I somehow cause some kind of hardware damage or is it just because of the drivers still not working?

Hi folks,

since Star Citizen 4.1, the game no longer runs under Proton or Lutris. It used to work flawlessly with the `EOS_USE_ANTICHEATCLIENTNULL=1` workaround.

Now:

- Game hangs at load (no crash).

- EAC throws a generic "module error".

- User reports suggest a new "heartbeat" check was enabled.

This effectively blocks all Wine/Proton environments – even GE-Proton or Steam Deck setups.

🧠 Has anyone found a workaround? Or is this a hard lock now due to EAC changes?

Spectrum thread for visibility:

➡️ [https://robertsspaceindustries.com/spectrum/community/SC/forum/50259/thread/4-1-eac-star-citizen-no-longer-launches-on-linux-v\](https://robertsspaceindustries.com/spectrum/community/SC/forum/50259/thread/4-1-eac-star-citizen-no-longer-launches-on-linux-v)

Would appreciate any insights – even a “won’t work” confirmation. We’re not asking for native Linux builds – just to not be silently excluded.