8 hours ago, cRyyy said:

unraid verison: 6.11.5 

dvb-plugin version: 2022.07.20

Please post your Diagnostics.

3 hours ago, ich777 said:

Please post your Diagnostics.

unraid-diagnostics-20230408-1042.zip

1 hour ago, cRyyy said:

unraid-diagnostics-20230408-1042.zip 156.29 kB · 0 downloads

Please append this to your syslinux.conf and reboot:

16 minutes ago, ich777 said:

Please append this to your syslinux.conf and reboot:

thanks, but no improvment. attached the new diagnostics unraid-diagnostics-20230408-1202.zip

9 minutes ago, cRyyy said:

thanks, but no improvment. attached the new diagnostics unraid-diagnostics-20230408-1202.zip

Please remember if you try the card in a different system woth a different OS that this is not saying much because what matters it the combination of the current hardware.

 

You are the first who is reporting such an error for 6.11.5 and the driver doesn’t change for a Unraid version.

I knew a few people who having none issues with this card/driver on 6.11.5

 

The only thing that I can recommend is that you create an Issue on GitHub from TBS.
Do you made sure that you disabled power saving in TVHeadend?

6 minutes ago, ich777 said:

Please remember if you try the card in a different system woth a different OS that this is not saying much because what matters it the combination of the current hardware.

 

You are the first who is reporting such an error for 6.11.5 and the driver doesn’t change for a Unraid version.

I knew a few people who having none issues with this card/driver on 6.11.5

 

The only thing that I can recommend is that you create an Issue on GitHub from TBS.
Do you made sure that you disabled power saving in TVHeadend?

power saving is disabled.

any errors or something in the diagnostics? 

any setting i should check in the BIOS?

2 minutes ago, cRyyy said:

any errors or something in the diagnostics? 

Nothing yet.

Please also make sure that the signal quality is decent.

 

BTW the error from previously was not caused by the TV card whatsoever, it was caused by another device in your system but could cause also troubles for your TV card since the timings for those must be perfect.

 

I really don't know what you could try, I just saw that you are using a Gigabyte board which are not the best in terms for BIOS support and have many bugs in them, at least that's my experience with them.

Back then (Sandy Bridge) I've also had a Gigabyte board where I had stutters and issues like you've described after I switched to a ASUS board everything was running smoothly again <- I used DigitalDevices cards in that case.

 

I can only recommend that you post an issue here with the exact description and with the syslog.txt, lscpci.txt, lscpu.txt and motherboard.txt from your Diagnostics.

You can also try to move the card to a different PCIe slot and see if that makes a difference.

Of course also make sure that you are on the latest BIOS version.

 

Before that you could also try to enable/disable various settings from the PCIe sub menu in your BIOS and see if that makes a difference.

 

Maybe someone over on GitHub knows how to solve that.

50 minutes ago, ich777 said:

Nothing yet.

Please also make sure that the signal quality is decent.

 

BTW the error from previously was not caused by the TV card whatsoever, it was caused by another device in your system but could cause also troubles for your TV card since the timings for those must be perfect.

 

I really don't know what you could try, I just saw that you are using a Gigabyte board which are not the best in terms for BIOS support and have many bugs in them, at least that's my experience with them.

Back then (Sandy Bridge) I've also had a Gigabyte board where I had stutters and issues like you've described after I switched to a ASUS board everything was running smoothly again <- I used DigitalDevices cards in that case.

 

I can only recommend that you post an issue here with the exact description and with the syslog.txt, lscpci.txt, lscpu.txt and motherboard.txt from your Diagnostics.

You can also try to move the card to a different PCIe slot and see if that makes a difference.

Of course also make sure that you are on the latest BIOS version.

 

Before that you could also try to enable/disable various settings from the PCIe sub menu in your BIOS and see if that makes a difference.

 

Maybe someone over on GitHub knows how to solve that.

thanks for your help, i update my BIOS from F4 to F5 (latest) and now the erros are gone and no flickering : )

3 minutes ago, cRyyy said:

thanks for your help, i update my BIOS from F4 to F5 (latest) and now the erros are gone and no flickering : )

But since you are using a Gigabyte board you are introducing most certainly other bugs...

Hi I am using Sundtek usb dvbt/c dongle single tuner and seem to have some issues with getting it detected.

