OOPS!
They say that hearing is the last to go. So mental clarity must be the first to go.
![Surprised :o](./images/smilies/icon_surprised.gif)
That's ominous. jakfish has just reported that fanspeed control is generally not working, unless you manually restart the fan control daemon script.rhadon wrote:CPU speed changing works fine, testing fan control takes more time
Code: Select all
#grep "Celeron" /proc/cpuinfo
Code: Select all
grep 'Celeron' /proc/cpuinfo | cut -d '(' -f2 | tail -c8
Code: Select all
# grep "Celeron" /proc/cpuinfo
model name : Intel(R) Celeron(R) M processor 900MHz
Code: Select all
# grep 'Celeron' /proc/cpuinfo | cut -d '(' -f2 | tail -c8
Celeron
Code: Select all
model name : Intel(R) Atom(TM) CPU N270 @ 1.6 GHz
Code: Select all
# cat /sys/devices/platform/eeepc/cpufv
770
Code: Select all
# cat /sys/devices/platform/eeepc/cpufv
768
Code: Select all
# cat /sys/devices/platform/eeepc/cpufv
769
A word of caution guys;rhadon wrote:After reboot it starts with the CPU speed 900 MHz, no matter I selected before.
Code: Select all
cat /proc/eee/fsb
Yes, that's what the Ubuntu Eee packages do ... but it's not necessarily the best approach.01micko wrote:It's time for a script in /root/Startup to execute the last remembered state.
Yes, I always did since I started reading this threadtempestuous wrote:Rolf, immediately after booting, I suggest you run this command -Code: Select all
cat /proc/eee/fsb