Temperature monitor - how hard to do?
 

OK - rig per sig with ASUS A7V8X-X mobo and I know I can read CPU and CASE temp because I do so in XP.

How hard for a n00b is this to do in SuSE (or any) Linux? I did a forum search and it seems beyonf n00b realms, need to put in place something (lmsensors?) to enable a sensors command - and if I can do that I can configure "gkrellm" maybe (whatever that is!)...

My question is - however much I might WANT to have this I probably do not NEED it so long as system stays stable - so in your opinions where in my learning curve would this comfortably sit?

I read temperature using the ACPI interface ...

gkrellm has a plugin for that as as well.


Cheers,
Tink

cheers
 

OK thanks - so that adds another complication (IE it is another way to "skin the cat") - but just a quick Google shows me this will mean a recompiled kernel, yes?

I immediately feel myself stepping away from n00bness if I go there.... that starts to mean that if I screw up my OS gets flakey, right?

Does not quite answer my question - plus I do realise Linux users think nothing of modding their kernel - I used Litestep with XP so I have some idea where things COULD be headed for me.

Now here - for temps - I want to keep my focus, JUST resolve that issue, and (If readily amenable) do so without touching the kernel. Possible or no? Hard or easy? This is the info I seek I guess...

What's your version of SuSE? It may well have acpi
compiled into the kernel already, and it only uses
apm because the daemon gets started first ...

What happens if you
Cheers,
Tink

SuSE is 9.1

and I get this:-

"paul@linux:~> skill -9 apmd
paul@linux:~> acpid
bash: acpid: command not found"

although I have found some power management options under system tools for things like closing lid of laptop (this is desktop though, using max sys power settings)

You may want to make sure you specify the full path to acpid. On my Vine box, acpid is under /usr/sbin. I get the same error if I simply type "acpid" like you do 'cause /usr/sbin is not part of my $PATH. I'd have to type "/usr/sbin/acpid" instead.

Try again as root ...

If that doesn't quite fix the problem try a
`locate acpid | grep bin`
Or, as daihard suggested, try a fully qualified path :)


Cheers,
Tink

tried both - locate = not found
grep = terminal window hangs (well, I waited a very long time, knowing the origins of GREP THIS etc I had some idea what might be going on there :)

thanks for trying though, I'll try the full path if I ever work out what it is!

I've been wanting to get temp monitoring working for some time now as well. I just recently found that my CPU heatsink was COMPLETELY covered with dust, and I had been overheating since the fan wasn't getting any air through the dust to cool it down, causing repeated system hangs that I couldn't diagnow for the longest time. I know my MB supports temp sensing as I can check the temp in the BIOS.

I just did the command suggested above, and here's what I got:

acpid: Can't open /proc/acpi/event: No such file or directory

So, I look and there is no acpi directory in /proc. Strangely though, when I tried to create this directory (after opening write perms for proc) it gives me

mkdir: cannot create directory 'acpi': No such file or directory

Um, huh? I'm root for pete's sake!!

So, I'm jumping on to this thread to see if I can get this working too...

Any ideas?