lm_sensors problem

[ral]

When I run "sensors" in the console I get this message:

 

"[ral@localhost ral]$ sensors

Can't access /proc file

/proc/sys/dev/sensors/chips or /proc/bus/i2c unreadable;

Make sure you have done 'modprobe i2c-proc'!

[ral@localhost ral]$"

 

Relevant system specs:

 

RedHat 8.0/Gnome

ECS K7S6A Motherboard (SiS 745 Chipset)

 

Checked out the help file, but still don't have a clue as to how to get it going. Only reading I care about really is tempreature. Motherboard has sensors which can be view in Windows.

 

Thanks in advance.

[MottS]

Just wondering .. did you 'modprobe i2c-proc' ??

 

If yes and it still doesn't work you may find something interesting on one of those posts.

 

There is links here to find if your hardware is supported by lm_sensors

http://www.mandrakeusers.org/viewtopic.php...light=lmsensors

 

Other post about lm_sensors:

http://www.club-nihil.net/mub/viewtopic.ph...light=lmsensors

http://www.club-nihil.net/mub/viewtopic.ph...light=lmsensors

http://www.club-nihil.net/mub/viewtopic.ph...light=lmsensors

 

Hope this help

 

MOttS

[ral]

I tried running "modprobe i2c-proc", but I got a command not found message. Thanks for the links... will go thorugh them in a bit and see what if I can find a soluction.

 

Thanks.

[ral]

According to http://mbm.livewiredev.com/comp/elite.html I have the following sensors:

 

K7S6A

 

Sensors Chip: SIS950/ITE705

 

Case Sensor: SIS950/ITE705 1

 

CPU Sensor: SIS950/ITE705 2

 

From the posts I tried the following:

 

[ral@localhost ral]$ su

Password:

[root@localhost ral]# sensors

Can't access /proc file

/proc/sys/dev/sensors/chips or /proc/bus/i2c unreadable;

Make sure you have done 'modprobe i2c-proc'!

[root@localhost ral]# sensors-detect

bash: sensors-detect: command not found

 

Will keep trying.

[MottS]

I tried running "modprobe i2c-proc", but I got a command not found message. Thanks for the links... will go thorugh them in a bit and see what if I can find a soluction.

 

Thanks.

 

You have to be root to 'modprobe'. You can see which 'i2c' modules are loaded by typing 'lsmod' as root. Here are mine just as an example:

$ su

Password:

# lsmod

...

...

w83781d                19504 0

i2c-proc                7088 0  [w83781d]

i2c-amd756              3664 0  (unused)

i2c-core            15332 0  [w83781d i2c-proc i2c-amd756]

...

...

 

For 'sensors-detect' (command not found), how did you install lm_sensors ? From an rpm or from a .tar.gz ? Because it doesn't seems to be in you $PATH. If you installed it with a .tar.gz package you could locate where the 'sensors-detect' binary is located by typing 'locate sensors'. If locate isn't installed try 'urpmi slocate && updatedb' as root and then 'locate sensors'.

 

K7S6A 

Sensors Chip: SIS950/ITE705 

Case Sensor: SIS950/ITE705 1 

CPU Sensor: SIS950/ITE705 2 

 

Did you verify if those chips are supported by lm_sensors ?

 

MottS

[MottS]

I checked HERE for you and you have to have loaded 'it87' to be able to talk with your chips. So check if 'it87' is loaded with 'lsmod' and if you don't see 'it87' then type 'modprobe it87'. Of course, you have to have run 'sensors-detect' before and the proper 'i2c-...' modules have to be loaded. (like i2c-proc, i2c-core, i2c-something_else and _maybe_ i2c-dev) ... check mine upthere.

 

Your chipsets are supported so it is supposed to work.

 

MottS

[ral]

If I remember correctly, lm_sensors is part of the RH8 default install.

 

Okay apparently with RH8 you need to log on as root in the X WIndow and can't just do it in the console :?:

 

 

"[root@localhost root]# sensors

Can't access /proc file

/proc/sys/dev/sensors/chips or /proc/bus/i2c unreadable;

Make sure you have done 'modprobe i2c-proc'!

[root@localhost root]# sensors-detect

This program will help you to determine which I2C/SMBus modules you need to

load to use lm_sensors most effectively.

You need to have done a `make install', issued a `depmod -a' and made sure

`/etc/conf.modules' (or `/etc/modules.conf') contains the appropriate

