Sup guys
I’m just new to RPi and OSMC, and I faced a problem with wi-fi connection
It doesn’t want to connect at all
Please, help me
Log file: Dropbox - kodi.log - Simplify your life
Please use a pastebin type site for logs… No one wants to clutter their drive with someone elses logs to view one time. We even provide a paste site for you http://paste.osmc.io
What chipset is the dongle using? How did you try to connect it and what is or isn’t happening? We need details more than “it doesn’t work” so that we can help.
This adapter is perfectly working on Windows and Raspbian
**
After I typed the password to connect to the network, it says that it connecting and after it fails and says that it can’t connect to network
please also provide the URL returned from
sudo journalctl | paste-logBump
**
Guys, really hot question. I dont know what to do. Need your help
Unfortunately I can’t tell from the logs what the root cause of the issue is - it appears to be reporting an authentication failure:
Jun 30 17:09:22 osmc wpa_supplicant[300]: wlan0: Trying to associate with f4:ec:38:fc:6f:26 (SSID='Marky' freq=2457 MHz)
Jun 30 17:09:22 osmc kernel: wlan0: send auth to f4:ec:38:fc:6f:26 (try 2/3)
Jun 30 17:09:22 osmc kernel: wlan0: authenticated
Jun 30 17:09:22 osmc kernel: wlan0: associate with f4:ec:38:fc:6f:26 (try 1/3)
Jun 30 17:09:22 osmc kernel: wlan0: associate with f4:ec:38:fc:6f:26 (try 2/3)
Jun 30 17:09:23 osmc kernel: wlan0: associate with f4:ec:38:fc:6f:26 (try 3/3)
Jun 30 17:09:23 osmc kernel: wlan0: association with f4:ec:38:fc:6f:26 timed out
Jun 30 17:09:23 osmc wpa_supplicant[300]: wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=4 ssid="Marky" auth_failures=1 duration=10 reason=CONN_FAILED
The only thing I can suggest really is testing that wifi adaptor on a different Wifi network or testing a different wifi adaptor on the same network.
This adapter is perfectly working on another divices and Raspbian. Also, I’ve got a couple devices working from time to time in this network fine.
**
This adapter(Ralink generic USB 802.11n adapter) has his own drivers on CD, that I hadn’t installed, because I din’t know how to install this( 2011_0719_RT3070_RT3370_RT5370_RT5372_Linux_STA_V2.5.0.3_DPO)
What version of OSMC are you using? i expect RC3
Have you installed all the updates released AFTER RC3 (you need to do that with a lan cable)?
After RC3 (you can fine tons of topics relating this issues) no one was able to connect to wifi (“connection failed”), until a couple of fixes by the dev team.
No, I’m using 2015.06-1
All updates are checked and installed
Should I try RC3 version?
I dont understand what’s the problem, but the adapter worked for one time after those manipulations:
Update through terminal(apt-get update and upgrade)
Reboot
Update through OSMC own updater
Reboot
Gone to Wireless and reenabled the adapter
**
After that it connected automatically and worked untill the end of session
After that I rebooted, and it didn’t work again(it fails to connect after typing password). Reenabling is not helping now
Hi!
On my Pi 1 model B I have a problem with the wifi failing to connect on a network which is password protected. It works fine if there is no encryption (open network). (I typed my pw correctly, tried at least 20 times and even with a password with only lowercase letters and no fancy characters).
I have the same wifi dongle on an other Pi (with Volumio) and it works perfectly with the password protected network.
So it seems there is a problem with osmc trying to connect to a wpa/wpa2 personal wifi.
Any idea?
Thank’s
Oliver
@Marky is that the same problem configuration as yours?
Rpi 1 model B with osmc fully updated up to july the 2nd.
Edit: the same happens after a clean install with new stable release.
I’ve got a RPi 2 model b with OSMC ver. 2015.06-1. Last checked updates today.
@oliver1 I face absolutely the same problem using OPENELEC, so the problem is in the Kodi core.
Can you both try connecting to wireless using the command line tool connmanctl. This will rule out (or implicate) the networking GUI.
To do so you’ll either need to temporarily connect Ethernet and run the command via an SSH session, or plug in a Keyboard and exit Kodi to log in at a local console session:
Once you’re logged into a command prompt the following demonstrates enabling wifi, scanning for networks and connecting to an authenticated network:
osmc@rpi2:~$ connmanctl
connmanctl> enable wifi
Enabled wifi
connmanctl> scan wifi
Scan completed for wifi
connmanctl> services
*AO Wired ethernet_b827ebd04564_cable
wifi_e894f6191023_hidden_managed_psk
VM420130-2G wifi_e894f6191023_564d1235f53035302d3247_managed_psk
connmanctl> agent on
Agent registered
connmanctl> connect wifi_e894f6191023_564d1235f53035302d3247_managed_psk
Agent RequestInput wifi_e894f6191023_564d1235f53035302d3247_managed_psk
Passphrase = [ Type=psk, Requirement=mandatory, Alternates=[ WPS ] ]
WPS = [ Type=wpspin, Requirement=alternate ]
Passphrase? xxxxxxxx
Connected wifi_e894f6191023_564d1235f53035302d3247_managed_psk
connmanctl> services
*AO Wired ethernet_b827ebd04564_cable
*AR VM420130-2G wifi_e894f6191023_564d1235f53035302d3247_managed_psk
wifi_e894f6191023_hidden_managed_psk
Let us know whether you are able to connect this way or not.
(BTW connmanctl has a very useful help command)
1 Like
Can’t be - Kodi itself has nothing to do with setting up wifi connections.
One thing OSMC and OpenElec share in common is using connman as the network manager which handles wireless connections. Raspbian does not use connman. There could potentially be an issue in connman - the above test with connmanctl may shed some more light.
Ok, will try in a few minutes
root@osmc:/home/osmc# connmanctl
connmanctl> connect wifi_0013efc5093b_4d61726b79_managed_psk
Error /net/connman/service/wifi_0013efc5093b_4d61726b79_managed_psk: Input/output error
connmanctl> connect wifi_0013efc5093b_4d61726b79_managed_psk
Error /net/connman/service/wifi_0013efc5093b_4d61726b79_managed_psk: Input/output error
connmanctl> enable wifi
Error wifi: Already enabled
connmanctl> scan wifi
Scan completed for wifi
connmanctl> services
*AO Wired ethernet_b827eb570082_cable
*A Marky wifi_0013efc5093b_4d61726b79_managed_psk
Vika wifi_0013efc5093b_56696b61_managed_psk
Sasha wifi_0013efc5093b_5361736861_managed_psk
Sherwood wifi_0013efc5093b_53686572776f6f64_managed_psk
connmanctl> agent on
Agent registered
connmanctl> connect wifi_0013efc5093b_4d61726b79_managed_psk
Agent ReportError wifi_0013efc5093b_4d61726b79_managed_psk
connect-failed
connmanctl> Retry (yes/no)? y
Agent ReportError wifi_0013efc5093b_4d61726b79_managed_psk
connect-failed
connmanctl> Retry (yes/no)? y
Connected wifi_0013efc5093b_4d61726b79_managed_psk
It seems that it worked on the third try.
Before you reboot after this session of manually connecting, can you capture the system journal ?
sudo journalctl | paste-log
The fact that it took 3 attempts to connect even using connmanctl immediately rules out a bug in the Networking GUI in OSMC settings.
If you’re absolutely sure that Raspbian connects reliably every time on the same Pi with the same wireless adaptor in the same location then it narrows the problem down to either the kernel driver for the wifi adaptor, a bug in connman or a problem with the wpa supplicant.