Hallo zusammen,
ich verzweifele gerade an der Lüftersteuerung meines PCs. Viel schlimmer ist aber, dass ich die Einrichtung schon geschafft hatte, ich mußte zwar fancontrol immer von Hand starten, aber dann verrichtete es seinen Dienst wie eingestellt.
Heute sieht es aber nun so aus (ohne dass ich wissentlich etwas verändert hätte):
michael@michael-MS-7042:~$ Loading configuration from /etc/fancontrol ... Common settings: INTERVAL=10 Settings for hwmon1/device/pwm2: Depends on hwmon1/device/temp1_input Controls hwmon1/device/fan1_input MINTEMP=20 MAXTEMP=70 MINSTART=150 MINSTOP=0 MINPWM=0 MAXPWM=255 Settings for hwmon1/device/pwm1: Depends on hwmon1/device/temp1_input Controls hwmon1/device/fan1_input MINTEMP=20 MAXTEMP=80 MINSTART=150 MINSTOP=0 MINPWM=0 MAXPWM=10 Device path of hwmon1 has changed Device name of hwmon1 has changed Configuration appears to be outdated, please run pwmconfig again
OK, "please run pwmconfig again", nichts leichter als das:
# pwmconfig revision 5857 (2010-08-22) This program will search your sensors for pulse width modulation (pwm) controls, and test each one to see if it controls a fan on your motherboard. Note that many motherboards do not have pwm circuitry installed, even if your sensor chip supports pwm. We will attempt to briefly stop each fan using the pwm controls. The program will attempt to restore each fan to full speed after testing. However, it is ** very important ** that you physically verify that the fans have been to full speed after the program has completed. /usr/local/sbin/pwmconfig: There are no pwm-capable sensor modules installed
Auch die Meldung "There are no pwm-capable sensor modules installed" hatte ich letzte Woche schon mal, hatte es aber nach langer Sucherei in verschiedenen Foren und Wikis geschafft, dass ich über pwmconfig die Einstellungen machen konnte. Dazu habe ich auch den Eintrag "acpi_enforce_resources=lax" in der /etc/efault/grub gemacht. Leider habe ich nicht aufgeschrieben, welche Schritte letztendlich zum Erfolg geführt hatten. ☹
sensors sieht nun so aus:
acpitz-virtual-0 Adapter: Virtual device temp1: +37.0°C (crit = +100.0°C)
Hier ist noch sensors-detect:
# sensors-detect revision 6031 (2012-03-07 17:14:01 +0100)
# System: MEDIONPC MS-7042
# Board: MICRO-STAR INTERNATIONAL CO., LTD MS-7042
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.
Some south bridges, CPUs or memory controllers contain embedded sensors.
Do you want to scan for them? This is totally safe. (YES/no):
Module cpuid loaded successfully.
Silicon Integrated Systems SIS5595... No
VIA VT82C686 Integrated Sensors... No
VIA VT8231 Integrated Sensors... No
AMD K8 thermal sensors... No
AMD Family 10h thermal sensors... No
AMD Family 11h thermal sensors... No
AMD Family 12h and 14h thermal sensors... No
AMD Family 15h thermal sensors... No
AMD Family 15h power sensors... No
Intel digital thermal sensor... No
Intel AMB FB-DIMM thermal sensor... No
VIA C7 thermal sensor... No
VIA Nano thermal sensor... No
Some Super I/O chips contain embedded 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 `National Semiconductor/ITE'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Nuvoton/Fintek'... Yes
Found `Winbond W83697HF/F/HG Super IO Sensors' Success!
(address 0x290, driver `w83627hf')
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor/ITE'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Nuvoton/Fintek'... No
Trying family `ITE'... No
Some systems (mainly servers) implement IPMI, a set of common interfaces
through which system health data may be retrieved, amongst other things.
We first try to get the information from SMBIOS. If we don't find it
there, we have to read from arbitrary I/O ports to probe for such
interfaces. This is normally safe. Do you want to scan for IPMI
interfaces? (YES/no):
Probing for `IPMI BMC KCS' at 0xca0... No
Probing for `IPMI BMC SMIC' at 0xca8... No
Some hardware monitoring chips are 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):
Lastly, we can probe the I2C/SMBus adapters for connected hardware
monitoring devices. This is the most risky part, and while it works
reasonably well on most systems, it has been reported to cause trouble
on some systems.
Do you want to probe the I2C/SMBus adapters now? (YES/no):
Using driver `i2c-viapro' for device 0000:00:11.0: VIA Technologies VT8237 South Bridge
Module i2c-dev loaded successfully.
Next adapter: saa7134[0] (i2c-0)
Do you want to scan it? (yes/NO/selectively):
Next adapter: SMBus Via Pro adapter at 0500 (i2c-1)
Do you want to scan it? (yes/NO/selectively):
Next adapter: Radeon i2c bit bus DVI_DDC (i2c-2)
Do you want to scan it? (YES/no/selectively):
Next adapter: Radeon i2c bit bus VGA_DDC (i2c-3)
Do you want to scan it? (YES/no/selectively):
Client found at address 0x50
Probing for `Analog Devices ADM1033'... No
Probing for `Analog Devices ADM1034'... No
Probing for `SPD EEPROM'... No
Probing for `EDID EEPROM'... Yes
(confidence 8, not a hardware monitoring chip)
Next adapter: Radeon i2c bit bus MONID (i2c-4)
Do you want to scan it? (YES/no/selectively):
Next adapter: Radeon i2c bit bus CRT2_DDC (i2c-5)
Do you want to scan it? (YES/no/selectively):
Now follows a summary of the probes I have just done.
Just press ENTER to continue:
Driver `w83627hf':
* ISA bus, address 0x290
Chip `Winbond W83697HF/F/HG Super IO Sensors' (confidence: 9)
Do you want to overwrite /etc/sysconfig/lm_sensors? (YES/no):
Copy prog/init/lm_sensors.init to /etc/init.d/lm_sensors
for initialization at boot time.
You should now start the lm_sensors service to load the required
kernel modules.
Unloading i2c-dev... OK
Unloading cpuid... OK
In /etc/modules habe ich folgendes eingetragen:
# Chip drivers modprobe w83627hf /usr/bin/sensors -s
Ich hoffe, mir kann jemand auf die Sprünge helfen. Wie gesagt, gestern ging alles noch. :-/
Viele Grüße, Michael