Unraid V6.2 Beta 19 DVB Files


CHBMB

222 posts in this topic Last Reply

Recommended Posts

Now Deprecated Please See Here

 

linuxserver_medium.png

 

DVB What?!

In order to use TVHeadEnd or MythTV with PCIe or USB DVB Tuners you need to run a special Unraid build which contains the necessary drivers. 

 

This replaces the Unraid bzroot and bzimage files (the OS) with newly created ones that have drivers for DVB hardware incorporated.

 

This post will include the latest builds I have done and be updated as LimeTech release new versions of Unraid as soon as I possibly can.

 

These are not necessary if you use Homerun or IPTV devices.

 

There are three steps necessary to getting a PVR Solution running on your Unraid Machine

 

1.  Installation Of DVB files

2.  Installation Of DVB Plugin (Only necessary for TVHeadEnd & MythTV Dockers - Not required for TVHeadEnd Plugin)

3.  Installation Of PVR Software: TVHeadEnd Docker, TVHeadEnd Plugin or MythTV Docker

 

1.  Installation Of DVB files

 

1.  Navigate to the root of your USB flash drive and rename bzroot & bzimage to bzroot-original & bzimage-original.

2.  Download the MediaBuild files and copy the new bzroot & bzimage into the root of your USB flash drive.

3.  Reboot

 

V6.2 BETA RELEASES

 

USE THESE AT YOUR OWN RISK.  I WILL NOT BE RESPONSIBLE FOR ANY DATA LOSS

 

I've created builds for the V6.2 Beta releases.

 

I will not be creating separate links for these as they often come quick and fast.  I will not be keeping these long term.  Once the Release Candidates are released, the Betas will be removed, and once Final hits, the Release Candidates will be removed.

 

To upgrade, first upgrade to LimeTech's normal (Non-DVB) build of V6.2 and ensure it boots and works as expected.  Then replace bzroot and bzimage as per normal with my DVB builds.  I will not be supporting direct upgrade from 6.1.x DVB to 6.2 DVB.

 

There are now three files involved in the DVB build

 

1.  bzimage

2.  bzroot

3.  bzroot-gui

 

The bzroot-gui file is common across all types of build, it is the same for stock Unraid, TBS, OpenElec & Digital Devices Experimental.  Accordingly, you can just keep the stock one that is installed.

 

Bzroot & Bzimage must be replaced as normal.

 

These are beta releases for Unraid and should be treated as such.  I will not be responsible for any data loss. 

 

Beta Builds Are Here.

 

OpenElec MediaBuild with Openelec Patch to include more drivers

Thanks to CvH over at the Openelec forums for this  :)

 

Unraid V6.1.9 V1.10 OpenELEC Drivers

bzimage

bzroot

bzimage.md5

bzroot.md5

 

Unraid V6.1.8 V1.10 OpenELEC Drivers

bzimage

bzroot

bzimage.md5

bzroot.md5

 

Unraid V6.1.7 V1.8 OpenELEC Drivers

bzimage

bzroot

bzimage.md5

bzroot.md5

 

Unraid V6.1.6 V1.6 OpenELEC Drivers

bzimage

bzroot

bzimage.md5

bzroot.md5

 

Unraid V6.1.5 V1.6 OpenELEC Drivers

bzimage

bzroot

bzimage.md5

bzroot.md5

 

Unraid V6.1.4 V1.6 OpenELEC Drivers

bzimage

bzroot

bzimage.md5

bzroot.md5

 

Unraid V6.1.3 V1.5 OpenELEC Drivers

bzimage

bzroot

bzimage.md5

bzroot.md5

 

Unraid V6.1.2 V1.5 OpenELEC Drivers

bzimage

bzroot

bzimage.md5

bzroot.md5

 

Unraid V6.1.1 V1.5 OpenELEC Drivers

bzimage

bzroot

bzimage.md5

bzroot.md5

 

Unraid V6.1 V1.5 OpenELEC Drivers

bzimage

bzroot

bzimage.md5

bzroot.md5

 

TBS unraid-dvb - Kernel Drivers with Official TBS Drivers

No thanks to TBS for making these closed source so unable to be included in kernel  ;D

 

