On March 20th, 2026 MSI released a BIOS update for B650 Tomahawk Wi-Fi motherboard. One of the changes says "Implemented the anti-cheat mechanism."

I looked around their forums and people seem to agree that it refers to Microsoft Pluton security processor.

Does anybody know what this change is actually about? Is it another initiative by Microsoft to further lock people out of their computers? Would it somehow hinder using Linux with this motherboard?

A screenshot from MSI website showing a description of a BIOS update. One the mentioned changes is "Implemented the anti-cheat mechanism."
[–] 9 points 8 months ago (2 children)

In my experience, Windows only fucks-up your Linux bootloader if they both share the same EFI System Partition. Keeping them separate fixes the issue. Though, this means that you'll have to install Windows first, since it will automatically pick your Linux ESP otherwise.

  • source
  • [–] 0 points 8 months ago*

    I am not using them myself but I have heard that some ThinkPads support Libreboot. Also, System76 sells laptops with Coreboot.

    I don't think choosing a particular Linux distro matters with them.

  • source
  • [–] 5 points 9 months ago*

    I absolutely loved the Lake House DLC when I first played it, way more than Control's AWE DLC. Glad you are liking it, too. Second half gets even weirder and yeah I can't praise it enough.

  • source
  • [–] 2 points 9 months ago*

    Hey, thanks for the update! You actually are quite experienced. These things are best taken slowly. I would recommend trying things out (including installation and dual booting another OS) on a virtual machine. VirtualBox is a good program for this on Windows. If things ever go south, you can just delete the VM and create another one, without affecting your main PC and files on it.

    Also, there is one unfortunate problem that will affect your graphics card. Nvidia recently dropped support for Pascal (GTX 10x series) and older graphics cards with version 590 of their driver.

    I highly recommend Bazzite. It has a dedicated version that supports legacy Nvidia cards. Its immutable nature makes is extremely hard to mess things up. Plus, it is getting really popular since last year. So, you are likely to get much better community support than Pop!_OS anyway.

  • source
  • parent
  • context
  • [–] 3 points 9 months ago

    I will start a new playthrough before Sea of Sorrow comes out and want to play in a different way. For far, I got all achievements just using the Hunter's Crest. Beast Crest should be a good enough change to keep things fresh.

  • source
  • [–] 8 points 9 months ago* (last edited 9 months ago) (1 child)

    Hey, buddy. You seem to be panicking. Please, take a moment to calm down, go for a walk outside for half an hour.

    Remember, you can't fuck-up your computer by just messing with its OS and software (unless you know how, which you definitely don't 😁). I would love to help you, but, unfortunately, the information you provided is not enough.

    Please, answer some of these questions, at least:

    • What were you trying to do?
    • Why did you even decide to install Pop!_OS?
    • Why did you decide to dual-boot with Windows?
    • You seem to lack necessary knowledge for installing an OS in general. Did you follow a tutorial for this? Or did you ask an "AI" chatbot (like ChatGPT) for help?

    If you can't answer the last question, I am afraid only way to help would be someone experienced to investigate your computer in real life. If that's not possible and you are okay with loss of data on that system, you can wipe it completely to install a fresh OS and start from beginning. I can help you make a choice in regards to the distro as well, if you tell me your hardware specifications.

  • source
  •  

    Hi, c/selfhosted! This is my first post on Fediverse and I am glad to be making it here.

    I recently got fed up with having to use Tailscale to access my server at home and decided to expose it publicly. A friend recommended segregating the server into a dedicated VLAN. My router's stock firmware does not allow that, so I flashed OpenWrt on it (I am amazed how simple and easy the process was).

    Getting the router to actually assign an IP address to the server was quite a headache (with no prior experience using OpenWrt), but I managed to do it at the end with a help from a tutorial video on YouTube.

    Now, everything is working perfectly fine and as I'd expect, except that all requests' IP addresses are set to the router's IP address (192.168.3.1), so I am unable to use proper rate limiting and especially fail2ban.

    I was hoping someone here would have an experience with this situation and help me.


    Edit: Solved thanks to @PotatoesFall@discuss.tchncs.de.

    I messed around with the port-forward settings with no luck in the past. Instead, disabling the “Masquerade” option in the firewall settings for the server’s VLAN worked.

    view more: next ›