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

  • istdaslol@feddit.org
    link
    fedilink
    arrow-up
    2
    ·
    18 days ago

    Could be flashed with a different microcode that works better with Linux. Just because it’s of the same model doesn’t mean it’s the same. Sometimes it’s as little as a flag that is set. Looking at you battleye

      • tetris11@feddit.uk
        link
        fedilink
        English
        arrow-up
        2
        ·
        17 days ago

        (cant believe Im writing this but) ever since I switched to Arch all those years ago, my Linux hardware problems ended.

        Turns out Linux is great when your kernel is relatively fresh by default.

  • stoly@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    18 days ago

    You will learn SO MUCH about computers by just trying to make your wifi or some other thing work. And then you will never have trouble with that thing again. I remember having to do wrapping of drivers, but I don’t know if that is still a thing.

  • KindnessisPunk@piefed.ca
    link
    fedilink
    English
    arrow-up
    0
    ·
    18 days ago

    Does anyone know a good Wi-Fi 7 chipset that plays well with AMD? I saw the Qualcomm one and it looks promising, but I’ve heard its support for Linux is spotty.

  • doughless@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    18 days ago

    You could try switching your wifi backend to iwd instead of wpa_supplicant.

    If you’re using NetworkManager, then create the file /etc/NetworkManager/conf.d/wifi_backend.conf, and add the following configuration:

    [device]
    wifi.backend=iwd
    
    • tal@lemmy.today
      link
      fedilink
      English
      arrow-up
      0
      ·
      18 days ago

      If it’s periodically dropping, I doubt that it’s going to be the userspace WiFi backend. I’d be more-inclined to blame either the driver or an (unlabeled) hardware variation.

      • doughless@lemmy.world
        link
        fedilink
        arrow-up
        0
        ·
        18 days ago

        I had this exact issue with both my desktop and server. Anytime I put any sort of load on the outbound connection, the wifi would cut out. After switching to the iwd backend, I haven’t had any issues.

  • ThunderLegend@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    0
    ·
    18 days ago

    Man that reminds me that I bought a Chinese motherboard to build my homelab and installed Debian. Great! One kernel upgrade later and my network card stopped working. Tried a lot of things but to preserve my mental health and to enjoy my jellyfin again, I just returned to the older kernel and voilá, everything worked again…so no updates for now …or ever

    • itsjess@lemmy.blahaj.zone
      link
      fedilink
      English
      arrow-up
      0
      ·
      18 days ago

      Have you ever compiled your own kernel? Could be the upgraded version doesn’t enable a module your motherboard needed or something. A fairly simple test would be to compile thw kernel with everything enabled as a module and use that

      • ThunderLegend@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        0
        ·
        18 days ago

        I did it once but I remember not being able to judge if I needed all the modules or what to flag on each line I saw. I tried to load the module this time after the upgrade but without success. Maybe I’ll try someday if I get the time…

    • baltakatei@sopuli.xyz
      link
      fedilink
      arrow-up
      0
      ·
      18 days ago

      Same happened with me and a USB video capture card I bought specifically for Debian Linux compatibility. One kernel upgrade later… doesn’t work. Try again on old kernel? Works. I’ll probably try in a few months, but I can’t be bothered now.

  • Monument@lemmy.sdf.org
    link
    fedilink
    English
    arrow-up
    0
    ·
    18 days ago

    My first Linux issue was that it didn’t support the USB hub I had at the time that was just always plugged into the windows machine I was installing Linux onto. So in 2003, I took my bulky tower to a friends house and it booted on the first try after weeks of failures trying on my own at home.
    I was both relieved, and incredibly annoyed.

    • The Picard Maneuver@piefed.worldOP
      link
      fedilink
      English
      arrow-up
      0
      ·
      18 days ago

      Realtek. I was reading that many Realtek chipsets cause intermittent wifi drops, and that since they’re pretty inexpensive, it’s simpler to just get one that works. So, I went with another company that advertises as Linux compatible out of the box, plugged it in, checked it with ‘lsusb’, and saw the exact same Realtek chipset that my old one has.

      • SavvyBeardedFish@reddthat.com
        link
        fedilink
        arrow-up
        0
        ·
        18 days ago

        Not sure if you have the same problem or not, but I had intermittent jitter spikes (and/or complete package drops) every 60 seconds on my Realtek chipset, ran:

        sudo iw dev wlan0 set power_save off

        And it’s been stable since (just had to make a udev rule to make it persistent across boot)