Contenu | Rechercher | Menus

Annonce

Si vous rencontrez des soucis à rester connecté sur le forum (ou si vous avez perdu votre mot de passe) déconnectez-vous et reconnectez-vous depuis cette page, en cochant la case "Me connecter automatiquement lors de mes prochaines visites". Attention, le forum rencontre actuellement quelques difficultés. En cas d'erreur 502, il ne faut pas re-valider l'envoi d'un message ou l'ouverture d'une discussion, au risque de créer un doublon.

La section divers se réorganise ! De nouvelles sous-sections à venir. (plus d'infos + donner son avis)

#1 Le 23/11/2012, à 22:37

frere capsule

Impossible de régler la vitesse du ventilateur

Bonjour,

je suis sur ubuntu 12.04, mon pc portable fait un bruit monstrueux depuis que je l'ai (ce n'est pas une histoire de poussière, j'ai vérifé).
Dés que je met la machine en route (bien avant que linux prend le controle) le ventillo se met a fond.
J'aimerais donc pouvoir régler moi même la vitesse du ventilo, ceci est normalement faisable grace a "pwmconfig", qui veut dire "pulse width modulation", qui veut dire qu'on peut régler la vitesse de rotation du ventilo en modulant la largeur des pulse électriques envoyé au moteur...

Bien entendu pour moi ca marche pâs ....

Normalement il faut faire comme suit :

installer lm-sensor

detecter les différentes sondes disponible dans le pc (vitesse de rotation du ventilo, mais aussi température, etc...) :

sudo sensors-detect

puis tester et configurer le ventilo avec

sudo  pwmconfig

voir par exemple :  http://linux.leunen.com/?p=604

Chez moi pwmconfig ne marche pas, voici ce qu'il donne :

nico@nico-K70ID:~$ sudo  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.

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

Pour résoudre ca il y a un tuto ( http://ubuntuforums.org/showthread.php?t=2780 ) mais je n'y arrive pas.
On dirait que les sondes ne sont pas detectées....


voici le résultat de sensors après avoir tenté toute la manip (ca n'a pas changé par rapport à avant) :

nico@nico-K70ID:~$ sensors
acpitz-virtual-0
Adapter: Virtual device
temp1:        +47.0°C  (crit = +105.0°C)

coretemp-isa-0000
Adapter: ISA adapter
Core 0:       +43.0°C  (high = +105.0°C, crit = +105.0°C)
Core 1:       +42.0°C  (high = +105.0°C, crit = +105.0°C)

nouveau-pci-0200
Adapter: PCI adapter
temp1:        +39.0°C  (high = +100.0°C, crit = +110.0°C)

On voit que mon ventilo n'est pas détecté (enfin il n'y a pas de capteur actif, sinon il y aurait une ligne avec "fan...").

Voici les manips "pas-à-pas" que j'ai reproduit :

*) en me placant dans le repertoire ou se trouve mkdev.sh que j'ai préalablement crée

nico@nico-K70ID:~/Documents/linux$ sudo ./mkdev.sh
[sudo] password for nico: 
/dev/i2c-0
/dev/i2c-1
/dev/i2c-2
/dev/i2c-3
/dev/i2c-4
/dev/i2c-5
/dev/i2c-6
/dev/i2c-7
/dev/i2c-8
/dev/i2c-9
/dev/i2c-10
/dev/i2c-11
/dev/i2c-12
/dev/i2c-13
/dev/i2c-14
/dev/i2c-15
/dev/i2c-16
/dev/i2c-17
/dev/i2c-18
/dev/i2c-19
/dev/i2c-20
/dev/i2c-21
/dev/i2c-22
/dev/i2c-23
/dev/i2c-24
/dev/i2c-25
/dev/i2c-26
/dev/i2c-27
/dev/i2c-28
/dev/i2c-29
/dev/i2c-30
/dev/i2c-31

*) Ensuite (j'ai répondu "yes" à tout) :

nico@nico-K70ID:~/Documents/linux$ sudo sensors-detect
# sensors-detect revision 5984 (2011-07-10 21:22:53 +0200)
# System: ASUSTeK Computer Inc. K70ID (laptop)

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): yes
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): yes
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'...               No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Nuvoton/Fintek'...               No
Trying family `ITE'...                                      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): yes
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): yes
Using driver `i2c-nforce2' for device 0000:00:03.2: nVidia Corporation nForce SMBus (MCP79)
Module i2c-dev loaded successfully.

Next adapter: SMBus nForce2 adapter at 4d00 (i2c-0)
Do you want to scan it? (YES/no/selectively): yes

Next adapter: nouveau-0000:02:00.0-2 (i2c-1)
Do you want to scan it? (YES/no/selectively): yes
Client found at address 0x28
Probing for `National Semiconductor LM78'...                No
Probing for `National Semiconductor LM79'...                No
Probing for `National Semiconductor LM80'...                No
Probing for `Winbond W83781D'...                            No
Probing for `Winbond W83782D'...                            No
Probing for `Winbond W83627HF'...                           No
Probing for `Winbond W83627EHF'...                          No
Probing for `Winbond W83627DHG/W83667HG/W83677HG'...        No
Probing for `Asus AS99127F (rev.1)'...                      No
Probing for `Asus AS99127F (rev.2)'...                      No
Probing for `Asus ASB100 Bach'...                           No
Probing for `Analog Devices ADM1029'...                     No
Probing for `ITE IT8712F'...                                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: nouveau-0000:02:00.0-0 (i2c-2)
Do you want to scan it? (YES/no/selectively): yes

Next adapter: nouveau-0000:02:00.0-6 (i2c-3)
Do you want to scan it? (YES/no/selectively): yes

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 cpuid... OK


*) Voici ce qui est  dit de faire au point 4 :

4. In this example, we add the modules in reverse order (order is critical!) in "/etc/modules".

Là je n'ai pas saisi... mais je pense qu'il n'y a rien à faire car sensor-detect semble avoir ajouté les ligne automatiquement :

Do you want to add these lines automatically to /etc/modules? (yes/NO)yes
Successful!

*) Ensuite le point 5,

nico@nico-K70ID:/etc/init.d$ sudo modprobe i2c-sensor
FATAL: Module i2c_sensor not found.
nico@nico-K70ID:/etc/init.d$ sudo modprobe i2c-viapro
nico@nico-K70ID:/etc/init.d$ 
nico@nico-K70ID:/etc/init.d$ sudo modprobe i2c-isa
FATAL: Module i2c_isa not found.
nico@nico-K70ID:/etc/init.d$ sudo modprobe it87
FATAL: Error inserting it87 (/lib/modules/3.2.0-33-generic-pae/kernel/drivers/hwmon/it87.ko): No such device
nico@nico-K70ID:/etc/init.d$ sudo depmod -a
nico@nico-K70ID:/etc/init.d$ sudo update-modules 
sudo: update-modules: command not found

Il semble qu'aucun module n'ai été ajouté non ????

Hors ligne

Haut de page ↑