WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: TC5 and lm-sensors - adapter scan hangs  (Read 6015 times)

Offline virtualbox

  • Newbie
  • *
  • Posts: 21
TC5 and lm-sensors - adapter scan hangs
« on: February 22, 2014, 09:23:31 AM »
Hi,

I wanted to use lm-sensors in TC5.2 to monitor cpu, chips and gpu temps (if possible also cpu %). I didn't find it in 5.x repo, so I got it from 4.x repo and installed it.

At first I was faced with the problem described here:
http://forum.tinycorelinux.net/index.php/topic,16465.msg97938.html

So I extracted lm_sensors.tcz, edited /usr/local/sbin/sensors-detect and changed the first line to #!/usr/local/bin/perl -w and mksquashed it again back together. That fixed the not found error and I managed to get the script running.

I executed sensors-detect as root and accepted the default answers.

But at the point where the script is supposed to scan the SMBus I801 adapter it hangs. Nothing gets printed to terminal and it never completes:
Code: [Select]
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):

I have installed and loaded hwmon-3.8.13-tinycore.tcz and i2c-3.8.13-tinycore.tcz.

Also build and installed lm-sensors from source (v.3.3.5), but the end result is the same - sensors-detect does not complete the scan and I can't manage to setup lm_sensors conf file with all the nessesary sensors in it.

If I answer "no" to skip the scan part, then the script do finish:
Code: [Select]
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:
Code: [Select]
# 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

But that gives me only one coretemp without the information from the chipsets etc.

I know that this seems to be something to do with lm-sensors itself and maybe isn't appropiate to ask this here in TC forum, but I thought to give it a try. Maybe someone could give me some hints to get this scan done (am I missing something?).

Code: [Select]
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

Code: [Select]
tc@box:~$ sensors --version
sensors version 3.3.3 with libsensors version 3.3.3

Code: [Select]
tc@box:~$ uname -a
Linux box 3.8.13-tinycore #2 SMP Fri Feb 7 16:25:56 UTC 2014 i686 GNU/Linux

Offline virtualbox

  • Newbie
  • *
  • Posts: 21
Re: TC5 and lm-sensors - adapter scan hangs
« Reply #1 on: February 27, 2014, 04:22:05 AM »
In Ubuntu with psensor (on top of lm-sensors) all the info is coming up (cpu, gpu and chipset temp + cpu %) just great, so it's definitely not hardware related problem.

My motherboard has ICH9 chipset, so as I understand I need the i2c-i801.ko.gz driver from i2c-3.8.13-tinycore.tcz package.

From http://www.mjmwired.net/kernel/Documentation/i2c/busses/i2c-i801:
Quote
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

But It hangs. In Ubuntu it works 100%.

When I run sudo sensors-detect, I get this in /var/log/messages:
Code: [Select]
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

But the scan never completes.

I was thinking, that maybe I need manually point to the right device address, but how to find out what address to use:
Code: [Select]
...
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:

Quote
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
« Last Edit: February 27, 2014, 04:51:02 AM by virtualbox »

Offline curaga

  • Administrator
  • Hero Member
  • *****
  • Posts: 11044
Re: TC5 and lm-sensors - adapter scan hangs
« Reply #2 on: February 27, 2014, 05:09:25 AM »
You could copy the generated conf file from Ubuntu as is?
The only barriers that can stop you are the ones you create yourself.

Offline virtualbox

  • Newbie
  • *
  • Posts: 21
Re: TC5 and lm-sensors - adapter scan hangs
« Reply #3 on: February 27, 2014, 07:10:19 AM »
In Ubuntu I didn't run sensors-detect manually - I just searched psensor in synaptic package manager and installed it (as dependency lm-sensors got installed also). And I can't find /etc/sysconfig/lm_sensors in Ubuntu anywere.

Code: [Select]
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

Doing the same search in TC results as (I haven't put the /etc/sysconfig/lm_sensors/ to backup yet):
Code: [Select]
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

I attached a picture (psensors.jpg) showing psensor in work. I haven't configured psensor or lm-sensor in Ubuntu in any way - just did auto install with synaptic. And sensor information seems fine (if I do alot of HDD writing, e.g. dd zero or urandom to HDD then chipset temp goes up.. the same with CPU [both cores].. and also GPU temp goes up while watching some HD stuff etc.. all seems real to me at this point).

Psensor conf files (these files contain only Gnome conf):
Code: [Select]
/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

I am wondering.. how does this psensor work and communicate with lm-sensors, as I'm unable to find lm-sensor conf.

=================================

The second part what I did realise, is that sensors-detect hangs in Ubuntu also. I executed:
Code: [Select]
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):

