-
Notifications
You must be signed in to change notification settings - Fork 513
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[v35][x88_64] Mac Mini Wireless Drivers #7894
Comments
"My question is, should the wireless card already be natively supported," <- theoretically, anything supported by the Linux kernel is supported. Newer cards are usually supported by the "all-firmwares" package buildroot uses. For a 2014 device, it's pretty much guaranteed to be in there. So, problem is likely somewhere else. Like a weird flag telling the chip to shutdown, or another OS holding the chip hostage. Or maybe it is that the 2014 Mac's Wi-Fi card is so obscure that no one has ever tried booting up a Linux-based OS on it and adding support for it specifically. With such little information, all we can do is guess. Could you add your logs and support files? If you don't know how: https://wiki.batocera.org/report_issue |
Absolutely, thanks for the response, and direction. |
Issue: Wireless card in Mac mini (late-2014) not working with V35 Expected result: Working wireless adapter Reproduction steps: Install batocera on internal HDD of Mac, attempt to browse wireless networks- none found. Logs and data: |
@xstrex it's a known problem with the bcm4360 chipset used in the macbooks / mac mini. I already did a PR for it - https://github.com/batocera-linux/batocera.linux/pull/7735/files I will make a build for you to test & verify it works. |
Ah! That makes sense! Yea I unloaded the loaded modules and was trying different installed modules, but not getting anywhere; which led me to the archlinux wiki, and those Happy to test, and thank you! Anything that helps the community/project. |
@xstrex here is the test build - https://drive.google.com/drive/folders/1_bqmR7CoZ78i7DolYt5b-RRqB5c-LPyN?usp=share_link instructions are in the readme to manually upgrade. Once you have manually upgrade you will need to do this... Via terminal, do the following...
|
Sweet, thank you! |
@xstrex ? |
Hi @dmanlfc, I have a TP-Link Archer T9E (which is a It doesn't seem to work in my case. I only see an IPv6 address under I tried to hack it and add |
@icypottle586 did you do this... Via terminal, do the following...
|
Yes I did. Without doing those |
Check your dmesg to see if there is still a conflict |
what particular message I should look for? I remember I grep'd the output and saw only 1 wlan0 message (don't remember the exact, basically like "found BCM4360" or something of that effect). |
anything related to wifi post a link to you dmesg file - |
Looks like I lost my install and it's a different archive up at google drive...would you please reupload it with the bcm4360 driver? Thanks! :-) |
Done |
lspci:
And it only has a link-local IPv6 address (fe80::). There's no b43 or brcm* or anything blacklist'd in |
I apologize, I was out of town and will give this a shot tomorrow. |
Going to try this when I get home. Same deal w/ Mac mini. These boxes are basically useless outside of emulation platforms or home servers. 4gb ram 4260u soldered. Batocera is not unique here however. B43 issues with Linux is due to b43 proprietary nature and has been an issue since the existence of the b43xx chipset. Thanks for working on this! |
@dmanlfc Performed the upgrade, and followed the steps as you suggested, strangely that did not work. Here's the output from the upgrade script:
Afterwards I moved the files in modprobe.d (and rebooted):
Here's the post-reboot
Also, lspci:
Looks like it's still defaulting to the wl driver, even though it's blacklisted. |
|
Well, it's loaded. I can see wlan0 in From the UI scanning for networks still fails, and manually imputing ssid/pass never connects. |
Yes connman is used. There have been reports 5ghz doesn't work well. |
Well the wireless adapter in the Mac is 2.4, and not 5. Also the AP auto-negotiates between 2.4 & 5 (Unifi) based on client abilities. If I'm seeing the wlan0 in ifconfig / iwconfig, should it be working, from a driver standpoint? I'll look through the configuration, and connman to see if I can find the issue. |
and you get a fe80:: IPv6 under wlan0? if so you're seeing exactly what I've been seeing, every symptom matches. |
Yep! after a reboot, from the UI IP is fe80:: for wlan0, and not connected to my ap. |
So, this is interesting. Per Arch docs, I've tried scanning for wifi, but when I try to list services, nothing returns, all from
|
try using wpa_supplicant directly
then then |
A good article to try too - https://shapeshed.com/linux-wifi/ |
No luck; after configuring
Also, what overlay command would I use to save changes made to /etc/wpa_supplicant.conf across reboots? wpa_cli:
iwconfig:
|
@dmanlfc What we are seeing is SSID scan shows absolutely nothing. So 2.4ghz/5ghz, method to get on to SSID, passphrase, or security etc would not matter. The issue is it can’t see any network or SSID at all, not that it sees the SSID and can’t connect to it. I would expect scanning existing SSIDs has to work, and because it doesn’t it’s something at driver level rather than at user-setup level. |
I suspect that the later kernel + all the patches to make it work with said kernel (taken from Arch Linux) are not helping here. There is not a lot I can do at this stage before I go on holiday. |
I’m under the impression these wl drivers are older drivers that newer kernels don’t use anymore, am I correct? Thanks for all the help! :-) |
No certain Broadcom chipsets still need the |
This one probably requires broadcom-sta not wl EDIT: trying to help, my inexperience shows here. wl IS STA, b43 is legacy fwcutter. It's been a while... |
I hear ya, it has been a while. Last time I remember messing with wireless drivers in Linux was patching the aironet module source code to enable promiscuous mode on a pcmcia card (dating myself here)! Anyways, wanted to ask, since we seem to be at a standstill for the moment, anything preventing me from going back to V35? Also, I picked up one of the new wireless usb dongles that supports 2.4Ghz & 5Ghz, to use, even thought it's not officially supported until V36. Any way of manually installing some drivers for that, to get some connectivity? Running an Ethernet cord through my place is not ideal, and getting old. |
Also having this issue :( Internet is not working when installing batocera in a MacBook Pro (retina, 13-inch, Mid 2014) My macbook also has the BCM4360 network adapter. Anyone had any luck? |
@dmanlfc |
I have the same problem with this chipset. The card says bcm84360ng. I can't get WiFi to work on Batocera. Unfortunately, LAN is not an option at this point. Is there still hope that it will work? |
I followed the instructions. but I can't find a .disabled file in the /etc/modprobe.d directory. I can't find blacklist-wl.conf either |
@jens-b |
that is really annoying. Is there an older version of Batocera somewhere that has the corresponding drivers? or how do I create my own build? |
Here is the guide how to build your own: Here is the pull request with all the changes that would add WL driver support but for some reason never got merged into master: If you do not have extensive experience with buildroot linux you are in for a journey ;) Maybe if enough people comment on that pull request it gets the attention of some batocera developers and we will see it in future versions. |
thank you for the detailed explanation. I think this goes far beyond what I know about Linux and what time I can spend in my free time. It's probably easier to use a compatible PC. really annoying |
Yeah - same here. I use a supported cheap USB Wifi-Adapter from Amazon instead. |
It never got merged because it didn't work & I don't have an old MacBook to troubleshoot with. |
@dmanlfc |
I Have one BCM94360 at Fenvi T919, doesn't work too :/ |
I've recently installed batocera on a Late-2014 Mac Mini; everything works flawlessly except for the internal wireless card.
Specs show that it's got a 802.11ac Wi-Fi (802.11a/b/g/n backwards compatible) and Bluetooth 4.0 standard.
lspci
for the wireless card showsbcm4360
chipset.A quick search suggest that shows that ArchLinux supports the chipset.
Now I know from your wiki I can't just blindly install a package with pacman, as it relies on your batocera-store, and the repos it depends on.
My question is, should the wireless card already be natively supported, since it's broadcom, and a few years old, or should I go down the path of making my own package and adding it myself?
Cheers
The text was updated successfully, but these errors were encountered: