Just to show you;
sudo sensors-detect
# sensors-detect revision 5818 (2010-01-18 17:22:07 +0100)
# System: Hewlett-Packard HP 625 (laptop)
# Board: Hewlett-Packard 1475
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
AMD Family 10h thermal sensors... Success!
(driver `k10temp')
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
Trying family `SMSC'... Yes
Found `SMSC FDC37B72x Super IO'
(
no hardware monitoring capabilities)
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
.............................................. 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-piix4' for device 0000:00:14.0: ATI Technologies Inc SB600/SB700/SB800 SMBus
Module i2c-dev loaded successfully.
Next adapter: Radeon i2c bit bus VGA (i2c-0)
Do you want to scan it? (YES/no/selectively): y
Next adapter: Radeon i2c bit bus LVDS (i2c-1)
Do you want to scan it? (YES/no/selectively): y
Client found at address 0x50
Probing for `EDID EEPROM'... Yes
(confidence 8, not a hardware monitoring chip)
Next adapter: Radeon i2c bit bus HDMI (i2c-2)
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:
Driver `k10temp' (autoloaded):
* Chip `AMD Family 10h thermal sensors' (confidence: 9)
No modules to load, skipping modules configuration.
Unloading i2c-dev... OK
-----------------------------------
The points is my laptop was working all fine and after the trouble started i installed sensors.
What i mentioned before is:
What has a graphic driver to do with my trip points and fan speed and why are they altered.
The moment i am switching maverick kernels and the best working so far is linux-headers-2.6.35-02063513. But all cut fan of at 70°C and i like to find the routine and the one who made it. This might be a simple bug but since i have seen Unity i am not sure what it is and i like to find out. You should see what happens when i use a proprietor graphic driver. All readings get haywire and heat build up or cooling is in seconds. Trip points get altered and with changing kernel just the same. Trip points get altered.
What i have found so far is that i might install or remove all packages intended to read temperature and control fan without any effect (except i have no readout)
Though, to repeat it for everybody to understand me better:- I am too stubborn to switch my OS now.
- It is not a Bios related issue
- It is no sensors issue
- fancontrol does not work on hp625 (/usr/sbin/pwmconfig: There are no pwm-capable sensor
- modules installed)
- Switching kernels alters trip points
- Switching graphic driver alters trip points
Why has my lowest trip point changed from 48°C to 70°C
Why are hwmon values used as trip point (70°C)
Since there should be a lower and a higher value for trip points, the routine i search for is probably mixing trip point values with hwmon values.
Why is it persistent:
Since i have changed kernels there should have been some change and was, but not with trip point for lowest fan speed.
I gave Lubuntu amd64 a try on a pen stick and had the same values.
If you dig around with google you find that all Ubuntu based distributions have similar problems with overheating (Mint,Überstudent,Lu-Ku-Xu and Ubuntu).
If i would think this is only my laptop or computer i had another OS for a long time but as i see the thing there are many people affected and since this funny effect
keeps Laptops silent the average User will not even notice.
To my opinion there is a routine introduced within Ubuntu kernels that keeps silence and renders my Laptop into a piece of chunk.
The greatest mistake i have done so far was to upgrade to 11.04. In order to downgrade i had to clean the harddrive and now the package history i would relish is missing. Accidental i have deleted my backup disk. (making another pen drive i chose the wrong drive to be deleted and 550MB are gone).
I have paid too much for my stupidity than to leave the thing at peace and use another OS.
Since grep '# include <linux/hwmon>' *.h
does not give any reply (probably a security feature) finding the routine is difficult.
Is there a chance to find a list of routines invoked at boot time???
with best regards your ultimate stubborn M.Peters