A number of years ago, I put 2 and 2 together and realized that while most of the time stuff “just works” in Linus (especially with modern versions), some hardware manufacturers have absolute ass Linux support. Predominantly, this occurs with Realtek components.
If at all possible, swap any NICs (wired, wireless, copper, optical, wireless, m.2, PCIE - doesn’t matter, it’s just that Realtek linux drivers tend to suck, and the hardware is often just not as good or efficient at the IC level) to Intel models - anything that meets your bandwidth requirements should do, and you can find them used all over the place, or salvage them from old hardware (cheap eBay 1L thin clients are a good place to pull these from, since you get a tiny computer AND a wireless NIC that you otherwise probably wouldn’t even use).
Also, sleep/hibernate is a thing that often gets wonky on a lot of Linux systems for a whole host of reasons, so simply shutting the thing down is often a better call.
A number of years ago, I put 2 and 2 together and realized that while most of the time stuff “just works” in Linus (especially with modern versions), some hardware manufacturers have absolute ass Linux support. Predominantly, this occurs with Realtek components.
If at all possible, swap any NICs (wired, wireless, copper, optical, wireless, m.2, PCIE - doesn’t matter, it’s just that Realtek linux drivers tend to suck, and the hardware is often just not as good or efficient at the IC level) to Intel models - anything that meets your bandwidth requirements should do, and you can find them used all over the place, or salvage them from old hardware (cheap eBay 1L thin clients are a good place to pull these from, since you get a tiny computer AND a wireless NIC that you otherwise probably wouldn’t even use).
Also, sleep/hibernate is a thing that often gets wonky on a lot of Linux systems for a whole host of reasons, so simply shutting the thing down is often a better call.