> > Well, there is an mdb hack (enable cpudrv_direct_pm) along with a couple > of ioctl(2) calls (PM_DIRECT_PM and PM_SET_CURRENT_POWER) that could > give you direct control over the frequency. I'm not convinced you really > want to go there though as I think you are misreading the messages from > dmesg.
it would be at least a good thing to know, right now, the laptop gets hot quite fast, i dont really care about raw speed, but i do care about the battery, right now, i run out of it in 1.5 hours is it playing with those settings safe? what would i need to do? > > The messages you've listed are printed to the system log whenever the > maximum power level changes. These maximums are set outside the scope of > Solaris by ACPI (and Solaris just complies with the request). All > setting a new maximum means is that your processor cannot run at a > frequency any higher than the new max power frequency. It does not mean > that you processor is running at the new maximum frequency. So even when > you processor has a new max power frequency of 1833 MHz, it could still > be running at 1000 MHz. You'll need to use cpu_info (and possibly > dtrace) if you want to know what frequency your processor is currently > running at. nacho _______________________________________________ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org