Jump to content
linuxserver.io

[Plugin] Linuxserver.io - Unraid DVB

1614 posts in this topic Last Reply

Recommended Posts

sure no problem i was doing this before you started :) hehe

About official TBS driver - better if you using CrazyCat build ;) because there always are latest TBS Driver official + many others ;)

https://bitbucket.org/CrazyCat/linux-tbs-drivers

 

Less work for you more  tuners support in one build ;)

 

I'm trying to keep things simple that's all. 

 

Did you ever try

 

modprobe -r ddbridge
modprobe ddbridge

 

To stop the I2C errors?  Curious to know.

 

Also heard anything from Digital Devices re the bug report as there doesn't seem to be any activity on their github repo for quite some time...

 

I will check today and let you know.

 

About opensource driver i compiled and tested on+ i can say

- yes tbs tuners works better (for me faster)

- if i have second tuner in system like DVBSky is also discovered by system and work

http://pastebin.com/y6UA2m2p

(on TBS official driver build, dvbsky driver just crash ... )

 

Share this post


Link to post

What about the CrazyCat ones? How do they get on? Might be a good compromise between official and opensource.

 

Sent from my LG-H815 using Tapatalk

 

 

Share this post


Link to post

@CHBMB i will try check latter i have busy day ....

What do you think about solution like CvM used in LibreELEC ?

please look on his source https://github.com/CvH/LibreELEC.tv/commits/dvb-drivers special init commit

 

He not creating system image with difrent modules like we, he compiling modules and make package and over script in boot

choosing which one load ... i think that solution could be better more simple etc.

 

And some starting script LimeTech could add to official image, then we dont will must even touch orginal bzimage etc.

and from webinterface user will just choose correct package of modules\

 

UPDATE:

i checked modprobe -r ddbridge, modprobe ddbridge with changing msi=x but is some problem

after unload module and load again im alwayes get in tvheadend no signal - no data - pull data timeout.

 

Share this post


Link to post

@CHBMB i will try check latter i have busy day ....

What do you think about solution like CvM used in LibreELEC ?

please look on his source https://github.com/CvH/LibreELEC.tv/commits/dvb-drivers special init commit

 

He not creating system image with difrent modules like we, he compiling modules and make package and over script in boot

choosing which one load ... i think that solution could be better more simple etc.

 

And some starting script LimeTech could add to official image, then we dont will must even touch orginal bzimage etc.

and from webinterface user will just choose correct package of modules\

 

I remember you talking about implementing this system a while ago, did you ever get around to trying it?  At the moment I don't have the time or inclination to completely redo the system for a number of reasons, firstly this system is working and the scripts make it relatively easy for me to produce the builds and upload them and everything is relatively stable.  I've got a fair bit on my plate at the moment both at work, home and support for ls.io.  Not saying it'll never happen but it's going to be a while before I could sit down and spend a considerable amount of time on this.  The other reason I'm reluctant to change things up is the difficulty is getting a decent amount of testers for these things.  Generally if it works, most users don't want to (understandably) mess around with their system.

 

Having spoken to LT a few times about this and they have looked at DVB in the past and decided it's not something they can really support (for some pretty sensible reasons) I'm not convinced you'd get them to agree to implementing anything at boot to support an "Unofficial" addon.

 

 

UPDATE:

i checked modprobe -r ddbridge, modprobe ddbridge with changing msi=x but is some problem

after unload module and load again im alwayes get in tvheadend no signal - no data - pull data timeout.

 

That's disappointing, as it was working for @icho2000 here.  Not sure how best to tackle this problem, going to ponder it for a while and see who else reports issues...

Share this post


Link to post

@CHBMB i will try check latter i have busy day ....

What do you think about solution like CvM used in LibreELEC ?

please look on his source https://github.com/CvH/LibreELEC.tv/commits/dvb-drivers special init commit

 

He not creating system image with difrent modules like we, he compiling modules and make package and over script in boot

choosing which one load ... i think that solution could be better more simple etc.

 

And some starting script LimeTech could add to official image, then we dont will must even touch orginal bzimage etc.

and from webinterface user will just choose correct package of modules\

 

