How to get CPU temperature on Athlon 64 ...

tomazN · 02-01-2006, 05:21 AM

I just upgraded with an Athlon 64 3700+ and upgraded (clean install) from suse 9.3 to suse 10. Previously i had mbmon and gkrellm for showing me cpu temp. motherboard temp. and some fan speeds.

xmbmon version 2.05 ( i got it here: http://www.nt.phys.kyushu-u.ac.jp/sh.../download.html ) doesnt want to compile now anymore, error is the 64 bit cpu.

Error on compile:

Code:

/xmbmon205> ./configure
checking for gcc... gcc
checking for C compiler default output... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for a BSD-compatible install... /usr/bin/install -c
checking how to run the C preprocessor... gcc -E
checking for X... libraries /usr/X11R6/lib64, headers /usr/X11R6/include
checking for gethostbyname... yes
checking for connect... yes
checking for remove... yes
checking for shmat... yes
checking for IceConnectionNumber in -lICE... yes
checking build system type... Invalid configuration `x86_64-unknown-linux-gnu': machine `x86_64-unknown' not recognized
configure: error: /bin/sh AC-TOOLS/config.sub x86_64-unknown-linux-gnu failed

And if i use lm_sensors i get in mbmon only one temp. and even that is always at 22 degres, so it isnt ok.

Any info what other kind of monitoring software i could use to get cpu temp. atleast if possible. Or maybe get a 64bit version of mbmon somewhere, but i couldnt find it.

Thx for the answers.

okmyx · 02-01-2006, 06:15 AM

Have you tried search for mbmon or gkrellm in the yast/suse repositories rather than compiling them from source?

tomazN · 02-12-2006, 09:28 AM

There is no mbmon xmbmon or gkrellm rpm`s for Suse 10 64bit, or even 32 bit.

HappyTux · 02-12-2006, 10:52 AM

Looks like it is getting the machine architecture wrong what does the output of uname -m show you. It should be something like this.

Code:

>$uname -m
x86_64

Try ./configure --help to see if there is some variable you can pass to the configure script to tell it the arch it should be compiling for.

tomazN · 02-12-2006, 12:21 PM

yes i get x86_64 by uname -m ...

output of configure --help

Code:

`configure' configures this package to adapt to many kinds of systems.

Usage: ./configure [OPTION]... [VAR=VALUE]...

To assign environment variables (e.g., CC, CFLAGS...), specify them as
VAR=VALUE.  See below for descriptions of some of the useful variables.

Defaults for the options are specified in brackets.

Configuration:
  -h, --help              display this help and exit
      --help=short        display options specific to this package
      --help=recursive    display the short help of all the included packages
  -V, --version           display version information and exit
  -q, --quiet, --silent   do not print `checking...' messages
      --cache-file=FILE   cache test results in FILE [disabled]
  -C, --config-cache      alias for `--cache-file=config.cache'
  -n, --no-create         do not create output files
      --srcdir=DIR        find the sources in DIR [configure dir or `..']

Installation directories:
  --prefix=PREFIX         install architecture-independent files in PREFIX
                          [/usr/local]
  --exec-prefix=EPREFIX   install architecture-dependent files in EPREFIX
                          [PREFIX]

By default, `make install' will install all the files in
`/usr/local/bin', `/usr/local/lib' etc.  You can specify
an installation prefix other than `/usr/local' using `--prefix',
for instance `--prefix=$HOME'.

For better control, use the options below.

Fine tuning of the installation directories:
  --bindir=DIR           user executables [EPREFIX/bin]
  --sbindir=DIR          system admin executables [EPREFIX/sbin]
  --libexecdir=DIR       program executables [EPREFIX/libexec]
  --datadir=DIR          read-only architecture-independent data [PREFIX/share]
  --sysconfdir=DIR       read-only single-machine data [PREFIX/etc]
  --sharedstatedir=DIR   modifiable architecture-independent data [PREFIX/com]
  --localstatedir=DIR    modifiable single-machine data [PREFIX/var]
  --libdir=DIR           object code libraries [EPREFIX/lib]
  --includedir=DIR       C header files [PREFIX/include]
  --oldincludedir=DIR    C header files for non-gcc [/usr/include]
  --infodir=DIR          info documentation [PREFIX/info]
  --mandir=DIR           man documentation [PREFIX/man]

X features:
  --x-includes=DIR    X include files are in DIR
  --x-libraries=DIR   X library files are in DIR

System types:
  --build=BUILD     configure for building on BUILD [guessed]
  --host=HOST       cross-compile to build programs to run on HOST [BUILD]

Optional Packages:
  --with-PACKAGE[=ARG]    use PACKAGE [ARG=yes]
  --without-PACKAGE       do not use PACKAGE (same as --with-PACKAGE=no)
  --with-x                use the X Window System

Some influential environment variables:
  CC          C compiler command
  CFLAGS      C compiler flags
  LDFLAGS     linker flags, e.g. -L<lib dir> if you have libraries in a
              nonstandard directory <lib dir>
  CPPFLAGS    C/C++ preprocessor flags, e.g. -I<include dir> if you have
              headers in a nonstandard directory <include dir>
  CPP         C preprocessor

Then tried with ./configure --build=x86_64 or ./configure --host=x86_64 both result in a error. I only found those two options to be at least a little logical for building with them. Still no go.

HappyTux · 02-12-2006, 12:32 PM

Quote:

Originally Posted by tomazN

yes i get x86_64 by uname -m ...

output of configure --help

Code:

System types:
  --build=BUILD     configure for building on BUILD [guessed]
  --host=HOST       cross-compile to build programs to run on HOST [BUILD]

Then tried with ./configure --build=x86_64 or ./configure --host=x86_64 both result in a error. I only found those two options to be at least a little logical for building with them. Still no go.

I would say those were the options to try the only other thing I can think of is going through the configure file itself and see if it is hard coded in there somewhere or maybe in the files it is calling from the configure other than this I think I am out of ideas here.

tomazN · 02-13-2006, 09:55 AM

Tried everything by now. I saw some .deb files with not suported but compiled xmbmon for athlon 64 on the debian archives. Can i somehow get that on my Suse 10.0 ? Or anyone can suggest which monitoring program can i use to see my temperature from processor ? (I have athlon 64 3700+ and Nforce 4 ultra motherboard from epox).

HappyTux · 02-13-2006, 01:33 PM

Quote:

Originally Posted by tomazN

Tried everything by now. I saw some .deb files with not suported but compiled xmbmon for athlon 64 on the debian archives. Can i somehow get that on my Suse 10.0 ? Or anyone can suggest which monitoring program can i use to see my temperature from processor ? (I have athlon 64 3700+ and Nforce 4 ultra motherboard from epox).

You could try the alien program if it is available to you it will convert between IIRC .deb .rpm and .tar.gz from Slackware also if you can get the source package from the Debian repos then have a look at it you may be able to build it from source I just checked here it is installable so it should build for you hopefully.

tomazN · 02-13-2006, 03:38 PM

Got it converted with alien fine. Also installed fine and showing correct temperatures if i use only mbmon or xmbmon. But if i use mbmmon as a daemon and with gkrellm then it shows wrong, have to figure that part yet. But atleast i got it on the box fine. Thx for this great info on alien. Will help sole some more problems i think

HappyTux · 02-13-2006, 04:29 PM

Quote:

Originally Posted by tomazN

Got it converted with alien fine. Also installed fine and showing correct temperatures if i use only mbmon or xmbmon. But if i use mbmmon as a daemon and with gkrellm then it shows wrong, have to figure that part yet. But atleast i got it on the box fine. Thx for this great info on alien. Will help sole some more problems i think

If you know the correct temperatures before you start the gkrellm then there is an adjustment factor you can use most times just up/down till you get it where you think it is right and you should be good to go.

tomazN · 02-13-2006, 04:51 PM

Only problem is it`s using the output from lm_sensors which is totaly wrong ...

Code:

/it87-isa-0290
Adapter: ISA adapter
VCore 1:   +2.58 V  (min =  +3.66 V, max =  +1.74 V)   ALARM
VCore 2:   +3.28 V  (min =  +1.66 V, max =  +3.26 V)
+3.3V:     +3.04 V  (min =  +0.13 V, max =  +2.02 V)
+5V:       +5.03 V  (min =  +0.81 V, max =  +1.40 V)
+12V:     +10.88 V  (min =  +2.56 V, max =  +3.14 V)
-12V:     -27.36 V  (min =  -3.55 V, max =  -0.85 V)
-5V:      -13.64 V  (min =  +3.82 V, max = -13.64 V)
Stdby:     +1.02 V  (min =  +0.00 V, max =  +0.00 V)
VBat:      +4.08 V
fan1:     11250 RPM  (min = 675000 RPM, div = 2)          ALARM
fan2:     135000 RPM  (min =    0 RPM, div = 1)          ALARM
fan3:     67500 RPM  (min =   -1 RPM, div = 2)          ALARM
M/B Temp:    -84°C  (low  =    +0°C, high =    +1°C)   sensor = diode   ALARM
CPU Temp:     -1°C  (low  =    -2°C, high =    +0°C)   sensor = diode   ALARM
Temp3:       -16°C  (low  =    +0°C, high =    -1°C)   sensor = diode   ALARM

mbmon hoever shows everything ok:

Code:

TEMP0 : 38.0
TEMP1 : 35.5
TEMP2 : 21.5
FAN0  :    0
FAN1  :  981
FAN2  :    0
VC0   :  +2.58
VC1   :  +3.28
V33   :  +1.52
V50P  :  +5.03
V12P  : +10.34
V12N  : -14.92
V50N  :  -7.71

I would like to use mbmon -r -P 1500 in gkrellm but i dont see no option to choose. Or can i disable lm_sensors r remove them somehow so they dont disturb gkrellm, i cant even chose which sensors to use, or tell gkrellm to which port mbmon is listening to. I remember i could do that on suse 9.3 but there i didnt have lm_sensors.

HappyTux · 02-13-2006, 05:09 PM

Quote:

Originally Posted by tomazN

Only problem is it`s using the output from lm_sensors which is totaly wrong ...

Code:

/it87-isa-0290
Adapter: ISA adapter
VCore 1:   +2.58 V  (min =  +3.66 V, max =  +1.74 V)   ALARM
VCore 2:   +3.28 V  (min =  +1.66 V, max =  +3.26 V)
+3.3V:     +3.04 V  (min =  +0.13 V, max =  +2.02 V)
+5V:       +5.03 V  (min =  +0.81 V, max =  +1.40 V)
+12V:     +10.88 V  (min =  +2.56 V, max =  +3.14 V)
-12V:     -27.36 V  (min =  -3.55 V, max =  -0.85 V)
-5V:      -13.64 V  (min =  +3.82 V, max = -13.64 V)
Stdby:     +1.02 V  (min =  +0.00 V, max =  +0.00 V)
VBat:      +4.08 V
fan1:     11250 RPM  (min = 675000 RPM, div = 2)          ALARM
fan2:     135000 RPM  (min =    0 RPM, div = 1)          ALARM
fan3:     67500 RPM  (min =   -1 RPM, div = 2)          ALARM
M/B Temp:    -84°C  (low  =    +0°C, high =    +1°C)   sensor = diode   ALARM
CPU Temp:     -1°C  (low  =    -2°C, high =    +0°C)   sensor = diode   ALARM
Temp3:       -16°C  (low  =    +0°C, high =    -1°C)   sensor = diode   ALARM

mbmon hoever shows everything ok:

Code:

TEMP0 : 38.0
TEMP1 : 35.5
TEMP2 : 21.5
FAN0  :    0
FAN1  :  981
FAN2  :    0
VC0   :  +2.58
VC1   :  +3.28
V33   :  +1.52
V50P  :  +5.03
V12P  : +10.34
V12N  : -14.92
V50N  :  -7.71

I would like to use mbmon -r -P 1500 in gkrellm but i dont see no option to choose. Or can i disable lm_sensors r remove them somehow so they dont disturb gkrellm, i cant even chose which sensors to use, or tell gkrellm to which port mbmon is listening to. I remember i could do that on suse 9.3 but there i didnt have lm_sensors.

I have never used the mbmon with the gkrellm but your right them temperatures you are getting from lm_sensors are strange indeed. Have you tried the xmbmon it is an X client front end to the mbmon so if all you want is the temperatures displayed it may be just what you are looking for.

tomazN · 02-13-2006, 05:16 PM

It works fine, but its soooo bad look and soo bad interface that i have to puke to be honest

I preffer gkrellm, and will work till i get it working or die, whichever comes first

HappyTux · 02-13-2006, 06:20 PM

Quote:

Originally Posted by tomazN

It works fine, but its soooo bad look and soo bad interface that i have to puke to be honest

I preffer gkrellm, and will work till i get it working or die, whichever comes first

Yeah most them X??? apps are butt ugly another idea may be Super Karamba which is what I use because the lm_sensor guys will not take the persons work who reverse engineered the uGuru chip on my Abit board to have support for his because they have to have a data sheet from the manufacturer but that is a rant for another time ... What I do is run the program (oguru) then grep the output for the parts I want and display it on my desktop with Super Karamba this may be something to check into.