Posts by erbas

  • Test LibreELEC images with KODI-19 for S9xxx

    Quote from DoktorX

    this setup for libreelec is complicated, on coreelec i create sd card put card in box and its working

    Feel free to use whatever you want!

    I don't think you read the post: Test LibreELEC images with KODI-19 for S9xxx

    Everything here is in tests we use the latest kernel!

    We are development supporters!

    These buildings may not be for you.

  • Test LibreELEC images with KODI-19 for S9xxx

    Quote from DoktorX

    ok so first problem that i solved was that i was unable to boot libreelec image in the first place and then i figure out that i need to run aml_autoscript.zip but that did not work so i reflashed my box firmware and i was able to use aml_autoscript.zip file and boot to libreelec.


    But now i cant use remote and i'm not sure if my dtb file is correct i used meson-gxm-q201.dtb but remote is not working i have try to add file remote.conf from coreelec sdcard root to libreelec sdcard root but this is not working

    Everything here is totally different from CoreELEC if you need support for CoreELEC.

    Make a brief reading of the first post!


    2. The start system in Coreelec is not compatible with LibreELEC, Armbian etc. If you run coreelec on your TV box, you will no longer be able to run LE and Armbian normally until the full recovery of the standard firmware via the USB Burn Tool and the new activation of the universal multi-boot, which is used in all new systems.

    Test LibreELEC images with KODI-19 for S9xxx


    Try using the KI Pro files! (control and the same model)

    Code
    1. copy rc_maps.cfg to /storage/.config
    2. copy mecool to /storage/.config/rc_keymaps

    Just restart the box.

    If it doesn't work, check if the files are white and blank, just copy and paste manually.

    mecool k1 pro (2).zip

  • Test LibreELEC images with KODI-19 for S9xxx

    Quote from DoktorX

    Ok so i dont get a'm i stupid of what, but how do i run this on my mecool pro l (s912)?

    I have downloaded and burn sd card with LibreELEC-ARMv8.arm-9.80-devel-20200626140824-569f834-amlgx.img image file and put that sd card back in tv box and when i power on tv box i see mecool logo and then i start boot android, i have try to press menu button on remore when box is booting in order to boot from sd card but nothing is working


    ps

    i can boot coreelec from sd card so i know that sd card reader on tv box is working

    Please note that the DTB configuration order has changed.

    Now a single configuration method is used for all Rockchip Allwinner Amlogic platforms. The file (uEnv.txt) is used for configuration DTB all platforms.

    Now a single configuration method is used for all platforms, using the file (uEnv.txt). You need to edit this file to configure it. You need to uncomment the two lines that are responsible for your platform and specify the correct DTB for your model. If you use this image to run on the one platform, you can delete it from the settings file (uEnv.txt) strings from other platforms.

    Test LibreELEC images with KODI-19 for S9xxx

    Edit the file (uEnv.txt)

    Place the model for your box.

    Here as an example: meson-gxl-s905x-p212.dtb

    Code
    1. FDT=/dtb/amlogic/meson-gxl-s905x-p212.dtb
    2. LINUX=/KERNEL
    3. APPEND=boot=LABEL=LIBREELEC disk=LABEL=STORAGE quiet console=ttyAML0,115200n8 console=tty0 systemd.debug_shell=ttyAML0

    If universal multiple upload has not yet been enabled on this device

    Single Armbian image for RK + AML + AW (aarch64 ARMv8) - TV boxes - Armbian forum

  • Building older 9.0.x images from source

    Quote from CvH

    add to make_target an command that deletes all modules that you are not interested in, so all that just dvb modules are there at the build folder

    you need to compile the full stack and remove it afterwards, if you disable it at compile time it won't work at all

    LibreELEC.tv/package.mk at master · LibreELEC/LibreELEC.tv · GitHub

    Can you help with this command?

    I just need the driver for TBS5520SE

    Don't know how to create the same!

  • Can't set up tvheadend server

    Be welcome!

    try another tvheadend.

    Perhaps the latest one will work, it will solve your problem.

    Tvheadend nightly builds for LibreELEC

    in your case raspberry pi 4

    RPi4-service.tvheadend42-4.3-1885.zip

    in the browser use: ip_raspberry_4:9981

    Tvheadend is in the repository, LibreELEC, Services. (More needs to be installed).


    Maybe it helps you!

    step by step.


    1. Install TVheadend add-ons

    From main Kodi menu:
    Add-ons - Install from repository - LibreELEC Add-ons - Services - Tvheadend Server 4.2 - Install
    Then:
    Add-ons - Install from repository - LibreELEC Add-ons - PVR clients - Tvheadend HTSP Client - Install
    No configuration on the LibreELEC box is required.


    2. Configure TVheadend from a PC/Mac

    Find the IP address of your LibreELEC box. From main Kodi menu:
    Settings - System information
    On a PC/Mac using a web browser visit IP:9981 (for example, 192.168.0.1:9981)
    The first screen allows you to select interface and EPG language.
    Select relevant languages and select Save & Next.

  • Test LibreELEC images with KODI-19 for S9xxx

    Quote from chewitt

    erbas I'm already on Linux 5.6 and will bump LE master to Linux 5.7 around 5.7-rc2 to keep the patch count under control. This means I am always working on a kernel one version ahead of working media_build support (which always lags) so there's no point in adding the drivers. Once video and audio things are more upstream (around 5.8) we can probably realign with the x86_64 kernel version and reintroduce those drivers.


    NB: News on the DVB front is that I submitted the missing pinctrl change on behalf of afl1 (his first in-abstentia commit to the kernel) and those are now merged upstream for Linux 5.7 .. and we've been coaching Availink on their efforts to provide public and modernised sources for their demod and some related tuner drivers. The mainline codebase will need someone to write a new V4L2 compatible demux driver, but I think that can be done, maybe by the Availink folks. I wouldn't expect usable code anytime soon, but there's light at the end of yet another long dark tunnel.

    chewitt Things are evolving this way!

    Does it bring any progress, any improvements?

    Will we have news?

    At what stage does this kernel version put LibreELEC?

    When can we start playing?

    LKML: Linus Torvalds: Linux 5.8-rc1

  • Building older 9.0.x images from source

    I'm not good at this, and it's not an easy task for me.

    Have a little patience. For the second step add to make_target, I have no idea how to solve it!

    but I am quarantined tried (I am only good at following ready commands)^^^^


    Well I managed to make the first step!

    Construcão LibreELEC 9.2.1, Commits · LibreELEC/LibreELEC.tv · GitHub

    after construction I put it on an SD card and the crazycat driver was ready for activation.

    I connected the TBS5520SE but did not detect tuners.

  • Building older 9.0.x images from source

    Quote from CvH

    The main problem is that media_build (or more specific the media_tree that is build by media_build) includes a lot drivers around the new mainline stack for decoding and whatnot at the gpu/soc. So if you use some media_build with some version of media_tree you loose all patches/fixes/improvements that are avaibvle at the normal kernel.

    The situation gets better and better with more stuff is finally merged at the kernel. We have also a idea how to fix the remaining parts but that is highly hacky - but is likely working (just copy DVB modules instead the whole media_tree stuff build by media_build).


    Of course you could merge it all down into a single kernel, but this is basically not maintainable.

    I don't know if that information comes and it can help in something!

    After going round in a circles I've managed to build a kernel with support for this device.

    I _think_ the problem is that the kernels shipped since 4.9.59 have multimedia support built in to the kernel instead of as a module. When we build the crazycat build, it wants to replace the multimedia module but it gets ignored if it's built in.

    Building crazycat's media_build on RPi3 - Raspberry Pi Forums


    highly hacky - but is likely working (just copy DVB modules instead the whole media_tree stuff build by media_build).

    You can direct me to this provisional situation.

    I would like to try this method!