A lot of continuity errors on some muxes

pavelpl · 2024-08-19T23:07:06+00:00

Hi! I have been using TVH with a tuner (https://www.linuxtv.org/wiki/index.php/Technisat_SkyStar_USB_HD) to receive satellite TV for several years. Recently...

Jonas Lang

pavelpl I noticed an error on the output of dmesg

Technisat USB2 I2C-error 60=7

https://lore.kernel.org/all/5434226B.3010804@gmx.net/t/

I’ve attached an old thread that relates to this error. I know you said you’ve updated nothing recently but I’m not convinced.

Could you unplug and plug back in your tuner and do dmesg again. I want to see if it’s in warm or cold state when you do this. Just paste the output here again when you do that.

pavelpl

Jonas Lang Here is fresh dmesg after plugging usb:

$ sudo dmesg | grep -E 'dvb|usb|techn'
[ 4667.136814] dvb-usb: error -71 while querying for an remote control event. [ 4667.193366] technisat-usb2: i2c-error: out failed 68 = -71 [ 4667.193641] technisat-usb2: i2c-error: out failed 68 = -71 [ 4667.240983] dvb-usb: error -71 while querying for an remote control event. [ 4667.311819] usb 3-4.1: USB disconnect, device number 4 [ 4667.327793] technisat-usb2: i2c-error: out failed 68 = -19 [ 4667.327799] technisat-usb2: i2c-error: out failed 68 = -19 [ 4667.327800] technisat-usb2: i2c-error: out failed 68 = -19 [ 4667.329071] dvb-usb: Technisat SkyStar USB HD (DVB-S/S2) successfully deinitialized and disconnected. [ 4670.330711] usb 3-4.1: new high-speed USB device number 6 using xhci_hcd [ 4670.434828] usb 3-4.1: New USB device found, idVendor=14f7, idProduct=0500, bcdDevice= 0.01 [ 4670.434846] usb 3-4.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 4670.434854] usb 3-4.1: Product: TechniSat USB device [ 4670.434861] usb 3-4.1: Manufacturer: TechniSat Digital [ 4670.434869] usb 3-4.1: SerialNumber: 0008C9F0422A [ 4670.438727] technisat-usb2: set alternate setting [ 4670.438801] technisat-usb2: firmware version: 17.63 [ 4670.438803] dvb-usb: found a 'Technisat SkyStar USB HD (DVB-S/S2)' in warm state. [ 4670.439101] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. [ 4670.439233] dvbdev: DVB: registering new adapter (Technisat SkyStar USB HD (DVB-S/S2)) [ 4670.439236] usb 3-4.1: media controller created [ 4670.440672] dvb-usb: MAC address: 00:08:c9:f0:42:2a [ 4670.440899] dvbdev: dvb_create_media_entity: media entity 'dvb-demux' registered. [ 4670.623648] usb 3-4.1: DVB: registering adapter 0 frontend 0 (Technisat SkyStar USB HD (DVB-S/S2))... [ 4670.623685] dvbdev: dvb_create_media_entity: media entity 'Technisat SkyStar USB HD (DVB-S/S2)' registered. [ 4670.624375] Registered IR keymap rc-technisat-usb2 [ 4670.624427] rc rc0: Technisat SkyStar USB HD (DVB-S/S2) as /devices/pci0000:00/0000:00:14.0/usb3/3-4/3-4.1/rc/rc0 [ 4670.624527] rc rc0: lirc_dev: driver technisat-usb2 registered at minor = 0, raw IR receiver, no transmitter [ 4670.624603] input: Technisat SkyStar USB HD (DVB-S/S2) as /devices/pci0000:00/0000:00:14.0/usb3/3-4/3-4.1/rc/rc0/input5 [ 4670.624857] dvb-usb: schedule remote query interval to 100 msecs. [ 4670.625105] dvb-usb: Technisat SkyStar USB HD (DVB-S/S2) successfully initialized and connected.
I must mention that after i plug USB again, I can't play any chanel. In TVH in Configuration -> DVB Inputs -> TV adapters I have red dot next to this adapter. I have to restart LXC container to make it work.

Jonas Lang

pavelpl that hasn’t gone to cold state and reloaded the firmware. I’m suspecting the issue lies with the fact you’re using TVH on a VM and something in the chain was updated recently. This is a similar issue to the one you describe https://forums.virtualbox.org/viewtopic.php?p=277872

pavelpl