Unraid V6.1.9 TBS Drivers V160219

bzimage

bzroot

bzimage.md5

bzroot.md5

 

Unraid V6.1.8 TBS Drivers V160126

bzimage

bzroot

bzimage.md5

bzroot.md5

 

Unraid V6.1.7 TBS Drivers V151229

bzimage

bzroot

bzimage.md5

bzroot.md5

 

Unraid V6.1.6 TBS Drivers V151105

bzimage

bzroot

bzimage.md5

bzroot.md5

 

Unraid V6.1.5 TBS Drivers V151105

bzimage

bzroot

bzimage.md5

bzroot.md5

 

Unraid V6.1.4 TBS Drivers V151105

bzimage

bzroot

bzimage.md5

bzroot.md5

 

Unraid V6.1.3 TBS Drivers V150728

bzimage

bzroot

bzimage.md5

bzroot.md5

 

Unraid V6.1.2 TBS Drivers V150728

bzimage

bzroot

bzimage.md5

bzroot.md5

 

Unraid V6.1.1 TBS Drivers V150728

bzimage

bzroot

bzimage.md5

bzroot.md5

 

Unraid V6.1.0 TBS Drivers V150728

bzimage

bzroot

bzimage.md5

bzroot.md5

 

Digital Devices Experimental unraid-dvb with Digital Devices Experimental Support

Digital Devices tuners only include support for DVB-S in the Kernel/Openelec builds.  DVB-T or DVB-C support requires this build.  You can read more about it here. Due to I2C Timeout errors, the fix detailed by Icho2000 has been included, see here. Icho2000 has also detailed how to use sleep with this build here

 

Unraid V6.1.9 Digital Devices Experimental Drivers V050316

bzimage

bzroot

bzimage.md5

bzroot.md5

 

Unraid V6.1.8 Digital Devices Experimental Drivers V090216

bzimage

bzroot

bzimage.md5

bzroot.md5

 

Unraid V6.1.7 Digital Devices Experimental Drivers V160116

bzimage

bzroot

bzimage.md5

bzroot.md5

 

Unraid V6.1.6 Digital Devices Experimental Drivers V021215

bzimage

bzroot

bzimage.md5

bzroot.md5

 

Unraid V6.1.5 Digital Devices Experimental Drivers V011215

bzimage

bzroot

bzimage.md5

bzroot.md5

 

Unraid V6.1.4 Digital Devices Experimental Drivers V051115

bzimage

bzroot

bzimage.md5

bzroot.md5

 

Unraid V6.1.3 Digital Devices Experimental Drivers V210915

bzimage

bzroot

bzimage.md5

bzroot.md5

 

Unraid V6.1.2 Digital Devices Experimental Drivers V090915

bzimage

bzroot

bzimage.md5

bzroot.md5

 

Unraid V6.1.1 Digital Devices Experimental Drivers V070915

bzimage

bzroot

bzimage.md5

bzroot.md5

 

Unraid V6.1.0 Digital Devices Experimental Drivers V010915

bzimage

bzroot

bzimage.md5

bzroot.md5

 

2.  Installation Of DVB Plugin For Docker PVR Solutions

This plugin from Saarg is used in conjuction with the TVHeadEnd docker and the MythTV docker, it checks for the presence of the mediabuild files, and that there are appropriate drivers for your DVB card.  More importantly, it sets appropriate permissions on the tuners so they can be used by the docker container.  (It is not required for the TVHeadEnd Plugin as this functionality is build into the plugin.)

Download it here.

 

3.  Installation Of PVR Software

 

For TVHeadEnd

Tvheadend is a TV streaming server and recorder for Linux, FreeBSD and Android supporting DVB-S, DVB-S2, DVB-C, DVB-T, ATSC, IPTV, SAT>IP and HDHomeRun as input sources.

Tvheadend offers the HTTP (VLC, MPlayer), HTSP (Kodi, Movian) and SAT>IP streaming.

 

Two forum members have currently got TVHeadEnd solutions for Unraid V6 users.  There is a conventional plugin from Mettbrot or if you prefer a docker container from Saarg, there is no real better way to do things, just different ways, so feel free to try either or both.

 

