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

Page 13 / 14 Prev Next
  RSS

Eightarmedpet
(@eightarmedpet)
Noble Member
Joined: 2 years ago
Posts: 1128
November 22, 2018 10:28 am  

So... my Vega arrived... I swapped out my 1070 and rebooted using the EFI Bootloader...

First boot my keyboard wasn't working, windows was doing some things in the back ground as ever, but neither external nor laptop keyboard ever worked, ffs windows, pull your shit together... (it may have been due to me plugging in the keyboard once booted)

Run DDU

Reboot, we've back, windows is messing about again with setting things up, I should have switched my wifi off, ffs windows, chill out...

Right, lets see what device manager is saying - "Vega".

Sorry, WUT? Yep... after uninstalling Nvidia gubbins and rebooting using this boot manager Windows managed to auto instal drivers needed for my Vega 56 and no error 12, I'm good to go!

Quick round of PUBG - FPS is a fraction lower than with my 1070 so going to see if there are any tweaks I can be doing to optimise.

Once again, a MASSIVE thanks to Goalque for this, I finally have my "perfect" set up (although I am already beginning to wonder about more power/quieter options) for both macOS and W10 (gaming performance in macOS is CRAP).

Second boot - back to error 12, livid...

2017 13" MacBook Pro Touchbar + [email protected] (AKiTiO Thunder3) + Win10
2017 13" MacBook Pro Touch Bar + [email protected] (Sonnet Breakaway Box) + Win10

2017 13" MacBook Pro Touch Bar + GTX1070 (debating 2070 upgrade) @32Gbps-TB3 (Razer Core V1) + Win10

2017 13" MacBook Pro Touch Bar + Vega 56 @32Gbps-TB3 (Razer Core V1) + Win10 & macOS 10.14+

---
LG 5K Ultrafine flickering issue fix


ReplyQuote
killengage
(@killengage)
Active Member
Joined: 10 months ago
Posts: 10
November 22, 2018 11:35 pm  

I have a iMac Pro with Aorus E-GPU 1080. It worked with automate script on 10.13. I reinstalled to Mojave and now when i insert the USB with EFI and select as boot i see a some info flashing by and screen stays black, no menu. Changed Mux to 0 or 1. No luck. Any idea's ?

Soon I will add my system & eGPU details or a build link to this my signature to give context to my posts


ReplyQuote
theitsage
(@itsage)
Famed Member Admin
Joined: 2 years ago
Posts: 3232
November 23, 2018 4:23 am  

@eightarmedpet I found booting with the PCIe Root Port #3 to the Wireless card would give me a better chance of AMD eGPU working. Once XConnect is running in Windows, simply re-enable the Root Port to use the wireless card.

Best ultrabooks for eGPU use

eGPU enclosure buying guide

86 external GPU build guides


ReplyQuote
ahs
 ahs
(@ahs)
New Member
Joined: 11 months ago
Posts: 3
November 23, 2018 10:34 pm  

System: nMP with AMD FirePro 700d and Akitio Node with 980ti hybrid, OS X 10.13.6
Enabled TB2 and installed NVIDIA Web driver with purge-wrangler
Boot form USB-Stick (Automate-eGPU EFi): no problem (apple_set_os.efi  is removed)
Following the steps as described: eGPU is activated without any problems
All other monitors are "going black" but the mouse pointer is still visible on the monitors connected to the Fire Pro
The optional steps ( 7) sudo pmset -a gpuswitch 2, 8) sudo pmset -a gpuswitch 1) simply do nothing

My problem is that I don't know where I have to write

<key>MuxSetting</key>
<integer>1</integer>

in config.plist (with or without <dict>)

Sorry for this question...

A very strange thing: one monitor connected to the dGPU now shows a mess of pixels but mouse pointer and screenshot marker are clearly visible. If I take a screenshot the png-file shows the correct screen image... a screenshot of the "pure black monitor" (mouse pointer and screenshot marker clearly visible) reveals a correct png-picture too...

PS: eGPU on nMP with 10.13.6 works for the first time "with the right speed", with all other methods massive lags occurred.

nMP with Xeon 2680 V2 (10 Core, 2.8 GHz), 32 GB RAM, 512 GB SSD, AMD FirePro 700d, eGPU Akitio Node, NVIDIA GeForce GTX 980 Ti 6143 MB


ReplyQuote
goalque
(@goalque)
Noble Member Admin
Joined: 2 years ago
Posts: 1315
November 24, 2018 7:05 pm  
Posted by: ahs

