Setup & Software Discussions
automate-eGPU EFI - eGPU boot manager for macOS and Windows
 

[Solved] automate-eGPU EFI - eGPU boot manager for macOS and Windows  

 of  27
  RSS

Civa
 Civa
(@civa)
Active Member
Joined: 4 months ago
 
Posted by: @mac_editor
Posted by: @civa

So this will work with Catalina? 

The patches work - don't know about the tool itself as I haven't tried.

Posted by: @civa

I understand, though does this impact system performance, at all? 

No.

Great, now I have another issue: 

I repaired disk permissions, reset PRAM and VRAM, and then reboot the Mac Mini. What I have noticed is the screen with the automate eGPU works when I have HDMI connected, but the moment I disconnect HDMI from the computer and the monitor, I cannot see the screen to boot from the thumb drive. 

I have two LG 35um95 monitors, and the entire purpose of this was to be able to daisy chain both the monitors, a function the LGs have, via thunderbolt.

I suspect the Mac Mini was reading one monitor from HDMI, and one from thunderbolt and once I removed HDMI, it couldn't activate the screen to see the boot from USB. 

I want to continually run both monitors, once the Vega 56 arrives. How can I do this?

Mac Mini (Late 2012) , quad core i7 2.6 GHz, 16 GB DDR3, and Dual internal SSDs, 1 TB and 4 TB

AKiTiO Node Pro AMD Radeon R9 290X


ReplyQuote
joevt
(@joevt)
Prominent Member
Joined: 2 years ago
 

@civa if you can't see the Startup Manager, then move automate-eGPU EFI stuff to an HFS+ partition like I described, then use the bless command --setBoot option to change the boot preference, so you don't need to hold any keys during startup. Use the Startup Disk preferences panel to change the boot option back to normal when you don't want that anymore.

I haven't used automate-eGPU before. Does it require user input in EFI? If so then you'll have a problem.

When the Vega 56 arrives, you'll probably want to connect the displays via DisplayPort directly to the Vega 56.

Mac mini (2018), Mac Pro (Early 2008), MacBook Pro (Retina, 15-inch, Mid 2015), GA-Z170X-Gaming 7, Sapphire Pulse Radeon RX 580 8GB GDDR5, Sonnet Echo Express III-D, Trebleet Thunderbolt 3 to NVMe M.2 case


ReplyQuote
Civa
 Civa
(@civa)
Active Member
Joined: 4 months ago
 
Posted by: @joevt

@civa if you can't see the Startup Manager, then move automate-eGPU EFI stuff to an HFS+ partition like I described, then use the bless command --setBoot option to change the boot preference, so you don't need to hold any keys during startup. Use the Startup Disk preferences panel to change the boot option back to normal when you don't want that anymore.

I haven't used automate-eGPU before. Does it require user input in EFI? If so then you'll have a problem.

When the Vega 56 arrives, you'll probably want to connect the displays via DisplayPort directly to the Vega 56.

I’m using an akitio node pro, so the display port isn’t necessary, though I could probably see if that’s possible, connecting the one via display port, and then connecting them both via thunderbolt (the link function on the LGs works in thunderbolt) 

yes, the automate eGPU requires input in EFI 

I’m wondering is there’s a way I can eliminate the usb drive, and make this part of the system. I was reading about purge wrangler, last night, and also saw it seems Mac Editor and one other person were doing this from their system drives, back in 2018.

Mac Mini (Late 2012) , quad core i7 2.6 GHz, 16 GB DDR3, and Dual internal SSDs, 1 TB and 4 TB

AKiTiO Node Pro AMD Radeon R9 290X


ReplyQuote
mac_editor
(@mac_editor)
Famed Member Moderator
Joined: 3 years ago
 
Posted by: @civa

I’m wondering is there’s a way I can eliminate the usb drive

@civa that’s what @joevt suggested in his long post.

Posted by: @joevt

if you can't see the Startup Manager, then move automate-eGPU EFI stuff to an HFS+ partition like I describe

