Posted: Sat Sep 01, 2007 3:22 am
Hi Pascal_TTH,
so sorry, it's not your fault it's mine, coding is just not really correct.
I got the same effect on my T40 coming up from standby:
fan control byte is read as "128", that's due to waking up and should be "1" (from last smart mode). The value of 128 is NOT found to be strange, as 128 means BIOS (as 64 means full speed). The values of 0 to 7, 64 and 128 are accepted as not strange, that has to be modified.
I made some data outlet in fancontrol v23 (csv,txt) to check this and here is my file:
http://staff-www.uni-marburg.de/~schmit ... st_csv.txt
Don't ruin your nights
troubadix
edit 12:27: now the code is changed
But still it could happen that coming from standyby/hibernate and fan control byte value is accidentally set to 1 to 7 by another process (not seen till now), fan will start with cooling down speed (as if coming from higher temps). There is no last resort
so sorry, it's not your fault it's mine, coding is just not really correct.
I got the same effect on my T40 coming up from standby:
fan control byte is read as "128", that's due to waking up and should be "1" (from last smart mode). The value of 128 is NOT found to be strange, as 128 means BIOS (as 64 means full speed). The values of 0 to 7, 64 and 128 are accepted as not strange, that has to be modified.
I made some data outlet in fancontrol v23 (csv,txt) to check this and here is my file:
http://staff-www.uni-marburg.de/~schmit ... st_csv.txt
Don't ruin your nights
edit 12:27: now the code is changed
But still it could happen that coming from standyby/hibernate and fan control byte value is accidentally set to 1 to 7 by another process (not seen till now), fan will start with cooling down speed (as if coming from higher temps). There is no last resort

