EFI Agent v1.3.2 (menu bar utility)

[headkaze]

On the screens that have no focus MountEFI icon will not dim.

Can you please try MountEFI v1.1.5

 

[BreBo]

Can you please try MountEFI v1.1.5

Fixed

 

[ski4evr]

The issue is that some users don't appear to have the "efi-boot-device" value set in their NVRAM

How do you set the value in NVRAM? I'm not getting the green highlight on my boot EFI

 

[headkaze]

How do you set the value in NVRAM? I'm not getting the green highlight on my boot EFI

Since it appears that many people don't have this value in NVRAM it would probably be better for me to get the boot EFI value another way. I'm just not sure what it would be.

 

[headkaze]

MountEFI v1.1.6 Released
- Added percentage bars showing space used on mounted partitions

 

[headkaze]

@jaymonkey @UtterDisbelief @ski4evr

vit9696 suggested I get the boot device from IODeviceTree:/chosen/boot-device-path. Please try MountEFI v1.1.7 and let me know if it shows the boot EFI correctly now.

 

[jaymonkey]

vit9696 suggested I get the boot device from IODeviceTree:/chosen/boot-device-path. Please try MountEFI v1.1.7 and let me know if it shows the boot EFI correctly now.

@headkaze,

That did it my friend ..... working now on my laptop.



However running MountEFI 1.1.7 on my desktop system results in the Boot EFI not being highlight (its disk1s1) in the image below ...



As you can see boot-device-path does exist in the ioreg, the data value is this :-

<02 01 0c 00 d0 41 03 0a 00 00 00 00 01 01 06 00 02 01 01 01 06 00 00 00 03 17 10 00 01 00 00 00 00 25 38 c3 71 b1 57 a3 04 01 2a 00 02 00 00 00 28 40 06 00 00 00 00 00 60 d2 97 3b 00 00 00 00 c5 2d c3 0f 95 d1 67 4c bb e2 5f 55 7b 29 66 d6 02 02 04 03 24 00 f7 fc 74 be 7c 0b f3 49 91 47 01 f4 04 2e 68 42 a0 37 ed 7f 2a 91 a4 34 b7 e1 ee 28 ca 59 46 a9 7f ff 04 00>

My desktop system has a non standard boot configuration, it boots Clover from an EFI partition on disk1 but MacOS is booted/run from NVMe disk3 (APFS disk 4), I have to do it this way as my motherboard lacks support for booting directly from NVMe, of course this is totally non-Mac standard so might be why it does not work ?

Still at least it works on my laptop now and I suspect that this new method should work for the majority of other users who where lacking the EFI being high-lighted.

Great work as always buddy.

Cheers
Jay

 

[headkaze]

My desktop system has a non standard boot configuration, it boots Clover from an EFI partition on disk1 but MacOS is booted/run from NVMe disk3 (APFS disk 4), I have to do it this way as my motherboard lacks support for booting directly from NVMe, of course this is totally non-Mac standard so might be why it does not work ?

Using IODeviceTree:/chosen/boot-device-path I have to assume the EFI location is on the same drive and I think IODeviceTree:/options/efi-boot-device has the same problem. As far as I'm aware there is no reliable way of knowing which is the exact EFI partition the system has booted from.

 

[headkaze]

FYI You can now drag the position of the splitter to adjust the table views

 

[UtterDisbelief]

@jaymonkey @UtterDisbelief @ski4evr

vit9696 suggested I get the boot device from IODeviceTree:/chosen/boot-device-path. Please try MountEFI v1.1.7 and let me know if it shows the boot EFI correctly now.

Great work! All is working now and properly highlighted.

I hadn't noticed the drive storage/amount used colour-bars before and that's looking pretty good too

Thanks for all your hard work on this. A very useful tool.