TBS 5980 USB Tuner on Vero 4K

Help and Support Vero 4K / Vero 4K +
1

Hi,

I am trying to connect my TBS 5980 usb tuner to my Vero 4K, but it seems that the firmware is not loading? Is the firmware for this tuner added to OSMC? I thought it was supposed to be added and supported for Vero 4K from May update? I have latest June update installed.

Uname -r
3.14.29-25-osmc

lsusb
Bus 001 Device 003: ID 734c:5980 TBS Technologies China

dmesg | grep usb
[    0.224737] usbcore: registered new interface driver usbfs
[    0.224769] usbcore: registered new interface driver hub
[    0.224824] usbcore: registered new device driver usb
[    0.341390] usbcore: registered new interface driver smsc95xx
[    0.341853] usbcore: registered new interface driver usb-storage
[    0.341938] usbcore: registered new interface driver usbserial
[    0.341961] usbcore: registered new interface driver usbserial_generic
[    0.341983] usbserial: USB Serial support registered for generic
[    0.342005] usbcore: registered new interface driver pl2303
[    0.342027] usbserial: USB Serial support registered for pl2303
[    0.342245] amlogic-new-usb2 d0078000.usb2phy: USB2 phy 
probe:phy_mem:0xd0078000, iomap phy_base:0xffffff800047e000
[    0.342330] amlogic-new-usb3 d0078080.usb3phy: This phy has no usb port
[    0.342350] amlogic-new-usb3 d0078080.usb3phy: USB3 phy 
probe:phy_mem:0xd0078080, iomap phy_base:0xffffff8000582080
[    0.344452] usbcore: registered new interface driver usbhid
[    0.344457] usbhid: USB HID core driver
[    2.529866] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[    2.529873] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.529879] usb usb1: Product: xHCI Host Controller
[    2.529884] usb usb1: Manufacturer: Linux 3.14.29-25-osmc xhci-hcd
[    2.529890] usb usb1: SerialNumber: xhci-hcd.0.auto
[    2.530548] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003
[    2.530555] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.530561] usb usb2: Product: xHCI Host Controller
[    2.530567] usb usb2: Manufacturer: Linux 3.14.29-25-osmc xhci-hcd
[    2.530572] usb usb2: SerialNumber: xhci-hcd.0.auto
[    2.848887] usb 1-1: new low-speed USB device number 2 using xhci-hcd
[    2.996883] usb 1-1: New USB device found, idVendor=2252, idProduct=1037
[    2.996894] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    2.996899] usb 1-1: Product: USB Keyboard Mouse
[    2.996904] usb 1-1: Manufacturer: HBGIC Technology Co., Ltd.
[    3.009922] input: HBGIC Technology Co., Ltd. USB Keyboard Mouse as /devices/c9000000.dwc3/xhci-hcd.0.auto/usb1/1-1/1-1:1.0/0003:2252:1037.0001/input/input2
[    3.010120] hid-generic 0003:2252:1037.0001: input,hidraw0: USB HID v1.10 Keyboard [HBGIC Technology Co., Ltd. USB Keyboard Mouse] on usb-xhci-hcd.0.auto-1/input0
[    3.018897] input: HBGIC Technology Co., Ltd. USB Keyboard Mouse as /devices/c9000000.dwc3/xhci-hcd.0.auto/usb1/1-1/1-1:1.1/0003:2252:1037.0002/input/input3
[    3.019143] hid-generic 0003:2252:1037.0002: input,hidraw1: USB HID v1.10 Mouse [HBGIC Technology Co., Ltd. USB Keyboard Mouse] on usb-xhci-hcd.0.auto-1/input1
[    3.138899] usb 1-2: new high-speed USB device number 3 using xhci-hcd
[    3.279007] usb 1-2: New USB device found, idVendor=734c, idProduct=5980
[    3.279018] usb 1-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    4.179465] dwc_otg: usb0: type: 2 speed: 0, config: 0, dma: 0, id: 0, phy: d0078000, ctrl: 0
[    4.179478] dwc_otg_driver_probe host only, not probe usb_otg!!!

