Hi, when you use Berrylan, are you not presented with 'BT WLAN'? This is the RPi that needs to be selected to setup the WiFi. Double check this and if its not showing up, then you will have to force the script to quit so you can get into raspi-config. I believe this is done by pressing 'ctrl+alt+f1' (or f2). Then you should be able to make changes to Raspi-Config. Try that and let us know what happens. - Mark 

@markyharris Thanks for getting back. Yes I forgot to mention that Berrylan wasn't showing anything for the Pi. I turned off the filtering in the app and could see all of my other nearby bluetooth devices but the BT WLAN wasn't one of them. With the ctrl+alt+f2 command I was able to stop the script and go into raspi-config and put in the SSID and passphrase, but it appears that I'm just unable to connect the board to wifi successfully. When I ethernet in the livesectional script runs just fine. Thanks for the help.

Glad you got it working. However, there isn't a reason the wifi feature shouldn't work. Might try rebooting after setting the SSID? I'm just thinking out loud here. - Mark

@markyharris unfortunately no change when I reboot. I've spent a few hours trying various things, including flashing the SD with the normal Raspberry Pi OS to see if the issue persists there. Interestingly, the WiFi setup works just fine when I do it through the GUI on the desktop. For some reason that isn't translating to raspi-config in the livesectional image. So ethernet and WiFi both work on Raspberry OS, and ethernet works on the livesectional image but unable to get WiFi connection nor does BT WLAN show up in Berrylan. Just trying to rule out hardware failures.

Maybe I'm barking up the wrong tree, but many online suggestions have been centered around making changes to the wpa_supplicant.conf file, which I have done several times and running various tests it doesn't look like the file is even seen. The path I am using is:

sudo nano /etc/wpa_supplicant/wpa_supplicant.conf

And the changes I make to it are:

ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
country=US
update_config=1

network={
 ssid="(my wifi name)"
 psk="(my password)"
}

Is the wpa_supplicant.conf file somewhere different in the livesectional image than it would be in the normal Raspberry OS (i.e. am I writing to the wrong place or a place that doesn't exist in the livesectional image)? Forgive me if I'm talking apples and oranges here. I'm no electronics newbie but I am very unfamiliar with the Pi and file structure. Maybe you'll see some red flags here that I don't. Or maybe I'll just include a very long ethernet cable in the box when I give this gift 🙂

Will

If I remember correctly, wpa_supplicant.conf is only read and used on the very first boot of an image. In other words you need to burn an image, then from your windows computer, alter the wpa_supplicant.conf with your ssid and password, then insert it into the RPi for its first boot. Then it uses the credentials.

Another thought; the 4B is the latest version of the hardware and the software may not be updated properly. So try this and see what happens;

type

sudo apt-get update

followed by

sudo apt-get upgrade

and then reboot

Hopefully this will update the needed packages so that it runs properly on the 4b. Let us know. - Mark

@markyharris gave it a couple of tries with fresh flashes but no luck I'm afraid. I've got a Pi 3A+ headed my way so I will give that a go and report back in case anyone else ever has the same issue. Thanks for the help.

Will

Just a follow up post - replaced the 4b with a 3A+ and everything worked fine. Not sure what was up with the 4 but all is well now!

Thanks for the update. I know we had the same issue with the 4a when it came out, but the update discussed took care of the issue. I'll have to purchase a 4b and set a board up to see what needs to be updated. So more to come at some point. - Mark

Unfortunately same exact problem here with a 4b.

Kris in MN