TVHeadEnd Plugin from Mettbrot

TVHeadEnd Docker from Saarg

 

For MythTV

 

MythTV is a Free Open Source software digital video recorder (DVR) project distributed under the terms of the GNU GPL. It has been under heavy development since 2002, and now contains most features one would expect from a good DVR (and many new ones that you soon won't be able to live without).

 

Sparklyballs has worked very hard to bring a MythTV docker container to Unraid, and the result of his efforts have now been released to the community in beta.

 

MythTV Docker from Sparklyballs

 

b.  Thank You

It's important to thank a lot of people who were extremely patient and helpful whilst I was trying to work out how to do this process.  In no particular order, thanks to ww & piotrasd, who were the early pioneers of this stuff on V5, gfjardim for kindly donating a script to make the whole process much easier, mettbrot & saarg of course for doing the real hard work of bringing the TVHeadEnd plugin & docker to Unraid V6, Sparklyballs for his work on MythTV, and Monkeyair who has changed his TV Tuner setup so much in the last few weeks and has enabled me to get so much practice doing these that I can now do them in my sleep.  ;D

 

c.  Linuxserver.io

I have been lucky enough to be invited to join ls.io and therefore we are now hosting these on the ls.io website, should prove a little more reliable than my personal dropbox.

 

Link to post
  • Replies 221
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Posted Images

Dropbox links are not working for me

 

Sorry about that, I set up the docker plugin to sync to /mnt/cache/dropbox but forgot to make the share cache only.  Mover moved everything over to the array last night and essentially emptied my dropbox account...

Not even the first time I've made this sort of mistake  ::)

 

:-[

 

The 6.0.0 links are now back up.  Apologies...

The older ones will take a little longer...

 

EDIT: Links to the older builds are back up, why anyone would want them is another matter but I set out to make them accessible, so they're accessible...  ::)

Link to post
  • 2 weeks later...
  • 2 weeks later...

Hi,

 

i got a little problem with setting up my Digitel Devices Cine CT V6 tuner card. I'm using Mediabuild with Openelec Patch Build 6.01.

So far it looks like my system finds the card during boot :

 

(form syslog)

Jul  8 20:15:41 Tower kernel: Digital Devices PCIE bridge driver, Copyright (C) 2010-11 Digital Devices GmbH
Jul  8 20:15:41 Tower kernel: DDBridge driver detected: Digital Devices DVBCT V6.1 DVB adapter

and lspci after booting :

02:00.0 Multimedia controller: Digital Devices GmbH Octopus DVB Adapter

.

 

But in /dev is no dvb folder. I just found a ddbridge folder. Inside is only on entry :  card0  nothing else.

 

According to http://wiki.openelec.tv/index.php/Supported_TV_Tuners this card is supported by openelec, so i thought it should work with this mediabuild. Did i miss anything or has anyone an idea what i can do?

tower-diagnostics-20150708-2017.zip

Link to post

Hey,

 

i also do have a problem here. Wanted to use tvheadend but also with the MediaBuild Files from here i only get these:

 

DDBridge driver detected: Digital Devices Cine S2 V6.5 DVB adapter

Port 0 (TAB 1): DUAL DVB-S2

DVB: registering new adapter (DDBridge)

DDBridge 0000:01:00.0: DVB: registering adapter 0 frontend 0 (STV090x Multistandard)...

DVB: registering new adapter (DDBridge)

DDBridge 0000:01:00.0: DVB: registering adapter 1 frontend 0 (STV090x Multistandard)...

 

But i have this Cine S2 V6.5 with an attached DuoFlex C/T/T2 extension. But i only see DVB-S2 in tvheadend. In my Windows VM there is the C-Part usable.

Do i have to change anything for using C? Don't use S2 anymore...

Link to post

Sorry guys, just moved house and no internet access at home at the moment, not even on mobile phone.  I think this is similar to a problem Monkeyair had which is detailed on Digital Devices website.  I did do a Mediabuild for Monkeyair to try and sort this out but he RMA'd the DVB-T component before we really got to the bottom of it.

 

You can also read about it here...

 

It'll be a little while before I am going to get to this one, i might have a copy of the mediabuild I did for Monkeyair around somewhere and if it's already in my dropbox I'll post links.  If it's on my Unraid box then there's nothing I can do until I get broadband up and running I'm afraid.

Link to post

No problem CHBMB,

 

i wanted to build it myself but the script isn't available in the dropbox anymore (build.sh)

 

Does anyone have this script (build.sh)?

 

I've reuploaded the script, had to use the original and update it to match the wiki, can't test it but give it a go.  Sorry about that..

Link to post

Ok looks good so far  8)

 

Jul  9 19:54:56 Tower kernel: Latest git patches (needed if you report a bug to linux-media@vger.kernel.org):
Jul  9 19:54:56 Tower kernel: 	1555f3bf5cc172e7d23c2b8db10d656d15bec13e [media] saa7164: fix compiler warning
Jul  9 19:54:56 Tower kernel: 	ebf984bb151e9952cccd060d3aba0b4d30a87e81 [media] v4l2: replace s_mbus_fmt by set_fmt in bridge drivers
Jul  9 19:54:56 Tower kernel: 	5eab4983777ba913efb42dd0f177b0dcdbd4f3d9 [media] v4l2: replace try_mbus_fmt by set_fmt in bridge drivers
Jul  9 19:54:56 Tower kernel: 	experimental: ada40c8874d5e4f8d7e9bd4518b8eff438822dc6 Added tag 2015-05-09 for changeset 66c6e6cc0e1b
Jul  9 19:54:56 Tower kernel: 	v4l-dvb-saa716x: d7e98fc592305a600909003da2b7cc4338242511 saa716x_ff: Do not return on command ready timeout
Jul  9 19:54:56 Tower kernel: Digital Devices PCIE bridge driver 0.9.18, Copyright (C) 2010-15 Digital Devices GmbH
Jul  9 19:54:56 Tower kernel: DDBridge driver detected: Digital Devices DVBCT V6.1 DVB adapter
Jul  9 19:54:56 Tower kernel: DDBridge: HW 00010009 REGMAP 00010004
Jul  9 19:54:56 Tower kernel: DDBridge: using 1 MSI interrupt(s)

Jul  9 19:54:56 Tower kernel: 0 netstream channels
Jul  9 19:54:56 Tower kernel: DVB: registering new adapter (DDBridge)
Jul  9 19:54:56 Tower kernel: scsi host1: ahci
Jul  9 19:54:56 Tower kernel: scsi host4: ahci
Jul  9 19:54:56 Tower kernel: DVB: registering new adapter (DDBridge)

And the dvb folder with the 2 adapters in it showed up also.. Installang TVheadend right now and will report back 8)

 

