[SLE] GKrellm and lm_sensors
Well just do that. Put the out put into /etc/rc.d/boot.local. In my case it says: # I2C adapter drivers modprobe i2c-isa # I2C chipdrivers modprobe w83781d In your case it may be something totally different. Check than if you have the right module option in /etc/modules.conf Whenever I install gkrellm after a new installation I reboot. After reboot, gkrellm will give you the display. Now you right click on gkrellm and finalize the display. Put cpu in front of the cpu temp. and proc (I think it was) in front of the system temp. Same for the speed of the fans. You can now refine the whole setup with max and minimum for all values. JP>I would like to use GKrellM to display the mobo and cpu JP>temperatures, but I <snip> JP>working? The output from sensors-detect helpfully says JP>"put this in some config files"... -- "640K ought to be enough for anybody." - Bill Gates, 1981 NTReader v0.36w(P)/Beta (Registered) in conjunction with Net-Tamer
In a previous message, Constant Brouerius van Nidek wrote:
Put the output [of sensors-detect] into /etc/rc.d/boot.local. [snip] Check than if you have the right module option in /etc/modules.conf
That was what I needed, thanks! The sensors-detect gives the less-than-useful path "some /etc/rc* file" :-) The only lingering problem now is that, during boot, modprobe complains that "modules.conf is more recent than /lib/modules/2.4.19-4GB/modules.dep" Is this serious? thanks, John -- John Pettigrew Headstrong Games john@headstrong-games.co.uk Fun : Strategy : Price http://www.headstrong-games.co.uk/ Board games that won't break the bank Valley of the Kings: ransack an ancient Egyptian tomb but beware of mummies!
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Le Vendredi 11 Octobre 2002 10:49, John Pettigrew a écrit :
In a previous message, Constant Brouerius van Nidek wrote:
Put the output [of sensors-detect] into /etc/rc.d/boot.local.
[snip]
Check than if you have the right module option in /etc/modules.conf
That was what I needed, thanks! The sensors-detect gives the less-than-useful path "some /etc/rc* file" :-)
The only lingering problem now is that, during boot, modprobe complains that "modules.conf is more recent than /lib/modules/2.4.19-4GB/modules.dep"
Is this serious?
It is not serious. If you want to get rid of it, just type: touche /etc/modules.conf /lib/modules/2.4.19-4GB/modules.dep - -- Thibaut Cousin E-mail : cousin@in2p3.fr Web : http://clrwww.in2p3.fr -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE90m5Lv1vqsTa1E4oRArqVAJ433io3uwYYAKTyMkaumnPhu/WKjQCggbcC qQ4beZX0nUWFxR69SXgtXkM= =JX+L -----END PGP SIGNATURE-----
* Thibaut Cousin; <cousin@in2p3.fr> on 13 Nov, 2002 wrote:
The only lingering problem now is that, during boot, modprobe complains that "modules.conf is more recent than /lib/modules/2.4.19-4GB/modules.dep"
Is this serious?
It is not serious. If you want to get rid of it, just type:
touche /etc/modules.conf /lib/modules/2.4.19-4GB/modules.dep
And why not "depmod -a" -- Togan Muftuoglu Unofficial SuSE FAQ Maintainer http://dinamizm.ath.cx
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Le Mercredi 13 Novembre 2002 16:39, Togan Muftuoglu a écrit :
* Thibaut Cousin; <cousin@in2p3.fr> on 13 Nov, 2002 wrote:
The only lingering problem now is that, during boot, modprobe complains that "modules.conf is more recent than /lib/modules/2.4.19-4GB/modules.dep"
Is this serious?
It is not serious. If you want to get rid of it, just type:
touche /etc/modules.conf /lib/modules/2.4.19-4GB/modules.dep
And why not "depmod -a"
I haven't tried this one. Sorry, I made a typo. The command is "touch", not "touche". - -- Thibaut Cousin E-mail : cousin@in2p3.fr Web : http://clrwww.in2p3.fr -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE90neqv1vqsTa1E4oRAoxRAKC/eBZ1EcMsnmRFKL16c3Egb4ZunQCcD5gu NdeXchfSeRSPdAIkj8Ih+YE= =8qkP -----END PGP SIGNATURE-----
* Thibaut Cousin; <cousin@in2p3.fr> on 13 Nov, 2002 wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Le Mercredi 13 Novembre 2002 16:39, Togan Muftuoglu a écrit :
* Thibaut Cousin; <cousin@in2p3.fr> on 13 Nov, 2002 wrote:
The only lingering problem now is that, during boot, modprobe complains that "modules.conf is more recent than /lib/modules/2.4.19-4GB/modules.dep"
Is this serious?
It is not serious. If you want to get rid of it, just type:
touche /etc/modules.conf /lib/modules/2.4.19-4GB/modules.dep
And why not "depmod -a"
I haven't tried this one. Sorry, I made a typo. The command is "touch", not "touche".
man depmod depmod - handle dependency descriptions for loadable kernel modules man touch touch - change file timestamps Looks to me for the above case depmod is a better solution yet YMMV -- Togan Muftuoglu Unofficial SuSE FAQ Maintainer http://dinamizm.ath.cx
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Le Mercredi 13 Novembre 2002 17:02, Togan Muftuoglu a écrit :
touche /etc/modules.conf /lib/modules/2.4.19-4GB/modules.dep
And why not "depmod -a"
I haven't tried this one. Sorry, I made a typo. The command is "touch", not "touche".
man depmod
depmod - handle dependency descriptions for loadable kernel modules
man touch
touch - change file timestamps
Looks to me for the above case depmod is a better solution yet YMMV
No. The problem you have is not a dependency problem. The module manager just checks that modules.conf (the configuration file) and modules.dep (the dependency file) have the same age. It can indeed happen that different ages for those files indicates a kernel change that has not been taken in account everywhere. But if all you do is changing modules.conf and not the kernel, then there is no real problem and you can ignore the warning. "Touching" the two files makes them the same age, so the warning disappears. - -- Thibaut Cousin E-mail : cousin@in2p3.fr Web : http://clrwww.in2p3.fr -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE90nnZv1vqsTa1E4oRAmuIAKDNYZk06l/GriAsXl3R0t+F69pclQCfV3Ew IH6EcKUGn4e70HM+GPCgVn4= =ECS/ -----END PGP SIGNATURE-----
On Fri, 11 Oct 2002, John Pettigrew wrote:
In a previous message, Constant Brouerius van Nidek wrote:
Put the output [of sensors-detect] into /etc/rc.d/boot.local. [snip] Check than if you have the right module option in /etc/modules.conf
That was what I needed, thanks! The sensors-detect gives the less-than-useful path "some /etc/rc* file" :-)
The only lingering problem now is that, during boot, modprobe complains that "modules.conf is more recent than /lib/modules/2.4.19-4GB/modules.dep"
Is this serious?
Usually not serious. Have you noticed that your clock is about a month behind? That might be the cause of this. Regards Ole
participants (5)
-
Constant Brouerius van Nidek -
John Pettigrew -
Ole Kofoed Hansen -
Thibaut Cousin -
Togan Muftuoglu