Sundtek Support Forum

what I noticed is, that the /dev/dvb disappears on the host after ubuntu reboot.
the container then won't start of course.
perhaps that was the reason, that somehow the container lost access to this folder previously and I missed something and just always tried to re-create the container and install drivers inside container and never noticed that there is something wrong with /dev/dvb
so after reboot, when I create the /dev/dvb content with the below commands, the tvh container starts fine and adapter is present in tvh interface. I'll observe further.

mkdir -p /dev/dvb/adapter0
mknod /dev/dvb/adapter0/frontend0 c 212 1
mknod /dev/dvb/adapter0/dvr0 c 212 5
mknod /dev/dvb/adapter0/demux0 c 212 3

it seems that this set of messages repeats. I wonder if it's every time the adapter disappears from TVHeadend. those are today's messages, but it's similar from yesterday when I tested plugging and unplugging the tuner from USB hub directly to HC4 port and back again. so perhaps every time the USB hub somehow loses power the adapter disappears from TVHeadend.
[Mon Dec  6 10:11:49 2021] usb 1-2.3: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 2 len 1 ret -71
[Mon Dec  6 10:11:49 2021] usb 1-2.3: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 2 len 1 ret -71
[Mon Dec  6 10:11:49 2021] usb 1-2.3: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 2 len 1 ret -71
[Mon Dec  6 10:11:49 2021] usb 1-2.3: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 2 len 1 ret -71
[Mon Dec  6 10:11:49 2021] usb 1-2.3: USB disconnect, device number 55
[Mon Dec  6 10:11:49 2021] usb 1-2.3: new high-speed USB device number 56 using xhci-hcd
[Mon Dec  6 10:11:49 2021] usb 1-2.3: New USB device found, idVendor=2659, idProduct=1502
[Mon Dec  6 10:11:49 2021] usb 1-2.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[Mon Dec  6 10:11:49 2021] usb 1-2.3: Product: SkyTV Ultimate 6 2016/Q1
[Mon Dec  6 10:11:49 2021] usb 1-2.3: Manufacturer: Sundtek
[Mon Dec  6 10:11:49 2021] usb 1-2.3: SerialNumber: U171212190229
[Mon Dec  6 10:11:49 2021] usb 1-2.3: Unsupported device
[Mon Dec  6 10:11:49 2021] usb 1-2.3: Unsupported device
[Mon Dec  6 10:11:49 2021] usb 1-2.3: Unsupported device
[Mon Dec  6 10:11:49 2021] usb 1-2.3: Unsupported device
[Mon Dec  6 10:11:49 2021] usb 1-2.3: Unsupported device
[Mon Dec  6 10:11:49 2021] usb 1-2.3: Unsupported device
[Mon Dec  6 10:11:49 2021] usb 1-2.3: Unsupported device
[Mon Dec  6 11:59:11 2021] docker0: port 1(vethd684a46) entered disabled state
[Mon Dec  6 11:59:11 2021] veth1d78fb8: renamed from eth0
[Mon Dec  6 11:59:11 2021] docker0: port 1(vethd684a46) entered disabled state
[Mon Dec  6 11:59:11 2021] device vethd684a46 left promiscuous mode
[Mon Dec  6 11:59:11 2021] docker0: port 1(vethd684a46) entered disabled state
[Mon Dec  6 11:59:11 2021] docker0: port 1(vethfec4937) entered blocking state
[Mon Dec  6 11:59:11 2021] docker0: port 1(vethfec4937) entered disabled state
[Mon Dec  6 11:59:11 2021] device vethfec4937 entered promiscuous mode
[Mon Dec  6 11:59:11 2021] IPv6: ADDRCONF(NETDEV_UP): vethfec4937: link is not ready
[Mon Dec  6 11:59:11 2021] docker0: port 1(vethfec4937) entered blocking state
[Mon Dec  6 11:59:11 2021] docker0: port 1(vethfec4937) entered forwarding state
[Mon Dec  6 11:59:12 2021] eth0: renamed from vetha074485
[Mon Dec  6 11:59:12 2021] IPv6: ADDRCONF(NETDEV_CHANGE): vethfec4937: link becomes ready
[Mon Dec  6 11:59:13 2021] amlogic-pcie-v2 fc000000.pcieA: the device class is not reported correctly from the register
[Mon Dec  6 11:59:16 2021] usb 1-2.3: usbfs: process 103060 (mediasrv) did not claim interface 0 before use
[Mon Dec  6 11:59:30 2021] usb 1-2.3: usbfs: process 103067 (mediasrv) did not claim interface 2 before use

