Unofficial LE for RK356x RK3328\RK3399 RK3588(s)

Quote from roel

It's already on 1.0.1 maybe that's the problem -> GitHub - CastagnaIT/repository.castagnait: CastagnaIT Kodi addons repository

Or just install 1.14.1 directly -> Releases · CastagnaIT/plugin.video.netflix · GitHub

Kodi 19, mainline LE have to use the v1.0.0 addon and the v1.0.1 addon is only for older Kodi 18 based images.

Android plays Netflix correctly so I don't know if it's perhaps a problem with software decoding on the mainline images or Netflix blocking LE user agent strings etc. I will try with some older Kodi 18 based LE images too and see if it works there.

I will see if i can try this evening on my station M1.

Quote from mo123

Anyone can test the Netflix addon on these images?

I tested it om my station M1, sorry for waiting. Netflix works for me.

Did a little bit of testing over Easter. As far as I can tell, the Linux part is working, but on the dtb side there seems to be some patching to do. My testings (Images from yesterday):

ROC-RK3399-PC: Booting. Libreelec Logo, Resizing ok. Reboot: Libreelec Logo...and nothing. (See attached File)

NanoPC-T4: everything's fine

Nanopi-M4V2: Bootloop, as I had in 9.2 until rk3399-nanopi-m4v2 was available.

Khadas Edge-V: Booting and starting. Ethernet took long to configure and leads to adress 169.xxx.xxx.xxx => no ethernet. Wifi fine.

RockPro64: After removing emmc everything's fine.

Rockpi 4: Everything's fine.

ROC-RK3399-PC_BOOT.txt

I tried to run the system on rk3399-roc-pc, but it stopped when it reached "Starting kernel ...".

Quote from dengkx

I tried to run the system on rk3399-roc-pc, but it stopped when it reached "Starting kernel ...".

I also had troubles getting this to work. My working SD: LibreELEC from 20210429. Also I burned a brand new SD-Card. In extlinux.conf replace rk3399-roc-pc with rk3399-roc-pc-mezzanine (if under windows you musn't use standard editor, please use notepad++ or something equivalent). I hope it will work for you...

Quote from slartibartfazz

I also had troubles getting this to work. My working SD: LibreELEC from 20210429. Also I burned a brand new SD-Card. In extlinux.conf replace rk3399-roc-pc with rk3399-roc-pc-mezzanine (if under windows you musn't use standard editor, please use notepad++ or something equivalent). I hope it will work for you...

I changed the device tree to rk3399-roc-pc-mezzanlne, and the result does not seem to change

I tried to run the system on rk3399-roc-pc, but it stopped when it reached "Starting kernel ...".In order to find the problem, I need to open the printing information after "Starting kernel...". How can I open the kernel to print the information?

Quote from balbes150

You are using images not from this theme. Most likely, these are the official versions of LE, they are discussed in another topic.

append: boot=UUID=3004-5504 disk=UUID=88ad0901-c5cc-4a0d-bd82-3935bf1814cd

I don't know why the official firmware can't run, but the image under this theme can run on rk3399-roc-pc. Can you tell me how the image here is compiled, or in which version of the source code it was compiled? I am new to LE, which puzzles me.

Quote from balbes150

These are not official test images for the RK33xx and rk3288 rk3188 platform.

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.

Display More

Hello, I downloaded the official LE source code. The compiled image cannot run on rk3399-roc-pc, and then it can be run using an unofficial image. I found that the problem appeared on uboot. Then replace the uboot of the official mirror with the uboot of the unofficial mirror and it can run normally. I would like to ask how this bootable uboot is compiled? Or is there a source code for the uboot?

Quote from digibooster

I have two dtb files for MX10 4GB / 32GB. LibreElec can be deployed with both. One Works without remote control, usb and wifi, but works power LED changes color. The second works with support for Wifi, usb and remote control, but the LED does not work and must be disconnected and reconnected to the power supply to turn it on again. Is it possible to somehow combine these two files to make everything work? I'm sorry if my English isn't okay. THX

rk3328-mx10-fast.dtb

rk3328-mx10.dtb

Hello,

I have an old mx10 4/32 and I would like to try those dtb. Unfortunately they reqiure a decription password. Any chance to post those without pass?