Kryptonite: TB1/2 Mac eGPU Support with FileVault, SIP, and ART Enabled
Thanks for the build guide, helped me a lot switching from automate-eGPU EFI to this great solution. But there should be some instructions how to edit the config.plist to implement the DSDT.aml into the boot process. I found this info in the reply to your post by @mac_editor here on page 4 of this thread.
Thanks again for the great work to all of you, it makes using an old 2015 15" Macbook Pro (without dGPU) much more fun!
The experience on Mac OS is seamless (plug and use) with SIP and FV on. Performance are great on the card.
Big Sur 11.5.
Macbook Air 2017.
AMD Radeon RX570 Sapphire Nitro +
One issue I am having is error 12 when using the EGPU on windows. Which DSDT override guide should I follow for this relatively new software?
Many thanks for this wonderful software. My set up was pretty much unusable up until I tried Kryptonite!
I'm a little new to this stuff & I've been trying to piece together the necessary modifications for info.plist. I got ProperTree & followed the rest of the directions to install Kryptonite. I eventually figured out AMDLegacySupport.kext needed to go into EFI/OC/Kexts. I believe I have the proper boot args (note I am not on a beta version of MacOS) and Kernel dictionary values. My confusion is happening with what I need to put into ACPI for "Delete" & "Patch" and whether or not SSDT-EC.aml is a file I have to create. I attached a picture of my info.plist.
- I disabled FireVault, GateKeeper, SecureBoot, SIP, & allowed booting from external media. Please let me know if any of that was unnecessary and/or whether any of those can be restored when installation is complete... "Disable T2 Security" wasn't very specific.
- DeviceID:0x73af for PowerColor Red Devil Radeon RX 6900 XT Ultimate
config.plist section that I edited as per instructions under NVRAM --> Add --> 74C436... --> boot-args --> (new siblings created for: krygpu=AMD (string), krytbtv=2 (tried as string and number), timeout=0)
That’s wrong. Everything needs to be in the boot-args string.
Follow the installation instructions to bless your volume again, which should hopefully fix the OpenCore label in boot selector (this is only cosmetic).
@mac_editor This may be a stupid question, but I see jason_gouw is on Big Sur & using the krytbtv boot-arg when the Readme for Kryptonite says that's only needed for Catalina and earlier. Is it needed for Big Sur as well? If so, I'll open an issue/pull request for the Readme to be updated & then I have more potentially stupid questions: is 3 a valid value despite the Readme saying only 1 & 2 are valid values? Do Thunderbolt 3 macs need krytbtv at all?
@mac_editor, I'm on the step where I need to reinstall macOS on top of my system. I've already uninstalled purge wrangler. I went ahead and did that reinstall, and checked to see if System Integrity Protection was enabled and it was still disabled. I did another reinstall and it wasn't disabled at all. I decided to NVRAM reset and that got things to work. Is everything still good up until this point?
Apologies to everyone who has been awaiting responses to their questions here.
the exception of the fact that restarting causes my monitor to go black
Boot screens are not supported on eGPUs (there may be ways but I haven't experimented) if you have FileVault enabled.
@neoplexer Set OpenCore as default boot device and disable it's boot selection menu (see README on Github). Then you can switch disks in macOS itself (OpenCore will not be overridden as long as you don't select disk from Apple Boot Selector/OPT key on boot). However, if you have FileVault enabled, boot screen (where you enter password) will not be visible on display connected to eGPU, so would need the iGPU anyway.
@netcho Windows should technically be unaffected by Kryptonite (which is a kext that can only run on macOS). I'm not sure if OpenCore is causing your issues but that may be so if not using it fixes Windows eGPU issues for you.
@silverscrub See post above yours for reference. Can follow same steps except use DSDT for your own Mac. Otherwise, I may have an alternative in the pipeline for bootcamp but I still need to do some testing there.
DeviceID:0x73af for PowerColor Red Devil Radeon RX 6900 XT Ultimate
This device ID is not supported on macOS - last I checked this GPU is non-functional (unless this has changed with 11.5.x - I don't know).
This may be a stupid question, but I see jason_gouw is on Big Sur & using the krytbtv boot-arg when the Readme for Kryptonite says that's only needed for Catalina and earlier. Is it needed for Big Sur as well?
It doesn't matter for Big Sur and serves a cosmetic purpose in the logs. As you correctly surmise, it is necessary to have for Catalina and older. Regarding the value itself, 1 and 2 are relevant to the patch itself. Inputting anything else would simply skip that patch on Catalina.
I went ahead and did that reinstall, and checked to see if System Integrity Protection was enabled and it was still disabled.
It won't enable itself automatically. Reinstall -> enable SIP (NVRAM reset will do the same) -> check if system boots properly (it will since you reinstalled and everything is clean). So you should be ok now. All that's left is to rest of the steps.
"Desultory reading is delightful, but to be beneficial, our reading must be carefully directed." — Seneca
Author: kryptonite ✧ purge-wrangler ✧ tbt-flash ✧ purge-nvda ✧ set-eGPU
Insights Into macOS Video Editing Performance
Launching Apps on Specific (e)GPUs on macOS
2014 15-inch MacBook Pro 750M
2018 15-inch MacBook Pro
So I'm feeling a bit baffled. I have an early 2011 MacBook Pro 13" + Razer Core X + AMD Sapphire RX 570 I'm trying to get working, without much luck. I've tried,(I think) all the tweaks here, but not really getting anywhere. The eGPU enclosure is recognised and visible in the system report, but never the card.
Running OCLP 0.2.4 (latest) Big Sur + Kryptonite also has the unfortunate side effect of killing my network card when I plug in the eGPU device. I've tried both booting with it connected as well as connecting after, neither seems to work.
Since I can use the eGPU on both my 2019 BP and my 20.04 linux setup, I'm sure there's no fault in the card or enclosure.
I've enabled debug, so can share that plus config.plist, just not sure how on here?
@mac_editor, I saw that making Navi22 GPUs work failed, but I didn't see that the AMDLegacySupport-Navi21XTXHNavi22Ids.kext failed to add the XTXH device ID to the existing drivers. Are you saying that both didn't work & that there's no way to make Navi21XTXH chips work with MacOS till Apple adds support?