Sundtek Support Forum

so, the /etc/sundtek.conf contains only line, which is loglevel=max
I restarted the container, I hope that this forces the sundtek driver to read the conf file and log the debug level of events in the mediasrv.log.

you said the mediasrv.log should be under /var/log/syslog, but it's in /var/log and it contains only this, events from 4 days ago.

2024-11-07 11:59:00 [195] Starting up Multimedia Framework (Aug 22 2024 14:52:09)
2024-11-07 11:59:00 [195] Detected DVB version.h
2024-11-07 11:59:00 [196] Starting service processor (PID 196)
2024-11-07 11:59:00 [195] API Version: 5.11
2024-11-07 11:59:00 [195] Running on Linux (4.9.277-82)
2024-11-07 11:59:00 [195] scanning devices
2024-11-07 11:59:00 [195] scanning for drivers
2024-11-07 11:59:00 [195] scanning for plugins
2024-11-07 11:59:00 [195] Starting up device manager
2024-11-07 11:59:00 [195] Setting permission of /dev/dvb to 777
2024-11-07 11:59:00 [195] This is to avoid problems if TV Applications are started as another user
2024-11-07 11:59:00 [195] as seen on eg. Synology NAS Systems where tvheadend is unable to read
2024-11-07 11:59:00 [195] /dev/dvb and because of that would not detect the TV tuner
2024-11-07 11:59:00 [195] scanning devices done
2024-11-07 11:59:00 [195] attached devices:
2024-11-07 11:59:00 [195] registering ID: 0
2024-11-07 11:59:00 [195] Memory mapped transfers are not available
2024-11-07 11:59:00 [195] Using dynamic configuration
2024-11-07 11:59:00 [195] DTV1 Transfer is set to: Bulk
2024-11-07 11:59:01 [196] Autostarting scripts in /etc/sundtek/
2024-11-07 11:59:02 [196] executed all available items
2024-11-07 11:59:02 [196] trying to load uinput module
2024-11-07 11:59:02 [196] loading uinput kernel extention failed, remote control will not work with lirc
2024-11-07 11:59:02 [195] No remote control support available
2024-11-07 11:59:02 [195] Initializing SYSV-IPC
2024-11-07 11:59:02 [195] Allocation using pg for type 65678
2024-11-07 11:59:02 [195] Allocated Shared memory buffer: 0x7f8f813000
2024-11-07 11:59:02 [195]
2024-11-07 11:59:02 [195] This device is using the new voltage control mechanism
2024-11-07 11:59:02 [195] Hardcoded limit 500mA
2024-11-07 11:59:02 [195] Vertical Polarisation is set to 13.00 Volt
2024-11-07 11:59:02 [195] Horizontal Polarisation is set to 19.80 Volt
2024-11-07 11:59:02 [195] Current limit is set to 1000 mA
2024-11-07 11:59:02 [195]
2024-11-07 11:59:02 [195] demodulator successfully attached (DVB_S/S2)!
2024-11-07 11:59:02 [195] Allocated Shared memory buffer: 0x7f8f7ad000
2024-11-07 11:59:02 [195] Allocated Shared memory buffer: 0x7f8f154000
2024-11-07 11:59:02 [195] Allocation using pg for type 16
2024-11-07 11:59:02 [195] Allocated Shared memory buffer: 0x7f8f06e000
2024-11-07 11:59:02 [195] Setting up default decoder settings
2024-11-07 11:59:02 [195] attaching video decoder
2024-11-07 11:59:03 [195] Configure urbs for bulk
2024-11-07 11:59:03 [195] Registering OSS emulation
2024-11-07 11:59:03 [195] registering: adapter0/0
2024-11-07 11:59:03 [195] registered virtual: /dev/dvb/adapter0/frontend0
2024-11-07 11:59:03 [195] registered virtual: /dev/dvb/adapter0/demux0
2024-11-07 11:59:03 [195] registered virtual: /dev/dvb/adapter0/dvr0
2024-11-07 11:59:03 [195] registered virtual: /dev/dsp0
2024-11-07 11:59:03 [195] registered virtual: /dev/video0
2024-11-07 11:59:03 [195] registered virtual: /dev/vbi0
2024-11-07 11:59:03 [195] Initializing Remote Control Support



on the other hand, this is what dmesg on the host (not inside container) says, and it's much more verbose this time.

