TBS 5220: tbs5220fe - tuner command is not responding

[WimKlim]

If the IR receiver is the problem then it should be sufficient to tape the IR diode, or not ?

[bolzerrr]

yes, exactly starts on line 189. the warning you get is harmless, just when you delete those lines the "buf" is not longer used, which is fine. however, i don't understand how that change can affect what you said on the message you sent me, i.e. the change makes the stick not working at all. i tested that modification myself and it's to disable the IR received. anyway, if those changes i suggested don't help then we need to wait for the new "dvb-usb-tbsqbox-id5220.fw", which i mentioned is under development.

Hi,

i did a mistake, it is now running correctly. But the second stick instantly tell me the error message. While searching for the mistake i tried both sticks on my windows PC and the second stick don´t work there, too.
The first stick behaves with that change like before, running fine for a while and then failing with the error.
Here is the log when stating:

Code: Select All Code

[  258.377633] dvb-usb: found a 'TBS 5220 USB2.0' in cold state, will try to load a firmware
[  259.011485] dvb-usb: downloading firmware from file 'dvb-usb-tbsqbox-id5220.fw'
[  259.019031] tbs5220: start downloading TBS5220 firmware
[  259.162316] dvb-usb: found a 'TBS 5220 USB2.0' in warm state.
[  259.169484] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[  259.178819] DVB: registering new adapter (TBS 5220 USB2.0)
[  259.474668] dvb-usb: MAC address: ff:ff:ff:ff:ff:ff
[  259.545428] tbs5220: Attached TBS5220FE!
[  259.545435]
[  259.551112] tbs5220 test driver
[  259.554544] DVB: registering adapter 0 frontend 0 (TurboSight TBS 5220 DVBC frontend)...
[  259.563796] input: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:1c.0/0000:02:00.0/usb4/4-2/4-2.3/input/input4
[  259.576065] dvb-usb: schedule remote query interval to 150 msecs.
[  259.582209] dvb-usb: TBS 5220 USB2.0 successfully initialized and connected.
[  259.589471] dvb-usb: found a 'TBS 5220 USB2.0' in cold state, will try to load a firmware
[  259.624155] dvb-usb: downloading firmware from file 'dvb-usb-tbsqbox-id5220.fw'
[  259.631831] tbs5220: start downloading TBS5220 firmware
[  259.773340] dvb-usb: found a 'TBS 5220 USB2.0' in warm state.
[  259.780123] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[  259.788990] DVB: registering new adapter (TBS 5220 USB2.0)
[  260.084330] dvb-usb: MAC address: 00:00:00:00:00:00
[  261.698183] TurboSight TBS 5220 Frontend:
[  261.698190]  tbs5220fe - tuner command is not responding
[  263.323583] TurboSight TBS 5220 Frontend:
[  263.323588]  tbs5220fe - tuner command is not responding
[  263.334710] tbs5220fe: tuner attach failed
[  263.338858] dvb-usb: no frontend was attached by 'TBS 5220 USB2.0'
[  263.346823] input: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:1c.0/0000:02:00.0/usb4/4-2/4-2.4/input/input5
[  263.359053] dvb-usb: schedule remote query interval to 150 msecs.
[  263.365127] dvb-usb: TBS 5220 USB2.0 successfully initialized and connected.
[  263.374567] usbcore: registered new interface driver tbs5220
[  288.460725] TurboSight TBS 5220 Frontend:
[  288.460730]  tbs5220fe - software version is 1.0.0.0
[  288.666772] TurboSight TBS 5220 Frontend:
[  288.666778]  tbs5220fe - Successfully Initialized


Those lines only apper with the second stick:
[ 263.334710] tbs5220fe: tuner attach failed
[ 263.338858] dvb-usb: no frontend was attached by 'TBS 5220 USB2.0'

[WimKlim]

I disabled the IR-receiver in tbs5220.c .
After a while I got again this problem :
I could receive the sender of one frequence but not the sender of the other frequencies .

[sp00ge]

Hi,

