1440 replies to this topic

[callumj09]

I updated my BIOS to the latest BETA available from Gigabyte's website and it solved the sleep issue. Thanks so much for the help, everything works amazingly.

Edit:

I do have two other small queries. Since this fresh install my secondary drive has been showing up in finder with an eject button next to it:



I'm not really sure why this is happening because that drive (2 separate partitions) is plugged to the same ports as my main drive. The only reason I can think why the main drive doesn't have it is because it's the startup disk.

My other query is about my keyboard. I use Apple's bluetooth keyboard but after waking from sleep the keys are bound differently - what are normally the keys to adjust sound control dashboard etc. I can replug my USB bluetooth adapter but that's a bit annoying to have to do every time.

Thanks

[Emilo]

d00d, on Nov 24 2009, 09:50 AM, said:

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?

I am using your DSDT and Kexts (replaced Device (PCI0) section in your DSDT to match my video card)
My Core i7 920 has D0 stepping.
Temperatures are displayed with latest Hardware Monitor application.
System is running in 64 bit mode.

My RAM and CPU Cooler info:
Mushkin Enhanced Redline (Model 998691): http://www.newegg.co...6-050-_-Product
Thermalright Ultra-120 Extreme: http://www.crazypc.c...1366-50985.html

Attached is my BIOS template.

Attached Files

•  GA_EX58_BIOS_F9e_template.zip   1.72K   49 downloads

[d00d]

callumj09, on Nov 24 2009, 10:07 AM, said:

I updated my BIOS to the latest BETA available from Gigabyte's website and it solved the sleep issue. Thanks so much for the help, everything works amazingly.

Edit:

I do have two other small queries. Since this fresh install my secondary drive has been showing up in finder with an eject button next to it:



I'm not really sure why this is happening because that drive (2 separate partitions) is plugged to the same ports as my main drive. The only reason I can think why the main drive doesn't have it is because it's the startup disk.

My other query is about my keyboard. I use Apple's bluetooth keyboard but after waking from sleep the keys are bound differently - what are normally the keys to adjust sound control dashboard etc. I can replug my USB bluetooth adapter but that's a bit annoying to have to do every time.

Thanks

Good to see that it solved your sleep issue.
I was initially wary of using a beta BIOS, but if nobody else has a problem on that forum after a few days it's probably stable, and you can easily back out.

