Posts by xleox

    Thank you for your interest in this matter, balbes150. It seems very promising, but I can only hope it works with your patches, since I had already installed another Armbian Buster-legacy solution and although HW acceleration worked smoothly neither the HDMI-CEC nor reboot worked properly with this 4.4 legacy kernels (to be able to reboot I had to unplug and plug again the power).


    I'll download and test it and let you know if it worked. Thank you again.

    hi xleox and anybody else interested in running libreelec in armbian, I think I finally make it working. Seems everything works. I will do more tests and try to make a step by step doc. I will post it here later.

    After thinking a while, I believe I was in wrong way bridging LE and armbian with docker. When running container in docker, even in priviledged mode, there are limitations in container. My goal is not to containerize LE, but just to use kodi well prepared in armbian. So, I decide to simply chroot to LE fs, so that kodi can run with full compability as in host. If we want to put some restriction to it by using 'unshare' and 'runuser' commands.

    Hey test0x01, these are excellent news indeed. Unfortunately I don't have enough programming skills to implement such solutions by myself, but I'm available to test, if necessary.

    No. But I encounter another problem that I can not resolve. The problem for me is that CEC stops working after switching HDMI source. Only a restart of container can make CEC working again. I tried this on many images with no success.

    In fact when I read your post I noticed that I had no idea if switching HDMI sources was causing the CEC issue here, so I did the tests and found that it works nicely no matter how many times I switch. Which means that at least here (TV Sony Bravia + RockPro64 + Armbian Focal 5.9.12-rockchip64, but had already tried one of ayufan's image before) the only HDMI event that causes the issue is turning the tv off.


    Also, not sure if it's related but I noticed these messages when I start the container (googled it but found no conclusive answer):


    Hi.


    I have been using this same approach too in a RockPro64, and I must say that everything works very stable (in my case I don't need to turn off the equipment, since I use it as a small server too), except for a small detail.


    Like you, I use HDMI-CEC, which works well at the beginning but stops working whenever I turn off the TV. I am aware of LibreELEC's CEC settings, and believe me I have tried to change them in several different ways, but to no avail. Whenever I turn off the TV using the remote control, the CEC stops working and I can only interact with LibreELEC using an alternative (I've been using Kore on my smartphone, but it's far from optimal). It only works again if I reset the container (systemctl stop libreelec, systemctl start libreelec).


    Did you happen to have this problem too? Do you have any suggestions on what to do?

    Mainline and Nightlies images of RK3399 doesn't support eMMC device block yet.


    If you want the eMMC support then try images by balbes150

    Hi there Aciel,


    Thank you for your reply. I've taken a look but apparently there's no image by balbez150 especially to the RockPro64 board.


    Anyway, I've seen a thread referring to a image developed to the NanoPC T4 board. Is this the one I'm supposed to use?

    Hi Joern-p,


    Thank you very much for your prompt reply. You see, the thing is that when I boot with both the SD card and the eMMC module inserted, although it boots normally from the SD card after boot it apparently doesn't recognize the eMMC module (so that I imagine I won't be able to use parted, dd nor any other tool on the eMMC from the running LibreELEC).


    In fact, this part of dmesg probably gives a hint on what's going on (I guess mmc1 would be the inserted secondary eMMC module):



    I googled it and apparently it's due to some lack of support in kernel to this given eMMC. That would explain why it works on other images (probably Ayufan's is optimized to that specific feature and the RockPro64 version of LibreELEC isn't).


    So the problem is I can flash LibreElec image on the eMMC but I can neither boot it as the system disk nor boot it as a secondary disk.


    I really don't know what to do now.

    Hello there,


    I've been using my RockPro64 for a couple of weeks booting from a SD card without issues. The thing is that I've just received my eMMC module and flashed the LibreElec image (based on instructions from the Pine64 wiki) but I got this error when trying to boot it for the first time:


    Code
    rockpro64 emmc grep: /proc/net/pnp: np such file or directory  ***
    Error in mount_flash: mount mount_common: Could not mount UUID ...

    ...

    followed by several other errors and ending up with a Kernel Panic.


    First I thought I had a defective eMMC card, but I tried one of ayufan images and it worked perfectly on the very first try. By the way I kept the sd card installation and it keeps booting from it without errors.


    These are the LibreELEC images I tried so far: LibreELEC-RK3399.arm-9.1.502-rockpro64 (the latest stable one) and RK3399.arm-9.80-nightly-20191031-cfe1640-rockpro64 (the latest nightly one).

    I tried to flash them using both BalenaEtcher (with default configurations) and the following dd line (both on Linux and macOS, and from two different computers):


    sudo gdd if=bionic-minimal-rockpro64-0.9.14-1159-arm64.img of=/dev/disk6 bs=4M conv=fsync status=progress


    (I've tried a couple of variations, as for example the macOS coreutils gdd and Linux dd, another values to parameter bs, etc. No success).


    Am I doing something wrong? Isn't the LibreELEC images compatible with eMMC modules? Could anyone please point me in the right direction?

    Hello there. This is my first post and I'd like a suggestion from you people if possible.


    I'm about to buy a SBC and that's the usage I have in mind:


    Basically I want it to be a media center, so I intend to install. The only services I intend to run apart from Kodi itself are Sonarr, Radarr, Bazarr and Transmission (maybe Jacket or another pkg if necessary, but it's mostly these ones). As for now my TV is 1080p but as I'll get a 4K TV asap I'd like my SBC to be 4k 60fps HDR ready and have HDMI-CEC support (so that I can use the TV remote). The origin of most of the videos I watch is my personal library (attached SATA disk and local 1GB network) and a Plex share from a friend (which I'd like to be able to direct play/stream instead of transcode).


    Having that in mind I narrowed things down to two models. Hardkernel Odroid N2 and Pine 64 RockPro64. I spent most of the last weekend comparing their tech specs, accessories, development maturity of the available images, reading their forums, etc, and I must say that they seem to be mostly the same to me. Considering my needs, which one of these two would you indicate to me?


    And more:


    Considering my usage will the 2GB RAM model do, or I must prefer the 4GB? I'm also getting an eMMC card. Will 8GB be enough?


    Thank you and I appreciate any help you may give me.