Contribute
Register

Can't use the option in Clover to open a UEFI Shell

Status
Not open for further replies.
I've read that the bcfg command in a EFI Shell might be another way to fix this issue. Does it matter?
 
hippyengineer said:
It has that entry.

sudo gpt show /dev/disk0
Password:
start size index contents
0 1 PMBR
1 1 Pri GPT header
2 32 Pri GPT table
34 6
40 409600 1 GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
409640 486717952 2 GPT part - 48465300-0000-11AA-AA11-00306543ECAC
487127592 1269536 3 GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC
488397128 7
488397135 32 Sec GPT table
488397167 1 Sec GPT header

Could the Windows entry be somehow stuck? Can I change that entry in the efibootmgr?
Click to expand...

I'll have to re-create an Ubuntu stick (mine got wiped out for 10.11 installer recently...)

Then I can check what it shows for the boot entry.

It wouldn't hurt if you re-create your entry for Clover.
 
I've tried to delete and recreate the Clover entry but I got this error,

ubuntu@ubuntu:~$ sudo efibootmgr -c -g -d /dev/sda1 -p 1 -b 0003 -L "Clover" -l '\EFI\BOOT\BOOTX64.efi'


******************************************************
Warning! This MBR disk does not have a unique signature.
If this is not the first disk found by EFI, you may not be able
to boot from it without a unique signature.
Run efibootmgr with the -w flag to write a unique signature
to the disk.
******************************************************

ubuntu@ubuntu:~$ sudo efibootmgr -c -g -d /dev/sda1 -p 1 -b 0003 -L "Clover" -l '\EFI\BOOT\BOOTX64.efi' -w
ubuntu@ubuntu:~$ sudo efibootmgr -v
BootCurrent: 0002
BootOrder: 0002,0000,0001
Boot0000* CT250BX100SSD1 BIOS(2,500,06)................-...........A..........................................
Boot0001* MAT****ADVD-RAM UJ8B0 BIOS(3,500,06)................-...........A..........................................
Boot0002* Acpi(PNP0A03,0)/Pci(1D|0)/Usb(0, 0)/Usb(1, 0)/HD(Part1,Sig00000000) ACPI(a0341d0,0)PCI(1d,0)USB(0,0)USB(1,0)HD(1,2,78bffe,00000000)

Your command listed in the http://www.tonymacx86.com/el-capita...de-booting-os-x-installer-laptops-clover.html does not seem to work.
 
hippyengineer said:
I've tried to delete and recreate the Clover entry but I got this error,

ubuntu@ubuntu:~$ sudo efibootmgr -c -g -d /dev/sda1 -p 1 -b 0003 -L "Clover" -l '\EFI\BOOT\BOOTX64.efi'


******************************************************
Warning! This MBR disk does not have a unique signature.
If this is not the first disk found by EFI, you may not be able
to boot from it without a unique signature.
Run efibootmgr with the -w flag to write a unique signature
to the disk.
******************************************************

ubuntu@ubuntu:~$ sudo efibootmgr -c -g -d /dev/sda1 -p 1 -b 0003 -L "Clover" -l '\EFI\BOOT\BOOTX64.efi' -w
ubuntu@ubuntu:~$ sudo efibootmgr -v
BootCurrent: 0002
BootOrder: 0002,0000,0001
Boot0000* CT250BX100SSD1 BIOS(2,500,06)................-...........A..........................................
Boot0001* MAT****ADVD-RAM UJ8B0 BIOS(3,500,06)................-...........A..........................................
Boot0002* Acpi(PNP0A03,0)/Pci(1D|0)/Usb(0, 0)/Usb(1, 0)/HD(Part1,Sig00000000) ACPI(a0341d0,0)PCI(1d,0)USB(0,0)USB(1,0)HD(1,2,78bffe,00000000)

Your command listed in the http://www.tonymacx86.com/el-capita...de-booting-os-x-installer-laptops-clover.html does not seem to work.
Click to expand...

Why is your HDD MBR?
 
Is that what this is showing, that the disk is MBR? I pulled the SSD disk out of the box and started by using the OSX disk utility to make it a GUID disk.

sudo gpt show /dev/disk0
Password:
start size index contents
0 1 PMBR
1 1 Pri GPT header
2 32 Pri GPT table
34 6
40 409600 1 GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
409640 486717952 2 GPT part - 48465300-0000-11AA-AA11-00306543ECAC
487127592 1269536 3 GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC
488397128 7
488397135 32 Sec GPT table
488397167 1 Sec GPT header

I suppose the disk could have been initialized as MBR when I got it and then I just tried to put the GUID on top of it.
 
Last edited:
hippyengineer said:
Is that what this is showing, that the disk is MBR? I pulled the SSD disk out of the box and started by using the OSX disk utility to make it a GUID disk.

sudo gpt show /dev/disk0
Password:
start size index contents
0 1 PMBR
1 1 Pri GPT header
2 32 Pri GPT table
34 6
40 409600 1 GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
409640 486717952 2 GPT part - 48465300-0000-11AA-AA11-00306543ECAC
487127592 1269536 3 GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC
488397128 7
488397135 32 Sec GPT table
488397167 1 Sec GPT header

I suppose the disk could have been initialized as MBR when I got it and then I just tried to put the GUID on top of it.
Click to expand...

Disk is GPT, not MBR.
 
I have been doing a lot of research about how to get this drive booting but I've not been able to come up with anything.

Did you have any luck Rehabman?
 
hippyengineer said:
I have been doing a lot of research about how to get this drive booting but I've not been able to come up with anything.

Did you have any luck Rehabman?
Click to expand...

Any luck with what?
 
Would you have any more suggestions to help me troubleshoot this booting issue? You mentioned that you would reload your Ubuntu stick to compare your GUID to mine, although you did quote the ID in post 19. You must be extremely busy, so any more help troubleshooting would be greatly appreciated.

I saw that Unibeast 6.1 was released and you mentioned that "OsxAptioFixDrv-64.efi should be used instead of OsxAptioFix2Drv-64.efi" so I thought a fresh restart with the drive and installation might be my next step.
 
hippyengineer said:
Would you have any more suggestions to help me troubleshoot this booting issue? You mentioned that you would reload your Ubuntu stick to compare your GUID to mine, although you did quote the ID in post 19. You must be extremely busy, so any more help troubleshooting would be greatly appreciated.
Click to expand...

I'll keep this post open. I haven't had time to create the Ubuntu USB to check.

I saw that Unibeast 6.1 was released and you mentioned that "OsxAptioFixDrv-64.efi should be used instead of OsxAptioFix2Drv-64.efi" so I thought a fresh restart with the drive and installation might be my next step.
Click to expand...


I don't recommend Unibeast for use with laptops. It isn't optimized at all for laptops.
 
Status
Not open for further replies.
Copyright © 2010 - 2024 tonymacx86 LLC
Back
Top