Below you'll find the questions that are asked most often by users (both old and new!). Hopefully you'll be able to find the answers to your problems quickly and easily.
Is OpenELEC free?
OpenELEC vs. XBMC Live. What is the difference to me?
I'm confused, which build do I need for my system?
What are unofficial builds and should I use them?
How do i use SSH?
What are the default SSH username / password?
How do I change the SSH password?
Where is the roadmap?
What is the relationship between OpenELEC and XBMC?
Can I sell hardware with OpenELEC pre installed?
How can I help?
Why are there so many versions of OpenELEC?
There are many different OpenELEC builds and the most appropriate one for your system will depend on what hardware you're running. See the below page for help choosing the right one for you:
We've implemented an automatic way of uploading troubleshooting logs to the pastebin website so you can just post URLs in the forums.
Example 1: To upload the message file:
The above command will return a URL pointing to the pastebin website where you can find your messages file
Example 2: We ask for the dmesg output:
You won't see the dmesg output like you normally would as it's been sent to pastebin. Again it will return with a URL which can be shared with developers or in the forum for others to troubleshoot issues.
The automatic update process may fail if you're running a snapshot release and you're upgrading to the latest release. If it does, follow this guide to update your system.
You may see the error:
Error Code: INIT_$ that means: Could not mount/flash/SYSTEM ### Starting debugging shell ....type exit to quit @@@ #
>forward to new URL in documentation
If you've upgraded from one of the 1.x stable builds to a PVR or Pre-Eden build, you'll notice that all of your shares that are mounted with netmount.conf don't work any more. NFS and SMB are now fully supported inside XBMC, so the netmount script isn't required anymore.
To add sources in XBMC from NAS shares, use one of the following when adding a new source:
The wiki link below will show you how to use SSH, and show you the commonly used commands.
The default user and password for the prebuilt binaries of OpenELEC are:
Both the username and password are case sensitive, so if you can't log on try checking caps lock is turned off!
At the moment it's not possible to change the root password as it's held in a read-only filesystem. However, for the really security conscious advanced user, you can change the password if you build OpenELEC from source.
We strive to support as many hardware devices as possible. We do have a list of supported hardware, although it's not complete so if your hardware isn't listed that doesn't mean it won't work. Since OpenELEC can be installed to a USB key, you can try it on your system without affecting the OS you're already running to see if your hardware is compatible or not. Either way, create a post in our Supported Hardware forum so we know. If it doesn't work, we'll do our best to add it in our next build.
Yes, it really is.
Sure. If it is useful to the majority of OpenELEC users and it and all it's dependencies can be added without compromising the project's goals then it would be viable for addition as a core feature. If it is large or of less overall interest it should be requested as an XBMC addon.
Certainly, but there is a stumbling block right now; in the short term we don't have the documentation or staff in house to support this. If you feel you can help us create and support add-ons for OpenELEC then please get in contact.
Definitely, however you need to be prepared to assist us. Post in the forum and wait for specific questions. Respond promptly, developer time is precious.
OpenELEC is built from the ground up to explicitly include only what is required. XBMC Live starts from a full Linux distribution and pars down from there, meaning your install contains large amounts of content you don't actually need. Also, OpenELEC is an appliance - meaning trivial system wide updates including XBMC. Live requires Linux knowledge and time to maintain. OpenELEC maintains itself automatically.
In the short term there will not be a roadmap. In these early days plans are changing as the OpenELEC team evolves. This may change in the future.
Yes, it is possible to dual boot OpenELEC with another OS but we don't support it. OpenELEC is meant to "own" the system and if you want to dual boot you accept the risk in doing so. Help is available in the forums.
Via the OpenELEC forum or IRC/chat channels. Remember support is free and fuelled by volunteers. Be courteous, patient and above all prepared to do your part. Remember to search the site guides and forum thouroughly BEFORE requesting help.
OpenELEC and XBMC are two different open source projects. Whilst there is some staff overlap and a good relationship between the projects they are discrete.
Unofficial builds are built by users. They may contain their own development code or some other tweak. In general, unless you have an absolute requirement that's only fulfilled by an unofficial build, always run official build. Unofficial builds are only supported by the user that creates them, not the OpenELEC team.
Yes, but please contact us to discuss first since it will increase our support workload.
In any way you see fit. Open source projects run on contributed code, donations, support in the forums and documentation. We welcome all assistance.
Good question. Because OpenELEC is a streamlined Linux distribution that includes only the essential software components and drivers needed to run XBMC and a handful of supporting apps/services, there were multiple images each supporting a specific set of Graphics/GPU chipsets.
The following builds are available for the previous version 3.x, "Frodo":
|ION||Systems with an Intel Atom CPU and an NVIDIA graphics card|
|Fusion||Systems with an AMD Exxx series CPU and AMD (ATI) HD graphics|
|Intel||Systems with Intel Core series or Atom CPU and Intel GMA graphics|
|Xtreamer||A specific build for on of our sponsors, the Xtreamer Ultra|
|Apple TV||A build for Apple TV generation 1 devices|
|Generic||A "catch-all" build for most systems (includes drivers for all of the above)|
|Generic OSS||A "catch-all" build for most systems including older systems|
|Raspberry Pi||An ARM build for the Raspberry Pi. This will not work with other ARM systems.|
If you don't know which one you need, use the Generic builds. If you have problems with your graphics, try the Generic OSS builds as they can support older graphics cards.
In addition, you will see options for 'Stable' (out current release), 'Legacy' (our last release) and 'Testing' (a preview of our next release). If you don't know which one you want, it's likely you want the stable release as the testing release may be unstable and the legacy release may be missing several features or lack support for newer hardware components.