Open AntonSchmied opened 5 years ago
regarding UPDATE You meant : editing startup.nsh while in the UEFI Shell seems to be a workaround FS0: edit startup.nsh and insert FS0: \EFI\ arch_grub \grubx64.efi
didn't you ?
yes, thanks for pointing out!
@AntonSchmied is this issue still valid or can we just close it?
So I also tried the "repackaging-approach" branch and the Issue remains. In my VM (Virtual Box 6.0) after creating a machine, in the Storage section I have 2 options:
Primary Master: ePC-disk001.vmdk and Secondary: the ApNonLinux.iso i have created with createNonLinuxImage.sh
If I simply start the machine via the VM GUI, it will switch to the ApNonLinux.iso and boot it. If I then delete the Secondary Option from the list, it will not boot the ApNonLinux VM automatically and i will have to proceed using the steps mentioned above.
Since this is a testing environment ... maybe it's not all that important ... However i would suggest adding the workaround to the README, or?
In Order for the VM to automatically boot into Arch NonLinux and not get stuck in the UEFI Shell, the following must be done:
in UEFI Shell:
in NonLinux
efibootmgr reference https://wiki.ubuntuusers.de/efibootmgr/
Assumption: This must happen during the NonLinux Installation NOTE
UPDATE editing startup.nsh while in the UEFI Shell seems to be a workaround FS0: edit startup.nsh and insert _FS0: \EFI\archgrub\grubx64.efi
Ctrl+S then Enter to save, Ctrl+q to quit