There is no EFI output over displays connected to eGPU except on 2018 Mac Mini. To see the menu, a display must be directly connected to the Mac mini (iGPU). Once done, you can plug in the display to your eGPU as needed. 

This post was modified 2 months ago

purge-wranglerpurge-nvdaset-eGPU
Insights Into macOS Video Editing Performance (Coming Soon)
2018 MacBook Pro 15" RP560X + RX 5700 XT (Mantiz Venus)


ReplyQuote
Civa
 Civa
(@civa)
Active Member
Joined: 4 months ago
 
Posted by: @mac_editor
Posted by: @civa

I’m wondering is there’s a way I can eliminate the usb drive

@civa that’s what @joevt suggested in his long post.

Posted by: @joevt

if you can't see the Startup Manager, then move automate-eGPU EFI stuff to an HFS+ partition like I describe

There is no EFI output over displays connected to eGPU except on 2018 Mac Mini. To see the menu, a display must be directly connected to the Mac mini (iGPU). Once done, you can plug in the display to your eGPU as needed. 

Okay, I understand now 
Is there any way I can boot with the eGPU? 
As in, if the utility is on the startup disk, could it not just reference the utility as part of the boot log? (Do not know if I’m using the correct terminology)

Mac Mini (Late 2012) , quad core i7 2.6 GHz, 16 GB DDR3, and Dual internal SSDs, 1 TB and 4 TB

AKiTiO Node Pro AMD Radeon R9 290X


ReplyQuote
mac_editor
(@mac_editor)
Famed Member Moderator
Joined: 3 years ago
 
Posted by: @goalque

There are a couple of key short cuts in EFI menu screen (after q is pressed): s=quick shut down, r=restart. Reset deletes the nvram setting if you have set the USB stick bootable (launch on startup = ON). The stick remembers the last chosen operating system and marks that as a "*" character. This flag can be used for quick boot or timed out warm reboots in the future.

@civa from the main post. You could set it up as this and boot blindly by pressing enter. 

Perhaps it may be easier for you to just use purge-wrangler instead if this feels complicated.

Finally, I also recommend searching through the forums first as most questions have been addressed previously before👍

purge-wranglerpurge-nvdaset-eGPU
Insights Into macOS Video Editing Performance (Coming Soon)
2018 MacBook Pro 15" RP560X + RX 5700 XT (Mantiz Venus)


ReplyQuote
Civa
 Civa
(@civa)
Active Member
Joined: 4 months ago
 
Posted by: @mac_editor
Posted by: @goalque

There are a couple of key short cuts in EFI menu screen (after q is pressed): s=quick shut down, r=restart. Reset deletes the nvram setting if you have set the USB stick bootable (launch on startup = ON). The stick remembers the last chosen operating system and marks that as a "*" character. This flag can be used for quick boot or timed out warm reboots in the future.

@civa from the main post. You could set it up as this and boot blindly by pressing enter. 

Perhaps it may be easier for you to just use purge-wrangler instead if this feels complicated.

Finally, I also recommend searching through the forums first as most questions have been addressed previously before👍

I DID set it up to boot from the USB (set to "ON"), it just isn't doing it. 
Will purge wrangler recognize the eGPU on boot up?

Mac Mini (Late 2012) , quad core i7 2.6 GHz, 16 GB DDR3, and Dual internal SSDs, 1 TB and 4 TB

AKiTiO Node Pro AMD Radeon R9 290X


ReplyQuote
joevt
(@joevt)
Prominent Member
Joined: 2 years ago
 
Posted by: @civa

I’m using an akitio node pro , so the display port isn’t necessary, though I could probably see if that’s possible, connecting the one via display port, and then connecting them both via thunderbolt (the link function on the LGs works in thunderbolt) 

The Display Port of the Node Pro is connected via Thunderbolt to the iGPU of the Mac Mini, and not the GPU in the Node Pro. The same is true for any Thunderbolt display connected to a Thunderbolt port (except the Thunderbolt ports of the BlackMagic eGPU).

