English > {Single, Dual, Quad} Sundtek SkyTV Ultimate

linuxserver/tvheadend + sundtek

<< < (3/5) > >>

tomasl:
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.

Sundtek:
early in the morning is best!

oh you have another tuner, sorry I thought you have a dual dvb-s2 tuner.

tomasl:
nope, I'm waiting for the quad tuner. ;)

I'll try to get to you early in the morning then. in upcoming 3 days.

tomasl:
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.

tomasl:
it again disappeared, but this time it was back again when I restarted container. I don't know why, but I assume because I haven't used the tuner since yesterday. Is there some "keepalive" setting in the driver or tvheadend that would prevent this?

Navigation

[0] Themen-Index

[#] Nächste Seite

[*] Vorherige Sete