automate-eGPU EFI - eGPU boot manager for macOS and Windows
 
Notifications
Clear all

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

 of  108
  RSS

OliverB
(@oliverb)
Noble Member
Joined: 2 years ago
 
Posted by: mac_editor

@oliverb If using an NVIDIA eGPU, you can get the internal display to function fully accelerated as well, if the eGPU is hot-plugged at the right time and no other peripherals are present.

I actually have my internal display fully accelerated, only that I cannot start DirectX Applications there, it got an error (see below). Workaround: I can start on the external display and drag it into the internal or I can start without DirectX (e.g. OpenGL).

Anyway, external display works perfectly and no need to hot-plug at the right time.

NoDirectXStartOnInterlDisplay

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

 
2018 15" MacBook Pro (RP560X) [8th,6C,H] + RX 5700 XT @ 32Gbps-TB3 (ASUS XG Station Pro) + Win10 & macOS 10.15.4 [build link]  


ReplyQuote
OliverB
(@oliverb)
Noble Member
Joined: 2 years ago
 

@mac_editor, perhaps you know what this strange artifact like a little window with disables scrowbars mean on my internal display (left side):

InternalDisplayLeft

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

 
2018 15" MacBook Pro (RP560X) [8th,6C,H] + RX 5700 XT @ 32Gbps-TB3 (ASUS XG Station Pro) + Win10 & macOS 10.15.4 [build link]  


ReplyQuote
mac_editor
(@mac_editor)
Famed Member Moderator
Joined: 3 years ago
 

@oliverb By accelerated I meant that the GPU driving the display is not a basic adapter. Hence you see the error while launching apps. Basically the internal AMD GPU can function alongside NVIDIA eGPU.

That artifact is just a glitch. 

purge-wranglertbt-flashpurge-nvdaset-eGPU
Insights Into macOS Video Editing Performance

Master Threads:
2014 15-inch MacBook Pro 750M
2018 15-inch MacBook Pro

 
2019 13" MacBook Pro [8th,4C,U] + RX Vega 64 @ 32Gbps-TB3 (Mantiz Venus) + macOS 10.14.6 & Win10 [build link]  


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

@oliverb We are talking about activating the Intel iGPU for internal display, do you have the same problem?

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
OliverB
(@oliverb)
Noble Member
Joined: 2 years ago
 
Posted by: mac_editor

@oliverb By accelerated I meant that the GPU driving the display is not a basic adapter. Hence you see the error while launching apps. Basically the internal AMD GPU can function alongside NVIDIA eGPU.

That artifact is just a glitch. 

Ah, this nasty little glitch remains stubbornly.
@goalque: Sorry, If I got little Off-Topic.. This is all very faszinating.

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

 
2018 15" MacBook Pro (RP560X) [8th,6C,H] + RX 5700 XT @ 32Gbps-TB3 (ASUS XG Station Pro) + Win10 & macOS 10.15.4 [build link]  


ReplyQuote
egpu_freak
(@egpu_freak)
Active Member
Joined: 2 years ago
 

my external display is able to detect my egpu, how can I use the egpu to accelerate my internal display and choose the app to be accelerated?

2017 13" MacBook Pro [7th,2C,U] + GTX 1060 @ 32Gbps-TB3 (Razer Core X) + macOS 10.13 & Win10 & Linux [build link]  

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

Then hold down the Option key and select "EFI Boot".

Type "devtree -b" to see which GPU is driving the internal display.

Our last chance is to access the gmux through IO address space:

mm -io 7D0 10 -n

mm -io 7C2 -n

What's the output?

Ok, this is what I've tried.

1- Shell_Full.efi on separate USB

devtree -b shows both the AMD and the Skylake EG2 graphic device. I can't tell which one is active from that screen, this is just the PCI tree
mm -io 7D0 10 -n -> nothing output
nm -io 7C2 -n -> 0xFF

1- Shell_Full.efi on separate USB, after running

sudo nvram fa4ce28d-b62f-4c99-9cc3-6815686e30f9:gpu-power-prefs=%01%00%00%00

Identical to step 1.
devtree -b shows both the AMD and the Skylake EG2 graphic device. I can't tell which one is active from that screen, this is just the PCI tree
mm -io 7D0 10 -n -> nothing output
nm -io 7C2 -n -> 0xFF

3- Install refind, run apple_set_os.efi then Full-Shell.efi
Identical to step 1.
devtree -b shows both the AMD and the Skylake EG2 graphic device. I can't tell which one is active from that screen, this is just the PCI tree
mm -io 7D0 10 -n -> nothing output
nm -io 7C2 -n -> 0xFF

4- Install refind, run nvram command, run apple_set_os.efi then Full-Shell.efi
Identical to step 1.
devtree -b shows both the AMD and the Skylake EG2 graphic device. I can't tell which one is active from that screen, this is just the PCI tree
mm -io 7D0 10 -n -> nothing output
nm -io 7C2 -n -> 0xFF

So the gmux doesn't seem to be impacted by any of those commands.

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

.

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

Ok, thanks. I have never seen value 0xFF before (you have a typo there, should be mm not nm). I suppose the AMD appears first in the device tree and has ”Primary Console Output Device” item?

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: 2 years ago
 
Posted by: goalque

Ok, thanks. I have never seen value 0xFF before (you have a typo there, should be mm not nm). I suppose the AMD appears first in the device tree and has ”Primary Console Output Device” item?

That is correct.
Primary Console Output Device is attached to AMD Radeon Baffin Video Adapter.

Could it be that the gmux device is now attached at a different address on those models?

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

.

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

@jya yes, it is very possible that the gmux device is located at the different offset. Current Linux drivers define it at 0x700.

To find out the correct IO offset, you need to look at ACPI tables and search for the minimum range value for this device. In Linux, you should be able to read registered port regions from the /proc/ioports file.

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  108