balbes150

Ver 20230516-EDK2-EFI-current (6.2.15) and 20230519-EDK2-EFI-edge (6.4-rc2) for Quartz64-A , Quartz64-B , SOQuartz + SOQuartz Model-A Baseboard You can install several variants of the kernel \ systems and choose the right one at startup, as on a regular PC.

Quote from wiki Boot Order The RK3566 boot ROM will search for a valid ID BLOCK in the following order on the support boot media: SPI NOR flash SPI NAND flash SD-Card eMMC https://wiki.pine64.org/wiki/Quartz64_Development

Pre-uncomment the line in the board configuration EDK_UBOOT=

Nothing. Everything you need is in the image. Just write to the SD card and run. Important - if a bootloader is installed in SPI\MTD, it must maintain the correct startup order, or it has been removed. For reference, RK has three levels of startup order control 1. Hardware, you cannot change it (SPI\NOR\MTD, SD, eMMC). 2. The primary boot loader level (can be set when building u-boot). 3. The level of the "secondary" loader in the u-boot itself (can be set when building u-boot).

No, when using the correct bootloader, the boot partition is not needed at all for any media (Sd\NVMe). Everything works without a separate boot partition. This is one of the differences between ArmbianTV and the official versions. Those who write about installation problems confuse the behavior of different systems and describe the problems of the official versions. Moreover, when using the version with EDK2-EFI, you can have several different systems/cores on the same media and choose the right one as on a regular PC.

This is compiled from the official GIT, which has nothing to do with the images from this topic. Versions with the 6.3 kernel have been around for a long time (example https://disk.yandex.ru/d/ELX8vysQhS4vSw including with EDK2 https://disk.yandex.ru/d/_TtzJba3LhrXTQ ), but HDMI is not there.

You have not completed an important step - BEFORE starting the installation on NVMe, you need to create a partition on NVMe, the script uses an existing partition (this is the right approach, many partitions can be placed on NVMe for different purposes and different systems) and the user chooses from the existing partitions where to install the system. Direct recording of the image to the media (eMMC\NVMe) is a very bad practice (exception, temporary removable media, SD\USB, which can be easily connected to another PC for monitoring \ overwriting), this option is recommended by fools who cannot create the installation procedure correctly. One of the reasons why direct recording is bad is that there may be faulty cells on the media and direct recording does not control this in any way. The correct approach is to create a file system with special utilities\commands that guarantee the correct creation of a partition and a file system with the necessary parameters.

You did not specify which system is installed on eMMC (which image exactly, which u-boot), did not specify what is written in MTD\SPI. This all dramatically changes the behavior of the device when loading.

Freeze kernel updates, when you upgrade, you get a kernel that does not work on opi-800.

The all EFI versions are NOT intended for installation on eMMC\NVMe, this is written in the specified topic.

ver current (kernel 6.2) work HDMi

Show the full UART log, only there you can see real startup errors. How do you do the installation on NVMe ? To do this, you need to use only armbian-config, do not do any manual copying. This option will not work with kernel 6.2 (pancsfc). panfork only works with Jammy If you use a barrel (5.5x2.1) to USB-C adapter with a conventional power supply 12v-3\4A (without PD), this is enough.

1. Completely erase MTD\SPI from all old versions. If you tried to use the versions from radxa or the official armbian, it will not work correctly. 2. Run the latest legacy version (5.10.110) of this theme from the SD card and completely erase the NVMe. 3. Using a power supply without PD. 4. Only after completing all the previous steps, start the system from the SD card, create a partition on NVMe with EXT4 and run the installation on NVMe+MTD.

I hope there will be working versions for this model soon.

ver 20230428-EDK2-EFI kernel legacy and current

where is the system installed ? If on USB\SD, you can connect the media to the PC and open the log file and see the full output (/var/log) and find the reason that causes the kernel to panic. If the system is on SATA\NVMe - start the system from SD\USB media, mount SATA\NVMe and see the same logs.

What kind of core panic are you writing about ? I don't see any messages about legacy kernel panic.

add image XFCE and Gnome3 kernel 5.10.110

add image XFCE and Gnome3 kernel 5.10.110

ver 20230427-EDK2-EFI-current kernel 6.2 ( work HDMI USB LAN etc )

Why such difficulties ? Just use normal images in which the NVMe + MTD installation works correctly via armbian-install.

ver 20230426-EDK2-EFI-edge kernel 6.3 (HDMI not work)

ver 20230426-EDK2-EFI-edge kernel 6.3 (HDMI not work)

Try. Starting from an SD card does not affect the installed system (if you yourself do not manually run special procedures for installing\replacing the system on NVMe\MTD). If you are lucky and your current u-boot is able to work with normal systems, the system will work from an SD card.

All the sources from which these images are assembled (including the kernel) are freely available in my git. The images from this topic are not related to the current official build system (the new official build system is broken).