module path before you can use some functions of this utility. Read

doc/modules for more information.

Also, you need to be `root', or at least have access to the /dev/i2c[-/]* files for some things. You can use prog/mkdev/mkdev.sh to create these /dev files

if you do not have them already.

If you have patched your kernel and have some drivers built-in you can

safely answer NO if asked to load some modules. In this case, things may

seem a bit confusing, but they will still work.

 

IF THIS IS AN IBM THINKPAD, PRESS CTRL-C NOW!

IBM Thinkpads have a severely broken i2c/SMBus implementation, just scanning

the bus will break your thinkpad forever!

 

We can start with probing for (PCI) I2C or SMBus adapters.

You do not need any special privileges for this.

Do you want to probe now? (YES/no):

Probing for PCI bus adapters...

Use driver `i2c-sis5595' for device 00:02.0: Silicon Integrated Systems SIS5595

Use driver `i2c-riva' for device 01:00.0: GeForce2 MX

Probe succesfully concluded.

 

We will now try to load each adapter module in turn.

Load `i2c-sis5595' (say NO if built into your kernel)? (YES/no):

/lib/modules/2.4.18-14/kernel/drivers/i2c/i2c-sis5595.o: init_module: No such device

Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.

You may find more information in syslog or the output from dmesg

/lib/modules/2.4.18-14/kernel/drivers/i2c/i2c-sis5595.o: insmod /lib/modules/2.4.18-14/kernel/drivers/i2c/i2c-sis5595.o failed

/lib/modules/2.4.18-14/kernel/drivers/i2c/i2c-sis5595.o: insmod i2c-sis5595 failed

Loading failed ()... skipping.

Load `i2c-riva' (say NO if built into your kernel)? (YES/no):

modprobe: Can't locate module i2c-riva

Loading failed ()... skipping.

** Note: i2c-riva module is available at

** http://drama.obuda.kando.hu/~fero/cgi-bin/rivatv.shtml

Do you now want to be prompted for non-detectable adapters? (yes/NO):

To continue, we need module `i2c-dev' to be loaded.

If it is built-in into your kernel, you can safely skip this.

i2c-dev is not loaded. Do you want to load it now? (YES/no):

Module loaded succesfully.

 

We are now going to do the adapter probings. Some adapters may hang halfway

through; we can't really help that. Also, some chips will be double detected;

we choose the one with the highest confidence value in that case.

If you found that the adapter hung after probing a certain address, you can

specify that address to remain unprobed. That often

includes address 0x69 (clock chip).

 

Some chips are also accessible through the ISA bus. ISA probes are

typically a bit more dangerous, as we have to write to I/O ports to do

this. Do you want to scan the ISA bus? (YES/no):

Probing for `National Semiconductor LM78'

Character in "C" format wrapped at /usr/sbin/sensors-detect line 963.

Trying address 0x0290... Failed!

Probing for `National Semiconductor LM78-J'

Character in "C" format wrapped at /usr/sbin/sensors-detect line 963.

Trying address 0x0290... Failed!

Probing for `National Semiconductor LM79'

Character in "C" format wrapped at /usr/sbin/sensors-detect line 963.

Trying address 0x0290... Failed!

Probing for `Winbond W83781D'

Character in "C" format wrapped at /usr/sbin/sensors-detect line 963.

Trying address 0x0290... Failed!

Probing for `Winbond W83782D'

Character in "C" format wrapped at /usr/sbin/sensors-detect line 963.

Trying address 0x0290... Failed!

Probing for `Winbond W83627HF'

Character in "C" format wrapped at /usr/sbin/sensors-detect line 963.

Trying address 0x0290... Failed!

Probing for `Winbond W83697HF'

Character in "C" format wrapped at /usr/sbin/sensors-detect line 963.

Trying address 0x0290... Failed!

Probing for `Silicon Integrated Systems SIS5595'

Trying general detect... Success!

