• village604@adultswim.fan
    link
    fedilink
    English
    arrow-up
    99
    ·
    13 days ago

    I really hope there’s a class action over this. Their software breaking your hardware isn’t a failure of the device and should be a recall instead of a warranty repair.

    • Nik282000@lemmy.ca
      link
      fedilink
      English
      arrow-up
      36
      arrow-down
      1
      ·
      13 days ago

      Lenovo has been absolute trash for a while now. They took the ThinkPad brand and destroyed any reputation it may have had, I’m not surprised by this at all.

      • Final Remix@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        12 days ago

        What’s left? I’m still rocking the same thinkpad since 2015 but it’s really struggling these days (almost time for Linux)

  • Brem@lemmy.world
    link
    fedilink
    English
    arrow-up
    32
    arrow-down
    3
    ·
    13 days ago

    Checks notes

    1. DO NOT update anything unless completely necessary

    ^Oh, that’s rule no. 2

  • D06M4@lemmy.zip
    link
    fedilink
    English
    arrow-up
    19
    ·
    edit-2
    13 days ago

    Prevention: blocking Windows Update.
    Solution: rolling back to a previous BIOS version.

    Too bad most people who purchased a Legion Go won’t know how to do any of that.

    This article has a bit more on the matter.

    Seems people with a Linux distro avoided the whole ordeal. Good for them. 🫶

    • Broadfern@lemmy.world
      link
      fedilink
      English
      arrow-up
      23
      ·
      13 days ago

      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.

      • Beacon@fedia.io
        link
        fedilink
        arrow-up
        35
        ·
        13 days 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.

      • MonkderVierte@lemmy.zip
        link
        fedilink
        English
        arrow-up
        2
        ·
        13 days ago

        How? Did they use fwupd? It’s also not integrated into some kind of auto-update on Arch (unlike Fedora for example).

  • nothingcorporate@lemmy.today
    link
    fedilink
    English
    arrow-up
    15
    arrow-down
    1
    ·
    12 days ago

    Remember when Lenovo got caught putting a rootkit in their bios? That should have been the end of anyone ever buying from them.

    • NewNewAugustEast@lemmy.zip
      link
      fedilink
      English
      arrow-up
      10
      ·
      edit-2
      12 days ago

      Remember them pre-installing superfish? Pushing ads into the browser, compromising HTTPS by adding their own root certificate, and it was all kept in the bios so even a wipe of the OS wasnt going to fix it.

      Or their software in the bios that pulled in lenovoo software before windows started?

      Or all the CVE’s their bios had?

      And then there is all the feedback software that they added that ran silently in the background.

      I am not sure they enshitified or just simply always have been shit.