• KISSmyOSFeddit@lemmy.world
    link
    fedilink
    arrow-up
    2
    arrow-down
    2
    ·
    5 months ago

    Something doesn’t add up. My guess is you’re using a MacBook but don’t want to tell us for obvious reasons.
    There’s literally no reason for “specific libraries and kernel modules” when installing Linux on any x86 PC. It makes no sense.

    • pizzaboi@lemm.ee
      link
      fedilink
      English
      arrow-up
      4
      arrow-down
      1
      ·
      5 months ago

      If they said that they went “back” to Windows, why would you assume a MacBook?

    • MudMan@fedia.io
      link
      fedilink
      arrow-up
      2
      arrow-down
      1
      ·
      5 months ago

      Hah. Nope. There’s a ton of custom features on hardware that need tweaking all over Windows laptops. There are entire forums dedicated to specific brands out there. None of this was much of a surprise, I had put off giving this a try because I had read about the hoops I’d have to jump through and been too lazy to try.

      • KISSmyOSFeddit@lemmy.world
        link
        fedilink
        arrow-up
        4
        ·
        5 months ago

        Huh. I’ve installed Linux on anything from an old 32bit netbook to a Fujitsu convertible that both had such a fucked up UEFI implementation they couldn’t even boot a standard Windows ISO without Ventoy in grub mode, as well as a cobbled-together Workstation with Nvidia graphics, and never ran into issues like this.

        • MudMan@fedia.io
          link
          fedilink
          arrow-up
          1
          ·
          5 months ago

          To each their own, but I can tell you I found people flagging all the issues I encountered online.

      • ugo@feddit.it
        link
        fedilink
        arrow-up
        2
        ·
        5 months ago

        What is this mysterious device that requires specific libraries and kernel modules? So I can state the fuck away from the device and the brand