Comment régler le RPM des ventilos ?

Bonjour à tous !!
Je voudrais savoir s’il ya moyen de réguler la vitesse de rotation de mes ventilos boitier.
J’ai 2 ventilos en façade (aspiration), et 1 à l’arrière du boitier (extraction) les 3 reliés à la carte mère. En ce qui concerne le ventirad, c’est un zalman 9700led avec fanmate (rehobus), donc pas de problème.
Sous w$, des utilitaires Asus permettent de créer des profils silencieux, mais quand je boot sur Debian c’est carrément la soufflerie.
Si quelqu’un a une astuce, ce serait sympa. Merci.

Bonjour,
il te faut déja installer et configurer lm-sensors.
Ce ne sont pas les tutos qui manquent!
En faisant une recherche sur le forum, tu trouveras aussi de nombreux fils de discution sur ce sujet.

Bonjour!!
lm-sensors installé, voilà ce que donne un sensors:

[code]~$ sensors
atk0110-acpi-0
Adapter: ACPI interface
Vcore Voltage: +1.10 V (min = +0.80 V, max = +1.60 V)
+3.3 Voltage: +3.30 V (min = +2.97 V, max = +3.63 V)
+5 Voltage: +4.92 V (min = +4.50 V, max = +5.50 V)
+12 Voltage: +11.76 V (min = +10.20 V, max = +13.80 V)
DDR Voltage: +2.10 V (min = +1.80 V, max = +2.10 V)
SB11 Voltage: +1.12 V (min = +0.80 V, max = +1.30 V)
SB15 Voltage: +1.50 V (min = +0.80 V, max = +1.80 V)
CPUPLL Voltage: +1.53 V (min = +1.20 V, max = +1.70 V)
NB11 Voltage: +1.12 V (min = +0.80 V, max = +1.80 V)
Dram VTT Volt: +1.05 V (min = +0.80 V, max = +2.00 V)
VTTCPU Voltage: +1.12 V (min = +0.80 V, max = +1.50 V)
CPU FAN Speed: 1318 RPM (min = 600 RPM, max = 7200 RPM)
CH_FAN1 Speed: 1790 RPM (min = 600 RPM, max = 7200 RPM)
CH_FAN2 Speed: 0 RPM (min = 600 RPM, max = 7200 RPM)
CH_FAN3 Speed: 0 RPM (min = 600 RPM, max = 7200 RPM)
Power_FAN Speed: 0 RPM (min = 600 RPM, max = 7200 RPM)
OPT1_FAN Speed: 0 RPM (min = 600 RPM, max = 7200 RPM)
OPT2_FAN Speed: 0 RPM (min = 600 RPM, max = 7200 RPM)
OPT3_FAN Speed: 747 RPM (min = 600 RPM, max = 7200 RPM)
CPU Temperature: +29.5°C (high = +60.0°C, crit = +95.0°C)
MB Temperature: +38.0°C (high = +50.0°C, crit = +95.0°C)
SB Temperature: +54.0°C (high = +65.0°C, crit = +95.0°C)
NB Temperature: +49.0°C (high = +65.0°C, crit = +95.0°C)
POWER Temperature: +40.0°C (high = +45.0°C, crit = +95.0°C)
OPT_FAN3 Temperature: +0.0°C (high = +45.0°C, crit = +95.0°C)
OPT_FAN2 Temperature: +0.0°C (high = +45.0°C, crit = +95.0°C)
OPT_FAN1 Temperature: +0.0°C (high = +45.0°C, crit = +95.0°C)

coretemp-isa-0000
Adapter: ISA adapter
Core 0: +48.0°C (high = +78.0°C, crit = +100.0°C)
Core 1: +50.0°C (high = +78.0°C, crit = +100.0°C)
[/code]
pour ce qui est de mon problème(regler le RPM des ventilos boitier) je ne sais pas comment m’y prendre,et je ne trouve que des tutos en Anglais et sur Ubuntu en plus :angry:
un pe’tit lien SVP :pray:

wiki.archlinux.org/index.php/Fan_Speed_Control
linux-attitude.fr/post/il-fait-chaud-ici

Environ 4s de recherche…

La plupart des tutos sous ubuntu s’applique a Debian.

[quote=“hasable”]
La plupart des tutos sous ubuntu s’applique a Debian.[/quote]
Ou disons, la plupart peuvent être adaptés pour fonctionner aussi sous Debian… faudrait pas ajouter un dépot PPA ou truc du genre :wink: (si si, on a déjà vu ça…)

$ pwmconfig bash: pwmconfig : commande introuvable
purkuaaa!!! :089

Cette commande semble fournie par le paquet fancontrol:

packages.debian.org/wheezy/all/f … l/filelist

[quote=“the_somberlain”]$ pwmconfig
bash: pwmconfig : commande introuvable

purkuaaa!!!
[/quote]“pwmconfig” => avec le compte root

========
ATK0110:
controler-la-vitesse-des-ventillateurs-t28888.html#p292129

@MicP:

même chose.

[code]ls -l /usr/sbin/pwmconfig[/code]
[code]which pwmconfig[/code]
[code]echo $PATH[/code]

Question stupide: est-ce que fancontrol est présent dans les paquets lm-sensors ou je dois l’installer avec un #apt-get install fancontrol
?!

Oui il faut que tu installes le paquet [mono]fancontrol[/mono].

Bonjour!!
fnacontrol installé, maintenant voilà ce que donne un # pwmconfig:

Les résultats de:

[quote=“Zbf”]Les résultats de:
Code:
sensors-detect[/quote]

[code]i# sensors-detect

sensors-detect revision 6031 (2012-03-07 17:14:01 +0100)

