Zotac IONITX-A vs. lm-sensors

[pgruber]

Hi!

I have above mentioned ZOTAC ION ITX-A (Atom330 and Nvidia ION-Chipset) running here with Ubuntu 9.04.

My problem is that sensors-detect from lm-sensors-package does not find any sensor.
Downloaded Version 3.1.1 and compiled it. No effort...

Can someone point me to the right direction?`

Board must have a chip as in BIOS I can see a temp, the voltages and the fans...

Thanks,
Patrick

[d-range]

I would also like to know how to read the sensors on the Zotac ION board (and probably other boards using the ION chipset as well)

So far I've tried recompiling to the latest kernel with all sensor/i2c/smbus/etc drivers enabled as modules, and upgraded lm-sensors to the latest development snapshot.

sensors-detect gives me:

# uname -a
Linux ionbox 2.6.30-ion #4 SMP PREEMPT Mon Jun 22 23:10:08 CEST 2009 i686 GNU/Linux

# sensors-detect revision 5249 (2008-05-11 22:56:25 +0200)

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): 
Probing for PCI bus adapters...
Found unknown SMBus adapter 10de:0aa2 at 0000:00:03.2.
Sorry, no supported PCI bus adapters found.

If you have undetectable or unsupported I2C/SMBus 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.
Do you want to load `i2c-dev' now? (YES/no): 
Module loaded successfully.

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 nForce2 adapter at 4d00 (i2c-0)
Do you want to scan it? (YES/no/selectively): 
Client found at address 0x4c
Probing for `National Semiconductor LM75'...                No
Probing for `Dallas Semiconductor DS75'...                  No
Probing for `Analog Devices ADT7466'...                     No
Probing for `Andigilog aSC7511'...                          No
Probing for `Dallas Semiconductor DS1621/DS1631'...         No
Probing for `Analog Devices ADM1021'...                     No
Probing for `Analog Devices ADM1021A/ADM1023'...            No
Probing for `Maxim MAX1617'...                              No
Probing for `Maxim MAX1617A'...                             No
Probing for `Maxim MAX1668'...                              No
Probing for `Maxim MAX1805'...                              No
Probing for `Maxim MAX1989'...                              No
Probing for `Maxim MAX6655/MAX6656'...                      No
Probing for `TI THMC10'...                                  No
Probing for `National Semiconductor LM84'...                No
Probing for `Genesys Logic GL523SM'...                      No
Probing for `Onsemi MC1066'...                              No
Probing for `Maxim MAX1619'...                              No
Probing for `National Semiconductor LM82/LM83'...           No
Probing for `National Semiconductor LM90'...                No
Probing for `National Semiconductor LM89/LM99'...           No
Probing for `National Semiconductor LM86'...                No
Probing for `Analog Devices ADM1032'...                     No
Probing for `Maxim MAX6657/MAX6658/MAX6659'...              No
Probing for `Maxim MAX6648/MAX6692'...                      No
Probing for `Maxim MAX6680/MAX6681'...                      No
Probing for `Winbond W83L771W/G'...                         No
Probing for `Texas Instruments TMP401'...                   No
Probing for `National Semiconductor LM63'...                No
Probing for `Fintek F75363SG'...                            No
Probing for `Maxim MAX6633/MAX6634/MAX6635'...              No
Probing for `Analog Devices ADT7461'...                     No
Probing for `Fintek F75383S/M'...                           No
Client found at address 0x50
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 No
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'...                                 No
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'...                                 No
Probing for `EDID EEPROM'...                                No
Client found at address 0x53
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 No
Probing for `EDID EEPROM'...                                No

Next adapter: SMBus nForce2 adapter at 4e00 (i2c-1)
Do you want to scan it? (YES/no/selectively): 
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

Next adapter: NVIDIA i2c adapter  (i2c-2)
Do you want to scan it? (YES/no/selectively): 

Next adapter: NVIDIA i2c adapter  (i2c-3)
Do you want to scan it? (YES/no/selectively): 

Next adapter: NVIDIA i2c adapter  (i2c-4)
Do you want to scan it? (YES/no/selectively): 

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): 
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
Probing for `IPMI BMC KCS' at 0xca0...                      No
Probing for `IPMI BMC SMIC' at 0xca8...                     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): 
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'...                                      No
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): 
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

Sorry, no sensors were detected.
Either your sensors are not supported, or they are connected to an
I2C or SMBus adapter that is not supported. See
http://www.lm-sensors.org/wiki/FAQ/Chapter3 for further information.
If you find out what chips are on your board, check
http://www.lm-sensors.org/wiki/Devices for driver status.

So it seems to find an nForce SMbus adapter and an nvidia i2c bus, but no sensors.

I know there's at least a temperature sensor on the board, because the nvidia control panel shows the gpu temperature (which I guess is also the CPU temperature because it's a single package). There are no entries in /proc/acpi/thermal_zone or /proc/acpi/fan though, so it seems the nvidia panel gets the temperature itself, probably via the nvidia-kernel module

This is all a little annoying because the Atom 330 doesn't support speedstep either, and I'd really like to have the fan spin only when it's absolutely necessary (I use the box as a media player but also as a private server that's always on but hardly ever doing anything that would make it sweat). Right now the CPU maxes out at 1.6Ghz all the time and the fan speed is always the same, with the nvidia control panel showing a temperature around 45C, so there should be quite some room for improvement.

[domi55]

Hi All,

I'm also interested in this. I have exactly the same problem.
Does anybody have an idea?

[kzanol]

Just played around a bit with an acer revo, also based on nvidia ion platform. Obviously got identical results initialy - looks like the problems are mostly caused by lack of automatic detection, actually reading the sensors works if you load the right modules:

* running ubuntu jaunty, kernel 2.6.28-13-generic

* the MCP79 SMBus interface is supported by i2c_nforce2, module has to be told about new device id however
* the actual sensor seems to be mostly compatible with lm85

# modprobe i2c-dev
# modprobe i2c-nforce2
# echo "10de 0aa2" > /sys/bus/pci/drivers/nForce2_smbus/new_id

# i2cdetect -l should now show you two new nvidia SMBus adapters:

i2c-0 i2c NVIDIA i2c adapter I2C adapter
i2c-1 i2c NVIDIA i2c adapter I2C adapter
i2c-2 i2c NVIDIA i2c adapter I2C adapter
i2c-3 smbus SMBus nForce2 adapter at 4d00 SMBus adapter
i2c-4 smbus SMBus nForce2 adapter at 4e00 SMBus adapter

# modprobe lm85

# sensors
lm85-i2c-3-2e
Adapter: SMBus nForce2 adapter at 4d00
V1.5: +1.84 V (min = +0.00 V, max = +3.32 V)
VCore: +1.20 V (min = +0.00 V, max = +2.99 V)
V3.3: +3.33 V (min = +0.00 V, max = +4.38 V)
V5: +5.08 V (min = +0.00 V, max = +6.64 V)
V12: +1.00 V (min = +0.00 V, max = +15.94 V)
CPU_Fan: 3590 RPM (min = 0 RPM)
fan2: 0 RPM (min = 0 RPM)
fan3: 0 RPM (min = 0 RPM)
fan4: 0 RPM (min = 0 RPM)
CPU Temp: +68.0°C (low = -127.0°C, high = +127.0°C)
Board Temp: +52.0°C (low = -127.0°C, high = +127.0°C)
Remote Temp: +59.0°C (low = -127.0°C, high = +127.0°C)
cpu0_vid: +0.000 V

Output looks fairly reasonable at first glance, not too sure about Board and Remote Temp though - Both CPU Temp & fan looks good & changes as expected with increased system load.

Bye, Martin

[vikjon0]

This looks good, but when I do
echo "10de 0aa2" > /sys/bus/pci/drivers/nForce2_smbus/new_id

I get
-bash: /sys/bus/pci/drivers/nForce2_smbus/new_id: Permission denied


Any ideas?

Running Asrock ION 330
***
uname -r
2.6.28-13-generic

[vikjon0]

Ok, thanks!

As root I can run all the commands and
# i2cdetect -l
gives the the expected result.

But
# sensors
still does not work.

Does it require this?:

recompiling to the latest kernel with all sensor/i2c/smbus/etc drivers enabled as modules, and upgraded lm-sensors to the latest development snapshot.

//J

[kzanol]

looks like the sensors actually used on the boards are vendor specific. The acer revo 3600 I've got uses an ADT7476 sensor which can be handled by the lm85 module.

after you've enabled the SMBus interface, you can rerun sensors-detect to see if/which sensors are found on your board.

Bye, Martin

[domi55]

@kzanol:

I can confirm that this procedure does not work for zotac ION ITX A boards:

i2cdetect seems to give the right output:

(T: XBMCLive)root@XBMCLive:/# i2cdetect -l
i2c-0   i2c             NVIDIA i2c adapter                      I2C adapter
i2c-1   i2c             NVIDIA i2c adapter                      I2C adapter
i2c-2   i2c             NVIDIA i2c adapter                      I2C adapter
i2c-3   smbus           SMBus nForce2 adapter at 4d00           SMBus adapter
i2c-4   smbus           SMBus nForce2 adapter at 4e00           SMBus adapter

But after re-running 'sensors-detect' I still get the message:

Sorry, no sensors were detected.

[domi55]

@kzanol: Are you able to help us on this problem?

[kzanol]

Some more information: As stated in my first post, my results where obtained on an acer revo, not on the zotac board; both are nvidia ion boards but the zotac uses a different hardware sensor. I haven't been able to figure out which one so far, will try to find some more info on this. Some good news: regardless of hardware sensors all ion boards share at least one sensor, namely the on-chip sensor in the atom cpu. The coretemp module required for reading such sensors doesn't yet support the atom cpu, so it doesn't work out of tzhe box. A patch to fix this has been available since 2.6.27; unfortunately it hasn't yet (as of 2.6.30) been integrated into the kernel source - there's an effort to get it included in one of the next kernel versions. In the meantime you can either patch your kernel source to add coretemp support for the atom CPU (http://mabene.icomedias.com/coretemp.patch) or you can use my patched coretemp.ko module (works with current jaunty kernel linux-image-2.6.28-13-generic, http://mabene.icomedias.com/coretemp.ko) bye, Martin