setting sensors limits... failled

Antes no me pasaba, pero desde que he estado instalando y desinstalando paquetes para ver cual me daba la temperatura de la máquina, ese mensaje aparece cada vez que ubuntu realiza el test de inicio.
Y no creo que tenga mucha trascencencia, pero ver el "failled" en rojo cada vez que arranco Ubuntu, me deja intranquilo. Y es que parece como que algo que puede fallar, algún día fallará y me dará un susto. Si alguien sabe como puedo hacer que me diga "ok" que me lo cuente. Supongo que es algo de la configuración de la placa madre y el chipset, pero no encuentro como configurarlo.

Imagen de gulkask
+1
0
-1

me pasa clavadito. si encuentro solucion la pego aqui, por cierto has conseguido ver la temperatura? a mi todos los programas me enseñan una temperatura pero no sube ni baja nunca.

+1
0
-1
Imagen de herald_childe
+1
0
-1

escribe en una consola sudo sensors-detect y ves contestando enter a todo

+1
0
-1
Imagen de borxa
+1
0
-1

No i2c device files found. Use prog/mkdev/mkdev.sh to create them.

+1
0
-1
Imagen de Anónimo
+1
0
-1

Me paso lo mismo que a vosotros. En el inicio me pone setting sensors limits failed y al hacer sudo sensors-detect me pone No i2c device files found. Use prog/mkdev/mkdev.sh to create them.

Puede ser que este sea el motivo de un problema que tengo. Mi portátil tiene dos ventiladores y en Windows se gestionan bien, pero con Ubuntu solo se me enciende uno, y si tiene mucha carga el procesador se calienta demasiado y deja de funcionar bien. Si alguien sabe como se controlan los ventiladores que me lo diga porque sino muy tristemente tendré que volverme a windows.

Saludos.

+1
0
-1
Imagen de juano
+1
0
-1

A mí también me pasaba eso, pero he visto por ahí que antes de poner "sudo sensors-detect" hay que escribir el siguiente comando: "sudo modprobe i2c-dev" y luego lo de "sudo sensors-detect" y aceptar todo

+1
0
-1
Imagen de Anónimo
+1
0
-1

ya hice esto "sudo modprobe i2c-dev" y luego lo de "sudo sensors-detect", y aun asi me da el mensaje
No i2c device files found. Use prog/mkdev/mkdev.sh to create them

+1
0
-1
Imagen de Anónimo
+1
0
-1

Pues a mi despues de seguir los pasos anteriores me sale esto y no se por donde cogerlo.

angel@angel678:~$ sudo modprobe i2c-dev
Password:
angel@angel678:~$ sudo sensors-detect
# sensors-detect revision 1.393 (2005/08/30 18:51:18)

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):
Probing for PCI bus adapters...
Use driver `i2c-i801' for device 00:1f.3: Intel 82801EB ICH5
Probe succesfully concluded.

We will now try to load each adapter module in turn.
Load `i2c-i801' (say NO if built into your kernel)? (YES/no):
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 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).

Next adapter: SMBus I801 adapter at 0400
Do you want to scan it? (YES/no/selectively):
Client found at address 0x08
Client found at address 0x44
Probing for `Maxim MAX6633/MAX6634/MAX6635'... Failed!
Client found at address 0x50
Probing for `SPD EEPROM'... Success!
(confidence 8, driver `eeprom')
Probing for `DDC monitor'... Failed!
Probing for `Maxim MAX6900'... Failed!
Client found at address 0x69

Next adapter: NVIDIA I2C Device
Do you want to scan it? (YES/no/selectively):

Next adapter: NVIDIA I2C Device
Do you want to scan it? (YES/no/selectively):

Next adapter: NVIDIA I2C Device
Do you want to scan it? (YES/no/selectively):
Client found at address 0x50
Probing for `SPD EEPROM'... Success!
(confidence 1, driver `eeprom')
Probing for `DDC monitor'... Success!
(confidence 8, driver `eeprom'), other addresses: 0x51 0x52 0x53 0x54 0x55 0x56 0x57
Probing for `Maxim MAX6900'... Failed!

Next adapter: bt848 #0 [sw]
Do you want to scan it? (YES/no/selectively):
Client found at address 0x60
Client found at address 0x61
Probing for `SMBus 2.0 ARP-Capable Device'... Success!
(confidence 1, driver `smbus-arp')

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):
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):
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 W83687THF 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/EHG Super IO Sensors'
Failed! (0x8282)

Do you want to scan for secondary Super I/O sensors? (YES/no):
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/EHG Super IO Sensors'
Failed! (skipping family)

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

Driver `eeprom' (should be inserted):
Detects correctly:
* Bus `SMBus I801 adapter at 0400'
Busdriver `i2c-i801', I2C address 0x50
Chip `SPD EEPROM' (confidence: 8)
* Bus `NVIDIA I2C Device'
Busdriver `UNKNOWN', I2C address 0x50 (and 0x51 0x52 0x53 0x54 0x55 0x56 0x57)
Chip `DDC monitor' (confidence: 8)

Driver `smbus-arp' (should be inserted):
Detects correctly:
* Bus `bt848 #0 [sw]'
Busdriver `UNKNOWN', I2C address 0x61
Chip `SMBus 2.0 ARP-Capable Device' (confidence: 1)

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)?

To make the sensors modules behave correctly, add these lines to
/etc/modules:

#----cut here----
# I2C adapter drivers
i2c-i801
# modprobe unknown adapter bt848 #0 [sw]
# modprobe unknown adapter NVIDIA I2C Device
# modprobe unknown adapter NVIDIA I2C Device
# modprobe unknown adapter NVIDIA I2C Device
i2c-isa
# I2C chip drivers
eeprom
# Warning: the required module smbus-arp is not currently installed on your system.
# For status of 2.6 kernel ports see http://secure.netroedge.com/~lm78/supported.html
# If driver is built-in to the kernel, or unavailable, comment out the following line.
smbus-arp
w83627hf
#----cut here----

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

+1
0
-1