How are these sensors read?
Sensor chips reside on either the ISA bus, the SMBus, or both.
See the file doc/chips/SUMMARY in our package for a list.
To communicate with chips on the ISA bus, the software uses
simple I/O reads and writes.
To communicate with chips on the SMBus, the software must
use an SMBus interface device, explained below.
What is the SMBus? And the I2C bus?
The SMBus is the "System Management Bus". More specifically, it is a
2-wire, low-speed serial communication bus used for basic health monitoring
and hardware management. It is a specific implementation of the more
general I2C (pronunciation: I-squared-C) bus. In fact, both I2C devices
and SMBus devices may be connected to the same (I2C) bus.
The SMBus (or I2C bus) starts at the host controller, used for
starting transactions on the SMBus. From the host interface, the
devices communicated with are the 'slave' devices. Each slave device has a
unique 7-bit address in which the host must refer to it with.
For each supported SMBus host, there is a separate kernel module
which implements the communication protocol with the host. Some SMBus hosts
really operate on the SMBus level; these hosts can not cope with pure I2C
devices. Other hosts are in fact I2C hosts: in this case, we implement
the SMBus protocol in terms of I2C operations. But these hosts can also
talk to pure I2C devices.
by fsateler on Thu 5 Jan 2006
*Tags*: hardware, monitoring, temperature
Sometimes it is useful to know the temperature of your hardware, to prevent
it from frying. This information can easily be found, if your hardware
provides the sensors needed, and we have the necessary software.
Most computers come with temperature sensors, which can be used to prevent
your hardware from excessive heat. The most important thing to watch is, of
course, your CPU temperature. This is where lm-sensors comes in. So, lets
install it:
# apt-get install lm-sensors
Please notice that lm-sensors needs a recent version of i2c, so your kernel
must have it installed (either via a 2.6 kernel (debian's default kernel
works), or a patch to your 2.4 kernel). Once we have it installed, we need
to configure it. A tool, sensors-detect can be used, but first we must
ensure the necessary files are created under /dev. If you have a static
/dev, you must manually create them:
# cd /dev && ./MAKEDEV i2c
If you have a dynamic /dev, then you need to load the i2c-dev module (I have
only dynamic /dev systems, so I don't know if this module needs to be loaded
also on those systems).
After this, you can proceed with the configuration.
Follow the instructions, throughout the wizard. Finally, we need to load the
modules sensors-detect told us that should be loaded. In my case, it was
i2c-viapro, i2c-isa, eeprom and w83627hf.
# modprobe -a i2c-viapro i2c-isa eeprom w83627hf
After this, we should be able to read sensor information. Just run the
sample sensors program shipped with lm-sensors, and watch all your sensors!
Now, there may be problems with the output: Information given by the
hardware must be translated, and sometimes the configuration file doesn't
handle your chip nicely. Check with your CMOS hardware monitor (probably by
rebooting) that the readings are correct, and if not, modify
/etc/sensors.conf (this file is extensively self-documented).
After you are done with /etc/sensors.conf, you can proceed to install a
sensor monitor compatible with lm-sensors (eg: ksensors, xsensors,
wmtemp). Alternatively, you might want to install the sensord daemon, which
logs to syslog.
Now that we have our CPU covered, we can get worried about the next
important thing: hard drives. This is simpler to set up. Just install the
hddtemp package.
# apt-get install hddtemp
With the package installed, we can now check our drives temperature. Note
that hddtemp must be run as root.
# hddtemp /dev/hd?
/dev/hda: Maxtor 6E040L0: 40 C
/dev/hdb: ST340824A: 47 C
/dev/hdc: CREATIVE CD-RW RW8439E: S.M.A.R.T. not available
/dev/hdd: LTN526: S.M.A.R.T. not available
As you can see, both my hard drives support temperature sensors, but my two
CD drives don't. Note that hddtemp is not limited to IDE drives, it's just
that I only have these.
Also, hddtemp has the ability to run as a daemon, but the Debian
installation comes disabled by default. To enable it, we must edit
/etc/default/hddtemp, and set it to RUN_DAEMON="true" (if you want, you can
set also which hard drives to check, to speed things up a bit). Then you can
run the provided init script, and hddtemp will be running.
Running hddtemp as a daemon, has the advantage of letting regular users
check the hard drives temperature, if we have netcat (or equivalent
software) installed:
$ nc localhost 7634 ; echo
|/dev/hda|Maxtor 6E040L0|39|C||/dev/hdb|ST340824A|47|C|
Now you can install a frontend (such as sensors-applet), and watch your
hardware's temperature in real time, and maybe be alerted of too high
temperatures.
|
!! |
% sensors-detect
# sensors-detect revision 4171 (2006-09-24 03:37:01 -0700)
This program will help you determine which kernel modules you need
to load to use lm_sensors most effectively. It is generally safe
and recommended to accept the default answers to all questions,
unless you know what you're doing.
We can start with probing for (PCI) I2C or SMBus adapters.
Do you want to probe now? (YES/no):
Probing for PCI bus adapters...
Use driver `i2c-viapro' for device 0000:00:11.0: VIA Technologies VT8237 South Bridge
We will now try to load each adapter module in turn.
Module `i2c-viapro' already loaded.
We are now going to do the I2C/SMBus adapter probings. Some chips may
be double detected; we choose the one with the highest confidence
value in that case.
Next adapter: SMBus Via Pro adapter at 0400
Do you want to scan it? (YES/no/selectively):
Client found at address 0x4a
Probing for `Analog Devices ADM1034'... No
Probing for `SPD EEPROM'... Success!
(confidence 8, driver `eeprom')
Probing for `SPD EEPROM'... Success!
(confidence 8, driver `eeprom')
Some chips are also accessible through the ISA I/O ports. We have to
write to arbitrary I/O ports to probe them. This is usually safe though.
Yes, you do have ISA I/O ports even if you do not have any ISA slots!
Do you want to scan the ISA I/O ports? (YES/no):
Probing for `VIA VT8231 Integrated Sensors'... No
Probing for `AMD K8 thermal sensors'... Success!
(confidence 9, driver `k8temp')
Some Super I/O chips may also contain sensors. We have to write to
standard I/O ports to probe them. This is usually safe.
Do you want to scan for Super I/O sensors? (YES/no):
Probing for Super-I/O at 0x2e/0x2f
Trying family `VIA/Winbond/Fintek'... Yes
Found `Winbond W83697HF Super IO Sensors' Success!
(address 0x290, driver `w83627hf')
Now follows a summary of the probes I have just done.
Just press ENTER to continue:
Driver `eeprom' (should be inserted):
Detects correctly:
* Bus `SMBus Via Pro adapter at 0400'
Busdriver `i2c-viapro', I2C address 0x50
Chip `SPD EEPROM' (confidence: 8)
* Bus `SMBus Via Pro adapter at 0400'
Busdriver `i2c-viapro', I2C address 0x51
Chip `SPD EEPROM' (confidence: 8)
EEPROMs are *NOT* sensors! They are data storage chips commonly
found on memory modules (SPD), in monitors (EDID), or in some
laptops, for example.
Driver `k8temp' (should be inserted):
Detects correctly:
* ISA bus, undetermined address (Busdriver `i2c-isa')
Chip `AMD K8 thermal sensors' (confidence: 9)
Driver `w83627hf' (should be inserted):
Detects correctly:
* ISA bus address 0x0290 (Busdriver `i2c-isa')
Chip `Winbond W83697HF Super IO Sensors' (confidence: 9)
I will now generate the commands needed to load the required modules.
Just press ENTER to continue:
To make the sensors modules behave correctly, add these lines to
/etc/modules:
#----cut here----
# I2C adapter drivers
i2c-viapro
# Chip drivers
eeprom
k8temp
w83627hf
#----cut here----
Do you want to add these lines to /etc/modules automatically? (yes/NO)yes
% modprobe i2c-viapro eeprom w83627hf
% sensors
k8temp-pci-00c3
Adapter: PCI adapter
Core0 Temp:
+51 C
documented on: 2007.08.01
by chris on Fri 26 Aug 2005
*Tags*: monitoring, munin
From the package description: Munin is a highly flexible and powerful
solution used to create graphs of virtually everything imaginable throughout
your network, while still maintaining a rattling ease of installation and
configuration.
Getting munin
Munin is in the Debian archive in two parts - munin - the part that creates
the monitoring graphs (you can think of this as the munin server), and
munin-node - the munin client program.
So - if monitoring one machine installation should be a simple:
apt-get install munin munin-node
Configuration
Configuration is conducted via configuration files inside the directory
/etc/munin:
munin.conf
The configuration of the grapher/collector.
The default configuration is set up to monitor the local machine. Things
that can be set here (defaults shown below)
# The data storage area
dbdir /var/lib/munin
# The place to put the generated web pages
htmldir /var/www/munin
# The log files
logdir /var/log/munin
# Temporary run files (pid file etc)
rundir /var/run/munin
# Where to look for the HTML templates
tmpldir /etc/munin/templates
You can also setup hosts to check here - the default is for localhost:
[localhost.localdomain]
address 127.0.0.1
use_node_name yes
Examples are given in this file for adding other hosts.
munin-node.conf
Setup of the node which server addresses can connect. For monitoring just
your local machine the default is fine.
plugin-conf.d/munin-node
Configuration of the plugins for this node. The syntax is simple:
[pluginname]
param val
param val
You can set user, group, etc for each plugin.
Allowed parameters are described at the top of the file.
plugins
A directory in which each file is a symlink to a real plugin in
/usr/share/munin/plugins.
Any plugin linked in here will be checked for and displayed in the resulting
web pages.
Add the plugins you want (e.g. if running exim4 then I'd add exim_mailqueue
and exim_mailstats).
You'll need to set user/group rights in the munin-node conf file.
Most plugins can be run from the command line with the autoconf param to
check if they can run - e.g.
./exim_mailstats autoconf yes
Running munin
Munin sets up a cron job via the file /etc/cron.d/munin which will run
/usr/bin/munin-cron.
Keeping an eye on these graphs will help you to keep your server running
healthily - and can give advance warning of problems to come.
Re: Monitoring systems with munin
here is the complete and step by step guide for munin configuration in debian
Re: Monitoring systems with munin
Two things that I find useful
munin-node-configure --suggest
which will show you what you could be running and if munin reckons it would
work
munin-node-configure --suggest --shell
which will generate a list of ln commands that can be run in a shell to
install the services that munin said "suggest: yes" to in the above output
documented on: 27 Mar 2006, chris
Re: Monitoring systems with munin
Personally, I've been using Cacti for some time now. I'd say it's prettier
than Munin (which is important when the graphs are being shown to
customers), and the built-in user authentication system makes it easy to
gives access to specific graphs or collections of graphs.
I'd definitely recommend it.
Re: Monitoring systems with munin
Yes - cacti does look nice. Seems a little heavier than munin though.
I think that for my use (two small PCs that serve websites for small groups
of people) that munin will probably do. If I was going to monitor larger
networks with SNMP enabled hardware etc - then cacti would probably be
better.
documented on: 27 Aug 2005, chris
Re: Monitoring systems with munin
Cacti can read the RRDtool files created by Munin. I did this with version
0.8.4 of cacti, so please take this with a grain of salt for newer versions.
-
Create a data template. One data source item per Munin RRD file. E.g. for
a CPU graph, define cpu_idle, cpu_nice, cpu_system and cpu_user. Enter
the values as used by Munin, e.g. step is 300.
-
Create a host template and associate the data template.
-
Create a graph template. For each value (idle, nice, system, user) define
an AREA and three GRPINTs, LAST, AVERAGE, and MAX.
-
Define data sources. Enter the correct Data Source Pathes to the Munin
RRD files. Again, do this for each value, idle, nice, system, user.
-
Define a graph using the data sources and the graph template.
I wrote this while inspecting the unused but still existing Cacti test
installation. So this probably won't work. Please post your recipe when you
got thi working.
documented on: 24 Aug 2006, Lupe
Re: adding new hosts to munin
OK - here's a sample 2 machine config (it's an anonymized copy of what I
have running):
On the server /etc/munin.conf contains
dbdir /var/lib/munin
htmldir /var/www/munin
logdir /var/log/munin
rundir /var/run/munin
tmpldir /etc/munin/templates
[host1.domain.tld]
address xxx.xxx.xxx.xxx
[host2.domain.tld]
address yyy.yyy.yyy.yyy
And the munin-node.conf contains
log_level 4
log_file /var/log/munin/munin-node.log
port 4949
pid_file /var/run/munin/munin-node.pid
background 1
setseid 1
host *
user root
group root
setsid yes
ignore_file ~$
ignore_file \.bak$
ignore_file %$
ignore_file \.dpkg-(tmp|new|old|dist)$
ignore_file \.rpm(save|new)$
host_name host1.domain.tld
allow ^127\.0\.0\.1$
allow ^xxx\.xxx\.xxx\.xxx$
On the second machine (client only) munin-node.conf contains
log_level 4
log_file /var/log/munin/munin-node.log
port 4949
pid_file /var/run/munin/munin-node.pid
background 1
setseid 1
host *
user root
group root
setsid yes
ignore_file ~$
ignore_file \.bak$
ignore_file %$
ignore_file \.dpkg-(tmp|new|old|dist)$
ignore_file \.rpm(save|new)$
host_name host2.domain.tld
allow ^127\.0\.0\.1$
allow ^xxx\.xxx\.xxx\.xxx$
allow ^yyy\.yyy\.yyy\.yyy$
If you're not [getting graph] I'd check the /var/log/munin files on both
server and client.
documented on: 24 Jan 2006, chris
munin: alerts?
Well, I managed to install munin on a server and one client machine — it
works quite nicely it seems.
This required me to do three things:
-
apt-get install smartmontool
which is apparently needed by munin's hddtemp_smartctl plugin ;
-
and ln -s /usr/share/munin/plugins/hddtemp_smartctl /etc/munin/plugins/hddtemp_smartctl
-
which 'activates' the plugin ;
-
and /etc/init.d/munin-node restart to apply these changes.
Now that this is done, I have temperature graphs for all my sensor-enabled
hard drives, which is pretty great. But ultimately staring at a graph all
day isn't all that efficient, so what I'd like to do now is have munin send
me an e-mail when the temperature of any drive hits, say, 42^C.
Unfortunately the official documentation pages are kinda incomplete at the
moment, so I'm not sure what to do.. there seems to be a page specifically
about sending alerts, but it's not too clear..
Am I supposed to just dive in and start modifying the actual
/etc/munin/plugins/hddtemp_smartctl plugin file (it's Perl) to stick in the
warning trigger values?
Or is there a cleaner, more global way of doing this somewhere?
Can anyone here provide an example?
munin: alerts?
> Many munin plugins have thresholds configured, and munin can send alerts to
> Nagios. See http://munin.projects.linpro.no/wiki/HowToContact[]
Yes, thank you, I am aware of this, as I have also visited that
page. Installing Nagios is not an option for now — I'm trying to keep the
root partition as small as possible for reasons I won't go into here — but
I did try to follow the non-Nagios instructions at the bottom of the page,
specifically this snippet:
contact.email.command mail -s "Munin-notification for ${var:group} :: ${var:host}" your@email.address.here
The problem is, I'm still not getting any e-mail alerts even though two of
my hard drives have reached 'critical' capacity levels, and my
Munin-generated pages recognize this fact by marking said values with an
orange background.
Does anyone have a clue as to what it is that I am missing?
(and while I do appreciate all advice from d-a users, I'd like to stress
that Nagios is not an answer in my opinion — given the fact that Munin
should already be able to send a simple mail by itself, I think installing
Nagios only for this purpose would be like installing Windows 98 for its
screensavers..)
munin: alerts?
I tend to use munin for monitoring of history/trends over time and nagios
for current status/warning.
documented on: 24 Jan 2006, chris
Newsgroups: comp.os.linux.hardware
Date: 1999/08/25
> Is there any way to monitor CPU temperature from within Linux? I have
> a Gigabyte 6bxd motherboard and the bios supports CPU temperature
> monitoring, but as far as I know there is no method for checking the
> cpu temperature from bios once the OS is loaded up. Any clues? Is
> there anything in /proc that I can check?
<snip>
Check out http://www.netroedge.com/~lm78/ which provides a kernel modules
(very easy to compile) which will create a /proc entry to read the
temperature. Your can also check out www.freshmeat.net for "temperature
monitors" or "lm78" programs.
Newsgroups: comp.os.linux.hardware
Date: 1999/11/17
>I've seen postings requesting/suggesting X-utilities to monitor
>the core temperature of the CPU.
>Are there any command-line programs that can do this?
>I wish run this on my workstation at school so that it can mail-out
>a warning message to my home address in case the CPU temperature
>goes above a certain threshold.
Actually, there is a shell script that does just that… It comes with the
lm_sensors package , under the progs/daemon directory. If there are any
alarms, it will send an email to the specified person.
Unfortunately, the temp3 line on my Asus P2B says the following:
temp3: +208.5c (limit = 80.0 C, hysteresis = +75.0 C).
(Obviously incorrect). The other two temp readings look accurate, and can
be confirmed by and looking that the temp in the BIOS …
So count me out for the alarm notification (untill this gets resolved,
anyway) <G>.
Newsgroups: uk.comp.os.linux
Date: 2002-03-31 12:24:34 PST
> > I've looked on freshmeat and there seems to be two ways to monitor the
> > cpu temp. Either gkrellm, or putting a patch into the kernel to add
> > cputemp to /proc.
> >
> > I have the debian testing version of gkrellm but there seems to be no
> > way to show cpu temperature... Do I have to patch the kernel in any
> > case? What's the best way to monitor the cpu temperature?
>
> I think you'd need ACPI support in the kernel (General Setup), enable ACPI
> support, ACPI Bus manager and Processor. Though whether this gives you the
> temperature or not would depend on what the ACPI in your BIOS supports.
>
> BTW, I've never used ACPI for monitoring, just to turn the box off when I
> shut down.
I don't think the processor module is responsible for temperature
monitoring, it seems to be for idel states. There's a "Thermal" module,
which I've tried compiling, but it just says "No such device" when I try
to modprobe it.
The only monitor front-end I've found which mentions a kernel patch
(apart from some PPC stuff which I don't think uses ACPI) is heatload,
but I can't find the patch itself anywhere.
Generally lm_sensors is what you need, but that doesn't seem to be
compatible with my motherboard, which is a VIA 82wotsit86B, while
lm_sensors seems only to support the A, and misdetetcs it or something.
cpu temperature monitoring
> > Ok, I just compiled i2c support into the kernel and rebooted, yes,
> > *rebooted*. I also did an apt-get install lm-sensors.
> > Now I get
> > paul@debian:~$ sensors
> > No sensors found!
>
> Have you run sensors-detect once?
>
> Have you put the appropriate lines into modules.conf and a startup script?
>
> Have you set it up to do a a "sensors -s" on every reboot?
Thanks for that. I feel somewhat frustrated though - why didn't
debconf tell me all that when I installed lm-sensors? I feel like
what should be a simple task is neccesitating an awful lot of hassle.
What's more, the installation files for the source of lm-sensors, as
far as I can see, mention none of those things. I now see that I was
supposed to read, several times, the thousand line FAQ. I think that
critical installation instructions should be in the installation
instructions, but that could just be me having a grumpy day…
Newsgroups: comp.os.linux.misc
Date: 16 Feb 2003 08:20:09 -0800
> Hi, I've got a new server and I was trying to configure the kernel
> correctly so that I could read information using lmsenors.
>
> I compiled in all of the I2C options, and now I have a
> /proc/sys/dev/sensors/chips file. However, the file is empty and the
> "sensors" command says "No sensors found!".
>
> I am sure that there is a sensor because the BIOS properly reports CPU temp
> and there's also an LED on the front that reports overheating. Is there
> some way to access that sensor with software? Am I missing compiling
> something in the linux kernel (I compiled in all the I2C options in
> 2.4.20)?
# cd /usr/src/linux
# make menuconfig
In the kernel configuration, go to Character Devices -> Hardware
sensors support. As you select [*] Hardware Sensors Support, you
should see a list of supported sensors expand. Did you select your
sensor module from that list?
If you haven't already, compile the ones that sound interesting as
modules. Then you can do "insmod" on each one that sounds interesting,
then re-check /proc/sys/dev/sensors/chips (or run "sensors" from the
lm_sensors package) to see if it worked.
You will also need some other i2c modules loaded. On my system, I do
the following:
modprobe i2c-core
modprobe i2c-isa
modprobe i2c-proc
modprobe w83781d # or whatever sensor you use.
Or insmod instead of modprobe, since I haven't specified any of this
in my /etc/modules.conf. The i2c-isa module is needed if your sensor
chip is on the ISA bus, as mine is.
I did add the following line to my /etc/modules.conf, but I'm not sure
why because it is never loaded:
alias char-major-89 i2c-dev
#############################
Or if that doesn't work you can try the script from the lm_Sensors
package called "sensors-detect". Run this and it should automatically
try each module to see if it works.
Newsgroups: alt.os.linux.suse
Date: 2003-02-03 09:21:18 PST
I have installed both the above packages from my SuSE CDs. I hear that
GKrellm can show the output from lm_sensors - but how do I do that?
a plugin, that should enable this, but when I try to compile it, I get all
sorts of errormessages…
GKrellm and lm_sensors ?
Make sure sensors is setup correctly, as root or su type sensors-detect in
a terminal and follow the prompts. Copy and paste the detected sensor to
/etc/modules.conf and I installed the modprobe commands to
/etc/init.d/boot.local
If all goes well at a terminal as a normal user or root type sensors. Output
similar to the following will be displayed:
anc@linux:~> sensors
w83782d-isa-0290
Adapter: ISA adapter
Algorithm: ISA algorithm
VCore 1: +1.66 V (min = +4.08 V, max = +4.08 V)
VCore 2: +1.48 V (min = +4.08 V, max = +4.08 V)
+3.3V: +3.48 V (min = +2.97 V, max = +3.63 V)
+5V: +5.04 V (min = +4.50 V, max = +5.48 V)
+12V: +12.46 V (min = +10.79 V, max = +13.11 V)
-12V: -11.88 V (min = -13.21 V, max = -10.90 V)
-5V: -5.20 V (min = -5.51 V, max = -4.51 V)
V5SB: +4.97 V (min = +4.50 V, max = +5.48 V)
VBat: +2.51 V (min = +2.70 V, max = +3.29 V)
fan1: 4891 RPM (min = 3000 RPM, div = 2)
fan2: 0 RPM (min = 3000 RPM, div = 2)
fan3: 0 RPM (min = 3000 RPM, div = 2)
temp1: +28^C (limit = +60^C) sensor =
thermistor
temp2: +30.5^C (limit = +60^C, hysteresis = +50^C) sensor =
PII/Celeron diode
temp3: +29.0^C (limit = +60^C, hysteresis = +50^C) sensor =
thermistor
vid: +1.650 V
alarms: Chassis intrusion detection ALARM
beep_enable:
Sound alarm disabled
eeprom-i2c-0-50
Adapter: SMBus PIIX4 adapter at 5000
Algorithm: Non-I2C SMBus adapter
Memory type: SDRAM DIMM SPD
SDRAM Size (MB): 128
eeprom-i2c-0-51
Adapter: SMBus PIIX4 adapter at 5000
Algorithm: Non-I2C SMBus adapter
Memory type: SDRAM DIMM SPD
SDRAM Size (MB): 128
dependent of course on your motherboard. Mine is Abit BE6-II with
winbond. Install Gkrellm from the Suse CD's. It will work under kDe or any
other GUI. Right click Gkrellm go to configuration, builtins, sensors.
You should find at least setup, voltages and info menues. Toggle the buttons
for CPU voltage to be displayed and apply. The fields with a blank label,
need a name before they can be displayed. On my gktrellm temp 1 was blank,
I called it CPU temp and hit apply, similarly for other sensors. All in all
a nice little application. Hope that helps.
GKrellm and lm_sensors ?
> #----cut here----
> # I2C adapter drivers
> modprobe i2c-isa
> # I2C chip drivers
> modprobe sis5595
> #----cut here----
>
> To make the sensors modules behave correctly, add these lines to either
> /etc/modules.conf or /etc/conf.modules:
>
> #----cut here----
> # I2C module options
> alias char-major-89 i2c-dev
> #----cut here----
>
> Do you want to generate /etc/sysconfig/lm_sensors? (YES/no):
> Copy /usr/share/doc/packages/sensors/prog/init/lm_sensors.init
> to /etc/init.d/lm_sensors for initialization at boot time.
Ok Stig, I realise now that you must still be on the original kernel with
8.0 so the sensors module is not in by default.
You need to put the first part in /etc/init.r/boot.local :
# I2C adapter drivers
modprobe i2c-isa
# I2C chip drivers
modprobe sis5595
and the last can be pit at the bottom of /etc/modules.conf :
# I2C module options
alias char-major-89 i2c-dev
I take it you did say yes to generate the config file at the end.
and that should then be it.
after the next boot it will load them automatically
or you could try by hand after you have added the line to modules.conf do a
(as root)
modprobe i2c-isa
modprobe sis5595
and see if you can get anything from sensors.
Newsgroups: comp.os.linux.hardware
Date: 2001-09-08 18:20:34 PST
> >> Argh! I think I hosed my lm_sensors! I had to regrab the source
> >> files for i2c and lm_sensors to get components. Now, my sensors
> >> are outputting wrong :(.
> >
> > May not be hosed. Use rmmod to remove any of the lmsensors modules
> > before running. Note: when I change kernels (upgrade) I just run the
> > install command in both the i2c and sensors directories.
>
> Um, how do I know which modules to remove?
lsmod will list all the currently running modules. To find out what
the module is use modinfo -d modulename. Some are self explanatory.
If you dump one by mistake just insmod or modprobe will reinstall it.
The difference is modprobe will load dependant modules as well. At
least that's what I understand the difference to be.
lm_sensors v2.6.1 not showing voltages?
Alright, I fixed my hosed sensors (caused by i2cdump 0 0x2d command from
http://www.netroedge.com/~lm78/readticket.cgi?ticket=659 link. Somehow, I
couldn't even reboot and shutdown my computer (had to unplug the power!!).
I guess sensors-detect did something bad to my computer during the probe.
Whew! I decided to boot to Windows 98 and upgraded Motherboard Monitor to
v4.18. It detected my chip! The chip was indeed GL518SM (same as
sensors-detect's probe). I reran the sesnors-detect and reconfigured. I
got everything back.
