RPi WiFi issues. Power_save ?

This is for ARMv8 based devices

RPi WiFi issues. Power_save ?

Postby MochaBrowser » Thu Mar 02, 2023 4:26 pm

Hi,

Just set up a headless Rpi 4 with WiFi only. Or tried at least.

The Pi boots, I see it appearing from the router and successfully getting an IP.

But I cannot connect via ssh :

$this->bbcode_second_pass_code('', '$ ssh alarm@192.168.1.72
ssh: connect to host 192.168.1.72 port 22: No route to host
')
and the Pi disconnects after a minute or so and disappears from the router's list of connected devices.

On the debian I used to do :

$this->bbcode_second_pass_code('', '
$ sudoedit /etc/rc.local
------------------------
[...]
iw dev wlan0 set power_save off
')
Is that still a problem with Arch linux as well ? I've just never been able to get this Pi to work reliably with WiFi...

Thanks very much !
MochaBrowser
 
Posts: 7
Joined: Wed Mar 01, 2023 10:35 pm

Re: RPi WiFi issues. Power_save ?

Postby MochaBrowser » Thu Mar 02, 2023 5:05 pm

I've managed to plug in a screen. When I reboot, wifi works for a few seconds, then I get
$this->bbcode_second_pass_code('', '
ieee80211 phy0: brcmf_p2p_send_action_frame: Unknown Frame: category 0xa, action 0x8
')
and network becomes unreachable. The screen is flooded with
$this->bbcode_second_pass_code('', '
brcmfmac: cfg80211_set_channel: set chanspec 0x**** fail, reason -52
')
relevant logs :
$this->bbcode_second_pass_code('', '
Mar 02 17:01:45 pisces systemd[370]: Reached target Sockets.
Mar 02 17:01:45 pisces systemd[370]: Reached target Basic System.
Mar 02 17:01:45 pisces systemd[370]: Reached target Main User Target.
Mar 02 17:01:45 pisces systemd[370]: Startup finished in 336ms.
Mar 02 17:01:45 pisces systemd[1]: Started User Manager for UID 0.
Mar 02 17:01:45 pisces systemd[1]: Started Session 1 of User root.
Mar 02 17:01:45 pisces login[363]: ROOT LOGIN ON tty1
Mar 02 17:01:50 pisces wpa_supplicant[360]: wlan0: Trying to associate with SSID 'Wifi'
Mar 02 17:01:50 pisces wpa_supplicant[360]: wlan0: Associated with 30:24:78:33:3d:b0
Mar 02 17:01:50 pisces wpa_supplicant[360]: wlan0: CTRL-EVENT-CONNECTED - Connection to 30:24:78:33:3d:b0 completed [id=0 id_str=]
Mar 02 17:01:50 pisces kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Mar 02 17:01:50 pisces systemd-networkd[291]: wlan0: Connected WiFi access point: Wifi (30:24:78:33:3d:b0)
Mar 02 17:01:50 pisces systemd-networkd[291]: wlan0: Gained carrier
Mar 02 17:01:50 pisces wpa_supplicant[360]: wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Mar 02 17:01:50 pisces systemd-networkd[291]: wlan0: DHCPv4 address 192.168.1.72/24, gateway 192.168.1.254 acquired from 192.168.1.254
Mar 02 17:01:50 pisces dbus-daemon[357]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.3' (uid=980 pid=291 comm="/usr/lib/systemd/systemd-networkd")
Mar 02 17:01:50 pisces systemd-timesyncd[323]: Network configuration changed, trying to establish connection.
Mar 02 17:01:51 pisces systemd[1]: Starting Hostname Service...
Mar 02 17:02:11 pisces systemd-resolved[321]: Clock change detected. Flushing caches.
Mar 02 17:02:11 pisces systemd-timesyncd[323]: Contacted time server 135.125.165.135:123 (0.arch.pool.ntp.org).
Mar 02 17:02:11 pisces systemd-timesyncd[323]: Initial clock synchronization to Thu 2023-03-02 17:02:11.662851 UTC.
Mar 02 17:02:11 pisces dbus-daemon[357]: [system] Successfully activated service 'org.freedesktop.hostname1'
Mar 02 17:02:11 pisces systemd[1]: Started Hostname Service.
Mar 02 17:02:11 pisces systemd-networkd[291]: Could not set hostname: Access denied
Mar 02 17:02:13 pisces systemd-networkd[291]: wlan0: Gained IPv6LL
Mar 02 17:02:13 pisces systemd-timesyncd[323]: Network configuration changed, trying to establish connection.
Mar 02 17:02:13 pisces systemd-timesyncd[323]: Contacted time server 135.125.165.135:123 (0.arch.pool.ntp.org).
Mar 02 17:02:20 pisces wpa_supplicant[360]: wlan0: WNM: Disassociation Imminent - Disassociation Timer 60
Mar 02 17:02:20 pisces wpa_supplicant[360]: wlan0: WNM: Preferred List Available
Mar 02 17:02:20 pisces wpa_supplicant[360]: wlan0: Trying to associate with SSID 'Wifi'
Mar 02 17:02:20 pisces systemd-networkd[291]: wlan0: Lost carrier
Mar 02 17:02:20 pisces kernel: ieee80211 phy0: brcmf_p2p_send_action_frame: Unknown Frame: category 0xa, action 0x8
Mar 02 17:02:20 pisces systemd-networkd[291]: wlan0: DHCP lease lost
Mar 02 17:02:21 pisces systemd-networkd[291]: wlan0: DHCPv6 lease lost
Mar 02 17:02:21 pisces systemd-timesyncd[323]: No network connectivity, watching for changes.
Mar 02 17:02:21 pisces systemd-networkd[291]: Could not set hostname: Access denied
Mar 02 17:02:31 pisces wpa_supplicant[360]: wlan0: Authentication with 30:24:78:33:3d:b4 timed out.
Mar 02 17:02:31 pisces wpa_supplicant[360]: BSSID 30:24:78:33:3d:b4 ignore list count incremented to 2, ignoring for 10 seconds
Mar 02 17:02:31 pisces wpa_supplicant[360]: wlan0: CTRL-EVENT-DISCONNECTED bssid=30:24:78:33:3d:b0 reason=3 locally_generated=1
Mar 02 17:02:31 pisces wpa_supplicant[360]: wlan0: CTRL-EVENT-DSCP-POLICY clear_all
Mar 02 17:02:31 pisces wpa_supplicant[360]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Mar 02 17:02:31 pisces wpa_supplicant[360]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY alpha2=FR
Mar 02 17:02:34 pisces kernel: brcmfmac: cfg80211_set_channel: set chanspec 0xd022 fail, reason -52
Mar 02 17:02:34 pisces kernel: brcmfmac: cfg80211_set_channel: set chanspec 0xd026 fail, reason -52
Mar 02 17:02:34 pisces kernel: brcmfmac: cfg80211_set_channel: set chanspec 0xd02a fail, reason -52
Mar 02 17:02:34 pisces kernel: brcmfmac: cfg80211_set_channel: set chanspec 0xd02e fail, reason -52
Mar 02 17:02:36 pisces kernel: brcmfmac: cfg80211_set_channel: set chanspec 0xd090 fail, reason -52')
MochaBrowser
 
Posts: 7
Joined: Wed Mar 01, 2023 10:35 pm


Return to ARMv8 Devices

Who is online

Users browsing this forum: No registered users and 26 guests