Tiny Core Base > Raspberry Pi
RasPi 3B - WiFi Not Detected
Rich:
Hi CentralWare
--- Quote from: CentralWare on January 02, 2025, 11:13:15 AM --- ... Is there a kill switch (or enable switch) for brcmfmac that you know of ? ...
--- End quote ---
util-linux has the rfkill program that might be worth checking out:
--- Code: ---tc@E310:~/Scripting/AddressParser$ rfkill --help
Usage:
rfkill [options] command [identifier ...]
Tool for enabling and disabling wireless devices.
Options:
-J, --json use JSON output format
-n, --noheadings don't print headings
-o, --output <list> define which output columns to use
-r, --raw use the raw output format
-h, --help display this help
-V, --version display version
Available output columns:
DEVICE kernel device name
ID device identifier value
TYPE device type name that can be used as identifier
TYPE-DESC device type description
SOFT status of software block
HARD status of hardware block
Commands:
help
event
list [identifier]
block identifier
unblock identifier
For more details see rfkill(8).
--- End code ---
CentralWare:
--- Quote from: Paul_123 on January 02, 2025, 03:08:53 PM ---Obviously the firmware needs to be loaded first or in the same tce-load call.
--- End quote ---
My make-shift wireless script does all four in one tce-load call.
The onboot listing was firmware, then wireless-KERNEL then tools.
--- Quote ---...if you manually added dtoverlay=disable-wifi to your config.txt
--- End quote ---
Nah, everything's fresh/default and I looked for overlays before I posted just in case something was in config to en/disable wifi/bt and to familiarize myself with the 15.x layout
SD is a fresh 15.x where mmcblk0p1 is 1GB fat32 and tce resides on it just to make my life simpler. :)
onboot owns the show; wpa_supplicant is called via bootlocal with a wait loop allowing wireless to settle and wlan0 to become available; loads wpa_supplicant.conf - otherwise dmesg > logfile
Confirmed: RasPi 3B (A+/B+ untested thus far) does in fact go "wonky" without the broadcom entry in cmdline
Power supply is 90W 3.3/5/12 USB-C (supposedly regulated - but I never benched it to prove it) but will look into psu issues just in case.
** Sadly, I vaguely recall a board conversation (which I thought was here -- but can't be sure) regarding the Pi3 and the radios and a vague inkling that something ridiculous like I2C plus IPv6 or what have you being a prerequisite (back then) of getting wifi and/or bt to play nice... but so much as changed since then it could only be hoped kernel patches/fixes went into the mix between then and now. Then again, I also remember an overlay fix that was needed to create alias/range addresses on wireless (ie: wlan0:0) and a problem with bindings where if wlan0 was used as a fail-safe it would crash the driver when eth0 went down... too many memory fragments... no defrag!!!
Back in the day there was talk about 3A/B having the means to disable wifi/bt when Pi3B was still an infant -- haven't Googled to see if that's just something in config or a bit switch in what we'll nick-name RasBIOS.
@Rich: Yes, I vaguely remember the name! :) Research notes updated for Manning and/or Googling as time permits.
Thanks guys; I appreciate the efforts!
Juanito:
I'm not sure if it's helpful, but wifi works on this RPi:
--- Code: ---cat /proc/cpuinfo | grep Model
Model: Raspberry Pi 3 Model B Rev 1.2
uname -a
Linux boxrpi3 6.6.47-piCore-v7 #20 SMP Sat Aug 31 14:54:55 EDT 2024 armv7l GNU/Linux
version
15.0
--- End code ---
..using:
--- Code: ---sudo cp /mnt/mmcblk0p2/conf/wpa_configure.conf /etc
#
tce-load -i firmware-rpi-wifi
tce-load -i wireless-KERNEL
tce-load -i wpa_supplicant
#
sleep 2
#
sudo wpa_supplicant -B -i wlan0 -c/etc/wpa_configure.conf
#
sudo udhcpc -b -i wlan0 -x hostname:boxrpi3 -p /var/run/udhcpc.wlan0.pid
--- End code ---
..and:
--- Code: ---cat wpa_configure.conf*
ctrl_interface=/var/run/wpa_supplicant
network={
ssid="blah"
key_mgmt=WPA-PSK
proto=WPA2
pairwise=CCMP
group=CCMP
psk="blah-blah"
}
--- End code ---
CentralWare:
@Juanito: Thanks for dropping in! 3 Boards identical to yours, for completely unknown reasons, two of the three act as though the wifi/bt chip isn't even soldered on.
--- Code: ---sudo cp /mnt/mmcblk0p2/conf/wpa_configure.conf /etc
--- End code ---
I do this from /opt but otherwise same process
--- Code: ---tce-load -i firmware / wireless / wpa
--- End code ---
Same here - I even added iw, usbutils, pciutils, etc. the first time around and wireless just isn't there, either by chip number or brcm driver identifier.
It's possible (though I cannot imagine how!?) the boards were damaged...
okay, maybe not (see image attachment - wifi chip bottom left corner... would be difficult to injure hiding along-side one of the DIN rail braces - while attached TO a DIN rail most of the time.)
Juanito:
Maybe the RPi OS has a test program?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version