Hallo,
ich habe versucht, eine manuelle Lüftersteuerung nach dem hiesigen Wiki (wiki.ubuntuusers.de/Lüftersteuerung)einzurichten. Es kommt allerdings zu unvorhergesehenen Fehlern.
In meinem Fall scheitert es daran, dass lm-sensors sich nicht vollständig konfigurieren lässt. sensors-detect erkennt erfolgreich die Temperatursensoren. Es erkennt aber keinerlei Lüfter. Deswegen schlägt mir ein erfolgreicher sensors-detect scan am Ende vor, das Modul "coretemp" zu laden:
flo@Papillon:~$ sudo sensors-detect
# sensors-detect revision 5984 (2011-07-10 21:22:53 +0200)
# System: Hewlett-Packard HP Pavilion dv6 Notebook PC (laptop)
# Board: Hewlett-Packard 17FA
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): y
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... Success!
(driver `coretemp')
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'... No
Trying family `ITE'... No
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor/ITE'... Yes
Found unknown chip with ID 0x8518
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):
Probing for `National Semiconductor LM78' at 0x290... No
Probing for `National Semiconductor LM79' at 0x290... No
Probing for `Winbond W83781D' at 0x290... No
Probing for `Winbond W83782D' at 0x290... 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-i801' for device 0000:00:1f.3: Intel Cougar Point (PCH)
Module i2c-i801 loaded successfully.
Module i2c-dev loaded successfully.
Next adapter: i915 gmbus disabled (i2c-0)
Do you want to scan it? (YES/no/selectively):
Next adapter: i915 gmbus ssc (i2c-1)
Do you want to scan it? (YES/no/selectively):
Next adapter: i915 GPIOB (i2c-2)
Do you want to scan it? (YES/no/selectively):
Next adapter: i915 gmbus vga (i2c-3)
Do you want to scan it? (YES/no/selectively):
Next adapter: i915 GPIOA (i2c-4)
Do you want to scan it? (YES/no/selectively):
Next adapter: i915 gmbus panel (i2c-5)
Do you want to scan it? (YES/no/selectively):
Client found at address 0x4f
Probing for `National Semiconductor LM75'... No
Probing for `National Semiconductor LM75A'... No
Probing for `Dallas Semiconductor DS75'... No
Probing for `Dallas Semiconductor DS1621/DS1631'... No
Probing for `Maxim MAX6642'... No
Probing for `Texas Instruments TMP421'... No
Probing for `Texas Instruments TMP422'... No
Probing for `Maxim MAX6633/MAX6634/MAX6635'... No
Probing for `NXP/Philips SA56004'... No
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: i915 GPIOC (i2c-6)
Do you want to scan it? (YES/no/selectively):
Client found at address 0x4f
Probing for `National Semiconductor LM75'... No
Probing for `National Semiconductor LM75A'... No
Probing for `Dallas Semiconductor DS75'... No
Probing for `Dallas Semiconductor DS1621/DS1631'... No
Probing for `Maxim MAX6642'... No
Probing for `Texas Instruments TMP421'... No
Probing for `Texas Instruments TMP422'... No
Probing for `Maxim MAX6633/MAX6634/MAX6635'... No
Probing for `NXP/Philips SA56004'... No
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: i915 gmbus dpc (i2c-7)
Do you want to scan it? (YES/no/selectively):
Next adapter: i915 GPIOD (i2c-8)
Do you want to scan it? (YES/no/selectively):
Next adapter: i915 gmbus dpb (i2c-9)
Do you want to scan it? (YES/no/selectively):
Next adapter: i915 GPIOE (i2c-10)
Do you want to scan it? (YES/no/selectively):
Next adapter: i915 gmbus reserved (i2c-11)
Do you want to scan it? (YES/no/selectively):
Next adapter: i915 gmbus dpd (i2c-12)
Do you want to scan it? (YES/no/selectively):
Next adapter: i915 GPIOF (i2c-13)
Do you want to scan it? (YES/no/selectively):
Next adapter: DPDDC-B (i2c-14)
Do you want to scan it? (YES/no/selectively):
Next adapter: Radeon i2c bit bus 0x90 (i2c-15)
Do you want to scan it? (YES/no/selectively):
Next adapter: Radeon i2c bit bus 0x91 (i2c-16)
Do you want to scan it? (YES/no/selectively):
Next adapter: Radeon i2c bit bus 0x92 (i2c-17)
Do you want to scan it? (YES/no/selectively):
Next adapter: Radeon i2c bit bus 0x93 (i2c-18)
Do you want to scan it? (YES/no/selectively):
Next adapter: Radeon i2c bit bus 0x94 (i2c-19)
Do you want to scan it? (YES/no/selectively):
Next adapter: Radeon i2c bit bus 0x95 (i2c-20)
Do you want to scan it? (YES/no/selectively):
Next adapter: Radeon i2c bit bus 0x96 (i2c-21)
Do you want to scan it? (YES/no/selectively):
Next adapter: Radeon i2c bit bus 0x97 (i2c-22)
Do you want to scan it? (YES/no/selectively):
Next adapter: SMBus I801 adapter at 6040 (i2c-23)
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'... Yes
(confidence 8, not a hardware monitoring chip)
Probing for `EDID EEPROM'... No
Client found at address 0x52
Probing for `Analog Devices ADM1033'... No
Probing for `Analog Devices ADM1034'... No
Probing for `SPD EEPROM'... Yes
(confidence 8, not a hardware monitoring chip)
Now follows a summary of the probes I have just done.
Just press ENTER to continue:
Driver `coretemp':
* Chip `Intel digital thermal sensor' (confidence: 9)
To load everything that is needed, add this to /etc/modules:
#----cut here----
# Chip drivers
coretemp
#----cut here----
If you have some drivers built into your kernel, the list above will
contain too many modules. Skip the appropriate ones!
Do you want to add these lines automatically to /etc/modules? (yes/NO)yes
Successful!
Monitoring programs won't work until the needed modules are
loaded. You may want to run 'service module-init-tools start'
to load them.
Unloading i2c-dev... OK
Unloading i2c-i801... OK
Unloading cpuid... OK
Sensors gibt dann aus:
flo@Papillon:~$ sensors acpitz-virtual-0 Adapter: Virtual device temp1: +53.0°C (crit = +99.0°C) coretemp-isa-0000 Adapter: ISA adapter Physical id 0: +53.0°C (high = +86.0°C, crit = +100.0°C) Core 0: +52.0°C (high = +86.0°C, crit = +100.0°C) Core 1: +48.0°C (high = +86.0°C, crit = +100.0°C) Core 2: +49.0°C (high = +86.0°C, crit = +100.0°C) Core 3: +44.0°C (high = +86.0°C, crit = +100.0°C) radeon-pci-0100 Adapter: PCI adapter temp1: -128.0°C
"coretemp-isa-0000" ist aber anscheinend noch nicht völlig ausgereift und bisher nur zum Auslesen von Temperaturen (und sonst nichts) geeignet. Der richtige Ansatzpunkt wäre deswegen wahrscheinlich das SPD EEPROM
Probing for `SPD EEPROM'... Yes
(confidence 8, not a hardware monitoring chip)Dementsprechend erkennt dann auch pwmconfig korrekt:
flo@Papillon:~$ sudo pwmconfig [sudo] password for flo: # 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/sbin/pwmconfig: There are no pwm-capable sensor modules installed'''
Ein ähnlicher Fehler trat anscheinend in der Vergangenheit häufig auf:
http://forum.ubuntuusers.de/topic/luefter-wie-steuern/?highlight=pwmconfig#post-3853172 http://forum.ubuntuusers.de/topic/cpu-luefter-drosseln-kontrollieren/?highlight=pwmconfig#post-3946992 http://forum.ubuntuusers.de/topic/problem-mit-lm-sensors-fancontrol-und-pwmconfi/?highlight=pwmconfig#post-4646452 (Man findet im Netz dutzende ähnlicher Posts)
Der Fehler war anscheinend unsauber geschriebene BIOS-Treiber, mit denen pwm-config nicht zurecht kam. Bis zum Kernel 2.6.14-rc1 gab es anscheinend einen funktionierenden Workaround, man konnte einfach das Modul it87 manuell laden und pwm auf die fehlerhaften Treiber vorbereiten. Das ging wohl so:
modprobe it87 fix_pwm_polarity=1
In allen neueren Kernelversionen aber wurde dies strikt verboten, weil dies einen Konflikt mit dem neuen Modul hwmon ausgelöst hat, was u.U. zu beschädigter Hardware führen könnte.
Dieses Verbot kann man umgehen, indem man in /etc/default/grub in der cmdline
acpi_enforce_resources=lax
einträgt und dann grub updatet.
Puh, so an diesem Punkt hänge ich jetzt gerade:
ERSTENS ist dieser Workaroung für Kernel 2.x vorgesehen gewesen, und ich bin mir nicht sicher, ob er für Kernel ab 3.x überhaupt geeignet ist und/oder vielleicht sogar gefährlicher geworden ist?
ZWEITENS funktioniert das wohl schon deshalb nicht (Hardware-Risiko beiseite), weil das Modul it87 gar nicht mehr enthalten ist:
flo@Papillon:~$ sudo modprobe it87 [sudo] password for flo: FATAL: Error inserting it87 (/lib/modules/3.2.0-32-generic/kernel/drivers/hwmon/it87.ko): No such device
Was tun? Kapitulieren ist keine Option... ☺