TBS 5220: tbs5220fe - tuner command is not responding

[bolzerrr]

I already mentioned this problem few month ago and did not found a solution. Now as i have some time to take care i did a complete fresh install:

- Fresh debian chroot on a synology diskstation DS214play
- Fresh compile of the latest TBS drivers
- Fresh compile of vdr

Problemdescription: Everything is running fine, but after a couple of hours (or minutes) i get following error:

Code: Select All Code

[36675.609505] TurboSight TBS 5220 Frontend:
[36675.609510]  tbs5220fe - tuner command is not responding
[36677.778026] TurboSight TBS 5220 Frontend:
[36677.778033]  tbs5220fe - tuner command is not responding
[36679.367474] TurboSight TBS 5220 Frontend:
[36679.367480]  tbs5220fe - tuner command is not responding
[36680.980884] TurboSight TBS 5220 Frontend:
[36680.980890]  tbs5220fe - tuner command is not responding


Here comes the dmesg on plugin of USB device:

Code: Select All Code

[37886.234676] usb 4-2.4: new high-speed USB device number 9 using etxhci_hcd_140303
[37886.257612] Got empty serial number. Generate serial number from product.
[37886.264517] drivers/usb/core/ethub.c (1891) Same device found. Change serial to ffffff84ffffffb6ffffff84ffffffb0
[37886.276026] dvb-usb: found a 'TBS 5220 USB2.0' in cold state, will try to load a firmware
[37886.313356] dvb-usb: downloading firmware from file 'dvb-usb-tbsqbox-id5220.fw'
[37886.320732] tbs5220: start downloading TBS5220 firmware
[37886.462436] dvb-usb: found a 'TBS 5220 USB2.0' in warm state.
[37886.468884] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[37886.479996] DVB: registering new adapter (TBS 5220 USB2.0)
[37886.775437] dvb-usb: MAC address: ff:ff:ff:ff:ff:ff
[37886.845196] tbs5220: Attached TBS5220FE!
[37886.845202]
[37886.851192] DVB: registering adapter 1 frontend 0 (TurboSight TBS 5220 DVBC frontend)...
[37886.860352] 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/input7
[37886.872447] dvb-usb: schedule remote query interval to 150 msecs.
[37886.878586] dvb-usb: TBS 5220 USB2.0 successfully initialized and connected.


Code: Select All Code

uname -a
Linux DiskStation 3.2.40 #4482 SMP PREEMPT Fri Apr 18 16:52:51 CST 2014 i686 GNU/Linux


Code: Select All Code

 lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 002: ID 05e3:0726 Genesys Logic, Inc. SD Card Reader
Bus 004 Device 002: ID 2109:2812
Bus 005 Device 002: ID 2109:0812
Bus 004 Device 003: ID 051d:0002 American Power Conversion Uninterruptible Power Supply
Bus 004 Device 009: ID 734c:5220 TBS Technologies China

I really hope to get support, otherwise those sticks are useless for me.

Best regards

[cody]

please, give us some more information:

1) you say " Everything is running fine, but after a couple of hours (or minutes) i get following error:" - is it working after the error starts happening or after that is no longer working?

2) you mentioned you use it on "synology diskstation DS214play", have you tried on regular PC in Linux?

3) does "synology diskstation DS214play" have USB 3.0 or USB 2.0 ports? if they are USB 3.0 ports is there BIOS option to switch them to Legacy Mode?

[bolzerrr]

Thanks for your reply.

1) case 2, it is working for a while, then TV signal stops and i see the error in the dmesg log. When i unload and reload the modules it start working until the error occurs again. Unfortunately the error occurs always.

2) Not yet i will try to setup a debian Vm for testing

3) Both- and i tried both, it makes no difference.

[bolzerrr]

I don´t get it working in a vm.

Can you give me some background information on what the message is telling me? What must happen that the message occurs?

If you need any further information let me know. I am also willing to test beta drivers or do anything else. Really want to get it running..

[cody]

the error messages means almost literal what it says - transactions between tuner chip on the device and the driver fail. also, obviously it doesn't recover from the condition, because the error happens over and over again and it needs reload/restart. so, no other 5220 users complained and that's why i'm asking for those tests, because i believe something specific and isolated to your environment triggers the problem, but it could be fault on your 5220 stick - if we cannot figure anything more with test from your side, then replacing that 5220 stick with new one is definitely the best next step. that way at least we will rule out your current 5220.

