Brian Masinick
I do not think there is a need for getting different network cards though, particularly if you are in laptop settings, it is rather unusual for an average user.
Instead, I would think a comprehensive set of firmware built into the OS distro would do.
So, e.g. if taking my example, two laptops, with different network cards are not able to connect or even be recognized by antiX 25 Beta1, but are fine under MX 25, why not just in the spirit of sharing adopt a more comprehensive set of firmware from MX, particularly that they are covering more, but with less space taken (over 1Gb antiX vs. 780Mb MX). The most unusual RTL usb adapter was recognized by MX, while pretty much mainstream Broadcom variety in Apple Macbook Pro not recognized in antiX.
So, from such experience it is only to gain much from adopting the MX kaboodle, which has been already put together as part of MX ahs, which is enhanced hardware support and save space as a bonus.
I have a feeling Beta2 will see this.
It IS possible to work around the issue; there are some methods to get Broadcom wireless cards working. The main reason some cards are not easily accessible is that for years Broadcom provided proprietary drivers, so they work fine with those drivers on any operating system that includes the proprietary wireless bundles. It may also be that newer Broadcom devices may have freely available drivers, but I’m not certain about that.
The Debian documents used to have a write-up about this; haven’t used it in a while so I’m not certain where it is, but a search ought to find it. If unsuccessful locating it, let me know and I’ll see if I can dig it up somewhere.
Also, as @anticapitalista already mentioned, there is a broadcom-sta-dkms package. I wonder if reinstalling it would help.
--
Brian Masinick
Alternate "Search B":
This search page