balbes150

It is advisable to check this version whether NVMe will work or not (NVMe will be available for mounting and accessing files on it). Tnx. https://disk.yandex.ru/d/pYKoFQ3JgWbC5w

Question to the owners of Quartz64. https://forum.pine64.org/showthread.php?tid=16312&pid=117497#pid117497

Clone my GIT and build the kernel (you can additionally change the configuration as you wish) - get a DEB package for manual installation\updating of the kernel on any system. The assembly can be done on the rock 5b itself, the assembly time is small.

You are using an old version of the kernel. Use the latest version of the images, there is already the necessary module there. https://github.com/150balbes/build/blob/ed6c18895b1ed1429ea1a22210a826039d177d58/config/kernel/linux-station-m3-current.config#L2939

Ver 20230526-edge kernel 6.4.rc3 work SD USB (USB-LAN)

Ver 20230526-edge kernel 6.4-rc3

Ver 20230526-edge kernel 6.4-rc3 (HDMI not works).

You can build your own version of the Bullseye image directly on your OPi 5 with different kernel versions (legacy - 5.10 has all the hardware running in it, current - 6.2 has HDMI LAN USB sound and there is HW acceleration, edge - 6.3\6.4 has no HDMI, works LAN USB) and then install it on NVMe.

The image name states: LEGACY\CURRENT\EDGE are kernel versions. LUNAR\SID is the Ubuntu\Debian version.

The quote you gave is outdated and not relevant. Installation on NVMe is performed from armbian-config. Start the system from the SD card, create a partition on NVMe (you do not need to format it), run armbian-config and select the option to install on NVMe+MTD(SPI) in the menu, answer the wizard's questions. The system will automatically do all the work, you don't need to copy anything with your hands. Important. these versions DO NOT work with PD power supplies.

The main branch build system is destroyed and cannot build these versions correctly.

Now it's clear why nothing works for you. See this topic, there are working images.

The exact link to the image. When a new installation is performed, you need to use the latest version of the desired system, updating the old ones is a bad way, there may be problems with the correct matching of new components with old scripts. I use modules PL2303HX , they work well with Rockchip at 1500000 speed This is not required, the script formats itself. Everything works for me without problems with multiple partitions.

there are no such devices in any form on the official page (there is no point in testing them). the media kernel obtained from armbian-next is useless and dangerous for users, it should not be in network repositories (getting it on existing systems will lead to problems). the same goes for u-boot.

The exact version of the image. The UART log. What type of MBR is used (DOS or GPT). ?

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.