I don't know the answers for sure but some things you can try:After disabling SIP, remounting / as read-write so you can copy the new kernel into /System/Library/Kernels with something like "mount -u -w /", which worked for meRegarding the second error, it loks like the SDK you're using is different from the OS you're trying to install the extension into. Double checkin your build settings for your kext, and perhaps some verbose output from kextutil would help. Try adding -v 6 to the command line.Neal
nealsid
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Last seen
User for
Post
Replies
Boosts
Views
Activity
Yeah, they do come from the kernel, at least as far as I can tell. Thank you, Quinn, I appreciate the information. Actually, having a predicate on "DK:" at the beginning would also seem to work well enough. Maybe after I get some more experience, I'll file that enhancement request, but as this is my first time writing a driver I'm not sure if what I need, or think I need, would be useful to others.
Thanks! I've been checking regularly, and still no luck. Worked around it with the "dk" boot flag for now, and it's just for a personal project, so it's not that big of a deal. I guess I got lucky with my first request, which was approved in a few days.
After a bit more experimenting, I found that my test dx/dy values are not large enough or need to be shifted left some amount, but the test program works as expected.
After a bit more experimenting, I found that my test dx/dy values are not large enough or need to be shifted left some amount, but the test program works as expected.
It doesn’t appear that there is, but, if you’re interested in workarounds, you can use the boot arg “dk=0x8001”, which disables DriverKit entitlement checks.
Seems sort of reasonable, but those are valuable commodities!
Sorry, it's been a few days since I did this, but I should mention that I created an App Id with MusicKit enabled, and am signing the app with a provisioning profile created for that App Id.
Ha! That fixed it. How embarrassing. However, I'd expected a dialogue presented by the macOS or MusicKit asking for access to the Media library, similar to iOS, and it doesn't seem usable to ship something that requires the user to add the app to that list manually. Thank you!
Yeah, I was not using large enough dx/dy values as I should have been.