Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
Nice small fix: The build ..347e removed the context menu artifact bug (see pictures).
Update from dev-4 to dev-5 went through, but I had to restart manually due to progress bar hanging near the end.
Guess the dark artefacts don't show on a dark background try again on a light background, they are still there.
 
Just curious, how do you permanently disable SIP? Are you modifying the operating system rather than the variable in NVRAM? It would be cool to change SIP settings on a volume by volume basis.
It's a kext within the OS (/Library/Extensions/SIPManager.kext). If the kext is removed and kextache is rebuilt, SIP will work like normal. It is NOT recommended to remove this on a patched system, as things will not work correctly with SIP enabled.
 
It's a kext within the OS (/Library/Extensions/SIPManager.kext). If the kext is removed and kextache is rebuilt, SIP will work like normal. It is NOT recommended to remove this on a patched system, as things will not work correctly with SIP enabled.

I know totally disabling SIP is the tested configuration, but SIP has a few other knobs. Of the following flags which ones are critical for patcher in your opinion:
  • csrutil enable --no-internal
  • csrutil enable --without kext
  • csrutil enable --without fs
  • csrutil enable --without debug
  • csrutil enable --without dtrace
  • csrutil enable --without nvram
I suppose kext and fs are critical. For your patcher, could one get away with simply excluding those features?
 
I successfully installed macOS Mojave PB3 on my MacBook mid 2009 only issues not getting the update for PB4 with the beta access utility
I had this problem on my 2010 MacBook, my solution was to remake the installer with PB4 and then install from the patched USB installer. After that, I was able to get the updates from the Apple servers (had an update for Xcode Command Line tools that wasn't there before.)
 
I had this problem on my 2010 MacBook, my solution was to remake the installer with PB4 and then install from the patched USB installer. After that, I was able to get the updates from the Apple servers (had an update for Xcode Command Line tools that wasn't there before.)
Yes small updates like that come through fine. The OS updates (from beta to beta) are problematic though.
 
  • Like
Reactions: TimothyR734
Yes small updates like that come through fine. The OS updates (from beta to beta) are problematic though.
Indeed, I haven't had the chance to update through the built in software update service, but I imagine you could boot to the USB installer in between update reboots and patch it every time so it can finish the update, but I'll have to wait until beta 6 comes out to try this.

Has anyone else done an OTA update this way?
 
Indeed, I haven't had the chance to update through the built in software update service, but I imagine you could boot to the USB installer in between update reboots and patch it every time so it can finish the update, but I'll have to wait until beta 6 comes out to try this.

Has anyone else done an OTA update this way?
Yes I did when beta5 came out
 
  • Like
Reactions: jackluke
Indeed, I haven't had the chance to update through the built in software update service, but I imagine you could boot to the USB installer in between update reboots and patch it every time so it can finish the update, but I'll have to wait until beta 6 comes out to try this.

Has anyone else done an OTA update this way?
Yes that’s pretty much standard procedure for system updates. Worked for me once from db3 to db4.
 
  • Like
Reactions: TimothyR734
I had this problem on my 2008. Had to manually copy the kexts from the High Sierra version of the patch, and that worked.

Edit: This would be AppleHDA.kext and IOAudioFamily.kext from El Capitan, to be specific. Those worked on High Sierra, and appear to work fine on Mojave as well.
Confirming that this worked for me to get volume control working. Grabbed the files from the High Sierra patcher and manually installed them. @dosdude1 maybe put this back in for iMac 7,1 and 8,1? Thanks!
 
Guess the dark artefacts don't show on a dark background try again on a light background, they are still there.
Right, but way better... almost not noticable any more. But we´re in beta... ;-)
 

Attachments

  • Screenshot 2018-08-03 at 06.43.22.png
    Screenshot 2018-08-03 at 06.43.22.png
    256.8 KB · Views: 213
Right, but way better... almost not noticable any more. But we´re in beta... ;-)
Yes but in your original post about this you suggested they were gone, I was merely pointing out they were still there, and I know we are in Beta. The thing to find out is if those with supported machines have the same issue.
 
  • Like
Reactions: TimothyR734
An update to the macOS Mojave Patcher has been released. These are the changes.

Code:
1.1.1 - 8/2/2018

- Fixed some minor glitches with the installer
- Added some extra features to the installer
 
I noticed @parrotgeek1 also wrote for Legacy Nvidia Tesla the very useful "NDRVShim.kext" instead replacing "IOGraphicsFamily.kext", as known less you replace more stability you get.

However, it seems like NDRVShim.kext just provides a stub function that doesn't actually do anything. This causes problems. So, replacing the IONDRVSupport.kext and IOGraphicsFamily.kext might actually be a better solution.

Or perhaps somebody can write an equivalent to NDRVShim that provides the function that IONDRVSupport needs in IOGraphicsFamily, so that only IONDRVSupport needs to be replaced, rather than both.

See my post here.

Anyways, my main point of these last few posts. @parrotgeek1 and @dosdude1, are you willing to release source code for the various things you've contributed here? Namely the patcher app, SIP kext and NDRVShim? For projects like these, it's always best if anyone can understand and make contributions to each part! And there's no reason I can see to keep things closed-source. Thank you in advance.

(Edited for clarity.)
 
Last edited:
However, it seems like NDRVShim.kext just provides a stub function that doesn't actually do anything. This causes problems. So, replacing the IONDRVSupport.kext and IOGraphicsFamily.kext might actually be a better solution.

Or perhaps somebody can write an equivalent to NDRVShim that provides the function that IONDRVSupport needs in IOGraphicsFamily, so that only IONDRVSupport needs to be replaced, rather than both.

See my post here.

Anyways, @parrotgeek1, are you willing to release source code for the various things you've contributed here? Namely the SIP kext and NDRVShim? Thank you in advance.

I knew your post, infact in manual patching I mainly followed your tips, tried few days ago the NDRVShim and looks working fine, maybe just an impression but it seems that NVDAStartup.kext work even keeping the untouched Mojave one.

edit:
I meant without using NVDAStartup.kext

edit2:
My mistake, legacy IONDRVSupport.kext and IOGraphicsFamily.kext are both mandatory without the NDRVShim.kext
 
Last edited:
However, it seems like NDRVShim.kext just provides a stub function that doesn't actually do anything. This causes problems. So, replacing the IONDRVSupport.kext and IOGraphicsFamily.kext might actually be a better solution.

Or perhaps somebody can write an equivalent to NDRVShim that provides the function that IONDRVSupport needs in IOGraphicsFamily, so that only IONDRVSupport needs to be replaced, rather than both.

See my post here.

Anyways, my main point of these last few posts. @parrotgeek1 and @dosdude1, are you willing to release source code for the various things you've contributed here? Namely the patcher app, SIP kext and NDRVShim? For projects like these, it's always best if anyone can understand and make contributions to each part! And there's no reason I can see to keep things closed-source. Thank you in advance.

(Edited for clarity.)

Many components of the patcher app can be freely viewed in the app’s contents but not all components.
 
  • Like
Reactions: TimothyR734
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.