Posts by vitalogy

    Yes, if a bootable SD card is present, the system starts from this SD card. You can boot Android if you power off the device, eject the SD card and power on the device again.

    Yeah, I saw this in the rtw -driver in mainline, that sdio should supported soon.

    But for now i have wifi ...

    I will pubish a build here, so other can use it, till its in mainline.

    Here is a patch to support WIFI on the Tanix TX6 64GB version with the builitin Cdtech 47822BS (Realtek 8822BS) chip.

    jernej - please have a look at this, it is working for me

    So bluetooth could be on the horizon, because it should be supported by the driver.

    I can also confirm eMMC is working ... here are two screenshots:

    1. LibreELEC:~ # dd if=LibreELEC-H6.arm-9.80-devel-20190824143152-5c3df44-tanix-tx6.img of=/dev/mmcblk1 bs=4M
    2. 137+1 records in
    3. 137+1 records out
    4. 575668224 bytes (549.0MB) copied, 2.173960 seconds, 252.5MB/s

    But do not forget to "sync", else you will see this dmesg:

    1. [ 23.342332] SQUASHFS error: zstd decompression error: 14
    2. [ 23.342358] SQUASHFS error: zstd decompression failed, data probably corrupt

    great work

    Sorry for asking this, but how ... never flashed eMMC.

    Is this the right way?

    1. dd if=LibreELEC-H6.arm-9.80-devel-20190824143152-5c3df44-tanix-tx6.img of=/dev/mmcblk1 bs=4M

    these changes are not in any public git

    Yes, I realized this, when I had looked into /dev with my image, build from LibreELEC git repo.

    With your image the device shows only these two blocks. So mmcblk0 is the sdcard and mmcblk1 should be the eMMC.

    LibreELEC:~ # ls /dev/mmc*

    1. /dev/mmcblk0 /dev/mmcblk1p1 /dev/mmcblk1p15 /dev/mmcblk1p4
    2. /dev/mmcblk0p1 /dev/mmcblk1p10 /dev/mmcblk1p16 /dev/mmcblk1p5
    3. /dev/mmcblk0p2 /dev/mmcblk1p11 /dev/mmcblk1p17 /dev/mmcblk1p6
    4. /dev/mmcblk1 /dev/mmcblk1p12 /dev/mmcblk1p18 /dev/mmcblk1p7
    5. /dev/mmcblk1boot0 /dev/mmcblk1p13 /dev/mmcblk1p2 /dev/mmcblk1p8
    6. /dev/mmcblk1boot1 /dev/mmcblk1p14 /dev/mmcblk1p3 /dev/mmcblk1p9

    uhm ...

    I saw the changes in git and build an image yesterday ... I could have saved myself ;)

    Installed the image from jernej:

    CEC - is working, here with a Denon AVR

    eMMC - put the image on /dev/mmcblk1, remove sdcard and reboot?

    jernej thanks for your work

    I have found some time, to look into lcdd addon and its dependencies:

    A builded and installed linux is not neccessarry to build libugpio. Libugpio deals direct with the sysfs gpio interface and no kernel functions are used.
    I think we can safely remove linux form libugpio
    Has someone tested the hd44780 gpio driver from lcdd?

    Sofar if you build lcdd by hand in a clean environment (make clean, scripts/create_addon lcdd), lirc is not builded before and configure gives a warning

    1. checking for main in -llirc_client... no
    2. configure: WARNING: The lirc driver needs the lirc client library

    When lirc is set as dependency or it is simple installed by another package, lcdd fails to build.

    1. In file included from /home/michael/workspace/,
    2.                  from /home/michael/workspace/
    3. /home/michael/workspace/ error: array type has incomplete element type 'struct pollfd'
    4.  int curl_poll(struct pollfd ufds, unsigned int nfds, int timeout_ms);

    vpeter had give a workaround for this: thread-3793-post-28178.html#pid28178

    Is lirc needed as a dependency for lcdd?

    Got it by installing fakeroot:host by hand
    Lcdd builds fine without an installed lirc package. With a manual installed lirc package I got the same error.
    So I disabled lirc in and lcdd build fine again.

    1. --enable-drivers=all,!lirc

    Okay a workaround is "make image" first, but when I will build only one addon for a project I have to build the whole image first? Hmm ... :dodgy:
    I got this error from building lcdd too. For two days all was fine, but now it won't build ...?
    I decided to make a clean build, but stumble about the fakeroot error.

    When I run the following command on a clean build (make clean, rm -r build.LibreELEC-imx6.arm-8.0-devel), I get this error:

    1. $ PROJECT=imx6 ARCH=arm scripts/create_addon lcdd

    When I run the command again, I get the following:

    1. $ PROJECT=imx6 ARCH=arm scripts/create_addon lcdd

    So fakeroot is missing. Should virtual/initramfs depend on fakeroot, or which package depends on fakeroot?


    I have also these messages in the log.
    My Raspberry has the WittyPi extension board, so he will wakeup at the set wakeuptime and tvheadend can recording.
    For example some TV programme over the night, then my TV/AVR is off. So the log is spammed with these messages.
    Probably in the near future it will kill my sdcard. :huh: :@

    If someone is interested to test it for RPi2/3:
    RPi2 LibreELEC image
    RPi2 Addon KoDisplay

    The LibreELEC image includes additional the fbtft kernel drivers and the addon the neccessary libs (pygame, SDL, SDL_ttf, SDL_image).
    In the addon settings select fbcon and the framebuffer device for the display, typically it should be /dev/fb1.
    Reboot if nothing is shown on your display.

    You can define your own layouts for the modes. You find the file in /storage/.kodi/userdata/addon_data/script.kodisplay/layout.xml.