The select the refind_local.cer file and answer 0 and yes to register the file with shim Navigate to the /EFI/BOOT folder on the USB stick that you booted the computer withįirst select the refind.cer file and answer 0 and yes to register the file with shim Make sure to go into the nf file and point the boot option to the vmlinuz-signed kernelīoot you UEFI system with the USB stick and you should see a boot screen that has the option Enroll key from disk select this Now copy the file refind_local.cer to the /EFI/BOOT folder on the USB stick and copy the file vmlinuz-signed to the /boot/syslinux folder on the USB stick Sbsign -key refind_local.key -cert refind_local.crt -output vmlinuz-signed vmlinuz Openssl x509 -in refind_local.crt -out refind_local.cer -outform DER Openssl req -new -x509 -newkey rsa:2048 -keyout refind_local.key -out refind_local.crt -nodes -days 3650 -subj "/CN=Porteus/" So the following two lines will create the key we are going to use to sign the kernel
Refind boot manager not finding ubuntudvd zip file#
Rename the file /EFI/BOOT/boot圆4.efi to /EFI/BOOT/grubx86.efiĬopy the file shim.efi and mokmanager.efi from the shim tgz file to the /EFI/BOOT folder on the USB stickĬopy the file refind.cer from the refind zip file to the /EFI/BOOT folder on the USB stick
Refind boot manager not finding ubuntudvd iso#
The create a parition that spans the whole USB stick.Ĭopy the contents of the porteus ISO to the USB stick gdisk util (so you can make a GPT partition on the USB drive)įirst you will need to use gdisk to create a GPT boot table to the USB stick. A USB stick (I am using one that is 2GB in size)Ĩ. A computer of VM that has can boot UEFIħ. sbsign (this is a tool that I found easiest to use on my Ubuntu desktop since you can get it from the package manager)Ħ. the shim boot loader ( I downloaded the file shim-signed-0.2.tgz)ĥ. rEFInd boot loader binary zip file from (make sure to download the binary zip file you only need a file from it)ģ. Porteus-3.1 (I used the LXQt iso just cause)Ģ. Sure, this is how I solved it (a more detailed version of this can be found at just don't run the efibootmgr step)ġ.
0 kommentar(er)
