Do not use Raspberry Pi Imager 1.9.4 to build an AllStarLink ASL3 Pi Appliance. There is a bug in the imager software with version 1.9.4 that breaks the WiFi network setup. Please use version 1.8.5 until there is a replacement for 1.9.4 that fixes the issue.
I have had a few bumpy rides when using the Pi-Imager over the last few years. The one I recall was when the admin password was set but then you couldn't login when the SD card was transferred to the Pi. Lots of fixes appeared talking about problems with the password hash.... use a generic hash and edit file x, y & z. It didn't work. I reverted to a very old version of the RPi imaging software where you couldn't even pick a username. You where stuck with the 'Life of pi' (aka pi) but it worked.
Thank you for the update. Looking at the imager download directory it's interesting they jump from v1.8.5 to v1.9.4. Last fall I had upgraded to v1.9.0. Can't be a coincidence that I posted about an issue with the Wi-Fi Manager after imaging with v1.9.0 back in December of last year. Wonder if the "bug" has been there for all of the v1.9.x versions. Double checked my current install and I had rolled back to v1.8.5.
interesting.
I have bult 3 nodes this last week using 1.8.5 and 3 of them would not work on wifi. my work around was to clone the sd card of the one I got working 3 weeks ago and change all the node numbers etc. I never could get the wifi to work on those otherwise.
Do we know if this is now stable? Reason being, I'm experiencing 2 different node issues with connection issues; Failed to start asl3-update-nodelist.service - Update ASL3 on-disk nodelist db. - I'm starting to think maybe it is Pi-Imager V1.9.6.
How are you currently accessing the server/node (Wi-Fi, Ethernet, monitor/keyboard/mouse)?
Most issues with asl3-update-nodelist are network related. How's the network connectivity from the server/node? Is there anything interesting reported by systemctl status asl3-update-nodelist.service?
Sorry - Late reply been busy with work and no time to play radio .. Yes that might be the cause. It was an update on top of.. I will give that a try - But I am getting two log errors - bgscan simple: failed to enable signal strength monitoring - second; nl80211 kernel reports registration to specific type not supported - Obviously these are causing me connection issues on a SHARI-PI Hat (Pi4) that I intend on using for a mobile setup.
Sorry - Late reply been busy with work and no time to play radio
As I said to Mike (in my reply to him) I'm getting two log errors - bgscan simple: failed to enable signal strength monitoring - second; nl80211 kernel reports registration to specific type not supported - Obviously these are causing me connection issues on a SHARI-PI Hat (Pi4) Wi-Fi that I intend on using for a mobile setup.
No they are not. They are not "Errors" in the sense of causing a problem. "bgscan" is an warning that the driver for the WiFi interface you're using doesn't support a particular type of signal strength scanning. The nl80211 message is the same type of thing. They're not the cause of any WiFi issues unless they're additional symptoms of failed/broken hardware.
.. Yes that might be the cause. It was an update on top of.. I will give that a try - But I am getting two log errors - bgscan simple: failed to enable signal strength monitoring - second; nl80211 kernel reports registration to specific type not supported - Obviously these are causing me connection issues on a SHARI-PI Hat (Pi4) that I intend on using for a mobile setup.