No sensors found!

Dieses Thema im Forum "Gentoo" wurde erstellt von Drizzt_DoUrden, 10.09.2005.

  1. #1 Drizzt_DoUrden, 10.09.2005
    Drizzt_DoUrden

    Drizzt_DoUrden Tripel-As

    Dabei seit:
    06.01.2003
    Beiträge:
    200
    Zustimmungen:
    0
    Hi Leute
    hab mir mal lm_sensors installed da ich keine lüfter mehr im Pc habe dachte ich is immer gut mal die Temps im auge zu haben.

    doch wenn ich sensors ausführe heisste es nur

    localhost neverwinter # sensors
    No sensors found!
    localhost neverwinter #


    dann bin ich erst mal hingegangen und habe ein sensors-detect gemacht

    localhost neverwinter # 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-viapro' for device 00:11.0: VIA Technologies VT8237 South Bridge
    Probe succesfully concluded.

    We will now try to load each adapter module in turn.
    Load `i2c-viapro' (say NO if built into your kernel)? (YES/no): y
    FATAL: Module i2c_viapro not found.
    Loading failed... skipping.
    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
    FATAL: Module i2c_dev not found.
    Loading failed, expect problems later on.

    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 Via Pro adapter at 0400
    Do you want to scan it? (YES/no/selectively): y
    Client found at address 0x2f
    Probing for `National Semiconductor LM78'... Failed!
    Probing for `National Semiconductor LM78-J'... Failed!
    Probing for `National Semiconductor LM79'... Failed!
    Probing for `National Semiconductor LM80'... Failed!
    Probing for `Winbond W83781D'... Failed!
    Probing for `Winbond W83782D'... Failed!
    Probing for `Winbond W83791D'... Failed!
    Probing for `Winbond W83792D'... Failed!
    Probing for `Winbond W83791SD'... Success!
    (confidence 3, driver `not-a-sensor')
    Probing for `Winbond W83627HF'... Failed!
    Probing for `Winbond W83627EHF'... Failed!
    Probing for `Asus AS99127F (rev.1)'... Failed!
    Probing for `Asus AS99127F (rev.2)'... Failed!
    Probing for `Asus ASB100 Bach'... Failed!
    Probing for `Analog Devices ADM9240'... Failed!
    Probing for `Dallas Semiconductor DS1780'... Failed!
    Probing for `National Semiconductor LM81'... Failed!
    Probing for `Analog Devices ADM1029'... Failed!
    Probing for `ITE IT8712F'... Failed!
    Probing for `ITE IT8705F / SiS 950'... Failed!
    Client found at address 0x48
    Probing for `National Semiconductor LM75'... Failed!
    Probing for `National Semiconductor LM77'... Failed!
    Probing for `Dallas Semiconductor DS1621'... Failed!
    Probing for `Maxim MAX6650/MAX6651'... Failed!
    Probing for `National Semiconductor LM92'... Failed!
    Probing for `National Semiconductor LM76'... Failed!
    Probing for `Maxim MAX6633/MAX6634/MAX6635'... Failed!
    Client found at address 0x49
    Probing for `National Semiconductor LM75'... Failed!
    Probing for `National Semiconductor LM77'... Failed!
    Probing for `Dallas Semiconductor DS1621'... Failed!
    Probing for `National Semiconductor LM92'... Failed!
    Probing for `National Semiconductor LM76'... Failed!
    Probing for `Maxim MAX6633/MAX6634/MAX6635'... Failed!
    Client found at address 0x4a
    Probing for `National Semiconductor LM75'... Failed!
    Probing for `National Semiconductor LM77'... Failed!
    Probing for `Dallas Semiconductor DS1621'... Failed!
    Probing for `National Semiconductor LM92'... Failed!
    Probing for `National Semiconductor LM76'... Failed!
    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 0x51
    Probing for `SPD EEPROM'... Success!
    (confidence 8, driver `eeprom')
    Client found at address 0x61
    Probing for `SMBus 2.0 ARP-Capable Device'... Success!
    (confidence 1, driver `smbus-arp')
    Client found at address 0x69
    Client found at address 0x6a

    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... Success!
    (confidence 8, driver `w83781d')
    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! (0x6012)
    Probing for `ITE 8705F Super IO Sensors'
    Failed! (0x6012)
    Probing for `ITE 8712F Super IO Sensors'
    Failed! (0x6012)
    Probing for `Nat. Semi. PC87351 Super IO Fan Sensors'
    Failed! (0x60)
    Probing for `Nat. Semi. PC87360 Super IO Fan Sensors'
    Failed! (0x60)
    Probing for `Nat. Semi. PC87363 Super IO Fan Sensors'
    Failed! (0x60)
    Probing for `Nat. Semi. PC87364 Super IO Fan Sensors'
    Failed! (0x60)
    Probing for `Nat. Semi. PC87365 Super IO Fan Sensors'
    Failed! (0x60)
    Probing for `Nat. Semi. PC87365 Super IO Voltage Sensors'
    Failed! (0x60)
    Probing for `Nat. Semi. PC87365 Super IO Thermal Sensors'
    Failed! (0x60)
    Probing for `Nat. Semi. PC87366 Super IO Fan Sensors'
    Failed! (0x60)
    Probing for `Nat. Semi. PC87366 Super IO Voltage Sensors'
    Failed! (0x60)
    Probing for `Nat. Semi. PC87366 Super IO Thermal Sensors'
    Failed! (0x60)
    Probing for `Nat. Semi. PC87372 Super IO Fan Sensors'
    Failed! (0x60)
    Probing for `Nat. Semi. PC87373 Super IO Fan Sensors'
    Failed! (0x60)
    Probing for `Nat. Semi. PC87591 Super IO'
    Failed! (0x60)
    Probing for `Nat. Semi. PC87371 Super IO'
    Failed! (0x60)
    Probing for `Nat. Semi. PC97371 Super IO'
    Failed! (0x60)
    Probing for `Nat. Semi. PC8739x Super IO'
    Failed! (0x60)
    Probing for `Nat. Semi. PC8741x Super IO'
    Failed! (0x60)
    Probing for `SMSC 47B27x Super IO Fan Sensors'
    Failed! (0x60)
    Probing for `SMSC 47M10x/13x Super IO Fan Sensors'
    Failed! (0x60)
    Probing for `SMSC 47M14x Super IO Fan Sensors'
    Failed! (0x60)
    Probing for `SMSC 47M15x/192 Super IO Fan Sensors'
    Success... but not activated
    Probing for `SMSC 47S42x Super IO Fan Sensors'
    Failed! (0x60)
    Probing for `SMSC 47S45x Super IO Fan Sensors'
    Failed! (0x60)
    Probing for `SMSC 47M172 Super IO'
    Failed! (0x60)
    Probing for `SMSC LPC47B397-NC Super IO'
    Failed! (0x60)
    Probing for `VT1211 Super IO Sensors'
    Failed! (0x60)
    Probing for `Winbond W83627HF Super IO Sensors'
    Failed! (0x60)
    Probing for `Winbond W83627THF Super IO Sensors'
    Failed! (0x60)
    Probing for `Winbond W83637HF Super IO Sensors'
    Failed! (0x60)
    Probing for `Winbond W83697HF Super IO Sensors'
    Success... found at address 0x0290
    Probing for `Winbond W83697SF/UF Super IO PWM'
    Failed! (0x60)
    Probing for `Winbond W83L517D Super IO'
    Failed! (0x60)
    Probing for `Winbond W83627EHF Super IO Sensors'
    Failed! (0x6012)

    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 `not-a-sensor' (should be inserted):
    Detects correctly:
    * Bus `SMBus Via Pro adapter at 0400'
    Busdriver `i2c-viapro', I2C address 0x2f
    Chip `Winbond W83791SD' (confidence: 3)

    Driver `eeprom' (should be inserted):
    Detects correctly:
    * Bus `SMBus Via Pro adapter at 0400'
    Busdriver `i2c-viapro', I2C address 0x50
    Chip `SPD EEPROM' (confidence: 8)
    * Bus `SMBus Via Pro adapter at 0400'
    Busdriver `i2c-viapro', I2C address 0x51
    Chip `SPD EEPROM' (confidence: 8)

    Driver `smbus-arp' (should be inserted):
    Detects correctly:
    * Bus `SMBus Via Pro adapter at 0400'
    Busdriver `i2c-viapro', I2C address 0x61
    Chip `SMBus 2.0 ARP-Capable Device' (confidence: 1)

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

    Driver `w83627hf' (should be inserted):
    Detects correctly:
    * ISA bus address 0x0290 (Busdriver `i2c-isa')
    Chip `Winbond W83697HF 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)? smbus

    If you want to load the modules at startup, generate a config file
    below and make sure lm_sensors gets started; e.g
    $ rc-update add lm_sensors default.

    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
    #----end 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.
    To load everything that is needed, execute the commands above...

    #----cut here----
    # I2C adapter drivers
    modprobe i2c-viapro
    modprobe i2c-isa
    # I2C chip drivers
    # Warning: the required module eeprom 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.
    modprobe 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.
    modprobe smbus-arp
    # Warning: the required module w83627hf 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.
    modprobe w83627hf
    # sleep 2 # optional
    /usr/bin/sensors -s # recommended

    Do you want to overwrite /etc/conf.d/lm_sensors? Enter s to specify other file name?
    (yes/NO/s): y
    Done.


    danach geht es aber leider immer noch nicht. Kommt der selbe Fehler. Was kann man da noch machen oder habe ich was übersehn.

    Mfg Drizzt
     
  2. Anzeige

    Schau dir mal diese Kategorie an. Dort findest du bestimmt etwas.
    Registrieren bzw. einloggen, um diese und auch andere Anzeigen zu deaktivieren
  3. name

    name Inactive user

    Dabei seit:
    28.08.2004
    Beiträge:
    592
    Zustimmungen:
    0
    Ort:
    Wien->127.0.0.1
    Mein tipp: nimm xmbmon, ist in portage drin, eine nicht X version ist auch enhalten.Falls er Command not found sagt: /usr/sbin ind die $PATH
     
  4. #3 Drizzt_DoUrden, 10.09.2005
    Drizzt_DoUrden

    Drizzt_DoUrden Tripel-As

    Dabei seit:
    06.01.2003
    Beiträge:
    200
    Zustimmungen:
    0
    name Danke dir
    also es hat sofort geklapt, nur muss ich nun rausfinden was das alles zu bedeuten hat :)

    Mfg Drizzt
     
  5. name

    name Inactive user

    Dabei seit:
    28.08.2004
    Beiträge:
    592
    Zustimmungen:
    0
    Ort:
    Wien->127.0.0.1
    kein problem, mir ist es mit lm_sensors ähnlich ergangen :)
     
  6. #5 ChrisMD, 10.09.2005
    ChrisMD

    ChrisMD Haudegen

    Dabei seit:
    30.06.2005
    Beiträge:
    619
    Zustimmungen:
    0
    Im Kernel wahrscheinlich garkeine Module für die Sensoren aktiviert?
     
  7. tig

    tig Tripel-As

    Dabei seit:
    09.02.2004
    Beiträge:
    229
    Zustimmungen:
    0
    Dafür ist doch
    Code:
    sensors-detect
    da

    ...

    Um rauszufinden welches Modul du brauchst.
     
  8. Anzeige

    Vielleicht findest du HIER Antworten.
    Registrieren bzw. einloggen, um diese und auch andere Anzeigen zu deaktivieren
  9. name

    name Inactive user

    Dabei seit:
    28.08.2004
    Beiträge:
    592
    Zustimmungen:
    0
    Ort:
    Wien->127.0.0.1
    er hat doch schon ne alternative die autodetect hat :)
     
  10. #8 ChrisMD, 10.09.2005
    ChrisMD

    ChrisMD Haudegen

    Dabei seit:
    30.06.2005
    Beiträge:
    619
    Zustimmungen:
    0
    Wenn die Module garnicht existieren kann man sie auch nicht nachladen.
     