[1553838.984414] docker0: port 5(veth530535f) entered disabled state
[1573794.834967] meson6-dwmac ff3f0000.ethernet eth0: Link is Down
[1573797.906832] meson6-dwmac ff3f0000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx
[1590976.267703] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 187 len 2 ret -71
[1590976.267976] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 187 len 1 ret -71
[1590976.268160] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 192 rq 187 len 1 ret -71
[1590976.268291] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 187 len 2 ret -71
[1590976.268776] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 187 len 1 ret -71
[1590976.268940] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 192 rq 187 len 1 ret -71
[1590976.269019] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 187 len 1 ret -71
[1590976.269161] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 192 rq 187 len 1 ret -71
[1590976.269290] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 187 len 1 ret -71
[1590976.269421] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 192 rq 187 len 1 ret -71
[1590976.269495] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 187 len 1 ret -71
[1590976.270440] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 192 rq 187 len 1 ret -71
[1590976.270553] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 187 len 1 ret -71
[1590976.270776] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 192 rq 187 len 1 ret -71
[1590976.270919] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 187 len 1 ret -71
[1590976.271360] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 192 rq 187 len 1 ret -71
[1590976.271493] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 187 len 1 ret -71
[1590976.271776] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 192 rq 187 len 1 ret -71
[1590976.271891] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 187 len 1 ret -71
[1590976.272077] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 192 rq 187 len 1 ret -71
[1590976.272153] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 187 len 1 ret -71
[1590976.272310] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 192 rq 187 len 1 ret -71
[1590976.272395] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 187 len 1 ret -71
[1590976.272572] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 192 rq 187 len 1 ret -71
[1590976.279730] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 187 len 1 ret -71
[1590976.279976] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 192 rq 187 len 1 ret -71
[1590976.280108] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 187 len 1 ret -71
[1590976.280293] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 192 rq 187 len 1 ret -71
[1590976.280374] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 187 len 1 ret -71
[1590976.280568] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 192 rq 187 len 1 ret -71
[1590976.280672] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 187 len 1 ret -71
[1590976.280862] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 192 rq 187 len 1 ret -71
[1590976.280946] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 187 len 1 ret -71
[1590976.281158] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 192 rq 187 len 1 ret -71
[1590976.328307] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 187 len 1 ret -71
[1590976.328625] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 192 rq 187 len 1 ret -71
[1590976.328763] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 187 len 1 ret -71
[1590976.328930] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 192 rq 187 len 1 ret -71
[1590976.329014] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 187 len 1 ret -71
[1590976.329152] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 192 rq 187 len 1 ret -71
[1590976.329279] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 187 len 1 ret -71
[1590976.329414] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 192 rq 187 len 1 ret -71
[1590976.329488] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 187 len 1 ret -71
[1590976.330186] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 192 rq 187 len 1 ret -71
[1590976.379983] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 187 len 1 ret -71
[1590976.380267] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 192 rq 187 len 1 ret -71
[1590976.380396] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 187 len 1 ret -71
[1590976.380563] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 192 rq 187 len 1 ret -71
[1590976.380698] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 187 len 1 ret -71
[1590976.380833] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 192 rq 187 len 1 ret -71
[1590976.380960] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 187 len 1 ret -71
[1590976.381095] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 192 rq 187 len 1 ret -71
[1590976.381172] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 187 len 1 ret -71
[1590976.381350] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 192 rq 187 len 1 ret -71
[1590976.391340] usb 1-2.4: USB disconnect, device number 12
[1590976.669541] usb 1-2.4: new high-speed USB device number 13 using xhci-hcd
[1590982.005279] usb 1-2.4: device descriptor read/64, error -71
[1590983.997597] usb 1-2-port4: Cannot enable. Maybe the USB cable is bad?
[1590984.101107] usb 1-2.4: new high-speed USB device number 14 using xhci-hcd
[1590984.901077] usb 1-2.4: device descriptor read/64, error -71
[1590985.865019] usb 1-2.4: device descriptor read/64, error -71
[1590985.973621] usb 1-2-port4: attempt power cycle
[1590987.261280] usb 1-2-port4: Cannot enable. Maybe the USB cable is bad?
[1590987.828853] usb 1-2.4: new high-speed USB device number 16 using xhci-hcd
[1590987.828903] usb 1-2.4: Device not responding to setup address.
[1590988.036993] usb 1-2.4: Device not responding to setup address.
[1590988.244808] usb 1-2.4: device not accepting address 16, error -71
[1590988.245781] usb 1-2.4: the parent's name is 1-2
[1590988.245851] usb 1-2-port4: Device no response
[1590988.251507] usb 1-2-port4: unable to enumerate USB device
[1590989.373206] usb 1-2-port4: Cannot enable. Maybe the USB cable is bad?
[1590989.476752] usb 1-2.4: new high-speed USB device number 18 using xhci-hcd
[1590991.708653] usb 1-2.4: device descriptor read/64, error -71
[1590994.544441] usb 1-2.4: device descriptor read/64, error -71
[1590994.652669] usb 1-2-port4: attempt power cycle
[1590995.304421] usb 1-2.4: new high-speed USB device number 19 using xhci-hcd
[1590999.458932] usb 1-2.4: device descriptor read/8, error -71
[1590999.585354] usb 1-2.4: device descriptor read/8, error -71
[1591000.028140] usb 1-2.4: new high-speed USB device number 20 using xhci-hcd
[1591005.163850] usb 1-2.4: device descriptor read/8, error -110
[1591005.345653] usb 1-2.4: device descriptor read/8, error -71
[1591005.451983] usb 1-2.4: the parent's name is 1-2
[1591005.452052] usb 1-2-port4: Device no response
[1591005.452103] usb 1-2-port4: unable to enumerate USB device
[1591005.703772] usb 1-2.4: new high-speed USB device number 21 using xhci-hcd
[1591010.899452] usb 1-2.4: device descriptor read/64, error -110
[1591010.899818] usb 1-2.4: Device no response
[1591017.967046] usb 1-2.4: device descriptor read/64, error -71
[1591018.178972] usb 1-2.4: new high-speed USB device number 22 using xhci-hcd
[1591023.442692] usb 1-2.4: device descriptor read/64, error -110
[1591023.443074] usb 1-2.4: Device no response
[1591039.057717] usb 1-2.4: device descriptor read/64, error -110
[1591039.058100] usb 1-2.4: Device no response
[1591039.169904] usb 1-2-port4: attempt power cycle
[1591039.821672] usb 1-2.4: new high-speed USB device number 23 using xhci-hcd
[1591045.097354] usb 1-2.4: device descriptor read/8, error -110
[1591050.473056] usb 1-2.4: device descriptor read/8, error -110
[1591050.684975] usb 1-2.4: new high-speed USB device number 24 using xhci-hcd
[1591055.848729] usb 1-2.4: device descriptor read/8, error -110
[1591061.224396] usb 1-2.4: device descriptor read/8, error -110
[1591061.332886] usb 1-2.4: the parent's name is 1-2
[1591061.332959] usb 1-2-port4: Device no response
[1591061.333009] usb 1-2-port4: unable to enumerate USB device