(confidence 9, driver `sis5595')

Probing for `VIA Technologies VT82C686 Integrated Sensors'

Trying general detect... Failed!

Probing for `ITE IT8705F / IT8712F / SiS 950'

Character in "C" format wrapped at /usr/sbin/sensors-detect line 963.

Trying address 0x0290... Failed!

Probing for `IPMI BMC KCS'

Trying address 0x0ca0... Failed!

Probing for `IPMI BMC SMIC'

Trying address 0x0ca8... Failed!

 

Now follows a summary of the probes I have just done.

Just press ENTER to continue:

 

Driver `sis5595' (should be inserted):

Detects correctly:

* ISA bus, undetermined address (Busdriver `i2c-isa')

Chip `Silicon Integrated Systems SIS5595' (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)?

 

WARNING! If you have some things built into your kernel, the

below list will contain too many modules. Skip the appropriate ones!

To load everything that is needed, add this to some /etc/rc* file:

 

#----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----

[root@localhost root]#"

 

 

It does not seem to work too well though:

 

 

"[ral@localhost ral]$ sensors

sis5595-isa-8008

Adapter: ISA adapter

Algorithm: ISA algorithm

VCore 1: +4.08 V (min = +4.08 V, max = +4.08 V) ALARM

VCore 2: +4.08 V (min = +4.08 V, max = +4.08 V) ALARM

+3.3V: +4.08 V (min = +4.08 V, max = +4.08 V) ALARM

+5V: +6.85 V (min = +6.85 V, max = +6.85 V) ALARM

fan1: 0 RPM (min = 0 RPM, div = 8 ) ALARM

fan2: 0 RPM (min = 0 RPM, div = 8 ) ALARM

temp: +51?C (limit = +51?C, hysteresis = +51?C) ALARM

alarms: Board temperature input (usually LM75 chips) ALARM

 

[ral@localhost ral]$"

[MottS]

You have to answer YES to everything questions. Did you ? Because there is nothing after 'will probe for isa bus stuff' (even if you don't have isa slots in your computer, you have an isa bus so don't skip that part!). Did you try 'modprobe it87' ?

 

I suggest you rerun 'sensors-detect' (answer YES to everything) and REBOOT. Now type 'sensors' and 'lsmod' and post their output here. We'll see what is loaded or not.

 

MottS

[ral]

I will have to continue later... I appreciate all the help and will try what you suggested, but am having some major linux problems right now which I need to resolve first.

 

I just wnated to say that people like you make Linux support the best in the world (I have about 40 pieces of licensed proprietary software so I really know what I am talking about).

 

Thanks.

[ral]

Okay did the whole thing again:

 

[root@localhost root]# sensors-detect

This program will help you to determine which I2C/SMBus modules you need to

load to use lm_sensors most effectively.

You need to have done a `make install', issued a `depmod -a' and made sure

`/etc/conf.modules' (or `/etc/modules.conf') contains the appropriate

module path before you can use some functions of this utility. Read

doc/modules for more information.

Also, you need to be `root', or at least have access to the /dev/i2c[-/]* files for some things. You can use prog/mkdev/mkdev.sh to create these /dev files

if you do not have them already.

If you have patched your kernel and have some drivers built-in you can

safely answer NO if asked to load some modules. In this case, things may

seem a bit confusing, but they will still work.

 

IF THIS IS AN IBM THINKPAD, PRESS CTRL-C NOW!

IBM Thinkpads have a severely broken i2c/SMBus implementation, just scanning

the bus will break your thinkpad forever!

 

We can start with probing for (PCI) I2C or SMBus adapters.

You do not need any special privileges for this.

Do you want to probe now? (YES/no): YES

Probing for PCI bus adapters...

Use driver `i2c-sis5595' for device 00:02.0: Silicon Integrated Systems SIS5595

Use driver `i2c-riva' for device 01:00.0: GeForce2 MX

Probe succesfully concluded.

 

We will now try to load each adapter module in turn.

Load `i2c-sis5595' (say NO if built into your kernel)? (YES/no): YES

/lib/modules/2.4.18-19.8.0/kernel/drivers/i2c/i2c-sis5595.o: init_module: No such device

Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.

You may find more information in syslog or the output from dmesg

/lib/modules/2.4.18-19.8.0/kernel/drivers/i2c/i2c-sis5595.o: insmod /lib/modules/2.4.18-19.8.0/kernel/drivers/i2c/i2c-sis5595.o failed

/lib/modules/2.4.18-19.8.0/kernel/drivers/i2c/i2c-sis5595.o: insmod i2c-sis5595

failed

Loading failed ()... skipping.

Load `i2c-riva' (say NO if built into your kernel)? (YES/no): YES

modprobe: Can't locate module i2c-riva

Loading failed ()... skipping.

** Note: i2c-riva module is available at

** http://drama.obuda.kando.hu/~fero/cgi-bin/rivatv.shtml

Do you now want to be prompted for non-detectable adapters? (yes/NO): YES

Load `i2c-elektor' (say NO if built into your kernel)? (YES/no): YES

/lib/modules/2.4.18-19.8.0/kernel/drivers/i2c/i2c-elektor.o: init_module: No such device

Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.

You may find more information in syslog or the output from dmesg

/lib/modules/2.4.18-19.8.0/kernel/drivers/i2c/i2c-elektor.o: insmod /lib/modules/2.4.18-19.8.0/kernel/drivers/i2c/i2c-elektor.o failed

/lib/modules/2.4.18-19.8.0/kernel/drivers/i2c/i2c-elektor.o: insmod i2c-elektor

failed

Loading failed ()... skipping.

Load `i2c-elv' (say NO if built into your kernel)? (YES/no): YES

/lib/modules/2.4.18-19.8.0/kernel/drivers/i2c/i2c-elv.o: init_module: No such device

Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.

You may find more information in syslog or the output from dmesg

/lib/modules/2.4.18-19.8.0/kernel/drivers/i2c/i2c-elv.o: insmod /lib/modules/2.4.18-19.8.0/kernel/drivers/i2c/i2c-elv.o failed

/lib/modules/2.4.18-19.8.0/kernel/drivers/i2c/i2c-elv.o: insmod i2c-elv failed

Loading failed ()... skipping.

Load `i2c-philips-par' (say NO if built into your kernel)? (YES/no): YES

Module loaded succesfully.

Load `i2c-velleman' (say NO if built into your kernel)? (YES/no): YES

/lib/modules/2.4.18-19.8.0/kernel/drivers/i2c/i2c-velleman.o: init_module: No such device

Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.

You may find more information in syslog or the output from dmesg

/lib/modules/2.4.18-19.8.0/kernel/drivers/i2c/i2c-velleman.o: insmod /lib/modules/2.4.18-19.8.0/kernel/drivers/i2c/i2c-velleman.o failed

/lib/modules/2.4.18-19.8.0/kernel/drivers/i2c/i2c-velleman.o: insmod i2c-velleman failed

Loading failed ()... skipping.

To continue, we need module `i2c-dev' to be loaded.

If it is built-in into your kernel, you can safely skip this.

i2c-dev is not loaded. Do you want to load it now? (YES/no): YES

Module loaded succesfully.

 

We are now going to do the adapter probings. Some adapters may hang halfway

through; we can't really help that. Also, some chips will be double detected;

we choose the one with the highest confidence value in that case.

If you found that the adapter hung after probing a certain address, you can

specify that address to remain unprobed. That often

includes address 0x69 (clock chip).

 

Some chips are also accessible through the ISA bus. ISA probes are

typically a bit more dangerous, as we have to write to I/O ports to do

this. Do you want to scan the ISA bus? (YES/no): YES

Probing for `National Semiconductor LM78'

Character in "C" format wrapped at /usr/sbin/sensors-detect line 963.

Trying address 0x0290... Failed!

Probing for `National Semiconductor LM78-J'

Character in "C" format wrapped at /usr/sbin/sensors-detect line 963.

Trying address 0x0290... Failed!

Probing for `National Semiconductor LM79'

Character in "C" format wrapped at /usr/sbin/sensors-detect line 963.

Trying address 0x0290... Failed!

Probing for `Winbond W83781D'

Character in "C" format wrapped at /usr/sbin/sensors-detect line 963.

Trying address 0x0290... Failed!

Probing for `Winbond W83782D'

Character in "C" format wrapped at /usr/sbin/sensors-detect line 963.

Trying address 0x0290... Failed!

Probing for `Winbond W83627HF'

Character in "C" format wrapped at /usr/sbin/sensors-detect line 963.

Trying address 0x0290... Failed!

Probing for `Winbond W83697HF'

Character in "C" format wrapped at /usr/sbin/sensors-detect line 963.

Trying address 0x0290... Failed!

Probing for `Silicon Integrated Systems SIS5595'

Trying general detect... Success!

(confidence 9, driver `sis5595')

Probing for `VIA Technologies VT82C686 Integrated Sensors'

Trying general detect... Failed!

Probing for `ITE IT8705F / IT8712F / SiS 950'

Character in "C" format wrapped at /usr/sbin/sensors-detect line 963.

Trying address 0x0290... Failed!

Probing for `IPMI BMC KCS'

Trying address 0x0ca0... Failed!

Probing for `IPMI BMC SMIC'

Trying address 0x0ca8... Failed!

 

 

Now follows a summary of the probes I have just done.

Just press ENTER to continue:

 

Driver `sis5595' (should be inserted):

Detects correctly:

* ISA bus, undetermined address (Busdriver `i2c-isa')

Chip `Silicon Integrated Systems SIS5595' (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

 

WARNING! If you have some things built into your kernel, the

below list will contain too many modules. Skip the appropriate ones!

To load everything that is needed, add this to some /etc/rc* file:

 

#----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----

 

 

After adding the appropriate lines and a reboot:

 

 

[ral@localhost ral]$ sensors

sis5595-isa-8008

Adapter: ISA adapter

Algorithm: ISA algorithm

VCore 1: +4.08 V (min = +4.08 V, max = +4.08 V) ALARM

VCore 2: +4.08 V (min = +4.08 V, max = +4.08 V) ALARM

+3.3V: +4.08 V (min = +4.08 V, max = +4.08 V) ALARM

+5V: +6.85 V (min = +6.85 V, max = +6.85 V) ALARM

fan1: 0 RPM (min = 0 RPM, div = 8) ALARM

fan2: 0 RPM (min = 0 RPM, div = 8) ALARM

temp: +51?C (limit = +51?C, hysteresis = +51?C) ALARM

alarms: Board temperature input (usually LM75 chips) ALARM

 

[ral@localhost ral]$

 

 

Run sensors detect again and selected SMBus:

 

[root@localhost root]# sensors-detect

This program will help you to determine which I2C/SMBus modules you need to

load to use lm_sensors most effectively.

You need to have done a `make install', issued a `depmod -a' and made sure

`/etc/conf.modules' (or `/etc/modules.conf') contains the appropriate

module path before you can use some functions of this utility. Read

doc/modules for more information.

Also, you need to be `root', or at least have access to the /dev/i2c[-/]* files for some things. You can use prog/mkdev/mkdev.sh to create these /dev files

if you do not have them already.

If you have patched your kernel and have some drivers built-in you can

safely answer NO if asked to load some modules. In this case, things may

seem a bit confusing, but they will still work.

 

IF THIS IS AN IBM THINKPAD, PRESS CTRL-C NOW!

IBM Thinkpads have a severely broken i2c/SMBus implementation, just scanning

the bus will break your thinkpad forever!

 

We can start with probing for (PCI) I2C or SMBus adapters.

You do not need any special privileges for this.

Do you want to probe now? (YES/no): YES

Probing for PCI bus adapters...

Use driver `i2c-sis5595' for device 00:02.0: Silicon Integrated Systems SIS5595

Use driver `i2c-riva' for device 01:00.0: GeForce2 MX

Probe succesfully concluded.

 

 

We will now try to load each adapter module in turn.

Load `i2c-sis5595' (say NO if built into your kernel)? (YES/no): YES

/lib/modules/2.4.18-19.8.0/kernel/drivers/i2c/i2c-sis5595.o: init_module: No such device

Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.

You may find more information in syslog or the output from dmesg

/lib/modules/2.4.18-19.8.0/kernel/drivers/i2c/i2c-sis5595.o: insmod /lib/modules/2.4.18-19.8.0/kernel/drivers/i2c/i2c-sis5595.o failed

/lib/modules/2.4.18-19.8.0/kernel/drivers/i2c/i2c-sis5595.o: insmod i2c-sis5595

failed

Loading failed ()... skipping.

Load `i2c-riva' (say NO if built into your kernel)? (YES/no): YES

modprobe: Can't locate module i2c-riva

Loading failed ()... skipping.

** Note: i2c-riva module is available at

** http://drama.obuda.kando.hu/~fero/cgi-bin/rivatv.shtml

Do you now want to be prompted for non-detectable adapters? (yes/NO): yes

Load `i2c-elektor' (say NO if built into your kernel)? (YES/no): YES

/lib/modules/2.4.18-19.8.0/kernel/drivers/i2c/i2c-elektor.o: init_module: No such device

Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.

You may find more information in syslog or the output from dmesg

/lib/modules/2.4.18-19.8.0/kernel/drivers/i2c/i2c-elektor.o: insmod /lib/modules/2.4.18-19.8.0/kernel/drivers/i2c/i2c-elektor.o failed

/lib/modules/2.4.18-19.8.0/kernel/drivers/i2c/i2c-elektor.o: insmod i2c-elektor

failed

Loading failed ()... skipping.

Load `i2c-elv' (say NO if built into your kernel)? (YES/no): YES

/lib/modules/2.4.18-19.8.0/kernel/drivers/i2c/i2c-elv.o: init_module: No such device

Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.

You may find more information in syslog or the output from dmesg

/lib/modules/2.4.18-19.8.0/kernel/drivers/i2c/i2c-elv.o: insmod /lib/modules/2.4.18-19.8.0/kernel/drivers/i2c/i2c-elv.o failed

/lib/modules/2.4.18-19.8.0/kernel/drivers/i2c/i2c-elv.o: insmod i2c-elv failed

Loading failed ()... skipping.

Load `i2c-philips-par' (say NO if built into your kernel)? (YES/no): YES

Module loaded succesfully.

Load `i2c-velleman' (say NO if built into your kernel)? (YES/no): YES

/lib/modules/2.4.18-19.8.0/kernel/drivers/i2c/i2c-velleman.o: init_module: No such device

Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.

You may find more information in syslog or the output from dmesg

/lib/modules/2.4.18-19.8.0/kernel/drivers/i2c/i2c-velleman.o: insmod /lib/modules/2.4.18-19.8.0/kernel/drivers/i2c/i2c-velleman.o failed

/lib/modules/2.4.18-19.8.0/kernel/drivers/i2c/i2c-velleman.o: insmod i2c-velleman failed

Loading failed ()... skipping.

To continue, we need module `i2c-dev' to be loaded.

If it is built-in into your kernel, you can safely skip this.

i2c-dev is not loaded. Do you want to load it now? (YES/no): YES

Module loaded succesfully.

 

 

We are now going to do the adapter probings. Some adapters may hang halfway

through; we can't really help that. Also, some chips will be double detected;

we choose the one with the highest confidence value in that case.

If you found that the adapter hung after probing a certain address, you can

specify that address to remain unprobed. That often

includes address 0x69 (clock chip).

 

Some chips are also accessible through the ISA bus. ISA probes are

typically a bit more dangerous, as we have to write to I/O ports to do

this. Do you want to scan the ISA bus? (YES/no): YES

Probing for `National Semiconductor LM78'

Character in "C" format wrapped at /usr/sbin/sensors-detect line 963.

Trying address 0x0290... Failed!

Probing for `National Semiconductor LM78-J'

Character in "C" format wrapped at /usr/sbin/sensors-detect line 963.

Trying address 0x0290... Failed!

Probing for `National Semiconductor LM79'

Character in "C" format wrapped at /usr/sbin/sensors-detect line 963.

Trying address 0x0290... Failed!

Probing for `Winbond W83781D'

Character in "C" format wrapped at /usr/sbin/sensors-detect line 963.

Trying address 0x0290... Failed!

Probing for `Winbond W83782D'

Character in "C" format wrapped at /usr/sbin/sensors-detect line 963.

Trying address 0x0290... Failed!

Probing for `Winbond W83627HF'

Character in "C" format wrapped at /usr/sbin/sensors-detect line 963.

Trying address 0x0290... Failed!

Probing for `Winbond W83697HF'

Character in "C" format wrapped at /usr/sbin/sensors-detect line 963.

Trying address 0x0290... Failed!

Probing for `Silicon Integrated Systems SIS5595'

Trying general detect... Success!

(confidence 9, driver `sis5595')

Probing for `VIA Technologies VT82C686 Integrated Sensors'

Trying general detect... Failed!

Probing for `ITE IT8705F / IT8712F / SiS 950'

Character in "C" format wrapped at /usr/sbin/sensors-detect line 963.

Trying address 0x0290... Failed!

Probing for `IPMI BMC KCS'

Trying address 0x0ca0... Failed!

Probing for `IPMI BMC SMIC'

Trying address 0x0ca8... Failed!

 

Now follows a summary of the probes I have just done.

Just press ENTER to continue:

 

Driver `sis5595' (should be inserted):

Detects correctly:

* ISA bus, undetermined address (Busdriver `i2c-isa')

Chip `Silicon Integrated Systems SIS5595' (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)? SMBus

 

WARNING! If you have some things built into your kernel, the

below list will contain too many modules. Skip the appropriate ones!

To load everything that is needed, add this to some /etc/rc* file:

 

#----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----

[root@localhost root]#

 

 

Same results though.