View unanswered posts    View active topics

All times are UTC - 6 hours





Post new topic Reply to topic  [ 40 posts ] 
Go to page 1, 2, 3  Next

Print view Previous topic   Next topic  
Author Message
Search for:
PostPosted: Sat Jan 30, 2010 1:20 pm 
Offline
Joined: Wed Dec 10, 2003 8:31 pm
Posts: 1996
Location: /dev/null
Introduction
Monitorix is a great system monitoring perl script that uses rrd databases to log system data. It also displays them graphically through a webserver (lighttpd on R6). The Howto will show you how to install it on your R6 box and get it working with mythweb. Note that the entire process shouldn't take more than 5 minutes. I wanted to put a fair amount of detail into this guide in support of newbs.

Image

For some screenshots, see the screenshots page of the official application.

I'm going to assume that most LinHES users have a Windows box they can use to access their LH box. I recommending using PuTTY to ssh into your LinHES box to accomplish the tasks ahead. Remember that you can't ssh as user mythtv (I think this is still the case with R6 isn't it?) so ssh into your LinHES box as the user you setup and switch to the mythtv user to complete the steps.

Code:
$ su - mythtv


Credit Where Credit is Due
With the help of res over at the Arch forums (mostly res actually) the Arch community now has a PKGBUILD for Monitorix. I have adapted the Arch package for LinHES and it's working just fine on my R6 box. Read on if you'd like to try it on your R6 box.

General Steps (brief)
1) Make sure sensors and hddtemp are installed
2) Get the source, make and install the package
3) Configure monitorix for your system and make a slight modification to lighttpd's config

Step 1. Install sensors and hddtemp (optional but recommended)

If you wish to have monitorix log your system temps and hdd temps, you'll need two packages in the LinHES repos. Get them now if you don't already have them installed.

Code:
$ sudo pacman -S lm_sensors hddtemp


If you don't know how to setup lm_sensors see the end of this post for a quick walk through.

Step 2. Get the Files for Monitorix and Install

Do the following:
Code:
$ mkdir ~/monitorix
$ cd ~/monitorix


Download the package source:
Code:
$ wget http://www.techarp.com/graysky/monitorix-linhes.tar.gz


Make an md5 checksum file with to the downloaded source against the md5sum I generated:

Code:
$ echo "925540f5204e2aefdcb4ead6625807da  monitorix-linhes.tar.gz" > monitorix-linhes.md5sum


Now verify the md5sum of the file you just downloaded like this:

Code:
$ md5sum -c monitorix-linhes.md5sum
monitorix-linhes.tar.gz: OK


If it didn't return an OK like the example above, delete monitorix-linhes.tar.gz and redownload. If it still fails, PM me.

Once you're confident the file is authentic, extract it like this:
Code:
$ tar zxvf monitorix-linhes.tar.gz && cd monitorix-linhes


Build the package:

Code:
$ makepkg -s


It may tell you that you need a few dependencies including fakeroot and rrdtool. This is normal. You can sudo to download them via the standard:

Code:
$ sudo pacman -S package1 pacakage2


Now re-run the makepkg -s command. That should go through some steps and leave you with a brand new package you can install like this:

Code:
$ sudo pacman -U monitorix-1.5.0-1-any.pkg.tar.gz


That's it!

Step 3. Configure Monitorix and Lighttpd
Before you can start it, you must edit the conf file for Monitorix and make a small modification to lighttpd's conf file as well.

Open up /etc/lighttpd/lighttpd.conf and insert a single line as shown. Again you can use nano if you wish.

Code:
$ sudo  nano /etc/lighttpd/lighttpd.conf


Look for #### CGI module section which should look like this:
Code:
#### CGI module
cgi.assign                 = ( ".pl"  => "/usr/bin/perl",
                                ".cgi" => "/bin/bash")


Change the cgi line as follows:

Code:
#### CGI module
cgi.assign                 = ( ".pl"  => "/usr/bin/perl",
                                ".cgi" => "/usr/bin/perl")


BTW, see this bugreport where jams says this modification is safe to make.

Now restart lighttpd:
Code:
$ sudo sv restart lighttpd


Almost there, now we'll setup /etc/monitorix.conf to match your system. If you want a detailed description of what every little setting in the file controls, see the man page. I'm not going to get into all of them in this HOWTO.

Note that if you are upgrading from a previous version of monitorix (1.4.1 or 1.4.2) then YOU MUST NOT USE YOUR OLD /etc/monitorix.conf with this release! Simply re-create your settings using the provided file.

Code:
$ man monitorix.conf


Load the conf up in nano:
Code:
$ sudo nano /etc/monitorix.conf


The first part of the document has some settings of interest. They control some basic settings and tell monitorix which data/graphs you want logged and displayed. Do NOT change our $OSTYPE at all! Here are some suggested ones to change:

our $HOSTNAME - your hostname.
our $ENABLE_LMTEMP - switch this on if you wanna log your temps.
our @HDDTEMP_LIST - If you system has more than one hdd, add it to the array.

