+- PINE64 (https://forum.pine64.org)
+-- Forum: PinePhone (https://forum.pine64.org/forumdisplay.php?fid=120)
+--- Forum: General Discussion on PinePhone (https://forum.pine64.org/forumdisplay.php?fid=127)
+--- Thread: no connect to wifi on first startup (/showthread.php?tid=13078)
no connect to wifi on first startup - derbaertigefrytz - 02-11-2021
I have tested several distributions (manjaro/phosh, ~/lorimi, mobian/phosh, ubuntu/lorimi) and observed similar problems with all of them.
With phosh, I can not connect to wifi, while in the setup wizard.
It either loops asking for the password, or refuses instantly to connect to my SSID.
My first run was very frustrating. No wifi!
I found out, that I can connect to wifi in phosh, when I try again, after the setup wizard completed.
I can select a properties button beside my SSID and select the security settings.
Though my SSID is detected as WPA encrypted, I have to select "WPA2 personal" from the encryption selection. It initially shows: none
After this is selected, I can enter my password and everything is fine in mobian and manjaro/phosh. wifi works.
In january, I was able to initally connect in ubuntu touch without problems.
Now, it loops prompting me for the password, though it shows "connected".
I can select "cancel" and everything is fine. wifi works.
Today, I tried manjaro/lorimi (newest developer).
It loops prompting me for the password. No connection.
Any idea?
My guess would be one of the four:
1. My location is Europe/Germany
2. My wifi router is a AVM Fritz Box (newest firmare)
3. Fritz Box security settings have "WPA2/WPA3" enabled.
4. My SSID is numerical (think of Douglas Adams).
Anyone with similar problems?
RE: no connect to wifi on first startup - derbaertigefrytz - 02-12-2021
modified the connection file
/etc/NetworkManager/system-connections/<SSID>.nmconnection
replaced the [wifi-security] section with
key-mgmt=wpa-psk
psk=<myKey>
This worked. I started a system upgrade with pacman.
After a while, the device locked itself and the wifi connection was lost. It did not come back.
The interrupted system upgrade rendered the system unbootable.
:-(