Wireless ac PCIe interface
Wireless ac PCIe interface
Mint doesn't automatically use closed source repos by default. You're looking for a distribution that includes kernel drivers, similar to how you use Ath9k, but those options aren't clearly listed in the Debian or Arch documentation. Your point about needing a proper server OS is important.
Don't assume anything until you test it. Back up your operating system before trying the product. If it works smoothly, you're good to go. If issues arise, simply reset and send the card back.
Many gadgets rely on custom firmware. This overview looks solid (though I can't confirm its current accuracy): https://en.wikipedia.org/wiki/Comparison...ss_drivers. It's okay to depend on proprietary firmware unless you have a strong reason to prefer open hardware. Usually, drivers with closed firmware perform well. Steer clear of those lacking a Mainline kernel driver at all!
I've been working with that chart a lot. The process has been quite time-consuming. I visit pbtech.co.nz to check what's available in NZ, then head to the OEM site to download the driver and see how it functions. I also look on Wikipedia and the Debian wiki to verify if it's included in the kernel. It's hard to find anything about ac speed. I prefer proprietary drivers because kernel drivers are much simpler, and they work across any Linux distribution. Installing one is straightforward. I've used the Ath9k chipset before—it's fully equipped, so I'm searching for a similar option with PCIe and high speed. Maybe I should ask the level1 forum for help.
Now I see why an open driver is necessary. Another forum with a similar audience might offer better support. (EDIT: after re-reading your message, I believe you might be mixing up open-source firmware drivers with closed-source ones. The latter can be frustrating to install, while the former should function smoothly once the firmware is available, typically found on most Linux installation media. If it isn’t present, copying a single binary usually suffices.) Drivers that rely on proprietary firmware often require downloading the firmware itself, usually located in /usr/lib/firmware, which most distributions handle via their package manager. Once that’s done, the driver behaves like any open-source driver from a user’s point of view—no issues with kernel updates.) Acquiring the firmware might involve more licensing considerations, though it isn’t strictly free software.