For example:
Code:
our @HDDTEMP_LIST = ("/dev/sda", "/dev/sdb");       # max 9 hard disk drives


our @MNT_LIST - If you want more drive partitions monitored, add them to the array (/myth should be there for you and / (root) is there by default without you adding it).

If you enabled the temp graph you'll also want to make changes to the our %SENSORS_LIST to match your own system. Here is an example from my system (Core2Duo chip).

Code:
our %SENSORS_LIST = ("MB" => "temp2",
                     "CPU1" => "Core 0",
                     "CPU2" => "Core 1",
                     "FAN1" => "fan1");


Again, at the end of the document I will give a quick howto for sensors. Also, you can always come back and re-edit this file at any time. You will need to restart monitorix whenever you make a change though.

Save the file after you have edited it to your liking. Now just start monitorix:

Code:
$ sudo /etc/rc.d/monitorix start


Remember, if you chance the conf file, you need to restart the monitorix daemon for the changes to get read.

Code:
$ sudo /etc/rc.d/monitorix restart


That's it. To see the data, browse to your mythweb. Note that it will take several minutes for data to get displayed graphically when you're starting with empty databases. Point your browser to:

http://IP.of.LinHES/monitorix/

If you like monitorix and want it to start automatically at boot, edit your /etc/runit/1.local and add a line for monitorix like so:

Code:
$sudo echo /etc/rc.d/monitorix start >> /etc/runit/1.local


That's it. Enjoy!

Mini Howto for Sensors
Okay, you installed sensors. First thing to do is to run the detect script to figure out which kernel modules are needed.

Code:
$ sudo sensors-detect


Answer yes to the questions and allow the script to finish scanning. When it does, You'll be presented with a line like this (again the results shown below are from my system - your results may vary):

Code:
Now follows a summary of the probes I have just done.
Just press ENTER to continue:

Driver `it87' (should be inserted):
  Detects correctly:
  * ISA bus, address 0x290
    Chip `ITE IT8718F Super IO Sensors' (confidence: 9)

Driver `coretemp' (should be inserted):
  Detects correctly:
  * Chip `Intel Core family thermal sensor' (confidence: 9)


What this is telling us is that there are two kernel modules needed for sensors to work: it87 and coretemp. To test them, modprobe them and then run sensors.

Code:
$ sudo modprobe it87
$ sudo modprobe coretemp
$ sensors
it8718-isa-0290
Adapter: ISA adapter
in0:         +0.94 V  (min =  +0.00 V, max =  +4.08 V)   
in1:         +1.86 V  (min =  +0.00 V, max =  +4.08 V)   
in2:         +3.30 V  (min =  +0.00 V, max =  +4.08 V)   
in3:         +2.99 V  (min =  +0.00 V, max =  +4.08 V)   
in4:         +4.08 V  (min =  +0.00 V, max =  +4.08 V)   ALARM
in5:         +0.00 V  (min =  +0.00 V, max =  +4.08 V)   ALARM
in6:         +4.08 V  (min =  +0.00 V, max =  +4.08 V)   ALARM
in7:         +3.01 V  (min =  +0.00 V, max =  +4.08 V)   
in8:         +3.09 V
fan1:        819 RPM  (min =   10 RPM)
fan2:          0 RPM  (min =    0 RPM)
temp1:       +33.0°C  (low  = +127.0°C, high = +127.0°C)  sensor = thermistor
temp2:       +20.0°C  (low  = +127.0°C, high = +60.0°C)  sensor = thermal diode
temp3:        -2.0°C  (low  = +127.0°C, high = +127.0°C)  sensor = thermistor
cpu0_vid:   +2.050 V

coretemp-isa-0000
Adapter: ISA adapter
Core 0:      +31.0°C  (high = +76.0°C, crit = +100.0°C) 

coretemp-isa-0001
Adapter: ISA adapter
Core 1:      +35.0°C  (high = +76.0°C, crit = +100.0°C)


So you can see the results for my system. I know that temp1 is the CPU temp and temp2 is the MB temp. Temp3 is meaningless since my board doesn't have an environment sensors. Core 0 and Core 1 are the temps of my two cores. Oh, and fan1 is the CPU fan. You can use these values in /etc/monitorix.conf as shown above for your system.

