Dual TBS 5520SE Libreelec 9.0.0 Intel Generic

  • Hi All, I've just updated to 9.0.0.

    I have 2 x TBS 5520SE that i have been using with TVHeadend on an Ubuntu box for some time.

    As LibreElec 9 has the TBS drivers as an option i thought i'd move my TVHeadend to the LibreElec box.

    With 1 tuner it works perfectly but as soon as i plug 2 tuners in and boot i get a kernel panic.

    With Ubuntu i use the TBS driver addition to media_build and 2 tuners work fine.

    any thoughts?

    Thanks


    Dave

  • I went through each of the driver add-ons and only the TBS one resulted in my tuner being detected after a reboot. I then tried adding the second tuner and it kernel panicked

  • TBS 5520 SE single unit on raspberry pi 3, thanks for the progress on this receiver driver by the way.

    I have used successfully the DVB-S and DVB-S2 (multistream) function, so far so good (4 LNBs on a DISEC)

    DVB-T, works as well with my mini antenna, unfortunately I have a limited signal coming in, so can't say much on this one.

    DVB-C, it seems that somehow the tuner is limited to UHF

    dmesg:

    [ 10.499247] si2183 3-0067: found a 'Silicon Labs Si2183-B60'

    [ 10.526574] si2183 3-0067: downloading firmware from file 'dvb-demod-si2183-b60-01.fw'

    [ 11.162743] si2183 3-0067: firmware version: 6.0.13

    [ 11.385472] usb 1-1.3: DVB: adapter 0 frontend 0 frequency 0 out of range (950000..2150000) Satellite segment OK

    [ 11.427817] si2157 4-0061: found a 'Silicon Labs Si2157-A30'

    [ 11.442484] si2157 4-0061: downloading firmware from file 'dvb-tuner-si2157-a30-01.fw'

    [ 11.885392] si2157 4-0061: firmware version: 3.1.3

    [ 11.885452] usb 1-1.3: DVB: adapter 0 frontend 1 frequency 0 out of range (174000000..862000000) this looks fine VHF and UHF

    [ 13.493109] Bluetooth: Core ver 2.22


    using the linux DVB log I found that

    2019-02-08 15:56:23.621 [ INFO]:mpegts: 586MHz in VOOBis - scan no data, failed

    2019-02-08 15:56:23.622 [ INFO]:subscription: 00F8: "scan" unsubscribing

    2019-02-08 15:56:23.622 [ DEBUG]:linuxdvb: Silicon Labs Si2183 #0 : DVB-C #1 - stopping 586MHz in VOOBis

    2019-02-08 15:56:23.622 [ INFO]:mpegts: 330MHz in VOOBis - tuning on Silicon Labs Si2183 #0 : DVB-C #1

    2019-02-08 15:56:23.622 [ DEBUG]:linuxdvb: Silicon Labs Si2183 #0 : DVB-C #1 - starting 330MHz in VOOBis

    2019-02-08 15:56:23.622 [ ERROR]:linuxdvb: Silicon Labs Si2183 #0 : DVB-C #1 - failed to tune [e=Invalid argument]

    2019-02-08 15:56:23.623 [ INFO]:mpegts: 458MHz in VOOBis - tuning on Silicon Labs Si2183 #0 : DVB-C #1

    2019-02-08 15:56:23.623 [ DEBUG]:linuxdvb: Silicon Labs Si2183 #0 : DVB-C #1 - starting 458MHz in VOOBis

    2019-02-08 15:56:23.623 [ ERROR]:linuxdvb: Silicon Labs Si2183 #0 : DVB-C #1 - failed to tune [e=Invalid argument]

    2019-02-08 15:56:23.623 [ INFO]:mpegts: 338MHz in VOOBis - tuning on Silicon Labs Si2183 #0 : DVB-C #1

    2019-02-08 15:56:23.623 [ DEBUG]:linuxdvb: Silicon Labs Si2183 #0 : DVB-C #1 - starting 338MHz in VOOBis

    2019-02-08 15:56:23.623 [ ERROR]:linuxdvb: Silicon Labs Si2183 #0 : DVB-C #1 - failed to tune [e=Invalid argument]

    2019-02-08 15:56:23.624 [ INFO]:mpegts: 482MHz in VOOBis - tuning on Silicon Labs Si2183 #0 : DVB-C #1

    2019-02-08 15:56:23.624 [ DEBUG]:linuxdvb: Silicon Labs Si2183 #0 : DVB-C #1 - starting 482MHz in VOOBis

    2019-02-08 15:56:23.624 [ INFO]:epggrab: 482MHz in VOOBis - registering mux for OTA EPG

    2019-02-08 15:56:24.636 [ INFO]:subscription: 00FD: "scan" subscribing to mux "482MHz", weigh: 6, adapter: "Silicon Labs Si2183 #0 : DVB-C #1", network: "VOOBis", service: "Raw

    PID Subscription"

    So above 470 MHz I can get a scan going, but in VHF, I can't.

    dmesg I see this too during the VHF scan.

    usb 1-1.3: DVB: adapter 0 frontend 1 frequency 386000000 out of range (470000000..862000000)

    So basically I can scan UHF channels but not the VHF (out of range)

    Is there anything I can change to enable VHF on the DVB-C tuner ?

  • About kernel panic and.the tbs5520se, it happened to me when I powered the tuner via a raspberry usb port, when the tuner is powered by an independant power supply no more kernel panic.

  • crazycat


    Back on the matter:


    Checked the addon, looks like the last version available, the addon update procedure comes back with currently no update for this addon.

    In dmesg in red, one reports that frequency 0 is out of range and the range is 174000000..862000000 unlike in the source code that sets it to 47000000 to 862000000.

    then thereafter it reports the range being 470000000..862000000

    so 470 Mhz to 862 Mhz

    Looks like the range has been redefined somewhere and is not what is should be from the source.

    [ 9.663739] usb 1-1.4: DVB: registering adapter 0 frontend 0 (Silicon Labs Si2183)...

    [ 9.663779] dvbdev: dvb_create_media_entity: media entity 'Silicon Labs Si2183' registered.

    [ 9.664096] usb 1-1.4: DVB: registering adapter 0 frontend 1 (Silicon Labs Si2183)...

    [ 9.664112] dvbdev: dvb_create_media_entity: media entity 'Silicon Labs Si2183' registered.

    [ 9.665738] dvb-usb: TBS 5520se USB2.0 successfully initialized and connected.

    [ 10.223527] si2183 3-0067: found a 'Silicon Labs Si2183-B60'

    [ 10.260105] si2183 3-0067: downloading firmware from file 'dvb-demod-si2183-b60-01.fw'

    [ 10.829542] si2183 3-0067: firmware version: 6.0.13

    [ 11.042009] usb 1-1.4: DVB: adapter 0 frontend 0 frequency 0 out of range (950000..2150000)

    [ 11.074038] si2157 4-0061: found a 'Silicon Labs Si2157-A30'

    [ 11.085370] si2157 4-0061: downloading firmware from file 'dvb-tuner-si2157-a30-01.fw'

    [ 11.480807] si2157 4-0061: firmware version: 3.1.3

    [ 11.480873] usb 1-1.4: DVB: adapter 0 frontend 1 frequency 0 out of range (174000000..862000000)

    [ 12.990290] Bluetooth: Core ver 2.22

    [ 12.990392] NET: Registered protocol family 31

    [ 12.990398] Bluetooth: HCI device and connection manager initialized

    [ 12.990421] Bluetooth: HCI socket layer initialized

    [ 12.990430] Bluetooth: L2CAP socket layer initialized

    [ 12.990458] Bluetooth: SCO socket layer initialized

    [ 12.996125] Bluetooth: HCI UART driver ver 2.3

    [ 12.996142] Bluetooth: HCI UART protocol H4 registered

    [ 12.996260] Bluetooth: HCI UART protocol Three-wire (H5) registered

    [ 12.996459] Bluetooth: HCI UART protocol Broadcom registered

    [ 1899.463754] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xDDE1

    [ 1899.468463] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready

    [ 1899.477012] 8021q: 802.1Q VLAN Support v1.8

    [ 1970.251834] usb 1-1.4: DVB: adapter 0 frontend 1 frequency 394000000 out of range (470000000..862000000)

    [ 1970.252155] usb 1-1.4: DVB: adapter 0 frontend 1 frequency 378000000 out of range (470000000..862000000)

    [ 1970.252385] usb 1-1.4: DVB: adapter 0 frontend 1 frequency 362000000 out of range (470000000..862000000)

    [ 1970.252601] usb 1-1.4: DVB: adapter 0 frontend 1 frequency 354000000 out of range (470000000..862000000)

    [ 1970.252841] usb 1-1.4: DVB: adapter 0 frontend 1 frequency 466000000 out of range (470000000..862000000)

    [ 1970.253044] usb 1-1.4: DVB: adapter 0 frontend 1 frequency 290000000 out of range (470000000..862000000)

    [ 1975.254176] usb 1-1.4: DVB: adapter 0 frontend 1 frequency 346000000 out of range (470000000..862000000)

    [ 1975.257073] usb 1-1.4: DVB: adapter 0 frontend 1 frequency 370000000 out of range (470000000..862000000)

    Edited 3 times, last by jcoenen (February 13, 2019 at 10:53 AM).

  • The tbs5520SE related driver (inc bug fix) has been compiled and is available here. Tested this morning on DVB-C, the VHF band is now available. Now I have to figure out a way to cable up both my satellite feed and cable TV in the same location (but that's hardware). Cheers to all the developpers.