So, is there an easy way to switch to Raybuntu's Version of Libreelec without loosing my complete setup?
Or does anyone know where to find the dvb driver in LE's filesystem so that I can try to replace the exising driver with the better one, without changing the whole LE installation/setup?
What does "without vdr support" exactly mean? --> I'm, no longer able to record live-tv with tvheadend? So also no timeshift?
The idea with improving the signal:
I have an quattro LNB --> round about 5..6m antenna cable (120dB version) --> a F-plug to F-plug connector to get the shielding grounded --> round about 10..15m antenna cable --> a quattro to 8 receiver multiswitch (with built in amplifier for each of the 4 inputs, all 4 channels are using max amplification) --> round about 10..15m antenna cable to the antenna wall-plug in the living room ---> 1,5m antenna cable to wetek play 2 box.
This setup worked for last 3 years (since installation) without any hassle with Dreambox 800HD and now with Wetek Play 2 with WeOS.... It's still strange to me that this is now an "driver" issue. But anyhow... On next weekend I try to improve the receiving signal on the antenna by fine tuning it.
Beside that, I'm not sure where to add an additional signal amplifier.. maybe at the F-plug-to-F-plug connector?
[hr]
I found out, that the LE build process (also raybuntu...) is getting it's drivers from here:
so, f.i.
Index of /devel/
Index of /devel/
-->
wetekdvb-20160307.tar.xz 10-Jul-2016 15:25 19100
wetekdvb-20160930.tar.xz 29-Sep-2016 23:45 31172
wetekdvb-20161127.tar.xz 27-Nov-2016 12:39 31188
wetekdvb-20170116.tar.xz 18-Jan-2017 10:38 31180
the archive contains .ko file, as well as firmware files.
The .ko driver file is put here:
/usr/lib/modules/3.14.29/wetekdvb/wetekdvb.ko
The firmware is copied to this folder:
/usr/lib/firmware
According to my installation, the md5sum indicates (compared to the content of the above mentioned archives), that the driver is from 20170116 version:
605b7b5ba2fbd266edb0e827197088e2 wetekdvb.ko
Would be great if zbigzbig20 can check the md5sum as well ("md5sum /usr/lib/modules/3.14.29/wetekdvb/wetekdvb.ko"), so that I try the "working one".
Sadly, /usr/lib/... is read-only mounted. But this is not a big issue
[hr]
Another question which is currently rising:
The wetek dvb driver is a kind of "binary blob" that directly comes from wetek.
So, why is WeOS (with latest updates) working quite well and Kodi with TVheadend is struggling with signal quality, if obviously both use the same driver?