Note: to get the needed kernel modules loaded at a reboot, simply add them to the modules array in /etc/rc.conf (again, this example is from my system so don't just copy/paste into your file):

Code:
MODULES=($MOD_BLACKLIST_ acpi_cpufreq !cpufreq_ondemand coretemp it87)


P.S. If you find this package useful, please vote for the flyspray task in which I requested its incorporation into the official LinHES repo.

_________________
Retired KM user (R4 - R6.04); friend to LH users.


Last edited by graysky on Mon May 03, 2010 2:32 pm, edited 18 times in total.


Top
 Profile  
 
 Post subject:
PostPosted: Fri Feb 05, 2010 2:04 am 
Offline
Joined: Sun Sep 04, 2005 7:48 pm
Posts: 264
Location: Perth, Australia
Hi graysky,

Thanks for the guide, i'm looking into doing this now, but hit a hurdle..

Firstly, I needed fakeroot and rrdtool before the makepkg would get anywhere.

Then when I had those, I got the following error
Code:
[mythtv@macdoodles-mythtv monitorix]$ makepkg -s
==> Making package: monitorix 1.4.1-2 any (Fri Feb  5 16:01:32 WST 2010)
==> Checking Runtime Dependencies...
==> Checking Buildtime Dependencies...
==> Retrieving Sources...
  -> Found monitorix-1.4.1.tar.gz in build dir
  -> Found monitorix.rc.d in build dir
==> Validating source files with md5sums...
    monitorix-1.4.1.tar.gz ... Passed
    monitorix.rc.d ... FAILED
==> ERROR: One or more files did not pass the validity check!


The file is the right name, the correct contents... I even added +x to see if that would make a difference... all to no avail....

Any ideas?

Cheers,

Nathan

_________________
LinHES: R6 | MB: Asus M3N-H/HDMI | CPU: AMD ??Mhz
Capture: 2xHDHR DVB-T
Graphics: Onboard 8300|PSU: Corsair vx450w
Cooling: Zalman cu?,
Display: Benq xx projector


Top
 Profile  
 
 Post subject:
PostPosted: Fri Feb 05, 2010 2:26 pm 
Offline
Joined: Wed Dec 10, 2003 8:31 pm
Posts: 1996
Location: /dev/null
nmcaullay wrote:
Hi graysky,

Thanks for the guide, i'm looking into doing this now, but hit a hurdle..

Firstly, I needed fakeroot and rrdtool before the makepkg would get anywhere.

Then when I had those, I got the following error
Code:
[mythtv@macdoodles-mythtv monitorix]$ makepkg -s
==> Making package: monitorix 1.4.1-2 any (Fri Feb  5 16:01:32 WST 2010)
==> Checking Runtime Dependencies...
==> Checking Buildtime Dependencies...
==> Retrieving Sources...
  -> Found monitorix-1.4.1.tar.gz in build dir
  -> Found monitorix.rc.d in build dir
==> Validating source files with md5sums...
    monitorix-1.4.1.tar.gz ... Passed
    monitorix.rc.d ... FAILED
==> ERROR: One or more files did not pass the validity check!


The file is the right name, the correct contents... I even added +x to see if that would make a difference... all to no avail....

Any ideas?

Cheers,

Nathan


The md5sum failing is odd. I would think that if one just copy/pastes the text I put in the code block, the md5sum of the resulting file would be the same. I requested that this to get added to the official repo which will make this process much easier. Lemme see if I can find a webhost somewhere for the PKGBUILD.

EDIT: Found one and edited the first post of this thread.

As to the rrdtool dependence, it's in the PKGBUILD so that behavior is normal. Pacman will not allow your user to install dependencies - only root can do that (or sudo).

Go ahead and try it now :)

_________________
Retired KM user (R4 - R6.04); friend to LH users.


Top
 Profile  
 
 Post subject:
PostPosted: Sat Feb 06, 2010 8:42 am 
Offline
Joined: Sun Sep 04, 2005 7:48 pm
Posts: 264
Location: Perth, Australia
All I can say is ..... bloody marvelous!

Thanks for taking the effort to document this, it gives a great output for those of us interested in how the system is performing...

The only thing that is not turning up is the fan speed, but probably i stuffed some of the config somewhere!

Cheers, and thanks....

Nathan

_________________
LinHES: R6 | MB: Asus M3N-H/HDMI | CPU: AMD ??Mhz
Capture: 2xHDHR DVB-T
Graphics: Onboard 8300|PSU: Corsair vx450w
Cooling: Zalman cu?,
Display: Benq xx projector


Top
 Profile  
 
 Post subject:
PostPosted: Sat Feb 06, 2010 8:44 am 
Offline
Joined: Sun Sep 04, 2005 7:48 pm
Posts: 264
Location: Perth, Australia
2 things to note

1) Wait long enough and the fan speed comes through :)
2) It took me 22 minutes from start to finish to get this installed and configured... thanks again for the guide, most valuable.

Cheers,

NAthan

_________________
LinHES: R6 | MB: Asus M3N-H/HDMI | CPU: AMD ??Mhz
Capture: 2xHDHR DVB-T
Graphics: Onboard 8300|PSU: Corsair vx450w
Cooling: Zalman cu?,
Display: Benq xx projector


Top
 Profile  
 
 Post subject:
PostPosted: Sat Feb 06, 2010 9:14 am 
Offline
Joined: Wed Dec 10, 2003 8:31 pm
Posts: 1996
Location: /dev/null
Glad you're enjoying it. Some of the data gets logged once per minute (temps, cpu load, etc.) while others get logged every 5 mins I believe (file system status for example). The system fan could be in this 5-min category.

