balbes150

This should be handled by the userpatches customize-image script.
 
Please dont send a PR to add this feature 

Sorry, I won't be able to attend, there are urgent personal matters in the family at this time.:)

Check U-Boot output on serial. It should say something like 4 GiB of RAM detected, 3 GiB used. That won't change, since it's impossible to use that extra GiB due to HW limitations.

This is an outdated startup option (using boot.scr and armbianENV.txt), I use extlinux. conf. You need to use a different configuration mechanism. I don't use this functionality, so I won't tell you what to do.

Negative. Users don't need and should not change build script internals. When you do, also your script will not update anymore. 

Try to find reasoning for current situation, not adjusting documentation to the use case that will not be supported. At least not this way.
 

u-boot sources perhaps?

IMHO the right option is to buy technical support for your model from Armbian. You will get a ready-made, normally working system and a constant update of your devices, taking into account security and new packages. As a bonus, you will get a wide selection of different Debian\Ubuntu systems with a desktop or server versions.

Version 20210703 for P1 and M1.
Kernel 5.10.47 5.12.14. For the Legacy version, the work with the installation of the media package has been fixed. Due to the peculiarities of installing the media package, for proper operation during subsequent system updates, I recommend freezing the current kernel, it differs from those that arrive in network repositories (the list of supported modules and devices has been significantly expanded).

Version 20210703 for P1 and M1.
Kernel 5.10.47 5.12.14. For the Legacy version, the work with the installation of the media package has been fixed. Due to the peculiarities of installing the media package, for proper operation during subsequent system updates, I recommend freezing the current kernel, it differs from those that arrive in network repositories (the list of supported modules and devices has been significantly expanded).

IMHO the right option is to buy technical support for your model from Armbian. You will get a ready-made, normally working system and a constant update of your devices, taking into account security and new packages. As a bonus, you will get a wide selection of different Debian\Ubuntu systems with a desktop or server versions.

This is forum - you are welcome to talk about, but demanding support is a bad idea. You can report bugs here but only if you pay commercial price for fixing it & if we agree / are free to accept a deal or if you will be the one fixing it.
 
 
By who? Why? Several years ago (i would estimate about 5 years) we have concluded its not possible without breaking others or without severe framework customisation / rework ... This is when incompetent people are making hardware and when you expect software can fix all those mistakes in this chaotic world. And you also believe we have to waste our private money for that. Attitude. Open source is not slavery.

new version of Armbian  20210614 with core 5.10.43.
Added support for analog audio and a standard remote control.

new version of Armbian  20210614 with core 5.10.43.
Added support for analog audio and a standard remote control.

The start system in Coreelec is not compatible with LibreELECE  Armbian  etc. If you run coreelec on your TV box, you will no longer be able to run LE and Armbian normally until the full recovery of the standard firmware via the USB Burn Tool and the new activation of the universal multi-boot, which is used in all new systems.
 
Questions that do not specify exact details (the exact image version, TV box model, detailed steps that were performed for DTB settings, and so on) will be ignored and deleted.
 
For all. I don't support s905x3. I don't have this equipment. All messages about this platform deleted. What works or doesn't work from this equipment - I don't know. I do not give any answers or comments on the s905x3 chip.
 
The build and publication of unified test images with a common core for the Rockchip Amlogic Allwinner platform begins.
 
Y-disk
https://yadi.sk/d/_rQgn_FosYuW0g
 
MEGA
https://mega.nz/#F!j9QSDQSQ!6WpasOlbZYIInfw6yo4phQ
 
Now you can download the latest versions of images and DEB packages from the official Armbian resource via the link. 
https://users.armbian.com/balbes150/
 
 
*********************************************************************************************************************************
Pay attention. Starting from version 20.08 (20200814), the configuration order for the used DTB changes.
 
Please note that the algorithm for initial configuration of the system for startup has changed. Instead of a file "uEnv.txt", the file "/extlinux/extlinux.conf " is now used. The rules for editing a file remain the same.
All Amlogic models now need the "u-boot.ext" file.
Before launching on Amlogic, you must copy or rename one of the existing files "u-boot-*" to "u-boot.ext".
 
For s905 (not X) - used u-boot-s905
For s905x and s912 - used u-boot-s905x-s912
For s905x2 and s922 - used u-boot-s905x2-s922
 
For g12a\g12b models, a single file is now used (files u-boot.sd and u-boot.usb now replaces one u-boot-s922 file).
For the Allwinner platform, you no longer need to rename the scripts "boot.scr".
All "boot.scr" scripts have been canceled and are not used.
 