System: nMP with AMD FirePro 700d and Akitio Node with 980ti hybrid, OS X 10.13.6
Enabled TB2 and installed NVIDIA Web driver with purge-wrangler
Boot form USB-Stick (Automate-eGPU EFi): no problem (apple_set_os.efi  is removed)
Following the steps as described: eGPU is activated without any problems
All other monitors are "going black" but the mouse pointer is still visible on the monitors connected to the Fire Pro
The optional steps ( 7) sudo pmset -a gpuswitch 2, 8) sudo pmset -a gpuswitch 1) simply do nothing

My problem is that I don't know where I have to write

<key>MuxSetting</key>
<integer>1</integer>

in config.plist (with or without <dict>)

Sorry for this question...

A very strange thing: one monitor connected to the dGPU now shows a mess of pixels but mouse pointer and screenshot marker are clearly visible. If I take a screenshot the png-file shows the correct screen image... a screenshot of the "pure black monitor" (mouse pointer and screenshot marker clearly visible) reveals a correct png-picture too...

PS: eGPU on nMP with 10.13.6 works for the first time "with the right speed", with all other methods massive lags occurred.

https://egpu.io/forums/mac-setup/two-new-egpu-solutions-on-macos-10-13-4-pure-efi-and-hybrid/paged/19/#post-45253

automate-eGPU EFIapple_set_os.efi
--
late-2016 13" Macbook Pro nTB + [email protected] (Netstor HL23T) + macOS & Win10
late-2016 13" Macbook Pro nTB + GTX980/[email protected] (Netstor HL23T) + macOS10.13 & Win10


ReplyQuote
NerdsLTD
(@nerdsltd)
New Member
Joined: 3 weeks ago
Posts: 3
November 25, 2018 10:24 am  

@goalque First, I'm insanely grateful for this amazing solution. I've looked carefully throughout this thread and wanted to confirm that there's no method to properly use a GTX 2070 on Mojave until nVIDIA releases web drivers which is completely up in the air at the moment.  That might happen next week, it might not happen until 2019. Correct? As of now, your boot process is exquisite for the VEGA 56 with OWC's Helios FX (one of the most underrated eGPU enclosures IMO).  nVidia's forums have the longest whinefest I've seen in quite some time. I'd just assume return the 2070 and get a 1080 (assuming that one works). Please let me know. Again, well done man! This is a beautiful solution!

Soon I will add my system & eGPU details or a build link to this my signature to give context to my posts


ReplyQuote
mac_editor
(@mac_editor)
Noble Member Moderator
Joined: 2 years ago
Posts: 1596
November 25, 2018 2:22 pm  

@ahs Please don't combine solutions - use either the script or EFI, not both. Only exception is if you only installed web drivers from the script (Option #5), otherwise not.

@nerdsltd NVIDIA Web drivers are not available for Mojave - so even the 10 series won't work for now. Driver development is in progress.

purge-wrangler.shpurge-nvda.shset-eGPU.sh
----
Troubleshooting eGPUs on macOS
Command Line Swiss Knife
----
Multiple Build Guides


ReplyQuote
ahs
 ahs
(@ahs)
New Member
Joined: 11 months ago
Posts: 3
November 25, 2018 6:13 pm  

@mac_editor  the script enabled TB2 and installed the NVIDIA web-driver (option 5), nothing else. OS X 10.13.6 was a complete new installation on an external SSD.
@goalque thank you for the link!

As mentioned above: NVIDIA eGPU functions properly and rendering with CUDA dependent software will work again. When I have more time, I will try to solve the problem... but surely not without the help of this community 😉

nMP with Xeon 2680 V2 (10 Core, 2.8 GHz), 32 GB RAM, 512 GB SSD, AMD FirePro 700d, eGPU Akitio Node, NVIDIA GeForce GTX 980 Ti 6143 MB


ReplyQuote
mac_editor
(@mac_editor)
Noble Member Moderator
Joined: 2 years ago
Posts: 1596
November 25, 2018 6:15 pm  

@ahs If you used option #5, then TB2 was not/should not be enabled. The EFI stick is doing that. Just clarifying 🙂 Good to hear it's working for you.

purge-wrangler.shpurge-nvda.shset-eGPU.sh
----
Troubleshooting eGPUs on macOS
Command Line Swiss Knife
----
Multiple Build Guides


ReplyQuote
NerdsLTD
(@nerdsltd)
New Member
Joined: 3 weeks ago
Posts: 3
November 26, 2018 1:04 am  

