Kryptonite: TB1/2 Mac eGPU Support with FileVault, SIP, and ART Enabled
 
Notifications
Clear all

Kryptonite: TB1/2 Mac eGPU Support with FileVault, SIP, and ART Enabled  

 of  22
  RSS

Nicholas
(@nicholas)
New Member
Joined: 7 months ago
 

Will there be any-chance at a later date to disable the on-board graphics .. I see no reason to have them activated if we are all using eGPU .. even now I'm just doing some light work on my MacBook Pro and it sounds like its about to take off .. Honestly 😕 

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

.

ReplyQuote
sparkplug37
(@sparkplug37)
New Member
Joined: 2 years ago
 

Just to say I stumbled upon this new method, as I had been using purge-wrangler before. So whilst rebuilding my Mac Pro 2013 with a fresh copy Big Sur (SIP enabled) I followed your instructions and after a bit of head scratching I added the AMD boot-args to the config.plist file, so the file changed from this:

<key>boot-args</key>
<string></string>

To this:

<key>boot-args</key>
<string>krygpu=AMD</string>

I rebooted and all has been well. Later I changed the timeout setting later and set the partition to boot as default. This has made me able once again to boot my Mac Pro 2013, connected via the eGPU to a dell 5k monitor, without any issues at all, bar the normal Radeon VII fans on sleep etc.

 

Many thanks and so I sent a small donation for your hard work.

 

For others my setup is Mac Pro 2013 10 core , 64GB RAM, Dual D700, 2TB Samsung Evo 970 MVME drive, Core X (Bus 0 via an apple thunderbolt 2/3 adaptor) and Radeon VII.

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

.

ReplyQuote
hahala
(@hahala)
Active Member
Joined: 2 months ago
 

@nicholas, Are you referring to the dGPU? For that, instructions have been added to the github page.

Tbh, I dont think the dGPU is the cause of fans blowing, but your CPU. Perhaps the internal cooling is not working optimal anymore, so you should check the state of your thermal paste or fans for dust.

 

2013 15" MacBook Pro (Nvidia GT750M) [4th,4C,H] + RX 6800 @ 16Gbps-TB2>TB3 (Razer Core X) + macOS 11.4; Win10


Nicholas liked
ReplyQuote
Jason Gouw
(@jason_gouw)
New Member
Joined: 2 months ago
 

@mac_editor, thank you! Also glad you have a way for the appreciative community to donate to your efforts!

 

I primarily using EGPU as a compute engine to help with video rendering times. Would Kryptonite support more than one EGPU? If so, any limit aside from TB bus bandwidth and diminishing returns with each addition EGPU? 

 

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

.

ReplyQuote
mac_editor
(@mac_editor)
Famed Member Moderator
Joined: 4 years ago
 
Posted by: @jason_gouw

I primarily using EGPU as a compute engine to help with video rendering times. Would Kryptonite support more than one EGPU? If so, any limit aside from TB bus bandwidth and diminishing returns with each addition EGPU? 

Kryptonite is only responsible for enabling GPU support on older macs. The functionality and capability is determined by macOS/Apple. I believe macOS supports at most 4 functional eGPUs IIRC. Bandwidth/diminishing returns depend on workload. Before considering multiple GPUs, make sure the apps you use are specifically designed to take advantage of them (example DaVinci Resolve).

 

Author: kryptonitepurge-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]  


PsyPryss liked
ReplyQuote
Jason Gouw
(@jason_gouw)
New Member
Joined: 2 months ago
 

@mac_editor, fantastic! And yep, I am using Davinci Resolve Studio =). 

 

Cheers!

Jason

 

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

.

ReplyQuote
ponqable
(@ponqable)
Active Member
Joined: 3 months ago
 
Posted by: @mac_editor

Also try the OpenCore way but set DisableLinkeditJettison to false in config.

Did so, but wouldn't change anything.

Posted by: @mac_editor

did you check if the lilu and Kryptonite kexts loaded after putting them in Library/Extensions

Yes.

Posted by: @mac_editor

That’s what happens normally on an unpatched system.

Ok, thx. I would guess then that the NVRAM options were unset when I was booting without OC or something..

On a different topic: I found the solution! xD

Short answer: Timing.

I slept some nights over your explanation ("...when you boot with the eGPU plugged in, the patch hasn't taken place and thus non-patched code is executed") and remembered good old times at my last job (🤮) having to trace timing bugs in release mode as they were not reproducible in debug mode.

I realized that - being a precautious (or better overcautious) programmer - I only tested the debug build with debug flags set, meaning I only tested the slow build and wondered why the kext injection would always take place after nvidia initialization 🤦

