Results 1 to 6 of 6

Thread: can't get lm-sensors 3.2 to work with i5 2500k, asrock motherboard

  1. #1
    Join Date
    Apr 2007
    Beans
    29

    can't get lm-sensors 3.2 to work with i5 2500k, asrock motherboard

    Hi,

    As the title says I can't get lm-sensors to work with my new i5 2500k processor. I'm using a brand new Asrock P67 Extreme 4 motherboard.

    I have compiled and installed lm-sensors 3.2 from source without issues.

    Output from sudo sensors-detect is as follows:
    Code:
    chr@storbudde:~/Desktop$ sudo sensors-detect 
    # sensors-detect revision 5861 (2010-09-21 17:21:05 +0200)
    # System: To Be Filled By O.E.M. To Be Filled By O.E.M.
    # Board: ASRock P67 Extreme4
    
    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): y
    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): y
    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): y
    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): y
    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): y
    Using driver `i2c-i801' for device 0000:00:1f.3: Intel Cougar Point (PCH)
    
    Next adapter: NVIDIA i2c adapter  (i2c-0)
    Do you want to scan it? (YES/no/selectively): y
    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-1)
    Do you want to scan it? (YES/no/selectively): y
    
    Next adapter: NVIDIA i2c adapter  (i2c-2)
    Do you want to scan it? (YES/no/selectively): y
    Client found at address 0x2e
    Probing for `Myson MTP008'...                               No
    Probing for `National Semiconductor LM78'...                No
    Probing for `National Semiconductor LM79'...                No
    Probing for `National Semiconductor LM80'...                No
    Probing for `National Semiconductor LM85'...                No
    Probing for `National Semiconductor LM96000 or PC8374L'...  No
    Probing for `Analog Devices ADM1027'...                     No
    Probing for `Analog Devices ADT7460 or ADT7463'...          No
    Probing for `SMSC EMC6D100 or EMC6D101'...                  No
    Probing for `SMSC EMC6D102'...                              No
    Probing for `SMSC EMC6D103'...                              No
    Probing for `Winbond WPCD377I'...                           No
    Probing for `Analog Devices ADT7467 or ADT7468'...          No
    Probing for `Analog Devices ADT7470'...                     No
    Probing for `Analog Devices ADT7473'...                     Success!
        (confidence 5, driver `adt7475')
    Probing for `Analog Devices ADT7475'...                     No
    Probing for `Analog Devices ADT7476'...                     No
    Probing for `Analog Devices ADT7490'...                     No
    Probing for `Andigilog aSC7611'...                          No
    Probing for `Andigilog aSC7621'...                          No
    Probing for `National Semiconductor LM87'...                No
    Probing for `Analog Devices ADM1024'...                     No
    Probing for `National Semiconductor LM93'...                No
    Probing for `Winbond W83781D'...                            No
    Probing for `Winbond W83782D'...                            No
    Probing for `Winbond W83791D'...                            No
    Probing for `Winbond W83792D'...                            No
    Probing for `Winbond W83793R/G'...                          No
    Probing for `Nuvoton W83795G/ADG'...                        No
    Probing for `Winbond W83627HF'...                           No
    Probing for `Winbond W83627EHF'...                          No
    Probing for `Winbond W83627DHG/W83667HG/W83677HG'...        No
    Probing for `Asus AS99127F (rev.1)'...                      No
    Probing for `Asus AS99127F (rev.2)'...                      No
    Probing for `Asus ASB100 Bach'...                           No
    Probing for `Winbond W83L786NR/NG/R/G'...                   No
    Probing for `Winbond W83L785TS-S'...                        No
    Probing for `Analog Devices ADM9240'...                     No
    Probing for `Dallas Semiconductor DS1780'...                No
    Probing for `National Semiconductor LM81'...                No
    Probing for `Analog Devices ADM1026'...                     No
    Probing for `Analog Devices ADM1025'...                     No
    Probing for `Texas Instruments AMC6821'...                  No
    Probing for `Analog Devices ADM1029'...                     No
    Probing for `Analog Devices ADM1030'...                     No
    Probing for `Analog Devices ADM1031'...                     No
    Probing for `Analog Devices ADM1022'...                     No
    Probing for `Texas Instruments THMC50'...                   No
    Probing for `Analog Devices ADM1028'...                     No
    Probing for `Texas Instruments THMC51'...                   No
    Probing for `ITE IT8712F'...                                No
    Probing for `SMSC DME1737'...                               No
    Probing for `SMSC SCH5027D-NW'...                           No
    Probing for `SMSC EMC2103'...                               No
    Probing for `Fintek F75373S/SG'...                          No
    Probing for `Fintek F75375S/SP'...                          No
    Probing for `Fintek F75387SG/RG'...                         No
    Probing for `Winbond W83791SD'...                           No
    
    Next adapter: NVIDIA i2c adapter  (i2c-3)
    Do you want to scan it? (YES/no/selectively): y
    
    Next adapter: NVIDIA i2c adapter  (i2c-4)
    Do you want to scan it? (YES/no/selectively): y
    
    Next adapter: NVIDIA i2c adapter  (i2c-5)
    Do you want to scan it? (YES/no/selectively): y
    
    Next adapter: NVIDIA i2c adapter  (i2c-6)
    Do you want to scan it? (YES/no/selectively): y
    
    Next adapter: NVIDIA i2c adapter  (i2c-7)
    Do you want to scan it? (YES/no/selectively): y
    
    Next adapter: SMBus I801 adapter at f000 (i2c-8)
    Do you want to scan it? (YES/no/selectively): y
    Client found at address 0x29
    Probing for `National Semiconductor LM78'...                No
    Probing for `National Semiconductor LM79'...                No
    Probing for `National Semiconductor LM80'...                No
    Probing for `Winbond W83781D'...                            No
    Probing for `Winbond W83782D'...                            No
    Probing for `Winbond W83627HF'...                           No
    Probing for `Winbond W83627EHF'...                          No
    Probing for `Winbond W83627DHG/W83667HG/W83677HG'...        No
    Probing for `Asus AS99127F (rev.1)'...                      No
    Probing for `Asus AS99127F (rev.2)'...                      No
    Probing for `Asus ASB100 Bach'...                           No
    Probing for `Analog Devices ADM1021'...                     No
    Probing for `Analog Devices ADM1021A/ADM1023'...            No
    Probing for `Maxim MAX1617'...                              No
    Probing for `Maxim MAX1617A'...                             No
    Probing for `Maxim MAX1668'...                              No
    Probing for `Maxim MAX1805'...                              No
    Probing for `Maxim MAX1989'...                              No
    Probing for `Maxim MAX6655/MAX6656'...                      No
    Probing for `TI THMC10'...                                  No
    Probing for `National Semiconductor LM84'...                No
    Probing for `Genesys Logic GL523SM'...                      No
    Probing for `Onsemi MC1066'...                              No
    Probing for `Maxim MAX1618'...                              No
    Probing for `Maxim MAX1619'...                              No
    Probing for `National Semiconductor LM82/LM83'...           No
    Probing for `Maxim MAX6654'...                              No
    Probing for `Maxim MAX6690'...                              No
    Probing for `Maxim MAX6680/MAX6681'...                      No
    Probing for `Maxim MAX6695/MAX6696'...                      No
    Probing for `Analog Devices ADM1029'...                     No
    Probing for `ITE IT8712F'...                                No
    Client found at address 0x51
    Probing for `Analog Devices ADM1033'...                     No
    Probing for `Analog Devices ADM1034'...                     No
    Probing for `SPD EEPROM'...                                 No
    Client found at address 0x53
    Probing for `Analog Devices ADM1033'...                     No
    Probing for `Analog Devices ADM1034'...                     No
    Probing for `SPD EEPROM'...                                 No
    
    Now follows a summary of the probes I have just done.
    Just press ENTER to continue: 
    
    Driver `adt7475':
      * Bus `NVIDIA i2c adapter '
        Busdriver `nvidia', I2C address 0x2e
        Chip `Analog Devices ADT7473' (confidence: 5)
    
    Do you want to overwrite /etc/sysconfig/lm_sensors? (YES/no): y
    Copy prog/init/lm_sensors.init to /etc/init.d/lm_sensors
    for initialization at boot time.
    You should now start the lm_sensors service to load the required
    kernel modules.
    and then sensors gives
    Code:
    chr@storbudde:~/Desktop$ sensors
    No sensors found!
    Make sure you loaded all the kernel drivers you need.
    Try sensors-detect to find out which these are.
    I think it wants me to load the driver "adt7475", but I think I already did that. I also manually added i2c_dev and i2c_i801 because it told me to before. lsmod output:
    Code:
    chr@storbudde:~/Desktop$ lsmod
    Module                  Size  Used by
    i2c_dev                 6310  0 
    i2c_i801               10156  0 
    nls_iso8859_1           4657  1 
    nls_cp437               6375  1 
    vfat                   10954  1 
    fat                    56244  1 vfat
    binfmt_misc             7984  1 
    parport_pc             30086  0 
    ppdev                   6804  0 
    snd_hda_codec_nvhdmi    15451  4 
    snd_hda_codec_realtek   300173  1 
    snd_hda_intel          26115  4 
    nvidia              10221046  48 
    snd_hda_codec         100919  3 snd_hda_codec_nvhdmi,snd_hda_codec_realtek,snd_hda_intel
    snd_hwdep               6660  1 snd_hda_codec
    snd_pcm                89104  3 snd_hda_intel,snd_hda_codec
    snd_seq_midi            5932  0 
    snd_rawmidi            22207  1 snd_seq_midi
    snd_seq_midi_event      7291  1 snd_seq_midi
    adt7475                26161  0 
    hwmon_vid               3154  1 adt7475
    snd_seq                57512  2 snd_seq_midi,snd_seq_midi_event
    snd_timer              23850  2 snd_pcm,snd_seq
    snd_seq_device          6912  3 snd_seq_midi,snd_rawmidi,snd_seq
    usbhid                 42030  0 
    hid                    84710  1 usbhid
    lp                     10201  0 
    snd                    64181  16 snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_rawmidi,snd_seq,snd_timer,snd_seq_device
    xhci_hcd               60528  0 
    soundcore               1240  1 snd
    shpchp                 34910  0 
    usb_storage            50372  1 
    intel_agp              32334  0 
    parport                37032  3 parport_pc,ppdev,lp
    snd_page_alloc          8588  2 snd_hda_intel,snd_pcm
    floppy                 65299  0 
    r8169                  42254  0 
    mii                     5261  1 r8169
    firewire_ohci          24839  0 
    firewire_core          54327  1 firewire_ohci
    crc_itu_t               1739  1 firewire_core
    Can anyone help? Really want to know the CPU temps since I want to overclock the processor.

    Cheers,
    Carl

  2. #2
    Join Date
    Dec 2007
    Beans
    504

    Re: can't get lm-sensors 3.2 to work with i5 2500k, asrock motherboard

    It is possibly a drivers issue.

    As far as I can make out, the lm-sensors drivers are not available for such new hardware. Short of writing them yourself, the best option may be to wait for a kernel upgrade in April when Natty Narwhal becomes available.

  3. #3
    Join Date
    Apr 2007
    Beans
    29

    Re: can't get lm-sensors 3.2 to work with i5 2500k, asrock motherboard

    Ah dammit, that's not very good news.

    Oh well, suppose I have to be patient with my clocking then.

    Thanks for the fast reply!

  4. #4
    Join Date
    Apr 2011
    Beans
    2

    Re: can't get lm-sensors 3.2 to work with i5 2500k, asrock motherboard

    I was able to make limited progress by compiling and installing the latest driver at http://roeck-us.net/linux/drivers/w83627ehf which supports the nct6776 found in the P67 Extreme4. You need to add it to /etc/sysconfig/lm_sensors. Unfortunately, only 2 fans show up, and I haven't looked into the voltages and temps.

    In case you're wondering about the names, this super I/O chip is made by Nuvoton which was spun off from Winbond in 2008.

  5. #5
    Join Date
    Apr 2011
    Beans
    2

    Re: can't get lm-sensors 3.2 to work with i5 2500k, asrock motherboard

    Fans 3-5 are not being enabled by the w83627ehf driver because it doesn't like the values in global registers 0x1c and 0x24. I suspect this is a BIOS problem.

    When I display these registers with:
    isadump -y -k 0x87,0x87 0x2e 0x2f

    I get something like:
    0 1 2 3 4 5 6 7 8 9 a b c d e f
    00: ff ff 00 ff ff ff ff 02 ff ff ff ff ff ff ff ff
    10: ff ff ff ff ff ff ff ff ff ff f8 0e 00 00 ff ff
    20: c3 33 ff 00 5c 00 00 98 00 ff 20 00 80 00 00 01
    30: 00 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff

    As an experiment, I overwrote these registers before loading the w83627ehf module:
    isaset -y -f 0x2e 0x87
    isaset -y -f 0x2e 0x87
    isaset -y 0x2e 0x2f 0x1c 0x3
    isaset -y 0x2e 0x2f 0x24 0x1c

    And all 5 fans show up. I'm not sure if there are any negative side effects such as blowing up my MB.

  6. #6
    Join Date
    Apr 2007
    Beans
    29

    Re: can't get lm-sensors 3.2 to work with i5 2500k, asrock motherboard

    Oh nice! Thanks for the answer!

    But since I'm a retard: how do I build, and make the computer use, the new drivers?

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •