Error opening freeldr.ini

[pe200012]

My GRUB config:

#!/bin/sh
exec tail -n +3 $0
# This file provides an easy way to add custom menu entries.  Simply type the
# menu entries you want to add after this comment.  Be careful not to change
# the 'exec tail' line above.
menuentry 'Quibble' {
        insmod part_gpt
        insmod fat
        search --no-floppy --set=root --fs-uuid "A66B-FA4C"
        chainloader /efi/quibble/quibble.efi
}

freeldr.ini

[FREELOADER]
TimeOut=10
DefaultOS=Windows

[Operating Systems]
Windows="Windows"
Windows_Debug="Windows (Debug)"

[Windows]
SystemPath=btrfs(9593f4b8-0c4f-4a43-8056-61953a08e088)\Windows
Options=/SUBVOL=106

[Windows_Debug]
SystemPath=btrfs(9593f4b8-0c4f-4a43-8056-61953a08e088)\Windows
Options=/SUBVOL=106 /DEBUG

efi partition:

/boot/efi
└── EFI
    ├── GRUB
    │   └── grubx64.efi
    └── quibble
        ├── drivers
        │   └── btrfs.efi
        ├── font.ttf
        ├── freeldr.ini
        └── quibble.efi

btrfs subvol list

ID 256 gen 475277 top level 5 path @root
ID 257 gen 475277 top level 5 path @home
ID 258 gen 475256 top level 5 path @data
ID 259 gen 474121 top level 5 path @swap
ID 260 gen 456120 top level 256 path @root/var/lib/portables
ID 261 gen 456120 top level 256 path @root/var/lib/machines
ID 262 gen 475161 top level 5 path @windows

[GlitchR9506]

I tried to use Quibble in VMWARE and got the same error, It worked when I moved quibble to the root of the partition \ instead of \efi\boot

[SzczurekYT]

I get this same error, when trying to boot (chainload) Quibble from Grub, no matter where I put Quibble. My UEFI doesn't support adding an entry for efi files so I'm stuck with chainloading from grub. @maharmstone Is there any way to debug this? Maybe you could add some more prints around somewhere here https://github.com/maharmstone/quibble/blob/7b9962b6001a8f05dac8243fda3cf73324f57d6f/src/menu.cpp#L407, that would for example show the path / directory / partition used? And If you do please drop a build here for testing, because c/c++ dependency management is kinda non existent, resulting in building a c/c++ project being something that exceeds my abilities.

[maharmstone]

What happens if you use GRUB to run the EFI shell, then use the shell to run Quibble?

[SzczurekYT]

What happens if you use GRUB to run the EFI shell, then use the shell to run Quibble?

I had this idea too, but I don't have EFI Shell too : ( (Or at least I didn't seen a option boot it anywhere) Around 30 minutes later: I think I managed to compile an EFI Shell from TianoCore, let's try it. I spent next 30 minutes learning how to use the EFI Shell. Here is the result: I chainloaded the shell from grub and tried to run Quibble from it. This time the menu showed up, so we have progress already. I tried to boot windows but it failed. Here are few photos showing successes and errors: The drivers load correctly The menu works Second try (I didn't record the first one) - Windows Debug option, resulted in this error Third try - Windows option without debug (first try had this same error):

Hope this help in some way. I feel like the freeldr.ini error is Grub specific, and the errors I had here are a separate issue. My hardware, and other details (I have dual boot setup on nvme disk):

[maharmstone]

file_open returned EFI_ACCESS_DENIED

That's not good. This is an error that Quibble is feeding through from the firmware, rather than one it's generating itself. I suspect your firmware is too broken for Quibble to work.

Maybe try updating it to the latest version, if you've not done this already.

[SzczurekYT]

file_open returned EFI_ACCESS_DENIED

That's not good. This is an error that Quibble is feeding through from the firmware, rather than one it's generating itself. I suspect your firmware is too broken for Quibble to work.

Maybe try updating it to the latest version, if you've not done this already.

I updated it like 2-3 days ago. One thing that came to my mind is Secure Boot. I started searching and I found out that my firmware has a submenu called Windows OS Settings, and in it there is an option called "Bios UEFI/CSM Mode" which was set to CSM. So I set it to UEFI, and then Secure Boot option setting appeared, so I disabled it. So now instead of CSM we have UEFI mode with Secure Boot disabled. Maybe this will change something. I don't know what CSM is, but as far as I understand CSM is something meant for older systems. With Grub no difference, still EFI_NOT_FOUND, maybe it will change something with EFI shell option. I will let you know when I will have some time to test this today or tomorrow.

[SzczurekYT]

Nope, no difference exact same error. I agree, that my firmware / uefi could be better. Edit: Another fact to note is I'm booting from ntfs, because btrfs is only bootable from Quibble, and both projects are just too experimental as of now.