rMBP broadcom wireless not working in slack64 14.1
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.
Distribution: Slack64-Current, Windows 11, EndeavourOS
Posts: 97
Rep:
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:
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.
Distribution: Slack64-Current, Windows 11, EndeavourOS
Posts: 97
Original Poster
Rep:
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)
[ 6.087197] b43-phy0: Found PHY: Analog 9, Type 7 (HT), Revision 1
[ 6.087827] apple_gmux: gmux device not present
[ 6.088357] Broadcom 43xx driver loaded [ Features: PMNLS ]
[ 6.094237] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
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.
Distribution: Slack64-Current, Windows 11, EndeavourOS
Posts: 97
Original Poster
Rep:
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"
Mode:Managed Frequency:2.412 GHz Access Point: 9C:1C:12:18:8D:12
Bit Rate=24 Mb/s Tx-Power=20 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Link Quality=70/70 Signal level=0 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:10 Invalid misc:0 Missed beacon:0
All of this combined as they are right now I can connect but it either drops to <1Kb/s speeds or tops out at 5Mb/s never gets the full bandwidth of my pipe (75M down / 50M up).
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)
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.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.