Posts by dmarkey

    A few problems on the X96max 2gb (I believe this is gigabit NIC) - with a build of the latest github branch.

    NIC not starting:

    Code
    [   15.752794] meson8b-dwmac ff3f0000.ethernet: Failed to reset the dma
    [   15.752808] meson8b-dwmac ff3f0000.ethernet eth0: stmmac_hw_setup: DMA engine initialization failed
    [   15.752815] meson8b-dwmac ff3f0000.ethernet eth0: stmmac_open: Hw setup failed

    HVEC crash

    Code
    [  565.048555] meson-vdec ff620000.video-decoder: Direct firmware load for meson/vdec/g12a_hevc.bin failed with error -2
    [  565.048571] meson-vdec ff620000.video-decoder: Unable to request firmware meson/vdec/g12a_hevc.bin
    [  565.074145] meson-vdec ff620000.video-decoder: Direct firmware load for meson/vdec/g12a_hevc.bin failed with error -2
    [  565.074162] meson-vdec ff620000.video-decoder: Unable to request firmware meson/vdec/g12a_hevc.bin
    [  565.094814] meson-vdec ff620000.video-decoder: Direct firmware load for meson/vdec/g12a_hevc.bin failed with error -2
    [  565.094829] meson-vdec ff620000.video-decoder: Unable to request firmware meson/vdec/g12a_hevc.bin
    [  565.105612] meson-vdec ff620000.video-decoder: Direct firmware load for meson/vdec/g12a_hevc.bin failed with error -2
    [  565.105625] meson-vdec ff620000.video-decoder: Unable to request firmware meson/vdec/g12a_hevc.bin

    CEC also fails in initialise.

    Anyone know the git

    Updated image Libreelec_s905_aarch64_20180425.

    Other options for s912 and arm will be added later as build and test.

    Major change.

    1. The shared dtb file (dtb.img) is excluded from the image. The startup script will attempt to use dtb data from internal memory. If the system fails to start in this mode, you must manually copy the correct file from the /device_trees directory to the root and rename it to "dtb.img " (this principle is exactly the same as it has long been used in all Armbian images). You can try all the files in a row, until you have selected an option with full support for all iron TV box.

    2. Added the ability to easily connect the settings file for the remote. It must be copied to the directory /storage/.config/rc_keymaps named remote-ir.conf. Additional manipulations are not required. Now already have one settings file for Khadas VIM\VIM2. If someone wants to add their own choices in the images - to send it to me indicating the model of the TV box.

    PROJECT=Amlogic ARCH=arm DEVICE=AMLG12 UBOOT_SYSTEM=box make image

    what UBOOT_SYSTEM should I use for the x96 MAX box (2g)?

    Yeah, that's mainline issue due to missing temperature monitor driver. 1.5Ghz @ 1.3volts is actually already a overclocking, more like 1.3 GHz would be maximum. Anyway, you don't need any of that extra speed if you watch videos which are HW decoded.

    I have to check that.

    Can you check if this is related to tinkerboard: disable 5s polling for CEC adapters by viulian · Pull Request #3506 · LibreELEC/LibreELEC.tv · GitHub ?

    Compiling with a similar patch fixes the problem.

    Code
    2019-06-02 21:00:00.710 T:3008897040   ERROR: Previous line repeats 1 times.
    2019-06-02 21:00:00.710 T:3008897040   ERROR: RetroPlayer[SAVE]: Failed to load savestate
    2019-06-02 21:00:01.270 T:3008897040   ERROR: RetroPlayer[RENDER]: Creating renderer for OpenGLES
    2019-06-02 21:00:01.289 T:2980615040 WARNING: CAESinkAlsa::InitializeHW - Using default alsa values - set failed
    2019-06-02 21:00:01.306 T:2980615040 WARNING: Previous line repeats 1 times.
    2019-06-02 21:00:01.306 T:2980615040   ERROR: CActiveAESink::OpenSink - no sink was returned
    2019-06-02 21:00:01.307 T:2989007744   ERROR: ActiveAE::InitSink - returned error
    2019-06-02 21:00:01.307 T:2989007744 WARNING: CActiveAE::StateMachine - signal: 10 from port: OutputControlPort not handled for state: 2

    I get this error when trying to play NES games, no sound, but works perfectly for movies and the GUI :(

    Tried the Orange PI PC image and it looks like it is working quite well.

    I spotted something that doesn't look right to me:

    * The Orange PI PC device tree operating points table has only three states, and the fastest is 1.0 Ghz. As far as I remember, the SoC was supposed to run up to 1.5Ghz @ 1.3volts

    * There is no cpufreq driver built in the kernel. Is it expected?

    * About CEC, there is a Kodi thread that apparently is using a lot of cpu time related to CEC. Doing a strace over it seems to continously scan the /sys directory in search for something and never stops. Maybe there's something missing to let it find the proper CEC device to listen to

    Yep is see the PeripBusCEC using a lot of CPU, and I have a CEC enabled TV.