1440 replies to this topic

[hanzoh]

Hi,

I looked at my temps in Windows 7 and OS X 10.6.2 (without SpeedStepFix) and they are identical!
In Windows the CPU gets the same voltage in idle as in OS X, except that in Windows it clocks down to 1.6GHz
(@ default BCLK 133 in BIOS). The only thing that generates heat is the voltage and as the CPU doesn't reduce it any further when it gets clocked to 1.6, there is no point to clock it there, I guess.

0.9V @ 2.67GHz = 0.9V @ 1.6GHz (in terms of temperature)

callumj09, on Nov 23 2009, 06:52 AM, said:

Hey, wondering if I can get a bit of help.

I seem to be getting kernel panics after following the appropriate DSDT steps for my board (EX58-UD3r) and they're all working correctly, and as shown in the image below AppleIntelCPUPowerManagement.kext is loaded. Although I think because of my current overclock it's causing it to panic. I have 191 BCLK with turbo boost (21x multi) enabled in the BIOS.

[...]

I'm guessing the solution is to bring my BCLK back down to 180 and disable turbo boost? I really not sure. Could you possible explain why OS X ups the multi to 22x?

As always, all help appreciated,

Thanks!

You should test new kexts or a new Mac OS X install with no overclock at all.
If your system doesn't panic with normal clocks, then try getting higher and stop when it gives you panics again.

[callumj09]

Heh, I lowered my clocks back down to the default settings and it works fine now. Gonna try to reconfigure the overclock though.

[d00d]

callumj09, on Nov 23 2009, 07:02 AM, said:

Heh, I lowered my clocks back down to the default settings and it works fine now. Gonna try to reconfigure the overclock though.

With DRAM voltage changed from auto to 1.54, and all other voltages set to auto, I can run at 4.1 GHz using BCLK set to 205.
I had to also disable turbo so the clock ratio wouldn't go higher than 20, or else the OS would KP;

CPU Clock Ratio ................................ [20x] 20
Intel® Turbo Boost Tech .................. [Enabled] disabled
CPU Cores Enabled ............................ [All] all
CPU Multi Threading .......................... [Enabled] enabled
CPU Enhanced Halt (C1E) ................... [Disabled] disabled
C3/C6/C7 State Support .................... [Disabled] disabled
CPU Thermal Monitor ......................... [Enabled] enabled
CPU EIST Function ............................ [Disabled] disabled
Bi-Directional PROCHOT ..................... [Enabled] disabled
Virtualization Technology ................... [Enabled] enabled

With the same settings I could boot and run at 4.2 GHz without KP using BCLK set to 210, but sometimes it would refuse to boot, possibly manually setting voltages would help.

[callumj09]

d00d, on Nov 23 2009, 12:42 PM, said:

With DRAM voltage changed from auto to 1.54, and all other voltages set to auto, I can run at 4.1 GHz using BCLK set to 205.
I had to also disable turbo so the clock ratio wouldn't go higher than 20, or else the OS would KP;

CPU Clock Ratio ................................ [20x] 20
Intel® Turbo Boost Tech .................. [Enabled] disabled
CPU Cores Enabled ............................ [All] all
CPU Multi Threading .......................... [Enabled] enabled
CPU Enhanced Halt (C1E) ................... [Disabled] disabled
C3/C6/C7 State Support .................... [Disabled] disabled
CPU Thermal Monitor ......................... [Enabled] enabled
CPU EIST Function ............................ [Disabled] disabled
Bi-Directional PROCHOT ..................... [Enabled] disabled
Virtualization Technology ................... [Enabled] enabled

With the same settings I could boot and run at 4.2 GHz without KP using BCLK set to 210, but sometimes it would refuse to boot, possibly manually setting voltages would help.

I seem to be able to boot trying those just fine, but sleep stops working for some reason. Should that happen?

Edit:

I just booted with 200 BCLK and 20x multi and disabled turbo boost (4.0GHz) and it seemed to work perfectly, I don't know for sure that the OC is stable because I haven't had a proper chance to stress test, but I played some 1080p video for a little while. The clock speed reports as 4.1GHz in OS X. But again, sleep still doesn't work for some reason.

