so can I delete that agent with clean my Mac?Out of curiosity, does the com.DD1.SIPLD.plist launch agent disable SIP if needed? Not sure what benefit checking csrutil status would be if SIP went active and disabled legacy USB support.
so can I delete that agent with clean my Mac?Out of curiosity, does the com.DD1.SIPLD.plist launch agent disable SIP if needed? Not sure what benefit checking csrutil status would be if SIP went active and disabled legacy USB support.
id be more worried about using clean my Mac lolso can I delete that agent with clean my Mac?
I believe I asked dosdude1 this very same question. Yes, it is safe to delete the launch agent/daemon.so can I delete that agent with clean my Mac?
no, it wouldn't. most of its code is copied and pasted from Apple's El Capitan IOUSBFamily, which is copyrighted. Also, as the developer, I would like to be in control of who signs my own kext.I am aware that it has to be checked for malicious intent. I am sure the legacyUSB.kext would be ok.
Really? So you prefer this ongoing battle with SIP because you don't like the idea of someone else getting Apple to sign the USB kext? There is nothing in Apple's guidelines that suggest getting it signed would be an issue. At worst, Apple could decline.no, it wouldn't. most of its code is copied and pasted from Apple's El Capitan IOUSBFamily, which is copyrighted. Also, as the developer, I would like to be in control of who signs my own kext.
Alright. You can try it.Really? So you prefer this ongoing battle with SIP because you don't like the idea of someone else getting Apple to sign the USB kext? There is nothing in Apple's guidelines that suggest getting it signed would be an issue. At worst, Apple could decline.
I do not know either. But it seems to be a problem. I actually run sip enabled except for kext.Alright. You can try it.
This whole thing is really weird to me because I have NEVER had SIP re-enable itself on any of my 3 computers. How is this happening to people?
I do not know either. But it seems to be a problem. I actually run sip enabled except for kext.
It is annoying that Apple seems to actively prevent machines capable of running (and often beneficially) macOS updates.
Did you use iperf to test your wifi transfer rates? The 5,2 I have here is getting about 218Mb/s on the 5GHz channel and 92Mb/s on the 2.4GHz channel. (with the system stating connection rates of 300 and 145 respectively).i was wondering if there is a fix for the wifi on macbook 5,2 mid 2009 download is slow...i have the latest build...i saw different solutions but i dont know what one has actually worked
no i should try it is it an app?Did you use iperf to test your wifi transfer rates? The 5,2 I have here is getting about 218Mb/s on the 5GHz channel and 92Mb/s on the 2.4GHz channel. (with the system stating connection rates of 300 and 145 respectively).
You'll have to have another system (mac or windows box) to test against (ideally, you'd want that system to be hardwired over ethernet, so you're getting a good indication of your macbook's wifi speeds).no i should try it is it an app?
Ok so now with the latest dev beta available a couple of days ago I cannot get it to appear in the App Store Updates.
I used CZO's patch last time and it was fine, but now I see that SIP is enabled, so went to start from my recovery partition but I now get the 'no system folder' sign so unable to boot to recovery partition in order to disable SIP.
So what next?
Do you still have one of dosdude1's usb installers kicking around? Re-patch your recovery partition.Well i am surprised that SIP was enabled, i could not have downloaded previous beta updates had it been enabled so i don't understand why its status had changed.
The recovery partition was patched when i first installed Sierra months ago.
I am fairly sure this issue has been covered in this thread. Easiest way is to boot from your patched USB Sierra installer and run the post-install tool again.Ok so now with the latest dev beta available a couple of days ago I cannot get it to appear in the App Store Updates.
I used CZO's patch last time and it was fine, but now I see that SIP is enabled, so went to start from my recovery partition but I now get the 'no system folder' sign so unable to boot to recovery partition in order to disable SIP.
So what next?
I assume you are talking about your software update patch? I do not use it currently but might switch. Thanks for the warning!SIP also prevents VMM injection to CPU flags, that is neccessary to enable software updates
Yeah rebooted to original install usb, repatched recovery partition, booted to recovery partition, disabled SIP, booted back to Sierra, still no updates available through App Store.Do you still have one of dosdude1's usb installers kicking around? Re-patch your recovery partition.
(always a good idea to keep one of those available).
Have you used something to enable unsupported computer to receive updates? I think easiest method is now the patch by czo. I don't know how it works so it may not have surivived when SIP was re-enabled.Yeah rebooted to original install usb, repatched recovery partition, booted to recovery partition, disabled SIP, booted back to Sierra, still no updates available through App Store.
Have you used something to enable unsupported computer to receive updates? I think easiest method is now the patch by czo. I don't know how it works so it may not have surivived when SIP was re-enabled.