I also have TVHeadend server and HTSP client installed, but there in the web interface I cannot see the tuner in Configuration->DVB Inputs->TV adapters.

In firmware folder I have these->
/lib/firmware
3.14.29-17-osmc
RTL8192E
RTL8192SU
ar3k
ar5523.bin
ar7010.fw
ar7010_1_1.fw
ar9170.fw
ar9271.fw
ath3k-1.fw
ath6k
brcm
config_43455c0.txt
dvb-cx18-mpc718-mt352.fw
dvb-demod-drxk-pctv.fw
dvb-demod-si2165.fw
dvb-dibusb-5.0.0.11.fw
dvb-fe-or51132-qam.fw
dvb-fe-or51132-vsb.fw
dvb-fe-or51211.fw
dvb-fe-tda10046.fw
dvb-fe-tda10071.fw
dvb-ttpci-01.fw
dvb-ttusb-dec-2000t.fw
dvb-ttusb-dec-2540t.fw
dvb-ttusb-dec-3000s.fw
dvb-usb-az6027-03.fw
dvb-usb-bluebird-01.fw
dvb-usb-it9135-01.fw
dvb-usb-it9135-02.fw
dvb-usb-terratec-h5-drxk.fw
dvb-usb-vp7049-0.95.fw
fw_bcm43455c0_ag.bin
htc_7010.fw
htc_9271.fw
mt7601u.bin
mt7610u_sta.template.dat
ngene_15.fw
ngene_17.fw
ngene_18.fw
nvram_43455c0.txt
rt2561.bin
rt2561s.bin
rt2661.bin
rt2860.bin
rt2870.bin
rt3070.bin -> rt2870.bin
rt3071.bin
rt3090.bin -> rt2860.bin
rt3290.bin
rt73.bin
rtl8192dufw.bin
rtl8192dufw_wol.bin
rtl_nic
rtlwifi
sms1xxx-hcw-55xxx-dvbt-01.fw
sms1xxx-hcw-55xxx-dvbt-02.fw
sms1xxx-hcw-55xxx-isdbt-02.fw
v4l-cx231xx-avcore-01.fw
v4l-cx23418-apu.fw
v4l-cx23418-cpu.fw
v4l-cx23418-dig.fw
v4l-cx23885-enc.fw
v4l-cx25840.fw

Which firmware is supposed to be loaded for TBS 5980?
This tuner is added to LibreELEC image, by using CrazyCat fork of media build by Ijalves to the Linux kernel 4.9.

2

Hi

I remember we discussed this before

I am not sure about TBS support. The drivers have always been out of tree due to a few issues.

I’m not sure which LE image you refer to but there is no 4.9 kernel for the SoC that Vero 4K uses at this time. We do use media_build however. Some DVB firmwares need to be added manually and DVB support is still in a state of flux

Sam

3

Hi Sam,

Yes I asked a month ago and you said it was going to be supported, see this thread.

https://discourse.osmc.tv/t/add-open-source-drivers-for-tbs-usb-tuners/37245

4

We have switched to media_build as per the discussion. So if that adds support for your device as suggested then it will work

Try adding the firmware and pasting proper debug logs so we can see what the issue is. To avoid bloat we don’t currently ship a lot of dvb firmwares

In the future it will be easier

5

Do I need to build the firmware my self or can I find a ARM driver to add manually?
Or maybe copy the firmware from LibreELEC if that is possible?

Do you have any suggestion?

6

No building necessary. You just need to copy a firmware file. Running dmesg on LibreELEC after plugging it in will probably tell you which file needs copying

Sam

7

Ok thank you Sam, I will install LibreELEC to my Raspberry Pi and find out, but not tonight though. I need to go to sleep now. :slight_smile: … I will reply back here of the results later on.

8

Cool, let me know how you get on

9

Is it this box?
https://www.linuxtv.org/wiki/index.php/TBS5980_(aka_TBS_Qbox_CI)

