El 16/09/2013 03:02, "Maykel Franco" <maykeldeb...@gmail.com> escribió: > > No sé si os habrá pasado alguna vez, pero no consigo que lm_sensors me > detecte las 4 cpus que tengo. Le hice un sensors-detect: > > root@debian-netbook:# sensors > coretemp-isa-0000 > Adapter: ISA adapter > Core 0: +59.0°C (crit = +100.0°C) > Core 1: +57.0°C (crit = +100.0°C) > > root@debian-netbook:# cat /proc/cpuinfo | grep -i processor > processor : 0 > processor : 1 > processor : 2 > processor : 3 > > > root@debian-netbook:# sensors > coretemp-isa-0000 > Adapter: ISA adapter > Core 0: +59.0°C (crit = +100.0°C) > Core 1: +57.0°C (crit = +100.0°C) > > root@debian-netbook:# cat /proc/cpuinfo | grep -i processor > processor : 0 > processor : 1 > processor : 2 > processor : 3 > root@debian-netbook:# sensors-detect > # sensors-detect revision 6170 (2013-05-20 21:25:22 +0200) > # System: TOSHIBA TOSHIBA NB520 [PLL52E-00E008CE] (laptop) > # Board: TOSHIBA PBU00 > > 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 > AMD Family 12h and 14h thermal sensors... No > AMD Family 15h thermal sensors... No > AMD Family 15h power sensors... No > AMD Family 16h 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): > 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): > 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 82801G ICH7 > Module i2c-dev loaded successfully. > > Next adapter: i915 gmbus ssc (i2c-0) > Do you want to scan it? (yes/NO/selectively): > > Next adapter: i915 gmbus vga (i2c-1) > Do you want to scan it? (yes/NO/selectively): > > Next adapter: i915 gmbus panel (i2c-2) > Do you want to scan it? (yes/NO/selectively): > > Next adapter: i915 gmbus dpc (i2c-3) > Do you want to scan it? (yes/NO/selectively): > > Next adapter: i915 gmbus dpb (i2c-4) > Do you want to scan it? (yes/NO/selectively): > > Next adapter: i915 gmbus dpd (i2c-5) > Do you want to scan it? (yes/NO/selectively): > > Next adapter: SMBus I801 adapter at 18a0 (i2c-6) > Do you want to scan it? (YES/no/selectively): > 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 > > 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 '/etc/init.d/kmod start' > to load them. > > Unloading i2c-dev... OK > Unloading cpuid... OK > > > > > He h estado googleando antes de postear aquí pero lo único que he > visto es que la gente ha tenido que compilar algun fichero, en el > kernel 2.6 > > Saludos. >
Hola, es probable que la CPU tenga 2 núcleos físicos con hyperthreading activo, lo que respondería al motivo por el que ves 4 nucleos, pero sólo 2 tienen sensor de temperatura. Comprueba el modelo de la CPU y busca esto que te indico en ark.intel.com. Sakudos, Javiet Silva > > -- > To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org > Archive: http://lists.debian.org/CAJ2aOA9p9qyKZrSHOv3V6mm-ABé1yquihbkmzr7hvc04_...@mail.gmail.com >