Remember to play around with the /etc/monitorix.conf to enable/disable different graphs.

BTW, I have been in contact with Jordi (the author of monitorix). He is considering the addition of GPU temp to his script.

_________________
Retired KM user (R4 - R6.04); friend to LH users.


Top
 Profile  
 
 Post subject:
PostPosted: Sat Feb 06, 2010 4:53 pm 
Offline
Joined: Fri Nov 03, 2006 6:25 pm
Posts: 47
Location: Montreal, Quebec
Cooool :D ,

I still have to figure out a few things but it installed like a charm. Great Howto again Graysky!

Keep up the good work !


Top
 Profile  
 
 Post subject:
PostPosted: Sat Feb 06, 2010 5:32 pm 
Offline
Joined: Wed Dec 10, 2003 8:31 pm
Posts: 1996
Location: /dev/null
Enjoy. What are you trying to figure out?

_________________
Retired KM user (R4 - R6.04); friend to LH users.


Top
 Profile  
 
 Post subject:
PostPosted: Sun Feb 07, 2010 5:04 am 
Offline
Joined: Sun Sep 04, 2005 7:48 pm
Posts: 264
Location: Perth, Australia
my money is on lm_sensors :)

_________________
LinHES: R6 | MB: Asus M3N-H/HDMI | CPU: AMD ??Mhz
Capture: 2xHDHR DVB-T
Graphics: Onboard 8300|PSU: Corsair vx450w
Cooling: Zalman cu?,
Display: Benq xx projector


Top
 Profile  
 
 Post subject:
PostPosted: Sun Feb 07, 2010 7:55 am 
Offline
Joined: Wed Dec 10, 2003 8:31 pm
Posts: 1996
Location: /dev/null
Post the output of:

$ sudo sensors-detect

_________________
Retired KM user (R4 - R6.04); friend to LH users.


Top
 Profile  
 
 Post subject:
PostPosted: Sun Feb 07, 2010 7:20 pm 
Offline
Joined: Fri Nov 03, 2006 6:25 pm
Posts: 47
Location: Montreal, Quebec
That's exactly it nmcaullay, lm sensors it bugging me, it does not give me lots of temp sensors and fans, here is the output of sensors-detect:

Code:
# sensors-detect revision 5249 (2008-05-11 22:56:25 +0200)

This program will help you determine which kernel modules you need
to load to use lm_sensors most effectively. It is generally safe
and recommended to accept the default answers to all questions,
unless you know what you're doing.

We can start with probing for (PCI) I2C or SMBus adapters.
Do you want to probe now? (YES/no):
Probing for PCI bus adapters...
Use driver `i2c-i801' for device 0000:00:1f.3: Intel ICH10

We will now try to load each adapter module in turn.
Module `i2c-i801' already loaded.
If you have undetectable or unsupported I2C/SMBus adapters, you can have
them scanned by manually loading the modules before running this script.

We are now going to do the I2C/SMBus adapter probings. Some chips may
be double detected; we choose the one with the highest confidence
value in that case.
If you found that the adapter hung after probing a certain address,
you can specify that address to remain unprobed.

Next adapter: ivtv i2c driver #0 (i2c-0)
Do you want to scan it? (YES/no/selectively):
Client found at address 0x1b
Handled by driver `wm8775' (already loaded), chip type `wm8775'
    (note: this is probably NOT a sensor chip!)
Client found at address 0x50
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 Yes
    (confidence 8, not a hardware monitoring chip)
Probing for `EDID EEPROM'...                                No
Client found at address 0x73
Probing for `FSC Poseidon II'...                            No
Probing for `FSC Heimdal'...                                No
Probing for `FSC Heracles'...                               No
Probing for `FSC Poseidon I'...                             No
Probing for `FSC Hermes'...                                 No
Probing for `FSC Scylla'...                                 No

Next adapter: SMBus I801 adapter at 1180 (i2c-1)
Do you want to scan it? (YES/no/selectively):
Client found at address 0x50
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 Yes
    (confidence 8, not a hardware monitoring chip)
Probing for `EDID EEPROM'...                                No
Client found at address 0x52
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 Yes
    (confidence 8, not a hardware monitoring chip)
Probing for `EDID EEPROM'...                                No

Next adapter: NVIDIA i2c adapter  (i2c-2)
Do you want to scan it? (YES/no/selectively):

Next adapter: NVIDIA i2c adapter  (i2c-3)
Do you want to scan it? (YES/no/selectively):

Next adapter: NVIDIA i2c adapter  (i2c-4)
Do you want to scan it? (YES/no/selectively):

Next adapter: NVIDIA i2c adapter  (i2c-5)
Do you want to scan it? (YES/no/selectively):

Next adapter: NVIDIA i2c adapter  (i2c-6)
Do you want to scan it? (YES/no/selectively):
Client found at address 0x50
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 No
Probing for `EDID EEPROM'...                                Yes
    (confidence 8, not a hardware monitoring chip)

Next adapter: NVIDIA i2c adapter  (i2c-7)
Do you want to scan it? (YES/no/selectively):

Next adapter: NVIDIA i2c adapter  (i2c-8)
Do you want to scan it? (YES/no/selectively):

Next adapter: NVIDIA i2c adapter  (i2c-9)
Do you want to scan it? (YES/no/selectively):

Some chips are also accessible through the ISA I/O ports. We have to
write to arbitrary I/O ports to probe them. This is usually safe though.
Yes, you do have ISA I/O ports even if you do not have any ISA slots!
Do you want to scan the ISA I/O ports? (YES/no):
Probing for `National Semiconductor LM78' at 0x290...       No
Probing for `National Semiconductor LM78-J' at 0x290...     No
Probing for `National Semiconductor LM79' at 0x290...       No
Probing for `Winbond W83781D' at 0x290...                   No
Probing for `Winbond W83782D' at 0x290...                   No
Probing for `IPMI BMC KCS' at 0xca0...                      No
Probing for `IPMI BMC SMIC' at 0xca8...                     No

Some Super I/O chips may also contain sensors. We have to write to
standard I/O ports to probe them. This is usually safe.
Do you want to scan for Super I/O sensors? (YES/no):
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor'...                   No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Fintek'...                       Yes
Found `Winbond W83627DHG Super IO Sensors'                  Success!
    (address 0x290, driver `w83627ehf')
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor'...                   No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Fintek'...                       No
Trying family `ITE'...                                      No

Some south bridges, CPUs or memory controllers may also contain
embedded sensors. Do you want to scan for them? (YES/no):
Silicon Integrated Systems SIS5595...                       No
VIA VT82C686 Integrated Sensors...                          No
VIA VT8231 Integrated Sensors...                            No
AMD K8 thermal sensors...                                   No
AMD K10 thermal sensors...                                  No
Intel Core family thermal sensor...                         Success!
    (driver `coretemp')
Intel AMB FB-DIMM thermal sensor...                         No

Now follows a summary of the probes I have just done.
Just press ENTER to continue:

Driver `w83627ehf' (should be inserted):
  Detects correctly:
  * ISA bus, address 0x290
    Chip `Winbond W83627DHG Super IO Sensors' (confidence: 9)

Driver `coretemp' (should be inserted):
  Detects correctly:
  * Chip `Intel Core family thermal sensor' (confidence: 9)

Do you want to overwrite /etc/conf.d/lm_sensors? (YES/no):
You should now start the lm_sensors service to load the required
kernel modules.


it does not find temp or fan sensors I am surprised here is the output of sensors:

Code:
[mythtv@Linhes ~]$ sensors
w83627dhg-isa-0290
Adapter: ISA adapter
VCore:       +2.04 V  (min =  +2.04 V, max =  +2.04 V)   ALARM
in1:        +13.46 V  (min = +13.46 V, max = +13.46 V)   ALARM
AVCC:        +4.08 V  (min =  +4.08 V, max =  +4.08 V)   ALARM
3VCC:        +4.08 V  (min =  +4.08 V, max =  +4.08 V)   ALARM
in4:         +2.04 V  (min =  +2.04 V, max =  +2.04 V)   ALARM
in5:         +2.04 V  (min =  +2.04 V, max =  +2.04 V)   ALARM
in6:         +6.53 V  (min =  +6.53 V, max =  +6.53 V)   ALARM
VSB:         +4.08 V  (min =  +4.08 V, max =  +4.08 V)   ALARM
VBAT:        +4.08 V  (min =  +4.08 V, max =  +4.08 V)   ALARM
Case Fan:      0 RPM  (min =    0 RPM, div = 128)  ALARM
CPU Fan:       0 RPM  (min =    0 RPM, div = 128)  ALARM
Aux Fan:       0 RPM  (min =    0 RPM, div = 128)  ALARM
fan4:          0 RPM  (min =    0 RPM, div = 128)  ALARM
Sys Temp:     -1.0°C  (high =  -1.0°C, hyst =  -1.0°C)  ALARM  sensor = diode
CPU Temp:     +0.0°C  (high =  +0.0°C, hyst =  +0.0°C)  ALARM  sensor = diode
AUX Temp:     +0.0°C  (high =  +0.0°C, hyst =  +0.0°C)  ALARM  sensor = diode
cpu0_vid:   +0.000 V

coretemp-isa-0000
Adapter: ISA adapter
Core 0:      +84.0°C  (high = +86.0°C, crit = +100.0°C)

coretemp-isa-0001
Adapter: ISA adapter
Core 1:      +80.0°C  (high = +86.0°C, crit = +100.0°C)

and yes I found out that it runs pretty hot! Not sure if it is reliable....

Thanks for any hints.


Top
 Profile  
 
 Post subject:
PostPosted: Sun Feb 07, 2010 8:16 pm 
Offline
Joined: Sun Sep 04, 2005 7:48 pm
Posts: 264
Location: Perth, Australia
Hey there,

wouldnt the following be the CPU?

Code:
Intel Core family thermal sensor...                         Success!
    (driver `coretemp')


Or is that some other sensor?

Seems quite high though? 80 degrees C....

Nathan

_________________
LinHES: R6 | MB: Asus M3N-H/HDMI | CPU: AMD ??Mhz
Capture: 2xHDHR DVB-T
Graphics: Onboard 8300|PSU: Corsair vx450w
Cooling: Zalman cu?,
Display: Benq xx projector


Top
 Profile  
 
 Post subject:
PostPosted: Mon Feb 08, 2010 2:12 pm 
Offline
Joined: Wed Dec 10, 2003 8:31 pm
Posts: 1996
Location: /dev/null
You are reading core temps but they are sky high - above the shutdown threshold for most C2D. I don't think that's accurate. Can you post the make/model of your motherboard?

You can find out all sorts of info on your hardware by running:

Code:
# dmidecode -q > info


Just copy/paste the output to the thread here. I'm guessing it's because R6 currently has an old version of sensors (3.0.2) when 3.1.2 is current and has up-to-date support.

_________________
Retired KM user (R4 - R6.04); friend to LH users.


Top
 Profile  
 
 Post subject:
PostPosted: Mon Feb 08, 2010 5:33 pm 
Offline
Joined: Fri Nov 03, 2006 6:25 pm
Posts: 47
Location: Montreal, Quebec
I figured the temperature was not accurate, the motherboard is Intel DG43NB. and yes I am running sensors 3.0.2-2
Code:
[root@Linhes mythtv]# pacman -Q | grep sens
lm_sensors 3.0.2-2



It's not the first Intel m/b that I have problems with lm_sensors, think it has a problem with them....

and here is the output of dmidecode, interesting.....taking notes...:



Code:
BIOS Information
   Vendor: Intel Corp.
   Version: NBG4310H.86A.0074.2009.0109.1614
   Release Date: 01/09/2009
   Address: 0xF0000
   Runtime Size: 64 kB
   ROM Size: 1024 kB
   Characteristics:
      PCI is supported
      BIOS is upgradeable
      BIOS shadowing is allowed
      ESCD support is available
      Boot from CD is supported
      Selectable boot is supported
      BIOS ROM is socketed
      EDD is supported
      5.25"/1.2 MB floppy services are supported (int 13h)
      3.5"/720 KB floppy services are supported (int 13h)
      3.5"/2.88 MB floppy services are supported (int 13h)
      Print screen service is supported (int 5h)
      8042 keyboard services are supported (int 9h)
      Serial services are supported (int 14h)
      Printer services are supported (int 17h)
      CGA/mono video services are supported (int 10h)
      ACPI is supported
      LS-120 boot is supported
      ATAPI Zip drive boot is supported
      BIOS boot specification is supported
      Targeted content distribution is supported

System Information
   Manufacturer:                                 
   Product Name:                                 
   Version:                                 
   Serial Number:                                 
   UUID: 08F78B7C-8589-11DD-AE68-0013D4D9C938
   Wake-up Type: Power Switch
   SKU Number: Not Specified
   Family: Not Specified

Base Board Information
   Manufacturer: Intel Corporation
   Product Name: DG43NB
   Version: AAE34877-402
   Serial Number: USNB838005BM
   Asset Tag: To be filled by O.E.M.
   Features:
      Board is a hosting board
      Board is replaceable
   Location In Chassis: To be filled by O.E.M.
   Type: Motherboard

Chassis Information
   Manufacturer:                                 
   Type: Desktop
   Lock: Not Present
   Version:                                 
   Serial Number:                                 
   Asset Tag:                                 
   Boot-up State: Safe
   Power Supply State: Safe
   Thermal State: Safe
   Security Status: None
   OEM Information: 0x00000000
   Height: Unspecified
   Number Of Power Cords: 1
   Contained Elements: 0

Processor Information
   Socket Designation: LGA775
   Type: Central Processor
   Family: Unknown
   Manufacturer: Intel(R) Corp.
   ID: FD 06 00 00 FF FB EB BF
   Version: Intel(R) Pentium(R) Dual  CPU  E2200  @ 2.20GHz   
   Voltage: 1.3 V
   External Clock: 200 MHz
   Max Speed: 4000 MHz
   Current Speed: 2200 MHz
   Status: Populated, Enabled
   Upgrade: Socket LGA775
   Serial Number: To Be Filled By O.E.M.
   Asset Tag: To Be Filled By O.E.M.
   Part Number: To Be Filled By O.E.M.

Cache Information
   Socket Designation: L1-Cache
   Configuration: Enabled, Not Socketed, Level 1
   Operational Mode: Write Back
   Location: Internal
   Installed Size: 32 KB
   Maximum Size: 32 KB
   Supported SRAM Types:
      Other
   Installed SRAM Type: Other
   Speed: Unknown
   Error Correction Type: None
   System Type: Unified
   Associativity: 8-way Set-associative

Cache Information
   Socket Designation: L2-Cache
   Configuration: Enabled, Not Socketed, Level 2
   Operational Mode: Varies With Memory Address
   Location: Internal
   Installed Size: 1024 KB
   Maximum Size: 1024 KB
   Supported SRAM Types:
      Other
   Installed SRAM Type: Other
   Speed: Unknown
   Error Correction Type: None
   System Type: Unified
   Associativity: 4-way Set-associative

Port Connector Information
   Internal Reference Designator: J1A1
   Internal Connector Type: None
   External Reference Designator: PS2Mouse
   External Connector Type: PS/2
   Port Type: Mouse Port

Port Connector Information
   Internal Reference Designator: J1A1
   Internal Connector Type: None
   External Reference Designator: Keyboard
   External Connector Type: PS/2
   Port Type: Keyboard Port

Port Connector Information
   Internal Reference Designator: J2A1
   Internal Connector Type: None
   External Reference Designator: TV Out
   External Connector Type: Mini Centronics Type-14
   Port Type: Other

Port Connector Information
   Internal Reference Designator: J2A2A
   Internal Connector Type: None
   External Reference Designator: COM A
   External Connector Type: DB-9 male
   Port Type: Serial Port 16550A Compatible

Port Connector Information
   Internal Reference Designator: J2A2B
   Internal Connector Type: None
   External Reference Designator: Video
   External Connector Type: DB-15 female
   Port Type: Video Port

Port Connector Information
   Internal Reference Designator: J3A1
   Internal Connector Type: None
   External Reference Designator: USB1
   External Connector Type: Access Bus (USB)
   Port Type: USB

Port Connector Information
   Internal Reference Designator: J3A1
   Internal Connector Type: None
   External Reference Designator: USB2
   External Connector Type: Access Bus (USB)
   Port Type: USB

Port Connector Information
   Internal Reference Designator: J3A1
   Internal Connector Type: None
   External Reference Designator: USB3
   External Connector Type: Access Bus (USB)
   Port Type: USB

Port Connector Information
   Internal Reference Designator: J9A1 - TPM HDR
   Internal Connector Type: Other
   External Reference Designator: Not Specified
   External Connector Type: None
   Port Type: Other

Port Connector Information
   Internal Reference Designator: J9C1 - PCIE DOCKING CONN
   Internal Connector Type: Other
   External Reference Designator: Not Specified
   External Connector Type: None
   Port Type: Other

Port Connector Information
   Internal Reference Designator: J2B3 - CPU FAN
   Internal Connector Type: Other
   External Reference Designator: Not Specified
   External Connector Type: None
   Port Type: Other

Port Connector Information
   Internal Reference Designator: J6C2 - EXT HDMI
   Internal Connector Type: Other
   External Reference Designator: Not Specified
   External Connector Type: None
   Port Type: Other

Port Connector Information
   Internal Reference Designator: J3C1 - GMCH FAN
   Internal Connector Type: Other
   External Reference Designator: Not Specified
   External Connector Type: None
   Port Type: Other

Port Connector Information
   Internal Reference Designator: J1D1 - ITP
   Internal Connector Type: Other
   External Reference Designator: Not Specified
   External Connector Type: None
   Port Type: Other

Port Connector Information
   Internal Reference Designator: J9E2 - MDC INTPSR
   Internal Connector Type: Other
   External Reference Designator: Not Specified
   External Connector Type: None
   Port Type: Other

Port Connector Information
   Internal Reference Designator: J9E4 - MDC INTPSR
   Internal Connector Type: Other
   External Reference Designator: Not Specified
   External Connector Type: None
   Port Type: Other

Port Connector Information
   Internal Reference Designator: J9E3 - LPC HOT DOCKING
   Internal Connector Type: Other
   External Reference Designator: Not Specified
   External Connector Type: None
   Port Type: Other

Port Connector Information
   Internal Reference Designator: J9E1 - SCAN MATRIX
   Internal Connector Type: Other
   External Reference Designator: Not Specified
   External Connector Type: None
   Port Type: Other

Port Connector Information
   Internal Reference Designator: J9G1 - LPC SIDE BAND
   Internal Connector Type: Other
   External Reference Designator: Not Specified
   External Connector Type: None
   Port Type: Other

Port Connector Information
   Internal Reference Designator: J8F1 - UNIFIED
   Internal Connector Type: Other
   External Reference Designator: Not Specified
   External Connector Type: None
   Port Type: Other

Port Connector Information
   Internal Reference Designator: J6F1 - LVDS
   Internal Connector Type: Other
   External Reference Designator: Not Specified
   External Connector Type: None
   Port Type: Other

Port Connector Information
   Internal Reference Designator: J2F1 - LAI FAN
   Internal Connector Type: Other
   External Reference Designator: Not Specified
   External Connector Type: None
   Port Type: Other

Port Connector Information
   Internal Reference Designator: J2G1 - GFX VID
   Internal Connector Type: Other
   External Reference Designator: Not Specified
   External Connector Type: None
   Port Type: Other

Port Connector Information
   Internal Reference Designator: J1G6 - AC JACK
   Internal Connector Type: Other
   External Reference Designator: Not Specified
   External Connector Type: None
   Port Type: Other

System Slot Information
   Designation: J6B2
   Type: x16 PCI Express
   Current Usage: In Use
   Length: Long
   ID: 0
   Characteristics:
      3.3 V is provided
      Opening is shared
      PME signal is supported

System Slot Information
   Designation: J6B1
   Type: x1 PCI Express
   Current Usage: Available
   Length: Short
   ID: 1
   Characteristics:
      3.3 V is provided
      Opening is shared
      PME signal is supported

System Slot Information
   Designation: J6D1
   Type: x1 PCI Express
   Current Usage: Available
   Length: Short
   ID: 2
   Characteristics:
      3.3 V is provided
      Opening is shared
      PME signal is supported

System Slot Information
   Designation: J7B1
   Type: x1 PCI Express
   Current Usage: Available
   Length: Short
   ID: 3
   Characteristics:
      3.3 V is provided
      Opening is shared
      PME signal is supported

System Slot Information
   Designation: J8B4
   Type: 32-bit PCI
   Current Usage: In Use
   Length: Short
   ID: 4
   Characteristics:
      3.3 V is provided
      Opening is shared
      PME signal is supported

System Slot Information
   Designation: J8D1
   Type: 32-bit PCI
   Current Usage: Available
   Length: Short
   ID: 5
   Characteristics:
      3.3 V is provided
      Opening is shared
      PME signal is supported

System Slot Information
   Designation: J8B3
   Type: 32-bit PCI
   Current Usage: Available
   Length: Short
   ID: 6
   Characteristics:
      3.3 V is provided
      Opening is shared
      PME signal is supported

On Board Device Information
   Type: Ethernet
   Status: Enabled
   Description:  Intel GbE NIC

On Board Device Information
   Type: Sound
   Status: Enabled
   Description:  HDA Device

On Board Device Information
   Type: Video
   Status: Disabled
   Description:  Intel G43 Video

OEM Strings
   String 1: To Be Filled By O.E.M.

System Configuration Options
   Option 1: To Be Filled By O.E.M.

BIOS Language Information
   Installable Languages: 1
      en|US|iso8859-1
   Currently Installed Language: en|US|iso8859-1

Physical Memory Array
   Location: System Board Or Motherboard
   Use: System Memory
   Error Correction Type: None
   Maximum Capacity: 4 GB
   Number Of Devices: 2

Memory Array Mapped Address
   Starting Address: 0x00000000000
   Ending Address: 0x0003FFFFFFF
   Range Size: 1 GB
   Partition Width: 0

Memory Device
   Total Width: 64 bits
   Data Width: 64 bits
   Size: 512 MB
   Form Factor: DIMM
   Set: None
   Locator: CHANNEL_A
   Bank Locator: CHANNEL A_DIMM0
   Type: DDR2
   Type Detail: Synchronous
   Speed: 667 MHz (1.5 ns)
   Manufacturer: Manufacturer0
   Serial Number: SerNum0
   Asset Tag: AssetTagNum0
   Part Number: PartNum0

Memory Device Mapped Address
   Starting Address: 0x00000000000
   Ending Address: 0x0001FFFFFFF
   Range Size: 512 MB
   Partition Row Position: 1

Memory Device
   Total Width: 64 bits
   Data Width: 64 bits
   Size: 512 MB
   Form Factor: DIMM
   Set: None
   Locator: CHANNEL_B
   Bank Locator: CHANNEL B_DIMM0
   Type: DDR2
   Type Detail: Synchronous
   Speed: 667 MHz (1.5 ns)
   Manufacturer: Manufacturer2
   Serial Number: SerNum2
   Asset Tag: AssetTagNum2
   Part Number: PartNum2

Memory Device Mapped Address
   Starting Address: 0x00020000000
   Ending Address: 0x0003FFFFFFF
   Range Size: 512 MB
   Partition Row Position: 1

System Boot Information
   Status: No errors detected


Top
 Profile  
 
 Post subject:
PostPosted: Mon Feb 08, 2010 6:05 pm 
Offline
Joined: Wed Dec 10, 2003 8:31 pm
Posts: 1996
Location: /dev/null
You might wanna post a flyspray task requesting an update to the sensors package.

_________________
Retired KM user (R4 - R6.04); friend to LH users.


Top
 Profile  
 

Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 40 posts ] 
Go to page 1, 2, 3  Next



All times are UTC - 6 hours




Who is online

Users browsing this forum: No registered users and 2 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Jump to:  
cron
Powered by phpBB® Forum Software © phpBB Group

Theme Created By ceyhansuyu