Important information. Starting from the date 20200327, the order of updating the system via the TAR archive changes. Now all images are divided into two groups (directories on the site) G12 and RK+AW+AML. Each group has a single TAR file, which is intended for updating all images from this group. I no longer release separate TAR files for each hardware variant. The TAR file is universal for all models in its group. Expanded the list of images for initial launch (writing to external media). The amlgxbb image is optimized for models with the s905 chip (in the future, it will be added to the EMMC installation mode for the s905). Currently supported installation in eMMC via the GUI is Kodi interface for s905x\s912\s905x2\s922x rk3328\rk3399 H6.
Please note that before installing in eMMC, you must create a full backup of eMMC. this will help in case of problems during installation, or you can return to the current state of the system in eMMC before performing the installation. Important. For the installation to work correctly in eMMC, you must update the universal multiboot to the latest version using the image from which you start the installation, i.e. before starting the installation re-activate the multiboot.
I tried kwiboo's source and when I put it on sd card it no longer boots. However all your build are flawless
write the Kwiboo image to a USB flash drive. Connect together with the SD card (with my version of LE that you have running) and the USB stick LE from Kwiboo and turn on the power. My images support starting the system from USB, if the flash drive has the correct DTB for your model, the LE Kwiboo system should start
hey balbes150 Can you post your source? I'd like to test few changes wrt packages etc.
email or PM me what model you want to build an image for , and I'll send you a link and commands to execute ( my build system is different from the official one).
Okay, that still doesnt explain why crypto and pillow are missing from the /usr/lib/python3.7/site-packages folder in the aarch64 build
The Pillow package is not built with the aarch64 architecture, it gives an error, so it is temporarily disabled from the build.
Using the one stored in the new image
Can you run the latest version of Armbian (the principle is the same as running LE)? In Armbian, you can easily perform a number of checks that will help understand the reason why eMMC does not work (they share a common core).
The image is not bootable.
Read the first message of the topic.
2. Cryptodome library missing in the build so addons that rely on cryptodome refuse to start
3. inputstream.ffmpegdirect is missing in the build
Describe in detail the steps for checking what I can check for myself.
eMMC fitur : Install to eMMC not working
i try with tar file, not compatible file
TV box model, the exact name of the files used. And a full description of all the steps.
v20200211 on SDcard as is (only replace config to rk3399-rock-pi-4.dtb)
Did I understand correctly that you didn't add a u-boot to the SD card and the system started with the current u-boot ?
p.s. with fdt others versions strings "pci" and "nvme" in dmesg are missing
Use the latest versions, where NVMe is defined on RockPI4b.
Which dtb do I have to use for h96 max rk3399 box?
I don't have such equipment, I don't test it.
Install2emmc script no longer works.
The image contains incorrect scripts. This has been fixed in the new images.
Added versions of aarch64 images for testing.
Everytime when nanopi reboot, MAC adress is different, then IP is different (Manual settings does not work)
Add to the settings file (uEnv.txt) in the string parameter APPEND "mac=your_address".
With 9.2.0 image
This version uses the old core 4, in my images the new core 5. In the new kernel, functions have just started to be added, not everything will work.
Now, if I use fdt file from version 20200201, nvme is mounted after mounting STORAGE and run kodi. I can use mount -o bind to the some directories.
If you create a partition on NVMe (ext4) and assign a label to It, you can immediately in the config file (uEnv.txt) specify (instead of the STORAGE label) this label to automatically use NVMe as the primary device for data in LE.
I'm test LibreELEC-RK.arm-9.80-devel-20200127120222-6e9040d-rk3399.img on rock pi. Not boot. On screen message after kernel boot "Could not mount flash/SYSTEM".
I'm make extlinux.conf and boot with radxa uboot. On screen message: Not found boot=LABEL.... . Replace to boot=/dev/mmcblk0p9 ... not found ...ha ... it place on /dev/mmcblk1p9 , emmc on mmcblk2 , nvme not found. This kernel only for khadas?
According to the description, you are not running the system correctly. What media is used ? What settings do you make for DTB ? What "internal" media is connected (eMMC NVMe)? What is in SPI ?
If setting is correct , the LE can be run without problems on RockPI 4.
New ver 20200118 kernel 5.5 and 5.4
The new version 20200116.
Please note that the DTB configuration order has changed. now a single configuration method is used for all Rockchip Allwinner Amlogic platforms. The file (uEnv.txt) is used for configuration DTB. The system installation script in eMMC has changed accordingly. If you have a kernel 5 system installed in eMMC, it is advisable to perform a clean installation in eMMC to upgrade to the new version.