[SOLVED] lm-sensors

Questions about hardware,drivers and peripherals
Forum rules
Before you post please read this

[SOLVED] lm-sensors

Postby Jamesc359 on Mon Oct 01, 2012 6:40 pm

Before I upgraded to LM 13 Maya 64Bit XFCE, I was using LM 12 Lisa LXDE 32Bit and I had access to a large variety of sensors through lm-sensors. Mostly CPU, GPU, System and a couple other temps as well as 3 fan speeds. After the upgrade I've lost access to everything except for the CPU sensor. Since I often times log into my computer remotely I have a bit of a desire to keep an eye on the current hardware status.

Any ideas and/or solutions as to why I don't have access to them after the upgrade would be greatly appreciated.

Thanks,
James

Code: Select all
james ~ $ sudo sensors-detect
[sudo] password for james:
# sensors-detect revision 6057 (2012-06-01 17:47:27 +0200)
# System: Gateway W3107 [SYS-xxxxxx]
# Board: First International Computer, Inc. K8MC51G

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
Module cpuid loaded successfully.
Silicon Integrated Systems SIS5595...                       No
VIA VT82C686 Integrated Sensors...                          No
VIA VT8231 Integrated Sensors...                            No
AMD K8 thermal sensors...                                   Success!
    (driver `k8temp')
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...                             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/ITE'...               No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Nuvoton/Fintek'...               No
Trying family `ITE'...                                      No
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor/ITE'...               No
Trying family `SMSC'...                                     Yes
Found `SMSC DME1737 Super IO'                               
    (hardware monitoring capabilities accessible via SMBus only)

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-nforce2' for device 0000:00:0a.1: nVidia Corporation nForce SMBus (MCP51)
Module i2c-dev loaded successfully.

Next adapter: SMBus nForce2 adapter at 1c00 (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'...                                 Yes
    (confidence 8, not a hardware monitoring chip)
Probing for `EDID EEPROM'...                                No
Client found at address 0x51
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 Yes
    (confidence 8, not a hardware monitoring chip)

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

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

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

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

Driver `k8temp' (autoloaded):
  * Chip `AMD K8 thermal sensors' (confidence: 9)

No modules to load, skipping modules configuration.

Unloading i2c-dev... OK
Unloading cpuid... OK



Code: Select all
james ~ $ sensors
acpitz-virtual-0
Adapter: Virtual device
temp1:        +40.0°C  (crit = +75.0°C)

k8temp-pci-00c3
Adapter: PCI adapter
Core0 Temp:   +38.0°C 
Last edited by Jamesc359 on Thu Oct 11, 2012 11:02 pm, edited 1 time in total.
“Gosh, you've... really got some nice toys here.”
User avatar
Jamesc359
Level 3
Level 3
 
Posts: 125
Joined: Sun May 06, 2012 1:42 pm

Linux Mint is funded by ads and donations.
 

Re: lm-sensors

Postby xenopeek on Mon Oct 08, 2012 8:49 am

This might be due to difference in kernels or available modules. Do you still have the Linux Mint 12 installation CD/DVD/USB? You might re-run sensors-detect from there to see what other modules where found to be loaded then.
User avatar
xenopeek
Level 21
Level 21
 
Posts: 14987
Joined: Wed Jul 06, 2011 3:58 am
Location: The Netherlands

Re: lm-sensors

Postby Jamesc359 on Thu Oct 11, 2012 10:59 pm

Thank you for your reply Vincent. I tried your suggestion, unfortunately it didn't help.

I did some extensive searching around and found that they've changed how the kernel handles resource conflicts between drives and the BIOS.

Long story short adding this line to my boot options fixed it.
acpi_enforce_resources=lax

Naturally I'd prefer a better long term solution, but this makes me happy for now. :)
“Gosh, you've... really got some nice toys here.”
User avatar
Jamesc359
Level 3
Level 3
 
Posts: 125
Joined: Sun May 06, 2012 1:42 pm


Return to Hardware Support

Who is online

Users browsing this forum: No registered users and 10 guests