balbes150

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).

you are trying to install the system with EDK2 - these images do not yet have an installation on NVMe, running only from external media (SD USB). To install on NVMe, you can use images from directories on the site without specifying EDK2. Direct recording of the entire image on NVMe is a bad practice imposed by ignoramuses who do not know how to properly assemble a system with a normal installation through the armbian-config\armbian-install script. All images from this theme (except versions with EDK2) have a normal installation procedure on NVMe. Use the appropriate images. Do not install the loader version from the EDK2 image in MTD\SPI, this loader only works with images collected in UEFI mode and does not work with extlinux.con mode, which is used in other images.

An SD card with a working system (with a working u-boot) must be installed in the device. Closing contacts only blocks the launch of u-boot from SPI (switches the launch to the SD card) and does not change anything \ does not erase in SPI. Cleaning SPI\MTD is performed from the system running from the SD card.

Try replacing DTB with this option. https://disk.yandex.ru/d/D5Xnjz_ciB_nvQ no

Test version 20230421-EDK2-EFI with support for system startup control on a monitor screen with a keyboard, as on a regular PC. Please note, this is a test version and bugs are possible. The process of starting the system before the image appears on the screen may take 10-30 seconds (depends on the speed of the SD card).

Test version 20230421-EDK2-EFI with support for system startup control on a monitor screen with a keyboard, as on a regular PC. Please note, this is a test version and bugs are possible. The process of starting the system before the image appears on the screen may take 10-30 seconds (depends on the speed of the SD card).