Posts by mpavlis76

I assume your message wasn't for me, because I definitely used the mentioned "LibreELEC driver selection" add-on.

But what can I do about one driver crashing? I can't do anything about it, or is there a solution? And what is it?

Output after using the command: dmesg | grep frontend

[    3.543617]  c8f6c28b0df073b94e8e835504fd3c12a63ee315 media: dvb-frontends/stid135: Updates from LLA 1.4.0.
[    3.544755]  c8f6c28b0df073b94e8e835504fd3c12a63ee315 media: dvb-frontends/stid135: Updates from LLA 1.4.0.
[    3.758109] TBSECP3 driver 0000:05:00.0: DVB: registering adapter 1 frontend 0 (STV091x Multistandard)...
[    3.879910] TBSECP3 driver 0000:05:00.0: DVB: registering adapter 2 frontend 0 (STV091x Multistandard)...
[    3.970257]  dvb_register_frontend+0x1f4/0x290 [dvb_core]
[  183.478659] TBSECP3 driver 0000:05:00.0: frontend register failed
[  183.599179] TBSECP3 driver 0000:05:00.0: frontend register failed

And here are the outputs after execution: dmesg | paste

Output from Kodi 18.x:

http://ix.io/3q3p

Output from Kodi 19.x:

http://ix.io/3q3y

The only difference should be only a few seconds during reboot, otherwise everything is exactly the same (hardware).

Thank you very much for any help,

Martin

Dears,

I have a plese for anyone who's able or willing to help me. At the moment I have a classic PC on which I am running LE on LibreELEC-Generic.x86_64-9.2.6.img.gz. Everything is fine here. As part of the upcoming migration to LibreELEC-Generic.x86_64-9.95.4.img.gz, I have a second disk in that PC and by simply specifying it within the BIOS, I learn which disk I want to boot from, which allows me to test the new version in peace.

My please is that there are two DVB-S2 cards in the PC:

- TBS 6905 (Quad DVB-S/S2)

- TechnoTrend TT-Budget S2-3200

On the existing Kodi, I selected CrazyCat as drivers using the LibreElec Module Drivers add-on, did a reboot and everything works as it should. If I do the same on the new Kodi 19.x, nothing happens and the system just doesn't "see" the card.

PS: I realized that in the past I uploaded TBS6905 firmware through the network into the "Configfiles/firmware/tbs6905" path, so I copy this folder 1:1 to the same location in the new Kodi. Unfortunately without any change.

Would someone be so kind and helpful as to advise me how I can get these satelite cards working in Kodi 19.x, please?

There are logs from my two Kodi installation on same computer:

- log from Kodi 18.9: http://ix.io/3pFF

- log from Kodi 19.1: http://ix.io/3pFE

Thank you in advance,

Martin

Sorry for my beginner's question, but won't I lose the possibility to use my satellite TV tuners in LibreELEC?

[   12.360161] TBSECP3 driver 0000:05:00.0: DVB: adapter 4 frontend 0 frequency 0 out of range (950000..2150000)
[   12.362360] TBSECP3 driver 0000:05:00.0: DVB: adapter 3 frontend 0 frequency 0 out of range (950000..2150000)
[   12.364753] TBSECP3 driver 0000:05:00.0: DVB: adapter 2 frontend 0 frequency 0 out of range (950000..2150000)
[   12.544195] budget_ci dvb 0000:04:00.0: DVB: adapter 1 frontend 0 frequency 0 out of range (950000..2150000)
[   12.546170] TBSECP3 driver 0000:05:00.0: DVB: adapter 0 frontend 0 frequency 0 out of range (950000..2150000)

Here is it: http://ix.io/3orN

Hi, same with me - this error was same in beta 1, beta 2 and beta 3.

The problem is, that when I initiate a system reboot, it will stop on this error an never reboot it.

I’m looking here for changes: Jenkins

Guys - unfortunately, I have to say that this add-on still doesn't work properly. Today I tried for few hours to find some / any solution, but without success. My testing was with Skylink CZ/SK add on - IPTV and access to their archive, with full support of developer of that Plugin.

Leia> Current version 2.4.7.1: unfortunately not able to play anything from Archive (except Sport 1, which works incomprehensibly), Live TV on the contrary works without problems

Matrix> Current version 2.6.13: unfortunately nothing works, except for one program within Live TV, the ČT24 program (not encrypted)

I tried to promote and humiliate the InputStream add-on to different versions, but unfortunately I couldn't find any working variant.

Any idea, what to do with it please?

PS: looks like that this problem is now known to Inputstream Adaptive addon, but nobody knows, when requested change will be merged to final code