[d00d]

callumj09, on Nov 23 2009, 08:37 AM, said:

I seem to be able to boot trying those just fine, but sleep stops working for some reason. Should that happen?

Edit:

I just booted with 200 BCLK and 20x multi and disabled turbo boost (4.0GHz) and it seemed to work perfectly, I don't know for sure that the OC is stable because I haven't had a proper chance to stress test, but I played some 1080p video for a little while. The clock speed reports as 4.1GHz in OS X. But again, sleep still doesn't work for some reason.

Manual sleep functionality (Power button and Apple:Sleep) works for me at any clock.
Automatic sleep only works for me using PenntNeu-script.
Removing the IRQ from RTC prevents sleep from functioning, make sure that the IRQs are only removed from PIC and TMR.

Update:
I removed the IRQ from RTC and it didn't cause sleep problems in 10.6.2, but it did in 10.6.1.

[callumj09]

d00d, on Nov 23 2009, 02:18 PM, said:

Manual sleep functionality (Power button and Apple:Sleep) works for me at any clock.
Automatic sleep only works for me using PenntNeu-script.
Removing the IRQ from RTC prevents sleep from functioning, make sure that the IRQs are only removed from PIC and TMR.

Sleep still functions on stock clocks though. I'll check my DSDT though.

Just checked and those sections look like this:

				Device (PIC)
				{
					Name (_HID, EisaId ("PNP0000"))
					Name (_CRS, ResourceTemplate ()
					{
						IO (Decode16,
							0x0020,			 // Range Minimum
							0x0020,			 // Range Maximum
							0x01,			   // Alignment
							0x02,			   // Length
							)
						IO (Decode16,
							0x00A0,			 // Range Minimum
							0x00A0,			 // Range Maximum
							0x01,			   // Alignment
							0x02,			   // Length
							)
					})
				}

				Device (TMR)
				{
					Name (_HID, EisaId ("PNP0100"))
					Name (ATT5, ResourceTemplate ()
					{
						IO (Decode16,
							0x0040,			 // Range Minimum
							0x0040,			 // Range Maximum
							0x00,			   // Alignment
							0x04,			   // Length
							)
					})
					Name (ATT6, ResourceTemplate ()
					{
						IO (Decode16,
							0x0040,			 // Range Minimum
							0x0040,			 // Range Maximum
							0x00,			   // Alignment
							0x04,			   // Length
							)
					})
					Method (_CRS, 0, NotSerialized)
					{
						If (LGreaterEqual (OSFX, 0x03))
						{
							If (HPTF)
							{
								Return (ATT6)
							}
							Else
							{
								Return (ATT5)
							}
						}
						Else
						{
							Return (ATT5)
						}
					}
				}

RTC section:

				Device (RTC)
				{
					Name (_HID, EisaId ("PNP0B00"))
					Name (ATT0, ResourceTemplate ()
					{
						IO (Decode16,
							0x0070,			 // Range Minimum
							0x0070,			 // Range Maximum
							0x00,			   // Alignment
							0x02,			   // Length
							)
					})
					Name (ATT1, ResourceTemplate ()
					{
						IO (Decode16,
							0x0070,			 // Range Minimum
							0x0070,			 // Range Maximum
							0x00,			   // Alignment
							0x02,			   // Length
							)
					})
					Method (_CRS, 0, NotSerialized)
					{
						If (LGreaterEqual (OSFX, 0x03))
						{
							If (HPTF)
							{
								Return (ATT1)
							}
							Else
							{
								Return (ATT0)
							}
						}
						Else
						{
							Return (ATT0)
						}
					}
				}

Oh, and here's my current DSDT if you want to have a look.

http://dl.dropbox.co...790162/DSDT.dsl

[d00d]

callumj09, on Nov 23 2009, 09:38 AM, said:

Sleep still functions on stock clocks though. I'll check my DSDT though.

Just checked and those sections look like this:

...

Oh, and here's my current DSDT if you want to have a look.

http://dl.dropbox.co...790162/DSDT.dsl

