Extracting the tables I found the DSDT does not have all the scope for the processor, and two ssdt tables come along.
It's similar problem as the dell Vostro 3300.
Finaly change in my DSDT the scope_PR with
Scope (_PR)
{
Processor (P001, 0x01, 0x00000410, 0x06)
{
}
Processor (P002, 0x02, 0x00000410, 0x06)
{
}
Processor (P003, 0x03, 0x00000410, 0x06)
{
}
Processor (P004, 0x04, 0x00000410, 0x06)
{
}
Processor (P005, 0x05, 0x00000410, 0x06)
{
}
Processor (P006, 0x06, 0x00000410, 0x06)
{
}
Processor (P007, 0x07, 0x00000410, 0x06)
{
}
Processor (P008, 0x08, 0x00000410, 0x06)
{
}
Method (PNOT, 0, Serialized)
{
Notify (P001, 0x80)
Sleep (0x64)
Notify (P001, 0x81)
Notify (P002, 0x80)
Sleep (0x64)
Notify (P002, 0x81)
Notify (P003, 0x80)
Sleep (0x64)
Notify (P003, 0x81)
Notify (P004, 0x80)
Sleep (0x64)
Notify (P004, 0x81)
Notify (P005, 0x80)
Sleep (0x64)
Notify (P005, 0x81)
Notify (P006, 0x80)
Sleep (0x64)
Notify (P006, 0x81)
Notify (P007, 0x80)
Sleep (0x64)
Notify (P007, 0x81)
Notify (P008, 0x80)
Sleep (0x64)
Notify (P008, 0x81)
}
}
Now with the mod I have at boot Pstate and cstates generated but still the cpu is on max.
ioreg -lw0 | grep CSTInfo returns nothing
ioreg -lw0 | grep PerformanceStateArray returns the array ok
I tried to create a ssdt.aml from the two but it makes no difference.
Not sure where to from now?