[Plugin] Linuxserver.io - Unraid DVB


Recommended Posts

That's fine.  Slower than mine, but more than acceptable.

 

Only other possibility is a javascript error.  Can go back to the settings, load unRaid DVB, wait a couple of minutes, then:

 

(I'm assuming you're using Chrome)

 

Right click anywhere within the window and say inspect.  Within the new window, click on "console" and then post whatever errors appear.

Link to comment

Unfortunately I get the same behaviour as before I went through unRAID versions (see screenshot on the previous page):

Edit: Occasionally I seem to be able to also produce the following warning, not sure whether it's related:
 

[Violation] Added non-passive event listener to a scroll-blocking 'mousewheel' event. Consider marking event handler as 'passive' to make the page more responsive. jquery-2.1.1.min.js:3 


 

samebehaviour.png

Edited by tbrasser
added occasionaly appearing warning
Link to comment

The browser is timing out on the response from the code.  And since there's no response the popup won't close.  Not sure why as I've ran that popup waiting for a response for over a half hour at a time.

 

Try:

  • A different browser
  • Clearing browser cache
  • or navigating to 10.0.0.10 instead of /server and try again.

The last resort is to download the file attached to the flash drive then

cp /boot/UnraidDVB.page /usr/local/emhttp/plugins/UnraidDVB/UnraidDVB.page[code]


 

Load the DVB settings again, wait say 10 minutes, and maybe something will appear on the screen.  After that, I'm completely out of ideas since neither I nor @CHBMB can replicate.  (Beyond completely simplifying your network and basically going back to a stock normal network) But try the above ideas first.

 

UnraidDVB.page

Edited by Squid
Link to comment

I tried that now. Also directly on the server (booted in gui mode). Still no luck. Im giving up for today. I'll post back here when I have found out more.

 

EDIT: I once again copied all the images to /boot manually and everything works! (well except for the DVB plugin, but the manual update worked, I can use my tuners now!)

 

Thanks for both of your time!

Edited by tbrasser
I managed to get it working somehow
Link to comment
On 21/07/2017 at 1:55 AM, tbrasser said:

I tried that now. Also directly on the server (booted in gui mode). Still no luck. Im giving up for today. I'll post back here when I have found out more.

 

EDIT: I once again copied all the images to /boot manually and everything works! (well except for the DVB plugin, but the manual update worked, I can use my tuners now!)

 

Thanks for both of your time!

 

Be interested to know why it wasn't working, but absolutely no idea on how to figure out how....

Link to comment
7 hours ago, CHBMB said:

 

Be interested to know why it wasn't working, but absolutely no idea on how to figure out how....