*************************************************************************************************************************************
 
How to run these images on the Amlogic platform .
Now all images Armbian and LE has all the files for activate the multi-boot. Anything addition to download and copy to media is not required.
 
1. Download the image for your device
2. Unpack
3. Burn the image on the medium
4. Configure in the file (uEnv.txt) launch parameters for the desired platform and model (uncomment the desired lines and comment out or delete unused ones)
 
If universal multi-upload has not yet been activated on this device, you need to activate it once. There are several options for activating multi-loading.
 
option A
- Connect the prepared media to the device and turn on the power, boot into Android
- Open the app "Update&Backup"
- Click on "Select" local update and chose the file on the removable media aml_autoscript.zip
- Start "Update"
- System will reboot twice and start running the system from external media.
 
option B
-  try using the "toothpick method"
 
 
How to run these images on the Rockchip and Allwinner platform .
1. Download the image for your device
2. Unpack
3. Burn the image on the medium
4. Configure in the file (uEnv.txt) launch parameters for the desired platform and model (uncomment the desired lines and comment out or delete unused ones)
5. If your device does not support USB startup , you can only use SD cards and you need to add the correct u-boot to the SD card (for details on how to add it, see the text of this message)
6. Connect the prepared media to the device and turn on the power
 
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 all platforms. 
Now a single configuration method is used for all platforms, using the file (uEnv.txt). You need to edit this file to configure it. You need to uncomment the two lines that are responsible for your platform and specify the correct DTB for your model. If you use this image to run on the one platform, you can delete it from the settings file (uEnv.txt) strings from other platforms.
 
Need to pick up the option for the file system will run. Pay attention, after you add\change the dtb file, you need to try to run the system and waiting to run 7-10 minutes. If not happened, repeat with a different dtb file.
 
Pay attention.
The installation algorithm in eMMC has changed. My recommend that you perform a clean installation in eMMC. Be sure to make a full backup of eMMC before installing it in eMMC.
The system installation scripts in eMMC have changed accordingly. If you have a system with eMMC core 5 installed on RK33xx, it is advisable to perform a clean installation in eMMC to upgrade to the new version. 
 
For the aw H6 platform, all scripts are already in the image (which have the ending aw). You need to rename the files with the replacement (remove the ".aw" ending).
 
Fix for correct color to G12 (Amlogic S905X2 S922X)
For models based on g12 (s905x2 s922), which have a problem not the correct color , 
If you are starting the system from an SD card, you need to copy file  u-boot.sd to u-boot.ext,
If you are starting the system from an USB, you need to copy file  u-boot.usb to u-boot.ext
When installing in eMMC, you do not need to do anything with your hands, the installation script itself will perform the necessary system configuration and when running from eMMC, the system will work with the correct color.
 
Please note, this version for the transition to the release of a single image for the platform Rockchip + Amlogic + Allwinner. The new image after writing to external media and after configuring the used dtb (and if necessary adding the desired u-boot option to run from the SD card on the Rockchip and Allwinner) can be used simultaneously on AML (s9xxx), RK (rk3399 and rk3328) and AW (H6). If the TV boxes RK (rk3328 and rk3399) and AW (H6) in eMMC installed a new version of u-boot  with support for starting the system with USB, adding u-boot to SD card is not required, the system will automatically start on with USB.
 
Important change. With this version (>= 20200218), you can easily add the desired u-boot on any PC (including Windows) .
 
To do this, new versions of u-boot are downloaded on the site.
 
https://yadi.sk/d/lTbXkrmZN5Hf6g
 
Rules for using the new u-boot option. Download, Armbian image, unpack. Write image Armbian to the SD card. Download and write the desired version of the u-boot file to SD card. Configure the DTB and the launch string (APPEND) in (uEnv.txt) for the desired model\platform.
 
Pay attention. Now you don't need to write u-boot with complex commands, you write the u-boot image with the same program as you usually write an Armbian image. This allows you to configure the system to run (including writing a u-boot image) on any PC (including Windows).
 
Pay attention. The new version changed the size of the partitions that are obtained when writing an image (all images have a fixed size of 5GB).  This u-boot entry option only applies to the new version 20200218 and subsequent versions. Don't try this for old images. This will not work on older images.
 
OLD add u-boot
 
 
 
