For users of rk3399, it is now possible to build a new image of LE not mediocre on your device RK3399 (if desired, you can use any TV box\SbS). It does not need a powerful PC or complex configuration of the virtual machine, and so on. If you are interested in trying this option, I can give you a brief instruction.
Posts by balbes150
-
-
Version 20200425.
Added support for analog audio (Jack 3.5) for the NanoPC T4.
-
I've tried both the C2 and K2 images (with the correct DTB) with my LaFrite, but neither will boot successfully. Any other advice?
What media did you try launching from ? What is in SPI and eMMC (does it have its own u-boot)?
The C2/K2 extlinux images will not boot on LaFrite; the C2/K2 are GXBB devices and LaFrite is GXL, so the device-specific u-boot 'fip' sources are not compatible.
You are confusing users, what you write applies only to the official versions. My versions use a single startup system and if configured correctly, you can run any image from RK AW AML.
We do not (and have no plan to) support emmc install on GXBB hardware.
This information is the same only for the official versions, in my images installation in eMMC works for all platforms.
is there some place where one can download your older builds, those where the HW acceleration wasn't broken?
No
Alternatively, is it possible to build from source an Image that works with your boot system? I've tried to look into it, but the guides are outdated and the required files aren't there anymore.
If you are a LE developer, email me at Slake in PM, I will explain in detail how to do this.
-
I should probably start a separate thread so that users don't get confused with the different setup in Oleg's images.
Yes, it would be a good solution. Now there are many differences in the composition of official images and my builds. This requires different handling rules, which may confuse users.
Will test with other files and formats later too, but mp4(as the testvideo) played always perfect in history and behaviour with that file on armbian is normal..
These are completely different systems, with different principles of working with media content, they do not need to be compared.
-
Version 20200421.
Added support for analog audio (Jack 3.5) for RockPI 4B.
-
Error: The location 16M is outside of the device /dev/mmcblk1mmcblk2.
Error: The location 533M is outside of the device /dev/mmcblk1mmcblk2.
Clean eMMC from old systems, they interfere with proper installation.
-
Then cyclically repeats step 3, 4.
This behavior usually occurs when the DTB is not correct.
-
New versions of ARM and AARCH64 (20200410).
Please note that all images and Addons are now built directly on ARM hardware (rk3399\s922x) without using cross-compilation.
If desired (in theory), everyone can assemble their own image on their own equipment.
-
I know this is still in development phase so there's one or two things need to be fix, but if there's a chance, can you put more wifi driver for my device (Fiberhome HG680P) it uses rtl8188fu (some varian uses rtl8188fs), thanx in advance!
rtl8188fu available in recent builds.
Which dtb should I use?
Correct. (which question - is the answer, I won't guess what your model is).
Should the AMLGX image work with the La Frite? Have been using the Amlogic nightly successfully but they're no longer being publish.
Have flash the USB drive successfully, and changed the uEnv file to reference the correct DTB file, but the La Frite just keeps cycling through its boot process and wont boot off the USB drive.
If you have a u-boot in SPI\eMMC, use the image for odroid-c2\nanopi-k2 with the correct DTB. All images (except g12) share a common core and differ only in a set of startup scripts.
-
-
1. Tried, but no difference, no messages in dmesg
2. Though I'm pretty sure I have the board revision 2.1 I tried the v2 version with no difference
Unfortunately, I don't have such equipment, I can't help you. The two previous users confirmed that LE works for them.
-
The site has a new version 20200407. The kernel 5.6.2. And added new WiFi modules.
-
The site has a new version 20200407. The core 5.6.2. And added new WiFi modules.
-
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.