My "best" gues of what could've gone wrong:
* corrupt download the first time around (didn't check the hashes or anything)
* my unraid webinterface has a history of being slow, with unraid DVB edition plugin timing-out for me even before 6.4, but usually after some weird sequence of refreshing and stopping the loading of the page I got it working. (Which means it got stuck after downloading the list of available images), refreshing plugins to update or docker containers always takes ages (with around 15 plugins to check and 25 containers). Maybe with the new webserver changes (I read something about nginx) this "workaround" I used to have to go through also failed. 
(My hardware is pretty old, dual-core i3 with hyperthreading, 12gb ddr2 ram, no dedicated gpu, and probably a realtek gigabit LAN interface that was never ever intented for any kind of server-y workloads.)

That being said, as long as plex isn't transcoding there are few hickups with the rest of the system.

Link to comment

Hey, just about 6 months in to my first unraid build and couldn't be happier. However, just decided to add a TV tuner, and ended up with the Hauppauge (1595) WinTV-dualHD. At first, I this this would not be a problem with the libelec drivers, but as it turns out, I can't get tvheadend to recognize the tuner after I've installed the DVB plugin (Unraid 6.3.2). The status page on the DVB plugin shows that the DVB kernel is installed with libreelec 1.21 drivers. However, the adapter driver is not found. Following Hauppage's instructions for Ubuntu, I have been able to get things working in an Ubuntu VM on the unraid server.

 

As it turns out, this version of the Hauppauge tuner is only natively supported in kernel 4.11 per the LinuxTV wiki. However, it does appear that there areways to patch these drivers into previous kernels. Unfortunately, that goes beyond my skillset. Would it be possible to have these drivers integrated? Or any chance someone might be able to provide some direction on how to do it myself?

 

Thanks!

Link to comment
Just now, ed_dantes said:

Hey, just about 6 months in to my first unraid build and couldn't be happier. However, just decided to add a TV tuner, and ended up with the Hauppauge (1595) WinTV-dualHD. At first, I this this would not be a problem with the libelec drivers, but as it turns out, I can't get tvheadend to recognize the tuner after I've installed the DVB plugin (Unraid 6.3.2). The status page on the DVB plugin shows that the DVB kernel is installed with libreelec 1.21 drivers. However, the adapter driver is not found. Following Hauppage's instructions for Ubuntu, I have been able to get things working in an Ubuntu VM on the unraid server.

 

As it turns out, this version of the Hauppauge tuner is only natively supported in kernel 4.11 per the LinuxTV wiki. However, it does appear that there areways to patch these drivers into previous kernels. Unfortunately, that goes beyond my skillset. Would it be possible to have these drivers integrated? Or any chance someone might be able to provide some direction on how to do it myself?

 

Thanks!

 

We're already on a kernel past that on the RC series and as far as I know the Hauppage card still doesn't work, despite all the components being present.  I'm currently working on RC7a so you can try that, but I won't be backporting to v6.3.5 and definitely not v6.3.2

  • Upvote 1
Link to comment
1 minute ago, CHBMB said:

 

We're already on a kernel past that on the RC series and as far as I know the Hauppage card still doesn't work, despite all the components being present.  I'm currently working on RC7a so you can try that, but I won't be backporting to v6.3.5 and definitely not v6.3.2

 

Ok, thanks.Tried to save some hardware and money by integrating the tuner into the unraid box but seems like it may just be easier to go with something like the HDHomeRun Connect.

Edited by ed_dantes
Link to comment

Currently im testing unraid for my Homeserver and I can't bring my dvb tuner working on it.

I used arch linux bevor and it was just fine.

 

My Hardware:

Intel Pentium G4500

MSI C236M

dvbsky s952 VER3.0a

 

I have unraid 6.3.5 dvb edition LibreELEC installed and there are two "Montage Technology M88RS6000" DVB adapters recognised.

 

Under System Devices I can find this:

[8086:190f] 00:00.0 Host bridge: Intel Corporation Skylake Host Bridge/DRAM Registers (rev 07)
[8086:1901] 00:01.0 PCI bridge: Intel Corporation Skylake PCIe Controller (x16) (rev 07)
[8086:1912] 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 530 (rev 06)
[8086:1911] 00:08.0 System peripheral: Intel Corporation Skylake Gaussian Mixture Model
[8086:a12f] 00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI Controller (rev 31)
[8086:a131] 00:14.2 Signal processing controller: Intel Corporation Sunrise Point-H Thermal subsystem (rev 31)
[8086:a160] 00:15.0 Signal processing controller: Intel Corporation Sunrise Point-H Serial IO I2C Controller #0 (rev 31)
[8086:a161] 00:15.1 Signal processing controller: Intel Corporation Sunrise Point-H Serial IO I2C Controller #1 (rev 31)
[8086:a13a] 00:16.0 Communication controller: Intel Corporation Sunrise Point-H CSME HECI #1 (rev 31)
[8086:a102] 00:17.0 SATA controller: Intel Corporation Sunrise Point-H SATA controller [AHCI mode] (rev 31)
[8086:a110] 00:1c.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #1 (rev f1)
[8086:a117] 00:1c.7 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #8 (rev f1)
[8086:a118] 00:1d.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #9 (rev f1)
[8086:a119] 00:1d.1 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #10 (rev f1)
[8086:a127] 00:1e.0 Signal processing controller: Intel Corporation Sunrise Point-H Serial IO UART #0 (rev 31)
[8086:a149] 00:1f.0 ISA bridge: Intel Corporation Sunrise Point-H LPC Controller (rev 31)
[8086:a121] 00:1f.2 Memory controller: Intel Corporation Sunrise Point-H PMC (rev 31)
[8086:a123] 00:1f.4 SMBus: Intel Corporation Sunrise Point-H SMBus (rev 31)
[1ade:3038] 03:00.0 Multimedia video controller: Spin Master Ltd. PCIe Video Bridge (rev 01)
[10ec:8168] 05:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)

 

