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

automate-eGPU EFI - eGPU boot manager for macOS and Windows  

 of  21
  RSS

goalque
(@goalque)
Noble Member Admin
Joined: 3 years ago
 
Posted by: elbat.
I can see GTX 1060 in System information but MBP is still using built in GPU.

That's good, everything is ok. What macOS build number? Get an external monitor or:
https://egpu.io/forums/mac-setup/potentially-accelerate-all-applications-on-egpu-macos-10-13-4/

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


ReplyQuote
natemac00
(@natemac00)
Eminent Member
Joined: 2 years ago
 
Posted by: goalque
Posted by: Pavelusha
Posted by: goalque
Thanks for reporting. I've not had time to test the security update. Not sure why @zipp0rsch's and @nu_ninja's RX 460 via TB1/TB2 stopped working.

I am on MacBook Pro 2018 with TB3. May be that's the difference?

Maybe, TB1/TB2 patches are not applied in the config.plist. Maybe they are now necessary. Can anyone confirm TB2 Mac + Nvidia eGPU? Working or not?

I could not get your script to work, if you see my above earlier post.

3D Cinema 4D/Octane Artist
Gigabyte Aorus GTX 1080 Gaming Box w/ TB2to3 Adapter
2013 Mac Pro
2014 MacBook Pro


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

@natemac00 I wasn't sure what did you mean by "some update I accidentally clicked on yesterday". The security update?

I suppose this can be fixed by editing the config.plist, add TB1/TB2 patches.

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


ReplyQuote
natemac00
(@natemac00)
Eminent Member
Joined: 2 years ago
 
Posted by: goalque

@natemac00 I wasn't sure what did you mean by "some update I accidentally clicked on yesterday". The security update?

I suppose this can be fixed by editing the config.plist, add TB1/TB2 patches.

I'm guessing it was the security update cause it didn't change the 10.13.6 part.

3D Cinema 4D/Octane Artist
Gigabyte Aorus GTX 1080 Gaming Box w/ TB2to3 Adapter
2013 Mac Pro
2014 MacBook Pro


ReplyQuote
mac_editor
(@mac_editor)
Noble Member Moderator
Joined: 2 years ago
 

I recall reading somewhere that booting into a recovery partition may resolve some firmware kinks. For those facing issues with automate-eGPU EFI consider trying to boot into recovery, and from there choose your startup disk and boot normally. Then retry the USB with the app. More debugging options could be SMC/NVRAM resets.

purge-wrangler.shpurge-nvda.shset-eGPU.shautomate-eGPU EFI Installer
----
Troubleshooting eGPUs on macOS
Command Line Swiss Knife

Multiple Build Guides
----
Current: MacBook Pro RP560X + 480/R9 Fury/Vega 64 | GTX 780/1070
Previous: 2014 MacBook Pro 750M + 480/R9 Fury | GTX 780/980 Ti/1070


ReplyQuote
elbat
(@elbat)
New Member
Joined: 9 months ago
 

@goalgue I'm on Mojave 10.14, should i downgrade to High Sierra to use set-eGPU.sh ?
 "Note: Mojave has this built-in now. As of this time, the new OS does not respect plist settings for some reason."

I want to use my Aourus GTX 1070 Gaming box for Octane renderer, is that even possible ?

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


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

@goalgue I'm on Mojave 10.14, should i downgrade to High Sierra to use set-eGPU.sh ?
 "Note: Mojave has this built-in now. As of this time, the new OS does not respect plist settings for some reason."

I want to use my Aourus GTX 1070 Gaming box for Octane renderer, is that even possible ?

Nvidia web drivers don’t exist for Mojave.

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


ReplyQuote
elbat
(@elbat)
New Member
Joined: 9 months ago
 

Ok thanks for the fast answer @goalque, I will downgrade to 10.13 and try again.

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


ReplyQuote
OliverB
(@oliverb)
Noble Member
Joined: 9 months ago
 
Posted by: itsage

A really nice feature of @goalque's EFI Boot Manager is the deactivation of dGPU activation of iGPU for 15" MacBook Pro in both macOS and Windows. I accidentally left the PCI Express Controller 1901 [to Radeon 450 dGPU] disabled when booted into macOS. Prior to using this EFI boot manager, next boot into Windows partition would result in a stuck Windows logo boot screen. Well this time the boot manager assisted Windows to use the iGPU for the internal display. All was working great.

In one of my progress updates, I mentioned storing the precompiled dsdt.aml file on this boot loader could provide Large Memory allocation in Boot Camp. My 2016 15" MacBook Pro is now effectively working in Windows as a iGPU-only Thunderbolt 3 laptop. The only non-working functionality is brightness adjustment. Large memory allocation helps me resolve error 12 with both Nvidia and AMD eGPU. I was actually able run two AMD RX 580 eGPUs once I disabled one of the PCIe Controllers to TB3 ports. Truly amazing work by @goalque!

Goalque's Tool is amazing, but not absolutely necessary for Bootcamp. By deactivating all drivers before plugging the eGPU I could get Windows to run solely on eGPU, no patch whatever necessary. Ok, I can't change the resolution one the internal display (run officially by Microsoft Basic Device Driver), but I don't really care.

PS: If I use the Efi-Bootdriver to boot my windows I get error 43....Of course for the unlocking of nVidia in macOsx this is a must. Shame on apple and its politics.

2018 15" MBP & 2015 13" MBP connected to RTX2080Ti GTX1080Ti GTX1080 Vega56 RX580 R9-290 GTX680


ReplyQuote
Eightarmedpet
(@eightarmedpet)
Noble Member
Joined: 2 years ago
 

Error 43 is usually driver/power related, when I tried the EFI bootloader Windows booted was if it was a fresh instal in a way and it had to re recognise all my peripherals and I had error 43 too until I reinstalled drivers.

2017 13" MacBook Pro Touch Bar
GTX1060 + AKiTiO Thunder3 + Win10
GTX1070 + Sonnet Breakaway Box + Win10
GTX1070 + Razer Core V1 + Win10
Vega 56 + Razer Core V1 + macOS + Win10
Vega 56 + Mantiz Venus + macOS + W10

---

LG 5K Ultrafine flickering issue fix


ReplyQuote
Research777
(@research777)
Active Member
Joined: 11 months ago
 
Posted by: Research777

Greetings

I'm completely confused)

For several months now I have been trying to connect the Aorus Gaming Box GTX1080 + TB3-TB2 / 1 adapter.

The task is simple, using eGPU to play Steam games.

iMac 21'5 (late 2012); i7; 16Gb; 1.12 Tb Fusion Drive; dGPU GT650M

When downloaded to MacOS, the HighSierra eGPU starts and is detected (using the NVIDIA purge-wrangler + web driver).

But Steam does not start, because No support for Open CL / GL in Web Drivers.

When loading Windows, the Bootcamp eGPU is not detected during the hotplug and does not boot from the connected eGPU. (

I tried different ways with loading Windows, even with a clean UEFI installation (there are other compatibility issues with two Nvidia dGPU + eGPU)

Can your automate-egpu-efi help me?

Guys! Help with the answer)

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


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

Sorry, I don’t know anything about iMacs. If it has the Intel iGPU, I would try MuxSetting=1 and disabling GT650M and force web drivers to use only the eGPU. Not sure how, I have no experience of Nvidia dGPU models.

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


ReplyQuote
Research777
(@research777)
Active Member
Joined: 11 months ago
 

All iMacs are executed without iGPU support only dGPU. But when booting your UEFI, it shows two intel HD4000 and GT650M graphic processors. Does it make sense to enable MuxSetting = 1?

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


ReplyQuote
NavilleZhang
(@navillezhang)
Trusted Member
Joined: 9 months ago
 

Hi:
I've tried using this instead of the traditional step-by-step guide.
I've downloaded the 1.0.5 files and installed them into my internal EFI (I installed reFINEd first and mounted my EFI using refined).
During start up, if I have eGPU plugged in prior to booting, I get a blackscreen.
I'm able to execute the automate-eGPU.efi in refined when eGPU is not plugged in, however it just stucks at ``Using Configuration ''``.

I'm using a 2016 15inch Macbook Pro, an NVIDIA eGPU and macOS Mojave. My kexts are clean.

EFI/CLOVER/misc/debug.log

0:100 0:100 MemLog inited, TSC freq: 2904465550
0:100 0:000 CPU was calibrated with RTC
0:100 0:000 start
0:100 0:000
0:100 0:000 Now is 2.11.2018, 22:4:39 (GMT)
0:100 0:000 Starting Clover revision: 4513 on Apple EFI
0:100 0:000 Build with: [Args: -mc --no-usb -D NO_GRUB_DRIVERS_EMBEDDED -t XCODE8 | -D DISABLE_USB_SUPPORT -D NO_GRUB_DRIVERS_EMBEDDED --conf=/Users/goalque/src/edk2/Conf -D USE_BIOS_BLOCKIO -D USE_LOW_EBDA -a X64 -b RELEASE -t XCODE8 -n 9 | OS: 10.13.6 | XCODE: 9.4.1] 0:100 0:000 SelfDevicePath=PciRoot(0x0)\Pci(0x1B,0x0)\Pci(0x0,0x0)\SasEx(0x01000000002538D0,0xDA7F04217074616C,0x0,NoTopology,0,0,0)\HD(1,GPT,695C9375-2F6A-48EF-A4D1-EB0C1E237C51,0x6,0x12C00) @79968E98
0:100 0:000 SelfDirPath = \EFI\Boot
0:730 0:629 Running on: '' with board ''
0:730 0:000 === [ GetCPUProperties ] ==================================
0:730 0:000 CPU Vendor = 756E6547 Model=506E3
0:730 0:000 The CPU supported SSE4.1
0:730 0:000 BrandString = Intel(R) Core(TM) i7-6920HQ CPU @ 2.90GHz
0:730 0:000 The CPU supported turbo
0:730 0:000 MSR 0x35 40008
0:730 0:000 TSC/CCC Information Leaf:
0:730 0:000 numerator : 242
0:730 0:000 denominator : 2
0:730 0:000 Calibrated ARTFrequency: 0
0:730 0:000 MSR 0xE2 before patch 60000008
0:730 0:000 MSR 0xCE 0008083B_F1011D00
0:730 0:000 corrected FLEX_RATIO = 1C0000
0:730 0:000 MSR 0x1B0 00000000
0:730 0:000 FSBFrequency = 0 MHz, DMI FSBFrequency = 0 MHz, Corrected FSBFrequency = 0 MHz
0:730 0:000 MaxDiv/MinDiv: 29.0/8
0:730 0:000 Turbo: 34/35/36/38
0:730 0:000 Features: 0xBFEBFBFF
0:730 0:000 Threads: 8
0:730 0:000 Cores: 4
0:730 0:000 FSB: 0 MHz
0:730 0:000 CPU: 0 MHz
0:730 0:000 TSC: 0 MHz
0:730 0:000 PIS: 0 MHz
0:730 0:000 ExternalClock: 0 MHz
0:730 0:000 === [ GetDevices ] ========================================
0:730 0:000 PCI (00|00:00.00) : 8086 1910 class=060000
0:730 0:000 PCI (00|00:01.00) : 8086 1901 class=060400
0:730 0:000 PCI (00|01:00.00) : 1002 67EF class=030000
0:730 0:000 - GFX: Model=AMD Radeon Pro 555 (ATI/AMD)
0:730 0:000 PCI (00|01:00.01) : 1002 AAE0 class=040300
0:730 0:000 - HDMI Audio:
0:730 0:000 PCI (00|00:02.00) : 8086 191B class=030000
0:730 0:000 - GFX: Model=Intel HD Graphics 530 (Intel)
0:730 0:000 PCI (00|00:14.00) : 8086 A12F class=0C0330
0:730 0:000 PCI (00|00:15.00) : 8086 A160 class=118000
0:730 0:000 PCI (00|00:16.00) : 8086 A13A class=078000
0:730 0:000 PCI (00|00:19.00) : 8086 A166 class=118000
0:730 0:000 PCI (00|00:1B.00) : 8086 A167 class=060400
0:730 0:000 PCI (00|02:00.00) : 144D A804 class=010802
0:730 0:000 PCI (00|00:1C.00) : 8086 A110 class=060400
0:730 0:000 PCI (00|03:00.00) : 14E4 43BA class=028000
0:730 0:000 - WIFI: Vendor=Broadcom
0:730 0:000 PCI (00|00:1E.00) : 8086 A127 class=118000
0:730 0:000 PCI (00|00:1E.01) : 8086 A128 class=118000
0:731 0:000 PCI (00|00:1E.02) : 8086 A129 class=118000
0:731 0:000 PCI (00|00:1E.03) : 8086 A12A class=118000
0:731 0:000 PCI (00|00:1F.00) : 8086 A151 class=060100
0:731 0:000 PCI (00|00:1F.02) : 8086 A121 class=058000
0:731 0:000 PCI (00|00:1F.03) : 8086 A170 class=040300
0:731 0:000 PCI (00|00:1F.04) : 8086 A123 class=0C0500
0:731 0:000 PCI (00|00:01.01) : 8086 1905 class=060400
0:731 0:000 PCI (00|04:00.00) : 8086 1578 class=060400
0:731 0:000 PCI (00|05:00.00) : 8086 15D3 class=060400
0:731 0:000 PCI (00|06:00.00) : 8086 15D2 class=088000
0:731 0:000 PCI (00|05:01.00) : 8086 15D3 class=060400
0:731 0:000 PCI (00|05:02.00) : 8086 15D3 class=060400
0:731 0:000 PCI (00|07:00.00) : 8086 15D4 class=0C0330
0:731 0:000 PCI (00|05:04.00) : 8086 15D3 class=060400
0:731 0:000 PCI (00|00:01.02) : 8086 1909 class=060400
0:731 0:000 PCI (00|7A:00.00) : 8086 1578 class=060400
0:731 0:000 PCI (00|7B:00.00) : 8086 15D3 class=060400
0:731 0:000 PCI (00|7C:00.00) : 8086 15D2 class=088000
0:731 0:000 PCI (00|7B:01.00) : 8086 15D3 class=060400
0:731 0:000 PCI (00|7B:02.00) : 8086 15D3 class=060400
0:731 0:000 PCI (00|7D:00.00) : 8086 15D4 class=0C0330
0:731 0:000 PCI (00|7B:04.00) : 8086 15D3 class=060400
0:731 0:000 === [ GetDefaultSettings ] ================================
0:731 0:000 Clover load options size = 60 bytes
0:737 0:006 EFI\CLOVER\config.plist loaded: Success
0:737 0:000 === [ GetListOfThemes ] ===================================
0:737 0:000 === [ Found config plists ] ===============================
0:737 0:000 - config.plist
0:737 0:000 === [ GetEarlyUserSettings ] ==============================
0:737 0:000 timeout set to 0
0:737 0:000 Custom boot CUSTOM_BOOT_DISABLED (0x0)
0:750 0:013 KextsToPatch: 3 requested
0:757 0:006 - [00]: IOGraphicsFamily (IOGraphicsFamily Patch (c) egpu.io [goalque])Data: 7A567F18, Len: 14 = Data: 7A567E98, Len: 14 = :: BinPatch :: data len: 14
0:797 0:039 - [01]: AppleGPUWrangler (AppleGPUWrangler Discrete Patch (c) egpu.io [goalque])Data: 7A567E98, Len: 14 = Data: 7A567F18, Len: 14 = :: BinPatch :: data len: 14
0:836 0:039 === [ LoadDrivers ] =======================================
1:112 0:276 === [ InitScreen ] ========================================
1:392 0:280 reinit: self device path=PciRoot(0x0)\Pci(0x1B,0x0)\Pci(0x0,0x0)\SasEx(0x01000000002538D0,0xDA7F04217074616C,0x0,NoTopology,0,0,0)\HD(1,GPT,695C9375-2F6A-48EF-A4D1-EB0C1E237C51,0x6,0x12C00)
1:399 0:006 === [ GetDefaultSettings ] ================================
1:633 0:234 === [ GetAcpiTablesList ] =================================
1:903 0:269 Get Acpi Tables List from RSDT:
1:921 0:018 - [00]: FACP Apple00 len=244
1:932 0:011 - [01]: UEFI EDK2 len=66
1:939 0:006 - [02]: ECDT Apple00 len=83
1:945 0:006 - [03]: HPET Apple00 len=56
1:952 0:006 - [04]: APIC Apple00 len=188
1:963 0:010 - [05]: MCFG Apple00 len=60
1:970 0:006 - [06]: SBST Apple00 len=48
1:976 0:006 - [07]: SSDT SmcDppt len=36
1:988 0:011 - [08]: SSDT PEG0GFX0 len=2045
1:994 0:006 - [09]: SSDT PEG0SSD0 len=36
2:006 0:011 - [10]: SSDT SsdtS3 len=49
2:012 0:006 - [11]: SSDT SataAhci len=221
2:019 0:006 - [12]: SSDT Sdxc len=184
2:025 0:006 - [13]: SSDT TbtPEG12 len=39278
2:032 0:006 - [14]: SSDT Xhci len=3122
2:040 0:008 - [15]: SSDT Cpu0Ist len=1554
2:051 0:011 - [16]: SSDT ApIst len=1450
2:058 0:006 - [17]: SSDT Cpu0Cst len=661
2:065 0:006 - [18]: SSDT ApCst len=281
2:071 0:006 - [19]: SSDT CpuSsdt len=3823
2:078 0:006 - [20]: DMAR SKL len=352
2:085 0:006 - [21]: VFCT Apple00 len=59524
2:092 0:007 === [ GetUserSettings ] ===================================
2:344 0:252 GetUserSettings done
2:355 0:011 GPU_INTERNAL
2:362 0:006 === [ ScanVolumes ] =======================================
2:640 0:277 Found 18 volumes with blockIO
2:647 0:006 - [00]: Volume: PciRoot(0x0)\Pci(0x1B,0x0)\Pci(0x0,0x0)\SasEx(0x01000000002538D0,0xDA7F04217074616C,0x0,NoTopology,0,0,0)
2:660 0:013 - [01]: Volume: PciRoot(0x0)\Pci(0x1B,0x0)\Pci(0x0,0x0)\SasEx(0x01000000002538D0,0xDA7F04217074616C,0x0,NoTopology,0,0,0)\HD(1,GPT,695C9375-2F6A-48EF-A4D1-EB0C1E237C51,0x6,0x12C00)
2:674 0:013 This is SelfVolume !!
2:680 0:006 - [02]: Volume: PciRoot(0x0)\Pci(0x1B,0x0)\Pci(0x0,0x0)\SasEx(0x01000000002538D0,0xDA7F04217074616C,0x0,NoTopology,0,0,0)\HD(2,GPT,DECE4BF9-279F-4BB1-AFD2-BCDCA8D4FE3B,0x12C06,0x5D991FA)
2:694 0:013 - [03]: Volume: PciRoot(0x0)\Pci(0x1B,0x0)\Pci(0x0,0x0)\SasEx(0x01000000002538D0,0xDA7F04217074616C,0x0,NoTopology,0,0,0)\HD(3,GPT,7AE09919-E55A-4380-A36B-C90D886929AC,0x5DABE00,0x1694400)
2:707 0:013 - [04]: Volume: PciRoot(0x0)\Pci(0x1B,0x0)\Pci(0x0,0x0)\SasEx(0x01000000002538D0,0xDA7F04217074616C,0x0,NoTopology,0,0,0)\HD(4,GPT,C2CDCB9C-8B0C-4CFF-B81F-439B897C523A,0x7440200,0x3AB00)
2:720 0:012 - [05]: Volume: PciRoot(0x0)\Pci(0x1B,0x0)\Pci(0x0,0x0)\SasEx(0x01000000002538D0,0xDA7F04217074616C,0x0,NoTopology,0,0,0)\HD(2,GPT,DECE4BF9-279F-4BB1-AFD2-BCDCA8D4FE3B,0x12C06,0x5D991FA)\VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,E8208FFCB1E5F241844A06777711CC58)
2:734 0:013 - [06]: Volume: PciRoot(0x0)\Pci(0x1B,0x0)\Pci(0x0,0x0)\SasEx(0x01000000002538D0,0xDA7F04217074616C,0x0,NoTopology,0,0,0)\HD(2,GPT,DECE4BF9-279F-4BB1-AFD2-BCDCA8D4FE3B,0x12C06,0x5D991FA)\VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,6A179C7CF5B1454ABBA3401785B67361)
2:748 0:013 - [07]: Volume: PciRoot(0x0)\Pci(0x1B,0x0)\Pci(0x0,0x0)\SasEx(0x01000000002538D0,0xDA7F04217074616C,0x0,NoTopology,0,0,0)\HD(2,GPT,DECE4BF9-279F-4BB1-AFD2-BCDCA8D4FE3B,0x12C06,0x5D991FA)\VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,AC67D34C67442348B69EA6CCB52399AF)
2:761 0:013 - [08]: Volume: PciRoot(0x0)\Pci(0x1B,0x0)\Pci(0x0,0x0)\SasEx(0x01000000002538D0,0xDA7F04217074616C,0x0,NoTopology,0,0,0)\HD(2,GPT,DECE4BF9-279F-4BB1-AFD2-BCDCA8D4FE3B,0x12C06,0x5D991FA)\VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,EB9C5CAB7025CB4A8B51631648EBF8BF)
2:775 0:013 - [09]: Volume: PciRoot(0x0)\Pci(0x1,0x1)\Pci(0x0,0x0)\Pci(0x2,0x0)\Pci(0x0,0x0)\USB(0x2,0x0)
2:794 0:019 USB volume
2:801 0:006 - [10]: Volume: PciRoot(0x0)\Pci(0x1,0x1)\Pci(0x0,0x0)\Pci(0x2,0x0)\Pci(0x0,0x0)\USB(0x2,0x0)\HD(1,GPT,7BB24A25-3C36-45AA-9979-13F402AC2172,0x28,0x64000)
2:820 0:019 Result of bootcode detection: bootable unknown (legacy)
2:827 0:006 USB volume
2:834 0:006 - [11]: Volume: PciRoot(0x0)\Pci(0x1,0x1)\Pci(0x0,0x0)\Pci(0x2,0x0)\Pci(0x0,0x0)\USB(0x2,0x0)\HD(2,GPT,64C7A74C-AAE6-458E-AF86-A62208E6001B,0x64028,0x3BA56360)
2:853 0:019 Result of bootcode detection: bootable unknown (legacy)
2:860 0:006 USB volume
2:867 0:006 - [12]: Volume: PciRoot(0x0)\Pci(0x1,0x1)\Pci(0x0,0x0)\Pci(0x2,0x0)\Pci(0x0,0x0)\USB(0x2,0x0)\HD(3,GPT,698C6B59-96D1-4816-89E1-309F7CACF537,0x3BABA388,0x40000)
2:886 0:019 USB volume
2:893 0:006 - [13]: Volume: PciRoot(0x0)\Pci(0x1,0x1)\Pci(0x0,0x0)\Pci(0x2,0x0)\Pci(0x0,0x0)\USB(0x2,0x0)\HD(4,GPT,5F48435A-5697-4C8F-878B-8112BE73E6D8,0x3BAFA388,0x20A7D3600)
2:914 0:021 Result of bootcode detection: bootable Windows (vista,win)
2:921 0:007 USB volume
2:928 0:006 - [14]: Volume: PciRoot(0x0)\Pci(0x1,0x1)\Pci(0x0,0x0)\Pci(0x2,0x0)\Pci(0x0,0x0)\USB(0x3,0x0)
2:950 0:022 USB volume
2:957 0:006 - [15]: Volume: PciRoot(0x0)\Pci(0x1,0x1)\Pci(0x0,0x0)\Pci(0x2,0x0)\Pci(0x0,0x0)\USB(0x3,0x0)\HD(1,GPT,F883C3EB-6A56-4877-8951-B54D463C3F1F,0x28,0x64000)
2:976 0:019 Result of bootcode detection: bootable unknown (legacy)
2:983 0:006 USB volume
2:990 0:006 - [16]: Volume: PciRoot(0x0)\Pci(0x1,0x1)\Pci(0x0,0x0)\Pci(0x2,0x0)\Pci(0x0,0x0)\USB(0x3,0x0)\HD(2,GPT,9A970313-0EFA-486A-9D44-35A326A65F4C,0x64800,0x1D1B67688)
3:009 0:019 Result of bootcode detection: bootable unknown (legacy)
3:016 0:006 USB volume
3:023 0:006 - [17]: Volume: PciRoot(0x0)\Pci(0x1,0x1)\Pci(0x0,0x0)\Pci(0x2,0x0)\Pci(0x0,0x0)\USB(0x3,0x0)\HD(3,GPT,D433796D-06A2-4E5D-A51E-AD7C82C05649,0x1D1BCBE88,0x40000)
3:044 0:021 USB volume
3:053 0:008 about to start LoadSelections
3:060 0:006 LoadSelections 1
3:067 0:006 fs index 0
3:073 0:006 USB file system found
3:080 0:006 LoadSelections 2
3:086 0:006 LoadSelections 3
3:093 0:006 LoadSelections 4
3:100 0:006 LoadSelections 5
3:106 0:006 LoadSelections 7
3:113 0:006 LoadSelections 8
3:120 0:006 LoadSelections 9

EDIT: apple_set_os.efi previously results in a temporary unbootable win10, I deleted it and the issue persists. And I only needs to run the eGPU in Bootcamp

EDIT2:  https://egpu.io/forums/pc-setup/need-help-with-a-strange-issue-with-my-bootcamped-nv-egpu/ this is my previous failed attempt at following the step-by-step guide, in case it's helpful for debugging the issue

RTX 2080Ti
2016 15' Macbook Pro with RP460
Akitio Node Pro


ReplyQuote
jya
 jya
(@jya)
Trusted Member
Joined: 2 years ago
 

FinAlly back home to test this solution.
Formatted a USB disk in FAT32, with GPT boot loader.
I then mounted the EFI partition and copied the EFI folder.

Rebooted while holding the option key. Selected the USB disk. That clears the screen and displays:
USB file system not found.

On this mac (macbook pro 15" 2018), on the SSD EFI I have refind installed. If I boot using refind instead and select the clover bootloader on the USB disk, then nothing happens.

Any ideas what I'm doing wrong?

Thanks in advance.
JY

Edit: I copied automate-eGPU.efi to the system's EFI/Boot partition and copied the clover folder across.
I then started automate-eGPU.efi from refind. It starts and show on the screen:
Starting-eGPU.efi
Using load options ''
apple_set_os started
Set os version to Mac OS X 10.9
Set os vendor to Apple Inc

And then it hangs there, making no more progress.

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


ReplyQuote
jya
 jya
(@jya)
Trusted Member
Joined: 2 years ago
 
Posted by: goalque

It would be more correct to say "activation of iGPU" because someone may misinterpret "deactivation of dGPU" as powering off. There is a set of commands to do that as well but in this case the gmux microcontroller just changes its state to iGPU prior to booting into macOS/Windows.

MuxSetting=0 (do nothing)
MuxSetting=1 (iGPU)
MuxSetting=2 (dGPU)

What would be required, to get only the effect of apple_set_os.efi and MuxSetting=1 (as all I'm trying to do is disable the dGPU and force the iGPU and not get a black screen once booted under Windows) ?

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


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

Hi:
I've tried using this instead of the traditional step-by-step guide.
I'm able to execute the automate-eGPU.efi in refined when eGPU is not plugged in, however it just stucks at ``Using Configuration ''``.

automate-eGPU.efi cannot be used with rEFInd or alone, it's designed to be used with the boot screen efi (bootx64.efi).

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
 
Posted by: jya

FinAlly back home to test this solution.
Formatted a USB disk in FAT32, with GPT boot loader.

Use Disk Utility in macOS. Try MS-DOS (FAT), Master Boot Record if GUID scheme doesn't work.

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


ReplyQuote
Acclaim
(@acclaim)
New Member
Joined: 2 years ago
 

I have copied the EFI folder to an external SSD (as well as an attempt with a USB flash drive) and am able to perform an EFI boot. Following the instructions, I have left the eGPU unplugged and thus it is not detected. When I select either "boot windows" or "boot mac" the line displays "Saving..." at the bottom and the system hangs from there. I must reboot in order to access either OS through the normal bootcamp methods.

Any thoughts?

Thanks in advance!

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


ReplyQuote
jya
 jya
(@jya)
Trusted Member
Joined: 2 years ago
 
Posted by: goalque
Posted by: jya

What would be required, to get only the effect of apple_set_os.efi and MuxSetting=1 (as all I'm trying to do is disable the dGPU and force the iGPU and not get a black screen once booted under Windows) ?

All you have to do is to edit config.plist's MuxSetting value. apple_set_os.efi is loaded automatically.

Thank you for your fast answer...

So while when booting the USB EFI (by holding the option key) only shows a blank screen with the message "USB File System not found", it turns out that the keyboard is active.
When pressing q it restarted into refind which is configured to start Windows by default. However once in Windows, the iGPU isn't appearing in the Device Manager which indicates to me that apple_set_os.efi hasn't been loaded.

I'm a bit at a loss now, I've re-read this entire thread twice now, tried various methods and work arounds (including the "official" steps) but I've made little progress 🙁

Edit: I'm running macOS 10.14.1 and Windows 10

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


ReplyQuote
nu_ninja
(@nu_ninja)
Estimable Member
Joined: 1 year ago
 

@goalque
So my egpu is now working on 10.14.1 with the EFI. I re-upgraded to see if mac_editor's method would do anything and before even trying that, it just worked. The only thing I can think of that would make a difference is, the first time I upgraded, I had booted with the EFI and left the egpu plugged in. Whereas this time I upgraded without any patches applied and the egpu disconnected.

Mid-2012 13" Macbook Pro (MacBookPro9,2) TB1 -> RX 460/560 (AKiTiO Node/Thunder2)
+ macOS 10.14+Win10
+ Linux Mint 19.1


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

What would be required, to get only the effect of apple_set_os.efi and MuxSetting=1 (as all I'm trying to do is disable the dGPU and force the iGPU and not get a black screen once booted under Windows) ?

All you have to do is to edit config.plist's MuxSetting value. apple_set_os.efi is loaded automatically.

Thank you for your fast answer...

So while when booting the USB EFI (by holding the option key) only shows a blank screen with the message "USB File System not found", it turns out that the keyboard is active.
When pressing q it restarted into refind which is configured to start Windows by default. However once in Windows, the iGPU isn't appearing in the Device Manager which indicates to me that apple_set_os.efi hasn't been loaded.

I'm a bit at a loss now, I've re-read this entire thread twice now, tried various methods and work arounds (including the "official" steps) but I've made little progress 🙁

We're posting at the same time 🙂 See my previous answer,
https://egpu.io/forums/mac-setup/automate-egpu-efi-egpu-boot-manager-for-macos-and-windows/paged/6/#post-46464

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
 
Posted by: nu_ninja

@goalque
So my egpu is now working on 10.14.1 with the EFI. I re-upgraded to see if mac_editor's method would do anything and before even trying that, it just worked. The only thing I can think of that would make a difference is, the first time I upgraded, I had booted with the EFI and left the egpu plugged in. Whereas this time I upgraded without any patches applied and the egpu disconnected.

If you are going to do any macOS/software updates, please always boot normally (no patches, eGPU disconnected).

And it is worth to mention again:

https://egpu.io/forums/mac-setup/automate-egpu-efi-egpu-boot-manager-for-macos-and-windows/paged/3/#post-45725

1) If you have to force power-off or a kernel panic occurs, please do one normal boot into macOS and login, shut down (without USB stick). Otherwise, the "EFI Boot" does not work on the next startup.

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


gcoban liked
ReplyQuote
mac_editor
(@mac_editor)
Noble Member Moderator
Joined: 2 years ago
 

For AMD eGPU users using EFI on TB1/2, the current 1.0.5 system does not allow for safe eGPU eject and uses the same NVIDIA patch which is not really needed.

First, check the thunderbolt version in Terminal, as not all Macs report correctly:

ioreg | grep NHIType

Outputs: AppleThunderboltNHIType2 = Thunderbolt 2, AppleThunderboltNHIType1 = Thunderbolt 1

Download the attachment for your particular thunderbolt version, rename it to config.plist if needed, and replace the config. file on your USB stick (save the old one just in case). I cannot test this but should enable AMD GPUs as though native on TB1/2 if I have adjusted the plist correctly. Would appreciate it if someone could test and let me know.

Honestly would be nicer if 1.0.5 had a little installer (could just be a line of Terminal for a script hosted on the forum).

purge-wrangler.shpurge-nvda.shset-eGPU.shautomate-eGPU EFI Installer
----
Troubleshooting eGPUs on macOS
Command Line Swiss Knife

Multiple Build Guides
----
Current: MacBook Pro RP560X + 480/R9 Fury/Vega 64 | GTX 780/1070
Previous: 2014 MacBook Pro 750M + 480/R9 Fury | GTX 780/980 Ti/1070


nu_ninja and goalque liked
ReplyQuote
nu_ninja
(@nu_ninja)
Estimable Member
Joined: 1 year ago
 

@mac_editor
Thanks so much, it's working for me!

Screen Shot 2018 11 02 at 8.37.33 PM

Mid-2012 13" Macbook Pro (MacBookPro9,2) TB1 -> RX 460/560 (AKiTiO Node/Thunder2)
+ macOS 10.14+Win10
+ Linux Mint 19.1


ReplyQuote
mac_editor
(@mac_editor)
Noble Member Moderator
Joined: 2 years ago
 

@nu_ninja Enjoy ;p and thanks for testing!

purge-wrangler.shpurge-nvda.shset-eGPU.shautomate-eGPU EFI Installer
----
Troubleshooting eGPUs on macOS
Command Line Swiss Knife

Multiple Build Guides
----
Current: MacBook Pro RP560X + 480/R9 Fury/Vega 64 | GTX 780/1070
Previous: 2014 MacBook Pro 750M + 480/R9 Fury | GTX 780/980 Ti/1070


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

For AMD eGPU users using EFI on TB1/2, the current 1.0.5 system does not allow for safe eGPU eject and uses the same NVIDIA patch which is not really needed.

Honestly would be nicer if 1.0.5 had a little installer (could just be a line of Terminal for a script hosted on the forum).

Thanks @mac_editor.

Yeah, an installer would be nice but the static config.plist pushes people to think what really happens under the hood. We need more like you 🙂

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


ReplyQuote
jya
 jya
(@jya)
Trusted Member
Joined: 2 years ago
 
Posted by: goalque
Posted by: jya

FinAlly back home to test this solution.
Formatted a USB disk in FAT32, with GPT boot loader.

Use Disk Utility in macOS. Try MS-DOS (FAT), Master Boot Record if GUID scheme doesn't work.

Hi.
OK, I had assumed being an EFI folder that it had to be placed in the EFI partition, but apparently not.
I formatted the stick to fat32 in Windows, copied the EFI folder across and rebooted. This time pressing option showed two USB boot option, both with the same name entry.
This time I did see screens showing that no eGPU and when validating I had the screen to decide which OS to boot: windows or macos.
I selected windows, at the bottom of the screen "saving" was displayed and then it stopped there. No more progress, no boot. Keyboard was no longer active,
So after a few minutes I did a hard reboot, it immediately rebooted under windows, showed the windows boot spinner and stayed there. This is similar to what I had experienced in the past playing with just the apple_set_os.efi and disabling the amd dGPU in the device manager:
The boot spinner keeps spinning, I can see that the keyboard is active (capslock make the left goes on). It's like windows has booted but is stuck on the boot screen.

So I don't know if the activate egpu efi is working, or if it is but really you can't go with just the iGPU on the 2018 MBP

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


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

@jya You still did something wrong. Stuck at ”saving...” means that the EFI app is unable to save the setting file to the USB stick.

You said: ”on the SSD EFI I have refind installed” -> why? You cannot use rEFInd. And please don’t use SSD, a normal USB stick works better.

I also said that use Disk Utility for formatting but you didn’t.

Confirm that your USB drive is NOT named ”EFI”.

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


ReplyQuote
jya
 jya
(@jya)
Trusted Member
Joined: 2 years ago
 
Posted by: goalque

@jya You still did something wrong. The text ”saving...” means that the EFI app is unable to save the setting file to the USB stick.

You said: ”on the SSD EFI I have refind installed” -> why? You cannot use rEFInd. And please don’t use SSD, a normal USB stick works better.

I also said that use Disk Utility for formatting but you didn’t.

Confirm that your USB drive is NOT named ”EFI”.

Ok. This time I used Disk Utility to format the USB stick, copied the EFI folder across. I set MuxSetting to 1. Rebooted while holding the Option key. Booted the USB, set to boot the mac. It rebooted right after, all good.
I can see that when setting MuxSetting to 2, after a reboot the internal display is running off the Radeon 560X. So that seems to have an effect.

Unfortunately, when booting under Windows with MuxSetting == 1, I either get the Windows boot spinner, or that weird flashing white pattern on the screen. Windows is definitely up and running, the capslock key works. When I plug a USB device I hear the windows chime etc... Just nothing visible.

When booting under macOS with MuxSetting == 1, and I plug an external screen, both the internal display and external display are running off the Radeon 560X, is this the expected behaviour?

From time to time, attempting to access automate-egpu.efi just locks up. I found that the workaround for this is to remove the USB stick, restart press the option key, select macOS and then go into System Preferences -> Startup Disk and re-select Macintosh HD.

So so far, it hasn't worked much better than with the egpu-switch windows utility + apple_set_os.efi , I get exactly the same behaviour (either spinner or flashing white screen when booting). But it's much easier to recover, having the ability to simply boot the USB stick and reset things is a massive progress.

Now if only I could make that damn iGPU work under Windows 🙁

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


ReplyQuote
Eightarmedpet
(@eightarmedpet)
Noble Member
Joined: 2 years ago
 

I HAVE GOT PAST ERROR 12! With my LG 5K display working too... Finally! I think it's down to this Bootmanager... will write up fully asap, testing on my 570 before ordering a Vega.

Tagging @itsage because i've bored him with my struggle over the year or so I have been posting here.

Worth noting - I havent had to disable any Thunderbolt ports.

Edit: Vega 56 bought.

2017 13" MacBook Pro Touch Bar
GTX1060 + AKiTiO Thunder3 + Win10
GTX1070 + Sonnet Breakaway Box + Win10
GTX1070 + Razer Core V1 + Win10
Vega 56 + Razer Core V1 + macOS + Win10
Vega 56 + Mantiz Venus + macOS + W10

---

LG 5K Ultrafine flickering issue fix


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

@jya Good, some progress. It works 100% if you do things correctly. Have you disabled all EFI security settings? rEFInd completely uninstalled? Latest BootCamp drivers installed? Latest Intel drivers installed? You shouldn't try MuxSetting=2 with apple_set_os.efi, use always MuxSetting=1 value.

And why MS-DOS (FAT)?

https://apple.stackexchange.com/questions/19658/what-format-for-my-external-drive-allows-use-with-mac-and-windows

FAT32 (called MS-DOS (FAT) by Disk Utility; a filesystem originally released in 1977 and updated a few times since, lastly in 1996) really is the only cross platform filesystem that is going to work fully out of the box with Windows and Mac OS X.

Be careful though, if you are using Disk Utility to format the drive, you should make sure to choose the Master Boot Record partitioning scheme (hit the "Options..." button below the "Partition Layout" control on the Partition pane).

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
 
Posted by: jya

When booting under macOS with MuxSetting == 1, and I plug an external screen, both the internal display and external display are running off the Radeon 560X, is this the expected behaviour?

How did you conclude that?

"Set an external eGPU-connected display as the primary display"
https://support.apple.com/en-us/HT208544

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


ReplyQuote
jya
 jya
(@jya)
Trusted Member
Joined: 2 years ago
 
Posted by: goalque

@jya Good, some progress. It works 100% if you do things correctly. Have you disabled all EFI security settings? rEFInd completely uninstalled? Latest BootCamp drivers installed? Latest Intel drivers installed? You shouldn't try MuxSetting=2 with apple_set_os.efi, use always MuxSetting=1 value.

And why MS-DOS (FAT)?

https://apple.stackexchange.com/questions/19658/what-format-for-my-external-drive-allows-use-with-mac-and-windows

FAT32 (called MS-DOS (FAT) by Disk Utility; a filesystem originally released in 1977 and updated a few times since, lastly in 1996) really is the only cross platform filesystem that is going to work fully out of the box with Windows and Mac OS X.

Be careful though, if you are using Disk Utility to format the drive, you should make sure to choose the Master Boot Record partitioning scheme (hit the "Options..." button below the "Partition Layout" control on the Partition pane).

I used the default settings for the USB stick when formatting for FAT, which is GPT. (I know what FAT is , being old enough 🙂 ) I can of course set it to use MBR instead. But it appears to work as is. My original error was to believe that the EFI folder had to be installed on the EFI partition. I didn't know that the EFI folder could be placed on the main partition and that it would still work.

I have the latest bootcamp drivers installed, the latest intel (from Intel website). I have uninstalled all the AMD drivers using the DDFU utility.
I've uninstalled all the custom EFI from the SSD's EFI partition (that is ubuntu, refind etc). I can access your automate-egpu.efi screen just fine, select either macOS, Windows or Reset. So it all seems okay now. I'm not sure reformating the USB stick to use MBR would make a difference, but at this stage, I no longer care 🙂

After a few boot, I did get the mac to boot under windows. Both the intel and AMD were showing in the device manager (AMD is showing as the Microsoft Basic adapter). However, as usual, as the Intel is showing there all working and active: no errors.

Capture

When you go into the settings display, you see that it's the Microsoft Basic Display Adapter:

Capture2

resolution of the screen is ultra-weird too: 3360x2100 nothing to do with reality.

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


goalque liked
ReplyQuote
jya
 jya
(@jya)
Trusted Member
Joined: 2 years ago
 
Posted by: goalque
Posted by: jya

When booting under macOS with MuxSetting == 1, and I plug an external screen, both the internal display and external display are running off the Radeon 560X, is this the expected behaviour?

How did you conclude that?

"Set an external eGPU-connected display as the primary display"
https://support.apple.com/en-us/HT208544

I'm not using an eGPU (I'm still trying to get the iGPU to be used as primary display adapter). For the work I do, using the Intel UHD 630 or a nvidia 10xx eGPU would achieve the same goal (have access to the 10 bits HW video decoders that the AMD lacks)

I can tell the dGPU is being usedm because under the System Information utility -> Graphic/Displays , both the internal display and the external display (an Apple TB display) are showing under the Radeon Pro 560X.

I had hoped that while the internal screen stays black when I set MuxSetting to 1 under Windows would work with the external screen. Or if I booted under macOS it would use the iGPU for both the internal display and the external display (again, no eGPU).. However that doesn't appear to be the case: external screen -> dGPU always active by default.

I had hoped that the Vega 16 and vega 20 found in the upcoming MBP 15" would have 10 bits HW decoder, however after contacting people I know at AMD, they are identical to the AMD Vega 56/64 found in the iMac Pro, just better power savings. So no 10 bits VP9

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


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

When booting under macOS with MuxSetting == 1, and I plug an external screen, both the internal display and external display are running off the Radeon 560X, is this the expected behaviour?

How did you conclude that?

"Set an external eGPU-connected display as the primary display"
https://support.apple.com/en-us/HT208544

I'm not using an eGPU (I'm still trying to get the iGPU to be used as primary display adapter). For the work I do, using the Intel UHD 630 or a nvidia 10xx eGPU would achieve the same goal (have access to the 10 bits HW video decoders that the AMD lacks)

I can tell the dGPU is being usedm because under the System Information utility -> Graphic/Displays , both the internal display and the external display (an Apple TB display) are showing under the Radeon Pro 560X.

The internal ports of the MBP are hardwired to dGPU (RP 560X) - the gmux has no other choice than dGPU in this situation when an external monitor is connected.

If you are going to use eGPU + apple_set_os.efi + MuxSetting=1, disconnect all displays from the internal ports of the MBP.

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


ReplyQuote
 of  21