The site has a new version 20200407. The core 5.6.2. And added new WiFi modules.
Posts by balbes150
-
-
I connected the serial console and found the system working except the output to the hdmi connected monitor. I appended the output of the serial console.
I don't have RocPro64, I can't check it myself.
1. Try disconnecting the HDMI cable after startup and reconnecting it.
2. Try other DTB (may need the DTB v2 version).
-
- wifi modules without mainline driver are not supported (mostly Realtek - RTL8189ETV, RTL8189FTV, RTL8822BS, etc.)
jernej Great work with H5. I used all your latest patches for 5.6. I Checked the resulting image on my Orangepi PC2 (H5) and surprisingly found no clips in my collection that I couldn't reproduce. By the way, I added support (patches for 5.6) for a number of WiFi RTL chips , if you have an interest, I can give a link to the ready-made patches for LE.
I connected OPI PC2 to 4K TV, set the maximum resolution to 4096x2160, video and Kodi interface work in 4K without problems.
-
New image 20200406.
An interesting behavior was detected when loading LE on rk3328\rk3399 from an SD card without using the correct u-boot (the SD card should not have any loader for the rk33xx platform). Please check the launch of the image for nanopi-k2 or odroid-c2 for those who have rk3328\rk3399 TV boxes with regular Android in eMMC. After writing the image to the SD card, you need to configure the dtb in the file (uEnv.txt) for the desired RK model. Do not change anything else and check the launch.
-
Found in the log file:
You need to place questions about official builds in the appropriate topics.
One question, what is the source of your build? Is it a nightly from the LibreElec Github or what it "underneath"?
I use my own modification (based on the official ones) for the build.
-
Yes. I tried rk3399-rockpro64.dtb and rk3399-rockpro64-v2.dtb.
Try using these DTB options.
-
Can i do replace u-boot on Windows?
This is possible, but you need the appropriate u-boot file.
And repositories do not work (failed to connect)
Is the network working ?
I use the normal DTB and not the V2
I didn't understand that phrase. Which DTB do you use ?
-
I get boot screen LE and then the boot does not go. I tried 4 latest builds:
You have configured DTB in the file (uEnv.txt) ?
-
-
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).
-
Important. Changed the directory location of the images. Now all images (for all supported platforms) are in one place.
-
Important. Changed the directory location of the images. Now all images (for all supported platforms) are in one place.
Just install Netflix plugin from the offical netflix repo
Netflix only works on 32 bits (arm), and is not supported on aarch64.
-
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.
-
And I'm using the same dtb "rockpro64".
Do you copy the old DTB manually into the system ?
