Hi,
after upgrading to OSMC January 2017 2017.01-1 I am no longer able to connect to secure networks or in networks with hidden SSID.
The previous version did not present a problem.
WiFi hasn’t been changed in this version so nothing obvious comes to mind.
Check power supply and logs.
What happens if you try and connect manually via the command line?
I can’t log in to the command line
When it comes written “osmc Login:” I write “osmc” but the answer is incorrect login.
I have a RP Zero then I run the association to a network without PW and not hidden SSID to load the logs.
sudo journalctl | paste-log
http://paste.osmc.io/jaqijopegi
dmesg | paste-log
http://paste.osmc.io/usajejimab
gen 30 17:36:01 osmc wpa_supplicant[259]: wlan0: SME: Trying to authenticate with a2:63:91:57:9e:8a (SSID='casabianco' freq=2412 MHz)
gen 30 17:36:01 osmc kernel: wlan0: authenticate with a2:63:91:57:9e:8a
gen 30 17:36:01 osmc wpa_supplicant[259]: wlan0: Trying to associate with a2:63:91:57:9e:8a (SSID='casabianco' freq=2412 MHz)
gen 30 17:36:01 osmc kernel: wlan0: send auth to a2:63:91:57:9e:8a (try 1/3)
gen 30 17:36:01 osmc kernel: wlan0: authenticated
gen 30 17:36:01 osmc kernel: wlan0: associating with AP with corrupt probe response
gen 30 17:36:01 osmc kernel: wlan0: associate with a2:63:91:57:9e:8a (try 1/3)
gen 30 17:36:01 osmc kernel: wlan0: RX AssocResp from a2:63:91:57:9e:8a (capab=0x411 status=0 aid=3)
gen 30 17:36:01 osmc connmand[192]: wlan0 {RX} 2 packets 282 bytes
gen 30 17:36:01 osmc connmand[192]: wlan0 {TX} 2 packets 288 bytes
gen 30 17:36:01 osmc connmand[192]: wlan0 {update} flags 102403 <UP,LOWER_UP>
gen 30 17:36:01 osmc connmand[192]: wlan0 {newlink} index 2 address 00:E1:B0:35:46:75 mtu 1500
gen 30 17:36:01 osmc connmand[192]: wlan0 {newlink} index 2 operstate 5 <DORMANT>
gen 30 17:36:01 osmc wpa_supplicant[259]: wlan0: Associated with a2:63:91:57:9e:8a
gen 30 17:36:01 osmc kernel: wlan0: associated
gen 30 17:36:01 osmc wpa_supplicant[259]: wlan0: WPA: Failed to set PTK to the driver (alg=3 keylen=16 bssid=a2:63:91:57:9e:8a)
gen 30 17:36:02 osmc kernel: wlan0: deauthenticating from a2:63:91:57:9e:8a by local choice (Reason: 1=UNSPECIFIED)
gen 30 17:36:02 osmc wpa_supplicant[259]: wlan0: CTRL-EVENT-DISCONNECTED bssid=a2:63:91:57:9e:8a reason=1 locally_generated=1
gen 30 17:36:02 osmc wpa_supplicant[259]: wlan0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect
gen 30 17:36:02 osmc wpa_supplicant[259]: wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=1 ssid="casabianco" auth_failures=1 duration=10 reason=WRONG_KEY
Given that I enter the data from the GUI could be a keyboard layout problem?
So before you enter the password you get a “incorrect login” or after entering password? Could that be a similar keyboard issue?
Maybe temporarily connect Ethernet and try login via SSH
Hi Sam.
I have the exact same problem that that Nicole has after the update of January 2017.01-1
I have also found other posters with exactly the same issue and I am wondering if there is a problem with this update.
My issue has not been resolved yet either. I am wondering if we need to open up a new thread and have everyone Post in one area regarding this problem?
Thanks in advance I’m sure everyone would appreciate a resolution to this
Hi Nicola.
I was wondering if you could do something to verify if you and I do indeed have the same problem. Your issue had to do with a hidden SSID.
If you remove the hidden SSID from your router are you then able to connect to the network?
The only way I could get the pie 3 to be seen by the router is to set the router to a open network. Before you remove the hidden SSID see what happens if you only put the router to open network?
Look forward from hearing from you let’s see if we can resolve this.
I didn’t make any changes to networking in the January update. If you believe the issue is introduced by January’s update, please confirm the bug does not occur in the December version and post a full set of logs for both versions
OK
I will make a disk backup of the January SD card and install the Dec.one.
I will have to get back next week, most likely Wednesday.