Jump to content
linuxserver.io

[Plugin] Linuxserver.io - Unraid DVB

1675 posts in this topic Last Reply

Recommended Posts

I was wondering if I can get some help and hoping this is the right place to post. I am having trouble getting my plex docker container to recognize my tuner. I am new to unraid but not new to linux, docker, etc. I have unraid 6.7.2, I am using binhex's plex container, I have plex pass, I have Community Apps and have downloaded Unraid DVB. I have tried both LibreELEC and TBS CrazyCat 6.7.2. I am using This Tuner. Plex will not detect the tuner.

Here is so more info from the community app unraid DVB:

unRAID Version:6.7.2

Linux Kernel Version:4.19.56

DVB Version:LibreELEC

Driver Version:1.3.1

DVB Kernel:Detected

DVB Adapter Drivers:Detected

DVB Adapter 0:LG Electronics LGDT3306A VSB/QAM Frontend

DVB Adapter 1:LG Electronics LGDT3306A VSB/QAM Frontend

Lastly, I stood up TvHeadEnd's docker and was able to find 40 or so tv channels through it. What am I missing?

Share this post


Link to post
3 hours ago, xTxHiLLx said:

I was wondering if I can get some help and hoping this is the right place to post. I am having trouble getting my plex docker container to recognize my tuner. I am new to unraid but not new to linux, docker, etc. I have unraid 6.7.2, I am using binhex's plex container, I have plex pass, I have Community Apps and have downloaded Unraid DVB. I have tried both LibreELEC and TBS CrazyCat 6.7.2. I am using This Tuner. Plex will not detect the tuner.

Here is so more info from the community app unraid DVB:

unRAID Version:6.7.2

Linux Kernel Version:4.19.56

DVB Version:LibreELEC

Driver Version:1.3.1

DVB Kernel:Detected

DVB Adapter Drivers:Detected

DVB Adapter 0:LG Electronics LGDT3306A VSB/QAM Frontend

DVB Adapter 1:LG Electronics LGDT3306A VSB/QAM Frontend

Lastly, I stood up TvHeadEnd's docker and was able to find 40 or so tv channels through it. What am I missing?

I guess you added the /dev/dvb device to the plex container?

Also remember that plex doesn't support all dvb cards. You might be lucky that it works even though it is not supported, but there is a different way of adding the card. It's all in the plex documentation.

 

Have you tested if it works in our plex container?

Share this post


Link to post
6 hours ago, saarg said:

I guess you added the /dev/dvb device to the plex container?

Also remember that plex doesn't support all dvb cards. You might be lucky that it works even though it is not supported, but there is a different way of adding the card. It's all in the plex documentation.

 

Have you tested if it works in our plex container?

After I posted, It hit me that I didn't add "--device=/dev/dvb" to extra parameters in the plex container like I did in the TvHeadEnd. It picked up afterward fine. Thanks for the reply. 

Share this post


Link to post
10 minutes ago, xTxHiLLx said:

After I posted, It hit me that I didn't add "--device=/dev/dvb" to extra parameters in the plex container like I did in the TvHeadEnd. It picked up afterward fine. Thanks for the reply. 

Good thing it was something simple 🙂

Share this post


Link to post

v6.8.0rc3 uploaded.  Still no TBS Crazy Cat....

Share this post


Link to post

I was wondering if anybody else has the problem that the plugin settings get stuck while "checking available builds" sometimes or throw an error message of not being able to reach the repository (see screenshot)...

 

Any ideas?

 

Unbenannt.JPG

Share this post


Link to post
I was wondering if anybody else has the problem that the plugin settings get stuck while "checking available builds" sometimes or throw an error message of not being able to reach the repository (see screenshot)...
 
Any ideas?
 
Unbenannt.thumb.JPG.124c49156f4bcb3ae9ff798597691519.JPG
Yeah, Digital Ocean has an issue at the minute with it's spaces, unfortunately that's where the builds are.

Sent from my Mi A1 using Tapatalk

Share this post


Link to post
1 minute ago, CHBMB said:

Yeah, Digital Ocean has an issue at the minute with it's spaces, unfortunately that's where the builds are.

Sent from my Mi A1 using Tapatalk
 

Ah, that explains it. Thanks for getting back on this so quickly! Guess I'll just have to sit tight and wait it out... :D

Share this post


Link to post
Oct 20 04:36:30 Tower kernel: 0x1c0002f0 [ write sol eol count=752 ]
Oct 20 04:36:30 Tower kernel: cx23885: cx23885[1]:   risc1:
Oct 20 04:36:30 Tower kernel: 0xfc7d9d60 [ INVALID sol eol 22 21 20 19 18 cnt0 resync 12 count=3424 ]
Oct 20 04:36:30 Tower kernel: cx23885: cx23885[1]:   risc2:
Oct 20 04:36:30 Tower kernel: 0x00000000 [ INVALID count=0 ]
Oct 20 04:36:30 Tower kernel: cx23885: cx23885[1]:   risc3:
Oct 20 04:36:30 Tower kernel: 0x1c0002f0 [ write sol eol count=752 ]
Oct 20 04:36:30 Tower kernel: cx23885: cx23885[1]:   (0x00010670) iq 0:
Oct 20 04:36:30 Tower kernel: 0x1c0002f0 [ write sol eol count=752 ]
Oct 20 04:36:30 Tower kernel: cx23885: cx23885[1]:   iq 1: 0xfc7da340 [ arg #1 ]
Oct 20 04:36:30 Tower kernel: cx23885: cx23885[1]:   iq 2: 0x00000000 [ arg #2 ]
Oct 20 04:36:30 Tower kernel: cx23885: cx23885[1]:   (0x0001067c) iq 3:
Oct 20 04:36:30 Tower kernel: 0x1c0002f0 [ write sol eol count=752 ]
Oct 20 04:36:30 Tower kernel: cx23885: cx23885[1]:   iq 4: 0xfc7da630 [ arg #1 ]
Oct 20 04:36:30 Tower kernel: cx23885: cx23885[1]:   iq 5: 0x00000000 [ arg #2 ]
Oct 20 04:36:30 Tower kernel: cx23885: cx23885[1]:   (0x00010688) iq 6:
Oct 20 04:36:30 Tower kernel: 0x1c0002f0 [ write sol eol count=752 ]
Oct 20 04:36:30 Tower kernel: cx23885: cx23885[1]:   iq 7: 0xfc7da050 [ arg #1 ]
Oct 20 04:36:30 Tower kernel: cx23885: cx23885[1]:   iq 8: 0x00000000 [ arg #2 ]
Oct 20 04:36:30 Tower kernel: cx23885: cx23885[1]:   (0x00010694) iq 9:
Oct 20 04:36:30 Tower kernel: 0x00000000 [ INVALID count=0 ]
Oct 20 04:36:30 Tower kernel: cx23885: cx23885[1]:   (0x00010698) iq a:
Oct 20 04:36:30 Tower kernel: 0x1c0002f0 [ write sol eol count=752 ]
Oct 20 04:36:30 Tower kernel: cx23885: cx23885[1]:   iq b: 0xfc7d9490 [ arg #1 ]
Oct 20 04:36:30 Tower kernel: cx23885: cx23885[1]:   iq c: 0x00000000 [ arg #2 ]
Oct 20 04:36:30 Tower kernel: cx23885: cx23885[1]:   (0x000106a4) iq d:
Oct 20 04:36:30 Tower kernel: 0x1c0002f0 [ write sol eol count=752 ]
Oct 20 04:36:30 Tower kernel: cx23885: cx23885[1]:   iq e: 0xfc7d9780 [ arg #1 ]
Oct 20 04:36:30 Tower kernel: cx23885: cx23885[1]:   iq f: 0x00000000 [ arg #2 ]
Oct 20 04:36:30 Tower kernel: cx23885: cx23885[1]: fifo: 0x00006000 -> 0x7000
Oct 20 04:36:30 Tower kernel: cx23885: cx23885[1]: ctrl: 0x00010670 -> 0x106d0
Oct 20 04:36:30 Tower kernel: cx23885: cx23885[1]:   ptr1_reg: 0x00006780
Oct 20 04:36:30 Tower kernel: cx23885: cx23885[1]:   ptr2_reg: 0x000108f8
Oct 20 04:36:30 Tower kernel: cx23885: cx23885[1]:   cnt1_reg: 0x0000001a
Oct 20 04:36:30 Tower kernel: cx23885: cx23885[1]:   cnt2_reg: 0x00000005

I've been having a lot of stability issues lately with my Hauppauge WinTV-QuadHD running on unRAID. Cables are all perfect (getting great SNR/SignalStrength), but it seems like something is still getting in the way on the hardware level (while all other boxes in the house have no trouble using the signal). Scanning for channels/services runs smoothly, all MUXes are reliably found. The problems start when tuning in to channels themselves, sometimes it works instantly, but sometimes I get something along the lines of "2019-10-20 04:36:29.720 linuxdvb: Silicon Labs Si2168 #3 : DVB-C #0 - poll TIMEOUT" in the tvheadend logs... When I go look in /var/log/syslog, I get messages like the ones attached, usually starting with "kernel: cx23885: cx23885[1]: mpeg risc op code error" and a lot of debug details following afterwards.

 

Any ideas? 

Edited by drdebian

Share this post


Link to post
4 hours ago, drdebian said:

Oct 20 04:36:30 Tower kernel: 0x1c0002f0 [ write sol eol count=752 ]
Oct 20 04:36:30 Tower kernel: cx23885: cx23885[1]:   risc1:
Oct 20 04:36:30 Tower kernel: 0xfc7d9d60 [ INVALID sol eol 22 21 20 19 18 cnt0 resync 12 count=3424 ]
Oct 20 04:36:30 Tower kernel: cx23885: cx23885[1]:   risc2:
Oct 20 04:36:30 Tower kernel: 0x00000000 [ INVALID count=0 ]
Oct 20 04:36:30 Tower kernel: cx23885: cx23885[1]:   risc3:
Oct 20 04:36:30 Tower kernel: 0x1c0002f0 [ write sol eol count=752 ]
Oct 20 04:36:30 Tower kernel: cx23885: cx23885[1]:   (0x00010670) iq 0:
Oct 20 04:36:30 Tower kernel: 0x1c0002f0 [ write sol eol count=752 ]
Oct 20 04:36:30 Tower kernel: cx23885: cx23885[1]:   iq 1: 0xfc7da340 [ arg #1 ]
Oct 20 04:36:30 Tower kernel: cx23885: cx23885[1]:   iq 2: 0x00000000 [ arg #2 ]
Oct 20 04:36:30 Tower kernel: cx23885: cx23885[1]:   (0x0001067c) iq 3:
Oct 20 04:36:30 Tower kernel: 0x1c0002f0 [ write sol eol count=752 ]
Oct 20 04:36:30 Tower kernel: cx23885: cx23885[1]:   iq 4: 0xfc7da630 [ arg #1 ]
Oct 20 04:36:30 Tower kernel: cx23885: cx23885[1]:   iq 5: 0x00000000 [ arg #2 ]
Oct 20 04:36:30 Tower kernel: cx23885: cx23885[1]:   (0x00010688) iq 6:
Oct 20 04:36:30 Tower kernel: 0x1c0002f0 [ write sol eol count=752 ]
Oct 20 04:36:30 Tower kernel: cx23885: cx23885[1]:   iq 7: 0xfc7da050 [ arg #1 ]
Oct 20 04:36:30 Tower kernel: cx23885: cx23885[1]:   iq 8: 0x00000000 [ arg #2 ]
Oct 20 04:36:30 Tower kernel: cx23885: cx23885[1]:   (0x00010694) iq 9:
Oct 20 04:36:30 Tower kernel: 0x00000000 [ INVALID count=0 ]
Oct 20 04:36:30 Tower kernel: cx23885: cx23885[1]:   (0x00010698) iq a:
Oct 20 04:36:30 Tower kernel: 0x1c0002f0 [ write sol eol count=752 ]
Oct 20 04:36:30 Tower kernel: cx23885: cx23885[1]:   iq b: 0xfc7d9490 [ arg #1 ]
Oct 20 04:36:30 Tower kernel: cx23885: cx23885[1]:   iq c: 0x00000000 [ arg #2 ]
Oct 20 04:36:30 Tower kernel: cx23885: cx23885[1]:   (0x000106a4) iq d:
Oct 20 04:36:30 Tower kernel: 0x1c0002f0 [ write sol eol count=752 ]
Oct 20 04:36:30 Tower kernel: cx23885: cx23885[1]:   iq e: 0xfc7d9780 [ arg #1 ]
Oct 20 04:36:30 Tower kernel: cx23885: cx23885[1]:   iq f: 0x00000000 [ arg #2 ]
Oct 20 04:36:30 Tower kernel: cx23885: cx23885[1]: fifo: 0x00006000 -> 0x7000
Oct 20 04:36:30 Tower kernel: cx23885: cx23885[1]: ctrl: 0x00010670 -> 0x106d0
Oct 20 04:36:30 Tower kernel: cx23885: cx23885[1]:   ptr1_reg: 0x00006780
Oct 20 04:36:30 Tower kernel: cx23885: cx23885[1]:   ptr2_reg: 0x000108f8
Oct 20 04:36:30 Tower kernel: cx23885: cx23885[1]:   cnt1_reg: 0x0000001a
Oct 20 04:36:30 Tower kernel: cx23885: cx23885[1]:   cnt2_reg: 0x00000005

I've been having a lot of stability issues lately with my Hauppauge WinTV-QuadHD running on unRAID. Cables are all perfect (getting great SNR/SignalStrength), but it seems like something is still getting in the way on the hardware level (while all other boxes in the house have no trouble using the signal). Scanning for channels/services runs smoothly, all MUXes are reliably found. The problems start when tuning in to channels themselves, sometimes it works instantly, but sometimes I get something along the lines of "2019-10-20 04:36:29.720 linuxdvb: Silicon Labs Si2168 #3 : DVB-C #0 - poll TIMEOUT" in the tvheadend logs... When I go look in /var/log/syslog, I get messages like the ones attached, usually starting with "kernel: cx23885: cx23885[1]: mpeg risc op code error" and a lot of debug details following afterwards.

 

Any ideas? 

Yes, i have the same tunner. The only Drivers that works for me is Crazy Cat.

 

I use the option (Force Old state) in tunners for try fix this issue. It's not 100% fix, But i think it helps.

 

That issue comes from TVH and i reported it support area.

 

They think that are some process loading and force tunner to get pull time out.

 

If you find some info share with us in unraid TVH topic, but not reply in this topic because is only related for DVB recognized process, and it's not our problem.

 

Best regards

Share this post


Link to post
5 hours ago, psycmos said:

Yes, i have the same tunner. The only Drivers that works for me is Crazy Cat.

 

I use the option (Force Old state) in tunners for try fix this issue. It's not 100% fix, But i think it helps.

 

That issue comes from TVH and i reported it support area.

 

They think that are some process loading and force tunner to get pull time out.

 

If you find some info share with us in unraid TVH topic, but not reply in this topic because is only related for DVB recognized process, and it's not our problem.

 

Best regards

Thanks for the info, I'll see what I can do to sort out my issues over here. Honestly I'm quite baffled that this is a TVH issue, since these kernel module messages looked to me like there is something strange going on at the hardware level...

 

EDIT: Turns out it is indeed a TVHeadend issue... As a quick workaround I installed the minisatip Docker image and let it handle /dev/dvb instead of TVHeadend, which now sees the DVB-C tuners through a networked SAT>IP layer provided by minisatip. This way TVH can no longer meddle with my tuner card and it all works like a charm!

Edited by drdebian
additional info & workaround

Share this post


Link to post

same with TBS6909 spam logs .. 

 

[63781.026278] i2c i2c-6: freq=1758000000 delsys=2 srate=27500000

[63781.163038] i2c i2c-6: freq=1699000000 delsys=2 srate=27500000

[63781.346317] i2c i2c-6: freq=1046000000 delsys=2 srate=27500000

[63782.042559] i2c i2c-6: freq=1758000000 delsys=2 srate=27500000

[63782.154471] i2c i2c-6: freq=1699000000 delsys=2 srate=27500000

[63783.049803] i2c i2c-6: freq=1758000000 delsys=2 srate=27500000

[63783.152968] i2c i2c-6: freq=1699000000 delsys=2 srate=27500000

[63783.346306] i2c i2c-6: freq=1046000000 delsys=2 srate=27500000

[63784.025295] i2c i2c-6: freq=1758000000 delsys=2 srate=27500000

[63784.177829] i2c i2c-6: freq=1699000000 delsys=2 srate=27500000

[63785.050631] i2c i2c-6: freq=1758000000 delsys=2 srate=27500000

[63785.179101] i2c i2c-6: freq=1699000000 delsys=2 srate=27500000

[63785.340063] i2c i2c-6: freq=1046000000 delsys=2 srate=27500000

[63786.034153] i2c i2c-6: freq=1758000000 delsys=2 srate=27500000

[63786.153010] i2c i2c-6: freq=1699000000 delsys=2 srate=27500000

[63786.328672] i2c i2c-6: freq=1046000000 delsys=2 srate=27500000

[63787.049807] i2c i2c-6: freq=1758000000 delsys=2 srate=27500000

[63787.178769] i2c i2c-6: freq=1699000000 delsys=2 srate=27500000

[63787.354013] i2c i2c-6: freq=1046000000 delsys=2 srate=27500000

[63788.153448] i2c i2c-6: freq=1699000000 delsys=2 srate=27500000

[63788.347595] i2c i2c-6: freq=1046000000 delsys=2 srate=27500000

[63789.046509] i2c i2c-6: freq=1758000000 delsys=2 srate=27500000

[63789.169173] i2c i2c-6: freq=1699000000 delsys=2 srate=27500000

[63789.327346] i2c i2c-6: freq=1046000000 delsys=2 srate=27500000

[63790.025551] i2c i2c-6: freq=1758000000 delsys=2 srate=27500000

[63790.169503] i2c i2c-6: freq=1699000000 delsys=2 srate=27500000

[63790.360797] i2c i2c-6: freq=1046000000 delsys=2 srate=27500000

[63791.072394] i2c i2c-6: freq=1758000000 delsys=2 srate=27500000

[63791.327473] i2c i2c-6: freq=1046000000 delsys=2 srate=27500000

[63792.151881] i2c i2c-6: freq=1699000000 delsys=2 srate=27500000

[63792.352090] i2c i2c-6: freq=1046000000 delsys=2 srate=27500000

Share this post


Link to post
On 10/20/2019 at 11:08 AM, drdebian said:

EDIT: Turns out it is indeed a TVHeadend issue... As a quick workaround I installed the minisatip Docker image and let it handle /dev/dvb instead of TVHeadend, which now sees the DVB-C tuners through a networked SAT>IP layer provided by minisatip. This way TVH can no longer meddle with my tuner card and it all works like a charm!

You save my day! :D Thanks a lot for the your trick!

Share this post


Link to post
9 hours ago, psycmos said:

You save my day! :D Thanks a lot for the your trick!

Glad to be of service! I actually ordered a HDHomeRun in my despair to circumvent the DVB/TVH issue, not being aware of the fantastic minisatip option... Guess I'll be sending that back now... :D

Share this post


Link to post
2 hours ago, drdebian said:

Glad to be of service! I actually ordered a HDHomeRun in my despair to circumvent the DVB/TVH issue, not being aware of the fantastic minisatip option... Guess I'll be sending that back now... :D

FWIW - I personally recommend network tuners to anyone asking me about DVB card these days. No need to worry about drivers compiling etc.

Share this post


Link to post
19 hours ago, j0nnymoe said:

FWIW - I personally recommend network tuners to anyone asking me about DVB card these days. No need to worry about drivers compiling etc.

Yes, this is certainly true. I think I'll hold on to both the DVB quad-tuner card as well as the SAT>IP/HDHR solutions... One can never have too many tuners you know... ;) 

Share this post


Link to post

TBS 5990 is no longer detected in Unraid 6.8.0rc3. TBS QBOX-S2 is detected correctly.

lsusb output:

Quote

 

Bus 004 Device 003: ID 1058:25a2 Western Digital Technologies, Inc. Elements 25A2

Bus 004 Device 002: ID 1058:25a2 Western Digital Technologies, Inc. Elements 25A2

Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

Bus 003 Device 003: ID 051d:0002 American Power Conversion Uninterruptible Power Supply

Bus 003 Device 002: ID 048d:9006 Integrated Technology Express, Inc. IT9135 BDA Afatech DVB-T HDTV Dongle

Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Bus 002 Device 003: ID 1058:25a2 Western Digital Technologies, Inc. Elements 25A2

Bus 002 Device 002: ID 0781:5583 SanDisk Corp. Ultra Fit

Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

Bus 001 Device 002: ID 0b05:1872 ASUSTek Computer, Inc. AURA LED Controller

Bus 001 Device 005: ID 734c:5928 TBS Technologies China Q-Box II DVB-S2 HD

Bus 001 Device 006: ID 734c:5990 TBS Technologies China 

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

 

 

Migrated back to 6.6.7 where 5990 works.

Edited by max007

Share this post


Link to post

v6.8.0rc4 uploaded still no CrazyCat

Share this post


Link to post

What's the "unraid.dvb" option in the build list, i.e.

image.png.53f05d31ae51b395525e00d66721c55a.png

 

Edit: it has the same description as rc4.

Edited by Rick Gillyon

Share this post


Link to post

Hi guys,

 

Can please anyone confirm that the Hauppauge WinTV dualHD works with LibreELEC or TBS OS drivers? I just bought different Silicon Labs Si2168 based tuner and it only worked with Crazy Cat drivers that seem to have uncertain future at this point so I am returning it.

 

I also have a Realtek RTL2838/Sony CXD2837ER based tuner. I was unable to make the Sony DVB-T2 tuner visible so I ended up only with the Realtek DVB-T capable. I found out that the cooperation between the RTL and CXD chips should be already fixed but I was unable to make it work with the available drivers. RTL chip itself works with LibreELEC package.

 

More info on the RTL/CXD issue:

https://git.linuxtv.org/media_tree.git/commit/?id=d695eb5b3b963230652db29eae341a9706c593f4 - RTL driver updated to work with the CXD demod

https://github.com/torvalds/linux/pull/567 - this suggest that it might work in kernel 5.0 but I still got only RTL chip in tvheadend visible

Share this post


Link to post

V6.8.0rc5 done

Sent from my Mi A1 using Tapatalk

Share this post


Link to post
On 10/23/2019 at 3:56 PM, max007 said:

TBS 5990 is no longer detected in Unraid 6.8.0rc3. TBS QBOX-S2 is detected correctly.

lsusb output:

 

Migrated back to 6.6.7 where 5990 works.

Same for me, 5990 ist not detected in 6.8.0rc5 TBS open source. No problems back in 6.7.2. 

 

Any further logs to provide?

Share this post


Link to post

does this include the nvidia drivers?  i run the nvidia kernel but have just added live tv to my emby set up, currently having to run it on a pi but ideally i’d like to run tvheadend in a container, but need both nvidia and dvb drivers.

Share this post


Link to post
2 hours ago, Fizzyade said:

does this include the nvidia drivers?  i run the nvidia kernel but have just added live tv to my emby set up, currently having to run it on a pi but ideally i’d like to run tvheadend in a container, but need both nvidia and dvb drivers.

It does not contain the nvidia drivers.

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.