4 ms·

I've been using an AX210 on a Ryzen based laptop since early 2022. I initially had issues with it causing the laptop to lockup hard, if iwlwifi module (AX210 d

I've been using an AX210 on a Ryzen based laptop since early 2022. I initially had issues with it causing the laptop to lockup hard, if iwlwifi module (AX210 driver) was loaded, on resume from suspend to disk. It was easy to work around using a hook script to down the interface and unload the module before suspend, and reload + up interface if it had been up at time of suspend. S3 suspend to ram / resume worked fine without the hack. Currently 6.1 kernel (Debian testing). When I initially put the work around in place it was IIRC 5.6 kernel, so maybe not an issue anymore, but haven't bothered checking to see. I only bought an Intel AX210 because it was cheapest tri-band card. The Intel card is pretty gimped (broken AP modes, breakage due to issues "magically" determining regulatory domain, Intel removed functionality in recent driver versions that could somewhat work around the first two issues so now impossible to mitigate, etc.). I would probably try a Mediatek card, if doing this today (in spite of my general policy of avoiding Mediatek). Last I checked, the equivalent Atheros chipset still had poor free driver support?!

rnk 3y ago
"It was easy..." - that doesn't sound that easy to me. I've honestly never had to do something like that to get linux working. Or maybe I'm too lazy and tried to work around things like that.
- sillystuff 3y ago
  You just drop a script into a "special" directory, and the scripts are run in alphabetical order with arguments that tell them if they are being called for a suspend or resume, and the type of suspend. Non-systemd, it is part of the acpi stuff. Systemd has its own special dir '/usr/lib/systemd/system-sleep' (there is no equivalent under /etc; and creating one yourself will not work). I don't recall the directory the acpi hook scripts used (it has been a while... ?something like /etc/acpid/hooks.d?), but it worked pretty much the same way. Supposedly you can use systemd targets to accomplish the same, but when I tried that, it was very unreliable-- apparently unreliable for others too since the special systemd dir exists, and the distribution is using it for its own hooks (Poettering has said it might go away at some point, though :/). The original dumb version (written in anger, after the first time the laptop crashed on resume post installing the Intel card, and a bit of testing to isolate it to the iwlwifi module) was just a few lines-- literally a couple minutes to write. It has grown since to about 10X the size to handle some details specific to my network setup more intelligently.

rnk 3y ago

"It was easy..." - that doesn't sound that easy to me. I've honestly never had to do something like that to get linux working. Or maybe I'm too lazy and tried to work around things like that.

sillystuff 3y ago
You just drop a script into a "special" directory, and the scripts are run in alphabetical order with arguments that tell them if they are being called for a suspend or resume, and the type of suspend. Non-systemd, it is part of the acpi stuff. Systemd has its own special dir '/usr/lib/systemd/system-sleep' (there is no equivalent under /etc; and creating one yourself will not work). I don't recall the directory the acpi hook scripts used (it has been a while... ?something like /etc/acpid/hooks.d?), but it worked pretty much the same way. Supposedly you can use systemd targets to accomplish the same, but when I tried that, it was very unreliable-- apparently unreliable for others too since the special systemd dir exists, and the distribution is using it for its own hooks (Poettering has said it might go away at some point, though :/). The original dumb version (written in anger, after the first time the laptop crashed on resume post installing the Intel card, and a bit of testing to isolate it to the iwlwifi module) was just a few lines-- literally a couple minutes to write. It has grown since to about 10X the size to handle some details specific to my network setup more intelligently.