Hello All,
I am new to this forum and to ClearOS, so please bear with me.
I have just completed a new HW build on which I have installed ClearOS.
I saw from other thread posted by Leon that his Reports- System- Hardware Report show the temperature (Temp1, Temp2, Temp3, etc.) assuming here at least one value is teh CPU temp.
When I run same report I unfortunately don't get any temperature readings (see attached) wonder why? And if someone here can help me to figure out what I can do!
Much appreciated!
Steen
PS: My build is the following:
MBO Mini-ITX = Jetway NF96FL-510-LF (Intel Atom, Dual Core, 1.66GHz, L2 1MB)
Chipset = NM10
RAM = Kingston 2GB (2x1GB Modules) 800MHz PC2-6400 DDR2
HD = Intel X25M SSD 40GB
Ethernet LAN = RTL8111DL Gigabit
Daughter Board = Jetway AD3RTLANG-LF (3 x 1 Gigabit)
Power Brick = 80w (12v/6.6A)
Case = M350 Universal Mini-ITX enclosure
Fan = SilenX Ixtrema Pro - Fan unit - 40 mm
I am new to this forum and to ClearOS, so please bear with me.
I have just completed a new HW build on which I have installed ClearOS.
I saw from other thread posted by Leon that his Reports- System- Hardware Report show the temperature (Temp1, Temp2, Temp3, etc.) assuming here at least one value is teh CPU temp.
When I run same report I unfortunately don't get any temperature readings (see attached) wonder why? And if someone here can help me to figure out what I can do!
Much appreciated!
Steen
PS: My build is the following:
MBO Mini-ITX = Jetway NF96FL-510-LF (Intel Atom, Dual Core, 1.66GHz, L2 1MB)
Chipset = NM10
RAM = Kingston 2GB (2x1GB Modules) 800MHz PC2-6400 DDR2
HD = Intel X25M SSD 40GB
Ethernet LAN = RTL8111DL Gigabit
Daughter Board = Jetway AD3RTLANG-LF (3 x 1 Gigabit)
Power Brick = 80w (12v/6.6A)
Case = M350 Universal Mini-ITX enclosure
Fan = SilenX Ixtrema Pro - Fan unit - 40 mm
In Hardware
Share this post:
Responses (23)
-
Accepted Answer
Thanks for that Tony. Grep "i2c" gives me nothing.
insmod /lib/modules/2.6.18-128.2.16.v5/kernel/drivers/hwmon/it87.ko gives me the same results and dmesg I posted. I know that I have the module i2c-i801 and this is what I get for modifo on that:
[root@Learn2Automate ~]# modinfo i2c-i801
filename: /lib/modules/2.6.18-194.8.1.v5/kernel/drivers/i2c/busses/i2c-i801.ko
license: GPL
description: I801 SMBus driver
author: Frodo Looijaard <frodol@dds.nl>, Philip Edelbrock <phil@netroedge.com>, and Mark D. Studebaker <mdsxyz123@yahoo.com>
srcversion: 1FF54D98A1DB8804FB22D3B
alias: pci:v00008086d00003B30sv*sd*bc*sc*i*
alias: pci:v00008086d00003A60sv*sd*bc*sc*i*
alias: pci:v00008086d00003A30sv*sd*bc*sc*i*
alias: pci:v00008086d00005032sv*sd*bc*sc*i*
alias: pci:v00008086d00002930sv*sd*bc*sc*i*
alias: pci:v00008086d0000283Esv*sd*bc*sc*i*
alias: pci:v00008086d0000269Bsv*sd*bc*sc*i*
alias: pci:v00008086d000027DAsv*sd*bc*sc*i*
alias: pci:v00008086d0000266Asv*sd*bc*sc*i*
alias: pci:v00008086d000025A4sv*sd*bc*sc*i*
alias: pci:v00008086d000024D3sv*sd*bc*sc*i*
alias: pci:v00008086d000024C3sv*sd*bc*sc*i*
alias: pci:v00008086d00002483sv*sd*bc*sc*i*
alias: pci:v00008086d00002443sv*sd*bc*sc*i*
alias: pci:v00008086d00002423sv*sd*bc*sc*i*
alias: pci:v00008086d00002413sv*sd*bc*sc*i*
depends: i2c-core
vermagic: 2.6.18-194.8.1.v5 SMP mod_unload 686 REGPARM 4KSTACKS gcc-4.1
I believe the kernel I'm running shows in the folder above, i.e. 2.6.18. Chipset for the sensor is ITE8702. I'll have to open my box to see what the mother board is; hardware report doesn't show that anywhere. Do you know if it shows up in the /dev directory anywhere?
I did give myself a scare yesterday playing around with modprobe so much (I'm persistent if nothing else). I decided to reboot after upgrading lm_sensors from the elrepo repo as a last ditch effort (after all the modprobe stuff. Well, both nics and my scsi devices were not loading and I lost all network capabilities as a result. I played with it a while and ultimately had to modprobe my nic card and scsi drivers (based on the aliases for them in modprobe.conf) and then depmod -a them. When I rebooted their drivers loaded up and I was up and running again. -
Accepted Answer
Strange... those symbols are sure in my system... but then again I have full kernel source and headers...
maybe that's the difference..
[root@danda src]# grep -R "i2c_isa_del_driver" *
kernels/2.6.18-194.8.1.v5-i686/kabi_whitelist: i2c_isa_del_driver
kernels/2.6.18-194.8.1.v5-i686/include/linux/i2c-isa.h:extern int i2c_isa_del_driver(struct i2c_driver *driver);
kernels/2.6.18-194.8.1.v5-i686/Module.symvers:0xf058911b i2c_isa_del_driver drivers/i2c/busses/i2c-isa EXPORT_SYMBOL
linux-2.6.18-194.8.1.v5/include/linux/i2c-isa.h:extern int i2c_isa_del_driver(struct i2c_driver *driver);
linux-2.6.18-194.8.1.v5/drivers/i2c/busses/i2c-isa.c:int i2c_isa_del_driver(struct i2c_driver *driver)
linux-2.6.18-194.8.1.v5/drivers/i2c/busses/i2c-isa.c:EXPORT_SYMBOL(i2c_isa_del_driver);
[root@danda src]# grep -R "i2c_isa_add_driver" *
kernels/2.6.18-194.8.1.v5-i686/kabi_whitelist: i2c_isa_add_driver
kernels/2.6.18-194.8.1.v5-i686/include/linux/i2c-isa.h:extern int i2c_isa_add_driver(struct i2c_driver *driver);
kernels/2.6.18-194.8.1.v5-i686/Module.symvers:0x2b3f38f2 i2c_isa_add_driver drivers/i2c/busses/i2c-isa EXPORT_SYMBOL
linux-2.6.18-194.8.1.v5/include/linux/i2c-isa.h:extern int i2c_isa_add_driver(struct i2c_driver *driver);
linux-2.6.18-194.8.1.v5/drivers/i2c/busses/i2c-isa.c:int i2c_isa_add_driver(struct i2c_driver *driver)
linux-2.6.18-194.8.1.v5/drivers/i2c/busses/i2c-isa.c:EXPORT_SYMBOL(i2c_isa_add_driver);
[root@danda src]#
Couple of little things...
using insmod with a path you can pick a specific driver that you are trying to load
depmod -a comes after the driver(s) is loaded
Which kernel are you actually running?
What is the exact manufacturer and model of your motherboard?
What is the Chipset ID of your 'sensors' chip? -
Accepted Answer
I tried that before my post, but I did it again anyway without getting any error prompt back, then modprobe it87 again and this is that cheap-version error I got:
[root@Learn2Automate hwmon]# depmod -a
[root@Learn2Automate hwmon]# modprobe it87
FATAL: Error inserting it87 (/lib/modules/2.6.18-194.8.1.v5/weak-updates/it87/it87.ko): No such device
How can there be no such device when I know the driver's in the hwmon directory and sensors-detect always detects the sensor, but doesn't write a driver into the lm_sensors config file?
Edit: OK, it wasn't a cheap-version directory, it was a weak-updates directory. There were some symbolic links in this guy that pointed to it87.ko and coretemp.ko drivers in this guy /lib/modules/2.6.18-194.el5/extra. I got rid of the symbolic link and copied the actual driver from /lib/modules/2.6.18-128.2.16.v5/kernel/drivers/hwmon into it and now when I modprobe it87 I get
[root@Learn2Automate ~]# modprobe it87
FATAL: Error inserting it87 (/lib/modules/2.6.18-194.8.1.v5/weak-updates/it87/it87.ko): Unknown symbol in module, or unknown parameter (see dmesg)
Look in my message log and I see
Feb 7 16:17:07 Learn2Automate kernel: it87: Unknown symbol i2c_isa_add_driver
Feb 7 16:17:07 Learn2Automate kernel: it87: Unknown symbol i2c_isa_del_driver
I'm too green at all this. Why is modprobe even looking in a weak-updates folder for it87.ko rather than the current kernel folder where the latest driver is, i.e. /lib/modules/2.6.18-128.2.16.v5/kernel/drivers/hwmon? -
Accepted Answer
-
Accepted Answer
OK...this is ridiculous. I updated lm_sensors and kmod-it87 and kmod-coretemp successfully and when I go to modprobe it87 and coretemp it tells me the modules aren't found! They're in the stinking hardware directory of the kernel drivers. The coretemp only shows up in kernel version 194.8.1.v5 while the it87 driver shows up in that and 128.2.16.v5. I know that modprobe will go through one version at a time, starting with the latest one, so it should pick the stinkin driver up. I know at one time my shell prompt spit back that the driver was in a cheap-version folder or something like that, after doing a modprobe, but it's not doing that now. -
Accepted Answer
Steen
Trying family 'VIA/Winbond/Nuvoton/Fintek' Yes
Found 'Fintek F71869FG Super IO Sensors' Success!
(address 0x290, driver 'to-be-written')
I have just installed an MSI motherboard for an AMD CPU that has a Fintek F71889FG chip, so I have had to look into this. It seems that the F71869, F71889 and F71882fg are all part of the same family and can use the f71882fg.ko driver...
First I upgraded lm_sensors to the elrepo version - see above in my append to Dirk
Then found source for f71882fg from here - http://lists.lm-sensors.org/pipermail/lm-sensors/2007-July/020270.html
There are probably later versions, I need to research... anyway downloaded the c source (in the attachment) - changed the Manufacturers Chipset Id to match mine, recreated a small Makefile and compiled..
Well - surprise - compiled with no errors and loaded OK...
Found addition for the /etc/sensors.conf here
http://www.mentby.com/michael-gerst/fintek-f71869-driver-found-a-working-configuration.html
This link also provides a patch for your f71869 chip...
It's working... EDIT removed url as this machine no longer runs ClearOS
sensors.conf file is a bit rough, but doing the scaling with mrtg I'm getting what I want...
Something similar would probably work for your Atom board... -
Accepted Answer
Dirk, have you tried upgrading to the versions in elrepo?
Getting started http://elrepo.org/tiki/tiki-index.php
lm-sensors - http://elrepo.org/tiki/lm_sensors
it78 - http://elrepo.org/tiki/kmod-it87
coretemp - http://elrepo.org/tiki/kmod-coretemp
I am now reading temps, fans and voltages on my newly installed D510 based Atom board with ITE it8718 chip.
The repository shouldn't be enabled by default (check!) - so to install use this format after following the 'Getting started" above...
yum --enablerepo=elrepo install lm_sensors -
Accepted Answer
I have the same problem with not having any temps show up in the hardware report. Anybody got a copy of their lm_sensors config file they can post? When I do sensors-detect this is my output:
# sensors-detect revision 5291 (2008-06-23 23:40:46 -0700)
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): y
Probing for PCI bus adapters...
Use driver `i2c-i801' for device 0000:00:1f.3: Intel 82801DB ICH4
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: SMBus I801 adapter at 5000 (i2c-0)
Do you want to scan it? (YES/no/selectively): y
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 0x51
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
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): y
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
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): y
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Fintek'... No
Trying family `ITE'... Yes
Found `ITE IT8702F Super IO Sensors' Success!
(address 0x290, driver `to-be-written')
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): y
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... No
Intel AMB FB-DIMM thermal sensor... No
Now follows a summary of the probes I have just done.
Just press ENTER to continue:
Driver `to-be-written' (should be inserted):
Detects correctly:
* ISA bus, address 0x290
Chip `ITE IT8702F Super IO Sensors' (confidence: 9)
Do you want to overwrite /etc/sysconfig/lm_sensors? (YES/no):
It detects the IT8720 sensor, but it doesn't write a module driver to the config file, saying it's 'to be written', but the lm_sensors site says it a legit driver (albeit for a later kernel than the latest one Clear uses. According to this site the module coretemp needs to be loaded. Both the ITE driver and coretemp are showing up in my src kernel directory. If I try to modprobe coretemp this is the output I get:
FATAL: Error inserting coretemp (/lib/modules/2.6.18-194.8.1.v5/kernel/drivers/hwmon/coretemp.ko): No such device
-
Accepted Answer
I am trying to find the sensor chip on the board, so far no success - I'll keep looking.
However, before I started to use clearos I tried endian, ipfire and smooth wall with same hardware in all three I could get at least the CPU temp via LM78 and coretemp, so how come its not possible under clearos?
I can live without knowing the fan speed RPMs, etc, just the CPU core temp is what I would like to have/see...
BR// Steen -
Accepted Answer
-
Accepted Answer
-
Accepted Answer
-
Accepted Answer
Physically check your board - I suspect you have the Fintek rather than a LM78 chip - but there is no way I can tell... you need to look.
As far as I know phpsysinfo uses the 'sensors' command to get the CPU temperature, and this information comes from the i2c chip module - not coretemp.
An example...
[root@atomii ~]# sensors
smsc47m192-i2c-0-2d
Adapter: SMBus I801 adapter at 3000
+2.5V: +2.55 V (min = +0.00 V, max = +3.32 V)
VCore: +1.16 V (min = +0.00 V, max = +2.99 V)
+3.3V: +3.28 V (min = +0.00 V, max = +4.38 V)
+5V: +4.95 V (min = +0.00 V, max = +6.64 V)
+12V: +12.38 V (min = +0.00 V, max = +15.94 V)
VCC: +3.28 V (min = +0.00 V, max = +4.38 V)
+1.5V: +1.58 V (min = +0.00 V, max = +1.99 V)
+1.8V: +1.77 V (min = +0.00 V, max = +2.39 V)
Chip Temp: +41.0°C (low = -127°C, high = +127°C)
CPU Temp: +61.0°C (low = +40°C, high = +70°C)
Sys Temp: +48.0°C (low = -127°C, high = +127°C)
vid: +2.050 V (VRM Version 8.2)
smsc47m1-isa-0680
Adapter: ISA adapter
fan1: 2065 RPM (min = 1280 RPM, div = 4)
fan2: 8474 RPM (min = 1280 RPM, div = 4)
[root@atomii ~]#
You will see this output layout matches the phpsysinfo content on my Web-Site..
Also with regards to coretemp - there was a patch needed for this to load with the original Intel Atoms and a further patch for the NM10 based ones... I have no idea whether these patches are incorporated into the ClearOS version, check the source code... time for you to do some research. -
Accepted Answer
hmm, but:
sensors-detects the Intel Atom thermal sensor as success and say the driver to be used/or used is 'coretemp" so is it not 'coretemp' I have to use? Or the LM78?
When I do modprobe coretemp I get a Fatal error.
Error inserting coretemp (/lib/modules/2.6.18-194.8.1.v5/kernel/drivers/hwmon/coretemp.ko): No such device
When I do modprobe lm_sensors I get a Fatal error.
Module lm_sensors not found.
Perhaps there is different versions of coretemp, LM78, lm_sensors depending on kernel version? -
Accepted Answer
If you really have the Fintek F71869FG chip, then maybe you should contact the lm-sensors team. (Check the chips on your motherboard) The comment against the F71869FG is "Waiting for someone with such hardware. Datasheet available."
In the meantime, I guess you are out of luck until a driver is written... -
Accepted Answer
hmmmm, I don't get a specific chip shown, what I get is:
Code:
Some south bridges, CPUs or memory controllers contain embedded sensors.
Do you want to scan for them?
...
Intel Core family thermal sensor... No
Intel Atom thermal sensor... Sucess!
(driver 'coretemp')
___
Some Super I/O chips contains embedded sensors...
Do you want to scan for Super I/O sensors?
...
Trying family 'VIA/Winbond/Nuvoton/Fintek' Yes
Found 'Fintek F71869FG Super IO Sensors' Success!
(address 0x290, driver 'to-be-written')
___
Some hardware monitoring chips are accessible through the ISA I/O ports.
Do you want to scan the ISA I/O ports?
Probing for 'National Semiconductor LM78' at 0x290... Success!
(confidence 6, driver 'lm78')
___
Lastly, we can probe the I2C/SMBus adapters for connected HW...
Do you want to probe the I2C/SMBus adapters now?
Using Driver 'i2c-i801' for device 0000:00:1f.3: Intel 82801H ICH8 Module i2c-dev loaded successfully.
___
This the output... -
Accepted Answer
Check to see if the i2c chip on your motherboard is supported (list on the Web-Site I provided - see Device Support Status). On my Atom board (made by Intel) it is smsc47m1/smsc47m192.
When you did the 'sensors-detect' - what chips, if any, were found?
Here is the relevant sections from mine...
....
Probing for `Texas Instruments THMC50'... No
Probing for `VIA VT1211 (I2C)'... No
Probing for `ITE IT8712F'... No
Probing for `ALi M5879'... No
Probing for `SMSC LPC47M15x/192/292/997'... Success!
(confidence 6, driver `smsc47m192')
Probing for `SMSC DME1737'... No
Probing for `SMSC SCH5027D-NW'... No
Probing for `Fintek F75373S/SG'... No
...
...
Trying family `National Semiconductor'... No
Trying family `SMSC'... Yes
Found `SMSC LPC47M15x/192/997 Super IO Fan Sensors' Success!
(address 0x680, driver `smsc47m1')
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor'... No
...
-
Accepted Answer
Tony,
Did the yum install lm_sensors
Did the sensor-detect
At end of the script I got this message:
Do you want to overwrite /etc/sysconfig/lm_sensors? (YES/no):
Starting lm_sensors: No sensors found!
Make sure you loaded all the kernel drivers you need.
Try sensors-detect to find out which these are. [FAILED]
For the "driver" found it is stated: Driver "coretemp" * Chip 'Intel Atom thermal sensor' (confidence: 9)
Then I did:
modprobe lm_sensors got the message Module lm_sensors not found
Then I found this article:
http://www.question-defense.com/2010/03/24/lm_sensors-on-cent-os-5-4-how-to-get-and-install-the-coretemp-module
Tried to follow the steps, but at end when I did:
modprobe coretemp got the message Error inserting Coretemp No such device
I see from your webpage that the Atom CPU you got is an Intel(R) Atom(TM) CPU 330 @ 1.60GHz while mine is an Intel(R) Atom(TM) CPU K510 @ 1.66GHz, but I guess that should not be an issue?
Suggestions? -
Accepted Answer
phpsysinfo is already installed on your system - it's what ClearOS Webconfig uses to display the hardware information page, and the program that created the display in your attachment.
However, to get cpu temperatures, fan speeds, voltages etc - you need to install and set up lm_sensors ( yum install lm_sensors) which phpsysinfo will then use to access and display the temps, voltages etc..
see http://www.lm-sensors.nu/ for more... -
Accepted Answer
-
Accepted Answer
Search these and the old Clark connect Forums for lm_sensors...
Also search for "hddtemp" if you want disk drive temps...
There is also a little doc on my site - url below...
phpsysinfo for an Atom system here... http://danda.poweredbyclear.com/frame-99-sysinfo.html
Please login to post a reply
You will need to be logged in to be able to post a reply. Login using the form on the right or register an account if you are new here.
Register Here »