this post was submitted on 04 Aug 2026
181 points (98.9% liked)

PC Gaming

15170 readers
547 users here now

For PC gaming news and discussion. PCGamingWiki

Rules:

  1. Be Respectful.
  2. No Spam or Porn.
  3. No Advertising.
  4. No Memes.
  5. No Tech Support.
  6. No questions about buying/building computers.
  7. No game suggestions, friend requests, surveys, or begging.
  8. No Let's Plays, streams, highlight reels/montages, random videos or shorts.
  9. No off-topic posts/comments, within reason.
  10. Use the original source, no clickbait titles, no duplicates. (Submissions should be from the original source if possible, unless from paywalled or non-english sources. If the title is clickbait or lacks context you may lightly edit the title.)

founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] Broadfern@lemmy.world 12 points 20 hours ago (2 children)

Maybe. I know someone who wiped their Legion clean and installed an Arch-based OS and still had the BIOS-brick issue. No idea if they managed to fix it themselves yet but it’s not purely a Windows problem.

[–] MonkderVierte@lemmy.zip 1 points 7 hours ago

How? Did they use fwupd? It's also not on auto-update on Arch (unlike Fedora for example).

[–] Beacon@fedia.io 22 points 20 hours ago

Yeah BIOS use happens at startup before the OS starts getting involved. While it's potentially possible that the bug was only in the windows updater, it's equally possible that it's present in both, or just Linux. Any OS is equally as able to install a faulty BIOS update.