Hallo,
ich habe suse 9.0 kernel linux-2.4.21-99 und Mainboard MSI-6585, basierend
auf den Chipsätzen si S648 und Si S963 mit Intel Pentium IV Prozessor mit
2,53 GHz.
ich hab sensors version 2.8.0 installiert. Alles wird angezeigt, nur die Lüfterdrehzahl wird nicht angezeigt, obwohl ich das bei einer früheren Installation
schon hatte. Unter XP werden auch alle Lüfter angezeigt.
Installiert habe ich das ganze so:
rechner:/home/user# 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/modules.conf' (or `/etc/conf.modules') 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 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.
BIOS vendor (ACPI): AMI
System vendor (DMI): Fujitsu Siemens
BIOS version (DMI): 07.00T
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-sis645' for device 00:00.0: Silicon Integrated Systems SIS648
Use driver `i2c-sis5595' for device 00:02.0: Silicon Integrated Systems SIS5595
Probe succesfully concluded.
We will now try to load each adapter module in turn.
Load `i2c-sis645' (say NO if built into your kernel)? (YES/no): yes
Module loaded succesfully.
Load `i2c-sis5595' (say NO if built into your kernel)? (YES/no): yes
/lib/modules/2.4.21-99-default/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.21-99-default/kernel/drivers/i2c/i2c-sis5595.o: insmod /lib/modules/2.4.21-99-default/kernel/drivers/i2c/i2c-sis5595.o failed
/lib/modules/2.4.21-99-default/kernel/drivers/i2c/i2c-sis5595.o: insmod i2c-sis5595 failed
Loading failed... skipping.
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.21-99-default/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.21-99-default/kernel/drivers/i2c/i2c-elektor.o: insmod /lib/modules/2.4.21-99-default/kernel/drivers/i2c/i2c-elektor.o failed
/lib/modules/2.4.21-99-default/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.21-99-default/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.21-99-default/kernel/drivers/i2c/i2c-elv.o: insmod /lib/modules/2.4.21-99-default/kernel/drivers/i2c/i2c-elv.o failed
/lib/modules/2.4.21-99-default/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.21-99-default/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.21-99-default/kernel/drivers/i2c/i2c-velleman.o: insmod /lib/modules/2.4.21-99-default/kernel/drivers/i2c/i2c-velleman.o failed
/lib/modules/2.4.21-99-default/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).
Next adapter: SMBus SiS645 adapter at 0x0c00 (Non-I2C SMBus adapter)
Do you want to scan it? (YES/no/selectively): yes
Client found at address 0x08
Client found at address 0x10
Client found at address 0x2f
Probing for `National Semiconductor LM78'... Failed!
Probing for `National Semiconductor LM78-J'... Failed!
Probing for `National Semiconductor LM79'... Failed!
Probing for `National Semiconductor LM80'... Success!
(confidence 3, driver `lm80')
Probing for `Winbond W83781D'... Failed!
Probing for `Winbond W83782D'... Failed!
Probing for `Winbond W83783S'... Failed!
Probing for `Winbond W83791D'... Failed!
Probing for `Winbond W83627HF'... Failed!
Probing for `Asus AS99127F'... Failed!
Probing for `Winbond W83L784R/AR'... Failed!
Probing for `Analog Devices ADM9240'... Failed!
Probing for `Dallas Semiconductor DS1780'... Failed!
Probing for `National Semiconductor LM81'... Failed!
Probing for `Analog Devices ADM1022'... Failed!
Probing for `Texas Instruments THMC50'... Failed!
Probing for `ITE IT8705F / IT8712F / SiS 950'... Failed!
Client found at address 0x50
Probing for `Serial EEPROM'... Success!
(confidence 8, driver `eeprom')
Probing for `DDC monitor'... Failed!
Client found at address 0x51
Probing for `Serial EEPROM'... Success!
(confidence 8, driver `eeprom')
Client found at address 0x52
Probing for `Serial EEPROM'... Success!
(confidence 8, driver `eeprom')
Client found at address 0x69
Client found at address 0x6a
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'
Trying address 0x0290... Failed!
Probing for `National Semiconductor LM78-J'
Trying address 0x0290... Failed!
Probing for `National Semiconductor LM79'
Trying address 0x0290... Failed!
Probing for `Winbond W83781D'
Trying address 0x0290... Failed!
Probing for `Winbond W83782D'
Trying address 0x0290... Failed!
Probing for `Winbond W83627HF'
Trying address 0x0290... Failed!
Probing for `Winbond W83697HF'
Trying address 0x0290... Success!
(confidence 8, driver `w83781d')
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 `VIA Technologies VT8231 Integrated Sensors'
Trying general detect... Failed!
Probing for `ITE IT8705F / IT8712F / SiS 950'
Trying address 0x0290... Failed!
Probing for `IPMI BMC KCS'
Trying address 0x0ca0... Failed!
Probing for `IPMI BMC SMIC'
Trying address 0x0ca8... Failed!
Some Super I/O chips may also contain sensors. Super I/O probes are
typically a bit more dangerous, as we have to write to I/O ports to do
this. Do you want to scan for Super I/O sensors? (YES/no): yes
Probing for `SMSC 47M1xx Super IO Fan Sensors'
Failed!
Probing for `VT1211 Super IO Sensors'
Failed! (0x60)
Probing for `Winbond W83627HF Super IO Sensors'
Failed! (0x60)
Probing for `Winbond W83627THF Super IO Sensors'
Failed! (0x60)
Probing for `Winbond W83697HF Super IO Sensors'
Success... found at address 0x0290
Now follows a summary of the probes I have just done.
Just press ENTER to continue:
Driver `lm80' (should be inserted):
Detects correctly:
* Bus `SMBus SiS645 adapter at 0x0c00' (Non-I2C SMBus adapter)
Busdriver `i2c-sis645', I2C address 0x2f
Chip `National Semiconductor LM80' (confidence: 3)
Driver `eeprom' (should be inserted):
Detects correctly:
* Bus `SMBus SiS645 adapter at 0x0c00' (Non-I2C SMBus adapter)
Busdriver `i2c-sis645', I2C address 0x50
Chip `Serial EEPROM' (confidence: 8)
* Bus `SMBus SiS645 adapter at 0x0c00' (Non-I2C SMBus adapter)
Busdriver `i2c-sis645', I2C address 0x51
Chip `Serial EEPROM' (confidence: 8)
* Bus `SMBus SiS645 adapter at 0x0c00' (Non-I2C SMBus adapter)
Busdriver `i2c-sis645', I2C address 0x52
Chip `Serial EEPROM' (confidence: 8)
Driver `w83781d' (should be inserted):
Detects correctly:
* ISA bus address 0x0290 (Busdriver `i2c-isa')
Chip `Winbond W83697HF' (confidence: 8)
Driver `sis5595' (should be inserted):
Detects correctly:
* ISA bus, undetermined address (Busdriver `i2c-isa')
Chip `Silicon Integrated Systems SIS5595' (confidence: 9)
Driver `w83627hf' (may not be inserted):
Misdetects:
* ISA bus address 0x0290 (Busdriver `i2c-isa')
Chip `Winbond W83697HF Super IO Sensors' (confidence: 8)
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)? I2C/SMBus
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----
To load everything that is needed, add this to some /etc/rc* file:
#----cut here----
# I2C adapter drivers
modprobe i2c-sis645
modprobe i2c-isa
# I2C chip drivers
modprobe lm80
modprobe eeprom
modprobe w83781d
modprobe sis5595
# sleep 2 # optional
/usr/local/bin/sensors -s # recommended
#----cut here----
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.
Do you want to generate /etc/sysconfig/lm_sensors? (YES/no): YES
Copy /usr/share/doc/packages/sensors/prog/init/lm_sensors.init
to /etc/init.d/lm_sensors for initialization at boot time.
rechner:/home/user # modprobe i2c-sis645
rechner:/home/user # modprobe i2c-isa
rechner:/home/user # modprobe lm80
rechner:/home/user # modprobe eeprom
rechner:/home/user# modprobe w83781d
rechner:/home/user# modprobe sis5595
rechner:/home/user # /usr/bin/sensors -s
rechner:/home/user # sensors
lm80-i2c-0-2f
Adapter: SMBus SiS645 adapter at 0x0c00
Algorithm: Non-I2C SMBus adapter
+5V: +6.71 V (min = +6.71 V, max = +6.71 V) ALARM
VTT: +2.55 V (min = +2.55 V, max = +2.55 V) ALARM
+3.3V: +4.43 V (min = +4.43 V, max = +4.43 V) ALARM
+Vcore: +3.76 V (min = +3.76 V, max = +3.76 V) ALARM
+12V: +16.10 V (min = +16.10 V, max = +16.10 V) ALARM
-12V: -16.11 V (min = -16.11 V, max = -16.11 V) ALARM
-5V: -6.70 V (min = -6.70 V, max = -6.70 V) ALARM
fan1: 0 RPM (min = 0 RPM, div = 8) ALARM
fan2: 0 RPM (min = 0 RPM, div = 8) ALARM
temp: -1.00 °C (hot:limit = -1°C, hysteresis = -1°C) ALARM
(os: limit = -1°C, hysteresis = -1°C) ALARM
alarms: Board temperature input (LM75) ALARM
eeprom-i2c-0-50
Adapter: SMBus SiS645 adapter at 0x0c00
Algorithm: Non-I2C SMBus adapter
Memory type: DDR SDRAM DIMM SPD
Memory size (MB): 512
eeprom-i2c-0-51
Adapter: SMBus SiS645 adapter at 0x0c00
Algorithm: Non-I2C SMBus adapter
Memory type: DDR SDRAM DIMM SPD
Memory size (MB): 256
eeprom-i2c-0-52
Adapter: SMBus SiS645 adapter at 0x0c00
Algorithm: Non-I2C SMBus adapter
Memory type: DDR SDRAM DIMM SPD
Memory size (MB): 256
w83697hf-isa-0290
Adapter: ISA adapter
Algorithm: ISA algorithm
VCore: +1.48 V (min = +1.71 V, max = +1.88 V)
+3.3V: +3.20 V (min = +3.13 V, max = +3.45 V)
+5V: +4.94 V (min = +4.72 V, max = +5.24 V)
+12V: +11.86 V (min = +10.79 V, max = +13.19 V)
-12V: -12.13 V (min = -13.21 V, max = -10.90 V)
-5V: -5.10 V (min = -5.26 V, max = -4.76 V)
V5SB: +5.39 V (min = +4.72 V, max = +5.24 V)
VBat: +3.10 V (min = +2.40 V, max = +3.60 V)
fan1: 0 RPM (min = 3000 RPM, div = 2)
fan2: 0 RPM (min = 3000 RPM, div = 2)
temp1: +26°C (limit = +60°C) sensor = thermistor
temp2: +31.5°C (limit = +60°C, hysteresis = +50°C) sensor = PII/Celeron diode
alarms:
beep_enable:
Sound alarm disabled
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
Weiß jemand wie man das mit den Lüfterdrehzahl richtig konfiguriert?
Ich glaube vor einem Jahr hat es auch mal mit Suse 9.0 funktioniert.
ich habe suse 9.0 kernel linux-2.4.21-99 und Mainboard MSI-6585, basierend
auf den Chipsätzen si S648 und Si S963 mit Intel Pentium IV Prozessor mit
2,53 GHz.
ich hab sensors version 2.8.0 installiert. Alles wird angezeigt, nur die Lüfterdrehzahl wird nicht angezeigt, obwohl ich das bei einer früheren Installation
schon hatte. Unter XP werden auch alle Lüfter angezeigt.
Installiert habe ich das ganze so:
rechner:/home/user# 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/modules.conf' (or `/etc/conf.modules') 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 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.
BIOS vendor (ACPI): AMI
System vendor (DMI): Fujitsu Siemens
BIOS version (DMI): 07.00T
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-sis645' for device 00:00.0: Silicon Integrated Systems SIS648
Use driver `i2c-sis5595' for device 00:02.0: Silicon Integrated Systems SIS5595
Probe succesfully concluded.
We will now try to load each adapter module in turn.
Load `i2c-sis645' (say NO if built into your kernel)? (YES/no): yes
Module loaded succesfully.
Load `i2c-sis5595' (say NO if built into your kernel)? (YES/no): yes
/lib/modules/2.4.21-99-default/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.21-99-default/kernel/drivers/i2c/i2c-sis5595.o: insmod /lib/modules/2.4.21-99-default/kernel/drivers/i2c/i2c-sis5595.o failed
/lib/modules/2.4.21-99-default/kernel/drivers/i2c/i2c-sis5595.o: insmod i2c-sis5595 failed
Loading failed... skipping.
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.21-99-default/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.21-99-default/kernel/drivers/i2c/i2c-elektor.o: insmod /lib/modules/2.4.21-99-default/kernel/drivers/i2c/i2c-elektor.o failed
/lib/modules/2.4.21-99-default/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.21-99-default/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.21-99-default/kernel/drivers/i2c/i2c-elv.o: insmod /lib/modules/2.4.21-99-default/kernel/drivers/i2c/i2c-elv.o failed
/lib/modules/2.4.21-99-default/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.21-99-default/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.21-99-default/kernel/drivers/i2c/i2c-velleman.o: insmod /lib/modules/2.4.21-99-default/kernel/drivers/i2c/i2c-velleman.o failed
/lib/modules/2.4.21-99-default/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).
Next adapter: SMBus SiS645 adapter at 0x0c00 (Non-I2C SMBus adapter)
Do you want to scan it? (YES/no/selectively): yes
Client found at address 0x08
Client found at address 0x10
Client found at address 0x2f
Probing for `National Semiconductor LM78'... Failed!
Probing for `National Semiconductor LM78-J'... Failed!
Probing for `National Semiconductor LM79'... Failed!
Probing for `National Semiconductor LM80'... Success!
(confidence 3, driver `lm80')
Probing for `Winbond W83781D'... Failed!
Probing for `Winbond W83782D'... Failed!
Probing for `Winbond W83783S'... Failed!
Probing for `Winbond W83791D'... Failed!
Probing for `Winbond W83627HF'... Failed!
Probing for `Asus AS99127F'... Failed!
Probing for `Winbond W83L784R/AR'... Failed!
Probing for `Analog Devices ADM9240'... Failed!
Probing for `Dallas Semiconductor DS1780'... Failed!
Probing for `National Semiconductor LM81'... Failed!
Probing for `Analog Devices ADM1022'... Failed!
Probing for `Texas Instruments THMC50'... Failed!
Probing for `ITE IT8705F / IT8712F / SiS 950'... Failed!
Client found at address 0x50
Probing for `Serial EEPROM'... Success!
(confidence 8, driver `eeprom')
Probing for `DDC monitor'... Failed!
Client found at address 0x51
Probing for `Serial EEPROM'... Success!
(confidence 8, driver `eeprom')
Client found at address 0x52
Probing for `Serial EEPROM'... Success!
(confidence 8, driver `eeprom')
Client found at address 0x69
Client found at address 0x6a
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'
Trying address 0x0290... Failed!
Probing for `National Semiconductor LM78-J'
Trying address 0x0290... Failed!
Probing for `National Semiconductor LM79'
Trying address 0x0290... Failed!
Probing for `Winbond W83781D'
Trying address 0x0290... Failed!
Probing for `Winbond W83782D'
Trying address 0x0290... Failed!
Probing for `Winbond W83627HF'
Trying address 0x0290... Failed!
Probing for `Winbond W83697HF'
Trying address 0x0290... Success!
(confidence 8, driver `w83781d')
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 `VIA Technologies VT8231 Integrated Sensors'
Trying general detect... Failed!
Probing for `ITE IT8705F / IT8712F / SiS 950'
Trying address 0x0290... Failed!
Probing for `IPMI BMC KCS'
Trying address 0x0ca0... Failed!
Probing for `IPMI BMC SMIC'
Trying address 0x0ca8... Failed!
Some Super I/O chips may also contain sensors. Super I/O probes are
typically a bit more dangerous, as we have to write to I/O ports to do
this. Do you want to scan for Super I/O sensors? (YES/no): yes
Probing for `SMSC 47M1xx Super IO Fan Sensors'
Failed!
Probing for `VT1211 Super IO Sensors'
Failed! (0x60)
Probing for `Winbond W83627HF Super IO Sensors'
Failed! (0x60)
Probing for `Winbond W83627THF Super IO Sensors'
Failed! (0x60)
Probing for `Winbond W83697HF Super IO Sensors'
Success... found at address 0x0290
Now follows a summary of the probes I have just done.
Just press ENTER to continue:
Driver `lm80' (should be inserted):
Detects correctly:
* Bus `SMBus SiS645 adapter at 0x0c00' (Non-I2C SMBus adapter)
Busdriver `i2c-sis645', I2C address 0x2f
Chip `National Semiconductor LM80' (confidence: 3)
Driver `eeprom' (should be inserted):
Detects correctly:
* Bus `SMBus SiS645 adapter at 0x0c00' (Non-I2C SMBus adapter)
Busdriver `i2c-sis645', I2C address 0x50
Chip `Serial EEPROM' (confidence: 8)
* Bus `SMBus SiS645 adapter at 0x0c00' (Non-I2C SMBus adapter)
Busdriver `i2c-sis645', I2C address 0x51
Chip `Serial EEPROM' (confidence: 8)
* Bus `SMBus SiS645 adapter at 0x0c00' (Non-I2C SMBus adapter)
Busdriver `i2c-sis645', I2C address 0x52
Chip `Serial EEPROM' (confidence: 8)
Driver `w83781d' (should be inserted):
Detects correctly:
* ISA bus address 0x0290 (Busdriver `i2c-isa')
Chip `Winbond W83697HF' (confidence: 8)
Driver `sis5595' (should be inserted):
Detects correctly:
* ISA bus, undetermined address (Busdriver `i2c-isa')
Chip `Silicon Integrated Systems SIS5595' (confidence: 9)
Driver `w83627hf' (may not be inserted):
Misdetects:
* ISA bus address 0x0290 (Busdriver `i2c-isa')
Chip `Winbond W83697HF Super IO Sensors' (confidence: 8)
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)? I2C/SMBus
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----
To load everything that is needed, add this to some /etc/rc* file:
#----cut here----
# I2C adapter drivers
modprobe i2c-sis645
modprobe i2c-isa
# I2C chip drivers
modprobe lm80
modprobe eeprom
modprobe w83781d
modprobe sis5595
# sleep 2 # optional
/usr/local/bin/sensors -s # recommended
#----cut here----
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.
Do you want to generate /etc/sysconfig/lm_sensors? (YES/no): YES
Copy /usr/share/doc/packages/sensors/prog/init/lm_sensors.init
to /etc/init.d/lm_sensors for initialization at boot time.
rechner:/home/user # modprobe i2c-sis645
rechner:/home/user # modprobe i2c-isa
rechner:/home/user # modprobe lm80
rechner:/home/user # modprobe eeprom
rechner:/home/user# modprobe w83781d
rechner:/home/user# modprobe sis5595
rechner:/home/user # /usr/bin/sensors -s
rechner:/home/user # sensors
lm80-i2c-0-2f
Adapter: SMBus SiS645 adapter at 0x0c00
Algorithm: Non-I2C SMBus adapter
+5V: +6.71 V (min = +6.71 V, max = +6.71 V) ALARM
VTT: +2.55 V (min = +2.55 V, max = +2.55 V) ALARM
+3.3V: +4.43 V (min = +4.43 V, max = +4.43 V) ALARM
+Vcore: +3.76 V (min = +3.76 V, max = +3.76 V) ALARM
+12V: +16.10 V (min = +16.10 V, max = +16.10 V) ALARM
-12V: -16.11 V (min = -16.11 V, max = -16.11 V) ALARM
-5V: -6.70 V (min = -6.70 V, max = -6.70 V) ALARM
fan1: 0 RPM (min = 0 RPM, div = 8) ALARM
fan2: 0 RPM (min = 0 RPM, div = 8) ALARM
temp: -1.00 °C (hot:limit = -1°C, hysteresis = -1°C) ALARM
(os: limit = -1°C, hysteresis = -1°C) ALARM
alarms: Board temperature input (LM75) ALARM
eeprom-i2c-0-50
Adapter: SMBus SiS645 adapter at 0x0c00
Algorithm: Non-I2C SMBus adapter
Memory type: DDR SDRAM DIMM SPD
Memory size (MB): 512
eeprom-i2c-0-51
Adapter: SMBus SiS645 adapter at 0x0c00
Algorithm: Non-I2C SMBus adapter
Memory type: DDR SDRAM DIMM SPD
Memory size (MB): 256
eeprom-i2c-0-52
Adapter: SMBus SiS645 adapter at 0x0c00
Algorithm: Non-I2C SMBus adapter
Memory type: DDR SDRAM DIMM SPD
Memory size (MB): 256
w83697hf-isa-0290
Adapter: ISA adapter
Algorithm: ISA algorithm
VCore: +1.48 V (min = +1.71 V, max = +1.88 V)
+3.3V: +3.20 V (min = +3.13 V, max = +3.45 V)
+5V: +4.94 V (min = +4.72 V, max = +5.24 V)
+12V: +11.86 V (min = +10.79 V, max = +13.19 V)
-12V: -12.13 V (min = -13.21 V, max = -10.90 V)
-5V: -5.10 V (min = -5.26 V, max = -4.76 V)
V5SB: +5.39 V (min = +4.72 V, max = +5.24 V)
VBat: +3.10 V (min = +2.40 V, max = +3.60 V)
fan1: 0 RPM (min = 3000 RPM, div = 2)
fan2: 0 RPM (min = 3000 RPM, div = 2)
temp1: +26°C (limit = +60°C) sensor = thermistor
temp2: +31.5°C (limit = +60°C, hysteresis = +50°C) sensor = PII/Celeron diode
alarms:
beep_enable:
Sound alarm disabled
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
Weiß jemand wie man das mit den Lüfterdrehzahl richtig konfiguriert?
Ich glaube vor einem Jahr hat es auch mal mit Suse 9.0 funktioniert.