The new version of the LE images 20190820.
Please note, now on the site I upload only one TAR file to update for the entire group of devices.
Posts by balbes150
-
-
the wireless doesn't work with this........and the wired only works if you disable the wireless
also the reboot doesn't work.....I see the linux output on the screen, gets to 'Reached target Reboot.' but it doesn't reboot....
This DTB I am only interested in working eMMC (installing to eMMC).
-
When installed to emmc goes to bootloop after the first reboot.
Check this option to work with eMMC.
-
In Kodi of the Android, the system informations display 4 Gb
LE correctly shows the real memory size. In Android firmware manufacturers often specifically deceive users, overestimate the real memory size.
I did a git pull today on your amlogic-master branch. Compiling (ARCH=arm) leads to the same result as above.
Show the UART log from the launch of my latest build 20190724. Self-Assembly from GIT can be different.
What programs are for this model?
img.gz
-
The first issue is the amount of RAM: only 3Gb are available.
How did you determine the size of RAM ?
Kodi crashed when I try to play a x265 video
As far as I remember, x265 is not supported yet.
-
Display More
By changing the line in a /extlinux file.
Tried all of them
Situation is similar :
WiFi, cec -OK
Ethernet, elementum launch - nope
During reboot there's an error something like "cannot configure ethernet mac"
Need to edit (env.ini). You can ignore the Mac address error.
-
the errors are the same not depending on dtb used. Seems like changing the dtb makes no difference
How do you configure the DTB ?
-
It boots, but without ethernet and a bunch of errors.
You have set up the DTB ?
with 1 GB
Most likely reboot due to insufficient RAM.
-
tested on generic S905X device
You need to specify the exact model and dtb with which you are testing.
(Monitoring U-Boot via minicom: U-Boot bin loaded and halt)., but update from a working Card (from 26.05) will boot (branch amlogic-master).
Can you show UART log ?
(build aarch64 amlogic-master)
I temporarily stopped building aarch64. What exact version of the image was used ?
I have Mecool BB2 Pro S912 3G/16GB, which dtb do i have to choose?
try all gxm*
-
1. Download following file multi-boot fix.zip:-
2. Extract the 2 files from this zip file - "aml_autoscript" and "aml_autoscript.zip"
3. Format SD card (I used rufus) to FAT32.
4. Copy "aml_autoscript" and "aml_autoscript.zip" to this SD card.
Everything you need is part of the image of LE. You don't need to download or record anything else. The rest of the instructions are correct.
hmmm when you state older versions of LibreELEC (how old?) and ref ukmark62 earlier post what is your recommendedmethod to check current status and correct?
If you encounter any errors in starting the system from external media - the first step is to update the multi-boot.
Understood, except this is what has been fully available in past via balbes150 builds, reboot into Android from LibreELEC and reboot into LibreELEC from Android without any need to regularily play around removing and re-inserting SD. (Well at least for kvim devices)
Android launch mode from LE (without disabling external media Sd and USB) is possible. But I do not have enough time to test this mode.
-
For all.
If you have run coreelec or an older version of LE. To launch new versions should be upgraded as a universal multi-boot to a new version (script aml_autoscript latest images). Older multi-boot versions have errors that are not compatible with newer versions.
-
Witch branch are you using to build?
Yes, I'm using this branch.
-
Version 20190716.
Expanded list of USB WiFi and USB sound.
Maybe the dtb is the cause??
I checked the operation on two s905x, the system starts up and works.
-
Version 20190713.
all images use common kernel 5.2.
-
no connection through the NIC.
Check this DTB option.
-
Added new images from LIMA for s905 s905x odroid-c2 with 5.2 kernel to the site.
Tried all the dtbs and it's either the same results (boot loop) or the box does not respond at all (no boot logos etc).
Perhaps on your model not compatible with new kernels u-boot. Multiboot activated with the latest images ?
-
What .dtb is to be used for X96 100Mb/s NIC devices?
I do not see a .dtb with -rmii in its name in any of the more recent images.
Fix image to site
I am using "meson-gxl-s905x-p212.dtb". I modified "UEnv.ini" and "extlinux.conf" on SD card to match this dtb and the install proceeded as normal.
Try all DTBS from the gxl group.
-
Update images 20190712. Pay attention. For chips S922 changed the names of the DTB files. If you are using a regular tar upgrade procedure, you must correct the name of the dtb you are using in the (uEnv.ini) file after the upgrade.
There is a reference to RTL8211F in one patch but I don't know if apply to
I know this patch well and even know the author of this change.
