Two new eGPU solutions on macOS 10.13.4: pure EFI and hybrid
I can confirm that the hybrid solution is working for me as design on MBP 13" TouchBar 2017 + Aorus Gaming Box 1070 + latest NVIDIA Drivers with SkipSetupDataForOSX=false in config.plist. I did not tried the Pure EFI...
The issue I encountered previously - Clover boot hang, was related to issue with the default boot entry not found. ( I installed solution on local drive)
unlocking 'Startup Disk' in system preferences fixed the problem for next reboot, but subsequent reboots still hang at Clover.
This is consistent with the following line from the Clover Wiki:
0:617 0:002 === [ GetEfiBootDeviceFromNvram ] =========================
0:618 0:000 Default boot entry not found
more info available at: https://www.tonymacx86.com/threads/solved-clover-wont-boot-from-default-boot-volume.221421/
I can confirm that this issue is not presented when the solution is installed on the external drive and it will boot properly.
@hkoster1 "Critical software component missing" is part of Apple's security mechanism in the newer firmwares, it seems that High Sierra checks the firmware against Apple's database:
even if the patch is done on the fly.
As said, Pure EFI isn't recommended approach, please choose the Hybrid.
It worked very well on my git:
Macbook Pro 15 2016
Razer Core X
Msi Gtx 970
I still have a few issues:
1. I use DisableMonitor to shut down the internal display. But the internal one keeps coming back whenever I quit from a full screen app.
2. Not sure if it is an issue. I got onely 2003 on the Unigine Valley Benchmark(Preset: Extreme HD).
3. When I try to watch 4k movie by Movist, it quits to the login screen.
@lexine When you installed the software on the "local drive", was it named "Macintosh HD" or something else, and what kind of Boot section was generated to the config.plist? The installer could pick up the unique volume ID instead of using volume name as it does now. Or might be easier to rewrite the boot logic all from scratch...
I don't have a backup of config.plist available now from those tests, but the default boot volume was set to Macintosh HD, I tried to change it for a disk UUID but no luck ... I noticed now that even when the solution is on USB stick I still need to select the start-up disk ... This is a complete new topic for me as I don't have so much experience with the Clover ... but anyway I noticed that it might have something to do with my nvram maybe? As the efi-boot-device is empty, but as soon as I setup the startup disk the variable will be created ... For sure I would need to study it a more to find out what is the problem ... but maybe someone else will already know 😉
Libors-MBP:~ lbaca$ nvram efi-boot-device
Here is the boot section which has been generated :
and here the disklist, I tried to used the UUID of the Macintosh HD and Preboot as recommended on other sites, but I did not had luck
Libors-MBP:~ lbaca$ diskutil list
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme 500.3 GB disk0
1: EFI EFI 314.6 MB disk0s1
2: Apple_APFS Container disk1 500.0 GB disk0s2
#: TYPE NAME SIZE IDENTIFIER
0: APFS Container Scheme - +500.0 GB disk1
Physical Store disk0s2
1: APFS Volume Macintosh HD 140.2 GB disk1s1
2: APFS Volume Preboot 22.6 MB disk1s2
3: APFS Volume Recovery 518.1 MB disk1s3
4: APFS Volume VM 1.1 GB disk1s4
I noticed now that even when the solution is on USB stick I still need to select the start-up disk ... This is a complete new topic for me as I don't have so much experience with the Clover ... but anyway I noticed that it might have something to do with my nvram maybe? As the efi-boot-device is empty, but as soon as I setup the startup disk the variable will be created ... For sure I would need to study it a more to find out what is the problem ... but maybe someone else will already know 😉
A quick look at the source revealed that there is a huge amount of code that will never be needed. I found the right spot:
UEFI boot: get gEfiBootDeviceGuid from NVRAM. // if present, ScanVolumes() will skip scanning other volumes // in the first run. // this speeds up loading of default macOS volume. GetEfiBootDeviceFromNvram(); }
Got the same error at some point once, I will try to reproduce the problem and then can fix it.
Not a mistake. Just remember to use installer's "Uninstall" option, don't do anything manually, otherwise the automate-eGPU.kext might be still in the cache. You might have the same issue as @lexine, regarding the default boot volume and nvram.
@goalque I just connected the eGPU while I was already working in MacOS (booted from EFI) and got the black screen on external monitoring, no surprise, it was the usual, so I logged of and back in but still black screen ... ok rebooted with EGPU connected, black screen ... change the SkipSetupDataForOSX back to true, rebooted now working ... so just to let you know that the screen is working for me with this value as well ... not sure what is going on, maybe my setup like to make fun of me ; -) ... I anyway I will enable debug log for next time .... I did not noticed anything special in the console log though ... any other place I can look next time to pin-point the problem ?