Printable View
Hi,
Regarding "smbus-arp" I think it is a bug or a bad explanation form "lm-sensors".
Unless I made a mistake, it is loaded under "i2c-core", i.e. execute "sudo modprobe i2c-core" to get it loaded.
I did so and then the message regarding smbus-arp did not figure anymore and additional data were available.
(If I am wrong pease post)
Juantxorena,
Check my later on the thread - I guess it is a part of "i2c-core".
A seemingly simple question: What does "SBr Temp" mean? I couldn't find anything about it on the lm-sensors home page...
A few questions..
This is wokring for me.
exmachina@ExMachina:~$ sensors
No sensors found!
exmachina@ExMachina:~$ sudo sensors
Password:
No sensors found!
exmachina@ExMachina:~$
is there a gui for this?
my laptop temp is usally 130 but can get up to 155.. kinda worries me
I have managed to install lm-sensors on my laptop (running kubuntu dapper). After I have followed the steps described in this how-to and rebooted my system, the cpu utilization increased to almost 100%. Most of the cpu time is consumed by kacpid. I didn't have this problem before.
Now I have uninstalled the whole lm-sensors package (using synaptic) but one of the how-to steps must have left a permanent modification, which causes kacpid to use 100% cpu time.
Even the whole boot process is slow now, it take 5-10 times longer. I had to disable acpi (kernel parameter: acpi=off) in order to be able to boot faster.
Can anyone imagine, which step has to be undone to avoid this freaky behaviour of kacpid.
I had the same problem. And the strange thing is, it also happens when I boot to Windows. I tried resetting to the default BIOS settings and that seemed to fix the issue.
For everyone using lm-sensors on Gnome, install the sensors-applet package.
It will place the sensors info on your Gnome panel and allow you to configure alarm levels and so on.
Screenshot of sensors-applet here on my pc
Very handy :)
Quote:
Originally Posted by LKRaider
embarrassing... how do I start them????
Found it! http://www.ubuntuforums.org/archive/...p/t-92504.html
I have intel 845GVSR board and i have recently installed Ubuntu 6.06LTS
I tried to configure lm-sensors as explained above. I tried the following
rivo@Xcc:~$ sudo sensors-detect
Password:
No i2c device files found. Use prog/mkdev/mkdev.sh to create them.
rivo@Xcc:~$ cd Desktop/
rivo@Xcc:~/Desktop$ chmod 755 mkdev.sh
rivo@Xcc:~/Desktop$ sudo ./mkdev.sh
/dev/i2c-0
/dev/i2c-1
/dev/i2c-2
/dev/i2c-3
/dev/i2c-4
/dev/i2c-5
/dev/i2c-6
/dev/i2c-7
/dev/i2c-8
/dev/i2c-9
/dev/i2c-10
/dev/i2c-11
/dev/i2c-12
/dev/i2c-13
/dev/i2c-14
/dev/i2c-15
/dev/i2c-16
/dev/i2c-17
/dev/i2c-18
/dev/i2c-19
/dev/i2c-20
/dev/i2c-21
/dev/i2c-22
/dev/i2c-23
/dev/i2c-24
/dev/i2c-25
/dev/i2c-26
/dev/i2c-27
/dev/i2c-28
/dev/i2c-29
/dev/i2c-30
/dev/i2c-31
rivo@Xcc:~/Desktop$ sudo sensors-detect
# sensors-detect revision 1.393 (2005/08/30 18:51:18)
This program will help you determine which I2C/SMBus modules you need to
load to use lm_sensors most effectively. You need to have i2c and
lm_sensors installed before running this program.
Also, you need to be `root', or at least have access to the /dev/i2c-*
files, for most things.
If you have patched your kernel and have some drivers built in, you can
safely answer NO if asked to load some modules. In this case, things may
seem a bit confusing, but they will still work.
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.
You do not need any special privileges for this.
Do you want to probe now? (YES/no): y
Probing for PCI bus adapters...
Use driver `i2c-i801' for device 00:1f.3: Intel 82801DB ICH4
Probe succesfully concluded.
We will now try to load each adapter module in turn.
Load `i2c-i801' (say NO if built into your kernel)? (YES/no): n
If you have undetectable or unsupported adapters, you can have them
scanned by manually loading the modules before running this script.
To continue, we need module `i2c-dev' to be loaded.
If it is built-in into your kernel, you can safely skip this.
i2c-dev is not loaded. Do you want to load it now? (YES/no): y
Module loaded succesfully.
We are now going to do the adapter probings. Some adapters may hang halfway
through; we can't really help that. Also, some chips will 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. That often
includes address 0x69 (clock chip).
Next adapter: I810/I815 DDC Adapter
Do you want to scan it? (YES/no/selectively): y
Client found at address 0x37
Client found at address 0x50
Probing for `SPD EEPROM'... Success!
(confidence 1, driver `eeprom')
Probing for `DDC monitor'... Success!
(confidence 8, driver `eeprom'), other addresses: 0x51 0x52 0x53 0x54 0x55 0 x56 0x57
Probing for `Maxim MAX6900'... Failed!
Client found at address 0x51
Probing for `SPD EEPROM'... Success!
(confidence 1, driver `eeprom')
Client found at address 0x52
Probing for `SPD EEPROM'... Success!
(confidence 1, driver `eeprom')
Client found at address 0x53
Probing for `SPD EEPROM'... Success!
(confidence 1, driver `eeprom')
Client found at address 0x54
Probing for `SPD EEPROM'... Success!
(confidence 1, driver `eeprom')
Client found at address 0x55
Probing for `SPD EEPROM'... Success!
(confidence 1, driver `eeprom')
Client found at address 0x56
Probing for `SPD EEPROM'... Success!
(confidence 1, driver `eeprom')
Client found at address 0x57
Probing for `SPD EEPROM'... Success!
(confidence 1, driver `eeprom')
Probing for `Sony Vaio EEPROM'... Failed!
Next adapter: I810/I815 I2C Adapter
Do you want to scan it? (YES/no/selectively): y
Some chips are also accessible through the ISA bus. ISA probes are
typically a bit more dangerous, as we have to write to I/O ports to do
this. This is usually safe though.
Do you want to scan the ISA bus? (YES/no): y
Probing for `National Semiconductor LM78'
Trying address 0x0290... Failed!
Probing for `National Semiconductor LM78-J'
Trying address 0x0290... Failed!
Probing for `National Semiconductor LM79'
Trying address 0x0290... Failed!
Probing for `Winbond W83781D'
Trying address 0x0290... Failed!
Probing for `Winbond W83782D'
Trying address 0x0290... Failed!
Probing for `Winbond W83627HF'
Trying address 0x0290... Failed!
Probing for `Winbond W83627EHF'
Trying address 0x0290... Failed!
Probing for `Winbond W83697HF'
Trying address 0x0290... Failed!
Probing for `Silicon Integrated Systems SIS5595'
Trying general detect... Failed!
Probing for `VIA Technologies VT82C686 Integrated Sensors'
Trying general detect... Failed!
Probing for `VIA Technologies VT8231 Integrated Sensors'
Trying general detect... Failed!
Probing for `ITE IT8712F'
Trying address 0x0290... Failed!
Probing for `ITE IT8705F / SiS 950'
Trying address 0x0290... Failed!
Probing for `IPMI BMC KCS'
Trying address 0x0ca0... Failed!
Probing for `IPMI BMC SMIC'
Trying address 0x0ca8... Failed!
Some Super I/O chips may also contain sensors. Super I/O probes are
typically a bit more dangerous, as we have to write to I/O ports to do
this. This is usually safe though.
Do you want to scan for Super I/O sensors? (YES/no): y
Probing for `ITE 8702F Super IO Sensors'
Failed! (0x1404)
Probing for `ITE 8705F Super IO Sensors'
Failed! (0x1404)
Probing for `ITE 8712F Super IO Sensors'
Failed! (0x1404)
Probing for `Nat. Semi. PC87351 Super IO Fan Sensors'
Failed! (0x14)
Probing for `Nat. Semi. PC87360 Super IO Fan Sensors'
Failed! (0x14)
Probing for `Nat. Semi. PC87363 Super IO Fan Sensors'
Failed! (0x14)
Probing for `Nat. Semi. PC87364 Super IO Fan Sensors'
Failed! (0x14)
Probing for `Nat. Semi. PC87365 Super IO Fan Sensors'
Failed! (0x14)
Probing for `Nat. Semi. PC87365 Super IO Voltage Sensors'
Failed! (0x14)
Probing for `Nat. Semi. PC87365 Super IO Thermal Sensors'
Failed! (0x14)
Probing for `Nat. Semi. PC87366 Super IO Fan Sensors'
Failed! (0x14)
Probing for `Nat. Semi. PC87366 Super IO Voltage Sensors'
Failed! (0x14)
Probing for `Nat. Semi. PC87366 Super IO Thermal Sensors'
Failed! (0x14)
Probing for `Nat. Semi. PC87372 Super IO Fan Sensors'
Failed! (0x14)
Probing for `Nat. Semi. PC87373 Super IO Fan Sensors'
Failed! (0x14)
Probing for `Nat. Semi. PC87591 Super IO'
Failed! (0x14)
Probing for `Nat. Semi. PC87371 Super IO'
Failed! (0x14)
Probing for `Nat. Semi. PC97371 Super IO'
Failed! (0x14)
Probing for `Nat. Semi. PC8739x Super IO'
Failed! (0x14)
Probing for `Nat. Semi. PC8741x Super IO'
Failed! (0x14)
Probing for `Nat. Semi. PCPC87427 Super IO'
Failed! (0x14)
Probing for `SMSC 47B27x Super IO Fan Sensors'
Failed! (0x14)
Probing for `SMSC 47M10x/13x Super IO Fan Sensors'
Failed! (0x14)
Probing for `SMSC 47M14x Super IO Fan Sensors'
Failed! (0x14)
Probing for `SMSC 47M15x/192 Super IO Fan Sensors'
Failed! (0x14)
Probing for `SMSC 47S42x Super IO Fan Sensors'
Failed! (0x14)
Probing for `SMSC 47S45x Super IO Fan Sensors'
Failed! (0x14)
Probing for `SMSC 47M172 Super IO'
Success... (no hardware monitoring capabilities)
Probing for `SMSC LPC47B397-NC Super IO'
Failed! (0x14)
Probing for `VT1211 Super IO Sensors'
Failed! (skipping family)
Probing for `Winbond W83627EHF/EHG Super IO Sensors'
Failed! (skipping family)
Do you want to scan for secondary Super I/O sensors? (YES/no): y
Probing for `ITE 8702F Super IO Sensors'
Failed! (skipping family)
Probing for `Nat. Semi. PC87351 Super IO Fan Sensors'
Failed! (skipping family)
Probing for `SMSC 47B27x Super IO Fan Sensors'
Failed! (skipping family)
Probing for `VT1211 Super IO Sensors'
Failed! (skipping family)
Probing for `Winbond W83627EHF/EHG Super IO Sensors'
Failed! (skipping family)
Now follows a summary of the probes I have just done.
Just press ENTER to continue:
Driver `eeprom' (should be inserted):
Detects correctly:
* Bus `I810/I815 DDC Adapter'
Busdriver `i2c-i810', I2C address 0x50 (and 0x51 0x52 0x53 0x54 0x55 0x56 0x 57)
Chip `DDC monitor' (confidence: 8)
I will now generate the commands needed to load the I2C modules.
Sometimes, a chip is available both through the ISA bus and an I2C bus.
ISA bus access is faster, but you need to load an additional driver module
for it. If you have the choice, do you want to use the ISA bus or the
I2C/SMBus (ISA/smbus)? smbus
To make the sensors modules behave correctly, add these lines to
/etc/modules:
#----cut here----
# I2C adapter drivers
i2c-i810
# I2C chip drivers
eeprom
#----cut here----
Do you want to add these lines to /etc/modules automatically? (yes/NO)y
rivo@Xcc:~/Desktop$ sudo /etc/init.d/module-init-tools
* Loading manual drivers... [ ok ]
rivo@Xcc:~/Desktop$ sudo modprobe i2c-i810
rivo@Xcc:~/Desktop$ sudo modprobe eeprom
rivo@Xcc:~/Desktop$ sudo modprobe i2c-i810 eeprom
rivo@Xcc:~/Desktop$ sensors
No sensors found!
rivo@Xcc:~/Desktop$ sudo depmod -a i2c-i810 eeprom
rivo@Xcc:~/Desktop$ sudo update-modules
I even tried reversing the order in which sensors-detect adds the modules but to no avail.
My /etc/modules
# /etc/modules: kernel modules to load at boot time.
#
# This file contains the names of kernel modules that should be loaded
# at boot time, one per line. Lines beginning with "#" are ignored.
lp
psmouse
# Generated by sensors-detect on Fri Aug 25 13:20:58 2006
# I2C chip drivers
eeprom
# I2C adapter drivers
i2c-i810
Can anyone help plz! :confused:
Installed lmsensors..all fine. but i cant see my cpu temp or fan speed. These are the sensors found:
# I2C adapter drivers
i2c-viapro
i2c-isa
# I2C chip drivers
eeprom
w83627hf
and this is the sensors list:
w83627hf-isa-0290
Adapter: ISA adapter
VCore 1: +4.08 V (min = +4.08 V, max = +4.08 V) ALARM (beep)
VCore 2: +4.08 V (min = +4.08 V, max = +4.08 V) ALARM (beep)
+3.3V: +4.08 V (min = +4.08 V, max = +4.08 V) ALARM (beep)
+5V: +6.85 V (min = +6.85 V, max = +6.85 V) ALARM (beep)
+12V: +15.50 V (min = +15.50 V, max = +15.50 V) ALARM (beep)
-12V: +6.06 V (min = +6.06 V, max = +6.06 V) ALARM (beep)
-5V: +5.10 V (min = +5.10 V, max = +5.10 V) ALARM (beep)
V5SB: +6.85 V (min = +6.85 V, max = +6.85 V) ALARM (beep)
VBat: +4.08 V (min = +4.08 V, max = +4.08 V) ALARM (beep)
fan1: 0 RPM (min = 0 RPM, div = 128) ALARM (beep)
fan2: 0 RPM (min = 0 RPM, div = 128) ALARM (beep)
fan3: 0 RPM (min = 0 RPM, div = 128) ALARM (beep)
temp1: -1°C (high = -1°C, hyst = -1°C) sensor = diode ALARM (beep)
temp2: +0.0°C (high = +0°C, hyst = +0°C) sensor = diode ALARM (beep)
temp3: +0.0°C (high = +0°C, hyst = +0°C) sensor = diode ALARM (beep)
vid: +0.000 V (VRM Version 2.4)
alarms: Chassis intrusion detection ALARM
beep_enable:
Sound alarm enabled
How can i turn on the temp sensors?