-
Notifications
You must be signed in to change notification settings - Fork 16
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
Fix for Booting Linux via UEFI. #4
Labels
Comments
This was referenced Jan 26, 2017
(In case you aren't dualbooting) a much simpler and less intrusive fix is to just move the GRUB file you want to have booted to |
@palob yes, which is why it's listed as the preferred workaround on the FAQ :) |
Closed
is this still an issue? |
Repository owner
deleted a comment from
ibedani
Dec 20, 2019
Repository owner
deleted a comment from
ibedani
Dec 20, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As it stands currently, without NVRAM support, systems running these firmwares are unable to boot some standard Linux distros after running the installer. This is because these distros do not install EFI GRUB to /EFI/BOOT/BOOTX64.EFI, the only place this firmware looks by default for a bootloader. Some distros (including Ubuntu) do this to avoid issues with Windows potentially overwriting that location, but it means that manual fixes are required to get these distro booting. :/
There seem to be two possible approaches to fixing this other than implementing some form of NVRAM: 1. Add additional path finding to Duet so that it can find Linux (and other) bootloaders. 2. Provide a Boot Management Utility, such as rEFInd in the firmware so that all installed Bootloaders will be automatically detected and displayed in simple GUI for users. Thanks!
Edit:
Link to my fix-it script for reference:
https://www.dropbox.com/s/cay7ni1cj3ec88l/UEFIFirmwareLinuxFixScript.sh?dl=0
This is to be run from a Linux Live USB after a Linux distro with this issue is installed to the hard drive.
The text was updated successfully, but these errors were encountered: