Sensors probems

Soupstuffs · 2009-10-20 21:05:32

Hello! I'm having some major problems with my computer sensors. I'm running on 2.6.31-ARCH (i686) on a Dell Vostro 1510.

I really want to be able to read my HDD temp, my CPU temps, my GUI temp, my battery temp, and my fan speed. I would also like to be able to detect my brightness and volume on Conky, but that's another story. Despite all of that, I can barely get my CPU sensors to work. I already installed lm_sensors and hddtemp and all of that nonsense. Here's what happens when I run sensors-detect.

[justin@Arch ~]$ sudo sensors-detect
Password: 
# sensors-detect revision 5729 (2009-06-02 15:51:29 +0200)
# System: Dell Inc. Vostro1510
# Board: Dell Inc. 0R780K

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 K10 thermal sensors...                                  No
Intel Core family thermal sensor...                         Success!
    (driver `coretemp')
Intel AMB FB-DIMM thermal sensor...                         No
VIA C7 thermal and voltage sensors...                       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/Fintek'...                       No
Trying family `ITE'...                                      No
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor'...                   No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/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 82801H ICH8
Module i2c-dev loaded successfully.

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

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

Do you want to overwrite /etc/conf.d/lm_sensors? (YES/no): n
To load everything that is needed, add this to one of the system
initialization scripts (e.g. /etc/rc.d/rc.local):

#----cut here----
# Chip drivers
modprobe coretemp
/usr/bin/sensors -s
#----cut here----

If you have some drivers 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 the needed
modules are loaded.

Unloading i2c-dev... OK

Yup, those are the only two sensors I have. Really strange for a new laptop, huh?

Additionally, my readings are as follows:

coretemp-isa-0000
Adapter: ISA adapter
Core 0:      +57.0°C  (high = +100.0°C, crit = +100.0°C)  

coretemp-isa-0001
Adapter: ISA adapter
Core 1:      +56.0°C  (high = +100.0°C, crit = +100.0°C)

I have no idea how they can be so high. It feels much, much cooler to the touch.

Can someone help me troubleshoot this?

Thanks in advance,
Soupstuffs

P.S. On a side note, if I keep setting the clock on my bios and deleting /var/lib/hwclock/adjtime yet the time and date are STILL incredibly off, does that mean there's something wrong with the clock battery? Is there anything else that could be causing it, because it was working fine until last week or so when I was trying to get the boot time lower. It just seems strange to me that a laptop that isn't even a year old would do that already.

jargoman · 2009-10-21 18:53:04

Ya newer laptops tend to have less support for sensors and what not as the hardware is new and the open source community has not caught up yet and the manufacturers have not released linux drivers.

Also with the newer cpu's they tend to run hotter. My amd athlon is running at 60c at this moment.

Soupstuffs · 2009-10-23 21:05:26

I think that's it.

Oh well, thanks for the reply. =/

Arch Linux

#1 2009-10-20 21:05:32

Sensors probems

#2 2009-10-21 18:53:04

Re: Sensors probems

#3 2009-10-23 21:05:26

Re: Sensors probems

Board footer