Hi Sunil, > A related question: gkrellm2 (2.2.9) refuses to see my sensors as reported > by abit driver, but its able to see bogus sensors reported by w83627hf if I > modprobe it. sensors and ksensors, both see the values correctly. > > Why would gkrellm not see them? Is there a configuration setting that > gkrellm reads which works for w83627hf but not for abituguru. gkrellm accesses /sys directly instead of using libsensors. The consequence of this unfortunate choice is that the results you get with gkrellm can differ from what all other hardware monitoring frontends report, and when support for new chips is added gkrellm doesn't benefit from the libsensors update and must implement support on its own. So you better complain to the gkrellm folks, there's nothing we can do about it. -- Jean Delvare
