Raspi-config won’t assign any other user then Pi. I logged in as root to run it (not su’d, logged in)
LAN connected being forced to static IP of 169.254.35.57 even after running asl-menu to select DHCP and rebooting
Receive “Can’t communicate with wpa_supplicant” (from raspi-config menu) despite fact that I created a correct /etc/wpa_supplicant/wpa_supplicant.conf. Also, the binary does exist in /usr/sbin
The 169.254 IP is an auto-assigned IP when a dynamic IP can’t be retrieved. Check your cable connections, try a different ethernet cable, or try using WiFi
wpa_supplicant is a daemon that runs for WiFi. Try running systemctl enable wpa_supplicant
I know that but I’m just reporting what raspi-config was doing. I tried to change its forced user of pi to root but it would not allow it.
Cable was good and the same cable/Pi had no issues obtaining an IP assignment from my router if NOT running the beta but rather ASL 1.01 I had a different SD card
I’m aware what wpa_supplicant is. I checked for the daemon was running (ps aux | grep wpa) and it was. As it turns out, there is no wpa_supplicant.conf supplied as part of the distro image. But even after I created a valid one, raspi-config reported what it did. Seems the image build needs some tweaking…
Hi - Just checking in to see if 2.0.0-beta.6 is still the latest version, as it was released 6 months ago? Are there any plans to move this out of beta to a mainstream/stable release? Have there been no updates in 6 months?
Just curious - and wanting to keep all my things up-to-date.
I suppose this is a clue, my understanding is that the image is supposed to be Debian 10 (Buster) and after trying to update the system and seeing that fail, I checked /etc/apt/sources.list and it is pointing to rasbian.raspberrypi.org.
Now I see everything in /etc/os-release references Raspbian, but I don’t think the Raspberry Pi organization supports Raspbian any more in favor of Raspberry Pi OS.