unknown sensors found on SiS648FX chipset

[tom.l.ferris@…]

Running sensors-detect misdetects my chipset as being a requiring the i2c-sis96x driver. However research has shown me that I have a SiS648FX chipset, which would use the (beta) i2c-sis645 driver. This was not included in my distro install, and in the readme for the source code it states that "The kernel modules in this package will NOT compile for 2.6". I have the 2.6.18.2-34 kernel. Uniwill 257SA0 motherboard inside OEM Fujitsu-Siemens Amilo D 1845 laptop. Believed that motherboard had no sensors until recently when PC Wizard 2007 detected sensors for CPU core voltage, battery voltage, and CPU temperature. How can I get some sensor readings?

Attached: lspci, sensors-detect, HWDinfo --generated by PC Wizard, details SMBus info.

[ticket]

This seems to have been corrected to some extent in 2.10.3:

[root@localhost ~]# sensors-detect
# sensors-detect revision 4348 (2007-03-18 02:45:21 -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...
Sorry, no known PCI bus adapters found.

We will now try to load each adapter module in turn.
If you have undetectable or unsupported 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.

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
Probing for `Silicon Integrated Systems SIS5595'...         No
Probing for `VIA VT82C686 Integrated Sensors'...            No
Probing for `VIA VT8231 Integrated Sensors'...              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): y
Probing for Super-I/O at 0x2e/0x2f
Trying family `ITE'...                                      Yes
Found unknown chip with ID 0xf411
Trying family `National Semiconductor'...                   Yes
Found unknown chip with ID 0xf411
Trying family `SMSC'...                                     Yes
Found unknown chip with ID 0xf411
Trying family `VIA/Winbond/Fintek'...                       Yes
Found unknown chip with ID 0xf411
Probing for Super-I/O at 0x4e/0x4f
Trying family `ITE'...                                      Yes
Found unknown chip with ID 0xec11
Trying family `National Semiconductor'...                   Yes
Found `Nat. Semi. PC87591 Super IO'                         
    (but not activated)
Trying family `SMSC'...                                     Yes
Found unknown chip with ID 0xec11
Trying family `VIA/Winbond/Fintek'...                       Yes
Found unknown chip with ID 0xec11

Some CPUs or memory controllers may also contain embedded sensors.
Do you want to scan for them? (YES/no): y
AMD K8 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 doc/FAQ,
doc/lm_sensors-FAQ.html or http://www.lm-sensors.org/wiki/FAQ
(FAQ #4.24.3) for further information.
If you find out what chips are on your board, check
http://www.lm-sensors.org/wiki/Devices for driver status.

However, the bus adapter is still not detected properly, so it appears that there is no support for my chipset in the 2.6 kernel? Output is the same as above even with i2c-sis96x driver loaded.

[khali]

The i2c-sis645 driver was renamed to i2c-sis96x in Linux 2.6. They are otherwise the same driver. The first sensors-detect output shows that the i2c-sis96x driver works fine for you. I have no idea why the SMBus master disappeared in the second sensors-detect output though, did you change anything in the meantime? Anyway, no sensors on the SMBus, so this doesn't really matter as far as lm-sensors is concerned.

Doesn't PC Wizard 2007 say what sensor device it found? That would help. Please also give the details (possibly a screenshot) of what values it displays exactly, and how they change over time.

What CPU is in this laptop?

[ticket]

Thanks for responding. The second sensors-detect output was from a fedora core 6 live cd, the first from OpenSuSE 10.2 (I am thinking of trying it out due to the availability of fedora rpms). Whenever I ran sensors-detect on virtually any distro using lm_sensors < 2.10.3 I always received message no sensors where found when running the command "sensors", I never even got readings from eeproms, although not sensors, but sensors-detect found them, does this indicate some kind of bug? Sensors-detect can find eeproms, but "sensors" does not display them when eeprom driver is loaded, so could other sensors not be displayed which the i2c-sis96x driver could find? But likewise it appears this is of no consequence if there are no sensors on the SMBus anyway. PC Wizard does not display what the sensors are. Emailed author twice, he replied once to paste the output of the HW dump (included in first ticket post as attachment) but have had no response. See attached screenshot. CPU temperature always stays at constant 75 deg C, I believe this is a BIOS issue which FSC never bothered to update. I tried to fix this by flashing a non-oem bios for my board which had improved i2c monitoring but all that did was cost me a CMOS bios chip. I have never noticed cpu core change, I believe this may be a similar issue. However sensors-detect from the new version of lm_sensors found loads of unknown sensors so I do believe that this is not a complete list. please let me know what I can do to probe my hw as I a am new to linux.

[khali]

SPD EEPROM contents can be read using the decode-dimms.pl script. It is expected that "sensors" no longer displays anything about them (they are not sensors after all.)

sensors-detect doesn't find unknown sensors, it finds one unknown chip, which may or may not include sensors. And actually I believe it is simply the PC87591 emulating another device at a different address, I seem to remember something like that with this chip. The bottom line is that I don't think there is any hardware monitoring chip in your laptop that lm-sensors can use.

I also don't think that PC Wizard 2007 found a stand-alone sensor device. For one thing, I hope it would give the chip name if it did. For another, it would certainly show many more values than it does in that case.

So I think that PC Wizard 2007 gets its temperature value from ACPI or possibly from a Fujitsu-Siemens-specific interface. Try loading the thermal ACPI kernel module (probably already loaded on a laptop anyway): modprobe thermal Then look in /proc/acpi/thermal, I guess you'll find a temperature value, or alternatively, run "acpi -t".

As for the CPU voltage, 1.116V seems a bit low for a Mobile Pentium 4 548 according to this page:

 http://users.erols.com/chare/elec.htm

CPU-Z seems to agree, it says 1.388V for that CPU model. Probably the Vcore is lowered when the CPU is idle. If it never changes, it could be a nominal Vcore value (computed from the VID pins) and not a measurement. The linux kernel doesn't present this value to user-space as far as I know, but you may look at the kernel logs for information when the appropriate CPUFreq driver is loaded.