Posts by treysis

So, I didn't have time much to investigate in too much detail, yet. A quick "dmesg | grep brcm" didn't show any differences between working and non-working boot.

I thought to try and see if the problem disappears when switching from 5 GHz WiFi to 2.4 GHz WiFi, but no difference.

However, now having both 2.4 and 5 GHz WiFi SSIDs set for auto-connect, I have a working workaround: after a "faulty" boot connecting to the previous WiFi will fail. However, now due to the second available WiFi, LE will connect to the other one and vice versa. So at least I'm left with working WiFi after each boot, no matter if faulty or not.

But WHY the connection to the previous WiFi fails, is still up for investigation when I have more time again.

Quote from VLouis

Also keep in your mind, you aren't the single person who use an RPi3 with LE and wifi connection. So using the search function on this forum could help too.

Yeah, that's how I ended up in this thread! Although I am using RPi4.

Quote from VLouis

So I pulled of the power and connected back after few seconds. The LE booted without any wifi issue...

And WiFi automatically connected to your AP after that?

Quote from VLouis

You got till now from two people the advice to install an LE13 nightly build and try it. So if you don't have a cheap, at least 8GB SDcard and a hour for this

I will! But yeah, I actually don't have a spare card lying around :/.

Quote from chewitt

ConnMan logs are somewhat human readable .. look for errors. Feel free to pastebin them somewhere (don't upload here please).

Will try looking at it! Always been a bit difficult for me figuring out where logfiles are with Kodi or LE in general. I also believe some state gets stuck for whatever weird reason.

Quote from VLouis

I'm using almost same config, RPi3B, wifi

3B or 3B+? 3B uses a different WiFi chip (Broadcom BCM43438) than RPi3B+/RPi4 (both Cypress CYW43455). So that would also point to a driver-related issue.

Oh, did I make it clear enough that WiFi also works if I shut the RPi4 down before booting? So it's not EVERY cold boot, just cold boot after sudden power loss. Doesn't mean it can't be driver releated.

Hm, maybe both. (I have to add I am not so sure anymore about the behavior in 11.) Bc after cold boot it will also ask for the wifi password when I try to connect manually. However, as I said, after reboot it works fine again. So the password is still remembered. So it seems as if the system or ConnMan think that the authentication didn't work.

I also tried the suggested script but it can't fix all issues. First, the 'systemctl restart connman' does fix the underlying problem: after running this command I can (manually) reconnect to the WiFi without having to enter the password, but it doesn't do so automatically. So manually is the issue, bc now all services complain after boot that there were obviously 'errors in name resolution'.

I also tried putting the systemctl restart connman command to the autostart.sh script, but looks like the timing there isn't right. I can have it wait so that I at least can manually connect, but it won't do the auto connect, unfortunately (yes, auto connect is set to true!).

Probably I could adjust the script to connect to the specific wifi profile, but that would lock it to my specific wifi. Well, would be good enough workaround but ideally I'd like to at least identify the underlying root cause!

Nope, definitely not the antenna, or it wouldn't be so reproducible. It's only after cold boot. Never after reboot. 100%. RPi is next to the AP.

The problem exists since at least 11. Why would a nightly solve it? There's nothing in the changelogs.

How would using a cable solve a WiFi problem? I am not complaining about connectivity issues, but about a WiFi problem.

It's more likely a problem with iwd and/or the WiFi driver.

Same problem on RasPi 4 with LubreELEC 11 and 12. Instead of manually connecting after a blackout, what also works is just rebooting from LibreELEC. So that makes it clear that autoconnect is still enabled. It's just that the hard shutdown causes some problem.