Re: Disable libsensors in 2.2.9
Bill WIlson <[email protected]>
| Newsgroups | gmane.comp.gnome.apps.gkrellm |
|---|---|
| Message-ID | <[email protected]> |
On Mon, 30 Oct 2006 00:37:21 -0600 Ian Pilcher <[email protected]> wrote: > Bill WIlson wrote: > > 2.2.9 doesn't use libsensors and uses sysfs only, so unless there is a patched > > 2.2.9 I'm not aware of, there must be something else going on. What's > > indicating that 2.2.9 is using libsensors? > > [pilcher@home ~]$ ldd /usr/bin/gkrellm > ... > libsensors.so.3 => /usr/lib/libsensors.so.3 (0x4f3db000) > ... > > Am I misinterpreting this? Ah, it has been patched! > [pilcher@home ~]$ gkrellm -d 0x80 > --- GKrellM 2.2.9 --- > hddtemp_daemon_read: can't connect to 127.0.0.1:7634. > libsensors error determining type for: via686a@6000/2.0V > libsensors error determining type for: via686a@6000/2.5V > At first, I thought that the "2.0V", "2.5V", etc., were coming from my > sensors.conf: > > chip "via686a-*" > > # These are the labels that the VP6 BIOS uses > > label "2.0V" "Vcore" # in0 > label "2.5V" "Vtt" # in1 - always around 1.6V, despite > the name > label "3.3V" "3.3V" # in2 > label "5.0V" "5V" # in3 > label "12V" "12V" # in4 [,,,] > Google found the patch that's been applied to add libsensors support to > 2.2.9. Here is the portion that's causing the error: Yeah, those labels are definitely not handled. If you look in the sysfs directory what are the names you find there for voltages. I'd like to be sure whether those names are the "in0" or "2.0V" types. The patched debug output doesn't tell you, but try looking for sensor file names in /sys/class/hwmon/hwmon0/device/. You may have only a hwmon0, or there may be a hwmon1 also. That patch is the one that was sent to me for libsensors support, but I don't think it was quite ready for general use because it cuts out the gkrellm sysfs code and it does not try to migrate the config. In 2.2.10 I fixed both of those issues and added the switch to allow running from either interface. In the patched 2.2.9 you have there is no way to get it to switch to reading from sysfs. But then that won't matter either if the sysfs names are of the "2.0V" type, and if that's the case, I would like to see a listing of all the names in the directory. Bill _______________________________________________ Gkrellm mailing list [email protected] http://lists.jutley.org/cgi-bin/mailman/listinfo/gkrellm