No input Signal -- DVBSky T680CI -- All in a sudden, suspect after Pi update?
Added by Jeroen Lindhout over 3 years ago
Dear all,
My set-up used to be working perfectly, but since a month or 2 it stopped working. I suspect after a Raspberry Pi update, but I can not seem to figure out what the problem is, as everything looks good to my opinion.
Any further suggestions, highly appreciated.
Some configuration details, and output.
When using a TVheadend client (Kodi) I now get the error message "No Signal".
First of all, the error I see in tvheadend.log
2021-03-15 15:47:18.722 [ INFO]:subscription: 00AB: "scan" subscribing to mux "474MHz", weight: 6, adapter: "Silicon Labs Si2168 #0 : DVB-C #0", network: "DVB-C Network", service: "Raw PID Subscription"
2021-03-15 15:47:23.716 [ INFO]:mpegts: 474MHz in DVB-C Network - scan no data, failed
2021-03-15 15:47:23.717 [ INFO]:subscription: 00AB: "scan" unsubscribing
2021-03-15 15:47:57.701 [ INFO]:http: 192.168.178.211: using ticket E3BBF9DA1FFEA8FA0E0B60FCF019D000FF390C0C for /stream/service/2080112d62fdb7a5d1c044ed24b02560
2021-03-15 15:47:57.701 [ INFO]:mpegts: 410MHz in DVB-C Network - tuning on Silicon Labs Si2168 #0 : DVB-C #0
2021-03-15 15:47:57.702 [ INFO]:subscription: 00AC: "HTTP" subscribing to service "DVB-C Network/410MHz/NPO 1", weight: 100, adapter: "Silicon Labs Si2168 #0 : DVB-C #0", network: "DVB-C Network", mux: "410MHz", provider: "Ziggo", profile="pass", hostname="192.168.178.211", username="#####", client="Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_6) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/14.0.3 Safari/605.1.15"
2021-03-15 15:48:03.701 [WARNING]:subscription: 00AC: service instance is bad, reason: No input detected
2021-03-15 15:48:05.702 [ NOTICE]:subscription: 00AC: No input source available for subscription "HTTP" to service "DVB-C Network/410MHz/NPO 1" in mux "410MHz in DVB-C Network"
2021-03-15 15:48:05.702 [WARNING]:webui: Couldn't start streaming /stream/service/2080112d62fdb7a5d1c044ed24b02560?ticket=E3BBF9DA1FFEA8FA0E0B60FCF019D000FF390C0C, No input detected
2021-03-15 15:48:05.702 [ INFO]:subscription: 00AC: "HTTP" unsubscribing, hostname="192.168.178.211", username="admin", client="Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_6) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/14.0.3 Safari/605.1.15"
2021-03-15 15:48:05.743 [ INFO]:http: 192.168.178.211: using ticket E3BBF9DA1FFEA8FA0E0B60FCF019D000FF390C0C for /stream/service/2080112d62fdb7a5d1c044ed24b02560
2021-03-15 15:48:05.743 [ INFO]:mpegts: 410MHz in DVB-C Network - tuning on Silicon Labs Si2168 #0 : DVB-C #0
2021-03-15 15:48:05.744 [ INFO]:subscription: 00AD: "HTTP" subscribing to service "DVB-C Network/410MHz/NPO 1", weight: 100, adapter: "Silicon Labs Si2168 #0 : DVB-C #0", network: "DVB-C Network", mux: "410MHz", provider: "Ziggo", profile="pass", hostname="192.168.178.211", username="#####", client="Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_6) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/14.0.3 Safari/605.1.15"
2021-03-15 15:48:11.745 [WARNING]:subscription: 00AD: service instance is bad, reason: No input detected
The output of dmesg
pi@tvserver:~ $ dmesg | grep dvb
[ 5.594144] usb 1-1.4: dvb_usb_v2: found a 'DVBSky T680CI' in warm state
[ 5.594595] usb 1-1.4: dvb_usb_v2: will pass the complete MPEG2 transport stream to the software demuxer
[ 5.594651] dvbdev: DVB: registering new adapter (DVBSky T680CI)
[ 5.595996] usb 1-1.4: dvb_usb_v2: MAC address: 00:18:42:54:68:0c
[ 5.636174] dvbdev: dvb_create_media_entity: media entity 'dvb-demux' registered.
[ 5.811711] dvbdev: dvb_create_media_entity: media entity 'dvb-ca-en50221' registered.
[ 5.819443] dvbdev: dvb_create_media_entity: media entity 'Silicon Labs Si2168' registered.
[ 5.821457] Registered IR keymap rc-dvbsky
[ 5.821926] rc rc0: lirc_dev: driver dvb_usb_dvbsky registered at minor = 0, scancode receiver, no transmitter
[ 5.822507] usb 1-1.4: dvb_usb_v2: schedule remote query interval to 300 msecs
[ 5.822531] usb 1-1.4: dvb_usb_v2: 'DVBSky T680CI' successfully initialized and connected
[ 5.822716] usbcore: registered new interface driver dvb_usb_dvbsky
[ 11.373553] si2168 11-0064: downloading firmware from file 'dvb-demod-si2168-b40-01.fw'
[ 305.842494] dvb_ca_en50221: dvb_ca adapter 0: DVB CAM detected and initialised successfully
PI Kernel version / Pi Model 4B V1.2
Raspbian GNU/Linux 10 (buster)
@
pi_at_tvserver:~ $ apt-cache policy raspberrypi-kernel
raspberrypi-kernel:
Installed: 1.20210303-1
Candidate: 1.20210303-1
Version table:
*** 1.20210303-1 500
500 http://archive.raspberrypi.org/debian buster/main armhf Packages
100 /var/lib/dpkg/status
@
If I remember correctly, on the DVBSky receiver there used to be little light indicating "Signal Lock", this light is off right now.
To be sure I also changed the COAX cable.
Once again, many thanks for any thoughts someone might have.
Regards,
Jeroen
Replies (9)
RE: No input Signal -- DVBSky T680CI -- All in a sudden, suspect after Pi update? - Added by saen acro over 3 years ago
dmesg |egrep "firmware|dvb|frontend|usb"
Post result.
RE: No input Signal -- DVBSky T680CI -- All in a sudden, suspect after Pi update? - Added by Jeroen Lindhout over 3 years ago
Dear Saen,
Thanks for reaching out so fast....
Here the output
Spotting this error line, no clue what it means:
@
brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.txt failed with error -2
dmesg |egrep "firmware|dvb|frontend|usb"
[ 0.090937] raspberrypi-firmware soc:firmware: Attached to firmware from 2021-03-10T10:12:47, variant start
[ 0.100951] raspberrypi-firmware soc:firmware: Firmware hash is 4b9ea44619376439c801684745a12299b45ae2bb
[ 0.151619] usbcore: registered new interface driver usbfs
[ 0.151696] usbcore: registered new interface driver hub
[ 0.151785] usbcore: registered new device driver usb
[ 0.152136] usb_phy_generic phy: supply vcc not found, using dummy regulator
[ 1.395366] usbcore: registered new interface driver r8152
[ 1.395455] usbcore: registered new interface driver lan78xx
[ 1.395534] usbcore: registered new interface driver smsc95xx
[ 1.402102] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.10
[ 1.402143] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1.402180] usb usb1: Product: xHCI Host Controller
[ 1.402210] usb usb1: Manufacturer: Linux 5.10.20-v7l+ xhci-hcd
[ 1.402241] usb usb1: SerialNumber: 0000:01:00.0
[ 1.404487] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.10
[ 1.404527] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1.404562] usb usb2: Product: xHCI Host Controller
[ 1.404592] usb usb2: Manufacturer: Linux 5.10.20-v7l+ xhci-hcd
[ 1.404623] usb usb2: SerialNumber: 0000:01:00.0
[ 1.407959] usbcore: registered new interface driver uas
[ 1.408083] usbcore: registered new interface driver usb-storage
[ 1.419572] usbcore: registered new interface driver usbhid
[ 1.419603] usbhid: USB HID core driver
[ 1.774089] usb 1-1: new high-speed USB device number 2 using xhci_hcd
[ 1.956992] usb 1-1: New USB device found, idVendor=2109, idProduct=3431, bcdDevice= 4.21
[ 1.957040] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[ 1.957074] usb 1-1: Product: USB2.0 Hub
[ 2.114573] usb 2-1: new SuperSpeed Gen 1 USB device number 2 using xhci_hcd
[ 2.146405] usb 2-1: New USB device found, idVendor=0bc2, idProduct=ac25, bcdDevice= 0.04
[ 2.146450] usb 2-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[ 2.146493] usb 2-1: Product: BUP Portable
[ 2.146526] usb 2-1: Manufacturer: Seagate
[ 2.146555] usb 2-1: SerialNumber: 00000000NAB7D6H7
[ 2.314132] usb 1-1.2: new full-speed USB device number 3 using xhci_hcd
[ 2.460127] usb 1-1.2: New USB device found, idVendor=0403, idProduct=6001, bcdDevice= 6.00
[ 2.460182] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 2.460225] usb 1-1.2: Product: FT232R USB UART
[ 2.460256] usb 1-1.2: Manufacturer: FTDI
[ 2.460285] usb 1-1.2: SerialNumber: AQ00FCU7
[ 2.574156] usb 1-1.4: new high-speed USB device number 4 using xhci_hcd
[ 2.714935] usb 1-1.4: New USB device found, idVendor=0572, idProduct=680c, bcdDevice= 0.00
[ 2.714986] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 2.715025] usb 1-1.4: Product: T680C
[ 2.715055] usb 1-1.4: Manufacturer: Bestunar
[ 2.715085] usb 1-1.4: SerialNumber: 20130114
[ 5.465207] usbcore: registered new interface driver usbserial_generic
[ 5.465307] usbserial: USB Serial support registered for generic
[ 5.476428] usbcore: registered new interface driver ftdi_sio
[ 5.546047] usbcore: registered new interface driver brcmfmac
[ 5.587045] usbserial: USB Serial support registered for FTDI USB Serial Device
[ 5.587071] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.txt failed with error -2
[ 5.587481] usb 1-1.2: Detected FT232RL
[ 5.594144] usb 1-1.4: dvb_usb_v2: found a 'DVBSky T680CI' in warm state
[ 5.594595] usb 1-1.4: dvb_usb_v2: will pass the complete MPEG2 transport stream to the software demuxer
[ 5.594651] dvbdev: DVB: registering new adapter (DVBSky T680CI)
[ 5.594674] usb 1-1.4: media controller created
[ 5.595996] usb 1-1.4: dvb_usb_v2: MAC address: 00:18:42:54:68:0c
[ 5.607545] usb 1-1.2: FTDI USB Serial Device converter now attached to ttyUSB0
[ 5.636174] dvbdev: dvb_create_media_entity: media entity 'dvb-demux' registered.
[ 5.711202] vc4-drm gpu: bound fe600000.firmwarekms (ops vc4_fkms_ops [vc4])
[ 5.711470] si2168 11-0064: firmware version: B 4.0.2
[ 5.811711] dvbdev: dvb_create_media_entity: media entity 'dvb-ca-en50221' registered.
[ 5.819414] usb 1-1.4: DVB: registering adapter 0 frontend 0 (Silicon Labs Si2168)...
[ 5.819443] dvbdev: dvb_create_media_entity: media entity 'Silicon Labs Si2168' registered.
[ 5.821457] Registered IR keymap rc-dvbsky
[ 5.821664] rc rc0: DVBSky T680CI as /devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.4/rc/rc0
[ 5.821926] rc rc0: lirc_dev: driver dvb_usb_dvbsky registered at minor = 0, scancode receiver, no transmitter
[ 5.822209] input: DVBSky T680CI as /devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.4/rc/rc0/input0
[ 5.822507] usb 1-1.4: dvb_usb_v2: schedule remote query interval to 300 msecs
[ 5.822531] usb 1-1.4: dvb_usb_v2: 'DVBSky T680CI' successfully initialized and connected
[ 5.822716] usbcore: registered new interface driver dvb_usb_dvbsky
[ 11.373553] si2168 11-0064: downloading firmware from file 'dvb-demod-si2168-b40-01.fw'
[ 12.067121] si2168 11-0064: firmware version: B 4.0.11
[ 12.106204] si2157 12-0060: firmware version: 3.0.5
[ 12.116207] usb 1-1.4: DVB: adapter 0 frontend 0 frequency 0 out of range (48000000..870000000)
[ 12.163669] si2157 12-0060: firmware version: 3.0.5
[ 305.842494] dvb_ca_en50221: dvb_ca adapter 0: DVB CAM detected and initialised successfully
@
Best, Jeroen
RE: No input Signal -- DVBSky T680CI -- All in a sudden, suspect after Pi update? - Added by dorin ilut over 3 years ago
i think that with TBS you need to rebuild the drivers after every kernel update. Try rebuilding the drivers using the method on the TBS github page: https://github.com/tbsdtv/linux_media/wiki. I had more or less the same issue at the last update and i thought the card was defective.
RE: No input Signal -- DVBSky T680CI -- All in a sudden, suspect after Pi update? - Added by Jeroen Lindhout over 3 years ago
I will give this a try, and report results.
regards, Jeroen
RE: No input Signal -- DVBSky T680CI -- All in a sudden, suspect after Pi update? - Added by dorin ilut over 3 years ago
Jeroen,
My bad...i thought it was a TBS...but you should check this: https://www.linuxtv.org/wiki/index.php/DVBSky
RE: No input Signal -- DVBSky T680CI -- All in a sudden, suspect after Pi update? - Added by saen acro over 3 years ago
Do next
service tvheadend stop
then if not installed install wscan
and run
w_scan -f c -x
RE: No input Signal -- DVBSky T680CI -- All in a sudden, suspect after Pi update? - Added by Jeroen Lindhout over 3 years ago
Dear all,
Really appreciate your suggestions here, looking at the drivers, I did not find anything useful for the DVBSky on a Raspberry pi. However, the web-site sort of stopped mentioned support for kernel 4.4.
So I decided to roll-back by firmware. Not sure if it helps, but thought it should not harm either.
rpi-update 993f47507f287f5da56495f718c2d0cd05ccbc19
The error message listed above is gone now.
[ 1.657667] usb 1-1.4: Manufacturer: Bestunar [ 1.657691] usb 1-1.4: SerialNumber: 20130114 [ 4.037708] usbcore: registered new interface driver brcmfmac [ 4.175129] usbcore: registered new interface driver usbserial_generic [ 4.175201] usbserial: USB Serial support registered for generic [ 4.184938] usbcore: registered new interface driver ftdi_sio [ 4.185013] usbserial: USB Serial support registered for FTDI USB Serial Device [ 4.185400] usb 1-1.2: Detected FT232RL [ 4.205541] vc4-drm soc:gpu: bound fe600000.firmwarekms (ops vc4_fkms_ops [vc4]) [ 4.232188] usb 1-1.2: FTDI USB Serial Device converter now attached to ttyUSB0 [ 4.507538] usb 1-1.4: dvb_usb_v2: found a 'DVBSky T680CI' in warm state [ 4.508211] usb 1-1.4: dvb_usb_v2: will pass the complete MPEG2 transport stream to the software demuxer [ 4.508259] dvbdev: DVB: registering new adapter (DVBSky T680CI) [ 4.509537] usb 1-1.4: dvb_usb_v2: MAC address: 00:18:42:54:68:0c [ 4.548847] si2168 7-0064: firmware version: B 4.0.2 [ 4.617851] usb 1-1.4: DVB: registering adapter 0 frontend 0 (Silicon Labs Si2168)... [ 4.618168] Registered IR keymap rc-dvbsky [ 4.618290] rc rc0: DVBSky T680CI as /devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.4/rc/rc0 [ 4.618483] input: DVBSky T680CI as /devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.4/rc/rc0/input0 [ 4.618674] rc rc0: lirc_dev: driver dvb_usb_dvbsky registered at minor = 0, scancode receiver, no transmitter [ 4.618689] usb 1-1.4: dvb_usb_v2: schedule remote query interval to 300 msecs [ 4.618706] usb 1-1.4: dvb_usb_v2: 'DVBSky T680CI' successfully initialized and connected [ 4.618847] usbcore: registered new interface driver dvb_usb_dvbsky [ 9.764129] si2168 7-0064: downloading firmware from file 'dvb-demod-si2168-b40-01.fw' [ 10.453839] si2168 7-0064: firmware version: B 4.0.11 [ 10.493876] si2157 8-0060: firmware version: 3.0.5 [ 10.493913] usb 1-1.4: DVB: adapter 0 frontend 0 frequency 0 out of range (42000000..870000000) [ 303.683044] dvb_ca_en50221: dvb_ca adapter 0: DVB CAM detected and initialised successfully
However, TVheadend still not working. In the meantime the suggestion from Saen came through, tried doing that, which seems to give some sort of result, output here:
w_scan version 20170107 (compiled for DVB API 5.10) WARNING: could not guess your country. Falling back to 'DE' guessing country 'DE', use -c <country> to override using settings for GERMANY DVB cable DVB-C scan type CABLE, channellist 7 output format initial tuning data WARNING: could not guess your codepage. Falling back to 'UTF-8' output charset 'UTF-8', use -C <charset> to override Info: using DVB adapter auto detection. /dev/dvb/adapter0/frontend0 -> CABLE "Silicon Labs Si2168": very good :-)) Using CABLE frontend (adapter /dev/dvb/adapter0/frontend0) -_-_-_-_ Getting frontend capabilities-_-_-_-_ Using DVB API 5.11 frontend 'Silicon Labs Si2168' supports INVERSION_AUTO QAM_AUTO FEC_AUTO FREQ (42.00MHz ... 870.00MHz) SRATE (1.000MSym/s ... 7.200MSym/s) -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_ 73000: sr6900 (time: 00:00.029) sr6875 (time: 00:03.779) 81000: sr6900 (time: 00:07.179) sr6875 (time: 00:10.589) 113000: sr6900 (time: 00:13.979) sr6875 (time: 00:17.749) 121000: sr6900 (time: 00:19.259) sr6875 (time: 00:22.619) 129000: sr6900 (time: 00:26.129) sr6875 (time: 00:27.679) 137000: sr6900 (time: 00:29.229) sr6875 (time: 00:32.619) 145000: sr6900 (time: 00:36.029) sr6875 (time: 00:37.549) 153000: sr6900 (time: 00:39.069) sr6875 (time: 00:40.589) 161000: sr6900 (time: 00:42.109) sr6875 (time: 00:43.629) 169000: sr6900 (time: 00:45.149) sr6875 (time: 00:46.669) 314000: sr6900 (time: 00:48.189) sr6875 (time: 00:49.709) 322000: sr6900 (time: 00:51.229) sr6875 (time: 00:52.749) 330000: sr6900 (time: 00:56.089) sr6875 (time: 00:57.639) 338000: sr6900 (time: 01:02.129) sr6875 (time: 01:03.679) 346000: sr6900 (time: 01:05.229) sr6875 (time: 01:06.749) 354000: sr6900 (time: 01:08.269) sr6875 (time: 01:11.609) 362000: sr6900 (time: 01:14.969) sr6875 (time: 01:16.519) Still scanning.... 858000: sr6900 (time: 13:17.550) sr6875 (time: 13:19.070) ERROR: Sorry - i couldn't get any working frequency/transponder Nothing to scan!!
regards Jeroen
RE: No input Signal -- DVBSky T680CI -- All in a sudden, suspect after Pi update? [Solved] - Added by Jeroen Lindhout over 3 years ago
Dear all,
I left the above problem as I could not crack it.
Just to exclude any possibility, I used another coax cable to test, and guess what, that was the issue. I suspect an internal issue with my cable. I could see a signal strength and all in TVheadend, but not TV.
An important lesson, it is not always software related.
Thanks all,
Jeroen
RE: No input Signal -- DVBSky T680CI -- All in a sudden, suspect after Pi update? - Added by Jeroen Lindhout over 3 years ago
Dear all,
Above problem is back. Does not seem to be the cable. It all comes down — I think — to the tuner “ not locking” the signal. When it all works, my t DVB Sky tuner has a green light burning “Lock”. This light is now off, and TVheadend does not work.
Does anyone what causes the tuner to lock or not to lock s signal?
Best regards,
Jeroen