Help me see what's wrong， thank you！ 9.8 compilation error
Which GIT\branch do you run the build from and with which command ?
Posts by balbes150
-
-
When downloading from an sd card via UART, I see the following:
The G12 image includes a u-boot for s922 (g12b), it will not work on s905x2 (g12a).
-
PROJECT=ARM DEVICE=ARM-ALL ARCH=aarch64 UBOOT_SYSTEM=rk3399-nanopi-m4 make image
PROJECT=ARM DEVICE=ARM-ALL ARCH=aarch64 PLATFORM=RK UBOOT_SYSTEM=rk3399-nanopi-m4 make image
Do you know how to build Kodi for ARM Linux, eg. for Manjaro Linux for RockPi 4, Edge-V RK3399?
The default Kodi for Manjaro is 64-bit but I want to build a 32-bit one so it can work with more addons and Widevine.
The Kodi wiki only explains it for Linux X86 and not for ARM devices and how to activate OpenGLES, Panfrost etc.
It must share some build steps with LibreELEC.
Even if you build KODI 32 bits, it won't work on Manjaro 64 bits.
-
Can you add dtb for Minix U22-XJ?
I don't have that kind of test equipment.
Source?
GitHub - LibreELEC/LibreELEC.tv: Just enough OS for KODI
ARCH=aarch64
-
Tronsmart Vega S95 Telos (Amlogic S905)
Show a photo of the device. For s905, you need to use the "gxbb" version (after recording the image, you do not need to change anything in the settings). You may need to switch to the fixed option in the settings for the sound to work correctly.
If the add-on compatibility is not needed, is there any actual advantage/hindrance in using arm or aarch64 images? I recall reading balbes150 mentioning temperature, but maybe I'm having a Mandela effect... Does one perform better than the other?
aarch64 runs faster than arm by about 20-30% faster.
-
The test version of the LE for AML s8xx (s805\s802\s812). Today there are two versions 20200430 and 20200503. You can find out more info in this topic.
Armbian for Amlogic S805 and S802/S812 - Page 21 - TV boxes - Armbian forum
-
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.
-
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.
