Setup & Software Discussions
Two new eGPU solutions on macOS 10.13.4: pure EFI and hybrid
 

Two new eGPU solutions on macOS 10.13.4: pure EFI and hybrid  

 of  19
  RSS

Ningauble77
(@ningauble77)
Estimable Member
Joined: 2 years ago
 
Posted by: goalque

I meant subsequent boots into macOS before the Windows Boot camp disabled the iGPU. Apple's firmware keeps only the dGPU active, and turns off the iGPU which affects the state. To keep them both active on Windows, apple_set_os.efi is required even if the AMD dGPU + Nvidia eGPU combo is operational (as with my M370X).

SkipSetupDataForOSX=false gives 100% success for me but not recommended as I want to minimize all hackintoshing stuff, and accessing the SMC might be risky.

Ok, sorry, the first thing I did after successful egpu boot was boot into bootcamp.  I have been leaving the igpu disabled in boot camp and just using the egpu for external display and the amd card for the internal display.  I need the dgpu functional when I am undocked and mobile in both MacOS and Windows, and have no need for accelerating the internal display in windows with the egpu when docked, I primarily run it in clamshell mode.

I use Windows primarily when at home and docked, and use MacOS primarily when mobile, so for me having an operational egpu in MacOS is as much about the convenience of not having to change things when switching back and forth as anything, which I assume will continue to be a work in progress.

2018 13 Macbook Pro + Core v2 + Radeon VII Win10 1809/MacOS 10.14.5 Beta
ASUS X99 Deluxe+Core v2 + Radeon VII Win10 1809


ReplyQuote
n9yty
(@n9yty)
Eminent Member
Joined: 2 years ago
 

Well, just putting this out for a data point.  I am sure my system *should* work, as I think @goalque has a system like mine, so it should work...  A mid-2015 15" Macbook Pro, MacBookPro11,5 with AMD Radeon R9 M370X. Trying to use an Auros 1070GTX box.

I had previous run fr34k's script, so I ran that in uninstall mode.
Then I reinstalled 10.13.5 using CMD-R into recovery and reinstall.
I then booted with nothing external connected except the eGPU.
Ran the installer, selected a 1GB MS-DOS SD card as destination, chose hybrid mode.
Kernel Panic during install.
Rebooting with the eGPU kernel panic loops.
Booting without the eGPU at least boots, plugging it in kernel panics.
Re-disabled SIP (somehow it got put back on), uninstalled
Rebooted, and installed again, this time it completed.
Still kernel panics if I boot with eGPU connected or when I plug it in.

After I did get the successful install to SD card, I tried to reboot using OPTION to pick the EFI boot from SD Card, the progress bar gets about 60% or 70% across and then is replaced with a circle w/line in it.

My main drive is not named "Macintosh HD" if that matters.

So, not sure what is different about my system, but I may have to join those on the sidelines as this is worked out a bit more. I'll keep watching, trying anything new that is posted to see if it can be made to work.

I didn't want to install onto the hard drive, as I thought I was supposed to install it to either an SD or USB, but if that is a wrong assumption let me know.

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


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