I remember you talking about implementing this system a while ago, did you ever get around to trying it?  At the moment I don't have the time or inclination to completely redo the system for a number of reasons, firstly this system is working and the scripts make it relatively easy for me to produce the builds and upload them and everything is relatively stable.  I've got a fair bit on my plate at the moment both at work, home and support for ls.io.  Not saying it'll never happen but it's going to be a while before I could sit down and spend a considerable amount of time on this.  The other reason I'm reluctant to change things up is the difficulty is getting a decent amount of testers for these things.  Generally if it works, most users don't want to (understandably) mess around with their system.

 

Having spoken to LT a few times about this and they have looked at DVB in the past and decided it's not something they can really support (for some pretty sensible reasons) I'm not convinced you'd get them to agree to implementing anything at boot to support an "Unofficial" addon.

 

yes in way to build dvb support inside system image, but that solution keep them out from support.

They only must add script which will call to load extrenal modules on boot (still bzroot will untouched by us)

and even if they upgrade unraid system without kernel bump we will able to use this same package of modules

(now each bump of unraid system you must recompile whole image) so thats less work.

 

thats the part of code

 

    # mount correct kernel modules dir
    MODULES_DIR="$(cat /sysroot/storage/downloads/dvb-drivers.txt 2>/dev/null)"
    if [ -n "$MODULES_DIR" ]; then
      MODULES_DIR="/sysroot/lib/modules/$MODULES_DIR"
      if [ -d "$MODULES_DIR" ]; then
        mount -o loop,ro "$MODULES_DIR" /sysroot/lib/modules/$(uname -r)
      fi
    fi
  }

 

in file dvb-drivers.txt is name which package of modules choose (it could be located on /boot/config/...

and this call triger to load external modules we can add in rc.modules ...

 

 

ping @limetech @jonp

Share this post


Link to post

piotrasd you were talking about this well over a year ago I remember. 

 

Did you ever actually get around to testing it in any way?

 

 

 

Sent from my LG-H815 using Tapatalk

 

 

Share this post


Link to post

im compiled yesterday own image of LE for friend with DVB tuner with that changes, and working without problem

addopting this to unraid is no problem. I sended PM to Limetech - let we wait what they answer

Share this post


Link to post

im compiled yesterday own image of LE for friend with DVB tuner with that changes, and working without problem

addopting this to unraid is no problem. I sended PM to Limetech - let we wait what they answer

Fancy putting something up on github for me to take a look at? 

 

Like I said I'm a bit busy with, well, life at the moment, but if you want to do some work on it I'll gladly have a play. 

Share this post


Link to post

@CHBMB little sorry how you this received :)

yes no problem im already looked in rc.modules in unraid how this addopt and maybe on days when i also wil have time i make some test build ;) im not expect any move from your side, your script are great, with them i maked new image for unraid in 10min.

 

And I appreciate what are you doing, for me DVB tuner user i just download ready image :) and i dont care about anything :)

 

That was idea for future, becuase how long im using unraid from 2011 i remember that always was problem and also like you i wanted force support, but im also fully understand LimeTech (is hard to keep support for dvbtuners ... ) better if they just focus on unRAID core. So thats could be some compromise and less for work. Im also agree with you, your solution with plugin is 100% good and enough ;)

Share this post


Link to post

Don't be sorry, but like I say, I don't have a great deal of free time either, which I guess is the reason you haven't managed to do this either.  If you want to work on something then I'm open to collaboration is what I was saying...

 

Sent from my LG-H815 using Tapatalk

 

 

Share this post


Link to post

So, piotrasd has come up with a solution to the ddbridge.conf issue for Digital Devices users.  Very grateful for the work and the testing he's done, enabling the Digital Devices builds to continue.  :)

 

Updated builds for V6.19 Digital Devices Github and Experimental and V6.2 RC2 Digital Devices Github are uploaded so please redownload, apply the changes detailed here, and then reboot.

Share this post


Link to post

V6.2 RC3 TBS DVB-S/T, DVB-C, CrazyCat TBS DVB-S/T, LibreELEC, Digital Devices Github (Patched) Builds uploaded

Share this post


Link to post

