Hey,
I updated Volumio to Version 3 and and could connect it to my wireless network (I’m using an AC dongle). I connected via network cable but I can’t activate the network adapter - it throws the error "Error: Command failed: sudo/bin/systemctl restart wireless.service Job for wireless.service failed. See ‘systemctl status wireless.service’ and ‘journalctl -xn’ for details.
When I ssh into volumio I get following results.
systemctl status wireless.service:
wireless.service - Wireless Services
Loaded: loaded (/lib/systemd/system/wireless.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sun 2022-01-30 15:25:28 UTC; 23s ago
Process: 2222 ExecStart=/volumio/app/plugins/system_controller/network/wireless.js start (code=exited, status=0/SUCCESS)
Process: 2264 ExecStartPost=/sbin/iw dev wlan0 set power_save off (code=exited, status=237/KEYRING)
Jan 30 15:25:27 volumio sudo[2232]: pam_unix(sudo:session): session opened for user root by (uid=0)
Jan 30 15:25:27 volumio sudo[2232]: pam_unix(sudo:session): session closed for user root
Jan 30 15:25:27 volumio wireless.js[2222]: Stopped aP
Jan 30 15:25:27 volumio sudo[2243]: root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/ip addr flush dev wlan0
Jan 30 15:25:27 volumio sudo[2243]: pam_unix(sudo:session): session opened for user root by (uid=0)
Jan 30 15:25:27 volumio sudo[2243]: pam_unix(sudo:session): session closed for user root
Jan 30 15:25:28 volumio iw[2264]: command failed: No such device (-19)
Jan 30 15:25:28 volumio systemd[1]: wireless.service: Control process exited, code=exited, status=237/KEYRING
Jan 30 15:25:28 volumio systemd[1]: wireless.service: Failed with result 'exit-code'.
Jan 30 15:25:28 volumio systemd[1]: Failed to start Wireless Services.
and journalctl -xn:
-- Logs begin at Thu 2019-02-14 10:12:00 UTC, end at Sun 2022-01-30 15:53:19 UTC. --
Jan 30 15:53:19 volumio-boxen hostapd[2133]: nl80211: deinit ifname=wlan0 disabled_11b_rates=0
Jan 30 15:53:19 volumio-boxen hostapd[2133]: Could not read interface wlan0 flags: No such device
Jan 30 15:53:19 volumio-boxen hostapd[2133]: nl80211 driver initialization failed.
Jan 30 15:53:19 volumio-boxen hostapd[2133]: wlan0: interface state UNINITIALIZED->DISABLED
Jan 30 15:53:19 volumio-boxen hostapd[2133]: wlan0: AP-DISABLED
Jan 30 15:53:19 volumio-boxen hostapd[2133]: wlan0: CTRL-EVENT-TERMINATING
Jan 30 15:53:19 volumio-boxen hostapd[2133]: hostapd_free_hapd_data: Interface wlan0 wasn't started
Jan 30 15:53:19 volumio-boxen systemd[1]: hostapd.service: Control process exited, code=exited, status=1/FAILURE
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit hostapd.service has exited.
I’m I seeing that right that he can’t detect the wireless dongle anymore after the update?
I’ve also tried several factory resets with no results.
Same here. After Upgrading from Volumio 3.1xx to 3.251 wireless does not work anymore (same error as above). This happens right after clicking the “save” button. With the old Version, wifi was working flawlessly.
Edit: After downgrading to Volumio 3.179, wireless is working again. Seems to be a bug in the current release.
Same issue here. RPi 2 with Wifi dongle was working with Volumio 3.1x out of the box.
When I could not update to 3.251 via OTA update, I downloaded the latest image and flashed it on SD.
After booting up, the Hotspot was not coming up, so I found a network cable to connect via that.
It looks, like the WiFi-dongle is not found anymore. Tried already with another SD card and with another WiFi dongle of the same type. Always the same issue.
Attached a full boot log. boot.txt (168.1 KB)
Here’s the section of the log that keeps repeating in a loop forever (I have cut the remaining lines from the log, after the Volumio start has finished):
hostapd.service: Service RestartSec=2s expired, scheduling restart.
hostapd.service: Scheduled restart job, restart counter is at 85.
Stopped Advanced IEEE 802.11 AP and IEEE 802.1X/WPA/WPA2/EAP Authenticator.
Starting Advanced IEEE 802.11 AP and IEEE 802.1X/WPA/WPA2/EAP Authenticator...
Configuration file: /etc/hostapd/hostapd.conf
Could not read interface wlan0 flags: No such device
nl80211: Driver does not support authentication/association or connect commands
nl80211: deinit ifname=wlan0 disabled_11b_rates=0
Could not read interface wlan0 flags: No such device
nl80211 driver initialization failed.
wlan0: interface state UNINITIALIZED->DISABLED
wlan0: AP-DISABLED
wlan0: CTRL-EVENT-TERMINATING
hostapd_free_hapd_data: Interface wlan0 wasn't started
hostapd.service: Control process exited, code=exited, status=1/FAILURE
hostapd.service: Failed with result 'exit-code'.
Failed to start Advanced IEEE 802.11 AP and IEEE 802.1X/WPA/WPA2/EAP Authenticator.
OK, this does not seem to be the issue here - at least not matching with the changelog info.
I tried to downgrade version by version to see, when it starts working again.
I tried 3.251, 3.224, 3.198 without success.
It only worked again, when I went back as far as 3.179 (2021-12-20).
The dongle I use is an TP-Link Archer.
I get the following response from lsusb:
Bus 001 Device 013: ID 2357:011e TP-Link
I found this page offering drivers for said adapter, but the current Kernel is not supported yet. Did not have time to look into how to compile a driver.
The install script gave some additional info:
*** Raspberry Pi wifi driver installer by MrEngman.
*** Performing self-update
*** Relaunching after update
*** Raspberry Pi wifi driver installer by MrEngman.
Your current kernel revision = 5.10.90-v7+
Your current kernel build = #1512
Checking for a wifi module to determine the driver to install.
Your wifi module is Bus 001 Device 004: ID 2357:011e TP-Link
And it uses the 8812au driver.
Your Pi revision number is a01041
You have a Pi 2B v1.1
Checking for a 8812au wifi driver module for your current kernel.
A driver does not exist for this update.