Contribute
Register

HP ProBook Installer 6.1: 4x30s and 4x40s support

HP ProBook Installer 6.1 (beta): Ivy bridge support

It says: P State 8, 29 and Current State: 8

EDIT: sometimes it also says: P State 8 and Current State: 8 or P State 29 and Current State: 29

Is that ok?

Thanks!
Does not sound right...
You can also try this.
Or just use your pc and watch HW monitor, enough to see if u get more then the 2 basic p-states, but not if you want more details.
 
HP ProBook Installer 6.1 (beta): Ivy bridge support

Run it again, but this time do something to simulate activity (go to Launchpad, then open and close all groups you have there, start or stop some programs, you may even make one GeekBench run) and then see if these are the only states you get.
You have SSDT.aml installed in /Extra, right?

Edit: with my current SSDT.aml (generated by the SSDT generator inside the ProBook Installer), I get these states for my CPU: 4/8/13 4:37:48 PM, P States: 8, 11, 15, 19, 22, 26

philip, I'm testing with no ssdt file in my extra folder. I'll let you know in a minute!
 
HP ProBook Installer 6.1 (beta): Ivy bridge support

Does not sound right...
You can also try this.
Or just use your pc and watch HW monitor, enough to see if u get more then the 2 basic p-states, but not if you want more details.

According to this kext, I have even more states:

4/8/13 4:45:56.000 PM kernel[0]: AICPUPMI: CPU P-States [ 8 11 15 19 22 25 26 29 30 32 ]

philip, I'm testing with no ssdt file in my extra folder. I'll let you know in a minute!

For this laptop, without SSDT.aml, you won't get more PStates than the lowest and the highest possible for your CPU.
 
HP ProBook Installer 6.1 (beta): Ivy bridge support

According to this kext, I have even more states:

4/8/13 4:45:56.000 PM kernel[0]: AICPUPMI: CPU P-States [ 8 11 15 19 22 25 26 29 30 32 ]

philip, while running geekbench, dpci manager says: P States: 8, 28, 29 (with the same geekbench score I was reaching before (6500)).

I will try now with the ssdt file in extra folder.

Thanks!
 
HP ProBook Installer 6.1 (beta): Ivy bridge support

For this laptop, without SSDT.aml, you won't get more PStates than the lowest and the highest possible for your CPU.

philip, you are right. With ssdt file in the extra folder: P States: 8, 11, 15, 19, 23, 26, 27, 28, 29 (but final geekbench score still the same (6500)).

Just testing to see differences!

Thanks!
 
HP ProBook Installer 6.1 (beta): Ivy bridge support

Well, I bet you'll see the difference in power consumption (ergo - battery time) and heat.
 
HP ProBook Installer 6.1 (beta): Ivy bridge support

Guys, what do you think about merging the DSDT generator with the SSDT generator? The SSDT generation is now fully automated procedure and both the DSDT and the SSDT are mandatory component, so I think the DSDT postinstall script can call the SSDT generator script as well.
 
HP ProBook Installer 6.1 (beta): Ivy bridge support

Guys, what do you think about merging the DSDT generator with the SSDT generator? The SSDT generation is now fully automated procedure and both the DSDT and the SSDT are mandatory component, so I think the DSDT postinstall script can call the SSDT generator script as well.

IMHO, it's a wonderful idea!
Less available options in the installer it means less errors/problems possibilities.
So for me, go on!

Thanks!
 
HP ProBook Installer 6.1 (beta): Ivy bridge support

Guys, what do you think about merging the DSDT generator with the SSDT generator? The SSDT generation is now fully automated procedure and both the DSDT and the SSDT are mandatory component, so I think the DSDT postinstall script can call the SSDT generator script as well.

There is one reason I can think of to keep them separate... and that is the case you have just upgraded your CPU and now wish to update only the SSDT without complicating matters in generating a new DSDT, and all the process involved with that including removing /Extra/dsdt.aml, installing Mini SSDTs, etc.
 
HP ProBook Installer 6.1 (beta): Ivy bridge support

There is one reason I can think of to keep them separate... and that is the case you have just upgraded your CPU and now wish to update only the SSDT without complicating matters in generating a new DSDT, and all the process involved with that including removing /Extra/dsdt.aml, installing Mini SSDTs, etc.

RM, after a CPU upgrade, it's "recommended" to re-patch the DSDT and, obviously, re-generate the SSDT, right?
So, they can be merged without any particular problem, don't you think?

Thanks!
 
Back
Top