RC4 uploaded yesterday.  Digital Devices have released a new build, so I've used that, if it still causes problems then post here and I'll revert to my patched version.  They didn't merge my PR but they may have fixed the issues anyway.

 

Sent from my LG-H815 using Tapatalk

 

 

Share this post


Link to post

Hi,

 

My update to rc4 hasn't worked, using LibreELEC with a USB dual tuner that uses the "Afatech AF9013" driver. It was working fine with rc3.

 

This is what I am seeing in the logs;

 

Aug 22 10:30:13 kernel: usb 4-1: dvb_usb_v2: found a 'Afatech AF9015 reference design' in warm state
Aug 22 10:30:13 kernel: usb 4-1: dvb_usb_v2: will pass the complete MPEG2 transport stream to the software demuxer
Aug 22 10:30:13 kernel: DVB: registering new adapter (Afatech AF9015 reference design)
Aug 22 10:30:13 kernel: i2c i2c-0: af9013: firmware version 5.24.0.0
Aug 22 10:30:13 kernel: usb 4-1: DVB: registering adapter 0 frontend 0 (Afatech AF9013)...
Aug 22 10:30:13 kernel: mxl5007t 0-00c0: creating new instance
Aug 22 10:30:13 kernel: usb 4-1: dvb_usb_af9015: command failed=2
Aug 22 10:30:13 kernel: mxl5007t_read_reg: 505: failed!
Aug 22 10:30:13 kernel: mxl5007t_get_chip_id: error -121 on line 818
Aug 22 10:30:13 kernel: mxl5007t_get_chip_id: unable to identify device @ 0-00c0
Aug 22 10:30:13 kernel: mxl5007t_attach: error -121 on line 891
Aug 22 10:30:13 kernel: usbcore: registered new interface driver dvb_usb_af9015

 

Any ideas?

 

Thanks,

Wob

Share this post


Link to post

Weird as nothing in the LE package has changed other than the kernel itself.  I'll have a think about this....

 

Sent from my LG-H815 using Tapatalk

 

 

Share this post


Link to post

Weird as nothing in the LE package has changed other than the kernel itself.  I'll have a think about this....

 

Sent from my LG-H815 using Tapatalk

 

When I can get near the box, I did the update remotely, I'll pull the usb tuner out and put it back in. i have rebooted a couple of times, but this could still help.

 

Thanks,

Wob

Share this post


Link to post

No Joy with remove\reinstall of usb device.

 

Let me know if I can supply anything else.

 

This is what I am seeing in the dvb plug in.

 

unRAID Version: 6.2.0-rc4

DVB Version: LibreELEC

Driver Version: 1.0.0

DVB Kernel: Detected

DVB Adapter Drivers: Not Detected

DVB Adapter 0: Afatech AF9013

Share this post


Link to post

I'll take a look when I get home tonight. Maybe I messed something up...

 

Sent from my LG-H815 using Tapatalk

 

 

Share this post


Link to post

No Joy with remove\reinstall of usb device.

 

Let me know if I can supply anything else.

 

This is what I am seeing in the dvb plug in.

 

unRAID Version: 6.2.0-rc4

DVB Version: LibreELEC

Driver Version: 1.0.0

DVB Kernel: Detected

DVB Adapter Drivers: Not Detected

DVB Adapter 0: Afatech AF9013

 

Looks like the firmware is missing, maybe something went wrong (aka I broke the script)  I've pushed another build to our server, would you mind testing and let me know.  Sorry for the hassle.

Share this post


Link to post

No hassle at all, I appreciate all your hard work.

 

Happy to test, will I see an updated DVB Plugin or do I just repull the LibreELEC build inside the plugin?

 

Thanks,

Wob

Share this post


Link to post

No hassle at all, I appreciate all your hard work.

 

Happy to test, will I see an updated DVB Plugin or do I just repull the LibreELEC build inside the plugin?

 

Thanks,

Wob

 

Just repull the LibreELEC build from within the plugin.

Share this post


Link to post

No hassle at all, I appreciate all your hard work.

 

Happy to test, will I see an updated DVB Plugin or do I just repull the LibreELEC build inside the plugin?

 

