just because everyone convinced you too use uefi as your true base OS doesn't mean it's not a driver issue. no matter how much you try to cover your own eyes.
same with cpu and microcode.
> it's always driver support.
Not necessarily, if it's an Intel module it might be a CNVi module instead of normal PCIe module, meaning it can only work on Intel platforms (because half of the WiFi hardware is actually within the CPU/chipset; see https://en.wikipedia.org/wiki/CNVi for more information).
plain old crappy software (driver) which you are not supposed to have access (despite all the filling being likely based on gpl)
https://www.intel.com/content/www/us/en/support/articles/000...
I prefer real WiFi.
I use the previous generation RTL8852A in my homegrown wifi router, and it works nicely as AP with the same driver and hostapd. The modules are small, and fit to laptops. (the ones I buy are actually some stock for laptops, that gets re-sold as spare parts I think)
Cheaper than the Qualcomm wifi chips, too.
Internet is full of bad experiences, but mostly from windows laptop users and from 2-3 years ago, around the time the driver was being upstreamed to Linux. It has been solid and growing in features ever since. Throughtput is pretty nice 500mbit/s for a single 80MHz channel setup I'm using and stable.
There's no other choice for actively manufacturer supported wifi device usable for AP for Linux anyway. Broadcom drivers are unsupported for years, and firmware heavy with lack of firmware updates from manufacturer. Bad combo. Intel is not for APs. And that's about it.