Parasite dans le son
gtrgib
Messages postés
544
Statut
Membre
-
gtrgib Messages postés 544 Statut Membre -
gtrgib Messages postés 544 Statut Membre -
Bonjour à tous,
Depuis 2 jours j'ai des parasites dans le son de mes hauts parleurs ou de mes écouteurs, que ce soit pour écouter de la musique ou encore pire lorsque je veux regarder un dvd.
Le problème ne vient pas des haut-parleurs et lorsque je regarde un DVD par exemple avec WinDVD, j'entend les parasite et si je cache WinDVD(ou tout autre lecteur avec lequel je visionne des vidéos) derrière un autre programme ou que je le mette dans la barre des tâches, les parasites diminue ou se font entendre moins. Mais dès que j'affiche le prog en premier plan alors ça devient insuportable.
Quelqu'un a une idée car j'ai ce problème autant sous Linux que sous Windows.
Voici ma configuration :
Un Pentium IV 3000MHz
512Mo de RAM
DD de 80Go WDC WD800JB-00JJC0
graveur DVD HL-DT-ST DVDRAM GSA-4163B
carte vidéo intégré SiS 661FX ainsi que la carte son intégré SoundMax
carte mère Asus P4S800-MX
écran plat 19' Flatron L1950S.
Petite kit de marque "Nikao" bon marché comprenant haut-parleurs
HP-2100, clavier HK-810, et souris obtique HM-708.
Carte résaux intégré SiS 900-Based PCI Fasted Ethernet Adapter
Merci
Depuis 2 jours j'ai des parasites dans le son de mes hauts parleurs ou de mes écouteurs, que ce soit pour écouter de la musique ou encore pire lorsque je veux regarder un dvd.
Le problème ne vient pas des haut-parleurs et lorsque je regarde un DVD par exemple avec WinDVD, j'entend les parasite et si je cache WinDVD(ou tout autre lecteur avec lequel je visionne des vidéos) derrière un autre programme ou que je le mette dans la barre des tâches, les parasites diminue ou se font entendre moins. Mais dès que j'affiche le prog en premier plan alors ça devient insuportable.
Quelqu'un a une idée car j'ai ce problème autant sous Linux que sous Windows.
Voici ma configuration :
Un Pentium IV 3000MHz
512Mo de RAM
DD de 80Go WDC WD800JB-00JJC0
graveur DVD HL-DT-ST DVDRAM GSA-4163B
carte vidéo intégré SiS 661FX ainsi que la carte son intégré SoundMax
carte mère Asus P4S800-MX
écran plat 19' Flatron L1950S.
Petite kit de marque "Nikao" bon marché comprenant haut-parleurs
HP-2100, clavier HK-810, et souris obtique HM-708.
Carte résaux intégré SiS 900-Based PCI Fasted Ethernet Adapter
Merci
18 réponses
Bonjour,
Apparemment l'OS n'est pas en question, sous win ou linux c'est pareil,
C'est donc un problème de matos,
tu dis :
Qu'as-tu modifié il y a 2 jours ?
connectique ? ajout de matos ?
Il me semble qu'il faut que tu cherches dans cette direction.
A+, cede.
Apparemment l'OS n'est pas en question, sous win ou linux c'est pareil,
C'est donc un problème de matos,
tu dis :
Depuis 2 jours
Qu'as-tu modifié il y a 2 jours ?
connectique ? ajout de matos ?
Il me semble qu'il faut que tu cherches dans cette direction.
A+, cede.
Vous n’avez pas trouvé la réponse que vous recherchez ?
Posez votre question
Bon, j'ai tout débranché et tout rebranché. Ça m'a pris plusieurs reset avant que ça redémarre car après plus rien ne fonctionnais et il n'y avait aucun bip qui aurais pue m'idiquer le problème.
Mon équipement ne date que de 1 ans depuis le mois d'aût...
Merci
Mon équipement ne date que de 1 ans depuis le mois d'aût...
Merci
Bonjour à tous, je revient un peu tard mais je vous explique pourquoi.
Finalement dimanche le 8 octobre dernier dans la soirée mon ordinateur m'a laissé tombé. Il n'y avait plus de bip au démarrage et après 1min 15sec il s'arrêtait.
J'ai été le porté chez un réparateur et c'était la carte mère qui était HS. J'ai reçu mon ordi hier soir avec une nouvelle carte mère ASUS P4S800D-X alors que j'avais une ASUS P4S800-MX. Quelqu'un connaît la différence?
Tout fonctionne bien pour l'instant mais je me demande par contre si la température de mon processeur n'est pas trop élévé. C'est un Pentium IV 3000MHz Intel 1024K 800MHz. La température au démarrage dans le Bios affichait 69 à 70 degré celcius et après une demi-heure elle montait jusqu'à 77,5 degré celcius et le MB se maintient à environ 27 degré celcius, le ventilo tourne à 2235RPM à 2265RPM.
Est ce normale?
Merci
Finalement dimanche le 8 octobre dernier dans la soirée mon ordinateur m'a laissé tombé. Il n'y avait plus de bip au démarrage et après 1min 15sec il s'arrêtait.
J'ai été le porté chez un réparateur et c'était la carte mère qui était HS. J'ai reçu mon ordi hier soir avec une nouvelle carte mère ASUS P4S800D-X alors que j'avais une ASUS P4S800-MX. Quelqu'un connaît la différence?
Tout fonctionne bien pour l'instant mais je me demande par contre si la température de mon processeur n'est pas trop élévé. C'est un Pentium IV 3000MHz Intel 1024K 800MHz. La température au démarrage dans le Bios affichait 69 à 70 degré celcius et après une demi-heure elle montait jusqu'à 77,5 degré celcius et le MB se maintient à environ 27 degré celcius, le ventilo tourne à 2235RPM à 2265RPM.
Est ce normale?
Merci
Je vient de constater que dans le Bios la température du cpu est d'environ 70 degré celcius et qu'elle augmente tranquillement si je reste dans le Bios. Et pourtant sous Windows avec un programme comme Aida32, la température du cpu affiche environ 55 degré celcius mais que la vitesse du ventilo est d'environ 2280RPM alors que dans le Bios c'est d'environ 2235RPM.
Quelqu'un comprend pourquoi?
Merci
Quelqu'un comprend pourquoi?
Merci
salut
petite question :
c est un pc de marque ou alors tu l as assembler ( monter ) si tu preferes ....
il est claire que + tu restes dans le bios + la temperature grimpe meme tres vite .........
normalement dans le bios section Power puis hardware monitor
tu peux changer la frequences des ventilos en fonction de la temperature ....
peut-etre mauvaise circulation de l aire ou alors tu manques peut-etre d un exhaust-Fan .....
petite question :
c est un pc de marque ou alors tu l as assembler ( monter ) si tu preferes ....
il est claire que + tu restes dans le bios + la temperature grimpe meme tres vite .........
normalement dans le bios section Power puis hardware monitor
tu peux changer la frequences des ventilos en fonction de la temperature ....
peut-etre mauvaise circulation de l aire ou alors tu manques peut-etre d un exhaust-Fan .....
Salut tufs,
C'est un pc de marque, je l'ai acheté comme ça l'an dernier en juillet 2005.
Je ne savais pas que je pouvais changer la vitesse des ventilos dans le Bios mais est ce dangereux?
Pourquoi ça grimpe autant dans le Bios car pourtant y a pas l'interface graphique et les programmes en tâche de font comme sous Windows ou Linux...
Mon ordi est très bien aéré, il n'y a rien autour et en ce moment il fait 4 degré celcius à l'extérieur et je ne chauffe pas mon appartement même si j'ai les doigts gelé.
Y a t'il un programme qui permet de voir la température du cpu et/ou MB sous Linux comme sous Windows?
Merci
C'est un pc de marque, je l'ai acheté comme ça l'an dernier en juillet 2005.
Je ne savais pas que je pouvais changer la vitesse des ventilos dans le Bios mais est ce dangereux?
Pourquoi ça grimpe autant dans le Bios car pourtant y a pas l'interface graphique et les programmes en tâche de font comme sous Windows ou Linux...
Mon ordi est très bien aéré, il n'y a rien autour et en ce moment il fait 4 degré celcius à l'extérieur et je ne chauffe pas mon appartement même si j'ai les doigts gelé.
Y a t'il un programme qui permet de voir la température du cpu et/ou MB sous Linux comme sous Windows?
Merci
Je vient de vérifier dans le Bios et je ne peu pas modifier la vitesse des ventilo, j'ai simplement le choix "Ignored" ou d'afficher sa vitesse.
Merci
Merci
re
tes ventilos fonctionnent-ils correctement parceque avec une temperature ambiante il fait 4 degré celcius à l'extérieur et je ne chauffe pas mon appartement même si j'ai les doigts gelé.
et cpu est d'environ 70 degré celcius et qu'elle augmente tranquillement tu as clairement un problem de refroidissement
maintennant la cause faut cherher ....
voilà pour ce qui concernne Linux :
Ventilation et temperature
Il existe 2 categories d outils ceux qui utilisent les informations fournies par l ACPI et ceux qui utilisent directement les composants
en charge de la surveillance thermique appelés Sensors
pour + de details voir google
pour l installation de sensors voir gestionnaire le paquet
lm_sensors ou paquet lm_sensors-devel ou meme gnome-applet-sensors
tout depends de la distrib utiliser pour mandriva par exemple :
# urpmi lm_sensors
voila cherche avec google il y a de bon wikis avant de te lancer !!
tes ventilos fonctionnent-ils correctement parceque avec une temperature ambiante il fait 4 degré celcius à l'extérieur et je ne chauffe pas mon appartement même si j'ai les doigts gelé.
et cpu est d'environ 70 degré celcius et qu'elle augmente tranquillement tu as clairement un problem de refroidissement
maintennant la cause faut cherher ....
voilà pour ce qui concernne Linux :
Ventilation et temperature
Il existe 2 categories d outils ceux qui utilisent les informations fournies par l ACPI et ceux qui utilisent directement les composants
en charge de la surveillance thermique appelés Sensors
pour + de details voir google
pour l installation de sensors voir gestionnaire le paquet
lm_sensors ou paquet lm_sensors-devel ou meme gnome-applet-sensors
tout depends de la distrib utiliser pour mandriva par exemple :
# urpmi lm_sensors
voila cherche avec google il y a de bon wikis avant de te lancer !!
Comment faire pour être certains que les ventilos fonctionnent correctement?
J'avais déjà d'installé Sensors et j'ai tapé "sensors-detect" et voilà le résultat mais je ne sais pas vraiement quoi faire avec ça :
This program will help you determine which I2C/SMBus modules you need to
load to use lm_sensors most effectively. You need to have i2c and
lm_sensors installed before running this program.
Also, you need to be `root', or at least have access to the /dev/i2c-*
files, for most things.
If you have patched your kernel and have some drivers built in, you can
safely answer NO if asked to load some modules. In this case, things may
seem a bit confusing, but they will still work.
It is generally safe and recommended to accept the default answers to all
questions, unless you know what you're doing.
We can start with probing for (PCI) I2C or SMBus adapters.
You do not need any special privileges for this.
Do you want to probe now? (YES/no): y
Probing for PCI bus adapters...
Use driver `rivatv' for device 01:00.0: RIVA UVTNT2
Probe succesfully concluded.
We will now try to load each adapter module in turn.
Module `rivatv' already loaded.
If you have undetectable or unsupported adapters, you can have them
scanned by manually loading the modules before running this script.
To continue, we need module `i2c-dev' to be loaded.
If it is built-in into your kernel, you can safely skip this.
i2c-dev is already loaded.
We are now going to do the adapter probings. Some adapters may hang halfway
through; we can't really help that. Also, some chips will be double detected;
we choose the one with the highest confidence value in that case.
If you found that the adapter hung after probing a certain address, you can
specify that address to remain unprobed. That often
includes address 0x69 (clock chip).
Some chips are also accessible through the ISA bus. ISA probes are
typically a bit more dangerous, as we have to write to I/O ports to do
this. This is usually safe though.
Do you want to scan the ISA bus? (YES/no): y
Probing for `National Semiconductor LM78'
Trying address 0x0290... Failed!
Probing for `National Semiconductor LM78-J'
Trying address 0x0290... Failed!
Probing for `National Semiconductor LM79'
Trying address 0x0290... Failed!
Probing for `Winbond W83781D'
Trying address 0x0290... Failed!
Probing for `Winbond W83782D'
Trying address 0x0290... Failed!
Probing for `Winbond W83627HF'
Trying address 0x0290... Failed!
Probing for `Winbond W83627EHF'
Trying address 0x0290... Failed!
Probing for `Winbond W83697HF'
Trying address 0x0290... Failed!
Probing for `Silicon Integrated Systems SIS5595'
Trying general detect... Failed!
Probing for `VIA Technologies VT82C686 Integrated Sensors'
Trying general detect... Failed!
Probing for `VIA Technologies VT8231 Integrated Sensors'
Trying general detect... Failed!
Probing for `ITE IT8712F'
Trying address 0x0290... Failed!
Probing for `ITE IT8705F / SiS 950'
Trying address 0x0290... Failed!
Probing for `IPMI BMC KCS'
Trying address 0x0ca0... Failed!
Probing for `IPMI BMC SMIC'
Trying address 0x0ca8... Failed!
Some Super I/O chips may also contain sensors. Super I/O probes are
typically a bit more dangerous, as we have to write to I/O ports to do
this. This is usually safe though.
Do you want to scan for Super I/O sensors? (YES/no): y
Probing for `ITE 8702F Super IO Sensors'
Failed! (0x8284)
Probing for `ITE 8705F Super IO Sensors'
Failed! (0x8284)
Probing for `ITE 8712F Super IO Sensors'
Failed! (0x8284)
Probing for `Nat. Semi. PC87351 Super IO Fan Sensors'
Failed! (0x82)
Probing for `Nat. Semi. PC87360 Super IO Fan Sensors'
Failed! (0x82)
Probing for `Nat. Semi. PC87363 Super IO Fan Sensors'
Failed! (0x82)
Probing for `Nat. Semi. PC87364 Super IO Fan Sensors'
Failed! (0x82)
Probing for `Nat. Semi. PC87365 Super IO Fan Sensors'
Failed! (0x82)
Probing for `Nat. Semi. PC87365 Super IO Voltage Sensors'
Failed! (0x82)
Probing for `Nat. Semi. PC87365 Super IO Thermal Sensors'
Failed! (0x82)
Probing for `Nat. Semi. PC87366 Super IO Fan Sensors'
Failed! (0x82)
Probing for `Nat. Semi. PC87366 Super IO Voltage Sensors'
Failed! (0x82)
Probing for `Nat. Semi. PC87366 Super IO Thermal Sensors'
Failed! (0x82)
Probing for `Nat. Semi. PC87372 Super IO Fan Sensors'
Failed! (0x82)
Probing for `Nat. Semi. PC87373 Super IO Fan Sensors'
Failed! (0x82)
Probing for `Nat. Semi. PC87591 Super IO'
Failed! (0x82)
Probing for `Nat. Semi. PC87371 Super IO'
Failed! (0x82)
Probing for `Nat. Semi. PC97371 Super IO'
Failed! (0x82)
Probing for `Nat. Semi. PC8739x Super IO'
Failed! (0x82)
Probing for `Nat. Semi. PC8741x Super IO'
Failed! (0x82)
Probing for `SMSC 47B27x Super IO Fan Sensors'
Failed! (0x82)
Probing for `SMSC 47M10x/13x Super IO Fan Sensors'
Failed! (0x82)
Probing for `SMSC 47M14x Super IO Fan Sensors'
Failed! (0x82)
Probing for `SMSC 47M15x/192 Super IO Fan Sensors'
Failed! (0x82)
Probing for `SMSC 47S42x Super IO Fan Sensors'
Failed! (0x82)
Probing for `SMSC 47S45x Super IO Fan Sensors'
Failed! (0x82)
Probing for `SMSC 47M172 Super IO'
Failed! (0x82)
Probing for `SMSC LPC47B397-NC Super IO'
Failed! (0x82)
Probing for `VT1211 Super IO Sensors'
Failed! (0x82)
Probing for `Winbond W83627HF Super IO Sensors'
Failed! (0x82)
Probing for `Winbond W83627THF Super IO Sensors'
Success... found at address 0x0290
Probing for `Winbond W83637HF Super IO Sensors'
Failed! (0x82)
Probing for `Winbond W83697HF Super IO Sensors'
Failed! (0x82)
Probing for `Winbond W83697SF/UF Super IO PWM'
Failed! (0x82)
Probing for `Winbond W83L517D Super IO'
Failed! (0x82)
Probing for `Winbond W83627EHF Super IO Sensors'
Failed! (0x8284)
Do you want to scan for secondary Super I/O sensors? (YES/no): y
Probing for `ITE 8702F Super IO Sensors'
Failed! (skipping family)
Probing for `Nat. Semi. PC87351 Super IO Fan Sensors'
Failed! (skipping family)
Probing for `SMSC 47B27x Super IO Fan Sensors'
Failed! (skipping family)
Probing for `VT1211 Super IO Sensors'
Failed! (skipping family)
Probing for `Winbond W83627EHF Super IO Sensors'
Failed! (skipping family)
Now follows a summary of the probes I have just done.
Just press ENTER to continue:
Driver `w83627hf' (should be inserted):
Detects correctly:
* ISA bus address 0x0290 (Busdriver `i2c-isa')
Chip `Winbond W83627THF Super IO Sensors' (confidence: 9)
I will now generate the commands needed to load the I2C modules.
Sometimes, a chip is available both through the ISA bus and an I2C bus.
ISA bus access is faster, but you need to load an additional driver module
for it. If you have the choice, do you want to use the ISA bus or the
I2C/SMBus (ISA/smbus)? i
To make the sensors modules behave correctly, add these lines to
/etc/modules.conf:
#----cut here----
# I2C module options
alias char-major-89 i2c-dev
#----cut here----
To load everything that is needed, add this to some /etc/rc* file:
#----cut here----
# I2C adapter drivers
modprobe i2c-isa
# I2C chip drivers
modprobe w83627hf
# sleep 2 # optional
/usr/bin/sensors -s # recommended
#----cut here----
WARNING! If you have some things built into your kernel, the list above
will contain too many modules. Skip the appropriate ones! You really should
try these commands right now to make sure everything is working properly.
Monitoring programs won't work until it's done.
Do you want to generate /etc/sysconfig/lm_sensors? (YES/no): y
Copy prog/init/lm_sensors.init to /etc/rc.d/init.d/lm_sensors
for initialization at boot time.
J'avais déjà d'installé Sensors et j'ai tapé "sensors-detect" et voilà le résultat mais je ne sais pas vraiement quoi faire avec ça :
This program will help you determine which I2C/SMBus modules you need to
load to use lm_sensors most effectively. You need to have i2c and
lm_sensors installed before running this program.
Also, you need to be `root', or at least have access to the /dev/i2c-*
files, for most things.
If you have patched your kernel and have some drivers built in, you can
safely answer NO if asked to load some modules. In this case, things may
seem a bit confusing, but they will still work.
It is generally safe and recommended to accept the default answers to all
questions, unless you know what you're doing.
We can start with probing for (PCI) I2C or SMBus adapters.
You do not need any special privileges for this.
Do you want to probe now? (YES/no): y
Probing for PCI bus adapters...
Use driver `rivatv' for device 01:00.0: RIVA UVTNT2
Probe succesfully concluded.
We will now try to load each adapter module in turn.
Module `rivatv' already loaded.
If you have undetectable or unsupported adapters, you can have them
scanned by manually loading the modules before running this script.
To continue, we need module `i2c-dev' to be loaded.
If it is built-in into your kernel, you can safely skip this.
i2c-dev is already loaded.
We are now going to do the adapter probings. Some adapters may hang halfway
through; we can't really help that. Also, some chips will be double detected;
we choose the one with the highest confidence value in that case.
If you found that the adapter hung after probing a certain address, you can
specify that address to remain unprobed. That often
includes address 0x69 (clock chip).
Some chips are also accessible through the ISA bus. ISA probes are
typically a bit more dangerous, as we have to write to I/O ports to do
this. This is usually safe though.
Do you want to scan the ISA bus? (YES/no): y
Probing for `National Semiconductor LM78'
Trying address 0x0290... Failed!
Probing for `National Semiconductor LM78-J'
Trying address 0x0290... Failed!
Probing for `National Semiconductor LM79'
Trying address 0x0290... Failed!
Probing for `Winbond W83781D'
Trying address 0x0290... Failed!
Probing for `Winbond W83782D'
Trying address 0x0290... Failed!
Probing for `Winbond W83627HF'
Trying address 0x0290... Failed!
Probing for `Winbond W83627EHF'
Trying address 0x0290... Failed!
Probing for `Winbond W83697HF'
Trying address 0x0290... Failed!
Probing for `Silicon Integrated Systems SIS5595'
Trying general detect... Failed!
Probing for `VIA Technologies VT82C686 Integrated Sensors'
Trying general detect... Failed!
Probing for `VIA Technologies VT8231 Integrated Sensors'
Trying general detect... Failed!
Probing for `ITE IT8712F'
Trying address 0x0290... Failed!
Probing for `ITE IT8705F / SiS 950'
Trying address 0x0290... Failed!
Probing for `IPMI BMC KCS'
Trying address 0x0ca0... Failed!
Probing for `IPMI BMC SMIC'
Trying address 0x0ca8... Failed!
Some Super I/O chips may also contain sensors. Super I/O probes are
typically a bit more dangerous, as we have to write to I/O ports to do
this. This is usually safe though.
Do you want to scan for Super I/O sensors? (YES/no): y
Probing for `ITE 8702F Super IO Sensors'
Failed! (0x8284)
Probing for `ITE 8705F Super IO Sensors'
Failed! (0x8284)
Probing for `ITE 8712F Super IO Sensors'
Failed! (0x8284)
Probing for `Nat. Semi. PC87351 Super IO Fan Sensors'
Failed! (0x82)
Probing for `Nat. Semi. PC87360 Super IO Fan Sensors'
Failed! (0x82)
Probing for `Nat. Semi. PC87363 Super IO Fan Sensors'
Failed! (0x82)
Probing for `Nat. Semi. PC87364 Super IO Fan Sensors'
Failed! (0x82)
Probing for `Nat. Semi. PC87365 Super IO Fan Sensors'
Failed! (0x82)
Probing for `Nat. Semi. PC87365 Super IO Voltage Sensors'
Failed! (0x82)
Probing for `Nat. Semi. PC87365 Super IO Thermal Sensors'
Failed! (0x82)
Probing for `Nat. Semi. PC87366 Super IO Fan Sensors'
Failed! (0x82)
Probing for `Nat. Semi. PC87366 Super IO Voltage Sensors'
Failed! (0x82)
Probing for `Nat. Semi. PC87366 Super IO Thermal Sensors'
Failed! (0x82)
Probing for `Nat. Semi. PC87372 Super IO Fan Sensors'
Failed! (0x82)
Probing for `Nat. Semi. PC87373 Super IO Fan Sensors'
Failed! (0x82)
Probing for `Nat. Semi. PC87591 Super IO'
Failed! (0x82)
Probing for `Nat. Semi. PC87371 Super IO'
Failed! (0x82)
Probing for `Nat. Semi. PC97371 Super IO'
Failed! (0x82)
Probing for `Nat. Semi. PC8739x Super IO'
Failed! (0x82)
Probing for `Nat. Semi. PC8741x Super IO'
Failed! (0x82)
Probing for `SMSC 47B27x Super IO Fan Sensors'
Failed! (0x82)
Probing for `SMSC 47M10x/13x Super IO Fan Sensors'
Failed! (0x82)
Probing for `SMSC 47M14x Super IO Fan Sensors'
Failed! (0x82)
Probing for `SMSC 47M15x/192 Super IO Fan Sensors'
Failed! (0x82)
Probing for `SMSC 47S42x Super IO Fan Sensors'
Failed! (0x82)
Probing for `SMSC 47S45x Super IO Fan Sensors'
Failed! (0x82)
Probing for `SMSC 47M172 Super IO'
Failed! (0x82)
Probing for `SMSC LPC47B397-NC Super IO'
Failed! (0x82)
Probing for `VT1211 Super IO Sensors'
Failed! (0x82)
Probing for `Winbond W83627HF Super IO Sensors'
Failed! (0x82)
Probing for `Winbond W83627THF Super IO Sensors'
Success... found at address 0x0290
Probing for `Winbond W83637HF Super IO Sensors'
Failed! (0x82)
Probing for `Winbond W83697HF Super IO Sensors'
Failed! (0x82)
Probing for `Winbond W83697SF/UF Super IO PWM'
Failed! (0x82)
Probing for `Winbond W83L517D Super IO'
Failed! (0x82)
Probing for `Winbond W83627EHF Super IO Sensors'
Failed! (0x8284)
Do you want to scan for secondary Super I/O sensors? (YES/no): y
Probing for `ITE 8702F Super IO Sensors'
Failed! (skipping family)
Probing for `Nat. Semi. PC87351 Super IO Fan Sensors'
Failed! (skipping family)
Probing for `SMSC 47B27x Super IO Fan Sensors'
Failed! (skipping family)
Probing for `VT1211 Super IO Sensors'
Failed! (skipping family)
Probing for `Winbond W83627EHF Super IO Sensors'
Failed! (skipping family)
Now follows a summary of the probes I have just done.
Just press ENTER to continue:
Driver `w83627hf' (should be inserted):
Detects correctly:
* ISA bus address 0x0290 (Busdriver `i2c-isa')
Chip `Winbond W83627THF Super IO Sensors' (confidence: 9)
I will now generate the commands needed to load the I2C modules.
Sometimes, a chip is available both through the ISA bus and an I2C bus.
ISA bus access is faster, but you need to load an additional driver module
for it. If you have the choice, do you want to use the ISA bus or the
I2C/SMBus (ISA/smbus)? i
To make the sensors modules behave correctly, add these lines to
/etc/modules.conf:
#----cut here----
# I2C module options
alias char-major-89 i2c-dev
#----cut here----
To load everything that is needed, add this to some /etc/rc* file:
#----cut here----
# I2C adapter drivers
modprobe i2c-isa
# I2C chip drivers
modprobe w83627hf
# sleep 2 # optional
/usr/bin/sensors -s # recommended
#----cut here----
WARNING! If you have some things built into your kernel, the list above
will contain too many modules. Skip the appropriate ones! You really should
try these commands right now to make sure everything is working properly.
Monitoring programs won't work until it's done.
Do you want to generate /etc/sysconfig/lm_sensors? (YES/no): y
Copy prog/init/lm_sensors.init to /etc/rc.d/init.d/lm_sensors
for initialization at boot time.
salut
ouvre une console places-toi comme root et tape se qui suit :
# modprobe i2c-isa
# modprobe w83627hf
si tu as une erreur [ modprobe w83627hf ] tu tapes alors se qui suit
# modprobe w83781d
et relance ton scan ==>>
ouvre une console places-toi comme root et tape se qui suit :
# modprobe i2c-isa
# modprobe w83627hf
si tu as une erreur [ modprobe w83627hf ] tu tapes alors se qui suit
# modprobe w83781d
et relance ton scan ==>>
Ok, voici le résultat après avoir fait ce que tu m'as indiqué mais je n'y comprend rien à tout ça:
This program will help you determine which I2C/SMBus modules you need to
load to use lm_sensors most effectively. You need to have i2c and
lm_sensors installed before running this program.
Also, you need to be `root', or at least have access to the /dev/i2c-*
files, for most things.
If you have patched your kernel and have some drivers built in, you can
safely answer NO if asked to load some modules. In this case, things may
seem a bit confusing, but they will still work.
It is generally safe and recommended to accept the default answers to all
questions, unless you know what you're doing.
We can start with probing for (PCI) I2C or SMBus adapters.
You do not need any special privileges for this.
Do you want to probe now? (YES/no): y
Probing for PCI bus adapters...
Use driver `rivatv' for device 01:00.0: RIVA UVTNT2
Probe succesfully concluded.
We will now try to load each adapter module in turn.
Load `rivatv' (say NO if built into your kernel)? (YES/no): y
Module loaded succesfully.
If you have undetectable or unsupported adapters, you can have them
scanned by manually loading the modules before running this script.
To continue, we need module `i2c-dev' to be loaded.
If it is built-in into your kernel, you can safely skip this.
i2c-dev is not loaded. Do you want to load it now? (YES/no): y
Module loaded succesfully.
We are now going to do the adapter probings. Some adapters may hang halfway
through; we can't really help that. Also, some chips will be double detected;
we choose the one with the highest confidence value in that case.
If you found that the adapter hung after probing a certain address, you can
specify that address to remain unprobed. That often
includes address 0x69 (clock chip).
Some chips are also accessible through the ISA bus. ISA probes are
typically a bit more dangerous, as we have to write to I/O ports to do
this. This is usually safe though.
Do you want to scan the ISA bus? (YES/no): y
Probing for `National Semiconductor LM78'
Trying address 0x0290... Failed!
Probing for `National Semiconductor LM78-J'
Trying address 0x0290... Failed!
Probing for `National Semiconductor LM79'
Trying address 0x0290... Failed!
Probing for `Winbond W83781D'
Trying address 0x0290... Failed!
Probing for `Winbond W83782D'
Trying address 0x0290... Failed!
Probing for `Winbond W83627HF'
Trying address 0x0290... Failed!
Probing for `Winbond W83627EHF'
Trying address 0x0290... Failed!
Probing for `Winbond W83697HF'
Trying address 0x0290... Failed!
Probing for `Silicon Integrated Systems SIS5595'
Trying general detect... Failed!
Probing for `VIA Technologies VT82C686 Integrated Sensors'
Trying general detect... Failed!
Probing for `VIA Technologies VT8231 Integrated Sensors'
Trying general detect... Failed!
Probing for `ITE IT8712F'
Trying address 0x0290... Failed!
Probing for `ITE IT8705F / SiS 950'
Trying address 0x0290... Failed!
Probing for `IPMI BMC KCS'
Trying address 0x0ca0... Failed!
Probing for `IPMI BMC SMIC'
Trying address 0x0ca8... Failed!
Some Super I/O chips may also contain sensors. Super I/O probes are
typically a bit more dangerous, as we have to write to I/O ports to do
this. This is usually safe though.
Do you want to scan for Super I/O sensors? (YES/no): y
Probing for `ITE 8702F Super IO Sensors'
Failed! (skipping family)
Probing for `Nat. Semi. PC87351 Super IO Fan Sensors'
Failed! (skipping family)
Probing for `SMSC 47B27x Super IO Fan Sensors'
Failed! (skipping family)
Probing for `VT1211 Super IO Sensors'
Failed! (0x82)
Probing for `Winbond W83627HF Super IO Sensors'
Failed! (0x82)
Probing for `Winbond W83627THF Super IO Sensors'
Success... found at address 0x0290
Probing for `Winbond W83637HF Super IO Sensors'
Failed! (0x82)
Probing for `Winbond W83697HF Super IO Sensors'
Failed! (0x82)
Probing for `Winbond W83697SF/UF Super IO PWM'
Failed! (0x82)
Probing for `Winbond W83L517D Super IO'
Failed! (0x82)
Probing for `Winbond W83627EHF Super IO Sensors'
Failed! (0x8284)
Do you want to scan for secondary Super I/O sensors? (YES/no): y
Probing for `ITE 8702F Super IO Sensors'
Failed! (skipping family)
Probing for `Nat. Semi. PC87351 Super IO Fan Sensors'
Failed! (skipping family)
Probing for `SMSC 47B27x Super IO Fan Sensors'
Failed! (skipping family)
Probing for `VT1211 Super IO Sensors'
Failed! (skipping family)
Probing for `Winbond W83627EHF Super IO Sensors'
Failed! (skipping family)
Now follows a summary of the probes I have just done.
Just press ENTER to continue:
Driver `w83627hf' (should be inserted):
Detects correctly:
* ISA bus address 0x0290 (Busdriver `i2c-isa')
Chip `Winbond W83627THF Super IO Sensors' (confidence: 9)
I will now generate the commands needed to load the I2C modules.
Sometimes, a chip is available both through the ISA bus and an I2C bus.
ISA bus access is faster, but you need to load an additional driver module
for it. If you have the choice, do you want to use the ISA bus or the
I2C/SMBus (ISA/smbus)? i
To make the sensors modules behave correctly, add these lines to
/etc/modules.conf:
#----cut here----
# I2C module options
alias char-major-89 i2c-dev
#----cut here----
To load everything that is needed, add this to some /etc/rc* file:
#----cut here----
# I2C adapter drivers
modprobe i2c-isa
# I2C chip drivers
modprobe w83627hf
# sleep 2 # optional
/usr/bin/sensors -s # recommended
#----cut here----
WARNING! If you have some things built into your kernel, the list above
will contain too many modules. Skip the appropriate ones! You really should
try these commands right now to make sure everything is working properly.
Monitoring programs won't work until it's done.
Do you want to generate /etc/sysconfig/lm_sensors? (YES/no): y
Copy prog/init/lm_sensors.init to /etc/rc.d/init.d/lm_sensors
for initialization at boot time.
Merci
This program will help you determine which I2C/SMBus modules you need to
load to use lm_sensors most effectively. You need to have i2c and
lm_sensors installed before running this program.
Also, you need to be `root', or at least have access to the /dev/i2c-*
files, for most things.
If you have patched your kernel and have some drivers built in, you can
safely answer NO if asked to load some modules. In this case, things may
seem a bit confusing, but they will still work.
It is generally safe and recommended to accept the default answers to all
questions, unless you know what you're doing.
We can start with probing for (PCI) I2C or SMBus adapters.
You do not need any special privileges for this.
Do you want to probe now? (YES/no): y
Probing for PCI bus adapters...
Use driver `rivatv' for device 01:00.0: RIVA UVTNT2
Probe succesfully concluded.
We will now try to load each adapter module in turn.
Load `rivatv' (say NO if built into your kernel)? (YES/no): y
Module loaded succesfully.
If you have undetectable or unsupported adapters, you can have them
scanned by manually loading the modules before running this script.
To continue, we need module `i2c-dev' to be loaded.
If it is built-in into your kernel, you can safely skip this.
i2c-dev is not loaded. Do you want to load it now? (YES/no): y
Module loaded succesfully.
We are now going to do the adapter probings. Some adapters may hang halfway
through; we can't really help that. Also, some chips will be double detected;
we choose the one with the highest confidence value in that case.
If you found that the adapter hung after probing a certain address, you can
specify that address to remain unprobed. That often
includes address 0x69 (clock chip).
Some chips are also accessible through the ISA bus. ISA probes are
typically a bit more dangerous, as we have to write to I/O ports to do
this. This is usually safe though.
Do you want to scan the ISA bus? (YES/no): y
Probing for `National Semiconductor LM78'
Trying address 0x0290... Failed!
Probing for `National Semiconductor LM78-J'
Trying address 0x0290... Failed!
Probing for `National Semiconductor LM79'
Trying address 0x0290... Failed!
Probing for `Winbond W83781D'
Trying address 0x0290... Failed!
Probing for `Winbond W83782D'
Trying address 0x0290... Failed!
Probing for `Winbond W83627HF'
Trying address 0x0290... Failed!
Probing for `Winbond W83627EHF'
Trying address 0x0290... Failed!
Probing for `Winbond W83697HF'
Trying address 0x0290... Failed!
Probing for `Silicon Integrated Systems SIS5595'
Trying general detect... Failed!
Probing for `VIA Technologies VT82C686 Integrated Sensors'
Trying general detect... Failed!
Probing for `VIA Technologies VT8231 Integrated Sensors'
Trying general detect... Failed!
Probing for `ITE IT8712F'
Trying address 0x0290... Failed!
Probing for `ITE IT8705F / SiS 950'
Trying address 0x0290... Failed!
Probing for `IPMI BMC KCS'
Trying address 0x0ca0... Failed!
Probing for `IPMI BMC SMIC'
Trying address 0x0ca8... Failed!
Some Super I/O chips may also contain sensors. Super I/O probes are
typically a bit more dangerous, as we have to write to I/O ports to do
this. This is usually safe though.
Do you want to scan for Super I/O sensors? (YES/no): y
Probing for `ITE 8702F Super IO Sensors'
Failed! (skipping family)
Probing for `Nat. Semi. PC87351 Super IO Fan Sensors'
Failed! (skipping family)
Probing for `SMSC 47B27x Super IO Fan Sensors'
Failed! (skipping family)
Probing for `VT1211 Super IO Sensors'
Failed! (0x82)
Probing for `Winbond W83627HF Super IO Sensors'
Failed! (0x82)
Probing for `Winbond W83627THF Super IO Sensors'
Success... found at address 0x0290
Probing for `Winbond W83637HF Super IO Sensors'
Failed! (0x82)
Probing for `Winbond W83697HF Super IO Sensors'
Failed! (0x82)
Probing for `Winbond W83697SF/UF Super IO PWM'
Failed! (0x82)
Probing for `Winbond W83L517D Super IO'
Failed! (0x82)
Probing for `Winbond W83627EHF Super IO Sensors'
Failed! (0x8284)
Do you want to scan for secondary Super I/O sensors? (YES/no): y
Probing for `ITE 8702F Super IO Sensors'
Failed! (skipping family)
Probing for `Nat. Semi. PC87351 Super IO Fan Sensors'
Failed! (skipping family)
Probing for `SMSC 47B27x Super IO Fan Sensors'
Failed! (skipping family)
Probing for `VT1211 Super IO Sensors'
Failed! (skipping family)
Probing for `Winbond W83627EHF Super IO Sensors'
Failed! (skipping family)
Now follows a summary of the probes I have just done.
Just press ENTER to continue:
Driver `w83627hf' (should be inserted):
Detects correctly:
* ISA bus address 0x0290 (Busdriver `i2c-isa')
Chip `Winbond W83627THF Super IO Sensors' (confidence: 9)
I will now generate the commands needed to load the I2C modules.
Sometimes, a chip is available both through the ISA bus and an I2C bus.
ISA bus access is faster, but you need to load an additional driver module
for it. If you have the choice, do you want to use the ISA bus or the
I2C/SMBus (ISA/smbus)? i
To make the sensors modules behave correctly, add these lines to
/etc/modules.conf:
#----cut here----
# I2C module options
alias char-major-89 i2c-dev
#----cut here----
To load everything that is needed, add this to some /etc/rc* file:
#----cut here----
# I2C adapter drivers
modprobe i2c-isa
# I2C chip drivers
modprobe w83627hf
# sleep 2 # optional
/usr/bin/sensors -s # recommended
#----cut here----
WARNING! If you have some things built into your kernel, the list above
will contain too many modules. Skip the appropriate ones! You really should
try these commands right now to make sure everything is working properly.
Monitoring programs won't work until it's done.
Do you want to generate /etc/sysconfig/lm_sensors? (YES/no): y
Copy prog/init/lm_sensors.init to /etc/rc.d/init.d/lm_sensors
for initialization at boot time.
Merci
salut
c est quoi ta distribution :
je viens de faire un teste à la vite pour voir :
[tufs@localhost ~]$ sensors
w83627hf-isa-0290
Adapter: ISA adapter
VCore 1: +1.46 V (min = +1.46 V, max = +1.60 V)
VCore 2: +1.47 V (min = +1.46 V, max = +1.60 V)
+3.3V: +3.33 V (min = +3.14 V, max = +3.47 V)
+5V: +5.00 V (min = +4.76 V, max = +5.24 V)
+12V: +11.92 V (min = +10.82 V, max = +13.19 V)
-12V: -11.87 V (min = -13.18 V, max = -10.80 V)
-5V: -5.35 V (min = -5.25 V, max = -4.75 V) ALARM
V5SB: +5.54 V (min = +4.76 V, max = +5.24 V) ALARM
VBat: +3.18 V (min = +2.40 V, max = +3.60 V)
fan1: 2721 RPM (min = 1298 RPM, div = 8)
fan2: 0 RPM (min = 42187 RPM, div = 8) ALARM
fan3: 0 RPM (min = -1 RPM, div = 8) ALARM
temp1: +27°C (high = -128°C, hyst = +0°C) sensor = thermistor ALARM
temp2: +33.5°C (high = +100°C, hyst = +95°C) sensor = diode
temp3: +61.5°C (high = +100°C, hyst = +95°C) sensor = thermistor
vid: +1.525 V (VRM Version 9.0)
alarms:
beep_enable:
Sound alarm enabled
[tufs@localhost ~]$
c est quoi ta distribution :
je viens de faire un teste à la vite pour voir :
[tufs@localhost ~]$ sensors
w83627hf-isa-0290
Adapter: ISA adapter
VCore 1: +1.46 V (min = +1.46 V, max = +1.60 V)
VCore 2: +1.47 V (min = +1.46 V, max = +1.60 V)
+3.3V: +3.33 V (min = +3.14 V, max = +3.47 V)
+5V: +5.00 V (min = +4.76 V, max = +5.24 V)
+12V: +11.92 V (min = +10.82 V, max = +13.19 V)
-12V: -11.87 V (min = -13.18 V, max = -10.80 V)
-5V: -5.35 V (min = -5.25 V, max = -4.75 V) ALARM
V5SB: +5.54 V (min = +4.76 V, max = +5.24 V) ALARM
VBat: +3.18 V (min = +2.40 V, max = +3.60 V)
fan1: 2721 RPM (min = 1298 RPM, div = 8)
fan2: 0 RPM (min = 42187 RPM, div = 8) ALARM
fan3: 0 RPM (min = -1 RPM, div = 8) ALARM
temp1: +27°C (high = -128°C, hyst = +0°C) sensor = thermistor ALARM
temp2: +33.5°C (high = +100°C, hyst = +95°C) sensor = diode
temp3: +61.5°C (high = +100°C, hyst = +95°C) sensor = thermistor
vid: +1.525 V (VRM Version 9.0)
alarms:
beep_enable:
Sound alarm enabled
[tufs@localhost ~]$
J'utilise Mandriva 2006.
Ok, je vient de taper "sensors" à la place de "sensors-detect" et voici le résultat:
w83627thf-isa-0290
Adapter: ISA adapter
VCore: +1.44 V (min = +0.70 V, max = +1.87 V)
+12V: +11.73 V (min = +11.86 V, max = +10.64 V) ALARM
+3.3V: +3.30 V (min = +1.17 V, max = +1.02 V) ALARM
+5V: +4.93 V (min = +0.43 V, max = +0.29 V) ALARM
-12V: -14.91 V (min = -14.91 V, max = -14.91 V) ALARM
V5SB: +4.95 V (min = +0.89 V, max = +5.46 V)
VBat: +0.00 V (min = +0.00 V, max = +1.17 V)
fan1: 0 RPM (min = 4218 RPM, div = 32) ALARM
CPU Fan: 0 RPM (min = 337500 RPM, div = 2) ALARM
fan3: 0 RPM (min = 157 RPM, div = 128) ALARM
M/B Temp: +28°C (high = +32°C, hyst = +1°C) sensor = thermistor
CPU Temp: +50.0°C (high = +80°C, hyst = +75°C) sensor = thermistor
temp3: -15.0°C (high = +80°C, hyst = +75°C) sensor = thermistor
vid: +0.275 V (VRM Version 9.0)
alarms:
beep_enable:
Sound alarm enabled
Maintenant je peu voir la température de CPU.
Merci
Ok, je vient de taper "sensors" à la place de "sensors-detect" et voici le résultat:
w83627thf-isa-0290
Adapter: ISA adapter
VCore: +1.44 V (min = +0.70 V, max = +1.87 V)
+12V: +11.73 V (min = +11.86 V, max = +10.64 V) ALARM
+3.3V: +3.30 V (min = +1.17 V, max = +1.02 V) ALARM
+5V: +4.93 V (min = +0.43 V, max = +0.29 V) ALARM
-12V: -14.91 V (min = -14.91 V, max = -14.91 V) ALARM
V5SB: +4.95 V (min = +0.89 V, max = +5.46 V)
VBat: +0.00 V (min = +0.00 V, max = +1.17 V)
fan1: 0 RPM (min = 4218 RPM, div = 32) ALARM
CPU Fan: 0 RPM (min = 337500 RPM, div = 2) ALARM
fan3: 0 RPM (min = 157 RPM, div = 128) ALARM
M/B Temp: +28°C (high = +32°C, hyst = +1°C) sensor = thermistor
CPU Temp: +50.0°C (high = +80°C, hyst = +75°C) sensor = thermistor
temp3: -15.0°C (high = +80°C, hyst = +75°C) sensor = thermistor
vid: +0.275 V (VRM Version 9.0)
alarms:
beep_enable:
Sound alarm enabled
Maintenant je peu voir la température de CPU.
Merci
