similar issue here, but something odd is happening as well.
using OSMC RC for raspberry pi 2, on powersupply @2100 mAh, only 2 non-factory items plugged into usb for now
osmc@osmc:~$ lsusb
Bus 001 Device 006: ID 0bda:8176 Realtek Semiconductor Corp. RTL8188CUS 802.11n WLAN Adapter
Bus 001 Device 005: ID 05fe:1010 Chic Technology Corp. Optical Wireless
my wifi will randomly stop working, so i check the osmc settings addon and am able to see the networks in range, without problem. i am able to select my network, and up pops the keyboard for inputting my wifi password. This is obviously strange because i was previously connected to the same network for at least 18 hours. i enter the password, and i get a wifi connecting dialog and then pops up an error, unable to connect to wifi network(or something) but was still able to see networks in range This continued each time i rebooted from the on screen reboot option, and was only resolved when i unplugged the rpi 2 and plugged it back in, at that time i was able to input the password and was able to connect. This same issue has been present from the first time i tried to connect to the wifi on a clean new install. Only way to resolve it is a hard reboot
I dont see anyhting in logs, but here are the 2 from.kodi/temp
almost unusable lol no its unusable unless you plan to use it without wifi rc version is less stable than the alpha version ? going back to raspbmc here until the final version is sorted and the creases are ironed out I know its slower but at least it does what you want it to not even video will stay on for longer than a minute pi just totally freezes doesn’t happen on alpha 4 or raspbmc so theres problems there somewhere
Well, for me, sometimes it works for 30mn, so i can watch a short episode before having to do a hard reset =)
And yes it was working really fine on alpha 4 with a Pi 2
I also miss the small fonts… the one on the RC are really huge!
We’re well aware of wireless driver issues in the RC and are working on getting them resolved. (If it was easy, it would have been done already, unfortunately it is anything but easy as wireless driver support in Linux is a bit of a minefield especially in the latest kernels)
However I think it’s unfair to say that Alpha 4 is “much more stable from all points of view” - looking at it from an inside perspective I can assure you that there are a LOT of problems with Alpha 4 that are resolved in the RC. I personally don’t agree that Alpha 4 is more stable, especially after having worked hard to fix so many problems present in Alpha 4.
If you have real problems with the RC aside from wireless then we need to know about them - giving up and going back to Alpha 4 does not help anyone - you will be stuck on Alpha 4 forever, (which is now orphaned and will never receive any updates) and any problems with the RC that you are seeing may not get resolved.
Don’t assume that because you see a problem that the problem is obvious and that everyone else (including the devs) see it. To get issues resolved moving forward people need to help test the RC, report the problems they find, be willing to test and provide logs when asked and so on.
We want to get the final release completed but if everyone just runs back to Alpha 4 because its “easier” then we will never get a good solid final release.
I’m sorry if I sounded dismissive. I know you guys are hard at work and my attitude does not help.
And I know what goes in to making a great product, and know that you guys are doing the best you can in doing it.
Now, maybe a little backstory will get you to understand my point of view. Me and my SO spend 10, 11 hours per day at work. I being a software dev, she being a HR consultant, have really busy lives. The only time we get to spend together, as you can imagine, is a couple of hours at the end of the day, when we watch something like friends or Seinfeld, and so on. For those two hours, I literally can’t afford to investigate problems, or search for workarounds, or verify and upload logs. We just can’t.
Also, this weekend is my first weekend free, without school, without deaths in the family, without parents in law visiting, etcetera. Based on this, I was planning on buying a second microsd on which to install the RC, without disrupting the current stable (for me) Alpha 4, and seeing how I can help out.
And my initial affirmation
was based on the fact, that I had huge freezing issues on RC, but no one else was mentioning them over here, so I didn’t want to start complaining for a issue, I probably was the only one to have. Was planning on going back at a later time (this weekend) to see if they persist, and if larger affecting problems (the wifi) have been fixed, so I can report my problem which is puny in comparison.
Updated using built in updates module from OSMC settings and a LAN connection. I then disconnected the LAN connection and tried the wifi but it fails to connect to my WiFi. Light on dongle in now blinking (wasn’t on RC1). Rebooted the device but same thing.
This thread has had a few too many replies for me to really keep track of
I’d suggest those still experiencing WiFi issues with RC2 start a new thread with the dmesg output, their dongle name and the symptoms they’re experiencing
So I just pulled the plug on my LAN connection again but left Wired enabled in OSMC settings. I then selected my WiFi and it connected but didn’t ask for my Wifi password. I then tried to recreate what I just did without any success. To get wifi to connect again I had to disconnect the LAN (leave adapter enabled). Close the network settings, go back into network settings and then connect to my Wifi.
Are you saying Wifi did not automatically connect while you had Ethernet connected, but that once you unplugged Ethernet Wifi did automatically connect ?
If so this is the expected behaviour. Even with SingleConnectedTechnology=false in /etc/connman.conf (a change we made recently) because Ethernet has higher priority than Wifi (PreferedTechnologies=ethernet,wifi in /etc/connman.conf) if you already have Ethernet plugged in (the higher priority device) it will not bother to auto connect the lower priority device.
You can still manually initiate a connection to wifi and they will both stay connected (until reboot) but it will only auto connect to wifi if Ethernet is unplugged. See the following connman documentation for an explanation: (Autoconnecting section)
Case
After connection to WLAN after few second/min i lost connection but only with internet internal network f.e. ssh still working, I can ping/telnet other computers in network.
To restore connection with internet I must restart router.
logs/others
WiFi connection is in good condition:
wavemon shows 96+% as link quality and 18dBm singal.
