Contribute
Register

[Success] i5 2500K - Zotac Z77- ITX - Mountain Lion

Status
Not open for further replies.
Joined
Jun 21, 2012
Messages
36
CPU
Xeon E3 1230 V2 IVY
Graphics
GTX670 OC 2GB
Mac
  1. iMac
  2. MacBook
  3. MacBook Air
  4. MacBook Pro
  5. Mac mini
  6. Mac Pro
Classic Mac
  1. eMac
  2. iBook
  3. iMac
  4. Power Mac
  5. PowerBook
Mobile Phone
  1. iOS
Podoboy,

Try the attached.

There is no need to re-compile it, just unzip and put it in the Extra folder.

Also got to org.chameleon.Boot.plist in the Extra folder, open it with text editor and add these lines to it if they are not there already:

<key>DropSSDT</key>
<string>Yes</string>

Also make sure in that plist it says:

<key>GeneratePstates</key>
<string>No</string>

This will then try to make sure that the system uses your pstates and not ones generated automatically by Chimera.

Hope this works okay.

Well Noted with very thanks. Let me do it now and get back to you soon.
 
Joined
Jul 27, 2012
Messages
18
Motherboard
Zotac z77-ITX - 10.8.2
CPU
core i5 3570K
Graphics
PNY GTX 660 Ti
Mac
Classic Mac
Mobile Phone
  1. iOS
Also got to org.chameleon.Boot.plist in the Extra folder, open it with text editor and add these lines to it if they are not there already:

<key>DropSSDT</key>
<string>Yes</string>

Also make sure in that plist it says:

<key>GeneratePstates</key>
<string>No</string>

This will then try to make sure that the system uses your pstates and not ones generated automatically by Chimera.

Hope this works okay.

Hi minihack, should I use this settings on my .plist with my own DSDT ?
 
Joined
Jun 21, 2012
Messages
36
CPU
Xeon E3 1230 V2 IVY
Graphics
GTX670 OC 2GB
Mac
  1. iMac
  2. MacBook
  3. MacBook Air
  4. MacBook Pro
  5. Mac mini
  6. Mac Pro
Classic Mac
  1. eMac
  2. iBook
  3. iMac
  4. Power Mac
  5. PowerBook
Mobile Phone
  1. iOS
Well Noted with very thanks. Let me do it now and get back to you soon.

I did it with latest attached one. but got the same result
"12. 9. 27. PM 9:16:51.000 kernel[0]: MSRDumper PStatesReached: 16 29 35 36 37"

and Below is my org.chameleon.Boot.list contents

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>Credits</key>
<string>Created with Champlist</string>
<key>DropSSDT</key>
<string>Yes</string>
<key>GeneratePstates</key>
<string>No</string>
<key>Boot Banner</key>
<string>No</string>
<key>Graphics Mode</key>
<string>1920x1080x32</string>
<key>Instant Menu</key>
<string>Yes</string>
<key>Theme</key>
<string>LoginToLion</string>
</dict>
</plist>

I keep asking you and feel very sorry for your time..so, Let me keep check what I can do more
such as I will boot with GeneratePstates=Yes. something. and Your any advice for this, will be appreciated. thank you. Keep you posted. thank you as always.
 
Joined
Jun 21, 2012
Messages
36
CPU
Xeon E3 1230 V2 IVY
Graphics
GTX670 OC 2GB
Mac
  1. iMac
  2. MacBook
  3. MacBook Air
  4. MacBook Pro
  5. Mac mini
  6. Mac Pro
Classic Mac
  1. eMac
  2. iBook
  3. iMac
  4. Power Mac
  5. PowerBook
Mobile Phone
  1. iOS
I did it with latest attached one. but got the same result
"12. 9. 27. PM 9:16:51.000 kernel[0]: MSRDumper PStatesReached: 16 29 35 36 37"

and Below is my org.chameleon.Boot.list contents

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>Credits</key>
<string>Created with Champlist</string>
<key>DropSSDT</key>
<string>Yes</string>
<key>GeneratePstates</key>
<string>No</string>
<key>Boot Banner</key>
<string>No</string>
<key>Graphics Mode</key>
<string>1920x1080x32</string>
<key>Instant Menu</key>
<string>Yes</string>
<key>Theme</key>
<string>LoginToLion</string>
</dict>
</plist>

I keep asking you and feel very sorry for your time..so, Let me keep check what I can do more
such as I will boot with GeneratePstates=Yes. something. and Your any advice for this, will be appreciated. thank you. Keep you posted. thank you as always.


WOW!! Big News, Finally I got it

12. 9. 27. PM 9:42:45.000 kernel[0]: MSRDumper PStatesReached: 16 29 30 31 32 33 35 36 37
I got the range from 16 to 37. Not sure which range is correct for MY CPU but it's huge improvements here.

Thanks to Minihack and Let me keep testing and posted you


Your DSDT/DROPSSDT=YES/GeneratePstates=No/SMIBIOS=MACPRO 3,1 Combination finally shows 9 pstates

Thank you.
 
Joined
May 27, 2010
Messages
2,383
Motherboard
Dell Optiplex 9030 All in One
CPU
i5-4690K
Graphics
HD 4600
Mac
  1. Mac mini
Classic Mac
  1. iMac
Mobile Phone
  1. iOS
Hi minihack, should I use this settings on my .plist with my own DSDT ?

As you have got pstates inside your DSDT now, it is usually better to use the DropSSDT=yes flag so it does not try and fetch stuff from other tables. For the same reason, if the P states in the DSDT are actually working then you do not want Chimera to guess at settings that might be right and just use the p-states from the DSDT.

Sometimes though you need to try the different flags and just see what works for you, but if you have gone to the trouble of putting stuff in the DSDT best to explicitly tell the system to use it.

[Sometimes for different boards using the Dropssdt flag causes problems......as with everything Hackintosh though it is a case of do what you think is right and if that doesn't work then try something different. :) ]

@podoboy. Great.:thumbup:
 
Joined
Jun 21, 2012
Messages
36
CPU
Xeon E3 1230 V2 IVY
Graphics
GTX670 OC 2GB
Mac
  1. iMac
  2. MacBook
  3. MacBook Air
  4. MacBook Pro
  5. Mac mini
  6. Mac Pro
Classic Mac
  1. eMac
  2. iBook
  3. iMac
  4. Power Mac
  5. PowerBook
Mobile Phone
  1. iOS
As you have got pstates inside your DSDT now, it is usually better to use the DropSSDT=yes flag so it does not try and fetch stuff from other tables. For the same reason, if the P states in the DSDT are actually working then you do not want Chimera to guess at settings that might be right and just use the p-states from the DSDT.

Sometimes though you need to try the different flags and just see what works for you, but if you have gone to the trouble of putting stuff in the DSDT best to explicitly tell the system to use it.

[Sometimes for different boards using the Dropssdt flag causes problems......as with everything Hackintosh though it is a case of do what you think is right and if that doesn't work then try something different. :) ]

@podoboy. Great.:thumbup:

Thanks Minihack from my hearts. Plus..I have installed own my APPLE IR RECEIVER that took from my mac-book pro and follow your super guide !! Now, My Cust-mac is 99.9% completed. for the 0.1%, I think that it's booting sound that exactly same with apple on bios level and booting screen stretch at 1920x1080 res. yeh!! those two are very minor issues/can't fixed forever. So, thank you!!
 
Joined
May 27, 2011
Messages
83
Motherboard
MacBook Pro
CPU
i7
Graphics
Nvidia GT 330M
Mac
  1. MacBook Pro
I have H77ITX-A-E which also come with Atheros AR9285 wifi card. I use DSDT to make it work, it connect to my wireless-n network. However, max speed is always 65M. Machine is very close to router, and signal is pretty consistent. What do you see if you are using same card?

Thanks

Noodle
 
Joined
Jun 21, 2012
Messages
36
CPU
Xeon E3 1230 V2 IVY
Graphics
GTX670 OC 2GB
Mac
  1. iMac
  2. MacBook
  3. MacBook Air
  4. MacBook Pro
  5. Mac mini
  6. Mac Pro
Classic Mac
  1. eMac
  2. iBook
  3. iMac
  4. Power Mac
  5. PowerBook
Mobile Phone
  1. iOS
As you have got pstates inside your DSDT now, it is usually better to use the DropSSDT=yes flag so it does not try and fetch stuff from other tables. For the same reason, if the P states in the DSDT are actually working then you do not want Chimera to guess at settings that might be right and just use the p-states from the DSDT.

Sometimes though you need to try the different flags and just see what works for you, but if you have gone to the trouble of putting stuff in the DSDT best to explicitly tell the system to use it.

[Sometimes for different boards using the Dropssdt flag causes problems......as with everything Hackintosh though it is a case of do what you think is right and if that doesn't work then try something different. :) ]

@podoboy. Great.:thumbup:


Hi Minihack

I did several test. please see below.

(1) with your first revision DSDT with SMIBIOS IMAC 12,1
5 p states / deep sleep able

(2) with your first revision DSDT with SMIBIOS MAC PRO 3,1
9 p states / deep sleep able

(3) with your second revision/shared DSDT with SMIBIOS IMAC 12,1
5 p states / deep sleep unable

(4) with your second revision DSDT with SMIBIOS MAC PRO 3,1
9 p states / deep sleep unable

Both DSDT Macmini = 2 p states
Both DSDT Macpro = 5,1 KP

I think I should go with (2) but before that..

Would you tell me what is the differences with First shared DSDT and second one ? I'm kinds of confusing now because of result of (2)/(4)

thank you as always
 
Joined
May 27, 2010
Messages
2,383
Motherboard
Dell Optiplex 9030 All in One
CPU
i5-4690K
Graphics
HD 4600
Mac
  1. Mac mini
Classic Mac
  1. iMac
Mobile Phone
  1. iOS
Hi Minihack

I did several test. please see below.

(1) with your first revision DSDT with SMIBIOS IMAC 12,1
5 p states / deep sleep able

(2) with your first revision DSDT with SMIBIOS MAC PRO 3,1
9 p states / deep sleep unable

(3) with your second revision/shared DSDT with SMIBIOS IMAC 12,1
5 p states / deep sleep unable

(4) with your first revision DSDT with SMIBIOS MAC PRO 3,1
9 p states / deep sleep unable

Both DSDT Macmini = 2 p states
Both DSDT Macpro = 5,1 KP

I think I might go with (1) but Would you tell me what is the differences with First shared DSDT and second one ? I'm kinds of confusing now because of result of (2) one.

thank you as always

Interesting!
First revision with p-states just had generic p-state information in the DSDT. I mean information that was in the Multibeast SSDT for i5/i7 copied into the DSDT. Second revision with p-states was taken by copying the p-state information from your own SSDT tables and copying that into the DSDT (using the simple structure of the multibeast SSDT - so your information, in a simple structure).
It looks like the general multibeast p-states are as good as your native ones. So that is okay, but as the general ones allow you deep sleep, maybe you should stick with those.
The different Mac models have different power state structures and the model you choose for the SMBIOS plist tells the power management (appleintelcpupowermanagement.kext) how to use the information it is given. It looks like the mac pro 3,1 gives you best powermanagement though.
It is possible to go into the powermanagement kext and change settings in the plists in there, so you could for instance if you really wanted go into the iMac12,2 definition and replace the information from that with information from the MacPro3,1 and if you are lucky that might give you 9 p-states and proper sleep.......or it might not. These are things to try on a rainy day if you are really bored. In any case, any change you make might be effective on one version of OSX and then change again the very next time they change their powermanagement kext.
Sleep and powermanagement are the two most difficult areas to get right and to keep correct. To be honest, I don't bother worrying too much about my system as long as it does not use too much power when idle and it can speed up when I want it to......
It is the price we pay for running OSX on non-standard non-Apple hardware.
 
Joined
Jun 21, 2012
Messages
36
CPU
Xeon E3 1230 V2 IVY
Graphics
GTX670 OC 2GB
Mac
  1. iMac
  2. MacBook
  3. MacBook Air
  4. MacBook Pro
  5. Mac mini
  6. Mac Pro
Classic Mac
  1. eMac
  2. iBook
  3. iMac
  4. Power Mac
  5. PowerBook
Mobile Phone
  1. iOS
Interesting!
First revision with p-states just had generic p-state information in the DSDT. I mean information that was in the Multibeast SSDT for i5/i7 copied into the DSDT. Second revision with p-states was taken by copying the p-state information from your own SSDT tables and copying that into the DSDT (using the simple structure of the multibeast SSDT - so your information, in a simple structure).
It looks like the general multibeast p-states are as good as your native ones. So that is okay, but as the general ones allow you deep sleep, maybe you should stick with those.
The different Mac models have different power state structures and the model you choose for the SMBIOS plist tells the power management (appleintelcpupowermanagement.kext) how to use the information it is given. It looks like the mac pro 3,1 gives you best powermanagement though.
It is possible to go into the powermanagement kext and change settings in the plists in there, so you could for instance if you really wanted go into the iMac12,2 definition and replace the information from that with information from the MacPro3,1 and if you are lucky that might give you 9 p-states and proper sleep.......or it might not. These are things to try on a rainy day if you are really bored. In any case, any change you make might be effective on one version of OSX and then change again the very next time they change their powermanagement kext.
Sleep and powermanagement are the two most difficult areas to get right and to keep correct. To be honest, I don't bother worrying too much about my system as long as it does not use too much power when idle and it can speed up when I want it to......
It is the price we pay for running OSX on non-standard non-Apple hardware.

Yes. totally understand..and I just realized that after read your last comments.

Actually, It was very mixed feeling to me that very lucky to know you and build my first machine all the time. in the same time, feel sorry to you to spend your time much

so, Naturally, I think that I have to get the maximized result with your DSDT quickly and correctly not to spend your time any more and 100% utilize your DSDT.

Since this is not a my personal diary. let me stop :)

Truly thank you. I couldn't even close without you and this thread.
 
Status
Not open for further replies.
Top