Mac mini (2018), Mac Pro (Early 2008), MacBook Pro (Retina, 15-inch, Mid 2015), GA-Z170X-Gaming 7, Sapphire Pulse Radeon RX 580 8GB GDDR5, Sonnet Echo Express III-D, Trebleet Thunderbolt 3 to NVMe M.2 case


ReplyQuote
Espionage724
(@espionage724)
Active Member
Joined: 4 months ago
 

This isn't working on Catalina (release 19A583); booting from the flash drive (created with command in 1st post) and selecting macOS, it just halts (nothing happens after 1 minute of waiting). In Mojave, doing this proceeded to boot macOS and go to the log-in screen.

MacBook Pro (Retina, 13-inch, Mid 2014)
AKiTiO Thunder2
XFX Radeon RX 580
macOS Catalina 10.15
Fedora Workstation 31 Beta


ReplyQuote
Bastion
(@bastion)
New Member
Joined: 2 months ago
 

I have installed EFI via the installer terminal script from @mac_editor 
When I launch the EFI usb disc, it detects the external gpu as well as the internal one. 
I hit q and choose my mac os, the screen freezes. When I choose windows, it loads the logo 2 times and then the mac shuts off.

Here is my set up:
Mac Mini 2018 with 16 gb ram and 6 core i5 intel processors at 3 ghz
Windows10 Pro partition on the internal SSD disc and boot camp too. 
Mac OSX Catalina 10.15

Akito Node Thunderbolt 3 with a AMD Radeon RX 580

Two monitors, the main one connected to the card, the secondary connected to the Mac Mini.

I have read through a substantial part of the posts here, but not all (its quite a lot) and tried some of the troubleshoots, but nothing worked so far. I have disabled security settings for the T2 chip and Fire Vault is disabled.

Hot plugging the card hasnt worked, clean start up several times hasnt worked, and several other things i've tried either.

After several hours I am at the ends of my wits. What am I doing wrong?

Thanks in advance for any advice you can give. Im am thrilled to have found a community so dedicated to such a special topic.

 

This post was modified 2 months ago

MAC Mini 2018 6 core i5 at 3 Ghz; 16 GB Ram
Internal SSD drive with boot camp and windows partition

Akito Node Thunderbolt 3 with AMD Radeon XR 580

External SSD for game files

External USB drive for EFI boot

2 Monitors; Samsung 23" and Samsung 27"


ReplyQuote
DidierC41
(@didierc41)
Active Member
Joined: 2 years ago
 

@goalque

Hi all, I am back on track after a while...

Since my setup was working like a charm with your great EFI solution v.1.0.4 and High Sierra 10.13.6, I was reluctant to update to v1.0.5 (and to update MacOS to Mojave or now Catalina that could break my setup).

But I decided to try (say to "prepare for future updates"), but I cannot get v1.0.5 to work: First, I had read through almost this entire thread and I could not find how I can uninstall automate-eGPU-EFI-v.1.0.4? I only have the installer .pkg file. But since the validate-kexts.sh says "ok", I tried v1.0.5 on my system.

Thus I set a clean USB stick (FAT32) and drop the v1.0.5 EFI folder on it, add the <key>MuxSetting</key> <integer>1</integer> in the config file (I have a MBP 15" late 2016 with dGPU), and boot (option) eGPU disconnected, got the splash screen with "No eGPU detected". And nothing else. I mean I cannot login, (eGPU not plugged), [q] has no effect, and I cannot open a terminal to type any pmset stuff.

Fortunately, if I option-boot using my v1.0.4 USB stick, the eGPU is still working like before, so v1.0.5 trial did not break my "obsolete" setup 🙂

I'm a little confused to ask such a dumb question several month after v1.0.5 release, I probably missed something? 

MacBookPro 15" 2016, MacOS 10.13.6 (17G8030), dGPU RP460, Sonnet eGFX BB550W, NVIDIA GTX 1080


ReplyQuote
mac_editor
(@mac_editor)
Famed Member Moderator
Joined: 3 years ago
 

Confirming that automate-eGPU EFI 1.0.5 is not functional on macOS Catalina - fails to load the OS. In my case, it remains stuck at the menu. Windows loads fine.

This post was modified 2 months ago

purge-wranglerpurge-nvdaset-eGPU
Insights Into macOS Video Editing Performance (Coming Soon)
2018 MacBook Pro 15" RP560X + RX 5700 XT (Mantiz Venus)


ReplyQuote
kamil6x
(@kamil6x)
New Member
Joined: 10 months ago
 

@goalque

Suggestions for editing the installer script.

1)Unzip hangs when it needs user input.

unzip -d "${target_dir}" "${target_dir}/EFI.zip" 1>/dev/null 2>&1
to: unzip -d "${target_dir}" "${target_dir}/EFI.zip"

2)Same with Curl as there is a handshake failure and it doesn't download EFI.zip.

curl -L -s -o "${target_dir}/EFI.zip" "https://egpu.io/wp-content/uploads/2018/10/EFI.zip"

to

curl -L -o "${target_dir}/EFI.zip" "https://egpu.io/wp-content/uploads/2018/10/EFI.zip"

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


ReplyQuote
mac_editor
(@mac_editor)
Famed Member Moderator
Joined: 3 years ago
 

@kamil6x

Thanks for the suggestions. I wrote that little installer. I will plan a better update to it once automate-eGPU EFI starts working on macOS Catalina.

purge-wranglerpurge-nvdaset-eGPU
Insights Into macOS Video Editing Performance (Coming Soon)
2018 MacBook Pro 15" RP560X + RX 5700 XT (Mantiz Venus)


ReplyQuote
AJ Scarcella
(@aj_scarcella)
Trusted Member
Joined: 2 months ago
 

Is @goalque still around? Seems like it's been a few months since they've last been here. I'd like to upgrade to Catalina, but not at the expense of breaking eGPU support.

Mac Pro 2013
OWC Mercury Helios FX
Radeon RX 580 8GB


slhdsnet liked
ReplyQuote
slhdsnet
(@slhdsnet)
Trusted Member
Joined: 12 months ago
 

@aj_scarcella

Ditto here, I did the upgrade to Catalina and sure enough, this broke the ability to use my eGPU via the automate-eGPU EFI installer...

nMP-Mac Pro (Late 2013) with AMD FirePro D300's (x2)
✧ macOS Catalina 10.15.1 (19B88) ✧
automate-eGPU EFI (v1.0.5) USB ✧ (Note: Awaiting update to re-enable TB1/2 patch for Catalina)
OWC Mercury Helios FX eGPU / AMD Radeon RX Vega 56 8GB / Apple TB3-TB2 Cable Adapter ✧
✧ NewerTech HDMI Headless Video Adapter ✧


ReplyQuote
goalque
(@goalque)
Noble Member Admin
Joined: 3 years ago
 
Posted by: @aj_scarcella

Is @goalque still around? Seems like it's been a few months since they've last been here. I'd like to upgrade to Catalina, but not at the expense of breaking eGPU support.

I am here but fully committed to my job which takes all my time, unfortunately not related to eGPUs. I'll look into this if I find time.

automate-eGPU EFIapple_set_os.efi
--
2018 13" MacBook Pro + Radeon [email protected] + Win10 1809


slhdsnet, blisster138, AJ Scarcella and 2 people liked
ReplyQuote
mac_editor
(@mac_editor)
Famed Member Moderator
Joined: 3 years ago

ReplyQuote
AJ Scarcella
(@aj_scarcella)
Trusted Member
Joined: 2 months ago
 

@goalque

Ah, totally fair. Thanks for the reply! Is it outside the realm of possibility to publish it to Github or something similar?

Mac Pro 2013
OWC Mercury Helios FX
Radeon RX 580 8GB


slhdsnet liked
ReplyQuote
joevt
(@joevt)
Prominent Member
Joined: 2 years ago
 
Posted by: @goalque

 

  • For NVIDIA, no changes are made, while for AMD, the NVIDIA NVRAM value is removed, and @goalque's NVIDIA patch is replaced with my Thunderbolt 1/2 patch, that enables native-like eGPU support with the eGPU icon in the menubar working as expected.

 

The Thunderbolt 1/2 patch isn't applied for Nvidia?

I would use the same config.plist for everyone and use the Disabled flag to remove patches that don't apply. Does this version of clover support the Disabled flag?

 

This post was modified 2 months ago

Mac mini (2018), Mac Pro (Early 2008), MacBook Pro (Retina, 15-inch, Mid 2015), GA-Z170X-Gaming 7, Sapphire Pulse Radeon RX 580 8GB GDDR5, Sonnet Echo Express III-D, Trebleet Thunderbolt 3 to NVMe M.2 case


ReplyQuote
Sereosh
(@sereosh)
Active Member
Joined: 2 years ago
 

Used to have a Catalina+Windows 10 installation, but decided to go back to High Sierra and stick to macos with my 1070 eGPU.

I have a 2016 MBP 15" with a Radeon Pro 460 and AORUS Gaming box 1070.

I got it working with this guide but I'm having a little problem: whenever I'm not using my eGPU and I want to connect an external display (for a powerpoint presentation, or connecting to a TV, stuff like that), the system will freeze. A temporary fix was to play around with the sudo pmset -a gpuswitch commands to re-enable the dGPU. Problem is whenever I come home and want to use my eGPU, I'll have terrible performance until I run those commands again.

Is there a way to avoid switching back and forth between forced iGPU to use my eGPU and activated dGPU for when I need to connect an external display?

 

EDIT: Hot plugging+logging out and logging back in seems to work without the commands? This is so confusing.

This post was modified 2 months ago

2016 MBP 15"
Radeon Pro 460 dGPU
AORUS Gaming Box 1070 eGPU
macOS 13.16.6


ReplyQuote
slhdsnet
(@slhdsnet)
Trusted Member
Joined: 12 months ago
 

@goalque

Fully agree with @aj_scarcella, i.e. totally fair and many thanks for your update.  You have been instrumental to making available the  automate-eGPU EFI installer for the Thunderbolt 1/2 community to begin with.  Hence am looking forward to any updates to your installer in the future.  Keep up with this awesome work of yours !!  With kind regards, Stephane.

nMP-Mac Pro (Late 2013) with AMD FirePro D300's (x2)
✧ macOS Catalina 10.15.1 (19B88) ✧
automate-eGPU EFI (v1.0.5) USB ✧ (Note: Awaiting update to re-enable TB1/2 patch for Catalina)
OWC Mercury Helios FX eGPU / AMD Radeon RX Vega 56 8GB / Apple TB3-TB2 Cable Adapter ✧
✧ NewerTech HDMI Headless Video Adapter ✧


ReplyQuote
mac_editor
(@mac_editor)
Famed Member Moderator
Joined: 3 years ago
 

@joevt

My Thunderbolt 1/2 patch is different from goalque’s NVIDIA patches (or more accurately IOPCITunneled patches), the former providing eGPU icon and proper eject mechanism as on native TB3 but on TB1/2 devices for AMD. The latter patch works as is, irrespective of Thunderbolt version, without eGPU icon in menu bar. I consider them as mutually exclusive patches. The default config the download provides applies the NVIDIA patches. Wasn’t sure what exact specs this app adhered to so the install script replaces the patch instead, but your suggestion makes sense if Disabled flag is supported. 

purge-wranglerpurge-nvdaset-eGPU
Insights Into macOS Video Editing Performance (Coming Soon)
2018 MacBook Pro 15" RP560X + RX 5700 XT (Mantiz Venus)


ReplyQuote
joevt
(@joevt)
Prominent Member
Joined: 2 years ago
 

@mac_editor For the Disabled flag, I guess it would depend on what version of Clover goalque 's boot loader is based on. Even if we don't have automate-eGPU EFI source code to check, he could at least give the version of Clover used and which features if any were removed so we can check Clover's source code.

About mutually exclusive, are you saying that the Thunderbolt 1/2 patch is not required to use Nvidia cards with Thunderbolt 2 Macs? The Thunderbolt 1/2 patch is only for enabling the eject eGPU menu which doesn't work with Nvidia eGPUs?

 

Mac mini (2018), Mac Pro (Early 2008), MacBook Pro (Retina, 15-inch, Mid 2015), GA-Z170X-Gaming 7, Sapphire Pulse Radeon RX 580 8GB GDDR5, Sonnet Echo Express III-D, Trebleet Thunderbolt 3 to NVMe M.2 case


ReplyQuote
mac_editor
(@mac_editor)
Famed Member Moderator
Joined: 3 years ago
 

@joevt

I think the logs might have the Clover version IIRC. If goalque hasn’t modified KernelAndKextPatches functionality, it should work as is.

The TB1/2 patch isn’t required for NVIDIA because the IOPCITunneled patch already bypasses it (along with capabilities like eGPU icon + it’s also done in multiple kexts for NVIDIA to work). Alone, the TB1/2 patch is insufficient to run NVIDIA cards. Hence I mentioned above that I consider them as mutually exclusive patches for implementations sake as the TB1/2 patch is sufficient for AMD cards. Sorry for the confusion. 

purge-wranglerpurge-nvdaset-eGPU
Insights Into macOS Video Editing Performance (Coming Soon)
2018 MacBook Pro 15" RP560X + RX 5700 XT (Mantiz Venus)


ReplyQuote
joevt
(@joevt)
Prominent Member
Joined: 2 years ago
 

@mac_editor Yup, debug.log says "Clover revision: 4513 on Apple EFI". It appears the Disabled flag has existed since 3327.

Mac mini (2018), Mac Pro (Early 2008), MacBook Pro (Retina, 15-inch, Mid 2015), GA-Z170X-Gaming 7, Sapphire Pulse Radeon RX 580 8GB GDDR5, Sonnet Echo Express III-D, Trebleet Thunderbolt 3 to NVMe M.2 case


ReplyQuote
goalque
(@goalque)
Noble Member Admin
Joined: 3 years ago
 

I just debugged and it doesn't find the boot.efi. Pointing to Preboot volume does not work anymore, or more precisely the suffix:

\\00000000-0000-0000-0000-000000000000\\System\\Library\\CoreServices\\boot.efi

I also tried searching by "Macintosh HD - Data" and hardcoding the Preboot volume uuid (from diskutil info command), but no luck.

status = gBS->LoadImage(FALSE, SelfImageHandle, path, NULL, 0, &image);

Returns "Not found". 

I recall that everything was working in 19A471t beta, FileVault enabled. Currently, changing DefaultVolume in config.plist has no effect because "Preboot" is hardcoded into source code in my implementation.

https://www.tonymacx86.com/threads/macos-10-15-catalina-is-now-available-on-the-mac-app-store.284169/page-80#post-2021094

"As others have mentioned on this thread, Clover is currently not booting macOS Catalina when the boot drive is encrypted with FileVault."

"Unfortunately, I have not read a single success story on this Catalina FileVault".

This post was modified 2 months ago

automate-eGPU EFIapple_set_os.efi
--
2018 13" MacBook Pro + Radeon [email protected] + Win10 1809


ReplyQuote
mac_editor
(@mac_editor)
Famed Member Moderator
Joined: 3 years ago
 

@goalque

Some other posted experiences are about slow boot into FileVault-enabled Catalina (eventually they do seem to get in though):

https://www.reddit.com/r/hackintosh/comments/d1m24i/extremely_slow_filevault_boot_on_catalina/

https://www.insanelymac.com/forum/topic/339035-pre-release-macos-catalina/?page=69&tab=comments#comment-2692344

https://sourceforge.net/p/cloverefiboot/tickets/607/?limit=25

In the suffix above, the zeroes are supposed to be the disk UUID I presume? The difference with Catalina is the addition of Volume Groups, but my Preboot Volume still retains the UUID for the main (non-data) disk, and not the ID of the Volume Group (which I thought could potentially be a case).

I also think dosdude1 has an APFS Booter which is required for older Macs and works on Catalina but not sure if its open source.

This post was modified 2 months ago

purge-wranglerpurge-nvdaset-eGPU
Insights Into macOS Video Editing Performance (Coming Soon)
2018 MacBook Pro 15" RP560X + RX 5700 XT (Mantiz Venus)


goalque liked
ReplyQuote
goalque
(@goalque)
Noble Member Admin
Joined: 3 years ago
 
Posted by: @mac_editor

In the suffix above, the zeroes are supposed to be the disk UUID I presume? The difference with Catalina is the addition of Volume Groups, but my Preboot Volume still retains the UUID for the main (non-data) disk, and not the ID of the Volume Group (which I thought could potentially be a case).

I also think dosdude1 has an APFS Booter which is required for older Macs and works on Catalina but not sure if its open source.

I am on macOS 10.15 (19A602). Somewhat worked on beta builds.

Yes, zeros are replaced with the correct disk UUID. I don't know what it should be now. The debug log "Device path str" shows the final path where it tries to boot. It is either string concatenation issue or a security improvement by Apple.

automate-eGPU EFIapple_set_os.efi
--
2018 13" MacBook Pro + Radeon [email protected] + Win10 1809


itsage liked
ReplyQuote
mac_editor
(@mac_editor)
Famed Member Moderator
Joined: 3 years ago
 

@goalque

Okay. I think the issue then is that your bootloader is pulling in the APFS Volume Group UUID instead of the actual volume in question. Here's the disk info for my boot disk "macOS":

Spoiler
Boot Disk Info

   Device Identifier:         disk1s5

   Device Node:               /dev/disk1s5

   Whole:                     No

   Part of Whole:             disk1

 

   Volume Name:               macOS

   Mounted:                   Yes

   Mount Point:               /

 

   Partition Type:            41504653-0000-11AA-AA11-00306543ECAC

   File System Personality:   APFS

   Type (Bundle):             apfs

   Name (User Visible):       APFS

   Owners:                    Enabled

 

   OS Can Be Installed:       Yes

   Booter Disk:               disk1s2

   Recovery Disk:             disk1s3

   Media Type:                Generic

   Protocol:                  PCI-Express

   SMART Status:              Verified

   Volume UUID:               AA35BF6B-E9DD-4F36-A70C-49CE2B830BE5

   Disk / Partition UUID:     AA35BF6B-E9DD-4F36-A70C-49CE2B830BE5

 

   Disk Size:                 440.0 GB (440000290816 Bytes) (exactly 859375568 512-Byte-Units)

   Device Block Size:         4096 Bytes

 

   Container Total Space:     440.0 GB (440000290816 Bytes) (exactly 859375568 512-Byte-Units)

   Container Free Space:      156.8 GB (156814884864 Bytes) (exactly 306279072 512-Byte-Units)

   Allocation Block Size:     4096 Bytes

 

   Read-Only Media:           No

   Read-Only Volume:          No

 

   Device Location:           Internal

   Removable Media:           Fixed

 

   Solid State:               Yes

   Hardware AES Support:      Yes

 

   This disk is an APFS Volume.  APFS Information:

   APFS Container:            disk1

   APFS Physical Store:       disk0s2

   Fusion Drive:              No

   APFS Volume Group:         4E5A5009-3743-46F1-AF49-211BEFF4771B

   FileVault:                 Yes

   Locked:                    No

The full device path str from my debug log:

Device path str: PciRoot(0x0)/Pci(0x1B,0x0)/Pci(0x0,0x0)/SasEx(0x0100000000000000,0x000000007074616C,0x0,NoTopology,0,0,0)/HD(2,GPT,1528ADA3-65D4-4F70-B475-7B9FDEAD77DF,0x12C06,0x66720FA)/VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,1EEFA3EA32654D4EA3B5E012AB9AEFD6)/\4E5A5009-3743-46F1-AF49-211BEFF4771B\System\Library\CoreServices\boot.efi

The UUID in the string is that of the APFS Volume Group whereas it should be that of the boot disk, which is (from spoiler above):