@Mac_editor Thank you for the confirmation

Soon I will add my system & eGPU details or a build link to this my signature to give context to my posts


ReplyQuote
(@florian_bartsch)
New Member
Joined: 4 weeks ago
Posts: 3
November 26, 2018 8:18 pm  

 I copied the Files on an USB Stick (Fat32). Then after selection EFI at Bootmanager i get a Black Screen. Anybody have this problem too? Solutions?

Soon I will add my system & eGPU details or a build link to this my signature to give context to my posts


ReplyQuote
Eightarmedpet
(@eightarmedpet)
Noble Member
Joined: 2 years ago
Posts: 1128
November 27, 2018 9:58 pm  
Posted by: theitsage

@eightarmedpet I found booting with the PCIe Root Port #3 to the Wireless card would give me a better chance of AMD eGPU working. Once XConnect is running in Windows, simply re-enable the Root Port to use the wireless card.

Trying this now... can only find ports 1,5,9 and 12 which I assume is because I’m on a 2017. 

GPU isn’t even detected if booted while plugged in. 

Unplug and replug once windiws has loaded loaded gives good ol error 12.

hotplugging after at windows logo and it’s recognised once booted but error 12. 

Facetime camera and bluetooth is disabled. 

Ive tried every bloody port. 

I only have the core conected. 

I am a combination of absolutely sick of this, confused why it worked for the first few goes, and absolutely sick of this. 

Despite great intial success and no changes being made the efi bootloader no longer works for me.

could it be down to the 8gb memory in the Vega where my 570 had 4gb? That ol chestnut.  Still doesn’t explain why my Vega worked on initial instal that windows actually handled automatically. 

2017 13" MacBook Pro Touchbar + [email protected] (AKiTiO Thunder3) + Win10
2017 13" MacBook Pro Touch Bar + [email protected] (Sonnet Breakaway Box) + Win10

2017 13" MacBook Pro Touch Bar + GTX1070 (debating 2070 upgrade) @32Gbps-TB3 (Razer Core V1) + Win10

2017 13" MacBook Pro Touch Bar + Vega 56 @32Gbps-TB3 (Razer Core V1) + Win10 & macOS 10.14+

---
LG 5K Ultrafine flickering issue fix


ReplyQuote
yjchua
(@yjchua)
Eminent Member
Joined: 2 years ago
Posts: 40
November 27, 2018 10:17 pm  
Posted by: Eightarmedpet
Posted by: theitsage

@eightarmedpet I found booting with the PCIe Root Port #3 to the Wireless card would give me a better chance of AMD eGPU working. Once XConnect is running in Windows, simply re-enable the Root Port to use the wireless card.

Trying this now... can only find ports 1,5,9 and 12 which I assume is because I’m on a 2017. 

GPU isn’t even detected if booted while plugged in. 

Unplug and replug once windiws has loaded loaded gives good ol error 12.

hotplugging after at windows logo and it’s recognised once booted but error 12. 

Facetime camera and bluetooth is disabled. 

Ive tried every bloody port. 

I only have the core conected. 

I am a combination of absolutely sick of this, confused why it worked for the first few goes, and absolutely sick of this. 

Despite great intial success and no changes being made the efi bootloader no longer works for me.

I also ran into error 12 issues on my other laptop (2016 13" touch bar MacBook Pro, but I reckon it'd be slightly different from your 2017).

Strangely though, I managed to bypass it by booting with apple_set_os.efi

Late-2016 15" rMBP (2.9/16/1TB/460)
Akitio Node + Asus Expedition RX 570 OC, 4GB


ReplyQuote
Eightarmedpet
(@eightarmedpet)
Noble Member
Joined: 2 years ago
Posts: 1128
November 28, 2018 9:18 am  

@yjchua cheers for the suggestion, I've used apple_set_os too but had other issues - it appeared to restrict bandwidth to the extent my LG 5K TB3 display remained blank, the bandwidth restriction is an assumption as I do not have enough technical knowledge to investigate/confirm.

May give it another go but make sure I try all ports as I don't believe I did last time...

Something Einstein said is nagging me slightly here...

2017 13" MacBook Pro Touchbar + [email protected] (AKiTiO Thunder3) + Win10
2017 13" MacBook Pro Touch Bar + [email protected] (Sonnet Breakaway Box) + Win10

2017 13" MacBook Pro Touch Bar + GTX1070 (debating 2070 upgrade) @32Gbps-TB3 (Razer Core V1) + Win10

2017 13" MacBook Pro Touch Bar + Vega 56 @32Gbps-TB3 (Razer Core V1) + Win10 & macOS 10.14+

---
LG 5K Ultrafine flickering issue fix


ReplyQuote
yjchua
(@yjchua)
Eminent Member
Joined: 2 years ago
Posts: 40
November 28, 2018 9:35 am  

@Eightarmedpet apple_set_os.efi shouldn't restrict bandwidth with AMD GPUs (at least it didn't for me).

