balbes150

Release is not just freezing the code and generating images. Its a time when we pull together stronger, agree and deal with common goals and ideas. Things we are dealing with are complicated. Linux is complex, our framework is getting there too and only together we can deal with all this.
 
I started on freezing the kernel version. There is also some breakage, some related to our patches, some not. But since we have to freeze it sooner or later, perhaps now its the right time.
 
This brings a few good things at once:
temporally release people that are working close with maintaining kernel code @going@jock@balbes150@amazingfate myself ... this can bring more resources on trying to match with / merge armbian-next. @rpardiniworked for moths on this. Lets review the code and help sorting out bugs. Again. IMHO it is possible to merge, but if code remain unstable by the code freeze date (2022-05-14), we are merging after new images are generated. asking @Contributor/Maintainer board maintainers to engage in images building and testing (currently still from master branch) and bug reporting as earlier as possible (once PR 3736 gets merged) reproducible build framework in release branch. Which is most important long term consequence. Additionally, we would like to finish u-boot upgrade on Rockchip and release major forum refactoring @TonyMac32 @piter75 @balbes150
 
Happy Workers' Day!

I assume Balbes will mention if BT is functional in other kernels than legacy...
 

Hi all.
I made a new video where I explain all the basics of working with Armbian xfce4.
This for the absolute beginners that come from Windows. But a more advanced user can maybe also learn a few things from it.
Here is the video.
Greetings,
NicoD

Presumably this is a crosstalk problem, USB 3.0 uses a high frequency that interferes with WiFi (the chips are too close to each other). Details are available on the khadas official forum.

no, it won't help, these are completely different kernels with a different driver organization.

Because it often enough has happened that user did unknown modifications and blame us for their mistakes. Therefor only official images are supported.

Updating images 20220317 (edge 5.17 and current 5.16).
The operation of the standard procedure for installing the system on eMMC via armbian-config has been verified (i.e. you can install the system on eMMC directly on the Quartz64 itself, no additional adapter is needed to write the eMMC module via USB).
Added support for starting the system from USB media. This greatly simplifies and expands the possibilities of running different systems (for example, during testing). Now you can use not only SD cards, but also any USB media to start (and/or work). For example, I installed and configured the Armbian working system on eMMC (with support for launching from USB) and now I easily launch other Armbian test images from ordinary USB flash drives, which is much easier to handle (no card readers are needed to write SD cards, the cost of USB flash drives is much lower and the choice of which models to use \ buy is much wider).

I recently received a sample of Quartz64. I have added CSC level support for Quartz64a to the ArmbianTV build system, after checking and testing, I plan to send a PR with these changes to the official Armbian build system.
 
The first test images for Quartz64 can be found at the link.

https://disk.yandex.ru/d/xMVoaZXFFcWuog

This has been possible for a long time (available in all versions of Armbian that switched to using extlinux.conf), but requires manual editing of extlinux.conf (changing the parameter that is responsible for loading by default it is enough to change one line).
Please note, extlinux.conf is a standard settings file that is well documented in u-boot. In fact, it is very close to the logic of using grub.cfg

I checked this information, yes there is a problem on T4. A PR with the proposed correction will be sent in the near future.
 
As a temporary solution for already downloaded 5.16 kernel images, you can replace DTB with a new one.
 
 
rk3399-nanopc-t4.dtb

The test version of ArmbianTV 20220324 with a new version of u-boot-2022. Allows you to select different systems when starting on the TV screen from the keyboard. This will allow you to have several different systems on eMMC at once and choose which system to run. Please note, this is a test version and there may be errors in it. I recommend checking its operation by launching it from an SD card.

Updating images 20220317 (edge 5.17 and current 5.16).
The operation of the standard procedure for installing the system on eMMC via armbian-config has been verified (i.e. you can install the system on eMMC directly on the Quartz64 itself, no additional adapter is needed to write the eMMC module via USB).
Added support for starting the system from USB media. This greatly simplifies and expands the possibilities of running different systems (for example, during testing). Now you can use not only SD cards, but also any USB media to start (and/or work). For example, I installed and configured the Armbian working system on eMMC (with support for launching from USB) and now I easily launch other Armbian test images from ordinary USB flash drives, which is much easier to handle (no card readers are needed to write SD cards, the cost of USB flash drives is much lower and the choice of which models to use \ buy is much wider).

