rMBP broadcom wireless not working in slack64 14.1
Hello,
After some grueling hours of triple booting my rMBP (early-2013; MacBookPro10,1) I finally was able to get clean installs of OS X 10.9.2, Win8.1x64 and Slack64 14.1 to run along side each other. One teensy problem, I have zero internet on slack. 1) Broadcom drivers (according to a lot of forums) generally suck. 2) There is no ethernet jack so I have to move between OS's/computers to download software & sadly, post this, heh 3) Thunderbolt port (thunderbolt to ethernet) doesn't work so I can not do any slack updates This is what I have gathered so far: As of kernel 3.2-rc3+ the broadcom driver wl.ko (which includes the broadcom 4331 device) is already included, just needs to load at start up. I have made the b43xx_blacklist.conf that includes: Code:
blacklist b43 Code:
wl: module license 'unspecified' taints kernel I found another forum suggesting to # blacklist bcma in place of wl.ko but that did not work either. Any help would be greatly appreciated... |
There's a slackbuild for the broadcom-sta driver. Try installing it using sbopkg. If you blacklisted the b43 and ssb modules you should have no problem installing that. I have the 4312 card and use the sta driver and have had no issues.
|
rMBP broadcom wireless not working in slack64 14.1
Already tried it. Was my first thought to use the slackbuild. Same results btw.
|
I saw a post in the ubuntu forums saying that they used the b43 drivers. I'm not sure if this would help your situation or not.
|
Hmm, well, I managed to get it working - somewhat. Fresh install of 14.1 (again), installed b43, b43 fcutter, and b43 firmware from slackbuilds.
I can finally run iwconfig wlan0 up iwlist wlan0 scan It returns maybe 3 networks; taking it as a good sign. Here is where the "somewhat" comes into play. I cannot see any network in wicd nor can I add a hidden network manually. Anything I should try? Here is the dmesg output regarding the wireless device Code:
[ 6.086452] b43-phy0: Broadcom 4331 WLAN found (core revision 29) |
Did you configure WICD correctly? You may need to go into properties and tell wicd that your wireless is using wlan0.
|
I setup wlan0 in wicd properties, never had to do that one before, and now I can see *some* networks, but cant connect to any of them.
|
I prefer network manager over wicd myself as I usually had similar problems with it.
Try setting up network manage to see if you can get it to connect to the networks. That might narrow it down to an issue with wicd then and not some other issue. |
Yes, Wicd works but not for everyone. NetworkManager works a bit better in the case of Broadcom hardware usually.
As far as the STA vs B43 driver issue. One is the freeware driver the other is the OEM driver and both equally work. It doesn't matter if it "taints" the kernel. Plenty of OEM drivers taint the kernel because they are proprietary packages, but they are safe to use, so don't let that message fool you. |
Well I wiped my system clean of b43 completely. Reinstalled network manager from Aliens repo, reinstalled b43-fwcutter, broadcom-sta and b43-firmware from slackbuilds.
I am able to connect to a wireless network without it dropping, however it is god awful slow. Getting in the 13-19Kbps down coming from a 75Mbps pipe something definitely is wrong with that one. Any ideas? Code:
wlan0 IEEE 802.11bg ESSID:"XXXXXXXX" |
with broadcom-sta installed you shouldn't need b43 at all. The sta is the only one I have installed and I also have b43 & ssb blacklisted.
|
Alright this is getting more annoying than I care to admit, this is what I have so far.
b43_blacklist.conf Code:
#Blacklist B43 Drivers Code:
bash-4.2# ifconfig Code:
bash-4.2# iwconfig Code:
bash-4.2# vi rc.modules-3.10.17 I know this card works fine in Win and OS X and gets the full speeds of the pipe on wireless. If i #blacklist wl and comment the modprobe b43 module I get no internet at all, the card doesn't even recognize SSIDs previously used/saved. Also, another great thing that came up, thunderbolt adapter no longer works. In the dmesg i can see that its leased a working IP but KDE Network Manager show it as not connected and nothing I do will force it to connect.doesnt About ready to scrap the idea of slack on this Mac. Ubuntu had the wireless working almost immediately after install. (I only tried it for S&G's) Any last thoughts, things to try etc? |
Quote:
In my notes I have this command, which I added to /etc/rc.d/rc.local to prevent the ssb module loading: Code:
modprobe -r wl; modprobe -r ohci_hcd ; modprobe -r ssb; modprobe wl; modprobe ohci-hcd I find the broadcom-sta driver from SBo to be the best one. I'm a bit confused by your rc.modules-3.10.17 file; are you loading the b43 driver too? Oh, and I have always found the wireless interface to be `eth1' on a Macbook, for some reason. |
Quote: I don't understand why it is showing what should be wlan0 as eth1...?
You might also check the config in /etc/udev/rules.d/70-persistant-net.rules Sometimes they get switched and you have to manually edit the file to switch them back.
|
Code:
bash-4.2# lsmod|grep ssb I did notice at the end of Linux loading (did not show in dmesg) that it said its being used and threw a FATAL ERROR. Code:
bash-4.2# rmmod ssb |
All times are GMT -5. The time now is 01:49 AM. |