On 02/02/2025 21:01, Rainer Dorsch wrote:
root@outdoor:~# cat /etc/network/interfaces
[...]
auto wlan0
Is there a chance that "allow-hotplug wlan0" might help? I use
NetworkManager for WiFi interfaces, so my remarks may have no sense.
Simply ignore them that case. My expectation is that hotplug might wait
till completion of device initialization.
root@outdoor:~# ip a
[...]
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP
group default qlen 1000
link/ether b8:5a:f7:82:aa:c2 brd ff:ff:ff:ff:ff:ff
Are there anything related to wpasupplicant or dhclient in the logs
(sudo journalctl -b)? There should be a way to make the tools more
verbose. I can not suggest specific commands, but perhaps "iw" and
"wpa_cli" may provide some info related to device state at this moment.
root@outdoor:~# ifdown wlan0
Killed old client process
Internet Systems Consortium DHCP Client 4.4.3-P1
So dhclient was running. Have you tried to wait for ~10 minutes? My
experience is that if ethernet cable is unplugged during boot then it
may take several minutes to get IP address after the cable is connected
(the reason to prefer NetworkManager on laptops). It is again the
hypothesis that dhclient is started too early before the link is ready.
[ 19.474457] brcmfmac mmc0:0001:1: firmware: failed to load brcm/
brcmfmac4330-sdio.solidrun,cubox-i-q.bin (-2)
[...]
[ 23.420532] ieee80211 phy0: brcmf_p2p_create_p2pdev: timeout occurred
[ 23.427094] ieee80211 phy0: brcmf_cfg80211_add_iface: add iface p2p-dev-
wlan0 type 10 failed: err=-5
Are firmware files necessary for p2p device only? If
firmware-b43-installer and firmware-b43legacy-installer packages can not
help, can firmware be obtained e.g. from vendor images for this board?
