I have USB DriverKit driver. When I use the log command below to get log, there is logs from my driver on my own M-series MacBook where the driver is built using developer account.
log stream | grep CompanyName
But on other mac like (M-series) Mac Mini, there is no log captured from driver though the driver is communicating with the machine correctly. The only log captured are from MacOS regarding CompanyName driver status/unload/load. The MacOS is Sonoma 14.7.2 and 14.7.3.
Please advise on how to get log from driver since writing to files is not allowed in DriverKit. I need logs to troubleshoot on Mac Mini.
Thanks.
I have USB DriverKit driver. When I use the log command below to get log, there is logs from my driver on my own M-series MacBook where the driver is built using developer account.
log stream | grep CompanyName
But on other mac like (M-series) Mac Mini, there is no log captured from driver though the driver is communicating with the machine correctly. The only log captured are from MacOS regarding CompanyName driver status/unload/load. The MacOS is Sonoma 14.7.2 and 14.7.3.
Please advise on how to get log from driver since writing to files is not allowed in DriverKit. I need logs to troubleshoot on Mac Mini.
I don't know exactly what's going on, but I do have a few things you can look and check:
-
Check out "Your Friend the System Log" for some general guidance on using the system log more effectively.
-
Make sure you're doing what this post recommends.
-
As a quick test, trying running "sudo log" instead of just "log". It's possible that a difference in account type (user vs. admin) is causing the data to be filtered.
-
Try grep-ing for something that's specifically in your log message content, not "metadata" (like your process name or bundle ID). Again, the filtering behavior can be tricky to predict but the message content is what's least likely to be filtered.
-
Collect a sysdiagnose immediately after testing and see what was actually logged. You may also want to install "Sysdiagnose (Unredacted)" to cover every possibility. If nothing is showing up in the sysdiagnose, then my guess is that either your specific build isn't actually logging or something specific to that machine is blocking it.
__
Kevin Elliott
DTS Engineer, CoreOS/Hardware