Thema:

No sensors found!

Die Seite wird geladen...

No sensors found! - Ähnliche Themen

  1. lmsensors Problem mit Debian-Sid. 2.6.39-2-amd64

    lmsensors Problem mit Debian-Sid. 2.6.39-2-amd64: Hallo ich hab ein mini Problem mit lmsensors sensors ergibt ---------- k10temp-pci-00c3 Adapter: PCI adapter temp1: +46.0°C (high =...
  2. sensors schlägt plötzlich Alarm- Wert ist aber ok

    sensors schlägt plötzlich Alarm- Wert ist aber ok: Nachdem sensors tagelang problemlos lief, plötzlich Alarm- hier die betreffende sensors-Befehlsausgabe: w83627dhg-isa-0a10 Adapter: ISA adapter...
  3. lmsensors und VMWare ??

    lmsensors und VMWare ??: Hallo zusammen, hoffe bin hier richtig und das Problem hatte auch schon mal jemand und es konnte gelöst werden? Kann doch da nicht der...
  4. lm-sensors 3.0.0 freigegeben

    lm-sensors 3.0.0 freigegeben: Mit der neuen Version 3.0.0 von lm-sensors enthält das Paket erstmals keine Kernel-Komponenten mehr, da alle Treiber nun im Standard-Linux-Kernel...
  5. lm-sensors fehler

    lm-sensors fehler: Hi, habe Debian Kernel 2.4 und da kommt diese fehler server:~# sensors Can't access procfs/sysfs file Kernel interface access error For...