August 29, 20169 yr Can anybody make a unraid docker conter for this tvheaend version : https://hub.docker.com/r/dreamcat4/tvheadend/ This version of tvheadend has support for dvb-c usb sundtek dongels
August 29, 20169 yr Where have you got that idea from? As far as I know the drivers need to be on the host, ie Unraid, not bundled up in the container. Sent from my LG-H815 using Tapatalk
August 29, 20169 yr Author Hi CHBMB I found it on the github from th e creator : you need to remove sundtek driver from host and install in the guest. (currently the only way - talked to sundtek support) i forked the dockerfile to do this: https://github.com/firsttris/docker-images/blob/master/tvh/master/Dockerfile regards tristan
August 29, 20169 yr Hi CHBMB I found it on the github from th e creator : you need to remove sundtek driver from host and install in the guest. (currently the only way - talked to sundtek support) i forked the dockerfile to do this: https://github.com/firsttris/docker-images/blob/master/tvh/master/Dockerfile regards tristan Well if you've got the dockerfile and that works, why request it? Just build the docker container yourself. As someone that is actively working on DVB stuff on Unraid and knowing the other guys here that are also working on DVB stuff in Unraid, I just don't see us taking this forward as it's such a single use case. We'd essentially be building a docker image for you and you only. So in that case it's better for you to make it yourself. Reading up about Sundtek that is some weird ass implementation of DVB in Linux..... EDIT: Also I'm suspicious that Sundtek may not truly understand docker, but I may be wrong.
August 29, 20169 yr Author oke I understand , is there a webpage or how to about making docker unraid image ?
August 29, 20169 yr Just had a quick look at this. If it were me, what I'd try is this: Open a telnet/SSH prompt to your Unraid machine and run this. wget http://www.sundtek.de/media/sundtek_netinst.sh chmod +x sundtek_netinst.sh sundtek_netinst.sh and see where you get...
August 29, 20169 yr Author I installed the driver , but its not showing up in tvheadend ( restarted tvheadend ) ( at github they mention that you need to remove sundtek driver from host and install in the guest.) output ofsundtek_netinst.sh : adding administrator to audio group for playback... unpacking... checking system... testing libc OK 2.17.0 64Bit System detected installing (netinstall mode) ... Downloading architecture specific driver ... 64bit Download finished, installing now ... installing remote control support finalizing configuration... (can take a few seconds) Starting driver... done.
August 29, 20169 yr Post the output of lsusb & the output of lspci (try and wrap code in tags, it's the # symbol above the editing pane in the forum) Can you post this github link?
August 29, 20169 yr Author Hi CHBMB here is the output lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID eb1a:51b2 eMPIA Technology, Inc. Bus 001 Device 002: ID 0951:162f Kingston Technology Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub lspci: 00:00.0 Host bridge: Intel Corporation Sky Lake Host Bridge/DRAM Registers (rev 07) 00:02.0 VGA compatible controller: Intel Corporation Sky Lake Integrated Graphics (rev 06) 00:08.0 System peripheral: Intel Corporation Sky Lake Gaussian Mixture Model 00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI Controller (rev 31) 00:14.2 Signal processing controller: Intel Corporation Sunrise Point-H Thermal subsystem (rev 31) 00:15.0 Signal processing controller: Intel Corporation Sunrise Point-H LPSS I2C Controller #0 (rev 31) 00:15.1 Signal processing controller: Intel Corporation Sunrise Point-H LPSS I2C Controller #1 (rev 31) 00:16.0 Communication controller: Intel Corporation Sunrise Point-H CSME HECI #1 (rev 31) 00:17.0 SATA controller: Intel Corporation Device a102 (rev 31) 00:1c.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #5 (rev f1) 00:1c.5 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #6 (rev f1) 00:1e.0 Signal processing controller: Intel Corporation Sunrise Point-H LPSS UART #0 (rev 31) 00:1f.0 ISA bridge: Intel Corporation Sunrise Point-H LPC Controller (rev 31) 00:1f.2 Memory controller: Intel Corporation Sunrise Point-H PMC (rev 31) 00:1f.3 Audio device: Intel Corporation Sunrise Point-H HD Audio (rev 31) 00:1f.4 SMBus: Intel Corporation Sunrise Point-H SMBus (rev 31) 01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15) 02:00.0 Multimedia controller: Device 544d:6178 github link : https://github.com/dreamcat4/docker-images/issues/15
August 29, 20169 yr Hi CHBMB here is the output lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID eb1a:51b2 eMPIA Technology, Inc. Bus 001 Device 002: ID 0951:162f Kingston Technology Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub lspci: 00:00.0 Host bridge: Intel Corporation Sky Lake Host Bridge/DRAM Registers (rev 07) 00:02.0 VGA compatible controller: Intel Corporation Sky Lake Integrated Graphics (rev 06) 00:08.0 System peripheral: Intel Corporation Sky Lake Gaussian Mixture Model 00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI Controller (rev 31) 00:14.2 Signal processing controller: Intel Corporation Sunrise Point-H Thermal subsystem (rev 31) 00:15.0 Signal processing controller: Intel Corporation Sunrise Point-H LPSS I2C Controller #0 (rev 31) 00:15.1 Signal processing controller: Intel Corporation Sunrise Point-H LPSS I2C Controller #1 (rev 31) 00:16.0 Communication controller: Intel Corporation Sunrise Point-H CSME HECI #1 (rev 31) 00:17.0 SATA controller: Intel Corporation Device a102 (rev 31) 00:1c.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #5 (rev f1) 00:1c.5 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #6 (rev f1) 00:1e.0 Signal processing controller: Intel Corporation Sunrise Point-H LPSS UART #0 (rev 31) 00:1f.0 ISA bridge: Intel Corporation Sunrise Point-H LPC Controller (rev 31) 00:1f.2 Memory controller: Intel Corporation Sunrise Point-H PMC (rev 31) 00:1f.3 Audio device: Intel Corporation Sunrise Point-H HD Audio (rev 31) 00:1f.4 SMBus: Intel Corporation Sunrise Point-H SMBus (rev 31) 01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15) 02:00.0 Multimedia controller: Device 544d:6178 github link : https://github.com/dreamcat4/docker-images/issues/15 Is the empia device the sundtek adapter? You could try passing through the USB with the device tag. I'll get back to you with more info when I'm on a computer.
August 29, 20169 yr As regards the link, that is you that has posted all the information from 8 months ago and forked it 8 months ago. SO I'm assuming you have had this up and working on a different system then?
August 29, 20169 yr Hi CHBMB I found it on the github from th e creator : you need to remove sundtek driver from host and install in the guest. (currently the only way - talked to sundtek support) i forked the dockerfile to do this: https://github.com/firsttris/docker-images/blob/master/tvh/master/Dockerfile regards tristan The dreamcat4 version does not have the sundtek drivers. The container you linked to is a fork of the dreamcat4 container.
August 29, 20169 yr Author As regards the link, that is you that has posted all the information from 8 months ago and forked it 8 months ago. SO I'm assuming you have had this up and working on a different system then? I had have it running on a debian system , but i'am migrating away from it , i never had it working with docker/unraid
August 29, 20169 yr Hi CHBMB I found it on the github from th e creator : you need to remove sundtek driver from host and install in the guest. (currently the only way - talked to sundtek support) i forked the dockerfile to do this: https://github.com/firsttris/docker-images/blob/master/tvh/master/Dockerfile regards tristan The dreamcat4 version does not have the sundtek drivers. The container you linked to is a fork of the dreamcat4 container. Yeah it's the OP that forked it, but I'm confused as on one hand he's asking someone to build him the container, yet on the other hand, he seems to have encountered this problem 8 months ago and presumedly sorted his issue by forking it. saarg, am i the only one that thinks installing the drivers in the container is a crazy way to go about solving this issue?
August 29, 20169 yr As regards the link, that is you that has posted all the information from 8 months ago and forked it 8 months ago. SO I'm assuming you have had this up and working on a different system then? I had have it running on a debian system , but i'am migrating away from it , i never had it working with docker/unraid So do you have a docker container built then? Unraid can use any container, it's just the webgui and template that is unique to unraid. When you had it running on debian, how did you do that?
August 29, 20169 yr OK, so you need to see this as a process and there are going to be two steps. 1. Get the sundtek card working on Unraid and visible 2. Pass the sunddtek card through to TVheadend Ignore getting a container built for now, as I am 99% sure that is not the way to do this. It would go against every other way to get DVB working with docker that I've seen.
August 29, 20169 yr Author As regards the link, that is you that has posted all the information from 8 months ago and forked it 8 months ago. SO I'm assuming you have had this up and working on a different system then? I had have it running on a debian system , but i'am migrating away from it , i never had it working with docker/unraid So do you have a docker container built then? Unraid can use any container, it's just the webgui and template that is unique to unraid. When you had it running on debian, how did you do that? No it is a standalone debian system on rasberry pi so no docker , sorry for the misunderstanding
August 29, 20169 yr Hi CHBMB I found it on the github from th e creator : you need to remove sundtek driver from host and install in the guest. (currently the only way - talked to sundtek support) i forked the dockerfile to do this: https://github.com/firsttris/docker-images/blob/master/tvh/master/Dockerfile regards tristan The dreamcat4 version does not have the sundtek drivers. The container you linked to is a fork of the dreamcat4 container. Yeah it's the OP that forked it, but I'm confused as on one hand he's asking someone to build him the container, yet on the other hand, he seems to have encountered this problem 8 months ago and presumedly sorted his issue by forking it. saarg, am i the only one that thinks installing the drivers in the container is a crazy way to go about solving this issue? You're not the only one...
August 29, 20169 yr Author OK, so you need to see this as a process and there are going to be two steps. 1. Get the sundtek card working on Unraid and visible 2. Pass the sunddtek card through to TVheadend Ignore getting a container built for now, as I am 99% sure that is not the way to do this. It would go against every other way to get DVB working with docker that I've seen. the sundtek adpter/driver is running on unraid, the output of /opt/bin/mediaclient --lc /opt/bin/mediaclient --lc **** List of Media Clients **** /dev/dvb/adapter2/frontend0: No client connected /dev/dvb/adapter2/dvr0: No client connected /dev/dvb/adapter2/demux0: No client connected /dev/video0: No client connected /dev/vbi0: No client connected /dev/radio0: No client connected /dev/rds0: No client connected /dev/mediainput0: No client connected /dev/dsp0: No client connected If i remove the usb adpter the output is /opt/bin/mediaclient --lc **** List of Media Clients **** Informatie about the driver and /opt/bin/mediaclient found on http://support.sundtek.com/index.php/topic,4.0.html (adapter 0,1 is a TBS6902 )
August 29, 20169 yr OK, so you need to see this as a process and there are going to be two steps. 1. Get the sundtek card working on Unraid and visible 2. Pass the sunddtek card through to TVheadend Ignore getting a container built for now, as I am 99% sure that is not the way to do this. It would go against every other way to get DVB working with docker that I've seen. the sundtek adpter/driver is running on unraid, the output of /opt/bin/mediaclient --lc /opt/bin/mediaclient --lc **** List of Media Clients **** /dev/dvb/adapter2/frontend0: No client connected /dev/dvb/adapter2/dvr0: No client connected /dev/dvb/adapter2/demux0: No client connected /dev/video0: No client connected /dev/vbi0: No client connected /dev/radio0: No client connected /dev/rds0: No client connected /dev/mediainput0: No client connected /dev/dsp0: No client connected If i remove the usb adpter the output is /opt/bin/mediaclient --lc **** List of Media Clients **** Informatie about the driver and /opt/bin/mediaclient found on http://support.sundtek.com/index.php/topic,4.0.html (adapter 0,1 is a TBS6902 ) The if you use my tvheadend DVB tuners container, you should have the dvb-t stick available in tvheadend.
August 29, 20169 yr The dvb-c stick adapter is not visable Did you do this: /opt/bin/mediaclient --setdtvmode=DVBT Also restart the tvheadend container after you get the drivers installed.
August 29, 20169 yr Author The dvb-c stick adapter is not visable Did you do this: /opt/bin/mediaclient --setdtvmode=DVBT Also restart the tvheadend container after you get the drivers installed. Hi saarg i did reset tvheadend after driver is installed , but the tvheadend does not recognize adapter 2 ( i use dvbc and not dvbt /opt/bin/mediaclient --setdtvmode=DVBC ) log tvheadend : Aug 29 20:51:34 NAS01 tvheadend[18]: linuxdvb: adapter added /dev/dvb/adapter1 Aug 29 20:51:34 NAS01 tvheadend[18]: linuxdvb: adapter added /dev/dvb/adapter0
August 29, 20169 yr The dvb-c stick adapter is not visable Did you do this: /opt/bin/mediaclient --setdtvmode=DVBT Also restart the tvheadend container after you get the drivers installed. Hi saarg i did reset tvheadend after driver is installed , but the tvheadend does not recognize adapter 2 ( i use dvbc and not dvbt /opt/bin/mediaclient --setdtvmode=DVBC ) log tvheadend : Aug 29 20:51:34 NAS01 tvheadend[18]: linuxdvb: adapter added /dev/dvb/adapter1 Aug 29 20:51:34 NAS01 tvheadend[18]: linuxdvb: adapter added /dev/dvb/adapter0 Show me the output of the below command in unraid. ls -la /dev/dvb
August 29, 20169 yr Author ls -la /dev/dvb total 0 drwxrwxrwx 5 nobody users 100 Aug 29 21:03 ./ drwxr-xr-x 17 root root 4000 Aug 29 21:03 ../ drwxr-xr-x 2 nobody users 120 Aug 29 20:50 adapter0/ drwxr-xr-x 2 nobody users 120 Aug 29 20:50 adapter1/ drwxrwxrwx 2 root root 100 Aug 29 21:03 adapter2/
Archived
This topic is now archived and is closed to further replies.