but every time i start a new docker container with tvheadend, tvheadend doesn't recognise any dvb tuner.

 

My configs are:

Repository: linuxserver/tvheadend

Network Typ: Bridge

Extra Parameters: --device=/dev/dvb/

Privileged: on (also tested with off)

Ports: 9981 and 9982 are exposed

 

Over SSH:

dmesg | grep -i dvb
[   13.825875] SMI PCIe driver 0000:03:00.0: card detected: DVBSky S952 V3
[   13.921538] DVB: registering new adapter (SMI_DVB)
[   14.112430] SMI PCIe driver 0000:03:00.0: DVB: registering adapter 0 frontend 0 (Montage Technology M88RS6000)...
[   14.119135] SMI PCIe driver 0000:03:00.0: DVBSky S952 V3 port 0 MAC: 00:18:42:54:55:52
[   14.119286] DVB: registering new adapter (SMI_DVB)
[   14.327619] SMI PCIe driver 0000:03:00.0: DVB: registering adapter 1 frontend 0 (Montage Technology M88RS6000)...
[   14.334326] SMI PCIe driver 0000:03:00.0: DVBSky S952 V3 port 1 MAC: 00:18:32:54:55:53
[   14.356402] Registered IR keymap rc-dvbsky
[   14.357715] input: IR (DVBSky S952 V3) as /devices/pci0000:00/0000:00:1c.7/0000:03:00.0/rc/rc0/input7
[   14.358079] rc rc0: IR (DVBSky S952 V3) as /devices/pci0000:00/0000:00:1c.7/0000:03:00.0/rc/rc0
 

Edited by Dbone
Link to comment

I just found the problem. Thanks a lot!

 

docker exec -it TVHeadend ls -la /dev/dvb

Quote

 

total 0

drwxr-xr-x  4 root root   80 Aug  1 19:22 .

drwxr-xr-x 14 root root 3460 Aug  1 19:22 ..

drwxr-xr-x  2 root root  120 Aug  1 19:22 adapter0

drwxr-xr-x  2 root root  120 Aug  1 19:22 adapter1

 

 

ls -la /dev/dvb

Quote

total 0
drwxr-xr-x  4 nobody users   80 Aug  1 14:15 ./
drwxr-xr-x 16 root   root  3620 Aug  1 14:15 ../
drwxr-xr-x  2 nobody users  120 Aug  1 14:15 adapter0/
drwxr-xr-x  2 nobody users  120 Aug  1 14:15 adapter1/

 

Edited by Dbone
Link to comment
2 minutes ago, CHBMB said:

It looked like permissions to me, which doesn't make sense as the plugin does a chmod at boot.

Sent from my LG-H815 using Tapatalk
 

 

The permissions are correct in unraid aren't they? Wonder how it ended up as root in the tvheadend container...

Link to comment
1 hour ago, saarg said:

 

What was the problem?

 

 

https://hub.docker.com/r/linuxserver/tvheadend/

Quote

User / Group Identifiers

Sometimes when using data volumes (-v flags) permissions issues can arise between the host OS and the container. We avoid this issue by allowing you to specify the user PUID and group PGID. Ensure the data volume directory on the host is owned by the same user you specify and it will "just work" â¢.

In this instance PUID=1001 and PGID=1001. To find yours use id user as below:


  $ id <dockeruser>
    uid=1001(dockeruser) gid=1001(dockergroup) groups=1001(dockergroup)

 

So what I have done:

 

id nobody

and i got a gid of 99 and a uid of 100

 

I just added this line to the Extra Parameters:

-e PGID=100 -e PUID=99

 

so my new Extra Parameters are:

--device=/dev/dvb/ -e PGID=100 -e PUID=99

 

This was the only thing that i have changed. I hope this could help you.

Edited by Dbone
Link to comment
  • Squid locked this topic
Guest
This topic is now closed to further replies.