I remembered there was another thing (something along the lines of spoof_osx) that didn't cause H2D issues.

PS - on 13", use the left side ports for full bandwidth. Also make sure that your cable is 0.5m or shorter if passive, and if longer, make sure it's active.

To check the bandwidth, use CL!ng on macOS. On Windows, use AIDA64.

Unthrottled H2D should exceed 2000MB/s.

Late-2016 15" rMBP (2.9/16/1TB/460)
Akitio Node + Asus Expedition RX 570 OC, 4GB


ReplyQuote
Eightarmedpet
(@eightarmedpet)
Noble Member
Joined: 2 years ago
Posts: 1128
November 28, 2018 9:44 am  

@yjchua maybe it was the spoof_osx that was causing the issues... I use left hand ports for eGPU but when my LG 5K is connected to the other it stays blank (although I can hear it being recognised).

Cables are correct.

Will see if running the monitor off the right hand ports works after I give apple_set_os another go (but not rEFInd due to built in spoof_osx)

Also, as mentioned, I remember something about high GB cards being even more of an issue, but think that was on TI.

2017 13" MacBook Pro Touchbar + [email protected] (AKiTiO Thunder3) + Win10
2017 13" MacBook Pro Touch Bar + [email protected] (Sonnet Breakaway Box) + Win10

2017 13" MacBook Pro Touch Bar + GTX1070 (debating 2070 upgrade) @32Gbps-TB3 (Razer Core V1) + Win10

2017 13" MacBook Pro Touch Bar + Vega 56 @32Gbps-TB3 (Razer Core V1) + Win10 & macOS 10.14+

---
LG 5K Ultrafine flickering issue fix


ReplyQuote
yjchua
(@yjchua)
Eminent Member
Joined: 2 years ago
Posts: 40
November 28, 2018 11:17 am  

@eightarmedpet did you disable PCI root port 9D18/9D19? This'll disable the right side ports to free up resources to eliminate Error 12 (disable the FaceTime camera too along with 9D18/9D19).

Late-2016 15" rMBP (2.9/16/1TB/460)
Akitio Node + Asus Expedition RX 570 OC, 4GB


ReplyQuote
Eightarmedpet
(@eightarmedpet)
Noble Member
Joined: 2 years ago
Posts: 1128

ReplyQuote
theitsage
(@itsage)
Famed Member Admin
Joined: 2 years ago
Posts: 3232
November 28, 2018 1:32 pm  

@eightarmedpet Can you take a screen capture of Device Manager similar to mine with the PCIe Root Ports all expanded? We want to locate to the wireless card attachment point then disable it. It's also best to run DDU to effectively reset resource allocation. I would imagine the rEFInd installation is still on your internal drive. That's ok. You can simply go back into macOS and set the default startup drive and the system will ignore rEFInd.

I've noticed sometime the system doesn't detect the Thunderbolt connection to the eGPU when booting up with @goalque EFI boot manager. What I typically do is to hot-unplug then hot-plug the eGPU at Windows desktop to get detection. Once it's recognized I would proceed to restart. It's not the easiest of process but that's life with an AMD eGPU in Boot Camp.

Best ultrabooks for eGPU use

eGPU enclosure buying guide

86 external GPU build guides


ReplyQuote
Eightarmedpet
(@eightarmedpet)
Noble Member
Joined: 2 years ago
Posts: 1128
November 28, 2018 1:42 pm  

@itsage cheers for the reply, will post a screen grab tonight, although I feel quite burned out on it all... rEFInd has long since been removed, all good there, run DDU before each new instal (and obv restart). 

I always had to unplug and unplug to get the egpu detected but restart wasn't needed/asked for, although I also tried restarting.

Really feel AMD need to do something to make their card work as easily as Nvidia ones do.

2017 13" MacBook Pro Touchbar + [email protected] (AKiTiO Thunder3) + Win10
2017 13" MacBook Pro Touch Bar + [email protected] (Sonnet Breakaway Box) + Win10