Updating images 20220317 (edge 5.17 and current 5.16).
The operation of the standard procedure for installing the system on eMMC via armbian-config has been verified (i.e. you can install the system on eMMC directly on the Quartz64 itself, no additional adapter is needed to write the eMMC module via USB).
Added support for starting the system from USB media. This greatly simplifies and expands the possibilities of running different systems (for example, during testing). Now you can use not only SD cards, but also any USB media to start (and/or work). For example, I installed and configured the Armbian working system on eMMC (with support for launching from USB) and now I easily launch other Armbian test images from ordinary USB flash drives, which is much easier to handle (no card readers are needed to write SD cards, the cost of USB flash drives is much lower and the choice of which models to use \ buy is much wider).

Not AFAIK, and also ISP camera support was planned but I am not sure of the current status. I think those are the two main points why someone would like to stay using legacy.
 
I wanted to do some standard packages for all distros in mainline, but I have been overloaded since some time ago, and I am not sure when will I be able to have a look at it. I will announce if it becomes ready.

Hi, have you tried this way to boot Armbian directly? 
https://wiki.stationpc.com/docs/stationpc/armbian

The described steps are intended for the device, as it leaves the factory, multi-boot is not activated in the factory firmware, you activated it yourself. You have already changed the state of your device (activating multi-boot changes the contents of eMMC and SPI, and changes the entire logic of starting systems from external media, not allowing you to start systems with a new format). In fact, the primary "activation\inclusion of multi-boot" is the transfer of the "old" (which does not know how to launch new systems from external media) version of u-boot to SPI. Until multiloading is fixed to work with new launch formats, multiloading needs to be disabled. I have already written to the Firefly developers what needs to be fixed in the multiload so that it works with all systems (with new and old formats). The correction is simple (just a few lines), but so far there is no answer from them.

The current version of Firefly multi-boot (which is installed in SPI) uses an outdated startup scheme that cannot work with new versions of Armbian. I am communicating with the Firefly developers to fix this issue.
 
Additional settings are needed to get a working image.
In the near future I plan to add CSC settings for quartz64.
 
This hardware is not supported and will not work.
 
Have you updated u-boot according to the instructions for Armbian?

https://en.t-firefly.com/product/industry/itx3588j
 

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

ver 20220205 kernel 5.10.96 for rk3188
 
Please note, now I am publishing new versions for rk3188 only on yandex disk (in order not to occupy Armbian resources with non-profile and unsupported versions that are released "as is" without any guarantees of work and support)

edge is not supported in the build system for TX6

You are violating the startup order, this is a test version and it does not contain startup scripts from the desktop. It needs to be run as an independent software. After booting the system, DO NOT log in to the desktop. Switch to any console (Ctrl+Alt+F1). We log in as a user (but it's better to use root, then there will be more control options) and launch kodi. The problems of a long startup may be related to new KODI packages or the latest version of the image with the 5.10.88 kernel (you can try earlier versions from yandex disk, there is a version with the 5.10.62 kernel). I have a system with the first versions of these packages, everything works quickly with them and the splash works.
 
I recommend using the correct package installation order.
 
 su -
 apt update
 apt install <full_patch>/kodi-mainline-bin_18.9-final-18.9bullseye0armbian1_arm64.deb
 apt install <full_patch>/kodi-mainline_18.9-final-18.9bullseye0armbian1_all.deb
(installing additional packages if they are needed)
 reboot

Download the Bullseye image with kernel 5.10 (for Station P1) and install the KODI package into it.
 
https://users.armbian.com/jmcc/packages/kodi-mainline/arm64/
 
 
By the way, the latest images for Station P1 use the media kernel with a full package of patches for HW, which go for LE. If @JMCC builds its mpv and KODI packages based on it, you can have HW acceleration on any Debian and Ubuntu system) with a 5.16 kernel.
 

You are behind the current state of rk3399 support. Now there is already support for HW GPU and VPU. I'm testing this on Firefly Station P1 (rk3399), everything works fine (kernel 5.1x), including 4k.
 
 
info glmark2 for Station P1
 
https://forum.altlinux.org/index.php?topic=36166.msg364846#msg364846