You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have successfully been running tpfanco on Ubuntu 14.04 (Trusty) on my X220
Tablet for quite some time, using Stephan's patch (from the discussion in issue
#2).
Yesterday, I decided to update the kernel and X stack using Ubuntu's "LTS
Enablement Stacks", see https://wiki.ubuntu.com/Kernel/LTSEnablementStack.
In other words, I ran the following command:
$ sudo apt-get install --install-recommends linux-generic-lts-utopic xserver-xorg-lts-utopic libgl1-mesa-glx-lts-utopic libegl1-mesa-drivers-lts-utopic
Afterwards, I noticed that tpfanco did not work properly anymore. In fact, it's
somewhat dangerous, since the fan is never turned on and will be stuck on 0 RPM
when tpfand is running. I didn't notice this until the powerclamp driver
(http://askubuntu.com/a/482326) kicked in to prevent the CPU from overheating.
I don't nearly have sufficient knowledge to determine what causes the issue,
and how specific the issue is to my setup. In any case, it does mean that using
tpfanco could currently be seriously unsafe(!).
In the tpfanco-admin GUI, no temperatures show up anymore, see the attached
screenshots.
To summarise my setup:
- Ubuntu 14.04, 64bit, updated using LTS Enablement Stack.
- Kernel version 3.16.0-31-generic (after updating using the Enamblement Stack,
3.13 before updating)
- Intel P-state enabled
- tpfand 0.95.3, patched with Stephan's patch for new thinkpads (from the
discussion in issue #2)
Original issue reported on code.google.com by [email protected] on 18 Mar 2015 at 12:02
I found the problem:
The system temperature inodes have been moved from
/sys/devices/platform/coretemp.0/temp*_input
to
/sys/devices/platform/coretemp.0/hwmon/hwmon1/temp*_input
I created a patch to account for this. The patch can be found in the discussion
of issue #2.
This issue can be closed.
Original issue reported on code.google.com by
[email protected]
on 18 Mar 2015 at 12:02Attachments:
The text was updated successfully, but these errors were encountered: