Re: no sensors detected in gkrellm

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sun, 2006-03-05 at 14:02 +0000, hicham wrote:
> On 3/5/06, Alessandro Brezzi <alessandro.brezzi@xxxxxxxxx> wrote:
> > 2006/3/5, hicham <hichamlinux@xxxxxxxxx>:
> >
> > > Hello
> > > I've went thru archives on getting gkrellm displayin cpu temp., Fan speed
> > ...
> > > I've used " sensors-detect" to get lm-sensors running, but it doesn't
> > > seem to be enough to get gkrellm sensors works
> >
> >
> >  do you reboot after sensors-detect?
> yes I did
> here is the  sensors-detect summary output :
> #########################################################################
> Now follows a summary of the probes I have just done.
>  Just press ENTER to continue:
> 
> Driver `to-be-written' (should be inserted):
>   Detects correctly:
>   * ISA bus address 0x0290 (Busdriver `i2c-isa')
>     Chip `Winbond W83627EHF Super IO Sensors' (confidence: 9)
> 
> 
>  I will now generate the commands needed to load the I2C modules.
>  Sometimes, a chip is available both through the ISA bus and an I2C bus.
>  ISA bus access is faster, but you need to load an additional driver module
>  for it. If you have the choice, do you want to use the ISA bus or the
>  I2C/SMBus (ISA/smbus)? ISA
> 
> To make the sensors modules behave correctly, add these lines to
> /etc/modprobe.conf:
> 
> #----cut here----
> # I2C module options
> alias char-major-89 i2c-dev
> #----cut here----
> --------------------------------------------------> " Those I've added
> in  /etc/modprobe.conf "
> 
> To load everything that is needed, add this to some /etc/rc* file:
> 
> #----cut here----
> # I2C adapter drivers
> modprobe i2c-isa
> # I2C chip drivers
> # no driver for Winbond W83627EHF Super IO Sensors yet
> # sleep 2 # optional
> /usr/bin/sensors -s # recommended
> #----cut here----
> --------------> " I don't know where to put those above lines which
> /etc/rc*  ?"

This is not usually needed, see below.  

However, if you wish they can be put in at the end
of /etc/rc.d/rc.local.

> 
> WARNING! If you have some things built into your kernel, the list above
> will contain too many modules. Skip the appropriate ones! You really should
> try these commands right now to make sure everything is working properly.
> Monitoring programs won't work until it's done.
> 
This is suggesting that you manually try doing the listed commands so
the modules get loaded/tested for loading before you make changes to
your files.

> Do you want to generate /etc/sysconfig/lm_sensors? (YES/no): YES
> Copy prog/init/lm_sensors.init to /etc/rc.d/init.d/lm_sensors
> for initialization at boot time.
> ##########################################################################
> 

If the lines were written to /etc/sysconfig/lm_sensors AND lm_sensors is
running as a service (IIRC that is defaulted on by FC4) then the modules
listed should already be running.

Try lsmod to see if the modules listed above are loaded, and also verify
that lm_sensors is running.

Note:  The modules must be loaded before sensors can use them.  If you
A. are not running lm_sensors or 
B. have not put the lines in /etc/rc.d/rc.local or 
C. have not manually run the listed commands to load the modules 
then sensors will not have anything to communicate with/report from.


[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux