This problem is occurring on Lucid with IBM ACPI sensors as well. it is caused by computertemp assuming that the sensor info always is under the device/ symlink in the sysfs hwmon directory, but Documentation/hwmon/sysfs-interface says:
> Up to lm-sensors 3.0.0, libsensors looks for hardware monitoring attributes
> in the "physical" device directory. Since lm-sensors 3.0.1, attributes found
> in the hwmon "class" device directory are also supported. Complex drivers
> (e.g. drivers for multifunction chips) may want to use this possibility to
> avoid namespace pollution. The only drawback will be that older versions of
> libsensors won't support the driver in question.
So computertemp should look directly in /sys/class/hwmon/hwmonX/ if device/ doesn't exist.
This problem is occurring on Lucid with IBM ACPI sensors as well. it is caused by computertemp assuming that the sensor info always is under the device/ symlink in the sysfs hwmon directory, but Documentation/ hwmon/sysfs- interface says:
> Up to lm-sensors 3.0.0, libsensors looks for hardware monitoring attributes
> in the "physical" device directory. Since lm-sensors 3.0.1, attributes found
> in the hwmon "class" device directory are also supported. Complex drivers
> (e.g. drivers for multifunction chips) may want to use this possibility to
> avoid namespace pollution. The only drawback will be that older versions of
> libsensors won't support the driver in question.
So computertemp should look directly in /sys/class/ hwmon/hwmonX/ if device/ doesn't exist.