I have installed both dvb-drvers and sundtek-driver plugins and the adapter is detected and showing as 

Detected Adapters:

adapter0

 

Set Extra Parameters: to "--device=/dev/bus/usb"

 

and added extra path as suggested

 

However it is still not showing up in binhex-tvheadend as a tuner. Do I need to delete one of the driver plugins or am I missing another step? Have rebooted server after driver install.

 

server-diagnostics-20230419-1135.zip lsusb.txt dmesg.txt

Edited April 19, 20233 yr by bally12345

1 hour ago, bally12345 said:

Set Extra Parameters: to "--device=/dev/bus/usb"

Do you also added the device path: /dev/dvb to the container template?

 

Did you follow the guide on how to install everything? I don't see the device in /dev/dvb

24 minutes ago, ich777 said:

Do you also added the device path: /dev/dvb to the container template?

 

Did you follow the guide on how to install everything? I don't see the device in /dev/dvb

 

No in fact I read you need to have that but not sure how you have both if im honest

5 minutes ago, bally12345 said:

No in fact I read you need to have that but not sure how you have both if im honest

Oh wait, I don't know if it is working with the binhex container since I don't know how he starts it and the sundtek driver installation script (which is pulled from sundtek itself) hacks into the startup routine...

 

Anyways you can try it, simply go in the Docker template and at the bottom click on " Add another Path, Port, Variable, Label or Device" from the drop down select "Device" at "Value" enter the path (eg: "/dev/dvb") click "Add" and "Apply".

 

You could also add the second device path like that so that you don't have to use the Extra Parameters.

 

5 minutes ago, ich777 said:

Oh wait, I don't know if it is working with the binhex container since I don't know how he starts it and the sundtek driver installation script (which is pulled from sundtek itself) hacks into the startup routine...

 

Anyways you can try it, simply go in the Docker template and at the bottom click on " Add another Path, Port, Variable, Label or Device" from the drop down select "Device" at "Value" enter the path (eg: "/dev/dvb") click "Add" and "Apply".

 

You could also add the second device path like that so that you don't have to use the Extra Parameters.

 

Unfortunately it didnt work, just tried with LSIO too but same. Nothing showing.

 

Tried adding adapter0 too which is showed on the driver plugin page

 

3 minutes ago, bally12345 said:

Tried adding adapter0 too which is showed on the driver plugin page

Please don't specify things that are already specified with the upper path, you just need /dev/dvb and /dev/bus/usb all other paths are not necessary, did you also pass through the script as described on the plugin page.

Did you also specify the exact name of the container when running the installer from the plugin page (case sensitive)?

Hi started again from fresh it is now working!!

Many thanks

Just now, bally12345 said:

Hi started again from fresh it is now working!!

@binhex how do you start your container in the Docker container? Does your container also support custom start scripts like it is for the linxuserver container in /etc/cont-init.d/ ?

 

These two things would be trivial for the Sundtek plugin to work properly.

Quick one from me, all of a sudden the lsio tvheadend container refuses to connect and I get the following in my logs

 

Apr 19 17:36:54 Server kernel: mediasrv[26610]: segfault at 4 ip 0000000000418457 sp 0000146db352f0f8 error 4 in mediasrv[405000+3c000] likely on CPU 0 (core 0, socket 0)

 

is this driver related or container issue?

 

Tried again with binhex container and same

 

