search

batocera-linux / batocera.linux

batocera.linux
https://batocera.org
Other
1.95k stars 501 forks source link

[v35][x88_64] Mac Mini Wireless Drivers #7894

Open xstrex opened 1 year ago

xstrex commented 1 year ago

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 shows bcm4360 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

Hew-ux commented 1 year ago

"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

xstrex commented 1 year ago

Absolutely, thanks for the response, and direction.

xstrex commented 1 year ago

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. Ifconfig only shows eth0 lspci shows bcm4360 wireless adapter. See (anonymized) attached logs.

Logs and data: batocera-support-20230112162806.tar.gz

dmanlfc commented 1 year ago

@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. The problem is, the wl driver conflicts with some existing linux kernel modules so we have to blacklist them...

xstrex commented 1 year ago

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 wl drivers.

Happy to test, and thank you! Anything that helps the community/project.

dmanlfc commented 1 year ago

@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...

cd /etc/modprobe.d Rename this so that the .disabled is removed from the name - i.e. macbook-wifi.conf

xstrex commented 1 year ago

Sweet, thank you! I just grabbed all the necessary files, and will get this done in the AM. Thanks for throwing this together so quickly! I see what your doing in the manual-upgrade.sh also, easy enough (I'm a Linux eng by trade).

dmanlfc commented 1 year ago

@xstrex ?

icypottle586 commented 1 year ago

Hi @dmanlfc, I have a TP-Link Archer T9E (which is a 03:00.0 Network controller: Broadcom Inc. and subsidiaries BCM4360 802.11ac Wireless Network Adapter (rev 03), tested both manual-upgrade.sh and the full image.

It doesn't seem to work in my case. I only see an IPv6 address under ifconfig and since my setup disallows IPv6 I get no connection there. Also SSID scan doesn't seem to work either.

I tried to hack it and add IPv6=off to ./etc/init.d/S08connman so it would add it to /var/lib/connman/batocera_wifi.config, and still couldn't get an IPv4 address.

dmanlfc commented 1 year ago

@icypottle586 did you do this...

Via terminal, do the following...

cd /etc/modprobe.d Rename this so that the .disabled is removed from the name - i.e. macbook-wifi.conf

mv macbook-wifi.conf.disabled macbook-wifi.conf Also rename the file blacklist-wl.conf to blacklist-wl.conf.disabled. mv blacklist-wl.conf blacklist-wl.conf.disabled Afterwards type: batocera-save-overlay This will make the changes permanent, then reboot.

icypottle586 commented 1 year ago

@icypottle586 did you do this...

Via terminal, do the following...

cd /etc/modprobe.d Rename this so that the .disabled is removed from the name - i.e. macbook-wifi.conf

mv macbook-wifi.conf.disabled macbook-wifi.conf Also rename the file blacklist-wl.conf to blacklist-wl.conf.disabled. mv blacklist-wl.conf blacklist-wl.conf.disabled Afterwards type: batocera-save-overlay This will make the changes permanent, then reboot.

Yes I did. Without doing those batocera_wifi.config wouldn't show up and there would be no wlan0 under ifconfig.

dmanlfc commented 1 year ago

Check your dmesg to see if there is still a conflict

icypottle586 commented 1 year ago

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).

dmanlfc commented 1 year ago

anything related to wifi any lines with - b43 & brcm*

post a link to you dmesg file - dmesg > dmesg.txt

icypottle586 commented 1 year ago

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! :-)

dmanlfc commented 1 year ago

Done

icypottle586 commented 1 year ago

lspci:

03:00.0 Network controller: Broadcom Inc. and subsidiaries BCM4360 802.11ac Wireless Network Adapter (rev 03)
    Subsystem: Broadcom Inc. and subsidiaries BCM4360 802.11ac Wireless Network Adapter
    Kernel driver in use: wl
    Kernel modules: bcma, wl
lsmod | grep wl
wl                   6471680  0

And it only has a link-local IPv6 address (fe80::).

There's no b43 or brcm* or anything blacklist'd in lsmod report.

xstrex commented 1 year ago

@xstrex ?

I apologize, I was out of town and will give this a shot tomorrow.

jonhaller commented 1 year ago

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!

xstrex commented 1 year ago

@dmanlfc Performed the upgrade, and followed the steps as you suggested, strangely that did not work.

Here's the output from the upgrade script:

