Den mandag den 4. september 2017 kl. 01.04.07 UTC skrev Guerlan: > but why it won't work? I was intersted in the reason behind this, and why it > wasn't fixed. Also, did you install rEFInd before?
UEFI and booting up through EFI should work just fine on most systems, however without secure boot enabled. If your motherboard allow it, disable your secure boot, or delete your secure boot keys. Some systems want you to do both to actually disable it fully, simply disabling it might not be enough without removing your keys also. Notice however, if you delete your secure boot keys, you will break any currently installed OS's relying on the secure boot keys. For example typical windows installations, but even other Linux systems using the keys will break. I have no idea about MacOS, but be sure to check before you delete your keys. Some motherboards allow you to backup your keys too, which might be an option if you just want to test it. But do your research and make backups before you take such risks. Once secure boot is disabled, you should be able to install with UEFI and load the EFI boot files. It's likely secure boot causing the problem, not UEFI/EFI. So in conclusion, legacy boot is definitely not the only option to install Qubes. I believe the reason is Qubes is still not supported in the secure boot keys, rather than a bug. There are UEFI bugs too, but it's supposed to be on few systems, unless you have Lenovo where UEFI bugs apparently happens frequently. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/31c2bf3d-3d15-4533-80a6-6fdec4e53d74%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
