ThinkWiki - User contributions [en]

Code/tp power monitor.py

2006-09-09T06:21:07Z

Micampe:

<pre>#!/usr/bin/python

# COPYRIGHT (C) 2006 Matthew Garman
# matthew (dot) garman (at) gmail (dot) com
# License: MIT <http://www.opensource.org/licenses/mit-license.php>

import sys, time, getopt, os, re

class tpPowerMonitorDataSource:

# The name of the file to parse for needed data (data_source_file) OR
# the name of a command whose output will be read as a file
# (os.popen(shell_command)).
#
# Typically, data_source_file will be something from /proc (or
# possibly /sys), and shell_command will be a utility+arguments such
# as "iwconfig eth1 power".
#
# Note that you should set EITHER data_source_file OR shell_command,
# but not both.
data_source_file = None
shell_command = None

# The line number of the data file containing our data OR the string
# that marks the beginning of the line in which we're interested
# (startswith_string) OR a regular expression to key the data for
# which we're looking (regexp_pattern).
line_number = None
startswith_string = None
regexp_pattern = None

# The string that delimits the line containing our data. This will be
# used as the parameter to split(). Note that you can leave this as
# None to split on whitespace.
split_string = None

# A mapping of data names to indices in the split string.
name_index_map = dict()

def __init__(self, file, cmd, line, swstr, pat, splstr, map):
self.data_source_file = file
self.shell_command = cmd
self.line_number = line
self.startswith_string = swstr
self.regexp_pattern = pat
self.split_string = splstr
self.name_index_map = map

def printMembers(self):
print "\t" + 'self.data_source_file = ' + str(self.data_source_file)
print "\t" + 'self.shell_command = ' + str(self.shell_command)
print "\t" + 'self.line_number = ' + str(self.line_number)
print "\t" + 'self.startswith_string = ' + str(self.startswith_string)
print "\t" + 'self.regexp_pattern = ' + str(self.regexp_pattern)
print "\t" + 'self.split_string = ' + str(self.split_string)
print "\t" + 'self.name_index_map = ' + str(self.name_index_map)

def readData(self, d):
# open the data source file or run the command that will produce
# the data
file = None
if self.data_source_file:
file = open(self.data_source_file, 'r')
elif self.shell_command:
file = os.popen(self.shell_command)
else:
print 'error: no data source defined'
self.printMembers()
# read the contents of the file into a list and close the file
lines = None
if file:
lines = file.readlines()
file.close()
else:
print 'error: data file not opened'
self.printMembers()
# now get the line in the file with our data
line = None
if lines:
if None != self.line_number:
line = lines[self.line_number]
elif self.startswith_string:
for l in lines:
if l.startswith(self.startswith_string):
line = l
break
elif self.regexp_pattern:
for l in lines:
if re.compile(self.regexp_pattern).match(l):
line = l
break
else:
print 'error: no lines in data file'
self.printMembers()
# now get the data we want from the line itself
if line:
fields = line.split(self.split_string)
for key in self.name_index_map.keys():
d[key] = fields[self.name_index_map[key]].strip()
else:
print 'error: could not find line with data in file'
self.printMembers()

# END --- class tpPowerMonitorDataSource

tp_data_sources = [

tpPowerMonitorDataSource(
'/proc/cpuinfo', # data file
None, # shell command
None, # line index
'cpu MHz', # startswith() string
None, # regexp pattern
':', # split string
{'proc_cpuinfo_cpu_mhz': 1} # name-to-index map
),

# http://thinkwiki.org/wiki/Ipw2200#Power_Management
tpPowerMonitorDataSource(
None, # data file
'/sbin/iwpriv eth1 get_power', # shell command
0, # line index
None, # startswith() string
None, # regexp pattern
':', # split string
{'iwpriv_get_power': 2} # name-to-index map
),

# http://forums.gentoo.org/viewtopic-t-447841.html
# see post from ruben on Wed Mar 29, 2006 4:09 am
tpPowerMonitorDataSource(
None,
'/usr/bin/sudo /sbin/hdparm -C /dev/sda',
None,
' drive state is',
None,
':',
{'hard_drive_power_state': 1}
),

# http://thinkwiki.org/wiki/Thermal_sensors
tpPowerMonitorDataSource(
'/proc/acpi/ibm/thermal',
None,
0,
None,
None,
None,
{'ibm_thermal_cpu': 1,
'ibm_thermal_hdaps': 2,
'ibm_thermal_pmcia': 3,
'ibm_thermal_gpu': 4,
'ibm_thermal_batt_fl': 5,
'ibm_thermal_batt_br': 7 }
),

# http://mailman.linux-thinkpad.org/pipermail/linux-thinkpad/2006-July/034738.html
tpPowerMonitorDataSource(
'/proc/acpi/processor/CPU/power',
None,
None,
'bus master activity',
None,
':',
{'bus_master_activity': 1}
),

tpPowerMonitorDataSource(
'/proc/acpi/battery/BAT0/state',
None,
None,
'present rate:',
None,
None,
{'battery0_state_present_rate': 2}
),

tpPowerMonitorDataSource(
None,
'/usr/bin/sudo /usr/sbin/radeontool dac',
0,
None,
None,
None,
{'radeontool_dac_ext_vga': -1}
),

tpPowerMonitorDataSource(
None,
'/usr/bin/sudo /usr/sbin/radeontool light',
0,
None,
None,
None,
{'radeontool_light_lcd': -1}
),

# http://forums.gentoo.org/viewtopic-t-343029-highlight-rovclock.html
tpPowerMonitorDataSource(
None,
'/usr/bin/sudo /usr/sbin/rovclock -i',
None,
'Core: ',
None,
None,
{'rovclock_gpu_clock': 1,
'rovclock_mem_clock': 4 }
),

tpPowerMonitorDataSource(
None,
'/sbin/iwconfig eth1',
None,
None,
'.*Power Management.*',
':',
{'wireless_power_mgmt_state': 1}
),

tpPowerMonitorDataSource(
'/proc/loadavg',
None,
0,
None,
None,
None,
{'proc_loadavg_1min': 0,
'proc_loadavg_5min': 1,
'proc_loadavg_15min': 2 }
),
]
log_data = list()
poll_freq_hz = 1
run_time_sec = 60*60
logfile = None

def collectPowerData():
global run_time_sec
global poll_freq_hz
global log_data
global logfile
global tp_data_sources

log = None
if logfile:
log = open(logfile, 'w')
log.write("time, data\n")
end_t = time.time()+run_time_sec
while time.time() < end_t:
datum = dict()
for dsrc in tp_data_sources:
dsrc.readData(datum)
log_data.append(datum)
if log: log.write(str(time.time()) + ', ' + str(datum) + "\n")
time.sleep(1.0/float(poll_freq_hz))
if log: log.close()

def createStats():
global log_data
global logfile
log = None
if logfile:
log = open(logfile, 'a')
if log: log.close()

def usage():
print 'Usage: ' + sys.argv[0] + \
'[-h] [-f freq_hz] [-t time_min] [-l logfile]'
print "\t-h Display this help"
print "\t-f freq_hz The polling frequency in Hertz, default=" \
+ str(poll_freq_hz)
print "\t-t time_min Total poll time in minutes, default=" \
+ str(run_time_sec/60)
print "\t-l logfile Write poll data to indicated log file"

def main():
global poll_freq_hz
global run_time_sec
global logfile

# parse options
# see: http://docs.python.org/lib/module-getopt.html
try:
opts, args = getopt.getopt(sys.argv[1:], "hf:t:l:")
except getopt.GetoptError:
usage()
sys.exit(2)
for o, a in opts:
if '-h' == o:
usage()
sys.exit()
if '-f' == o:
poll_freq_hz = int(a)
if '-t' == o:
run_time_sec = int(a)*60
if '-l' == o:
logfile = a

# do stuff
print 'running for ' + str(run_time_sec/60) + ' minutes'
print 'poll rate: ' + str(poll_freq_hz) + ' Hz'
print 'logfile: ' + str(logfile)
collectPowerData()
print '...done!'
print 'Data points collected: ' + str(len(log_data))
sum = 0
for d in log_data:
sum += int(d['battery0_state_present_rate'])
avg = float(sum) / float(len(log_data))
print 'Average power draw: ' + str(avg)
if logfile: log = open(logfile, 'a')
if log:
log.write('Average power draw: ' + str(avg))
log.close()

if __name__ == '__main__':
main()
</pre>

HDAPS

2006-06-04T09:24:43Z

Micampe: switch workspace by smacking your laptop

{| width="100%"
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__
|style="vertical-align:top" |
=== HDAPS - IBM Active Protection System Linux Driver ===
This is the Linux driver for monitoring the acceleratometer known as [[Active Protection System|IBM Active Protection System]].

The driver only enables reading of the acceleration data. It does '''not''' perform [[#Harddisk Protection|automatic disk head parking]]. But there are already some other useful [[#Applications|applications]] for HDAPS, using the {{path|/sys}} interface it provides.
|}

=== Features ===
*provides accelerometer values via sysfs
*provides a joystick type input device

=== Project Homepage / Availability ===
*[http://hdaps.sourceforge.net/ Project Homepage]
*The driver is included in the 2.6-mm series of kernels since August, 26th 2005.
*The driver is now in the mainline (2.6.14). (use as modul if you want use tp_smapi, Gentoo and X41)

=== Status ===
A driver is included in recent Linux kernels and is actively maintained.

=== How to install the driver ===
If you are using a version of the Linux kernel < 2.6.14, please upgrade. I struggled long and hard to get the driver working with an old version of the kernel, and it was a mess. I gave up, upgraded my kernel, and one recompile later, HDAPS was working.

=== Harddisk Protection ===
As mentioned above, the hdaps kernel driver is only responsible for reading the accelerometer data and exporting it through the sysfs interface. In order to use this information to protect the disk, some additional steps are required.

See [[How to protect the harddisk through APS]].

=== Input device support ===
The hdaps driver in the lastest kernels (2.6.14 and later?) also exports a joystick type input device, which can be used by games.

=== Applications ===
====Disk head parking====
* Kernel patch (apply using 'patch -p1 -l < hdaps_xx.patch')
**[http://lwn.net/Articles/154923/ disk park patch] <tt>an experimental patch for parking the disk (Linux 2.6.14 for 2.6.15 see below)</tt>
**[http://jenster.dyndns.org/files/blk_freeze-01-nodetection-for-2.6.14.patch disk park patch adapted for the t41p model] <tt> kernel 2.6.14 *([http://sourceforge.net/mailarchive/message.php?msg_id=13214288 capability detection disabled], no libata support)</tt>
**[http://jenster.dyndns.org/files/blk_freeze-01-nodetection-for-2.6.15.patch disk park patch adapted for the t41p model] <tt> kernel 2.6.15 *([http://sourceforge.net/mailarchive/message.php?msg_id=13214288 capability detection disabled], no libata support)</tt>
**[http://www.dresco.co.uk/hdaps/hdaps_protect.20060118.patch sata/ide disk protection patch for 2.6.15]
**[http://www.dresco.co.uk/hdaps/hdaps_protect.20060430.patch Latest sata/ide disk protection patch for 2.6.16]
**[http://whoopie.gmxhome.de/linux/patches/2.6.16-tj/05-hdaps_protect-20060430-for-2.6.16-tj.patch Latest sata/ide disk protection patch for use with the experimental hotplug patches] - See [[How_to_hotswap_UltraBay_devices]]
*Userspace daemon
**[http://www.dresco.co.uk/hdaps/hdapsd-20060409.c Latest userspace parking daemon]
*GUI monitoring
**[http://www.oakcourt.dyndns.org/projects/khdapsmon/ khdapsmon] <tt>KDE System Tray app similar to the Windows one (also at [http://www.kde-apps.org/content/show.php?content=34134 kde-apps.org])</tt>
**[http://www.dresco.co.uk/hdaps/gnome-hdaps-applet-20060120.tar.gz gnome-hdaps-applet] <tt>visual display of disk protection status in gnome panel</tt>
See [[How to protect the harddisk through APS]] for more information.

====Security & safety====
*[[Script for theft alarm using HDAPS]]

====Tilt monitoring====
*[http://www.mulliner.org/collin/gkibm-acpi.php gkhdaps] <tt>a GKrellM applet displaying tilt data</tt>
*[http://rlove.org/log/2005082203.html gnome-tilt] <tt>a gnome applet showing tilt data</tt>

====Visualisation (of ThinkPad orientation)====
*[http://rlove.org/log/2005082401.html hdaps-gl] <tt>a little app animating a 3D-ThinkPad</tt>
*[https://sourceforge.net/project/showfiles.php?group_id=138242 hdapsgl-applet] <tt> a GNOME applet animating a 3D-ThinkPad</tt>
*[https://sourceforge.net/project/showfiles.php?group_id=138242 wmadhps] <tt>a WindowMaker DockApp animating a 3D-ThinkPad</tt>
*[http://www.cs.cmu.edu/~ecc/gyro.tar.gz OpenGL gyroscope hack] <tt>keeps your display levelled when tilting the ThinkPad</tt>

====Games====
*Robert Love mentions a [http://icculus.org/neverball/ Neverball] patch on [http://rlove.org/log/2005100302.html his blog] to keep the display aligned. However, the link there seems broken.
*Turn your ThinkPad into a Jedi Weapon (hey, it [http://isnoop.net/blog/2006/05/20/macsaber-turn-your-mac-into-a-jedi-weapon works for Mac laptops])

====Other====

*[http://micampe.it/2006/06/04/here-comes-the-smackpad smack.py] - switch workspace by smacking your laptop, inspired by the [http://blog.medallia.com/2006/05/smacbook_pro.html SmackBook]

=== Interesting links related to this project ===
* [https://lists.sourceforge.net/lists/listinfo/hdaps-devel HDAPS mailinglist and its archive]
* #hdaps channel on irc.freenode.org
* [https://sourceforge.net/projects/hdaps/ hdaps projects] overview of userspace programs using hdaps
* [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=TPAD-HDFIRM IBM ThinkPads hardware drive firmware site]
* [http://www.paul.sladen.org/thinkpad-r31/accelerometer.html http://www.paul.sladen.org/thinkpad-r31/accelerometer/]
* http://bugs.gentoo.org/show_bug.cgi?id=119845 Gentoo ebuild for hdaps driver and daemon including a initscript

[[Category:R50]] [[Category:R50p]] [[Category:R51]] [[Category:R52]] [[Category:T41]] [[Category:T41p]] [[Category:T42]] [[Category:T42p]] [[Category:T43]] [[Category:T43p]] [[Category:T60]] [[Category:T60p]] [[Category:X40]] [[Category:X41]] [[Category:X41 Tablet]] [[Category:X60]] [[Category:X60s]] [[Category:Z60m]] [[Category:Z60t]] [[Category:Drivers]]

Talk:ThinkWiki

2006-01-07T17:01:24Z

Micampe: reverted spam

There are at least two different forms of date notation used on the main page.
One way should be picked. I would suggest ISO standard YYYY-MM-DD
http://www.cl.cam.ac.uk/~mgk25/iso-time.html
-David Mattli

The main page of ThinkWiki is not protected, so feel free to edit it. But do it with caution - it's the primary connection to the all content of our '''ThinkWiki''' ;-)

--[[User:Akw|akw]] 00:11, 25 Sep 2004 (CEST)
----
I added to wikipedia-like templates. To edit them go to Template:ThinkWiki_Preamble and Template:ThinkWiki_News.
Shall we put the other parts of the page in templates, too? If we do so, we could have that nice block design from wikipedia on our mainpage.

--[[User:Akw|akw]] 11:37, 25 Sep 2004 (CEST)

----
I think this is too much color. Makes it less readable, takes longer to orientate than the plain list style layout.

Liked it with only the two blocks in the beginning.

If we want to use blocks for everything, please stick to fewer colors. I think the yellow of the first block is not bad, and else i'd suggest light grey, maybe light blue.

However, if we stick to having all in blocks, how about [[User:Wyrfel/mainlayouttest | this color scheme]]?

[[User:Wyrfel|Wyrfel]] 16:35, 25 Sep 2004 (CEST)

----
Made [[User:Wyrfel/mainlayouttest-LTP | another Mainpage layout sketch]]. This tries to resemble the Tux and IBM logo colors and therefor looks quite "fresh".

[[User:Wyrfel|Wyrfel]] 18:59, 25 Sep 2004 (CEST)

: Too colorful for my taste, I think the other one is better --[[User:Nomeata|Nomeata]] 19:46, 28 Sep 2004 (CEST)
----
'''Important change:''' Moved Main_Page to ThinkWiki for cosmetical reasons..

--[[User:Akw|akw]] 16:54, 26 Sep 2004 (CEST)
----

== Needed: older ThinkPad specs... ==

As you can tell by my userid here, I've got a 600E. There are a whole lot of them out there thanks to the fact it was the current model during the Dot-Com era. We should cover the older ThinkPads and their quirks as well as the later models.

I also had a 365X, which is now living with a friend in the UK.

Yes, the next ThinkPad I'll probably score is a T4x, they are really kewl machines and inspire technolust in this geek. But until then, I love my 600E and I'm looking forward to some upgrades this weekend.

I will make copious notes on the upgrade process, which will include the installation of a 40GB hard drive and using the stock 10GB drive as extra Windows storage space. I have a hard drive bay module so the stock drive can be reused. The vast majority of the HD will be given over to an install of Debian Linux, with a 7GB Windows 2K partition because the University I will be attending a year from now demands it. (Yeah, I know, sucks, doesn't it.)

ThinkPad different,
Michelle

----
I totally agree.

All specs of all models can be found on the IBM support pages, we just need volunteers to transfer the infos into internal pages.

Since this is not the most interesting thing to do and hence it would be best if people using older ThinkPads transfer the specs for their models themselves. The same goes for other articles as installation infos, problems or whatever. I had a 570 once and loved it even though T30s where available at the same time...and i'd like to see more about these machines here, which everyone of them had some special characteristics and ideas behind them. So please show up, proud owners of Thinkpad 730TEs. 701s, 360Ps, Transnotes etc. ... ! ;)

Owners of the newer machines should take care of writing their articles (especially when creating new pages or sections) in a way that they are open for older models as well...i.e. make clear in the page or section title that its a specific topic for newer models.

Thanks,
[[User:Wyrfel|Wyrfel]] 00:45, 29 Sep 2004 (CEST)
----
I just inserted [[Special:Benchmarks|Benchmarks]] into the main menu.

--[[User:Akw|akw]] 14:07, 15 Oct 2004 (CEST)
----
I replaced the old logo with the great new one crafted by [[User:Wyrfel|Wyrfel]]

--[[User:Akw|akw]] 14:22, 1 Mar 2005 (CET)

:The new logo is too large to fit the sidebar. I can only see the yellow center with the ThinkWiki text and the left foot of Tux. I am using 1024x768 resolution and Opera. --[[User:137.226.40.2|137.226.40.2]] 14:37, 1 Mar 2005 (CET)
----

In Firefox the rest of the logo appears overlaid over the page frame. Interesting, that Opera doesn't do this.

However, we'll fix this soon.

[[User:Wyrfel|Wyrfel]] 19:57, 1 Mar 2005 (CET)

----
:Well, I am using Firefox and I only see half of Tux without any overlay. I guess I'll wait for the fix :-) --[[User:80.146.81.192|80.146.81.192]] 21:33, 1 Mar 2005 (CET)
----
Strange, it works with firefox and epiphany for me. I'll fix it.
----
Ok, now the smaller logo image is online. Looks nice for me :-)

--[[User:Akw|akw]] 22:15, 1 Mar 2005 (CET)
----
=== Main Page now protected ===
I had to protect the mainpage from editing because of vandalism.
Everyone who wants to add something to the mainpage is asked to post it here, the admins ([[User:Akw|akw]],
[[User:Wyrfel|Wyrfel]]) will insert it into the mainpage. You can also [[ThinkWiki:Contact|contact us]] to make your suggestions!

We're sorry for inconvenience. :-(

--[[User:Akw|akw]] 10:20, 2 Mar 2005 (CET)
----

----

Hei Arno,

i tried to do some stuff with templates, but it seems like templates in this version of MediaWiki are lacking some features and also seem a bit buggy (or i want too much). Is it troublesome to update to 1.4rc1? Shell we wait for the stable?
[[User:Wyrfel|Wyrfel]] 01:09, 14 Mar 2005 (CET)
----

=== Updates todo ===

== MediaWiki Update ==

I updated the thinkwiki software to version mediawiki 1.4.4. I hope this update will not be too painful.
There is still a problem with URL rewriting, so I had to deactivate the .htaccess file. Because of this, we got this ugly URLS with this '''index.php''' before the entry. The problem seems to be with the wiki config file '''LocalSettings.php''' and/or the '''.htaccess''' file.
I hope I get it fixed soon.

== Thinkpad and Apple Cinema 20' ==

I have a thinkpad R50. I have det required docking station with DVI.
If i try to boot my computer from the docking station nothing happends - it seems that it freezes up.
The only way i can get the monitor to work is:
1. boot the computer disconnected from the docking.
2. when the computer has booted i place it on the docking station. Then i works!!!

Do you know how to solve the problem.

Hope to hear from you.
----
Try changing the bootup display settings in the BIOS. Are you talking about Linux or Windows?
== Spelling: HOWTOs ==
Could anyone be so kind to correct "Howto's" to "Howtos"?
----
Done. [[User:Wyrfel|Wyrfel]] 12:00, 2 Aug 2005 (CEST)
----

== ThinkPad Buyers guide ==

It would be cool is there was a buyer guide to 2nd hand think pads.
- For people wishing to join in by gettine there own thingpad!!
----
This is a bit hard to accomplish. Remember that ThinkWiki is a site with international scope. What makes sense (in my opinion) is a page that has some notes and hints about what to care for, what are weak parts etc. . But it wouldn't make much sense to create a list of sites where to get them. Or maybe that's just what you meant. ;-) I'll look into creating some infrastructure for that on occasion.

[[User:Wyrfel|Wyrfel]] 03:02, 11 Aug 2005 (CEST)
----

== T43 and Embedded Visual C++ ==

Hi

Has anyone successfully gotten T34 and Embedded Visual C++ to work?
I could install the necessary softwares but when test is done using the 'Hello World!' program, the system just restarts itself.

regards,
Ponce

== This is a great general resource for ANY Thinkpad user ==

The promoted Linux-centricity is a minus, IMO. Regardless of the density of Linux content currently extant, the Linux focus seems exclusionary and probably drives away a lot of thinkpad users with useful content to add.

----
IBM probably has the best support website in the industry (albeit somewhat difficult to navigate), therefore ANY ThinkPad user may find general information there. The good thing about ThinkWiki is that it caters to a specific need, namely the (often difficult) task of installing the linux operating system on ThinkPad notebooks.
--[[User:MJK|MJK]] 14:54, 14 Sep 2005 (CEST)

----
I have to agree with MJK. ThinkWikis clear focus is Linux on ThinkPads. IBM provides pretty good support for Windows users, i.e. it wouldn't make sense to double driver listings and such here, since what IBM provides in this area is sufficient. What we can do, however, and what we are already doing here, is to provide additional information for Windows users as well. That's why we introduced Windows as one of our listed distributions and that's also why you find Windows related information scattered around the place. Linux users are searching Windows related ThinkPad sites for information that might be useful for their Linux installations. Let Windows users do the same the other way around. I'll add a little hint to the main page, but we won't change the primary focus. At least not now.

[[User:Wyrfel|Wyrfel]] 19:24, 15 Sep 2005 (CEST)
----

== TODO and FIXME templates? ==

Could a special way to add TODOs and FIXMEs to pages (maybe a template or whatever - I'm not to familiair with Wiki technologies) be considered? I'd like to add some TODOs and FIXMEs but would like to do that in a standardized way ...

[[User:Pebolle|Paul Bolle]] 22:42, 29 Sep 2005 (CEST)
----
Good point, i'll create templates. [[User:Wyrfel|Wyrfel]] 00:25, 30 Sep 2005 (CEST)
----
Ok, did some of it. There are Stub, Todo and Fixme templates now. Also, pages tagged with these templates will be categorized in [[:Category:NeedsEditing]]. Todo and Fixme should be used within sections and take one parameter, which should be a job description. Stub should only be used at the very beginning of a page.

[[User:Wyrfel|Wyrfel]] 01:52, 30 Sep 2005 (CEST)
----

== Nitpicking ==
Navigation bar: please s/$Think$p$ad$/\1P\2/g

Search bar: either drop Go or drop Search (they are equal, aren't they?)

How to read ThinkWiki seems to be better of as a normal entry in the first (upper left) table (and not as a "minor" item in the HOWTOs table).

I would suggest to make ThinkPad models (now a "minor" item in Hardware) the first entry in Hardware.

[[User:Pebolle|Paul Bolle]] 21:13, 8 Oct 2005 (CEST)
----
Hi, I am looking for some t series users for our beta program. Plese contact mtippett@ati.com.
----

==A Forum?==

I'm just curious if the idea of a public forum (using phpBB, SMF, whatever) has ever been considered. I think this would be excellent add-on to complement the Wiki. It'd make asking questions for guests and member's alike easier, and possibly afterwards the answers could be contributed into the article. Just an idea. --[[User:DuffDudeX1|DuffDudeX1]] 20:45, 31 Oct 2005 (CET)
----
There are ThinkPad Forums already, i.e. look at the [[Links]] page.

Moreover, there's the linux-thinkpad [[Mailinglists|mailinglist]] that serves this purpose. ThinkWiki's role is rather to complement that mailing list with a more static way of gathering information and to be found more easily.

[[User:Wyrfel|Wyrfel]] 23:54, 31 Oct 2005 (CET)
----

Oh, thanks for pointing that out, I didn't even notice the links page, I'll have to take a look.

--[[User:DuffDudeX1|DuffDudeX1]] 00:04, 1 Nov 2005 (CET)

== Nice skin, folks... ==

We'd like to steal it, for our geographically local wiki, if no one minds. What pieces would we need for that?<br>--baylink@wp, etc; jra@baylink.com

----
Just customize your main.css in your monobook folder.

--[[User:Akw|akw]] 10:00, 28 Dec 2005 (CET)
----

== Wiki ToDo List ==

Hi, I just setup a [[User:Akw/ToDo|ToDo List]] regarding the wiki for me on [[User:Akw/ToDo]].

This is for server admininstration tasks. Feel free to add some points if I forgot something more or less important.
I am going to work on the topic in the beginning of next year. I am offline now until 2006/01/06, so I wish a happy good year to all of you (except for the spammers and vandals, of course) ;-)

--[[User:Akw|akw]] 10:31, 29 Dec 2005 (CET)

Embedded Security Subsystem

2005-12-20T13:59:32Z

Micampe: reverted vandalism and fixed link

{| width="100%"
|style="vertical-align:top;padding-right:20px;width:10px;" | [[Image:ESS.jpg|IBM Embedded Security Subsystem]] __NOTOC__
|style="vertical-align:top" |
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;">
=== The Embedded Security Subsystem ===
The Embedded Security Subsystem is nothing but a chip installed on the Thinkpads mainboard that can take care of certain security related tasks conforming to the TCPA standard. It was first introduced among the T23 models and is now under the name Embedded Security Subsystem 2.0 an integral part of most of the modern Thinkpads. The functions of the chip are bound to three main groups:
* public key functions
* trusted boot functions
* initialization and management functions

The purpose of the whole thing is to keep the user's sensitive data out of range from software based attacks (like viruses, internet attacks etc.). One way the chip offers to achieve this is by providing storage for keys along with the neccessary functions to handle them within itself, so that a i.e. a private key never has to leave the chip (can't be seen by any piece of software). Besides this there are more complex topics covered by the functionality of the chip. If you want to find out more about it you can find good documents on the [http://www.research.ibm.com/gsal/tcpa/ IBM Research TCPA resources page].</div>
|}

==Trusted or Treacherous?==

TC - Trusted Computing - will be the biggest change of the information landscape since decades. Besides positive features like a more secure hardware storage for cryptographic keys, an analysis of the proposed TCG-standards shows some problematic properties. <br />
As ThinkPads of recent generations following the ThinkPad {{T23}} ([[Embedded Security Subsystem#Models featuring this Technology|see the complete list of models]]) are equipped with this disputed TCG-/TCPA-Technology, it can be interesting, which promises of the TCG are fulfilled inside your ThinkPad and which parts of the TCG-specifications still seem to be a privacy issue for every user of digital devices like a MP3-player or a ThinkPad - so please read [[TCPA/TCG - Trusted or Treacherous|this article]] for more details.

==Linux Support==
Two linux drivers are available, a [[tpm|classical one]] and a [[tpmdd|newer one]].
Coverage of functionality of the first is unknown so far, the second is part of a bigger project aiming to provide a usable security framework.

David Stafford (one of the developers of the tpm code at IBM) on March 10, 2005 sent me the most recent version of the tpm-kml code. With his permission, I quote his email:

"I am attaching our latest driver and library.
This version is in the process of kernel mailing list review, and
will hopefully be accepted into the official kernel. It works
much better across various 2.6 kernels. Note that this builds
three modules tpm, tpm_atmel, and tpm_nsc. You modprobe the
tpm_atmel (for all current shipping atmel based systems), or
tpm_nsc (for the coming national based systems).

Also note that there is a conflict with the snd-intel8x0
kernel module (they each try to grab the LPC bus). You can
either: load the tpm modules first (such as in initrd or
rc.sysinit, before sound), or recompile the snd-intel8x0, turning
off the MIDI and JOYSTICK support. The latest 2.6.11 version
of snd-intel8x0 also reportedly fixes things."

Compiling this library was easy. Compiling the driver on my 2.6.8-686 (debian testing) laptop failed. But the library works with the driver I compiled from the tpm-2.0 package IBM made available on its pages (see the links below).

Gijs

The T43 requires a patch posted to the LKML by Kylene Jo Hall: [http://marc.theaimsgroup.com/?l=linux-kernel&m=111884603309146&w=2 LKML posting]. An updated patch for linux 2.6.12 is available [http://shamrock.dyndns.org/~ln/linux/tpm_2.6.12.diff here].

The atmel driver comes with 2.6.12.

==Versions & Features==
=== Embedded Security Chip ===
IBM introduced it's TCPA/TCG features with some of the [[:Category:T23|T23]] models. The earlier of them didn't yet have the Embedded Security Subsystem, but a kind of pre 1.0 version called the Embedded Security Chip. This chip had the following capabilities:
*Data communications authentication and encryption
*Storage of encrypted passwords

=== Embedded Security Subsystem (1.0) ===
The original Embedded Security Subsystem (in IBM documents there is no use of the additive version-number 1.0) claims to be compliant with TCG specs, but apparently did not fully implement any specific TCG spec.

The Embedded Security Subsystem has the following features:
*hardware key storage
*multi-factor authentication
*local file encryption
*enhances VPN security

=== Embedded Security Subsystem 2.0 ===
The Embedded Security Subsystem 2.0 conforms to the TCG TPM 1.1b specification, with a TPM manufactured by either Atmel or National Semiconductor.

The Embedded Security Subsystem 2.0 has the following features:
*hardware key storage
*multi-factor authentication
*local file encryption
*enhances VPN security
*TCG compliant

==Models featuring this Technology==
===IBM Embedded Security Chip===
*ThinkPad {{T23}}
===IBM Embedded Security Subsystem===
*ThinkPad {{A30p}}
*ThinkPad {{R31}}
*ThinkPad {{T23}}, {{T30}}, {{T41}}
*ThinkPad {{X22}}, {{X23}}, {{X24}}

===IBM Embedded Security Subsystem 2.0===
*ThinkPad {{R32}}, {{R40}}, {{R50}}, {{R50p}}, {{R51}}, {{R52}}
*ThinkPad {{T40}}, {{T40p}}, {{T41}}, {{T41p}}, {{T42}}, {{T42p}}, {{T43}}, {{T43p}}
*ThinkPad {{X30}}, {{X31}}, {{X32}}, {{X40}}, {{X41}}, {{X41T}}
*ThinkPad {{Z60m}}, {{Z60t}}
[[Category:Glossary]]

==TCPA/TCG clean models==
*all models produced before 2000
*all i Series models
*ThinkPad [[:Category:240X|240X]]
*ThinkPad [[:Category:A20m|A20m]], [[:Category:A20p|A20p]], [[:Category:A21e|A21e]], [[:Category:A21m|A21m]], [[:Category:A21p|A21p]], [[:Category:A22e|A22e]], [[:Category:A22m|A22m]], [[:Category:A22p|A22p]], [[:Category:A30|A30]]
*ThinkPad [[:Category:T20|T20]], [[:Category:T21|T21]]
*ThinkPad [[:Category:X20|X20]], [[:Category:X21|X21]], [[:Category:X22|X22]]
*ThinkPad [[:Category:TransNote|TransNote]]

==External Sources==
*[http://www.pc.ibm.com/us/think/thinkvantagetech/security.html IBMs ThinkVantage<sup>TM</sup> Technologies Embedded Security Subsystem page]
*[http://www.pc.ibm.com/presentations/us/thinkvantage/56/index.html?shortcut=ess& IBMs ThinkVantage<sup>TM</sup> Technologies Flash presentation - Embedded Security Subsystem]
*[http://www.research.ibm.com/gsal/tcpa/ IBM Research TCPA resources page]
*[http://www.prosec.rub.de/trusted_grub.html Trusted Grub]

How to save memory

2005-12-15T17:26:29Z

Micampe: /* Window Manager */ fixed typo and added wmx

{| width="100%"
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__
|style="vertical-align:top" |This page is meant as a collection of information on how to save memory to make Linux work reasonable on older system with limited amount of RAM.

Most distributions nowadays don't take much care about it anymore, so there are a lot of things you can do to save memory. To get a smoothly working linux environment on a low memory machine you will need to conciously choose a lot of aspects of your system, most importantly the graphical environment, desktop environment and applications. This page provides detailed information about these various optimization possibilities.
|}

==Alternative graphical environments==
{{Todo|...}}

==Streamlining the desktop environment==
The common Desktop environments GNOME and KDE are, in their modern state, focused more on features, integration, and beauty rather than on resource saving. Understandable, but running Linux on an older ThinkPad with limited RAM requires conscious and sensitive resource usage more than anything else. The good thing about Linux is that a lot of things stay adjustable and customizable. So lets see what we can do about desktops.

One of the most important things is to decide for one graphical widget library and stick with that when you are choosing your desktop environment and applications. Having several toolkits in use means more libraries being loaded and hence more memory being used by those. Possibilities are:
* [http://www.fltk.org/ FLTK]
* [http://www.fox-toolkit.org/ FOX toolkit]
* [http://www.gnustep.org GNUstep toolkit]
* [http://www.gtk.org/ GTK] <tt>(not recommended, use GTK 2 if possible)</tt>
* [http://www.gtk.org/ GTK 2]
* [http://www.lesstif.org/ Lesstif] / [http://www.openmotif.org/ OpenMotif]
* [http://www.trolltech.com/products/qt/index.html QT]
* [http://www.windowmaker.org/development-wings.html WINGs] <tt>(kind of a lightweight GNUstep toolkit, provided by the WindowMaker developers)</tt>
* [http://www.x.org/ X Toolkit]

Of those, at current state, there are enough applications for the X Toolkit, GTK, GTK 2 and QT to provide you with a solution for every task you should want.

===GNOME===
It's like with humans, the worst feature is in most cases also the best one. For GNOME it is probably the many little parts it consists of. Makes it hard to install, but enables one to customize the installation. So, the first thing you should do to streamline GNOME is not to launch it. Sound stupid? Well, lets have a look.

GNOME is basically a set of libraries built around the GTK+ libs and extending its functionality. Add some nice little applications, a session manager, a panel, beautiful icons, and some other stuff and you have GNOME as you know it. Reversing those additions is what you can do to use GNOME applications on a machine that this desktop environment would normally take your nerves on.

The GNOME panel, the session manager, the desktop manager and the window manager are all parts of GNOME that eat a lot of memory for something that others can do in a maybe little less beautiful but much more resource saving way.
So first off configure your login manager not to launch gnome-session at login. If you are using GDM this is quite straight forward, you just need to add a different session script, launching your favorite window manager. See the list below and pick one, lets say i.e. WindowMaker. WindowMaker uses a desktop menu, a dock and a notification area to provide you with an organized way of launching applications and iconfying running ones. So we don't need a panel anymore. Also, think if you really need icons on your desktop. If you do, think about using something like ROX filer instead of nautilus for that. In any case, tell nautilus not to manage the desktop by default by unchecking the according setting within gconf-editor. To keep GNOME applications happy we would need to have gconf and gnome-settings-manager running at every session start. One way to do this is to either include them in your new session script. They both need to be running to make GNOME applications realize their settings properly.

===KDE===
{{Todo|...}}

===Alternative Desktop Environments===
First of all, it is important to notice that GNOME and KDE are not the only Desktop Environments around.
Other complete (featuring most of: window management, session management, desktop management, file management and panel) desktop environments are:
*[http://xfce.org/ XFCE] <tt>uses GTK 2</tt>
*[http://ede.sourceforge.net Equinox Desktop Environment] <tt>uses eFLTK, a modified version of FLTK</tt>
*[http://www.nongnu.org/antiright/ AntiRight Desktop Environment] <tt>uses LessTif / OpenMotif</tt>
*[http://foxdesktop.sourceforge.net/ FOX Desktop Environment] <tt>uses FOX Toolkit</tt>
*[http://www.gnustep.org/ GNUstep] <tt>provides it's own toolkit</tt>

But also, some Window Managers exceed the task of managing windows towards providing a functional workbench. See below for a list.

===Building your own Desktop===

====Window Manager====
If you want to build your own customized desktop, a good start is choosing the window manager of your liking.

Here's a list of some of them:
*including basic Desktop Environment functionality
**the [[Wikipedia:NextStep|NextStep]] alike ones
***[http://www.windowmaker.org/ WindowMaker] <tt>(probably the most widespread NextStep like WM)</tt>
***[http://www.afterstep.org/ AfterStep] <tt>(another one of those)</tt>
***[http://blackboxwm.sourceforge.net/ BlackBox]
***[http://fluxbox.sourceforge.net/ FluxBox] <tt>(tabbed windows, lighweight)</tt>
***[http://www.pekwm.org PekWM] <tt>(kind of a one man show, but feature rich and extremely customizable)</tt>
**others
***[http://www.icewm.org/ IceWM] <tt>(lightweight, widespread)</tt>
*pure WindowManagers
**[http://golem.sourceforge.net/ Golem]
**[http://home.earthlink.net/~lab1701/larswm/ LarsWM] <tt>(unique tiling Window Manager)</tt>
**[http://www.nongnu.org/ratpoison/ ratpoison] <tt>(modeled after gnu screen)</tt>
**[http://fvwm.org/ fvwm] <tt>(small but powerful)</tt>
**[http://www.all-day-breakfast.com/wm2/ wm2] <tt>really small Window Manager</tt>
**[http://www.all-day-breakfast.com/wmx/ wmx] <tt>slightly more featureful version of wm2</tt>

====Taskbar/Panel====
Another thing that especially users coming to Linux from the Windows world would probably like is a Panel or Taskbar.

Here's a collection of independant low resource panels:
*[http://www.chatjunkies.org/fspanel/ F***ing Small Panel] <tt>(doesn't use any toolkit)</tt>
*[http://freshmeat.net/projects/hpanel/ HPanel] <tt>(doesn't use any toolkit)</tt>
*[http://fbpanel.sourceforge.net/ fbpanel] <tt>(depends on GTK 2)</tt>
*[http://jodrell.net/projects/perlpanel Perl Panel] <tt>(depends on GTK 2, gnomevfs, perl)</tt>
*[http://www.gkrellm.net/ GKrellM] <tt>(depends on GTK 2, flexible plugin based skinable vertical panel)</tt>

====Desktop Pinboard====
Then, the next thing you might be looking for is how to get icons onto your desktop. Usually this is done by the file manager who displays the content of a special directory as icons on the desktop. See the File Manager section to follow this approach.

However, you might decide for a really lightwight file manager which doesn't offer this feature. In that case all hope is not lost, for there are also special programs specialized in desktop icon management. Such are:
* [http://idesk.sourceforge.net/ iDesk] <tt>(recent versions need imlib2 only)</tt>

====File Manager====
File Managers are the fourth really important compontent of a desktop environment. There are plenty out their ranging from resource hugs to really lightweight and slim ones.

File Managers come with three distinct general user interface approaches: the two pane gui, the spacial and the browser gui. The browser gui is the one the Windows Explorer starting from Windows 2000 uses as well as earlier versions of Nautilus. The spacial view is the one known from Windows 95 and more recent versions of Nautilus. The two pane view is know to many from Norten Commander, Directory Opus or your favorite FTP client.

The following list provides an overview.
*FLTK
** [http://www.oksid.ch/flfm/ Fast Light File Manager] <tt>(spacial gui)</tt>
* FOX toolkit
** [http://roland65.free.fr/xfe/ X File Explorer] <tt>(browser and two pane gui)</tt>
*GTK
** [http://www.kaisersite.de/dfm/ Desktop File Manager] <tt>(spacial gui, incl. desktop icon management)</tt>
** [http://www.uwyn.com/projects/fm/ FM] <tt>(spacial, MAC OS 9 like gui)</tt>
** [http://radekc.regnet.cz/ Seksi Commander] <tt>(two pane gui)</tt>
*GTK 2
** [http://rox.sourceforge.net/ ROX Filer] <tt>(highly productive spacial gui, incl. panel and desktop icon management)</tt>
** [http://blog.perldude.de/projects/filer/ Filer] <tt>(browser and two pane gui, requires Perl)</tt>
** [http://xffm.sourceforge.net/ XFFM] <tt>(browser and spacial gui, requires some XFCE libs)</tt>
** [http://logicaldesktop.sourceforge.net/ Logical Desktop] <tt>(browser gui, actually a very special approach)</tt>
** [http://tuxcmd.sourceforge.net/ Tux Commander] <tt>(two pane gui)</tt>
** [http://emelfm2.net/emelFM2/ emelFM2] <tt>(two pane gui with full customizable menu and toolbar, the best for power users)</tt>
** [http://thunar.xfce.org/index.xhtml Thunar] <tt>(requires some XFCE libs)</tt>
* OpenMotif
** [http://www.musikwissenschaft.uni-mainz.de/~ag/xplore/xplore.php Xplore] <tt>(browser gui with productive 4 pane concept)</tt>
* QT 2
** [http://www.hi-net.cz/blaza/bfcommander/en/index.html BF-Commander] <tt>(two pane gui)</tt>
* Tcl/Tk
** [http://users.tkk.fi/~mkivinie/X-Files/ X-Files] <tt>(two pane gui)</tt>
*X Toolkit
** [http://www.musikwissenschaft.uni-mainz.de/~ag/xfm/ X File Manager] <tt>(spacial gui)</tt>
** [http://www.boomerangsworld.de/worker/ Worker] <tt>(two pane gui, highly productive and configurable)</tt>
** [http://xnc.dubna.su/ X Northern Captain] <tt>(interesting flexible two pane gui)</tt>
*3D Filemanagers
** [http://www.determinate.net/webdata/seg/tdfsb.html TDFSB] <tt>(3D gui, the most impressing 3D file browser so far)</tt>
** [http://www.forchheimer.se/bfm/ Brutal File Manager] <tt>(3D gui more for fun than productivity)</tt>
** [http://turma.sourceforge.net/software/3dfile/ 3DFile] <tt>(3D gui)</tt>
** [http://orbis.sourceforge.net/ Orbis] <tt>(3D gui)</tt>

==Choosing applications==
===Web Browser===
This is highly dependend on the way you use your browser, it's often worth it to try out all and just track general
memory usage. Remember that <tt>top</tt> and <tt>ps</tt> don't report correct memory usage, track totals only.

====Firefox====
Firefox is graphical web browser. One can install features like AdBlock and FlashClicktoplay which will decrease memory and
processor usage by hiding Flash and Java -adverts.

====Opera====
Opera is graphical web browser. You can easily enable/disable plug-ins and java (press F12) and decrease memory usage.
Opera uses QT as toolkit, so you may shave off some Mbytes off memory usage by using dynamically linked version if you use KDE.

====Konqueror====
Konqueror is graphical web browser. It's integrated with KDE and has several advanced features (esp. ca. KDE 3.5).
You may save some megabytes by using it instead of other browsers when using KDE.
It's not necessarily heavy even when used without running KDE.

====Dillo====
Dillo is minimalistic and very small graphical web browser.

====Elinks/Lynx====
elinks/lynx are both text mode web browsers. <tt>elinks</tt> handles tables and formatting much nicer than <tt>lynx</tt>.
Both go very easy on memory footprint.

{{Todo|...}}

==Disabling unneeded system deamons==
Another thing you can do to improve performance is to get rid of unneaded system daemons launched from your init scripts. Disable them by using the according configuration interface of your distro or by deleting links in the according runlevel directories (usually in <code>/etc/rc.d/</code>).

Daemons you usually don't need:
* httpd <tt>(Apache web server)</tt>
* mysqld <tt>(MySQL database server)</tt>
* smbd <tt>(SMB windows filesharing server)</tt>
* pppd <tt>(PPP server for connections through modems and serial lines)</tt>

==Adjusting filesystems==
You can also try to optimize memory usage by making sure that you have as little as possible of your filesystem residing in RAM. To do this make sure that the following mount points are set to reside on your harddisk in {{path|/etc/fstab}}.
* /dev (not possible if you use udev)
* /tmp

==Other tips==
===Disk space===
When using Debian/Ubuntu/other derivative, use <tt>aptitude</tt> as package manager, and use it as soon as possible. Use it and only it to install and remove packages.

One of it's most usefull features is that it tracks packages you install and marks packages installed via dependency as such, so when you remove a package that is no longer used, or package updates and doesn't use a library anymore, that dependency will get uninstalled.

You can mark packages installed as automatically installed by hitting 'M' (uppercase m), it will be marked for deinstallation if it's not longer required.

Talk:Fglrx

2005-12-14T20:39:52Z

Micampe:

So, I'm searching up and down and there seems to be no way to enable the TV output without an ad-hoc xorg.conf. So my question is, what is ''fireglcontrolpanel'' useful for?

--[[User:Micampe|Micampe]] 21:39, 14 Dec 2005 (CET)

Category:Models

2005-12-14T12:12:17Z

Micampe: reverted

{| width="100%"
|style="vertical-align:top" |
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;">
=== ThinkPad Models ===
This page offers information about the various models published throughout the [[ThinkPad History|history of ThinkPad computers]].<br />
You can also read about the [[ThinkPad|origin of the ThinkPad branch]].<br />
If you need more specific information about a precise model, try to find it within the [[Hardware Specifications]].
</div>
|}

The following is a list of various [[Thinkpad series|series of Thinkpad computers]]:

Talk:SMAPI support for Linux

2005-12-13T08:33:24Z

Micampe:

Great, great work! Really! This completely rocks. I just stopped my battery from charging at 77% and restarted charging a bit later, no problems whatsoever. BTW, this is on kernel 2.6.14.3.

--[[User:Spiney|spiney]] 21:25, 5 Dec 2005 (CET)
----
None of the fuctions is working on my T40, kernel 2.6.14-mm2.

--[[User:Lammic|lammic]], 2005.12.05

Works for me on a T41 running 2.6.12-10-686 (Ubuntu 5.10).

--[[User:berndtnm|berndtnm]], 2005.12.06

Including stop_charge_thresh? That one seems to be missing on the T42p.

--[[User:Thinker|Thinker]] 00:46, 7 Dec 2005 (CET)
----

tp_smapi works just fine on an R52 with Ubuntu Breezy stock kernel.

--[[User:Micampe|Micampe]] 12:52, 7 Dec 2005 (CET)

----

''To set the thresholds for starting and stopping battery charging (in percent of current capacity):''

'''current''' really? That'd be weird, I'd expect it to be percent of '''total''' capacity.

--[[User:Micampe|Micampe]] 14:39, 7 Dec 2005 (CET)

"Current full charge capacity", as opposed to "current remaining capacity" or "designed full charge capacity"...

--[[User:Thinker|Thinker]] 15:05, 7 Dec 2005 (CET)
----

Battery features don't work with my T41p. I can't check this with windows. Can anybody try these features?

-- Nils, 7 Dec 2005
----

Nils, does cdrom_speed work for you on the T41p? Could you provide the details requested in the README (dmesg etc.)?

--[[User:Thinker|Thinker]] 21:57, 7 Dec 2005 (CET)
----

CDRom Speed seems to work. (I see no warnings, but I have to do a speed test.) Now, I've send all outputs to the email-address in the readme.

-- Nils, 8 Dec 2005
----

==Changing the CD speed when the CD is being accessed will hang your computer==

I don't have this problem on my T40p. CDROM is mounted and file on CD is opened. Change speed do '''not''' hang my system.

-- Stefan Schmidt
----

An open file looks fine if you're not reading/writing at that point. But my T43 does hangs on this:
# dd if=/dev/scd0 of=/dev/null &
# echo 1 > /sys/devices/platform/smapi/cdrom_speed

--[[User:Thinker|Thinker]] 16:41, 7 Dec 2005 (CET)
----

OK, sorry. I was to fast. My system hangs on this commands, too. :(

-- Stefan Schmidt

Works well. Great.

T42 2373-8zh. Working :cdrom_speed and start_charge_thresh. Untest : inhibit_charge_minutes.

-- Haifeng Chen

cdrom_speed works on my T40.

-- [[User:Lammic|lammic]], 2005.12.09

== "thinkpad" module kernel compatibility ==

Ajunge, how do you compile the "thinkpad" module compile on kernel >=2.6.9? The latest thinkpad version (5.8) still uses "get_cpu_ptr" and "set_cpu_ptr", which were removed in 2.6.9.

--[[User:Thinker|Thinker]] 13:53, 10 Dec 2005 (CET)
----

== Feature support matrix ==
I think it would be a good idea to reflect the supported fetures on each machine in a matrix. The listing is really complex.

--[[User:StefanSchmidt|StefanSchmidt]]

Something like that:

{| border="1" cellpadding="2"
|+Feature support matrix
|-
! × !! start_charge_thresh !! stop_charge_thresh !! inhbit_charge_minutes !! cdrom_speed !! battery status
|-
! G41
| bgcolor=green|working || bgcolor=red|not working || bgcolor=green|working || bgcolor=green|working || unknown
|-
! R40
| bgcolor=red|not working || bgcolor=red|not working || bgcolor=red|not working || bgcolor=green|working || unknown
|-
! R50p
| bgcolor=red|not working || bgcolor=red|not working || bgcolor=red|not working || bgcolor=green|working || unknown
|-
! R51
| bgcolor=green|working || bgcolor=red|not working || bgcolor=green|working || unknown || unknown
|-
! R52
| bgcolor=green|working || bgcolor=green|working || bgcolor=green|working || bgcolor=green|working || unknown
|-
! T40
| bgcolor=red|not working || bgcolor=red|not working || bgcolor=red|not working || bgcolor=green|working || unknown
|-
! T40p
| bgcolor=red|not working || bgcolor=red|not working || bgcolor=red|not working || bgcolor=green|working || unknown
|-
! T41
| bgcolor=green|working || bgcolor=red|not working || bgcolor=green|working || unknown || unknown
|-
! T41p
| bgcolor=red|not working || bgcolor=red|not working || bgcolor=red|not working || bgcolor=green|working || unknown
|-
! T42
| bgcolor=green|working || unknown || unknown || bgcolor=green|working || unknown
|-
! T42p
| bgcolor=green|working || bgcolor=red|not working || bgcolor=green|working || unknown || unknown
|-
! T43
| bgcolor=green|working || bgcolor=green|working || bgcolor=green|working || bgcolor=green|working || bgcolor=green|working
|-
! T43p
| bgcolor=green|working || bgcolor=green|working || bgcolor=green|working || bgcolor=green|working || unknown
|-
! X31
| bgcolor=red|not working || bgcolor=red|not working || bgcolor=red|not working || unknown || unknown
|-
! X32
| bgcolor=red|not working || bgcolor=red|not working || bgcolor=red|not working || unknown || unknown
|-
! X40
| bgcolor=green|working || bgcolor=red|not working || bgcolor=green|working || unknown || unknown
|-
! X41
| bgcolor=green|working || bgcolor=green|working || bgcolor=green|working || unknown || unknown
|}

----

Good idea. Care to help converting the current data? While at it, we need a new "battery status" column for the new features in tp_smapi 0.09.

--[[User:Thinker|Thinker]] 01:47, 13 Dec 2005 (CET)
----

Should we have a "Kernel version" column too?

--[[User:Micampe|Micampe]] 09:33, 13 Dec 2005 (CET)

Talk:SMAPI support for Linux

2005-12-13T08:32:29Z

Micampe: updated table with real data. please check.

Ordering Recovery CDs

2005-12-10T00:06:47Z

Micampe: vandalism

Information on getting Recovery CDs from IBM.

The information on this page is unofficial. It is gathered from personal experiences. It is here to raise your chances of success when you give it a try yourself.

==About Recovery CDs==
Recovery CDs enable you to reproduce the original software state on your ThinkPad. Until the beginning of 2001 IBM delivered recovery CDs with the ThinkPads, but starting with the A30/T23/X22 models ThinkPads have a [[Predesktop Area]], which's purpose is to make Recovery CDs obsolete. However, this is flawed logic, since you will lose both the installed OS AND the [[Predesktop Area]] upon failure of the hard drive. Also, if you buy a drive upgrade the [[Predesktop Area]] will not be on the new drive. Furthermore, spyware and viruses are lately being designed to infiltrate recovery partitions, so if you restore the system from such, you will restore the invading malware along with it. For the time being, Recovery CDs are available on request.

Recovery CDs are localized, meaning that there are specific versions for each language. The language you will get depends on the language of the OS that was shipped with your ThinkPad. There's usually no way to get CDs in a different language from IBM.

==How to get them==

===Creating Recovery CDs from the preinstalled O/S===
In some Thinkpads IBM supplies a utility to create the recovery CDs. You'll find a utility called "Create Recovery Discs" in the "ACCESS IBM" folder of the Start Menu. To create the Recovery discs, you'll need a CD/DVD writer and blank media. The Product Recovery discs set consist of one Rescue and Recovery disc and one or more Product recovery discs. (2 DVDRs should suffice for the entire set)

===From IBM===
Should you fail to create a set of recovery discs before your harddrive fails, you may try to contact IBM service and request for a set.
This can be done by eMail or phone.
[http://www.ibm.com/support/ Support phone numbers] are available online.
They are officially called ''Recovery CD service parts.''
If you actually get them, or not, seems to be more a personal decision of the service person dealing with you than following fixed rules. Also it seems to depend on your country (see below).

They will usually expect you to tell them a good reason for your request (see below).
As with every service request, you'll also have to provide your model and serial number to verify the warranty state.
The warranty for your Thinkpad is usually quite long though (3 years in my case), and you can
[http://www-307.ibm.com/pc/support/site.wss/ check online] if your warranty is still in force.
The model number is also used to determine which CDs you will get.

Orders placed during the first month after purchase have proven to be the most successful. Note some people needed to pay a $45.00 fee, plus shipping and tax, for the CDs, regardless of when ordering them. Again, this seems to depend on the mood of the service rep that handles your case.

Note that Recovery CDs are only available for Windows XP Professional for the X24, as per the Customer Service Center in Atlanta, GA. All other operating systems (Windows 2000, 98SE, OS/2, etc...) are no longer available. XP Home was apparently never available for the X24.

====Good reasons to tell====
*You replaced (or will be replacing) your hard drive.
*You installed Linux or some other OS and accidentally removed/destroyed the [[Predesktop Area]].

====What happens then====
Once it's decided that you get the CDs, they usually get shipped very fast. Times from 16h to 3 days have been reported, 3 days being the time to expect. The shipping can even happen without prior confirmation of your request, so don't be worried if you hear nothing within this time.

A Dutch IBM customer reported next-day delivery of recovery CDs, on three different occasions. A customer in Belgium had to wait 8 days, so sometimes delivery is not that fast.

====Country overview====
Please put an entry for your country into this table if it's missing and you made a try to get the Recovery CDs.
{| border="1" cellspacing="0" cellpadding="2"
|-
! style="vertical-align:top;background-color:#cfefcf;" | CDs received in
! style="vertical-align:top;background-color:#ffcfbc;" | CDs were denied in
|-
| style="vertical-align:top;background-color:#e9f9e9;" |
*Argentina
*Austria
*Australia (depends on the service rep & reason)
*Belgium
*Canada
*Denmark
*Finland
*France
*Germany (cost: 39,90 Euro (+VAT) if device is out of warranty), otherwise is free
*Italy
*The Netherlands
*Norway
*Philippines
*Spain
*Sweden
*Switzerland
*UK
*USA
*Turkey
| style="vertical-align:top;background-color:#fff0e0;" |
*Israel but received after calling IBM Europe
*Australia, payment was requested
*India, just a plain "not possible"
*Russia, service reps claim that these CDs are not for end-users
|}

[[Category:Windows]] [[Category:A30]] [[Category:A30p]] [[Category:A31]] [[Category:A31p]] [[Category:G40]] [[Category:G41]] [[Category:R30]] [[Category:R31]] [[Category:R32]][[Category:R40]] [[Category:R40e]] [[Category:R50]] [[Category:R50e]] [[Category:R50p]] [[Category:R51]] [[Category:R52]] [[Category:T23]] [[Category:T30]] [[Category:T40]] [[Category:T40p]] [[Category:T41]] [[Category:T41p]] [[Category:T42]] [[Category:T42p]] [[Category:T43]] [[Category:T43p]] [[Category:X22]] [[Category:X23]] [[Category:X24]] [[Category:X30]] [[Category:X31]] [[Category:X32]] [[Category:X40]] [[Category:X41]]

Talk:Predesktop Area

2005-12-09T16:39:01Z

Micampe: How to get the AccessIBM to work

==Use the HPA for GNU/Linux?==
More interesting than removing the HPA (which includes a.o. Acces IBM Predesktop Area, some other tools and a backup of the pre-installed OS) would be to use this area for GNU/Linux too. At least, removing the HPA only saves 3,5 GB on my 60 GB hard disk. It would be worth a try to see whether the backup of the pre-installed OS on the largest PSA could be replaced by a backup of your favourite GNU/Linux distribution.

Elaborating on my ideas a few days later, I'd guess the following could be tried:
* see whether GRUB can be made to boot the Access IBM Predekstop Area (I guess by "chainloading" the bootsector of its PSA). Right now GRUB refuses to load sectors outside the partioned area. I've got absolutely no idea if it's possible to write a hack to overcome that restriction. Need to contact the GRUB people about that ...
* write a HPA or SPA driver. That driver should provide something like "/dev/hpa", "/dev/hpa0", etc or "/dev/spa", "/dev/spa0", whatever. The idea here is that it allows you to simply mount (ro!) the Hidden Protected Area (given the correct BIOS settings). Probably just an addaption of the current drivers for (IDE?) harddisks. (This might mean "/dev/hda" and "/dev/hpa" overlap: dangerous?) That would probably need - way - more coding skills than I have ...
* write some userspace tools for the HPA/the SPAs (things like: dumpbeer, printDoS).

It should be clear these are basically random ideas. Still feedback would be appreciated ...
----
Hei,

interesting ideas, but i'd only see a point in it if one could keep Win and Linux rescue stuff in the HPA. That means it would need to be expandable or fit the stuff for both systems.
[[User:Wyrfel|Wyrfel]] 20:03, 15 Mar 2005 (CET)
----
Thanks.

Short answer: that should be possible.

Long answer: I see little in the specs (as I understand them now) to stop one from adding (say) an extra 3 GB GNU/Linux-rescue PSA or something like that. We might try to do that first by changing the BEER and DoS manually. (Not sure whether Phoenix added some proprietary stuff to keep you from booting it. The PSA should always be accesable with the proper BIOS setting.) It might be mandatory to put it on a FAT filesystem. The hard part probably is to have it show up in the Access IBM Predesktop Area. (My guess is you need to regenerate the FirstSight "graphical shell". If that's correct we probably only can use the FirstWare tools "hidden" on their little PSA. That's no fun. Well it might a little fun if we try FreeDOS).

[[User:Pebolle|Paul Bolle (not logged in)]]
----
Update: a trivial patch to grub allows it to also work outside the partioned area:

--- /var/tmp/rpm/BUILD/grub-0.95/stage2/disk_io.c.oud 2004-05-23 18:35:24.000000000 +0200
+++ /var/tmp/rpm/BUILD/grub-0.95/stage2/disk_io.c 2005-03-18 22:38:30.050907408 +0100
@@ -297,8 +297,8 @@
* Check partition boundaries
*/
if (sector < 0
- || ((sector + ((byte_offset + byte_len - 1) >> SECTOR_BITS))
- >= part_length))
+ /*|| ((sector + ((byte_offset + byte_len - 1) >> SECTOR_BITS))
+ >= part_length)*/)
{
errnum = ERR_OUTSIDE_PART;
return 0;

I made a grub CD with a grub patched with the above. Now I can "cat" the bootsector of the Predesktop Area from the grub shell (when booting of that grub CD). But I haven't yet managed to boot the Predesktop Area (dangerous stuff!) To be continued ...

[[User:Pebolle|Paul Bolle]] Fri Mar 18 22:42:43 CET 2005

----

I've been playing around with the predesktop area tonight. I was simply trying to just leave the diagnostics stuff and remove the windows part. I wrote some programs to read/write the BEER data and stuff, but I wasn't able to get the system to boot it, it kept erroring "Authentication of System Services failed" (or something along those lines). I will play around with this some more later

[[User:Invisi|Tim Nordell]]
----

A quick look with a hexeditor gave me two instances of "Application authentication has failed!" in the FirstSight application. Does that sound familair?

[[User:Pebolle|Paul Bolle]] Fri Apr 1 19:35:30 CEST 2005

----

Actually it wasn't that. I did a search of that too, the message itself was not in the predesktop area at all. What also is interesting is the fw*.exe utilities for manipulating the predesktop area, contains the string "MD5" which makes me wonder if there is an md5 hash of each "predesktop" partition. I know on the IBM whitepaper it states there being a signature so that non-signed applications can not be run. Could a simple "md5" be the signature?

[[User:Invisi|Tim Nordell]] 12:01, 3 Apr 2005 (CEST)

----

*What is it that you were trying to do (what did trigger the error you saw)?

*About ten of the fw*.exe utilities contain the phrase "MD5 Checksums do not match". So they could very well be using MD5 sums for some sort of validation. But they could use the MD5 sums in a lot of ways actually, so I won't yet speculate ...

[[User:Pebolle|Paul Bolle]] Sun Apr 3 15:11:10 CEST 2005

== Predesktop Area ==

I made a program that takes the BEER record at the end, parses it out to a ".cfg" file, lets you modify it, recalibrate the start spots for the records, and write it out to disk again. It doesn't directly access hda, 'cept for reading the original beer record. It makes a script file to go with the files you have, to read in the HPA data, and to write it out again with the new record.

Anyways, I tried simply removing the last record from the BEER, which is the windows recovery partition. It didn't like that.

----

Did you update the two's complement checksum at the end of the BEER?

[[user:Pebolle|Paul Bolle]]

----

Yep, I updated that. If I don't update that, it doesn't even say that failed message. I also made a seperate program to update the checksum so you can also modify the beer record by hand with a hex editor and have valid checksums.

== Linux kernel support ==
{{Todo|research and add to article}}
* Add a section on dmesg and hdparm -I output:
(...)
Commands/features:
Enabled Supported:
(...)
* Host Protected Area feature set
(...)
SET MAX security extension
Address Offset Reserved Area Boot
(...)

* Check boot parameters: is hda=stroke still valid?
Kernel command line: ro root=LABEL=/ acpi=off hda=stroke
ide_setup: hda=stroke -- BAD OPTION

* Recent (2.6.10 and up?) kernels disable HPAs automatically (in drivers/ide/ide-disk.c). Dmesg example:

hda: Host Protected Area detected.
current capacity is 110194034 sectors (56419 MB)
native capacity is 117210240 sectors (60011 MB)
hda: Host Protected Area disabled.

This should be (further researched and) added to this section (maybe with some pointers to the unexpected consequences of this new approach ...)

[[User:Pebolle|Paul Bolle]] 22:06, 6 Sep 2005 (CEST)

* SRCMOS24.EXE

In the PSA used by the Predesktop Area I found a "hidden" executable: SRCMOS24.EXE (it is not mentioned in the FAT). This executable can capture and update CMOS data. It might only be used by the FirstSight program to display (part of) the BIOS info. It might be nice to see what it can do and if similar things are possible under GNU/Linux.

[[User:Pebolle|Paul Bolle]] 22:01, 7 Sep 2005 (CEST)

== Newer thinkpads don't use Phoenix Firstware? ==

On my T42 that arrived yesterday, the predesktop area looks a lot like MS Windows. The widget set, the fonts, even the boot sequence looks exactly like Windows 2000. Debian-installer indentified it as "Microsoft Windows NT/2000/XP", while it identified my XP partition as "Microsoft Windows XP Professional"

Has Lenovo/IBM changed their system, or is this Phoenix stuff really just Windows?

-- [[Evan.Heidtmann]]

Evan,

Could it be that you're talking about the preinstalled version of Windows here? As far as I know (using information to be found on the internet, not personal research) the preinstalled OS will reformat its partition from FAT32 to NTFS at first boot. That could explain the difference in the identification by the Debian installer (which I never really used).

Moreover the Predesktop Area is part of the HPA and the HPA is not an partition. It seems unlikely that the Debain installer notices the HPA. As far as I know there are at present no GNU/Linux tools with a (useful) support of HPAs.

[[User:Pebolle|Paul Bolle]] 15:43, 4 Aug 2005 (CEST)

My T42P (model 2373HSG) is using a cut-down version of Windows XP as the pre-desktop area. I'm not sure whether it's a special IBM thing or just a [http://www.microsoft.com/licensing/programs/sa/benefits/winpe.mspx Windows PE] (preinstallation environment) setup. It includes Java and Python, which are used by some of the IBM tools, and the Opera web browser.

It's no longer an HPA but a 487MB hidden FAT32 called IBM_SERVICE located at the end of the disk.

--[[User:Korourke|Korourke]]

== Rescue and Recovery via grub? ==

Did anyone get the Rescue and Recovery partition to boot via grub on recent models? On a T43 with
rootnoverify (hd0,1)
chainloader +1
the Rescue and Recovery partition starts booting nicely and then, a few seconds in the R&R loading sequence, chokes with a
STOP: c000021a {Fatal System Error}
The Session Manager Initialization system process terminated unexpectedly with a status of 0xc000003a (0x00000000 0x00000000).
The system has been shut down.
The problem started right after installing grub into the MBR (I couldn't get the preinstalled MBR to boot grub from an active primary partition). It seems oblivious to the Predesktop BIOS setting.

The same problem has been reported by others with other models (for example [http://forums.fedoraforum.org/archive/index.php/t-19433.html here] for a T42).

[[User:Thinker|Thinker]] 11:35, 30 Sep 2005 (CEST)

Your "Rescue and Recovery partition" seems not to be a HPA (which isn't a partition). Maybe we should open a new page for that system.

[[User:Pebolle|Paul Bolle]] 21:54, 30 Sep 2005 (CEST)

It may very well not be an HPA , but the BIOS stil calls it a "Predesktop Area". Anyway, the partition is actually a VFAT partition (even though it has type 0x12, "Compaq Diagnostics"). It seems to boot into PC-DOS (using {{path|NTDETECT.EXE}} so it looks like Windows startup) and then its {{path|AUTOEXEC.BAT}} runs a fancy GUI.
--[[User:Thinker|Thinker]] 23:31, 30 Sep 2005 (CEST)
----
Right, there has been a lot of confusion about this, we should have a separate page. Introduced an edit link (called Rescue and Recovery) on the [[ThinkPad Technologies]] page for that purpose.

== Suggestions for projects ==

I'd guess it would be rather nice to have GNU/Linux tools (like sfdisk and parted) HPA aware. The most urgent change would be to have those programs at least recognize and respect a HPA (e.g.: do not write in or otherwise use the HPA area; unless the user gives a --force option or something similar).

As for now, I realize I caused this error: ENOPATCH.

[[User:Pebolle|Paul Bolle]] 22:56, 5 Nov 2005 (CET)

== Keeping functionality of the blue AccessIBM button ==

Somebody figured out [http://sharadware.com/2005/07/11/suse-linux-winxp-access-ibm-on-the-thinkpad-t43/|how to keep the AccessIBM functionality] when installing Linux, quite easy fix. How come nobody thought about it before? :)
(link got from [[Installing_Ubuntu_5.04_on_a_ThinkPad_T43_%281875%29|here]])

--[[User:Micampe|Micampe]] 17:39, 9 Dec 2005 (CET)

Thermal Sensors

2005-12-09T13:59:43Z

Micampe: /* ThinkPad {{R51}} */ typo

This page aims to summarize known information about the locations and properties of thermal sensors on ThinkPad laptops.

==Accessing the sensors==
The primary means of accessing the thermal sensors is through the [[ibm-acpi]] module, which provides up to 11 thermal sensors (some of which may be inactive) when loaded with the <tt>experimental=1</tt> option. Up to eight thermal sensors are exposed at {{path|/proc/acpi/ibm/thermal}}:

# cat /proc/acpi/ibm/thermal;
temperatures: 44 41 33 42 33 -128 30 -128

On some models there are three additional sensors at Embedded Controller offsets 0xC0 to 0xC2, which can be read by parsing {{path|/proc/acpi/ibm/ecdump}}:

# perl -ne 'm/^EC 0xc0: .(..) .(..) .(..) / or next; print hex($1)." ".hex($2)." ".hex($3)."\n"' < /proc/acpi/ibm/ecdump
40 48 43

The [[Active Protection System]] accelerometer also reports a temperature (but it is not certain that the sensor location is inside the HDAPS chip):

# cat /sys/bus/platform/drivers/hdaps/hdaps/temp1
41

Finally, the hard disk temperature can be read through the SMART interface:

# smartctl -A /dev/hda | grep Temperature
194 Temperature_Celsius 0x0022 145 097 000 Old_age Always - 31

==Sensor locations==

This information is model specific.

===ThinkPad {{T43}}===

The following image, prepared by Shmidoax, summarizes the results of his experiments using cooling spray to cool down components and observe the effect on the sensors.

[[Image:T43-thermal-sensors.jpg|ThinkPad T43 thermal sensors|600px]] (click to enlarge)

[[Image:T43-2668-thermal-sensors-zoom.jpg|ThinkPad T43 thermal sensors - zoom|500px]] (click to enlarge)

Summary:

EC offset Index in "thermal" Location (estimated)
0x78 1 CPU
0x79 2 Between PCMCIA slot and CPU (same as HDAPS module)
0x7A 3 PCMCIA slot
0x7B 4 GPU
0x7C 5 Battery (front left)
0x7D 6 n/a
0x7E 7 Battery (rear right)
0x7F 8 n/a
0xC0 none Bus between Northbridge and DRAM
0xC1 none Southbridge (under Mini-PCI card, under touchpad)
0xC2 none Power circuitry, on underside of system board under F2 key

===ThinkPad {{T40}}===

The location of one of the sensors is identified [http://forum.thinkpads.com/viewtopic.php?t=11574 here].

EC offset Index in "thermal" Location (estimated)
0x78 1 CPU
0x79 2 System board under rear left corner of Mini-PCI module
0x7A 3 ?
0x7B 4 GPU
0x7C 5 Battery
0x7D 6 n/a
0x7E 7 Battery
0x7F 8 n/a
0xC0 none n/a
0xC1 none n/a
0xC2 none n/a

===ThinkPad {{R51}}===

The [[ibm-acpi]] documentation includes the report by Thomas Gruber:

EC offset Index in "thermal" Location (estimated)
0x78 1 CPU
0x79 2 Mini-PCI
0x7A 3 HDD
0x7B 4 GPU
0x7C 5 Battery
0x7D 6 n/a
0x7E 7 Battery
0x7F 8 n/a
0xC0 none ?
0xC1 none ?
0xC2 none ?

File:T43-2686-DGU-CDC.jpg

2005-12-07T15:26:17Z

Micampe:

ThinkPad T43 2686-DGU internal photo: [[CDC slot]] with [[IBM Integrated 56K Modem (MDC-2)]]. At the front of the picture you can see the three antenna wires (white, black, light gray) coming in from the LCD - two wires for the WiFi antennas and one for the BlueTooth antenna (which just goes around the CDC and is taped underneath it, since this one doesn't have Bluetooth).

Talk:Fan control scripts

2005-12-07T15:19:55Z

Micampe:

Wyrfel, are you sure the recent (19:54, 27 Oct 2005) cosmetic change was a good idea? The extensive chunks of code make it hard to grok the structure of the article in the absense of separator lines (which "===" doesn't have). --[[User:Thinker|Thinker]] 22:10, 27 Oct 2005 (CEST)
----
We can discuss this. From my point of view, the chunks of code distinguish themselves from each other quite well, because they are each in one code block.

I do not like the <nowiki>=</nowiki> section level - and so far we avoided them on all pages - because
* it generates H1 headings, which is the same as the page heading,
* having more than one level with the hbars is confusing/less readable, because they are not very well distinguishable. This way i.e. the "Other" section looked like a separate empty secion.

I think the way it's now, the separator lines make it possible to easily distinguish the different main sections, while when you have both levels with separator lines, an additional task of distinguishing H1 and H2 separators is necessary.

However, i see your point as well and would like to hear more opinions/arguments.

[[User:Wyrfel|Wyrfel]] 22:31, 27 Oct 2005 (CEST)
----

===<tt>bash</tt> script with fine control over fan speed (for unpatched kernels)===
Moved to the [[ACPI fan control script|article page]], after joint development by [[User:Spiney|Spiney]] and [[User:Thinker|Thinker]].

----

''Note that the fan levels, thresholds and anti-pulsing hacks are system-specific, so you may need to adjust them.''

I think it'd probably be nice to have a table of the suggested values here. Those in the "unpatched kernels" script seems to work fine on my R52, but the other scripts all have different values.

--[[User:Micampe|Micampe]] 08:19, 12 Nov 2005 (CET)

== Sensor-specific variable-speed script ==

Here's a new variable-speed control script that lets you define the temperature range separately for each sensor. To keep things simple, it auto-computes the trip points (unlike the current script). Works well on a {{T43}}, and (just barely) keeps the fan off most of the time with CPU undervolting and [[fglrx]] set to maximum power saving. Feedback on other machines would be appreciated.

Any idea what are the sensors at EC offsets 0x79, 0x7A, 0xC0, 0xC1, 0xC2? On the T43, 0x79 seems to be the same as the HDAPS sensor (it never deviates by more than one degree from what the HDAPS sensor tells directly), but I don't know where it's located. Sensor 0x7A is uncorrelated with disk temperature and activity, so it can't be HDD like reported ofor R52. Sensor 0xC1 seems to be under the palm-rest (see discussion in [[Talk:Problem_with_fan_noise]]).

This version also lets the EC read the RPM sensor every few minutes even when the anti-pulsing hack (which normally prevents this) is in use.

<i><b>Script moved to the [[ACPI fan control script#Variable speed control scripts|article page]]</b></i>.
{{HINT|If you followed a link here looking for thermal sensor information, see the [[ACPI fan control script#Variable speed control scripts|article page]].}}

Feedback very much welcome.

--[[User:Thinker|Thinker]] 23:08, 27 Nov 2005 (CET)
----

== Fan enable/disable scripts ==

We currently have two types of scripts -- the old ones which only enable/disable the fan, and the new ones which control the fan speed. Do the latter supercede the former, or do we know of models on which only enable/disable works? Maybe eventually the enable/disable scripts should be "archived" in the talk page to reduce clutter in the article?

--[[User:Thinker|Thinker]] 00:08, 28 Nov 2005 (CET)
----

Things seem pretty stable for the variable-speed script and the [[Patch_for_controlling_fan_speed#Models_on_which_this_patch_works|list of working models]] looks good. Since it is superior to the enable/disable scripts in regard to both the annoyance and the impact on hardware, I'll change the organization of the page to put that script first (unless someone objects)..

--[[User:Thinker|Thinker]] 16:07, 7 Dec 2005 (CET)
----

I don't see the point in having the enable/disable scripts when the variable speed one works fine. I'd vote for moving the old scripts here and only keep the better ones in the article, unless somebody has a sane use case for which those are bettere than the new scripts.

--[[User:Micampe|Micampe]] 16:19, 7 Dec 2005 (CET)

Talk:SMAPI support for Linux

2005-12-07T13:39:59Z

Micampe:

Talk:Problem with fan noise

2005-12-07T11:56:49Z

Micampe: /* Fan speed control? */

== Problem with fan noise on R51 1829 L7G (ATI M9) ==

On my R51 the fan is behaving like this:

* > 45C -> fan on;
* < 38C -> fan off.

By using cpufreq + laptop_mode + Xorg DynamicClocks + WiFi power management, I get the fan stopped time to time, but only for 3 minutes time (transition from 38 C -> 45 C). The cooling down cycle is taking 20 minutes in the best case.

I knew about the 'ibm_acpi experimental=1' trick, but in my opinion this is not very useful since nobody can guarantee that a temperature greater then 45 C will not damage the laptop and in the same time the transition time is very short (the laptop gets hot fast without fan).

== Thinkpad T42 Radeon Mobility M7 ==

When Xorg is running, the fan is always on and pretty loud !
Setting DynamicClocks does not help

it's clear that the GPU is the problem on the thinkpad :

after 10minutes with the fan off
temperatures: 44 47 33 52 32 -128 24 -128

1: CPU
2: Mini PCI Module
3: HDD
4: GPU
5: Battery
6: N/A
7: Battery
8: N/A

Controlling the fan speed would be really cool !

What is the maximum temperature not to cross ?
----
Word on the 'net is that 85 degrees is the max operating temp for most of the Intel chips. I've seen some high 70's all the time (just put it on carpet for awhile and play some quake3 :). I wouldn't let your processor get much higher than 85...

----
Older versions of xorg (i.e. 6.7.0) don't seem to be able to use the DynamicClocks option although it's set in the xorg.conf. Search the log to find out if it's really used.

== Thinkpad R32 with Radeon Mobility M6 ==

Updating xorg-x11 from 6.7.0 to 6.8.2 and using Speedstep (with the ondemand module in this case) helped cooling the system down significantly:

* before updating the CPU was ~62 C in idle state, and got very near the critical temperature (72 C) during heavy load - I even got some freezes because of the heat ;)
* after the update the CPU is ~54 C in idle state, and still gets to about 68 C while under heavy load

The second sensor (which may be the GPU) is somehow fixed to 50 C (maybe a bug?)

The fan on the R32 is behaving like this:

* > 61 -> fan in state 2 (quite noisy)
* < 55 -> fan in state 1 (less noisy :) )

But I remember using my old SuSE distribution with kernel 2.4.16, apm and some old x11 version the fan actually stopped completely from time to time.

Concerning the maximum temperature of the CPU, I found that the critical temperature on the R32 for the CPU sensor is 72 C
(using {{cmdroot|cat /proc/acpi/thermal_zone/THM0/trip_points }} )

== Fan Control script: more safe version ==

ibm_acpi works well on my R50 and R51. But to rely on it completely, I modified the script in two ways:

1. It catches verious signals and turns the fan on before it quits

2. It turns off the fan under very strict conditions, leaving it on when unexpected errors occur.

Here is my script:

#!/bin/sh

# july 2005 Erik Groeneveld, erik@cq2.nl
# More conservatiev and saver version
# It make sure the fan is on in case of errors
# and only turns it off when all temps are ok.

IBM_ACPI=/proc/acpi/ibm
THERMOMETER=$IBM_ACPI/thermal
FAN=$IBM_ACPI/fan
MAXTRIPPOINT=65
MINTRIPPOINT=60
TRIPPOINT=$MINTRIPPOINT

echo fancontrol: Thermometer: $THERMOMETER, Fan: $FAN
echo fancontrol: Current `cat $THERMOMETER`
echo fancontrol: Controlling temperatures between $MINTRIPPOINT and $MAXTRIPPOINT degrees.

# Make sure the fan is turned on when the script crashes or is killed
trap "echo enable > $FAN; exit 0" HUP KILL INT ABRT STOP QUIT SEGV TERM

while [ 1 ];
do
command=enable
temperatures=`sed s/temperatures:// < $THERMOMETER`
result=
for temp in $temperatures
do
test $temp -le $TRIPPOINT && result=$result.Ok
done
if [ "$result" = ".Ok.Ok.Ok.Ok.Ok.Ok.Ok.Ok" ]; then
command=disable
TRIPPOINT=$MAXTRIPPOINT
else
command=enable
TRIPPOINT=$MINTRIPPOINT
fi
echo $command > $FAN
# Temperature ramps up quickly, so pick this not too large:
sleep 5
done

----
I added this script to the other ones. Don't wander about my talk edits, i didn't realize i was on the talk page. [[User:Wyrfel|Wyrfel]] 01:48, 13 Aug 2005 (CEST)
----

== X41 ==

Same fan problem here on the X41. Once it starts it won't stop (unless it is _very_ cold outside). Undervolting the CPU doesn't help - still the same problem.

== Fan speed control? ==

Only the X31 and X40 have an ACPI method for controlling the FAN speed (this is why ibm_acpi provides this functionality just for these models).

What will happen if we take the "FANS" method from the [http://acpi.sourceforge.net/dsdt/view.php?id=219 X40 DSDT], paste it into a iasl-disassembled DSDT of (say) a T43, recompile it and [http://gaugusch.at/kernel.shtml tell the kernel] to use the patched DSDT? ibm_acpi will present the functionality, but it may or may not work.

--[[User:Thinker|Thinker]] 16:16, 28 Sep 2005 (CEST)

Any risk of damaging the hardware when doing this? E.g. what does occur if the system overheats - will the CPU be destroyed are does it automatically switch of? As I've just bought a new X41 I don't want to take any stupid risks - but otherwise I'd say let's try it out.

--gst Thu Sep 29 18:14:13 CEST 2005

I think Intel CPUs have some built-in thermal protection, but I'd hate to test it. And of course, any fiddling with the hardware at this level might damage it. That said, when the CPU is mostly idle it keeps a reasonable temperature even when the fan is disabled, so as long as you keep an eye on both the CPU usage meter and /proc/acpi/ibm/thermal, things should be pretty safe temperature-wise. For extra safety you can force the CPU to its lowest speed via {{path|/sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq}}.
--[[User:Thinker|Thinker]] 18:33, 29 Sep 2005 (CEST)

----

Anybody tried to slow down the fan and have it running at ~1000-1500rpm? That would make it almost silent and you could have it always running (like Apple does on Macs).

--[[User:Micampe|Micampe]] 12:56, 7 Dec 2005 (CET)

== Further discussion ==

I've just found a very interesting thread regarding the same issue on HP notebooks. IMO it provides many insight information about heat/fan problems in general, the URL is: http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=853249
Especially the posts by the HP engineer "Andy Fisher" are very interesting. IBM should be able to provide the same BIOS fix as HP did (maybe I should have bought an HP notebook instead of a Thinkpad?).

I've also contacted IBM/Lenovo support via the website about the fan issue. Maybe it helps when others do this as well (especially people who bought larger quantities) so that this issue is taken serious by Lenovo. Is there already any official response to this problem?

--gst Thu Sep 29 19:40:34 CEST 2005
----

Two of the changes mentioned by the HP engineer make perfect sense here: raise the low trip points and make speed transition gradual. Oh, and get rid of the annoying beat pattern (a brief speed pulse every few seconds) it sometimes gets into!

But from our perspective, what would probably be best is to do the whole thing in software, providing the flexibility for personal preferences and smart decisions. The hardware would only enforce emergency override or throttle/shutdown for extreme temperatures. Then we could do cute things like having a software daemon lower the thresholds in a noisy environment (as judged using the built-in microphone) or when the laptop is on the user's lap (as judged by the built-in accelometers).

--[[User:Thinker|Thinker]] 18:47, 30 Sep 2005 (CEST)

I noticed that on my T43 the fan is usually in one of two modes, low speed (around 3300 RPM, triggered around CPU=47deg) and medium speed (around 4100 RPM, can't figure out the trip condition). The former is nearly inaudible, but the latter is quite noticable in the absense of strong background noises.

Now, the problem is that once it has tripped into medium speed, it usually never comes back to low speed until the next reboot. So once it happens, to quiet things down I can only run one of the fan-disabling scripts given here. But with a disabled fan the T43 is not thermally stable, so it will spend its time moving back and forth between the hysteresis thresholds, i.e., toggling between 4100 RPM and 0 RPM every few minutes. This is quite silly and annoying, when staying at low speed would be both more stable and more quiet.

I hope someone will find a way to control the fan speed, or at least to reset the embedded controller's hysteresis state.

--[[User:Thinker|Thinker]] 10:29, 6 Oct 2005 (CEST)

When you do changes to e.g. the Energy Schema in Windows or you eject the Thinkpad of the Docking Station it seems that the controllers state is rest. At least on the X41 the fan does stop until it reaches the threshold to start some minutes later. So it should be doable. --85.124.171.70

That's good. But just like a bunch of other functions (e.g., controlling the battery charge threshold), it probably uses low-level undocumented proprietary interfaces which are very hard to figure out without the help of IBM/Lenovo, who are in denial about the whole thing. --[[User:Thinker|Thinker]] 01:40, 16 Oct 2005 (CEST)

----

== Works fine with APM instead of ACPI? ==

On my X41 the fan starts after about 10 minutes of use and doesn't stop (until it is rather cold in my room - and even then it runs most of the time ;) A friend of mine who has a X41 too (though another model) and who does use NetBSD and APM doesn't experience this problem. He claims that the fan only comes up if the system is not idle. So either it is colder in his room, the X41 model which he has doesn't have this flaw or APM does use different tresholds than ACPI.

* Then why not just try the {{bootparm|acpi|off}} kernel parameter and see what happens? --[[User:Thinker|Thinker]] 18:14, 30 Sep 2005 (CEST)

I currently don't have physical access to the X41. Will try in a few days.

== Rewiring the fan? ==

Since IBM/Lenovo shows no intention of fixing their embedded controller firmware or releasing its specs, how about getting the embedded controller out of the loop? I'd be happy as a clam if my fan was hard-wired to work at a constant 3000RPM, with temperatures kept at bay in software through CPU frequenty control.

Assuming the fan has the standard 3-wire connector, we can probaby keep the sensor and ground wires untouched, and rewire the positive wire to some nearby current source of appropriate voltage (through a resistor, for fine-tuning). The trick would be to find an easily tappable source that can handle an extra 2W and has the appropriate voltage (i.e., just slightly higher than what the fan needs to rotate at that RPM, so we don't waste too much energy in the resistor). Any idea what are the typical fan voltages and what would be an appropriate hookup point?

--[[User:Thinker|Thinker]] 01:59, 16 Oct 2005 (CEST)
----

== Secret sensor and the cause of fan always on ==

On my {{T43}}, ecdump offsets 0xC0-0xC2 seem to include 3 more temperature sensors that are not seen in {{path|/proc/acpi/ibm/thermal}}:
# cat /proc/acpi/ibm/thermal;
temperatures: 44 41 33 42 33 -128 30 -128
# perl -ne 'm/^EC 0xc0: .(..) .(..) .(..) / or next; print hex($1)." ".hex($2)." ".hex($3)."\n"' < /proc/acpi/ibm/ecdump
40 48 43

Note the "48" entry (EC offset 0xC1). Something's pretty hot even at full full speed (level 7, 4700RPM). This sensor increases very quickly when the system starts (in fact, faster than anything else when the CPU is undervolted and [[fglrx]] is in maximum powersaving).

Now, note this: the fan kicks up from low speed to medium speed whenever this sensor reaches 46 degrees, even if no other sensor changes; and this seems to usually be the first trigger encountered. Moreover, this sensor hovers around 47-48 degrees even on an idle machine. Taken together, '''this fully explains the "fan always on" behavior: a previously-unnoticed sensor that's always hot.'''

Any idea what this sensor is? It seems correlated with WiFi: there's a 2deg difference when I toggle {{path|/sys/bus/pci/drivers/ipw2200/*/rf_kill}} (without ever being associated so this shouldn't affect anything else), and heavy WiFi data transfer increases temperature by several more degrees. This suggests the sensor is located in or close to the mini-PCI slot (i.e., under the touchpad). That region is indeed often hot to the touch. But why would the mini-PCI slot get so hot? Could it be the southbridge, which sits under the mini-PCI slot with no heatsink and poor ventilation? Can anyone correlate this sensor other specific activity, or with blocking of specific ventilation holes, or with cooling of specific components? If it's the mini-PCI slot? The operating temperature of the Intel 2200BG is [ftp://download.intel.com/network/connectivity/resources/doc_library/tech_brief/2200bg_prodbrief.pdf 0-80 deg].

Caveat: this is my experience with a {{T43}} after [[Pentium M undervolting and underclocking|undervolting]] the CPU and activating [[How to make use of Graphics Chips Power Management features|maximal GPU powersaving using fglrx]]. It could be that for other people, other components are the first to trigger. But either way, those are 3 temperature sensors we didn't know of and they're used by the Embedded Controller's algorithm.

--[[User:Thinker|Thinker]] 16:20, 20 Nov 2005 (CET)
----

At the moment I am experimenting with controlling the fan on Windows XP with a self written tool on a {{T43}} (Model 2668 97G). Having found the information about the secret sensors here I built these into the program and it seems that after starting my cooled (placed outside) {{T43}} the 0xC1 sensor indeed rises fastest but also cools down quite quicky especially if also the CPU is cool. I have seen it hotter than the CPU but not much cooler, so probably it is a small chip connected to the colling element of the CPU.

The values at 0xC0 and 0xC2 also seem to show temperature values here, while 0xC4 is always at 128.

First experiments indicate that as long as all the temperature value are below 43Â°C the Thinkpad comes up with no fan and stays that way. (The fan control register at EC offset 0x2F set to 0x80, see the bottom of the [[patch for controlling fan speed]] page for a description of this register). If 43Â°C are reached on the 0xC1 sensor, the fan kicks in with low speed while 43Â°C on the CPU do not activate the fan. With regard to the CPU the kick-in seems to be around 48Â°C.

Once the fan is on, it goes off again if all the seonsors drop to the area of 38Â°C or lower (the value may not be precise). But it hardly happens on it's own, for tests I placed it outside in cold weather.

On [http://forum.thinkpads.com/ forums.thinkpad.com] is a ([http://forum.thinkpads.com/viewtopic.php?t=14580http://forum.thinkpads.com/viewtopic.php?t=14580 discussion]) from users who experimented with physically cooling the North- and Southbridge without success. In a different thread there a user claimed that he worked with a couple of Thinkpads and silenced them by turning off unused devices, WLAN being among them.

With the XP WLAN device disabled the temperature on 0xC1 stays around 41Â°C here even if there is heavy activity on the CPU. It rises as soon as the WLAN device is enabled but hardly goes any hotter than 44Â°C. But I also could not make it go hot at all running on battery. And the heat reading there somehow more or less follows the value of the CPU.

Bottom line on my {{T43}} (2668 97G): Fan kicks in for CPU around 48Â°C or 0xC1 at 43Â°C and then never goes off again unless you use external cooling. 0xC1 sensor could to be related to WLAN (I'm not really sure about it) and/or is probably placed near the CPU. It could also have something to do with running the machine no AC rather than battery.

-- Shimdoax - 2005-11-27
----

Shimdoax, you said "''I have seen it hotter than the CPU but not much cooler, so probably it is a small chip connected to the colling element of the CPU''", but also "''the temperature on 0xC1 stays around 41Â°C here even if there is heavy activity on the CPU''". It follows that your CPU is never much hotter than 41Â°C, which I find unlikely... Anyway, on my T43, sensor 0cC1 is correlated with the CPU but very slightly; it is more correlated with the GPU, but not very much either.

I suspect that sensor 0xC1 sits on the system board under the touchpad, since this is consistent with all of the following:
* In idle with wireless off, sensor 0xC1 has roughly the same temperature as the GPU (which is adjacent on the system board, under the spacebar and TrackPoint buttons).
* Correlation with the WLAN card activity (which is sandwiched between the system board and the touchpad).
* Quick warm-up (the southbridge is also on the system board under the touchpad, and has no heat spreader).
* Negligible effect of fan speed on 0xC1 temperature (the touchpad area is cramped and lacks decent ventilation, hence has negligible air flow).
* When I place a 12cm-by-12cm pad of thick thermally isolating material (a folded fleece blanket...) under the touchpad, 0xC1 temperature consistently rises by 2-3 degrees (and cools back when I remove the pad); other sensors seem unaffected.

If this is indeed the case, it's hard to see what can be done (other than using a fan control script with an increased threshold for this sensor). It looks like IBM/Lenovo counted on this area being passively cooled through the bottom of the case - see how the bottom of the laptop is designed to allow air flow under the front quarter? However, once the desk under the laptop has warmed up (or if air flow is blocked, as when the laptop is sitting on the top of a lap), things just cook up. The [http://forum.thinkpads.com/viewtopic.php?t=14580http://forum.thinkpads.com/viewtopic.php?t=14580 mods] which thermally connet the southbridge to the GPU cooling assembly might improve things a bit, but on my system sensor 0xC1 isn't much hotter than the GPU anyway. Maybe ventilation can be improved by letting in more air through the speaker grills on the front - does anyone know what things looks like, under the very front of the palmrest? This won't solve "fan always on" since it will help only when the fan is on, but it may let the fan run at a lower speed.

BTW, Shimdoax, how are you monitoring/controlling the EC under Windows?

--[[User:Thinker|Thinker]] 18:22, 27 Nov 2005 (CET)
----

Thinker,

I currently don't know where to read the GPU temp from, so I can't say much about it (I'm running XP and have not found drivers or tools that would display the GPU).

However, regarding my experiments: I had the machine on my desk earlier today (when I wrote the post) on AC with WLAN connection to the office network and "Max. Battery Life" Scheme. I had taken it from the trunk of the car (it's quite cold outside, around freezing). During the whole experiments the CPU hardly went higher than 46Â°C, most of the time it was around 39Â°C to 43Â°C. I wasn't very systematic in these tests, these were just first observations.

However, I think I can confirm that the 43Â°C on the C1 triggers the fan on my machine here. 48Â°C to 50Â°C on the CPU also triggers the fan on. Then I put the laptop outside the window twice. Temperatures dropped quite quickly and around MAX(CPU, 0xC1) of 38Â°C the fan turned itself off.

Further tests on the WLAN revealed mixed results about correlation. If the CPU goes up the C1 also goes up, even if WLAN is disabled. On the other hand I had cases where WLAN (big folder copy) made the C1 rise ahead of the CPU. The way I tested it, mostly the C1 triggered the fan before the CPU did. This at least explains why CPU undervolting/clocking doesn't help much.

But I think you're right. Without custom scripts I guess it will be hard to keep the C1 below 43Â°C. This value may even be intentional by IBM. If it is really near the palmrest, higher values may cause burns (I once read about a guy who actually burnt his balls [no joke!] by working with a laptop which had a 42Â°C - 45Â°C battery temp. in his lap for an hour or two). So they may think that fan noise is preferrable to bad publicity.

Hence I'm not counting on IBM. Instead I'm currently writing a custom fan control program for XP, that's how I read the EC there. I'll post a first version [http://forum.thinkpads.com/viewtopic.php?t=17715 here] later today. Maybe some folks from the hardware modding thread will help to locate the sensors with some cooling spray.

-- Shimodax - 2005-11-27
----

Shimodax,

Great to see work on a Windows solution, especially from Emtec! (Alas, I let my ZOC registration expire when I switched to Linux). Will you be releasing the source code?

If the 0xC1 sensor is near the southbridge then it will be affected by CPU activity both because of related southbridge activity and by thermal conductance via the motherboard; but I've seen 0xC1 at 47deg and CPU at 59deg (after a long burn-in), so they can't be too close. About the palmrest, IBM actually brags about low palm rest temperature in some of their marketing publication. But ironically the hottest and worst-cooled area of the laptop (where I suspect 0xC1 sits) is in the bottom center right under the touchpad - which tends to coincide with certain anatomical regions... BTW, GPU temp is EC offset 0x7B; there a partial list inside my new fan control script at [[Talk:ACPI_fan_control_script]] (I'll move it to the article page soon).

--[[User:Thinker|Thinker]] 23:20, 27 Nov 2005 (CET)
----

+LOL+ I wouldn't have expected that anybody would know me :-)

Yes, I'll release source code soon. I took quite some pain in writing this tool without our proprietary classes and libs in order to be able to release the source (or at least maintain a basic Open Source version). I'll see if SourceForge accepts the project (applied on Saturday), otherwise I'll have find another place.

Thanks for the info about the GPU ...

Markus

-- Shimodax - 23:42 (CET) - 2005-11-27
----

For the record: the new [http://forum.thinkpads.com/viewtopic.php?p=111974 "Shimodax fan control tool : sharing values"] topic at the thinkpads.com forums tracks some other users' experience with their sensor. So far the only new observation is that sensor 0x7A (3rd) is probably in the vicinity of the the CPU or northbridge.

--[[User:Thinker|Thinker]] 12:53, 28 Nov 2005 (CET)
----

Just now I see the C2 higher than C1 and rest of the system for the first time. Only difference I can think of is the fact that the battery is loading. I hooked it on with 6% left about 30 minutes ago. Usage was mainly web broswing (firefox, maybe a webpage with animated gif ads). C2 triggered the fan at 50Â°C two times.

CPU 42Â°C (0x78)
APS 41Â°C (0x79)
X7A 34Â°C (0x7A)
GPU 44Â°C (0x7B)
BAT 40Â°C (0x7C)
BAT 31Â°C (0x7E)
XC0 40Â°C (0xC0)
XC1 46Â°C (0xC1)
XC2 48Â°C (0xC2)

-- Shimodax 00:17 CET - 2005-11-30
----

Upon further casual observation I would like to offer the theory that the C2 sensor is indeed related to battery loading and may be located rear/left (under the Esc/F1) on a T43. See: page 2 on [http://forum.thinkpads.com/viewtopic.php?p=111974 "Shimodax fan control tool : sharing values"]

-- Shimodax 13:27 CET - 2005-12-01
----

I happen to have a photo of that area from the last time I opened my T43, and indeed it looks like there's some power circuitry there:

[[Image:T43-2686-DGU-CDC.jpg|500px|T43 CDC]]

Those two "150 A47L" are just above the ventilation grill. Any idea what they could be?

--[[User:Thinker|Thinker]] 20:11, 1 Dec 2005 (CET)
----

Don't know ... they could look like power stabilizing transistors, but I have very little knowledge of electronic (especially of SMD circuits) so that's just wild guessing.

Hoever, the system is currently loading battery again and I played with the fan. The C2 does react to the fan quite slowly and when I forced the fan off it rose no higher than 55Â°C. Also from touching the bottom of the laptop, I'd say the hottest part of that area is between the grill and the latch for the DRAM expansion (probably below the thing in the center of your photo).

-- Shimodax 01:53 CET - 2005-12-02

----

Makes perfect sense. So 0xC2 sits under the CDC and monitors the power circuitry (not just battery charging, since it also heats up slightly above its environment without a battery). Then XC2->PWR, I guess. Two more to go: 0x7A and 0xC0 (both are nice and cool here).

--[[User:Thinker|Thinker]] 03:35, 2 Dec 2005 (CET)
----

I'll then rename it in my tool with the next release. Btw, do you have any idea what the APS might be on other models?

-- Shimodax 14:07 CET - 2005-12-03
----

It's easy to check if 0x79 is the HDAPS accelerometer or not: read the HDAPS temperature directly and compare. For getting the HDAPS temperature you can follow the Linux hdaps.c driver, or just reboot to Linux and look at {{path|/sys/bus/platform/drivers/hdaps/hdaps/temp1}} (and at {{path|/proc/acpi/ibm/thermal}} for the first 8 EC sensors). On my T43, the 0x79 always matches the HDAPS sensor (usually identical but sometimes 1 degree off, probably due to a different sampling time). BTW, my [[ACPI_fan_control_script#Variable_speed_control_scripts|ACPI fan control script]] monitors both, just in case.

Speaking of which, the table at the top of that script reflects all knowledge gleaned from the forum.tinkpads.com discussion. Feel free to update it (maybe we should move it to a separate and more spacious page?).

--[[User:Thinker|Thinker]] 15:03, 3 Dec 2005 (CET)
----

For another view of the 0xC2 area, including a peek under the CDC card, see IBM/Lenovo's [http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=MIGR-51451 CDC removal movie]. There seems to be nothing very exciting visible on the upper side on the motherboard (but judging by the plastic buldge in the bottom of the case, there's probably some circuitry on the underside).

--[[User:Thinker|Thinker]] 16:39, 3 Dec 2005 (CET)
----
I just had the idea that 0xC0 could be the Northbridge chip. See [http://forum.thinkpads.com/viewtopic.php?p=111974 "Shimodax fan control tool : sharing values"]

-- Shimodax 23:15 CET - 2005-12-05
----

Yes, 0xC0 is very much correlated with CPU temperature. But if it's the northbrighe then it's surpsigingly cool, since northbridges usually run pretty hot, and the 815PM has a small surface area and no cooling assembly whatsoever, see here:

[[Image:ThinkPad-T43-under-keyboard-left.jpg|500px|T43 systemboard]] (click to enlarge)

--[[User:Thinker|Thinker]] 00:45, 5 Dec 2005 (CET)
----
Mmmh, I guess I'll remove the keyboard and play with some cooling spray. It seems that a good part of the inside area can be reached through the opening of the keyboard.

-- Shimodax 23:15 CET - 2005-12-05

-----
Just in case - these [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-50233 instructions and movies] are pretty useful. It looks like the palmrest should be easy to remove too, but I didn't try that.

Keep us posted :-)

And please take plenty of photos! You never know what you'll want to look up later (as with those 0xC2 power chips above).

--[[User:Thinker|Thinker]] 17:34, 6 Dec 2005 (CET)
----
Someone on a [http://thinkpad-forum.de/forum/viewtopic.php?p=29286#29286 German forum] reported that he saw pictures on an U.S. forum where someone said he located the 0xC1 with cooling spray. Seems indeed to be below the left of the touchpad on the mainboard (pictures on the forum article linked above)

-- Shimodax 22:50 CET - 2005-12-06

Interesting. That's a T40, right? Similar layout but different cooling assembly. Anyway, the T40 didn't have HDAPS, but on the T43 the HDAPS accelerometer chip is just 1 or 2 centimeters down from the location of the chip marked here. And on the T43, sensor 0xC1 and direct HDAPS reads give very different results. So maybe they moved 0xC1 away on the T43? Or, maybe the temperatures read through by HDAPS driver actually come from a separate sensor located elsewhere (unlikely but possible).

--[[User:Thinker|Thinker]] 01:05, 7 Dec 2005 (CET)
----

Talk:SMAPI support for Linux

2005-12-07T11:52:51Z

Micampe:

SMAPI support for Linux

2005-12-07T08:18:40Z

Micampe: Added R52 to supported models

ThinkPad laptops include a proprietary interface called SMAPI BIOS (System Management Application Program Interface) which provides some
hardware control functionality that is not exposed by any other interface (e.g., ACPI).

The SMAPI interfaces changes a lot between models, and is poorly documented, so Linux support is not exhaustive for most models. There are currently two SMAPI access mechanisms available: <tt>thinkpad</tt> and <tt>tpctl</tt> for older ThinkPads, and <tt>tp_smapi</tt> for newer ones.

{{WARN|These drivers use undocumented features and direct hardware access. They thus cannot be guaranteed to work, and may cause arbitrary damage
(especially on models they weren't tested on).}}

==Using the <tt>thinkpad</tt> module==

This solution consists of a module, called <tt>thinkpad</tt>, and a user-space tool caled <tt>tpctl</tt>. It provides very rich functionality for older ThinkPads, but on newer ThinkPads much of this functionality is exposed and supported through an ACPI interface and the SMAPI access does not work anymore. For details, see the [http://tpctl.sourceforge.net/README README] and [http://tpctl.sourceforge.net/SUPPORTED-MODELS list of supported models].

* Project page: http://tpctl.sourceforge.net/
* You need to download the [http://sourceforge.net/project/showfiles.php?group_id=1212&package_id=29354t thinkpad module] and [http://sourceforge.net/project/showfiles.php?group_id=1212&package_id=1204 tpctl userspace tool].
* There is also an optional GUI: [http://sourceforge.net/project/showfiles.php?group_id=1212&package_id=99929 configure-thinkpad].

==Using the <tt>tp_smapi</tt> module==

The <tt>tp_smapi</tt> kernel module exposes some features of the SMAPI BIOS found on recent ThinkPads via a sysfs interface. Currently, the only implemented functionality is control over battery charging (this is useful for [[Maintenance#Battery_Treatment|increasing battery lifetime]], or for using a leftover under-spec power supply that can't handle the combined power draw of running and charging).

* Project page: http://tpctl.sourceforge.net/
* You need to donwnload only the [http://sourceforge.net/project/showfiles.php?group_id=1212&package_id=171579 tp_smapi kernel module].

To compile and load the module:

# tar xzvf tp_smapi-0.06.tgz
# cd tp_smapi-0.06
# make load

To install permanently (optional):

# make install
# modprobe tp_smapi

Example of usage:

# echo 40 > /sys/devices/platform/smapi/start_charge_thresh
# echo 70 > /sys/devices/platform/smapi/stop_charge_thresh
# cat /sys/devices/platform/smapi/*_charge_thresh
40
70

To unconditionally inhibit charging for 17 minutes:

# echo 17 > /sys/devices/platform/smapi/inhibit_charge_minutes

To cancel charge inhibiting:

# echo 0 > /sys/devices/platform/smapi/inhibit_charge_minutes

If you get a "not supported" error, your laptop doesn't provide the specific function (or at least not via SMAPI).

Other things that can be controlled through SMAPI, but are not supported in this version of the driver, include forcing battery discharge, PCI bus power saving, CPU power saving control, extended smart battery information, CD/DVD drive speed control and fan control. See the included README file for more information.

====Models on which this driver works====
* ThinkPad {{T43}}, {{T43p}}, {{X41}}, {{R52}} (all functions)
* ThinkPad {{T42p}}, {{X40}}, {{G41}} (all except <tt>stop_charge_thresh</tt>)
* ThinkPad {{T40p}} (only cdrom_speed)

For the details, see the README file inside the package.
If you have new data, please report it on the [[Talk:SMAPI support for Linux|discussion]] page.

====Models on which none of the functions work====
* ThinkPad {{T40}}, {{R50p}}, {{R40}}, {{X31}} and probably all earlier models. These apparently don't have the relevant capabilities, even under Windows.

Please update the above and report your experience on the [[Talk:SMAPI support for Linux|discussion]] page. If the module loads but gives "not supported" errors when you try to use it, report whether the corresponding functionality is available under Windows - maybe your ThinkPad just can't do that.

[[Category:Tools]] [[Category:Patches]]

WD90C24

2005-12-05T22:39:25Z

Micampe: vandalism

__NOTOC__
{| width="100%"
|style="vertical-align:top" |
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;">
=== WD90C24 ===
This is a Western Digital video adapter

=== Features ===
* Chipset: WD90C24, WD90C24A or WD90C24A2
* 1MB DRAM
* Interface: VL-Bus 2.0
</div>
|style="vertical-align:top" |
|}

=== Linux X.Org driver ===
This chip is not supported by X.org, the best you can get is 640x480 with 16 colors with the 'vga' driver as part of the X.Org distribution

=== Linux XFree86 driver ===
XFree86 3.3.6 was the last version to support this chip with the 'svga' driver.

==== ThinkPad LCD ====
Display on the internal LCD works as long as you set the monitor settings correct.

==== External VGA port ====
??

=== Linux kernel Framebuffer driver ===
??

=== ThinkPads this chip may be found in ===
* {{345C}}, {{345CS}}
* {{355}}
* {{360}}, {{360C}}, {{360Cs}}, {{360CE}}, {{360CSE}}, {{360P}}, {{360PE}}
* {{370C}}
* {{355C}}, {{355Cs}}
* {{510Cs}}
* {{750}}, {{750C}}, {{750Cs}}, {{750P}}
* {{755C}}, {{755Cs}}, {{755CE}}, {{755CSE}}, {{755CD}}, {{755CDV}}, {{755CV}}, {{755CX}}
* {{820}}, {{850}}

[[Category:Components]]

WD90C24

2005-12-05T22:38:48Z

Micampe: reverted vandalism

__NOTOC__
{| width="100%"
|style="vertical-align:top" |
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;">
=== WD90C24 ===
This is a Western Digital video adapter

=== Features ===
* Chipset: WD90C24, WD90C24A or WD90C24A2
* 1MB DRAM
* Interface: VL-Bus 2.0
</div>
|style="vertical-align:top" |
|}

=== Linux X.Org driver ===
This chip is not supported by X.org, the best you can get is 640x480 with 16 colors with the 'vga' driver as part of the X.Org distribution

=== Linux XFree86 driver ===
X6 was the last version to support this chip with the 'svga' driver.

==== ThinkPad LCD ====
Display on the internal LCD works as long as you set the monitor settings correct.

==== External VGA port ====
??

=== Linux kernel Framebuffer driver ===
??

=== ThinkPads this chip may be found in ===
* {{345C}}, {{345CS}}
* {{355}}
* {{360}}, {{360C}}, {{360Cs}}, {{360CE}}, {{360CSE}}, {{360P}}, {{360PE}}
* {{370C}}
* {{355C}}, {{355Cs}}
* {{510Cs}}
* {{750}}, {{750C}}, {{750Cs}}, {{750P}}
* {{755C}}, {{755Cs}}, {{755CE}}, {{755CSE}}, {{755CD}}, {{755CDV}}, {{755CV}}, {{755CX}}
* {{820}}, {{850}}

[[Category:Components]]

SMAPI support for Linux

2005-12-04T22:30:12Z

Micampe: typo

Talk:How to make use of Graphics Chips Power Management features

2005-12-02T13:11:49Z

Micampe: /* aticonfig and Xorg.0.log don't match */

Experimentally, it seems that [[rovclock]] determines the maximum frequency, and "DynamicClocks" tells the chip to a lower frequency when possible. They are thus complementary. --[[User:Thinker|Thinker]] 18:59, 27 Oct 2005 (CEST)

== show current power state with fglrx? ==

Switching power states using {{cmd|aticonfig|}} seems to work fine. Seems, because I can't really see in which state the ATI chip is currently in. Or can I?

--[[User:Spiney|spiney]] 14:40, 20 Nov 2005 (CET)
----

You can (destructively) check whether it's in a specific state by trying to switch to that state. If it's alredy there, it will give an error. If not, it will switch and (on my machine) cause a brief screen blink. Indeed, brilliant engineering.

--[[User:Thinker|Thinker]] 15:32, 20 Nov 2005 (CET)
----

== aticonfig and Xorg.0.log don't match ==
I was testing this PowerPlay business and I saw that aticonfig --lsp outputs:

core/mem [flags]
---------------
1: 105/122 MHz [low voltage]
2: 209/182 MHz [low voltage]
3: 297/230 MHz [default state]

But Xorg.0.log reports that the states are:
(II) fglrx(0): POWERplay version 3. 4 power states available:
(II) fglrx(0): 1. 297/230MHz @ 60Hz [enable load balancing]
(II) fglrx(0): 2. 105/122MHz @ 60Hz [low voltage, enable sleep]
(II) fglrx(0): 3. 250/230MHz @ 60Hz [thermal diode mode]
(II) fglrx(0): 4. 209/182MHz @ 60Hz [low voltage]

Am I the only one that think this is kind of odd? I'm using a R52 with a X300 card.
Omarkj

----

I can confirm I have the same values on the same hardware. Also, it seems rovclock can't read the correct speeds. It reads values well over 400MHz. --[[User:Micampe|Micampe]] 14:11, 2 Dec 2005 (CET)

Fan control scripts

2005-11-30T19:25:04Z

Micampe: fixed typo

==Fan enable/disable scripts==

===<tt>sh</tt> script example===

#!/bin/sh

MAXTEMP=50

while [ 1 ];
do
fan=no

for temp in `sed s/temperatures:// < /proc/acpi/ibm/thermal`
do
test $temp -gt $MAXTEMP && fan=yes
done

command='disable'
test "$fan" = "yes" && command='enable'
echo $command > /proc/acpi/ibm/fan

sleep 20
done

===<tt>sh</tt> script with more features===

#!/bin/sh

# fan control-script
#
# based upon ibm-acpi 0.11 (experimental=1 !)
#
# eliminates anoying "fan always on" in battery mode
# works with hysteresis (DELTA) so that always-turn-on/turn-off is avoided
# fan acivates at MAXTEMP and cools down CPU, GPU etc. to MAXTEMP-DELTA than the fan is turned off
# furthermore detects if AC is on and gives back fan control to default behaviour than
#
# one can change MAXTEMP and DELTA to individual values
# but take care of your THINKPAD don`t melt it!
#
# have fun!
# mk 05.05.05

MAXTEMP=51
DELTA=4

SWITCHTEMP=$MAXTEMP

#make sure the script doesn't leave the fan off on error
trap "echo enable > /proc/acpi/ibm/fan" EXIT

while [ 1 ];
do
for ac in `sed s/state:// < /proc/acpi/ac_adapter/AC/state`
do
if [ "$ac" = "off-line" ]; then
fan=no
for temp in `sed s/temperatures:// < /proc/acpi/ibm/thermal`
do
test $temp -gt $SWITCHTEMP && fan=yes
done

if [ "$fan" = "yes" ]; then
command='enable'
SWITCHTEMP=`expr $MAXTEMP - $DELTA`
else
SWITCHTEMP=$MAXTEMP
command='disable'
fi

else # ac-adapter on -> set fan control to standard behaviour
command='enable'
fi

echo $command > /proc/acpi/ibm/fan
sleep 15
done
done

===<tt>sh</tt> script with extra safety functionality===
ibm_acpi usually works well. But to rely on it completely, this script provides some extra safety functionality:
# It catches various signals and turns the fan on before it quits.
# It turns off the fan under very strict conditions, leaving it on when unexpected errors occur.

#!/bin/sh

# july 2005 Erik Groeneveld, erik@cq2.nl
# It makes sure the fan is on in case of errors
# and only turns it off when all temps are ok.

IBM_ACPI=/proc/acpi/ibm
THERMOMETER=$IBM_ACPI/thermal
FAN=$IBM_ACPI/fan
MAXTRIPPOINT=65
MINTRIPPOINT=60
TRIPPOINT=$MINTRIPPOINT

echo fancontrol: Thermometer: $THERMOMETER, Fan: $FAN
echo fancontrol: Current `cat $THERMOMETER`
echo fancontrol: Controlling temperatures between $MINTRIPPOINT and $MAXTRIPPOINT degrees.

# Make sure the fan is turned on when the script crashes or is killed
trap "echo enable > $FAN; exit 0" HUP KILL INT ABRT STOP QUIT SEGV TERM

while [ 1 ];
do
command=enable
temperatures=`sed s/temperatures:// < $THERMOMETER`
result=
for temp in $temperatures
do
test $temp -le $TRIPPOINT && result=$result.Ok
done
if [ "$result" = ".Ok.Ok.Ok.Ok.Ok.Ok.Ok.Ok" ]; then
command=disable
TRIPPOINT=$MAXTRIPPOINT
else
command=enable
TRIPPOINT=$MINTRIPPOINT
fi
echo $command > $FAN
# Temperature ramps up quickly, so pick this not too large:
sleep 5
done

==Variable speed control scripts==

While the above scripts only toggle the fan on and off, the following scripts also sets the fan speed according to sytem temperatures. In addition, they include a hack for preventing the annoying fan pulsing that occurs on some systems. Note that the fan levels, thresholds and anti-pulsing hacks are system-specific, so you may need to adjust them.

===<tt>bash</tt> script with fine control over fan speed===

The following requires only [[ibm-acpi]] 0.11 or higher (e.g., as found in kernel 2.6.14 and higher) with the <tt>experimental=1</tt> module parameter. It supports (optional) daemon mode and logging to syslog.

This scripts uses a different temperature range for each sensor, since they have different specs and thermal systems. For each sensor, a fan level is chosen based on the minimum and maximum temperatures configured for that sensor; then the actual fan level is set to the slowest that will satisfy all sensors. There are also some hysteresis features - see the script for the details. The method of controlling fan speed is documented [[Patch for controlling fan speed#Hardware specs|here]].

Current options:

Usage: ./tp-fancontrol [OPTION]...

Available options:
-s N shift up temperature thresholds by N degrees
(positive for quieter, negative for cooler)
-t test mode
-q quiet mode
-d daemon mode, go into background (implies -q)
-l log to syslog
-k kill daemon (ignores all but -p)
-p pid file location for daemon mode, default: /var/run/tp-fancontrol.pid

{{WARN|This script relies on undocumented hardware features and overrides nominal hardware behavior. It may thus cause arbitrary damage to your laptop or data. Watch your temperatures!}}
{{WARN|The list of temperature ranges used below is much more liberal than the rules used by the embedded controller firmware, and is derived mostly from anecdotal evidene, hunches and wishful thinking. It is also model-specific.}}

With no further ado, here is the script:

<pre>
#!/bin/bash

# tp-fancontrol 0.2.3 (http://thinkwiki.org/wiki/ACPI_fan_control_script)
# Provided under the GNU General Public License version 2 or later or
# the GNU Free Documentation License version 1.2 or later, at your option.
# See http://www.gnu.org/copyleft/gpl.html for the Warranty Disclaimer.

# This script dynamically controls fan speed on some ThinkPad models
# according to user-defined temperature thresholds. It implements its
# own decision algorithm, overriding the ThinkPad embedded
# controller. It also implements a workaround for the fan noise pulse
# experienced every few seconds on some ThinkPads.
#
# Run 'tp-fancontrol --help' for options.
#
# WARNING: This script relies on undocumented hardware features and
# overrides nominal hardware behavior. It may thus cause arbitrary
# damage to your laptop or data. Watch your temperatures!
#
# WARNING: The list of temperature ranges used below is much more liberal
# than the rules used by the embedded controller firmware, and is
# derived mostly from anecdotal evidence, hunches and wishful thinking.
# It is also model-specific.

# Temperature ranges, per sensor:
# (min temperature: when to step up from 0-th fan level,
# max temperature: when to step up to maximum fan level)
THRESHOLDS=( # Sensor ThinkPad model
# R51 T42 T43/p
# min max # ---------- ------- --- ----
50 70 # EC 0x78 CPU CPU CPU
47 60 # EC 0x79 miniPCI ? HDAPS through EC (under center left of miniPCI)
43 55 # EC 0x7A HDD ? ?
49 68 # EC 0x7B GPU GPU GPU
37 52 # EC 0x7C BAT BAT BAT (front left)
45 55 # EC 0x7D n/a n/a n/a
34 45 # EC 0x7E BAT BAT BAT (rear right)
45 55 # EC 0x7F n/a n/a n/a
45 55 # EC 0xC0 ? n/a ?
48 60 # EC 0xC1 ? n/a Southbridge under miniPCI?
50 65 # EC 0xC2 ? n/a Charging circuitry?
47 60 # HDAPS HDAPS HDAPS HDAPS direct access (under center left of miniPCI)
)

LEVELS=( 0 2 4 7) # Fan speed levels
ANTIPULSE=( 0 1 0 0) # Prevent fan pulsing noise at this level
# (reduces frequency of fan RPM updates)

OFF_THRESH_DELTA=2 # when gets this much cooler than 'min' above, may turn off fan
MIN_THRESH_SHIFT=0 # increase min thresholds by this much
MIN_WAIT=120 # minimum time (seconds) to spend in a given level before stepping down

IBM_ACPI=/proc/acpi/ibm
HDAPS_TEMP=/sys/bus/platform/drivers/hdaps/hdaps/temp1
LOGGER=/usr/bin/logger
INTERVAL=3
SETTLE_TIME=6
RESETTLE_TIME=300

PID_FILE=/var/run/tp-fancontrol.pid
VERBOSE=true
DRY_RUN=false
DAEMONIZE=false
AM_DAEMON=false
KILL_DAEMON=false
SYSLOG=false

usage() {
echo "
Usage: $0 [OPTION]...

Available options:
-s N shift up temperature thresholds by N degrees
(positive for quieter, negative for cooler)
-t test mode
-q quiet mode
-d daemon mode, go into background (implies -q)
-l log to syslog
-k kill daemon (ignores all but -p)
-p pid file location for daemon mode, default: $PID_FILE
"
exit 1;
}

while getopts 's:qtdlp:kh' OPT; do
case "$OPT" in
s) # shift thresholds
MIN_THRESH_SHIFT="$OPTARG"
;;
t) # test mode
DRY_RUN=true
;;
q) # quiet mode
VERBOSE=false
;;
d) # go into background and daemonize
DAEMONIZE=true
;;
l) # log to syslog
SYSLOG=true
;;
p) # different pidfile
PID_FILE="$OPTARG"
;;
k) # kill daemon
KILL_DAEMON=true
;;
h) # short help
usage
;;
\?) # error
usage
;;
esac
done
[ $OPTIND -gt $# ] || usage # no non-option args

# no logger found, no syslog capabilities
$SYSLOG && [ ! -x $LOGGER ] && SYSLOG=false

if $DRY_RUN; then
echo "$0: Dry run, will not change fan state."
VERBOSE=true
DAEMONIZE=false
fi

thermometer() { # output list of temperatures
# Base temperatures from ibm-acpi:
[ -r $IBM_ACPI/thermal ] || { echo "$0: Cannot read $IBM_ACPI/thermal" 2>&1 ; exit 1; }
read X Y < $IBM_ACPI/thermal
[ "$X" == "temperatures:" ] || { echo "$0: Bad temperatures: $X $Y" >&2; exit 1; }
echo -n "$Y ";
# Extended temperatures at EC offsets 0xC0 to 0xC2:
[ -r $IBM_ACPI/ecdump ] || { echo "$0: Cannot read $IBM_ACPI/ecdump" 2>&1; exit 1; }
perl -e 'm/^EC 0xc0: .(..) .(..) .(..) / and print hex($1)." ".hex($2)." ".hex($3)." " and exit 0 while <>; exit 1' < $IBM_ACPI/ecdump
# HDAPS temperature (optional):
[ -r $HDAPS_TEMP ] && echo -n "`cat $HDAPS_TEMP` "
return 0
}

speedometer() { # output fan speed RPM
sed -n 's/^speed:[ \t]*//p' $IBM_ACPI/fan
}

setlevel() { # set fan speed level
$DRY_RUN || echo 0x2F $1 > $IBM_ACPI/ecdump
}

getlevel() { # get fan speed level
perl -e 'm/^EC 0x20: .* (..)$/ and print $1 and exit 0 while <>; exit 1' < $IBM_ACPI/ecdump
}

cleanup() { # clean up after work
$AM_DAEMON && rm -f "$PID_FILE" 2> /dev/null
$SYSLOG && $LOGGER -t "`basename $0`[$$]" \
"Shutting down, switching to automatic fan control"
$DRY_RUN || echo enable > $IBM_ACPI/fan
}

floor_div() {
echo $(( (($1)+1000*($2))/($2) - 1000 ))
}

control_fan() {
# Enable the fan in default mode if anything goes wrong:
set -e -E -u
trap "cleanup; exit 2" HUP INT ABRT QUIT SEGV TERM
trap "cleanup" EXIT

IDX=0
START_TIME=0
MAX_IDX=$(( ${#LEVELS[@]} - 1 ))
SETTLE_LEFT=0
RESETTLE_LEFT=0
FIRST=true
$SYSLOG && $LOGGER -t "`basename $0`[$$]" "Starting dynamic fan control"

# Control loop:
while true; do
TEMPS=`thermometer`
$VERBOSE && SPEED=`speedometer`
$VERBOSE && ECLEVEL=`getlevel`
NOW=`date +%s`

# Calculate new level index by placing temperatures into Z-regions:
# Z >= 2*I means "must be at index I or higher"
# Z = 2*I+1 is hysteresis: "don't step down if currently at I+1"
# hence the Z-regions are, for d=(MAX-MIN)/(2*MAX_IDX-1) :
# Z=0:{-infty..MIN-d) Z=1:{MIN-d..MIN) Z=2:{MIN..MIN+d} Z=3:{MIN+d..MIN+2d} ... Z=2*MAX_IDX:{MAX-d, MAX}

MAX_Z=$(( IDX>0 ? ( NOW>START_TIME+MIN_WAIT ? 2*(IDX-1) : 2*IDX ) : 0 ))
SENSOR=0
Z_STR="$MAX_Z+"
TEMP_STR="";
for TEMP in $TEMPS; do
[ $((2*SENSOR+2)) -le ${#THRESHOLDS[@]} ] ||
{ echo "Too many sensors, not enough values in THRESHOLDS" 2>&1; exit 1; }
if [ $TEMP == -128 ]; then
Z='_'; TEMP='_' # inactive sensor
else
MIN=$((THRESHOLDS[SENSOR*2] + MIN_THRESH_SHIFT));
MAX=$((THRESHOLDS[SENSOR*2+1]))
if (( TEMP < MIN - OFF_THRESH_DELTA )); then
Z=0
else
Z=$(( `floor_div $(( (TEMP-MIN)*(2*MAX_IDX-2) )) $((MAX-MIN))` + 2 ))
fi
[ $MAX_Z -gt $Z ] || MAX_Z=$Z
fi
Z_STR="${Z_STR}${Z}"
TEMP_STR="${TEMP_STR}${TEMP} "
(( ++SENSOR ))
done
[ $SENSOR -gt 0 ] || { echo "No temperatures read" >&2; exit 1; }

(( (MAX_Z == 2*IDX-1) && ++MAX_Z )) # hysteresis
NEW_IDX=$(( MAX_Z/2 ))
[ $NEW_IDX -le $MAX_IDX ] || NEW_IDX=$MAX_IDX

# Transition
$FIRST && OLDLEVEL='?' || OLDLEVEL=${LEVELS[$IDX]}
NEWLEVEL=${LEVELS[$NEW_IDX]}
$VERBOSE && echo "L=$OLDLEVEL->$NEWLEVEL EC=$ECLEVEL RPM=`printf %4s $SPEED` T=($TEMP_STR) Z=$Z_STR"
if [ $OLDLEVEL != $NEWLEVEL ]; then
START_TIME=$NOW
$SYSLOG && $LOGGER -t "`basename $0`[$$]" "Changing fan level: $OLDLEVEL->$NEWLEVEL"
fi

setlevel $NEWLEVEL

sleep $INTERVAL

# If needed, apply anti-pulsing hack after a settle-down period (and occasionally re-settle):
if [ ${ANTIPULSE[${NEW_IDX}]} == 1 ]; then
if [ $NEWLEVEL != $OLDLEVEL -o $RESETTLE_LEFT -le 0 ]; then # start settling?
SETTLE_LEFT=$SETTLE_TIME
RESETTLE_LEFT=$RESETTLE_TIME
fi
if [ $SETTLE_LEFT -ge 0 ]; then
SETTLE_LEFT=$((SETTLE_LEFT-INTERVAL))
else
setlevel 0x40 # disengage briefly to fool embedded controller
sleep 0.5
RESETTLE_LEFT=$((RESETTLE_LEFT-INTERVAL))
fi
fi

IDX=$NEW_IDX
FIRST=false
done
}

if $KILL_DAEMON ; then
if [ -f "$PID_FILE" ]; then
set -e
DPID="`cat \"$PID_FILE\"`"
kill "$DPID"
rm "$PID_FILE"
$VERBOSE && echo "Killed process $DPID"
else
$VERBOSE && echo "Daemon not running."
exit 1
fi
elif $DAEMONIZE ; then
if [ -e "$PID_FILE" ]; then
echo "$0: File $PID_FILE already exists, refusing to run."
exit 1
else
AM_DAEMON=true VERBOSE=false control_fan 0<&- 1>&- 2>&- &
echo $! > "$PID_FILE"
exit 0
fi
else
[ -e "$PID_FILE" ] && echo "WARNING: daemon already running"
control_fan
fi
</pre>

The authors of the script ([[User:Thinker|Thinker]] and [[User:Spiney|Spiney]]) disclaim all warranty for this script, and makes it available the terms of the [http://www.gnu.org/copyleft/gpl.html GPL] version 2 or later, or at your option, the [http://www.gnu.org/copyleft/fdl.html GFDL].

===<tt>bash</tt> script with fine control over fan speed (requires kernel patch)===

The following is a simpler patch (without extra features like daemon mode and logging). It requires the [[patch for controlling fan speed]].

<pre>
#!/bin/bash

# This script dynamically controls fan speed on some ThinkPad models
# according to user-defined temperature thresholds. It implements its
# own decision algorithm, overriding the ThinkPad embedded
# controller. It also implements a workaround for the fan noise pulse
# experienced every few seconds on some ThinkPads.
#
# The script requires the ibm_acpi patch at
# http://thinkwiki.org/wiki/Patch_for_controlling_fan_speed
#
# WARNING: This script relies on undocumented hardware features and
# overrides nominal hardware behavior. It may thus cause arbitrary
# damage to your laptop or data. Watch your temperatures!
#
# This file is placed in the public domain and may be freely distributed.

LEVELS=( 0 2 4 7) # Fan speed levels
UP_TEMPS=( 52 60 68 ) # Speed increase trip points
DOWN_TEMPS=( 48 56 64 ) # Speed decrease trip points

ANTIPULSE=( 0 1 0 0) # Prevent fan pulsing noise at this level
# (this also prevents fan speed updates)

IBM_ACPI=/proc/acpi/ibm
FAN=$IBM_ACPI/fan
INTERVAL=3
VERBOSE=true
DRY_RUN=false

[[ "$1" == "-t" ]] && { DRY_RUN=true; echo "$0: Dry run, will not change fan state."; }

# Enable the fan in default mode if anything goes wrong:
set -e -E -u
$DRY_RUN || trap "echo enable > $FAN; exit 0" EXIT HUP INT ABRT QUIT SEGV TERM

thermometer() { # output list of temperatures
read X Y < $IBM_ACPI/thermal
[[ "$X" == "temperatures:" ]] || {
echo "$0: Bad temperatures: $X $Y" >&2
exit 1
}
echo "$Y";
}

speedometer() { # output fan speed
cat $FAN | sed '/^speed/!d; s/speed:[ \t]*//'
}

IDX=0
MAX_IDX=$(( ${#LEVELS[@]} - 1 ))
SETTLE=0

while true; do
TEMPS=`thermometer`
$VERBOSE && SPEED=`speedometer`

# Calculate new level
NEWIDX=$IDX
DOWN=$(( IDX > 0 ))
for TEMP in $TEMPS; do
# Increase speed as much as needed
while [[ $NEWIDX -lt $MAX_IDX ]] &&
[[ $TEMP -ge ${UP_TEMPS[$NEWIDX]} ]]; do
(( NEWIDX ++ ))
DOWN=0
done
# Allow decrease (by one index)?
if [[ $DOWN == 1 ]] &&
[[ $TEMP -gt ${DOWN_TEMPS[$(( IDX - 1 ))]} ]]; then
DOWN=0
fi
done
if [[ $DOWN == 1 ]]; then
NEWIDX=$(( IDX - 1 ))
fi

# Transition
OLDLEVEL=${LEVELS[$IDX]}
NEWLEVEL=${LEVELS[$NEWIDX]}
$VERBOSE && echo "tpfan: Temps: $TEMPS Fan: $SPEED Level: $OLDLEVEL->$NEWLEVEL"
$DRY_RUN || echo level $NEWLEVEL > $FAN

sleep $INTERVAL

# If needed, apply anti-pulsing hack after a settle-down period:
if [[ ${ANTIPULSE[${NEWIDX}]} == 1 ]]; then
if [[ $NEWLEVEL == $OLDLEVEL ]]; then
if [[ $SETTLE -ge 0 ]]; then
(( SETTLE -= INTERVAL ))
else
$DRY_RUN || echo level disengaged >> $FAN
sleep 0.5
fi
else
SETTLE=6
fi
fi

IDX=$NEWIDX
done
</pre>

The [[User:Thinker|author]] of the script disclaims all warranty for this script, and releases it to the public domain (meaning you may use it and further distribute it under any terms you wish, including incorporating it into other software).

==Init scripts==

===Init script example===

#! /bin/sh

N=/etc/init.d/fan

set -e

case "$1" in
start)
# make sure privileges don't persist across reboots
if [ -d /var/run/fan ] && [ "x`ls /var/run/fan`" != x ]
then
touch -t 198501010000 /var/run/fan/*
fi
fan.sh & # Script from above
;;
stop|reload|restart|force-reload)
killall fan.sh
echo enable > /proc/acpi/ibm/fan
;;
*)
echo "Usage: $N {start|stop|restart|force-reload}" >&2
exit 1
;;
esac

exit 0

===Init script example for gentoo===
Assume one of the above control scripts is /usr/sbin/ibm-fancontrold, for gentoo use the following init script in /etc/init.d/ibm-fancontrol.
Copy the script to /etc/init.d/ibm-fancontrol, then do

# rc-update add ibm-fancontrol default

This will add the init script to the default runlevel.

#!/sbin/runscript
# 2005 Gilbert Tiefengruber
# Distributed under the terms of the GNU General Public License v2
# IBM Fancontrol init script for IBM Thinkpad laptops (tested with R50)
# This init script was written for gentoo 2005.1, kernel 2.6.12
# You need the ibm_acpi kernel module version 0.11 or greater
# load the module with experimental=1 to enable the fan controls

depend() {
need localmount
}
checkconfig() {
if [ ! -e /proc/acpi/ibm/fan ]; then
eerror "The ibm_acpi module must be loaded with (experimental=1)"
return 1
fi
}
start() {
checkconfig || return 1
ebegin "Starting ibm-fancontrold"
start-stop-daemon --quiet -p /var/run/ibm-fancontrold.pid -m -b --start -a /usr/sbin/ibm-fancontrold
eend ${?}
}
stop() {
ebegin "Stopping ibm-fancontrold"
start-stop-daemon --stop --quiet -p /var/run/ibm-fancontrold.pid
eend ${?}
}

==Other==

===fanctrld===

[http://log.does-not-exist.org/archives/2005/08/13/2043_t_43_fan_control_daemon.html fanctrld] is a daemon (written in C) that controls the Thinkpad's fan. The basic approach is to monitor both temperature and fan speed. The fan is enabled when a certain temperature is exceeded, and disabled when the BIOS slows down the fan below a certain speed.

==See also==

* Shimodax's ThinkPad fan control tool for a Windows offers functionality similar to these scripts; see the [http://forum.thinkpads.com/viewtopic.php?t=17715 forum discussion] at thinkpads.com.
* Yury Polyanskiy has a [http://mailman.linux-thinkpad.org/pipermail/linux-thinkpad/2005-November/030697.html kernel patch] for automatic fan control in kernelspace (only enable/disable based on maximum temperature).

[[Category:Scripts]]

Help:Reading

2005-11-30T16:01:17Z

Micampe: reverted spam

{| width="100%"
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__
|style="vertical-align:top" |
This page is supposed to guide you in using [[ThinkWiki]]. It offers you strategies on how to find information here in case you need help about a specific topic or just want to know something about your ThinkPad or ThinkPads in general.
|}

==Generic starting points==
There are five generic starting points that can help you whatever your mission might be:
*You can start browsing on the [[ThinkWiki|ThinkWiki start page]]. We will try to keep all ThinkWiki pages accessable in a logical structure that branches out from there.
*You can always use the Search field on the left, enter some word designating what you are looking for, press the search button and hope that one of the search results will be helpful.
*From our [[:Category:Models|ThinkPad models overview]] you can pick your particular model page to get a list with all articles concerning that model.
*And on the [[:Category:Distributions|distributions]] page you can choose your distribution and find all pages containing information related to that distro.
*You can try browsing the [[:Category:ThinkWiki|Categories]].

==Finding help for a specific problem==
ThinkWiki most likely doesn't provide a single page covering exactly your problem. It rather offers you generic starting points where you can start your hunt for information that may give you clues to a solution. The most typical starting points for your solution hunt are:
*The [[Known Problems]] page list pages covering specific problems people have run into with partial or complete solutions to them.
*If you look for information on how to install a specific distro on a specific model, look at the [[Installation]] page.
*In case you have problems installing or configuring a special driver, look at the [[HOWTOs - Driver Installation|Driver installation HOWTO listing]].
*In case you need help or information about the preloaded system, backing it up or recovering it, look at the [[How to recover the preloaded OS|Preload Recovery page]].
*If you run into Power Management related problems, the [[How to make use of Power Management features|Power Management HOWTO]] should help.
There are several more HOWTO pages accessible from the [[ThinkWiki|ThinkWiki main page]]

==Finding information about a specific model==
There are two places to start for that:
*The [[:Category:Models|ThinkPad models overview]] page. It contains a list of all models known to the editors of ThinkWiki, each of them containing general information about that model as well as a list of all articles with information related to it. I.e. if you want to know about the ThinkPad X22, just click on the [[:Category:X22|X22]] page and you'll find all we know about it.
*The second place to look at is the [[Hardware Specifications]] page. Here you will find a list of model and type numbers, ordered by model. Just click on a type number and you'll find detailed specifications of exactly that type. In case your exact model-type number isn't there, look at one of the IBM provided PDF documents linked from that page.

==Finding information about ThinkPads in general==
If you are planning to buy a notebook and want to start with an overall impression of ThinkPads, try the following pages:
*The [[ThinkPad History]] gives a historic overview about the appearance of ThinkPads in chronological order, accompanied with some information about their specialties and features.
*The [[Thinkpad Technologies]] page lists several of the technologies found in various ThinkPads. Each single Technology page in turn holds a list of ThinkPads this featuring this technology.
*Look at the [[Components]] or [[:Category:Components|Components Category]] pages to find out about hardware used in ThinkPad computers.

==Finding information about your specific distribution==
As said above, the [[:Category:Distributions|distributions]] page holds a list of distributions you can find information about on ThinkWiki. Each of the single distribution pages listed there in turn contain a list of all articles with relevant information for that distribution.

==If you don't find what you are looking for==
Well, go figure - and let us know your findings here. ;-) Ok, more seriously, the [[Links]], [[Mailinglists]] and [[IRC]] pages list other sources of useful information. Also pay attention to the "External Sources" and "Related Links" sections found on almost every page. They usually contain a list of useful links to pages outside ThinkWiki. And of course, [http://www.google.org Google] is always your friend.

Good luck.

ATI Mobility Radeon X300

2005-11-30T11:19:10Z

Micampe: fixed typo

__NOTOC__
{| width="100%"
|style="vertical-align:top" |
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;">
=== ATI Mobility Radeon X300 ===
This is a ATI video adapter
=== Features ===
* Chipset: ATI M22
* PCI ID: 1002:5460
* PCI Express x16
* 32 or 64MB GDDR1 on-chip video memory
* "HyperMemory": can use system memory for graphics processing
* "PowerPlay 4.0" technology for dynamic engine clock, memory clock and core voltage, refresh rate reduction and thermal status reporting.
</div>
|style="vertical-align:top" |
|}

See [http://www.ati.com/products/radeonx300/specs.html specifications] from ATI, as well as the [http://www.ati.com/products/embedded/mobilityradeonx300/M22-CSP64_Product_Snapshot.pdf "snapshot" data sheet] (referes to the 32MB on-chip, 128MB "HyperMemory" version).

=== Linux driver ===
Use Driver "radeon" in the xorg.conf file - it works at least for xorg 6.8.2, maybe older versions too. Currently (as of xorg 6.8.2) this will only give you 2D-acceleration, though. To enable 3D acceleration as well you need to use the binary ATI driver [[fglrx]].

There is also an open source Radeon [http://r300.sf.net/ driver] with 3D acceleration support (merged into [http://dri.freedesktop.org here] recently), but it's still highly experimental and does not support all features.

==== ThinkPad LCD ====
Display on the internal LCD works as long as you set the monitor settings correct.

==== External VGA port ====
There are known problems. Both the <tt>radeon</tt> and [[fglrx]] drivers turn off the switching between internal and external port.

=====With the <tt>vesa</tt> driver=====
Using the "vesa" driver built into X.org, mode switching modes. However, this loses acceleration and some capabilities.

=====With the <tt>radeon</tt> drive=====
On-the-fly swiching doesn't work. To activate both ports in clone mode with a reasonable CRT refresh rate, use the following in {{path|/etc/X11/xorg.conf}}:

Section "Device"
Identifier "Videocard0"
VendorName "Videocard vendor"
BoardName "ATI Radeon Mobility X300"

Driver "radeon"
Option "DynamicClocks" "on"

Option "MergedFB" "on"
Option "MonitorLayout" "LVDS, CRT"
Option "CRT2Hsync" "50-75"
Option "CRT2VRefresh" "50-82"
EndSection

Note that without the <tt>MonitorLayout</tt> option, if the external monitor is connected when X starts then the LCD will be deactivated and you will need to restart X.

(Tested wth Fedora Core 4 on ThinkPad {{T43}}).

See also the related discussion about [[Additional options for the radeon driver]].

=====With the [[fglrx]] driver=====
On-the-fly switching doesn't work either. To use both ports, either have the monitor connected during X startup, or force activation of both ports by adding
Option "ForceMonitors" "lvds,crt1"
to the <tt>Device</tt> section in your {{path|/etc/X11/xorg.conf}}. Powering the CRT port consumes 400-500mW, regardless of whether a CRT is attached.

==== S-Video port (TV-out) ====

Works with the proprietary [[fglrx]] driver (as of version 8.19.10). To activate, add
Option "ForceMonitors" "lvds,tv"
to the <tt>Device</tt> section in your {{path|/etc/X11/xorg.conf}} and restart X.

==== DVI port ====
??

=== 3D acceleration ===
OpenGL 3D acceleration is proided by the proprietary [[fglrx]] driver (when DRI is enabled). Note that performance is affected by the power saving mode.

=== Linux kernel Framebuffer driver ===

radeonfb might cause problems with hardware acceleration under X on some systems, vesafb and vesafb-tng on the other hand has been reported to work just fine.

=== Clock rates, voltage and power===
{| border="1" cellspacing="0" cellpadding="2"
|+ Clock rates, voltages and power {{footnote|1}}
! Mode !! core freq !! memory freq !! voltage !! idle !! 3DMarks (Windows, 1600x1200, LCD only)
|-
| Performance || 300 || 230 MHz || 1.15V || 2.98 W || 8.28 W
|-
| Balanced || 183 || 210 MHz || 1.00V || 1.71 W || 3.88 W
|-
| Battery || 120 || 105 MHz || 1.00V || 1.61 W || 2.74 W
|}

{| border="1" cellspacing="0" cellpadding="2"
|+ ATI drivers for Windows {{footnote|2}} and [[fglrx]]
! Mode !! core freq !! memory freq
|-
| Performance || 297.00 || 229.50
|-
| Balanced || 209.25 || 182.25
|-
| Battery || 104.63 || 121.50
|}

Experimentally, the difference between the Performance and Battery settings under Linux with the <tt>radeon</tt> driver and <tt>DynamicClocks</tt> enabled is roughly 0.3W and 3-4 degrees in GPU temperature on a ThinkPad {{T43}}. Further frequency reduction leads to display flickering or corruption.

See [[How to make use of Graphics Chips Power Management features]] for details on how to control this using [[Rovclock]], [[How to make use of Graphics Chips Power Management features|<tt>DynamicClocks</tt> option to the <tt>radeon</tt> driver]] and or the [[fglrx]] driver.

Presently the lowest idle-mode power consumption is achieved using the proprietary [[fglrx]] driver and
# aticonfig --set-powerstate=1 --effective=now

=== ThinkPads this chip may be found in ===
* {{R52}}
* {{T43}}
* {{Z60m}}

{{footnotes|
#according to the [http://www.ati.com/products/embedded/mobilityradeonx300/M22-CSP64_Product_Snapshot.pdf "Snapshot" data sheet] (which refers to the 32MB on-chip, 128MB "HyperMemory" version)
#inspected using [http://www.pbus-167.com/chc.htm Notebook Hardware Control]
}}

[[Category:Components]]

ATI Mobility Radeon X300

2005-11-15T21:24:22Z

Micampe:

__NOTOC__
{| width="100%"
|style="vertical-align:top" |
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;">
=== ATI Mobility Radeon X300 ===
This is a ATI video adapter
=== Features ===
* Chipset: ATI M22
* PCI ID: 1002:5460
* PCI Express x16
* 32 or 64MB GDDR1 on-chip video memory
* "HyperMemory": can use system memory for graphics processing
* "PowerPlay 4.0" technology for dynamic engine cloc, memory clock and core voltage, refresh rate reduction and thermal status reporting.
</div>
|style="vertical-align:top" |
|}

See [http://www.ati.com/products/radeonx300/specs.html specifications] from ATI, as well as the [http://www.ati.com/products/embedded/mobilityradeonx300/M22-CSP64_Product_Snapshot.pdf "snapshot" data sheet] (referes to the 32MB on-chip, 128MB "HyperMemory" version).

=== Linux driver ===
Use Driver "radeon" in the xorg.conf file - it works at least for xorg 6.8.2, maybe older versions too. Currently (as of xorg 6.8.2) this will only give you 2D-acceleration, though. To enbable 3D acceleration as well you need to use the binary ATI driver [[fglrx]].

There is also an open source Radeon [http://r300.sf.net/ driver] with 3D acceleration support (merged into [http://dri.freedesktop.org here] recently), but it's still highly experimental and does not support all features.

==== ThinkPad LCD ====
Display on the internal LCD works as long as you set the monitor settings correct.

==== External VGA port ====
There are known problems. Both the <tt>radeon</tt> and [[fglrx]] drivers turn off the switching between internal and external port.

=====With the <tt>vesa</tt> driver=====
Using the "vesa" driver built into X.org, mode switching modes. However, this loses acceleration and some capabilities.

=====With the <tt>radeon</tt> drive=====
On-the-fly swiching doesn't work. To use both ports, start X without an external monitor, and then connect the external monitor. Both displays will be active, and cannot be switched off until you exit X. Note that if the external monitor is connected when X starts, the LCD will be deactivated and you will need to restart X. To have a reasonable refresh rate on the external monitor (the default is the LCD's 50Hz), use the following in {{path|/etc/X11/xorg.conf}}:

Section "Device"
Identifier "Videocard0"
VendorName "Videocard vendor"
BoardName "ATI Radeon Mobility X300"

Driver "radeon"
Option "DynamicClocks" "on"

Option "MergedFB" "on"
Option "CRT2Hsync" "50-75"
Option "CRT2VRefresh" "30-82"
EndSection

(Tested wth Fedora Core 4 on ThinkPad {{T43}}).

See also the related discussion about [[Additional options for the radeon driver]].

=====With the [[fglrx]] driver=====
On-the-fly switching doesn't work either. To use both ports, either have the monitor connected during X startup, or force activation of both ports by adding
Option "ForceMonitors" "lvds,crt1"
to the <tt>Device</tt> section in your {{path|/etc/X11/xorg.conf}}. Powering the CRT port consumes 400-500mW, regardless of whether a CRT is attached.

==== S-Video port (TV-out) ====

Works with the proprietary [[fglrx]] driver (as of version 8.19.10). To activate, add
Option "ForceMonitors" "lvds,tv"
to the <tt>Device</tt> section in your {{path|/etc/X11/xorg.conf}} and restart X.

==== DVI port ====
??

=== 3D acceleration ===
OpenGL 3D acceleration is proided by the proprietary [[fglrx]] driver. Note that the default power mode is low-performance (and high-power). To change to a faster mode, you can for example run
# aticonfig --set-powerstate=2 --effective=now
(see [[How to make use of Graphics Chips Power Management features]]).

=== Linux kernel Framebuffer driver ===

radeonfb might cause problems with hardware acceleration under X on some systems, vesafb and vesafb-tng on the other hand has been reported to work just fine.

=== Clock rates, voltage and power===
{| border="1" cellspacing="0" cellpadding="2"
|+ Clock rates, voltages and power {{footnote|1}}
! Mode !! core freq !! memory freq !! voltage !! idle !! 3DMarks (Windows, 1600x1200, LCD only)
|-
| Performance || 300 || 230 MHz || 1.15V || 2.98 W || 8.28 W
|-
| Balanced || 183 || 210 MHz || 1.00V || 1.71 W || 3.88 W
|-
| Battery || 120 || 105 MHz || 1.00V || 1.61 W || 2.74 W
|}

{| border="1" cellspacing="0" cellpadding="2"
|+ ATI driver for Windows {{footnote|2}}
! Mode !! core freq !! memory freq
|-
| Performance || 297.00 || 229.50
|-
| Balanced || 209.25 || 182.25
|-
| Battery || 104.63 || 121.50
|}

Experimentally, the difference between the Performance and Battery settings under Linux with <tt>DynamicClocks</tt> enabled is roughly 0.3W and 3-4 degrees in GPU temperature on a ThinkPad {{T43}}. Further frequency reduction leads to display flickering or corruption.

Clock rates can be changed through [[Rovclock]], and are also affected by the [[How to make use of Graphics Chips Power Management features|<tt>DynamicClocks</tt> option to the <tt>radeon</tt> driver]].

=== ThinkPads this chip may be found in ===
* {{R52}}
* {{T43}}
* {{Z60m}}

{{footnotes|
#according to the [http://www.ati.com/products/embedded/mobilityradeonx300/M22-CSP64_Product_Snapshot.pdf "Snapshot" data sheet] (which refers to the 32MB on-chip, 128MB "HyperMemory" version)
#inspected using [http://www.pbus-167.com/chc.htm Notebook Hardware Control]
}}

[[Category:Components]]

Talk:Fan control scripts

2005-11-12T07:19:06Z

Micampe:

How to build your own Ultrabay drive

2005-11-08T23:49:34Z

Micampe: /* The Limitations */

{{WARN|No warranty of any kind is given for the correctness of the following instructions. Following them can damage your machine. Proceed at your own risk.}}
{{NOTE|This article is written with UltraBay 2000 drives in mind. But should be appliable for UltraSlimBay and other kinds of UltraBay devices as well.}}
Optical [[UltraBay]] drives like CD-ROM and DVD drives or burners are usually a bit more expensive than their non-IBM counterparts. Additionally more modern technologies are not available for discontinued [[UltraBay]] standards. A solution to this annoyance is to take a standard slim form factor notebook drive and turn it into an UltraBay drive yourself.

==The Basics==
The "big secret" about UltraBay drives is that basically they are just standard slim form factor notebook drives equipped with an UltraBay frame. This frame is just a mechanical addition with an integrated connector adapter.

As curious people found, the inner connector of an UltraBay frame is nothing more than a standard interface for such drives. Hence, it is generally possible to disassemble an old UltraBay drive and attach the frame to a newer or better one.

There are, however, some things to consider...

==The Limitations==
Even though these slim form factor drives seem to have a standard form factor at first look, it turns out that there are marginal mechanical differences. This makes it hard if at all possible to know beforehand if the UltraBay frame from your old drive will perfectly fit onto the new one. The fact is that different UltraBay drives even for the same UltraBay standard have frames with different mechanical characteristics. Small differences can sometimes be adjusted by modifying parts of the frame, but this is of course not the nicest solution.

The most varying part is the Blending, which is usually not compatible even among drives of the same manufacturer. The position of the eject button, the drive LED, the emergency eject hole and the way the blending is attached to the drive all vary a lot. Do precise research before you buy anything. One solution here is to keep the original blending of the drive, since the UltraBay blending is independent from the rest of the frame. The disadvantage is an optical one: the standard blendings are usually flat whereas the UltraBay blendings usually are a bit thicker at the top and thinner at the bottom. Also, for some UltraBay standards you would have to cut out the lower right edge of the blending, since the standard drive blendings are usually rectangle shaped.

==UltraBay 2000==
The UltraBay 2000 frame consists of four parts: Front bezel, left wing, right wing and the back plate containing the connector interface.

The left and right parts are attached with little screws in holes which are at standardised positions and should usually fit among all drives. However, the actual drives show tiny variations in width, which are leveraged by the left and right parts. Hence these can be a bit thicker or thinner (fractions of 1mm). Putting a somewhat wide frame part onto a somewhat wide drive might result in an UltraBay drive that doesn't fit into the bay at all because it's just a tiny little bit too wide. This can be dealt with e.g. by sanding one of the side frame parts, but it's better if all components fit correctly in the first place. Also, the side frames have hatches fitting into the holes in the back part. Among frames these hatches vary in thickness and length and hence, again, might not fit easily. Again, they can be adjusted by cutting them a bit.

{| border=1 cellspacing=0 cellpadding=2
|+ UltraBay 2000 drives and compatible alternative drives
|-
! UltraBay drive !! IBM Part-Nr. !! actual drive !! compatible drive !! needed steps to make fitting
|-
| 24x CD-ROM drive || ... || TEAC CD-224E || ... || ...
|-
| 8x DVD drive || 27L3447 || Matsushita SR-8175-M || ... || ...
|-
| 8x DVD drive || 08K9648 || Matsushita SR-8176-M || ... || ...
|}

Maintenance

2005-11-05T00:29:09Z

Micampe: reverted vandalism

{| width="100%"
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__
|style="vertical-align:top" |
Here you can find general hints about keeping your ThinkPad in good shape. Look at your [[:Category:Models|models category page]] for IBMs official maintenance guide for that model.
|}
==Battery Treatment==
{| border=1 cellspacing=0 cellpadding=2 style="vertical-align:top;"
|+Battery life expanding guide
|- style="background:#efefef;white-space:nowrap;"
! style="background:#ffdead;" | Battery Type !! NiCd !! NiMH !! Lithium ion
|- style="vertical-align:top;"
! style="background:#ffdead;" | General
|
*always do complete discharge/charge cycles
*avoid exposing the battery (or notebook) to excessive heat
|
*always do complete discharge/charge cycles
*avoid exposing the battery (or notebook) to excessive heat
|
*never completely discharge the battery, partial dis-/recharges are better
*remove battery when on AC
*avoid exposing the battery (or notebook) to excessive heat
|- style="vertical-align:top;"
! style="background:#ffdead;" | Charging
|
*discharge before charging
|
*discharge before charging
|
*avoid charging if battery is nearly full
*keep notebook off while charging
*fully discharge battery every 30 or so charges to recalibrate fuel guage
|- style="vertical-align:top;"
! style="background:#ffdead;" | Storage
|
*almost discharged
*cool and dry
|
*almost discharged
*cool and dry
|
*never fully charged or discharged, ideally at about 40%
*cool and dry, but do not freeze them
|}

{{HINT|Newer Thinkpads have software that lets you set charge thresholds. If you use your Laptop at a desk, use this software to keep your batteries in good condition. '''[as this is a site geared toward Linux, it would be helpful to know how one can accomplish this in Linux]'''}}

===The problem with 600 series batteries===
ThinkPad 600 power management causes batteries to die before they should. Read more about this on the [[Problem with Thinkpad 600 batteries|associated problem page]].

===Reviving Batteries===
Some people experience sudden drops in their batteries capacity.

A way to get these batteries back to full capacity is to run the "Battery Rundown" function of IBMs "PC Doctor for DOS".
The program is downloadable from IBMs support site as three floppy disk images. For those who do not have a floppy, David Smith prepared a [http://www.mypchelp.com/~dsmith/ibmutil/ibm_t22_pcdiag.iso bootable CD image] from the T22 floppy images.

===External Sources===
* [http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=ibm&lndocid=MIGR-50944 IBM Support - Extending battery life]
* [http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=ibm&lndocid=MIGR-51038 IBM Support - Battery troubleshooting]
* [http://www.pc.ibm.com/ww/thinkpad/batterylife/ IBM Benchmark]
* [http://batteryuniversity.com Battery University]
* [http://www.batteryuniversity.com/parttwo-34.htm BatteryUniversitys info about prolonging lithium ion batteries]
* [http://www.buchmann.ca/Chap10-page6.asp prolonging lithium ion batteries in Buchmanns Battery FAQ]

==Cleaning the Display==
If you discover markings that look like originating from the TrackPoint or keyboard, or for information on how to avoid these, look at [[Problem with key and trackpoint markings on the display|this page]].

===External Sources===
* [http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=ibm&lndocid=MIGR-4A2P54 IBM Support - LCD care and cleaning instructions]
* [http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=ibm&lndocid=MIGR-52190 IBM Support - System cleaning instructions]

==Dealing with spilling accidents==
#Don't panic.
#Don't flip or tilt the computer to prevent the liquid from spreading all over the inside of the case.
#Shut down the OS and turn off the power:
##Unplug the computer.
##Remove the battery.
#Tilt the computer so that everything that leaked into the case can flow out the same way.
#Allow the computer to dry before switching it on again.
#For minor accidents this might already be sufficient. For major flooding you should either bring the computer to a dealer who knows how to open and clean it from inside. Or you can read the Hardware Maintenance Manual, open, clean, and dry the computer yourself.

See also [http://www.moneysense.ca/spending/technology/columnist.jsp?content=986628 Act quickly, carefully if you spill on laptops] on MoneySense.ca

==Harddisk Backup==
*[[How to copy a Linux installation]]
*[[How to copy a Windows installation]]
===External Sources===
*[http://gamma.nic.fi/~point/win2copy.htm Guide on copying Windows 2000/XP to another partition]

==Recovering BIOS passwords==
Password recovery procedure for IBM ThinkPads
using R24RF08 and IBMpass

'''1. Introduction.'''

As you probably know, IBM ThinkPad uses a small eeprom (ATMEL 24RF08) to store different OEM
issues like serial number, UUID, etc. The supervisor password (SVP) is stored also into this little chip.
So, anybody should figure that he needs to read the eeprom in order to find the password string. The first problem is that 24RF08 is not an ordinary eeprom. The second is that the password is written in a special scan code.
To read properly you need a software (and an interface) specially designed for this eeprom.
This software is R24RF08 (eeprom reader) and IBMpass (password revealer) disponible at www.allservice.ro . Diagrams are included in the reader kit

'''2. Locating the eeprom. Soldering.'''

No need to unsolder the 24RF08 eeprom, just solder 3 wires to SDA, SCL and GND pins of the
eeprom. There are two eeprom layouts (see interface schematics described bellow), orresponding to 8 pin or 14 pin eeproms. Locate the eeprom first according to your model (E.g. T20-23 and T30 have the eeprom underneath TP, and can be accessed by removing the RAM modules cover, no need to dismantle the laptop.) and solder the wires using a soldering iron with a fine tip. Also, you can use 0.15 -0.20 mm enamel coated wires or similar small diameter insulated wires. These wires will be connected later to the interface.
Tip: You can use clips to connect the wires or you can solder on the PCB traces leading to the
eeprom pins. Once again, be careful and double, triple check the soldering if necessary till you are positively sure you have done the right job.

'''3. Choose and build the interface.'''

Since version 2.0, R24RF08 and W24RF08(eeprom writer) are compatible with a wide range of eeprom programmers. By default, both programs set the COM port signals to use direct logic level to access I2C bus. We provide here 2 schematics that are relevant for direct logic signals and for inverse logic signals (simple-i2cprog.pdf and driven-i2cprog.pdf). Also, depending of the interface you build, you can invert the logics for SDA-In, SDA-Out, and SCL COM port signals by some command line parameters described later in this document.
a) The file simple-i2cprog.pdf contains the schematic diagram of a simple interface (known as SIPROG)based on 2 zeners and 2 resistors. This is a classic, easy to build circuit and works with soldered or unsoldered eeproms. The purpose of the 2 zeners is to convert RS232 levels (+/- 5V) to TTL levels, needed by the eeprom. It uses direct logic signals to I2C eeprom and is powered by the COM port. However, this interface works with in-system eeproms but is dependant on COM port current and eeprom bus impedance. R24RF08 works natively with this circuit, no need to change the lines signals with command line parameters. This circuit works pretty well with almost all Thinkpads series.
b) The second interface is described in driven-i2cprog.pdf. The circuit uses MAX 232 as a RS232 to TTL driver and its main purpose is to work with soldered eeproms. The advantage of MAX232 is the TTL outputs that are more reliable and more powerful when work with soldered, in-system eeproms (dependency free from the COM port current). Due of the internal inverters of MAX232 the interface responds to an inverse signal logic level. R24RF08 needs /x, /d, /i switches to be specified in the command line.
What these switches mean:
/x - invert serial clock, also known as SCL;
/d - invert serial data output, also known as SDA-Out;
/i - invert serial data input, also known as SDA-In.
All those can be used in any combination to meet any interface specification.

'''4. How is it working:'''

Prepare your technician PC by connecting the interface to the COM1 port (donâ€™t connect the wires to eeprom yet). Turn on the ThinkPad and press F1 to enter BIOS Setup. When you are prompted for the password and thereâ€™s no other activity like HDD access or so, connect the wires (GND first!, SDA, SCL) to the corresponding wires from the interface (attached before to COM1) and execute R24RF08:

-for SI-PROG interface (as described in 3.a above):
r24rf08.exe <filename.ext>. where filename.ext is the file where eeprom content will be stored.
Example: r24rf08 mytp.bin

-for MAX232 driven I2C interface (as described in 3.b above):
r24rf08.exe <filename.ext> /x /d /i. where /x /d /i are command line parameters (switches) for this kind of interface.
Example: r24rf08 mytp2.bin /x/d /i

Use exactly the instructed switches to avoid possible damages to your eeprom data!
The file should be created in the same folder. Finally, disconnect the wires (GND last!) and turn off the ThinkPad by pressing on/off switch.

'''5. Reveal the password.'''

Now, you have the .bin file but you need to dump in scan code to retrieve the password. IBMpass 2.0 Lite is a free tool that will do the job. Just open the eeprom dump youâ€™ve created before and search for 0x330, 0x340 lines. The password is located on 0x338 (and 0x340 depending on model) in scan code. For 24C01 eeproms the password is located at 0x38, 0x40. If the password won't work for the very first time then your eeprom may use newer IBM scancodes. In this case switch to alternate scan codes to find it. For those who want quick answers the recommended version is IBMpass 1.1. Usage for IBMpass 1.1 (command line only):

ibmpass mytp.bin â€“ use â€œ/aâ€ switch to see in alternate scan code if needed:
ibmpass mytp.bin /a

For some old models like 570 or 770Z you need to execute the eeprom patcher first. This will reset the read protection on the password offset. To do that just execute patcher.exe before the reading operation, without rebooting the laptop:

-for SI-PROG:
patcher.exe , then immediately
r24rf08.exe <filename.ext>

-for Driven-I2C (Max232) you must insert the switches:
patcher.exe /x /d /i, then immediately
r24rf08.exe <filename.ext> /x /d /i

W24RF08, the writer version, has included the complete APP reset operation you donâ€™t need to use patcher.

Remember, use 3 wires from the interface and 3 wires from eeprom! Connect them after your
ThinkPad is powered and disconnect them right after you read the content, before you switch off the laptop.

===External Sources===
* [http://www.allservice.ro R24RF08 & IBMpass author's webpage.]
* [http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=ibm&lndocid=MIGR-59377 IBM Support - Lost or forgotten password]

User:Micampe

2005-11-05T00:27:48Z

Micampe:

==Machines==
* My first ThinkPad [[:Category:R52|R52 1846-4CG]]

Talk:Problems with SATA and Linux

2005-11-03T15:50:19Z

Micampe: what are the advantages of SATA?

regarding the "BIOS error 2010 on user-installed hard disk":
the text says that corruption occurs if you use a harddisk without the specific ibm bios. would be interesting if it is possible to fix this problem in the kernel so that you can use any disk and the kernel doesn't use specific ATA commands which are known to cause problems.

in the tabook i didn't find any specification of the SATA bridge. it would be interesting:
1) what type it is
2) if it is fixed on the mainboard or if it is possible to solder in a new one

----

Another interesting question is whether these ThinkPads can be hacked to accept a real SATA system disk, by bypassing the SATA-to-PATA bridge (this would probably involve some soldering and cutting). If the BIOS can also handle that then it may come in handy, since some new high-capacity 2.5" disks have only SATA versions.
--[[User:Thinker|Thinker]] 02:56, 8 Oct 2005 (CEST)

----

'''Z series'''

Since the Z series uses a SATA controller and disk, without the bridge, would it be possible to make SATA ATAPI support as a module that you could load only when using the optical drive? Then, for everyday use, the experimental options of PATA and ATAPI with ata_piix would not be needed, moving you one step further in the direction of stability.

----

I have an R52 with Ubuntu Breezy and no problems with SATA (I personally asked the developers to include the needed patches).

However, I'd like to know wheter there are any advantages with this configuration. Future proof? Power saving? Speed?

Anybody cares to comment?

-- [[User:Micampe|Michele]]