lm-sensors findet keine Sensoren?!

  • Hallo,


    hat nicht zwingend mit yaVDR zu tun, aber da ich yaVDR am laufen habe wüsst ich nicht wo ich sonst posten soll...


    Ich würde gerne meine CPU/GPU Temps sehen und bin nach googeln auf lm-sensors gestoßen.


    Nach Installation und anschließendem


    Code
    sudo sensors-detect



    bekomm ich nur:




    # sensors-detect revision 5818 (2010-01-18 17:22:07 +0100)
    # System: System manufacturer System Product Name
    # Board: ASUSTeK Computer INC. P8H61-M LE


    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):
    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
    Intel Core family thermal sensor... No
    Intel Atom thermal sensor... No
    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'... No
    Trying family `SMSC'... No
    Trying family `VIA/Winbond/Nuvoton/Fintek'... Yes
    Found unknown chip with ID 0xc333
    (logical device B has address 0x290, could be sensors)
    Probing for Super-I/O at 0x4e/0x4f
    Trying family `National Semiconductor'... No
    Trying family `SMSC'... No
    Trying family `VIA/Winbond/Nuvoton/Fintek'... No
    Trying family `ITE'... No


    Some systems (mainly servers) implement IPMI, a set of common interfaces
    through which system health data may be retrieved, amongst other things.
    We first try to get the information from SMBIOS. If we don't find it
    there, we have to read from arbitrary I/O ports to probe for such
    interfaces. This is normally safe. Do you want to scan for IPMI
    interfaces? (YES/no):
    Probing for `IPMI BMC KCS' at 0xca0... No
    Probing for `IPMI BMC SMIC' at 0xca8... 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):
    Found unknown SMBus adapter 8086:1c22 at 0000:00:1f.3.
    Sorry, no supported PCI bus adapters found.


    Next adapter: cx23885[0] (i2c-0)
    Do you want to scan it? (yes/NO/selectively):


    Next adapter: cx23885[0] (i2c-1)
    Do you want to scan it? (yes/NO/selectively):


    Next adapter: cx23885[0] (i2c-2)
    Do you want to scan it? (yes/NO/selectively):


    Next adapter: NVIDIA i2c adapter (i2c-3)
    Do you want to scan it? (YES/no/selectively):


    Next adapter: NVIDIA i2c adapter (i2c-4)
    Do you want to scan it? (YES/no/selectively):


    Next adapter: NVIDIA i2c adapter (i2c-5)
    Do you want to scan it? (YES/no/selectively):


    Next adapter: NVIDIA i2c adapter (i2c-6)
    Do you want to scan it? (YES/no/selectively):


    Next adapter: NVIDIA i2c adapter (i2c-7)
    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'... No
    Probing for `EDID EEPROM'... Yes
    (confidence 8, not a hardware monitoring chip)


    Next adapter: NVIDIA i2c adapter (i2c-8)
    Do you want to scan it? (YES/no/selectively):


    Next adapter: NVIDIA i2c adapter (i2c-9)
    Do you want to scan it? (YES/no/selectively):


    Next adapter: NVIDIA i2c adapter (i2c-10)
    Do you want to scan it? (YES/no/selectively):


    Sorry, no sensors were detected.
    Either your system has no sensors, or they are not supported, or
    they are connected to an I2C or SMBus adapter that is not
    supported. If you find out what chips are on your board, check
    http://www.lm-sensors.org/wiki/Devices for driver status.


    (sry, mit code tags hat ers total umformatiert)



    Code
    sensors -u


    ergibt dann


    Code
    No sensors found!Make sure you loaded all the kernel drivers you need.Try sensors-detect to find out which these are.


    Kann das wirklich sein, dass er keine findet/ich keine habe oder muss ich noch was installieren/konfigurieren?


    Meine Hardware:


    Asus P8H61-M LE
    Asus ENGT520
    Pentium G620



    Danke und Gruß

    Asus P8H61M-LE, Intel G620, Asus ENGT520, Tevii S470, yaVDR 0.5a

  • Evtl. kennt dein acpi Modul (wenn das richtige für asus geladen ist) schon die Sensordaten?


    Schau mal unter /sys/class/thermal oder ähnlichen.


    cu

  • Etwas hat er ja gefunden:


    Trying family `VIA/Winbond/Nuvoton/Fintek'... Yes
    Found unknown chip with ID 0xc333
    (logical device B has address 0x290, could be sensors)


    Wenn das ein recht neues Board ist dann wird der Chip vermutlich von lm-sensors und/oder Kernel-Treiber noch nicht unterstützt.
    Das könnte lt. Google ein Nuvoton NCT6776F sein, für den das Kernel-Modul aber bisher nicht im Kernel ist sondern selbst kompiliert werden muss.

  • Schau mal hier . Damit habe ich mich auch schon rumgeschlagen. Funktioniert sogar einigermaßen, ist aber noch nicht stable gewesen, daher bei lm-sensors nicht enthalten und nur manuell zu installieren.

    Proxmox VE, Tyan Xeon Server, OMV, MLD-Server 5.1
    MLD 5.1 64bit: Asus AT5iont-t, ION2, 4GB Ram, SSHD 2,5" 1Tb, HEX TFX 300W 82+, Cine S2 V6.2 , 38W max.
    Yavdr 0.5:
    Zotac D2550ITXS-A-E mit GT610 OB, TT S2-4100 PCI-e ,Joujye NU-0568I-B
    Yavdr 0.5:
    Sandy Bridge G840, Tests und Energieverbrauch , CoHaus CIR, Cine S2 V6.2
    MLD 5.1 Beebox N3150
    , DVBSky S960 und 1Tb WD Blue

  • Zumindest in einem Fall hatte unsere Einstellung acpi_enforce_resources=lax negative auswirkung gehabt. Evtl. möchtest du das mal rausnehmen, update-grup und reboot und danach sensors-detect nochmal ausführen ?

    VDR User: 87 - LaScala LC14B - LG/Phillipps 6,4" VGA Display | Asrock H61/U3S3 | G630T | 1x 16GB Mobi Mtron 3035 1x WD 750GB 2,5" |1x L4m DVB-S2 Version 5.4

  • Schau einmal hier hatte das selbe Problem, der Hinweis von Steffen_b hat geholfen!
    Gruß
    Norman

    VDR: Lüfterloses Gehäuse mit AT3IONT-I WLAN 2,5" 60 GB SSD und Video 1 TB unter yaVDR64-0.5.0; TV Karte Linux4Media cineS2 DVB-S2 Twin Tuner (v5) >> Bilder in der Galerie

  • hmm bringt alles keine Veränderung, er findet nichts.
    Den Vorschlag von Torsten73 hab ich noch nicht getestet aber sooo wichtig ist es nun auch nicht mit den sensoren, thx trotzdem.

    Asus P8H61M-LE, Intel G620, Asus ENGT520, Tevii S470, yaVDR 0.5a

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!