[root@BATOCERA /userdata/system/upgrade]# ./manual-upgrade.sh
cp: can't stat '/boot/config.txt': No such file or directory
batocera-boot.conf
boot/
boot/initrd.gz
boot/batocera.board
boot/syslinux/
boot/syslinux/libutil.c32
boot/syslinux/syslinux.cfg
boot/syslinux/menu.c32
boot/linux
boot/batocera.update
boot/syslinux.cfg
EFI/
EFI/BOOT/
EFI/BOOT/bootia32.efi
EFI/BOOT/bootx64.efi
EFI/BOOT/libutil.c32
EFI/BOOT/ldlinux.e32
EFI/BOOT/ldlinux.e64
EFI/BOOT/syslinux.cfg
EFI/BOOT/menu.c32
EFI/syslinux.cfg
tools/
tools/btrfs_on_windows/
tools/btrfs_on_windows/readme.txt
tools/btrfs_on_windows/x86/
tools/btrfs_on_windows/x86/ubtrfs.dll
tools/btrfs_on_windows/x86/mkbtrfs.exe
tools/btrfs_on_windows/x86/btrfs.sys
tools/btrfs_on_windows/x86/shellbtrfs.dll
tools/btrfs_on_windows/x64/
tools/btrfs_on_windows/x64/ubtrfs.dll
tools/btrfs_on_windows/x64/mkbtrfs.exe
tools/btrfs_on_windows/x64/btrfs.sys
tools/btrfs_on_windows/x64/shellbtrfs.dll
tools/btrfs_on_windows/btrfs.inf
tools/btrfs_on_windows/btrfs.cat
mv: can't rename 'config.txt.upgrade': No such file or directory

Reboot now DMAN!

Afterwards I moved the files in modprobe.d (and rebooted):

total 22K
-rw-r--r--    1 root     root         202 Jan 11 06:06 8188eu.conf
-rw-r--r--    1 root     root          46 Jul 10  2022 8192cu.conf
-rw-r--r--    1 root     root         325 Jul 10  2022 blacklist-ath_pci.conf
-rw-r--r--    1 root     root        1.6K Jul 10  2022 blacklist.conf
-rw-r--r--    1 root     root         210 Jul 10  2022 blacklist-firewire.conf
-rw-r--r--    1 root     root         697 Jul 10  2022 blacklist-framebuffer.conf
-rw-r--r--    1 root     root         156 Jul 10  2022 blacklist-modem.conf
lrwxrwxrwx    1 root     root          47 Jan  7 13:08 blacklist-nouveau.conf -> /var/run/nvidia/modprobe/blacklist-nouveau.conf
-rw-r--r--    1 root     root        1.0K Jul 10  2022 blacklist-oss.conf
-rw-r--r--    1 root     root          50 Jan  7 13:11 blacklist-r8169.conf
-rw-r--r--    1 root     root         583 Jul 10  2022 blacklist-rare-network.conf
-rw-r--r--    1 root     root        1.1K Jul 10  2022 blacklist-watchdog.conf
-rw-r--r--    1 root     root          13 Jan 12 20:34 blacklist-wl.conf.disabled
-rw-r--r--    1 root     root          68 Jan 11 06:06 bluetooth.conf
-rw-r--r--    1 root     root          23 Jan  7 09:39 hid-nintendo.conf
-rw-r--r--    1 root     root         719 Jan 12 20:09 intel-dsp.conf
-rw-r--r--    1 root     root         499 Jan 12 20:34 macbook-wifi.conf
lrwxrwxrwx    1 root     root          40 Jan  7 13:08 nvidia-drm.conf -> /var/run/nvidia/modprobe/nvidia-drm.conf
-rwxr-xr-x    1 root     root          73 Jan 11 06:06 rtw88.conf
-rw-r--r--    1 root     root          33 Jan  7 09:40 xone-blacklist.conf
-rw-r--r--    1 root     root         321 Jan  7 09:40 xpadneo.conf

Here's the post-reboot lsmod:

Module                  Size  Used by
8021q                  40960  0
garp                   16384  1 8021q
stp                    16384  1 garp
mrp                    20480  1 8021q
llc                    16384  2 stp,garp
hid_sony               49152  0
hid_playstation        32768  0
led_class_multicolor    16384  1 hid_playstation
ff_memless             20480  2 hid_sony,hid_playstation
hidp                   32768  1
ledtrig_timer          16384  0
rfcomm                 90112  4
algif_hash             16384  1
algif_skcipher         16384  1
af_alg                 32768  6 algif_hash,algif_skcipher
bnep                   28672  2
iptable_nat            16384  0
nf_nat                 57344  1 iptable_nat
nf_conntrack          172032  1 nf_nat
nf_defrag_ipv6         24576  1 nf_conntrack
nf_defrag_ipv4         16384  1 nf_conntrack
libcrc32c              16384  2 nf_conntrack,nf_nat
iptable_mangle         16384  0
snd_seq_dummy          16384  0
snd_hrtimer            16384  1
snd_seq                86016  7 snd_seq_dummy
snd_seq_device         16384  1 snd_seq
intel_rapl_msr         20480  0
intel_rapl_common      32768  1 intel_rapl_msr
x86_pkg_temp_thermal    20480  0
snd_hda_codec_hdmi     81920  1
intel_powerclamp       20480  0
coretemp               20480  0
btusb                  65536  0
btrtl                  28672  1 btusb
kvm_intel             372736  0
btbcm                  24576  1 btusb
btmtk                  16384  1 btusb
btintel                45056  1 btusb
kvm                  1114112  1 kvm_intel
bluetooth             942080  39 btrtl,hidp,btmtk,btintel,btbcm,bnep,btusb,rfcomm
ecdh_generic           16384  2 bluetooth
ecc                    40960  1 ecdh_generic
irqbypass              16384  1 kvm
joydev                 28672  0
input_leds             16384  0
applesmc               24576  0
hid_appleir            16384  0
i915                 3227648  9
crct10dif_pclmul       16384  1
crc32_pclmul           16384  0
ghash_clmulni_intel    16384  0
sha512_ssse3           45056  0
snd_hda_codec_cirrus    24576  1
aesni_intel           393216  4
snd_hda_codec_generic    98304  1 snd_hda_codec_cirrus
drm_buddy              20480  1 i915
crypto_simd            16384  1 aesni_intel
wl                   6471680  0
cryptd                 28672  3 crypto_simd,ghash_clmulni_intel
ledtrig_audio          16384  1 snd_hda_codec_generic
ttm                    90112  1 i915
snd_hda_intel          57344  0
drm_display_helper    196608  1 i915
snd_intel_dspcfg       36864  1 snd_hda_intel
snd_intel_sdw_acpi     20480  1 snd_intel_dspcfg
efi_pstore             16384  0
snd_hda_codec         184320  4 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec_cirrus
snd_hda_core          118784  5 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_codec_cirrus
drm_kms_helper        233472  2 drm_display_helper,i915
mei_me                 53248  0
snd_hwdep              16384  1 snd_hda_codec
lpc_ich                28672  0
snd_pcm               151552  4 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_core
mei                   155648  1 mei_me
usbhid                 65536  1 hid_sony
fb_sys_fops            16384  1 drm_kms_helper
tg3                   192512  0
snd_timer              40960  3 snd_seq,snd_hrtimer,snd_pcm
syscopyarea            16384  1 drm_kms_helper
sysfillrect            16384  1 drm_kms_helper
sysimgblt              16384  1 drm_kms_helper
video                  65536  1 i915
mac_hid                16384  0
wmi                    36864  1 video

Also, lspci:

[root@BATOCERA /etc/modprobe.d]# lspci -vv |grep -A66 02:00.0
02:00.0 Network controller: Broadcom Inc. and subsidiaries BCM4360 802.11ac Wireless Network Adapter (rev 03)
        Subsystem: Apple Inc. BCM4360 802.11ac Wireless Network Adapter
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0, Cache Line Size: 256 bytes
        Interrupt: pin A routed to IRQ 18
        Region 0: Memory at a0600000 (64-bit, non-prefetchable) [size=32K]
        Region 2: Memory at a0400000 (64-bit, non-prefetchable) [size=2M]
        Capabilities: [48] Power Management version 3
                Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
                Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=2 PME-
        Capabilities: [58] MSI: Enable- Count=1/1 Maskable- 64bit+
                Address: 0000000000000000  Data: 0000
        Capabilities: [68] Vendor Specific Information: Len=44 <?>
        Capabilities: [ac] Express (v2) Endpoint, MSI 00
                DevCap: MaxPayload 256 bytes, PhantFunc 0, Latency L0s <4us, L1 unlimited
                        ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset- SlotPowerLimit 10W
                DevCtl: CorrErr+ NonFatalErr+ FatalErr+ UnsupReq+
                        RlxdOrd+ ExtTag- PhantFunc- AuxPwr+ NoSnoop+
                        MaxPayload 128 bytes, MaxReadReq 1024 bytes
                DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr+ TransPend-
                LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Exit Latency L0s <2us, L1 <32us
                        ClockPM+ Surprise- LLActRep- BwNot- ASPMOptComp+
                LnkCtl: ASPM L0s L1 Enabled; RCB 64 bytes, Disabled- CommClk+
                        ExtSynch- ClockPM+ AutWidDis- BWInt- AutBWInt-
                LnkSta: Speed 2.5GT/s, Width x1
                        TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
                DevCap2: Completion Timeout: Range ABCD, TimeoutDis+ NROPrPrP- LTR+
                         10BitTagComp- 10BitTagReq- OBFF Via WAKE#, ExtFmt- EETLPPrefix-
                         EmergencyPowerReduction Not Supported, EmergencyPowerReductionInit-
                         FRS- TPHComp- ExtTPHComp-
                         AtomicOpsCap: 32bit- 64bit- 128bitCAS-
                DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- LTR+ 10BitTagReq- OBFF Disabled,
                         AtomicOpsCtl: ReqEn-
                LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance- SpeedDis-
                         Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
                         Compliance Preset/De-emphasis: -6dB de-emphasis, 0dB preshoot
                LnkSta2: Current De-emphasis Level: -3.5dB, EqualizationComplete- EqualizationPhase1-
                         EqualizationPhase2- EqualizationPhase3- LinkEqualizationRequest-
                         Retimer- 2Retimers- CrosslinkRes: unsupported
        Capabilities: [100 v1] Advanced Error Reporting
                UESta:  DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
                UEMsk:  DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
                UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
                CESta:  RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr-
                CEMsk:  RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr+
                AERCap: First Error Pointer: 00, ECRCGenCap+ ECRCGenEn- ECRCChkCap+ ECRCChkEn-
                        MultHdrRecCap- MultHdrRecEn- TLPPfxPres- HdrLogCap-
                HeaderLog: 00000000 00000000 00000000 00000000
        Capabilities: [13c v1] Device Serial Number 6c-40-00-ff-ff-00-00-01
        Capabilities: [150 v1] Power Budgeting <?>
        Capabilities: [160 v1] Virtual Channel
                Caps:   LPEVC=0 RefClk=100ns PATEntryBits=1
                Arb:    Fixed- WRR32- WRR64- WRR128-
                Ctrl:   ArbSelect=Fixed
                Status: InProgress-
                VC0:    Caps:   PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
                        Arb:    Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256-
                        Ctrl:   Enable+ ID=0 ArbSelect=Fixed TC/VC=ff
                        Status: NegoPending- InProgress-
        Capabilities: [1b0 v1] Latency Tolerance Reporting
                Max snoop latency: 3145728ns
                Max no snoop latency: 3145728ns
        Capabilities: [220 v1] Physical Resizable BAR
                BAR 2: current size: 2MB, supported: 1MB 2MB
        Kernel driver in use: wl
        Kernel modules: bcma, wl

Looks like it's still defaulting to the wl driver, even though it's blacklisted.

dmanlfc commented 1 year ago

wl is the driver we want it to use

xstrex commented 1 year ago

Well, it's loaded. I can see wlan0 in ifconfig as well as iwconfig, is batocera using some kind of network manager, like NM, or conman or something?

From the UI scanning for networks still fails, and manually imputing ssid/pass never connects.

dmanlfc commented 1 year ago

Yes connman is used.

There have been reports 5ghz doesn't work well. Try to separate the ssid so you use 2.4ghz.

xstrex commented 1 year ago

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.

icypottle586 commented 1 year ago

From the UI scanning for networks still fails, and manually imputing ssid/pass never connects.

and you get a fe80:: IPv6 under wlan0? if so you're seeing exactly what I've been seeing, every symptom matches.

xstrex commented 1 year ago

Yep! after a reboot, from the UI IP is fe80:: for wlan0, and not connected to my ap.

xstrex commented 1 year ago

So, this is interesting.

Per Arch docs, I've tried scanning for wifi, but when I try to list services, nothing returns, all from connmanctl:

connmanctl> scan wifi
Scan completed for wifi
connmanctl> services
*AR Wired                ethernet_ac87a311aff3_cable
connmanctl>
dmanlfc commented 1 year ago