2017 13" MacBook Pro Touch Bar + GTX1070 (debating 2070 upgrade) @32Gbps-TB3 (Razer Core V1) + Win10

2017 13" MacBook Pro Touch Bar + Vega 56 @32Gbps-TB3 (Razer Core V1) + Win10 & macOS 10.14+

---
LG 5K Ultrafine flickering issue fix


theitsage liked
ReplyQuote
eight_io
(@eight_io)
New Member
Joined: 2 weeks ago
Posts: 1
November 29, 2018 3:59 pm  

MBP 15" late 2016 with touchbar. Sonnet Breakaway box, GeForce 1080 ti.

eGPU is not detected in EFI boot menue if eGPU connected before the boot.

 However, when selecting MacOS from the menu, disconnecting eGPU, logging in, connecting the eGPU, logging off -- everything works. That proves that hardware is OK.

However on bootcamp (Windows 10), nothing happens vis-a-vis the eGPU. It is not detected after hot pluging/logging off etc.

What are my actions debugging this?

Thanks.

Soon I will add my system & eGPU details or a build link to this my signature to give context to my posts


ReplyQuote
detunedradios
(@detunedradios)
Trusted Member
Joined: 11 months ago
Posts: 60
November 30, 2018 1:45 am  

This EFI appears to be creating a recurring issue on my 2016 15” MBP.

Whenever I use this EFI to boot into Windows, then restart back into macOS normally (not using the EFI), I get a sleep/wake issue where the internal display becomes a garbled red mess when I open the lid. It seems like an issue with the iGPU - if I plug in an external monitor directly to the Mac and kick in the dGPU it fixes it temporarily. Resetting the SMC totally resolves it, at least until I use this EFI again. Now I’m having to basically reset my SMC every time I go between Windows (using this) back to macOS.

2016 15" MacBook Pro - 2.7GHz Core i7, Radeon Pro 460 4GB, 1TB SSD
Sonnet Breakaway Box 350, modded with 650W PSU, with Radeon RX Vega 64


ReplyQuote
mac_editor
(@mac_editor)
Noble Member Moderator
Joined: 2 years ago
Posts: 1596
November 30, 2018 2:57 am  

@detunedradios Are you using MuxSetting=1 and apple_set_os.efi (part of EFI solution)?

The thing with MuxSetting=1 is that the effect may linger on the next boot (even if it is clean) [i.e., you use EFI stick to boot any OS, mux is updated, then you boot without stick, the setting is still affecting system]. Rebooting clean twice into macOS usually cleans out the mux preference in the EFI. Basically, controlling gmux stuff is ugly however it's done.

purge-wrangler.shpurge-nvda.shset-eGPU.sh
----
Troubleshooting eGPUs on macOS
Command Line Swiss Knife
----
Multiple Build Guides


ReplyQuote
The_Livy
(@the_livy)
New Member
Joined: 2 weeks ago
Posts: 4
November 30, 2018 3:06 am  
Posted by: yathree

Just tried this on my 2017 iMac 5K with RP580 dGPU, macOS 10.13.6, and GTX1080ti eGPU in OWC Mercury Helios FX.
I have the latest web drivers installed, and your validation script said my system was 'clean'.

  • Copied the files onto a FAT32-formatted external HDD
  • Did EFI boot (with eGPU turned off)
  • The automate-eGPU screen loads just fine
  • Hit q, then selected 'Boot mac OS' from the menu
  • It freezes on this menu screen and never goes anywhere

Tried several times with the same result. Help? 🙂

First of all: Hello everyone, I'm new here, had some trouble signing up (didn't get the password email 4 times until i did it with Internet Explorer and an outlook mail address, sorry for cluttering the memberlist);

I don't know if this issue has been resolved yet, but I did some testing and came across the same issue:

It appears to only work if the Apple OS Partition was formatted in APFS. I tried installing High Sierra on a HFS+ Volume (in order to be able to read from Windows without buying a new driver) and figured out, that automate-eGPU EFI freezes when trying to boot to macOS installed to the HFS+ Volume, converting HFS+ to APFS results in a working automate-eGPU EFI for me.