Thanks,

Wob

 

Just repull the LibreELEC build from within the plugin.

I did a repull and reboot but same result. Any other ideas? Can I post any logs to help?

 

Sent from my SM-G900I using Tapatalk

 

 

Share this post


Link to post

Only other thing is I whether I missed the kernel module for your card when I was making the .config so I've recompiled from scratch.  I've uploaded a new build again.  Fingers crossed.

 

Definitely included it this time.  ;)

 

Share this post


Link to post

Still no luck, here are some snippits from my syslog. Can I run any commands to help diagnose the problem?

 

Aug 24 09:23:41 TheBox kernel: usb 4-1: new high-speed USB device number 2 using xhci_hcd
Aug 24 09:23:41 TheBox kernel: Afatech DVB-T 2: Fixing fullspeed to highspeed interval: 10 -> 7
Aug 24 09:23:41 TheBox kernel: input: Afatech DVB-T 2 as /devices/pci0000:00/0000:00:1c.6/0000:04:00.0/usb4/4-1/4-1:1.1/0003:15A4:9016.0001/input/input5
Aug 24 09:23:41 TheBox kernel: hid-generic 0003:15A4:9016.0001: input,hidraw0: USB HID v1.01 Keyboard [Afatech DVB-T 2] on usb-0000:04:00.0-1/input1

Aug 24 09:23:41 TheBox kernel: usb 4-1: dvb_usb_v2: found a 'Afatech AF9015 reference design' in cold state
Aug 24 09:23:41 TheBox kernel: usb 4-1: dvb_usb_v2: downloading firmware from file 'dvb-usb-af9015.fw'

Aug 24 09:23:41 TheBox kernel: usb 4-1: dvb_usb_v2: found a 'Afatech AF9015 reference design' in warm state
Aug 24 09:23:41 TheBox kernel: ipmi_si IPI0001:00: Found new BMC (man_id: 0x00000b, prod_id: 0x2000, dev_id: 0x13)
Aug 24 09:23:41 TheBox kernel: ipmi_si IPI0001:00: IPMI kcs interface initialized
Aug 24 09:23:41 TheBox kernel: usb 4-1: dvb_usb_v2: will pass the complete MPEG2 transport stream to the software demuxer
Aug 24 09:23:41 TheBox kernel: DVB: registering new adapter (Afatech AF9015 reference design)
Aug 24 09:23:41 TheBox kernel: i2c i2c-0: af9013: firmware version 5.24.0.0
Aug 24 09:23:41 TheBox kernel: usb 4-1: DVB: registering adapter 0 frontend 0 (Afatech AF9013)...
Aug 24 09:23:41 TheBox kernel: mxl5007t 0-00c0: creating new instance
Aug 24 09:23:41 TheBox kernel: usb 4-1: dvb_usb_af9015: command failed=2
Aug 24 09:23:41 TheBox kernel: mxl5007t_read_reg: 505: failed!
Aug 24 09:23:41 TheBox kernel: mxl5007t_get_chip_id: error -121 on line 818
Aug 24 09:23:41 TheBox kernel: mxl5007t_get_chip_id: unable to identify device @ 0-00c0
Aug 24 09:23:41 TheBox kernel: mxl5007t_attach: error -121 on line 891
Aug 24 09:23:41 TheBox kernel: usbcore: registered new interface driver dvb_usb_af9015