You are missing the IRQ in RTC, put it back and sleep will function.
Did you use fassl's DSDT Patcher that removes the IRQ from RTC?
Better to use iasl or DSDTSE and make manual edits.
Here's the original code that includes the IRQ (with CMOS fix);

				Device (RTC)
				{
					Name (_HID, EisaId ("PNP0B00"))
					Name (ATT0, ResourceTemplate ()
					{
						IO (Decode16,
							0x0070,			 // Range Minimum
							0x0070,			 // Range Maximum
							0x00,			   // Alignment
							0x02,			   // Length
							)
						IRQNoFlags ()
							{8}
					})
					Name (ATT1, ResourceTemplate ()
					{
						IO (Decode16,
							0x0070,			 // Range Minimum
							0x0070,			 // Range Maximum
							0x00,			   // Alignment
							0x02,			   // Length
							)
					})
					Method (_CRS, 0, NotSerialized)
					{
						If (LGreaterEqual (OSFX, 0x03))
						{
							If (HPTF)
							{
								Return (ATT1)
							}
							Else
							{
								Return (ATT0)
							}
						}
						Else
						{
							Return (ATT0)
						}
					}
				}

Update:
I removed the IRQ from RTC and it didn't cause sleep problems in 10.6.2, but it did in 10.6.1.

[The Real Deal]

public utility topic      

d00d, let me know, in idle and load what are your temps? Stock rad?


PS: Could you point me in the direction to get rid of the "x.x" in my smbios.plist?





PPS: Do you have more infos listed about your material in the system profiler?





TRD

[callumj09]

d00d, on Nov 23 2009, 03:35 PM, said:

You are missing the IRQ in RTC, put it back and sleep will function.
Did you use fassl's DSDT Patcher that removes the IRQ from RTC?
Better to use iasl or DSDTSE and make manual edits.
Here's the original code that includes the IRQ (with CMOS fix);

				Device (RTC)
				{
					Name (_HID, EisaId ("PNP0B00"))
					Name (ATT0, ResourceTemplate ()
					{
						IO (Decode16,
							0x0070,			 // Range Minimum
							0x0070,			 // Range Maximum
							0x00,			   // Alignment
							0x02,			   // Length
							)
						IRQNoFlags ()
							{8}
					})
					Name (ATT1, ResourceTemplate ()
					{
						IO (Decode16,
							0x0070,			 // Range Minimum
							0x0070,			 // Range Maximum
							0x00,			   // Alignment
							0x02,			   // Length
							)
					})
					Method (_CRS, 0, NotSerialized)
					{
						If (LGreaterEqual (OSFX, 0x03))
						{
							If (HPTF)
							{
								Return (ATT1)
							}
							Else
							{
								Return (ATT0)
							}
						}
						Else
						{
							Return (ATT0)
						}
					}
				}

I'm using a GUI version of iasl called iaslMe, you just drag the files and it compiles/decompiles it.

I just did the above and decompiled DSDT.aml again after compiling to check if the IRQ part still existed and it did, rebooted and tried sleep but it's not working still. The computer wakes, but I just hear a continual fan noise from my GPU and nothing happens.

My current clock is 4.0GHz (20x200) with turbo boost disabled and all custom voltages.

Any ideas? I'm really stuck on this...

Here's my current compiled DSDT if you want to take a look: http://dl.dropbox.co...790162/DSDT.aml

Thanks

[d00d]

The Real Deal, on Nov 23 2009, 11:06 AM, said:

public utility topic      

d00d, let me know, in idle and load what are your temps? Stock rad?

PS: Could you point me in the direction to get rid of the "x.x" in my smbios.plist?

PPS: Do you have more infos listed about your material in the system profiler?

TRD

My idle is around 47C at 4.1 GHz and no turbo, and up around 95C running mprime, using a Noctua NH-U12P SE2.
I'm not sure why you have x.x if it's not defined that way in smbios.plist.
My System Profiler:Hardware screen shows the same fields as yours.

callumj09, on Nov 23 2009, 11:20 AM, said:

I'm using a GUI version of iasl called iaslMe, you just drag the files and it compiles/decompiles it.

