Gracias Gracias:  0
Me Gusta Me Gusta:  0
No me Gusta No me Gusta:  0
Página 1 de 3 123 ÚltimoÚltimo
Mostrando resultados del 1 al 10 de 23

Tema: Editar superkaramba

  1. #1
    Fecha de Ingreso
    01-diciembre-2004
    Mensajes
    669
    Post Thanks / Like
    Poder de Credibilidad
    16

    Editar superkaramba

    bueno le paso a contar que estoy editando un tema de super karamba pero quiero que me de unos datos y no se como.

    los datos son estos:
    Propiedades del sensor :
    Tsystem 32 C (90 F)
    Tcpu 69 C (156 F)
    Taux 33 C (91 F)
    Fcpu 3409 RPM
    Fpowersupply 2935 RPM
    Vcore 1.47 V
    Vaux 1.95 V
    Vio 3.28 V
    Sensor

    --------------------------------------------------------------------------------


    Propiedades del sensor :
    Tipo de sensor Winbond W83627HF (ISA 290h)

    Temperaturas :
    Placa base 32 C (90 F)
    Procesador 69 C (156 F)
    Aux 33 C (91 F)
    Seagate ST360020A 30 C (86 F)

    Ventiladores :
    Procesador 3409 RPM
    Alimentaci� 2935 RPM

    Valores de voltaje :
    Ncleo CPU 1.47 V
    CPU Auxiliar 1.95 V
    +3.3 V 3.28 V
    +5 V 5.16 V
    +12 V 12.40 V
    -12 V -12.28 V
    -5 V -5.30 V
    Puesta en espera +5 V 4.92 V
    Bater� VBAT 2.91 V
    Debug Info V 5C 7A CD C0 CC 20 30 20 (01)
    Debug Info T 32 69 33
    Estos datos salen del programa EVEREST Home Edition bajo windows.
    el tema que yo quiero incluirlos en mi tema de superkaramba y no se como.
    alguno save?
    desde ya las gracias

    PD: Todo los temas que he bajado estos datos o no me los da o da medidas muy extrañas

  2. #2
    Fecha de Ingreso
    22-enero-2005
    Ubicación
    Valladolid
    Mensajes
    291
    Post Thanks / Like
    Poder de Credibilidad
    16
    Bueno necesitas tener corriendo el lm_sensors que es el que da la temperaturas en linux.
    Y un vez que ya lo tienes para meterlo en el karamba puedes hacerlo como
    Código:
     TEXT X=155 Y=7 SENSOR=SENSOR TYPE="fan1" FORMAT="%V rpm "FONT="Fixed" FONTSIZE=14 BGCOLOR=0,0,0 SHADOW=1
    donde fan1 es un ventilador. fan2 es otro y asi sucesivamente. para las temperaturas es lo mismo pero con temp1 , temp2, etc... .Así de fácil.

    También se puede hacer mediante sensor = program y program="x" donde x es un comando que metas tu en el terminal para que te salga lo que quieras de salida.
    Por ejemplo:
    Para sacar el voltaje de core, no es más que con sensors de linux pongas este comando:
    Código:
    sensors |grep 'VCore 1'|awk '{print $3}'
    El grep hace el filtrado de una de las líneas y el awk selecciona una palabra. Eso lo metes donde pone antes x y ya está tienes el vcore en karamba.
    A ver si con esta ayuda lo puedes aplicar a demás casos

    Saludos
    OpenSuse 10.2 Kde 3.55 Opera 9.10

  3. #3
    Fecha de Ingreso
    01-diciembre-2004
    Mensajes
    669
    Post Thanks / Like
    Poder de Credibilidad
    16
    ok gracias tengo el sensors solo es el mismo que el Im_sensors, no?
    Bueno tambien baje el ksensors para verlo en kde pero las lecturas son malas.
    Ej me mostrava como 69º cuando la bios me marcava 43º y no era problema de estar en otra medida

  4. #4
    Fecha de Ingreso
    22-enero-2005
    Ubicación
    Valladolid
    Mensajes
    291
    Post Thanks / Like
    Poder de Credibilidad
    16
    Si es sensors. Mira a ver si sensors te marca bien la temperatura en el comando terminal. Lo del ksensors es muy relativo.
    Saludos
    OpenSuse 10.2 Kde 3.55 Opera 9.10

  5. #5
    Fecha de Ingreso
    19-noviembre-2004
    Mensajes
    118
    Post Thanks / Like
    Poder de Credibilidad
    16
    A mí sensors me da una temperatura, la temp 3, con 70º. ¿Qué temperatura es esta?

    adeu

  6. #6
    Fecha de Ingreso
    01-diciembre-2004
    Mensajes
    669
    Post Thanks / Like
    Poder de Credibilidad
    16
    Cita Iniciado por Kaisermart
    Si es sensors. Mira a ver si sensors te marca bien la temperatura en el comando terminal. Lo del ksensors es muy relativo.
    Saludos
    mmmmm no me anda capas lo estoy haciendo mal

    kaleimn@linux:~> sensors -v
    sensors version 2.9.0 with libsensors version 2.9.0
    kaleimn@linux:~> sensors
    No sensors found!
    kaleimn@linux:~> sensors -s
    No sensors found!
    kaleimn@linux:~> sensors-detect
    bash: sensors-detect: command not found
    kaleimn@linux:~>
    Le estoy erando al comando (el yast me da que sensors esta instalado)

  7. #7
    Fecha de Ingreso
    22-enero-2005
    Ubicación
    Valladolid
    Mensajes
    291
    Post Thanks / Like
    Poder de Credibilidad
    16
    Sensors detect se hará como root. Y luego ten cuidado con todo lo que pone y tal.

    Saludos
    OpenSuse 10.2 Kde 3.55 Opera 9.10

  8. #8
    Fecha de Ingreso
    01-diciembre-2004
    Mensajes
    669
    Post Thanks / Like
    Poder de Credibilidad
    16
    bueno ise esto a ver si esta bien y en que me puede ayudar
    linux:~ # sensors-detect

    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 `i2c-i801' for device 00:1f.3: Intel 82801BA ICH2
    Use driver `rivatv' for device 01:00.0: GeForce2 MX2
    Probe succesfully concluded.

    We will now try to load each adapter module in turn.
    Module `i2c-i801' already loaded.
    Load `rivatv' (say NO if built into your kernel)? (YES/no): y
    FATAL: Module rivatv not found.
    Loading failed... skipping.
    ** Note: rivatv module is available at http://rivatv.sourceforge.net/
    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).

    Next adapter: SMBus I801 adapter at 5000
    Do you want to scan it? (YES/no/selectively): y
    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 0x51
    Probing for `SPD EEPROM'... Success!
    (confidence 8, driver `eeprom')
    Client found at address 0x52
    Probing for `SPD EEPROM'... Success!
    (confidence 8, driver `eeprom')
    Client found at address 0x69

    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... Success!
    (confidence 8, driver `w83781d')
    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 IT8705F / IT8712F / 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! (0x52)
    Probing for `Winbond W83627HF Super IO Sensors'
    Success... found at address 0x0290
    Probing for `Winbond W83627THF Super IO Sensors'
    Failed! (0x52)
    Probing for `Winbond W83637HF Super IO Sensors'
    Failed! (0x52)
    Probing for `Winbond W83697HF Super IO Sensors'
    Failed! (0x52)
    Probing for `Winbond W83697SF/UF Super IO PWM'
    Failed! (0x52)
    Probing for `Winbond W83L517D Super IO'
    Failed! (0x52)

    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)

    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 5000' (Algorithm unavailable)
    Busdriver `i2c-i801', I2C address 0x50
    Chip `SPD EEPROM' (confidence: 8)
    * Bus `SMBus I801 adapter at 5000' (Algorithm unavailable)
    Busdriver `i2c-i801', I2C address 0x51
    Chip `SPD EEPROM' (confidence: 8)
    * Bus `SMBus I801 adapter at 5000' (Algorithm unavailable)
    Busdriver `i2c-i801', I2C address 0x52
    Chip `SPD EEPROM' (confidence: 8)

    Driver `w83781d' (may not be inserted):
    Misdetects:
    * ISA bus address 0x0290 (Busdriver `i2c-isa')
    Chip `Winbond W83627HF' (confidence: 8)

    Driver `w83627hf' (should be inserted):
    Detects correctly:
    * ISA bus address 0x0290 (Busdriver `i2c-isa')
    Chip `Winbond W83627HF 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/modprobe.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-i801
    modprobe i2c-isa
    # I2C chip drivers
    modprobe eeprom
    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 /usr/share/doc/packages/sensors/prog/init/lm_sensors.init.suse
    to /etc/init.d/lm_sensors for initialization at boot time.
    Ahora como sigo?
    Y desde ya gracias

  9. #9
    Fecha de Ingreso
    01-diciembre-2004
    Mensajes
    669
    Post Thanks / Like
    Poder de Credibilidad
    16
    Hablando del tema miren lo que encontre http://www.maxoverclocking.com/ele_esq6.html

  10. #10
    Goltnor Invitado

    Talking

    Cita Iniciado por kaleimn
    bueno ise esto a ver si esta bien y en que me puede ayudar
    Ahora como sigo?
    Y desde ya gracias
    Bueno a lo largo del foro hay muchos temas que hablan de ello...

    Si colocas "Sensores" en la busqueda del foro encontraras como se hace.

    Al final de este tema: Monitorizar Temperatura Nuestro amigo riven cuenta como se hace...




Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Temas Similares

  1. Superkaramba y Liquid Weather
    By Clufis in forum Software
    Respuestas: 10
    Último mensaje: 05-oct-2006, 05:55
  2. Hay paquetes de SuperKaramba 0.35?
    By Trimax in forum Software
    Respuestas: 2
    Último mensaje: 10-feb-2005, 23:43
  3. superkaramba y sensores (ayuda plz)
    By yakko in forum Software
    Respuestas: 14
    Último mensaje: 06-feb-2005, 12:53
  4. SuperKaramba
    By Goltnor in forum Software
    Respuestas: 0
    Último mensaje: 04-nov-2004, 01:18
  5. Pregntas sobre SuperKaramba
    By zhonnetiks in forum Software
    Respuestas: 1
    Último mensaje: 30-sep-2004, 07:05

Marcadores

Normas de Publicación

  • No puedes crear nuevos temas
  • No puedes responder mensajes
  • No puedes subir archivos adjuntos
  • No puedes editar tus mensajes
  •