Tiny Core Base > Raspberry Pi
RasPi 3B - WiFi Not Detected
Rich:
Hi CentralWare
--- Quote from: CentralWare on January 01, 2025, 06:35:08 PM --- ... Since the Pi3B is supposed to have wireless onboard, I picked a few of those to run a wireless project on and immediately ran into a wall.
cpuinfo Model: Raspberry Pi 3 Model B Rev 1.2
version 15.x ArmHF
uname: 6.6.47-piCore-v7 ...
--- End quote ---
I'm not up on pi history, but that sounds like a model that's been around for a while.
Try with and older known version (TC14, TC13, etc) and see if you get the same result.
If you do, it's likely a hardware problem (broken board?).
If you don't, it's likely a software issue.
Paul_123:
A bit more info.
Board info
--- Code: ---tc@box:~$ cat /proc/device-tree/model
Raspberry Pi 3 Model B Rev 1.2tc@box:~$
tc@box:~$ cat /proc/cpuinfo | grep Revision
Revision : a22082
tc@box:~$
--- End code ---
With no wifi extensions mounted, you should see the following in dmesg. This is the communication bus to the wifi chip.
--- Code: ---tc@box:~$ dmesg | grep mmc1
[ 2.250432] mmc1: new high speed SDIO card at address 0001
--- End code ---
Loading driver
--- Code: ---tc@box:~$ tce-load -i firmware-rpi-wifi
firmware-rpi-wifi.tcz: OK
tc@box:~$ tce-load -i wireless-KERNEL.tcz
regdb.tcz: OK
wireless-6.6.47-piCore-v7.tcz: OK
tc@box:~$ dmesg
.......
[ 327.411774] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[ 327.422081] Loaded X.509 cert 'benh@debian.org: 577e021cb980e0e820821ba7b54b4961b8b4fadf'
[ 327.431600] Loaded X.509 cert 'romain.perier@gmail.com: 3abbc6ec146e09d1b6016ab9d6cf71dd233f0328'
[ 327.433041] Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[ 327.434437] Loaded X.509 cert 'wens: 61c038651aabdcf94bd0ac7ff06c7248db18c600'
[ 327.477827] brcmfmac: F1 signature read @0x18000000=0x1541a9a6
[ 327.485979] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1
[ 327.486752] usbcore: registered new interface driver brcmfmac
[ 327.724607] brcmfmac: brcmf_c_process_txcap_blob: no txcap_blob available (err=-2)
[ 327.725217] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM43430/1 wl0: Jul 19 2021 03:24:18 version 7.45.98 (TOB) (56df937 CY) FWID 01-8e14b897
--- End code ---
CentralWare:
--- Quote from: Juanito on January 04, 2025, 04:26:17 AM ---Maybe the RPi OS has a test program?
--- End quote ---
My thoughts exactly... Raspbian images are currently in the download queue but the download site is painfully slow from here, so it'll be a bit before I can create cards.
--- Quote from: Rich on January 04, 2025, 11:39:31 AM ---If you do, it's likely a hardware problem (broken board?).
If you don't, it's likely a software issue.
--- End quote ---
I have my home NAS dumping TCL onto a pair of piCore SD cards (2.x to 16.x) at the moment (partition 1 being 2GB Fat32 w/ piCore, partition 2 being the balance of 400GB) which was the point of the RasPi-3B units in the first place (to host the TCL repo on a pair of RasPi boards; one for the existing layout, the other for development on the new whilst working from home.) I'll be taking the two faulty 3B boards back to the office Monday and have someone bench 'em and see exactly what you and @Juanito suggested. I got these boards when 3B was just released (bought about a dozen in the first batch) so anything is possible - they sat in inventory for a bit as Raspbian and Pi Foundation released the hardware before it was ready to be released (firmware/software) but we'll see!
--- Quote from: Paul_123 on January 04, 2025, 01:09:54 PM ---A bit more info.
--- End quote ---
Thank you for the data; I'll run it against the pair of "duds" Monday. In fact, I'm going to have all of our Pi3 boards pulled from the rack and benched; wireless/btooth tested to see if there's a common problem with the boards we bought (not that there'd be a warranty left in them!! :) ) Mind you, we don't normally use Pi3 boards for wireless projects thus why this has gone unnoticed for so long.
So far, using the working 3B model I was able to create a pair of SD cards (plus kernel drivers for v6) which operated properly on the 3B so they could be transferred over to Pi-0W boards if needed.
On the first Pi-0W everything looks to have worked successfully, even with the brcmfmac feature disabled. Speaking of which, this should verify the RasPi-3 models needing that kernel flag (it's listed for the 3A+ and my 3B needed it as well.)
Take care, my friends!
Paul_123:
It’s only if you are using wpa_supplicant 2.11. It should not affect drivers loading or being detected.
I know zero2W needs it.
CentralWare:
LOL - since we're knee deep in 15.x, how about an extension request of mdadm.tcz for piCore??
--- Quote ---I know zero2W needs it.
--- End quote ---
I'd need to read up on the problem more thoroughly but if I were to speculate, it sounds like a WPA2/3 packet problem where if we're telling the kernel to disable a feature specific to Broadcom's radios, MY guess would be this should be an issue for ANY model of RasPi with the same/similar onboard or USB based Broadcom chip. Whether it's isolated just to WPA# Personal I can't say yet.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version