Edit:

And it is up and running  8)  Thanks for your help CHBMB !

Link to post

Ok looks good so far  8)

 

Jul  9 19:54:56 Tower kernel: Latest git patches (needed if you report a bug to linux-media@vger.kernel.org):
Jul  9 19:54:56 Tower kernel: 	1555f3bf5cc172e7d23c2b8db10d656d15bec13e [media] saa7164: fix compiler warning
Jul  9 19:54:56 Tower kernel: 	ebf984bb151e9952cccd060d3aba0b4d30a87e81 [media] v4l2: replace s_mbus_fmt by set_fmt in bridge drivers
Jul  9 19:54:56 Tower kernel: 	5eab4983777ba913efb42dd0f177b0dcdbd4f3d9 [media] v4l2: replace try_mbus_fmt by set_fmt in bridge drivers
Jul  9 19:54:56 Tower kernel: 	experimental: ada40c8874d5e4f8d7e9bd4518b8eff438822dc6 Added tag 2015-05-09 for changeset 66c6e6cc0e1b
Jul  9 19:54:56 Tower kernel: 	v4l-dvb-saa716x: d7e98fc592305a600909003da2b7cc4338242511 saa716x_ff: Do not return on command ready timeout
Jul  9 19:54:56 Tower kernel: Digital Devices PCIE bridge driver 0.9.18, Copyright (C) 2010-15 Digital Devices GmbH
Jul  9 19:54:56 Tower kernel: DDBridge driver detected: Digital Devices DVBCT V6.1 DVB adapter
Jul  9 19:54:56 Tower kernel: DDBridge: HW 00010009 REGMAP 00010004
Jul  9 19:54:56 Tower kernel: DDBridge: using 1 MSI interrupt(s)

