Obviously your l337n355 commands your state of mind and being that, if you are in fact a male, you cant' admit to your mistakes like a man, like I can. Since you have totally authority over this thread, I leave it to you to help the OP. You seemed to have made further progress with helping her situation out than I have.

"Hmmm... Did someone make you chief post reviewer and value assessor?" No, in fact, you're the one with the mighty l337 intellect who corrects peoples mistakes and manipulates people's words.

Have fun. And don't let the hippo out the crate too often...it makes you misconstruct your own words to cover yourself.

I'm catching up here and from what I can deduce, I am now thinking along the lines of agreeing with the suggestions of getting an updated kernel and recompiling. If that doesn't solve the issue, I'll just see what's up at the lm_sensors site and see if they have it listed as a possibility or not. If there's no intention around to create a driver, maybe I can find a helpful hacker to help me write one (maybe even learn to code a driver myself some day) and see where it goes from there.

For now, I'm putting this on my list of "unresolved issues" to get back to after I finish with the easier fixes and installations I have yet to do.

Thanks to all for your suggestions.

lm_sensors has a beta driver for the W83637HF chip since 04-04-2004. It's in lm_sensors version 2.8.5 and (I assume) later versions.

The lm_sensors information is here (page down to the "New and Requested Sensor Chip Drivers" section), and the driver information is here

Try updating your lm_sensors + dependencies before updating your kernel. When I installed 10.0 OE, the lm_sensors from the official repository wouldn't detect my W83637HF driver, so I downloaded and installed the lm_sensors packages from the cooker repository and now it works fine. Just a thought.

Estatik and Opjose: take your arguments off-line. Feel free to disagree with each other, but do so in a non-confrontational manner. You are not helping anyone by sniping at each other.

tour - thanks for the info. On your advice, I went and uninstalled the lm_sensors and gkrellm I had already and then downloaded, compiled and installed the latest lm_sensors and gkrellm. Still gkrellm is saying 'no sensors detected' in the Builtins/Sensors/info tab.

Typing 'sensors' at the root command line gives me this:

eeprom-i2c-0-51
Adapter: SMBus I801 adapter at 0500
Memory type: DDR SDRAM DIMM
Memory size (MB): 256

eeprom-i2c-0-50
Adapter: SMBus I801 adapter at 0500
Memory type: DDR SDRAM DIMM
Memory size (MB): 256

I'm now at a loss. I did answer "YES" to all the questions when doing sensors-detect and copy/pasted the info in the right files (first set to /etc/modules.conf, second set to /etc/rc.d/rc.modules)

I am not sure what to try next.

Maybe mgd's suggestion of updating your kernel will help. IIRC, when I initially installed 10.0 OE, I updated everything at once, including the kernel via urpmi. I guess it wouldn't hurt.

Thing is, I did update my packages using the Software Media Manager to first find a mirror. I had to try several before I found one that would update. About 190+ packages had been updated. Oddly, KDE is still 3.2 though. I don't know where to get a better list of update sites to use. I am not sure how current they are or which one is the best to use. Help on that would be appreciated as well.

Under Mandrake 9.2, I got lm_sensors working and displaying temperatures and fan speed in gkrellm, in about twenty minutes! Now with 10.1, unable to get them to work and reading all this stuff, I'm just totally discouraged, at least for
the time being. Seems strange that something that worked so easily becomes next to impossible in an "upgrade."

10.0 can be said to be a "done" release while 10.1 is still in Release Candidate form.

And yeah there are a number of things that appear to be problematic in 10.1 CE (or R.C. for me!) that were not so in 10.0.

I could hardly get ANYTHING to work in 10. That's why I went back to 9.2, which I had just the way I wanted it, waited till 10.1 thinking it would be better. Some things are, but it's really frustrating to spend sometimes hours getting things to work right, only to have all that work be for nothing next time "improvements" come around. Can't get the sensors to work, can't get standby battery support monitoring to work, had to put my mouse back in PS2 slot... Well, I won't whine anymore here as it's really off-topic, but the sensors issue happened to be one I was working on (to no good) when I read this thread.

I realise this is an old post now, but I had exactly the same problem (more or less). I was running an Abit IC7-G board on Mandrake 10.0, and trying to get Gkrellm running by installin lm_sensors properly. It came up with exactly the same messages:

So I just did modprobe w83781d instead and it was fine - no error message. When I ran sensors, it gave me all the output, whereas before it just gave the eeproms, just like FuzzieDice. I then amended my /etc/sysconfig/lm_sensors file so that the line for w83627hf was replaced with w83781d.

Since last posting in this thread, I successfully installed Mdk 10.1 Official, and after much toil got lm_sensors working, BUT with bogus voltage values being reported. The temperatures and fan speed look fine, just the voltages are all wrong (min larger than max!) and give alarms every couple of SECONDS. So I had to disable lm_sensors.

As it stands now, the people at lm_sensors are working on my trouble ticket and just today I've sent oodles of information to them. So far they are baffled but I imagine they'll figure out before long what's wrong.

We do know that it appears the /etc/sensors.conf file has NO effect on the sensors in my setup. That's the baffling part.

Normally what you are seeing indicates that the module is using the wrong calculation algorhythm for a particular sensor.

This can actually be modified (it's in the docs) but is REALLY tedious to do.

Yeah, it was telling me that my system temperature was 250° centigrade. All the other temps too were basically 10x too high. I just modeified the factor settings to '0.1' and they look fine now.