New Pi4b on 2.535 Unable to enable wifi

Just setup a brand new Pi4 with latest RoPieee build. Seems to work fine with Ethernet, but every time I try to toggle “enable wifi” the UI freezes with the “Start interface and scan for networks…” message. Needs a hard power reset to reconnect via Ethernet.

Filed feedback: b5fbd3fdb26daf92

When the UI is frozen I can still connect via SSH, if that helps troubleshoot further?

Hi,

How long are you waiting? The configuration and scanning of the interface can take up to 10 seconds.

Thanks

I’ve left it for 10+mins.

FWIW I’ve tried re-flashing the image and been through countless reboots.

Thanks for getting back to me so soon!

Hmmm. ok. The logs don’t show much because of the reboot.

Can you try again? And after 15 seconds or so just change the url back to the root of the webpage?
And then send me the feedback?

Thanks

As soon as I “Enable” wifi the web server is unresponsive. I can’t refresh the page, or navigate directly to the root. Requires a reboot before the UI server comes back online.

Ok.

Can you then do the same, but after 10 seconds or so log in via SSH and do the following:

/opt/RoPieee/sbin/send-feedback

Thanks

Done. Although it didn’t generate an ID.

Ok. I’ve got no clue what’s going on, so that requires some more debugging if you’re up to it.
Can you login and run the following:

/opt/RoPieee/lib/enable_wifi
iwconfig

Thanks

Here’s the output:

[root@ropieee ~]# /opt/RoPieee/lib/enable_wifi
trying WiFi driver 8723bu...
trying WiFi driver 88x2bu...
trying WiFi driver 8192eu...
trying WiFi driver rt2800usb...
trying WiFi driver 8812au...
trying WiFi driver rtl8xxxu...
trying WiFi driver brcmfmac...
[root@ropieee ~]# iwconfig
eth0      no wireless extensions.

wlan0     IEEE 802.11  ESSID:off/any  
          Mode:Managed  Access Point: Not-Associated   Tx-Power=31 dBm   
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          
lo        no wireless extensions.

Thanks.

Ok Thanks.

At least that’s ok.
What if you go back to the webinterface now?

Interface still functions, but wifi is listed as disabled.

I tried enabling wifi from the UI and faced the same hang. Then tried to enable via SSH immidiately after the hang, and the console hung here:

[root@ropieee ~]# /opt/RoPieee/lib/enable_wifi
trying WiFi driver 8723bu...
trying WiFi driver 88x2bu...

And it is not coming back? 100% sure?

You can basically test it a few times by runnning:

/opt/RoPieee/lib/enable_wifi

followed by a

/opt/RoPieee/lib/disable_wifi

Tried again after a reboot, doesn’t seem to hang in the same spot.

[root@ropieee ~]# /opt/RoPieee/lib/enable_wifi
trying WiFi driver 8723bu...
trying WiFi driver 88x2bu...
trying WiFi driver 8192eu...
trying WiFi driver rt2800usb...
trying WiFi driver 8812au...
trying WiFi driver rtl8xxxu...
trying WiFi driver brcmfmac...

Gotta give up for now. This was a fresh out the box Pi and SD card, will try with a different pi distribution tomorrow to rule out a hardware issue.

Ok Thanks for now.

This is certainly not an hardware error, I’m pretty sure this is software related.

If it helps you or anyone else; this is happening on a Raspberry Pi 4 Model B Rev 1.1

As another data point, I have the same Pi4 Model, and I just tested the wireless — no problems at all, so there is something specific going on.

Hi, same problem here on my RPI3B+
Fresh install, turned Wifi onboard on, no Wifi, see picturesScreenshot 2020-06-28 at 17.55.24 Screenshot 2020-06-28 at 17.54.34
info send: 48531228a5bf334e Info Field Wifi stays empty.

Cheers John.

Just installed DietPi on this same device and SD card and WIFI is confirmed to be functioning, scanning, and connecting to the network.

Your installation failed. You need to reinstall.

Thanks