[bolzerrr]

I have two of those stick and the problem happen with both. Also i already sent them back and received new ones and nothing changed. So if you have no further hint or dependencies i could check i guess i have no chance to get them proper working

[bolzerrr]

i am active in a german VDR portal and there are 2 more users describing the same issue. I asked them for logs maybe this can help.

[bolzerrr]

Got response, sound very the same:

pschneider@Samweis:~$ dmesg | grep dvb
[ 22.440841] dvb-usb: found a 'TBS 5220 USB2.0' in cold state, will try to load a firmware
[ 22.544332] dvb-usb: downloading firmware from file 'dvb-usb-tbsqbox-id5220.fw'
[ 22.668190] dvb-usb: found a 'TBS 5220 USB2.0' in warm state.
[ 22.668803] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 22.843674] dvb-usb: MAC address: ff:ff:ff:ff:ff:ff
[ 22.972059] dvb-usb: schedule remote query interval to 150 msecs.
[ 22.972075] dvb-usb: TBS 5220 USB2.0 successfully initialized and connected.

pschneider@Samweis:~$ dmesg | grep tbs
[ 22.544332] dvb-usb: downloading firmware from file 'dvb-usb-tbsqbox-id5220.fw'
[ 22.544342] tbs5220: start downloading TBS5220 firmware
[ 22.859523] tbs5220fe: module license 'TurboSight Proprietary' taints kernel.
[ 22.969824] tbs5220: Attached TBS5220FE!
[ 22.972166] usbcore: registered new interface driver tbs5220
[ 70.958518] tbs5220fe - software version is 1.0.0.0
[ 71.067817] tbs5220fe - Successfully Initialized

on failure:

pschneider@Samweis:~$ dmesg | grep tbs
[66098.664036] tbs5220fe - tuner command is not responding
[66100.824034] tbs5220fe - tuner command is not responding
[66102.408032] tbs5220fe - tuner command is not responding
[66104.016033] tbs5220fe - tuner command is not responding


pschneider@Samweis:~$ lsusb
Bus 001 Device 002: ID 734c:5220 TBS Technologies China
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

pschneider@Samweis:~$ uname -a
Linux Samweis 3.13.0-24-generic #47-Ubuntu SMP Fri May 2 23:31:42 UTC 2014 i686 i686 i686 GNU/Linux

pschneider@Samweis:~$ dmesg | grep usb
pschneider@Samweis:~$

nach reboot :

pschneider@Samweis:~$ dmesg | grep usb
[ 0.676204] usbcore: registered new interface driver usbfs
[ 0.676233] usbcore: registered new interface driver hub
[ 0.676250] usbcore: registered new device driver usb
[ 1.712211] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[ 1.712219] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1.712225] usb usb1: Product: EHCI Host Controller
[ 1.712230] usb usb1: Manufacturer: Linux 3.13.0-24-generic ehci_hcd
[ 1.712236] usb usb1: SerialNumber: 0000:00:1d.7
[ 1.713487] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001
[ 1.713495] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1.713501] usb usb2: Product: UHCI Host Controller
[ 1.713506] usb usb2: Manufacturer: Linux 3.13.0-24-generic uhci_hcd
[ 1.713512] usb usb2: SerialNumber: 0000:00:1d.0
[ 1.714404] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001
[ 1.714411] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1.714417] usb usb3: Product: UHCI Host Controller
[ 1.714423] usb usb3: Manufacturer: Linux 3.13.0-24-generic uhci_hcd
[ 1.714429] usb usb3: SerialNumber: 0000:00:1d.1
[ 1.715312] usb usb4: New USB device found, idVendor=1d6b, idProduct=0001
[ 1.715319] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1.715325] usb usb4: Product: UHCI Host Controller
[ 1.715331] usb usb4: Manufacturer: Linux 3.13.0-24-generic uhci_hcd
[ 1.715337] usb usb4: SerialNumber: 0000:00:1d.2
[ 1.716253] usb usb5: New USB device found, idVendor=1d6b, idProduct=0001
[ 1.716261] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1.716267] usb usb5: Product: UHCI Host Controller
[ 1.716272] usb usb5: Manufacturer: Linux 3.13.0-24-generic uhci_hcd
[ 1.716278] usb usb5: SerialNumber: 0000:00:1d.3
[ 2.024079] usb 1-4: new high-speed USB device number 2 using ehci-pci
[ 2.156816] usb 1-4: New USB device found, idVendor=734c, idProduct=5220
[ 2.156827] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 2.156833] usb 1-4: Product: TBS 5220
[ 2.156839] usb 1-4: Manufacturer: TBS-Tech
[ 22.258398] dvb-usb: found a 'TBS 5220 USB2.0' in cold state, will try to load a firmware
[ 22.563889] dvb-usb: downloading firmware from file 'dvb-usb-tbsqbox-id5220.fw'
[ 22.796134] dvb-usb: found a 'TBS 5220 USB2.0' in warm state.
[ 22.796318] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 22.965341] dvb-usb: MAC address: ff:ff:ff:ff:ff:ff
[ 23.088625] input: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:1d.7/usb1/1-4/input/input15
[ 23.088810] dvb-usb: schedule remote query interval to 150 msecs.
[ 23.088822] dvb-usb: TBS 5220 USB2.0 successfully initialized and connected.
[ 23.088940] usbcore: registered new interface driver tbs5220