AA35BF6B-E9DD-4F36-A70C-49CE2B830BE5

For reference, my Preboot volume boot.efi path is:

/Volumes/Preboot/AA35BF6B-E9DD-4F36-A70C-49CE2B830BE5/System/Library/CoreServices/boot.efi
This post was modified 2 months ago

purge-wranglerpurge-nvdaset-eGPU
Insights Into macOS Video Editing Performance (Coming Soon)
2018 MacBook Pro 15" RP560X + RX 5700 XT (Mantiz Venus)


goalque and itsage liked
ReplyQuote
goalque
(@goalque)
Noble Member Admin
Joined: 3 years ago
 

It was originally "Macintosh HD" disk, but FileVault worked only with the "Preboot" volume.

I can search for the correct volume handle by name, maybe one of those legacy HDs or "Whole Disk Boot". These names are given by the EFI environment in the log:

Volume name: Whole Disc Boot
Volume name: EFI
Volume name: Legacy HD2
Volume name: Legacy HD3
Volume name: Legacy HD4
Volume name: Preboot

I will try later.

automate-eGPU EFIapple_set_os.efi
--
2018 13" MacBook Pro + Radeon [email protected] + Win10 1809


itsage and mac_editor liked
ReplyQuote
mac_editor
(@mac_editor)
Famed Member Moderator
Joined: 3 years ago

itsage liked
ReplyQuote
goalque
(@goalque)
Noble Member Admin
Joined: 3 years ago
 

Does anyone happen to have Catalina beta logs? Would be interesting to see if the first part of the "Device path str" remains the same. The suffix now goes wrong due to likely bug in APFSContainer_Support() method.

https://sourceforge.net/p/cloverefiboot/code/HEAD/tree/rEFIt_UEFI/refit/main.c

It seems to pick up the Volume Group UUID always. However, manually added "Preboot" UUID suffix (the value from diskutil command) didn't work either when I tested.

automate-eGPU EFIapple_set_os.efi
--
2018 13" MacBook Pro + Radeon [email protected] + Win10 1809


ReplyQuote
mac_editor
(@mac_editor)
Famed Member Moderator
Joined: 3 years ago
 
Posted by: @goalque

However, manually added "Preboot" UUID suffix (the value from diskutil command) didn't work either when I tested.

Interesting. Assuming Preboot volume is accessible as always, I would have expected the UUID of the primary volume (for clarification, not the UUID of Preboot volume itself) to have worked. Guess something more has changed. Edit: looks like it worked, see below. 

This post was modified 2 months ago

purge-wranglerpurge-nvdaset-eGPU
Insights Into macOS Video Editing Performance (Coming Soon)
2018 MacBook Pro 15" RP560X + RX 5700 XT (Mantiz Venus)


ReplyQuote
goalque
(@goalque)
Noble Member Admin
Joined: 3 years ago
 

"Preboot" volume + "Macintosh HD" UUID combo worked! Logged into macOS 10.15 successfully FileVault enabled 🙂 I will test more tomorrow. So we just need to wait for APFSContainer_Support() fix in Clover.

This post was modified 2 months ago

automate-eGPU EFIapple_set_os.efi
--
2018 13" MacBook Pro + Radeon [email protected] + Win10 1809


ReplyQuote
goalque
(@goalque)
Noble Member Admin
Joined: 3 years ago
 

Here's the quick fix.

https://egpu.io/wp-content/uploads/2019/10/automate-eGPU.efi_.zip

Replace the old automate-eGPU.efi and add a new key-value pair into config.plist (under Boot dict):

<key>MacOSVolumeUUID</key>
<string>00000000-0000-0000-0000-000000000000</string>
where the string value is your "Macintosh HD" UUID:
diskutil info "Macintosh HD" | grep "Volume UUID"

Worked fine with HD 7970 but GTX 780 did not provide eGPU screen output.

This post was modified 2 months ago

automate-eGPU EFIapple_set_os.efi
--
2018 13" MacBook Pro + Radeon [email protected] + Win10 1809


ReplyQuote
 of  27