LibreELEC 8.x images for additional dvb drivers

  • Well, what can I say, installed the standard release and all is back to normal after reconfiguration.


    All three tuner are recognised and functional.


    So the bottom line is, don't try to fix it when it works.


    So sorry for bringing the (non) issue here

  • Ha it's .... me again.


    Just got another tuner, this time a tbs5520SE. I smacked it onto my stock raspberry (and the stiock 8.2 LS distro), got the following messages


    [1536489.022775] usb 1-1.1.2: new high-speed USB device number 8 using dwc_otg

    [1536489.116547] usb 1-1.1.2: New USB device found, idVendor=734c, idProduct=5521

    [1536489.116560] usb 1-1.1.2: New USB device strings: Mfr=0, Product=0, SerialNumber=0

    [1536489.140734] dvb-usb: found a 'TBS 5520se USB2.0' in cold state, will try to load a firmware

    [1536489.141001] usb 1-1.1.2: Direct firmware load for dvb-usb-tbsqbox-id5521.fw failed with error -2


    In the /lib/firmware I found a dvb-usb-tbsqbox-id5520.fw not the one for the tuner apparently.


    So what image should I use to see if that thing is working (being interrested by the multistream (DVB-S2X) and the DVB-C/DVB-S capabilities.


    Any hint ?

  • Did anyone try to backport drivers for the Khadas VIM2 dvb board. Its supposedly run from the kernel, but the driver embedded in the kernel will not scan channels because it was not sufficiently adapted from the KI pro driver it is based upon. I see little chance that it will be fixed within the kernel so is their a backport driver. It works within the Leia builds of CE but not within the test builds of LE Leia.


    Running Leia has been as right royal pain in the ass and I would dearly like to revert to a stable Krypton build on my VIM2.


    Shoog

  • Update,


    Loaded the cvh.libreelec.**/LibreELEC/8.2_Krypton/8.2.0/ on a card, but curiously it does not boot on my Pi3, it did on a pi2 though.


    Selected the original drivers from tbs, the firmware loads (not the same name as in the stock 8.2) but several kinky messages seems to indicate that the something is not fully working (and at least tvheadend server does not like it), I then tried the crazycat version, but same thing the firmware (same as above i.e. dvb-usb-tbsqbox-id5521.fw) is not found in the lib.


    I found a version here: dvb-firmware/firmware at master · AlexELEC/dvb-firmware · GitHub


    and also here : dvb-firmware/firmware at master · LibreELEC/dvb-firmware · GitHub


    But I'm not sure it will work with the driver if I can manage to get it in the squashfs.



    Ran out of ideas ...


    UPDATE: I see that the master on github is actually the 8.9 so I will give it a go later on today.

    Edited 3 times, last by jcoenen ().

  • Got the 8.9 alpha on a card and on the Pi2.


    Selected the tbs drivers and it locks up.


    The other driver options in the driver add-on do not recognise the TBS5520SE so no problems there.


    Tried without the device it boots and as soon as the device is connected, driver loads, firmware load and then locks up.


    Does not sound too good.

  • Selected the tbs drivers and it locks up.

    huh ? could you remotely access your box ?

    could you try

    disconnect the dvb box, choose the tbs drivers, then restart and then attach the usb dvb device again ?

  • Hi there,


    I was sitting next to the box with a keyboard attached, and it was froozen.

    Initially, I selected tbs drivers waited for the reboot, the tbs5520Se was attached, I ssh'd into the box, checked dmesg and I saw the firmware loading successfully, then some dump messages (Hex lines) and then it locked up.


    After I tried the other dvb drivers (just in case), the machine was stable, but as expected the device was not recognized.


    Re-selecting the tbs drivers resulted in a freeze shorlty after the kodi interface showed up.


    I also tried without attaching the device, waited for the boot to finish, ssh'd in, plug in the device and quckly checked dmesg, I haven't seen the hex dumps in dmesg but it locked up again as a result of the device being connected.


    I will try it out on a RPI3B+ tonight (which should not make any difference).

  • Really weird, I hooked it up on a raspberry 3 B+ using the same CD card, booted up, then connected it and here's the result


    usb 1-1.1.2: DVB: adapter 1 frontend 1 frequency 0 out of range (174000000..862000000)

    [ 508.748375] Unable to handle kernel paging request at virtual address fffffffe

    [ 508.748386] pgd = a37ac000

    [ 508.748391] [fffffffe] *pgd=2f7fa861, *pte=00000000, *ppte=00000000

    [ 508.748415] Internal error: Oops: 37 [#1] SMP ARM

    [ 508.748443] Modules linked in: si2157(O) av201x(O) si2183(O) dvb_usb_tbs5520se(O) dvb_usb(O) hci_uart bluetooth ecdh_generic rc_tt_1500(O) sp2(O) ts2020(O) brcmfmac brcmutil dvb_usb_dvbsky(O) m88ds3103(O) dvb_usb_v2(O) i2c_mux dvb_core(O) videobuf2_vmalloc(O) videobuf2_memops(O) videobuf2_common(O) videodev(O) media(O) rc_core(O) cfg80211 rfkill bcm2835_gpiomem fixed

    [ 508.748626] CPU: 3 PID: 626 Comm: tvh:tcp-start Tainted: G O 4.14.67 #1

    [ 508.748646] Hardware name: BCM2835

    [ 508.748662] task: a671f080 task.stack: a35e6000

    [ 508.748690] PC is at __kmalloc_track_caller+0x230/0x284

    [ 508.748708] LR is at 0xfffffffe

    [ 508.748724] pc : [<8026e2d0>] lr : [<fffffffe>] psr: a0070013

    [ 508.748743] sp : a35e7ca0 ip : 000002a4 fp : a35e7cdc

    [ 508.748761] r10: a0070013 r9 : 8074f61c r8 : ae8019c0

    [ 508.748779] r7 : 00000780 r6 : 014102c0 r5 : ae8019c0 r4 : a36f9000

    [ 508.748800] r3 : 00000000 r2 : af11bc94 r1 : a0070013 r0 : 000002a4

    [ 508.748821] Flags: NzCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment user

    [ 508.748843] Control: 10c5383d Table: 237ac06a DAC: 00000055

    [ 508.748862] Process tvh:tcp-start (pid: 626, stack limit = 0xa35e6210)

    [ 508.748882] Stack: (0xa35e7ca0 to 0xa35e8000)

    [ 508.748905] 7ca0: a35e7cf4 0000001a af114480 fffffffe 000005a8 a35e7d0f 014000c0 014000c0

    [ 508.748933] 7cc0: 8074f61c 00000780 a345cb00 a345cbf4 a35e7d04 a35e7ce0 8074f568 8026e0ac

    [ 508.748962] 7ce0: a3550780 000006b8 014000c0 00000001 ae8c4b40 a345cb00 a35e7d34 a35e7d08

    [ 508.748990] 7d00: 8074f61c 8074f540 a3550a80 a345cb00 000005a8 a345cb00 000005a8 00000000

    [ 508.749026] 7d20: a3550900 a345cb00 a35e7d5c a35e7d38 807b96d8 8074f5c0 000005a8 000005a8

    [ 508.749060] 7d40: 000005a8 000005a8 00000000 00000000 a35e7e2c a35e7d60 807ba2a0 807b9688

  • As for the detection ...


    [ 266.616738] usb 1-1.2: USB disconnect, device number 4

    [ 266.825246] usb 1-1.2: new full-speed USB device number 7 using dwc_otg

    [ 266.971256] usb 1-1.2: New USB device found, idVendor=076b, idProduct=3021

    [ 266.971267] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0

    [ 266.971272] usb 1-1.2: Product: Smart Card Reader USB

    [ 266.971276] usb 1-1.2: Manufacturer: OMNIKEY AG

    [ 271.485552] usb 1-1.1.2: new high-speed USB device number 8 using dwc_otg

    [ 271.575816] usb 1-1.1.2: New USB device found, idVendor=734c, idProduct=5521

    [ 271.575832] usb 1-1.1.2: New USB device strings: Mfr=0, Product=0, SerialNumber=0

    [ 271.600731] dvb-usb: found a 'TBS 5520se USB2.0' in cold state, will try to load a firmware

    [ 271.614110] dvb-usb: downloading firmware from file 'dvb-usb-tbsqbox-id5521.fw'

    [ 271.614127] tbs5520se: start downloading TBS5520se firmware

    [ 271.728884] dvb-usb: found a 'TBS 5520se USB2.0' in warm state.

    [ 271.729265] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.

    [ 271.736627] dvbdev: DVB: registering new adapter (TBS 5520se USB2.0)

    [ 271.736643] usb 1-1.1.2: media controller created

    [ 271.736767] tbs5520se: read eeprom failed.

    [ 271.736771] dvb-usb: MAC address reading failed.

    [ 271.737576] dvbdev: dvb_create_media_entity: media entity 'dvb-demux' registered.

    [ 271.744276] i2c i2c-5: Added multiplexed i2c bus 6

    [ 271.744288] si2183 5-0067: Silicon Labs Si2183 successfully attached

    [ 271.749105] i2c i2c-6: av201x: Airoha Technology AV201x successfully attached

    [ 271.793660] usb 1-1.1.2: USB disconnect, device number 8

    [ 271.916121] si2157 6-0061: Silicon Labs Si2147/2148/2157/2158 successfully attached

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

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

    [ 271.916458] usb 1-1.1.2: DVB: registering adapter 1 frontend 1 (Silicon Labs Si2183)...

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

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

    [ 271.917533] usbcore: registered new interface driver tbs5520se

    [ 271.930730] dvb-usb: TBS 5520se USB2.0 successfully deinitialized and disconnected.

    [ 273.535651] usb 1-1.1.2: new high-speed USB device number 9 using dwc_otg

    [ 273.626060] usb 1-1.1.2: New USB device found, idVendor=734c, idProduct=5521

    [ 273.626069] usb 1-1.1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0

    [ 273.626074] usb 1-1.1.2: Product: TBS 5521

    [ 273.626078] usb 1-1.1.2: Manufacturer: TBS-Tech

    [ 273.626583] dvb-usb: found a 'TBS 5520se USB2.0' in cold state, will try to load a firmware

    [ 273.626601] dvb-usb: downloading firmware from file 'dvb-usb-tbsqbox-id5521.fw'

    [ 273.626607] tbs5520se: start downloading TBS5520se firmware

    [ 273.738993] dvb-usb: found a 'TBS 5520se USB2.0' in warm state.

    [ 273.739301] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.

    [ 273.746882] dvbdev: DVB: registering new adapter (TBS 5520se USB2.0)

    [ 273.746900] usb 1-1.1.2: media controller created

    [ 273.822615] dvb-usb: MAC address: 00:22:ab:c0:4c:58

    [ 273.823519] dvbdev: dvb_create_media_entity: media entity 'dvb-demux' registered.

    [ 273.828927] i2c i2c-5: Added multiplexed i2c bus 6

    [ 273.828937] si2183 5-0067: Silicon Labs Si2183 successfully attached

    [ 273.829027] i2c i2c-6: av201x: Airoha Technology AV201x successfully attached

    [ 273.834929] si2157 6-0061: Silicon Labs Si2147/2148/2157/2158 successfully attached

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

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

    [ 273.895519] usb 1-1.1.2: DVB: registering adapter 1 frontend 1 (Silicon Labs Si2183)...

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

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

  • For information, I installed on an old laptop ubuntu 16 (32 bit processor) and proceeded with recompilation of the drivers picked up from the TBS website, then compiled and installed tvheadend (apt-get not working).


    Rebooted, plugged in the TBS5520SE, started tvheadend, drivers loaded, device is seen by tvheadend.

    Connected my Disec, config TVHeadend and scanned the Satellites, I got everything including the multistream.


    Haven't tried the DVBC as I don't have a feed at the moment.

  • are that the old drivers or these Home · tbsdtv/linux_media Wiki · GitHub ?

    I am trying to make the TBS5520SE working on LE too, using Odroid C2. Having same problem as JC, tried also with some older version of TBS open source drivers I have installed on my Debian box half year ago and it was instantly detected and working perfectly...


    Have been playing with CE as there is no CvH LE build for Odroid C2... but in general its completely same on CE/Odroid and LE/Rpi3

  • The one I recompiled on my laptop (intel 32 bits) and on a NUC (intel 64) were picked up from

    hxxp*://github.com/tbsdtv/linux_media/wiki


    Both instances are working, I can access both DVBT and DVBS devices (not simultaneously though, but that's normal I guess).

    The only drawback is that if a EPG grab is running on the DVBS it locks the device and I cannot use a stream from the DVBT.

    To be fair, tvheadend does not expect both DVBs running on the same USB device. I disabled the EPGgrab and since then I can switch back and forth between DVBT and DVBS.


    Sorry for the delay.

  • Hi,

    should I try tis version for DVBSky S960 DVB-S2? It has a long lasting problem on newer kernels.

    Or maybe an LE 9 Alpha version (if I'm correct, the additional drivers are included in LE 9.x versions?).


    Running Rpi2.


    Thanks.