[bolzerrr]

Another one:

hier meine log-Ausgabe aus openSuse :

[ 80.488977] dvb-usb: found a 'TBS 5220 USB2.0' in cold state, will try to load a firmware
[ 80.530984] dvb-usb: downloading firmware from file 'dvb-usb-tbsqbox-id5220.fw'
[ 80.530987] tbs5220: start downloading TBS5220 firmware
[ 80.647746] dvb-usb: found a 'TBS 5220 USB2.0' in warm state.
[ 80.647799] DVB: registering new adapter (TBS 5220 USB2.0)
[ 80.647802] tbs5220: read eeprom failed.
[ 80.663508] dvb-usb: no frontend was attached by 'TBS 5220 USB2.0'
[ 80.663648] dvb-usb: TBS 5220 USB2.0 successfully initialized and connected.
[ 80.663665] usbcore: registered new interface driver tbs5220
[ 80.681225] dvb-usb: TBS 5220 USB2.0 successfully deinitialized and disconnected.
[ 82.404180] usb 1-1.5: Product: TBS 5220
[ 82.404182] usb 1-1.5: Manufacturer: TBS-Tech
[ 82.404499] dvb-usb: found a 'TBS 5220 USB2.0' in cold state, will try to load a firmware
[ 82.404530] dvb-usb: downloading firmware from file 'dvb-usb-tbsqbox-id5220.fw'
[ 82.404531] tbs5220: start downloading TBS5220 firmware
[ 82.521738] dvb-usb: found a 'TBS 5220 USB2.0' in warm state.
[ 82.522035] DVB: registering new adapter (TBS 5220 USB2.0)
[ 82.830169] tbs5220: Attached TBS5220FE!
[ 82.830603] DVB: registering adapter 0 frontend 0 (TurboSight TBS 5220 DVBC frontend)...
[ 82.831208] dvb-usb: TBS 5220 USB2.0 successfully initialized and connected.
[ 158.214297] TurboSight TBS 5220 Frontend:
tbs5220fe - software version is 1.0.0.0
[ 158.333022] TurboSight TBS 5220 Frontend:
tbs5220fe - Successfully Initialized
[ 1355.583232] TurboSight TBS 5220 Frontend:
tbs5220fe - tuner command is not responding
[ 1356.970239] TurboSight TBS 5220 Frontend:
tbs5220fe - tuner command is not responding
[ 1358.379258] TurboSight TBS 5220 Frontend:
tbs5220fe - tuner command is not responding

[cody]

maybe, access speed is too high in some environment and triggers the problem. despite, you found few other cases, at least no other such complains reached me. anyway, please, try the following:

open

"linux-tbs-drivers/linux/drivers/media/dvb/dvb-usb/tbs5220.c"

in any text editor and fine the following lines

Code: Select All Code

         buf[0] = 6;
         buf[1] = 1;
         tbs5220_op_rw(d->dev->udev, 0x8a, 0, 0,
               buf, 2, TBS5220_WRITE_MSG);

delete them, then save the file and rebuild and reinstall the drivers:

# sudo make
# sudo make install

remove your 5220 stick from the computer (to lost it's current settings), reboot the computer then, insert again 5220 and start testing. BTW, if you want to be sure you're using the modified test driver, instead just delete the above lines you can replace them with:

Code: Select All Code

printk("tbs5220 test driver\n");

that way when the driver loads, you will see that message on 'dmesg' output and be sure indeed you're running the modified driver.