Nightly images for A20, A64, H3, H5, H6 and R40 boards

  • 20200725 nightly image.

    It looks like "Invert stereoscopic 3D mode (flip eyes)" switch doesn't work.

    Nothing happens when I turn it on and off. As a result, my Samsung TV displays the image incorrectly.

  • As I understand, the switch itself can be verified with simple display.

    For example, in side by side mode it should switch left and right sides of the screen.

  • Hi, I use an twenty years old kenwood home theater, it do their best with DTS audio encoding, until now i used a 4geek playO that run very well.

    Now i want to try a new media player, and i bought a beelink GS1, connected with the toslink optic cable, it play audio in format stereo and ac3 with no issue, but with DTS audio it start to fliker.

    i made a short video of the problem


    I tried VLC and MX player.

    Now i tried LEbec, i activated passthrouth and connected the media player to the home theater with a HDMI/audio splitter, but same problem, the DTS led on the home theater start flicker on/off.

    There i something that i can do to solve the problem?


    thanks for the help


    Matteo Fabbri

  • freenix I just tested latest LE master image on my OrangePi Win on a freshly unpacked SD card and it still works fine for me.


    At this point it would be useful to get Kodi log and output of dmesg command. You can do that either over ssh or serial terminal. Ssh is easier, if you don't have it already enabled, just append ssh at the end of APPEND line in extlinux config on SD card. If that doesn't work, you'll have to connect serial dongle to the board and enable it in extlinux conf by modifying APPEND line - switch console parameters around and append systemd.debug-shell=1 at the end. In either case, please provide output of dmesg command and content of .kodi/temp/kodi.log

  • freenix I just tested latest LE master image on my OrangePi Win on a freshly unpacked SD card and it still works fine for me.


    At this point it would be useful to get Kodi log and output of dmesg command. You can do that either over ssh or serial terminal. Ssh is easier, if you don't have it already enabled, just append ssh at the end of APPEND line in extlinux config on SD card. If that doesn't work, you'll have to connect serial dongle to the board and enable it in extlinux conf by modifying APPEND line - switch console parameters around and append systemd.debug-shell=1 at the end. In either case, please provide output of dmesg command and content of .kodi/temp/kodi.log

    LibreELEC-A64.arm-9.80-devel-20200805221609-bd5130b-orangepi-win.img.gz


    U-Boot SPL 2020.04 (Aug 05 2020 - 19:54:16 +0200)

    DRAM: 2048 MiB

    Trying to boot from MMC1

    NOTICE: BL31: v2.2(release):9.0.0-3780-geabee4a8a97c-dirty

    NOTICE: BL31: Built : 21:12:59, Aug 4 2020

    NOTICE: BL31: Detected Allwinner A64/H64/R18 SoC (1689)

    NOTICE: BL31: Found U-Boot DTB at 0x40800e0, model: OrangePi Win/Win Plus

    NOTICE: BL31: PMIC: Detected AXP803 on RSB.



    U-Boot 2020.04 (Aug 05 2020 - 19:54:16 +0200) Allwinner Technology


    CPU: Allwinner A64 (SUN50I)

    Model: OrangePi Win/Win Plus

    DRAM: 2 GiB

    MMC: [email protected]: 0, [email protected]: 1

    Loading Environment from FAT... *** Warning - bad CRC, using default environment


    In: [email protected]

    Out: [email protected]

    Err: [email protected]

    Net: No ethernet found.

    starting USB...

    No working controllers found

    Hit any key to stop autoboot: 0

    switch to partitions #0, OK

    mmc0 is current device

    Scanning mmc 0:1...

    Found /extlinux/extlinux.conf

    Retrieving file: /extlinux/extlinux.conf

    183 bytes read in 5 ms (35.2 KiB/s)

    1: LibreELEC

    Retrieving file: /KERNEL

    21524488 bytes read in 1128 ms (18.2 MiB/s)

    append: boot=UUID=0508-1625 disk=UUID=084266b3-ef42-4473-85a7-fbf6d8269ca8 quiet console=ttyS0,115200 console=tty1 systemd.debug-shell=1

    Retrieving file: /sun50i-a64-orangepi-win.dtb

    30039 bytes read in 5 ms (5.7 MiB/s)

    ## Flattened Device Tree blob at 4fa00000

    Booting using the fdt blob at 0x4fa00000

    Loading Device Tree to 0000000049ff5000, end 0000000049fff556 ... OK


    Starting kernel ...


    [ 0.198532] sun50i-de2-bus 1000000.bus: Error couldn't map SRAM to device

    [ 0.199304] sun4i-usb-phy 1c19400.phy: Couldn't request ID GPIO

    [ 0.395076] sun8i-dw-hdmi 1ee0000.hdmi: Couldn't get regulator

    [ 0.395586] sun4i-drm display-engine: Couldn't bind all pipelines components

    [ 0.410605] sun4i-usb-phy 1c19400.phy: Couldn't request ID GPIO



    and it's all from the console.......................


    LibreELEC-A64.arm-9.80-nightly-20200808-63dfb3b-orangepi-win.img.gz

    replaced file


    system booted

    these are logs

    log-2020-08-09-12.25.56.zip

    Edited once, last by freenix ().

  • Is anyone having problems with the backup and restore feature? Backups are working fine but every time I time to restore on a new image it pops up the dialog the the progress bar and immediately closes without doing anything.

  • They may not give support but still let users to build like armbian Ihave orange pi lite and banana pi m2 zero and can´t get kodi to work because they doesn´t make a config file for os to build our own!

  • It's simple - < 1 GiB RAM boards are not supported because I don't want to deal with low memory situations, at least for now. Anything that it's supported in LE master branch can be treated as (semi)officially supported, so that's why there are no such boards. This is different than Armbian which has a notion of community supported boards. Still, it's extremely easy to add any H3 board on your own - just few lines in scripts/uboot_helper. However, if SoC is not yet officially supported (like H2+) then it's more work. I have zero reason to add support for H2+ because I don't have (or know) any H2+ board with at least 1 GiB of RAM.