![]() rEFInd documentation has more about this. ![]() ![]() Maybe registering the refind.efi binary's hash rather than the signing key via MokManager is the way to go. I'm sure there's a way to make it work, but I was too exhausted to dig into registering keys via EFI command line. After re-enabling secure boot, it would present me with an annoying dialog saying "Invalid signature" (as you can see at the bottom of the post), although it'd proceed booting anyways (and it didn't even complain about my signed kernel either!) I ended up disabling secure boot again because I disliked that dialog more than the red boot screen. My shoulder and neck hurt, since the Surface Pro screen is lower than my computer monitor (I would have to look down, comparing to looking straight to my computer monitor when Im using my PC), and putting my arm in a different position when using the. That's largely correct given this configuration it's possible to enable Secure Boot and still boot into rEFInd/Ubuntu (getting rid of that annoying red boot screen.)Īlthough it definitely worked at some point, after tweaking settings over and over, in the end, however, I struggled getting the firmware to verify the rEFInd's signature using my custom key I registered via MokManager. Ive been using it on my table that I use for my computer. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |