Always on 10.14.1? Are you sure? Also when you used reFiND 0.11.3's built-in spoof_osx feature?
About the security content of macOS Mojave 10.14.1
https://support.apple.com/en-us/HT209193
"EFI
Available for: macOS High Sierra 10.13.6, macOS Mojave 10.14
Impact: A local user may be able to modify protected parts of the file system
Description: A configuration issue was addressed with additional restrictions.
CVE-2018-4342: Timothy Perfitt of Twocanoes Software"
@goalque I am running macOS 10.14.2 Beta 1. I can confirm that I can indeed switch the mux to the iGPU (MuxSetting=1) and boot with the internal display working as long as:
- RP560X is disabled
- Intel Drivers are not installed
To confirm, I uninstalled the 560X device from Windows and the display was working fine (indicator that it was indeed muxed to iGPU). Installing the driver results in a black screen, though in one case I did get iGPU acceleration as well, but then the installer told me to restart and I did and back to square one. Here, maybe what I could have done after driver installation was disable the iGPU, reboot to a basic adapter, and re-enable - might have an iGPU display every boot if I did this each time maybe. Might have had an iGPU accelerated display then. Some more testing might yield something positive on 2018 MBP-end.
I also used the set_os compiled by 0xbb (replaced on the EFI stick) but I don't think that made a difference here (it was the Intel drivers). Safe to say that the EFI stick seems to be doing what it's supposed to really. In my case, its only the 2018 MBP differences causing issues.
Another note: Booting with the eGPU plugged in + EFI stick with set_os, my eGPU does not work at all. Hot-plugging does work (just that it results in Error 12 but might work for NVIDIA eGPU).
@mac_editor Did you use gpu-switch integrated.bat to attach iGPU to internal display? When I tested the 2018 15" MBP back in August, this forced attachment would result circle dots then black screen. Removing all graphics drivers allows the internal display to work but there's no acceleration. Windows simply drives the internal display with basic drivers.
@itsage Yes, I was only able to accomplish that (working internal display, no acceleration, but on iGPU), sans integrated.bat. MuxSetting=1 was sufficient. I saw your suggestion over at the Vega build I posted yesterday. I can get the internal display to turn on if the dGPU is disabled and I boot with the Vega plugged in, as with an NVIDIA GPU. Hot-plugging always results in Code 12 - I disabled the right-side ports and wifi controller. Have not tried left-side ports/plugging in to right-side ports.
Mostly what I'm looking at next is undervolting Vega in macOS. It already works well generally but in benches I can sometimes see those "peak currents" affecting performance (sudden FPS drop). Someone on the insanelymac forum has posted how to do this by modifying the AMD10000Controller, and there's a lot of base64 to deal with so looking into it for now. Perhaps a codeless kext and some data patterns may allow generating the soft power table data with custom settings easier.
Always on 10.14.1? Are you sure? Also when you used reFiND 0.11.3's built-in spoof_osx feature?
About the security content of macOS Mojave 10.14.1
https://support.apple.com/en-us/HT209193
"EFI
Available for: macOS High Sierra 10.13.6, macOS Mojave 10.14
Impact: A local user may be able to modify protected parts of the file system
Description: A configuration issue was addressed with additional restrictions.
CVE-2018-4342: Timothy Perfitt of Twocanoes Software"
Always on 10.14, I always upgrade to the lastest released macOS version. Can't say it's 10.14.1, but definitely some version of Mojave
EDIT: Come to think about it, I did a few reformat and reinstall macOS during these days, and the reinstall was using Mojave downloaded from the internet. So if the recovery is picking the latest version, I might have upgraded from 10.14 to 10.14.1, but overall I've always been on Mojave since the day I receive the card
RTX 2080Ti
2016 15' Macbook Pro with RP460
Akitio Node Pro
@mac_editor
IIUTC, you managed to achieve what I'm trying to do on a AMD card?
Basically your steps on a vanilla Win10 is that:
mux=1 (which I think keeps Intel iGPU alive in Windows)&& disable dGPU.
May I ask how exactly you disable the dGPU and keep iGPU alive? I've been trying that in my previous attempt but as long as I plug-in the eGPU, the system either freeze/went black/restart
And is there any method I can keep WiFi and the four ports alive? I don't quite understand the DSDT method, also didn't find a exactly match precompiled DSDT. IIUTC that method also has the danger of bricking my Mac?
RTX 2080Ti
2016 15' Macbook Pro with RP460
Akitio Node Pro
Always on 10.14.1? Are you sure? Also when you used reFiND 0.11.3's built-in spoof_osx feature?
About the security content of macOS Mojave 10.14.1
https://support.apple.com/en-us/HT209193
"EFI
Available for: macOS High Sierra 10.13.6, macOS Mojave 10.14
Impact: A local user may be able to modify protected parts of the file system
Description: A configuration issue was addressed with additional restrictions.
CVE-2018-4342: Timothy Perfitt of Twocanoes Software"Always on 10.14, I always upgrade to the lastest released macOS version. Can't say it's 10.14.1, but definitely some version of Mojave
EDIT: Come to think about it, I did a few reformat and reinstall macOS during these days, and the reinstall was using Mojave downloaded from the internet. So if the recovery is picking the latest version, I might have upgraded from 10.14 to 10.14.1, but overall I've always been on Mojave since the day I receive the card
You already said running 10.14.1 earlier. It doesn't matter if you were on Mojave - that wasn't my question. It matters if you made a firmware update after you tried rEFInd 0.11.3's built-in spoof_osx and you said "no firmware updates".
I was suspecting that a firmware update was the cause for iGPU invisibility on Windows. 10.14.1 brings a security firmware update.
@itsage Yes, I was only able to accomplish that (working internal display, no acceleration, but on iGPU), sans integrated.bat. MuxSetting=1 was sufficient. I saw your suggestion over at the Vega build I posted yesterday. I can get the internal display to turn on if the dGPU is disabled and I boot with the Vega plugged in, as with an NVIDIA GPU. Hot-plugging always results in Code 12 - I disabled the right-side ports and wifi controller. Have not tried left-side ports/plugging in to right-side ports.
Mostly what I'm looking at next is undervolting Vega in macOS. It already works well generally but in benches I can sometimes see those "peak currents" affecting performance (sudden FPS drop). Someone on the insanelymac forum has posted how to do this by modifying the AMD10000Controller, and there's a lot of base64 to deal with so looking into it for now. Perhaps a codeless kext and some data patterns may allow generating the soft power table data with custom settings easier.
What makr you think you're on the iGPU? From what I've seen it's always the Microsoft Basic Display even with the Intel active appearing as working in the device manager.
AFAICT, its using the 560X, is if you disable that device, now you get a black screen.
You can disable or uninstall the Intel drivers and you get the exact same outcome : if booted with apple_set_os and the Intel is now seen, regardless of active or not, the amd is no longer fully functional, the display adapter is Microsoft Basic one, but display still goes through the AMD
Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts
@goalque: I had similar outcome with the MBP 15" 2018 while it was running 10.14, prior the EFI update.
Would be unfortunate if Apple decided to cripple the earlier models just the same
Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts
Always on 10.14.1? Are you sure? Also when you used reFiND 0.11.3's built-in spoof_osx feature?
About the security content of macOS Mojave 10.14.1
https://support.apple.com/en-us/HT209193
"EFI
Available for: macOS High Sierra 10.13.6, macOS Mojave 10.14
Impact: A local user may be able to modify protected parts of the file system
Description: A configuration issue was addressed with additional restrictions.
CVE-2018-4342: Timothy Perfitt of Twocanoes Software"Always on 10.14, I always upgrade to the lastest released macOS version. Can't say it's 10.14.1, but definitely some version of Mojave
EDIT: Come to think about it, I did a few reformat and reinstall macOS during these days, and the reinstall was using Mojave downloaded from the internet. So if the recovery is picking the latest version, I might have upgraded from 10.14 to 10.14.1, but overall I've always been on Mojave since the day I receive the card
You already said running 10.14.1 earlier. It doesn't matter if you were on Mojave - that wasn't my question. It matters if you made a firmware update after you tried rEFInd 0.11.3's built-in spoof_osx and you said "no firmware updates".
I was suspecting that a firmware update was the cause for iGPU invisibility on Windows. 10.14.1 brings a security firmware update.
I understand, I misunderstand the mechanics that I thought firmware updates are part of the OS update.
I havn't manually updated my firmware, as you can see I don't even know how to. The only steps I've done during this period is multiple complete disk wipe and restore from internet.
EDIT: And restore from TM backups
RTX 2080Ti
2016 15' Macbook Pro with RP460
Akitio Node Pro
Firmware updates are part of the OS update. It's still unclear if you made macOS updgrade (from 10.14 to 10.14.1) between [rEFInd 0.11.3's built-in spoof_osx] and [automate-eGPU-EFI apple_set_os.efi].
Firmware updates are part of the OS update. It's still unclear if you made macOS updgrade (from 10.14 to 10.14.1) between [rEFInd 0.11.3's built-in spoof_osx] and [automate-eGPU-EFI apple_set_os.efi].
All I did was multiple recovery from internet. I guess the internet recovery forced an EFI update during the process.
I noticed you mentioned that those are permanent. Does that mean I should just return my card ? : (
RTX 2080Ti
2016 15' Macbook Pro with RP460
Akitio Node Pro
Internet recovery downloads the newest firmware. Security reasons is a good explanation.
Internet recovery downloads the newest firmware. Security reasons is a good explanation.
Does that mean I’ll never ever able to Bootcamp a NVIDIA eGPU on this Mac unless Apple decided to get their shit straight?
RTX 2080Ti
2016 15' Macbook Pro with RP460
Akitio Node Pro
You have community support, we do our best but cannot promise anything. Only Apple can provide official Boot Camp support.
You have community support, we do our best but cannot promise anything. Only Apple can provide official Boot Camp support.
Thanks. But from my understanding here, since you mentioned Apple’s new EFI’s “Security Features” disabled EFI program’s access to the underlying firmware, there is nothing us can do?
RTX 2080Ti
2016 15' Macbook Pro with RP460
Akitio Node Pro
It still works great on macOS, right? Thus far, we are only speculating if this is due to Apple's EFI security updates or something else. However, doesn't look promising.
It still works great on macOS, right? Thus far, we are only speculating if this is due to Apple's EFI security updates or something else. However, doesn't look promising.
Not exactly. 2080Ti doesn’t have macOS drivers : ( So pretty much useless. Should we stick a thread or something to warn fellow users not to upgrade?
RTX 2080Ti
2016 15' Macbook Pro with RP460
Akitio Node Pro
I meant the patching mechanism generally in macOS. GTX 780 might work, Apple provides built-in Nvidia Kepler drivers (but not IOPCITunnelCompatible) on Mojave. Anyway, I am not in a hurry to update 😀
I meant the patching mechanism generally in macOS. GTX 780 might work, Apple provides built-in Nvidia Kepler drivers (but not IOPCITunnelCompatible) on Mojave. Anyway, I am not in a hurry to update 😀
Good thing I read this thread, I was about to update 😛
Yeah but GTX 780 is IMHO way too old to consider. I will probably stop buying Macs after this. At this point I honestly feel like this is a commercial act disguised as a "Security Update"
RTX 2080Ti
2016 15' Macbook Pro with RP460
Akitio Node Pro
AFAICT, its using the 560X, is if you disable that device, now you get a black screen.
You can disable or uninstall the Intel drivers and you get the exact same outcome : if booted with apple_set_os and the Intel is now seen, regardless of active or not, the amd is no longer fully functional, the display adapter is Microsoft Basic one, but display still goes through the AMD
I believe I answered this in the post prior to the one you quoted.
@mac_editor
IIUTC, you managed to achieve what I'm trying to do on a AMD card?
Basically your steps on a vanilla Win10 is that:
mux=1 (which I think keeps Intel iGPU alive in Windows)&& disable dGPU.May I ask how exactly you disable the dGPU and keep iGPU alive? I've been trying that in my previous attempt but as long as I plug-in the eGPU, the system either freeze/went black/restart
And is there any method I can keep WiFi and the four ports alive? I don't quite understand the DSDT method, also didn't find a exactly match precompiled DSDT. IIUTC that method also has the danger of bricking my Mac?
I am on a 2018 MBP and I was aiming to address a different issue: whether muxing is functioning as expected or not. I got the display working on a basic adapter - which was the Intel at the time and the RP560X disabled/uninstalled.
I updated my 2016 15" MacBook Pro to 10.14.2 beta. The new Boot ROM is 250.0.0.0.0. Nothing changed regarding eGPU Boot Camp and @goalque's EFI Boot Manager. The PCI Express x16 Controller - 1901 to Radeon Pro 450 dGPU has been disabled for a while now and I can still switch back and forth between Windows and macOS. It works well with only the Intel HD Graphics 530 iGPU driving the internal display.
Brightness adjustment is the only thing not working in this configuration. My boot process involves eGPU EFI Boot Manager installed on a 512MB FAT partition on the internal drive. I had apple_set_os-efi and precompiled DSDT.aml in this boot loader to activate the iGPU as well as Large Memory. MuxSetting is set to 1.
I typically have the eGPU connected prior to boot. However there are firmware compatibility issues between Intel 6th gen i7-H CPUs and RTX GPUs. So I wait until Windows fully loads to hot-plug the RTX 2070 eGPU. Nvidia cards can work via hot-plug and hot-unplug does not cause BSOD. Hot-plugging AMD cards results in error 12 so either restart or have them connected at boot.
 |
 |
Here are some screen captures of AIDA and HWiNFO and Unigine benchmarks through the internal display.
 |
 |
 |
 |
 |
@goalque it would be easier for interested users to spot if you could link to the installer as an alternative approach on the main page:
I noticed T2 chip Macs have iBridge version next to Boot ROM version now.
I updated my 2016 15" MacBook Pro to 10.14.2 beta. The new Boot ROM is 250.0.0.0.0. Nothing changed regarding eGPU Boot Camp and @goalque's EFI Boot Manager. The PCI Express x16 Controller - 1901 to Radeon Pro 450 dGPU has been disabled for a while now and I can still switch back and forth between Windows and macOS. It works well with only the Intel HD Graphics 530 iGPU driving the internal display.
Brightness adjustment is the only thing not working in this configuration. My boot process involves eGPU EFI Boot Manager installed on a 512MB FAT partition on the internal drive. I had apple_set_os-efi and precompiled DSDT.aml in this boot loader to activate the iGPU as well as Large Memory. MuxSetting is set to 1.
I typically have the eGPU connected prior to boot. However there are firmware compatibility issues between Intel 6th gen i7-H CPUs and RTX GPUs. So I wait until Windows fully loads to hot-plug the RTX 2070 eGPU. Nvidia cards can work via hot-plug and hot-unplug does not cause BSOD. Hot-plugging AMD cards results in error 12 so either restart or have them connected at boot.
Here are some screen captures of AIDA and HWiNFO and Unigine benchmarks through the internal display.
Mind shareing your setup guide for this? Since I can't find the DSDT for RP460
RTX 2080Ti
2016 15' Macbook Pro with RP460
Akitio Node Pro
I think your setup issue is with trying too many different things at once. I'd recommend reading through my eGPU Boot Camp guide. Follow those steps and you'll have a working eGPU in Windows. It will also get you more familiar with the laptop and the way it interacts with the eGPU. The only difference is RTX card. Don't plug it in prior to boot. Hot-plug once Windows fully loads in step 4.
If you're interested in doing DSDT Override, take a look at @nando4's fix error 12 guide. It would be helpful to have the 2016 15" MacBook Pro RP460 in the Repository too.
I think your setup issue is with trying too many different things at once. I'd recommend reading through my eGPU Boot Camp guide. Follow those steps and you'll have a working eGPU in Windows. It will also get you more familiar with the laptop and the way it interacts with the eGPU. The only difference is RTX card. Don't plug it in prior to boot. Hot-plug once Windows fully loads in step 4.
If you're interested in doing DSDT Override, take a look at @nando4's fix error 12 guide. It would be helpful to have the 2016 15" MacBook Pro RP460 in the Repository too.
That was actually the first doc I tried, however it was very confusing in certain regards and I never got that to fully work. The closest to success I had was 3DMark detecting the eGPU. However the performance looks like its still using dGPU and after a reboot it's gone again. In fact my first post was using this guide. During that setup I had WiFi issues and random crashes and whatnot.
For example, this part
The 15″ MacBook Pro is rather challenging to allocate resources for the external graphics card. By disabling the x16 PCIe controller – 1901 to the discrete Radeon Pro GPU, we found Windows likely has enough resources for an external GPU. For us this method has worked with GTX 980 Ti, GTX 1070, and GTX 1080 eGPU. From eGPU.io members’ experience, Windows has a harder time with AMD cards. When we tried the RX 580 and RX Vega 56 eGPU, we needed to also disable the PCI Express x8 Controller – 1905 that connects to the left Thunderbolt 3 ports. External GPU works reliably using the right-side ports that connect to the PCI Express x4 Controller – 1909
Suggests I should disable 1901 , and 1905 only if I'm using AMD eGPU.
However slightly below this, it says
Nvidia eGPU can work without error 12 when the PCIe Controller x8 -1905 is disabled. AMD eGPU needs the PCIe Controller x16 – 1901 disabled as well to free up enough resources. Select View » Devices by connection in Device Manager and locate PCIe Controller x16 – 1901 to disable it.
Which suggests I should disable 1905 when using NVIDIA eGPU and 1901 if AMD. Which is completely opposite to the above statement
Slightly below this, I read
- Connect the external GPU to designated Thunderbolt 3 port and power MacBook Pro on
- Cold boot shows rEFInd boot menu (hold OPTION at boot if apple_set_os.efi is on USB drive)
- Press ENTER on apple_set_os.efi boot item – MacBook Pro’s display flashes briefly to confirm selection
- Press ARROW key to Windows 10 volume then press ENTER to boot
Which means I should cold boot with eGPU plugged in, that gave me blackscreen, now I know it's RTX issues. But at that time I had absolutely no idea and thought my setup was wrong. I formatted the whole system many times and still had no luck, then I went here and decided to try out the automated solution, yet still no luck.
RTX 2080Ti
2016 15' Macbook Pro with RP460
Akitio Node Pro
@navillezhang I don't think the statements are opposite at all. I believe @itsage is pointing out that NVIDIA eGPU can work either by disabling 1901 or just 1905. For AMD, 1901 is needed, plus more (1901 frees more resources vs. 1905, latter sufficient for NVIDIA, not AMD). I believe he may have the best answer, but that was my inference.
@navillezhang I don't think the statements are opposite at all. I believe @itsage is pointing out that NVIDIA eGPU can work either by disabling 1901 or just 1905. For AMD, 1901 is needed (1901 frees more resources vs. 1905, latter sufficient for NVIDIA, not AMD). I believe he may have the best answer, but that was my inference.
I see, english is not my first language. So I misunderstood the first part as disable 1901 for NVIDIA,1905 for AMD and vice versa for the second part. Nevertheless in my only probably successful attempt, I lost the eGPU driver after reboot, is this a well known Win10 bug or I'm missing steps?
Thanks
RTX 2080Ti
2016 15' Macbook Pro with RP460
Akitio Node Pro
AFAIK, firmware/EFI updates are persistent. Once done, you can't go back.
This used to be possible. https://forums.macrumors.com/threads/guide-how-to-get-back-old-efi-after-downgrade-from-yosemite.1803934/
And downloads up to the Mid-2014 MBP (2015's firmware are available) from Apple's website. As we know, we don't have the firmwares for the newer devices (unless someone dumped and saved them) but it would seem, technically, that it is possible. Anyhow, irrelevant here but worth noting 
Hi,
Somehow with this app, I can boot Mac OS X but not Windows 10. It just hung if I chose 'Load Windows'. It doesn't matter if my eGPU is connected or not. 🙁
I can boot Windows 10 if I bypass this app. But I have to hot plug the eGPU when dots are spinning, which I hope that this app would fix.
iMac Retina 4K, 21", Late 2015, Mojave, iGPU 6200
MBP Retina, 13", Early 2015, Mojave, iGPU 6100
Aorus Gaming Box GTX1080
@navillezhang I think you should consider retrying on a clean bootcamp installation/ensure non-modded state install, with this EFI. First just attempt getting the iGPU to work. Test multiple boots in this config. and then go on to the eGPU (hotplug/DSDT/etc.).
While it's not for NVIDIA eGPU, which is actually easier, I believe following most of the steps there should give you a system that can initialize any single eGPU properly (he initialized 2).
Instead of using integrated.bat you could use MuxSetting=1.