balbes150

Everything works without this patch. https://github.com/armbian/build/blob/master/patch/u-boot/u-boot-rockchip64-mainline/general-support-recovery-button.patch

Now I checked the launch of the latest night version on NanoPC T4 and found that the system does not start from the SD card (u-boot for some reason does not perceive the mmc 1 SD card). Perhaps the reason is the SD card, but I tried on the same SD card my system versions (LE and Armbian), where u-boot.2020.10 is used, the SD card works without problems (u-boot sees and starts the system from it). Has anyone experienced the same problem on T4 ?

Watch carefully the first post of this topic, how to configure and run the system on rk3328.

You didn't specify this "little thing", but it fundamentally changes the behavior of the entire startup system.

I don't understand what this is about.

What settings are set ? What media is used ?

Is there any statistics on the number of image downloads ? It is interesting to understand that there may be images that no one downloads. Perhaps then you can exclude them from the regular build and not waste resources on such images (models) by removing them from the build system.

When performing a build using this key (last commit, MASTER branch) I get an error. Is this a local error in my build environment, or are others observing similar behavior ? Pre-build without CLEAN_LEVEL="" passes without errors. The error occurs during a subsequent build with saving (using) already buils packages.

ver 20201014 for rk3288 kernel 5.9

Funny thing is, I haven't seen any outrage about HK using startup protection on "foreign" hardware in its u-boot, which causes the firmware in the device to be destroyed if it's not HK hardware. Where are you defenders of freedom ? I have long seen that most of all squeal about the violation of rights of those who themselves are engaged in theft and piracy, that would hide behind the freedom of their personal dirty deeds to get their personal benefits at someone else's expense. Yes, I warn all fans of freebies in advance that they would not try to hack and try to run my future versions, which will be designed for specific supported models, on their unsupported hardware and for all the consequences of disrupting the operation of their devices, they will be to blame themselves.

For some AML devices (for which there will be support), their own images will be released, specifically designed for this equipment, with protection from use by thieves and pirates. These images will be protected from use on devices that are not intended for this purpose. When trying to run on non-intended devices, users will have problems (immediately or over time, clearly visible or hidden, such as the gradual destruction of the system, etc.). Now there are many fans of freebies. They buy all sorts of shit and try to run ArmbianTV on it, but the manufacturers of this shit did not spend a single dollar, did not take any technical support in the development of the system. These manufacturers expect to steal (themselves or through users) the development of systems that were paid for by hardware manufacturers. I fully agree with manufacturers who want to protect their investments in software development from theft by pirates (users of equipment whose manufacturers / sellers did not take any part in this).

Thank you, I haven't laughed like this in a long time. So, when for many years I released images (that you absolutely used for free) at my own expense and in my personal time, which no one pays for, this is normal. But when I stopped this release and closed the possibility of illegal (pirated / stolen) use of my work, it became not normal. Very funny logic you have.

In this case, contact the Chinese sellers of these crafts for the release of ArmbianTV and support.

Look carefully at the first message of the topic - s905x3 is not supported. therefore, there are no working\safe options for it. Where does this conclusion come from ?

Models that are well supported in ArmbianTV NanoPC t4 Firefly Station P1 RockPI 4B Renegade Elite (roc-rk3399-pc)

This requires test hardware, I don't have any, so I don't have any plans to add support for these models.

yes

Ver 20201014 kernel 5.9 Pay attention. This is the latest version of ArmbianTV images, where there are files for AML. The following images will not contain this data.

Information for users of TV boxes on the Anlogic platform. At the beginning of the year, I already warned that support for AML will be reduced, now it's time, I completely stop supporting all TV boxes based on AML. Therefore, for those who definitely need ArmbianTV, I strongly recommend that you no longer buy models of TV boxes with Amlogic chips and switch to using supported hardware. AML support is Available exclusively for several models whose manufacturers cooperate with Armbian. In all new versions of images and the kernel, I will add various security mechanisms that will create serious problems, including hardware problems and hardware failure. Therefore, I strongly recommend that you do not try to launch new versions of ArmbianTV images using non-standard mechanisms used in old images , and not listen to the advice of outsiders who have nothing to do with the development of ArmbianTV. This is fraught with serious problems at unpredictable times.

The 5.9 kernel is in the testing state, and the DEB will only be available after verification. Use a system with the 5.8 kernel.

ver 20201007 for rk3288 kernel 5.9-rc8

ver 20201007 kernel 5.9-rc8

And the second option causes this problem. Crappy media or card reader on the device. This has been discussed many times.

I do not know, I have not tested this functionality.

I checked the ArmbianTV installation in eMMC on Firefly Station P1. Everything works. Now we can assume that this model has full support for ArmbianTV.