Thanks for the awesome rEFInd that I use on many PCs. On Raspberry Pi5 with RPi5 UEFI v0.3 it fails in same way as OP with "Synchronous Exception at 0x000000003E628F38" (v0.13.3.5) or "Synchronous Exception at 0x000000003E628F40" (v0.14.2). I have tried to enable log_level 4 but rEFInd never writes a log (it's installed alt name as /EFI/BOOT/BOOTAA64.EFI); incidentally Ventoy ARM64 does work. I tried renaming tools_arch and drivers_arch folders and prefix with hide_ to reduce files pulled in but...
Thanks for the awesome rEFInd that I use on many PCs. On Raspberry Pi5 with UEFI v0.3 it fails in same way as OP with "Synchronous Exception at 0x000000003E628F38" (v0.13.3.5) or "Synchronous Exception at 0x000000003E628F40" (v0.14.2). I have tried to enable log_level 4 but rEFInd never writes a log (it's installed alt name as /EFI/BOOT/BOOTAA64.EFI); incidentally Ventoy ARM64 does work. I tried renaming tools_arch and drivers_arch folders and prefix with hide_ to reduce files pulled in but nothing...
Thanks for the awesome rEFInd that I use on many PCs. On Raspberry Pi5 with UEFI v0.3 it fails in same way as OP with "Synchronous Exception at 0x000000003E628F38" (v0.13.3.5) or "Synchronous Exception at 0x000000003E628F40" (v0.14.2). I have tried to enable log_level 4 but rEFInd never writes a log (it's installed alt name as /EFI/BOOT/BOOTAA64.EFI); incidentally Ventoy ARM64 does work. I tried renaming tools_arch and drivers_arch folders and prefix with hide_ to reduce files pulled in but nothing...