Raspberry Pi 4 - Won't Connect to WiFi after Configuration

[AlphaXrayPapa]

Update: the primary issue seems to be that I'm not seeing the list of my open SSID's in the interface.
There might be other issues at play as well related to not being able to mount the SSD, but let's start there.

I just got Meteobridge installed on my RPi4 and I cannot get the system to join my WiFi network.
1) I'm using the specified "Industrial" SD Card from the Meteobridge Wiki (wiki).
2) I flashed the image from the the wiki to the card using BalenaEtcher.
3) I connected it to the network via ethernet and configured via the UI, including the WiFi setting.
4) I disconnected the ethernet cable, restarted the RPi and I see this on the screen instead...

RPi_screenoutput.png (192.83 KiB) Viewed 14012 times

Those last three lines didn't come up on the initial boot and there's more that should take place after that before the software is fully functional so as of now, this system is non-functional. To make that easier to read, they are.

Code: Select all

EXT4-fs (mmcblk0p3): Mount option "data=ordered" incompatible with ext2
EXT4-fs (mmcblk0p3): recovery complete
EXT4-fs (mmcblk0p3): mounted filesystem with ordered data mode. Opts: commit=60,data=ordered,max_batch_time=1000000,min_batch_time=1000000,errors=remount-ro

I'm not sure this is the problem, only that this is where the messages stop. Has anyone encountered this and can they help me figure out how to correct it?

I can access the command line by hitting enter at this point, so there's some functionality.

[AlphaXrayPapa]

I hadn't been watching what the screen was doing as the unit is another room, but when I came the following messages are repeated on screen. A possible clue perhaps?

Code: Select all

/dev/sda1: Can't open blockdev
/dev/sda: Can't open blockdev

RPi_screenoutput-02.png (144.43 KiB) Viewed 14008 times

[AlphaXrayPapa]

Some more clues.

1) I noted on setup that I'm not seeing a list of available of Wireless SSID's. At first I kind of ignored this, but now I think it's a hint at something being wrong.

2) Possibly related to the above, I'm not using the default IP ranges for my local network here. So this device isn't going to be starting out at 192.168.1.0. That said, if that's a problem, should there not be some way to update this to the range you are using?

In this thread: viewtopic.php?t=17250. A user requested support on having a vary similar issue. I've added my comments there as well.

[AlphaXrayPapa]

I happened to have an older RPi 4 on hand, it's a v1.2 board. The problem with the v1.4 firmware is the same and the v1.3 won't boot at all.