Posts by balbes150

  • Status of NanoPC-T4 (RK3399)

    Quote from Mario.D

    So is there not a .img file lIBREeLEC for the M4 that is all complete and tested that is 9 yet? The one on Rockchip – LibreELEC PINE64 RockPro64

    LibreELEC-RK3399.arm-9.2.0-rockpro64.img.gz won't load. I don't know why.

    The legacy one PINE64 RockPro64 LibreELEC-RK3399.arm-8.90.015-rockpro64.img.gz works fine.

    This image is for another model. Its launch before (without additional settings), you can consider a lucky coincidence. You can try changing the settings and check the startup to M4.


    Quote from Mario.D

    But I don't find any that are the LibreElec? Anyone know the right one to load?

    There are several options for LE images that you may be able to run on try your M4. See this topic, earlier posts. There is information on how to configure and verify the launch of LE on the T4 (this principle is suitable for tuning and M4). There is no guarantee that this will work for you.

  • Unofficial LE for RK356x RK3328\RK3399 RK3588(s)

    Quote from zeus24

    Can you check your build parameters? Maybe it is not possible to just build one image for all RK3399 boards and then handle the difference via the DTB. (but I am no expert).

    The u-boot parameters in my build are correct (for the models I use). I am using a new u-boot with a set of new features that are not present in the old version of u-boot that you built. In theory, it is probably possible to build a new u-boot that will work on your model. But I don't have RockPro64 for such tests. RK startup principles cannot work with multiple u-boot variants at the same time. To work around this problem, you need to use the combined startup option (simultaneously using an SD card with the desired u-boot and necessarily without the system + the entire system on a USB drive). But for this option, you need to make changes to the u-boot sources that you used.

  • Unofficial LE for RK356x RK3328\RK3399 RK3588(s)

    Quote from zeus24

    Tried the latest image (20191210) on RK3399 RockPro with 5.4 kernel - Not booting (LEDs are not even active). I changed the DTB in extlinux.cfg and even tried to removed the "quiet" flag. Unfortuantly my RockPro is only connected to a TV, so if the RockPro hangs very early in the boot I cannot help.

    If you have any working system on the SD card that starts normally, you will be able to check the LE. You need to try to replace the u-boot in LE, on the version with a working SD card. You need to perform a few additional steps when preparing an SD card.

    1. Remove from working SD card u-boot. This can be done with this command on a Linux PC.

    dd if=/dev/<name_you_SD_works_card> of=u-boot-rockpro.img bs=1M count=16

    2. Write LE to SD card, configure DTB and replace u-boot with taken from working SD card. U-boot replacement is performed by two commands.

    dd if=u-boot-rockpro.img of=/dev/<new_SD_card_LE> conv=fsync bs=1 count=442

    dd if=u-boot-rockpro.img of=/dev/<new_SD_card_LE> conv=fsync bs=512 skip=1 seek=1

    After that, you can try running LE on RockPro. The last two commands write a working u-boot and save the existing partition table for the system written to the SD card. By the way, in the same way you can replace u-boot for Armbian system and check the start of any image.

  • @balbes150 LE images with Kodi-19 for S9xxx

    The new version of images 20191209. This version changes the DTB setting principle for the Odroid N2 model. Now the principle of setting is the same for all devices. You need to use two files (uEnv.ini) and (extlinux.conf). For models based on g12 (s905x2 s922), which have a problem not the correct color of the Kodi interface, you need to use the SD card to write the image and additionally download and copy the file to the SD card (u-boot.ext).

    https://yadi.sk/d/b2kpfvh33wlnlw

  • Status of NanoPC-T4 (RK3399)

    Quote from JerryPenguin

    5. Add Index of / as installation path in the file manager.

    6. install the ZIP repository.emby.kodi-1.0.6.zip via Add-Ons.

    I tested another installation option, I did not use the 5 and 6 step. I don't add third-party repositories. Immediately chose the search for addon EMBY and put the found versions with dependencies (they will be correct, because collected with a new version of KODI and Python3). Everything is installed without errors.

  • Unofficial LE for RK356x RK3328\RK3399 RK3588(s)

    If in Manjaro did not change the kernel (did not add patches), in the kernel everything should be enough (you can try to take DTB from their image). WiFi requires several elements. Try adding firmware (you may need your own options for Rock PI 4). I don't have this equipment, I can't help you with finding bugs. Do not pay attention to the options, they do not work yet (designed for AML).

  • Status of NanoPC-T4 (RK3399)

    Quote from Aciel

    And also when using the YouTube Adon,

    I checked, the youtube plugin works on kernel version 5 (20191125).


    Quote from JerryPenguin

    After that the normal LE configuration starts, but after selecting the language the configuration process stops.

    I can only reboot LE or turn off the SBC.

    The speed of the old flash drive will be low, so when you first start (when there is a parallel intensive process of various settings) you need to take your time. I never change the settings in the wizard, only when the system works at least 20-30 minutes, you can start changing the settings. Try slowly (without changing) to go through the wizard settings and change them in an already running system.

    With kernel 4 I have a Kodi interface running in 4K mode (4026). On 5 core the interface in 4K mode is not switched yet.

  • Unofficial LE for RK356x RK3328\RK3399 RK3588(s)

    These are not official test images for the RK33xx and rk356x rk3588(s).

    Pay attention. Starting from version (20200826), the configuration order for the used DTB changes.

    Please note that the algorithm for initial configuration of the system for startup has changed. Instead of a file "uEnv.txt", the file "/extlinux/extlinux.conf " is now used. The rules for editing a file remain the same.

    After writing the image, you must correctly configure the DTB used in the file uEnv.txt

    kernel 5.

    Images rk3328 and r3399 and 3288 are universal, when starting from USB media images are interchangeable (the only difference is used for the image u-boot and UART console output settings). Tar archives for updating are also universal.

    Note that the new generic images now use a single download directory.

    Important. Changed the directory location of the images. Now all images (for all supported platforms) are in one place.

    LIBREELEC — Yandex.Disk


    Old (not support_

    https://yadi.sk/d/xhf45z3bk-joga


    Add u-boot to SD card

    If you have any working system on the SD card that starts normally, you will be able to check the LE. You need to try to replace the u-boot in LE, on the version with a working SD card. You need to perform a few additional steps when preparing an SD card.

    1. Remove from working SD card u-boot. This can be done with this command on a Linux PC.

    dd if=/dev/<name_you_SD_works_card> of=u-boot-rockpro.img bs=1M count=16

    2. Write LE to SD card, configure DTB and replace u-boot with taken from working SD card. U-boot replacement is performed by two commands.

    dd if=u-boot-rockpro.img of=/dev/<new_SD_card_LE> conv=fsync bs=1 count=442

    dd if=u-boot-rockpro.img of=/dev/<new_SD_card_LE> conv=fsync bs=512 skip=1 seek=1

    After that, you can try running LE on RockPro. The last two commands write a working u-boot and save the existing partition table for the system written to the SD card. By the way, in the same way you can replace u-boot for Armbian system and check the start of any image.

    Support model :

    Firefly Station M1 (rk3328)

    Firefly Station P1 (rk3399)

    Firefly-rk3399 (rk3399)

    Firefly Station M2 (rk3566)

    Firefly Station P2 (rk3568)

    NanoPC T4 (rk3399)

    Quartz64 A (rk3566)

    Quartz64 B (rk3566)

    Banana Pi BPI-R2 Pro (rk3568)

    Firefly Station M3 (rk3588s)