Slackware - ARM This forum is for the discussion of Slackware ARM. |
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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
|
|
04-06-2018, 09:34 AM
|
#1
|
Slackware Contributor
Registered: May 2015
Distribution: Slackware
Posts: 1,911
|
Raspberry Pi 3 B+ Wifi NIC not found
I installed my Raspberry Pi 3 B+ using the sarpi3-installer_slack14.2_30Mar18_sp1.img.xz image. I did a ftp network installation using ftp.slackware.org.uk. It boots up just fine and the ethernet port works. As I've said in another thread, I plan to use this Pi as a replacement for my wireless router.
I could use the rpi-update script, but would prefer not to. I prefer to run the 14.2 image instead of -current. It looks like the onboard wireless NIC is not recognized and no kernel module is loaded.
Code:
# iwconfig && lsusb && lsusb -t
lo no wireless extensions.
eth1 no wireless extensions.
Bus 001 Device 007: ID 046d:c227 Logitech, Inc. G15 Refresh Keyboard
Bus 001 Device 005: ID 046d:c226 Logitech, Inc. G15 Refresh Keyboard
Bus 001 Device 004: ID 046d:c223 Logitech, Inc. G11/G15 Keyboard / USB Hub
Bus 001 Device 006: ID 0424:7800 Standard Microsystems Corp.
Bus 001 Device 003: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
Bus 001 Device 002: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=dwc_otg/1p, 480M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
|__ Port 1: Dev 3, If 0, Class=Hub, Driver=hub/3p, 480M
|__ Port 1: Dev 6, If 0, Class=Vendor Specific Class, Driver=lan78xx, 480M
|__ Port 2: Dev 4, If 0, Class=Hub, Driver=hub/4p, 12M
|__ Port 1: Dev 5, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M
|__ Port 1: Dev 5, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
|__ Port 4: Dev 7, If 0, Class=Human Interface Device, Driver=usbhid, 12M
# ifconfig wlan0 up
wlan0: ERROR while getting interface flags: No such device
# ifconfig wlan1 up
wlan1: ERROR while getting interface flags: No such device
I have the following kernel packages installed:
Code:
# ls /var/log/packages/| grep kernel
kernel-firmware-20160628git-noarch-1
kernel-headers-4.4.14-arm-1
kernel-modules-armv5-4.4.14_armv5-arm-2
kernel-modules-sarpi3-4.14.31-armv7-1_slack14.2_30Mar18_sp1
kernel-source-4.4.14-arm-2
kernel_armv5-4.4.14-arm-2
kernel_sarpi3-4.14.31-armv7-1_slack14.2_30Mar18_sp1
I updated the kernel firmware to kernel-firmware-20180330_a3be6d4-noarch-1_slack14.2.
I have the following dmesg output:
Code:
# dmesg | grep brcmfmac
[ 3.983580] brcmfmac: F1 signature read @0x18000000=0x15264345
[ 3.990694] brcmfmac: brcmf_fw_map_chip_to_name: using brcm/brcmfmac43455-sdio.bin for chip 0x004345(17221) rev 0x000006
[ 4.008543] usbcore: registered new interface driver brcmfmac
[ 4.063628] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43455-sdio.txt failed with error -2
[ 5.141476] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 0x50
[ 6.153155] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 0x50
Last edited by mralk3; 04-06-2018 at 10:07 AM.
Reason: Added dmesg output
|
|
|
04-06-2018, 11:19 AM
|
#2
|
Slackware Contributor
Registered: May 2015
Distribution: Slackware
Posts: 1,911
Original Poster
|
I ended up downloading the Raspbian brcm80211 firmware, extracted the .deb using ar, and used scp to copy it to my 3 B+, and ran modprobe to load it.
Download the Raspbian package.
Code:
$ mkdir -p ~/Downloads/rpi3_wifi_firmware
$ cd ~/Downloads/rpi3_wifi_firmware
$ wget https://archive.raspberrypi.org/debian/pool/main/f/firmware-nonfree/firmware-brcm80211_20161130-3+rpt3_all.deb
Extract the package, and extract data.tar.xz. data.tar.xz has the firmware in it.
Code:
$ ar x firmware-brcm80211_20161130-3+rpt3_all.deb
$ tar xvf data.tar.xz
./
./lib/
./lib/firmware/
./lib/firmware/brcm/
..snip..
./lib/firmware/brcm/brcmfmac43455-sdio.bin
./lib/firmware/brcm/brcmfmac43455-sdio.clm_blob
./lib/firmware/brcm/brcmfmac43455-sdio.txt
..snip..
Copied the firmware to my Pi.
Code:
$ cd lib/firmware/brcm/
$ scp brcmfmac43455-sdio.txt pi@rpi3s:~/
$ scp brcmfmac43455-sdio.bin pi@rpi3s:~/
$ scp brcmfmac43455-sdio.clm_blob rpi3s:~/
On the Pi 3 B+ I then copied the files to where they belong and loaded the driver.
Code:
# cd /lib/firmware/brcm
# cp /home/pi/brcmfmac43455-sdio.txt .
# cp /home/pi/brcmfmac43455-sdio.bin .
# cp /home/pi/brcmfmac43455-sdio.clm_blob .
Code:
# rmmod brcmfmac
# # modprobe -vvv brcmfmac
modprobe: INFO: custom logging function 0x1905c registered
insmod /lib/modules/4.14.31-v7-arm/kernel/drivers/net/wireless/broadcom/brcm80211/brcmfmac/brcmfmac.ko
modprobe: INFO: context 0x254178 released
Now I have wifi.
Code:
# iwconfig
wlan0 IEEE 802.11 ESSID:off/any
Mode:Managed Access Point: Not-Associated
Retry short limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:on
Last edited by mralk3; 04-06-2018 at 11:28 AM.
|
|
5 members found this post helpful.
|
04-09-2019, 04:30 PM
|
#3
|
LQ 5k Club
Registered: Nov 2002
Location: Somewhere inside 9.9 million sq. km. Canada
Distribution: Slackware 15.0, current, slackware-arm-currnet
Posts: 6,299
|
WIFI on a Raspberry PI 3 model B+
Thank-you for your detailed post. I followed it and now have WIFI working on a new PI 3 b+ install.
I had started out with wlan0 not found also. FWIW, I have kernel 4.19.34 installed on current.
|
|
|
07-04-2019, 02:26 PM
|
#5
|
Member
Registered: Jun 2004
Distribution: Slackware
Posts: 241
Rep:
|
The "error -2" is a file-not-found error, it can't find brcmfmac43455-sdio.txt.
The kernel-firmware package has a brcmfmac43455-sdio.raspberrypi,3-model-b-plus.txt file. I symlinked brcm43455-sdio.txt to this and it appears to work. I don't know if there's a better or more-approved way to load this file.
Code:
[ 4.561507] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
[ 4.832063] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
[ 4.843507] brcmfmac: brcmf_c_process_clm_blob: no clm_blob available (err=-2), device may have limited channels available
[ 4.855635] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Mar 1 2015 07:29:38 version 7.45.18 (r538002) FWID 01-6a2c8ad4
The version in kernel-firmware is really old (Mar 1 2015, licensing issues preventing it from being updated) and doesn't provide the .clm_blob file, but loading it like this might work in a pinch.
More reading material near the bottom of this thread about the source of these files: https://bugs.alpinelinux.org/issues/9549
|
|
|
07-09-2019, 01:06 PM
|
#6
|
SARPi Maintainer
Registered: Nov 2012
Distribution: Slackware ARM, AArch64
Posts: 1,065
|
work-around for the missing RPi3 & 4 wireless firmware
Quote:
Originally Posted by elyk
The "error -2" is a file-not-found error, it can't find brcmfmac43455-sdio.txt.
The kernel-firmware package has a brcmfmac43455-sdio.raspberrypi,3-model-b-plus.txt file. I symlinked brcm43455-sdio.txt to this and it appears to work. I don't know if there's a better or more-approved way to load this file.
The version in kernel-firmware is really old (Mar 1 2015, licensing issues preventing it from being updated) and doesn't provide the .clm_blob file, but loading it like this might work in a pinch.
|
In order to address this issue...
SARPi now includes the new brcmfmac43430 and brcmfmac43455 wireless device firmware via the ' sarpi-hacks' packages for the Raspberry Pi 3 and 4. This package can be upgraded over any existing package but be aware it may change some of your config settings. Please see the sarpi-hacks.README (included) file before installing it: http://sarpi.fatdog.eu/files/extra/sarpi-hacks.README
The installation of the new firmware in this package relies on the old firmware being present. If you find that you're still missing the new firmware after installing the sarpi-hacks packages, run the following command and remove/install it again:
Code:
~# touch /lib/firmware/brcm/brcmfmac43430a0-sdio.bin
Until MoZes decides to include the new [RPi] Broadcom 43430 and 43455 wireless device firmware in Slackware ARM [and there's no valid reason(s) why he should], the above is how you can install it easily. This only applies to sarpi-hacks packages for the Raspberry Pi 3 and 4.
[EDIT] SARPi images and packages available from here: http://sarpi.fatdog.eu/index.php?p=downloads
Last edited by Exaga; 07-09-2019 at 03:45 PM.
Reason: forgot downloads URL
|
|
1 members found this post helpful.
|
07-26-2019, 06:04 AM
|
#7
|
Member
Registered: Feb 2017
Location: Hungary
Distribution: Slackware
Posts: 304
Rep:
|
Hi,
I have a Raspberry Pi 4 Model B Rev 1.1 board with fresh install of Slackware ARM -current.
I upgraded the kernel using raspi-update to version 4.19.60-v7l+
Currently I have no Bluetooth and WLAN interfaces after boot, even though I installed sarpi4-hacks.
Quote:
# ls -l /lib/firmware/brcm/
total 992
-rw-r--r-- 1 root root 388739 Jul 8 10:51 brcmfmac43430-sdio.bin
-rw-r--r-- 1 root root 1121 Jul 8 10:51 brcmfmac43430-sdio.txt
-rw-r--r-- 1 root root 600487 Jul 8 10:51 brcmfmac43455-sdio.bin
-rw-r--r-- 1 root root 14036 Jul 8 10:51 brcmfmac43455-sdio.clm_blob
-rw-r--r-- 1 root root 2054 Jul 8 10:51 brcmfmac43455-sdio.txt
# ls -l /var/log/packages/sarpi4-hacks-4.0-armv7l-1_slackcurrent_18Jul19_sp1
-rw-r--r-- 1 root root 1114 Jul 26 06:46 /var/log/packages/sarpi4-hacks-4.0-armv7l-1_slackcurrent_18Jul19_sp1
#
|
If I unload and reload the appropriate kernel module, I get:
Quote:
# rmmod brcmfmac
# modprobe -vvv brcmfmac
modprobe: INFO: custom logging function 0x19cd0 registered
insmod /lib/modules/4.19.60-v7l+/kernel/drivers/net/wireless/broadcom/brcm80211/brcmfmac/brcmfmac.ko
modprobe: INFO: context 0x12e12f0 released
# dmesg | tail
[ 741.077722] Bluetooth: HCI device and connection manager initialized
[ 741.078678] Bluetooth: HCI socket layer initialized
[ 741.078689] Bluetooth: L2CAP socket layer initialized
[ 741.078715] Bluetooth: SCO socket layer initialized
[ 1045.994554] usbcore: deregistering interface driver brcmfmac
[ 1053.965316] brcmfmac: F1 signature read @0x18000000=0x15264345
[ 1053.971389] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
[ 1053.972698] usbcore: registered new interface driver brcmfmac
[ 1055.072138] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 0x50
[ 1056.082187] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 0x50
# hciconfig ; echo ============= ; iwconfig
=============
eth0 no wireless extensions.
lo no wireless extensions.
#
|
What step may I have missed?
Thanks!
|
|
|
07-26-2019, 06:21 AM
|
#8
|
SARPi Maintainer
Registered: Nov 2012
Distribution: Slackware ARM, AArch64
Posts: 1,065
|
Quote:
Originally Posted by wowbaggerHU
Hi,
I have a Raspberry Pi 4 Model B Rev 1.1 board with fresh install of Slackware ARM -current.
I upgraded the kernel using raspi-update to version 4.19.60-v7l+
Currently I have no Bluetooth and WLAN interfaces after boot, even though I installed sarpi4-hacks.
If I unload and reload the appropriate kernel module, I get:
What step may I have missed?
Thanks!
|
I will look into this. It might not be soon [today] though. I'm very busy right now but as time permits I'll get back to you.
[EDIT]
I still haven't had time to look into this. My guess is; it's either going to be missing firmware or drivers that's causing the problem. Of which, you can 'borrow' from Raspbian if you're struggling to find them.
Last edited by Exaga; 07-30-2019 at 01:43 AM.
Reason: edit
|
|
1 members found this post helpful.
|
08-02-2019, 06:04 AM
|
#9
|
Member
Registered: Feb 2017
Location: Hungary
Distribution: Slackware
Posts: 304
Rep:
|
Quote:
Originally Posted by Exaga
I still haven't had time to look into this. My guess is; it's either going to be missing firmware or drivers that's causing the problem. Of which, you can 'borrow' from Raspbian if you're struggling to find them.
|
After copying over the broadcom firmware files distributed with the Raspbian image, the wlan0 interface is now up:
Code:
root@sarpi4:~# dmesg | fgrep brcmfmac
[ 3.472180] brcmfmac: F1 signature read @0x18000000=0x15264345
[ 3.481324] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
[ 3.486497] usbcore: registered new interface driver brcmfmac
[ 3.763330] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
[ 3.783832] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Feb 27 2018 03:15:32 version 7.45.154 (r684107 CY) FWID 01-4fbe0b04
root@sarpi4:~# iwconfig
wlan0 IEEE 802.11 ESSID:off/any
Mode:Managed Access Point: Not-Associated
Retry short limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:on
eth0 no wireless extensions.
lo no wireless extensions.
root@sarpi4:~#
The Bluetooth hci0 interface is still absent however both on my PI3B+ and on my PI4.
|
|
|
08-03-2019, 02:30 PM
|
#10
|
SARPi Maintainer
Registered: Nov 2012
Distribution: Slackware ARM, AArch64
Posts: 1,065
|
Quote:
Originally Posted by wowbaggerHU
After copying over the broadcom firmware files distributed with the Raspbian image, the wlan0 interface is now up:
Code:
root@sarpi4:~# dmesg | fgrep brcmfmac
[ 3.472180] brcmfmac: F1 signature read @0x18000000=0x15264345
[ 3.481324] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
[ 3.486497] usbcore: registered new interface driver brcmfmac
[ 3.763330] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
[ 3.783832] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Feb 27 2018 03:15:32 version 7.45.154 (r684107 CY) FWID 01-4fbe0b04
root@sarpi4:~# iwconfig
wlan0 IEEE 802.11 ESSID:off/any
Mode:Managed Access Point: Not-Associated
Retry short limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:on
eth0 no wireless extensions.
lo no wireless extensions.
root@sarpi4:~#
The Bluetooth hci0 interface is still absent however both on my PI3B+ and on my PI4.
|
I can't remember off the top of my head which BT drivers the RPi4 uses. However, you can just copy those over the same as you did with the wireless shizzle.
|
|
|
08-04-2019, 06:07 AM
|
#11
|
Member
Registered: Feb 2017
Location: Hungary
Distribution: Slackware
Posts: 304
Rep:
|
Quote:
Originally Posted by Exaga
I can't remember off the top of my head which BT drivers the RPi4 uses. However, you can just copy those over the same as you did with the wireless shizzle.
|
Well, I copied over all the files and folders from underneath /lib/firmware from Raspbian to Sarpi, and did a reboot on both my PI 3B+ and PI 4, but no Bluetooth on either of them.
Regarding the WLAN firmware question I stand a bit puzzled. I see no additional files being added in relation to brcmfmac43455, but the adapter seems to work with the following content of /lib/firmware/brcm (the files copied from Raspbian -- you can compare it to the file list from my previous post):
Code:
root@sarpi4:/lib/firmware/brcm# ls -l
total 15480
-rw-r--r-- 1 root root 36264 May 1 16:20 BCM43430A1.hcd
-rw-r--r-- 1 root root 56759 May 1 16:20 BCM4345C0.hcd
-rw-r--r-- 1 root root 96224 Apr 18 15:35 bcm43xx-0.fw
-rw-r--r-- 1 root root 180 Apr 18 15:35 bcm43xx_hdr-0.fw
-rw-r--r-- 1 root root 385067 Apr 18 15:35 brcmfmac43143-sdio.bin
-rw-r--r-- 1 root root 397312 Apr 18 15:35 brcmfmac43143.bin
-rw-r--r-- 1 root root 348160 Apr 18 15:35 brcmfmac43236b.bin
-rw-r--r-- 1 root root 455745 Apr 18 15:35 brcmfmac43241b0-sdio.bin
-rw-r--r-- 1 root root 403855 Apr 18 15:35 brcmfmac43241b4-sdio.bin
-rw-r--r-- 1 root root 408682 Apr 18 15:35 brcmfmac43241b5-sdio.bin
-rw-r--r-- 1 root root 479232 Apr 18 15:35 brcmfmac43242a.bin
-rw-r--r-- 1 root root 253748 Apr 18 15:35 brcmfmac4329-sdio.bin
-rw-r--r-- 1 root root 222126 Apr 18 15:35 brcmfmac4330-sdio.bin
-rw-r--r-- 1 root root 451566 Apr 18 15:35 brcmfmac4334-sdio.bin
-rw-r--r-- 1 root root 400864 Apr 18 15:35 brcmfmac43340-sdio.bin
-rw-r--r-- 1 root root 569291 Apr 18 15:35 brcmfmac4335-sdio.bin
-rw-r--r-- 1 root root 202107 Apr 18 15:35 brcmfmac43362-sdio.bin
-rw-r--r-- 1 root root 562183 Apr 18 15:35 brcmfmac4339-sdio.bin
-rw-r--r-- 1 root root 388739 Apr 18 15:35 brcmfmac43430-sdio.bin
-rw-r--r-- 1 root root 1121 Apr 18 15:35 brcmfmac43430-sdio.txt
-rw-r--r-- 1 root root 382455 Apr 18 15:35 brcmfmac43430a0-sdio.bin
-rw-r--r-- 1 root root 600487 Apr 18 15:35 brcmfmac43455-sdio.bin
-rw-r--r-- 1 root root 14036 Apr 18 15:35 brcmfmac43455-sdio.clm_blob
-rw-r--r-- 1 root root 2054 Apr 18 15:35 brcmfmac43455-sdio.txt
-rw-r--r-- 1 root root 626140 Apr 18 15:35 brcmfmac4350-pcie.bin
-rw-r--r-- 1 root root 623304 Apr 18 15:35 brcmfmac4350c2-pcie.bin
-rw-r--r-- 1 root root 605388 Apr 18 15:35 brcmfmac4354-sdio.bin
-rw-r--r-- 1 root root 648770 Apr 18 15:35 brcmfmac4356-pcie.bin
-rw-r--r-- 1 root root 526383 Apr 18 15:35 brcmfmac4356-sdio.bin
-rw-r--r-- 1 root root 557056 Apr 18 15:35 brcmfmac43569.bin
-rw-r--r-- 1 root root 550333 Apr 18 15:35 brcmfmac43570-pcie.bin
-rw-r--r-- 1 root root 633817 Apr 18 15:35 brcmfmac4358-pcie.bin
-rw-r--r-- 1 root root 595472 Apr 18 15:35 brcmfmac43602-pcie.ap.bin
-rw-r--r-- 1 root root 635449 Apr 18 15:35 brcmfmac43602-pcie.bin
-rw-r--r-- 1 root root 1105361 Apr 18 15:35 brcmfmac4366b-pcie.bin
-rw-r--r-- 1 root root 623448 Apr 18 15:35 brcmfmac4371-pcie.bin
-rw-r--r-- 1 root root 457994 Apr 18 15:35 brcmfmac4373-sdio.bin
-rw-r--r-- 1 root root 479232 Apr 18 15:35 brcmfmac4373.bin
root@sarpi4:/lib/firmware/brcm#
On top of this, I am getting the following on by PI 3B+ with the firmware from Raspbian:
Code:
root@sarpi3-build:~# dmesg | fgrep brcmfmac
[ 3.741344] brcmfmac: F1 signature read @0x18000000=0x1541a9a6
[ 3.748316] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1
[ 3.754366] usbcore: registered new interface driver brcmfmac
[ 3.993528] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1
[ 3.999137] brcmfmac: brcmf_c_process_clm_blob: no clm_blob available (err=-2), device may have limited channels available
[ 4.007321] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM43430/1 wl0: Oct 23 2017 03:55:53 version 7.45.98.38 (r674442 CY) FWID 01-e58d219f
|
|
|
08-04-2019, 10:39 AM
|
#12
|
SARPi Maintainer
Registered: Nov 2012
Distribution: Slackware ARM, AArch64
Posts: 1,065
|
Quote:
Originally Posted by wowbaggerHU
The Bluetooth hci0 interface is still absent however both on my PI3B+ and on my PI4.
|
I'm sure it's the BCM43<-something->.hcd and/or the bcm43xx*.fw files for the bluetooth.
OK. I finally had some time to look into this. After doing some quick testing, it appears that the Broadcom BCM43438/BCM43455 wireless firmware shipped with SARPi images and packages definitely isn't working. Installing the same firmware from the latest Raspbian Buster image seems to work perfectly.
The latest SARPi Slackware ARM installer images and packages [04 Aug 2019] for the Raspberry Pi 3 and 4 now includes the above firmware which has been tested and verified to be working as expected.
Grab these here: http://sarpi.fatdog.eu/index.php?p=downloads
If you find any further problems please let me know.
Thanks.
[EDIT] First time when I rebooted after updating my wireless interface didn't show up. So...
Code:
~# ifconfig wlan0 up
Now it's working as normal.
Last edited by Exaga; 08-06-2019 at 06:11 AM.
Reason: edit
|
|
1 members found this post helpful.
|
09-28-2019, 03:11 PM
|
#13
|
Member
Registered: Dec 2018
Location: Orlando, FL
Distribution: Slackware AARCH64 and X86_64
Posts: 356
Rep:
|
Raspberry Pi 3 B+ Wifi NIC not found
My wifi isn't working on the Sarpi64 latest release. I've tried everything listed. Copying from the Raspberry release. Copying brcmfmac43455-sdio.raspberrypi,3-model-b-plus.txt to brcmfmac43455-sdio.txt. Wifi still won't show.
|
|
|
11-25-2019, 10:18 AM
|
#14
|
SARPi Maintainer
Registered: Nov 2012
Distribution: Slackware ARM, AArch64
Posts: 1,065
|
Quote:
Originally Posted by kermitdafrog8
My wifi isn't working on the Sarpi64 latest release. I've tried everything listed. Copying from the Raspberry release. Copying brcmfmac43455-sdio.raspberrypi,3-model-b-plus.txt to brcmfmac43455-sdio.txt. Wifi still won't show.
|
SARPi64 is highly experimental and should only be installed on that basis and understanding; and for that porpoise. I shared this work mainly for those who have time to waste on getting things working - and in the hope that it might be facilitating towards a Slackware ARM64 port. For SARPi64, wireless is the least of my concerns and if it isn't already last on the "Todo" list - it is now.
|
|
|
All times are GMT -5. The time now is 07:15 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|