Aug 24 09:24:02 TheBox root: plugin: installing: /boot/config/plugins/UnraidDVB.plg
Aug 24 09:24:02 TheBox root: plugin: running: anonymous
Aug 24 09:24:02 TheBox root:
Aug 24 09:24:02 TheBox root:
Aug 24 09:24:02 TheBox root:
Aug 24 09:24:02 TheBox root:
Aug 24 09:24:02 TheBox root: plugin: running: anonymous
Aug 24 09:24:02 TheBox root: plugin: skipping: /boot/config/plugins/UnraidDVB/UnraidDVB-2016.08.18.txz already exists
Aug 24 09:24:02 TheBox root: plugin: running: /boot/config/plugins/UnraidDVB/UnraidDVB-2016.08.18.txz
Aug 24 09:24:02 TheBox root:
Aug 24 09:24:02 TheBox root: +==============================================================================
Aug 24 09:24:02 TheBox root: | Installing new package /boot/config/plugins/UnraidDVB/UnraidDVB-2016.08.18.txz
Aug 24 09:24:02 TheBox root: +==============================================================================
Aug 24 09:24:02 TheBox root:
Aug 24 09:24:02 TheBox root: Verifying package UnraidDVB-2016.08.18.txz.
Aug 24 09:24:02 TheBox root: Installing package UnraidDVB-2016.08.18.txz:
Aug 24 09:24:02 TheBox root: PACKAGE DESCRIPTION:
Aug 24 09:24:02 TheBox root: Package UnraidDVB-2016.08.18.txz installed.
Aug 24 09:24:02 TheBox root:
Aug 24 09:24:02 TheBox root:
Aug 24 09:24:02 TheBox root: plugin: running: anonymous
Aug 24 09:24:02 TheBox root: V6.2 compatible
Aug 24 09:24:02 TheBox root:
Aug 24 09:24:02 TheBox root: ----------------------------------------------------
Aug 24 09:24:02 TheBox root:  UnraidDVB has been installed.
Aug 24 09:24:02 TheBox root:  CHBMB/Squid
Aug 24 09:24:02 TheBox root:  Version: 2016.08.18
Aug 24 09:24:02 TheBox root: ----------------------------------------------------
Aug 24 09:24:02 TheBox root:
Aug 24 09:24:02 TheBox root: plugin: installed

Aug 24 09:24:55 TheBox root: tvheadend: Error response from daemon: error gathering device information while adding custom device "/dev/dvb": lstat /dev/dvb: no such file or directory Error: failed to start containers: tvheadend

 

Edit:

 

Also just noting I can see the firmware file located /lib/firmware/dvb-usb-af9015.fw

 

And I have the following related files.

 

/sys/bus/usb/drivers/dvb_usb_af9015

/sys/module/rc_core/holders/dvb_usb_af9015

/sys/module/dvb_usb_v2/holders/dvb_usb_af9015

/sys/module/dvb_usb_af9015

/sys/module/dvb_usb_af9015/drivers/usb:dvb_usb_af9015

/lib/modules/4.4.18-unRAID/kernel/drivers/media/usb/dvb-usb-v2/dvb-usb-af9015.ko.gz

 

Share this post


Link to post

Still no luck, here are some snippits from my syslog. Can I run any commands to help diagnose the problem?

 

Aug 24 09:23:41 TheBox kernel: usb 4-1: new high-speed USB device number 2 using xhci_hcd
Aug 24 09:23:41 TheBox kernel: Afatech DVB-T 2: Fixing fullspeed to highspeed interval: 10 -> 7
Aug 24 09:23:41 TheBox kernel: input: Afatech DVB-T 2 as /devices/pci0000:00/0000:00:1c.6/0000:04:00.0/usb4/4-1/4-1:1.1/0003:15A4:9016.0001/input/input5
Aug 24 09:23:41 TheBox kernel: hid-generic 0003:15A4:9016.0001: input,hidraw0: USB HID v1.01 Keyboard [Afatech DVB-T 2] on usb-0000:04:00.0-1/input1

Aug 24 09:23:41 TheBox kernel: usb 4-1: dvb_usb_v2: found a 'Afatech AF9015 reference design' in cold state
Aug 24 09:23:41 TheBox kernel: usb 4-1: dvb_usb_v2: downloading firmware from file 'dvb-usb-af9015.fw'