I just did the above and decompiled DSDT.aml again after compiling to check if the IRQ part still existed and it did, rebooted and tried sleep but it's not working still. The computer wakes, but I just hear a continual fan noise from my GPU and nothing happens.

My current clock is 4.0GHz (20x200) with turbo boost disabled and all custom voltages.

Any ideas? I'm really stuck on this...

Here's my current compiled DSDT if you want to take a look: http://dl.dropbox.co...790162/DSDT.aml

Thanks

Your DSDT looks correct, but appears to be based on a BIOS older than F9e that has CPU8, 9 and A through F for future i9 support.
I couldn't get sleep to work correctly until I used F9e with Chameleon-2.0-RC3-r658-bin.tar.gz and netkas's boot_v10.5.zip as the bootloader.
Do you have the `Start up automatically after a power failure' option checked in Energy Saver?

[callumj09]

d00d, on Nov 23 2009, 09:58 PM, said:

My idle is around 47C at 4.1 GHz and no turbo, and up around 95C running mprime, using a Noctua NH-U12P SE2.
I'm not sure why you have x.x if it's not defined that way in smbios.plist.
My System Profiler:Hardware screen shows the same fields as yours.

Your DSDT looks correct, but appears to be based on a BIOS older than F9e that has CPU8, 9 and A through F for future i9 support.
I couldn't get sleep to work correctly until I used F9e with Chameleon-2.0-RC3-r658-bin.tar.gz and netkas's boot_v10.5.zip as the bootloader.
Do you have the `Start up automatically after a power failure' option checked in Energy Saver?

Probably a good time to note that I don't have the UD5, I have a UD3R - so it's a different BIOS. I'm using the latest BIOS available for my board (F6) available from here:

http://www.giga-byte...?ProductID=2989

Is there a way those DSDT fixes can be modified specifically for this BIOS/board? And yes, I do have that option checked in prefs, the only power management function I have disabled is HDD sleep.

I'm also using PC-EFI 10.5

[d00d]

callumj09, on Nov 23 2009, 05:21 PM, said:

Probably a good time to note that I don't have the UD5, I have a UD3R - so it's a different BIOS. I'm using the latest BIOS available for my board (F6) available from here:

http://www.giga-byte...?ProductID=2989

Is there a way those DSDT fixes can be modified specifically for this BIOS/board? And yes, I do have that option checked in prefs, the only power management function I have disabled is HDD sleep.

I'm also using PC-EFI 10.5

The DSDT fixes should work on any GA-EX58 board including the UD3, except for the ALC889 modification, because you have an ALC888.
I'd suggest using a newer BIOS from http://forums.tweakt...est-bios-28441/

[callumj09]

d00d, on Nov 23 2009, 10:53 PM, said:

The DSDT fixes should work on any GA-EX58 board including the UD3, except for the ALC889 modification, because you have an ALC888.
I'd suggest using a newer BIOS from http://forums.tweakt...est-bios-28441/

What I have is the newest, the rest are in BETA. It should work ...surely?

[Emilo]

d00d,

I have trouble with sound. For some reason my sound outputs through black jack.
Would you add your modified ALC889a.kext to original post.

Thank you.

[d00d]

Emilo, on Nov 23 2009, 06:13 PM, said:

d00d,

I have some trouble to get sound to work.
Would you add your modified ALC889a.kext to original post.

Thank you.

Unmodified there's three sound assertion messages, modified there's two.
Remove the following;
        <key>BuiltInHDA</key>
        <dict>
...
        </dict>

[Emilo]

d00d, on Nov 23 2009, 07:16 PM, said:

Unmodified there's three sound assertion messages, modified there's two.
Remove the following;
        <key>BuiltInHDA</key>
        <dict>
...
        </dict>

Removed the following code, but sound still outputs from black jack only:

		<key>BuiltInHDA</key>
		 <dict>
			 <key>CFBundleIdentifier</key>
			 <string>com.apple.driver.AppleHDAController</string>
			 <key>CodecAddressFilterArray</key>
			 <array>
				 <dict>
					 <key>CodecAddressMask</key>
					 <data>AQAAAA==</data>
					 <key>LayoutID</key>
					 <integer>16392</integer>
				 </dict>

[d00d]

Emilo, on Nov 23 2009, 08:03 PM, said:

Removed the following code, but sound still outputs only from black jack:

		<key>BuiltInHDA</key>
		 <dict>
			 <key>CFBundleIdentifier</key>
			 <string>com.apple.driver.AppleHDAController</string>
			 <key>CodecAddressFilterArray</key>
			 <array>
				 <dict>
					 <key>CodecAddressMask</key>
					 <data>AQAAAA==</data>
					 <key>LayoutID</key>
					 <integer>16392</integer>
				 </dict>

You didn't remove the whole section, remove all of BuiltinHDA up to the following line;
<key>HDA Platform Resource</key>
That doesn't solve any functional problem though, it just removes one of the three sound assertion messages.

[Emilo]

d00d, on Nov 23 2009, 08:12 PM, said:

You didn't remove the whole section, remove all of BuiltinHDA up to the following line;
<key>HDA Platform Resource</key>
That doesn't solve any functional problem though, it just removes one of the three sound assertion messages.

Edited the kext properly this time. Thank you.
Also fixed black jack output issue, but as you said it was different problem.

Awesome setup.

With overclock @ 4.0GHz, Thermalright Ultra-120 Extreme cooler and following voltages I am getting 37C at idle:
- Core voltage: 1.336V
- CPU PLL: 1.88V
- QPI/VTT: 1.34V
- Dram Voltage: 1.6V
All power saving features and Intel Turbo Bust are disabled in BIOS.

[The Real Deal]

Same temperature here. Delta 42-48° Celcius @ 1.25 vcore and a third party rad with nullcpu..

I asked about the sytem profiler because here, the person reffers two lines relating to the SMC.



Is there a way to fix the shutdown issues with the DSDT? I would like to give a try with the master chief re/start solution kext.


Thanks d00d

[d00d]

Emilo, on Nov 23 2009, 08:44 PM, said:

Edited the kext properly this time. Thank you.
Also fixed black jack output issue, but as you said it was different problem.

Awesome setup.

With overclock @ 4.0GHz, Thermalright Ultra-120 Extreme cooler and following voltages I am getting 37C at idle:
- Core voltage: 1.336V
- CPU PLL: 1.88V
- QPI/VTT: 1.34V
- Dram Voltage: 1.6V
All power saving features and Intel Turbo Bust are disabled in BIOS.

That's running cooler than mine at 19C ambient, did you manually set voltages to be able to boot, to get lower temperatures, or both?

The Real Deal, on Nov 24 2009, 08:58 AM, said:

Same temperature here. Delta 42-48° Celcius @ 1.25 vcore and a third party rad with nullcpu..

I asked about the sytem profiler because here, the person reffers two lines relating to the SMC.

Is there a way to fix the shutdown issues with the DSDT? I would like to give a try with the master chief re/start solution kext.

Thanks d00d

The second SMC Version and Serial Number lines are for the Apple hardware processor tray.
The GB board doesn't have a two part MB, so one line for each is appropriate.

I don't have a shutdown issue, but I've been following that thread.
It appears that there's a problem with restart after sleep and wake, but I generally use shutdown instead so I didn't notice the problem.

Topic updated for speed step on 10.6.2;

You can also go further than how Apple intended the MacPro4,1 to work by using MP41SpeedStepFix.kext (10.6.0 and 10.6.1) or MacPro4_1.plist (10.6.2) to give your machine the speed step capability of reducing clock speed under idle conditions.
Replace /System/Library/Extensions/IOPlatformPluginFamily.kext/Contents/PlugIns/ACPI_SMC_PlatformPlugin.kext/Contents/Resources/MacPro4_1.plist with the modified one.
The CPU will clock down to 60% with either solution.
It will clock up to 105% (x21) for MP41SpeedStepFix.kext or 110% (x22) for MacPro4_1.plist, if turbo is enabled in BIOS, or 100% if disabled.
...
THe KiNG's MP41SpeedStepFix.kext (10.6.0 and 10.6.1): google for the link
demong1's MacPro4_1.plist (10.6.2): located in the same forum site and topic as MP41SpeedStepFix.kext