Jul  9 19:54:56 Tower kernel: 0 netstream channels
Jul  9 19:54:56 Tower kernel: DVB: registering new adapter (DDBridge)
Jul  9 19:54:56 Tower kernel: scsi host1: ahci
Jul  9 19:54:56 Tower kernel: scsi host4: ahci
Jul  9 19:54:56 Tower kernel: DVB: registering new adapter (DDBridge)

And the dvb folder with the 2 adapters in it showed up also.. Installang TVheadend right now and will report back 8)

 

Edit:

And it is up and running  8)  Thanks for your help CHBMB !

 

Great! 

 

Is it 6.0.0 or 6.0.1?

Link to post

I don't get my DVB-C to work :(

 

It still only finds my DVB-S2 ...

I tried to make a new image with your script and everything worked. i also added cxd2099 as supposed before but doesn't work (I'm no real compile-pro :-) )

 

With your 6.0.0 image:

 

DDBridge driver detected: Digital Devices Cine S2 V6.5 DVB adapter
Port 0: Link 0, Link Port 0 (TAB 1): DUAL DVB-S2
Port 1: Link 0, Link Port 1 (TAB 2): DUAL DVB-C/T/T2
DVB: registering new adapter (DDBridge)
DVB: registering new adapter (DDBridge)
DVB: registering new adapter (DDBridge)
DVB: registering new adapter (DDBridge)
ddbridge 0000:01:00.0: DVB: registering adapter 0 frontend 0 (STV090x Multistandard)...
ddbridge 0000:01:00.0: DVB: registering adapter 1 frontend 0 (STV090x Multistandard)...
ddbridge 0000:01:00.0: DVB: registering adapter 2 frontend 0 (CXD2837 DVB-C DVB-T/T2)...
ddbridge 0000:01:00.0: DVB: registering adapter 3 frontend 0 (CXD2837 DVB-C DVB-T/T2)...

 

Great!

Could you please tell short how you added the support so i can build my 6.0.1 release with it? :)

Link to post

Difficult to explain as it was a while ago but essentially followed the instructions I posted in my initial response.  Couldn't work out how to install mercurial in Slack so used a Ubuntu VM, created the mediabuild experimental tar then copied it to my array, then did a new mediabuild, installed the tar packages then rsynced them to the new bzroot and hey presto.

Link to post

If anyone else is using the experimental mediabuild and the syslog is getting spammed with I2C Timeout errors, do the following:

 

goto /etc/modprobe.d

create ddbridge.conf

and insert the following :

 

options ddbridge msi=0

 

save file and reboot the server. The Error should be gone

Link to post
goto /etc/modprobe.d

create ddbridge.conf

and insert the following :

 

options ddbridge msi=0

 

save file and reboot the server. The Error should be gone

 

You must unpack bzroot, and create this file after that again pack, becuase after restart this file just gone !

And in some cases i know this maybe help hide errors is syslog but when you start using more than 2 tuners you will

get pixels block on screen, please test careful and let me know.

 

(i have friends wich using DD tuners and from half year we not solved this problem, problem always exist when you start using more than 2 tuners... - and using i mean play/record stream from 3 or more tuners from difrents transponders)

Link to post

Still got no Internet but I try and check this thread when I can.

 

For clarity can icho2000 confirm that all is working still and he hasn't seen the issue piotrasd has described.

 

Skeal can you also let us know if you're getting timeout errors.

 

Once I'm online at home and have the information I'll do a 6.0.1 build and if necessary add in the ddbridge.conf file.

 

 

Link to post

So far i cant see any problems. Had both tuners now running for like 7 hours with the ddbridge.conf file in place.

 

But i have only 2 tuners so i cant test what happens with 3+ tuners. And as piotrasd stated the problem only happens with 3+ tuners in action.

So iam not sure what my tests here are worth.

 

To be on the safe side, i would suggest to leave the ddbridge.conf out. I can copy it to its location with a script in the go file to keep my syslog clean :)

Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.