balbes150

I don't do Docker support, and I have no idea what it takes.

On the TX6, I removed the bottom cover of the case and use this model upside down (so that the radiator looks up and has a good run for air movement). I do not know what kind of idiot designs TV boxes in China, they put the board in the case with the radiator down, this is complete idiocy. Apparently, these "engineers" did not go to school and do not know the laws of physics at all - hot air always moves up (if there is no fan). Therefore, with passive cooling (without forced air supply from the fan), it is necessary to place the radiator so that the air passes to it as best as possible and the heated air freely goes up.

Try renaming the aml_autoscript file to factory_update_param.ubt But please note, I do not know how this can affect the device, it can lead to irreversible consequences and you will get a brick.

Yes, I moved all the builds to a single version with the official Armbian, one ext4 partition. To work with it, you either need to have Linux (you can run it without installing it on a PC via LiveCD), or install EXT4-enabled drivers in windows. https://disk.yandex.ru/d/8vNYuuxynz1L0w?w=1

Try using different dtbs from my Libreelec image for rk3328 on the latest version of ArmbianTV (kernel 5.10.19). There are more different dtbs in LE that may work better with your model variant. There's an mx10 version out there, try it out.

I tested without making any changes. There are a large number of different sets of equipment and components, which are all called MX10. Perhaps you have an option with bad components. I found that on my instance, everything works fine with increased memory and frequency parameters, but this does not mean that it will work for everyone.

ArmbianTV is an extended version of the official Armbian.

These images are not intended for such use. They are written to the SD card by the appropriate program for recording images. Also on your device, you may need to adapt the standard firmware to run external systems from the SD card.

The new version 20210303. Fixed installation in eMMC. I checked on TX6, the installation in eMMC works correctly (I selected the first line in the menu), the system starts normally from eMMC. But I don't guarantee that it will work correctly on other models.

Here is just the opposite situation. By removing unnecessary (unused) options, you get simplified support and reduced costs. Extra options cause more compatibility problems when a broken driver of one platform breaks the work of others and you spend time figuring out why the main device does not work. Fewer options = fewer build issues when changes to the source code are not compatible with the current patches. This is the law of programming, the fewer elements (code in processing), the fewer errors in the output and easier support (no cross-influences). I don't insist, it's just information.

Our kernel build system is now used by a lot of users not mediocre on the devices themselves. For them, when the native kernel is built on the device itself, the extra options in the configuration result in a few extra hours. Moreover, the optimization is very simple, copy the current configuration file with a new name, disable unnecessary platforms in the current rockchip64. If necessary, I can send a PR if there is a decision on which name to use for the general kernel configuration, or I can use something like "arm-64".

New version ArmbianTV of images for RK3288 and RK3188. rk3288 \ rk3188 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

To analyze the error, need a UART log.

New images are available for rk3188 (20210301). https://disk.yandex.ru/d/bmsU1aueVGLPjA?w=1 Anyone can build their own version, I added build support for rk3188 and rk3288 to my GIT.

I'll add your use case (sd + nvme) to install, but you have to check it yourself.

I asked you many times which option (string) of the installation you choose, and there was an exact indication of which option is checked and working (eMMC+NVMe). And now you write that you used the first line of SD + NVMe, which was clearly stated - this option is not working. The SD+NVMe variant has not been developed and tested.

question. Currently, the rockchip64-current kernel config has options for other platforms (AW AML iMX), this config is used exclusively for RK, why waste resources on unnecessary options ? There may have been plans to make a universal configuration, but then it makes sense to make a separate file that can be used for general configurations.

I did a system installation check on NVMe on Renegade Elite, the permutation of the mshlyapa takes too long and doesn't make sense to check (technically it is the same device as the P1, the difference is only in the DTB used). Downloaded the latest image of Buster is a legacy https://disk.yandex.ru/d/h_pMzFbuFXseOA?w=1 . unpacked it. I wrote it to the SD card. Configured DTB in extlinux.conf . Started the system, performed the initial configuration of the system on the SD card. Started the installation (the third item in the menu, installing u-boot on eMMC and installing rootfs on NVMe). Selected EXT4 file systems for both devices (mmcblk and nvme). I waited until the installation was complete and turned off the device. I pulled out the SD card and turned on the power. The system started automatically with NVMe. I specifically compared the UUID in the extlinux.conf and fstab settings, they are the same, while eMMC and NMVe have different UUIDs and they are correctly specified in fstab. Compared the UUID with the SD card, it has its own (different) UUID. Where do I look for the error ? Please note, this is important. If you do not remove the SD card, the system must start from it, this is the correct behavior of u-boot (the startup priority, regardless of where the u-boot is located, is strictly set by the USB SD eMMC).

In theory, the standard installation procedure via armbian-config should work, but I haven't checked how it works yet, errors are possible.

Firefly Station M1 is rk3328, I tried these images on MX10, all the main hardware is working. You can try installing a new kernel (rockchip64) from the network repositories, but look carefully at the settings, the startup data may change (DTB, mount parameters, etc.). Check the heating again, the TV boxes have a disgusting cooling system, it needs to be reworked, only after that the device starts working under load. Yes, there is, but everything has its time.

I don't have an extra hat with NVMe for the P1, so I can't test it right now. But when I tested the installation on NVMe, everything worked correctly, I'm not yet ready to say why it doesn't work for you.

by the way, you can test from USB media, all ArmbianTV images support launching from USB (the order of polling and launching USB SD eMMC systems). I.e. if you install in eMMC or connect one SD card with ArmbianTV to P1, you can test other systems from USB flash drives by simply connecting them to the USB port (if you connected a USB flash drive with the system, it will start first, if you disconnect the USB flash drive, the system will start from eMMC or SD card). this means that you can burn any ArmbianTV image to an SD card, and then burn any system to USB flash drives (including the official versions of Armbian, ArmbianTV, Libreelec). connect SD card and USB flash drive at power-on, autostart u-boot from SD card and then he autoruns the system with the USB stick, as not affecting the OS in the eMMC or SD card.

I tried a youtube video in 4K in full screen. Chromium works, the video goes smoothly, but sometimes there are microfreezes, it is not clear whether it is because of the Internet, or something else. Firefox can't handle 4K full-screen, although the window shows everything without problems. The temperature with Chromium does not exceed 60 degrees (full-screen 4K video).

I found a 4K TV (I took it away from the children for a while) . I check the latest image of Buster-legacy (with a patch https://github.com/armbian/build/pull/2650 ) with a media script on 4K. When the frequency of the display settings is 60 Hz, the screen constantly flashes\turns off, if I switch the settings to 30 Hz, everything works without problems (the resolution works 4096*2160 and 3840x2160). The temperature when playing full-screen 4K content (via GST Player), only 47-50 degrees. By the way, for some reason, the control via the remote control does not work in GSTplayer, the control works in MPV (you can adjust the sound, rewind, and the rest). In the desktop itself, can control the remote control (select applications, launch them). Naturally, in KODI, the remote control is very convenient and controls all the functions.

Tnx As it turned out, freezing the kernel will not help when installing the media script, it still has the same error - hard binding to a specific kernel. If you freeze the core, the media script forcibly replaces it with the wrong old core from the network reps @JMCC . And you have to manually install the new kernel after installing the media script (via dpkg -i). You can download the new kernel packages here. https://disk.yandex.ru/d/Di4DV9Jxug5NAA?w=1