try using wpa_supplicant directly

wpa_passphrase <your-SSID> <your-passphrase> | tee /etc/wpa_supplicant.conf note: replace SSID & passphrase accordingly ^

then wpa_supplicant -B -c /etc/wpa_supplicant.conf -i wlan0

then iwconfig if that shows it associated to the wifi - then toggle wifi in batocera to try to get an IP.

dmanlfc commented 1 year ago

A good article to try too - https://shapeshed.com/linux-wifi/

xstrex commented 1 year ago

No luck; after configuring wpa_supplicant.conf and rerunning it as a daemon, with the config file as stated above. iwconfig remains Not-Associated, and wpa_cli is unable to scan..

[root@BATOCERA /userdata/system]# vi /etc/wpa_supplicant.conf
[root@BATOCERA /userdata/system]# wpa_supplicant -B -c /etc/wpa_supplicant.conf -i wlan0
Successfully initialized wpa_supplicant
[root@BATOCERA /userdata/system]# wpa_cli
wpa_cli v2.10
Copyright (c) 2004-2022, Jouni Malinen <j@w1.fi> and contributors

This software may be distributed under the terms of the BSD license.
See README for more details.

Selected interface 'wlan0'

Interactive mode

<3>CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
<3>CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
<3>CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
<3>CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
<3>CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
<3>CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
<3>CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
<3>CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
> scan
OK
<3>CTRL-EVENT-SCAN-FAILED ret=-22
> scan_results
bssid / frequency / signal level / flags / ssid
>

Also, what overlay command would I use to save changes made to /etc/wpa_supplicant.conf across reboots? batocera_save_overlay?

wpa_cli:

> list_networks
network id / ssid / bssid / flags
0       <ssid>  any
> enable_network 0
OK
> status
wpa_state=DISCONNECTED
address=6c:40:08:b6:49:9c

iwconfig:

wlan0     IEEE 802.11  ESSID:off/any
          Mode:Managed  Access Point: Not-Associated   Tx-Power=200 dBm
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
icypottle586 commented 1 year ago

@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.

dmanlfc commented 1 year ago

@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 user-setup.

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.

icypottle586 commented 1 year ago

@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 user-setup.

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.

@dmanlfc

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! :-)

dmanlfc commented 1 year ago

@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 user-setup.

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.

@dmanlfc

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 wl driver module. Especially those from a Mac.

jonhaller commented 1 year ago

@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 user-setup.

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.

@dmanlfc 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 wl driver module. Especially those from a Mac.

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...

xstrex commented 1 year ago

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.

FranDepascuali commented 1 year ago

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?

donbernhardo commented 11 months ago

@dmanlfc I was trying to give it a shot but the current build on your google drive (39-dev) seems not to include the wl kernel module anymore. Is there any chance to get it?

jens-b commented 11 months ago

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?

jens-b commented 11 months ago

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 what am I doing wrong?

donbernhardo commented 11 months ago

@jens-b The build that is currently in that google drive does not contain the wl kernel module and associated changes anymore. To my knowledge there is currently no way other than bulding your own custom batocera build to support the wl wifi driver. Needles to say that this is inplausable for most users.

jens-b commented 11 months ago

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?

donbernhardo commented 11 months ago

Here is the guide how to build your own: https://wiki.batocera.org/compile_batocera.linux

Here is the pull request with all the changes that would add WL driver support but for some reason never got merged into master: https://github.com/batocera-linux/batocera.linux/pull/7735

If you do not have extensive experience with buildroot linux you are in for a journey ;) I abandoned the idea of building my own due to the complexity getting it all to work. Not even talking about the possibility of additional kernel patches for the WL driver you would have to get from Arch in order to make that driver work with the newer kernel. The pull request was way back in batocera 35.

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.

jens-b commented 11 months ago

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

donbernhardo commented 11 months ago

Yeah - same here. I use a supported cheap USB Wifi-Adapter from Amazon instead.

dmanlfc commented 11 months ago

It never got merged because it didn't work & I don't have an old MacBook to troubleshoot with.

donbernhardo commented 11 months ago

@dmanlfc I understand. Thanks for trying it though. I would be available for testing, troubleshooting and trying things out should you ever decide to come back to this.

Duduzera1997 commented 9 months ago

I Have one BCM94360 at Fenvi T919, doesn't work too :/