Wow, a lot, will take me some time to read up, but thanks!

OK - here's a brief summary... much is from locally written scripts...

The graphing is done by mrtg - http://oss.oetiker.ch/mrtg/
M/B Voltages, Temps etc lm_sensors + local scripts - http://www.lm-sensors.org/
Cable & ADSL Stats - locally written scripts
System performance - local scripts data from sysstat - http://sebastien.godard.pagesperso-orange.fr/
HDD temps using hddtemp / local script - http://savannah.nongnu.org/projects/hddtemp/
System Information - phpsysinfo / local script - https://github.com/phpsysinfo/phpsysinfo
vnstat - writeup here - http://www.sraellis.tk/master.php?topic=vnstat_installv7
misc locally written scripts for ntp. mail, used disk space etc

specific details relating to scripts for an individual item available by request...

Tony Ellis wrote:

Brian - not sure how to answer, exactly what is it you are interested in?
...
The sum total of all the reports as per left-hand frame menu?

What I perceive is that you are using dynamic dns, the web server, and something to keep the sum total of all updated. I recognize the graphs from ClearOS 5.2, but you have more, core temps etc.

If you can give me the key words or a few suggested links to try to do something similar, that would be great.

Well my hardware is an HP N40L so thats really my problem. I have had to compile a jc24.ko module for the kernel. Install it and make sure that was loaded. Ran sensors-detect and now its detected and ends up as an entry in my lm_sensors.conf file. So yipee but still not seeing anything other than the processor temp when I run sensors.

So I am pretty sure I have it configured ok but I have seen loads of posts on the internet where people have been having the same problem getting lm_sensors to display sensors on this hardware regardless of distro. So I am giving up

Have you run "sensors-detect"? If not, you will need to.

Whats in /etc/sysconfig/lm_sensors ?

Nothing in mine which probably why mine doesnt work :P

Brian - not sure how to answer, exactly what is it you are interested in?

The right hand frame entitled "System Information: alice.sraellis.com (127.0.0.1)"...
The display of voltages, temperatures and fan speed... or
The sum total of all the reports as per left-hand frame menu?

Tony Ellis wrote:

No problem with an Atom board - problem appears to be with ........

Voltages, Temps and Fan Speed here... http://danda.poweredbyclear.com/frame-14-sysinfo.html

Tony, is there a website I can follow to do what you have done here on "danda...frame-14...html"?

I'm two hours away from my clearosbox and would be able to check the server on my smartphone if I had this setup!

Brian.

Good Luck - only other suggestion I can make at this time is to compile and try the standalone driver...

Hi Tony ,

My lm_sensors configuration file is in fact /etc/sensors3.conf .. not sure why, but i've seem some references to it in the lmsensors page.
The ls -lad `updatedb && locate w83627ehf.ko` didn't made any diference. I'll try to investigate more, in the mean time I guess I'll have to stick to what I have so far. Anyway, thanks a lot for your help!

Carlos

Hmm - the configuration file has always been /etc/sensors.conf in my experience, not /etc/sensors3.conf or was that a typo...

However, without the driver loading that is immaterial...

Are you sure modprobe found the driver you compiled? This should find them all and their dates...

ls -lad `updatedb && locate w83627ehf.ko`

Note the ` is a back tick - often to the left of the 1 key

You also seem to be running a very old kernel. There have been several updates since 2.6.32-220.13.1.v6.x86_64 and the latest I believe is 2.6.32-279.5.2.v6.x86_64... not that I think that is your problem.

I only see hwmon in lsmod

[root@sys etc]# lsmod

Module                  Size  Used by

ipt_REDIRECT            1840  3 

xt_NFQUEUE              2186  1 

xt_mark                 1057  1 

bluetooth              99548  0 

rfkill                 19735  1 bluetooth

nfnetlink_queue         7919  1 

nf_conntrack_netlink    17264  0 

nfnetlink               4152  4 nfnetlink_queue,nf_conntrack_netlink

hwmon_vid               3132  0 

coretemp                7619  0 

xt_state                1492  6 

nf_nat_h323             8830  0 

nf_conntrack_h323      67696  1 nf_nat_h323

nf_nat_pptp             4653  0 

nf_nat_proto_gre        3028  1 nf_nat_pptp

nf_nat_irc              1883  0 

nf_nat_ftp              3507  0 

ipt_MASQUERADE          2466  1 

xt_IMQ                  1350  0 

imq                     4615  0 

nf_conntrack_pptp      12166  1 nf_nat_pptp

nf_conntrack_proto_gre     7195  1 nf_conntrack_pptp

arc4                    1475  0 

ecb                     2209  0 

ppp_mppe                6404  0 

ppp_generic            25443  1 ppp_mppe

slhc                    5901  1 ppp_generic

nf_conntrack_irc        5530  1 nf_nat_irc

nf_conntrack_ftp       12913  1 nf_nat_ftp

ipt_REJECT              2383  1 

ipt_LOG                 5845  0 

iptable_nat             6190  1 

nf_nat                 22726  8 ipt_REDIRECT,nf_nat_h323,nf_nat_pptp,nf_nat_proto_gre,nf_nat_irc,nf_nat_ftp,ipt_MASQUERADE,iptable_nat

nf_conntrack_ipv4       9506  9 iptable_nat,nf_nat

nf_conntrack           79485  15 nf_conntrack_netlink,xt_state,nf_nat_h323,nf_conntrack_h323,nf_nat_pptp,nf_nat_irc,nf_nat_ftp,ipt_MASQUERADE,nf_conntrack_pptp,nf_conntrack_proto_gre,nf_conntrack_irc,nf_conntrack_ftp,iptable_nat,nf_nat,nf_conntrack_ipv4

nf_defrag_ipv4          1483  1 nf_conntrack_ipv4

iptable_mangle          3349  1 

iptable_filter          2793  1 

ip_tables              17831  3 iptable_nat,iptable_mangle,iptable_filter

ipv6                  322349  76 

ppdev                   8729  0 

parport_pc             22978  0 

parport                37265  2 ppdev,parport_pc

8139too                30892  0 

8139cp                 22297  0 

mii                     5271  2 8139too,8139cp

i2c_i801               11231  0 

i2c_core               31276  1 i2c_i801

sg                     30124  0 

e1000e                219532  0 

snd_hda_codec_realtek   309541  1 

snd_hda_intel          25548  0 

snd_hda_codec          91845  2 snd_hda_codec_realtek,snd_hda_intel

snd_hwdep               6780  1 snd_hda_codec

snd_seq                56591  0 

snd_seq_device          6596  1 snd_seq

snd_pcm                84702  2 snd_hda_intel,snd_hda_codec

snd_timer              23057  2 snd_seq,snd_pcm

snd                    70023  8 snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_seq,snd_seq_device,snd_pcm,snd_timer

soundcore               8086  1 snd

snd_page_alloc          8630  2 snd_hda_intel,snd_pcm

ext4                  364410  3 

mbcache                 8144  1 ext4

jbd2                   88834  1 ext4

sd_mod                 39520  3 

crc_t10dif              1541  1 sd_mod

ahci                   40455  2 

video                  21032  0 

output                  2505  1 video

dm_mirror              14101  0 

dm_region_hash         12170  1 dm_mirror

dm_log                 10122  2 dm_mirror,dm_region_hash

dm_mod                 81692  11 dm_mirror,dm_log

[root@sys etc]# 

I have the following in /etc/sensors3.conf

(...)

chip "w83627ehf-*" "w83627dhg-*"



    label in0 "Vcore"

    label in2 "AVCC"

    label in3 "VCC"

    label in7 "3VSB"

    label in8 "Vbat"



    set in2_min  3.3 * 0.90

    set in2_max  3.3 * 1.10

    set in3_min  3.3 * 0.90

    set in3_max  3.3 * 1.10

    set in7_min  3.3 * 0.90

    set in7_max  3.3 * 1.10

    set in8_min  3.0 * 0.90

    set in8_max  3.0 * 1.10



(...)

I tried to see if the module exists, and it does
[root@sys etc]# modprobe -l |grep w83627
kernel/drivers/hwmon/w83627hf.ko
kernel/drivers/hwmon/w83627ehf.ko
kernel/drivers/watchdog/w83627hf_wdt.ko

and then tried to load it but with no success...
[root@sys hwmon]# modprobe w83627ehf
FATAL: Error inserting w83627ehf (/lib/modules/2.6.32-220.13.1.v6.x86_64/kernel/drivers/hwmon/w83627ehf.ko): No such device


not sure why I can't load it :S

Carlos...

Is the driver actually loaded?

# lsmod | grep w83627ehf

Is hwmon loaded?

# lsmod | grep hwmon

Do you have a section in /etc/sensors.conf configured for the W83627UHG?

Hi Tony, after my previous post I kept digging to make this work and eventually I got this to work! Well... kinda... :dry:

here is what i did:

I add another repo (not sure it is needed/helpful)
# rpm -Uvh http://apt.sw.be/redhat/el6/en/x86_64/rpmforge/RPMS/rpmforge-release-0.5.2-2.el6.rf.x86_64.rpm

(then install the dependencies needed for lm_sensors)
# yum install gcc
# yum install bison
# yum install flex

go to lm_sensors page and got this file http://dl.lm-sensors.org/lm-sensors/releases/lm_sensors-3.3.2.tar.bz2

(extract the file)
# tar jxf lm_sensors-3.3.2.tar.bz2

(compile it)
# make
# make install

(check the installed version)
# sensors --version
sensors version 3.3.2 with libsensors version 3.3.2

(run detection)
# sensors-detect

(...)

Now follows a summary of the probes I have just done.

Just press ENTER to continue: 



Driver `w83627ehf':

  * ISA bus, address 0x290

    Chip `Winbond W83627UHG/NCT6627UD Super IO Sensors' (confidence: 9)



Driver `coretemp':

  * Chip `Intel digital thermal sensor' (confidence: 9)



Do you want to overwrite /etc/sysconfig/lm_sensors? (YES/no): y

Starting lm_sensors: loading module coretemp w83627ehf     [  OK  ]

Unloading i2c-dev... OK



[root@sys lm_sensors-3.3.2]# sensors

coretemp-isa-0000

Adapter: ISA adapter

Core 0:       +45.0°C  (high = +80.0°C, crit = +100.0°C)

Core 1:       +44.0°C  (high = +80.0°C, crit = +100.0°C)

Unfortunately I only get CPU temperatures. I don't get any voltages nor fan RPMs.
Where did I go wrong? Am I missing something?

Carlos - you might be able to get support for your chip this way...
If you look at this page http://lm-sensors.org/wiki/Devices you will see two options for W83627UHG

1) install lm_sensors version 3.2 2
2) use standalone driver

The standalone driver wording (in red for me) is a link to the source at http://khali.linux-fr.org/devel/misc/w83627ehf/ if you clink on it

Downloaded the source and it compiled with no problems using ClearOS 6.2 64-bit version. W83627UHG support has been added to the w83627ehf driver... (I can test on a 6.3 32-bit machine if necessary)

Then tried to load it - and got "error inserting './w83627ehf.ko': -1 No such device" so it obviously driver tried to load - but could not find the device for the simple reason that machine doesn't have that chip on the motherboard :-)

So install the development tools (see elsewhere in these forums), compile and install the driver and you should be good to go with the driver...

Then just find any lm_sensors version 3.2 rpm and extract just the sensors.conf.default and use that for the /etc/sensors.conf so you have the configuration options for the W83627UHG chip.
See http://www.cyberciti.biz/tips/how-to-extract-an-rpm-package-without-installing-it.html or google how to do that...

Detection of the W83627UHG was added to lm_sensors version 3.1.1 so the above would probably just work...

Hi,

I have an Intel D2500CC Atom board which uses the Winbond W83627UHG chip. The lm_sensors version that is available in ClearOS repositories is 3.1.1 but the Winbond W83627UHG chip is only supported in version 3.2 according to lm-sensors website

Any suggestion on how can I overcome this ? Maybe add some other repository? :unsure:
Please help! Thanks in advance.

Yes investigating on the lines of OpenIPMI and ipmitool only.

No problem with an Atom board - problem appears to be with driver for the chip on your board not available... supposed to have been there since kernel 2.6.24 - but must have been left out somewhere...
Maybe you should investigate OpenIPMI and ipmitool...

My firewall

[root@alice ~]# sensors

atk0110-acpi-0

Adapter: ACPI interface

Vcore Voltage:     +1.07 V  (min =  +0.85 V, max =  +1.60 V)

 +3.3 Voltage:     +3.23 V  (min =  +2.97 V, max =  +3.63 V)

 +5 Voltage:       +4.76 V  (min =  +4.50 V, max =  +5.50 V)

 +12 Voltage:     +12.16 V  (min = +10.20 V, max = +13.80 V)

CPU FAN Speed:       0 RPM  (min =  600 RPM)

CHASSIS FAN Speed:2265 RPM  (min =  600 RPM)

CPU Temperature:   +29.0°C  (high = +60.0°C, crit = +95.0°C)  

MB Temperature:    +28.0°C  (high = +45.0°C, crit = +75.0°C)  



coretemp-isa-0000

Adapter: ISA adapter

Core 0:      +24.0°C  (high = +80.0°C, crit = +100.0°C)  

Core 1:      +25.0°C  (high = +80.0°C, crit = +100.0°C)  



[root@alice ~]# cat /etc/*release*

ClearOS Community release 6.3.0 (Final)

ClearOS Community release 6.3.0 (Final)

ClearOS Community release 6.3.0 (Final)

cpe:/o:redhat:enterprise_linux:6:ga:community

[root@alice ~]# 

Voltages, Temps and Fan Speed here... http://danda.poweredbyclear.com/frame-14-sysinfo.html

Tried the same but am running into issues due to missing ipmisensors. Read around and found that building a custom kernel is the only way to get the same working. Has anyone had success out of the box?

Issue currently encountered when running sensors-detect :

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

Driver `ipmisensors':
* ISA bus, address 0xca8
Chip `IPMI BMC KCS' (confidence: 8)

Warning: the required module ipmisensors is not currently installed
on your system. If it is built into the kernel then it's OK.
Otherwise, check http://www.lm-sensors.org/wiki/Devices for
driver availability.

No modules to load, skipping modules configuration.

Unloading i2c-dev... OK

System reporting is in development, no idea if it will include lm_sensors output

You can install and configure manually...'yum install lm_sensors'