I have 2 tuners (skytv and dual, I was waiting for quad tuner which never was released), connected via USB hub, I'll remove the older skytv dongle and USB hub and will connect it directly to my home linux NAS which has sadly only one USB port (...) and will observe if that's not the USB hub causing this.

ok, it happened twice in past few days. this is output from dmesg

[829781.271485] usb 1-2.4: usbfs: usb_submit_urb returned -19
[829781.271488] usb 1-2.4: USB disconnect, device number 9
[829781.549966] usb 1-2.4: new high-speed USB device number 10 using xhci-hcd
[829781.675198] usb 1-2.4: New USB device found, idVendor=2659, idProduct=1802
[829781.675204] usb 1-2.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[829781.675207] usb 1-2.4: Product: Dual S2
[829781.675209] usb 1-2.4: Manufacturer: Sundtek
[829781.675212] usb 1-2.4: SerialNumber: U220618172741
[829781.683682] usb 1-2.4: Unsupported device
[830891.207803] usb 1-2.4: USB disconnect, device number 10
[830891.482322] usb 1-2.4: new high-speed USB device number 11 using xhci-hcd
[830891.607588] usb 1-2.4: New USB device found, idVendor=2659, idProduct=1802
[830891.607595] usb 1-2.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[830891.607597] usb 1-2.4: Product: Dual S2
[830891.607600] usb 1-2.4: Manufacturer: Sundtek
[830891.607603] usb 1-2.4: SerialNumber: U220618172741
[830891.618709] usb 1-2.4: Unsupported device

I only enabled the debug logging of the sundtek driver after first time it happened, so the driver debug log should have at least one set of events recorded, if I'm lucky. where should I look for the driver debug log file?

nevermind, I think I found it.

*/1 * * * * /usr/bin/timeout 1m bash -c "dmesg -w | tail -f | grep -qsm 1 'Sundtek' && docker exec tvh /opt/bin/mediaclient --shutdown && sleep 10 && docker exec tvh /opt/bin/mediaclient --start"

I'll try to restart it using crontab this way.

Build date is 2021-08-03 07:12:24, so it says. I downloaded driver and installed driver using the instructions in top of the sundtek.com page.

I created the /etc/sundtek.conf, with loglevel=max inside, inside the TVH container.
the file /var/log/mediasrv.log exist inside the container and at the host, but it's empty right now.
do I need to restart the container so the new loglevel setting is applied?

the tuner disconnect happened without my action, it always does. last time I stopped the container and re-plugged dual tuner in the USB port, then started the container and the tuner was again available in TVH.

next time this happens, I'll try to reach you via chat first.
thanks for support.

next time it happens I'll try dmesg. thanks for hint.

and I have both tuners plugged to AC mains with the provided adapter as well.
so they are not only powered from USB port, does it still matter what's the system's input power source rating?

I have Odroid HC4 with 4A AC, laptop like, adapter. so I guess it should be enough, even it's running two 3.5" HDDs.

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.