Any news?
Thats nice to know …thanks
I can confirm that there is definitively a problem with wifi dongles.
Mine is a TPLINK TL-WN725N V2 (chipset rtl8188eu) and is running on my new Raspberry 2.
It seems to work, but after a while (~10 - 20 hrs) it disconnects from the network apparently with no reason (or, even if connected to the WiFi network, simply don’t work: no ssh, no smb share etc.), . This dongle works fine with Raspbmc and Raspberry mod. B.
If there’s something I can do to to track down the problem, please let me know 
Epg.
A debug log would be nice…
Next time it drops the connection upload your logs using the log uploader in OSMC settings. (before rebooting) Of particular interest is the system Journal, but all logs may be helpful.
For what it’s worth rtl8192cu and rtl8188eu seem to be the two drivers that between them are causing most of the wifi problems reported.
@DBMandrake: I agree, a log file would be nice, but how can I upload them (using the log uploader) if my Internet connection fails?
I could try to re-connect to the wifi network using remore and OSMC Settings->Network and, if it works, upload the logs via log uploader, right?
If I can’t reconnect using keyboard/remote, the only way is to reboot my Raspberry 2, so I think the logs aren’t so useful to upload, but maybe I’m wrong.
Ah, just a question: with “sudo journalctl” (new systemd log files?) I can obtain all the system logs (except kodi log) or there are other commands to show the logs (in Raspbmc I have the system logs in /var/logs and I can easily view these logs).
About the driver: rtl8188eu.ko with raspbmc have never had any failure in connection stability, perhaps the dongle itself is not so fast.
Thank you.
Epg.
log is uploaded after failing wifi connection
1 putty did disconect .
2 could not read NAS anymore to play media
3 attached lan cable
4 uploaded log via osmc log uploader
log name uzehawohas
ping times before failing
Pinging 192.168.1.254 with 32 bytes of data:
Reply from 192.168.1.254: bytes=32 time=1ms TTL=64
Reply from 192.168.1.254: bytes=32 time=1ms TTL=64
Reply from 192.168.1.254: bytes=32 time=1ms TTL=64
Reply from 192.168.1.254: bytes=32 time=1ms TTL=64
Ping statistics for 192.168.1.254:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 1ms, Average = 1ms
ping after failing
ping 192.168.1.254
Pinging 192.168.1.254 with 32 bytes of data:
Reply from 192.168.1.254: bytes=32 time=237ms TTL=64
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 192.168.1.254:
Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),
Approximate round trip times in milli-seconds:
Minimum = 237ms, Maximum = 237ms, Average = 237ms
tried to upload a full log by omsc log upload did not get a conformation or a log name
If you have a keyboard, once the problem occurs you could exit from Kodi, press ESC then log in at the console.
Then save a copy of the current journal to a file:
sudo journalctl >journal.log
After that you can reboot or do whatever you need to to get a network connection and use the paste-log command to upload the saved log:
paste-log journal.log
journalctl replaces all of the log files that were previously saved by syslog in /var/log. There are many command line options for journalctl that lets you filter based on the source of the log messages etc.
Raspbmc used a 3.14 kernel, OSMC uses a 3.18 kernel, so the kernels and drivers are very different. We are forced to use a 3.18 kernel to support the Pi 2 but the later kernels seem to be more problematic with some wireless adaptors, but we are doing our best to solve this issue.
2 Likes
managed to upload some logs
do the devs need more info ??
A link to the logs perhaps ? 
log files uploaded by, programs\osmcsettings\log uploader
first log : see above
1 log name uzehawohas
second log
2 if i do a batch of files i dont get a file name only http:\paste.osmc.io ,no file name (bug?)
uploaded a log at: time 12:47 cet march 28
3 also have a journal.txt, can i upload it here in plane text?
I have a Raspberry Pi B+ with a similar problem. When the screensaver kicks in, WIFI is lost. Can’t ping the device anymore.
I’ve connected a keyboard to the RPi. When I tap a key the screensaver stops and shortly after the WIFI comes back up and I can login again.
EDIT: WIth media-center stopped the WIFI-connection remains unstable. Dropping out for a couple of minutes every now and then. Very frustrating, as I’m trying to copy in my ~/.kodi directory from a RaspBMC backup…
EDIT2: some logging:
2015-03-28 16:18:27] nfs: server 10.0.1.220 not responding, still trying
[2015-03-28 16:21:01] nfs: server 10.0.1.220 not responding, still trying
[2015-03-28 16:21:09] wlan0: authenticate with bc:f2:af:9d:7c:35
[2015-03-28 16:21:09] wlan0: send auth to bc:f2:af:9d:7c:35 (try 1/3)
[2015-03-28 16:21:09] wlan0: authenticated
[2015-03-28 16:21:09] wlan0: associating with AP with corrupt beacon
[2015-03-28 16:21:09] wlan0: associate with bc:f2:af:9d:7c:35 (try 1/3)
[2015-03-28 16:21:09] wlan0: RX AssocResp from bc:f2:af:9d:7c:35 (capab=0x31 status=0 aid=5)
[2015-03-28 16:21:09] rtl8192cu:rtl92cu_set_hw_reg():<0-0> switch case not processed
[2015-03-28 16:21:09] rtl8192c_common:rtl92c_fill_h2c_cmd(): return H2C cmd because of Fw download fail!!!
[2015-03-28 16:21:09] rtl8192c_common:rtl92c_fill_h2c_cmd(): return H2C cmd because of Fw download fail!!!
[2015-03-28 16:21:09] rtl8192c_common:rtl92c_fill_h2c_cmd(): return H2C cmd because of Fw download fail!!!
[2015-03-28 16:21:09] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[2015-03-28 16:21:09] wlan0: associated
[2015-03-28 16:21:27] nfs: server 10.0.1.220 not responding, timed out
[2015-03-28 16:21:32] nfs: server 10.0.1.220 not responding, timed out
[2015-03-28 16:21:36] nfs: server 10.0.1.220 OK
My Pi B+ using RTL8192CU appears to have a more stable connection after the latest update. The connection is still up after 8+ hours (prior it would last less than an hour). I am still having an issue that it does not automatically connect if I reboot the PI, I have to manually initiate the connection each time. Let me know if a log would help and I can upload one.
Yes, a log will help.
maybey polluting the forum .if so let me know i wil delete it
Yes, absolutely polluting. Please use http://paste.osmc.io or similar to provide a COMPLETE, uncut debug log.
I just installed OSMC (RC1) (been a raspbmc user for a long time), and am having issues with wifi drop outs. I can confirm it works after a reboot, but shortly after, it stops till I reboot again. I am currently using the edimax ew-7811un and it works ok under raspbmc. Is this a known issue? I can provide additional detail if needed.
I am running the RPi B not B+ or RPi 2
Yes many have this on RC including me on both my wifi adapters.
I can confirm that this happens to me also on 3 wifi adaptors also tried them using raspbmc no problems there so its an issue with the rc version strange that I had no drops at all using the alpha 4 version of osmc so whats changed since then ? so many people have the same issue but nothing has been resolved as of yet can the devs say why ?
Read above that the new 3.18 linux kernel(alpha4 had 3.14)that support pi2 is the culprit … Hope there is a fix soon. Lucky me I didnt sell my old pi with raspbmc.
1 Like
Just wanted to add I am having the same issue with a RPi B and the Edimax ew-7811un