Posts by NooN

Hello CvH,

I tried to get the system better known.
Do you know if it is possible to use the u-boot to first boot from network (it seems possible to put the kernel and system file on tftp/nfs) and if this does not work, that the emmc/sd will get used?
I have the feeling, that the emmc connector is not build to get disconnected and connected so much.
Alternatively first boot from sd than from emmc.

The systems I build are not working so well. The process seems not so easy and lengthy.
The kernel drivers from the media_build are put into an extra directory. Can it be that there will be an mix from the kernel drivers and the media_build drivers be loaded that did not work correctly?

I bought a new receiver the haupage solohd that I thought is a good choice. But the patch for it is not in the old 3.14 kernel and I did not get it working. My plan is to use the C1 as an headless DVB-T/T2 server and the C2 as kodi device on the tv. So I can put an new Kernel on the C1 and with luck this will work (it i get this to work, maybe). Otherwise an old laptop must do this job.
I'm a little disappointment how hard this is.

Greetings NooN

Hello CvH,

at the moment I'm asking my self if it is worth the effort.
Where I life is in really near future the transition to DVB-T2.
I'm still looking at the market to find the best stick to use with Linux and Kodi...
But this is an other problem...

If there is demand that this stick works, I will continue to try to solve the issue.

Hello,
the image from Kszaq did not work. I tried different dtd files an nothing happend on the screen or network.
So I tried an other way with the help of a friend:
We used the old Image from wrxtasy with his kernel.
Then we unpacked the system image and put into it the kernel modules and libMali.so.

The system then boots and gives a strange message about "boot=" that i can't completly read. It get's cut left and on the top. seems something to do with the television.
After 60s the system boots normaly.

Then I can install tvheadend and the A800 receiver get's recognized. Also the scan works and the tv stations are found.
dmesg is: USXf
the tvheadend log is: LdQc

Something that puzzeled me is:
The kernel is newer. wrxtasy used a 3.14.65 version. Your Image has the version 3.14.29.
The libMali.so of yout image did not work: there was a version difference: 9.00 to 8.00.
Replaceing it fixed this problem.

The only thing that's bugging me: the resolution is not stable in this kernel. The screen get's distored and recovers now and then. This is why I want to use an other image in the first place.

I don't know where to go from this point on. Is it hard to make this images? maybe I can try to incorperate the 3.14.65 kernel in the normal way.?

Thanks for your help.

I tried to debug the problem with tvheadend and the dvb-tuner
Maybe the config von wrxtasy can help you, this is the last working image that worked for me.
Thanks for your help

log from "HTS Tvheadend 4.1.2401" with the config "CRASH,main,fastscan,dvb,linuxdvb,scanfile": RggG
dmesg: NZiG

This is from the last working version I have.
Version string:LibreELEC (WRXTASY) Version: 7.1.0
dmesg: hRXJ
log from "HTS Tvheadend 4.1.2401" with config "CRASH,main,fastscan,dvb,linuxdvb,scanfile": MCDT
the kernel config from /proc/config.gz: iPAc

Hello,

I tried the image. There is a driver and the A800 is visible in tvheadend.
But I did not get the tuner set or an mux configured.
This is very strange.
The dmesg output is there: KbiG

Thank you for your time and effort.

Wow. This kernel is almost 3 years old. What does an update prevent to 4.9 or at least 3.17 (this is the last kernel with LTS until 2017)?

Has the driver so much changed between the libreelec kernel and the mainline linux kernel?

Hello CvH,

I tried your image and I'm sorry to say that it does not work with the DVB-T adapter.
The dmesg|paste got me this URL: eKdL

lsmod does not show the module:

LibreELEC:~ # lsmod
Module                  Size  Used by
8021q                  19087  0
rtc_pcf8563             3551  0
dvb_usb_dibusb_common     4554  0
dib3000mc              12024  0
dibx000_common          6664  1 dib3000mc
dvb_usb                21063  1 dvb_usb_dibusb_common
dvb_core               88767  1 dvb_usb
ir_lirc_codec           5044  3
lirc_dev                8136  1 ir_lirc_codec
meson_ir                3793  0
rc_core                18885  5 lirc_dev,meson_ir,ir_lirc_codec,dvb_usb
mali                  200880  5
amlvideodri            10882  0
videobuf_res            5594  1 amlvideodri
videobuf_core          16779  2 amlvideodri,videobuf_res
videodev              146341  1 amlvideodri
media                  21290  3 dvb_usb,videodev,dvb_core
autofs4                24843  0
fbcon                  37535  0
bitblit                 4444  1 fbcon
softcursor              1200  1 bitblit
font                    7279  1 fbcon

In the /proc/config.gz there is also the "CONFIG_DVB_USB_A800" not set.
I think the driver/module got not build

Thanks for your help.

Hello CvH,

I can test an image and have a Odroid-C2.
I found out, that there is also a firmware-file needed: dvb-usb-avertv-a800-02.fw
That can I extract from an image from wrxtasy.

Hello,

could you please activate the Avermedia DVB-T A800 driver in the Kernel.
The name of the option is CONFIG_DVB_USB_A800.

Thanks