• 507 Posts
  • 2.28K Comments
Joined 3 年前
cake
Cake day: 2023年7月19日

help-circle

  • The EBF module can be inspected, and EAC won’t have kernel access, so that limits it significantly. Things like crowdstrike, completely hiding it’s processes, etc shouldn’t be possible without it having kernel access.

    The systemd service can easily be confirmed to only run while a game is running as well. You can even restrict the service to be masked except when specific games are running.

    EAC having root access is a valid concern though, it will have full access to your entire filesystem. Normally you can restrict what files a systemd service can access, so we may be able to quarantine this to block any privacy concerns. However we’ll have to wait until it comes out to know that part.

    Overall it’s not perfect, but users will have much higher ability to audit it on Linux versus the Windows version.



  • My understanding is that there’s a systemd service that runs only when the game runs, and that uses ePBF to restrict read/write access to the game files while it’s running (to prevent tampering). The tpm/secure boot/recognized kernel part is to make sure the user doesn’t have a modified kernel that will lie to the anti-cheat.

    If everything works like they say, they shouldn’t have access to the non-game files and no direct kernel access. So privacy should be maintained, and theoretically no risk of a EAC bug or exploit causing a full system crash.

    Overall it sounds much better to me than windows anti-cheat, but that’s a pretty low bar.













  • Thanks for sharing, hopefully it will help someone.

    From reading on the issue, it may be a timeout during a large TRIM operation. With larger drives, you can have large scale TRIM operations fail for a couple reasons, but it mostly comes down to the volume of the requested consecutive operations being more than the NVME drive’s controller can handle in one go, or more than it can handle within the typical 30 second timeout window for these commands.

    If it was this, you could either temporarily disable trim for the drive before running the install, or possibly tweak the mkfs commands in the install script to include the nodiscard option.


  • There’s different thumbstick parts for LCD and OLED, the switch you’re talking about is only on the LCD thumbsticks, and it’s for switching between type A and type B sticks (the LCD originally had 2 different thumbstick parts that aren’t interchangeable). When replacing sticks for the LCD deck, you used to have to check if you had A or B sticks and order different models depending on that, but the added A/B switch means there’s now only one LCD stick model to buy.

    The OLED sticks have some completely different design parts, for example the LB/RB buttons are actually part of the OLED stick, which is nice since those can be permanently ruined by dropping the deck. Repairing broken LB/RB on the LCD deck is much harder, but changes like this means you can’t have interchangeable sticks between LCD and OLED.







  • A recent steamOS update said it was laying the foundation for hibernation, which should be a more battery friendly alternative to sleep.

    The second part depends on the game, some will just work. Others need to run a first launch script and install some stuff before launch, which I agree should be part of the download process. Finally some games require license check or additional network access on first launch while the game is running, and this part can’t be automated by valve. Overall it’s just a good habit to always run newly installed games once, at least long enough to get to the main menu.