Raspberry Pi + TBS tuner

Pepe Suriano

Hi to all! I have a RPI2 and a TBS 5881 DVB-T tuner, I actually use the tuner with my linux PC with kodi and it runs amazing, but I want to use it with my raspberry pi because of HDMI-CEC capability, the problem is that tbs only have x86-64 drivers and they are not open source, and there is not ARM suport.

There are open drivers for TBS
https://github.com/ljalves/linux-tbs-drivers
I could install this, but my backend (tvheadend) still not recognize the tuner

Has anybody an idea on how could I make it work with my pi?

Thanks!

mpmc

Pepe Suriano wrote:
> Hi to all! I have a RPI2 and a TBS 5881 DVB-T tuner, I actually use the tuner with my linux PC with kodi and it runs amazing, but I want to use it with my raspberry pi because of HDMI-CEC capability, the problem is that tbs only have x86-64 drivers and they are not open source, and there is not ARM suport.
>
> There are open drivers for TBS
https://github.com/ljalves/linux-tbs-drivers
I could install this, but my backend (tvheadend) still not recognize the tuner
>
> Has anybody an idea on how could I make it work with my pi? >

> Thanks!

You can't, see https://github.com/ljalves/linux_media/wiki for details on what cards are supported by ljalves' drivers.

Your only option is to plead with TBS to release ARM compatible drivers which they won't (I know I've tried) or buy another more supported tuner the mygica T230 is very good, anything with the Silicon labs Si21x8 chipset, PCTV 292E, WinTVSoloHD etc.

If you find a tuner what you like the look of google it along side linux to see how well it's supported.

