Arch Linux ARM was installed successfully on a Raspberry Pi3 which will be added to a small network. The first attempt at setting up wifi on the Pi3 failed, showing alarm wpa_supplicant[323]: wlan0: Could not read SSID from driver
.
The Pi3 is the only device that failed to connect. An Arch Linux laptop, and an Ubuntu laptop, both connected successfully using the same configuration.
Summary of steps
A very simple /etc/wpa_supplicant/wpa_supplicant-wlan0.conf
was created:
# wpa_passphrase MYSSID mypassphrase > /etc/wpa_supplicant/wpa_supplicant-wlan0.conf
This produced:
ap_scan=0
network={
ssid="MYSSID"
#psk="mypassphrase"
psk=long-alpha-numeric-key
}
Enable the service:
# systemctl enable wpa_supplicant@wlan0
A very basic systemd-networkd
unit was created:
nano /etc/systemd/network/mypi3-wireless.network
This produced:
[Match]
Name=wlan0
[Network]
DHCP=yes
# reboot
(the systemd-networkd service is pre-enabled on ArchLinux ARM)
After rebooting and discovering no wifi connection:
# systemctl status wpa_supplicant@wlan0
Shows:
alarm systemd[1]: Started WPA aemon (interface-specific version)
alarm wpa_supplicant[3l32]: Successfully initialized wpa_supplicant
alarm wpa_supplicant[332]: wlan0: Could not read SSID from driver
This device attempts to connect to a Linksys ACM3200WRT router with OpenWRT. It is tempting to assume that this is an OpenWRT issue, however, the pi3 is the only device in the network that won't connect.
What am I missing? Thanks in advance.
country=XX
inwpa_supplicant.conf
) - if it's not a pi3B+ I apologise for the comment noise :p – Jaromanda X Aug 8 '18 at 4:52/etc/wpa_supplicant/wpa_supplicant-wlan0.conf
(obviously you can remove the ssid and password) - you've shown how you created itwpa_passphrase MYSSID mypassphrase >
but does that do the whole job? – Jaromanda X Aug 8 '18 at 5:05