Mario, danke für die Tips, aber ich krieg das immernoch nicht hin. Ich habe mal sensors-detect laufen lassen und dann smbus genommen, der erkennt auch alles wie mir scheint, der gibt auch ne Empfehlung der zu ladenden Module raus, aber eines der Module aus der Empfehlung ( smbus-arp ) hab ich gar nicht im System, kann er also nicht laden. Anbei mal mein sensors-detect ... ( hoffe ist nicht zu viel post )

...

server:~ # sensors-detect

This program will help you determine which I2C/SMBus modules you need to load to use lm_sensors most effectively. You need to have i2c and lm_sensors installed before running this program. Also, you need to be `root', or at least have access to the /dev/i2c-* files, for most things. 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.

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-i801' for device 00:1f.3: Intel 82801EB ICH5 Probe succesfully concluded.

We will now try to load each adapter module in turn. Load `i2c-i801' (say NO if built into your kernel)? (YES/no): YES Module loaded succesfully. Do you now want to be prompted for non-detectable adapters? (yes/NO): 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): 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 I801 adapter at d800 (Algorithm unavailable) Do you want to scan it? (YES/no/selectively): YES Client found at address 0x08 Client found at address 0x0c Client found at address 0x2e Probing for `Myson MTP008'... Failed! Probing for `National Semiconductor LM78'... Failed! Probing for `National Semiconductor LM78-J'... Failed! Probing for `National Semiconductor LM79'... Failed! Probing for `National Semiconductor LM80'... Failed! Probing for `National Semiconductor LM85'... Failed! Probing for `Analog Devices ADM1027 or ADT7463'... Success! (confidence 7, driver `lm85') Probing for `SMSC EMC6D100 and EMC6D101'... Failed! Probing for `National Semiconductor LM87'... Failed! Probing for `Winbond W83781D'... Failed! Probing for `Winbond W83782D'... Failed! Probing for `Winbond W83791D'... Failed! Probing for `Winbond W83627HF'... Failed! Probing for `Asus AS99127F (rev.1)'... Failed! Probing for `Asus AS99127F (rev.2)'... Failed! Probing for `Asus ASB100 Bach'... Failed! Probing for `Winbond W83L785TS-S'... Failed! Probing for `Analog Devices ADM9240'... Failed! Probing for `Dallas Semiconductor DS1780'... Failed! Probing for `National Semiconductor LM81'... Failed! Probing for `Analog Devices ADM1026'... Failed! Probing for `Analog Devices ADM1025'... Failed! Probing for `Analog Devices ADM1024'... Failed! Probing for `Analog Devices ADM1029'... Failed! Probing for `Analog Devices ADM1030'... Failed! Probing for `Analog Devices ADM1031'... 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 0x44 Client found at address 0x50 Probing for `SPD EEPROM'... Success! (confidence 8, driver `eeprom') Probing for `DDC monitor'... Failed! Client found at address 0x52 Probing for `SPD EEPROM'... Success! (confidence 8, driver `eeprom') Client found at address 0x61 Probing for `SMBus 2.0 ARP-Capable Device'... Success! (confidence 1, driver `smbus-arp') Client found at address 0x69

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): no

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): no

Now follows a summary of the probes I have just done. Just press ENTER to continue:

Driver `lm85' (should be inserted): Detects correctly: * Bus `SMBus I801 adapter at d800' (Algorithm unavailable) Busdriver `i2c-i801', I2C address 0x2e Chip `Analog Devices ADM1027 or ADT7463' (confidence: 7)

Driver `eeprom' (should be inserted): Detects correctly: * Bus `SMBus I801 adapter at d800' (Algorithm unavailable) Busdriver `i2c-i801', I2C address 0x50 Chip `SPD EEPROM' (confidence: 8) * Bus `SMBus I801 adapter at d800' (Algorithm unavailable) Busdriver `i2c-i801', I2C address 0x52 Chip `SPD EEPROM' (confidence: 8)

Driver `smbus-arp' (should be inserted): Detects correctly: * Bus `SMBus I801 adapter at d800' (Algorithm unavailable) Busdriver `i2c-i801', I2C address 0x61 Chip `SMBus 2.0 ARP-Capable Device' (confidence: 1)

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

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

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

#----cut here---- # I2C adapter drivers modprobe i2c-i801 # I2C chip drivers modprobe lm85 modprobe eeprom modprobe smbus-arp # sleep 2 # optional /usr/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.suse to /etc/init.d/lm_sensors for initialization at boot time.

server:~ # modprobe i2c-i801 server:~ # modprobe lm85 server:~ # modprobe eeprom server:~ # modprobe smbus-arp FATAL: Module smbus_arp not found. server:~ #

Das wars ... Gruß Tom

...

-----Original Message----- From: Mario van der Linde [mailto:suse@vdlinde.org] Sent: Tuesday, August 16, 2005 7:18 PM To: suse-linux@suse.com Subject: Re: FW: SuSE Linux 9.1 & kernel 2.6.12.4: Probleme mit "sensors"

Hallo Tom,

Am Dienstag, 16. August 2005 19:04 schrieb Tom Henderson:

...

Hallo Mario,

[lsmod-Ausgabe] Nun, die Module scheinen geladen zu sein, aber ...

...

und was ISA oder SMBus angeht, ich habs erstmal mit ISA versucht ...

... holen die i2c-Module die Daten über den SMBus. Lass noch mal sensors-detect laufen und wähle den SMBus. Bei meinem Rechner hatte ich auch Probleme damit, sensors in Verbindung mit dem ISA-Bus zum laufen zu kriegen.

...

Gruß

Tom

Gruss Mario

[TOFU entsorgt]

-- Um die Liste abzubestellen, schicken Sie eine Mail an: suse-linux-unsubscribe@suse.com Um eine Liste aller verfuegbaren Kommandos zu bekommen, schicken Sie eine Mail an: suse-linux-help@suse.com