For RK33xx
if you have windows and can't use the add u-boot commands to the SD card, use the SD+USB combination , write only the new u-boot to the SD card, and write the Armbian image to a USB storage device. And connect them together to the TV box.
 
To turn on the sound on models AML
where it is not present after the initial start. To enable audio , run the script (sound.sh).  You need to run the script
 
sudo sound.sh
 
 
 
Odroid N2
When starting from an SD card on Odroid N2, you must, after recording the image, write uboot to the SD card, configure uEnv.txt, additionally rename the script (boot.scr.aw) in (boot.scr). To be able to start any system from any media (USB SD eMMC), i'm recommend using the updated version of u-boot-SPI. Details about u-boot-SPI for Odroid N2 can be found here.
 
 
 
 

A test version of the image Armbian for TV boxes on the basis of RK3328. Tested on MVR9
http://freaktab.com/forum/tv-player-support/rockchip-based-tv-players/rk3328-devices/653167-bqeel-mvr9-rk3328-quad-core-64bit-cortex-a53-android-7-2-16gb-2-4ghz-wifi-bt4
 
All basic functions work. For running. Download. Unpack. To record on the SD card. Connect the SD card to TV box, connect a keyboard and mouse. To turn the power on the TV box. The system should start within 2-3 minutes. You must perform the initial configuration of Armbian.

https://yadi.sk/d/DSO6euzB3ahemo
 
https://mega.nz/#F!zoZywCTQ!9sNfXIAB3m_DyLl5I8P94w
 
The system of choosing the correct dtb has changed.
Please note, now it should be done on a different principle (files do not need to be copied).
To select the desired dtb, you need to change the line in the text file "/extlinux/extlinux.conf". In the line "FDT" you need to change the name of the file that the system will use at startup. The list of available files (names to specify in the configuration) can be found in the "dtb"directory. If you do not know exactly what file you need , you can enter all available names in turn and check the operation of the system. In accordance with this, the system installation script in eMMC has been changed. The steps to install the system on the eMMC remain the same.
 
Added a utility to full backup and restore the entire eMMC "ddbr". Checked mode the backup MVR9. Now if you try to check the recovery mode.
 
The order of installation in eMMC.
 
1. Download, unzip and burn the image to SD card.
2. Start Armbian on the TV box and perform the initial setup of the system.
3. If the system works correctly and you are satisfied, run the utility "ddbr" and create a full backup of eMMC (this is a prerequisite).
4. Rename the file "/boot/mvr9-uboot.img" in "/boot/uboot.img".
5. Run as user "root" script "/boot/create-mbr-linux.sh"
6. To run the script "/root/install.sh"
 
Pay attention to the correct operation of the installation procedure need to comply strictly with the order of the steps.

New version ArmbianTV of images for RK3288 and RK3188.
 
 
rk3288 \ rk3188
 
https://users.armbian.com/balbes150/
 
https://mega.nz/#F!j9QSDQSQ!6WpasOlbZYIInfw6yo4phQ
 
rk3188
https://disk.yandex.ru/d/7wqSh5Z5bv9q1g?w=1
 
rk3288
https://disk.yandex.ru/d/fRZwre9HDgAKHw?w=1
 
 
 
 
This link contains images with Libreelec for rk3288 and  rk3188, testing these images can help with the development of media functions for rk3288 and rk3188.
 
https://disk.yandex.ru/d/8vNYuuxynz1L0w?w=1

New Image 20210123 for H6, kernel 5.10.9
 
https://yadi.sk/d/0a41swJcEAZ0SQ?w=1
 
 
https://mega.nz/folder/j9QSDQSQ#6WpasOlbZYIInfw6yo4phQ/folder/K9BRjSaZ

If you have bisected my previous replies you would also notice one important information: "we are running with 1/1000 of needed resources". But since you only care about yourself and how to abuse this service to solve your expensive technical case without helping us, you didn't.
 
Also laziness is something I don't support and have no intention to hide that. If you are lazy and seek for my attention it is your gamble to be treated bad. Have you ever thought this might be taken as an insult?
 
 
This is not a commercial support service and you are not a client. We pay for this support and it is our gift to you. 99% of questions on this forum has nothing to do with our work so it has no moral relationship to give you support. And in best effort manner. This is my best effort. I don't have time for a betrer one.
 
Sadly support burden is extreme, while you totally don't care about that. Why should we care? I was very polite and professional in the past, just to see if that change anything. You were more satisfied, absolutely, but the negative impact on our side was even more extreme and I could get insane spending too much time "with my clients" that just takes and give nothing and are even spreading BS like you do.
 
