QUOTE (Slice @ Dec 8 2011, 09:05 AM)

PS. CPU0 <-> P001 naming does matter.
Ok thanks, will try it and watch a difference.
One problem is still left: Sometimes sleepmode just sleeps monitor and hds, but not the whole computer including cpus, the power led still is on. Sometimes the computer completly sleeps, also cpu and power led blinks, system is quiet. This behaviour can only be changed by restarting computer.
Any idea what could cause this randomly phenomena?
Sleep/wake are power states. Get native CPU power management working right and that issue could fix itself.
Slice:
Dec 8 11:44:40 localhost kernel[0]: AppleACPICPU: ProcessorId=1 LocalApicId=0 Enabled
Dec 8 11:44:40 localhost kernel[0]: AppleACPICPU: ProcessorId=2 LocalApicId=1 Enabled
Dec 8 11:44:40 localhost kernel[0]: AppleACPICPU: ProcessorId=3 LocalApicId=130 Disabled
Dec 8 11:44:40 localhost kernel[0]: AppleACPICPU: ProcessorId=4 LocalApicId=131 Disabled
CODE
Scope (_PR)
{
Processor (P001, 0x01, 0x00000810, 0x06) {}
Alias (P001, CPU1)
Processor (P002, 0x02, 0x00000000, 0x00) {}
Alias (P002, CPU2)
Processor (P003, 0x03, 0x00000000, 0x00) {}
Alias (P003, CPU3)
Processor (P004, 0x04, 0x00000000, 0x00) {}
Alias (P004, CPU4)
}
It can depend on which state your CPU - even GPU, ethernet, USB controller - is in. If all parts aren't playing by the rules (ACPI as interpreted by OS X) then you can have this kind of unpredictable behavior when entering or exiting S3/S4 states.
The best you can do is to try to get as many aspects of power management working as "Mac-like" as you can.
Some reading material, use it for inspiration:
http://www.insanelymac.com/forum/index.php?showtopic=168014http://www.projectosx.com/forum/index.php?showtopic=564http://www.insanelymac.com/forum/index.php?showtopic=225766 (<--obsolete files but good information)
This post has been edited by Gringo Vermelho: Dec 10 2011, 03:54 PM
QUOTE (Gringo Vermelho @ Dec 8 2011, 05:51 PM)

Dec 8 11:44:40 localhost kernel[0]: AppleACPICPU: ProcessorId=1 LocalApicId=0 Enabled
Dec 8 11:44:40 localhost kernel[0]: AppleACPICPU: ProcessorId=2 LocalApicId=1 Enabled
Dec 8 11:44:40 localhost kernel[0]: AppleACPICPU: ProcessorId=3 LocalApicId=130 Disabled
Dec 8 11:44:40 localhost kernel[0]: AppleACPICPU: ProcessorId=4 LocalApicId=131 Disabled
CODE
Scope (_PR)
{
Processor (P001, 0x01, 0x00000810, 0x06) {}
Alias (P001, CPU1)
Processor (P002, 0x02, 0x00000000, 0x00) {}
Alias (P002, CPU2)
Processor (P003, 0x03, 0x00000000, 0x00) {}
Alias (P003, CPU3)
Processor (P004, 0x04, 0x00000000, 0x00) {}
Alias (P004, CPU4)
}
It may depends also on SSDT tables.
But it is good news. We can write here 0 and MacOSX calculates own values and enables all Cores independent on DSDT.
Hi again

I puzzled out that one reason that prevents sleep was an old firewire interface. Romving it's services, the computer nogoes to sleep for 1 second and then wake up a little (harddrives and fans on again), but still black, until I press a key or mouse (like S1 sleep).
System log:
QUOTE
Oct 18 22:56:34 wstation loginwindow[1109]: loginwindow SleepWakeCallback WILL sleep
Oct 18 22:56:40 wstation com.apple.autofsd[1117]: automount: Mount for UUID=E728D092-E738-4634-B723-BE4B3B46BC93 has no path for the directory to mount
Oct 18 22:56:45 wstation loginwindow[1109]: loginwindow SleepWakeCallback will power on
Oct 18 22:56:46 wstation loginwindow[1109]: handleUnlockResult
Oct 18 22:56:46 wstation configd[16]: Sleep: Success - AC - Software Sleep
Oct 18 22:56:46 wstation configd[16]: Wake: Success - AC
Oct 18 22:56:46 wstation configd[16]: Hibernate Statistics
Oct 18 22:56:53 wstation configd[16]: network configuration changed.
Oct 18 22:56:53 wstation configd[16]: PMConnection AirPort configd plug-in com.apple.powermanagement.applicationresponse.slowresponse 7935 ms
Oct 18 22:56:53 wstation configd[16]: PMConnection IPConfiguration com.apple.powermanagement.applicationresponse.slowresponse 7938 ms
Any idea now what could cause this?