Jump to content

Haswell early reboot, Mavericks, locked MSRs, and HP Envy 15-J063CL (i7-4700MQ)

RehabMan

By RehabMan,
in OSx86 10.9 (Mavericks)

 Share
469 posts in this topic

Recommended Posts

RehabMan
RehabMan
Posted
  • Author
Posted

I made several tests without success;

 

i54670k,GAZ87N, CPU bios settings (EIST and states) Auto/Disable/Enabled, Clover2352, KernelPm true, SMBios MacPro5,1,4,1,iMac14,2,13,2, no states between 8-34 only turbo states...

 

I don't understand where I wrong...

Most Gigabyte boards are not MSR locked, so no need for replacing the kernel or KernelPm.

 

No states between idle and nominal appears to be normal for xcpm. It is that way on my MacBookAir6,2. It is that way on real iMacs (haswell or ivy), so it appears it is intentional. On a desktop, jumping from idle -> nominal is not an issue. And it appears Apple doesn't believe it is an issue on laptops either.

Whether it can operate normally via Chameleon on Ivy Bridge?

What is the question?

Link to comment
Share on other sites
giacomoleopardo
giacomoleopardo
Posted
Posted

Hey RehabMan, I'm getting a little confused, here.

My specs

ASUS Z9PE-D8 WS socket 2011, chipset Intel C602

Dual CPU Xeon E5-2687W

Mountain Lion 10.8.5 (including supplemental update)

 

I'd like to try your 10.8.5 kernel patch + patched AppleIntelCPUPowerManagement.kext. Does that make any sense for this rig?

How can I apply the 10.8.5 patch to the native 10.8.5 kernel?

Link to comment
Share on other sites
RehabMan
RehabMan
Posted
  • Author
Posted

Hey RehabMan, I'm getting a little confused, here.

My specs

ASUS Z9PE-D8 WS socket 2011, chipset Intel C602

Dual CPU Xeon E5-2687W

Mountain Lion 10.8.5 (including supplemental update)

 

I'd like to try your 10.8.5 kernel patch + patched AppleIntelCPUPowerManagement.kext. Does that make any sense for this rig?

How can I apply the 10.8.5 patch to the native 10.8.5 kernel?

I doubt it, but you could always try. I don't think anyone knows the secret sauce for LGA2011 PM. You will probably have to wait until the new MacPro is out and we see what's changed/what is present in the new MacPro ioreg.

Can work normally on Ivy Bridge?My question is how to settings my Ivy Desktop to work speedstep and SSDT?

I don't know do you understand me?

For Ivy Bridge, the kernel does not use xpcm by default (even on real Apple hardware) unless specified with kernel flag "-xcpm". And yes, if you had an Ivy CPU, and wanted to use xcpm, and had locked MSRs, you could use a patched kernel, and -xcpm to force the kernel into xcpm mode.

 

The same setup requirements are still there: Proper smbios, DropOem SSDT c/pstate tables, provide valid SSDT for your CPU: ssdtPRgen.sh script or Clover generated c/p states, whichever one works better.

Link to comment
Share on other sites
RehabMan
RehabMan
Posted
  • Author
Posted

Do you think like this?

 

<key>Kernel flag</key>

<string>-xcpm</string>

It is either that or "-xcpm=1" (I didn't look at the disassembled code that carefully).

 

I use Chameleon.

This is my DSDT,SSDT and ioreg.

Your ioreg shows AppleIntelCPUPowerManagement loading. This is because you're using the mach_kernel attached to post #1 instead of patched vanilla mach_kernel (I can see that also in ioreg). The mach_kernel in the attachment is built from sources, and therefore is "xcpm free." If you wish to use xcpm, use patched vanilla mach_kernel.

Link to comment
Share on other sites
crusher
crusher
Posted
Posted

Your ioreg shows AppleIntelCPUPowerManagement loading. This is because you're using the mach_kernel attached to post #1 instead of patched vanilla mach_kernel (I can see that also in ioreg). The mach_kernel in the attachment is built from sources, and therefore is "xcpm free." If you wish to use xcpm, use patched vanilla mach_kernel.

 

Where a found this mach_kernel?


It is either that or "-xcpm=1" (I didn't look at the disassembled code that carefully).
 

Your ioreg shows AppleIntelCPUPowerManagement loading. This is because you're using the mach_kernel attached to post #1 instead of patched vanilla mach_kernel (I can see that also in ioreg). The mach_kernel in the attachment is built from sources, and therefore is "xcpm free." If you wish to use xcpm, use patched vanilla mach_kernel.

 

Where a found this mach_kernel.I use a your mach_kernel to #1 post.

Link to comment
Share on other sites
RehabMan
RehabMan
Posted
  • Author
Posted

I now to use your patch from your blog?

It is just a one line perl script. Use copy/paste to Terminal, with vanilla mach_kernel in your current directory. Be sure to copy the entire line.

Link to comment
Share on other sites
RehabMan
RehabMan
Posted
  • Author
Posted

Sorry to be such a pain, but How do I apply that patch? I've never used a perl script.

See post #212.

Sorry to be such a pain, but How do I apply that patch? I've never used a perl script.

For easier access (and slightly easier copy/paste), I have edited post #1 to include the perl patches from my blog.

Link to comment
Share on other sites
crusher
crusher
Posted
Posted

For 10.9:

perl -pi -e 's|\x74\x6c(\x48\x83\xc7\x28\x90\x8b\x05\x5e\x30\x5e\x00\x85\x47\xdc)\x74\x54(\x8b\x4f\xd8\x45\x85\xc0\x74\x08\x44\x39\xc1\x44\x89\xc1)\x75\x44(\x0f\x32\x89\xc0\x48\xc1\xe2\x20\x48\x09\xc2\x48\x89\x57\xf8\x48\x8b\x47\xe8\x48\x85\xc0\x74\x06\x48\xf7\xd0\x48\x21\xc2\x48\x0b\x57\xf0\x49\x89\xd1\x49\xc1\xe9\x20\x89\xd0\x8b\x4f\xd8\x4c\x89\xca)(\x0f\x30\x8b\x4f\xd8\x0f\x32\x89\xc0\x48\xc1\xe2\x20\x48\x09\xc2\x48\x89\x17\x48\x83\xc7\x30\xff\xce)\x75\x99(\x5d\xc3)\x90{7}|\x74\x73${1}\x74\x5b${2}\x75\x4b${3}\x66\x81\xf9\xe2\x00\x74\x02${4}\x75\x92${5}|g' mach_kernel

 

 

Do you think this patch?

Link to comment
Share on other sites
giacomoleopardo
giacomoleopardo
Posted
Posted

See post #212.

 

For easier access (and slightly easier copy/paste), I have edited post #1 to include the perl patches from my blog.

After copying the script 

Last login: Mon Dec  2 18:37:32 on ttys000
localhost:~ al-one$ perl -pi -e 's|\x74\x69(\x48\x83\xc7\x28\x90\x8b\x05\xfe\xce\x5f\x00\x85\x47\xdc)\x74\x51(\x8b\x4f\xd8\x45\x85\xc0\x74\x05\x44\x39\xc1)\x75\x44(\x0f\x32\x89\xc0\x48\xc1\xe2\x20\x48\x09\xc2\x48\x89\x57\xf8\x48\x8b\x47\xe8\x48\x85\xc0\x74\x06\x48\xf7\xd0\x48\x21\xc2\x48\x0b\x57\xf0\x49\x89\xd1\x49\xc1\xe9\x20\x89\xd0\x8b\x4f\xd8\x4c\x89\xca)(\x0f\x30\x8b\x4f\xd8\x0f\x32\x89\xc0\x48\xc1\xe2\x20\x48\x09\xc2\x48\x89\x17\x48\x83\xc7\x30\xff\xce)\x75\x9c(\x5d\xc3)\x90{7}(\x90{3})|\x74\x70${1}\x74\x58${2}\x75\x4b${3}\x66\x81\xf9\xe2\x00\x74\x02${4}\x75\x95${5}${6}|g'/mach_kernel

nothing happens, no words in terminal. Is that the way I'm supposed to do that? Be patient, man :)

Link to comment
Share on other sites
RehabMan
RehabMan
Posted
  • Author
Posted

After copying the script 

Last login: Mon Dec  2 18:37:32 on ttys000
localhost:~ al-one$ perl -pi -e 's|\x74\x69(\x48\x83\xc7\x28\x90\x8b\x05\xfe\xce\x5f\x00\x85\x47\xdc)\x74\x51(\x8b\x4f\xd8\x45\x85\xc0\x74\x05\x44\x39\xc1)\x75\x44(\x0f\x32\x89\xc0\x48\xc1\xe2\x20\x48\x09\xc2\x48\x89\x57\xf8\x48\x8b\x47\xe8\x48\x85\xc0\x74\x06\x48\xf7\xd0\x48\x21\xc2\x48\x0b\x57\xf0\x49\x89\xd1\x49\xc1\xe9\x20\x89\xd0\x8b\x4f\xd8\x4c\x89\xca)(\x0f\x30\x8b\x4f\xd8\x0f\x32\x89\xc0\x48\xc1\xe2\x20\x48\x09\xc2\x48\x89\x17\x48\x83\xc7\x30\xff\xce)\x75\x9c(\x5d\xc3)\x90{7}(\x90{3})|\x74\x70${1}\x74\x58${2}\x75\x4b${3}\x66\x81\xf9\xe2\x00\x74\x02${4}\x75\x95${5}${6}|g'/mach_kernel
nothing happens, no words in terminal. Is that the way I'm supposed to do that? Be patient, man :)

 

Yes. It is customary for Unix command line programs to provide no output unless there are errors, or their primary purpose is to provide output (eg 'ls' 'echo', 'diskutil list', etc.) You could compare the md5 sum between vanilla kernel and patched kernel if you want to see if there was a change. Or look at the timestamp on the file.

 

FYI: You seem to be missing a space between the closing ' and /mach_kernel.

 

Also, note that in order to modify a file directly that is in installed to root (eg. /mach_kernel) you would have to preface the command with 'sudo'.

Link to comment
Share on other sites
giacomoleopardo
giacomoleopardo
Posted
Posted

Here's the result.

Last login: Mon Dec  2 19:13:52 on ttys000
localhost:~ al-one$ sudo perl -pi -e 's|\x74\x69(\x48\x83\xc7\x28\x90\x8b\x05\xfe\xce\x5f\x00\x85\x47\xdc)\x74\x51(\x8b\x4f\xd8\x45\x85\xc0\x74\x05\x44\x39\xc1)\x75\x44(\x0f\x32\x89\xc0\x48\xc1\xe2\x20\x48\x09\xc2\x48\x89\x57\xf8\x48\x8b\x47\xe8\x48\x85\xc0\x74\x06\x48\xf7\xd0\x48\x21\xc2\x48\x0b\x57\xf0\x49\x89\xd1\x49\xc1\xe9\x20\x89\xd0\x8b\x4f\xd8\x4c\x89\xca)(\x0f\x30\x8b\x4f\xd8\x0f\x32\x89\xc0\x48\xc1\xe2\x20\x48\x09\xc2\x48\x89\x17\x48\x83\xc7\x30\xff\xce)\x75\x9c(\x5d\xc3)\x90{7}(\x90{3})|\x74\x70${1}\x74\x58${2}\x75\x4b${3}\x66\x81\xf9\xe2\x00\x74\x02${4}\x75\x95${5}${6}|g' /mach_kernel 
Password:
localhost:~ al-one$ /sbin/md5 /mach_kernel 
MD5 (/mach_kernel) = 539c3a1e2fef063384b44543765b8a39
localhost:~ al-one$ /sbin/md5 /Users/al-one/Documents/mach_kernel 
MD5 (/Users/al-one/Documents/mach_kernel) = e835be83eb956af0b63d28f69bfb22b3
localhost:~ al-one$

The first one is the patched kernel, and the second is the vanilla one. Therefore, I guess it's been patched. What do you think?

Link to comment
Share on other sites
RehabMan
RehabMan
Posted
  • Author
Posted

Here's the result.

Last login: Mon Dec  2 19:13:52 on ttys000
localhost:~ al-one$ sudo perl -pi -e 's|\x74\x69(\x48\x83\xc7\x28\x90\x8b\x05\xfe\xce\x5f\x00\x85\x47\xdc)\x74\x51(\x8b\x4f\xd8\x45\x85\xc0\x74\x05\x44\x39\xc1)\x75\x44(\x0f\x32\x89\xc0\x48\xc1\xe2\x20\x48\x09\xc2\x48\x89\x57\xf8\x48\x8b\x47\xe8\x48\x85\xc0\x74\x06\x48\xf7\xd0\x48\x21\xc2\x48\x0b\x57\xf0\x49\x89\xd1\x49\xc1\xe9\x20\x89\xd0\x8b\x4f\xd8\x4c\x89\xca)(\x0f\x30\x8b\x4f\xd8\x0f\x32\x89\xc0\x48\xc1\xe2\x20\x48\x09\xc2\x48\x89\x17\x48\x83\xc7\x30\xff\xce)\x75\x9c(\x5d\xc3)\x90{7}(\x90{3})|\x74\x70${1}\x74\x58${2}\x75\x4b${3}\x66\x81\xf9\xe2\x00\x74\x02${4}\x75\x95${5}${6}|g' /mach_kernel 
Password:
localhost:~ al-one$ /sbin/md5 /mach_kernel 
MD5 (/mach_kernel) = 539c3a1e2fef063384b44543765b8a39
localhost:~ al-one$ /sbin/md5 /Users/al-one/Documents/mach_kernel 
MD5 (/Users/al-one/Documents/mach_kernel) = e835be83eb956af0b63d28f69bfb22b3
localhost:~ al-one$
The first one is the patched kernel, and the second is the vanilla one. Therefore, I guess it's been patched. What do you think?

 

The md5 output matches my results here for the 10.8.5 mach_kernel.

Link to comment
Share on other sites
RehabMan
RehabMan
Posted
  • Author
Posted

Tried the patched kernel, deleted NullCPUPowermanagement.kext and kernel panic, of course with Kernel Flag -xcpm or -xcpm=1 in org.chameleon.Boot.plist. I guess LGA2011 doesn't care about your effort, still it needs NullCPUPowerManagement.kext.

At least if I did it right!

That is what I would expect. I don't think OS X supports PM at all on LGA2011. We need to wait for the new MacPro...

Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...