Notifications
Clear all

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

 of  121
  RSS

goalque
(@goalque)
Noble Member Admin
Joined: 5 years ago
 
Posted by: NavilleZhang
Posted by: goalque
Posted by: NavilleZhang
No firmware updates. I've always been on macOS Mojave

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.

automate-eGPU EFIapple_set_os.efi

Mid 2015 15-inch MacBook Pro eGPU Master Thread

 
2018 13" MacBook Pro [8th,4C,U] + Radeon VII @ 32Gbps-TB3 (ASUS XG Station Pro) + Win10 1809 [build link]  


ReplyQuote
jya
 jya
(@jya)
Trusted Member
Joined: 4 years ago
 
Posted by: mac_editor

@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

To do: Create my signature with system and expected eGPU configuration information to give context to my posts. I have no builds.

.

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

@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

To do: Create my signature with system and expected eGPU configuration information to give context to my posts. I have no builds.

.

goalque liked
ReplyQuote
NavilleZhang
(@navillezhang)
Trusted Member
Joined: 3 years ago
 
Posted by: goalque
Posted by: NavilleZhang
Posted by: goalque
Posted by: NavilleZhang
No firmware updates. I've always been on macOS Mojave

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


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

@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

AFAIK, firmware/EFI updates are persistent. Once done, you can't go back.

automate-eGPU EFIapple_set_os.efi

Mid 2015 15-inch MacBook Pro eGPU Master Thread

 
2018 13" MacBook Pro [8th,4C,U] + Radeon VII @ 32Gbps-TB3 (ASUS XG Station Pro) + Win10 1809 [build link]  


ReplyQuote
goalque
(@goalque)
Noble Member Admin
Joined: 5 years ago
 
Posted by: NavilleZhang
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.

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]. 

automate-eGPU EFIapple_set_os.efi

Mid 2015 15-inch MacBook Pro eGPU Master Thread

 
2018 13" MacBook Pro [8th,4C,U] + Radeon VII @ 32Gbps-TB3 (ASUS XG Station Pro) + Win10 1809 [build link]  


ReplyQuote
NavilleZhang
(@navillezhang)
Trusted Member
Joined: 3 years ago
 
Posted by: goalque
Posted by: NavilleZhang
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.

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


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

Internet recovery downloads the newest firmware. Security reasons is a good explanation.

automate-eGPU EFIapple_set_os.efi

Mid 2015 15-inch MacBook Pro eGPU Master Thread

 
2018 13" MacBook Pro [8th,4C,U] + Radeon VII @ 32Gbps-TB3 (ASUS XG Station Pro) + Win10 1809 [build link]  


ReplyQuote
NavilleZhang
(@navillezhang)
Trusted Member
Joined: 3 years ago
 
Posted by: goalque

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


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

You have community support, we do our best but cannot promise anything. Only Apple can provide official Boot Camp support.

automate-eGPU EFIapple_set_os.efi

Mid 2015 15-inch MacBook Pro eGPU Master Thread

 
2018 13" MacBook Pro [8th,4C,U] + Radeon VII @ 32Gbps-TB3 (ASUS XG Station Pro) + Win10 1809 [build link]  


ReplyQuote
 of  121