In Ubuntu there is this nouveau adapter, that gets scanned, in TC there is only SMBus I801 adapter. Nevertheless both failed to scan SMBus I801 adapter :(

I'm really desperated, because I really like TC and want to use it as a minimal virtualization host and I want to have this possibility to monitor system temps.

Offline virtualbox

  • Newbie
  • *
  • Posts: 21
Re: TC5 and lm-sensors - adapter scan hangs
« Reply #4 on: February 27, 2014, 07:33:54 AM »
If I run sensors in TC (without sensors-detect), I get this:
Code: [Select]
tc@box:~$ sensors
acpitz-virtual-0
Adapter: Virtual device
temp1:        +71.5 C  (crit = +107.0 C)

Even if I execute sensors-detect and answer "no" to SMBus I801 adapter scan, this output remains the same. And this temp seems to high for CPU, chipset or GPU. As it states, it is a virtual device, so maybe it's calculated somehow. But I need real hardware temps.

================================================================

OK, I digged in lm-sensor webpage and found this at http://lm-sensors.org/wiki/Devices:

SENSOR CHIP DRIVERS
ManufacturerChipDetected by sensors-detectDriverBus typeSupported since kernelStatus / Comments
DellInspiron, Latitude, Precision, Vostronoi8kBIOS3.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.

PC I2C/SMBUS BUS DRIVERS
ManufacturerChipDriverSupported since kernelStatus / Comments
IntelICH9i2c-i8012.6.20Interrupt support is now available, try the  standalone i2c-i801 driver.

So as it seems by this information, sensors-detect doesn't have support for Dell Latitude.

Please, don't get angry at me that I didn't research this before starting this thread - I did, but somehow this didn't get my attension.

Anyway, the problem is still up, but I managed to get some answers - that is more than nothing i guess.

I didn't know that Dell doesn't support sensors information easily:
http://lists.lm-sensors.org/pipermail/lm-sensors/2014-February/041157.html ([lm-sensors] why must Dell machine use i8k?)
http://www.motherboardpoint.com/dell-fan-speed-control-t186638.html (Dell fan speed control)

So I must try this i8k driver and see, if this helps me with this problem.
« Last Edit: February 27, 2014, 08:44:14 AM by virtualbox »

Offline virtualbox

  • Newbie
  • *
  • Posts: 21
Re: TC5 and lm-sensors - adapter scan hangs
« Reply #5 on: February 27, 2014, 09:17:38 AM »
Turns out this i8k driver exist in TC:
Code: [Select]
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

I loaded the module and did lsmod:
Code: [Select]
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

Now when I execute sensors I get this:
Code: [Select]
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

The fan speed info is kind of funny, but I don't care about it. It gives this CPU line, 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..

...and what abount GPU and chipset temps..
« Last Edit: February 27, 2014, 09:19:45 AM by virtualbox »

Offline Rich

  • Administrator
  • Hero Member
  • *****
  • Posts: 11634
Re: TC5 and lm-sensors - adapter scan hangs
« Reply #6 on: February 27, 2014, 10:15:36 AM »
Hi virtualbox
Quote
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
baseline for what the idle temperature should be.

Offline tinypoodle

  • Hero Member
  • *****
  • Posts: 3857
Re: TC5 and lm-sensors - adapter scan hangs
« Reply #7 on: February 27, 2014, 11:29:32 AM »
1. How do the "crit" values reported by sensors compare between Core & Ubuntu?

2. Have you tried to get CPU temp through acpi? Comparing temp reported by acpi vs. sensors could be of interest.
"Software gets slower faster than hardware gets faster." Niklaus Wirth - A Plea for Lean Software (1995)

Offline virtualbox

  • Newbie
  • *
  • Posts: 21
Re: TC5 and lm-sensors - adapter scan hangs
« Reply #8 on: February 27, 2014, 02:49:14 PM »
Hi virtualbox
Quote
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
baseline for what the idle temperature should be.
Yes, 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.

I did some testing in Ubuntu and in TC to see, how CPU, chipset and GPU temps raise while at work.. and it seems real temp that gets reported under TC (acpitz-virtual-0 and i8k). Temps raise and fall pretty quickly, so that first tricked me to believe that temp in TC is bit to high. But it's definitely not GPU temp - it's whether chipset or CPU. But if it's CPU then which core? So maybe it's chipset temp (in Ubuntu I got similar temps for chipset, but CPU is also in the same category; to sort this out I need to avg. some period, but at this point it doesn't matter so much which one it is).

CONFIRMED: in UBUNTU psensor settings reveal that acpitz is chipset and 2 CPU cores have separate settings and are named as 'Intel CPU'. GPU is named as 'Nvidia GPU' (in "Edit Sensor Preferences" window).

1. How do the "crit" values reported by sensors compare between Core & Ubuntu?

2. Have you tried to get CPU temp through acpi? Comparing temp reported by acpi vs. sensors could be of interest.
If I execute sensors in Ubuntu I get this:
Code: [Select]
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)

tinypoodle, I'm not familiar with temp through acpi. I did searched around in /proc/acpi but as I remember I didn't find anything temp related. Can you be more specific as what do you mean through acpi?

So I'm still faced the question, how to get GPU (and CPU) temps under TC.. with this i8k driver. Maybe I need to configure i8k somehow.. or lm-sensor manually?
« Last Edit: February 27, 2014, 03:32:40 PM by virtualbox »