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.
The broadcom-sta driver works on kernel 3.x as well. I've used it on my -current prior to building my own mainline kernel. Just watch out for its aggressive power management when in use (e.g. it blocks packets when on battery power, so I had to do 'iwconfig wlan0 power off' to get my connection back.)
I have the b43 driver in usage and attempted to load the firmware, but for some reason Wicd still says that there is no wireless connection, when I have a wireless router in-use. I loaded the 5.100.138 firmware but so far, nothing.
I attempted to build the STA driver but the compile failed. After searching the internet I found a patch and attempted and compiled it manually using this patch: http://www.mindwerks.net/2011/11/wir...12-3-2-kernel/ and instructions on the webpage, but even with the driver module loaded, it still fails to recognize the device. I'm still troubleshooting this, so hopefully, I'll find out what I'm doing wrong.
@ReaperX7: You also have to blacklist the 'b43' and 'ssb' modules if you're using the STA driver. I've written a guide on Slackwiki for this since it's the most frequently asked hardware question on the Slackware IRC channel. See if it helps: http://slackwiki.com/Broadcom_Wireless. Of course, you need to add the patch to the Slackbuild first, since you're using kernel 3.X.
Distribution: Slackware 14.1 64 bit MLED with XFCE 4.12
I have the same wireless card and when I set it up using wicd I would iwconfig to find out if the wireless card was listed as eth1 or eth2, etc and then go into wicd and go to preferences and then tell wicd what the wireless was listed as (eth1 or eth2). Sometimes I would notice that my wireless connection would be renamed from eth1 to eth2 and I would just repeat this process to get it working.
I have it working! I am using it right now to write these lines
Greetings fellow Slackers:
I have been upgrading from 13.37 to -current for the last week.
I own a Broadcom wireless card ( 04:00.0 Network controller: Broadcom Corporation BCM4312 802.11b/g LP-PHY (rev 01), pci 0000:04:00.0: [14e4:4315] type 0 class 0x000280 ). I can use it with no problems whatsoever, with the standard Slackware normal and huge 2.6.37 and 2.6.38 (testing) kernels, and the firmware version 126.96.36.199, it just works and causes no problems at all.
During the upgrade process, the first thing I tested was the kernel from -current. As usual, I test the huge kernel first. It loads with no problems, with just one line complaining about my sound card (but it works anyway, it just complains that it is initialized with a generic method or something). The wireless driver worked with kernel 3.2 and the 4.178 firmware.
After that I upgraded everything to -current, and everything worked except the Phonon MPlayer backend (one of the libraries, it blocks the KDE sound system but not most apps specially music players - I can live without the start up sound), a complaint with no side effects about modprobe -bv acpi unexpectedly exiting, and the wireless card (which is actually serious from my point of view as I needed to reboot time after time just to test the card and connect to the internet and change the firmware, and so on...). So I decided to investigate it first.
I tried the 5.100.138 firmware. It does not work. It does bring the interface up but it does not work. I tried reloading the module, reloading udev, playing with udev persistent network rules. No success. I had to switch between firmware versions as the 1337 kernel seems to hate 5.100.138. Every time I tried to load the card it gave me errors about flags, link not ready, etc etc. (checking the logs).
Then I remembered that it worked the first time, even with firmware version 4, before upgrading to -current, with just the 3.2.23 kernel. I thought it might be udev. So I checked the changelog for any possible issues and then I just downgraded udev to 13.37 udev (udev 165 build 2). So that's how I am able to write these lines. It just works. Firmware 4.178. Huge Slackware -current kernel.
During the downgrade I remember having seen some lines about a b43xx rules file. I'll investigate about it later. Maybe I might be able to use udev 175 (which would be good) but I don't want to push my luck. Ah, the modprobe -bv complaint is still there even after I downgraded udev. So it's most likely not related to udev.
Okay I'm not using the Broadcom-STA driver and I'm using the default B43 drivers and SlackBuild B43-FWCutter + B43-Firmware package and the Wireless finally does show up after the last udev update (Thanks Patrick!!!), but the wireless still has problems with connectivity such as the wireless will connect to the router, get an IP address, but if I open a web browser I can not get any web pages to come up at all like I'm not even connected to the internet at all. This has been a continuous issue for me with this netbook regarding the wireless...
I can connect to the modem and network but there is not internet or network connectivity between devices.
At this point, I really need help figuring out what is going on.
Is this a DNS issue?
Is this a problem with the B43 driver and firmware (if it is getting a working STA Slackbuild to compile is an issue requiring a patch and editing SlackBuilds is not my strong point)?
Or is this just a problem with the BCM4312 itself such as a hardware failure?
Here's my grep readout:
[13.229750] b43-phy0: Broadcom 4312 WLAN found (core revision 15)
ifconfig and iwconfig both show an IPv4 address for each interface.
Update (additional info):
I did once have trouble with a router using DNSMasq and had to keep it disabled on the router for Linux based Networks to connect using Wi-Fi.