@n9yty, when you say "kernel panic during install", at what stage exactly? In rebuilding kext caches? The system notification pop-up shows the stage. If so, the installer needs to prompt user to unplug the eGPU at the later stage, since the installed kext alone will always cause a kernel panic, if the eGPU is plugged in (didn't happen to me during installation, but very possible). And by the way, I noticed my SD card becomes easily write protected when I slide it in. When you finally succeeded, please turn on the debug log to see where it halts. For example, @lexine reported "Default boot entry not found". Clover's default boot volume logic is fixable.

automate-eGPU EFIapple_set_os.efi
--
2018 13" MacBook Pro + Radeon [email protected] + Win10 1809


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

Any chance of adding the menu bar icon back in? Personally I really like seeing it as I find it a nice reassurance it has worked. Did I read you removed it because hot plugging isn't possible right now?

2017 13" MacBook Pro Touch Bar
GTX1060 + AKiTiO Thunder3 + Win10
GTX1070 + Sonnet Breakaway Box + Win10
GTX1070 + Razer Core V1 + Win10
Vega 56 + Razer Core V1 + macOS + Win10
Vega 56 + Mantiz Venus + macOS + W10

---

LG 5K Ultrafine flickering issue fix


ReplyQuote
goalque
(@goalque)
Noble Member Admin
Joined: 3 years ago
 
Posted by: Eightarmedpet

Any chance of adding the menu bar icon back in? Personally I really like seeing it as I find it a nice reassurance it has worked. Did I read you removed it because hot plugging isn't possible right now?

Hot plugging works well in hybrid. Hot-unplugging doesn't with Nvidia, therefore it is just confusing, especially when showing "null". In the future, users can choose whether to show it or not in preferences, maybe another icon. @mac_editor is working on an add-on for my automate-eGPU EFI, so at some point, we have a graphical interface for config.plist editing.

With AMDs, the icon will be always visible (no AMD support atm).

automate-eGPU EFIapple_set_os.efi
--
2018 13" MacBook Pro + Radeon [email protected] + Win10 1809


ReplyQuote
Riss
 Riss
(@riss)
Eminent Member
Joined: 2 years ago
 
Posted by: goalque

@Riss, I can provide a new version without eGPU validation for those who want to test Nvidia cards which aren't on the list atm. Once confirmed, I will add it. There seems be a possible vBIOS problem with the Titan X Pascal, not even pci scanning in EFI detects this card with @shrapnl's nMP, has anyone else the Titan X to confirm?

Great thanks! I'll test both Quadro and GTX 780 with my MBP 15" 2014 laptop & Mac mini 2012

mid 2014 MBP 15" GT750m | Mac mini 2012 | Akitio Thunder 2 & 3 | GTX 780 3GB (flashed) | Quadro P2000 (stock)


ReplyQuote
goalque
(@goalque)
Noble Member Admin
Joined: 3 years ago
 
Posted by: Riss
Posted by: goalque

@Riss, I can provide a new version without eGPU validation for those who want to test Nvidia cards which aren't on the list atm. Once confirmed, I will add it. There seems be a possible vBIOS problem with the Titan X Pascal, not even pci scanning in EFI detects this card with @shrapnl's nMP, has anyone else the Titan X to confirm?

Great thanks! I'll test both Quadro and GTX 780 with my MBP 15" 2014 laptop & Mac mini 2012

You're welcome 🙂 By the way, @shrapnl's Titan X (Pascal) did work fine with a 13" MBP but for some reason nMP's pci enumeration didn't see the card.

automate-eGPU EFIapple_set_os.efi
--
2018 13" MacBook Pro + Radeon [email protected] + Win10 1809


ReplyQuote
ghettocivic
(@ghettocivic)
Active Member
Joined: 1 year ago
 
Posted by: goalque
Posted by: Riss
Posted by: goalque

@Riss, I can provide a new version without eGPU validation for those who want to test Nvidia cards which aren't on the list atm. Once confirmed, I will add it. There seems be a possible vBIOS problem with the Titan X Pascal, not even pci scanning in EFI detects this card with @shrapnl's nMP, has anyone else the Titan X to confirm?

Great thanks! I'll test both Quadro and GTX 780 with my MBP 15" 2014 laptop & Mac mini 2012

You're welcome 🙂 By the way, @shrapnl's Titan X (Pascal) did work fine with a 13" MBP but for some reason nMP's pci enumeration didn't see the card.

I would be interested in testing my setup as well with the 750 Ti when this is available

MacBook Pro 13" Late 2013 + Akitio Thunder2 + Sapphire RX570 ITX


ReplyQuote
psonice
(@psonice)
Estimable Member
Joined: 2 years ago
 

@goalque Great to see you got it released 🙂 Has anyone tried an iMac yet? If not, what's the status there - likely issues, probably ok, or unknown? (I'll try either way, but if it's "likely issues" I'll hold until I have a bit more time to deal with any fallout).

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


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

Unknown. Possible known issues at present (concerns all machines):

-the final stage kext cache rebuilding may yield a kernel panic -> solution: unplug the eGPU during the installation, as soon as it is detected by the installer

- "Default boot entry not found" in the debug log -> solution: do nvram reset and select the macOS as the primary boot disk if Boot Camp installed, and install the EFI on the external USB stick always.