Previous dmesg was from LXC container from my serwer this one is when i plug tuner on my laptopto test via VLC/Kaffeine:
[ 9443.918215] usb 3-6: new high-speed USB device number 13 using xhci_hcd [ 9444.045248] usb 3-6: New USB device found, idVendor=14f7, idProduct=0500, bcdDevice= 0.01 [ 9444.045263] usb 3-6: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 9444.045266] usb 3-6: Product: TechniSat USB device [ 9444.045269] usb 3-6: Manufacturer: TechniSat Digital [ 9444.045271] usb 3-6: SerialNumber: 0008C9F0422A [ 9444.048884] technisat-usb2: set alternate setting [ 9444.049073] technisat-usb2: firmware version: 17.63 [ 9444.049077] dvb-usb: found a 'Technisat SkyStar USB HD (DVB-S/S2)' in warm state. [ 9444.049509] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. [ 9444.049778] dvbdev: DVB: registering new adapter (Technisat SkyStar USB HD (DVB-S/S2)) [ 9444.049785] usb 3-6: media controller created [ 9444.051332] dvb-usb: MAC address: 00:08:c9:f0:42:2a [ 9444.051801] dvbdev: dvb_create_media_entity: media entity 'dvb-demux' registered. [ 9444.157363] i2c i2c-15: Attaching STV6110x [ 9444.159129] technisat-usb2: i2c-error: 60 = 7 [ 9444.222675] usb 3-6: DVB: registering adapter 0 frontend 0 (Technisat SkyStar USB HD (DVB-S/S2))... [ 9444.222698] dvbdev: dvb_create_media_entity: media entity 'Technisat SkyStar USB HD (DVB-S/S2)' registered. [ 9444.223579] Registered IR keymap rc-technisat-usb2 [ 9444.223635] rc rc0: Technisat SkyStar USB HD (DVB-S/S2) as /devices/pci0000:00/0000:00:14.0/usb3/3-6/rc/rc0 [ 9444.223739] rc rc0: lirc_dev: driver technisat-usb2 registered at minor = 0, raw IR receiver, no transmitter [ 9444.223802] input: Technisat SkyStar USB HD (DVB-S/S2) as /devices/pci0000:00/0000:00:14.0/usb3/3-6/rc/rc0/input36 [ 9444.224465] dvb-usb: schedule remote query interval to 100 msecs. [ 9444.224693] dvb-usb: Technisat SkyStar USB HD (DVB-S/S2) successfully initialized and connected.

pavelpl

Jonas Lang Yes, but:

1) the problem exist even when I use this tuner on different machine (laptop) and different app.
2) I use container not VM. Container is using bare matal hardware but in isolation. I have tried VMs in the past but there was problem with passthrough USB to it (similiar issues like this from above link) There is a solution for that - passthrough whole usb controller not only USB device.

Jonas Lang

pavelpl I only use TVH directly on the machine via Ubuntu OS. No need for VM, Dockers or any other containers.

As I mentioned above I’m not convinced your tuner is at fault and while buying a different model on eBay might make sense it’s a crap shoot. Does it work, is it the correct revision etc,etc. Keep looking out for a Sat/IP tuner. I got a Digibit Twin new for €70 recently.

pavelpl

This DigiBit is fair offer but it's out of stock everywhere 🙂. Why do you think tuner is not broken ?

Jonas Lang

pavelpl I’ve seen similar issues to the one you are experiencing and it usually comes down to kernel/firmware/driver issues. The I2C error raises concerns too.

Have you tried swapping around the tuner on different USB ports on your computer or removing other USB devices in case they are causing conflicts.

Don’t waste money buying another tuner unless you are sure it will work in Linux. Some retailers do have older revisions of USB tuners in stock but you need to confirm the vendor id

From your original post could you confirm if you are having the difficulties with channels that are DVBS or DVBS2

Jonas Lang

Again another post reporting continuity errors on certain muxes and only being reported quite recently. Are you using Astra 19.2 to tune muxes too.

You can see there’s so many variables involved in trying isolate your issue. That particular tuner you use is quite sensitive so any minor changes to infrastructure may well be causing your issue

https://tvheadend.org/d/8276-continuity-errors-on-tbs6904-on-dvb-s2

pavelpl

Jonas Lang I've done some reboots, changing ports etc. and now there is no i2c errors in logs, but issue is still here 🙂 I'm using Hotbird 13. I read that few monts ago they migrate to some new sattelites Hot Bird 13F i Hot Bird 13G, maybe it's related. Problem I have refers to DVB-S2.

Jonas Lang

pavelpl could I suggest trying your tuner on a Windows machine if you haven’t already done so. I’m curious to see what signal strength and signal quality it reports.

It may well be that the firmware in Linux is no longer functioning correctly with your tuner in a particular kernel. A Windows session may well prove this.

Do bear in mind your tuner is quite old and there will be no further development work done on it in Linux for obvious reasons. You may need to purchase a more suitable tuner.

pavelpl

Jonas Lang Could you recomend some app for widnows?

pavelpl

Jonas Lang It was good idea to check it on Windows. It seems to work ...

Jonas Lang

pavelpl as I suspected. Your tuner is working and It’s definitely a Linux issue. You’ve now proven that by testing and working in Windows.

I’ve a feeling I saw a Linux patch created to resolve that issue somewhere. Keep searching the web and you may come across it. I’ll search a bit more when I have the time.

Jonas Lang

Jonas Lang just one more question. In Linux are you using a USB hub powered or passive to connect your USB devices

pavelpl

Jonas Lang Passive

Jonas Lang

pavelpl I reckon that’s your problem so. Try removing the passive hub and plugging the tuner directly into the PC USB port. Let me know what happened.

pavelpl

Jonas Lang I've switched tuner from hub directly into USB on the machine and it's the same. I even changed usb cable to another one to eliminate this factor.

Jonas Lang

pavelpl I’ve come across this. Again change of kernel causing issue with this tuner raspberrypi/linux2886

Jonas Lang

A final note on this tuner. This is the patch I remember seeing. Again you’ll need a good working knowledge of Linux to apply this patch but it does look like it will resolve the issue of not being able to tune DVBS2 channels.
https://www.linuxtv.org/wiki/index.php/Technisat_SkyStar_USB_2_HD_CI

« Previous Page