nonlinear-labs-dev / Audiophile2NonLinux

This repo is deprecated (it was eaten up by C15 repo)
0 stars 0 forks source link

VM does not boot NonLinux automatically #2

Open AntonSchmied opened 5 years ago

AntonSchmied commented 5 years ago

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:

  1. switch to fs0:
  2. navigate to EFI/arch_grub and execute grubx64.efi

in NonLinux

  1. insert a new Entry in EFIs NVRAM using _sudo efibootmgr --create --disk /dev/sda --part 1 --label "Arch NonLinux" --loader \EFI\archgrub\grubx64.efi
  2. change Boot order sudo efibootmgr -o 0003,0002,0001,0000 (1. Arch NonLinux, 2. EFI Internl Sell, 3. EFI Hard Drive, EFI DVD/CDROM)

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

majjam commented 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 ?

AntonSchmied commented 5 years ago

yes, thanks for pointing out!

hhoegelo commented 5 years ago

@AntonSchmied is this issue still valid or can we just close it?

AntonSchmied commented 5 years ago

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?