Hi @mintsuki, hi @BarryK,
The Windows entries of my limine.cfg file result in a "Unsupported protocol specified" error.
The first one was auto-generated by EasyOS limine installer.
In the second one, changed from :// to () as seen in some examples on the web and also in what appears to be recommended by the documentation.
:Windows 11
COMMENT=Windows bootup
PROTOCOL=chainload
IMAGE_PATH=uuid://734d66df-feec-4d3e-aa02-fe8c44b43a58/EFI/Microsoft/Boot/bootmgfw.efi
:Windows 11 2
COMMENT=Windows bootup
PROTOCOL=chainload
IMAGE_PATH=uuid(734d66df-feec-4d3e-aa02-fe8c44b43a58):/EFI/Microsoft/Boot/bootmgfw.efi
Besides the protocol, that should be referring to uuid, I don't know what to place afterwards, given:
Code: Select all
# ls -l /dev/disk/by-uuid/ | grep p1
lrwxrwxrwx 1 root root 15 Jan 7 15:49 5E31-6311 -> ../../nvme0n1p1
#
# ls -l /dev/disk/by-partuuid/ | grep p1
lrwxrwxrwx 1 root root 15 Jan 7 15:49 734d66df-feec-4d3e-aa02-fe8c44b43a58 -> ../../nvme0n1p1
Should be the 5E31-6311 or the 734d66df-feec-4d3e-aa02-fe8c44b43a58?
guid, uuid or other?
As per the CONFIG.md file of the documentation, it seems it could use both.
@mintsuki, I tried to find reach for the Limine documentation.
It seems to be well documented and thorough, but one thing that I found missing is a user oriented help. It seemed to me that it's very developer centered. Maybe I'm wrong, but didn't find out those examples.
It would be wonderful, if you could be so kind as to provide a page of several working examples of all possible combinations for several operating systems.
For EasyOS, with partuid, uuid, file system label, device number, etc
For FatDog with the use of the initrd-nano and the parameter mergeinitrd1
For Windows, with those same partuid, uuuid, etc.
Examples of what is the "protocol limine", when it's useful. Same for multiboot, efi_chainload, and others.