I didn't have chance to contact you. my kid's kindergarten has covid holidays. but I was able to make it work again. so those are steps I took:

1) uninstall sundtek driver
./sundtek_netinst.sh -u

2) delete the /dev/dvb directory

3) I didn't install the driver with the -createnodes parameter but found manual way to do it on your wiki pages for synology
mkdir -p /dev/dvb/adapter0
mknod /dev/dvb/adapter0/frontend0 c 212 1
mknod /dev/dvb/adapter0/dvr0 c 212 5
mknod /dev/dvb/adapter0/demux0 c 212 3

4) created docker container
docker create --name=tvh \
-v tvh:/config \
-v tvhpicons:/picons \
-v /drives/data2/REC/:/recordings \
-e PUID=1000 -e PGID=1000 \
-e TZ=CET \
-p 9981:9981 \
-p 9982:9982 \
--device=/dev/dvb:/dev/dvb \
--device=/dev/bus/usb:/dev/bus/usb \
--restart always \
linuxserver/tvheadend:arm64v8-latest

5) started and entered the docker container and installed the driver there
./sundtek_netinst.sh -docker -use-custom-path=/config

6) restarted the container and the adapter appeared in the tvheadend web interface and it's working again.

I have no idea what I did wrong before, I tried many times, but I could swear I did it same except the step 3. I hope this time it will work without issues or at least that this is the way how to replicate the successful installation on HC4 with ubuntu and tvheadend docker image.

what do you mean two tuners? both analog and DVB-S2 on SkyTV 6? I don't need that analog one.
HC4 USB port is rated 500mA, so I don't want to take the risk something happens to the USB port or the HW behind that.
do you know of some reliable USB self-powered hub?

I'll try to catch you on the chat one day evening.

aaand it doesn't work again...
I haven't touched it. I turned up the TV and HTSP client couldn't connected.
so I restarted TVH container and I got this error:
root@odroid:~# docker start tvh
Error response from daemon: error gathering device information while adding custom device "/dev/dvb": no such file or directory
Error: failed to start containers: tvh

so I checked directory and it's not present...
root@odroid:~# cd /dev/dvb
-bash: cd: /dev/dvb: No such file or directory

I stopped container, ran ./sundtek_netinst.sh –createnodes and started the container and adapter was missing.

so I installed it inside the container again with ./sundtek_netinst.sh -docker -use-custom-path=/config and still nothing.
I removed container, added it again, ran ./sundtek_netinst.sh -u, then ./sundtek_netinst.sh –createnodes again and ./sundtek_netinst.sh -docker -use-custom-path=/config inside the container, restarted the container and nothing.
I checked tvheadend startup script under /usr/bin and LD_PRELOAD is there with correct values, I checked mediaclient -e and it shows the adapter on the host as well as inside docker container. what the...

Hi, thank for response. see the answers for your questions.

tvheadend startup script content:
#!/bin/sh
/opt/bin/mediasrv -d --wait-for-devices --pluginpath=/opt/bin
LD_PRELOAD=/opt/lib/libmediaclient.so /usr/bin/tvheadend.bin $@

sundtek driver is arm64:
root@odroid:/opt/bin# ./mediaclient --arch
Architecture: arm64

and I asumed same for tvheadend container as it started just fine without specifically downloading the arm64 image. but just to be sure I explicitly downloaded arm64 image with arm64v8-latest tag and I can see the sundtek adapter finally. thank you.

Hello, I'd like to ask similar question. I'm thinking about buying Asustor AS6302T. is there recorded successful installation and usage of SkyTV dongle with Asustor NAS? Sorry that I'm asking about SkyTV in MediaTV Pro section.