Jump to content

SMC Monitor


oldnapalm
 Share

87 posts in this topic

Recommended Posts

that is a ok?

 

 

Jan 25 11:00:50 localhost kernel[0]: IT87x: based on code from Open Hardware Monitor project by Michael Möller (C) 2010
Jan 25 11:00:50 localhost kernel[0]: IT87x: mozodojo (C) 2011
Jan 25 11:00:50 localhost kernel[0]: IntelCPUMonitor: Based on code by mercurysquad, superhai (C)2008
Jan 25 11:00:50 localhost kernel[0]: User defined TjMax=0
Jan 25 11:00:50 localhost kernel[0]: IT87x: found ITE IT8728F
Jan 25 11:00:50 localhost kernel[0]: IntelCPUMonitor: CPU family 0x6, model 0x2a, stepping 0x7, cores 4, threads 8
Jan 25 11:00:50 localhost kernel[0]: IntelCPUMonitor: Using efi
Jan 25 11:00:50 localhost kernel[0]: IntelCPUMonitor: BusClock=100MHz FSB=401MHz
Jan 25 11:00:50 localhost kernel[0]: IntelCPUMonitor: Platform string T9
Jan 25 11:00:50 localhost kernel[0]: IntelCPUMonitor: CPU0 Tjmax 98
Jan 25 11:00:50 localhost kernel[0]: IntelCPUMonitor: CPU1 Tjmax 98
Jan 25 11:00:50 localhost kernel[0]: IntelCPUMonitor: CPU2 Tjmax 98
Jan 25 11:00:50 localhost kernel[0]: IntelCPUMonitor: CPU3 Tjmax 98

 

Slice only Voltage on cpu and ddr is very High ..because ?

I have setting in bios 1.36 on cpu and 1.5 on DDR

 

schermata012455952alle1.png

Link to comment
Share on other sites

Hello everyone,

 

SMC Monitor don't work for me.I use new IntelCPUMonitor (32/64 bit) by mitch_de.

My processor is sandy bridge i7 2630QM @2,00Ghz.

 

My kernel log.

 

http://pastebin.com/6u4ieg2z

 

Jan 26 16:43:25 localhost kernel[0]: IntelCPUMonitor: CPU family 0x6, model 0x2a, stepping 0x7, cores 4, threads 8

Jan 26 16:43:25 localhost kernel[0]: IntelCPUMonitor: Using efi

Jan 26 16:43:25 localhost kernel[0]: IntelCPUMonitor: BusClock=99MHz FSB=399MHz

Jan 26 16:43:25 localhost kernel[0]: IntelCPUMonitor: Platform string T9

Jan 26 16:43:25 localhost kernel[0]: IntelCPUMonitor: CPU0 Tjmax 100

Jan 26 16:43:25 localhost kernel[0]: IntelCPUMonitor: CPU1 Tjmax 100

Jan 26 16:43:25 localhost kernel[0]: IntelCPUMonitor: CPU2 Tjmax 100

Jan 26 16:43:25 localhost kernel[0]: IntelCPUMonitor: CPU3 Tjmax 100

DSDT without ATI.aml.zip

Link to comment
Share on other sites

  • 2 weeks later...
  • 1 month later...

I read all 5 pages of this thread and have not found a simple Yes or No to the following question.

 

Are the live CPU clocks and voltage readings precise or not?

 

In my case, no mater what P-States variables I dictate OSPM to use, according to SMC Monitor they always stay the same.

Ex: Q6600 bios set to 3.43GHz: Setting P0 to 3.43Ghz or 3.449GHz SMC Monitor always writes it as 3.411Ghz Where does it read it from, I don't know?

Same with voltage setting P3 to Vid 0.9375V or 0.19125V SMC Monitor always writes it as 1.1625V Where does it read it from, I don't know?

My _PSS P-States are all populated. There are no 0(zeros) for MHz and THD in milliwatts.

Generate p-states / C-states are set to no.

 

I can't figure it out and it's driving me nuts! A

It's as if there is a P-State Object hard coded for the Q6600 somewhere and SMC Monitor simply reads that data ever time it gets a P-State change notification.

OR it's using a formula and some variable, for which it can't read correctly, to populate the P-States window.

Is it asking the BIOS/ACPI/CPU (not OSPM) for the data?

 

It's also frustrating because the system acts as if my custom P-States are in effect but if I base my self on SMC Monitor, OS X's OSPM is buggy.

 

I've tried PStatChanger.app just to read the variables and it's behaviour is similar. It reads the MHz's ok but VID's and Power Tc's never change (same values as SMC Monitor)

 

also if SMC Monitor is open while IOREG is also open, IOREG's cpu usage increase and responses are very very slow. Is SMC Monitor also using the same resources as IOREG?

 

Basically I am looking for a tool that will give me the correct P-States and live P-State change history so I can see if my changes are being read and used correctly by OSPM.

 

Actually my gut feelings tell me my P-States are being used and the tools reading them are wrong. but until I am 100% sure.....

 

PS I am aware if the amount of time and energy required to create tools/apps for the community. Just in case you thought I was bitching. Which I am not, in fact I'm VERRY GRATEFUL!

Link to comment
Share on other sites

it reads values out of SMC, these are injected via SuperIO ( Winbond, ITE, Fintek)

you can get HWMonitor from HWSensor Project which is basicly the same

MSRDumper.kext reads the actual speedsteps in kernel ( so as near to the core you can have it)

 

3 possibilities all read out of the same pot ( CPU)

 

the thing is, intel, apple dont let you look into, how they do it,

but maybe we want to know to much about.

Link to comment
Share on other sites

it reads values out of SMC, :

FakeSMC?

 

these are injected via SuperIO ( Winbond, ITE, Fintek):

I have a vanilla install P35 with ICH9R.

 

you can get HWMonitor from HWSensor Project which is basicly the same :

I did and get the same readings, they are all off.

 

MSRDumper.kext reads the actual speedsteps in kernel ( so as near to the core you can have it):

It works, in console I see the all available Multi's except 6(bug) and the multi currently in use. The multis are properly used and reported.

 

3 possibilities all read out of the same pot ( CPU):

Yes correct but still does not make sense. ex. I telling the cpu to be at 3.430GHz @ 1.3V when switching to multi 9. Why can't it report back the same values(retorical)? No mater what I tell it, it always reports back the same erroneous values except the multi, those are ok.

 

the thing is, intel, apple dont let you look into, how they do it,but maybe we want to know to much about.:

To get the values do we absolutely have to go through OSPM or can we technically ask the cpu directly?

 

Is this MSRDumper open source?

Link to comment
Share on other sites

  • 1 month later...
  • 2 weeks later...
 Share

×
×
  • Create New...