Board: ASUSTeK Computer INC. Maximus II Formula

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): y
Probing for Super-I/O at 0x2e/0x2f
Trying family National Semiconductor/ITE'... No Trying familySMSC’… No
Trying family VIA/Winbond/Nuvoton/Fintek'... Yes FoundWinbond W83667HG Super IO Sensors’ Success!
(address 0x290, driver w83627ehf') Probing for Super-I/O at 0x4e/0x4f Trying familyNational Semiconductor/ITE’… No
Trying family SMSC'... No Trying familyVIA/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 forIPMI 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 forNational Semiconductor LM79’ at 0x290… No
Probing for Winbond W83781D' at 0x290... No Probing forWinbond 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 ICH10
Module i2c-dev loaded successfully.

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

Driver `w83627ehf’:

  • ISA bus, address 0x290
    Chip `Winbond W83667HG Super IO Sensors’ (confidence: 9)

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
w83627ehf
#----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)y
Successful!

Monitoring programs won’t work until the needed modules are
loaded. You may want to run '/etc/init.d/kmod start’
to load them.

Unloading i2c-dev… OK
Unloading cpuid… OK
[/code]

[quote=“the_somberlain”]Code:
cat /etc/modules[/quote]

# cat /ets/modules cat: /ets/modules: Aucun fichier ou dossier de ce type

/etc/, pas /ets/

bonjour,
j’ai eu les pires galères avec le module w83627ehf et une carte ASUS.
Tu dois pouvoir retrouver ça sur le forum.
Il fallait désactiver un truc au boot du kernel, je ne me rappelle plus quoi

@ piratebab

[quote=“piratebab”]… Tu dois pouvoir retrouver ça sur le forum. …[/quote]Je m’en souviens : debian-fr.org/configurer-fr … it=atk0110

============
@ the_somberlain
Le lien que j’avais transmis (dans mon premier post de ce fil de discussion) résume très bien la situation des développeurs de “lm-sensors” au sujet de l’ATK0110.

Et plus récemment, il y a encore :
bugtrack.almico.com/view.php?id=1961

@Zbf:

[code]~$ cat /etc/modules

/etc/modules: kernel modules to load at boot time.

This file contains the names of kernel modules that should be loaded

at boot time, one per line. Lines beginning with “#” are ignored.

Parameters can be specified after the module name.

loop

Generated by sensors-detect on Fri Dec 6 19:31:07 2013

Chip drivers

coretemp
w83627ehf

Generated by sensors-detect on Sat Dec 7 10:00:06 2013

Chip drivers

coretemp
w83627ehf

Generated by sensors-detect on Sat Dec 7 14:51:08 2013

Chip drivers

coretemp
w83627ehf
[/code]
et:

$ lsmod Module Size Used by bnep 17567 2 rfcomm 33700 0 bluetooth 119455 10 rfcomm,bnep rfkill 19012 3 bluetooth nfsd 216170 2 nfs 308313 0 nfs_acl 12511 2 nfs,nfsd auth_rpcgss 37143 2 nfs,nfsd fscache 36739 1 nfs lockd 67306 2 nfs,nfsd sunrpc 173730 6 lockd,auth_rpcgss,nfs_acl,nfs,nfsd hwmon_vid 12430 0 loop 22641 0 snd_hda_codec_hdmi 30824 1 snd_hda_codec_analog 78059 1 radeon 718093 0 ttm 53664 1 radeon drm_kms_helper 31370 1 radeon snd_hda_intel 26259 3 drm 183952 3 drm_kms_helper,ttm,radeon snd_hda_codec 78031 3 snd_hda_intel,snd_hda_codec_analog,snd_hda_codec_hdmi evdev 17562 8 snd_hwdep 13186 1 snd_hda_codec snd_pcm 68083 3 snd_hda_codec,snd_hda_intel,snd_hda_codec_hdmi power_supply 13475 1 radeon iTCO_wdt 17081 0 snd_page_alloc 13003 2 snd_pcm,snd_hda_intel iTCO_vendor_support 12704 1 iTCO_wdt acpi_cpufreq 12935 0 mperf 12453 1 acpi_cpufreq processor 28157 3 acpi_cpufreq button 12937 0 i2c_algo_bit 12841 1 radeon i2c_i801 16870 0 pcspkr 12579 0 coretemp 12898 0 asus_atk0110 17297 0 i2c_core 23876 5 i2c_i801,i2c_algo_bit,drm,drm_kms_helper,radeon snd_seq 45126 0 snd_seq_device 13176 1 snd_seq snd_timer 22917 2 snd_seq,snd_pcm snd 52889 15 snd_timer,snd_seq_device,snd_seq,snd_pcm,snd_hwdep,snd_hda_codec,snd_hda_intel,snd_hda_codec_analog,snd_hda_codec_hdmi soundcore 13065 1 snd thermal_sys 18040 1 processor ext4 350763 3 crc16 12343 2 ext4,bluetooth jbd2 62115 1 ext4 mbcache 13114 1 ext4 usbhid 36418 0 sg 25874 0 hid 81328 1 usbhid sd_mod 36136 5 sr_mod 21899 0 crc_t10dif 12348 1 sd_mod cdrom 35401 1 sr_mod usb_storage 43870 0 firewire_ohci 35772 0 ata_generic 12479 0 floppy 53087 0 firewire_core 48449 1 firewire_ohci crc_itu_t 12347 1 firewire_core pata_marvell 12568 0 ahci 24997 0 libahci 22860 1 ahci ata_piix 29535 4 uhci_hcd 26865 0 libata 140630 5 ata_piix,libahci,ahci,pata_marvell,ata_generic scsi_mod 162269 5 libata,usb_storage,sr_mod,sd_mod,sg sky2 45442 0 ehci_hcd 40215 0 usbcore 128741 5 ehci_hcd,uhci_hcd,usb_storage,usbhid usb_common 12354 1 usbcore

Tu peux faire le ménage dans ton fichier module, tu as des lignes dupliquées.
Et dans ton lsmod, je ne vois pas le w83627ehf de chargé.
Tu n’as aucun message d’erreur au boot (dmesg)