Armbian and LibreELEC and AltLinux for Quartz64

[balbes150]

Extreme long boot time

login setup is annoying Level could be bit lower , can't even use thc013 as username

no graphical desktop debian and hirsute

uboot from android on emmc (like firefly uboot) doesnt like the sd  it panics

the errors are

ITS queue timeout (128 65)
ITS cmd its_build_invall_cmd failed

panfrost fde60000.gpu: get clock failed -517
panfrost fde60000.gpu: clk init failed -517

Bluetooth: hci0: command 0x0c03 tx timeout
Bluetooth: hci0: BCM: Reset failed (-110)

ow and your uboot is set at 1560  .


well that is for the images didnt build "build" yet
current wants to build 5.10 ? 
bad defconfig   not many have a dvdsky pcie card for testing pcie
0426-MALI-bifrost-resolve-error-when-make-clean.patch
0434-MALI-bifrost-fix-compilation-errors-when-CONFIG_DEBU.patch
0471-MALI-bifrost-fix-an-error-in-Kbuild.patch
thought those were the patches i reverted to get hdmi/graphics working on the 5.10 from 01-18 (wich has a fix for vop grf)  for a rk356x board
another brand has a newer 5.10 on their git but i didnt build that kernel yet

ow and for 4.19 you could just throw the 2 mali update patches from 5.10

ah i see
your on 5.14 , 5.17 is more stable i think
i would follow the original dts without the ebc setting more.
pgwipeout gives it a lot of attention .

and i saw that earlier you are patching the hdmi and change the setting from a to c , i cannot follow that or i dont see why .

./compile.sh EXPERT=yes CREATE_PATCHES=yes WIREGUARD=no EXTRA_WIFI=no

might take a look at warpme  minimyth2 repo he also has a multiboard kernel

>Extreme long boot time 

I compared the startup time of Armbian and your Debian-K5. The order of the test is to mark the time from the moment the power supply is connected to the outlet until the lightdm login prompt appears in Armbian or the desktop in your assembly. Armbian - 30-32 seconds, your build is 25-30 seconds. The difference of 5-7 seconds is of course "sooooo" long. 
Please note that it is not necessary to compare the INITIAL launch, when many additional operations are performed in the system, but the time when the system is launched in the future.


>login setup is annoying Level could be bit lower , can't even use thc013 as username

I am annoyed by a lot of things done "wrong" in your Debian image (questionable security settings, the absence of many packages \ programs I need, the "inconvenient" location of the panel, and much more). According to your logic, should I consider your system "bad"?



>no graphical desktop debian and hirsute

Not true, the desktop is perfectly displayed and works in all "desktop" images. Especially for you, I give links to screenshots of the desktop.

https://disk.yandex.ru/i/rKXuto4nXCKJqA
https://disk.yandex.ru/i/M59ofCSK9qvexQ

>uboot from android on emmc (like firefly uboot) doesn't like the sd it panics

Armbian uses a new version of the main u-boot 2022.04, which the old u-boot-2017 does not understand. I don't think it's a big problem. If you really need such a bundle, replace the u-boot on the SD card with the old version, since this is done elementary with one command. moreover, soon I plan to update the "old" u-boot-2017 and add support for USB startup and the need for an additional u-boot disappears


>well that is for the images didnt build "build" yet
>current wants to build 5.10 ?

The current version in my git is exclusively for tests, it will not be in the main build system, as well as there will be no public images with the 5.10 kernel (at least until the official version of this kernel from Rockchip for all rk35xx models is released).


>ow and for 4.19

I don't plan to add this kernel for Quartz64