- "Critical software component missing" error message, user error -> solution: do not boot through the normal macOS disk image when the eGPU is plugged in. Always hold down the Option key, and select "EFI boot".

The next version will skip Clover's unreliable DefaultVolume setting, and uses my own method, looping through all volumes and checks the existence of boot.efi.

automate-eGPU EFIapple_set_os.efi
--
2018 13" MacBook Pro + Radeon [email protected] + Win10 1809


ReplyQuote
mac_editor
(@mac_editor)
Noble Member Moderator
Joined: 2 years ago
 

@goalque Maybe for third issue can patch on the fly, some of kext’s Info.plist settings when booted from EFI stick. In default boot it would not be invoked even with eGPU plugged in. Also there might be a way to change string EFI Boot to something else for clarity in one of the links you shared with me privately.

purge-wrangler.shpurge-nvda.shset-eGPU.shautomate-eGPU EFI Installer
----
Troubleshooting eGPUs on macOS
Command Line Swiss Knife

Multiple Build Guides
----
Current: MacBook Pro RP560X + 480/R9 Fury/Vega 64 | GTX 780/1070
Previous: 2014 MacBook Pro 750M + 480/R9 Fury | GTX 780/980 Ti/1070


ReplyQuote
Shrapnl
(@shrapnl)
Eminent Member
Joined: 2 years ago
 

Yep, and this same card and enclosure (Sonnet 550) work fine with an Alienware 17" laptop I have.  So the differences are Alienware/nMP and TB3/TB2-3 adaptor and TB2 cable.  Weirdly though the nMP does show the Sonnet 550 enclosure in System Report.  But no card...

2018 MacBook Pro 15" - Sonnet 550 - NVidia Titan X (Pascal)


ReplyQuote
Chippy McChipset
(@chippy-mcchipset)
Reputable Member
Joined: 2 years ago
 

Looks like it's been an eventful few days. Thank you @goalque for all your efforts.

We intend to test the new solutions in the coming days, but it's been a while since I've run any of the scripts here (was waiting for this type of setup / something that might be reasonably stable for recommendation to third parties). Here's my understanding of this new process:

0. No requirements to install any other scripts from this site prior.
1. Launch the installer and install the contents to a Fat 32 USB thumb drive.
2. Make sure the system is cleared of prior NVIDIA script files (i.e. this process doesn't automatically remove anything at any stage).
3. Mount the thumb drive and then option-boot.
4. Choose the EFI or Hybrid installer (Hybrid recommended)
5. When that process is finished, reboot and at the login screen, plug in the eGPU with the NVIDIA card installed.
6. See what happens.

Is that close / am I misunderstanding anything?

2016-2018 Macs, Sonnet eGPUs, RX, WX, Vega AMD cards, GTX 1070 and RTX 2080, various 4K displays


ReplyQuote
n9yty
(@n9yty)
Eminent Member
Joined: 2 years ago
 
Posted by: goalque

@n9yty, when you say "kernel panic during install", at what stage exactly? In rebuilding kext caches? The system notification pop-up shows the stage. If so, the installer needs to prompt user to unplug the eGPU at the later stage, since the installed kext alone will always cause a kernel panic, if the eGPU is plugged in (didn't happen to me during installation, but very possible). And by the way, I noticed my SD card becomes easily write protected when I slide it in. When you finally succeeded, please turn on the debug log to see where it halts. For example, @lexine reported "Default boot entry not found". Clover's default boot volume logic is fixable.

I believe it was when rebuilding the kernel caches, but I honestly can’t say 100% because I looked away, but that was the last thing I saw.

Pretty sure write protect isn’t an issue, but I will watch it, try again with debug log, and let you know.

Thanks for sharing your great work and time helping us to get it working.

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


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

I've uninstalled. 

When I plugged my eGPU in without booting from EFI/USB it caused a system shutdown black screen - ok, not something I would do that regular but the instal has obviously effected something at a system level, however slight, which causes these types of crashes from happening. I also have limited use for an eGPU in MacOS due to running an Ultrafine (headless HDMI is a clumsy faff of a work around IMO).

Will keep an eye on the thread to see how it develops, best of luck guys and thanks again @goalque for your cracking work.

2017 13" MacBook Pro Touch Bar
GTX1060 + AKiTiO Thunder3 + Win10
GTX1070 + Sonnet Breakaway Box + Win10
GTX1070 + Razer Core V1 + Win10
Vega 56 + Razer Core V1 + macOS + Win10
Vega 56 + Mantiz Venus + macOS + W10

---

LG 5K Ultrafine flickering issue fix


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

@chippy-mcchipset Exactly.

@n9yty I thought so. You should always unplug the eGPU, just after detected by the installer, during the installation. Otherwise, rebuilding caches may cause a kernel panic, the next version will notify the user.

@eightarmedpet This is normal if the automate-eGPU.kext is still in the kernel cache. Uninstalling (SIP disabled) isn't enough, the system must be rebooted at least once or twice also, without keeping the eGPU plugged in. After that, it should not happen again anymore. If it does, please check that you don't have other solution's kexts in /Library/Extensions/ folder.

EDIT: the "Uninstall" option doesn't uninstall Nvidia web drivers, you have to do it by yourself. With TB3 and Nvidia eGPU (without booting from EFI), it's possible that system will crash anyway if some Nvidia drivers get loaded.

automate-eGPU EFIapple_set_os.efi
--
2018 13" MacBook Pro + Radeon [email protected] + Win10 1809


ReplyQuote
pengus77
(@pengus77)
Active Member
Joined: 1 year ago
 

Hi @goalque

I think I found a little bug that really isn't bothering that much, just a heads up. Basically when booting without EFI on battery the system works perfectly fine unless I connect a TB device (say, a TB->ETH adapter). At that point the system doesn't go to sleep anymore when closing the lid. If I unplug the adapter and close the lid, the system goes to sleep normally. I have the hybrid kext installed.

Also, when the external eGPU-connected display is set as primary, the menubar appears both on the internal and the external display at the same time. Again, not bothering, just reporting 🙂

Anyway, all is still perfectly smooth on this side 😉

MacBook Pro Mid-2014 - GT750M - Sonnet eGFX Breakaway Box TB3 with TB2 adapter - NVidia GTX 1080


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

@pengus77 I don't think this has anything to do with the software installation, 750M model has many issues itself due to the Nvidia dGPU. Nvidia has to solve them, the web driver isn't designed for eGPUs, it's a beta driver for dGPU.

Uncheck "Mirror Displays". Thanks!

automate-eGPU EFIapple_set_os.efi
--
2018 13" MacBook Pro + Radeon [email protected] + Win10 1809


ReplyQuote
pengus77
(@pengus77)
Active Member
Joined: 1 year ago
 

I don't use Mirror Displays and it's never been checked 🙂
Anyway maybe it's because I'm using the old drivers to enable OpenGL / Metal on the external screen. Will sit and wait, maybe it'll solve itself 🙂 

Edit: Nevermind, solved the double-menubar. Had set the "Displays have multiple spaces" option and totally forgot about it.

What about the no-sleep-when-closing-lid-if-tb-dev-attached?

MacBook Pro Mid-2014 - GT750M - Sonnet eGFX Breakaway Box TB3 with TB2 adapter - NVidia GTX 1080


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

ReplyQuote
pengus77
(@pengus77)
Active Member
Joined: 1 year ago
 

Aye, already went and done all of that. The point is that it doesn't sleep when closing the lid ONLY if there's a TB device attached (not the eGPU, that's expected). When the device is removed the laptop sleeps like a baby. This has started to happen after installing this software in hybrid mode. Again, not a huge issue, but seems like something worth reporting 🙂

MacBook Pro Mid-2014 - GT750M - Sonnet eGFX Breakaway Box TB3 with TB2 adapter - NVidia GTX 1080


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

Maybe, due to the web driver or some other bug, macOS is thinking that there is an external display connected through the TB2 port.

https://support.apple.com/en-us/ht201834

What if you uninstall the web driver? (normal boot, not via EFI, and the eGPU disconnected).

automate-eGPU EFIapple_set_os.efi
--
2018 13" MacBook Pro + Radeon [email protected] + Win10 1809


ReplyQuote
pengus77
(@pengus77)
Active Member
Joined: 1 year ago
 

Ok, I'll try that leaving the codeless kext installed. I've always had the webdriver installed because of some cuda code I have to write every now and then, so I can assure you that the webdriver alone doesn't cause the bug I reported. I'll let you know the test results later today when I'm done with work 🙂

MacBook Pro Mid-2014 - GT750M - Sonnet eGFX Breakaway Box TB3 with TB2 adapter - NVidia GTX 1080


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

Okay, the purpose of the codeless kext is just to activate NVDAStartupWeb.kext when there is an Nvidia eGPU present, and make the driver IOPCITunnelCompatible (because Nvidia hasn't done so).

I would like to to get rid of this codeless automate-eGPU.kext completely without modifying binaries/plists. If someone has an idea, let me know. "Pure EFI" can do this, but I would prefer an approach without SSDT table dropping.

automate-eGPU EFIapple_set_os.efi
--
2018 13" MacBook Pro + Radeon [email protected] + Win10 1809


itsage liked
ReplyQuote
pengus77
(@pengus77)
Active Member
Joined: 1 year ago
 

Just for pure information: the codeless automate-eGPU.kext should be installed in the main /System/Library/Extensions or is designed to stay on the USB target chosen by the installer?

MacBook Pro Mid-2014 - GT750M - Sonnet eGFX Breakaway Box TB3 with TB2 adapter - NVidia GTX 1080


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

Nope, the installer puts it under /Library/Extensions. The installer deletes it and rebuilds caches when you choose "Uninstall" (no matter if USB/internal disk).

automate-eGPU EFIapple_set_os.efi
--
2018 13" MacBook Pro + Radeon [email protected] + Win10 1809


ReplyQuote
psonice
(@psonice)
Estimable Member
Joined: 2 years ago
 

@goalque nearly but not quite working on iMac (2014 with Radeon 295x [edit: plus 1080ti in sonnet 550 over tb2]). Setup:

- held R on boot, restored macOS 10.13.5
- removed nvdaegpu kext (which was still in extensions)
- updated Nvidia drivers
- unplugged everything

i then installed your tools on an external USB drive with the GPU connected, disconnected after GPU detected. Installation went fine. Booted via EFI from then on. Results:

- Boot with eGPU connected: black internal display, severe lag

- attach EGPU after login, logout and back in: corrupt internal display with visible mouse, external display connected to eGPU working fine 

I tried variations with the DisplayPort cable attached later, no joy

Also tried setting skipdata in the plist, no difference  tried disabling forceIntegrated too as there’s no integrated GPU in this iMac, no difference.

Anything else you want me to try? And is it worth trying pure mode?

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


goalque liked
ReplyQuote
philw
(@philw)
Trusted Member
Joined: 2 years ago
 

@psonice similar result on my 2014 27" - black screens and basically no success with hybrid...

Given up on all my Macs...but successfully running: Gigabyte Designare Z390, Core i9-9900K, 64GB RAM, 2x Internal GTX 1080TI, 2x GTX 1070 eGPU (Sonnet eGFX)


goalque and psonice liked
ReplyQuote
itsage
(@itsage)
Famed Member Admin
Joined: 3 years ago
 

If you experience black screen, check your Login items. Check and remove some items the folders, "LaunchAgents" and "LaunchDaemons" in /Library as well as ~/Library.

Best ultrabooks for eGPU use

eGPU enclosure buying guide

109 external GPU build guides


psonice and goalque liked
ReplyQuote
goalque
(@goalque)
Noble Member Admin
Joined: 3 years ago
 

Thanks for the first iMac reports. This was a bit expected. Does it have Intel iGPU at all? If not, then there is no workaround atm due to Nvidia eGPU & AMD dGPU framebuffer conflict. Furthermore, your dGPU may appear differently in ioreg than with MBPs. Pls type "ioreg -l > ~/Desktop/ioreg.txt" and search for the block by the dGPU device id.

automate-eGPU EFIapple_set_os.efi
--
2018 13" MacBook Pro + Radeon [email protected] + Win10 1809


itsage liked
ReplyQuote
philw
(@philw)
Trusted Member
Joined: 2 years ago
 

@goalque No Intel, just AMD Radeon R9 M290X 🙂

Given up on all my Macs...but successfully running: Gigabyte Designare Z390, Core i9-9900K, 64GB RAM, 2x Internal GTX 1080TI, 2x GTX 1070 eGPU (Sonnet eGFX)


ReplyQuote
goalque
(@goalque)
Noble Member Admin
Joined: 3 years ago
 
Posted by: psonice

- attach EGPU after login, logout and back in: corrupt internal display with visible mouse, external display connected to eGPU working fine 

This was good news. The eGPU monitor as the primary (the dock visible)? If so, you can use SwitchResX's internal screen disabling feature to get rid of UI lag.

If you disconnect the eGPU display, is it possible to use CUDA-Z or other GPGPU-oriented apps?

automate-eGPU EFIapple_set_os.efi
--
2018 13" MacBook Pro + Radeon [email protected] + Win10 1809


ReplyQuote
psonice
(@psonice)
Estimable Member
Joined: 2 years ago
 
Posted by: goalque

Does it have Intel iGPU at all? If not, then there is no workaround atm due to Nvidia eGPU & AMD dGPU framebuffer conflict. Furthermore, your dGPU may appear differently in ioreg than with MBPs. Pls type "ioreg -l > ~/Desktop/ioreg.txt" and search for the block by the dGPU device id.

No intel GPU. 

Took a look in ioreg. The device ID according to system profiler is 0x6938. Searching for that gives no direct matches but various strings beginning with that number. Items that match:

AMD9000ControllerWrangler
AMDRadeonX4000_AMDRadeonHWServicesVI
AMD9000Controller
AMDRadeonX4000_AMDTongaGraphicsAccelerator

There's also some serious WTF grade oddness going on now. I have the external display connected to the iMac directly instead of the eGPU (which is currently disconnected). Well, the mac fires up OK with both monitors "working", but it's now detecting the internal (27"/5K) display as 18". Wat. And it thinks it has an 8:9 aspect ratio and offers 800x900 resolution. It's a bit stretched to say the least...

Don't have SwitchRes but ResExtreme reports it as 18" with odd resolutions too.

Will reboot without EFI and see if that still happens.

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


ReplyQuote
philw
(@philw)
Trusted Member
Joined: 2 years ago
 

I wish Apple would hurry up with whatever the new Mac Pro is.... I feel like iMac and C4D / Cuda rendering are destined to be troublesome 🙂 unless I ditch all my GPU renderers and spend the cash on processor cores for Arnold instead...

Given up on all my Macs...but successfully running: Gigabyte Designare Z390, Core i9-9900K, 64GB RAM, 2x Internal GTX 1080TI, 2x GTX 1070 eGPU (Sonnet eGFX)


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

@psonice iMac's Thunderbolt ports are wired to AMD dGPU - as with the nMP, I suppose you cannot use any of them normally, while the Nvidia eGPU is plugged in.

There should be matches: ioreg -l | grep 0x6938 (or 0x69381002). 1002 is vendor id. Would be interesting to see the result of this command:

ioreg -n GFX0@0 | sed -E '/{/,/\| }$/!d' | grep \"device-id\" | sed 's/.*\<\(.*\)\>.*/\1/' | sed -E 's/^(.{2})(.{2}).*$/\2\1/'

 

automate-eGPU EFIapple_set_os.efi
--
2018 13" MacBook Pro + Radeon [email protected] + Win10 1809


ReplyQuote
psonice
(@psonice)
Estimable Member
Joined: 2 years ago
 
Posted by: goalque

Would be interesting to see the result of this command:

ioreg -n GFX0@0 | sed -E '/{/,/\| }$/!d' | grep \"device-id\" | sed 's/.*\<\(.*\)\>.*/\1/' | sed -E 's/^(.{2})(.{2}).*$/\2\1/'

 

That's a lot of of regex 😉 Output of that: 6938

And yes, there are matches for 0x69381002.

What do you think the block is here? It's clearly workable somehow as it works fine under 10.13.3 with the old enabling script, just not with Apple's changes with 10.13.4+. Is the AMD/Nvidia framebuffer conflict new in 10.13.4?

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


ReplyQuote
 of  19