Armbian and LibreELEC and AltLinux for Quartz64

[balbes150]

The Armbian build system has added support for building images for Quartz64. Test images are available via links.


Quartz64 A

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

https://users.armbian.com/balbes150/quartz64/



SOQuartz + SOQuartz Model-A Baseboard.

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

https://users.armbian.com/balbes150/soquartz/


Quartz64 B

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




The Armbian build system allows anyone who does not even have special skills to work with complex compilation and assembly procedures. independently (for example, not mediocre on the Quartz64 device itself) to build your own kernel version (change the configuration and get your own version of the kernel) or completely your own version of the image with different DE or package composition. To do this, it is enough to follow very simple steps.

Code:

sudo su
git clone https://github.com/150balbes/build
cd build
./compile.sh

In a simple graphical interface, you can easily select the desired options and start the build process. More details about the build process can be found on the official Armbian documentation resources.

https://docs.armbian.com/


EDK2-EFI

https://users.armbian.com/balbes150/edk2/

[shaggy013]

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

[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

[shaggy013]

gonna test again
with graphics i could be wrong due i downloaded the wrong image .

[shaggy013]

GRAPHICS WORKS my bad with that

sd 64gb samsung

boot times
1st
2.16 -> login
3.23 -> till destop

2nd boot

1:30 -> desktop starts

i send you the bootlog

https://drive.google.com/file/d/18Qr1wrO...sp=sharing

Yeah you may call the bsp bad in that way it is almost plain open source availble from rockchip, even more with a 5.10 kernel , security or pretty wasnt the goal of the custom bsp . but nice to hear you take a glimps of it i never timed boot .
for more security and pretty downstream,images from balbes150 armbian and change the dtb or build from source and mara slackware images and source. but that is not the topic

Indeed andorid uboot is not a big issue or problem ,it can happen and just noticed it .

And for the rest BIG THUMBS UP that you take it to through the armbian aprove system .

ow mirros is updated

[balbes150]

GRAPHICS WORKS  my bad with that

sd 64gb samsung

boot times
1st
2.16 -> login
3.23 -> till destop

2nd boot

1:30 -> desktop starts

i send you the bootlog

Yeah you may call the bsp bad in that way it is almost plain open source availble from rockchip,  even more with a 5.10 kernel ,  security or pretty wasnt the goal of the custom bsp . but nice to hear you take a glimps of it i never timed boot .
for more security and pretty downstream,images from balbes150  armbian and change the dtb or build from source and  mara slackware images and source.  but that is not the topic

Indeed andorid uboot is not a big issue or problem ,it can happen and just noticed it .

And for the rest BIG THUMBS UP  that you take it to through the  armbian aprove system  .

ow mirros is updated

>i send you the bootlog

Sorry, but I probably missed something, but I don't see any startup log or did I misunderstand something in this message?

[shaggy013]

yeah i cant find the attach button

https://drive.google.com/file/d/18Qr1wrO...sp=sharing

here is the bootlog

[balbes150]

yeah i cant find the attach button

https://drive.google.com/file/d/18Qr1wrO...sp=sharing

here is the bootlog

Yes, I see such messages in the log (not only for Quartz64, but also on other RK models), I think this may be a problem of the initial stage of development, not all modes (models) of the SD card are supported yet. More often I see this on old (slow) SD cards.



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).
The operation of HDMI sound and analog sound has been tested.

Since I have no way to check NVMe (there is no Pine64 adapter to install NVMe in PCIe), please ask those who have such adapters to check whether NVMe is detected or not.

[balbes150]

I checked the launch of the latest version with the Bullsey XFCE EDGE kernel using a USB flash drive connected to USB 2.0. The startup time before the login screen saver appears is about 70-80 seconds. Not bad for an old USB stick and a slow USB 2.0 port.


for the sake of curiosity, I recorded the latest version of manjaro on a USB flash drive, connected it to Quartz64, the system started up and works fine completely from USB media. I.e., can very quickly switch from Armbian (which is installed on eMMC with a new u-boot that supports launching from USB media) to any system on USB media for work or testing.

[balbes150]

Good news. Now there is an option for Quartz64 in the official Armbian build system.


https://github.com/armbian/build/blob/ma...rtz64a.wip