Need Help... How do I get my built in wireless to work in Slack 13.37
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
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 ESSIDff/any Mode:Managed Access Point: Not-Associated Tx-Power=0 dBm Retry long limit:7 RTS thrff Fragment thrff Encryption keyff Power Managementff
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?
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.
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.
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
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...http://slackbuilds.org/result/?search=Broadcom&sv=13.37 ...But i can't guarantee it's for your card. If you get no errors from ifconfig eth* up ....it shouldn't be a firmware issue ...but I'm not wifi expert.
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.
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 : http://linuxwireless.org/en/users/Drivers/b43
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.
<snip>
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'.
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.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.