[SOLVED] Slackware does not see any wireless connection
SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Broadcom 43xx wireless support (mac80211 stack) (B43)
b43 is a driver for the Broadcom 43xx series wireless devices.
Check "lspci" for something like
"Broadcom Corporation BCM43XX 802.11 Wireless LAN Controller"
to determine whether you own such a device.
This driver supports the new BCM43xx IEEE 802.11G devices, but not
the old IEEE 802.11B devices. Old devices are supported by
the b43legacy driver.
Note that this has nothing to do with the standard that your AccessPoint
supports (A, B, G or a combination).
IEEE 802.11G devices can talk to IEEE 802.11B AccessPoints.
It is safe to include both b43 and b43legacy as the underlying glue
layer will automatically load the correct version for your device.
This driver uses V4 firmware, which must be installed separately using
This driver can be built as a module (recommended) that will be called "b43".
If unsure, say M.
Symbol: B43 [=m]
Type : tristate
Prompt: Broadcom 43xx wireless support (mac80211 stack)
Defined at drivers/net/wireless/b43/Kconfig:1
Depends on: NETDEVICES [=y] && WLAN [=y] && SSB_POSSIBLE [=y] && MAC80211 [=m] && HAS_DMA [=y]
-> Device Drivers
-> Network device support (NETDEVICES [=y])
-> Wireless LAN (WLAN [=y])
Selects: SSB [=m] && FW_LOADER [=y]
I'm not sure if it needs additional firmware, in the kernel-help there's no firmware mentioned
What did you answer to this choice during install?
Which type of network setup would you like?
"static IP" "Use a static IP address to configure ethernet"
"DHCP" "Use a DHCP server to configure ethernet"
"loopback" "Set up a loopback connection (modem or no net)"
"NetworkManager" "Autoconfigure network using NetworkManager"
If you did not choose the last option, then the NetworkManager daemon will not start on boot and you will not be able to configure your network using the NM appet.
Simple to cure though:
They say that the card needs additional firmware, but I have a Broadcom-card in my subnotebook which once needed additional firmware, but with the recenct kernels (> 3) doesn't need it any more.
I made a mistake, it's not Broadcom in my computer.