SIP is permanently disabled, it needs to be for the patches to work correctly. Not sure what's causing the black display after sleep.
Oh, alright. I was just wondering about it. Thank you!
I still have those bugs on and off.
Same here..
SIP is permanently disabled, it needs to be for the patches to work correctly. Not sure what's causing the black display after sleep.
I still have those bugs on and off.
Guess the dark artefacts don't show on a dark background try again on a light background, they are still there.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.
SIP is permanently disabled, it needs to be for the patches to work correctly. Not sure what's causing the black display after sleep.
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.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.
Actually @parrotgeek1 wrote most of it. I'm not sure if he wants to share the source code or not, but I'll ask him.That's awesome. Did you write it? Is there source code available somewhere?
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 successfully installed macOS Mojave PB3 on my MacBook mid 2009 only issues not getting the update for PB4 with the beta access utility
Yes small updates like that come through fine. The OS updates (from beta to beta) are problematic though.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.)
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.Yes small updates like that come through fine. The OS updates (from beta to beta) are problematic though.
Yes I did when beta5 came outIndeed, 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.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?
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!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.
Oh, great. I'll add that back, then.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!
Right, but way better... almost not noticable any more. But we´re in beta... ;-)Guess the dark artefacts don't show on a dark background try again on a light background, they are still there.
I hope this isn't a repeat answer, but I had this happen on the same machine. Reinstall the Legacy Sound from patch updater, and reboot.Sound on MacBook Pro Late 2011 13inch 2,4 GHz i5 no longer working after updating to Public Beta 4. Only AirPlay working but no internal speakersView attachment 774056
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.Right, but way better... almost not noticable any more. But we´re in beta... ;-)
correct, I did not notice itYes 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.
1.1.1 - 8/2/2018
- Fixed some minor glitches with the installer
- Added some extra features to the installer
Actually @parrotgeek1 wrote most of it. I'm not sure if he wants to share the source code or not, but I'll ask him.
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, @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.
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.)