Regulacja Obrotami Wentylatora Cpu

[rakon]

Witam

 

na fujitsu siemens rx 100 s6 z fedora 14 wentylatory chodzą bardzo głośno w biosie patrzyłem jest to około 3000 rpm. Czy istnieje jakieś oprogramowanie do regulacji tych obrotów ?

[Raven]

Tak, nazywa się BIOS.

[rakon]

No na tyle to bystry jestem, w Biosie nie ma możliwości regulacji, można tylko zobaczyć aktualne parametry

[@sunrise]

Może tak ma być, w końcu to rack 1u. Patrzyłeś co mówi lm_sensors, /proc/acpi. Instalowałeś oprogramowanie producenta?

[rakon]

na windows 2008 chodzi cicho, przetestowałem, fujitsu supportuje tylko Windowsy, red hata enterp. i suse linux enterp. Pakiety od red-hata instalują się na fedorze ?

[3k_PL]

Pakiety od red-hata instalują się na fedorze ?

Nie radziłbym. No chyba że masz dostęp do src.rpm wtedy robisz rebuild i może coś z tego będzie.

Co Ci pokazał

sensors

[rakon]

z tego co pamiętam to nie mam lm-sensors na razie, jutro będę w pracy zainstaluję i zobaczymy. Myślę że raczej będzie bez rewelacji bo próbowałem już instalować debiana (też wyją wiatraki) i sprawdzałem sensor-detect praktycznie nie wiele wykrył a sensors wyświetlił chyba z pięć linijek parametrów. Patrzyłem na stronce lm-sensors i akurat dla Fujitsu dla chipsetu tego serwera nie ma wsparcia

 

Wyniki z debiana

polecenie sensors-detect:

# sensors-detect revision 5861 (2010-09-21 17:21:05 +0200)
# System: FUJITSU PRIMERGY RX100 S6
# Board: FUJITSU D2863

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
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'...                   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'...                   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):
Found `IPMI BMC KCS' at 0xca2...                            Success!
   (confidence 8, driver `ipmisensors')

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 3400/5 Series (PCH)
Module i2c-dev loaded successfully.

Next adapter: SMBus I801 adapter at 1840 (i2c-0)
Do you want to scan it? (YES/no/selectively):
Client found at address 0x18
Handled by driver `adm1021' (already loaded), chip type `max1617'
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'...                                No

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

Driver `adm1021':
 * Bus `SMBus I801 adapter at 1840'
   Busdriver `i2c_i801', I2C address 0x18
   Chip `max1617' (confidence: 6)

Driver `coretemp':
 * Chip `Intel digital thermal sensor' (confidence: 9)

Driver `ipmisensors':
 * ISA bus, address 0xca2
   Chip `IPMI BMC KCS' (confidence: 8)

Warning: the required module ipmisensors is not currently installed
on your system. If it is built into the kernel then it's OK.
Otherwise, check http://www.lm-sensors.org/wiki/Devices for
driver availability.

To load everything that is needed, add this to /etc/modules:
#----cut here----
# Adapter drivers
ipmi-si
# Chip drivers
adm1021
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)

Unloading i2c-dev... OK
Unloading cpuid... OK

 

polecenie sensors:

Adapter: ACPI interface
power1:      51.00 W  (interval =  60.00 s)

max1617-i2c-0-18
Adapter: SMBus I801 adapter at 1840
temp1:        +0.0°C  (low  = +16.0°C, high = +65.0°C)
temp2:        +2.0°C  (low  =  +1.0°C, high =  +3.0°C)

[3k_PL]

Paczki z RedHata możesz często instalować na CentOS-ie sobie przypomniałem.

A wiatraki mają przewód 3 czy 4 żyłowy?

[djkl]

Witam,

 

mi polecenie sensors wyrzuca:

acpitz-virtual-0
Adapter: Virtual device
temp1:       +50.0°C  (crit = +100.0°C)                  

coretemp-isa-0000
Adapter: ISA adapter
Core 0:      +37.0°C  (high = +100.0°C, crit = +100.0°C)  

coretemp-isa-0001
Adapter: ISA adapter
Core 1:      +37.0°C  (high = +100.0°C, crit = +100.0°C)  

 

Prędkość obrotów wentylatora w moim laptopie jest uzależniona tylko od temperatury "wirtualnej":

Adapter: Virtual device
temp1:       +50.0°C  (crit = +100.0°C)      

 

Mogę go mocno rozgrzać, a wentylator cały czas będzie kręcił z tą samą prędkością.

 

Mam tak od czasu pierwszej instalacji KDE 4. Wcześniej gdy miałem KDE 3.5 (siłą rzeczy inny kernel był), wszystko działało ok, tzn prędkość obrotów wentylatora była zmienna - zależnie od nagrzania procka.

Nie wiem jak go zmusić, aby słuchał się coretemp-isa-0000 Adapter: ISA adapter, po to by działał prawidłowo.

 

Dodam, że na równolegle zainstalowanym XP prędkość cały czas jest zmienna (wiadomo, zależnie od potrzeb).

 

 

Pozdrawiam

[Gość cross]

Przylaczylbym sie do prosby stworzenia tutoriala co do regulacji obrotów CPU.

Otóz u mnie wyglada to tak: Fedora 17

 

[root@localhost ~]# sensors --version
sensors version 3.3.2 with libsensors version 3.3.2

 

[root@localhost ~]# sensors-detect

# sensors-detect revision 6031 (2012-03-07 17:14:01 +0100)
# Board: Gigabyte Technology Co., Ltd. 8I865P-G

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
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): y
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'... Yes
Found `ITE IT8712F Super IO Sensors' Success!
(address 0x290, driver `it87')
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): y
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): y
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): y
Using driver `i2c-i801' for device 0000:00:1f.3: Intel 82801EB ICH5
Module i2c-dev loaded successfully.

Next adapter: nouveau-0000:01:00.0-0 (i2c-0)
Do you want to scan it? (YES/no/selectively): y

Next adapter: nouveau-0000:01:00.0-1 (i2c-1)
Do you want to scan it? (YES/no/selectively): y

Next adapter: nouveau-0000:01:00.0-2 (i2c-2)
Do you want to scan it? (YES/no/selectively): y

Next adapter: SMBus I801 adapter at 1400 (i2c-3)
Do you want to scan it? (yes/NO/selectively): y
Client found at address 0x4e
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 `Analog Devices ADM1021'... No
Probing for `Analog Devices ADM1021A/ADM1023'... No
Probing for `Maxim MAX1617'... No
Probing for `Maxim MAX1617A'... No
Probing for `Maxim MAX1668'... No
Probing for `Maxim MAX1805'... No
Probing for `Maxim MAX1989'... No
Probing for `Maxim MAX6642'... No
Probing for `Maxim MAX6655/MAX6656'... No
Probing for `TI THMC10'... No
Probing for `National Semiconductor LM84'... No
Probing for `Genesys Logic GL523SM'... No
Probing for `Onsemi MC1066'... No
Probing for `Maxim MAX1618'... No
Probing for `Maxim MAX1619'... No
Probing for `National Semiconductor LM82/LM83'... No
Probing for `Maxim MAX6654'... No
Probing for `Maxim MAX6690'... No
Probing for `Maxim MAX6659'... No
Probing for `Maxim MAX6647'... No
Probing for `Maxim MAX6680/MAX6681'... No
Probing for `Maxim MAX6695/MAX6696'... No
Probing for `Texas Instruments TMP411'... No
Probing for `Texas Instruments TMP421'... No
Probing for `Texas Instruments TMP422'... No
Probing for `Texas Instruments AMC6821'... No
Probing for `National Semiconductor LM64'... No
Probing for `National Semiconductor LM73'... No
Probing for `Maxim MAX6633/MAX6634/MAX6635'... No
Probing for `NXP/Philips SA56004'... No
Probing for `Fintek F75121R/F75122R/RG (VID+GPIO)'... No
Probing for `Fintek F75111R/RG/N (GPIO)'... No
Probing for `ITE IT8201R/IT8203R/IT8206R/IT8266R'... Yes
(confidence 6, not a hardware monitoring chip)
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

Next adapter: bt878 #0 [sw] (i2c-4)
Do you want to scan it? (yes/NO/selectively): y
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'... No

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

Driver `it87':
* ISA bus, address 0x290
Chip `ITE IT8712F Super IO Sensors' (confidence: 9)

Do you want to overwrite /etc/sysconfig/lm_sensors? (YES/no): y
Unloading i2c-dev... OK

 

[root@localhost ~]# pwmconfig
# 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.

/sbin/pwmconfig: There are no pwm-capable sensor modules installed

Zamiana

 

and go to line 68. Delete these three lines:

Code:
MATCH='*/fan[1-9]_pwm'
else
MATCH='*/pwm[1-9]'and replace with:


Code:
MATCH='*/pwm[1-9]'
else
MATCH='*/fan[1-9]_pwm'
You just turned the if/else around! Now pwmconfig should work.

Tez nie bardzo pomaga, bo u mnie schemat MATCH wyglada nieco inaczej, jest MATCH=$device/' ... itd

Nie bardzo wiem co dalej. :/

sensors zwraca

 

[root@localhost ]# sensors
acpitz-virtual-0
Adapter: Virtual device
temp1: +21.8°C (crit = +75.8°C)

Nie jest zle, ale wiatrak napierdziela strasznie