-   Slackware (
-   -   Need Help... How do I get my built in wireless to work in Slack 13.37 (

KidZero 09-06-2011 09:21 AM

Need Help... How do I get my built in wireless to work in Slack 13.37
Ok so I checked to see if the system could find my wireless...
This is what I got
IEEE 802.11bg ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=0 dBm Retry long limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:off

so therefor I know when its probed its located..
is it not working because Power Management:Off
or is it because I have to run a certain command in bash..
If so can anyone help with this problem with detailed info?

Thank You

croxen 09-06-2011 11:20 AM

There are quite a few Slackware wireless tutorials on the web. Here's just one:

But just to get things started, since I know the system has loaded the driver, and I know my device node for my particular onboard wireless is "eth1" (for some it will be something else, like "wlan0"), and I know the name for my wireless network access point is MYNETWORK (which assigns addresses via DHCP), I start by issuing a couple of commands from root:

iwconfig eth1 essid MYNETWORK

and then:

dhcpcd eth1

to see if I can get an address lease. If I get a lease from MYNETWORK and dhcpcd forks to the background, ifconfig eth1 should show that the interface eth1 now has has an address and netmask and everything is ready to go.

Robert.Thompson 09-06-2011 11:41 AM

May be this will help:

scam 09-06-2011 12:26 PM

Why not try wicd till you figure out the commands to setup your wifi card. I haven't used wifi for awhile so commands pretty vague.

iwlist eth1 <- show AP's (access points)
iwconfig eth1 essid <my router>

Then if it associates to the router
dhcpcd eth1

Or install wicd
slackpkg install wicd
gpasswd -a <username> plugdev,netdev

Not sure if you need both added to user, but you will need to log out and then log back in for the groups to be added. Then start wicd up...hope that's helpful.

KidZero 09-06-2011 12:41 PM

Wicd hasnt been working for me.. and all i have is wireless internet im at a wifi hotspot and decided to try and get the built in wireless to work other than my verizon wireless modem... Ive been working on that one for days trying to usb_modeswitch the wireless usb modem

scam 09-06-2011 01:01 PM

What wifi card is it? lspci ..what does it show? might help more.

KidZero 09-06-2011 01:22 PM

02:02.0 Network controller: Broadcom Corporation BCM4306 802.11b/g Wireless LAN Controller (rev 03)

scam 09-06-2011 01:35 PM

You might need the firmware, I have a card similar to that...but not sure of the spec..I had to install the firmware from slackbuilds... ...But i can't guarantee it's for your card. If you get no errors from ifconfig eth* up shouldn't be a firmware issue ...but I'm not wifi expert.

SqdnGuns 09-06-2011 02:18 PM

Once you get the firmware installed and using Wicd, be sure to go into the settings and tell it the wireless is wlan0 or else Wicd has no idea that there is a wireless card.

Konphine 09-06-2011 04:07 PM

I believe Broadcom 43XX cards require "ndiswrapper" which can be found in the SlackBuilds repository here:

scam 09-07-2011 03:46 AM

I've just booted up my other machine with the broadcom wifi card and lsci shows..

00:0e.0 Network controller: Broadcom Corporation BCM4318 [AirForce One 54g] 802.11g Wireless LAN Controller (rev 02)

I installed these packages from

Root > ls /var/log/packages/b43*

croxen 09-07-2011 08:35 AM

Broadcom 43xx cards don't require the NDIS wrapper. Some will work with the standard b43 driver, others work best if you compile/install/configure Broadcom's own "wl" kernel module (which is what I use for my particular Broadcom wireless "n" card in Slack 13.37).

The standard b43 driver doc, which includes discussion (and links) of such things as proprietary Broadcom firmware and the vast variety of 43xx cards here :

Or, if you choose, the Broadcom wl driver source (and the patch, which you'll need to compile the driver in 2.6.37 and above) is here:

Broadcom's own doc pertaining to the wl driver is here:

The wl module and the b43 module family are mutually exclusive. To load wl you have to unload bcm43xx, b43, b43legacy, and ssb. To load b43 (and related), you need to unload wl if currently loaded.

onebuck 09-07-2011 10:01 AM



Originally Posted by croxen (Post 4463821)
The wl module and the b43 module family are mutually exclusive. To load wl you have to unload bcm43xx, b43, b43legacy, and ssb. To load b43 (and related), you need to unload wl if currently loaded.

If you use the 'wl' module then be sure to blacklist the modules in '/etc/modprobe.d/blacklist.conf': bcm43xx, b43, b43legacy. 'ssb' will be loaded with 'wl'.

mRgOBLIN 09-07-2011 10:39 PM

I just installed a laptop with the same chipset.

I simply had to extract and install the firmware with fwcutter after which wicd was able to scan and connect just fine.

ReaperX7 09-07-2011 11:47 PM

Installing these packages in this order will enable your wireless card with any network management tool (including Wicd):

1. b43-fwcutter (B43XX Firmware Cutter)

2. b43-firmware (B43XX Firmware Package)

Install b43-fwcutter first and then b43-firmware.

You should not install the "wl" (broadcom-sta) driver as it's designed only for these a/b/g/n chipsets:


And the b43legacy-firmware is for the older Broadcom chipsets from revision 2 and earlier, as well as 802.11-B only devices.

You need the firmware plain and simple really. And yes NDISWrapper is not required for your wireless card. NDISWrapper is mostly for USB devices used for wireless networking purposes.

The only Broadcom chip not yet supported by any driver or firmware package is the BCM4331.

All times are GMT -5. The time now is 10:33 AM.