Your duty is that people that helps (we) feel alright. Not the other way around.
 
you have to be careful not to waste our time, attention and stress us out by asking questions which were already asked on our expense, you have to be careful not to waste our time, attention and stress us out by asking questions that has nothing to do with our work on our expense, you have to be careful not to waste our time, attention and stress us out by asking questions without supplying any logs on our expense, you have to be careful not to waste our time, attention and stress us out by demanding support on our expense, you have to be careful not to demand from us to fix something for you on our expense, you have to be careful not to demand from us to develop something for you on our expense, you have to be careful not to open stupid replies like this since its your attitude that has to be changed, you don't insult and stress us with your unnecessary questions, you have to check if you can help us prior to asking for help on our expense, you can get at a subscription to show you are not yet another gift abuser on our expense.  
Check forum rules for more. We invest a lot of our time to provide you a ground for communication without insulting us, but you never read it since you don't care. Its all about your problem. Which I totally don't care about - if that is my personal expense daling with - if you pay, I will make an exception. I only care about our common problems. Once we rule them out, many people can't complain about them anymore ....
 

After you.
 
 
Providing polite answer is extremly time consuming (i lost 100 EUR for this polite answer too you and I am sure you will never pay me back) and it can create us much more damage then short answer like this one - with a valuable hint. I don't have intention to chat or make "friendship" with my "clients". 365 day in a year * +10 hours is something I could easily lost if going the suicidal route you recommend. I tried that, but the negative impact is too extreme.
 
Get some reality touch before giving advices.

You must take into account not only the processor specs, but also the kernel support. I would stay away from Amlogic for that reason, and bring in Rockchip into the equation.

Version 20210513. Fixed startup with Legacy kernel, now these images work correctly.

A test version of the image Armbian for TV boxes on the basis of RK3328. Tested on MVR9
http://freaktab.com/forum/tv-player-support/rockchip-based-tv-players/rk3328-devices/653167-bqeel-mvr9-rk3328-quad-core-64bit-cortex-a53-android-7-2-16gb-2-4ghz-wifi-bt4
 
All basic functions work. For running. Download. Unpack. To record on the SD card. Connect the SD card to TV box, connect a keyboard and mouse. To turn the power on the TV box. The system should start within 2-3 minutes. You must perform the initial configuration of Armbian.

https://yadi.sk/d/DSO6euzB3ahemo
 
https://mega.nz/#F!zoZywCTQ!9sNfXIAB3m_DyLl5I8P94w
 
The system of choosing the correct dtb has changed.
Please note, now it should be done on a different principle (files do not need to be copied).
To select the desired dtb, you need to change the line in the text file "/extlinux/extlinux.conf". In the line "FDT" you need to change the name of the file that the system will use at startup. The list of available files (names to specify in the configuration) can be found in the "dtb"directory. If you do not know exactly what file you need , you can enter all available names in turn and check the operation of the system. In accordance with this, the system installation script in eMMC has been changed. The steps to install the system on the eMMC remain the same.
 
Added a utility to full backup and restore the entire eMMC "ddbr". Checked mode the backup MVR9. Now if you try to check the recovery mode.
 
The order of installation in eMMC.
 
1. Download, unzip and burn the image to SD card.
2. Start Armbian on the TV box and perform the initial setup of the system.
3. If the system works correctly and you are satisfied, run the utility "ddbr" and create a full backup of eMMC (this is a prerequisite).
4. Rename the file "/boot/mvr9-uboot.img" in "/boot/uboot.img".
5. Run as user "root" script "/boot/create-mbr-linux.sh"
6. To run the script "/root/install.sh"
 
Pay attention to the correct operation of the installation procedure need to comply strictly with the order of the steps.

Due to the insane amount of detail you gave with your error description it will take quite a while to sort things out.

Sorry, I was away. I'll try to fix it ASAP

Congratulations!   Are you marrying S905X?    

Hi! reminding everyone of meeting
 
 

That is correct. Support: https://docs.armbian.com/#what-is-supported creates costs which are 99% covered by us, which means it will wait for a free slot. This can be stretched from days to years. You have to understand that this vendor never covered us a single minute for supporting troubles their customers have by using (one if not the best available) OS for their hardware. Nor "you" see and feel the necessity to cover support costs you make. Since none of you see value in getting help, there is no warranty we will fix this and you might need to wait months ... 
 
Workaround = use old builds.