New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
refind will not start with f2fs_x64.efi 1.6 #23
Comments
Please run everything from the UEFI Shell and report what you see after running the command |
Sorry - I have a bit of a catch-22 here. My UEFI firmware does not include a shell. I have to load the shell externally from refind but refind won't even start with the f2fs 1.6 driver in its driver search path. |
@marlock9, thanks for the report. My guess is that you are hitting one of the new Can I therefore please ask you to run the same test with this |
Nevermind, I'm pretty sure I have identified the issue now. This is due to version 1.6 freeing the Device Path, which we should of not do, as this is a system allocated resource. So, of course, once you start freeing Device Paths for volumes that the system might still be trying to access, all kind of bad things happen... I've actually managed to replicate the error above on one of my systems, and confirmed that not trying to free the Device Path fixed it. I'll produce a 1.7 release of EfiFs with this fix when I get a chance... In the meantime, you may want to test with this |
I have now released EfiFs v1.7 that should fix the issue. If there is still a problem, let me know. |
Using refind 0.12.0-1 to boot debian bullseye. Refind does not even start when using the 1.6 version of f2fs efi driver. No problem with 1.5.
The text was updated successfully, but these errors were encountered: