balbes150

And there are a number of important differences between ArmbianTV and the official versions. For example, there are two sections. The first boot partition is necessarily made available for any PC (Windows Linux MAC etc), in particular it uses FAT. This is crucial. This allows any user, on any device, to easily configure system startup for their device. In case of problems with startup, it can connect the media to any PC and easily edit startup parameters, enable new options, change settings, add/delete files, etc. With official versions, this is not possible on a Windows PC, which greatly narrows the circle of users who want to start using Linux (Armbian). The official versions also use oters technologies. Installation in eMMC using direct bitwise copying of the source system (via DD). use of the UUID, etc. Please note that I do not impose anything on anyone or criticize the official version. I'm just stating the differences. Developers of the official version decide what to do and what to use.

Why create a bunch of similar images (systems) that differ only in minimal settings (DTB and command line, etc), and then spend a lot of resources to keep such similar systems up to date ?

At the moment, the official Armbian does not have support for TV boxes (this is not a claim, there is a lot of work to do and there is no urgent need for this yet), so there is no place to add support.

Images with two kernel versions are available for testing. Legacy. Uses the 5.4 core built using source code and patches (with minor fixes) that are used to build the rockchip. DEV. The core 5.7-rc7 is used (the sources are shared with the version I use to build aarhc64 images). There are no patches in this version yet. The legacy version has almost all the working hardware on UM3. On the DEV version, not everything works, but there is access to eMMC. how it is used (the setting for running is the same as the aarch64 version of images). To configure dtb, use the file (uEnv.txt). At this stage, I used settings and patches from MIQI to build the u-boot. I tried the u-boot version from Q8, it works the same way, but I haven't decided which version is better to use yet (I haven't fully figured out what the pros and cons of these u-boot versions are). The link to the images and the launch order will be placed in the first message.

I checked the images for Q8. Yes, they work, but they have a number of disadvantages that make it difficult to easily launch Armbian on TV boxes.

Built the first ArmbianTV test image for rk3288. I checked its work on Ugoos UM3. After removing the regular u-boot from eMMC, the system starts without problems and works from the SD card . At this stage, I have not yet found the u-boot source code to build a version of u-boot that can work in dual boot mode (without removing the regular u-boot). This version is included in Linuxium images. Which I used to first prepare the system to run ArmbiaTV (creating a full backup of the entire eMMC and removing the regular u-boot from eMMC). If you want to try a new image, I can upload it to the site and provide step-by-step instructions for launching UM3 (the process is quite simple and can be easily performed by any user).

ver 20200531

ver 20200529

The first results of studying the sent TV boxes. Ugoos UM3 (rk3288). First, the cons. This model does not have a LAN port. You have to use an external network card for LAN-USB. Positive. For this model, there is a ready-made Linux Ubuntu 15 image, with a simple installation procedure in eMMC. You can choose to install the dual boot option (Android+Ubuntu), or install only Linux (Ubuntu) in eMMC. I checked both options. Work. For those who need a minimal version of Ubuntu with the old core 3.10 and XFCE, after a small revision, the regular version of Ubuntu will be enough. This model has a properly designed WiFi (high-quality external antenna). The only modification I made was to remove the top plastic cover so that the cooling system would work normally. The presence of standard firmware with Linux makes it much easier to run other versions of Linux (Armbian and Libreelec). The Ugoos UM3 model has improved options with LAN and more ports it is UT3\UT3s. But I warn you right away, I don't have UT3\UT3s models, so I don't know how compatible they are with UM3 and whether it will be possible to have their General support. Result. My overall impression of UM3 is positive and I look forward to further development on adapting Armbian and Libreelec for this model. Another good news about the launch of ArmbianTV on UM3 (rk3288). Several different systems could be started from external media. There is a working u-boot that allows you to start the system from an SD card. At the first stage, managed to launch Armbian in a combined version (SD+USB). Works with HDMI and USB output (these are important basic systems that allow you to start working with Armbian on UM3), there is audio via HDMI. Works USB WiFi (one of the old models). Now I have the Foundation to create a full-fledged ArmbianTV image for UM3.

To upgrade from the old core, you need to restore the original firmware and go through all the steps for a clean installation. Or perform all the steps manually (do not wait for a detailed step-by-step guide for the manual option, you will have to solve everything yourself on the spot).

If I'm not confused, downloading from USB 3 already works for me. I'm need to look at these patches more closely.

Version 20200529. Added 4K support for rk3399 and rk3328.

Contact the manufacturer. Your problem is related to the lack of proper support in the main kernel, only related to the Khadas products (necessary fixes) that they should provide for their products.

I opened this theme to support running ArmbianTV on 32-bit ARM models. To date, there are first results on launching ArmbianTV on the Rockchip rk3288 and AML s8xx platform (in the future, by analogy with aarch64, I plan to switch to a common image for all 32-bit models of TV boxes). The link to the images https://yadi.sk/d/85ZvBuXyyenf_A MEGA (name -rk3288) 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/ Recommended startup procedure on UM3. 1. Install the Linux firmware version in eMMC (either a dual boot or a single Linux). 2. follow these instructions to download and run the Linux version from linuxium https://forum.freaktab.com/forum/tv-player-support/rk3288-devices/21091-use-windows-to-create-an-sd-card-so-you-can-run-linux-on-a-rk3288-device (do not forget to immediately expand the system partition to the entire media after writing the image). After launch, make a full backup eMMC with the DD command (or copy the ddbr utility to the system and use it). 3. Erase the first 4Mb on eMMC (using a simple DD command). 4. Download, unpack and burn the ArmbianTV image to your SD card. 5. Connect to the TV box and turn on the power. The system will start automatically. For those who are not afraid to lose their regular firmware and be able to easily restore it later, you can use the "accelerated" launch option (erase eMMC use the tools for Rockchip TV boxes).

I added a fix for the fan and build new versions of images 20.05.5 20200528. But I haven't tested the fan yet.

The build only works in BIonic.

If I don't forget, I'll try to add this option to the next versions.

Check the latest core (in the latest images 20200527). I don't see any problems when I start from an SD card on RockPI 4B. Important. Before recording the ArmbianTV image, you need to completely clear the SD card of all old "tails" (perform a reset of the entire card with the DD command).

Artificial tests have little to do with actual operation (so I'm not looking forward to getting an S905x3)

Your results are correlated with mine , this is a good indicator and it is important that the build was successful (this means it is reproducible for any user).

Hmmm, with eMMC should have been faster, I have an SD card (which is obviously slower than eMMC) on Ugoos X2 (s905x2) the build went a little faster (201 minutes of focal-server). May have been affected by the Internet speed. What was the Internet speed during the build ?

ver 20200527 kernel 5.7-rc7

Used the kernel and u-boot from NVIDIA. Perhaps the Armbian builds do not have enough settings\script to manage. You need to compare both systems and look for what is missing. I don't have time for this yet. You can check and find the solution yourself, it's not difficult (compare and copy from the source system where it works to Armbian). If you have ready-made solutions, I can quickly include them in the build of subsequent images.

If you want to try it, it's your right. I won't waste any more time answering you.

So I need a new install of a current image, and I can't use an environment that has been upgraded? Correct? I will try that when I have a chance. Thanks You can use the current system, but you need to manually add two directories\files to work with qemu (you can take them from the last finished image), see the log, it will indicate what is missing. The rest should work and install automatically.