Sundtek

The sample device will be shipped early next week, we just finished the assembly of the latest MediaTV Pro (DVB-C/T/T2/AnalogTV/FM Radio/S-Video/Composite) devices

it's only about the device nodes on the host. You can install the driver already. When rebooting the system you might have to repeat step #1 , this part will change because it only creates dummy device nodes in /dev/dvb Step #2 will persist.

this does not work with our devices, they need to be installed either on the host (for host use) or in the docker image (for docker image use). The driver process uses shared memory and sys-v IPC, and that will be blocked between docker and the host.

the documentation works, however ich777 said that we should put the mknod commands into /boot/config/go that will eliminate step #1 of the install process; so the driver only would have to be installed in the docker image.

We will have some new DVB-C tuners available from next week on then we can send a device to you. Last time when you asked we had low stock... you just hit the wrong time.

it only creates the dvb dummy device nodes with mknod in the background - nothing else. It can be skipped if the device nodes are created another way.

All the Sundtek TV drivers needs on the host is the device nodes because docker uses them for access restriction as mentioned - it uses the major/minor ids (eg. in the list below major 212 minor 1 - n) TVHeadend won't be allowed to access the device nodes if we only create them inside the docker. they have to be present on the host before starting the docker image. And aside of that whenever unraid updates the kernel - it won't bother the sundtek driver - we have no kernel drivers. We simulate them aside the existing infrastructure (so we won't touch anything existing) using some very smart interfaces in Linux which have been there for over 2 decades too. The driver is only doing a mknod on the host - do you have any better advise where to put that on the host? The real driver is fully installed inside the docker. ideally there should be a field somewhere asking how many device nodes do you want to create on the host? mkdir -p /dev/dvb/adapter0 mkdir -p /dev/dvb/adapter1 #crwxrwxrwx 1 root root 212, 1 Dec 19 20:44 frontend0 #crwxrwxrwx 1 root root 212, 5 Dec 19 20:44 dvr0 #crwxrwxrwx 1 root root 212, 3 Dec 19 20:44 demux0 mknod /dev/dvb/adapter0/frontend0 c 212 1 mknod /dev/dvb/adapter0/dvr0 c 212 5 mknod /dev/dvb/adapter0/demux0 c 212 3 #crwxrwxrwx 1 root root 212, 7 Dec 19 20:44 frontend0 #crwxrwxrwx 1 root root 212, 11 Dec 19 20:44 dvr0 #crwxrwxrwx 1 root root 212, 9 Dec 19 20:44 demux0 mknod /dev/dvb/adapter1/frontend0 c 212 7 mknod /dev/dvb/adapter1/dvr0 c 212 11 mknod /dev/dvb/adapter1/demux0 c 212 9 or something like this: #!/bin/bash if [ "$#" -ne "1" ]; then echo "Argument $0 n" echo " n.. number of adapters" exit 1 fi n=$1 for i in $(seq 0 $(($n-1))); do mkdir -p /dev/dvb/adapter$i mknod /dev/dvb/adapter0/frontend0 c 212 $(($i*6+1)) mknod /dev/dvb/adapter0/dvr0 c 212 $(($i*6+5)) mknod /dev/dvb/adapter0/demux0 c 212 $(($i*6+3)) done

The post is old, I have just updated the documentation today. It always worked but the installation (without documentation) on that particular system might have been a little bit challenging. I managed to install unraid in a Virtualbox VM today so I was able to add some documentation about it. "Not supported" was the status before I put the documentation online.

I documented how to make the sundtek tuners work with linuxserver.io/tvheadend

Actually the sundtek devices all work with unraid. #1 Set up the driver on the host system Open a terminal as root (console) and run: cd /tmp wget http://sundtek.de/media/sundtek_netinst.sh chmod 777 sundtek_netinst.sh ./sundtek_netinst.sh -dockerhost (this will only take care that some dummy nodes are created in /dev/dvb/, access control will be handled by major/minor numbers of the existing files. When the driver is started on the host it will exit directly due to the dockerhost flag and only create the nodes) #2 Set up the driver inside the tvheadend docker ... install the tvheadend docker, add an extra device driver for /dev/bus/usb open the host terminal and enter the tvheadend docker image: docker exec -it tvheadend /bin/sh cd /tmp wget http://sundtek.de/media/sundtek_netinst.sh chmod 777 sundtek_netinst.sh ./sundtek_netinst.sh -docker -use-custom-path /config (this will rename the tvheadend binary to tvheadend.bin and put a script in between which will start the driver inside the docker - followed by the actual tvheadend binary). #3 that's it restart the tvheadend docker. Sundtek Dual USB DVB-S/S2/S2X:

exactly. yes but docker is a little bit handicapped when it comes to device support, docker needs to know which major / minor IDs should be allowed -- in advance when starting the docker. lxr containers are more flexible. Anyway: Our driver additionally needs access to /dev/bus/usb (major / minor ids) and "template" files need to be created in /dev/dvb/ ... on the host system so it is allowed to create the corresponding nodes inside of docker What do you use DVB-S or DVB-C? depending on which device you might need we might send a sample to you if you want. Adding support for the driver would add support for all devices which have been sold since 2008. There are many supported systems out there and far more than any other tuner supports.

The drivers are different, they're userspace drivers (not depending on any kernel particular kernel version); they will always be out of any tree because we maintain them. As far as I remember unraid was mentioned a few times, and it works but needs some installation/configuration work. The entry/documentation in our wiki about docker containers is for a regular ubuntu system; that's why it might not work exactly the same way with unraid. Libreelec has its own sundtek plugin, I'm not sure how far unraid is using/re-using the libreelec work.