Re: Use of sensors

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

 



If you're reunning Fedora you should put those on
modprobe.conf and not module.conf, you can check what
is loaded with lsmod.

Not sure what the VID is, maybe some sort of VIDeo
Memory information ... not sure though...

I think after you edit your  modprobe.conf you HAVE TO
reboot, unless you run the modprobe's.

--- Mike McCarty <mike.mccarty@xxxxxxxxxxxxx>
escribió:

> Igor Guarisma wrote:
> 
> >Did you run sensors-detect??
> >  
> >
> I just did, and created an /etc/modules.conf with
> just the lines
> below in it.
> 
> Here's the last part of the output:
> 
> ===============================================
> 
> To make the sensors modules behave correctly, add
> these lines to
> /etc/modules.conf:
>                                                     
>                            
> 
> #----cut here----
> # I2C module options
> alias char-major-89 i2c-dev
> #----cut here----

This ones in /etc/modprobe.conf

>                                                     
>                            
> 
> To load everything that is needed, add this to some
> /etc/rc* file:
>                                                     
>                            
> 
> #----cut here----
> # I2C adapter drivers
> modprobe i2c-i801
> modprobe i2c-isa
> # I2C chip drivers
> modprobe eeprom
> modprobe w83627hf
> # sleep 2 # optional
> /usr/bin/sensors -s # recommended
> #----cut here----

This ones on /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.
> ====================================================
> 
> How can I tell which are built in? And which file
> should I put those
> commands into?
> 
> As root, I ran the programs listed above, and now
> sensors outputs
> 
> ===============================================
> 
> $ sensors
> w83627thf-isa-0290
> Adapter: ISA adapter
> VCore:     +1.48 V  (min =  +1.93 V, max =  +1.93 V)
> +12V:     +12.59 V  (min = +10.82 V, max = +13.19 V)
> +3.3V:     +3.04 V  (min =  +3.14 V, max =  +3.47 V)
> +5V:       +4.93 V  (min =  +4.75 V, max =  +5.25 V)
> -12V:     -14.91 V  (min = -10.80 V, max = -13.18 V)
> V5SB:      +4.97 V  (min =  +4.76 V, max =  +5.24 V)
> VBat:      +2.30 V  (min =  +2.40 V, max =  +3.60 V)
> fan1:     3054 RPM  (min =    0 RPM, div = 2)
> CPU Fan:     0 RPM  (min =    0 RPM, div = 2)
> fan3:        0 RPM  (min =    0 RPM, div = 8)
> M/B Temp:    +59°C  (high =   +63°C, hyst =   +55°C)
>   sensor = 
> PII/Celeron diode
> CPU Temp:  +33.5°C  (high =  +120°C, hyst =  +115°C)
>   sensor = thermistor
> temp3:     +21.0°C  (high =  +120°C, hyst =  +115°C)
>   sensor = thermistor
> ERROR: Can't get VID data!
> alarms:
> beep_enable:
>           Sound alarm disabled
>  
> eeprom-i2c-0-50
> Adapter: SMBus I801 adapter at 0500
> Memory type:            DDR SDRAM DIMM
> Memory size (MB):       256
> 
>
=====================================================
> 
> What is the error related to VID data?

I have no idea, maybe some video ram info.

> >Or restarted lm_sensors??
> >  
> >
> I haven't done that, but it seems that I'm getting
> some info now.
> 
> Thanks.
> 
> Mike

No problem

-----

Mazin...go!!!
Mazinkaiza...go!!!
Visit http://mazingo.cjb.net  for episodes ONLINE!!!
Visit #mechaworld @ irc.mircx.com to talk and download!!!
irc://irc.mircx.com/MechaWorld

__________________________________________________
Correo Yahoo!
Espacio para todos tus mensajes, antivirus y antispam ¡gratis! 
Regístrate ya - http://correo.espanol.yahoo.com/ 


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

  Powered by Linux