The drives have eject buttons because of the SATA hot plug functionality of the MB, and the one that has the active OS wouldn't have an eject button.
This is convenient when you want to be able to mount and unmount external eSATA drives connected  through the PCI slot eSATA interface that's included with UD4 through UD7, if that's connected to one or two of the six SATA ICH10 MB ports.
UD7 also has two combination USB and powered eSATA ports at the back panel.
The non OS drives can be ejected in the Finder, and mounted again with Disk Utility or by unplug and plug.
It's correct functionality, but if you didn't want the eject capability, device-id `0x81, 0x26, 0x00, 0x00' can instead be set in the IDE1 section of the DSDT and you wouldn't need to use OrangeIconFix.kext either.
That would incorrectly show ESB2 instead of ICH10 in System Profiler:Hardware:Serial-ATA however.

I don't have an answer for the BT sleep issue, perhaps someone else has a solution.

[The Real Deal]

EDIT:

Ok, i have placed the demong1's plist in the right place but i don't get that part:


"use MacPro4,1 as model name.LPC-ICH10 in DSDT"


Please, could you explain this part in a clearer way?

[d00d]

The Real Deal, on Nov 24 2009, 01:14 PM, said:

About the speedstep, which kext from apple allow this? The AppleIntelCPUPowerManagement?

I already use the evOspeedstep.kext, did you compare this one with the MP41....? The X21 multiplier works great with an O/C and turbo enabled thus far. Considering i have disabled some power savers, EIST,C1E, etc,... i'm not sure the i7 could run at low voltage. The 42-48°C value in idle speak for itself i guess.

Speed step is directly related to ACPI_SMC_PlatformPlugin.kext.
In ioreg at IOService:/AppleACPIPlatformExpert/CPU0@0/AppleACPICPU/ACPI_SMC_PlatformPlugin you will see CPUPLimit with a value of 0x0, a different value if it's not activated, or not there at all if not enabled.

I haven't experimented with evospeedstep.kext because I can't locate the download link on their site.

[The Real Deal]

Oh sorry, i have just edited my message

[d00d]

The Real Deal, on Nov 24 2009, 01:14 PM, said:

Ok, i have placed the demong1's plist in the right place but i don't get that part:
"use MacPro4,1 as model name.LPC-ICH10 in DSDT"

I assume it means to identify your machine as MacPro4,1 in smbios.plist, fix the DSDT's PX40 section so that AppleLPC.kext loads, and fix the IDE1 section to identify the controller as ICH10.

[The Real Deal]

Thank you.

[d00d]

The Real Deal, on Nov 24 2009, 03:46 PM, said:

I confirm i don't have a CPUPLimit value at the moment.

.. it's already fine for the smbios plist, but i'm a beginner with the dsdt edition and the PX40... it's chinese for me

Here is a screencap, does everything looks right for you?

d00d, you have patched your DSDT or the AppleLPC.kext?

Your PX40 shows no modifications, please read page 1.

[The Real Deal]

I think i got it know, your infos are helpful I managed to patch my dsdt, LPC works fine now.



I see that you don't use a disabler, i just wonder how you managed this because i get a kp without it on startup. (My AppleHPET loads)


A lot of question i know


TY




EDIT 25/11


Today , i removed the nullcpupowermanagement.kext to check if i got a kp at the load process. And no kp..

The only thing which is different, is my dsdt with the PX40 mod; checked the automatic restart after an electrical failure, that's all.

I confirm the LPC and HPET are loaded (sytem profiler) but still noCPULimit shown in my registry.

I probably have to mod the dsdt to include some p states to reach a vanilla speedstep at this stage.

I noticed as well, that my temperature didn't increase without a disabler this time. Before i get + 8°C. Perfs are the same.

[d00d]

The Real Deal, on Nov 24 2009, 04:26 PM, said:

Today , i removed the nullcpupowermanagement.kext to check if i got a kp at the load process. And no kp..

The only thing which is different, is my dsdt with the PX40 mod; checked the automatic restart after an electrical failure, that's all.

I confirm the LPC and HPET are loaded (sytem profiler) but still noCPULimit shown in my registry.

I probably have to mod the dsdt to include some p states to reach a vanilla speedstep at this stage.

The following message indicates that you are still using a disabler kext so that AppleIntelCPUPowerManagementClient.kext and AppleIntelCPUPowerManagement.kext don't load;
kernel[0]: ACPI_SMC_PlatformPlugin::start - waitForService(resourceMatching(AppleIntelCPUPowerManagement) timed out

The following message indicates that you are clocked over 2.96 GHz, but haven't corrected the CPU section of your DSDT to pass CStates to the OS, see page 1;
kernel[0]: ACPI_SMC_PlatformPlugin::gatherCStateOverrides - failed to set c-state demotion data: -1

Use demong1's MacPro4_1.plist to get CPUPLimit speed step down clocking, see page 1.

[The Real Deal]

The AppleIntelCPUPowerManagementClient.kext is not shown in my system profiler/extensions.

Here is my list of kext (E/E) (BIOS F7 and different install)


AppleIntelPIIXATA
Fakesmc
IOAHCIBlockStorageInjector
JMicronATA
LegacyHDA
LegacyJMB36xSATA
OpenHaltRestart




I thought that none of these kexts, acted like a disabler and interacted with AppleIntelCPU.....


My CPU section in DSDT is not modded at the moment cause i'm still searching a maximum infos about this subject. I don't want to brick my CPU with a bad manip.

And the demon plist was placed in the right kext, and this last installed with kext utility before the screenshots.



Thx.

[d00d]

The Real Deal, on Nov 25 2009, 02:52 PM, said:

The AppleIntelCPUPowerManagementClient.kext is not shown in my system profiler/extensions.

Here is my list of kext (E/E) (BIOS F7 and different install)

AppleIntelPIIXATA
Fakesmc
IOAHCIBlockStorageInjector
JMicronATA
LegacyHDA
LegacyJMB36xSATA
OpenHaltRestart

I thought that none of these kexts, acted like a disabler and interacted with AppleIntelCPU.....

My CPU section in DSDT is not modded at the moment cause i'm still searching a maximum infos about this subject. I don't want to brick my CPU with a bad manip.

And the demon plist was placed in the right kext, and this last installed with kext utility before the screenshots.

Thx.

Then you are loading a disabler.
Do you have an Extensions.mkext that contains a disabler?
If you don't trust that the CPU modifications to DSDT that I describe are valid, then you can clock at 2.96 GHz or lower, and you will automatically get CStates.

[The Real Deal]

I have an Extensions.mkext built from scratch with kext utility, no disabler or nullcpu in E/E when the app proceed.

I fully trust your mod, i am a beginner and before applying something, the best way for me to learn is to find how does it work and why.


This mob drive me nuts.    Anyway, thx for your help.

[d00d]

The Real Deal, on Nov 25 2009, 04:45 PM, said:

I have an Extensions.mkext built from scratch with kext utility, no disabler or nullcpu in E/E when the app proceed.

I fully trust your mod, i am a beginner and before applying something, the best way for me to learn is to find how does it work and why.

This mob drive me nuts.    Anyway, thx for your help.

No problem, it's better to understand what you are doing first.
AppleIntelCPUPowerManagementClient.kext isn't loading, but is AppleIntelCPUPowerManagement.kext loading?
Dumb question perhaps, but is it possible that one or both were deleted from /System/Library/Extensions/?

[The Real Deal]

Hey d00d

Even both are loaded (and thus present in S/L/E), no disabler, it doesn't change anything. I checked everything twice.



Did you deleted a file somewhere related with the power management? If my memory serves me right, i read something about that through the board.

And better of all, without a disabler, i lost again my overall perfs (decrease by 50%).. with 10.6, no disabler were used, it was fine. 10.6.2 introduced an update of those two kexts, but you are aware about it.

[d00d]

The Real Deal, on Nov 26 2009, 09:15 AM, said:

Hey d00d

Even both are loaded (and thus present in S/L/E), no disabler, it doesn't change anything. I checked everything twice.

Did you deleted a file somewhere related with the power management? If my memory serves me right, i read something about that through the board.

And better of all, without a disabler, i lost again my overall perfs (decrease by 50%).. with 10.6, no disabler were used, it was fine. 10.6.2 introduced an update of those two kexts, but you are aware about it.

So now you have both kexts loading, but no CPUPlimit.
I haven't deleted any files related to native power management, nor noticed any performance drop.
Both binaries in AppleIntelCPUPowerManagementClient.kext and AppleIntelCPUPowerManagement.kext are dated 20090801, so how have these been changed for 10.6.2?
Running at 3.2 GHz without making the CPU DSDT changes means that you are running without CStates (and possibly affecting CPUPlimit?), and therefore not running with full native power management.
Perhaps that is why you see a performance loss.
I suggest you clock to 2.96 GHz or lower to automatically get CStates, to see if you get CPUPlimit then.
If your 3.2 GHz *is* base 2.96 GHz with x22 turbo, then I don't know what to suggest at this point.

[digital_dreamer]

d00d, on Nov 23 2009, 10:35 AM, 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)
						}
					}
				}

Thanks for bringing this issue up again, d00d. My script was coded to remove the IRQ and following line during the CMOS reset fix. I suppose I should remove/comment that portion out.
I originally had it in because on some boards these lines would cause a KP. I know this is for the UD5, but are some boards where you would want those lines out? I might understand this better if I knew what the lines do - respond to a interrupt request?

MAJ

[d00d]

digital_dreamer, on Nov 26 2009, 05:43 PM, said:

Thanks for bringing this issue up again, d00d. My script was coded to remove the IRQ and following line during the CMOS reset fix. I suppose I should remove/comment that portion out.
I originally had it in because on some boards these lines would cause a KP. I know this is for the UD5, but are some boards where you would want those lines out? I might understand this better if I knew what the lines do - respond to a interrupt request?

MAJ

There's no IRQ in the RTC section of the DSDT obtained from an Apple hardware MacPro4,1, so I don't know the logic behind when not having it on the GA-EX58 MBs that it causes sleep issues.
I can't speak to MBs from other manufacturers, as I've only worked with Gigabyte's X58 chipset MB.
I'd suggest that the script conditionally not remove the IRQ when the user is installing OS X on a GA-EX58, and removing it when installing on an MB where it's known to causes problems.

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]

d00d, on Nov 26 2009, 04:25 PM, said:

So now you have both kexts loading, but no CPUPlimit.
I haven't deleted any files related to native power management, nor noticed any performance drop.
Both binaries in AppleIntelCPUPowerManagementClient.kext and AppleIntelCPUPowerManagement.kext are dated 20090801, so how have these been changed for 10.6.2?
Running at 3.2 GHz without making the CPU DSDT changes means that you are running without CStates (and possibly affecting CPUPlimit?), and therefore not running with full native power management.
Perhaps that is why you see a performance loss.
I suggest you clock to 2.96 GHz or lower to automatically get CStates, to see if you get CPUPlimit then.
If your 3.2 GHz *is* base 2.96 GHz with x22 turbo, then I don't know what to suggest at this point.

My setting is: 160X20 and.. turbo enabled, so X22 with one core I will set the defaut value, maybe it'll operate a change like you suggest.


btw, do you have a score at geekbench 32/64, @ 4.2 + RAM specs please?