MrBoyi

Yep. Totally missed that. Didn't come to my mind it's new and needs to be partition first. It works now, as intended.

I build a bullseye version from the trunk. Before that I used the Ubuntu jammy version by using Joshua Reik's dtb on an armbian image. Two issues that I run into: The problematic Intel Ax201 wifi can't seem to be detected. Spend the whole day trying to make it work but fail. armbian-config feature 'Install to/update boot loader' can't be used to move image to NVMe and bootloader to MTD flash. NVMe drive is not given as a destination option even though it can detected by the system.

The debug console output of the failed loading of Armbian_23.08.0-trunk_Orangepi5-plus_jammy_legacy_5.10.160_gnome_desktop is as below: ... U-Boot 2017.09-armbian (May 31 2023 - 17:58:42 +0000) Model: RK3588 Orange Pi 5 Plus PreSerial: 2, raw, 0xfeb50000 DRAM: 15.7 GiB Sysmem: init Relocation Offset: eda65000 Relocation fdt: eb9f9a98 - eb9fecc8 CR: M/C/I Using default environment mmc@fe2c0000: 0, mmc@fe2e0000: 1 Bootdev(atags): mmc 0 MMC0: Legacy, 52Mhz PartType: EFI DM: v2 boot mode: None Model: RK3588 Orange Pi 5 Plus CLK: (sync kernel. arm: enter 1008000 KHz, init 1008000 KHz, kernel 0N/A) b0pll 24000 KHz b1pll 24000 KHz lpll 24000 KHz v0pll 24000 KHz aupll 24000 KHz cpll 1500000 KHz gpll 1188000 KHz npll 24000 KHz ppll 1100000 KHz aclk_center_root 702000 KHz pclk_center_root 100000 KHz hclk_center_root 396000 KHz aclk_center_low_root 500000 KHz aclk_top_root 750000 KHz pclk_top_root 100000 KHz aclk_low_top_root 396000 KHz Net: No ethernet found. Hit key to stop autoboot('CTRL+C'): 0 switch to partitions #0, OK mmc0 is current device mmc@fe2c0000: 0 (SD) mmc@fe2e0000: 1 switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot.scr reading /boot.scr 3476 bytes read in 2 ms (1.7 MiB/s) ## Executing script at 00500000 Boot script loaded from mmc 0 reading /armbianEnv.txt 172 bytes read in 1 ms (168 KiB/s) reading /uInitrd 15256294 bytes read in 1224 ms (11.9 MiB/s) reading /Image 34638336 bytes read in 2775 ms (11.9 MiB/s) reading /dtb/rockchip/rk3588-orangepi-5-plus.dtb 265256 bytes read in 31 ms (8.2 MiB/s) ** Unable to read file /dtb/rockchip/overlay/rockchip-rk3588-fixup.scr ** Unknown command 'kaslrseed' - try 'help' Fdt Ramdisk skip relocation ## Loading init Ramdisk from Legacy Image at 0a200000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 15256230 Bytes = 14.5 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 0x0a100000 Booting using the fdt blob at 0x0a100000 reserving fdt memory region: addr=a100000 size=a7000 'reserved-memory' cma: addr=10000000 size=10000000 'reserved-memory' ramoops@110000: addr=110000 size=f0000 Using Device Tree in place at 000000000a100000, end 000000000a1a9fff Adding bank: 0x00200000 - 0xf0000000 (size: 0xefe00000) Adding bank: 0x100000000 - 0x3fc000000 (size: 0x2fc000000) Adding bank: 0x3fc500000 - 0x3fff00000 (size: 0x03a00000) Total: 4644.846 ms Starting kernel ... [2J[3J[-1;-1fdone. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... Scanning for Btrfs filesystems done. Begin: Waiting for root file system ... Begin: Running /scripts/local-block ... done. done. Gave up waiting for root file system device. Common problems: - Boot args (cat /proc/cmdline) - Check rootdelay= (did the system wait long enough?) - Missing modules (cat /proc/modules; ls /dev) ALERT! PARTUUID=614e0000-0000 does not exist. Dropping to a shell!

@Efe Çetin I've downloaded the ' Armbian_23.08.0-trunk_Orangepi5-plus_jammy_legacy_5.10.160_gnome_desktop'. It can boot successfully but it stucks while loading the linux filesystem at initramfs: ALERT! PARTUUID=614e0000-0000 does not exist. Dropping to a shell! None of the /dev/mmcblk1p1 or /dev/mmcblk1p2 of my sdcard has that PARTUUID. The rootdev in armbianEnv.txt refers to the UUID of /dev/mmcblk1p2. I can boot Orange Pi's Debian successfully by using the same sdcard so I don't think that's the problem. Any idea? Regards.