|
|
Post by Mat HD on Oct 14, 2018 10:20:04 GMT
As quoted from a guide on the website egpu.io ... "By default, Apple’s firmware switches off the internal GPU when there is eGPU or dGPU present and you’re booting into another OS than macOS. This happens especially with multi-slot enclosures such as Sonnet Echo Express III-D and Netstor NA211TB. Depending on the eGPU, iGPU may stay enabled with a single-slot enclosure but it’s not absolutely certain." Essentially this is a bug (though possibly deliberate) in the EFI booting firmware. It also affects the BlackMagic eGPU, with users reporting the internal display not working in BootCamp when the eGPU is connected. SOLUTION:Use a modified version of the booting kernel which keeps the internal GPU active even if an eGPU is present. The full instructions can be found here: egpu.io/forums/mac-setup/how-to-keep-mbps-irisiris-pro-activated-when-booting-into-windows-boot-camp/Have fun! |
|
|
|
Post by buffaloseven on Dec 10, 2018 2:10:28 GMT
Just thought I'd note that this doesn't work with 2018 Macbook Pros; the internal display will be locked at 2100P and the eGPU cannot properly accelerate applications displayed on it. Furthermore, installing the Intel Display Drivers will essentially break the ability to output to the internal display.
All hope is not lost, though, as the October 2018 update to Windows 10 allows eGPUs to mux back to the internal display using a dGPU instead of iGPU. If you're using an AMD card in your eGPU, the main issue at the moment is Error 43 on the dGPU when the eGPU is active, so the laptop screen remains blank. Hopefully future AMD drivers can sort this issue out. That said, though, it seems like a solution wont' be too far away as despite the error, Windows 10 still recognizes my RP560X as the "low power GPU" and my RX580 as the "high power GPU". It feels like it won't be too long before AMD eGPUs are plug and play on both macOS and Windows using a Macbook Pro!
|
|
|
|
Post by mckingsley on Jan 28, 2019 8:39:50 GMT
This is all interesting stuff for sure.
First, is there a reason I wan to use these custom drivers if I'm running an eGPU? (sonnet box and Radeon 580)?
I seemed to get everything working with the legit radeon drivers on their website although not really sure how and it did take some tweaking.
i also had the issue at first with my laptop screen not displaying but I think I got it working by turning off my wireless (so it wouldn't try to keep downloading the replacement driver), then disabling the internal radeon 555 and rebooting and now it's staying disabled and my laptop screen lights up along with my external screen.
|
|
|
|
Post by Mat HD on Jan 28, 2019 11:32:21 GMT
This is all interesting stuff for sure. First, is there a reason I wan to use these custom drivers if I'm running an eGPU? (sonnet box and Radeon 580)? I seemed to get everything working with the legit radeon drivers on their website although not really sure how and it did take some tweaking. i also had the issue at first with my laptop screen not displaying but I think I got it working by turning off my wireless (so it wouldn't try to keep downloading the replacement driver), then disabling the internal radeon 555 and rebooting and now it's staying disabled and my laptop screen lights up along with my external screen. You may still get a small performance boost with my drivers as I’ve applied some further mods. |
|
|
|
Post by buffaloseven on Aug 18, 2019 19:35:54 GMT
Status update!
I recently updated to the July v2 drivers on the latest version of Windows 10. I'm interested in if there's anything Matt did in his rewrite or if this is all on MS/AMD's end, but my eGPU now functions with the internal display utilizing AMD XConnect with the discrete 560X/external RX 580 pairing. I can use the internal or external display and choose which GPU is utilized in rendering.
Windows 10 makes it a bit of a pain; you have to go to Settings > Graphic Settings and then browse for the executable you want to set the GPU preference for. Once it's added to the list, you then click on it, click on options, and then choose which GPU you want it to use. Personally, I much prefer macOS' simple App > Get Info > Check Prefer eGPU. That said, it all seems to work (with the expected performance hit for the internal display.
I've noticed a few bugs; for example Hitman 2's menus seem to run at 4 FPS on the internal display. I haven't had too much time to play with it though, so I might be able to figure my way around it. I successfully ran No Man's Sky, Subnautica, and Assassin's Creed: Odyssey on my internal display using the RX 580 eGPU.
So that's great!
|
|
|
|
Post by buffaloseven on Aug 18, 2019 22:08:50 GMT
Follow-up update: With the August 2019 drivers, internal and external displays continue to work properly with eGPU connected. Very pleased to see that the only real hiccup with the eGPU setup on a Mac seems to be corrected!
|
|