Since I just scrolled up a bit and saw another message: I also did some testing on Bootloader Icons. First I realized that the macOS High Sierra USB Installer I created in order to install on a HFS+ volume had an Icon in the Apple Bootloader, I then found a "hidden" file called .VolumeIcon.icns on the drive and decided to just try copying it to the root folder of my macOS partition; this lead to the macOS partition now having this nice High Sierra Icon in my Bootloader; I then created an Icon with the same Thunderbolt logo i just saw above (sorry, didn't read all the posts) from the same icns and would love to share that icns file with you (if only I could upload files yet). I copied that icns to the FAT32 partition on which i put automate-eGPU EFI onto in order for it to show this icon for the eGPU partition (i didn't like the idea of needing a USB stick plugged in at all times, so I decided to go with a separate 300MB FAT32 partition). The only thing i couldn't figure out is where to put the icns file for the Windows partition. While macOS picks it up and shows the icon in Finder, the bootloader doesn't seem to recognize it anywhere on the NTFS volume (I also tried copying it to multiple folders within Windows/Boot and the EFI partition (EFI/Microsoft,etc.) - but sadly the bootloader won't pick it up) If anyone knows how to work this out, I would appreciate a hint!

Last of all: Thank you so much for the great work you all put into this website, I really appreciate it and probably would have never dared to try the whole eGPU setup myself! (running a 2017 13" MacBook Pro with TouchBar + Aorus Gaming Box 1070)

MacBook Pro 13" TouchBar 2017 + Aorus Gaming Box 1070
Silent Modded Case with optimized card power target/fan curve to reduce temperatures/component wear - will create a topic on it (and some details on performance "loss") soon


ReplyQuote
NavilleZhang
(@navillezhang)
Trusted Member
Joined: 2 months ago
Posts: 53
November 30, 2018 5:51 am  

Gentlemen. I've verified that my RTX card is working properly on a PC. And now I get disable 1901 on my 2016 15inch rmbp without any problem. However, since disabling 1901 alone still gets me error 12. I poked around even more and can now confirm the cause of me disabling 1905 results in a instant bluescreen, is actually due to an AMD HDMI AudioDriver left behind at port 1905. DDI didn't remove it anyhow so I'd like to ask if there is any alternative solutions for this

RTX 2080Ti
2016 15' Macbook Pro with RP460
Akitio Node Pro


ReplyQuote
casualslyce
(@casualslyce)
Active Member
Joined: 5 months ago
Posts: 8
December 2, 2018 10:57 pm  

Hi all. I am having a hard time with the first step. I really thought I'd erased all previous solutions but am getting "Invalid system kext found" after running the validate-kexts script. 

I had my Aorus 1070 up and running in bootcamp for a little while using the @itsage solution, but it was never reliably stable and would ultimately BSOD and require redoing the whole procedure. My end goal is to use the Oculus Rift in Windows and I suspect many of  my issues were related to bandwidth -- between the gaming box, the multiple oculus sensors, and an external hard drive I just have a ton of stuff plugged in.

I've uninstalled everything I think might have been conflicting, done a clean re-install of High Sierra through recovery mode, and tried rebuilding the kext library, but still get the same message. 

kextcache -system-caches yields the following:

Kext with invalid signatured (-67030) allowed: <OSKext 0x7f9fe2eca9d0 [0x7fff92493af0]> { URL = "IONDRVSupport.kext/ -- file:///System/Library/Extensions/", ID = "com.apple.iokit.IONDRVSupport" }

My next step is reformatting the drive and doing a complete re-install, but I'm not looking forward to it. Any insight is greatly appreciated. Thanks 🙂

 

2016 Macbook Pro TB Radeon 460 | Aorus 1070 | High Sierra 10.13.6 | Bootcamp Windows 1803


ReplyQuote
mac_editor
(@mac_editor)
Noble Member Moderator
Joined: 2 years ago
Posts: 1596
December 3, 2018 3:37 am  

@casualslyce No need to erase your drive to fix that. Just install macOS onto current installation again.

purge-wrangler.shpurge-nvda.shset-eGPU.sh
----
Troubleshooting eGPUs on macOS
Command Line Swiss Knife
----
Multiple Build Guides


ReplyQuote
jensph
(@jensph)
New Member
Joined: 3 weeks ago
Posts: 2
December 3, 2018 4:40 pm  

Hi!

I have a 15" MBP from late 2016, trying to set up an eGPU (Razor Core X with GeForce GTX 1060) on the High Sierra 10.13.06 OS on the partition I want to use the eGPU. However, I also have a partition with Mojave and when I want to boot with the EFI USB, the High Sierra partition does not appear as an option. Any idea what I could do? Do I have to have High Sierra on the partition?

Super grateful for any help 🙂

Cheers

Soon I will add my system & eGPU details or a build link to this my signature to give context to my posts


ReplyQuote
Eightarmedpet
(@eightarmedpet)
Noble Member
Joined: 2 years ago
Posts: 1128
December 3, 2018 8:40 pm  

I’m prob speaking way too soon but I may have cracked it. 

Slight odd behaviour from this bootloader not detecting the egpu even once fully booted. The work around for me was to hotplug as you do with Nvidia cards after boot selection via EFI Bootloader. 

Even made add my own thread as I was expecting this to take weeks to work out...

https://egpu.io/forums/pc-setup/my-personal-experience-with-the-hell-that-is-error-12/#post-49006

2017 13" MacBook Pro Touchbar + [email protected] (AKiTiO Thunder3) + Win10
2017 13" MacBook Pro Touch Bar + [email protected] (Sonnet Breakaway Box) + Win10

2017 13" MacBook Pro Touch Bar + GTX1070 (debating 2070 upgrade) @32Gbps-TB3 (Razer Core V1) + Win10

2017 13" MacBook Pro Touch Bar + Vega 56 @32Gbps-TB3 (Razer Core V1) + Win10 & macOS 10.14+

---
LG 5K Ultrafine flickering issue fix


ReplyQuote
mac_editor
(@mac_editor)
Noble Member Moderator
Joined: 2 years ago
Posts: 1596
December 3, 2018 9:10 pm  

@eightarmedpet That was happening to me with AMD eGPU as well if I booted with the EFI stick into Windows (15" 2018, don't need it for Windows, only testing). Already plugged in eGPU would not be detected. Hot-Plugging would detect the GPU (hot plug after full boot = Error 12).

purge-wrangler.shpurge-nvda.shset-eGPU.sh
----
Troubleshooting eGPUs on macOS
Command Line Swiss Knife
----
Multiple Build Guides


ReplyQuote
Eightarmedpet
(@eightarmedpet)
Noble Member
Joined: 2 years ago
Posts: 1128
December 3, 2018 9:33 pm  
Posted by: mac_editor

@eightarmedpet That was happening to me with AMD eGPU as well if I booted with the EFI stick into Windows (15" 2018, don't need it for Windows, only testing). Already plugged in eGPU would not be detected. Hot-Plugging would detect the GPU (hot plug after full boot = Error 12).

Glad I’m not the only one. If I was prone to a smoke I may have gotten somewhat paranoid that it was just me and all some sort of conspiracy, next stop posting about flat earth theories on Instagram!

2017 13" MacBook Pro Touchbar + [email protected] (AKiTiO Thunder3) + Win10
2017 13" MacBook Pro Touch Bar + [email protected] (Sonnet Breakaway Box) + Win10

2017 13" MacBook Pro Touch Bar + GTX1070 (debating 2070 upgrade) @32Gbps-TB3 (Razer Core V1) + Win10

2017 13" MacBook Pro Touch Bar + Vega 56 @32Gbps-TB3 (Razer Core V1) + Win10 & macOS 10.14+

---
LG 5K Ultrafine flickering issue fix


mac_editor liked
ReplyQuote
goalque
(@goalque)
Noble Member Admin
Joined: 2 years ago
Posts: 1315
December 3, 2018 9:48 pm  
Posted by: Eightarmedpet

I’m prob speaking way too soon but I may have cracked it. 

Slight odd behaviour from this bootloader not detecting the egpu even once fully booted. The work around for me was to hotplug as you do with Nvidia cards after boot selection via EFI Bootloader. 

Even made add my own thread as I was expecting this to take weeks to work out...

https://egpu.io/forums/pc-setup/my-personal-experience-with-the-hell-that-is-error-12/#post-49006

It depends on the enclosure if you need hot plugging or not. I would avoid those with USB extensions on the back. This EFI boot loader doesn't do anything magical for Windows by default. You can achieve the same result with gpu-switch and running apple_set_os.efi manually, then chain load bootmgfw.efi. Do you have the large memory area defined in DSDT?

Disabling acpi somewhat helped on Linux:

https://egpu.io/forums/thunderbolt-linux-setup/problems-with-amd-rx-580-akitio-node-tb3-ubuntu-18-10/#post-45835

https://bugzilla.kernel.org/show_bug.cgi?id=201527

"The AMD developers believe the issue might be caused by PCI BAR resource issues - specifically some of the PCI to TB bridges not getting the necessary resources."

Maybe you could try something similar by turning off firmware PCI settings?
https://docs.microsoft.com/en-us/windows-hardware/drivers/devtest/bcdedit--set

usefirmwarepcisettings [ yes | no ]
Enables or disables the use of BIOS-configured peripheral component interconnect (PCI) resources.

I wouldn't trust that workaround though... there are a lot of affecting variables: the BARs of the AMD card, the Apple firmware, the Thundebolt port, and the enclosure you are using.

automate-eGPU EFIapple_set_os.efi
--
late-2016 13" Macbook Pro nTB + [email protected] (Netstor HL23T) + macOS & Win10
late-2016 13" Macbook Pro nTB + GTX980/[email protected] (Netstor HL23T) + macOS10.13 & Win10


ReplyQuote
Eightarmedpet
(@eightarmedpet)
Noble Member
Joined: 2 years ago
Posts: 1128
December 3, 2018 9:54 pm  

Something that avoids me having to  “You can achieve the same result with gpu-switch and running apple_set_os.efi manually, then chain load bootmgfw.efi.” Is pretty magical to me because I wouldn’t know where to start with half of that - also I think Apple_set_os was responsible for blocking my LG 5k from working. 

Im on a 2017 13 inch Mbp so large memory by default, no need to mess with DSDT. 

I would love AMD to fix this with Navi this January...

2017 13" MacBook Pro Touchbar + [email protected] (AKiTiO Thunder3) + Win10
2017 13" MacBook Pro Touch Bar + [email protected] (Sonnet Breakaway Box) + Win10

2017 13" MacBook Pro Touch Bar + GTX1070 (debating 2070 upgrade) @32Gbps-TB3 (Razer Core V1) + Win10

2017 13" MacBook Pro Touch Bar + Vega 56 @32Gbps-TB3 (Razer Core V1) + Win10 & macOS 10.14+

---
LG 5K Ultrafine flickering issue fix


goalque liked
ReplyQuote
goalque
(@goalque)
Noble Member Admin
Joined: 2 years ago
Posts: 1315
December 3, 2018 10:02 pm  
Posted by: Eightarmedpet

Something that avoids me having to  “You can achieve the same result with gpu-switch and running apple_set_os.efi manually, then chain load bootmgfw.efi.” Is pretty magical to me because I wouldn’t know where to start with half of that - also I think Apple_set_os was responsible for blocking my LG 5k from working. 

Im on a 2017 13 inch Mbp so large memory by default, no need to mess with DSDT. 

I would love AMD to fix this with Navi this January...

From my signature, keeping iGPU activated when booting into Windows using apple_set_os.efi 🙂

Hoping that Apple engineers push some effort into the Windows side as well... I guess it's not on the priority list.

automate-eGPU EFIapple_set_os.efi
--
late-2016 13" Macbook Pro nTB + [email protected] (Netstor HL23T) + macOS & Win10
late-2016 13" Macbook Pro nTB + GTX980/[email protected] (Netstor HL23T) + macOS10.13 & Win10


ReplyQuote
mac_editor
(@mac_editor)
Noble Member Moderator
Joined: 2 years ago
Posts: 1596
December 3, 2018 10:08 pm  
Posted by: goalque

Hoping that Apple engineers push some effort into the Windows side as well... I guess it's not on the priority list.

I would be happy if they fix the audio drivers in Win. for the 2018 MBP at least. Fortunately as I use a USB AMP/DAC it's ok, but both internal speakers, 3.5mm jack, and internal microphone are nearly unusable. God they're bad (at least on 15"). Wrt eGPU, They need to sort out much macOS-side too. Example: Plug in eGPU (native) to a sleeping MBP on 10.14.1/2 -> typically black screens. And a lot of other things.

purge-wrangler.shpurge-nvda.shset-eGPU.sh
----
Troubleshooting eGPUs on macOS
Command Line Swiss Knife
----
Multiple Build Guides


goalque liked
ReplyQuote
iaomw
(@iaomw)
Active Member
Joined: 2 years ago
Posts: 17
December 8, 2018 11:10 pm  

It works great on macOS. But I got issue with Windows.
Is that possible to work with external WTG (Windows to Go) usb disk?

I mean the macOS is still on the internal disk, but windows is on the external usb disk. 
When I was trying to load windows from your EFI menu, it will just froze here forever.

Sorry, if this is already discussed somewhere in the form. It's difficult to search.

Soon I will add my system & eGPU details or a build link to this my signature to give context to my posts


Maximilian M liked
ReplyQuote
Page 13 / 14 Prev Next