Aug 24 09:23:41 TheBox kernel: usb 4-1: dvb_usb_v2: found a 'Afatech AF9015 reference design' in warm state
Aug 24 09:23:41 TheBox kernel: ipmi_si IPI0001:00: Found new BMC (man_id: 0x00000b, prod_id: 0x2000, dev_id: 0x13)
Aug 24 09:23:41 TheBox kernel: ipmi_si IPI0001:00: IPMI kcs interface initialized
Aug 24 09:23:41 TheBox kernel: usb 4-1: dvb_usb_v2: will pass the complete MPEG2 transport stream to the software demuxer
Aug 24 09:23:41 TheBox kernel: DVB: registering new adapter (Afatech AF9015 reference design)
Aug 24 09:23:41 TheBox kernel: i2c i2c-0: af9013: firmware version 5.24.0.0
Aug 24 09:23:41 TheBox kernel: usb 4-1: DVB: registering adapter 0 frontend 0 (Afatech AF9013)...
Aug 24 09:23:41 TheBox kernel: mxl5007t 0-00c0: creating new instance
Aug 24 09:23:41 TheBox kernel: usb 4-1: dvb_usb_af9015: command failed=2
Aug 24 09:23:41 TheBox kernel: mxl5007t_read_reg: 505: failed!
Aug 24 09:23:41 TheBox kernel: mxl5007t_get_chip_id: error -121 on line 818
Aug 24 09:23:41 TheBox kernel: mxl5007t_get_chip_id: unable to identify device @ 0-00c0
Aug 24 09:23:41 TheBox kernel: mxl5007t_attach: error -121 on line 891
Aug 24 09:23:41 TheBox kernel: usbcore: registered new interface driver dvb_usb_af9015

Aug 24 09:24:02 TheBox root: plugin: installing: /boot/config/plugins/UnraidDVB.plg
Aug 24 09:24:02 TheBox root: plugin: running: anonymous
Aug 24 09:24:02 TheBox root:
Aug 24 09:24:02 TheBox root:
Aug 24 09:24:02 TheBox root:
Aug 24 09:24:02 TheBox root:
Aug 24 09:24:02 TheBox root: plugin: running: anonymous
Aug 24 09:24:02 TheBox root: plugin: skipping: /boot/config/plugins/UnraidDVB/UnraidDVB-2016.08.18.txz already exists
Aug 24 09:24:02 TheBox root: plugin: running: /boot/config/plugins/UnraidDVB/UnraidDVB-2016.08.18.txz
Aug 24 09:24:02 TheBox root:
Aug 24 09:24:02 TheBox root: +==============================================================================
Aug 24 09:24:02 TheBox root: | Installing new package /boot/config/plugins/UnraidDVB/UnraidDVB-2016.08.18.txz
Aug 24 09:24:02 TheBox root: +==============================================================================
Aug 24 09:24:02 TheBox root:
Aug 24 09:24:02 TheBox root: Verifying package UnraidDVB-2016.08.18.txz.
Aug 24 09:24:02 TheBox root: Installing package UnraidDVB-2016.08.18.txz:
Aug 24 09:24:02 TheBox root: PACKAGE DESCRIPTION:
Aug 24 09:24:02 TheBox root: Package UnraidDVB-2016.08.18.txz installed.
Aug 24 09:24:02 TheBox root:
Aug 24 09:24:02 TheBox root:
Aug 24 09:24:02 TheBox root: plugin: running: anonymous
Aug 24 09:24:02 TheBox root: V6.2 compatible
Aug 24 09:24:02 TheBox root:
Aug 24 09:24:02 TheBox root: ----------------------------------------------------
Aug 24 09:24:02 TheBox root:  UnraidDVB has been installed.
Aug 24 09:24:02 TheBox root:  CHBMB/Squid
Aug 24 09:24:02 TheBox root:  Version: 2016.08.18
Aug 24 09:24:02 TheBox root: ----------------------------------------------------
Aug 24 09:24:02 TheBox root:
Aug 24 09:24:02 TheBox root: plugin: installed

Aug 24 09:24:55 TheBox root: tvheadend: Error response from daemon: error gathering device information while adding custom device "/dev/dvb": lstat /dev/dvb: no such file or directory Error: failed to start containers: tvheadend

 

That syslog is quite revealing, seems there have been problems along these lines before with this tuner and kernel upgrades.  At the moment I can only assume that something in the Linux kernel has broken this.  Give me a few days and I'll do some investigating, can't promise I can fix this one to be honest if it is a kernel issue. 

 

I've pored over my scripts for creating these builds and can't see anything amiss and I've reviewed the logs, but I'll try and do one manually to make sure when I get a couple of hours free.

Share this post


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.