balbes150

In other words, is this a problem in the source image itself (the generation script does not have execution rights in it) ? Is it possible for those who already use these images to write a simple command, what should do before starting the update (add execution rights to the script) ?

Do you already have a package with the fixed kernel ? If there is a package, I can check it (as a standalone deb package).

when updating, the uInitrd is not generated (it is completely absent). There may be an error in the kernel package. The SD card is fine, I used Desktop and updating a large number of packages did not cause problems. Which kernel package is currently used for the upgrade ?

The log clearly says that the kernel started, enable full log output mode (verbose=). And completely erase the eMMC with the dd command. Then all settings will be used only from the SD card.

Write down what order of steps you need to check, and I'll try to reproduce it myself. By the way, with intensive use of the system, SD cards get very hot and when they cool down (if the card reader is worn out), failures may occur (contacts are broken not predictably).

In the message log from u-boot-2015. I am testing C2 with the latest nightly builds (u-boot-2020.04) and have not found the specified failures yet. If your sample has been used extensively, is it possible that the card reader or SD card may have worn out ?

Add u-boot, as indicated in the instructions, selecting from the available on the site in the u-boot directory

IMHO @NicoD photo from the message above is quite suitable for this.

1. Enable full log mode, most likely there are messages about system startup and there may be answers why there is no startup. 2. Check which DTB is used and try other DTBS from the image. You may be using the default DTB mode that is set in u-boot. this DTB may not work with your model.

Sorry, I don't quite understand why you need photos of my TV boxes ?

Judging by the log, u-boot works fine and passes control to the kernel. The DTB setting may be incorrect. Try before writing the Armbian image to the SD card, perform a full SD card cleanup. Most likely, you have previously written a system with GPT to the SD card and its "remnants" (a backup copy at the end of the Sd card) prevent it from starting. https://www.stationpc.com/forum.php?mod=viewthread&tid=97&extra=page%3D1%26filter%3Dauthor%26orderby%3Ddateline

I tried the latest night image of Focal 5.9.8 from November 13, running from an SD card. In startup mode with SD \ emmc, I didn't find any problems with rebooting (I rebooted many times).

Try to post your data, they may also be considered.

Why waste time on trolls ? They are used only to "take". It's useless to explain anything to these trolls. For them, you need to use one answer - with all their requirements and claims, let them contact the manufacturer/seller from whom they bought this equipment.

I don't use docer, so I don't know what's wrong with it.

You may not have tried full NVMe media. After that, you won't want to use USB for a working system. Or you will use USB 3, only for fast transfer of a large data array if there is no network. Either to create backups or clone the system. PAE = slow and incomplete excessive complexity of use (due to restrictions on program usage).

Perhaps someone will be interested in this information. https://www.stationpc.com/thread-84-1-1.html

RPi can turn 32 bits into 64 bits to access 8 GB of RAM ?

Quote from the first message of the topic where you wrote your messages. For all. I don't support s905x3. ..... All messages about this platform deleted. ....

Your model does not attempt to access the launch from external media at all. Try writing the image with another program to the SD card (the SD card is a key element for starting the system). Either the manufacturer may not be using a standard SD card connection, or the firmware may have blocked this option. Try stopping the u-boot startup (press and hold the space bar while powering up). If the launch is not interrupted, you will have to try to completely erase the eMMC (details on how to do this with the RK tools are available on the forum in other topics).

@jockThe TV boxes section is closed for users to add information, so your topics have been moved. If necessary, specify a place on the forum where it is better to move your topics.

This is the only way to find out what is happening at startup and try to find the cause of the problem.

Replaced the SD cards and all images from the site worked. For some reason, only Sandisk works, other cards give do not predictable behavior. On my builds with u-boot-20.10, all cards work without problems.

Strange behavior. If you use the latest night image T4 from the site (from the download page from 17 10 2020), the SD card does not work. If I start building an image for T4 from the latest Master, and then take the u-boot files from the received package and manually write them to the SD card, everything starts working.

Sori, it seems the reason is in a different patch. I had to remove all patches (except changing the order of SD \ eMMC). And now you need to check all the patches to find which one breaks the download from the SD card.