Imagenes de instalación de las versiones estables para Mageia y OpenMandriva.
OpenMandriva: Mageia (Mageia 9) 20/Agosto/2023 - Anuncio, Descargas.
Blogdrake recomienda descargar las imágenes de instalación (iso) vía torrent para evitar corrupción de datos, aprovechar mejor su ancho de banda y mejorar la difusión de las distribuciones.
Poca duración bateria en portátil Compaq Presario CQ45-118LA
Saludos.
Mi portátil Compaq CQ45-118LA (procesador AMD Athlon X2 dual-core (QL-60), la vida de la batería no he logrado que sea la esperada. Comparando con WinVi$ta, dura una tercera parte (1/3). Cuando tenia instalada la versión 2009.1 de 32 bits, la vida de la batería era la mitad que desde WinVi$ta, cuando sucedió la tercera actualización automática del sistema, la vida de la batería se arregló y era casi igual que desde WinVi$ta. E instalado la versión 2009.1 de 64 bits desde hace un mes y medio y a pesar de las actualizaciones automáticas del sistema, la vida de la batería solo es un tercio (1/3) comparado con WinVi$ta. Hace unas semanas vi en BlogDrake , una posible solución, la apliqué y no funciona, ya que al ejecutar el comando “cpufreq-info”:
[root@real ~]# cpufreq-info
cpufrequtils 005: cpufreq-info (C) Dominik Brodowski 2004-2006
Report errors and bugs to cpufreq@vger.kernel.org, please.
analyzing CPU 0:
no or unknown cpufreq driver is active on this CPU
analyzing CPU 1:
no or unknown cpufreq driver is active on this CPU
[root@real ~]#
Apliqué también lo que vi en esta entrada y nada:”Ventilador de Laptop siempre encendido”
Esto es lo que sale:
[mauricio@real ~]$ su -
Password:
[root@real ~]# sensors-detect
# sensors-detect revision 5569 (2008-12-15 09:36:09 +0100)
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.
We can start with probing for (PCI) I2C or SMBus adapters.
Do you want to probe now? (YES/no): no
As you skipped adapter detection, we will only scan already loaded
adapter modules.
If you have undetectable or unsupported I2C/SMBus 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.
Do you want to load `i2c-dev' now? (YES/no): nno
Well, you will know best.
We are now going to do the I2C/SMBus adapter probings. Some chips may
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.
Next adapter: SMBus PIIX4 adapter at 0b00 (i2c-0)
Do you want to scan it? (YES/no/selectively): no
Some chips are also 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): no
Some Super I/O chips may also contain 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): no
Some south bridges, CPUs or memory controllers may also contain
embedded sensors. Do you want to scan for them? (YES/no): no
Sorry, no sensors were detected.
Either your sensors are not supported, or they are connected to an
I2C or SMBus adapter that is not supported. See doc/FAQ,
doc/lm_sensors-FAQ.html or http://www.lm-sensors.org/wiki/FAQ
(FAQ #4.24.3) for further information.
If you find out what chips are on your board, check
http://www.lm-sensors.org/wiki/Devices for driver status.
[root@real ~]# no
-bash: no: command not found
[root@real ~]# sensors-detect
# sensors-detect revision 5569 (2008-12-15 09:36:09 +0100)
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.
We can start with probing for (PCI) I2C or SMBus adapters.
Do you want to probe now? (YES/no): YES
Probing for PCI bus adapters...
Use driver `i2c-piix4' for device 0000:00:14.0: ATI Technologies Inc SB600 SMBus
We will now try to load each adapter module in turn.
Module `i2c-piix4' already loaded.
If you have undetectable or unsupported I2C/SMBus 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.
Do you want to load `i2c-dev' now? (YES/no): YES
Module loaded successfully.
We are now going to do the I2C/SMBus adapter probings. Some chips may
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.
Next adapter: SMBus PIIX4 adapter at 0b00 (i2c-0)
Do you want to scan it? (YES/no/selectively): YES
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
Client found at address 0x51
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
Some chips are also 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 LM78-J' 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
Probing for `IPMI BMC KCS' at 0xca0... No
Probing for `IPMI BMC SMIC' at 0xca8... No
Some Super I/O chips may also contain 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'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Fintek'... No
Trying family `ITE'... No
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Fintek'... No
Trying family `ITE'... No
Some south bridges, CPUs or memory controllers may also contain
embedded sensors. Do you want to scan for them? (YES/no): YES
Silicon Integrated Systems SIS5595... No
VIA VT82C686 Integrated Sensors... No
VIA VT8231 Integrated Sensors... No
AMD K8 thermal sensors... No
AMD K10 thermal sensors... No
Intel Core family thermal sensor... No
Intel AMB FB-DIMM thermal sensor... No
VIA C7 thermal and voltage sensors... No
Sorry, no sensors were detected.
Either your sensors are not supported, or they are connected to an
I2C or SMBus adapter that is not supported. See doc/FAQ,
doc/lm_sensors-FAQ.html or http://www.lm-sensors.org/wiki/FAQ
(FAQ #4.24.3) for further information.
If you find out what chips are on your board, check
http://www.lm-sensors.org/wiki/Devices for driver status.
[root@real ~]# sensors
No sensors found!
Make sure you loaded all the kernel drivers you need.
Try sensors-detect to find out which these are.
[root@real ~]#
Agradezco mucho sus ayudas.
- Entra a tu cuenta o crea una para poder comentar.
Usuario
# 92717 te cuento, la baja capacidad
te cuento, la baja capacidad de la bateria se debe a que tu sistema esta funcionando al máximo posible.
Sobre el comando cpufreq-info, te avisa que no hay ningun driver controlando las cpu, por lo tanto no puede leer de ellos y trabaja al máximo.
En tu caso (por el procesador que tienes) el modulo a cargar seria powernow-k8
puedes intentarlo como root, desde una consola con
# modprobe powernow-k8y luego de eso ejecutar
$ cpufreq-infoy te dará la info de tus cpu's
deben salir los max y minimos de las frecuencias junto a otros datos (en la linea hardware limits)
ahora.. esos limites llevalos al fichero /etc/conf.d/cpufreq
en min freq y max freq respectivamente, y dejas en governor "ondemand", que en mi opinion es lo ideal para un laptop
luego de eso, vas al MCC y echas a correr cpufreq y le das a la opcion de que parta al inicio
saludos!
espero te sirva
Usuario
# 107470 pregunta
Saludos.
Deseo colocar los valores de:
MIN_FREQ=
MAX_FREQ=
Que se encuentran en el fichero: /etc/sysconfig/cpufreq, cuyo contenido es:
# set cpufreq governor if defined
# possible choices are: ondemand powersave userspace performance
GOVERNOR=ondemand
# minimum frequency
#MIN_FREQ=
# maximum frequency
#MAX_FREQ=
# Uncomment to use acpi-cpufreq as fallback
#USE_ACPI_CPUFREQ=yes
Los valores que me da el comando: cpufreq-info son:
hardware limits: 950 MHz - 1.90 GHz
available frequency steps: 1.90 GHz, 950 MHz
available cpufreq governors: ondemand, userspace, performance
current policy: frequency should be within 950 MHz and 1.90 GHz.
Tengo 2 preguntas en concreto:
Los valores (950.000 y 1900.000, los tomo de la salida del comando: watch grep \"cpu MHz\" /proc/cpuinfo)
Gracias mil por su colaboración.
NOTA: la ruta que Ud da (/etc/conf.d/cpufreq), no se encuentra el fichero.
Mauricio Pacheco M.
Manager Information System
http://www.quantum-ai.tk
Usuario: Mageia2 64 bits
Escritorio: KDE
Registered user #419099
http://linuxcounter.net/
Usuario
# 92720 Powenowd
Como ya te han respondido, tu cpu debe ir siempre a tope por eso la poca duración de la batería. Necesitas alguna solución para hacer uso de la capacidad de las cpus de AMD (cool and quiet) de regular su velocidad y consumo dependiendo de la necesidad de cada momento con lo que aumentas la duración de la batería en un uso normal del portátil (navegar, redactar...) y menor ruido al tener menor calentamiento y menor consumo.
Mi solución fue:
urpmi powenowd
Te instala Powenow Daemon que en mi portatil con cpu AMD funciona de maravilla. Después puedes poner el plasmoide (si usas kde4) del monitor de batería en panel de herramientas o donde quieras y con un simple clik puedes cambiar el perfil de energía (prefomance, powersave,...).
Usuario
# 92919 probaré
No tengo internet, por lo tanto hasta hoy acceso. Les cuento luego como me fue.
Gracias]!!!
NOTA:
Hasta ahora el asunto va así:
[root@real ~]# modprobe powernow-k8
[root@real ~]# cpufreq-info
cpufrequtils 005: cpufreq-info (C) Dominik Brodowski 2004-2006
Report errors and bugs to cpufreq@vger.kernel.org, please.
analyzing CPU 0:
driver: powernow-k8
CPUs which need to switch frequency at the same time: 0
hardware limits: 950 MHz - 1.90 GHz
available frequency steps: 1.90 GHz, 950 MHz
available cpufreq governors: userspace, performance
current policy: frequency should be within 950 MHz and 1.90 GHz.
The governor "performance" may decide which speed to use
within this range.
current CPU frequency is 1.90 GHz (asserted by call to hardware).
analyzing CPU 1:
driver: powernow-k8
CPUs which need to switch frequency at the same time: 1
hardware limits: 950 MHz - 1.90 GHz
available frequency steps: 1.90 GHz, 950 MHz
available cpufreq governors: userspace, performance
current policy: frequency should be within 950 MHz and 1.90 GHz.
The governor "performance" may decide which speed to use
within this range.
current CPU frequency is 1.90 GHz (asserted by call to hardware).
[root@real ~]#
Mauricio Pacheco M.
Manager Information System
http://www.informaticamp.tk
Registered user #419099
http://counter.li.org/
Mauricio Pacheco M.
Manager Information System
http://www.quantum-ai.tk
Usuario: Mageia2 64 bits
Escritorio: KDE
Registered user #419099
http://linuxcounter.net/
Usuario
# 94873 Lo que he hecho
Hasta ahora ninguno supera la hora con batería. Qué debo hacer para que la mejor opción quede funcionando cada vez que arranque le pc?. Las pruebas que he hecho son las siguientes:
Lo que he hecho:
desinstale cpufreq 1.0 noarch
instalé cpufreqd 2.3.4 x86_64
se instaló además lib64cpufreqd 2.3.4 x86_64
se encontraban instalados:
cpufrequtils 005 x86_64
lib64cpufreq0 005 x86_64
Resultado:
[mauricio@real ~]$ su -
Password:
[root@real ~]# cpufreq-info
cpufrequtils 005: cpufreq-info (C) Dominik Brodowski 2004-2006
Report errors and bugs to cpufreq@vger.kernel.org, please.
analyzing CPU 0:
no or unknown cpufreq driver is active on this CPU
analyzing CPU 1:
no or unknown cpufreq driver is active on this CPU
[root@real ~]# cpufreq-set
At least one parameter out of -f/--freq, -d/--min, -u/--max, and
-g/--governor must be passed
[root@real ~]# modprobe powernow-k8
[root@real ~]# cpufreq-info
cpufrequtils 005: cpufreq-info (C) Dominik Brodowski 2004-2006
Report errors and bugs to cpufreq@vger.kernel.org, please.
analyzing CPU 0:
driver: powernow-k8
CPUs which need to switch frequency at the same time: 0
hardware limits: 950 MHz - 1.90 GHz
available frequency steps: 1.90 GHz, 950 MHz
available cpufreq governors: userspace, performance
current policy: frequency should be within 950 MHz and 1.90 GHz.
The governor "performance" may decide which speed to use
within this range.
current CPU frequency is 1.90 GHz (asserted by call to hardware).
analyzing CPU 1:
driver: powernow-k8
CPUs which need to switch frequency at the same time: 1
hardware limits: 950 MHz - 1.90 GHz
available frequency steps: 1.90 GHz, 950 MHz
available cpufreq governors: userspace, performance
current policy: frequency should be within 950 MHz and 1.90 GHz.
The governor "performance" may decide which speed to use
within this range.
current CPU frequency is 1.90 GHz (asserted by call to hardware).
[root@real ~]#
Después de estos cambios, reinicie el sistema, al ejecutar el comando:
cpufreq-info:
[root@real ~]# cpufreq-info
cpufrequtils 005: cpufreq-info (C) Dominik Brodowski 2004-2006
Report errors and bugs to cpufreq@vger.kernel.org, please.
analyzing CPU 0:
no or unknown cpufreq driver is active on this CPU
analyzing CPU 1:
no or unknown cpufreq driver is active on this CPU
De modo que a ejecutar de nuevo el comando:
[root@real ~]# modprobe powernow-k8
[root@real ~]# cpufreq-info
cpufrequtils 005: cpufreq-info (C) Dominik Brodowski 2004-2006
Report errors and bugs to cpufreq@vger.kernel.org, please.
analyzing CPU 0:
driver: powernow-k8
CPUs which need to switch frequency at the same time: 0
hardware limits: 950 MHz - 1.90 GHz
available frequency steps: 1.90 GHz, 950 MHz
available cpufreq governors: userspace, performance
current policy: frequency should be within 950 MHz and 1.90 GHz.
The governor "performance" may decide which speed to use
within this range.
current CPU frequency is 1.90 GHz (asserted by call to hardware).
analyzing CPU 1:
driver: powernow-k8
CPUs which need to switch frequency at the same time: 1
hardware limits: 950 MHz - 1.90 GHz
available frequency steps: 1.90 GHz, 950 MHz
available cpufreq governors: userspace, performance
current policy: frequency should be within 950 MHz and 1.90 GHz.
The governor "performance" may decide which speed to use
within this range.
current CPU frequency is 1.90 GHz (asserted by call to hardware).
Fui al “Centro de Control de Mandriva” y en los servicios del sistema, no arrancó el servicio “cpufreqd”, el cual esta activado para que arranque al inicio, por lo tanto lo arranque manualmente
Desconecté el cable de energía y ejecute de nuevo el comando:
[root@real ~]# cpufreq-info
cpufrequtils 005: cpufreq-info (C) Dominik Brodowski 2004-2006
Report errors and bugs to cpufreq@vger.kernel.org, please.
analyzing CPU 0:
driver: powernow-k8
CPUs which need to switch frequency at the same time: 0
hardware limits: 950 MHz - 1.90 GHz
available frequency steps: 1.90 GHz, 950 MHz
available cpufreq governors: ondemand, userspace, performance
current policy: frequency should be within 950 MHz and 1.90 GHz.
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 950 MHz (asserted by call to hardware).
analyzing CPU 1:
driver: powernow-k8
CPUs which need to switch frequency at the same time: 1
hardware limits: 950 MHz - 1.90 GHz
available frequency steps: 1.90 GHz, 950 MHz
available cpufreq governors: ondemand, userspace, performance
current policy: frequency should be within 950 MHz and 1.90 GHz.
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 950 MHz (asserted by call to hardware).
Por lo cual bajo la frecuencia de 1.90 Ghz a 950 Mhz, solo duro 1 minuto y volvió a los 1.90 Ghz, 12 minutos después regreso a los 950 Mhz, en el administrador de energía el perfil dice que está en “powersave”. Han transcurrido 20 minutos desde que desconecté el cable de poder y ya ha consumido el 25%. Han transcurrido 30 minutos a consumido 55%, la frecuencia sigue en 950 Mhz. Aviso “carga de bateria a alcanzado el nivel bajo” han transcurrido 38 minutos, ha consumido el 75%, pasó a “Aggressive Powersave”, está trabajando en 950 Mhz. Nivel de alerta a los 41 minutos ha consumido el 89% pasó a “Xtreme powersave”. Batería en 5% a los 44 minutos. En 0% a los 45 minutos. Se apago a los
Antes que lo olvide, me dices que la info de max y mín, la lleve a la carpeta: /etc/conf.d/cpufreq. Tal vez se debe a que el Mandriva que tengo instalado es de 64bits y no de 32 bits.
[mauricio@real ~]$ su -
Password:
[root@real ~]# cpufreq-info
cpufrequtils 005: cpufreq-info (C) Dominik Brodowski 2004-2006
Report errors and bugs to cpufreq@vger.kernel.org, please.
analyzing CPU 0:
no or unknown cpufreq driver is active on this CPU
analyzing CPU 1:
no or unknown cpufreq driver is active on this CPU
[root@real ~]# cpufreq-set
At least one parameter out of -f/--freq, -d/--min, -u/--max, and
-g/--governor must be passed
[root@real ~]# modprobe powernow-k8
[root@real ~]# cpufreq-info
cpufrequtils 005: cpufreq-info (C) Dominik Brodowski 2004-2006
Report errors and bugs to cpufreq@vger.kernel.org, please.
analyzing CPU 0:
driver: powernow-k8
CPUs which need to switch frequency at the same time: 0
hardware limits: 950 MHz - 1.90 GHz
available frequency steps: 1.90 GHz, 950 MHz
available cpufreq governors: userspace, performance
current policy: frequency should be within 950 MHz and 1.90 GHz.
The governor "performance" may decide which speed to use
within this range.
current CPU frequency is 1.90 GHz (asserted by call to hardware).
analyzing CPU 1:
driver: powernow-k8
CPUs which need to switch frequency at the same time: 1
hardware limits: 950 MHz - 1.90 GHz
available frequency steps: 1.90 GHz, 950 MHz
available cpufreq governors: userspace, performance
current policy: frequency should be within 950 MHz and 1.90 GHz.
The governor "performance" may decide which speed to use
within this range.
current CPU frequency is 1.90 GHz (asserted by call to hardware).
[root@real ~]# cpufreq-set
At least one parameter out of -f/--freq, -d/--min, -u/--max, and
-g/--governor must be passed
[root@real ~]# cpufreq-info
cpufrequtils 005: cpufreq-info (C) Dominik Brodowski 2004-2006
Report errors and bugs to cpufreq@vger.kernel.org, please.
analyzing CPU 0:
driver: powernow-k8
CPUs which need to switch frequency at the same time: 0
hardware limits: 950 MHz - 1.90 GHz
available frequency steps: 1.90 GHz, 950 MHz
available cpufreq governors: userspace, performance
current policy: frequency should be within 1.90 GHz and 1.90 GHz.
The governor "performance" may decide which speed to use
within this range.
current CPU frequency is 1.90 GHz (asserted by call to hardware).
analyzing CPU 1:
driver: powernow-k8
CPUs which need to switch frequency at the same time: 1
hardware limits: 950 MHz - 1.90 GHz
available frequency steps: 1.90 GHz, 950 MHz
available cpufreq governors: userspace, performance
current policy: frequency should be within 1.90 GHz and 1.90 GHz.
The governor "performance" may decide which speed to use
within this range.
current CPU frequency is 1.90 GHz (asserted by call to hardware).
[root@real ~]# cpufreq-info
cpufrequtils 005: cpufreq-info (C) Dominik Brodowski 2004-2006
Report errors and bugs to cpufreq@vger.kernel.org, please.
analyzing CPU 0:
driver: powernow-k8
CPUs which need to switch frequency at the same time: 0
hardware limits: 950 MHz - 1.90 GHz
available frequency steps: 1.90 GHz, 950 MHz
available cpufreq governors: ondemand, userspace, performance
current policy: frequency should be within 950 MHz and 1.90 GHz.
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 950 MHz (asserted by call to hardware).
analyzing CPU 1:
driver: powernow-k8
CPUs which need to switch frequency at the same time: 1
hardware limits: 950 MHz - 1.90 GHz
available frequency steps: 1.90 GHz, 950 MHz
available cpufreq governors: ondemand, userspace, performance
current policy: frequency should be within 950 MHz and 1.90 GHz.
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 950 MHz (asserted by call to hardware).
[root@real ~]# cpufreq-info
cpufrequtils 005: cpufreq-info (C) Dominik Brodowski 2004-2006
Report errors and bugs to cpufreq@vger.kernel.org, please.
analyzing CPU 0:
driver: powernow-k8
CPUs which need to switch frequency at the same time: 0
hardware limits: 950 MHz - 1.90 GHz
available frequency steps: 1.90 GHz, 950 MHz
available cpufreq governors: ondemand, userspace, performance
current policy: frequency should be within 1.90 GHz and 1.90 GHz.
The governor "performance" may decide which speed to use
within this range.
current CPU frequency is 1.90 GHz (asserted by call to hardware).
analyzing CPU 1:
driver: powernow-k8
CPUs which need to switch frequency at the same time: 1
hardware limits: 950 MHz - 1.90 GHz
available frequency steps: 1.90 GHz, 950 MHz
available cpufreq governors: ondemand, userspace, performance
current policy: frequency should be within 1.90 GHz and 1.90 GHz.
The governor "performance" may decide which speed to use
within this range.
current CPU frequency is 1.90 GHz (asserted by call to hardware).
[root@real ~]# cpufreq-info
cpufrequtils 005: cpufreq-info (C) Dominik Brodowski 2004-2006
Report errors and bugs to cpufreq@vger.kernel.org, please.
analyzing CPU 0:
driver: powernow-k8
CPUs which need to switch frequency at the same time: 0
hardware limits: 950 MHz - 1.90 GHz
available frequency steps: 1.90 GHz, 950 MHz
available cpufreq governors: ondemand, userspace, performance
current policy: frequency should be within 1.90 GHz and 1.90 GHz.
The governor "performance" may decide which speed to use
within this range.
current CPU frequency is 1.90 GHz (asserted by call to hardware).
analyzing CPU 1:
driver: powernow-k8
CPUs which need to switch frequency at the same time: 1
hardware limits: 950 MHz - 1.90 GHz
available frequency steps: 1.90 GHz, 950 MHz
available cpufreq governors: ondemand, userspace, performance
current policy: frequency should be within 1.90 GHz and 1.90 GHz.
The governor "performance" may decide which speed to use
within this range.
current CPU frequency is 1.90 GHz (asserted by call to hardware).
[root@real ~]# cpufreq-info
cpufrequtils 005: cpufreq-info (C) Dominik Brodowski 2004-2006
Report errors and bugs to cpufreq@vger.kernel.org, please.
analyzing CPU 0:
driver: powernow-k8
CPUs which need to switch frequency at the same time: 0
hardware limits: 950 MHz - 1.90 GHz
available frequency steps: 1.90 GHz, 950 MHz
available cpufreq governors: ondemand, userspace, performance
current policy: frequency should be within 950 MHz and 1.90 GHz.
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 950 MHz (asserted by call to hardware).
analyzing CPU 1:
driver: powernow-k8
CPUs which need to switch frequency at the same time: 1
hardware limits: 950 MHz - 1.90 GHz
available frequency steps: 1.90 GHz, 950 MHz
available cpufreq governors: ondemand, userspace, performance
current policy: frequency should be within 950 MHz and 1.90 GHz.
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 950 MHz (asserted by call to hardware).
[root@real ~]# cpufreq-info
cpufrequtils 005: cpufreq-info (C) Dominik Brodowski 2004-2006
Report errors and bugs to cpufreq@vger.kernel.org, please.
analyzing CPU 0:
driver: powernow-k8
CPUs which need to switch frequency at the same time: 0
hardware limits: 950 MHz - 1.90 GHz
available frequency steps: 1.90 GHz, 950 MHz
available cpufreq governors: ondemand, userspace, performance
current policy: frequency should be within 950 MHz and 1.90 GHz.
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 950 MHz (asserted by call to hardware).
analyzing CPU 1:
driver: powernow-k8
CPUs which need to switch frequency at the same time: 1
hardware limits: 950 MHz - 1.90 GHz
available frequency steps: 1.90 GHz, 950 MHz
available cpufreq governors: ondemand, userspace, performance
current policy: frequency should be within 950 MHz and 1.90 GHz.
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 950 MHz (asserted by call to hardware).
[root@real ~]# cpufreq-info
cpufrequtils 005: cpufreq-info (C) Dominik Brodowski 2004-2006
Report errors and bugs to cpufreq@vger.kernel.org, please.
analyzing CPU 0:
driver: powernow-k8
CPUs which need to switch frequency at the same time: 0
hardware limits: 950 MHz - 1.90 GHz
available frequency steps: 1.90 GHz, 950 MHz
available cpufreq governors: ondemand, userspace, performance
current policy: frequency should be within 950 MHz and 1.90 GHz.
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 950 MHz (asserted by call to hardware).
analyzing CPU 1:
driver: powernow-k8
CPUs which need to switch frequency at the same time: 1
hardware limits: 950 MHz - 1.90 GHz
available frequency steps: 1.90 GHz, 950 MHz
available cpufreq governors: ondemand, userspace, performance
current policy: frequency should be within 950 MHz and 1.90 GHz.
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 950 MHz (asserted by call to hardware).
[root@real ~]# cpufreq-info
cpufrequtils 005: cpufreq-info (C) Dominik Brodowski 2004-2006
Report errors and bugs to cpufreq@vger.kernel.org, please.
analyzing CPU 0:
driver: powernow-k8
CPUs which need to switch frequency at the same time: 0
hardware limits: 950 MHz - 1.90 GHz
available frequency steps: 1.90 GHz, 950 MHz
available cpufreq governors: powersave, ondemand, userspace, performance
current policy: frequency should be within 950 MHz and 950 MHz.
The governor "powersave" may decide which speed to use
within this range.
current CPU frequency is 950 MHz (asserted by call to hardware).
analyzing CPU 1:
driver: powernow-k8
CPUs which need to switch frequency at the same time: 1
hardware limits: 950 MHz - 1.90 GHz
available frequency steps: 1.90 GHz, 950 MHz
available cpufreq governors: powersave, ondemand, userspace, performance
current policy: frequency should be within 950 MHz and 950 MHz.
The governor "powersave" may decide which speed to use
within this range.
current CPU frequency is 950 MHz (asserted by call to hardware).
[root@real ~]# cpufreq-info
cpufrequtils 005: cpufreq-info (C) Dominik Brodowski 2004-2006
Report errors and bugs to cpufreq@vger.kernel.org, please.
analyzing CPU 0:
driver: powernow-k8
CPUs which need to switch frequency at the same time: 0
hardware limits: 950 MHz - 1.90 GHz
available frequency steps: 1.90 GHz, 950 MHz
available cpufreq governors: powersave, ondemand, userspace, performance
current policy: frequency should be within 950 MHz and 950 MHz.
The governor "powersave" may decide which speed to use
within this range.
current CPU frequency is 950 MHz (asserted by call to hardware).
analyzing CPU 1:
driver: powernow-k8
CPUs which need to switch frequency at the same time: 1
hardware limits: 950 MHz - 1.90 GHz
available frequency steps: 1.90 GHz, 950 MHz
available cpufreq governors: powersave, ondemand, userspace, performance
current policy: frequency should be within 950 MHz and 950 MHz.
The governor "powersave" may decide which speed to use
within this range.
current CPU frequency is 950 MHz (asserted by call to hardware).
[root@real ~]# cpufreq-info
cpufrequtils 005: cpufreq-info (C) Dominik Brodowski 2004-2006
Report errors and bugs to cpufreq@vger.kernel.org, please.
analyzing CPU 0:
driver: powernow-k8
CPUs which need to switch frequency at the same time: 0
hardware limits: 950 MHz - 1.90 GHz
available frequency steps: 1.90 GHz, 950 MHz
available cpufreq governors: powersave, ondemand, userspace, performance
current policy: frequency should be within 950 MHz and 950 MHz.
The governor "powersave" may decide which speed to use
within this range.
current CPU frequency is 950 MHz (asserted by call to hardware).
analyzing CPU 1:
driver: powernow-k8
CPUs which need to switch frequency at the same time: 1
hardware limits: 950 MHz - 1.90 GHz
available frequency steps: 1.90 GHz, 950 MHz
available cpufreq governors: powersave, ondemand, userspace, performance
current policy: frequency should be within 950 MHz and 950 MHz.
The governor "powersave" may decide which speed to use
within this range.
current CPU frequency is 950 MHz (asserted by call to hardware).
[root@real ~]#
Desinstalé “cpufreq”, al entrar al “Centro de Control Mandriva” luego a “Examinar y configurar el hardware” pidio instalar el “cpufreq”, lo instalé.
Ahora e revisado “Habilitar o deshabilitar los servicios del sistema” hay 2 demonios “cpufreq” arranca y “cpufreqd” no arranca (ambos tienen marcada la opción “al iniciar”).
“cpufreq” no arranca manualmente, al ejecutar por consola como “root”, “cpufreq-info” dice:
[root@real ~]# cpufreq-info
cpufrequtils 005: cpufreq-info (C) Dominik Brodowski 2004-2006
Report errors and bugs to cpufreq@vger.kernel.org, please.
analyzing CPU 0:
no or unknown cpufreq driver is active on this CPU
analyzing CPU 1:
no or unknown cpufreq driver is active on this CPU
[root@real ~]#
al ejecutar el demonio “powernowd” manualmente ya que está marcado para que inicie, no lo hace y salen errores por lo tanto,.primero entrar en consola como usuario “root” y ejecutar “modprobe powernow-k8”, luego ejecutar “cpufreq-set -c 0 -g ondemand”, enseguida ejecutar “cpufreq-set -c 1 -g ondemand”, por ser el procesador Dual-Core. Ahora si al iniciar el demonio “powernowd” lo hace. Después de todo esto al digitar “cpufreq-info” sale la siguiente información; antes de mostrar la información quisiera saber que debo hacer para que este proceso sea automático cada vez que enciendo el portátil, es necesario también arrancar el demonio “cpufreqd”?:
Portátil con cable de energía enchufado:
[root@real ~]# cpufreq-info
cpufrequtils 005: cpufreq-info (C) Dominik Brodowski 2004-2006
Report errors and bugs to cpufreq@vger.kernel.org, please.
analyzing CPU 0:
driver: powernow-k8
CPUs which need to switch frequency at the same time: 0
hardware limits: 950 MHz - 1.90 GHz
available frequency steps: 1.90 GHz, 950 MHz
available cpufreq governors: powersave, ondemand, userspace, performance
current policy: frequency should be within 1.90 GHz and 1.90 GHz.
The governor "powersave" may decide which speed to use
within this range.
current CPU frequency is 1.90 GHz (asserted by call to hardware).
analyzing CPU 1:
driver: powernow-k8
CPUs which need to switch frequency at the same time: 1
hardware limits: 950 MHz - 1.90 GHz
available frequency steps: 1.90 GHz, 950 MHz
available cpufreq governors: powersave, ondemand, userspace, performance
current policy: frequency should be within 1.90 GHz and 1.90 GHz.
The governor "powersave" may decide which speed to use
within this range.
current CPU frequency is 1.90 GHz (asserted by call to hardware).
[root@real ~]#
Portátil sin cable de energía enchufado (con batería):
[root@real ~]# cpufreq-info
cpufrequtils 005: cpufreq-info (C) Dominik Brodowski 2004-2006
Report errors and bugs to cpufreq@vger.kernel.org, please.
analyzing CPU 0:
driver: powernow-k8
CPUs which need to switch frequency at the same time: 0
hardware limits: 950 MHz - 1.90 GHz
available frequency steps: 1.90 GHz, 950 MHz
available cpufreq governors: powersave, ondemand, userspace, performance
current policy: frequency should be within 950 MHz and 950 MHz.
The governor "powersave" may decide which speed to use
within this range.
current CPU frequency is 950 MHz (asserted by call to hardware).
analyzing CPU 1:
driver: powernow-k8
CPUs which need to switch frequency at the same time: 1
hardware limits: 950 MHz - 1.90 GHz
available frequency steps: 1.90 GHz, 950 MHz
available cpufreq governors: powersave, ondemand, userspace, performance
current policy: frequency should be within 950 MHz and 950 MHz.
The governor "powersave" may decide which speed to use
within this range.
current CPU frequency is 950 MHz (asserted by call to hardware).
[root@real ~]#
[root@real ~]# cpufreq-info
cpufrequtils 005: cpufreq-info (C) Dominik Brodowski 2004-2006
Report errors and bugs to cpufreq@vger.kernel.org, please.
analyzing CPU 0:
driver: powernow-k8
CPUs which need to switch frequency at the same time: 0
hardware limits: 950 MHz - 1.90 GHz
available frequency steps: 1.90 GHz, 950 MHz
available cpufreq governors: powersave, ondemand, userspace, performance
current policy: frequency should be within 950 MHz and 1.90 GHz.
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 950 MHz (asserted by call to hardware).
analyzing CPU 1:
driver: powernow-k8
CPUs which need to switch frequency at the same time: 1
hardware limits: 950 MHz - 1.90 GHz
available frequency steps: 1.90 GHz, 950 MHz
available cpufreq governors: powersave, ondemand, userspace, performance
current policy: frequency should be within 950 MHz and 1.90 GHz.
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 950 MHz (asserted by call to hardware).
[root@real ~]#
Solo duró 40 minutos, la mitad del tiempo que en Window$ Vi$ta. :(
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
PRUEBAS:
No arrancar el demonio “cpufreqd”, iniciar “modprobe powernow-k8”, al ejecutar “cpufreq-info” (con corriente de la pared): Temperatura: 70°C-71°C-72°C “es normal esa temperatura? Creo que no”
[root@real ~]# cpufreq-info
cpufrequtils 005: cpufreq-info (C) Dominik Brodowski 2004-2006
Report errors and bugs to cpufreq@vger.kernel.org, please.
analyzing CPU 0:
driver: powernow-k8
CPUs which need to switch frequency at the same time: 0
hardware limits: 950 MHz - 1.90 GHz
available frequency steps: 1.90 GHz, 950 MHz
available cpufreq governors: userspace, performance
current policy: frequency should be within 950 MHz and 1.90 GHz.
The governor "performance" may decide which speed to use
within this range.
current CPU frequency is 1.90 GHz (asserted by call to hardware).
analyzing CPU 1:
driver: powernow-k8
CPUs which need to switch frequency at the same time: 1
hardware limits: 950 MHz - 1.90 GHz
available frequency steps: 1.90 GHz, 950 MHz
available cpufreq governors: userspace, performance
current policy: frequency should be within 950 MHz and 1.90 GHz.
The governor "performance" may decide which speed to use
within this range.
current CPU frequency is 1.90 GHz (asserted by call to hardware).
[root@real ~]#
Activé “cpufreq-set -c 0 -g ondemand” y “cpufreq-set -c 1 -g ondemand”, la temperatura bajo a 62°C-61°C-60°C-66°C:
[root@real ~]# cpufreq-set -c 0 -g ondemand
[root@real ~]# cpufreq-set -c 1 -g ondemand
[root@real ~]#
[root@real ~]# cpufreq-info
cpufrequtils 005: cpufreq-info (C) Dominik Brodowski 2004-2006
Report errors and bugs to cpufreq@vger.kernel.org, please.
analyzing CPU 0:
driver: powernow-k8
CPUs which need to switch frequency at the same time: 0
hardware limits: 950 MHz - 1.90 GHz
available frequency steps: 1.90 GHz, 950 MHz
available cpufreq governors: ondemand, userspace, performance
current policy: frequency should be within 950 MHz and 1.90 GHz.
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 950 MHz (asserted by call to hardware).
analyzing CPU 1:
driver: powernow-k8
CPUs which need to switch frequency at the same time: 1
hardware limits: 950 MHz - 1.90 GHz
available frequency steps: 1.90 GHz, 950 MHz
available cpufreq governors: ondemand, userspace, performance
current policy: frequency should be within 950 MHz and 1.90 GHz.
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 950 MHz (asserted by call to hardware).
[root@real ~]#
Al activar el demonio “powernowd”, (está para que inicie al comienzo y no sucede), el comando “cpufreq-info” dice: (cambio de “governor “ondemand” a “userspace”). Temperatura: 63°C-64°C
[root@real ~]# cpufreq-info
cpufrequtils 005: cpufreq-info (C) Dominik Brodowski 2004-2006
Report errors and bugs to cpufreq@vger.kernel.org, please.
analyzing CPU 0:
driver: powernow-k8
CPUs which need to switch frequency at the same time: 0
hardware limits: 950 MHz - 1.90 GHz
available frequency steps: 1.90 GHz, 950 MHz
available cpufreq governors: ondemand, userspace, performance
current policy: frequency should be within 950 MHz and 1.90 GHz.
The governor "userspace" may decide which speed to use
within this range.
current CPU frequency is 950 MHz (asserted by call to hardware).
analyzing CPU 1:
driver: powernow-k8
CPUs which need to switch frequency at the same time: 1
hardware limits: 950 MHz - 1.90 GHz
available frequency steps: 1.90 GHz, 950 MHz
available cpufreq governors: ondemand, userspace, performance
current policy: frequency should be within 950 MHz and 1.90 GHz.
The governor "userspace" may decide which speed to use
within this range.
current CPU frequency is 950 MHz (asserted by call to hardware).
[root@real ~]#
Ahora probar sin corriente de la pared (con batería), chequear con “cpufreq-info” regularmente y el tiempo de vida de la batería con las distintas opciones.
Activando “modprobe powernow-k8” e iniciando el demonio “powernowd”:
Temperatura: 52°C-53°C-59°C-60°C-61°C- Hora: 1:55-2:31= 36 minutos
[root@real ~]# modprobe powernow-k8
[root@real ~]# cpufreq-info
cpufrequtils 005: cpufreq-info (C) Dominik Brodowski 2004-2006
Report errors and bugs to cpufreq@vger.kernel.org, please.
analyzing CPU 0:
driver: powernow-k8
CPUs which need to switch frequency at the same time: 0
hardware limits: 950 MHz - 1.90 GHz
available frequency steps: 1.90 GHz, 950 MHz
available cpufreq governors: userspace, performance
current policy: frequency should be within 950 MHz and 1.90 GHz.
The governor "userspace" may decide which speed to use
within this range.
current CPU frequency is 950 MHz (asserted by call to hardware).
analyzing CPU 1:
driver: powernow-k8
CPUs which need to switch frequency at the same time: 1
hardware limits: 950 MHz - 1.90 GHz
available frequency steps: 1.90 GHz, 950 MHz
available cpufreq governors: userspace, performance
current policy: frequency should be within 950 MHz and 1.90 GHz.
The governor "userspace" may decide which speed to use
within this range.
current CPU frequency is 950 MHz (asserted by call to hardware).
Ahora lo anterior y activando: “cpufreq-set -c 0 -g ondemand” y “cpufreq-set -c 1 -g ondemand”:
[root@real ~]# cpufreq-set -c 0 -g ondemand
[root@real ~]# cpufreq-set -c 1 -g ondemand
[root@real ~]# cpufreq-info
cpufrequtils 005: cpufreq-info (C) Dominik Brodowski 2004-2006
Report errors and bugs to cpufreq@vger.kernel.org, please.
analyzing CPU 0:
driver: powernow-k8
CPUs which need to switch frequency at the same time: 0
hardware limits: 950 MHz - 1.90 GHz
available frequency steps: 1.90 GHz, 950 MHz
available cpufreq governors: ondemand, userspace, performance
current policy: frequency should be within 950 MHz and 1.90 GHz.
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 950 MHz (asserted by call to hardware).
analyzing CPU 1:
driver: powernow-k8
CPUs which need to switch frequency at the same time: 1
hardware limits: 950 MHz - 1.90 GHz
available frequency steps: 1.90 GHz, 950 MHz
available cpufreq governors: ondemand, userspace, performance
current policy: frequency should be within 950 MHz and 1.90 GHz.
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 950 MHz (asserted by call to hardware).
[root@real ~]#
Temperatura: 63°C-62°C- Hora:13:20-14:02 (5% batería)=42 14:15=55 se apagó.
Otra manera:
Activando “modprobe powernow-k8”, “cpufreq-set -c 0 -g ondemand” y “cpufreq-set -c 1 -g ondemand”
Conectado a la pared, la temperatura baja de 71°C a 60°C
[root@real ~]# modprobe powernow-k8
[root@real ~]# cpufreq-info
cpufrequtils 005: cpufreq-info (C) Dominik Brodowski 2004-2006
Report errors and bugs to cpufreq@vger.kernel.org, please.
analyzing CPU 0:
driver: powernow-k8
CPUs which need to switch frequency at the same time: 0
hardware limits: 950 MHz - 1.90 GHz
available frequency steps: 1.90 GHz, 950 MHz
available cpufreq governors: userspace, performance
current policy: frequency should be within 950 MHz and 1.90 GHz.
The governor "performance" may decide which speed to use
within this range.
current CPU frequency is 1.90 GHz (asserted by call to hardware).
analyzing CPU 1:
driver: powernow-k8
CPUs which need to switch frequency at the same time: 1
hardware limits: 950 MHz - 1.90 GHz
available frequency steps: 1.90 GHz, 950 MHz
available cpufreq governors: userspace, performance
current policy: frequency should be within 950 MHz and 1.90 GHz.
The governor "performance" may decide which speed to use
within this range.
current CPU frequency is 1.90 GHz (asserted by call to hardware).
[root@real ~]# cpufreq-set -c 0 -g ondemand
[root@real ~]# cpufreq-set -c 1 -g ondemand
[root@real ~]# cpufreq-info
cpufrequtils 005: cpufreq-info (C) Dominik Brodowski 2004-2006
Report errors and bugs to cpufreq@vger.kernel.org, please.
analyzing CPU 0:
driver: powernow-k8
CPUs which need to switch frequency at the same time: 0
hardware limits: 950 MHz - 1.90 GHz
available frequency steps: 1.90 GHz, 950 MHz
available cpufreq governors: ondemand, userspace, performance
current policy: frequency should be within 950 MHz and 1.90 GHz.
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 950 MHz (asserted by call to hardware).
analyzing CPU 1:
driver: powernow-k8
CPUs which need to switch frequency at the same time: 1
hardware limits: 950 MHz - 1.90 GHz
available frequency steps: 1.90 GHz, 950 MHz
available cpufreq governors: ondemand, userspace, performance
current policy: frequency should be within 950 MHz and 1.90 GHz.
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 950 MHz (asserted by call to hardware).
[root@real ~]#
Usando batería:
[root@real ~]# cpufreq-info
cpufrequtils 005: cpufreq-info (C) Dominik Brodowski 2004-2006
Report errors and bugs to cpufreq@vger.kernel.org, please.
analyzing CPU 0:
driver: powernow-k8
CPUs which need to switch frequency at the same time: 0
hardware limits: 950 MHz - 1.90 GHz
available frequency steps: 1.90 GHz, 950 MHz
available cpufreq governors: ondemand, userspace, performance
current policy: frequency should be within 950 MHz and 1.90 GHz.
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 950 MHz (asserted by call to hardware).
analyzing CPU 1:
driver: powernow-k8
CPUs which need to switch frequency at the same time: 1
hardware limits: 950 MHz - 1.90 GHz
available frequency steps: 1.90 GHz, 950 MHz
available cpufreq governors: ondemand, userspace, performance
current policy: frequency should be within 950 MHz and 1.90 GHz.
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 950 MHz (asserted by call to hardware).
[root@real ~]#
Temp: 61°C-60°C-59°C 16:25-17:08=43 – 17:17=53
activando modo laptop:
19:45 – 20:28= 43 minutos
Mauricio Pacheco M.
Manager Information System
http://www.informaticamp.tk
Registered user #419099
http://counter.li.org/
Mauricio Pacheco M.
Manager Information System
http://www.quantum-ai.tk
Usuario: Mageia2 64 bits
Escritorio: KDE
Registered user #419099
http://linuxcounter.net/