I was wondering if this issue was ever resolved ?
I've finally managed to get my TBS 5220 working in Fedora
(Thanks to xiaocao in my other thread http://www.tbsdtv.com/forum/viewtopic.php?f=145&t=9565&p=34125#p34125)
but after a few minutes of scanning for channels the device seems to stop responding and all I get now is the following error.

Code: Select All Code

[   14.321359] dvb-usb: no frontend was attached by 'TBS 5220 USB2.0'


Thanks,

[stilmant]

I've succeeded to reproduce what I think would be the issue related to problems listed in this thread.
Indeed, I've multiple laptops across the world and I've sometime that issue occurring on some laptops:
-Error(2): /dev/dvb/adapter0/frontend0: No such file or directory
What strange is that I have this kind of issue occurring only on some laptops, and in fact it is appearing that those laptop are all running with the same batch of TBS5220 tuner purchased last year.
Thus we can suspect hardware error, and indeed I isolated two TBS5220 tuners, and those are indeed showing at least one hardware difference in the USB connector insulator color:

Difference between two TBS5220: Good=back, White=Bad

Now both are working, but white USB connector will lose at some occasion its frontend.

I can reproduce the issue by quickly disconnecting and reconnecting the tuner.
With the black one, this will cause no problem. With the white one the tuner will be loaded without its frontend. And the tuner is then in such a hardware state that you need to maintain it disconnected some time before being able to reconnect it with full success.

good (black connector), quick unplug and replug

Code: Select All Code

[  304.047791] usb 1-1: USB disconnect, device number 3
[  304.071508] dvb-usb: TBS 5220 USB2.0 successfully deinitialized and disconnected.
[  305.292355] usb 1-1: new high-speed USB device number 4 using xhci_hcd
[  305.422251] usb 1-1: New USB device found, idVendor=734c, idProduct=5220
[  305.422262] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[  305.423584] dvb-usb: found a 'TBS 5220 USB2.0' in cold state, will try to load a firmware
[  305.423648] dvb-usb: downloading firmware from file 'dvb-usb-tbsqbox-id5220.fw'
[  305.423654] tbs5220: start downloading TBS5220 firmware
[  305.576873] dvb-usb: found a 'TBS 5220 USB2.0' in warm state.
[  305.577288] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[  305.577773] DVB: registering new adapter (TBS 5220 USB2.0)
[  305.579105] tbs5220: read eeprom failed.
[  305.579114] dvb-usb: MAC address reading failed.
[  305.580362] dvb-usb: no frontend was attached by 'TBS 5220 USB2.0'
[  305.581576] input: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:1c.7/0000:27:00.0/usb1/1-1/input/input22
[  305.581780] dvb-usb: schedule remote query interval to 150 msecs.
[  305.581789] dvb-usb: TBS 5220 USB2.0 successfully initialized and connected.
[  305.581962] usb 1-1: USB disconnect, device number 4
[  305.617628] dvb-usb: TBS 5220 USB2.0 successfully deinitialized and disconnected.
[  307.219745] usb 1-1: new high-speed USB device number 5 using xhci_hcd
[  307.350146] usb 1-1: New USB device found, idVendor=734c, idProduct=5220
[  307.350157] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[  307.350162] usb 1-1: Product: TBS 5220
[  307.350167] usb 1-1: Manufacturer: TBS-Tech
[  307.351104] dvb-usb: found a 'TBS 5220 USB2.0' in cold state, will try to load a firmware
[  307.351175] dvb-usb: downloading firmware from file 'dvb-usb-tbsqbox-id5220.fw'
[  307.351178] tbs5220: start downloading TBS5220 firmware
[  307.504264] dvb-usb: found a 'TBS 5220 USB2.0' in warm state.
[  307.504595] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[  307.504940] DVB: registering new adapter (TBS 5220 USB2.0)
[  307.851316] dvb-usb: MAC address: ff:ff:ff:ff:ff:ff
[  318.173637] TurboSight TBS 5220 Frontend:
 tbs5220fe - software version is 1.0.0.0
[  318.405409] TurboSight TBS 5220 Frontend:
 tbs5220fe - Successfully Initialized
[  318.405420] tbs5220: Attached TBS5220FE!

[  318.406153] DVB: registering adapter 0 frontend 0 (TurboSight TBS 5220 DVBC frontend)...
[  318.407058] input: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:1c.7/0000:27:00.0/usb1/1-1/input/input23
[  318.407198] dvb-usb: schedule remote query interval to 150 msecs.
[  318.407207] dvb-usb: TBS 5220 USB2.0 successfully initialized and connected.

Bad (white connector), quick unplug and replug

Code: Select All Code

[  476.246675] usb 1-1: USB disconnect, device number 7
[  476.271497] dvb-usb: TBS 5220 USB2.0 successfully deinitialized and disconnected.
[  477.554883] usb 1-1: new high-speed USB device number 8 using xhci_hcd
[  477.684843] usb 1-1: New USB device found, idVendor=734c, idProduct=5220
[  477.684854] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[  477.686026] dvb-usb: found a 'TBS 5220 USB2.0' in cold state, will try to load a firmware
[  477.686086] dvb-usb: downloading firmware from file 'dvb-usb-tbsqbox-id5220.fw'
[  477.686090] tbs5220: start downloading TBS5220 firmware
[  477.839378] dvb-usb: found a 'TBS 5220 USB2.0' in warm state.
[  477.839780] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[  477.840176] DVB: registering new adapter (TBS 5220 USB2.0)
[  477.841223] tbs5220: read eeprom failed.
[  477.841239] dvb-usb: MAC address reading failed.
[  477.842369] dvb-usb: no frontend was attached by 'TBS 5220 USB2.0'
[  477.843776] input: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:1c.7/0000:27:00.0/usb1/1-1/input/input26
[  477.843956] dvb-usb: schedule remote query interval to 150 msecs.
[  477.843964] dvb-usb: TBS 5220 USB2.0 successfully initialized and connected.
[  477.844135] usb 1-1: USB disconnect, device number 8
[  477.876181] dvb-usb: TBS 5220 USB2.0 successfully deinitialized and disconnected.
[  479.481917] usb 1-1: new high-speed USB device number 9 using xhci_hcd
[  479.612862] usb 1-1: New USB device found, idVendor=734c, idProduct=5220
[  479.612872] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[  479.612877] usb 1-1: Product: TBS 5220
[  479.612881] usb 1-1: Manufacturer: TBS-Tech
[  479.614471] dvb-usb: found a 'TBS 5220 USB2.0' in cold state, will try to load a firmware
[  479.614524] dvb-usb: downloading firmware from file 'dvb-usb-tbsqbox-id5220.fw'
[  479.614527] tbs5220: start downloading TBS5220 firmware
[  479.766401] dvb-usb: found a 'TBS 5220 USB2.0' in warm state.
[  479.766830] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[  479.767230] DVB: registering new adapter (TBS 5220 USB2.0)
[  480.131114] dvb-usb: MAC address: ff:ff:ff:ff:ff:ff
[  480.154190] dvb-usb: no frontend was attached by 'TBS 5220 USB2.0'
[  480.155113] input: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:1c.7/0000:27:00.0/usb1/1-1/input/input27
[  480.155269] dvb-usb: schedule remote query interval to 150 msecs.
[  480.155278] dvb-usb: TBS 5220 USB2.0 successfully initialized and connected.

~$ dvbsnoop -s feinfo
dvbsnoop V1.4.50 -- http://dvbsnoop.sourceforge.net/
Error(2): /dev/dvb/adapter0/frontend0: No such file or directory


Notice that the behavior for both tuners once reconnecting it is to run the driver 'initialization step' two times, first to detect tuner is in "cold" state and load firmware, in that step the frontend is not attached for both tuners, but on second "boot", the frontend can't be attached for some reason on the "white tuner"

For info, this is a normal boot of white tuner (not from a quick unplug-plug)

Code: Select All Code

[  362.022956] usb 1-1: new high-speed USB device number 7 using xhci_hcd
[  362.153892] usb 1-1: New USB device found, idVendor=734c, idProduct=5220
[  362.153902] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[  362.153907] usb 1-1: Product: TBS 5220
[  362.153911] usb 1-1: Manufacturer: TBS-Tech
[  362.155044] dvb-usb: found a 'TBS 5220 USB2.0' in cold state, will try to load a firmware
[  362.155154] dvb-usb: downloading firmware from file 'dvb-usb-tbsqbox-id5220.fw'
[  362.155159] tbs5220: start downloading TBS5220 firmware
[  362.307442] dvb-usb: found a 'TBS 5220 USB2.0' in warm state.
[  362.307845] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[  362.308125] DVB: registering new adapter (TBS 5220 USB2.0)
[  362.641137] dvb-usb: MAC address: ff:ff:ff:ff:ff:ff
[  372.900382] TurboSight TBS 5220 Frontend:
 tbs5220fe - software version is 1.0.0.0
[  373.140199] TurboSight TBS 5220 Frontend:
 tbs5220fe - Successfully Initialized
[  373.140210] tbs5220: Attached TBS5220FE!

[  373.141068] DVB: registering adapter 0 frontend 0 (TurboSight TBS 5220 DVBC frontend)...
[  373.142105] input: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:1c.7/0000:27:00.0/usb1/1-1/input/input25
[  373.142350] dvb-usb: schedule remote query interval to 150 msecs.
[  373.142359] dvb-usb: TBS 5220 USB2.0 successfully initialized and connected

Hopping this could help to fine tune this tuner.

[steven]

Hi stilmant

Please have a try test the white one in windows with our latest DVBT or DVBC driver:
http://www.tbsdtv.com/download/document ... .0.0.7.zip
check whether is ok

Thanks

Kind Regards

steven

[stilmant]

Hello Steven,

I'm not sure how to test on windows since I don't have my software on that platform and the issue of the device loosing the frontend on remote laptop happen randomly without being sure from my side what is causing that. (I don't remember seeing it caused by unplugging the tuner and reconnecting it from logs, will try to record such logs next time this will happen on those remote laptops: They are not connected all the time.)

However I can test the quick disconnection and quick re-plug of the tuner on Windows. We can notice this two steps of loading firmware at cold state and then a firm driver initialization at a second steps.

I did 'succeed' to get an initialization error with the White tuner but after many tries (20?) and thus this is not systematic.

Windows issue at one quick unplug/plug with white tuner

I don't know if this is helping you and if this was the test requested.

I've try to do the same with "black" tuner but without success so far.