Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problem with reporting Intel registers, v1.8e #14

Open
ahmed-ais opened this issue Oct 12, 2016 · 2 comments
Open

Problem with reporting Intel registers, v1.8e #14

ahmed-ais opened this issue Oct 12, 2016 · 2 comments

Comments

@ahmed-ais
Copy link

ahmed-ais commented Oct 12, 2016

For some reason, REPORT_INTEL_REGS is set to 0 in AppleIntelInfo.h rendering the logIntelRegs setting in Info.plist useless. Overriding this value allow dumping the registers but with wrong values (0xffffffff). I've seen your words about this issue for Skylake but I'm running on Haswell and have the issue under both 10.11 and 10.12.

@ahmed-ais ahmed-ais changed the title Reporting Intel Registers is disabled Problem with reporting Intel registers, v1.8e Oct 12, 2016
@Piker-Alpha
Copy link
Owner

Yes. To stop it from reporting errors/useless data.

If you want it, then you need to change the value in the header file and compile the kext yourself. Problem solved. I think. No?

@ahmed-ais
Copy link
Author

Thanks but I was able to figure this out and I got 0xffffffff registers problem mentioned in the issue post above. The weird thing is that even older versions of the kext that used to return correct registers values (back to v1.0) now fail to return anything but 0xffffffff. So I believe it's not something in your code that cases it but rather a problem with graphic driver maybe. Thanks for the support.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants