tc@box:~$ sudo /usr/local/sbin/sensors-detect
# sensors-detect revision 6085 (2012-10-30 18:18:45 +0100)
# System: Dell Inc. Latitude E6400 (laptop)
# Board: Dell Inc. 0X574R
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.
Some south bridges, CPUs or memory controllers contain embedded sensors.
Do you want to scan for them? This is totally safe. (YES/no):
Module cpuid loaded successfully.
Silicon Integrated Systems SIS5595... No
VIA VT82C686 Integrated Sensors... No
VIA VT8231 Integrated Sensors... No
AMD K8 thermal sensors... No
AMD Family 10h thermal sensors... No
AMD Family 11h thermal sensors... No
AMD Family 12h and 14h thermal sensors... No
AMD Family 15h thermal sensors... No
AMD Family 15h power sensors... No
Intel digital thermal sensor... Success!
(driver `coretemp')
Intel AMB FB-DIMM thermal sensor... No
VIA C7 thermal sensor... No
VIA Nano thermal sensor... No
Some Super I/O chips contain embedded 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/ITE'... No
Trying family `SMSC'... Yes
Found unknown chip with ID 0x4680
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor/ITE'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Nuvoton/Fintek'... No
Trying family `ITE'... No
Some hardware monitoring chips are 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 LM79' at 0x290... No
Probing for `Winbond W83781D' at 0x290... No
Probing for `Winbond W83782D' at 0x290... No
Lastly, we can probe the I2C/SMBus adapters for connected hardware
monitoring devices. This is the most risky part, and while it works
reasonably well on most systems, it has been reported to cause trouble
on some systems.
Do you want to probe the I2C/SMBus adapters now? (YES/no):
Using driver `i2c-i801' for device 0000:00:1f.3: Intel ICH9
Module i2c-dev loaded successfully.
Next adapter: SMBus I801 adapter at 1100 (i2c-0)
Do you want to scan it? (YES/no/selectively):
tc@box:~$ sudo /usr/local/sbin/sensors-detect
# sensors-detect revision 6085 (2012-10-30 18:18:45 +0100)
# System: Dell Inc. Latitude E6400 (laptop)
# Board: Dell Inc. 0X574R
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.
Some south bridges, CPUs or memory controllers contain embedded sensors.
Do you want to scan for them? This is totally safe. (YES/no):
Silicon Integrated Systems SIS5595... No
VIA VT82C686 Integrated Sensors... No
VIA VT8231 Integrated Sensors... No
AMD K8 thermal sensors... No
AMD Family 10h thermal sensors... No
AMD Family 11h thermal sensors... No
AMD Family 12h and 14h thermal sensors... No
AMD Family 15h thermal sensors... No
AMD Family 15h power sensors... No
Intel digital thermal sensor... Success!
(driver `coretemp')
Intel AMB FB-DIMM thermal sensor... No
VIA C7 thermal sensor... No
VIA Nano thermal sensor... No
Some Super I/O chips contain embedded 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/ITE'... No
Trying family `SMSC'... Yes
Found unknown chip with ID 0x4680
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor/ITE'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Nuvoton/Fintek'... No
Trying family `ITE'... No
Some hardware monitoring chips are 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 LM79' at 0x290... No
Probing for `Winbond W83781D' at 0x290... No
Probing for `Winbond W83782D' at 0x290... No
Lastly, we can probe the I2C/SMBus adapters for connected hardware
monitoring devices. This is the most risky part, and while it works
reasonably well on most systems, it has been reported to cause trouble
on some systems.
Do you want to probe the I2C/SMBus adapters now? (YES/no):
Using driver `i2c-i801' for device 0000:00:1f.3: Intel ICH9
Next adapter: SMBus I801 adapter at 1100 (i2c-0)
Do you want to scan it? (YES/no/selectively): no
Now follows a summary of the probes I have just done.
Just press ENTER to continue:
Driver `coretemp':
* Chip `Intel digital thermal sensor' (confidence: 9)
Do you want to overwrite /etc/sysconfig/lm_sensors? (YES/no):
Copy prog/init/lm_sensors.init to /etc/init.d/lm_sensors
for initialization at boot time.
You should now start the lm_sensors service to load the required
kernel modules.
And the /etc/sysconfig/lm_sensors content:# Generated by sensors-detect on Sat Feb 22 14:10:53 2014
# This file is sourced by /etc/init.d/lm_sensors and defines the modules to
# be loaded/unloaded.
#
# The format of this file is a shell script that simply defines variables:
# HWMON_MODULES for hardware monitoring driver modules, and optionally
# BUS_MODULES for any required bus driver module (for example for I2C or SPI).
HWMON_MODULES="coretemp"
# For compatibility reasons, modules are also listed individually as variables
# MODULE_0, MODULE_1, MODULE_2, etc.
# You should use BUS_MODULES and HWMON_MODULES instead if possible.
MODULE_0=coretemp
tc@box:~$ lspci
00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub (rev 07)
00:01.0 PCI bridge: Intel Corporation Mobile 4 Series Chipset PCI Express Graphics Port (rev 07)
00:19.0 Ethernet controller: Intel Corporation 82567LM Gigabit Network Connection (rev 03)
00:1a.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 03)
00:1a.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 (rev 03)
00:1a.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 (rev 03)
00:1a.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 03)
00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03)
00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 (rev 03)
00:1c.1 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 (rev 03)
00:1c.2 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 3 (rev 03)
00:1d.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 03)
00:1d.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 03)
00:1d.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 03)
00:1d.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 93)
00:1f.0 ISA bridge: Intel Corporation ICH9M-E LPC Interface Controller (rev 03)
00:1f.2 SATA controller: Intel Corporation ICH9M/M-E SATA AHCI Controller (rev 03)
00:1f.3 SMBus: Intel Corporation 82801I (ICH9 Family) SMBus Controller (rev 03)
01:00.0 VGA compatible controller: nVidia Corporation G98M [Quadro NVS 160M] (rev a1)
0c:00.0 Network controller: Intel Corporation Ultimate N WiFi Link 5300
tc@box:~$ sensors --version
sensors version 3.3.3 with libsensors version 3.3.3
tc@box:~$ uname -a
Linux box 3.8.13-tinycore #2 SMP Fri Feb 7 16:25:56 UTC 2014 i686 GNU/Linux
Kernel driver i2c-i801
2
3 Supported adapters:
4 * Intel 82801AA and 82801AB (ICH and ICH0 - part of the
5 '810' and '810E' chipsets)
6 * Intel 82801BA (ICH2 - part of the '815E' chipset)
7 * Intel 82801CA/CAM (ICH3)
8 * Intel 82801DB (ICH4) (HW PEC supported)
9 * Intel 82801EB/ER (ICH5) (HW PEC supported)
10 * Intel 6300ESB
11 * Intel 82801FB/FR/FW/FRW (ICH6)
12 * Intel 82801G (ICH7)
13 * Intel 631xESB/632xESB (ESB2)
14 * Intel 82801H (ICH8)
15 * Intel 82801I (ICH9)
16 * Intel EP80579 (Tolapai)
17 * Intel 82801JI (ICH10)
18 * Intel 5/3400 Series (PCH)
19 * Intel 6 Series (PCH)
20 * Intel Patsburg (PCH)
21 * Intel DH89xxCC (PCH)
22 * Intel Panther Point (PCH)
23 * Intel Lynx Point (PCH)
24 * Intel Lynx Point-LP (PCH)
25 * Intel Avoton (SOC)
26 * Intel Wellsburg (PCH)
27 * Intel Coleto Creek (PCH)
28 * Intel Wildcat Point-LP (PCH)
29 Datasheets: Publicly available at the Intel website
box authpriv.notice sudo: tc : TTY=pts/0 ; PWD=/home/tc ; USER=root ; COMMAND=/usr/local/sbin/sensors-detect
box user.info kernel: i2c /dev entries driver
...
Lastly, we can probe the I2C/SMBus adapters for connected hardware
monitoring devices. This is the most risky part, and while it works
reasonably well on most systems, it has been reported to cause trouble
on some systems.
Do you want to probe the I2C/SMBus adapters now? (YES/no): yes
Using driver `i2c-i801' for device 0000:00:1f.3: Intel ICH9
Next adapter: SMBus I801 adapter at 1100 (i2c-0)
Do you want to scan it? (YES/no/selectively): selectively
Please enter one or more addresses not to scan. Separate them with commas.
You can specify a range by using dashes. Example: 0x58-0x5f,0x69.
Addresses:
tc@box:~$ lsmod
Module Size Used by Tainted: P
i2c_dev 12288 2
cpuid 12288 0
cpufreq_stats 12288 0
cpufreq_userspace 12288 0
cpufreq_powersave 12288 0
cpufreq_conservative 12288 0
iwldvm 86016 0
mac80211 155648 1 iwldvm
iwlwifi 57344 1 iwldvm
wl 3833856 0
i2c_i801 16384 1
cfg80211 110592 4 iwldvm,mac80211,iwlwifi,wl
lib80211 12288 1 wl
dell_wmi 12288 0
acpi_cpufreq 12288 1
sparse_keymap 12288 1 dell_wmi
squashfs 24576 245
microcode 12288 0
pcspkr 12288 0
loop 20480 490
video 16384 0
battery 16384 0
e1000e 106496 0
wmi 12288 1 dell_wmi
backlight 12288 1 video
lpc_ich 16384 0
ac 12288 0
mfd_core 12288 1 lpc_ich
mperf 12288 1 acpi_cpufreq
ubu:~$ sudo find / -name '*sensors*'
/etc/init.d/lm-sensors
/etc/rcS.d/S47lm-sensors
/etc/sensors.d
/etc/sensors3.conf
/home/tc/.gconf/apps/psensor/sensors
/lib/systemd/system/lm-sensors.service
/lib/udev/rules.d/69-cd-sensors.rules
/lib/modules/3.11.0-12-generic/kernel/drivers/iio/common/st_sensors
/lib/modules/3.11.0-12-generic/kernel/drivers/iio/common/st_sensors/st_sensors_i2c.ko
/lib/modules/3.11.0-12-generic/kernel/drivers/iio/common/st_sensors/st_sensors_spi.ko
/lib/modules/3.11.0-12-generic/kernel/drivers/iio/common/st_sensors/st_sensors.ko
/lib/modules/3.11.0-12-generic/kernel/drivers/iio/common/hid-sensors
/lib/modules/3.11.10/kernel/drivers/iio/common/hid-sensors
/lib/modules/3.11.10/kernel/drivers/iio/common/st_sensors
/lib/modules/3.11.10/kernel/drivers/iio/common/st_sensors/st_sensors.ko
/lib/modules/3.11.10/kernel/drivers/iio/common/st_sensors/st_sensors_i2c.ko
/lib/modules/3.11.10/kernel/drivers/iio/common/st_sensors/st_sensors_spi.ko
/usr/bin/sensors-conf-convert
/usr/bin/sensors
/usr/lib/x86_64-linux-gnu/libsensors.so.4.3.2
/usr/lib/x86_64-linux-gnu/libsensors.so.4
/usr/lib/x86_64-linux-gnu/colord-sensors
/usr/sbin/sensors-detect
/usr/share/doc/lm-sensors
/usr/share/doc/lm-sensors/temperature-sensors
/usr/share/doc/libsensors4
/usr/share/man/man1/sensors.1.gz
/usr/share/man/man1/sensors-conf-convert.1.gz
/usr/share/man/man5/sensors.conf.5.gz
/usr/share/man/man8/sensors-detect.8.gz
/usr/share/vim/vim74/syntax/sensors.vim
/usr/share/vim/vim74/ftplugin/sensors.vim
/usr/share/libsensors4
/usr/share/app-install/desktop/xsensors:xsensors.desktop
/usr/src/linux-headers-3.11.0-12/include/linux/iio/common/st_sensors_i2c.h
/usr/src/linux-headers-3.11.0-12/include/linux/iio/common/st_sensors_spi.h
/usr/src/linux-headers-3.11.0-12/include/linux/iio/common/st_sensors.h
/usr/src/linux-headers-3.11.0-12/drivers/iio/common/hid-sensors
/usr/src/linux-headers-3.11.0-12/drivers/iio/common/st_sensors
/usr/src/linux-headers-3.11.0-12-generic/include/config/iio/st/sensors
/usr/src/linux-headers-3.11.0-12-generic/include/config/sensors
/usr/src/linux-headers-3.11.10/drivers/iio/common/hid-sensors
/usr/src/linux-headers-3.11.10/drivers/iio/common/st_sensors
/usr/src/linux-headers-3.11.10/include/linux/iio/common/st_sensors_i2c.h
/usr/src/linux-headers-3.11.10/include/linux/iio/common/st_sensors_spi.h
/usr/src/linux-headers-3.11.10/include/linux/iio/common/st_sensors.h
/usr/src/linux-headers-3.11.10/include/config/sensors
/usr/src/linux-headers-3.11.10/include/config/iio/st/sensors
/var/lib/dpkg/info/lm-sensors.postinst
/var/lib/dpkg/info/lm-sensors.md5sums
/var/lib/dpkg/info/lm-sensors.preinst
/var/lib/dpkg/info/lm-sensors.list
/var/lib/dpkg/info/libqt5sensors5:amd64.list
/var/lib/dpkg/info/lm-sensors.postrm
/var/lib/dpkg/info/libqt5sensors5:amd64.postrm
/var/lib/dpkg/info/lm-sensors.conffiles
/var/lib/dpkg/info/libsensors4:amd64.list
/var/lib/dpkg/info/libsensors4:amd64.md5sums
/var/lib/dpkg/info/libsensors4:amd64.preinst
/var/lib/dpkg/info/libsensors4:amd64.postinst
/var/lib/dpkg/info/libsensors4:amd64.postrm
/var/lib/dpkg/info/libsensors4:amd64.conffiles
/var/lib/dpkg/info/libsensors4:amd64.shlibs
/var/lib/dpkg/info/libsensors4:amd64.symbols
tc@box:~$ sudo find / -name '*sensors*'
/etc/sensors3.conf
/etc/sensors.d
/etc/sysconfig/lm_sensors
/tmp/sensors_find_ubuntu
/tmp/sensors-detect_short
/tmp/sensors-detect
/tmp/psensors_gconf
/tmp/psensors.jpg
/tmp/tcloop/lm_sensors
/tmp/tcloop/lm_sensors/etc/sensors.d
/tmp/tcloop/lm_sensors/etc/sensors3.conf
/tmp/tcloop/lm_sensors/usr/local/bin/sensors
/tmp/tcloop/lm_sensors/usr/local/bin/sensors-conf-convert
/tmp/tcloop/lm_sensors/usr/local/lib/libsensors.a
/tmp/tcloop/lm_sensors/usr/local/lib/libsensors.so
/tmp/tcloop/lm_sensors/usr/local/lib/libsensors.so.4
/tmp/tcloop/lm_sensors/usr/local/lib/libsensors.so.4.3.2
/tmp/tcloop/lm_sensors/usr/local/sbin/sensors-detect
/usr/local/sbin/sensors-detect
/usr/local/bin/sensors-conf-convert
/usr/local/bin/sensors
/usr/local/tce.installed/lm_sensors
/usr/local/lib/libsensors.so.4.3.2
/usr/local/lib/libsensors.so.4
/usr/local/lib/libsensors.so
/usr/local/lib/libsensors.a
/home/tc/.gconf/apps/psensor/sensors/lmsensor@32@nouveau-pci-0100@32@temp1
/home/tc/.gconf/apps/psensor/sensors/lmsensor@32@coretemp-isa-0000@32@Core@32@1
/home/tc/.gconf/apps/psensor/sensors/lmsensor@32@coretemp-isa-0000@32@Core@32@0
/home/tc/.gconf/apps/psensor/sensors/lmsensor@32@acpitz-virtual-0@32@temp1
ubu:~$ sudo sensors-detect
[sudo] password for tc:
# sensors-detect revision 6085 (2012-10-30 18:18:45 +0100)
# System: Dell Inc. Latitude E6400 (laptop)
# Board: Dell Inc. 0X574R
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.
Some south bridges, CPUs or memory controllers contain embedded sensors.
Do you want to scan for them? This is totally safe. (YES/no):
Module cpuid loaded successfully.
Silicon Integrated Systems SIS5595... No
VIA VT82C686 Integrated Sensors... No
VIA VT8231 Integrated Sensors... No
AMD K8 thermal sensors... No
AMD Family 10h thermal sensors... No
AMD Family 11h thermal sensors... No
AMD Family 12h and 14h thermal sensors... No
AMD Family 15h thermal sensors... No
AMD Family 15h power sensors... No
Intel digital thermal sensor... Success!
(driver `coretemp')
Intel AMB FB-DIMM thermal sensor... No
VIA C7 thermal sensor... No
VIA Nano thermal sensor... No
Some Super I/O chips contain embedded 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/ITE'... No
Trying family `SMSC'... Yes
Found unknown chip with ID 0x4680
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor/ITE'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Nuvoton/Fintek'... No
Trying family `ITE'... No
Some hardware monitoring chips are 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 LM79' at 0x290... No
Probing for `Winbond W83781D' at 0x290... No
Probing for `Winbond W83782D' at 0x290... No
Lastly, we can probe the I2C/SMBus adapters for connected hardware
monitoring devices. This is the most risky part, and while it works
reasonably well on most systems, it has been reported to cause trouble
on some systems.
Do you want to probe the I2C/SMBus adapters now? (YES/no):
Using driver `i2c-i801' for device 0000:00:1f.3: Intel ICH9
Module i2c-i801 loaded successfully.
Module i2c-dev loaded successfully.
Next adapter: nouveau-0000:01:00.0-0 (i2c-0)
Do you want to scan it? (yes/NO/selectively):
Next adapter: nouveau-0000:01:00.0-1 (i2c-1)
Do you want to scan it? (yes/NO/selectively):
Next adapter: nouveau-0000:01:00.0-2 (i2c-2)
Do you want to scan it? (yes/NO/selectively):
Next adapter: nouveau-0000:01:00.0-3 (i2c-3)
Do you want to scan it? (yes/NO/selectively):
Next adapter: nouveau-0000:01:00.0-4 (i2c-4)
Do you want to scan it? (yes/NO/selectively):
Next adapter: nouveau-0000:01:00.0-5 (i2c-5)
Do you want to scan it? (yes/NO/selectively):
Next adapter: nouveau-0000:01:00.0-8 (i2c-6)
Do you want to scan it? (yes/NO/selectively):
Next adapter: nouveau-0000:01:00.0-9 (i2c-7)
Do you want to scan it? (yes/NO/selectively):
Next adapter: nouveau-0000:01:00.0-10 (i2c-8)
Do you want to scan it? (yes/NO/selectively):
Next adapter: nouveau-0000:01:00.0-11 (i2c-9)
Do you want to scan it? (yes/NO/selectively):
Next adapter: SMBus I801 adapter at 1100 (i2c-10)
Do you want to scan it? (YES/no/selectively):
tc@box:~$ sensors
acpitz-virtual-0
Adapter: Virtual device
temp1: +71.5 C (crit = +107.0 C)
Manufacturer | Chip | Detected by sensors-detect | Driver | Bus type | Supported since kernel | Status / Comments |
Dell | Inspiron, Latitude, Precision, Vostro | no | i8k | BIOS | 3.0 or standalone driver | (2011-05-27) The driver is old, but it did not implement the standard hwmon interface until kernel 3.0. Please test the standalone driver and report. The monitoring part should be working fine, but the fan speed control part is still experimental. |
Manufacturer | Chip | Driver | Supported since kernel | Status / Comments |
Intel | ICH9 | i2c-i801 | 2.6.20 | Interrupt support is now available, try the standalone i2c-i801 driver. |
tc@box:~$ modinfo i8k
filename: kernel/drivers/char/i8k.ko.gz
license: GPL
author: Massimo Dal Zotto (dz@debian.org)
description: Driver for accessing SMM BIOS on Dell laptops
depends:
vermagic: 3.8.13-tinycore SMP mod_unload 486
parm: fan_mult:Factor to multiply fan speed with
parm: power_status:Report power status in /proc/i8k
parm: restricted:Allow fan control if SYS_ADMIN capability set
parm: ignore_dmi:Continue probing hardware even if DMI data does not match
parm: force:Force loading without checking for supported models
tc@box:~$ sudo modprobe i8k
tc@box:~$ lsmod
Module Size Used by Tainted: P
i8k 12288 0
i2c_dev 12288 4
cpuid 12288 0
cpufreq_stats 12288 0
cpufreq_powersave 12288 0
cpufreq_userspace 12288 0
cpufreq_conservative 12288 0
iwldvm 86016 0
mac80211 155648 1 iwldvm
iwlwifi 57344 1 iwldvm
wl 3833856 0
i2c_i801 16384 2
cfg80211 110592 4 iwldvm,mac80211,iwlwifi,wl
lib80211 12288 1 wl
dell_wmi 12288 0
sparse_keymap 12288 1 dell_wmi
acpi_cpufreq 12288 1
squashfs 24576 245
microcode 12288 0
pcspkr 12288 0
loop 20480 490
video 16384 0
e1000e 106496 0
battery 16384 0
backlight 12288 1 video
wmi 12288 1 dell_wmi
ac 12288 0
lpc_ich 16384 0
mfd_core 12288 1 lpc_ich
mperf 12288 1 acpi_cpufreq
tc@box:~$ sensors
acpitz-virtual-0
Adapter: Virtual device
temp1: +62.5 C (crit = +107.0 C)
i8k-virtual-0
Adapter: Virtual device
Right Fan: 108210 RPM
CPU: +62.0 C
but its hard to believe this temp is right. Or maybe the psensor in Ubuntu has thouse temps wrong all the time. Its really hard to figure this out..If you go into your machines BIOS setup, is there a page that displays the CPU temperatures? That should provide a decent
Hi virtualboxYes, I was thinking the same thing at some moment, but unfortunately dell's bios doesn't have this kind of information. It would be good to compare these.Quotebut its hard to believe this temp is right. Or maybe the psensor in Ubuntu has thouse temps wrong all the time. Its really hard to figure this out..If you go into your machines BIOS setup, is there a page that displays the CPU temperatures? That should provide a decent
baseline for what the idle temperature should be.
1. How do the "crit" values reported by sensors compare between Core & Ubuntu?If I execute sensors in Ubuntu I get this:
2. Have you tried to get CPU temp through acpi? Comparing temp reported by acpi vs. sensors could be of interest.
ubu:~$ sensors
acpitz-virtual-0
Adapter: Virtual device
temp1: +45.5°C (crit = +107.0°C)
coretemp-isa-0000
Adapter: ISA adapter
Core 0: +43.0°C (high = +105.0°C, crit = +105.0°C)
Core 1: +44.0°C (high = +105.0°C, crit = +105.0°C)
nouveau-pci-0100
Adapter: PCI adapter
temp1: +43.0°C (high = +95.0°C, hyst = +3.0°C)
(crit = +105.0°C, hyst = +2.0°C)
(emerg = +110.0°C, hyst = +5.0°C)