Page 45 of 48 FirstFirst ... 354344454647 ... LastLast
Results 441 to 450 of 478

Thread: HOW TO: Install and configure lm-sensors

  1. #441
    Join Date
    Feb 2009
    Beans
    122

    Re: HOW TO: Install and configure lm-sensors

    Any ideas?

  2. #442
    Join Date
    Feb 2008
    Location
    I'm lost ... HELP!
    Beans
    1,014
    Distro
    Xubuntu

    Re: HOW TO: Install and configure lm-sensors

    Quote Originally Posted by akernan View Post
    Any ideas?
    Try changing your /etc/modules to :
    Code:
    # /etc/modules: kernel modules to load at boot time.
    #
    # This file contains the names of kernel modules that should be loaded
    # at boot time, one per line. Lines beginning with "#" are ignored.
    
    lp
    rtc
    
    #lm-sensors & i2c
    
    modprobe coretemp
    /usr/bin/sensors -s
    
    #cpuid
    #i2c-i801
    #i2c-dev
    #coretemp
    If that helps you can try removing the red #'s one by one.
    Last edited by miegiel; October 16th, 2011 at 04:30 PM.

  3. #443
    Join Date
    Feb 2008
    Location
    I'm lost ... HELP!
    Beans
    1,014
    Distro
    Xubuntu

    Re: HOW TO: Install and configure lm-sensors

    Quote Originally Posted by Little Blue View Post
    Hi, I recently installed a few updates on my lucid LTS box and now lm-sensors no longer works. I had a lot of trouble getting it working to begin with and now I'm extremely lost.

    This is the output of sensors-detect using the default options:

    Code:
    # sensors-detect revision 5946 (2011-03-23 11:54:44 +0100)
    # System: Packard Bell ixtreme M5800
    
    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): 
    Module cpuid loaded successfully.
    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
    AMD Family 12h and 14h thermal sensors...                   No
    Intel digital thermal sensor...                             Success!
        (driver `coretemp')
    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'...               No
    Trying family `ITE'...                                      Yes
    Found `ITE IT8721F/IT8758E Super IO Sensors'                Success!
        (address 0xa10, driver `it87')
    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): 
    
    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): 
    Using driver `i2c-i801' for device 0000:00:1f.3: Intel 3400/5 Series (PCH)
    Module i2c-i801 loaded successfully.
    Module i2c-dev loaded successfully.
    
    Next adapter: SMBus I801 adapter at 0400 (i2c-0)
    Do you want to scan it? (yes/NO/selectively): 
    
    Now follows a summary of the probes I have just done.
    Just press ENTER to continue: 
    
    Driver `it87':
      * ISA bus, address 0xa10
        Chip `ITE IT8721F/IT8758E Super IO Sensors' (confidence: 9)
    
    Driver `coretemp':
      * Chip `Intel digital thermal sensor' (confidence: 9)
    
    Do you want to overwrite /etc/sysconfig/lm_sensors? (YES/no): 
    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.
    
    Unloading i2c-dev... OK
    Unloading i2c-i801... OK
    Unloading cpuid... OK
    I have copied files around as suggested as I would like to to start at boot. When a reboot didn't get things working I then tried to start the service manually, service lm-sensors start, but I get this error message: .: 39: Can't open /etc/init.d/functions. Looking in my /etc/init.d directory, there is no functions file!

    sensors just gives
    Code:
    acpitz-virtual-0
    Adapter: Virtual device
    temp1:        +30.0°C  (crit = +110.0°C)
    which is a far cry from what it used to produce. I don't actually know what its attempting to measure there but it doesn't tally up with what the bios measurements are, whatever it is...

    /etc/modules contains
    Code:
    # /etc/modules: kernel modules to load at boot time.
    #
    # This file contains the names of kernel modules that should be loaded
    # at boot time, one per line. Lines beginning with "#" are ignored.
    
    lp
    modprobe
    modprobe
    
    # For temperature sensing
    coretemp
    it87
    I've been looking around and other scripts that have issues with a missing functions file tend to just comment an offending line out. Other times I've seen it get replaced with /lib/lsb/init-functions, which I do have. Is this the safest thing to do or is there some unmet dependency that hasn't been met / did I miss something?

    Any help's appreciated, and if anyone needs any more info please let me know!

    Cheers!
    See what happens if you remove 1 of the modprobe lines /etc/modules. I know no sane reason to have it in there twice, though your problem might be caused by something else.

  4. #444
    Join Date
    Feb 2009
    Beans
    122

    Re: HOW TO: Install and configure lm-sensors

    Quote Originally Posted by miegiel View Post
    Try changing your /etc/modules to :
    Code:
    # /etc/modules: kernel modules to load at boot time.
    #
    # This file contains the names of kernel modules that should be loaded
    # at boot time, one per line. Lines beginning with "#" are ignored.
    
    lp
    rtc
    
    #lm-sensors & i2c
    
    modprobe coretemp
    /usr/bin/sensors -s
    
    #cpuid
    #i2c-i801
    #i2c-dev
    #coretemp
    If that helps you can try removing the red #'s one by one.
    This did not help, coretemp would not load.

  5. #445
    Join Date
    Feb 2008
    Location
    Birmingham, UK
    Beans
    38
    Distro
    Ubuntu 12.04 Precise Pangolin

    Re: HOW TO: Install and configure lm-sensors

    Quote Originally Posted by miegiel View Post
    See what happens if you remove 1 of the modprobe lines /etc/modules. I know no sane reason to have it in there twice, though your problem might be caused by something else.
    Cheers, I dunno how that happened, makes no sense... Ultimately though, didn't help... I still get that error when I try to start the service...
    Code:
    blue@ruby:~$ sudo service lm-sensors start
    .: 39: Can't open /etc/init.d/functions

  6. #446
    Join Date
    Feb 2008
    Location
    I'm lost ... HELP!
    Beans
    1,014
    Distro
    Xubuntu

    Re: HOW TO: Install and configure lm-sensors

    @Little Blue
    Do you remember if you installed lm-sensors from the ubuntu repository or compiled it from the http://www.lm-sensors.org source?

    AFAIK /etc/init.d/functions shouldn't exist in ubuntu, but the source code from lm-sensors.org might expect it to exist. There is also a naming issue, ubuntu (and debian) use lm-sensors, while lm-sensors.org uses lm_sensors (note the - and _). This might cause problems updating related packages.

    @akernan
    Did you install/upgrade to 11.10 yet? If so/not, consider doing a clean install instead of upgrading. It might solve your problems, but remember to backup the important stuff (or everything) in your home first.

  7. #447
    Join Date
    Feb 2009
    Beans
    122

    Re: HOW TO: Install and configure lm-sensors

    Quote Originally Posted by miegiel View Post
    @Little Blue
    Do you remember if you installed lm-sensors from the ubuntu repository or compiled it from the http://www.lm-sensors.org source?

    AFAIK /etc/init.d/functions shouldn't exist in ubuntu, but the source code from lm-sensors.org might expect it to exist. There is also a naming issue, ubuntu (and debian) use lm-sensors, while lm-sensors.org uses lm_sensors (note the - and _). This might cause problems updating related packages.

    @akernan
    Did you install/upgrade to 11.10 yet? If so/not, consider doing a clean install instead of upgrading. It might solve your problems, but remember to backup the important stuff (or everything) in your home first.
    I didn't update to 11.10 yet, still on 10.10. I installed lm-sensor from the repo and got a newer version from lm-sensor.org site.

  8. #448
    Join Date
    Feb 2008
    Location
    I'm lost ... HELP!
    Beans
    1,014
    Distro
    Xubuntu

    Re: HOW TO: Install and configure lm-sensors

    Quote Originally Posted by akernan View Post
    I didn't update to 11.10 yet, still on 10.10. I installed lm-sensor from the repo and got a newer version from lm-sensor.org site.
    That might be causing your problems too then. IIRC lm-sensors is installed in ubuntu by default now. So you only need to run
    Code:
    sudo sensors-detect
    and you're done. Note that the how-to in the first post is from October 2004, you should use it for inspiration only. And if you do want to compile it from source, I suspect you should uninstall (or even purge) the lm-sensors from the repo first.

    But it's time for you to move on to 11.10. Since 10.10 is not a LTS release you will only get updates for a year after it's release (October 2010).
    Last edited by miegiel; October 17th, 2011 at 08:39 PM. Reason: I was wrong, stroked out :)

  9. #449
    Join Date
    Sep 2011
    Beans
    17

    Re: HOW TO: Install and configure lm-sensors

    Please help me, this is my output :

    themoon@Marksman:~$ sudo sensors-detect #YES for all Y/N question
    # sensors-detect revision 5984 (2011-07-10 21:22:53 +0200)
    # Board: Intel Corporation DG31GL

    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): YES
    Module cpuid loaded successfully.
    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
    AMD Family 12h and 14h thermal sensors... No
    AMD Family 15h thermal sensors... No
    AMD Family 15h power sensors... No
    Intel digital thermal sensor... Success!
    (driver `coretemp')
    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): YES
    Probing for Super-I/O at 0x2e/0x2f
    Trying family `National Semiconductor/ITE'... No
    Trying family `SMSC'... No
    Trying family `VIA/Winbond/Nuvoton/Fintek'... Yes
    Found `Winbond W83627DHG Super IO Sensors' Success!
    (address 0x290, driver `w83627ehf')
    Probing for Super-I/O at 0x4e/0x4f
    Trying family `National Semiconductor/ITE'... 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): YES
    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): YES
    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): YES
    Using driver `i2c-i801' for device 0000:00:1f.3: Intel 82801G ICH7
    Module i2c-i801 loaded successfully.
    Module i2c-dev loaded successfully.

    Next adapter: i915 gmbus disabled (i2c-0)
    Do you want to scan it? (YES/no/selectively): YES

    Next adapter: i915 gmbus ssc (i2c-1)
    Do you want to scan it? (YES/no/selectively): YES

    Next adapter: i915 GPIOB (i2c-2)
    Do you want to scan it? (YES/no/selectively): YES

    Next adapter: i915 gmbus vga (i2c-3)
    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'... No
    Probing for `EDID EEPROM'... No

    Next adapter: i915 GPIOA (i2c-4)
    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'... No
    Probing for `EDID EEPROM'... No

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

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

    Next adapter: i915 gmbus dpc (i2c-7)
    Do you want to scan it? (YES/no/selectively): YES

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

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

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

    Next adapter: i915 gmbus reserved (i2c-11)
    Do you want to scan it? (YES/no/selectively): YES

    Next adapter: i915 gmbus dpd (i2c-12)
    Do you want to scan it? (YES/no/selectively): YES

    Next adapter: i915 GPIOF (i2c-13)
    Do you want to scan it? (YES/no/selectively): YES

    Next adapter: SMBus I801 adapter at f000 (i2c-14)
    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

    Now follows a summary of the probes I have just done.
    Just press ENTER to continue:

    Driver `w83627ehf':
    * ISA bus, address 0x290
    Chip `Winbond W83627DHG Super IO Sensors' (confidence: 9)

    Driver `coretemp':
    * Chip `Intel digital thermal sensor' (confidence: 9)

    Do you want to overwrite /etc/sysconfig/lm_sensors? (YES/no): YES
    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.

    Unloading i2c-dev... OK
    Unloading i2c-i801... OK
    Unloading cpuid... OK
    What am I to do in next step ?

    This is my /etc/modules :

    # /etc/modules: kernel modules to load at boot time.
    #
    # This file contains the names of kernel modules that should be loaded
    # at boot time, one per line. Lines beginning with "#" are ignored.

    psmouse
    mousedev
    ide-cd
    ide-disk
    ide-generic
    lp

    #For lm-sensors, i2c modules
    it87
    i2c-viapro
    i2c-isa
    but Ican not run /etc/init.d/module-init-tools, it shows:
    Usage: /etc/init.d/module-init-tools COMMAND

    my /etc/modprobe.d/local:
    alias char-major-89 i2c-dev
    But when i run update-modules, it shows:
    update-modules: command not found

    I tried
    sudo modprobe i2c-sensor

    WARNING: All config files need .conf: /etc/modprobe.d/local, it will be ignored in a future release.
    WARNING: All config files need .conf: /etc/modprobe.d/aliases, it will be ignored in a future release.
    FATAL: Module i2c_sensor not found.
    the same for
    sudo modprobe i2c-viapro
    sudo modprobe i2c-isa
    sudo modprobe it87



    themoon@Marksman:~$ sensors
    No sensors found!
    Make sure you loaded all the kernel drivers you need.
    Try sensors-detect to find out which these are.
    How can I fix this
    Iam using Ubuntu oneiric

  10. #450
    Join Date
    Feb 2008
    Location
    Birmingham, UK
    Beans
    38
    Distro
    Ubuntu 12.04 Precise Pangolin

    Re: HOW TO: Install and configure lm-sensors

    Quote Originally Posted by miegiel View Post
    @Little Blue
    Do you remember if you installed lm-sensors from the ubuntu repository or compiled it from the http://www.lm-sensors.org source?

    AFAIK /etc/init.d/functions shouldn't exist in ubuntu, but the source code from lm-sensors.org might expect it to exist. There is also a naming issue, ubuntu (and debian) use lm-sensors, while lm-sensors.org uses lm_sensors (note the - and _). This might cause problems updating related packages.
    It was a bit of both. Tried the repo version but that didn't recognise my sensors (it was a fairly new setup at the time), and went to lm-sensors.org to see if there was anything there that hadn't filtered down into the repos yet. I compiled it from there and eventually I'd managed to coax it into working, which its now stopped.

    I'm going to guess then the best thing to do is try and purge my system of all this stuff and reinstall from the repos to see if they now work? I guess sudo aptitude remove lm-sensors --purge will uninstall anything added by the repos but removing the stuff I compiled?

    Thanks for your help

Page 45 of 48 FirstFirst ... 354344454647 ... LastLast

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
  •