Compiler errors (not GUI)

[GoogleCodeExporter]

Ran 'make' in i7z folder, and after installing libncurses, got this:

gcc  -g -O0 -fomit-frame-pointer -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 
-DBUILD_MAIN -Wall -Dx64_BIT -lncurses -lpthread -lrt  i7z.c helper_functions.c 
i7z_Single_Socket.c i7z_Dual_Socket.c -o i7z
i7z_Single_Socket.c: In function ‘print_i7z_socket_single’:
i7z_Single_Socket.c:557:16: warning: unused variable ‘time_to_save’
i7z_Dual_Socket.c: In function ‘print_i7z_socket’:
i7z_Dual_Socket.c:495:9: warning: implicit declaration of function 
‘logCpuFreq_dual_d’

What version of the product are you using (the download version or the svn
version and which one)? On what operating system?
BTW is it a 32-bit or a 64-bit OS/Kernel?
Downloaded the tar.gz, running 64-bit Ubuntu 11.04.

Original issue reported on code.google.com by buns...@gmail.com on 6 Dec 2011 at 4:17

[GoogleCodeExporter]

Hi

does it generate a i7z executable? if so, then you can ignore the warnings and 
run sudo ./i7z; i made a bunch of variables but not using them and thats why 
the compiler is throwing those warnings. 

thanks

Original comment by abhirana on 6 Dec 2011 at 7:20

[GoogleCodeExporter]

Oops. 

Lesson learned. Thanks for replying :)

It appears to show load for the whole core, and not just Logical Core [1-4] 
which is only 'half the physical core'. Is that correct? In my case, I have a 
load on (log.) Core 8, but not Core 4, but I think the load is showing up as C1.

Original comment by buns...@gmail.com on 6 Dec 2011 at 7:30

[GoogleCodeExporter]

What's cpufreq? It says the info in cpuinfo (/proc/cpuinfo, right?) might be 
wrong if cpufreq is enabled, but I don't know what that is...

Oh yes, is there any way to pin the temperatures to a panel? Can I use the GUI 
somehow for that?

Original comment by buns...@gmail.com on 6 Dec 2011 at 7:33

[GoogleCodeExporter]

yup, it just shows for one of the logical cores. had to make that choice as 
there was not enough space. though the core that is not printed (logical 
sibling) will have similar states. afaik the cores that are in siblings (same 
core but hyperthreads of that core) will always be in the same state

yeah cpuinfo is /proc/cpuinfo which doesnot reflect turbo. and when the machine 
is overclocked and cpufreq is enabled it doesnot calculate the current 
frequencies correctly as it assumes the base freq of 133.33 for nehalems and 
100 for sandy bridges as a fixed values. and most people with a locked cpu push 
the freq to a higher number

about the temperature, i dont log it somewhere right now but will do that too 
in the next version.

if you are good with scripting you could output the results of the following. 
you will need to install msr-tools (apt-get install msr-tools for debian, 
ubuntu)

sudo rdmsr 0x19C --bitfield 23:16 -d --processor 0

that will read the 100-temperature for the processor 0. the value returned is 
how far away the cpu is from the max temp (usually its 100 for i7s).
for me it prints out to be 18
so the real temperature is 100 - 18 = 82*C

you could output that in a file or something and then probably read in conky or 
i think if you have kde4 you could point one of those temperature applet to 
read from a file

Original comment by abhirana on 6 Dec 2011 at 7:47

[GoogleCodeExporter]

Original comment by abhirana on 31 Mar 2012 at 8:34

• Changed state: Done