Sensors.conf für Asus A7N8X-E Suse 9.1 gesucht

[Arounder]

Hey Zusammen..!

Ich wollte mal fragen ob von euch einer eine funktionierende sensors.conf für das Asus A7N8X-E Deluxe hat?!

Gegoogelt hab ich schon, und die SuFu hab ich auch schon benützt.. :(

THX ciao :cool:

[BBlack]

Hast denn auch einfach mal das sensors detect ausgeführt? Grade bei nem Asus sollte des eigentlich passen....

[Arounder]

??? ich glaub ich muss hier mal dazu sagen das ich Linux erst seit cira 1 Monate benützte :ugly:

kannst du das ein bisschen näher erklären? THX

[Arounder]

auf der Seite von http://mbm.livewiredev.com/ hab ich folgende Infos über mein Board gefunden:
Board: A7N8X Deluxe
Sensor Chip: ASB100
Case Sensor: Asus 1
CPU Sensor: Asus 2 for socket and W83L785TS S Diode
Remarks: rev < 2.0 nForce HQ
&
A7N8X Deluxe - ASB100- Asus 2 - Asus 1 for socket and W83L785TS S Diode - rev >= 2.0 nForce HQ


also bei der Sensors-detect bekomm ich folgendes:
?!
Linuxserver:/home/arounder # 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.

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.
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 `rivatv' for device 03:00.0: GeForce2 MX
Use driver `i2c-nforce2' for device 00:01.1: nVidia Corporation nForce2 SMBus (MCP)
Probe succesfully concluded.

We will now try to load each adapter module in turn.
Load `rivatv' (say NO if built into your kernel)? (YES/no): yes
FATAL: Module rivatv not found.
Loading failed... skipping.
** Note: rivatv module is available at http://rivatv.sourceforge.net/
Load `i2c-nforce2' (say NO if built into your kernel)? (YES/no): yes
Module loaded succesfully.
If you have undetectable or unsupported adapters, you can have them
scanned by manually loading the modules before running this script.

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 nForce2 adapter at 5500 (Algorithm unavailable)
Do you want to scan it? (YES/no/selectively): yes
Client found at address 0x08
Client found at address 0x2d
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'... Failed!
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 W83783S'... 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'... Success!
(confidence 8, driver `asb100'), other addresses: 0x48 0x49
Probing for `Winbond W83L784R/AR'... Failed!
Probing for `Winbond W83L785R'... Failed!
Probing for `Genesys Logic GL518SM Revision 0x00'... Failed!
Probing for `Genesys Logic GL518SM Revision 0x80'... Failed!
Probing for `Genesys Logic GL520SM'... Failed!
Probing for `Genesys Logic GL525SM'... 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 `Philips NE1619'... 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!
Probing for `ALi M5879'... Failed!
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'... 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 `Analog Devices ADM9240'... Failed!
Probing for `Dallas Semiconductor DS1780'... Failed!
Probing for `National Semiconductor LM81'... Failed!
Probing for `Analog Devices ADM1029'... 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 0x37
Client found at address 0x48
Probing for `National Semiconductor LM75'... Success!
(confidence 6, driver `lm75')
Probing for `Dallas Semiconductor DS1621'... Failed!
Probing for `Maxim MAX6650/MAX6651'... Failed!
Client found at address 0x49
Probing for `National Semiconductor LM75'... Success!
(confidence 6, driver `lm75')
Probing for `Dallas Semiconductor DS1621'... Failed!
Client found at address 0x61
Probing for `SMBus 2.0 ARP-Capable Device'... Success!
(confidence 1, driver `smbus-arp')

Next adapter: SMBus nForce2 adapter at 5000 (Algorithm unavailable)
Do you want to scan it? (YES/no/selectively): yes
Client found at address 0x08
Client found at address 0x50
Probing for `SPD EEPROM'... Success!
(confidence 8, driver `eeprom')
Probing for `DDC monitor'... Failed!
Probing for `Maxim MAX6900'... Failed!
Client found at address 0x52
Probing for `SPD EEPROM'... Success!
(confidence 8, driver `eeprom')

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. This is usually safe though.

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... Failed!
Probing for `Silicon Integrated Systems SIS5595'
Trying general detect... Failed!
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. This is usually safe though.

Do you want to scan for Super I/O sensors? (YES/no): yes
Probing for `ITE 8702F Super IO Sensors'
Failed!
Probing for `ITE 8705F Super IO Sensors'
Failed!
Probing for `ITE 8712F Super IO Sensors'
Failed!
Probing for `Nat. Semi. PC87351 Super IO Fan Sensors'
Failed!
Probing for `Nat. Semi. PC87360 Super IO Fan Sensors'
Failed!
Probing for `Nat. Semi. PC87363 Super IO Fan Sensors'
Failed!
Probing for `Nat. Semi. PC87364 Super IO Fan Sensors'
Failed!
Probing for `Nat. Semi. PC87365 Super IO Sensors'
Failed!
Probing for `Nat. Semi. PC87366 Super IO Sensors'
Failed!
Probing for `Nat. Semi. PC87372 Super IO Fan Sensors'
Failed!
Probing for `SMSC 47B27x Super IO Fan Sensors'
Failed!
Probing for `SMSC 47M10x/13x Super IO Fan Sensors'
Failed!
Probing for `SMSC 47M14x Super IO Fan Sensors'
Failed!
Probing for `SMSC 47M15x/192 Super IO Fan Sensors'
Failed!
Probing for `VT1211 Super IO Sensors'
Failed! (0x87)
Probing for `Winbond W83627HF Super IO Sensors'
Failed! (0x87)
Probing for `Winbond W83627THF Super IO Sensors'
Failed! (0x87)
Probing for `Winbond W83637HF Super IO Sensors'
Failed! (0x87)
Probing for `Winbond W83697HF Super IO Sensors'
Failed! (0x87)
Probing for `Winbond W83697UF Super IO PWM'
Failed! (0x87)

Do you want to scan for secondary Super I/O sensors? (YES/no): yes
Probing for `ITE 8702F Super IO Sensors'
Failed!
Probing for `ITE 8705F Super IO Sensors'
Failed!
Probing for `ITE 8712F Super IO Sensors'
Failed!
Probing for `Nat. Semi. PC87351 Super IO Fan Sensors'
Failed!
Probing for `Nat. Semi. PC87360 Super IO Fan Sensors'
Failed!
Probing for `Nat. Semi. PC87363 Super IO Fan Sensors'
Failed!
Probing for `Nat. Semi. PC87364 Super IO Fan Sensors'
Failed!
Probing for `Nat. Semi. PC87365 Super IO Sensors'
Failed!
Probing for `Nat. Semi. PC87366 Super IO Sensors'
Failed!
Probing for `Nat. Semi. PC87372 Super IO Fan Sensors'
Failed!
Probing for `SMSC 47B27x Super IO Fan Sensors'
Failed!
Probing for `SMSC 47M10x/13x Super IO Fan Sensors'
Failed!
Probing for `SMSC 47M14x Super IO Fan Sensors'
Failed!
Probing for `SMSC 47M15x/192 Super IO Fan Sensors'
Failed!
Probing for `VT1211 Super IO Sensors'
Failed!
Probing for `Winbond W83627HF Super IO Sensors'
Failed!
Probing for `Winbond W83627THF Super IO Sensors'
Failed!
Probing for `Winbond W83637HF Super IO Sensors'
Failed!
Probing for `Winbond W83697HF Super IO Sensors'
Failed!
Probing for `Winbond W83697UF Super IO PWM'
Failed!

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

Driver `asb100' (should be inserted):
Detects correctly:
* Bus `SMBus nForce2 adapter at 5500' (Algorithm unavailable)
Busdriver `i2c-nforce2', I2C address 0x2d (and 0x48 0x49)
Chip `Asus ASB100 Bach' (confidence: 8)

Driver `lm75' (may not be inserted):
Misdetects:
* Bus `SMBus nForce2 adapter at 5500' (Algorithm unavailable)
Busdriver `i2c-nforce2', I2C address 0x48
Chip `National Semiconductor LM75' (confidence: 6)
* Bus `SMBus nForce2 adapter at 5500' (Algorithm unavailable)
Busdriver `i2c-nforce2', I2C address 0x49
Chip `National Semiconductor LM75' (confidence: 6)

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

Driver `eeprom' (should be inserted):
Detects correctly:
* Bus `SMBus nForce2 adapter at 5000' (Algorithm unavailable)
Busdriver `i2c-nforce2', I2C address 0x50
Chip `SPD EEPROM' (confidence: 8)
* Bus `SMBus nForce2 adapter at 5000' (Algorithm unavailable)
Busdriver `i2c-nforce2', I2C address 0x52
Chip `SPD EEPROM' (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)? 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-nforce2
# I2C chip drivers
modprobe asb100
modprobe smbus-arp
modprobe eeprom
# 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.
Linuxserver:/home/arounder #

[Arounder]

soo und wenn ich jetzt Module ausführe bekomm ich jetzt schonmal das: :)

Linuxserver:/home/arounder # sensors
asb100-i2c-1-2d
Adapter: SMBus nForce2 adapter at 5500
VCore 1: +1.62 V (min = +1.26 V, max = +1.90 V)
+3.3V: +3.31 V (min = +2.96 V, max = +3.63 V)
+5V: +4.78 V (min = +4.49 V, max = +5.51 V)
+12V: +11.80 V (min = +9.55 V, max = +14.41 V)
-12V (reserved):
-12.32 V (min = -0.00 V, max = -0.00 V)
-5V (reserved):
-5.17 V (min = -0.00 V, max = -0.00 V)
CPU Fan: 4383 RPM (min = 20454 RPM, div = 2)
Chassis Fan:
4041 RPM (min = 42187 RPM, div = 2)
Power Fan:3770 RPM (min = 42187 RPM, div = 2)
M/B Temp: +53°C (high = +80°C, hyst = +75°C)
CPU Temp (Intel):
+32°C (high = +80°C, hyst = +75°C)
Power Temp:
+125°C (high = +80°C, hyst = +75°C)
CPU Temp (AMD):
+25°C (high = +80°C, hyst = +75°C)
vid: +1.600 V
alarms:

eeprom-i2c-0-52
Adapter: SMBus nForce2 adapter at 5000
Memory type: DDR SDRAM DIMM
Memory size (MB): 256

eeprom-i2c-0-50
Adapter: SMBus nForce2 adapter at 5000
Memory type: DDR SDRAM DIMM
Memory size (MB): 256

[Arounder]

-Upp-

Wollte nur nochmal fragen ob hier irgendjemand mit diesem Mainboard hier ist, der es hinbekommen hat Sensors & Superkaramba zum laufen zu bringen..

ciao

[windoofcrasher]

Ich habe das A7N8x deluxe rev. 1.04. Bei mir funktioniert zwar sensors mit folgender Ausgabe:
eeprom-i2c-0-50
Adapter: SMBus nForce2 adapter at 5000
Memory type: DDR SDRAM DIMM
Memory size (MB): 128

eeprom-i2c-0-52
Adapter: SMBus nForce2 adapter at 5000
Memory type: DDR SDRAM DIMM
Memory size (MB): 128

asb100-i2c-1-2d
Adapter: SMBus nForce2 adapter at 5500
VCore1: +1.79 V (min = +1.18 V, max = +1.79 V) ALARM
+3.3V: +3.36 V (min = +2.96 V, max = +3.63 V)
+5V: +4.89 V (min = +4.49 V, max = +5.51 V)
+12V: +11.93 V (min = +9.54 V, max = +14.40 V)
-12V: -12.47 V (min = -0.00 V, max = -0.00 V)
-5V: -5.20 V (min = -0.00 V, max = -0.00 V)
CPU Fan: 0 RPM (min = -1 RPM, div = 2)
Chassis Fan:
0 RPM (min = 84375 RPM, div = 2)
Case Temp: +25°C (high = +80°C, hyst = +75°C)
CPU Temp: +40°C (high = +80°C, hyst = +75°C)
Sys Temp: +29°C (high = +80°C, hyst = +75°C)
vid: +1.750 V
alarms:

Ebenso sehe ich die Temperaturen in gkrellm.
Nur mit KDE klappt es noch nicht: Weder ksensors, ksim oder Systemüberwachung hat irgendwelche sensoren zur Auswahl.

Ich verwende SuSE 8.2 mit Kernel 2.4.20, lm-sensors-2.8.7 und i2c-2.8.7.

Gruß
Windoofcrasher

[derJoe]

Bei mir laufen die Sensoren vom A7N8X-Deluxe (rev. 2 glaub ich) in gkrellm und in superkaramba unter KDE.

Für Superkaramba müssen in der sensors.conf die Leerzeichen bei "CPU Fan", "CPU Temp" usw. entfernt werden, z.B. stattdessen ein "_".

Der entsprechende Teil aus meiner /etc/sensors.conf:



chip "asb100-*"
set vrm 9.0

label in0 "VCore_1"
set in0_min vid * 0.95
set in0_max vid * 1.05

label in1 "VCore_2"
ignore in1
set in1_min vid * 0.95
set in1_max vid * 1.05

label in2 "+3.3V"
set in2_min 3.3 * 0.95
set in2_max 3.3 * 1.05

label in3 "+5V"
compute in3 1.68 * @ , @ / 1.68
set in3_min 5.0 * 0.95
set in3_max 5.0 * 1.05

label in4 "+12V"
compute in4 3.8 * @ , @ / 3.8
set in4_min 12 * 0.90
set in4_max 12 * 1.10

label in5 "-12V_(reserved)"
#ignore in5
compute in5 -@ * 3.97 , -@ / 3.97
set in5_max -12 * 0.90
set in5_min -12 * 1.10

label in6 "-5V_(reserved)"
#ignore in6
compute in6 -@ * 1.666 , -@ / 1.666
set in6_max -5 * 0.95
set in6_min -5 * 1.05

label temp2 "MB"
set temp2_over 45
set temp2_hyst 40

label temp1 "CPU"
#ignore temp1
set temp1_over 60
set temp1_hyst 50

# PWRTMP connector on P4S333, for external sensor
label temp3 "Power_Temp"
#ignore temp3
set temp3_over 45
set temp3_hyst 40


# Used for Athlon diode, ignore for P4S333
label temp4 "CPU_Temp_(AMD)"
set temp4_over 60
set temp4_hyst 50
#ignore temp4

label fan1 "CPU_Fan"
set fan1_div 4
set fan1_min 2000

label fan2 "Chassis_Fan"
set fan2_div 2
set fan2_min 4000

label fan3 "Power_Fan"
set fan3_div 2
set fan3_min 4000


Allerdings bin ich mir mit der Zuordnung der Senoren nicht 100%ig sicher.

Gruß

derJoe

[Arounder]

schön, das auch nach längerer Zeit mal jemand drauf antwortet =) *respekt*

Ich werd´s morgen hoffentlich auch mal ausprobieren können..
werde davon berichtern ;) ciao

[grenzdebil]

Moin!

Ich hoffe dies ist der richtige Thread dafür(ausgiebeiges Belästigen der SuFu brachte keine besseren Ergebnisse ;) ).

Ich habe auch SUSE 9.1 auf einem A7N8X-E deluxe (AMD 2800) laufen und habe mit "sensors detect" die sensoren ans Laufen gebracht.

Mein Problem: unter Windows XP habe Ich bei normalem Betrieb eine CPU-Lüfter Drehzahl von ca. 1300 U/min, GKrellM zeigt mir jedoch ca. 3400 U/min an. :eek: (jeweils ruhender Desktop)

Ich weiß leider nicht, ob diese Anzeige Korrekt ist, Ich hatte schon vorher das Gefühl, daß die Kiste unter SUSE lauter ist als unter XP, aber so krass ist der unterschied auch nicht und die CPU Temperatur ist auch nicht niedriger als unter XP (was ja so sein sollte wenn der Lüfter weit mehr als doppelt so schnell rotiert...).


Meine Fragen daher:

1. Hat jemand ein ähnliches Problem?

2. Wenn es am Sensor liegt, welchen Multiplikator müsste Ich verwenden? Gibt es da Beispiele?

3. Wenn der Lüfter tatsächlich höher dreht, was kann Ich tun, um ihn unter Linux zu "bändigen"?
Wird er überhaupt von seiten des Betriebssystems geregelt?
Im BIOS ist eigentlich eingestellt, daß selbiges diese Aufgabe übernimmt, ein abschalten dieser Option bringt augenscheinlich keine Drehzahlveränderung...



Für Hinweise, die zur Ergreifung des Täters führen...
...vielen Dank! :D