I've recently acquired an ARM64 development system, and have committed a number of bug fixes that I've discovered on this platform. These aren't yet in any official release, but you can download the source code from the git repository and build it yourself; or there's this unofficial interim binary version: https://www.rodsbooks.com/refind-bin-0.13.3.5.zip
I can't promise this will fix your problems, but it might. UEFI implementations tend to have quirky system-specific issues. If this pre-release version does not fix your problems, please enable logging at level 4, try again, and share the refind.log file that rEFInd generates.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
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 nothing helped.
Would love to get this incredibly useful rEFInd on Pi5 now that Pi5 supports UEFI - can you provide any help please?
I have also read your site many times over the years and can't recall any way to run debug version but am happy to build from source with extra debug and try that if that assists in any way?
I am also happy to send you a RPi5 if this assists?
Last edit: Hue Holleran 2024-07-13
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello, rEFInd (ARM64) will not load on tow-boot on Pinebook Pro.
I don't know if this might be a Tow-boot or a rEFInd issue though.
It displays (see attached picture) then immediately reboots.
Sorry for the poor quality of the pic, I had to get it with my phone, and id displays for so short that I didn't have a chance to get it any better...
Last edit: Swâmi Petaramesh 2022-11-23
Same issue on a Raspberry Pi 4 runnind edk2 UEFI firmware.
So, is rEFInd for aarch64 basically broken ?
I've recently acquired an ARM64 development system, and have committed a number of bug fixes that I've discovered on this platform. These aren't yet in any official release, but you can download the source code from the git repository and build it yourself; or there's this unofficial interim binary version:
https://www.rodsbooks.com/refind-bin-0.13.3.5.zip
I can't promise this will fix your problems, but it might. UEFI implementations tend to have quirky system-specific issues. If this pre-release version does not fix your problems, please enable logging at level 4, try again, and share the
refind.log
file that rEFInd generates.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 nothing helped.
Would love to get this incredibly useful rEFInd on Pi5 now that Pi5 supports UEFI - can you provide any help please?
I have also read your site many times over the years and can't recall any way to run debug version but am happy to build from source with extra debug and try that if that assists in any way?
I am also happy to send you a RPi5 if this assists?
Last edit: Hue Holleran 2024-07-13