@
Bram77
Found a few of lm_sensors "tricks" this is obviously ION1 orientated, more specifically the 330HT but seem to work with 270 (like acer etc)
For the ION1 in particular we dont want to read
cpu coretemp-isa-0000 values (for advancedsettings.xml) because these values are wrong!
28C (we wish)
So we want instead to query the
nct6775-isa-0290 temperatures, the more accurate "100% to bios readings" is:
Code:
cputempcommand>echo "$(sensors -u | tail -n64 | grep temp1_input | awk '{print $2 }' |awk '{printf("%d\n",$1 + 0.5);}') C"</cputempcommand>
That being so, if we ever issue "sensors" command the output is showing "ALARM" for the ION1 (
in1 in4 in5 there is no in6 or fan 3 in ION1,
not that we can do anything with fans just yet) this is a either to calculate values or tell sensors3.conf to ignore the ALARM values, personally, I prefer to have things along normal(ish),
Here your spolied for choices, you can do nothing (leave the sensor3.conf untouched, use the actual present values use sensor3, up to you!
For the
sensors3.conf which "calculates" all present values here
For the
sensors3.conf which ignores all "ALARM" except SYSTIN (
we give this some values for min/max) and Not present FAN3 here
To shut up, the incessant questions at sensors-detect (this is untested either way, because no idea how to implement in script) found via
Automatic lm_sensors deployment
archwiki website Wrote:If you wish to deploy lm-sensors on multiple different Linux machines issue is that sensors-detect ask you quite a few questions. There are few tricks that you can use to automate replies.
First one is if you wish to accept defaults which sensors-detect suggest you need just to press [ENTER] all the time. To automate this use this one liner:
Code:
# yes "" | sensors-detect
If you wish to override defaults and answer YES to all questions then use this oneliner:
Code:
# yes | sensors-detect
I always tried to get the fan controllers working but never found a way I could figure out,
quietfan looks promising but its above my paygrade.
however if you do this:
found via here
Code:
perl -le 'sysopen($raw_port,"/dev/port",O_RDWR); foreach my $p (0x4932,0x4934,0x4936) {
sysseek $raw_port,$p,0;sysread $raw_port,$res,2; printf("0x%x: %s\n",$p,unpack("S",$res)*60); }'
You can actually get the speed values for minimum/medium/high, so you can in theory control these from terminal or in some sort of control program like
quietfan, but like I said above my paygrade! I could never get a reply from the guy there.
cheers