High Sierra UEFI Boot Issue

[IsaacOB1]

Hi,
I recently installed High Sierra onto my computer which is currently running Windows 10 on one drive and High Sierra on another so its dual booted with clover. The issue im having is that im only able to boot from UEFI enabled USB as the EFI partition from the Internal HDD isn't showing in BIOS and no matter how many times i use MultiBeast or Clover setup to install the bootloader onto the internal HDD it doesn't do anything.

Things Ive tried:

• Formatting EFI Partition to Fat32
• Different Kexts and config.plist configurations
• Changing multiple BIOS settings
• Reinstalling OSX
• Using Legacy

Even when i try and install kexts and drivers to the USB nothing changes. Not sure if its the BIOS or its settings but have been trying to get it working for a while now and im running out of things to try. If there's anyone who can help it would be greatly appreciated. Feel free to ask for any resources you need. ie screenshots or logs

Thanks

 

[IsaacOB1]

Accidentally made in wrong place can someone move this to the High Sierra section. Thanks

 

[vulgo]

The issue im having is that im only able to boot from UEFI enabled USB as the EFI partition from the Internal HDD isn't showing in BIOS and no matter how many times i use MultiBeast or Clover setup to install the bootloader onto the internal HDD it doesn't do anything.

Configure your UEFI to load Clover. See this post

 

[IsaacOB1]

Configure your UEFI to load Clover. See this post

By the looks of things that post is for booting from the same drive where Im using two separate ones. I also tried using the software suggested for windows but it appears that my windows installation isn't UEFI and is legacy will this be a issue with installing clover boot loader?

 

[IsaacOB1]

Here is a picture of my BIOS boot list and as you can see only the USB in UEFI shows up and also there seems to be two Mac OSX's listed which don't seem to do anything.

 

[vulgo]

Here is a picture of my BIOS boot list and as you can see only the USB in UEFI shows up and also there seems to be two Mac OSX's listed which don't seem to do anything.
View attachment 292987

Most firmwares will allow booting from internal drives using a file placed at /efi/boot/bootx64.efi hence that post refers specifically to booting from a single drive. Yours apparently does not. The Mac OS X entries are a vendor-specific device path (for real macs).

Use the EFI shell that comes with Clover.

map

lists potential filesystems. You need to find the EFI partition you installed Clover to.

fs0:

to change to FS0: if that is the EFI partition

cd efi
cd clover

then

bcfg boot add 0 cloverx64.efi "Clover"

If booting from USB make sure you don't add the path to the USB Clover.

 

[IsaacOB1]

Most firmwares will allow booting from internal drives using a file placed at /efi/boot/bootx64.efi hence that post refers specifically to booting from a single drive. Yours apparently does not. The Mac OS X entries are a vendor-specific device path (for real macs)

So its the motherboard BIOS at issue here. Is there anything that can be done to allow it to see internal EFI's. Can clover and Mac OSX run in legacy mode with my motherboard?

 

[vulgo]

So its the motherboard BIOS at issue here. Is there anything that can be done to allow it to see internal EFI's. Can clover and Mac OSX run in legacy mode with my motherboard?

Updated post 6 with shell commands.

 

[IsaacOB1]

Most firmwares will allow booting from internal drives using a file placed at /efi/boot/bootx64.efi hence that post refers specifically to booting from a single drive. Yours apparently does not. The Mac OS X entries are a vendor-specific device path (for real macs).

Use the EFI shell that comes with Clover.


lists potential filesystems. You need to find the EFI partition you installed Clover to.

to change to FS0: if that is the EFI partition

then

If booting from USB make sure you don't add the path to the USB Clover.

Ive done that and it adds Clover to the boot list but only works when USB is in. Is this because I've done it to the wrong path?

 

[vulgo]

Is this because I've done it to the wrong path?

Could be. Remove the entry you just added

bcfg boot rm 0

then look at the output of 'map' again