Apr 19 17:56:29 Server emhttpd: cmd: /usr/local/emhttp/plugins/sundtek-driver/include/install.sh binhex-tvheadend
Apr 19 17:56:30 Server kernel: process 'e72a9e0ac073aef54ee2c88eb355e1f7bed5fc3aa8941b46831b1b2445b34d97/tmp/.sundtek/chk64bit' started with executable stack
Apr 19 17:56:34 Server kernel: docker0: port 9(vethac0d4c3) entered disabled state
Apr 19 17:56:34 Server kernel: vethfa70f9d: renamed from eth0
Apr 19 17:56:34 Server avahi-daemon[10418]: Interface vethac0d4c3.IPv6 no longer relevant for mDNS.
Apr 19 17:56:34 Server avahi-daemon[10418]: Leaving mDNS multicast group on interface vethac0d4c3.IPv6 with address fe80::9488:3cff:fe05:b643.
Apr 19 17:56:34 Server kernel: docker0: port 9(vethac0d4c3) entered disabled state
Apr 19 17:56:34 Server kernel: device vethac0d4c3 left promiscuous mode
Apr 19 17:56:34 Server kernel: docker0: port 9(vethac0d4c3) entered disabled state
Apr 19 17:56:34 Server avahi-daemon[10418]: Withdrawing address record for fe80::9488:3cff:fe05:b643 on vethac0d4c3.
Apr 19 17:56:34 Server kernel: docker0: port 9(veth60ddc49) entered blocking state
Apr 19 17:56:34 Server kernel: docker0: port 9(veth60ddc49) entered disabled state
Apr 19 17:56:34 Server kernel: device veth60ddc49 entered promiscuous mode
Apr 19 17:56:34 Server kernel: docker0: port 9(veth60ddc49) entered blocking state
Apr 19 17:56:34 Server kernel: docker0: port 9(veth60ddc49) entered forwarding state
Apr 19 17:56:35 Server kernel: eth0: renamed from vethb74e2d7
Apr 19 17:56:35 Server kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth60ddc49: link becomes ready
Apr 19 17:56:36 Server avahi-daemon[10418]: Joining mDNS multicast group on interface veth60ddc49.IPv6 with address fe80::6cf1:a5ff:fe73:2a6a.
Apr 19 17:56:36 Server avahi-daemon[10418]: New relevant interface veth60ddc49.IPv6 for mDNS.
Apr 19 17:56:36 Server avahi-daemon[10418]: Registering new address record for fe80::6cf1:a5ff:fe73:2a6a on veth60ddc49.*.
Apr 19 17:56:37 Server kernel: mediasrv[11875]: segfault at 4 ip 0000000000413bd7 sp 000014c46bdfcc88 error 4 in mediasrv[400000+69000] likely on CPU 11 (core 10, socket 1)
Apr 19 17:56:37 Server kernel: Code: 89 70 20 48 89 50 28 31 c0 c3 48 89 70 30 48 89 50 38 31 c0 c3 66 66 66 66 66 2e 0f 1f 84 00 00 00 00 00 48 8b 87 c0 c5 00 00 <8b> 40 04 c3 0f 1f 44 00 00 48 8b 87 c0 c5 00 00 8b 00 c3 66 0f 1f

 

Edited April 19, 20233 yr by bally12345

55 minutes ago, bally12345 said:

is this driver related or container issue?

Can you try to reboot your server?

 

Did you change anything? I thought it was working? Are you sure that USB Tuner is still connected and that the USB cable has no defect and plugged in all the way?

14 hours ago, ich777 said:

Can you try to reboot your server?

 

Did you change anything? I thought it was working? Are you sure that USB Tuner is still connected and that the USB cable has no defect and plugged in all the way?

 

Hi it was showing as connected but after reboot it disappeared. Then after another reboot came back. I think it is a faulty device now. It is probably about 8years old and happen to find it again last week so thought I would try it.

17 minutes ago, bally12345 said:

It is probably about 8years old and happen to find it again last week so thought I would try it.

Please check the USB Extension or change the USB port where it is plugged in, often times the extension cable can be faulty too if you are using one.

4 hours ago, ich777 said:

Please check the USB Extension or change the USB port where it is plugged in, often times the extension cable can be faulty too if you are using one.

Yep I am using one! You might be right... Will try plugging directly into back of server.

Unable to plugin directly due to size and vga plug next to it.

Tried another shorter extension cable but same.

Anyone able to recommend a dual or greater pci card for dvbt2 but must be low profile to fit in 2u chassis

Sent from my SM-G991B using Tapatalk

32 minutes ago, bally12345 said:

Anyone able to recommend a dual or greater pci card for dvbt2 but must be low profile to fit in 2u chassis

I would recommend DigitalDevices or Sundtek, I really can't recommend TBS anymore because of their drivers and lacking support.

I would recommend DigitalDevices or Sundtek, I really can't recommend TBS anymore because of their drivers and lacking support.

I had a little play around but for some reason the adapter is detected in unraid but the blue activity light does come on.

Tried the same adapter in my Vu+ Zero enigma2 box and the blue light comes on fine.

Sent from my SM-G991B using Tapatalk