So, now testing release mode everything works absolutely nicely! (strangely i also don't have to set krytbtv, which i noticed by accident..)

So, if you want to reproduce my (former) issues, just test debug build with debug flags set on a slow machine with an nvidia egpu. As my machine has a 3rd gen i7 and boots from an ssd it apparently does not have to be a particularly slow machine, but the slower the more likely i would say...

But for me: Everything works great now!

Thx dude, your awesome! (especially: deploying a most critical bug fix in under half an hour! Grin 👍)

2012 Mac Mini Server [3rd,4C,Q] + GTX 770 @ 10Gbps-TB1>TB3 (Sonnet Breakaway 550) + macOS 10.15.7 + Win10 (21H1)


PsyPryss liked
ReplyQuote
mac_editor
(@mac_editor)
Famed Member Moderator
Joined: 4 years ago
 
Posted by: @ponqable

(strangely i also don't have to set krytbtv, which i noticed by accident..)

It's not needed for NVIDIA patches and only needed for AMD GPUs when using macOS 10.15 or older. 10.15.1 or newer doesn't need krytbtv.

It was really only conjecture on my part regarding the timing. Good to hear it works for you with the release kexts and kudos for figuring it out. We learn something everyday haha.

Posted by: @ponqable

So, if you want to reproduce my (former) issues, just test debug build with debug flags set on a slow machine with an nvidia egpu. As my machine has a 3rd gen i7 and boots from an ssd it apparently does not have to be a particularly slow machine, but the slower the more likely i would say...

The slowest machine I have is the 2014 15" MBP so I'll test on that but it could be fast enough to not reproduce the problem. At least we know now that timing can be key. Thanks again!

Author: kryptonitepurge-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]  


PsyPryss liked
ReplyQuote
ponqable
(@ponqable)
Active Member
Joined: 3 months ago
 
Posted by: @mac_editor

only needed for AMD GPUs when using macOS 10.15 or older

Ah, ok. So "macOS ≤ 10.15" really means "macos < 10.15.1". I thought "≤" included all of "10.15.X". Also I did not understand that "Provide Thunderbolt NHI version. Required for macOS ≤ 10.15. Must be 1 or 2." only applies to AMD. What does "Thunderbolt NHI" stand for? Google did not help me with that (or i'm dumb).

Posted by: @mac_editor

It was really only conjecture on my part regarding the timing. Good to hear it works for you with the release kexts and kudos for figuring it out. We learn something everyday haha.

Indeed haha! Maybe you could add a short note to "Installation" step 4 first to try out Kryptonite-RELEASE as DEBUG might infer timing issues (i.e. on older macs)..?

Posted by: @mac_editor

The slowest machine I have is the 2014 15" MBP so I'll test on that but it could be fast enough to not reproduce the problem.

I would guess it's slow enough, as my mac mini also has an 2.3 Ghz i7 with 6MB L3 and was upgraded to 16GB DDR3 and 512GB SSD. So it almost exactly matches the 2015 15'' mbp with 2,2 Ghz (i.e. except for the gpu, which is fixed by your great work as I'm now able to upgrade the GPU to nearly open end :D)

Posted by: @mac_editor

At least we know now that timing can be key. Thanks again!

I'm just happy to be able to help and contribute a small part to your work as i do benefit a lot from that: For the current years I really don't have the money to spend for new hardware, so being able to maximize the lifetime of my belongings is really worth quite a lot of money I just don't have.

I just hope small donations like mine stack up on your end because I really do appreciate your practice of free software, seeing that not many contributors will or can invest their time in such manner.

But you do and that's awesome!

2012 Mac Mini Server [3rd,4C,Q] + GTX 770 @ 10Gbps-TB1>TB3 (Sonnet Breakaway 550) + macOS 10.15.7 + Win10 (21H1)


ReplyQuote
mac_editor
(@mac_editor)
Famed Member Moderator
Joined: 4 years ago
 
Posted by: @ponqable

What does "Thunderbolt NHI" stand for?

Thunderbolt Native Host Interface I believe. You can see Thunderbolt NHI device(s) in ioregistry output (ioreg). This is in reference to the host thunderbolt controller.

Posted by: @ponqable

Maybe you could add a short note to "Installation" step 4 first to try out Kryptonite -RELEASE as DEBUG might infer timing issues (i.e. on older macs)..?

The installation instructions already say to use the RELEASE version, and I already added a note regarding the debug kext issue on slower machines.

Posted by: @ponqable

I'm just happy to be able to help and contribute a small part to your work as i do benefit a lot from that: For the current years I really don't have the money to spend for new hardware, so being able to maximize the lifetime of my belongings is really worth quite a lot of money I just don't have.

I just hope small donations like mine stack up on your end because I really do appreciate your practice of free software, seeing that not many contributors will or can invest their time in such manner.

But you do and that's awesome!

Thank you for the help and kind words! I enjoy this stuff so don't feel the time sink.

I started off on egpu.io as a typical user trying to get eGPU working on my system too. At the time, automate-eGPU.sh was the way to go for eGPU support on Macs. The script was open source and as I used it, I became curious about how it all worked. And so my journey started, and here we are. I've kept everything I build open source/free to allow for others to dive in, learn, and contribute in the same spirit.

Author: kryptonitepurge-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]  


ponqable and PsyPryss liked
ReplyQuote
 of  22