When you have OSMC, why would one even need LE/OE is what I don’t understand.
That is what I hope to discover…
Noobs install went fine. Boot OSMC and initial wizard went fine. Connect Wifi fine (only 2.4 GHz).
First, update OSMC, from 2016.10-1 to 2016.10-2, then reboot.
Now into My OSMC > Pi Config.
Enable my HifiBerry Digi+ overlay gives: “Warning: GPIO remote support with default pins incompatible with HifiBer…” (cut off and no message scroll?). Hmm, “Enable LIRC GPIO support” is enabled by default. Google “OSMC LIRC”. Ah, that’s for a Infrared remote receiver, which I don’t have connected for the moment. So disable that I suppose.
Is there no wiki walk-through for all the Pi Config settings? That would save a lot of Googling.
IMHO settings should always explain themselves onscreen.
Reboot. Check the Digi+ works. Mute TV-sound, receiver on… And oh yes, choose Kodi audio output device of course. Yes, sound on my receiver!
Switching skin to Confluence gives a Third attempt works. ???
its nice and all with this “review” but please pick a OS and stick with it cause we seen enough of these OSMC vs *elec threads to last us for a lifetime, we all have our own reasons for running the mediacenters and we made our choice.
as for your sad face as its been said for bugs there is a demand for debug logs or else your issue didnt happen
Now to try to get on the 5GHz network wih the Edimax USB dongle.
First disable the internal Pi 3 Wifi adapter.
Search of the forum gives two obscure suggestions:
First this one, with no explanation of what it exactly does (perhaps more than I want?),
and a second option, blacklisting the drivers for the onboard Broadcom wifi as per over in the RaspberryPi forum
/etc/modprobe.d/raspi-blacklist.conf #wifi blacklist brcmfmac blacklist brcmutil
Let’s see which works. Can I edit this comfortably from the My OSMC Pi Config Editor? Let’s try the blacklist option first, as I understand what it will do. Hmm, strange editor. And is this config.txt just for OSMC, or SDcard wide, so also for LibreElec? Well, I can soon find out now I have my Noobs multiboot…
Nope. The blacklist option doesn’t work. The onboard Wifi is still there.
I thought maybe switch back to OSMC skin for better editor experience, but that was a mistake. Now when I get into the editor and select a line, the edit or delete dialogue appears in the darkened background! Behind the config.txt lines! Ouch. Why not simply Nano, which everyone wil get along with, instead of this prehistoric attempt at a text editor?
Okay, better get back to Confluence and try the other method (dtoverlay=sdhost)…
Oooh, switching skins immediately gives really weird often corrupted results, better reboot every time… (I can imagine, but it should suggest or force that).
Yep, that second option (dtoverlay=sdhost) worked. Now there’s only one 2.4GHz plus my 5GHz. And clicking on the 5GHz even allows me to connect!
Pi 3 with OSMC and Edimax USB Wifi dongle.
OSMC lists both onboard and Edimax 2.4GHz plus the Edimax 5GHz. wlan number is arbitrary? and not physical?
Whichever wlan 2.4GHz I choose it will change to the other wlan.
Choosing 5GHz does nothing, clicking does nothing.
First attempt to disable onboard Wifi with blacklist in OSMC config editor is to no avail.
Second attempt with quick and dirty solution in (dtoverlay=sdhost) DOES work.
Now to be seen how stable the Edimax 5GHz is. Any issues will be in a separate thread if here at all.
I booted to LibreElec and it still shows both 2.4GHz plus the 5GHz networks.
Lesson learned: Pi config is OS specific. Separate for every OS on your SD.
A plus for LibreElec: it simply allowed me to connect with my 5GHz without uncomfortable config editing, in contrast to OSMC (see my previous post on this thread).
A big plus for OSMC: it allows me to set the HifiBerry Digi overlay from the GUI (graphical user interface) without any config editing, allowing me to choose my Digi+ in the Kodi Audio settings.
Until now I don’t see any major mind blasting difference. Could you give me the three most important reasons for choosing OSMC in a nutshell?
Are both OSMC and LibreElec not simply thin shells around Kodi?
I was with one (OpenElec). And it went away.
I’ll get round to uploading debug logs when I’ve bitten through the first hurdles on my own. I’m not intending to waste my time on debugging software I simply want to use, out of the box… RTFM is so prehistoric. Any software that calls itself ‘stable’ should be self documenting and work OOTB for 95%.
been using OSMC for the better parts of 2 years seldom had any issues that i couldnt resolve myself and those times that i had to resolve it via help Sam Nazarko has always been around to fix my issues.
its all about knowing Debian and for those that actually use a real OS and not a busybox knows that its all about RTFM
[quote=“SaintNick, post:12, topic:20109, full:true”]Are both OSMC and LibreElec not simply thin shells around Kodi?
LibreELEC is a thin shell around Kodi, OSMC is a thick shell around Kodi. OSMC is a full Debian derivative OS under the hood so you can use it for other things as well as simply driving Kodi
You can edit the dtoverlay=sdhost option in the Config Editor. If you wish to blacklist the modules, it must go in a different file.
Just for the loaded OS if you are running NOOBS.
Can you upload a log? This has been covered in the Wiki.
You can use nano to edit files. This is explained in the Wiki. You can use vim, emacs or whatever editor you like. You can also login via WinSCP and edit it from your PC. But in your first post you said you didn’t want to have to use SSH or the command line. A lot of our users come from Windows backgrounds and don’t know how to use nano
I understand that this is new to you: in the new My OSMC we will add some more features, like disabling internal WiFi, but this is low on the list of priorities. A lot of your questions are answered on the Wiki.
If you do choose to use OSMC as your daily driver, you should install it from osmc.tv/download. NOOBS is great for trying several OS, but it’s not good once you know what you want (as you’ll want to use the full size of your SD card).
This is also covered in the Wiki.
Now I see the problem. Nice try, but that’s the lazy way out. We’ve spent time preparing resources to help newcomers. If you don’t read them, you will be confused. OSMC is based on Debian, which is quite expandable (you have 40,000 packages you can install from the command line). Depending on what you want to do, you’re always going to read around the subject.
The more people bother to read the Wiki, the more likely we are to expand it. But if you have suggestions, you can improve it. Just click the ‘Make this page better’. I haven’t had a lot of time to work on the Wiki lately.
Haha. I deserved that.
Right, I’m heading over to the wiki for a simple walkthrough on installing VNC. Will be back…
I’m back already.
Wiki search for “VNC” gives “No results”
Next option, dig into the forum, hope I don’t catch unnecessarily old/depricated results…
I remember for OpenElec it was not too difficult (client version was important!)
Search VNC on the forum
Other bits and bobs are on the Wiki
I’ll agree that our onboarding for the less familiar sucks. I’m working on improving that.
To save you from disaster
Great! VNC is now working for me. Now I can actually tinker away with OSMC while family are watching TV.
Sandbird’s how-to for installing the VNC service worked almost in one go, except for missing sudo in the instructions for starting the service. I’v suggested Sanbird update and add that.
So anyone wishing to install VNC on OSMC:
- use Sandbird’s how-to for installing the server part on the Pi
- Windows users use RealVNC VNC Viewer 5.2.3 (r8648) for client (later versions do/may NOT work in this scenario)
- do NOT expect to watch movies with VNC
Always good to see a newcomer find solutions to their problems.
Let us know how you get on.
What else does dtoverlay=sdhost do, other than disabling the internal wifi? It sounds like it might do a lot more. Should I prefer the blacklist option?
SDHost is already the default overlay.
By adding this overlay directly, you are overriding default parameters and disabling the SDIO hookup.
Either way will work perfectly fine.