Menu

#6 can not generate EFI boot

1.0
open
None
2018-01-11
2017-09-30
No

Repro procedure
With UEFI boot only real machine
1 assign entire disk to feliz
2 complete installation process

The resulted installtion can not boot. grub screen did not appear. It does not have /boot/efi. But has ESP.

I think

before bootloader setting,
you need to
make /boot/efi
and mount ESP at /boot/efi

line134 of feliz.sh should be
--efi_directory=/boot/efi, not /boot

Discussion

  • angeltoast

    angeltoast - 2017-09-30

    Thank you. I have been busy on other things, but I will start on this soon. Thanks for your suggestion - I will include it in the code.

     
  • angeltoast

    angeltoast - 2017-10-02

    I hope you will find that this is working correctly now. Thanks for your help.

     
  • Kohhei Mugitani

    Kohhei Mugitani - 2017-10-03

    I think intel ucode loading is necessary for Intel CPU.
    Obviously intel ucode loading is inappropriate for AMD CPU.

    cf https://wiki.archlinux.org/index.php/Microcode

     
  • Kohhei Mugitani

    Kohhei Mugitani - 2017-10-25

    With 10.11 release, still can not generate EFI boot installation.

    This time, I already assigned sda1=fat32/ESP, sda2=ext4/boot and sda3=ext4 root before feliz procedure.

    With EFI boot only Intel CPU machine,
    1 boot from feliz USB stick
    2 select own select installation and exisiting partitions.

    The result, grub menu did not appear.

    With resque USB stick, I found out.

    ESP has no contents.
    /etc/fstab has two desc for / and /boot. But it does not have ESP.
    According to my understandig, GRUB EFI needs mounted ESP.

    Also /boot does not have intel ucode file which means this installation does not have intel microcode.
    According to my understanding, Arch Linux has intel microcode file fot initramfs at /boot.

     
    • angeltoast

      angeltoast - 2017-10-25

      Thanks for your help and suggestions. There is clearly more work for me to do on this. Sorry it is still not fixed.

       
  • Kohhei Mugitani

    Kohhei Mugitani - 2017-10-26

    Mightbe that problem was caused by misidentification of exisiting partitions.
    My impression is, feliz is quite weak if user chose existing partitions because it likely misidentified the partitions.
    After EFI boot fail, I tried MBR installation with sda1=BIOS boot,sda2=fat/ESP,sda3=ext4/boot and sda4=ext4 root. But feliz also failed MBR boot installation. feliz identified sda3 as swap.
    Then I tried SwagArch. I already know SwagArch has quite long life bugs for EFI boot installation and intel microcode.(why he did not kill bugs!)
    However, SwagArch USB stick boot gave me X env and it identified existing partitions. Therefore I was able to handle the situation with refind.

    Have you conducted some testing with real machine? It seems like virtualbox has bugs for EFI boot env.

     
  • angeltoast

    angeltoast - 2018-01-11

    Sorry for the long delay before replying.
    I have completed a huge rewrite of Feliz, and hope that many of the previous problems have been fixed. The weakness of handling EFI is really because of my inexperience. I continue to learn, but EFI will probably be Feliz's weakest part.

     

Log in to post a comment.

MongoDB Logo MongoDB