Do not bother with Astrometa sticks (they're cheap and tempting) at the moment the driver isn't quite ready.

HTH

Pepe Suriano

Thanks Mark, that's a good point, but I am not planning to buy extra readers (I already have a pair), the idea is to make the best effort to make TBS5881 work with my RPI, in TBS forums some people claim to have it working, but I could not contact them and there is no info of how they manage to do it, that's why I prefer to continue trying to make it work with my Pi, because it is proved that it works apart from the ausence of official ARM support

thanks

mpmc

Pepe Suriano wrote:
> Thanks Mark, that's a good point, but I am not planning to buy extra readers (I already have a pair), the idea is to make the best effort to make TBS5881 work with my RPI, inTBS forums some people claim to have it working, but I could not contact them and there is no info of how they manage to do it, that's why I prefer to continue trying to make it work with my Pi, because it is proved that it works apart from the ausence of official ARM support
>

> thanks

Got a link? I suspect they may have used the ARM modules TBS use for the TBS Matrix.

ProfYaffle

Leave the TBS tuner on your Linux PC and use SAT>IP to export it to a second tvheadend instance on the Pi...?

Pepe Suriano

Prof, my idea is to use just only the Pi, due to practical and to power consume difference

Mark: here are some cases:

http://www.tbsdtv.com/forum/viewtopic.php?p=29912&sid=ade0364d201eaae04728173e841efff2#p29912

http://www.tbsdtv.com/forum/viewtopic.php?p=28003#p28003

I tried again to install open source drivers and I remember that when it arrives to first ia32 file it stops compiling:

LD [M] /root/DriverCrazyCat/linux-tbs-drivers/v4l/tbs6980fe.o
ld: /root/DriverCrazyCat/linux-tbs-drivers/v4l/tbs6980fe_driver.o: Relocations in generic ELF (EM: 3)
ld: /root/DriverCrazyCat/linux-tbs-drivers/v4l/tbs6980fe_driver.o: Relocations in generic ELF (EM: 3)
ld: /root/DriverCrazyCat/linux-tbs-drivers/v4l/tbs6980fe_driver.o: Relocations in generic ELF (EM: 3)
ld: /root/DriverCrazyCat/linux-tbs-drivers/v4l/tbs6980fe_driver.o: Relocations in generic ELF (EM: 3)
ld: /root/DriverCrazyCat/linux-tbs-drivers/v4l/tbs6980fe_driver.o: Relocations in generic ELF (EM: 3)
ld: /root/DriverCrazyCat/linux-tbs-drivers/v4l/tbs6980fe_driver.o: Relocations in generic ELF (EM: 3)
ld: /root/DriverCrazyCat/linux-tbs-drivers/v4l/tbs6980fe_driver.o: Relocations in generic ELF (EM: 3)
ld: /root/DriverCrazyCat/linux-tbs-drivers/v4l/tbs6980fe_driver.o: Relocations in generic ELF (EM: 3)
ld: /root/DriverCrazyCat/linux-tbs-drivers/v4l/tbs6980fe_driver.o: Relocations in generic ELF (EM: 3)
ld: /root/DriverCrazyCat/linux-tbs-drivers/v4l/tbs6980fe_driver.o: Relocations in generic ELF (EM: 3)
ld: /root/DriverCrazyCat/linux-tbs-drivers/v4l/tbs6980fe_driver.o: Relocations in generic ELF (EM: 3)
/root/DriverCrazyCat/linux-tbs-drivers/v4l/tbs6980fe_driver.o: error adding symbols: File in wrong format
make[3]:* [/root/DriverCrazyCat/linux-tbs-drivers/v4l/tbs6980fe.o] Error 1
make[2]:* [_module_/root/DriverCrazyCat/linux-tbs-drivers/v4l] Error 2
make[2]: Leaving directory `/usr/src/linux-headers-3.18.0-20-rpi2'
make[1]:* [default] Error 2
make[1]: Leaving directory `/root/DriverCrazyCat/linux-tbs-drivers/v4l'

make:* [all] Error 2

is it possible to avoid these files to see if that finishes compiling?

mpmc

Pepe Suriano wrote:
> Prof, my idea is to use just only the Pi, due to practical and to power consume difference
>
> Mark: here are some cases:
>
>
http://www.tbsdtv.com/forum/viewtopic.php?p=29912&sid=ade0364d201eaae04728173e841efff2#p29912
>
>
http://www.tbsdtv.com/forum/viewtopic.php?p=28003#p28003
>
> I tried again to install open source drivers and I remember that when it arrives to first ia32 file it stops compiling:
>
> LD [M] /root/DriverCrazyCat/linux-tbs-drivers/v4l/tbs6980fe.o
> ld: /root/DriverCrazyCat/linux-tbs-drivers/v4l/tbs6980fe_driver.o: Relocations in generic ELF (EM: 3)
> ld: /root/DriverCrazyCat/linux-tbs-drivers/v4l/tbs6980fe_driver.o: Relocations in generic ELF (EM: 3)
> ld: /root/DriverCrazyCat/linux-tbs-drivers/v4l/tbs6980fe_driver.o: Relocations in generic ELF (EM: 3)
> ld: /root/DriverCrazyCat/linux-tbs-drivers/v4l/tbs6980fe_driver.o: Relocations in generic ELF (EM: 3)
> ld: /root/DriverCrazyCat/linux-tbs-drivers/v4l/tbs6980fe_driver.o: Relocations in generic ELF (EM: 3)
> ld: /root/DriverCrazyCat/linux-tbs-drivers/v4l/tbs6980fe_driver.o: Relocations in generic ELF (EM: 3)
> ld: /root/DriverCrazyCat/linux-tbs-drivers/v4l/tbs6980fe_driver.o: Relocations in generic ELF (EM: 3)
> ld: /root/DriverCrazyCat/linux-tbs-drivers/v4l/tbs6980fe_driver.o: Relocations in generic ELF (EM: 3)
> ld: /root/DriverCrazyCat/linux-tbs-drivers/v4l/tbs6980fe_driver.o: Relocations in generic ELF (EM: 3)
> ld: /root/DriverCrazyCat/linux-tbs-drivers/v4l/tbs6980fe_driver.o: Relocations in generic ELF (EM: 3)
> ld: /root/DriverCrazyCat/linux-tbs-drivers/v4l/tbs6980fe_driver.o: Relocations in generic ELF (EM: 3)
> /root/DriverCrazyCat/linux-tbs-drivers/v4l/tbs6980fe_driver.o: error adding symbols: File in wrong format
> make[3]:* [/root/DriverCrazyCat/linux-tbs-drivers/v4l/tbs6980fe.o] Error 1
> make[2]:* [_module_/root/DriverCrazyCat/linux-tbs-drivers/v4l] Error 2
> make[2]: Leaving directory `/usr/src/linux-headers-3.18.0-20-rpi2'
> make[1]:* [default] Error 2
> make[1]: Leaving directory `/root/DriverCrazyCat/linux-tbs-drivers/v4l'
> make:* [all] Error 2
>
>

> is it possible to avoid these files to see if that finishes compiling?

Those posts you linked to are for the TBS5280 not the +*5281*+ they are two different devices.

+There is no way of getting your device working on a Raspberry Pi because there are no open source drivers for it.+

There isn't much else that you can do apart from contacting lja & ask him to look into getting your device working with the open source drivers.

Pepe Suriano

I know they are two different devices, but the fact was the same, the idea was that they were TBS tuners (without drivers for ARM) that managed to work with RPI

In these post they mention that they used a patch, could it be applicable for 5881 maybe?

mpmc

Pepe Suriano wrote:
> I know they are two different devices, but the fact was the same,the idea was that they were TBS tuners (without drivers for ARM) that managed to work with RPI

TBS have many cards some drivers are open source some aren't and TBS won't release the source for those drivers due to NDA.

>In these post they mention that they used a patch, could it be applicable for 5881 maybe?

I very much doubt it, the devices might be completely different inside have different components and require different drivers. You could try it but I don't think it'll work not without some modification at least (whatever that may be).

+TBS great hardware shame about the shit drivers..+

Pepe Suriano

Hi, we tried with the patch and it worked!

tvheadend shows it as "Silicon Labs Si2168 : DVB-T #0", it does not display it as a DVBC device

I have read that tvheadend have some problems with multi-standard tuners, is there a possibility to make it work as DVBC also?

Regards

mpmc

Pepe Suriano wrote:
> Hi, we tried with the patch and it worked!
>
> tvheadend shows it as "Silicon Labs Si2168 : DVB-T #0", it does not display it as a DVBC device
>
> I have read that tvheadend have some problems with multi-standard tuners, is there a possibility to make it work as DVBC also?
>

> Regards

By works you mean:-

A) The driver is loaded and I can see the device.

B) The driver is loaded it tunes and I'm able to see a picture.

Tvheadend doesn't have those issues anymore and the Si2** does support DVB-C it's not showing up on yours because of a driver problem.

This is mine:-

http://i.imgur.com/b6L0qBX.png?1

HTH

Pepe Suriano

Which drivers have you used and how do you installed them?

Just to compare with mine's and see any difference (we have same demod)

Thanks for all

mpmc

Pepe Suriano wrote:
> Which drivers have you used and how do you installed them?
>
> Just to compare with mine's and see any difference (we have same demod)
>

> Thanks for all

Just the ones used in the standard kernel.