[Solved] automate-eGPU EFI - eGPU boot manager for macOS and Windows
Hi Tony, may I ask you a few follow up questions please:
1. What's the version of your Nvidia web driver? (for e.g. 318.104.22.168.40.113)
2. Which version of automate-efi are you using (1.0.4 or 1.0.5)?
3. Did you load into a separate USB (Fat32) disk for EFI booting or use internal Hdd efi partition?
Sorry for the barrage of questions, I still can't bypass the gpu detection error unfortunately - not sure whether it's because of the web driver not supporting pascal architecture GPUs.
Thanks in advance!
@goalque Thank you very much for the tool! It works for me, but not always... Sometimes I could boot into Win with both GPU working, sometimes the eGPU just didn't show up. I have two questions:
1. Currently I'm using Mac mini 2018 and Core X with Vega 65. On the screen of EFI bootloader, it always says eGPU is not connected. When I was using RX580 and GTX1070 Gaming box, it always says eGPU connected, and they were working trouble free in Win 10. May I ask why the bootloader cannot detect my eGPU?
2. when using your command to check the cleanness of my mac kexts, it shows I have modified kext. Maybe this is because I tried to make GTX1070 work in OS X, but I really don't recall I changed any kexts. Could you please tell me how to clean my system
Thank you so much!
I think the second question is because I used pruge wrangler command. I will try to recover from it by using
I am also confused about this and I didn't find the answer from goalque. Do you know if I should do the step 3,4 every time or just the first time?Thanks!
The questions have been answered:
I have no specific answers for everything, I don't know
Using my 15-inch MPB 2018 with Radeon 560X dGPU, I always had to switch off the dGPU with "pmset -a gpuswitch 0" when plugging an nVidia eGPU. If it was not done, the internal screen would go black and the system would go slow very soon.
This is a huge relief, as the switching on/off is really annoying and can have several bad effects.
Is there some explanation for this? Are the nVidia web drivers just better for the GTX1050 than for the GTX1080Ti? What about other nVidia cards?
Almost working? but getting kernel panic.
I've got a mid 2014 13" macbook pro (based in the keyboard I think it is the UK version) intel iris 1536 built in graphics
Mac OS version 10.13.6 ( 17G65 )
I used the Benjamin-Dobell script to install nVidia drivers
it claims to have installed version 322.214.171.124.40.105
I used mac_editor's automate-eGPU-EFI-install.txt script to create a thumb drive with goalque's automate-eGPU EFI 1.0.5. Thumb drive seems to work. It gives me an EFI menu if I hold down option, etc
I am currently doing this:
shutdown and restart without EFI thumb drive twice
insert thumb drive and boot with EFI
hotplug akitio node
I can hear the akitio node fan spin up and the 1080Ti fans and lights come on.
The HDMI display plugged into the 1080Ti stays black.
But then... The mouse pointer keeps moving for a bit but mouse clicks stop working. Sometimes the mouse will freeze 20-30 sec or so after hotplug the laptop screen goes black and I get the "your computer restarted because of a problem" death screen.
after a reboot, the crash report says:
panic ... NVRM ... Read Error
Kernel Extensions in backtrace:
BSD process name corresponding to current thread: kernel_task
On my very first attempt to get things running, ( now many tries ago and details hazy) system report showed the atiko node under the thunderbolt tab and showed the nvidia card under the graphics/displays tab, I thought I was home-free, but after a minute or two, the system froze, screen went blank and the system rebooted (similar signature to what I am seeing now I think.)
In the current pattern of behavior, the system becomes non responsive to mouse events before I can navigate through system report.
It seems like it Nvidia drivers are related to the panic, so it seems like the mac is talking to the node and the driver is getting loaded.
Any hints, thoughts, or suggestions of things to try next?
Would anyone know how to change operating system names in bootloader? After installing Automate-GPU 1.0.4 it incorrectly replaced my bootcamp grey icons. My windows icon completely disappeared and created 2 blue diamond shaped icons of which both logged into Mac OSX but one was incorrectly named as "Windows"
Another question was if Gatekeeper and partial SIP can be enabled or must be disabled always?
I have installed Windows 10 on a USB SSD drive. When trying to load windows through this EFI loader, the system freezes after selecting Windows. Any ideas?
Also, how can I get rid of black screen when booting to windows with eGPU? Does this loader help in this case?
Will this work with windows 10 iso on an external drive? I have windows 10 on my external drive and I just added the eGPU- efi to an MS DOS (FAT) partition on the same hard drive I boot up and get black screen. I’m currently on a 2017 MBP nTB, with a core x and amd RX Vega 64
As said earlier in this thread, I don't know if external Win10 installations work. Probably not. I don't have time to debug, unfortunately. I've tested only the internal disk, Win10 installed through the Boot Camp Assistant. Turn on the Clover debug flag to identify where the boot process is failing. The app looks for the hidden volume "EFI" (disk0s1 identifier) and tries to use Windows startup efi file from there, and if doesn't exist, you cannot boot into Windows. Be sure that your USB stick isn't labeled as "EFI".