OpenELEC with media_build


Update (13 Nov 2012): Since OpenELEC is now on a recent kernel there’s no point to media_build any more, and I won’t be doing any further builds. Some DVB drivers aren’t enabled, but this is easy to rectify (it didn’t take very long to get CE6230 support mentioned below sorted out).

Update (10 Nov 2012): Since newer kernels were included in OpenELEC at the end of October I’ve not been able to create new releases with media_build. The good news is that it913x DVB adaptors (like mine) now work just fine with regular OpenELEC. The bad news is that various other DVB adaptors (e.g. CE6230) are missing from regular OpenELEC. If I figure out some other way of including missing drivers I’ll create some new builds – but don’t hold your breath.

A lot of people have been having issues with driver support for digital TV devices that can be fixed with the media_build drivers. I’m pleased to announce that I’m now publishing release bundles that include media_build using the same automated mechanism that I put together for regular release bundles and SD card images (NB I have no plans to do SD card images for media_build as it’s relatively trivial to copy a release bundle onto an SD card).

10 Responses to “OpenELEC with media_build”

  1. 1 mojstermiha

    It is possible to build OpenELEC with enabled module 8021q and vconfig? Is this enabled by default in PVR package if I build it myself?
    Thanks! :)

    • 8021q and vconfig are already in the mainstream build (and the media_build variant this post is about). If you don’t have them then try updating (I just tested with r12017).

  2. 3 eyeamok

    I built my own Generic-OSS with the media build file from Stefan Saraev, but it is 6 months old and genpix skywalker not recognized,however geniatech dvb works now, so my question is this Could you post a Generic-OSS version with latest media build, or could you tell me how to use my own compiled folder of media build. I downloaded and compiled v4ldvb already from,_Build_and_Install_V4L-DVB_Device_Drivers, basic approach, no errors. not sure how to add to generic-OSS build
    or after looking thru meta file I guess it would be just as easy to edit the Http address and PKG version if that works?? sorry dont have a raspberry yet.

    • I only started doing this because OpenELEC support on the Raspberry Pi was somewhat behind the mainstream, so I have no plans to do builds for x86 etc.

      I’ve had a go myself at trying to merge compiled drivers into an OpenELEC release bundle and ran into a nightmarish web of complexity.

      The best suggestion that I can make is that you have a go at building for yourself. If you don’t have a suitable machine to run the build on then take a look at my guide on building in the cloud (Azure IaaS might have issues around its storage subsystem, but if you’re just after a single build then the 3 month free trial should get you there). You’ll probably have to follow Tiago Pires’s guide to get the media_build stuff added, but after that all that should need to change is the ‘make’ line.

      • 5 eyeamok

        Tiago Pires’s guide?? do you have a link to this, did a search found nothing.

  3. 6 eyeamok

    Never mind that is the guide I have been following, I just changed the Package line to
    PROJECT=Generic_OSS ARCH=i386 PVR=yes make release
    and edited the option file in Generic_OSS and it works fine,
    I was just looking for a Newer version of media_build to pull and install, Stefan Saraev version is 6 months old and doesn’t load genpix driver.

    If you have a newer version of media_build couldn’t I just link to it in the meta file and pull from it instead of stefan saraev’s?? or are you using that version also??

    • Here’s Tiago’s guide, though it sounds like you already know what you’re doing.

      I’ve just been using Stefan’s version of media_build (as that was sufficient for the USB DVB device I have).

  4. 8 Vic

    Hi Chris, I’ve been using your builds till Oct 26th. I’m trying to compile & enable my dvb ec168 driver but without luck, can you please explain me how can I do that?

    This is my log with yours…
    Jan 1 01:00:08 openelec kernel: [ 4.440042] dvb-usb: found a ‘E3C EC168 DVB-T USB2.0 reference design’ in cold state, will try to load a firmware
    Jan 1 01:00:14 openelec kernel: [ 10.744985] dvb-usb: downloading firmware from file ‘dvb-usb-ec168.fw’
    Jan 1 01:00:14 openelec kernel: [ 10.989208] dvb-usb: found a ‘E3C EC168 DVB-T USB2.0 reference design’ in warm state.
    Jan 1 01:00:14 openelec kernel: [ 10.991130] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
    Jan 1 01:00:15 openelec kernel: [ 11.001966] DVB: registering new adapter (E3C EC168 DVB-T USB2.0 reference design)
    Jan 1 01:00:15 openelec user.warn kernel: [ 11.158925] DVB: registering adapter 0 frontend 0 (E3C EC100 DVB-T)…

    With mine nothing.


    • If you take a look in you’ll find a file called linux.arm.conf, and in that file you’ll find (presently on line 1511):

      # CONFIG_DVB_USB_EC168 is not set

      change that to:


      and run the build again, which should give you a version with the driver you need enabled. If that works out for you I’d suggest raising a feature request (as an issue) in the OpenELEC GitHub to get that driver enabled by default.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.

%d bloggers like this: