The weird thing is that it seems to be working? Either I misdiagnosed the problem, or maybe my old one was just broken.

  • Eeyore_Syndrome@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    9
    ·
    edit-2
    18 hours ago

    Some distros have crusty old kernels/firmware and thus lack optimal support to boot lol.

    Anyway even with Qualcomm Wi-Fi 7, it was not great even a month back. 🙄

    I had to rebase to Bazzite-Testing and back to Bazzite-Stable a few times… Ended up pinning an older testing image for a while to keep working wifi while Fedora upstream fixed their crap.

    The joy of Atmoic made that super simple and painless I’ll say.

    Rolling back updates on tradish distros can be painful to the point of reinstall sometimes lol.

    • Possibly linux@lemmy.zip
      link
      fedilink
      English
      arrow-up
      3
      ·
      16 hours ago

      I personally would avoid Wifi 7 or anything newer. It takes a while to develop kernel support and it will be a bad experience. Wifi 7 support was only finished in the last year or two and it is going to be buggy.

      • jaxxed@lemmy.world
        link
        fedilink
        arrow-up
        5
        ·
        edit-2
        16 hours ago

        This.

        Don’t expect the brand new gear to work on Linux. It takes a while for the neckbeards to get access and write the drivers.

        Heck, even new gear from companies that contribute their own drivers can be shaky.

        I’m sorry, but for desktop, Linux can’t be relied on as stable for early gear adoption. Usually even the specs are in limbo still.

        This is coming from a linux/bsd only user for many years.

        • Possibly linux@lemmy.zip
          link
          fedilink
          English
          arrow-up
          1
          ·
          12 hours ago

          The vast majority of hardware is support maintained by the manufacturer. However, it takes quite a while for it to trickle down. Linux is purely a monothic kernel so bugs can be very bad.

    • rumba@lemmy.zip
      link
      fedilink
      English
      arrow-up
      2
      ·
      15 hours ago

      yup, same problems with v4l and a kernel incongruency. NixOS to the rescue. Add a line to pin the kernel and everything keeps working like nothing ever happened.