#1
Posted 06 August 2009 - 01:28 PM
#2
Posted 06 August 2009 - 07:55 PM
Use mkexttool to edit extensions.mkext
Be sure to keep a backup!!!!
#3
Posted 06 August 2009 - 10:23 PM
I took disabler.kext out of extensions.mkext and out of /Extra/Extensions and now sleep works again.
Use mkexttool to edit extensions.mkext
Be sure to keep a backup!!!!
@jimmydigital00
You're right. Sleep mode's working after I removed Disabler.kext (IntelCPUPMDisabler).
edit:
Also, I tried to remove AppleIntelCPUPowerManagement.kext, the system couldn't get to sleep. I had to reinstall the kext.
I would like to know what AppleIntelCPUPowerManagement.kext is working for. I read some said that CPU temperature will increase if the kext was loaded.
#4
Posted 06 August 2009 - 10:56 PM
#5
Posted 06 August 2009 - 11:36 PM
I took disabler.kext out of extensions.mkext and out of /Extra/Extensions and now sleep works again.
Use mkexttool to edit extensions.mkext
Be sure to keep a backup!!!!
Can you please explain in more detail as I am needing just some hand holding. Thanks.
#6
Posted 06 August 2009 - 11:48 PM
Anyone can help me, the disabler.kext did not resolve the problem
#7
Posted 07 August 2009 - 12:02 AM
#8
Posted 07 August 2009 - 12:06 AM
#9
Posted 07 August 2009 - 12:11 AM
Should be located either in Extra or in System/Library/Extensions
Both Disabler and IntelCPUPMDisabler perform similar tasks so you may have one or the other.
Check for these files in
/Extra
/System/Library/Extensions
Also use mkext tool
to check the Extensions.mkext file as well.
You will need to create a new .mkext using the mkext tool after removing the file.
#10
Posted 07 August 2009 - 12:16 AM
#11
Posted 07 August 2009 - 12:18 AM
#12
Posted 07 August 2009 - 01:45 AM
I still can't do a timed sleep (which was a problem before the update), but manually from the Apple Menu works.
#13
Posted 07 August 2009 - 01:49 AM
I rolled back to mach_kernel 9.7 from 9.8 and that solved my sleep problems.
I still can't do a timed sleep (which was a problem before the update), but manually from the Apple Menu works.
Could you send me the 10.5.7 kernel? I don't have it available. thanks!
#14
Posted 07 August 2009 - 03:42 AM
#15
Posted 07 August 2009 - 04:05 AM
Disabler.kext also disables AppleEFIRuntime.kext and AppleSMC.kext (or something like that). Whats weird is that removing Disabler.kext fixes sleep for some while at the same time AppleEFIRuntime.kext is known to prevent sleep (including on my laptop). I just installed 10.5.8 so once I reboot I will know if sleep still works or not.Both Disabler and IntelCPUPMDisabler perform similar tasks so you may have one or the other.
#16
Posted 07 August 2009 - 05:47 AM
You can also try removing IntelCPUPMDisabler.kext
Should be located either in Extra or in System/Library/Extensions
Both Disabler and IntelCPUPMDisabler perform similar tasks so you may have one or the other.
Check for these files in
/Extra
/System/Library/Extensions
Also use mkext tool
to check the Extensions.mkext file as well.
You will need to create a new .mkext using the mkext tool after removing the file.
I got up this pass. But, how to install the new Extensions.mkext from mkext tool If when delete Extensions.mkext from System/Library/Extensions he is substitutes for original arquive?
obs: Sorry for my bad english? I am Brasilian. rsrs
#17
Posted 07 August 2009 - 06:06 AM
#18
Posted 07 August 2009 - 06:36 AM
I am running voodoopower as well to control p-states, as AppleIntelCPUPowerManagement is not working for that.
Under 10.5.7 sleep&resume worked fine without AppleIntelCPUPowerManagement.
#19
Posted 07 August 2009 - 07:23 AM
sleep doesnt work in 10.5.8..but its fine in previous versions..post solution if there any..tnx
Were u using EFI v9 or Chameleon 2 / EFI v10?
#20
Posted 07 August 2009 - 08:12 AM
I took disabler.kext out of extensions.mkext and out of /Extra/Extensions and now sleep works again.
Use mkexttool to edit extensions.mkext
just for the record:
deleting the kexts + removing the extensions.mkext (backup is booted) AND/OR (not sure) -f @darwin does the same, as either deleting or a -f boot creates a new extensions.mkext (from the kexts found in extensions folder) ?
i always do both : )
also i "touch" the extensions folder, and perform a permission repair before rebooting with -f.
can anybody give me an "amen" please, that this is correct... : )
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users



Sign In
Create Account








