antiX-full has broadcom-sta-common and some people have had issues with wireless, fixed by removing /etc/modprobe.d/broadcom-sta-common.conf

antiX-base does not have broadcom-sta-common.

So do we need it or not?

Anti, for me, getting rid of the sta firmware and sticking to the use of firmware-b43-installer works much better.

More on this, anti, based on experimenting with some other distros. Today, I was messing around with the year or two old PCLinuxOS"Full Monty" Edition, which came out, I think, around Christmas in 2010 or early 2011. It had been working just fine until recently, but all of a sudden, wireless went away. That was curious, because antiX and PCLinuxOS are two systems that nearly always get wireless right.

Doing some investigation, I found the very same issue we were having with antiX M12.0 Test 2"Full Edition": too many Broadcom firmware drivers. They had one called Broadcom-wl, which appeared to be the same as the one we call"Broadcom STA". I wired up, got rid of it, got rid of some other firmware that wasn't being used on my hardware, then I reinstalled the firmware-b43-fwcutter package they had, ran modprobe -r b43 then modprobe b43, and without that extra firmware conflicting, I got it up without an issue.

Of course, it's possible to blacklist everything but the driver that you are using, but to me, at least on Debian-based systems, including only two Broadcom firmware packages, firmware-b43-installer and firmware-b43legacy-installer, then having the system select the right one, based on which Broadcom wireless interface is actually present, seems to do the job and cover the entire Broadcom product line, based on what I've read over and over on the Debian Wiki in the Wifi and Wireless sections.

Hope this helps. If anyone thinks otherwise, I hope they speak up soon, because I am recommending that we take this approach, which has worked PERFECTLY for me in antiX Base, but was giving me problems in antiX Full until I pared it down. Please comment, and let's adjust what gets included based on feedback; if none, please go with my suggestion.

I got a laptop with broadcom, but bought myself a netgear WG111, which runs with free software.
I just downloaded the test-iso. If someone tells me what commands exactly i have to run i will be happy to do it
(yes, i am not good with wireless).
I will fiddle with it now anyway (but if i do it without instructions it might take forever...)

What i do recall is that one method for the broadcom worked, while the other failed. Let me look for the thread to figure out which one failed (and which one worked).
Looks like this method kinda worked for me:
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://wiki.debian.org/wl"
linktext was:"http://wiki.debian.org/wl"
====================================

@nadir: While
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://wiki.debian.org/wl"
linktext was:"http://wiki.debian.org/wl"
====================================
- which uses the Broadcom WL driver *might* work for you, I have had much better success, personally, using the b43 driver, which, on Debian-based systems, comes from the firmware-b43-installer (or the firmware-b43legacy installer, if you have a really old Broadcom wireless interface). Personally, I find the site
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://wiki.debian.org/bcm43xx"
linktext was:"http://wiki.debian.org/bcm43xx"
====================================
, which discusses both b43 and b43legacy, to be more helpful and more reliable. If you read the reference that you provided, notice that it has several caveats. The site
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://wiki.debian.org/bcm43xx"
linktext was:"http://wiki.debian.org/bcm43xx"
====================================
, in my opinion, provides much better drivers, and superior support for any difficulties, which nearly always result due to redundant and conflicting drivers installed on the same system.

If your setup works, fine, but I'd expect that the drivers I mention, in the long run, will serve you much better. Check it out and see if you agree with me or not.

Kinda good news:
I couldn't get it running at all, with none of the options.
I tried for ca 2 hours.
For testing there is no broadcom-sta-source at all, it is mentioned at the Debian wiki. So i enabled sid repos and now"m-a a-i broadcom-sta" failed with an error (for unknown reasons).

Like said above: i am not good with wireless at all. I barely know about blacklisting.

Edit: what i recall is that most options (besides broadcom-sta) didn't gave an error message.
But when i did:
ifconfig
it didn't show the wlan0, while
ifconfig -a
sometimes showed it, sometimes not (but if trying to set it up with wicd-gtk it didn't work)
I also got a strange"rfkill ...." error, which i didn't understand.

My chipset is 4313.
I used the new antiX testing iso from sourceforge.
I will try again, and what you said.
Thanks for your explanations.