that says:

Install the firmware file required by TBS5980 driver

Go to http://www.tbsdtv.com/products/tbs5980-dvb-s2-ci-tv-tuner-usb.html, tab Download, download the linux driver in the zip archive, get the dvb-usb-tbsqbox-id5980.fw file and copy it /lib/firmware

cd /usr/src
mkdir tbs5980-firmware
cd tbs5980-firmware
wget http://www.tbsiptv.com/download/tbs5980/tbs-linux-sources_v151229.zip
unzip tbs-linux-sources_v151229.zip
cp dvb-usb-tbsqbox-id5980.fw /lib/firmware
10

Yes that is the box, but you link to the old proprietary firmware driver. TBS has switched to develop an opensource driver, which is a fork of Ijalves. Information of this you can read in TBS forum.

11

Ok, seems that you are already deep in the troubleshooting.
While normally I would assume the opensource driver still depend on the original firmware.

12

Logs will help us get this running. Get some rest!

13

If there is an opensource project in the works, have you tired asking them for help? They may be able to help you build the driver on the 4K.

14

Hi Sam,

I have now been testing the LibreELEC 8.0.2 for RaspberryPi2 image and I can confirm that this image do support my tuner. The firmware it is loading is this one →
dvb-usb-tbsqbox-id5980.fw

I have copied over this firmware driver to folder /lib/firmware/ on my Vero4K but it is not loading it?

I enabled the Debug Logging and re-started the Vero4K. Then I plug in my TBS 5980 tuner. The log is after this procedure.
Debug log

Do you have any idea?

15

The Kodi log would not be related to loading the firmware and getting the stick ready.
For that dmesg/journalctl is crucial. You can upload via
grab-logs -J -K

16

Ah ok, here is the log then. :slight_smile:
Debug log2

17

Ok, looking at the log file no driver is loaded for your stick so I guess that the driver is not part of the backport that @sam_nazarko included or the module not activated in the build

18

Hi,

The new fw file is only downloaded to USB tuner, if the tuner is found in ‘cold’ state.
If the tuner is found in ‘warm’ state, then the fw that is already downloaded in the USB tuner is used.
(ie your new fw file is ignored).

Try unplugging the USB tuner, and then check dmesg.
Then plug in the USB tuner, and check dmesg again.

with dmesg, when you plug in the USB tuner, then you should see something like this…

- $ dmesg
- < ...... lines cut for clarity ..... >
- usb 5-2: USB disconnect, address 3
- usb 5-2: new high speed USB device using ehci_hcd and address 8
- dvb-usb: found a 'Hanftek UMT-010 DVB-T USB2.0' in **cold state, will try to load a firmware**
- dvb-usb: downloading firmware from file 'dvb-usb-umt-010-02.fw' to the 'Cypress FX2'
- dvb-usb: Hanftek UMT-010 DVB-T USB2.0 successfully initialized and connected.
- usb 5-2: USB disconnect, address 8
- dvb-usb: generic DVB-USB module successfully deinitialized and disconnected.

If you don’t see the ‘cold state’ in dmesg when you plug in the USB tuner, then try renaming your original fw file, and then try replacing it with your new fw file.

HTH.
Best regards,
Niall.

19

Hi,

I have tried to do as you suggested by renaming the *.fw file but I cannot make it work.

The only output I get from dmesg with my tuner is → 

usb 1-2: new high-speed USB device number 3 using xhci-hcd
usb 1-2: New USB device found, idVendor=734c, idProduct=5980
usb 1-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0

Maybe the reason is as @fzinken said that the driver is not part of the backport that is included or the module not activated in the build? Only @sam_nazarko can answer this I guess? @sam_nazarko can you please reply with status? Maybe include it for next update? :slight_smile:

20

I’ll look in to this.
DVB needs a kick up the butt. Thought we were close but seemingly a bit more is needed; the skipping issue was quite pressing so took a bit of time for June.

Not to worry, it’s on the list

Sam