How do I go about troubleshooting this? So, the place to start is actually with this log message: eventually ends with provider entitlements check failed The log message is the final, generic, error message printed by IOUserService when the entitlement check process fails. A few things to understand about what this tells you about what HASN'T gone wrong: Basic entitlement validation happens outside the kernel well before this point. So getting to this point means that your DEXT is at least somewhat coherently signed, even if it doesn't actually work. IOKit passive matching happens at the same time as entitlement checking (just before actually), so this message means that either your passive match failed or your entitlement configuration was wrong. So, the next step here is to actually take a closer look at this logging: In the logs I see the matching log entry for my driver, and it goes through some setup that mentions my driver and some entries that do not. Focusing on the entitlement checking side, each IOK
Topic:
App & System Services
SubTopic:
Drivers
Tags: