Been pulling my hair out for a couple of days now but really like what Clover can do:
I have put together a usb stick with Clover and can boot into my MB mounted PCI-e NVMe drive just fine if I press 'F3 > Enter' once the Clover GUI has been displayed.
System: uname -a
Linux ZimaOS-Production 6.12.25 #3 SMP PREEMPT_DYNAMIC Mon Apr 20 05:09:01 UTC 2026 x86_64 GNU/Linux
The issue I have now - being able to bypass the Clover GUI completely and booting to that same volume without user input
config.plist.txt
preboot.log
Here are the volumes once booted and running via F3>Enter
zimaAdmin@ZimaOS-Production:~ ➜ $ lsblk -o NAME,LABEL,FSTYPE,PARTUUID,MOUNTPOINT | grep nvme
nvme0n1
├─nvme0n1p1 casaos-boot vfat b3dd0952-733c-4c88-8cba-cab9b8b4377f /mnt/boot
├─nvme0n1p2 squashfs 26700fc6-b0bc-4ccf-9837-ea1a4cba3e65
├─nvme0n1p3 squashfs 8d3d53e3-6d49-4c38-8349-aff6859e82fd /
├─nvme0n1p4 squashfs fc02a4f0-5350-406f-93a2-56cbed636b5f
├─nvme0n1p5 squashfs a3ec664e-32ce-4665-95ea-7ae90ce9aa20
├─nvme0n1p6 33236519-7f32-4dff-8002-3390b62c309d
├─nvme0n1p7 casaos-overlay ext4 f1326040-5236-40eb-b683-aaa100a9afcf /mnt/overlay
└─nvme0n1p8 casaos-data ext4 a52a4597-fa3a-4851-aefd-2fbe9f849079 /DATA
zimaAdmin@ZimaOS-Production:/mnt/boot/EFI/BOOT ➜ $ ls -la
total 730
drwxr-xr-x 2 root root 2048 May 26 12:08 .
drwxr-xr-x 3 root root 2048 Sep 5 2025 ..
-rwxr-xr-x 1 root root 733184 May 26 12:19 bootx64.efi
-rwxr-xr-x 1 root root 2307 May 26 12:19 grub.cfg
-rwxr-xr-x 1 root root 1024 Jun 2 09:51 grubenv
-rwxr-xr-x 1 root root 1024 May 26 12:19 grubenv-A
-rwxr-xr-x 1 root root 1024 May 26 12:19 grubenv-B
I can confirm the proper config.plist was loaded. Find attached the preboot.log which shows the config.plist being loaded. Also find attached my much truncated config.plist
67:224 0:000 - [06]: Volume: PciRoot(0x0)\Pci(0x1,0x0)\Pci(0x0,0x0)\NVMe(0x1,51-DC-11-00-02-0D-08-00)\HD(1,GPT,B3DD0952-733C-4C88-8CBA-CAB9B8B4377F,0x800,0x10000)
Could this be the main issue?
5:396 0:000 - [01]: 'CLOVER'
5:396 0:000 AddLoaderEntry for Volume Name=CLOVER
5:396 0:000 skipped because entry is hidden
5:396 0:000 - [06]: 'casaos-boot'
5:400 0:003 AddLoaderEntry for Volume Name=casaos-boot
5:400 0:000 skipped because entry is hidden
Been pulling my hair out for a couple of days now but really like what Clover can do:
I have put together a usb stick with Clover and can boot into my MB mounted PCI-e NVMe drive just fine if I press 'F3 > Enter' once the Clover GUI has been displayed.
System: uname -a
Linux ZimaOS-Production 6.12.25 #3 SMP PREEMPT_DYNAMIC Mon Apr 20 05:09:01 UTC 2026 x86_64 GNU/Linux
The issue I have now - being able to bypass the Clover GUI completely and booting to that same volume without user input
config.plist.txt
preboot.log
Here are the volumes once booted and running via F3>Enter
zimaAdmin@ZimaOS-Production:~ ➜ $ lsblk -o NAME,LABEL,FSTYPE,PARTUUID,MOUNTPOINT | grep nvme
nvme0n1
├─nvme0n1p1 casaos-boot vfat b3dd0952-733c-4c88-8cba-cab9b8b4377f /mnt/boot
├─nvme0n1p2 squashfs 26700fc6-b0bc-4ccf-9837-ea1a4cba3e65
├─nvme0n1p3 squashfs 8d3d53e3-6d49-4c38-8349-aff6859e82fd /
├─nvme0n1p4 squashfs fc02a4f0-5350-406f-93a2-56cbed636b5f
├─nvme0n1p5 squashfs a3ec664e-32ce-4665-95ea-7ae90ce9aa20
├─nvme0n1p6 33236519-7f32-4dff-8002-3390b62c309d
├─nvme0n1p7 casaos-overlay ext4 f1326040-5236-40eb-b683-aaa100a9afcf /mnt/overlay
└─nvme0n1p8 casaos-data ext4 a52a4597-fa3a-4851-aefd-2fbe9f849079 /DATA
zimaAdmin@ZimaOS-Production:/mnt/boot/EFI/BOOT ➜ $ ls -la
total 730
drwxr-xr-x 2 root root 2048 May 26 12:08 .
drwxr-xr-x 3 root root 2048 Sep 5 2025 ..
-rwxr-xr-x 1 root root 733184 May 26 12:19 bootx64.efi
-rwxr-xr-x 1 root root 2307 May 26 12:19 grub.cfg
-rwxr-xr-x 1 root root 1024 Jun 2 09:51 grubenv
-rwxr-xr-x 1 root root 1024 May 26 12:19 grubenv-A
-rwxr-xr-x 1 root root 1024 May 26 12:19 grubenv-B
I can confirm the proper config.plist was loaded. Find attached the preboot.log which shows the config.plist being loaded. Also find attached my much truncated config.plist
67:224 0:000 - [06]: Volume: PciRoot(0x0)\Pci(0x1,0x0)\Pci(0x0,0x0)\NVMe(0x1,51-DC-11-00-02-0D-08-00)\HD(1,GPT,B3DD0952-733C-4C88-8CBA-CAB9B8B4377F,0x800,0x10000)
Could this be the main issue?
5:396 0:000 - [01]: 'CLOVER'
5:396 0:000 AddLoaderEntry for Volume Name=CLOVER
5:396 0:000 skipped because entry is hidden
5:396 0:000 - [06]: 'casaos-boot'
5:400 0:003 AddLoaderEntry for Volume Name=casaos-boot
5:400 0:000 skipped because entry is hidden