ThinkWiki - User contributions [en]

Talk:HDAPS

2010-04-21T18:15:25Z

Lunatico:

== Smackpad and Compiz ==

There are a few references to scripts that will switch the workspace when you tap the laptop on the side. I googled for a while and all I could find was pretty old stuff.

A few of the links I found are:

[http://wiki.compiz.org/Plugins/Smackpad Compiz Smackpad Plugin] This one looks very interesting but how do you install it?

[http://www.eugen-feller.de/?p=12 Compiz Smackpad] I could not clone the software.

[http://blog.micampe.it/articles/2006/06/04/here-comes-the-smackpad Here comes the smackpad] No luck here either.

Etc...

So, has anyone got this working recently? How?

Thanks! --[[User:Lunatico|Lunatico]] 18:15, 21 April 2010 (UTC)

== Careful with Gnome HDAPS applet ==

This applet polls /sys/block/sda/device/unload_heads and loads the corresponding icon from disk '''every 10th of a second'''. I'd like to talk to the upstream developer and fix that, but I wouldn't recommend its usage meanwhile. I guess we should warn users in the wiki page? --[[User:Berto|Berto]] 14:40, 3 April 2010 (UTC)

--[[User:Lunatico|Lunatico]] 17:45, 21 April 2010 (UTC) Can you elaborate more on this? I'm using the gnome applet and haven't had any perceivable issues.

== Question regarding the example udev rule ? ==
The example udev rule is as follows.
* KERNEL=="event[0-9]*", ATTRS{phys}=="hdaps/input1", ATTRS{modalias}=="input:b0019v1014p5054e4801-*", SYMLINK+="input/hdaps/accelerometer-event"

Where is the '''b0019v1014p5054e4801''' being taken from?

It is from "udevinfo --attribute-walk --name /dev/input/event9" (only with the tp_smapi module)

== Where can one find the recent hdapsd version mentioned in the article ? ==
The article mentions "New interface (requires hdapsd dated 2008-10-04 or newer)" without giving any clue about where one can find such a version, I looked in repositories, google and elsewhere in this very site and found an outdated http://www.dresco.co.uk/hdaps/ , as a newcomer here, it eludes me completely. [[User:Bugmenot1|Bugmenot1]] 21:38, 28 November 2008 (CET)

:I had the same problem, I think I found it via [[How_to_protect_the_harddisk_through_APS#Manual_compilation_from_source]], it links to a mailing list post at [http://article.gmane.org/gmane.linux.drivers.hdaps.devel/1040] which has an attached source file at [http://cache.gmane.org//gmane/linux/drivers/hdaps/devel/1040-001.bin], this can be compiled easily with ''gcc -o hdapsd hdapsd.c''. Why this is not released cleanly on the original homepage eludes me as well... --[[User:Centic|Centic]] 12:34, 30 November 2008 (CET)

== "Reduced Power" hdapsd Consuming More Power ==

There is a link to a "reduced power" version of hdapsd, which is supposed to lower the number of timer interrupts (thereby reducing the power consumed by the daemon). From my experiments (using powertop), however, this program requires about twice as many interrupts to operate in "low power" mode as it does using the (older) sysfs interface. It also consumes enough CPU cycles to force my CPU back on periodically, consuming more power. Has anybody else had this experience?

--[[User:Mbsullivan|Mbsullivan]] 05:41, 24 August 2007 (UTC)

:Well, not really. With tp_smapi 0.31 and older hdapsd I had wakeups from hdapsd and from the hdaps module, now powertop only shows about 50wakeups from hdapsd (which are really from the module, but this is a bug in powertop, it tells who first called a function, not whose function it is [it's a function in the module code]). So I get a lower power consumption with the newer pair of tpsmapi and hdapsd
:--[[User:Zhenech|Zhenech]] 07:26, 24 August 2007 (UTC)

== I hawe a problem ==

I tray to start working my IBM x40 with hdaps function but I can't make it right.

The main problem is in a not hanging variables when I read
/sys/devices/platform/hdaps/position

==I also have this problem!==
Hi, I also have this problem that on my X40 the device/platform/hdaps/position does not give the right response. It is simply constant (128,1).
Does anyone have a clue? I use the suse kernel 2.6.16.13-4-default from suse10.1. the hdaps sources in that kernel are the same as in the original kernel.
thanks in advance,
----

Does the HDAPS sensor work under Windows (as observed from actual disk parking, or the graphical animation)?
Also, try loading [[tp_smapi]], it includes some patches for the hdaps driver. Does it help?

--[[User:Thinker|Thinker]] 16:45, 8 June 2006 (CEST)
----

HI Again,
HDAPS does work under windows. When I had windows running and then reboot the machine, hdaps is running under suse10.1 also. If I, however, turn off the machine and restart it, then, hdaps does *not* work anymore.
I remember that with suse 10.0 and the separate module, hdaps did work.
HDAPS now works with tp_smapi as suggested above.
Still, where does the problem derive from?

----

The hdaps in the vanilla kernel has some bugs (i.e., in doesn't talk to the hardware correctly) which tp_smapi fixes. Looks like you've hit one of these.

--[[User:Thinker|Thinker]] 18:05, 12 June 2006 (CEST)
----

==laptop acpi problem with hdaps==
 UPDATE: the problem seems fixed in the version 0.21 
<s>
My my both IBM T42/T43 laptops freezes time to times with the follow:

kernel 2.6.16/sata patch 
hdaps build as a module from the kernel.
tp_smapi 0.20/hdapsd

The freez is quite common then I access CD-ROM,but it also might freez without touching anything. 
After the freez keyboard doesn't work or priting some character,power button doesn't work, however mouse might continue to work. 
KDE battery systray shows discarchged batteries. 
Still under investigation that cases the problem. 
The related software:
khdapsmon 0.1.2 
ibm-acpi build-in as a module from the kernel(for ksensors)
modified ksensors without lm_sensors with a patch
http://bugs.gentoo.org/show_bug.cgi?id=116661

--noname 00:25, 13 June 2006 (CEST)Anton

----

You're the 2nd one reporting this. The fact you can reproduce it on two machines may be very helpful! Are these machines configured identically? Do they run the same software? Can you send your kernel .config, and precise kernel version + patches, to the e-mail address in the tp_smapi README? Please specify which hdaps or tp_smapi -related applications you're typically running.

BTW, if you have [[swsusp]] or [[Software Suspend 2]] installed, you can do a suspend-to-disk cycle to recover from the hang.

--[[User:Thinker|Thinker]] 11:53, 13 June 2006 (CEST)
----

I also have the follow
[[Problems_with_SATA_and_Linux#No_DMA_on_DVD_drive]].
So I switched cdrom driver from IDE to ATA and it fixed the problem.
However HDAPS has stared to freez a machine if I shake it then HDD is active.
The issue might be not related to ACPI but I'll log it here for now.

I'll send configs. Thank you.
ps. 0.21 is out so let me try the new version.
--noname 08:34, 22 June 2006 (CEST)Anton
</s>

== hdaps and /sys ==

Hey Fellas,

I've just upgraded from 2.6.15.2, where the patches all dropped in ok and all was well, to 2.6.17.6, where hdaps is built into the kernel.
the hdapsd daemon referenced on thinkwiki looks in /sys/block/<drive>/queue/protect to get started.
The default drivers that come with 2.6.17.6 for hdaps apparently dont put anything in /queue there, so there is no 'protect' directory.
Has anyone else experienced this? I'd love to get my drive protection back :)
ON THE UPSIDE! - the Ricoh card reader in my z60m came to life, and I can read sd cards (but not sony memory sticks, oddly enough)
Any input would be awesome!
dan@itkinetix.com

----

You need an extra kernel patch for "protect". Please read the page more carefully.

--[[User:Thinker|Thinker]] 00:24, 22 July 2006 (CEST)
----

== Gnome HDAPS-Applet and the new interface ==

I just installed my first linux kernel with the new hdaps disk protection interface. Since the file that controls the (un)parking of the disk heads has changed with this interface, you have to edit the GNOME HDAPS applet source before compiling to make it work. Simply replace the lines 
 
<nowiki>#define SYSFS_PROTECT_FILE_HDA "/sys/block/hda/queue/protect"</nowiki> 
<nowiki>#define SYSFS_PROTECT_FILE_SDA "/sys/block/sda/queue/protect"</nowiki> 
 
with these: 
 
<nowiki>#define SYSFS_PROTECT_FILE_HDA "/sys/block/hda/device/unload_heads"</nowiki> 
<nowiki>#define SYSFS_PROTECT_FILE_SDA "/sys/block/sda/device/unload_heads"</nowiki> 
 
Then proceed with the instructions in the included INSTALL file. 
 
Another hint: On Ubuntu 8.10, install the hdapsd package, then compile the new version of hdapsd and replace the binary in /usr/sbin. Afterwards edit the /etc/init.d/hdapsd file so it looks for the new interface. Otherwise it will never start hdapsd bcause it's looking for the /sys/block/<device>/queue/protect file which simply doesn't exist. You may want to use the init script I posted at https://bugs.launchpad.net/ubuntu/+source/hdapsd/+bug/303915/comments/3 
And don't forget that udev-rule to create the symlink hdapsd needs to work!

Kind regards, 
--[[User:Gollo|Gollo]] 20:15, 18 December 2008 (CET)

== Older discussion ==

So, this is in the stable kernel now, but what userspace program do we need to actually park the heads?
--[[User:MrStaticVoid|MrStaticVoid]] 01:26, 30 Oct 2005 (CEST)
----
Yes the hdaps driver is in the 2.6.14 kernel, but support to park the heads quickly and freeze the disk queue (to prevent the heads from getting un-parked) is not. There is some disagreement into how that should be implemented.

In other words, the hdaps driver for the moment is rather useless, unless you want to use it to play games.

--[[User:Tonko|Tonko]] 02:10, 30 Oct 2005 (CEST)

----
I head rumours that you can make SDL handle this like a joystick, e.g. for playing Neverball. Can anyone confirm or deny that? Thanx --[[User:Nomeata|Nomeata]] 01:16, 16 Nov 2005 (CET)

Yes it is possible to use it as a joystick, as Tonko allready mentioned.
/dev/input/jsX modprobe joydev

Ozi

Thanks, I didn't have the joydev module. Rebuilding... --[[User:129.13.186.1|129.13.186.1]] 15:30, 16 Nov 2005 (CET)

----
Yeah, it's a pretty good party trick - set up the HDAPS joystick as xmame input. You can play Ms. Pac-man by tilting your laptop to make pac-man navigate the maze. You can imagine that the pac-man "rolls" downhill, just like those old wooden marble-puzzles that you see around. Heh, can actually clear a level or two.

Marble madness was strangely unsatisfying though, and just didn't work well (probably due to the diagonal nature of the screen in that game).

--[[User:gsmenden|gsmenden]] 20:10, 13 Jan 2006 (CEST)

----
Anyone got the queue freezing patch running on 2.6.16? I'm going to try to manually merge it but didn't want to duplicate someone else's work.

--[[User:Ajbarr|Ajbarr]] 19:12, 22 March 2006 (CET)

Talk:HDAPS

2010-04-21T17:45:37Z

Lunatico: /* Careful with Gnome HDAPS applet */

== Careful with Gnome HDAPS applet ==

This applet polls /sys/block/sda/device/unload_heads and loads the corresponding icon from disk '''every 10th of a second'''. I'd like to talk to the upstream developer and fix that, but I wouldn't recommend its usage meanwhile. I guess we should warn users in the wiki page? --[[User:Berto|Berto]] 14:40, 3 April 2010 (UTC)

--[[User:Lunatico|Lunatico]] 17:45, 21 April 2010 (UTC) Can you elaborate more on this? I'm using the gnome applet and haven't had any perceivable issues.

== Question regarding the example udev rule ? ==
The example udev rule is as follows.
* KERNEL=="event[0-9]*", ATTRS{phys}=="hdaps/input1", ATTRS{modalias}=="input:b0019v1014p5054e4801-*", SYMLINK+="input/hdaps/accelerometer-event"

Where is the '''b0019v1014p5054e4801''' being taken from?

It is from "udevinfo --attribute-walk --name /dev/input/event9" (only with the tp_smapi module)

== Where can one find the recent hdapsd version mentioned in the article ? ==
The article mentions "New interface (requires hdapsd dated 2008-10-04 or newer)" without giving any clue about where one can find such a version, I looked in repositories, google and elsewhere in this very site and found an outdated http://www.dresco.co.uk/hdaps/ , as a newcomer here, it eludes me completely. [[User:Bugmenot1|Bugmenot1]] 21:38, 28 November 2008 (CET)

:I had the same problem, I think I found it via [[How_to_protect_the_harddisk_through_APS#Manual_compilation_from_source]], it links to a mailing list post at [http://article.gmane.org/gmane.linux.drivers.hdaps.devel/1040] which has an attached source file at [http://cache.gmane.org//gmane/linux/drivers/hdaps/devel/1040-001.bin], this can be compiled easily with ''gcc -o hdapsd hdapsd.c''. Why this is not released cleanly on the original homepage eludes me as well... --[[User:Centic|Centic]] 12:34, 30 November 2008 (CET)

== "Reduced Power" hdapsd Consuming More Power ==

There is a link to a "reduced power" version of hdapsd, which is supposed to lower the number of timer interrupts (thereby reducing the power consumed by the daemon). From my experiments (using powertop), however, this program requires about twice as many interrupts to operate in "low power" mode as it does using the (older) sysfs interface. It also consumes enough CPU cycles to force my CPU back on periodically, consuming more power. Has anybody else had this experience?

--[[User:Mbsullivan|Mbsullivan]] 05:41, 24 August 2007 (UTC)

:Well, not really. With tp_smapi 0.31 and older hdapsd I had wakeups from hdapsd and from the hdaps module, now powertop only shows about 50wakeups from hdapsd (which are really from the module, but this is a bug in powertop, it tells who first called a function, not whose function it is [it's a function in the module code]). So I get a lower power consumption with the newer pair of tpsmapi and hdapsd
:--[[User:Zhenech|Zhenech]] 07:26, 24 August 2007 (UTC)

== I hawe a problem ==

I tray to start working my IBM x40 with hdaps function but I can't make it right.

The main problem is in a not hanging variables when I read
/sys/devices/platform/hdaps/position

==I also have this problem!==
Hi, I also have this problem that on my X40 the device/platform/hdaps/position does not give the right response. It is simply constant (128,1).
Does anyone have a clue? I use the suse kernel 2.6.16.13-4-default from suse10.1. the hdaps sources in that kernel are the same as in the original kernel.
thanks in advance,
----

Does the HDAPS sensor work under Windows (as observed from actual disk parking, or the graphical animation)?
Also, try loading [[tp_smapi]], it includes some patches for the hdaps driver. Does it help?

--[[User:Thinker|Thinker]] 16:45, 8 June 2006 (CEST)
----

HI Again,
HDAPS does work under windows. When I had windows running and then reboot the machine, hdaps is running under suse10.1 also. If I, however, turn off the machine and restart it, then, hdaps does *not* work anymore.
I remember that with suse 10.0 and the separate module, hdaps did work.
HDAPS now works with tp_smapi as suggested above.
Still, where does the problem derive from?

----

The hdaps in the vanilla kernel has some bugs (i.e., in doesn't talk to the hardware correctly) which tp_smapi fixes. Looks like you've hit one of these.

--[[User:Thinker|Thinker]] 18:05, 12 June 2006 (CEST)
----

==laptop acpi problem with hdaps==
 UPDATE: the problem seems fixed in the version 0.21 
<s>
My my both IBM T42/T43 laptops freezes time to times with the follow:

kernel 2.6.16/sata patch 
hdaps build as a module from the kernel.
tp_smapi 0.20/hdapsd

The freez is quite common then I access CD-ROM,but it also might freez without touching anything. 
After the freez keyboard doesn't work or priting some character,power button doesn't work, however mouse might continue to work. 
KDE battery systray shows discarchged batteries. 
Still under investigation that cases the problem. 
The related software:
khdapsmon 0.1.2 
ibm-acpi build-in as a module from the kernel(for ksensors)
modified ksensors without lm_sensors with a patch
http://bugs.gentoo.org/show_bug.cgi?id=116661

--noname 00:25, 13 June 2006 (CEST)Anton

----

You're the 2nd one reporting this. The fact you can reproduce it on two machines may be very helpful! Are these machines configured identically? Do they run the same software? Can you send your kernel .config, and precise kernel version + patches, to the e-mail address in the tp_smapi README? Please specify which hdaps or tp_smapi -related applications you're typically running.

BTW, if you have [[swsusp]] or [[Software Suspend 2]] installed, you can do a suspend-to-disk cycle to recover from the hang.

--[[User:Thinker|Thinker]] 11:53, 13 June 2006 (CEST)
----

I also have the follow
[[Problems_with_SATA_and_Linux#No_DMA_on_DVD_drive]].
So I switched cdrom driver from IDE to ATA and it fixed the problem.
However HDAPS has stared to freez a machine if I shake it then HDD is active.
The issue might be not related to ACPI but I'll log it here for now.

I'll send configs. Thank you.
ps. 0.21 is out so let me try the new version.
--noname 08:34, 22 June 2006 (CEST)Anton
</s>

== hdaps and /sys ==

Hey Fellas,

I've just upgraded from 2.6.15.2, where the patches all dropped in ok and all was well, to 2.6.17.6, where hdaps is built into the kernel.
the hdapsd daemon referenced on thinkwiki looks in /sys/block/<drive>/queue/protect to get started.
The default drivers that come with 2.6.17.6 for hdaps apparently dont put anything in /queue there, so there is no 'protect' directory.
Has anyone else experienced this? I'd love to get my drive protection back :)
ON THE UPSIDE! - the Ricoh card reader in my z60m came to life, and I can read sd cards (but not sony memory sticks, oddly enough)
Any input would be awesome!
dan@itkinetix.com

----

You need an extra kernel patch for "protect". Please read the page more carefully.

--[[User:Thinker|Thinker]] 00:24, 22 July 2006 (CEST)
----

== Gnome HDAPS-Applet and the new interface ==

I just installed my first linux kernel with the new hdaps disk protection interface. Since the file that controls the (un)parking of the disk heads has changed with this interface, you have to edit the GNOME HDAPS applet source before compiling to make it work. Simply replace the lines 
 
<nowiki>#define SYSFS_PROTECT_FILE_HDA "/sys/block/hda/queue/protect"</nowiki> 
<nowiki>#define SYSFS_PROTECT_FILE_SDA "/sys/block/sda/queue/protect"</nowiki> 
 
with these: 
 
<nowiki>#define SYSFS_PROTECT_FILE_HDA "/sys/block/hda/device/unload_heads"</nowiki> 
<nowiki>#define SYSFS_PROTECT_FILE_SDA "/sys/block/sda/device/unload_heads"</nowiki> 
 
Then proceed with the instructions in the included INSTALL file. 
 
Another hint: On Ubuntu 8.10, install the hdapsd package, then compile the new version of hdapsd and replace the binary in /usr/sbin. Afterwards edit the /etc/init.d/hdapsd file so it looks for the new interface. Otherwise it will never start hdapsd bcause it's looking for the /sys/block/<device>/queue/protect file which simply doesn't exist. You may want to use the init script I posted at https://bugs.launchpad.net/ubuntu/+source/hdapsd/+bug/303915/comments/3 
And don't forget that udev-rule to create the symlink hdapsd needs to work!

Kind regards, 
--[[User:Gollo|Gollo]] 20:15, 18 December 2008 (CET)

== Older discussion ==

So, this is in the stable kernel now, but what userspace program do we need to actually park the heads?
--[[User:MrStaticVoid|MrStaticVoid]] 01:26, 30 Oct 2005 (CEST)
----
Yes the hdaps driver is in the 2.6.14 kernel, but support to park the heads quickly and freeze the disk queue (to prevent the heads from getting un-parked) is not. There is some disagreement into how that should be implemented.

In other words, the hdaps driver for the moment is rather useless, unless you want to use it to play games.

--[[User:Tonko|Tonko]] 02:10, 30 Oct 2005 (CEST)

----
I head rumours that you can make SDL handle this like a joystick, e.g. for playing Neverball. Can anyone confirm or deny that? Thanx --[[User:Nomeata|Nomeata]] 01:16, 16 Nov 2005 (CET)

Yes it is possible to use it as a joystick, as Tonko allready mentioned.
/dev/input/jsX modprobe joydev

Ozi

Thanks, I didn't have the joydev module. Rebuilding... --[[User:129.13.186.1|129.13.186.1]] 15:30, 16 Nov 2005 (CET)

----
Yeah, it's a pretty good party trick - set up the HDAPS joystick as xmame input. You can play Ms. Pac-man by tilting your laptop to make pac-man navigate the maze. You can imagine that the pac-man "rolls" downhill, just like those old wooden marble-puzzles that you see around. Heh, can actually clear a level or two.

Marble madness was strangely unsatisfying though, and just didn't work well (probably due to the diagonal nature of the screen in that game).

--[[User:gsmenden|gsmenden]] 20:10, 13 Jan 2006 (CEST)

----
Anyone got the queue freezing patch running on 2.6.16? I'm going to try to manually merge it but didn't want to duplicate someone else's work.

--[[User:Ajbarr|Ajbarr]] 19:12, 22 March 2006 (CET)

Install Ubuntu Intrepid Ibex on a T61p

2009-04-03T14:35:25Z

Lunatico: /* Kernel Panic (System freezes and Caps lock blinks) */

=What works out of the box?=
*Wireless (Intel 3945ABG or 4965AGN)
**Only tested G mode
*Wired LAN
*Video (VESA)
**Hardware Drivers panel offers to install nVIDIA proprietary drivers on first boot.
*Touchpoint and Trackpad
**Including scroll at the right side of the pad by default.
**Middle-button scrolling does NOT work (fix below)
*Optical drive
**Optiarc AD-7910A works fine with Brasero disc burning
***Tested: CD-R, DVD+R
*Sound card
*SD/MMC Memory card reader (Ricoh)
**Only tested SD (non-HC) cards.
*Control buttons/Hotkeys
**Volume control buttons
**Screen brightness control
**Thinklight control
**WLAN/BT/OFF toggle
**Media player control
**fingerprint reader does NOT work (fix below)
*Some ACPI features
**Battery status, power graphs and history
**Lid states and events
**Only tested with a single 6-cell battery
*ACPI features
** Suspend to RAM
** Suspend to Disk (Hibernate) FINALLY!! Be patient, though.
** STR and STD work even with full disk encryption (DM-crypt + LVM)!

=Getting the hardware to work=
==Display/Video==
Installing the proprietary NVidia drivers is highly recommended, EVEN IF you won't use 3D acceleration, because the open source nv driver will drain your battery much faster since it does not support PowerMizer at all. Practically, this means that the GPU will constantly run at full speed, thus consuming ~12 Watts more than it would otherwise (which is a LOT of power for a laptop).

The first time you boot Ubuntu, you should get an alert asking if you want to install the binary driver. If not, it can be installed from the Hardware Drivers panel at

System --> Administration --> Hardware Drivers.

You will have a choice between the 173 and 177 version of the driver (Note: if you want to have better 2D performance without breaking suspend/resume, you will have to manually install the 180.25 driver manually as it is not included in the official Intrepid repo).
*pro:
**Version 177 is recommended because it will provide Suspend to disk functionality, whereas v173 will not.
*con:
**version 177 causes a log out bug that is addressed below.
**version 177 might show some issues like terminal output not updating in some very weird cases (which I did not see in v173, this seems to have something to do with powermizer as well ...)
*Early version of the 180 drivers break the suspension/resume, however 180.25(beta) driver has fixed this issue as well as improved 2D performance in X. As of Jan 29, 2009, the 180 series drivers have been added to the official repository under the name nvidia-glx-180. The 'intrepid-updates' repository has to be enabled via
System --> Administration --> Software Sources --> Updates

to download the drivers. The 180.11 version does not seem to have any suspend / hibernate issues.

Once the proprietary drivers are installed, the "NVidia X Server Settings" program will be available in System --> Administration.

===Version 177 logout/X restart fix===
There is a known issue in the v177 proprietary NVidia driver - See Launchpad bug [http://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-177/+bug/258357 258357]. Once you install the v177 driver, logging out or restarting X will cease to work, though suspend to RAM/Disk will continue to function.

The work around is as follows:
* In /etc/gdm/gdm.conf , increase the value for GdmXserverTimeout to about 60. When logging out or restarting X, X will hang for ~35 seconds. By increasing the value from its default, GDM will give X more time before it assumes X is faulty.

===Choppy Compiz animations===
NVidia's PowerMizer feature will slow down the GPU when "inactive" even on AC power.

The NVidia driver does not report the correct refresh rate of the display to Compiz, resulting in choppy animations and effects. To fix this, install the <code>compizconfig-settings-manager</code> package, then go to System --> Preferences --> Advanced Desktop Effects Settings (also might be called CompizConfig Settings Manager). Click on General Options, go to the Display Settings tab, uncheck the Detect Refresh rate box and drag the Refresh Rate slider to 60. Also, check the Sync To VBlank box. This will improve the smoothness of the window animations significantly if you're sensitive to the choppy animations.

Compiz animations can also be choppy due to NVidia's PowerMizer feature, which slows down the GPU to conserve power when it is not in use. This works well for 3D games which constantly use 3D acceleration, but poorly for Compiz which uses the GPU in small bursts. It seems that the interval of the PowerMizer is way too long and is not speeding up when using in bursts. Fortunately, the situation seems to have improved in version 177 of the NVidia driver. To workaround this problem, I made a couple of shell scripts which keep the GPU at its highest speed while running on AC power. The first one is named "powermizer-loop" and does most of the work:

#!/bin/sh

while true; do

powerstate=`cat /proc/acpi/ac_adapter/AC/state | awk '{print $2}'`

if [ $powerstate = "on-line" ]; then
nvidia-settings -q all > /dev/null
fi
sleep 25;
done

The second is named "powermizer-off" and starts up powermizer-loop when I log in, ensuring that only one copy runs at a time:

#!/bin/sh

killall powermizer-loop
~/powermizer-loop &

I put both of these scripts in my home directory and made them executable by doing:

chmod a+x powermizer-loop powermizer-off

Then to make powermizer-off run on login, I opened System --> Preferences --> Sessions, clicked on Add, and entered the command to run the script, i.e. "/home/<user>/powermizer-off".

Of course, performance still suffers when running on battery, but hopefully NVidia will fix this problem in a future version of their driver.

=== EDID misdetection ===

EDID (Extended Display Identification Data) might be misdetected for your display, which reduces the number of resolutions available in the NVidia X Server Settings application. (For example, I was unable to set my laptop's screen to 1024x768 for use with a projector during a presentation.) If you encounter this problem, add the following lines to /etc/X11/xorg.conf in the "Screen" section:

Option "UseEdidFreqs" "FALSE"
Option "HorizSync" "40-70"

The 40-70 values are just an example. They seem to work well with my 1680x1050 display. You should put the values of your display there. On a 1920x1200 display, making this change prevents the display from coming on when X starts.

A better but more complicated way would be using Phoenix EDID Designer to dump and fix the EDID data and then setup the Nvidia driver so it will use the customized EDID data, as described at [http://myricci.com/index.php?option=com_content&task=view&id=36]

==Microphone/Sound In==
Might need to be turned on in the mixer. See [[Install Ubuntu Hardy Heron on a T61p#Internal Microphone/Microphone Input Jack]]

==Front radio kill switch==
When killing Wireless LAN with the killswitch at the front, you won't be able to get WLAN back up after switching back. See Launchpad bugs [http://bugs.launchpad.net/ubuntu/+source/hal/+bug/289286 289286] and [http://bugs.launchpad.net/ubuntu/+source/linux-ubuntu-modules-2.6.24/+bug/193970 193970] and the [https://wiki.ubuntu.com/IntrepidReleaseNotes#Cannot%20reactivate%20Intel%203945/4965%20wireless%20if%20booting%20with%20killswitch%20enabled Release Notes] on the Ubuntu Wiki.

This will be solved in intrepid-updates eventually.

For now there are a few ways to bring the interface back up (choose one):
* Right click the network manager icon in the tray, uncheck Enable Wireless, then check it again does the trick (at least for me)
* {{cmdroot|ip l s wlan0 up}}
* {{cmdroot|modprobe -r iwl3945 && modprobe iwl3945}}
* reboot
* suspend and resume

== Middle-button Scrolling ==
Xorg.conf is not used to configure mice and keyboards anymore, but evdev is. This makes the configuration of middle-click scrolling a little bit different than previous versions of Ubuntu.

[http://mvogt.wordpress.com/2008/08/15/xorg-evdev-and-emulatewheel/ Michael Vogt described] how to get middle-click scrolling to work again in Intrepid.

{{cmduser| sudo gedit /etc/hal/fdi/policy/mouse-wheel.fdi}}

Paste and save the following code, which will give vertical wheel emulation only:
<match key="info.product" string="TPPS/2 IBM TrackPoint">
<merge key="input.x11_options.EmulateWheel" type="string">true</merge>
<merge key="input.x11_options.EmulateWheelButton" type="string">2</merge>
<merge key="input.x11_options.ZAxsisMapping" type="string">4 5</merge>
<merge key="input.x11_options.Emulate3Buttons" type="string">true</merge>
</match>
There is [http://psung.blogspot.com/2008/09/scrolling-with-thinkpads-trackpoint-in.html another method] to get horizontal scrolling as well, but this is not confirmed to work.

source:
*[[Installing_Ubuntu_8.10_%28Intrepid_Ibex%29_on_a_ThinkPad_T61#Emulate_Wheel_.28Middle-click_scrolling.29| Installing Ubuntu 8.10 (Intrepid Ibex) on a ThinkPad T61 - Emulate Wheel (Middle-click scrolling)]]

==Fingerprint Reader==

The [http://thinkfinger.sourceforge.net Thinkfinger] package allows you to swipe a finger in most places where you would have to type your password. This works with sudo, gksudo and on the login page and with a little fix also for the screen saver. Also, you are still required to type your user name on the login screen.

0) Set up the third party repository (optional but recommended!)

due to this [https://bugs.launchpad.net/ubuntu/+source/thinkfinger/+bug/256429 Bug #256429: Carriage-return required after finger scan] you need to press the return key after you swipe your finger with the current version of the kernel and the packages in ubuntu. The bug is caused by the fact that it does not recognize the fingerprint reader 100% correctly ([https://bugs.launchpad.net/ubuntu/+source/thinkfinger/+bug/256429/comments/29 Description of the root cause]) , as a temporary workaround there is a special package repository.

The packages present in ubuntu intrepid will work but you need to press enter after you swipe your finger.

Click System -> administration -> software sources
go to the tab "third-party software" and click Add ...

Enter in the popup window:

deb http://ppa.launchpad.net/jon-oberheide/ubuntu intrepid main

Click Add source, it will ask to refresh the package list, click reload.

1) Install the following packages:

{{cmduser| sudo apt-get install thinkfinger-tools libpam-thinkfinger libthinkfinger0}}

2) For your user:

{{cmduser| sudo tf-tool --acquire && sudo tf-tool --verify}}

A completed fingerprint setup should look something like this:

frank@Laptop:~$ sudo tf-tool --acquire && sudo tf-tool --verify

ThinkFinger 0.3 (http://thinkfinger.sourceforge.net/)
Copyright (C) 2006, 2007 Timo Hoenig <thoenig@suse.de>

Initializing... done.
Please swipe your finger (successful swipes 3/3, failed swipes: 0)... done.
Storing data (/tmp/test.bir)... done.

ThinkFinger 0.3 (http://thinkfinger.sourceforge.net/)
Copyright (C) 2006, 2007 Timo Hoenig <thoenig@suse.de>

Initializing... done.
Please swipe your finger (successful swipes 1/1, failed swipes: 0)... done.
Result: Fingerprint does match.
frank@CLaptop:~$

This will store your fingerprint information in /home/$USERNAME/.thinkfinger.bir

You should do this step for each user who wants to use the fingerprint reader

3) Enable use of reader for authentication:

{{cmduser| sudo gedit /etc/pam.d/common-auth}}

add
auth sufficient pam_thinkfinger.so
before the line which contains pam_unix.so and add
try_first_pass
to the end of the line containing pam_unix.so.

So it should look something like this:
...
auth sufficient pam_thinkfinger.so
auth [success=1 default=ignore] pam_unix.so nullok_secure try_first_pass
...

4) Check uinput kernel module:

{{cmduser|lsmod | grep uinput}}
If the output starts with uinput, then you're done.
If you don't get any output, then it needs to be started and set to start on boot.

Start uinput:

{{cmduser|sudo modprobe uinput}}

Start on boot:

{{cmduser|sudo gedit /etc/modules}}

make sure there is a line like this or add it at the bottom:
uinput

5) Enabling thinkfinger for gnome-screensaver

*create this file:
{{cmduser|sudo gedit /etc/udev/rules.d/60-thinkfinger.rules}}
with this contents:
#
# udev rules file for the thinkfinger fingerprint scanner
# gives access to the fingerprint reader to those in the "fingerprint" group
#
# Taken from:
# http://www.thinkwiki.org/wiki/Install_Ubuntu_Intrepid_Ibex_on_a_T61p#Fingerprint_Reader
# which was taken and modified from:
# http://www.thinkwiki.org/wiki/How_to_enable_the_fingerprint_reader_with_ThinkFinger
# http://article.gmane.org/gmane.linux.drivers.thinkfinger/329

# SGS Thomson Microelectronics Fingerprint Reader
SYSFS{idVendor}=="0483", SYSFS{idProduct}=="2016", SYMLINK+="input/thinkfinger-%k", MODE="0660", GROUP="fingerprint"

# the also-needed uinput device
KERNEL=="uinput", MODE="0660", GROUP="fingerprint"

*Make the group:
{{cmduser|sudo groupadd fingerprint}}
*per user:
{{cmduser|sudo gpasswd -a $USERNAME fingerprint && sudo chown $USERNAME:root /home/$USERNAME/.thinkfinger.bir }}

Reboot your laptop and you should be ready to swipe!

Sources:
* [[Install_Ubuntu_Gutsy_Gibbon_on_a_T61p#Fingerprint_Reader| Install Ubuntu Gutsy Gibbon on a T61p]]
* [https://bugs.launchpad.net/ubuntu/+source/thinkfinger/+bug/256429 Bug #256429: Carriage-return required after finger scan] & [https://bugs.launchpad.net/ubuntu/+source/thinkfinger/+bug/256429/comments/21 Solution for the bug in the comments]
* [https://launchpad.net/~jon-oberheide/+archive Repository for the third party fix] credits to [https://launchpad.net/~jon-oberheide Jon Oberheide]
* [[How_to_enable_the_fingerprint_reader_with_ThinkFinger| General page about Fingerprint reader with thinkfinger]] & [[How_to_enable_the_fingerprint_reader_with_ThinkFinger#xscreensaver.2Fgnome-screensaver| Specific gnome-screensaver section]]

==Hard Drive Active Protection System (APS ~ HDAPS)==
Please add to this section

Some interesting links:
* [[Active_Protection_System| Description of APS]]
* [[How_to_protect_the_harddisk_through_APS| How to protect the harddisk through APS]]
* [[Tp_smapi| tp_smapi kernel modules]]

=Other Problems=
== Resume Disables WLAN ==
On power up CDMA WLAN module is enabled, if user suspense and resumes it is turned off - no known fix.
Additionally fn-F5 turns off bluetooth but no option to turn off WLAN using function keys. This is problem is on the 6459CTO.

== Resume Requests WIFI Network Key ==
On resume Network Manager request the wifi network key several times before connecting to network. This has been noted on a 6459CTO laptop and no known fix is available. Currently with this problem it takes several minutes to regain network access after resume.

== Black Screen on Resume ==
On the 6459CTO with default 8.10 install suspend did not work. Enabling the proposed updates to be installed to your system might fix this issue. To enable the proposed updates go to the 'Software Sources' - tab 'Updates' in System -> Administration. Tick the 'Proposed updates (intrepid-updates)' checkbox, close 'Software Sources' to reload the package lists. Then, check for updates with the software updater (there should be some), update and reboot afterwards.

== Wireless not working after resume (Atheros) ==
After resuming from suspend, I am unable to reconnect to my wireless network. Network Manager asks me for my password over and over again but never succeeds in connecting. I'm using the Thinkpad (Atheros) A/B/G wireless card.

To fix this problem, I followed the instructions listed at https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/275692. Specifically, I created a file called /etc/pm/config.d/01-modules and put the following line in it:

SUSPEND_MODULES="ath_pci"

== Brightness control on battery power ==
By default, when unplugging the AC power while the system is running, the brightness of the display goes down even when you have set not to in the Power Management settings and you are not able to reach a brightness level as high as possible when connected to AC power. This is not a software setting or GNOME bug, but a BIOS setting. In the BIOS you can find a brightness setting in the Power section. Set it to high for normal, expected behavior. You can let the GNOME Power Manager still lower the brightness, but you will be able to increase it when needed.

== Kernel Panic (System freezes and Caps lock blinks) ==
When you are connected via Wireless and using it a lot some times you computer just freezes? This is caused by a bug on the wireless card drivers for the Intel Corporation PRO/Wireless 4965 AG or AGN.
To fix you need newer drivers from the backport modules:

sudo apt-get install linux-backports-modules-intrepid

--[[User:Lunatico|Lunatico]] 14:34, 3 April 2009 (UTC)

=Software Install=
==Adobe Flash==
Adobe has plug-ins direct for 32 bit version for x64 download the libflashplayer.so file from here:
http://labs.adobe.com/downloads/flashplayer10.html
Then copy to the mozilla plugins directory
sudo cp libflashplayer.so /usr/lib/firefox-addons/plugins/

=Other Information=
== Saving power ==
Some nice information on power saving you can find at

http://www.lesswatts.org

A tool that allows you to test most tips and tricks to reduce power is powertop, you can install it using

{{cmduser|sudo apt-get install powertop}}

and run it with:

{{cmduser|sudo powertop}}

For more information see http://www.lesswatts.org/projects/powertop/
== Battery control by tp_smapi ==
You need to load a kernel module first:
sudo modprobe tp_smapi

Now, you will be able to have significantly more control over your battery charging via /sys/devices/platform/smapi.

For example, you could set a threshold value of 90% for charging, preventing the battery from charging all the way in exchange for a reduction in the loss of battery capacity that occurs after multiple cycles.
echo "90" | sudo tee -a /sys/devices/platform/smapi/BAT0/stop_charge_thresh
(by default this was set to 86% on my laptop)

View the number of charge cycles your battery has had in its lifetime:
cat /sys/devices/platform/smapi/BAT0/cycle_count

While AC connected, force discharging of your battery:
echo "1" | sudo tee -a /sys/devices/platform/smapi/BAT0/force_discharge

For convenience, you could load the kernel module at boot time by adding it to /etc/modules.
echo "tp_smapi" | sudo tee -a /etc/modules

If you have an Ultrabay battery, you might want to place this [http://forum.thinkpads.com/viewtopic.php?p=433463#p433463 script] into <code>/etc/crontab</code> to keep the Ultrabay battery from being completely discharged to 0%, which permanently damages the battery.
# rolls to BAT0 when remaining capacity on BAT1 is less than 20%. Change .2 if wanted. Swap BAT0 and BAT1 if tp_smapi thinks the ultrabay is BAT0.
awk '{if (/remaining capacity/) left=$3; if (/last full capacity/) full=$4} END {if ((left/full) < .2) system("echo 1 > /sys/devices/platform/smapi/BAT0/force_discharge")}' /proc/acpi/battery/BAT1/*
Remember the script needs root in order to write to the files in <code>/sys/devices/platform/smapi/BAT{0,1}/</code>.

= Compared to Hardy (8.04) =
Why upgrade your T61p to Intrepid or why not? (Specific for T61p)
== Improvements ==
*Ricoh SD card reader now reads read-only SD card. (Tested with Adata 150X 2GB SD card)
*Newer Wireless LAN drivers. For Intel cards this results in working LED, more sensitive reception, increased stability of connections and some 802.1x bugfixes.
*Out-of-the-box Suspend to RAM functionality (also faster resume). Not on 6459, (see above)
*Working but slow Suspend to Disk functionality.

== Bugs and Regressions ==
*Hard radio killswitch (at the front) cannot bring WLAN back up after killing it. (workaround available)
*X hangs for approx. 35 seconds when restarting or logging out. (workaround available)
*Atheros WLAN not working after resume from Suspend to RAM (but a workaround is available; [[#Wireless_not_working_after_resume_.28Atheros.29|see above]]).

[[Category:T61p]]
[[Category:Ubuntu]]
[[Category:Ubuntu 8.10]]

Install Ubuntu Intrepid Ibex on a T61p

2009-04-03T14:34:26Z

Lunatico: /* Kernel Panic (System freezes and Caps lock blinks) */

=What works out of the box?=
*Wireless (Intel 3945ABG or 4965AGN)
**Only tested G mode
*Wired LAN
*Video (VESA)
**Hardware Drivers panel offers to install nVIDIA proprietary drivers on first boot.
*Touchpoint and Trackpad
**Including scroll at the right side of the pad by default.
**Middle-button scrolling does NOT work (fix below)
*Optical drive
**Optiarc AD-7910A works fine with Brasero disc burning
***Tested: CD-R, DVD+R
*Sound card
*SD/MMC Memory card reader (Ricoh)
**Only tested SD (non-HC) cards.
*Control buttons/Hotkeys
**Volume control buttons
**Screen brightness control
**Thinklight control
**WLAN/BT/OFF toggle
**Media player control
**fingerprint reader does NOT work (fix below)
*Some ACPI features
**Battery status, power graphs and history
**Lid states and events
**Only tested with a single 6-cell battery
*ACPI features
** Suspend to RAM
** Suspend to Disk (Hibernate) FINALLY!! Be patient, though.
** STR and STD work even with full disk encryption (DM-crypt + LVM)!

=Getting the hardware to work=
==Display/Video==
Installing the proprietary NVidia drivers is highly recommended, EVEN IF you won't use 3D acceleration, because the open source nv driver will drain your battery much faster since it does not support PowerMizer at all. Practically, this means that the GPU will constantly run at full speed, thus consuming ~12 Watts more than it would otherwise (which is a LOT of power for a laptop).

The first time you boot Ubuntu, you should get an alert asking if you want to install the binary driver. If not, it can be installed from the Hardware Drivers panel at

System --> Administration --> Hardware Drivers.

You will have a choice between the 173 and 177 version of the driver (Note: if you want to have better 2D performance without breaking suspend/resume, you will have to manually install the 180.25 driver manually as it is not included in the official Intrepid repo).
*pro:
**Version 177 is recommended because it will provide Suspend to disk functionality, whereas v173 will not.
*con:
**version 177 causes a log out bug that is addressed below.
**version 177 might show some issues like terminal output not updating in some very weird cases (which I did not see in v173, this seems to have something to do with powermizer as well ...)
*Early version of the 180 drivers break the suspension/resume, however 180.25(beta) driver has fixed this issue as well as improved 2D performance in X. As of Jan 29, 2009, the 180 series drivers have been added to the official repository under the name nvidia-glx-180. The 'intrepid-updates' repository has to be enabled via
System --> Administration --> Software Sources --> Updates

to download the drivers. The 180.11 version does not seem to have any suspend / hibernate issues.

Once the proprietary drivers are installed, the "NVidia X Server Settings" program will be available in System --> Administration.

===Version 177 logout/X restart fix===
There is a known issue in the v177 proprietary NVidia driver - See Launchpad bug [http://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-177/+bug/258357 258357]. Once you install the v177 driver, logging out or restarting X will cease to work, though suspend to RAM/Disk will continue to function.

The work around is as follows:
* In /etc/gdm/gdm.conf , increase the value for GdmXserverTimeout to about 60. When logging out or restarting X, X will hang for ~35 seconds. By increasing the value from its default, GDM will give X more time before it assumes X is faulty.

===Choppy Compiz animations===
NVidia's PowerMizer feature will slow down the GPU when "inactive" even on AC power.

The NVidia driver does not report the correct refresh rate of the display to Compiz, resulting in choppy animations and effects. To fix this, install the <code>compizconfig-settings-manager</code> package, then go to System --> Preferences --> Advanced Desktop Effects Settings (also might be called CompizConfig Settings Manager). Click on General Options, go to the Display Settings tab, uncheck the Detect Refresh rate box and drag the Refresh Rate slider to 60. Also, check the Sync To VBlank box. This will improve the smoothness of the window animations significantly if you're sensitive to the choppy animations.

Compiz animations can also be choppy due to NVidia's PowerMizer feature, which slows down the GPU to conserve power when it is not in use. This works well for 3D games which constantly use 3D acceleration, but poorly for Compiz which uses the GPU in small bursts. It seems that the interval of the PowerMizer is way too long and is not speeding up when using in bursts. Fortunately, the situation seems to have improved in version 177 of the NVidia driver. To workaround this problem, I made a couple of shell scripts which keep the GPU at its highest speed while running on AC power. The first one is named "powermizer-loop" and does most of the work:

#!/bin/sh

while true; do

powerstate=`cat /proc/acpi/ac_adapter/AC/state | awk '{print $2}'`

if [ $powerstate = "on-line" ]; then
nvidia-settings -q all > /dev/null
fi
sleep 25;
done

The second is named "powermizer-off" and starts up powermizer-loop when I log in, ensuring that only one copy runs at a time:

#!/bin/sh

killall powermizer-loop
~/powermizer-loop &

I put both of these scripts in my home directory and made them executable by doing:

chmod a+x powermizer-loop powermizer-off

Then to make powermizer-off run on login, I opened System --> Preferences --> Sessions, clicked on Add, and entered the command to run the script, i.e. "/home/<user>/powermizer-off".

Of course, performance still suffers when running on battery, but hopefully NVidia will fix this problem in a future version of their driver.

=== EDID misdetection ===

EDID (Extended Display Identification Data) might be misdetected for your display, which reduces the number of resolutions available in the NVidia X Server Settings application. (For example, I was unable to set my laptop's screen to 1024x768 for use with a projector during a presentation.) If you encounter this problem, add the following lines to /etc/X11/xorg.conf in the "Screen" section:

Option "UseEdidFreqs" "FALSE"
Option "HorizSync" "40-70"

The 40-70 values are just an example. They seem to work well with my 1680x1050 display. You should put the values of your display there. On a 1920x1200 display, making this change prevents the display from coming on when X starts.

A better but more complicated way would be using Phoenix EDID Designer to dump and fix the EDID data and then setup the Nvidia driver so it will use the customized EDID data, as described at [http://myricci.com/index.php?option=com_content&task=view&id=36]

==Microphone/Sound In==
Might need to be turned on in the mixer. See [[Install Ubuntu Hardy Heron on a T61p#Internal Microphone/Microphone Input Jack]]

==Front radio kill switch==
When killing Wireless LAN with the killswitch at the front, you won't be able to get WLAN back up after switching back. See Launchpad bugs [http://bugs.launchpad.net/ubuntu/+source/hal/+bug/289286 289286] and [http://bugs.launchpad.net/ubuntu/+source/linux-ubuntu-modules-2.6.24/+bug/193970 193970] and the [https://wiki.ubuntu.com/IntrepidReleaseNotes#Cannot%20reactivate%20Intel%203945/4965%20wireless%20if%20booting%20with%20killswitch%20enabled Release Notes] on the Ubuntu Wiki.

This will be solved in intrepid-updates eventually.

For now there are a few ways to bring the interface back up (choose one):
* Right click the network manager icon in the tray, uncheck Enable Wireless, then check it again does the trick (at least for me)
* {{cmdroot|ip l s wlan0 up}}
* {{cmdroot|modprobe -r iwl3945 && modprobe iwl3945}}
* reboot
* suspend and resume

== Middle-button Scrolling ==
Xorg.conf is not used to configure mice and keyboards anymore, but evdev is. This makes the configuration of middle-click scrolling a little bit different than previous versions of Ubuntu.

[http://mvogt.wordpress.com/2008/08/15/xorg-evdev-and-emulatewheel/ Michael Vogt described] how to get middle-click scrolling to work again in Intrepid.

{{cmduser| sudo gedit /etc/hal/fdi/policy/mouse-wheel.fdi}}

Paste and save the following code, which will give vertical wheel emulation only:
<match key="info.product" string="TPPS/2 IBM TrackPoint">
<merge key="input.x11_options.EmulateWheel" type="string">true</merge>
<merge key="input.x11_options.EmulateWheelButton" type="string">2</merge>
<merge key="input.x11_options.ZAxsisMapping" type="string">4 5</merge>
<merge key="input.x11_options.Emulate3Buttons" type="string">true</merge>
</match>
There is [http://psung.blogspot.com/2008/09/scrolling-with-thinkpads-trackpoint-in.html another method] to get horizontal scrolling as well, but this is not confirmed to work.

source:
*[[Installing_Ubuntu_8.10_%28Intrepid_Ibex%29_on_a_ThinkPad_T61#Emulate_Wheel_.28Middle-click_scrolling.29| Installing Ubuntu 8.10 (Intrepid Ibex) on a ThinkPad T61 - Emulate Wheel (Middle-click scrolling)]]

==Fingerprint Reader==

The [http://thinkfinger.sourceforge.net Thinkfinger] package allows you to swipe a finger in most places where you would have to type your password. This works with sudo, gksudo and on the login page and with a little fix also for the screen saver. Also, you are still required to type your user name on the login screen.

0) Set up the third party repository (optional but recommended!)

due to this [https://bugs.launchpad.net/ubuntu/+source/thinkfinger/+bug/256429 Bug #256429: Carriage-return required after finger scan] you need to press the return key after you swipe your finger with the current version of the kernel and the packages in ubuntu. The bug is caused by the fact that it does not recognize the fingerprint reader 100% correctly ([https://bugs.launchpad.net/ubuntu/+source/thinkfinger/+bug/256429/comments/29 Description of the root cause]) , as a temporary workaround there is a special package repository.

The packages present in ubuntu intrepid will work but you need to press enter after you swipe your finger.

Click System -> administration -> software sources
go to the tab "third-party software" and click Add ...

Enter in the popup window:

deb http://ppa.launchpad.net/jon-oberheide/ubuntu intrepid main

Click Add source, it will ask to refresh the package list, click reload.

1) Install the following packages:

{{cmduser| sudo apt-get install thinkfinger-tools libpam-thinkfinger libthinkfinger0}}

2) For your user:

{{cmduser| sudo tf-tool --acquire && sudo tf-tool --verify}}

A completed fingerprint setup should look something like this:

frank@Laptop:~$ sudo tf-tool --acquire && sudo tf-tool --verify

ThinkFinger 0.3 (http://thinkfinger.sourceforge.net/)
Copyright (C) 2006, 2007 Timo Hoenig <thoenig@suse.de>

Initializing... done.
Please swipe your finger (successful swipes 3/3, failed swipes: 0)... done.
Storing data (/tmp/test.bir)... done.

ThinkFinger 0.3 (http://thinkfinger.sourceforge.net/)
Copyright (C) 2006, 2007 Timo Hoenig <thoenig@suse.de>

Initializing... done.
Please swipe your finger (successful swipes 1/1, failed swipes: 0)... done.
Result: Fingerprint does match.
frank@CLaptop:~$

This will store your fingerprint information in /home/$USERNAME/.thinkfinger.bir

You should do this step for each user who wants to use the fingerprint reader

3) Enable use of reader for authentication:

{{cmduser| sudo gedit /etc/pam.d/common-auth}}

add
auth sufficient pam_thinkfinger.so
before the line which contains pam_unix.so and add
try_first_pass
to the end of the line containing pam_unix.so.

So it should look something like this:
...
auth sufficient pam_thinkfinger.so
auth [success=1 default=ignore] pam_unix.so nullok_secure try_first_pass
...

4) Check uinput kernel module:

{{cmduser|lsmod | grep uinput}}
If the output starts with uinput, then you're done.
If you don't get any output, then it needs to be started and set to start on boot.

Start uinput:

{{cmduser|sudo modprobe uinput}}

Start on boot:

{{cmduser|sudo gedit /etc/modules}}

make sure there is a line like this or add it at the bottom:
uinput

5) Enabling thinkfinger for gnome-screensaver

*create this file:
{{cmduser|sudo gedit /etc/udev/rules.d/60-thinkfinger.rules}}
with this contents:
#
# udev rules file for the thinkfinger fingerprint scanner
# gives access to the fingerprint reader to those in the "fingerprint" group
#
# Taken from:
# http://www.thinkwiki.org/wiki/Install_Ubuntu_Intrepid_Ibex_on_a_T61p#Fingerprint_Reader
# which was taken and modified from:
# http://www.thinkwiki.org/wiki/How_to_enable_the_fingerprint_reader_with_ThinkFinger
# http://article.gmane.org/gmane.linux.drivers.thinkfinger/329

# SGS Thomson Microelectronics Fingerprint Reader
SYSFS{idVendor}=="0483", SYSFS{idProduct}=="2016", SYMLINK+="input/thinkfinger-%k", MODE="0660", GROUP="fingerprint"

# the also-needed uinput device
KERNEL=="uinput", MODE="0660", GROUP="fingerprint"

*Make the group:
{{cmduser|sudo groupadd fingerprint}}
*per user:
{{cmduser|sudo gpasswd -a $USERNAME fingerprint && sudo chown $USERNAME:root /home/$USERNAME/.thinkfinger.bir }}

Reboot your laptop and you should be ready to swipe!

Sources:
* [[Install_Ubuntu_Gutsy_Gibbon_on_a_T61p#Fingerprint_Reader| Install Ubuntu Gutsy Gibbon on a T61p]]
* [https://bugs.launchpad.net/ubuntu/+source/thinkfinger/+bug/256429 Bug #256429: Carriage-return required after finger scan] & [https://bugs.launchpad.net/ubuntu/+source/thinkfinger/+bug/256429/comments/21 Solution for the bug in the comments]
* [https://launchpad.net/~jon-oberheide/+archive Repository for the third party fix] credits to [https://launchpad.net/~jon-oberheide Jon Oberheide]
* [[How_to_enable_the_fingerprint_reader_with_ThinkFinger| General page about Fingerprint reader with thinkfinger]] & [[How_to_enable_the_fingerprint_reader_with_ThinkFinger#xscreensaver.2Fgnome-screensaver| Specific gnome-screensaver section]]

==Hard Drive Active Protection System (APS ~ HDAPS)==
Please add to this section

Some interesting links:
* [[Active_Protection_System| Description of APS]]
* [[How_to_protect_the_harddisk_through_APS| How to protect the harddisk through APS]]
* [[Tp_smapi| tp_smapi kernel modules]]

=Other Problems=
== Resume Disables WLAN ==
On power up CDMA WLAN module is enabled, if user suspense and resumes it is turned off - no known fix.
Additionally fn-F5 turns off bluetooth but no option to turn off WLAN using function keys. This is problem is on the 6459CTO.

== Resume Requests WIFI Network Key ==
On resume Network Manager request the wifi network key several times before connecting to network. This has been noted on a 6459CTO laptop and no known fix is available. Currently with this problem it takes several minutes to regain network access after resume.

== Black Screen on Resume ==
On the 6459CTO with default 8.10 install suspend did not work. Enabling the proposed updates to be installed to your system might fix this issue. To enable the proposed updates go to the 'Software Sources' - tab 'Updates' in System -> Administration. Tick the 'Proposed updates (intrepid-updates)' checkbox, close 'Software Sources' to reload the package lists. Then, check for updates with the software updater (there should be some), update and reboot afterwards.

== Wireless not working after resume (Atheros) ==
After resuming from suspend, I am unable to reconnect to my wireless network. Network Manager asks me for my password over and over again but never succeeds in connecting. I'm using the Thinkpad (Atheros) A/B/G wireless card.

To fix this problem, I followed the instructions listed at https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/275692. Specifically, I created a file called /etc/pm/config.d/01-modules and put the following line in it:

SUSPEND_MODULES="ath_pci"

== Brightness control on battery power ==
By default, when unplugging the AC power while the system is running, the brightness of the display goes down even when you have set not to in the Power Management settings and you are not able to reach a brightness level as high as possible when connected to AC power. This is not a software setting or GNOME bug, but a BIOS setting. In the BIOS you can find a brightness setting in the Power section. Set it to high for normal, expected behavior. You can let the GNOME Power Manager still lower the brightness, but you will be able to increase it when needed.

== Kernel Panic (System freezes and Caps lock blinks) ==
This is caused by a bug on the wireless card drivers for the Intel Corporation PRO/Wireless 4965 AG or AGN.
To fix you need newer drivers from the backport modules:

sudo apt-get install linux-backports-modules-intrepid

--[[User:Lunatico|Lunatico]] 14:34, 3 April 2009 (UTC)

=Software Install=
==Adobe Flash==
Adobe has plug-ins direct for 32 bit version for x64 download the libflashplayer.so file from here:
http://labs.adobe.com/downloads/flashplayer10.html
Then copy to the mozilla plugins directory
sudo cp libflashplayer.so /usr/lib/firefox-addons/plugins/

=Other Information=
== Saving power ==
Some nice information on power saving you can find at

http://www.lesswatts.org

A tool that allows you to test most tips and tricks to reduce power is powertop, you can install it using

{{cmduser|sudo apt-get install powertop}}

and run it with:

{{cmduser|sudo powertop}}

For more information see http://www.lesswatts.org/projects/powertop/
== Battery control by tp_smapi ==
You need to load a kernel module first:
sudo modprobe tp_smapi

Now, you will be able to have significantly more control over your battery charging via /sys/devices/platform/smapi.

For example, you could set a threshold value of 90% for charging, preventing the battery from charging all the way in exchange for a reduction in the loss of battery capacity that occurs after multiple cycles.
echo "90" | sudo tee -a /sys/devices/platform/smapi/BAT0/stop_charge_thresh
(by default this was set to 86% on my laptop)

View the number of charge cycles your battery has had in its lifetime:
cat /sys/devices/platform/smapi/BAT0/cycle_count

While AC connected, force discharging of your battery:
echo "1" | sudo tee -a /sys/devices/platform/smapi/BAT0/force_discharge

For convenience, you could load the kernel module at boot time by adding it to /etc/modules.
echo "tp_smapi" | sudo tee -a /etc/modules

If you have an Ultrabay battery, you might want to place this [http://forum.thinkpads.com/viewtopic.php?p=433463#p433463 script] into <code>/etc/crontab</code> to keep the Ultrabay battery from being completely discharged to 0%, which permanently damages the battery.
# rolls to BAT0 when remaining capacity on BAT1 is less than 20%. Change .2 if wanted. Swap BAT0 and BAT1 if tp_smapi thinks the ultrabay is BAT0.
awk '{if (/remaining capacity/) left=$3; if (/last full capacity/) full=$4} END {if ((left/full) < .2) system("echo 1 > /sys/devices/platform/smapi/BAT0/force_discharge")}' /proc/acpi/battery/BAT1/*
Remember the script needs root in order to write to the files in <code>/sys/devices/platform/smapi/BAT{0,1}/</code>.

= Compared to Hardy (8.04) =
Why upgrade your T61p to Intrepid or why not? (Specific for T61p)
== Improvements ==
*Ricoh SD card reader now reads read-only SD card. (Tested with Adata 150X 2GB SD card)
*Newer Wireless LAN drivers. For Intel cards this results in working LED, more sensitive reception, increased stability of connections and some 802.1x bugfixes.
*Out-of-the-box Suspend to RAM functionality (also faster resume). Not on 6459, (see above)
*Working but slow Suspend to Disk functionality.

== Bugs and Regressions ==
*Hard radio killswitch (at the front) cannot bring WLAN back up after killing it. (workaround available)
*X hangs for approx. 35 seconds when restarting or logging out. (workaround available)
*Atheros WLAN not working after resume from Suspend to RAM (but a workaround is available; [[#Wireless_not_working_after_resume_.28Atheros.29|see above]]).

[[Category:T61p]]
[[Category:Ubuntu]]
[[Category:Ubuntu 8.10]]

Install Ubuntu Intrepid Ibex on a T61p

2009-03-23T12:48:19Z

Lunatico: /* Other Problems */

=What works out of the box?=
*Wireless (Intel 3945ABG or 4965AGN)
**Only tested G mode
*Wired LAN
*Video (VESA)
**Hardware Drivers panel offers to install nVIDIA proprietary drivers on first boot.
*Touchpoint and Trackpad
**Including scroll at the right side of the pad by default.
**Middle-button scrolling does NOT work (fix below)
*Optical drive
**Optiarc AD-7910A works fine with Brasero disc burning
***Tested: CD-R, DVD+R
*Sound card
*SD/MMC Memory card reader (Ricoh)
**Only tested SD (non-HC) cards.
*Control buttons/Hotkeys
**Volume control buttons
**Screen brightness control
**Thinklight control
**WLAN/BT/OFF toggle
**Media player control
**fingerprint reader does NOT work (fix below)
*Some ACPI features
**Battery status, power graphs and history
**Lid states and events
**Only tested with a single 6-cell battery
*ACPI features
** Suspend to RAM
** Suspend to Disk (Hibernate) FINALLY!! Be patient, though.
** STR and STD work even with full disk encryption (DM-crypt + LVM)!

=Getting the hardware to work=
==Display/Video==
Installing the proprietary NVidia drivers is highly recommended, EVEN IF you won't use 3D acceleration, because the open source nv driver will drain your battery much faster since it does not support PowerMizer at all. Practically, this means that the GPU will constantly run at full speed, thus consuming ~12 Watts more than it would otherwise (which is a LOT of power for a laptop).

The first time you boot Ubuntu, you should get an alert asking if you want to install the binary driver. If not, it can be installed from the Hardware Drivers panel at

System --> Administration --> Hardware Drivers.

You will have a choice between the 173 and 177 version of the driver (Note: if you want to have better 2D performance without breaking suspend/resume, you will have to manually install the 180.25 driver manually as it is not included in the official Intrepid repo).
*pro:
**Version 177 is recommended because it will provide Suspend to disk functionality, whereas v173 will not.
*con:
**version 177 causes a log out bug that is addressed below.
**version 177 might show some issues like terminal output not updating in some very weird cases (which I did not see in v173, this seems to have something to do with powermizer as well ...)
*Early version of the 180 drivers break the suspension/resume, however 180.25(beta) driver has fixed this issue as well as improved 2D performance in X. As of Jan 29, 2009, the 180 series drivers have been added to the official repository under the name nvidia-glx-180. The 'intrepid-updates' repository has to be enabled via
System --> Administration --> Software Sources --> Updates

to download the drivers. The 180.11 version does not seem to have any suspend / hibernate issues.

Once the proprietary drivers are installed, the "NVidia X Server Settings" program will be available in System --> Administration.

===Version 177 logout/X restart fix===
There is a known issue in the v177 proprietary NVidia driver - See Launchpad bug [http://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-177/+bug/258357 258357]. Once you install the v177 driver, logging out or restarting X will cease to work, though suspend to RAM/Disk will continue to function.

The work around is as follows:
* In /etc/gdm/gdm.conf , increase the value for GdmXserverTimeout to about 60. When logging out or restarting X, X will hang for ~35 seconds. By increasing the value from its default, GDM will give X more time before it assumes X is faulty.

===Choppy Compiz animations===
NVidia's PowerMizer feature will slow down the GPU when "inactive" even on AC power.

The NVidia driver does not report the correct refresh rate of the display to Compiz, resulting in choppy animations and effects. To fix this, install the <code>compizconfig-settings-manager</code> package, then go to System --> Preferences --> Advanced Desktop Effects Settings (also might be called CompizConfig Settings Manager). Click on General Options, go to the Display Settings tab, uncheck the Detect Refresh rate box and drag the Refresh Rate slider to 60. Also, check the Sync To VBlank box. This will improve the smoothness of the window animations significantly if you're sensitive to the choppy animations.

Compiz animations can also be choppy due to NVidia's PowerMizer feature, which slows down the GPU to conserve power when it is not in use. This works well for 3D games which constantly use 3D acceleration, but poorly for Compiz which uses the GPU in small bursts. It seems that the interval of the PowerMizer is way too long and is not speeding up when using in bursts. Fortunately, the situation seems to have improved in version 177 of the NVidia driver. To workaround this problem, I made a couple of shell scripts which keep the GPU at its highest speed while running on AC power. The first one is named "powermizer-loop" and does most of the work:

#!/bin/sh

while true; do

powerstate=`cat /proc/acpi/ac_adapter/AC/state | awk '{print $2}'`

if [ $powerstate = "on-line" ]; then
nvidia-settings -q all > /dev/null
fi
sleep 25;
done

The second is named "powermizer-off" and starts up powermizer-loop when I log in, ensuring that only one copy runs at a time:

#!/bin/sh

killall powermizer-loop
~/powermizer-loop &

I put both of these scripts in my home directory and made them executable by doing:

chmod a+x powermizer-loop powermizer-off

Then to make powermizer-off run on login, I opened System --> Preferences --> Sessions, clicked on Add, and entered the command to run the script, i.e. "/home/<user>/powermizer-off".

Of course, performance still suffers when running on battery, but hopefully NVidia will fix this problem in a future version of their driver.

=== EDID misdetection ===

EDID (Extended Display Identification Data) might be misdetected for your display, which reduces the number of resolutions available in the NVidia X Server Settings application. (For example, I was unable to set my laptop's screen to 1024x768 for use with a projector during a presentation.) If you encounter this problem, add the following lines to /etc/X11/xorg.conf in the "Screen" section:

Option "UseEdidFreqs" "FALSE"
Option "HorizSync" "40-70"

The 40-70 values are just an example. They seem to work well with my 1680x1050 display. You should put the values of your display there. On a 1920x1200 display, making this change prevents the display from coming on when X starts.

A better but more complicated way would be using Phoenix EDID Designer to dump and fix the EDID data and then setup the Nvidia driver so it will use the customized EDID data, as described at [http://myricci.com/index.php?option=com_content&task=view&id=36]

==Microphone/Sound In==
Might need to be turned on in the mixer. See [[Install Ubuntu Hardy Heron on a T61p#Internal Microphone/Microphone Input Jack]]

==Front radio kill switch==
When killing Wireless LAN with the killswitch at the front, you won't be able to get WLAN back up after switching back. See Launchpad bugs [http://bugs.launchpad.net/ubuntu/+source/hal/+bug/289286 289286] and [http://bugs.launchpad.net/ubuntu/+source/linux-ubuntu-modules-2.6.24/+bug/193970 193970] and the [https://wiki.ubuntu.com/IntrepidReleaseNotes#Cannot%20reactivate%20Intel%203945/4965%20wireless%20if%20booting%20with%20killswitch%20enabled Release Notes] on the Ubuntu Wiki.

This will be solved in intrepid-updates eventually.

For now there are a few ways to bring the interface back up (choose one):
* Right click the network manager icon in the tray, uncheck Enable Wireless, then check it again does the trick (at least for me)
* {{cmdroot|ip l s wlan0 up}}
* {{cmdroot|modprobe -r iwl3945 && modprobe iwl3945}}
* reboot
* suspend and resume

== Middle-button Scrolling ==
Xorg.conf is not used to configure mice and keyboards anymore, but evdev is. This makes the configuration of middle-click scrolling a little bit different than previous versions of Ubuntu.

[http://mvogt.wordpress.com/2008/08/15/xorg-evdev-and-emulatewheel/ Michael Vogt described] how to get middle-click scrolling to work again in Intrepid.

{{cmduser| sudo gedit /etc/hal/fdi/policy/mouse-wheel.fdi}}

Paste and save the following code, which will give vertical wheel emulation only:
<match key="info.product" string="TPPS/2 IBM TrackPoint">
<merge key="input.x11_options.EmulateWheel" type="string">true</merge>
<merge key="input.x11_options.EmulateWheelButton" type="string">2</merge>
<merge key="input.x11_options.ZAxsisMapping" type="string">4 5</merge>
<merge key="input.x11_options.Emulate3Buttons" type="string">true</merge>
</match>
There is [http://psung.blogspot.com/2008/09/scrolling-with-thinkpads-trackpoint-in.html another method] to get horizontal scrolling as well, but this is not confirmed to work.

source:
*[[Installing_Ubuntu_8.10_%28Intrepid_Ibex%29_on_a_ThinkPad_T61#Emulate_Wheel_.28Middle-click_scrolling.29| Installing Ubuntu 8.10 (Intrepid Ibex) on a ThinkPad T61 - Emulate Wheel (Middle-click scrolling)]]

==Fingerprint Reader==

The [http://thinkfinger.sourceforge.net Thinkfinger] package allows you to swipe a finger in most places where you would have to type your password. This works with sudo, gksudo and on the login page and with a little fix also for the screen saver. Also, you are still required to type your user name on the login screen.

0) Set up the third party repository (optional but recommended!)

due to this [https://bugs.launchpad.net/ubuntu/+source/thinkfinger/+bug/256429 Bug #256429: Carriage-return required after finger scan] you need to press the return key after you swipe your finger with the current version of the kernel and the packages in ubuntu. The bug is caused by the fact that it does not recognize the fingerprint reader 100% correctly ([https://bugs.launchpad.net/ubuntu/+source/thinkfinger/+bug/256429/comments/29 Description of the root cause]) , as a temporary workaround there is a special package repository.

The packages present in ubuntu intrepid will work but you need to press enter after you swipe your finger.

Click System -> administration -> software sources
go to the tab "third-party software" and click Add ...

Enter in the popup window:

deb http://ppa.launchpad.net/jon-oberheide/ubuntu intrepid main

Click Add source, it will ask to refresh the package list, click reload.

1) Install the following packages:

{{cmduser| sudo apt-get install thinkfinger-tools libpam-thinkfinger libthinkfinger0}}

2) For your user:

{{cmduser| sudo tf-tool --acquire && sudo tf-tool --verify}}

A completed fingerprint setup should look something like this:

frank@Laptop:~$ sudo tf-tool --acquire && sudo tf-tool --verify

ThinkFinger 0.3 (http://thinkfinger.sourceforge.net/)
Copyright (C) 2006, 2007 Timo Hoenig <thoenig@suse.de>

Initializing... done.
Please swipe your finger (successful swipes 3/3, failed swipes: 0)... done.
Storing data (/tmp/test.bir)... done.

ThinkFinger 0.3 (http://thinkfinger.sourceforge.net/)
Copyright (C) 2006, 2007 Timo Hoenig <thoenig@suse.de>

Initializing... done.
Please swipe your finger (successful swipes 1/1, failed swipes: 0)... done.
Result: Fingerprint does match.
frank@CLaptop:~$

This will store your fingerprint information in /home/$USERNAME/.thinkfinger.bir

You should do this step for each user who wants to use the fingerprint reader

3) Enable use of reader for authentication:

{{cmduser| sudo gedit /etc/pam.d/common-auth}}

add
auth sufficient pam_thinkfinger.so
before the line which contains pam_unix.so and add
try_first_pass
to the end of the line containing pam_unix.so.

So it should look something like this:
...
auth sufficient pam_thinkfinger.so
auth [success=1 default=ignore] pam_unix.so nullok_secure try_first_pass
...

4) Check uinput kernel module:

{{cmduser|lsmod | grep uinput}}
If the output starts with uinput, then you're done.
If you don't get any output, then it needs to be started and set to start on boot.

Start uinput:

{{cmduser|sudo modprobe uinput}}

Start on boot:

{{cmduser|sudo gedit /etc/modules}}

make sure there is a line like this or add it at the bottom:
uinput

5) Enabling thinkfinger for gnome-screensaver

*create this file:
{{cmduser|sudo gedit /etc/udev/rules.d/60-thinkfinger.rules}}
with this contents:
#
# udev rules file for the thinkfinger fingerprint scanner
# gives access to the fingerprint reader to those in the "fingerprint" group
#
# Taken from:
# http://www.thinkwiki.org/wiki/Install_Ubuntu_Intrepid_Ibex_on_a_T61p#Fingerprint_Reader
# which was taken and modified from:
# http://www.thinkwiki.org/wiki/How_to_enable_the_fingerprint_reader_with_ThinkFinger
# http://article.gmane.org/gmane.linux.drivers.thinkfinger/329

# SGS Thomson Microelectronics Fingerprint Reader
SYSFS{idVendor}=="0483", SYSFS{idProduct}=="2016", SYMLINK+="input/thinkfinger-%k", MODE="0660", GROUP="fingerprint"

# the also-needed uinput device
KERNEL=="uinput", MODE="0660", GROUP="fingerprint"

*Make the group:
{{cmduser|sudo groupadd fingerprint}}
*per user:
{{cmduser|sudo gpasswd -a $USERNAME fingerprint && sudo chown $USERNAME:root /home/$USERNAME/.thinkfinger.bir }}

Reboot your laptop and you should be ready to swipe!

Sources:
* [[Install_Ubuntu_Gutsy_Gibbon_on_a_T61p#Fingerprint_Reader| Install Ubuntu Gutsy Gibbon on a T61p]]
* [https://bugs.launchpad.net/ubuntu/+source/thinkfinger/+bug/256429 Bug #256429: Carriage-return required after finger scan] & [https://bugs.launchpad.net/ubuntu/+source/thinkfinger/+bug/256429/comments/21 Solution for the bug in the comments]
* [https://launchpad.net/~jon-oberheide/+archive Repository for the third party fix] credits to [https://launchpad.net/~jon-oberheide Jon Oberheide]
* [[How_to_enable_the_fingerprint_reader_with_ThinkFinger| General page about Fingerprint reader with thinkfinger]] & [[How_to_enable_the_fingerprint_reader_with_ThinkFinger#xscreensaver.2Fgnome-screensaver| Specific gnome-screensaver section]]

==Hard Drive Active Protection System (APS ~ HDAPS)==
Please add to this section

Some interesting links:
* [[Active_Protection_System| Description of APS]]
* [[How_to_protect_the_harddisk_through_APS| How to protect the harddisk through APS]]
* [[Tp_smapi| tp_smapi kernel modules]]

=Other Problems=
== Resume Disables WLAN ==
On power up CDMA WLAN module is enabled, if user suspense and resumes it is turned off - no known fix.
Additionally fn-F5 turns off bluetooth but no option to turn off WLAN using function keys. This is problem is on the 6459CTO.

== Resume Requests WIFI Network Key ==
On resume Network Manager request the wifi network key several times before connecting to network. This has been noted on a 6459CTO laptop and no known fix is available. Currently with this problem it takes several minutes to regain network access after resume.

== Black Screen on Resume ==
On the 6459CTO with default 8.10 install suspend did not work. Enabling the proposed updates to be installed to your system might fix this issue. To enable the proposed updates go to the 'Software Sources' - tab 'Updates' in System -> Administration. Tick the 'Proposed updates (intrepid-updates)' checkbox, close 'Software Sources' to reload the package lists. Then, check for updates with the software updater (there should be some), update and reboot afterwards.

== Wireless not working after resume (Atheros) ==
After resuming from suspend, I am unable to reconnect to my wireless network. Network Manager asks me for my password over and over again but never succeeds in connecting. I'm using the Thinkpad (Atheros) A/B/G wireless card.

To fix this problem, I followed the instructions listed at https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/275692. Specifically, I created a file called /etc/pm/config.d/01-modules and put the following line in it:

SUSPEND_MODULES="ath_pci"

== Brightness control on battery power ==
By default, when unplugging the AC power while the system is running, the brightness of the display goes down even when you have set not to in the Power Management settings and you are not able to reach a brightness level as high as possible when connected to AC power. This is not a software setting or GNOME bug, but a BIOS setting. In the BIOS you can find a brightness setting in the Power section. Set it to high for normal, expected behavior. You can let the GNOME Power Manager still lower the brightness, but you will be able to increase it when needed.

== Kernel Panic (System freezes and Caps lock blinks) ==
This is caused by a bug on the wireless card drivers on the Intel Corporation PRO/Wireless 4965 AG or AGN.
To fix you need newer drivers on the backport modules:

sudo apt-get install linux-backports-modules-intrepid

=Software Install=
==Adobe Flash==
Adobe has plug-ins direct for 32 bit version for x64 download the libflashplayer.so file from here:
http://labs.adobe.com/downloads/flashplayer10.html
Then copy to the mozilla plugins directory
sudo cp libflashplayer.so /usr/lib/firefox-addons/plugins/

=Other Information=
== Saving power ==
Some nice information on power saving you can find at

http://www.lesswatts.org

A tool that allows you to test most tips and tricks to reduce power is powertop, you can install it using

{{cmduser|sudo apt-get install powertop}}

and run it with:

{{cmduser|sudo powertop}}

For more information see http://www.lesswatts.org/projects/powertop/
== Battery control by tp_smapi ==
You need to load a kernel module first:
sudo modprobe tp_smapi

Now, you will be able to have significantly more control over your battery charging via /sys/devices/platform/smapi.

For example, you could set a threshold value of 90% for charging, preventing the battery from charging all the way in exchange for a reduction in the loss of battery capacity that occurs after multiple cycles.
echo "90" | sudo tee -a /sys/devices/platform/smapi/BAT0/stop_charge_thresh
(by default this was set to 86% on my laptop)

View the number of charge cycles your battery has had in its lifetime:
cat /sys/devices/platform/smapi/BAT0/cycle_count

While AC connected, force discharging of your battery:
echo "1" | sudo tee -a /sys/devices/platform/smapi/BAT0/force_discharge

For convenience, you could load the kernel module at boot time by adding it to /etc/modules.
echo "tp_smapi" | sudo tee -a /etc/modules

If you have an Ultrabay battery, you might want to place this [http://forum.thinkpads.com/viewtopic.php?p=433463#p433463 script] into <code>/etc/crontab</code> to keep the Ultrabay battery from being completely discharged to 0%, which permanently damages the battery.
# rolls to BAT0 when remaining capacity on BAT1 is less than 20%. Change .2 if wanted. Swap BAT0 and BAT1 if tp_smapi thinks the ultrabay is BAT0.
awk '{if (/remaining capacity/) left=$3; if (/last full capacity/) full=$4} END {if ((left/full) < .2) system("echo 1 > /sys/devices/platform/smapi/BAT0/force_discharge")}' /proc/acpi/battery/BAT1/*
Remember the script needs root in order to write to the files in <code>/sys/devices/platform/smapi/BAT{0,1}/</code>.

= Compared to Hardy (8.04) =
Why upgrade your T61p to Intrepid or why not? (Specific for T61p)
== Improvements ==
*Ricoh SD card reader now reads read-only SD card. (Tested with Adata 150X 2GB SD card)
*Newer Wireless LAN drivers. For Intel cards this results in working LED, more sensitive reception, increased stability of connections and some 802.1x bugfixes.
*Out-of-the-box Suspend to RAM functionality (also faster resume). Not on 6459, (see above)
*Working but slow Suspend to Disk functionality.

== Bugs and Regressions ==
*Hard radio killswitch (at the front) cannot bring WLAN back up after killing it. (workaround available)
*X hangs for approx. 35 seconds when restarting or logging out. (workaround available)
*Atheros WLAN not working after resume from Suspend to RAM (but a workaround is available; [[#Wireless_not_working_after_resume_.28Atheros.29|see above]]).

[[Category:T61p]]
[[Category:Ubuntu]]
[[Category:Ubuntu 8.10]]

Talk:Thermal Sensors

2009-01-18T15:37:17Z

Lunatico: /* T61? */

== 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)
----
Yep, that was a T40. Well, I purchased a can of cooling spray today. First results without opening the machine indicate 0xC2 is near the grill below the Esc-F3 keys. The currently still unknown 0x7A cools down if I spray into the PCMCIA slot (also makes sense to place a sensor there, I'd say it is on the mainboard below the slots).

Probably will open the case tonight or tomorrow. I guess for precise results I'll need to remove the bezel and the fan ... quite an adventure ;-). Will keep you posted of further results.

-- Shimodax 2005-12-07
----

Speaking of the PCMCIA port - I noticed that under heavy CPU load with the fan on, if I insert a PC Card into the slot then the CPU and 0x79 (HDAPS) temperature quickly go up a couple of degrees. This happens even if the PC Card is turned off or not inserted all the way in (no electric contact). Probably blocked airflow.

--[[User:Thinker|Thinker]] 20:08, 7 Dec 2005 (CET)
----
I opened the thing today and played around a bit. Here's my assesment of where the sensors are:
[http://img363.imageshack.us/img363/545/pc080805custom22ef.jpg Image] (dunno how to upload an image here, feel free to add it to thinkwiki directly).

C1 is most likely the Southbridge chip itself, APS and BUS are the small highlighted chips or very near them. PWR did not react much to the spray, but does react to spraying throught the grill on the bottom of the case, so it's probably on the underside.

-- Shimodax 2005-12-08

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

----

Shimodax,

Beautiful, beautiful work! Got everything back in working order, I hope, including those pesky screwcap stickers?

This confirms our information/guesses about CPU,GPU,BAT,BAT2,PWR and Southbridge, and solves the mystery of 0x7A (PCMCIA) and 0xCA (Northbridge-RAM bus). A few notes:

* 0x79 is a surprise - it is quite far from the HDAPS acceleromater chip (search for "accelerometer" [ftp://ftp.software.ibm.com/pc/pccbbs/mobiles_pdf/39t2393.pdf here]), even though it gives the same temperatures as when reading the accelerometer's IO ports. But this explains why 0x89 quickly gets hotter under load when the PCMCIA port is blocked.
* The mapping is indeed different from the R52 one that people keep citing because of the ibm-acpi documentation - the 2nd and 3rd sensors are ''not'' HDD and Mini-PCI.
* Some of the chips are a quite distant from the hot components they presumably monitor. Most significantly, when some usage causes the Northbridge to heat up rapidly, by the time sensor 0xC0 says 55 degrees the Northbridge core is probably above 60.

Shimodoax, it would be great if you could upload more (unprocessed) photos, either to the Wiki (using the "Upload file" button on the left navigation bar) or by links. Deserves its own Wikipage, I think. It will save a lot of people the need to open their laptop too... For example, in regard to a discussion from yesterday further up the page - got a clear photo of the fan power connector, by any chance?

--[[User:Thinker|Thinker]] 18:38, 8 Dec 2005 (CET)
----

See [[Thermal sensors]].

--[[User:Thinker|Thinker]] 19:48, 8 Dec 2005 (CET)
----
Just for the record: I did not test the two BAT locations, these were taken from your previous description. Regarding the other locations, I'm quite sure about them but not 100% definite. I would not treat them as bullet proof fact until someone else confirms the experiment.

The whole procedure went quite smoothly. I just found that there were three screws missing in my machine but luckily I had ordered a thinkpad screw kit on Ebay a few days ago. Also, on my model I did not need the stickers, all screws were without one. Just mone minor mishap happened when I stuck one of the #2 screws in the wrong hole (there is an empty hole that looks like a screw hole about 4mm from the intended location) and had a hard time getting the screw out.

I still have no idea how to upload stuff here, maybe becaue I don't have an account here. I do have a couple more pictures, also larger ones, although they are not too great photography. I'll upload them to the thinkpad forum via imageshack and you can grab them and put them here.

-- Shimodax -- 2005-12-08
----
Maybe those missing screws were the 3 optional Torx screws "protecting" the wireless card (lip service to FCC regulations). Yes, uploads require an account (registation is straightforward, and has some perks). BTW, and that extra hole fooled me too. :-)

--[[User:Thinker|Thinker]] 20:45, 8 Dec 2005 (CET)
----
One of the missing screws was the one that secures the HD, the other were two #1 near the front.
I just zipped and uploaded the other pictures to our server: [http://www.emtec.com/zzstuff/T43-2668.zip T43-2668.zip]. Feel free to upload or use them anywhere you want.

-- Shimodax -- 2005-12-08
----
Thinker, [[Talk:Problem with fan noise#Correct BIOS settings?|this]] could be related. [[User:Piccobello|Piccobello]] 11:12, 25 November 2006 (CET)
----

== Southbridge sensor 0xC1 ==

The southbridge on the T43 does not have a built-in thermal sensor, according to its specs (see [[Intel 82801FBM]]). So sensor 0xC1 may be adjacent or on the underside of the system board.
--Thinker
----

That's possible. Spraying the Southbridge chip did yield the most direct temperature changes, but they were not as quick as I would have expected (I attributed that to the large size of the chip). So it may indeed be the underside or something near (there wasn't anything visible that looked like the BUS or APS sensors in my picture.)

--Shimodax
----

Since the southbridge is the hottest thing around, and moreover has a large ceramic package, it gives the quickest heat exchange with the cooling spray (i.e., it "absorbs the cold" fastest). Thermal conductance through the PCB would then allow the sensor to be anywhere nearby. Similarly for some of the other locations, which to my (untrained) eye look more like power regulation components than sensors. So the actual sensors are probably on the underside (otherwise you'd spot them, and it also makes sense in the bottlenek is the user's lap rather than the chips), in the vicinity of the identified components.

--[[User:Thinker|Thinker]] 17:33, 11 Dec 2005 (CET)
----
For what it is worth, the other ones (BUS,APS) did react very directly, even to very targeted and short bursts of cold (in one instance BUS went down to zero with one burst). Also, they look quite like the thing the user on the thinkpads forum had identified on the T40. With the southbridge I sprayed that specifically also (just covering the chip) but results were not nearly as direct as with the small chips. Reason could have been that the chip itself generated heat from the core at the same time but if the SB doesn't have it's own sensor, a themrmal sensor on the underside would fit the observation quite as well (or even better).

--Shimodax

== "APS" sensor 0x79 ==

About the 0x79 sensor: I previously claimed that it's the HDAPS chip, because it gave the same values as reading the the Linux [[hdaps]] driver (which reads ports 0x1600-0x161f directly). This didn't sit well with Shmidoax's cooling spray experiment. Well, my original claim is misguided - it turns out that the interface at ports 0x1600-0x161f also reports stuff unrelated to HDAPS (namely battery information), so it's probably yet another view into the embedded controller and there's no reason to assign its temperature reports to the HDAPS accelerometer.

--[[User:Thinker|Thinker]] 00:50, 13 Dec 2005 (CET)
----

== Embedded controller firmware disassembly ==

[http://forum.thinkpads.com/viewtopic.php?t=20958 This thread] points to, and discusses, a commented (partial) disassembly of the embedded controller. It may provide useful hints about the sensors.

--[[User:Thinker|Thinker]] 07:07, 24 February 2006 (CET)
----

== empty screw hole ==

----
Anybody know what the empty screw hole on the bottom panel is?

Thanks

Shiyang

----

There's a screw hole under the Ultrabay slot, for an optional screw that locks in the Ultrabay device. There's also a hole (or two, on the T60) for drainage of spilled liquid from the keyboards.

--[[User:Thinker|Thinker]] 13:16, 17 March 2006 (CET)
----

== Thermal sensors on X40 ==

I was reading the locations of the sensors reported on other Thinkpads, but they seem to be different on the X40 (results with running Debian Testing).

$ cat /proc/acpi/ibm/thermal
temperatures: 42 43 47 38 -128 -128 -128 -128
$ smartctl -A /dev/hda | grep Temperature
194 Temperature_Celsius 0x0022 100 072 000 Old_age Always - 35 (Lifetime Min/Max 9/54)
$ cat /sys/bus/platform/drivers/hdaps/hdaps/temp1
39

So I ran some tests. The first thermal sensor show the CPU temperature, it rises significantly when doing CPU-intensive work (e.g. compiling). The second seems to be the GPU/Chipset (since it's an integrated GPU); temperatures on CPU and GPU rise several degrees when running e.g. glxgears. The third sensors I think should be underneath space key/mouse buttons; this is the hottest spot of the laptop and this sensor shows the highest temperatur (ok, this is just a guess). The fourth sensor seems to be related to the wireless mini pci card; its temperature shows a clear correlation to switching power saving on/off for the ipw2100.

With battery put back in the battery's two sensors are shown.

$ cat /proc/acpi/ibm/thermal
temperatures: 42 43 47 42 35 -128 33 -128

None of the sensors show the HDAPS or the HDD temperature.
The results so far are:

Index Location (estimated)
1 CPU
2 GPU/Chipset
3 Unknown
4 MiniPCI
5 System battery
6 n/a
7 System battery
8 n/a

No sensors show up when reading from ecdump (something wrong here?):

perl -ne 'print join(" ",map(hex,m/\w+/g))."\n" if s/^EC 0xc0://' < /proc/acpi/ibm/ecdump
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

Can someone confirm this? Other suggestions?

--shze 11:54, 14 May 2008 (CET)

----

The X40 doesn't have 0xC0 sensors, the HDD temperature you get from the HDD is not available through any other channel in any other thinkpad -- you may have an HDD sensor that is near the HDD in some thinkpads but that's not the same as a sensor inside the HDD :-)

As for the HDAPS temperature being different from the other normal sensors, now THAT is an interesting detail. Are you sure it is not on the regular sensor list?

--[[User:Hmh|hmh]] 17:07, 14 June 2008 (CEST)

== T61? ==

There doesn't seem to be any mention of the T61 in this article. Does anyone know about its /proc/acpi/ibm/thermal ? [[User:Zro|Zro]] 05:13, 13 June 2008 (CEST)

No, someone will have to open it and do the dirty work.

:Thanks [[User:Lunatico|Lunatico]] for adding the [[Thermal_Sensors#ThinkPad_T61|T61 temp zones]]. My results, however, are a little different. I notice that you have ''position 4'' listed as "n/a", yet I get a non-null (''not'' -128) result for that sensor position. Is this perhaps a difference w/ single processor vs SMP (multiprocessor) machines? My results are as follows for the record:
:<pre>temperatures: 46 43 34 54 34 -128 31 -128 39 44 42 -128 -128 -128 -128 -128</pre>
:Perhaps on SMP 1&2 are each a cpu then pushing the following results forward 1 position? Any ideas? [[User:Zro|Zro]] 19:51, 13 January 2009 (CET)

Well [[User:Zro|Zro]] I'm not sure why that difference. I don't understand what you mean about the single and multiprocessor machines. As far as I know the [http://www.thinkwiki.org/wiki/Category:T61#Standard_Features|T61 comes with Core Duo]. So as far as the 4th sensor I wouldn't have an answer for you. I still haven't got time to figure out sensors 9, 10 and 11 though, if you find that out let me know (and update [http://www.thinkwiki.org/wiki/Thermal_Sensors#ThinkPad_T61|my post]). I also have a T60p which also have some unknown sensors. Thanks! --[[User:Lunatico|Lunatico]] 15:37, 18 January 2009 (UTC)

Talk:Thermal Sensors

2009-01-18T15:36:46Z

Lunatico: /* T61? */

Installing Ubuntu 8.10 (Intrepid Ibex) on a ThinkPad T61

2008-12-18T21:53:46Z

Lunatico: /* Fingerprint Reader with ThinkFinger */

NOTE: I copied the 8.04 document and created this one with the information. Please help to update it so it accurately reflects 8.10.

== Items that work out of the box ==

'''Intel Video:''' 2D and 3D acceleration works

'''Nvidia Video:''' 2D and 3D acceleration works

'''Wireless:''' Intel cards tested. Atheros cards also works.

'''Wireless WAN:''' Cingular/AT&T card tested.

'''Network Card:''' Intel 10/100/1000 tested

'''Wireless switch:''' Tested (Only has an effect over the bluetooth, wifi is unaffected)

'''Webcam:''' Tested with cheese and skype.

'''Headphones:''' Works out of the box

'''Microphone:''' Just needs to be activated, see section [[#Audio|below]]

'''Keyboard Shortcuts:''' Most of them work out of the box, some need to be activated, see section [[#Multimedia_Keys|below]]

'''Fingerprint Reader:''' With ThinkFinger, not as functional after upgrade (need to hit 'Enter'), see below

== Items that need (some) tweaking to obtain full functionality ==

=== Sound (too quiet) ===
Sound works "out of the box", but is too quiet for many people. To fix this you need to do the following:
<pre>
gksudo gedit /etc/modprobe.d/alsa-base
</pre>
and add
<pre>
options snd-hda-intel model=thinkpad
</pre>
to the very end of the file ({{path|/etc/modprobe.d/alsa-base}}).

=== Open Source Intel Wifi Driver ===
The following information is important if you are upgrading from a previous version (2007 or earlier) of Ubuntu to 8.10.

Intel has created a new Linux Wifi driver project for Intel Wireless cards, "[[Iwlwifi]]". This driver is Open Source and no longer requires the Intel daemon to run in addition. This project will support the [[:Category:T61 | T61]]'s Wifi [[Intel PRO/Wireless 3945ABG Mini-PCI Express Adapter | Intel 3945ABG network adapter]] and [[Intel PRO/Wireless 4965AGN Mini-PCI Express Adapter| Intel 4965AGN network adapter]].

An automatic migration will occur when upgrading from [[Installing Ubuntu 7.10 (Gutsy Gibbon) on a ThinkPad T61|Ubuntu 7.10]] to Ubuntu 8.04. However, there is a caveat to be aware of:
* The new driver wants to name the interface wlan0 (by default -- you can rename it to anything you want), and requires a different entry in {{path|/etc/udev/rules.d/70-persistent-net.rules}}, which handles the naming of interfaces. Simply edit this file and delete your old entry for the ipw3945 driver, then unload/reload the new driver, or simply reboot. A new entry will automatically be created that is appropriate for the new driver. Here's an example of the lines to delete:
<pre>
# PCI device 0x8086:0x4227 (ipw3945)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:1b:77:a4:0e:2f", NAME="eth1"
</pre>

If you need to perform a manual migration, the Ubuntu Help Community has written some [https://help.ubuntu.com/community/WifiDocs/Driver/iwlwifi_Intel_3945_4965/gutsy documentation] that will make this very easy to do.

An additional note
'''System lock-ups with Intel 4965 wireless'''

The version of the iwlagn wireless driver for Intel 4965 wireless chipsets included in Linux kernel version 2.6.27 causes kernel panics when used with 802.11n or 802.11g networks. Users affected by this issue can install the linux-backports-modules-intrepid package, to install a newer version of this driver that corrects the bug. (Because the known fix requires a new version of the driver, it is not expected to be possible to include this fix in the main kernel package.)
http://www.ubuntu.com/getubuntu/releasenotes/810

==== To enable the Wifi LED with the Atheros cards ====

First check if this solution works on your computer. Open a terminal and run this commands:

sysctl dev.wifi0.ledpin=1
sysctl dev.wifi0.softled=3

Now connect to a wireless network and the LED should start working. If so and you want to make the changes permanent then:

1) Create a file ~/wifiLED and copy/paste the following into it:

#!/bin/bash
#
# Commands to enable the wireless LED
sysctl dev.wifi0.ledpin=1
sysctl dev.wifi0.softled=3

2) sudo cp ~/wifiLED /etc/init.d

3) sudo chmod 755 /etc/init.d/wifiLED

4) sudo update-rc.d wifiLED defaults 90

After you reboot your wireless led should be working.

--[[User:Lunatico|Lunatico]] 22:44, 18 December 2008 (CET)

=== Network connection after suspend/resume ===
Networking may not work after a suspend or resume operation, this is because of the ath_pci driver and can be worked around by creating the file {{path|/etc/pm/config.d/madwifi}} and adding the single line
<pre>
SUSPEND_MODULES=ath_pci
</pre>
which causes the driver to be unloaded on suspend and reloaded on resume.

=== Fingerprint Reader with ThinkFinger ===
Here are the general instruction on [http://www.thinkwiki.org/wiki/How_to_enable_the_fingerprint_reader_with_ThinkFinger how to enable the fingerprint reader with ThinkFinger]
Add the PPA repositories to your source.list (/etc/apt/source.list):
<pre>
deb http://ppa.launchpad.net/jon-oberheide/ubuntu intrepid main
deb-src http://ppa.launchpad.net/jon-oberheide/ubuntu intrepid main
</pre>
Update installer:
<pre>
$ sudo apt-get update
</pre>
And install:
<pre>
$ sudo apt-get install thinkfinger-tools
</pre>
From: [http://www.eastwoodzhao.com/ubuntu-810-intrepid-ibex-thinkfinger-fingerprint-reader/ Ubuntu 8.10 Intrepid Ibex - ThinkFinger Fingerprint Reader]

'''NOTE:''' Just the above didn't worked for me. [http://www.thinkwiki.org/wiki/Install_Ubuntu_Intrepid_Ibex_on_a_T61p#Fingerprint_Reader This] did worked like a charm. --[[User:Lunatico|Lunatico]] 22:53, 18 December 2008 (CET)

=== Emulate Wheel (Middle-click scrolling) ===
[http://mvogt.wordpress.com/2008/08/15/xorg-evdev-and-emulatewheel/ Michael Vogt described] how to get middle-click scrolling to work again in Intrepid. Xorg.conf is not used to configure mice and keyboards anymore, but evdev is. This makes the configuration of middle-click scrolling a little bit different than previous versions of Ubuntu. In terminal:
<pre>
sudo gedit /etc/hal/fdi/policy/mouse-wheel.fdi
</pre>
Past and save the following code, which will give vertical wheel emulation only:
<pre>
<match key="info.product" string="TPPS/2 IBM TrackPoint">
<merge key="input.x11_options.EmulateWheel" type="string">true</merge>
<merge key="input.x11_options.EmulateWheelButton" type="string">2</merge>
<merge key="input.x11_options.ZAxsisMapping" type="string">4 5</merge>
<merge key="input.x11_options.Emulate3Buttons" type="string">true</merge>
</match>
</pre>
There is [http://psung.blogspot.com/2008/09/scrolling-with-thinkpads-trackpoint-in.html another method] to get horizontal scrolling as well, but I don't think it worked for me.

[[Category: Ubuntu 8.10]]
[[Category: T61]]

Installing Ubuntu 8.10 (Intrepid Ibex) on a ThinkPad T61

2008-12-18T21:45:31Z

Lunatico: /* Items that need (some) tweaking to obtain full functionality */

NOTE: I copied the 8.04 document and created this one with the information. Please help to update it so it accurately reflects 8.10.

== Items that work out of the box ==

'''Intel Video:''' 2D and 3D acceleration works

'''Nvidia Video:''' 2D and 3D acceleration works

'''Wireless:''' Intel cards tested. Atheros cards also works.

'''Wireless WAN:''' Cingular/AT&T card tested.

'''Network Card:''' Intel 10/100/1000 tested

'''Wireless switch:''' Tested (Only has an effect over the bluetooth, wifi is unaffected)

'''Webcam:''' Tested with cheese and skype.

'''Headphones:''' Works out of the box

'''Microphone:''' Just needs to be activated, see section [[#Audio|below]]

'''Keyboard Shortcuts:''' Most of them work out of the box, some need to be activated, see section [[#Multimedia_Keys|below]]

'''Fingerprint Reader:''' With ThinkFinger, not as functional after upgrade (need to hit 'Enter'), see below

== Items that need (some) tweaking to obtain full functionality ==

=== Sound (too quiet) ===
Sound works "out of the box", but is too quiet for many people. To fix this you need to do the following:
<pre>
gksudo gedit /etc/modprobe.d/alsa-base
</pre>
and add
<pre>
options snd-hda-intel model=thinkpad
</pre>
to the very end of the file ({{path|/etc/modprobe.d/alsa-base}}).

=== Open Source Intel Wifi Driver ===
The following information is important if you are upgrading from a previous version (2007 or earlier) of Ubuntu to 8.10.

Intel has created a new Linux Wifi driver project for Intel Wireless cards, "[[Iwlwifi]]". This driver is Open Source and no longer requires the Intel daemon to run in addition. This project will support the [[:Category:T61 | T61]]'s Wifi [[Intel PRO/Wireless 3945ABG Mini-PCI Express Adapter | Intel 3945ABG network adapter]] and [[Intel PRO/Wireless 4965AGN Mini-PCI Express Adapter| Intel 4965AGN network adapter]].

An automatic migration will occur when upgrading from [[Installing Ubuntu 7.10 (Gutsy Gibbon) on a ThinkPad T61|Ubuntu 7.10]] to Ubuntu 8.04. However, there is a caveat to be aware of:
* The new driver wants to name the interface wlan0 (by default -- you can rename it to anything you want), and requires a different entry in {{path|/etc/udev/rules.d/70-persistent-net.rules}}, which handles the naming of interfaces. Simply edit this file and delete your old entry for the ipw3945 driver, then unload/reload the new driver, or simply reboot. A new entry will automatically be created that is appropriate for the new driver. Here's an example of the lines to delete:
<pre>
# PCI device 0x8086:0x4227 (ipw3945)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:1b:77:a4:0e:2f", NAME="eth1"
</pre>

If you need to perform a manual migration, the Ubuntu Help Community has written some [https://help.ubuntu.com/community/WifiDocs/Driver/iwlwifi_Intel_3945_4965/gutsy documentation] that will make this very easy to do.

An additional note
'''System lock-ups with Intel 4965 wireless'''

The version of the iwlagn wireless driver for Intel 4965 wireless chipsets included in Linux kernel version 2.6.27 causes kernel panics when used with 802.11n or 802.11g networks. Users affected by this issue can install the linux-backports-modules-intrepid package, to install a newer version of this driver that corrects the bug. (Because the known fix requires a new version of the driver, it is not expected to be possible to include this fix in the main kernel package.)
http://www.ubuntu.com/getubuntu/releasenotes/810

==== To enable the Wifi LED with the Atheros cards ====

First check if this solution works on your computer. Open a terminal and run this commands:

sysctl dev.wifi0.ledpin=1
sysctl dev.wifi0.softled=3

Now connect to a wireless network and the LED should start working. If so and you want to make the changes permanent then:

1) Create a file ~/wifiLED and copy/paste the following into it:

#!/bin/bash
#
# Commands to enable the wireless LED
sysctl dev.wifi0.ledpin=1
sysctl dev.wifi0.softled=3

2) sudo cp ~/wifiLED /etc/init.d

3) sudo chmod 755 /etc/init.d/wifiLED

4) sudo update-rc.d wifiLED defaults 90

After you reboot your wireless led should be working.

--[[User:Lunatico|Lunatico]] 22:44, 18 December 2008 (CET)

=== Network connection after suspend/resume ===
Networking may not work after a suspend or resume operation, this is because of the ath_pci driver and can be worked around by creating the file {{path|/etc/pm/config.d/madwifi}} and adding the single line
<pre>
SUSPEND_MODULES=ath_pci
</pre>
which causes the driver to be unloaded on suspend and reloaded on resume.

=== Fingerprint Reader with ThinkFinger ===
Here are the general instruction on [http://www.thinkwiki.org/wiki/How_to_enable_the_fingerprint_reader_with_ThinkFinger how to enable the fingerprint reader with ThinkFinger]
Add the PPA repositories to your source.list (/etc/apt/source.list):
<pre>
deb http://ppa.launchpad.net/jon-oberheide/ubuntu intrepid main
deb-src http://ppa.launchpad.net/jon-oberheide/ubuntu intrepid main
</pre>
Update installer:
<pre>
$ sudo apt-get update
</pre>
And install:
<pre>
$ sudo apt-get install thinkfinger-tools
</pre>
From: [http://www.eastwoodzhao.com/ubuntu-810-intrepid-ibex-thinkfinger-fingerprint-reader/ Ubuntu 8.10 Intrepid Ibex - ThinkFinger Fingerprint Reader]

=== Emulate Wheel (Middle-click scrolling) ===
[http://mvogt.wordpress.com/2008/08/15/xorg-evdev-and-emulatewheel/ Michael Vogt described] how to get middle-click scrolling to work again in Intrepid. Xorg.conf is not used to configure mice and keyboards anymore, but evdev is. This makes the configuration of middle-click scrolling a little bit different than previous versions of Ubuntu. In terminal:
<pre>
sudo gedit /etc/hal/fdi/policy/mouse-wheel.fdi
</pre>
Past and save the following code, which will give vertical wheel emulation only:
<pre>
<match key="info.product" string="TPPS/2 IBM TrackPoint">
<merge key="input.x11_options.EmulateWheel" type="string">true</merge>
<merge key="input.x11_options.EmulateWheelButton" type="string">2</merge>
<merge key="input.x11_options.ZAxsisMapping" type="string">4 5</merge>
<merge key="input.x11_options.Emulate3Buttons" type="string">true</merge>
</match>
</pre>
There is [http://psung.blogspot.com/2008/09/scrolling-with-thinkpads-trackpoint-in.html another method] to get horizontal scrolling as well, but I don't think it worked for me.

[[Category: Ubuntu 8.10]]
[[Category: T61]]

Installing Ubuntu 8.10 (Intrepid Ibex) on a ThinkPad T61

2008-12-18T21:44:12Z

Lunatico: /* Items that need (some) tweaking to obtain full functionality */

NOTE: I copied the 8.04 document and created this one with the information. Please help to update it so it accurately reflects 8.10.

== Items that work out of the box ==

'''Intel Video:''' 2D and 3D acceleration works

'''Nvidia Video:''' 2D and 3D acceleration works

'''Wireless:''' Intel cards tested. Atheros cards also works.

'''Wireless WAN:''' Cingular/AT&T card tested.

'''Network Card:''' Intel 10/100/1000 tested

'''Wireless switch:''' Tested (Only has an effect over the bluetooth, wifi is unaffected)

'''Webcam:''' Tested with cheese and skype.

'''Headphones:''' Works out of the box

'''Microphone:''' Just needs to be activated, see section [[#Audio|below]]

'''Keyboard Shortcuts:''' Most of them work out of the box, some need to be activated, see section [[#Multimedia_Keys|below]]

'''Fingerprint Reader:''' With ThinkFinger, not as functional after upgrade (need to hit 'Enter'), see below

== Items that need (some) tweaking to obtain full functionality ==

=== Sound (too quiet) ===
Sound works "out of the box", but is too quiet for many people. To fix this you need to do the following:
<pre>
gksudo gedit /etc/modprobe.d/alsa-base
</pre>
and add
<pre>
options snd-hda-intel model=thinkpad
</pre>
to the very end of the file ({{path|/etc/modprobe.d/alsa-base}}).

=== Open Source Intel Wifi Driver ===
The following information is important if you are upgrading from a previous version (2007 or earlier) of Ubuntu to 8.10.

Intel has created a new Linux Wifi driver project for Intel Wireless cards, "[[Iwlwifi]]". This driver is Open Source and no longer requires the Intel daemon to run in addition. This project will support the [[:Category:T61 | T61]]'s Wifi [[Intel PRO/Wireless 3945ABG Mini-PCI Express Adapter | Intel 3945ABG network adapter]] and [[Intel PRO/Wireless 4965AGN Mini-PCI Express Adapter| Intel 4965AGN network adapter]].

An automatic migration will occur when upgrading from [[Installing Ubuntu 7.10 (Gutsy Gibbon) on a ThinkPad T61|Ubuntu 7.10]] to Ubuntu 8.04. However, there is a caveat to be aware of:
* The new driver wants to name the interface wlan0 (by default -- you can rename it to anything you want), and requires a different entry in {{path|/etc/udev/rules.d/70-persistent-net.rules}}, which handles the naming of interfaces. Simply edit this file and delete your old entry for the ipw3945 driver, then unload/reload the new driver, or simply reboot. A new entry will automatically be created that is appropriate for the new driver. Here's an example of the lines to delete:
<pre>
# PCI device 0x8086:0x4227 (ipw3945)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:1b:77:a4:0e:2f", NAME="eth1"
</pre>

If you need to perform a manual migration, the Ubuntu Help Community has written some [https://help.ubuntu.com/community/WifiDocs/Driver/iwlwifi_Intel_3945_4965/gutsy documentation] that will make this very easy to do.

An additional note
'''System lock-ups with Intel 4965 wireless'''

The version of the iwlagn wireless driver for Intel 4965 wireless chipsets included in Linux kernel version 2.6.27 causes kernel panics when used with 802.11n or 802.11g networks. Users affected by this issue can install the linux-backports-modules-intrepid package, to install a newer version of this driver that corrects the bug. (Because the known fix requires a new version of the driver, it is not expected to be possible to include this fix in the main kernel package.)
http://www.ubuntu.com/getubuntu/releasenotes/810

=== Network connection after suspend/resume ===
Networking may not work after a suspend or resume operation, this is because of the ath_pci driver and can be worked around by creating the file {{path|/etc/pm/config.d/madwifi}} and adding the single line
<pre>
SUSPEND_MODULES=ath_pci
</pre>
which causes the driver to be unloaded on suspend and reloaded on resume.

=== Fingerprint Reader with ThinkFinger ===
Here are the general instruction on [http://www.thinkwiki.org/wiki/How_to_enable_the_fingerprint_reader_with_ThinkFinger how to enable the fingerprint reader with ThinkFinger]
Add the PPA repositories to your source.list (/etc/apt/source.list):
<pre>
deb http://ppa.launchpad.net/jon-oberheide/ubuntu intrepid main
deb-src http://ppa.launchpad.net/jon-oberheide/ubuntu intrepid main
</pre>
Update installer:
<pre>
$ sudo apt-get update
</pre>
And install:
<pre>
$ sudo apt-get install thinkfinger-tools
</pre>
From: [http://www.eastwoodzhao.com/ubuntu-810-intrepid-ibex-thinkfinger-fingerprint-reader/ Ubuntu 8.10 Intrepid Ibex - ThinkFinger Fingerprint Reader]

=== Emulate Wheel (Middle-click scrolling) ===
[http://mvogt.wordpress.com/2008/08/15/xorg-evdev-and-emulatewheel/ Michael Vogt described] how to get middle-click scrolling to work again in Intrepid. Xorg.conf is not used to configure mice and keyboards anymore, but evdev is. This makes the configuration of middle-click scrolling a little bit different than previous versions of Ubuntu. In terminal:
<pre>
sudo gedit /etc/hal/fdi/policy/mouse-wheel.fdi
</pre>
Past and save the following code, which will give vertical wheel emulation only:
<pre>
<match key="info.product" string="TPPS/2 IBM TrackPoint">
<merge key="input.x11_options.EmulateWheel" type="string">true</merge>
<merge key="input.x11_options.EmulateWheelButton" type="string">2</merge>
<merge key="input.x11_options.ZAxsisMapping" type="string">4 5</merge>
<merge key="input.x11_options.Emulate3Buttons" type="string">true</merge>
</match>
</pre>
There is [http://psung.blogspot.com/2008/09/scrolling-with-thinkpads-trackpoint-in.html another method] to get horizontal scrolling as well, but I don't think it worked for me.

==== To enable the Wifi LED with the Atheros cards ====

First check if this solution works on your computer. Open a terminal and run this commands:

sysctl dev.wifi0.ledpin=1
sysctl dev.wifi0.softled=3

Now connect to a wireless network and the LED should start working. If so and you want to make the changes permanent then:

1) Create a file ~/wifiLED and copy/paste the following into it:

#!/bin/bash
#
# Commands to enable the wireless LED
sysctl dev.wifi0.ledpin=1
sysctl dev.wifi0.softled=3

2) sudo cp ~/wifiLED /etc/init.d

3) sudo chmod 755 /etc/init.d/wifiLED

4) sudo update-rc.d wifiLED defaults 90

After you reboot your wireless led should be working.

--[[User:Lunatico|Lunatico]] 22:44, 18 December 2008 (CET)

[[Category: Ubuntu 8.10]]
[[Category: T61]]

Installing Ubuntu 8.04 (Hardy Heron) and Ubuntu 8.10 (Intrepid Ibex) on a ThinkPad X200

2008-12-08T12:47:56Z

Lunatico: /* Sensors */

==Overview==

Some items in this page still date from before the 8.10 final release. Please keep a close eye out, and if needed, refer to [http://ubuntuforums.org/showthread.php?p=5897839 this X200 owners' thread] on the Ubuntu forums.

Started off working w. Ubuntu 8.04 install using the optical drive in the X200 ultrabase. Everything went swimmingly - ethernet worked out of the box as did the optical drive itself.

Wound up upgrading to the 8.10 beta b/c of wireless troubles. See below.

==Ultrabay==

Handles install without any problem - note: while the machine is in the bay, it forces you to use the ethernet port on the bay.

==Ethernet==

Intel GigE worked out of the box w. 8.04 and 8.10.

==Wireless==

Ah, the wireless.

run <lshw -C network> and sort out which wireless hardware you're working with.

===Atheros===

For Atheros, check out [http://ubuntuforums.org/showthread.php?t=905126 this forum post]

===Intel 5300===

====On 8.04====

For Intel 5300 on 8.04, neither the recommended drivers (iwl5000) nor ndiswrapper did the trick. It's possible that manually-upgrading the kernel to 2.27 would do it.

====On 8.10====

With 8.10 the Intel 5300 works out of the box. Running <lshw -C network> again shows that it's the iwlagn driver (pre-loaded with the 2.27 kernel) that does the trick.

== Sensors ==

The gnome sensors applets allow you to monitor all important temperatures, including battery, hdd, cpu and gpu and system fan.
sudo apt-get install sensors-applet hddtemp

Add the hardware sensor monitor to the panel and then configure it. You will see a lot of datasources.

* libsensors: temp9 and temp10 seem to be mainboard/Nortbridge or power regulator sensors.
* hddtemp: /dev/sda is the sensor of the harddisk. It is important to keep the harddisk always below 45°, normally under 40°. This is no problem with the X200, the hdd cooling system seems to be very good.
* ibm-acpi: cpu, mPCI, GPU and FAN are intersting sensors.

==Power Mgmt==

Not sure what's going on here yet, but the battery claims to have only ~3 hours of life after a full charge.

The "laptop" mode is by default disabled in ubuntu (for some historical weird hang up, I guess). To enable it, edit the file:

/etc/default/acpi-support

Change the following line:

ENABLE_LAPTOP_MODE=false

to be:

ENABLE_LAPTOP_MODE=true

Then your battery can provide you with some extra time (about half an hour~one hour). You can also enable it through [http://www.lesswatts.org/projects/powertop/ powertop] together with other tweaks. So far no hang is observed.

==Display==

With 8.10 things don't work well if you stick with the "preconfigured" xorg.conf settings: the default resolution is only 1074x768 and the highest setting that the laptop display is capable of (1280x800) doesn't even show up in the System -> Preferences -> Screen Resolution applet. To make matters worse, VGA output is a royal pain.

Here's a step-by-step guide to improve the situation if you just want to get the laptop display working properly:

* First, make sure you've got the latest drivers for your Intel 4500MHD video card:

$ sudo apt-get install xserver-xorg-video-intel

* Once that's over and done with, open up your xorg.conf file (note: be careful with this file):

$ sudo gedit /etc/X11/xorg.conf

* Make the part that isn't commented out (i.e. that isn't preceded by a #) look like this:

Section "Monitor"
Identifier "Configured Monitor"
EndSection

Section "Monitor"
Identifier "HDMI-1"
Option "Ignore" "True"
EndSection

Section "Monitor"
Identifier "HDMI-2"
Option "Ignore" "True"
EndSection

Section "Screen"
Identifier "Default Screen"
Monitor "Configured Monitor"
Device "Configured Video Device"
DefaultDepth 24
SubSection "Display"
Modes "1280x800" "1024x768"
# The following line was an auto-configuration added by an external VGA projector; you might leave it out to try
# letting the system detect dimensions appropriate for whatever display you happen to use.
Virtual 2432 864
EndSubSection
EndSection

Section "Device"
Identifier "Configured Video Device"
Driver "intel"
Option "monitor-HDMI-1" "HDMI-1"
Option "monitor-HDMI-2" "HDMI-2"
EndSection

* Note: those HDMI settings are really important because they get rid of some imaginary monitors (see [[Installing_Debian_on_an_X200 | this other X200 installation notes post]] for more details). Save your new xorg.conf file and quit the Gedit text editor. Also quit any other open programs and log-out from your session to reset the X-server and apply the new settings.

* When you log back in, all the new settings should "just work," but don't be alarmed if things look a little weird or if the screen resolution still isn't the full 1280x800...
:To make sure the xorg.conf changes "stuck" and that the resolution is set properly, open the aforementioned Screen Resolution applet: System -> Preferences -> Screen Resolution. Make sure the the box that says "Mirror Screens" is unchecked and click the "Detect Displays" button. In the little colorful diagram thingy, there should just be a big rectangle that says "laptop 12"" (or whatever portion of those words fits in the rectangle). Click on this "laptop" rectangle to make sure and activate it. Once you've clicked on it, look for the drop-down menu that says the resolution and re-set this to "1280 x 800 (16:10)." If there are other "imaginary" displays activated (there shouldn't be with the HDMI workaround in the xorg.conf file included above) use the same drop-down menu to turn them to "Off." Click "Apply" at the bottom and close the applet. Log out again to activate the new settings. If all goes according to plan, your 12800x800 display should now work like a charm!

* Once you've got that all sorted out, go ahead and hook the X200 up to an external display via the VGA port (so far, I've only tried it directly from the laptop and not from the ultrabase). Open the Screen Resolution applet again and click "detect displays." Choose a resolution for the external display and decide whether you want a mirrored output or not. Click apply (here the system may prompt you to accept virtual display settings - say yes and confirm by typing your password), close the applet and log-out again to reset X. Once you log in, you should have an external display working perfectly.

==Suspend and Hibernate==

There will be conflicting reports and confusion about this, because there is at least one problem causing ''intermittent'' suspend/hibernate crashes. In other words, things may appear to work, and then they may not.

If you experience a crash while resuming (my guess is that you will, eventually), first attempt the fix described here:

[[Install_Ubuntu_8.10_(Intrepid_Ibex)_on_an_T400#Suspend.2FHibernate|Workaround on T400]]

Apparently, this is a mulitprocessor problem, and the workaround to disable one core at Suspend/Hibernate is relatively easy to implement.

'''Confirmations:'''

On a up to date 8.10 system (as of Nov 12th: linux-2.6.27-8, video-intel-2.4.1ubuntu10) suspend now seems to work perfectly. Before the above multi-processor workaround, resuming from suspend used to crash about half of the time. Not a single crash has been observed since the workaround.

Seconded; this appeared to fix it for me as well (12/2/08), on a fully updated 8.10, with no other modifications to stock.

Additional information about various potential fixes is included below for reference, though I didn't (so far) need to do anything aside from what's described above.

'''Older workarounds:'''

Without tweaking drivers and xorg.conf suspending thcrough the Gnome desktop does not work - seems to be related to the problems with the display. Some people have reported no problems with Hibernate, while others...you get the idea. If you're one of those having problems, read on...

Once you've followed the instructions to get the Intel video card drivers installed (see above) Hibernate (suspend to disk) *should* work and Sleep/Suspend (suspend to RAM) *might* work (there are some conflicting reports out there). If you like, you can examine/tweak the settings in system -> preferences -> power management.

If the suspend/sleep still doesn't work, try the following work-around to get the system to recognize the sleep settings.

First, create a text file called "sleep_module" in the /etc/pm/config.d directory:

sudo gedit /etc/pm/config.d/sleep_module

In the new file, enter:

SLEEP_MODULE=kernel

Then save this new file and exit your text editor as well as your other apps. Do a reboot and try out your freshly reconfigured suspend funciton. As before, you can examine/tweak the settings in system -> preferences -> power management.

Note: Consider using "sudo -e" for editing files.

'''Update:''' The latest updates to 8.10 (still in beta at the time of this writing) appear to include a sleep_module configuration file that includes this tweak.

I had lots of problems with both hibernate and suspend. I have disabled lots of (for me at least) unneeded devices in the bios, and now at least hibernat works. My x200 bios configuration is now like this:

* Network
* wake on lan disabled
* flash over lan disabled
* ethernet lan option rom disabled
* hdd dma enabled
* wireless lan and wimax enabled
* SATA AHCI
* CPU
* multiprocessing enabled
* intel virtualisation enabled
* intel vt-d enabled
* Intel AMT
* AMT Control disabled
* IO Port access
* ethernet enabled
* wlan enabled
* wimax enabled
* wwan enabled
* bluetooth enabled
* wireless usb disabled
* modem disabled
* usb enabled
* expresscard slot disabled
* ultrabay hdd disabled
* memory card disabled
* camera enabled
* microphone enabled
* fingerprint reader disabled

I left the rest at bios defaults. Of course, you may one some of these devices enabled, but this is a starting point to get hibernate/suspend working and by enabling one after the other you should be able to find the device/s that cause problems.

Note: with this setup i get 4h30min battery time instead of 3h55min

===Hibernate fails with Virtualbox running===

-> http://ubuntuforums.org/showpost.php?p=4582777&postcount=3

To circumvent this, put this in ~/bin/vbox_suspend:

#!/bin/bash
for x in `vboxmanage -nologo list runningvms`
do
vboxmanage -nologo controlvm $x savestate
done

and make it executable. you can test it by running ~/bin/vbox_suspend, which should save all your running virtual machines.

put the following lines in /etc/pm/sleep.d/90virtualbox and make it executable as well:

#!/bin/bash
case $1 in
hibernate)
su YOURUSER -c /home/YOURUSER/bin/vbox_suspend
;;
esac

This is not very elegant (as the user is hard-coded), but it works.
I have tried to make the machines resume on thaw, but it would place the vms on the wrong workspace even if it know which X server to use, which it doesn't.

==Sound==

(Mostly) works out of the box under 8.04 and 8.10

Worth noting the apparent problems w. Skype and Medibuntu on 8.10 - some of this [http://ubuntuforums.org/showthread.php?t=925211 appears to have been resolved] recently and will hopefully make it into the final release. Sound playback within Skype still failing despite the workaround.

==Camera==

Works with Cheese Webcam Booth on 8.10. Also with Kopete on 8.10.

==VGA==

"Unclaimed"
[[Category:X200]]

==Tablet==

The X200 Tablet uses a wacom device. The instructions for configuring xorg in 8.10 to work with wacom input do seem to work.

https://help.ubuntu.com/community/WacomTroubleshooting

Just follow the directions for a SERIAL tablet (which is indeed what you have).

Here is an xorg.conf that has both the resolution fix and the tablet fixes (tested on 8.10 with an X200 tablet, multitouch - i.e. pen and fingertip - screen):

Section "InputDevice"
Driver "wacom"
Identifier "stylus"
Option "Device" "/dev/ttyS0" # SERIAL ONLY
Option "Type" "stylus"
Option "ForceDevice" "ISDV4" # Tablet PC ONLY
EndSection

Section "InputDevice"
Driver "wacom"
Identifier "eraser"
Option "Device" "/dev/ttyS0" # SERIAL ONLY
Option "Type" "eraser"
Option "ForceDevice" "ISDV4" # Tablet PC ONLY
EndSection

Section "InputDevice"
Driver "wacom"
Identifier "cursor"
Option "Device" "/dev/ttyS0" # SERIAL ONLY
Option "Type" "cursor"
Option "ForceDevice" "ISDV4" # Tablet PC ONLY
EndSection

Section "InputDevice"
Driver "wacom"
Identifier "pad"
Option "Device" "/dev/ttyS0" # SERIAL ONLY
Option "Type" "pad"
EndSection

# Uncomment the following section if you you have a TabletPC that upports touch
Section "InputDevice"
Driver "wacom"
Identifier "touch"
Option "Device" "/dev/ttyS0" # SERIAL ONLY
Option "Type" "touch"
Option "ForceDevice" "ISDV4" # Serial Tablet PC ONLY
# Adding manual calibration, since proper calibration seems impossible.
Option "BottomX" "915"
Option "BottomY" "940"
Option "TopX" "48"
Option "TopY" "90"
EndSection

Section "Monitor"
Identifier "Configured Monitor"
EndSection

Section "Monitor"
Identifier "HDMI-1"
Option "Ignore" "True"
EndSection

Section "Monitor"
Identifier "HDMI-2"
Option "Ignore" "True"
EndSection

Section "Screen"
Identifier "Default Screen"
Monitor "Configured Monitor"
Device "Configured Video Device"
DefaultDepth 24
SubSection "Display"
Modes "1280x800" "1024x768"
EndSubSection
EndSection

Section "Device"
Identifier "Configured Video Device"
Driver "intel"
Option "monitor-HDMI-1" "HDMI-1"
Option "monitor-HDMI-2" "HDMI-2"
EndSection

Section "ServerLayout"
Identifier "Default Layout"
Screen "Default Screen"
InputDevice "stylus" "SendCoreEvents"
InputDevice "eraser" "SendCoreEvents"
InputDevice "cursor" "SendCoreEvents" # For non-LCD tablets only
InputDevice "pad" # For Intuos3/CintiqV5/Graphire4/Bamboo tablets
InputDevice "touch" "SendCoreEvents" # Only a few TabletPCs support this typeEndSection
EndSection

You may also want to download the "wacom-tools" package.

When I started experimenting with this, the touchscreen portion of multitouch was quite miscalibrated, and the distro's wacom-tools package has a bug which seems to prevent calibration of the touchscreen via wacomcpl. In fact, it seems to have a series of bugs, judging based on what I've found in google. My solution was to futilely experiment with various xsetwacom values (as documented [http://linuxwacom.sourceforge.net/index.php/howto/xsetwacom here]) for a few minutes, and then try the values [http://dkukawka.blogspot.com/2008/07/lenovo-thinkpad-x61t-touch-support.html posted by an X61t user]. :) These were close enough to be a starting point. Then I fiddled some more, and the results are included in the xorg.conf above. With luck, these numbers will just work for you, and you won't have any issue. If not, check out the linux wacom documentation and experiment with new calibration values via xsetwacom.

==TrackPoint==

Trackpoint scrolling is, as of 12/02/08, not in a good way on 8.10.

There are numerous instructions on the net which don't work for the X200, including instructions here ([How to configure the TrackPoint]).

On the X200, the HAL-based instructions in the last section may work, but only until suspend/resume or VT switching, due to a [https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/282387|known bug in evdev].

I do have it working, but it is not pretty:

* Create a patched evdev. The following is based on instructions from the bug report. These instructions will be extremely fragile - they work for me today but could stop working at any point, based on updates to evdev or changes to the bug. The lines below do the following:
** Set up a work area
** Download the patch from the bug report
** Prepare your environment for building evdev
** Download the evdev sources
** Patch them
** Produce a new deb
** Install it

sudo bash
cd /usr/local/src/
mkdir evdev
cd evdev
wget http://launchpadlibrarian.net/19254960/preinit.diff
apt-get build-dep xserver-xorg-input-evdev
apt-get source xserver-xorg-input-evdev
cd xserver-xorg-input-evdev-2.0.99+git20080912
patch -p1 < ../preinit.diff
debian/rules binary
cd ..
dpkg -i xserver-xorg-input-evdev_2.0.99*.deb

* Add xinput lines to your .profile; with this patch, the normal HAL method no longer works (though note, I have not tested this with no hal policy for the trackpoint at all, just left the non-working one in place. YMMV).

# TEMPORARY FIX FOR BROKEN EVDEV/HAL for TrackPoint scrolling:
xinput set-int-prop "TPPS/2 IBM TrackPoint" "Wheel Emulation" 8 1
xinput set-int-prop "TPPS/2 IBM TrackPoint" "Wheel Emulation Button" 8 2
xinput set-int-prop "TPPS/2 IBM TrackPoint" "Wheel Emulation Y Axis" 8 4 5

* reboot your system.

This _should_ enable trackpoint scrolling that will be durable through suspend/resumes.

At some point they will fix the upstream evdev package, and/or adjust other configs. You may see this suddenly stop working after an update (evdev was updated but this fix wasn't in the update); in which case, re-run the steps above to create an updated patched evdev (hopefully). Or the update may carry an upstream fix; latest word in the bug is that the unstable upstream debian packages work out of the box. In which case you should simply come back and reexamine whether the xinput lines in the .profile are still necessary at a later date, or you can use the more canonical HAL profile to control the trackpoint properties.

==Rotating the Screen==

A classic gripe of linux tablet users is that they can rotate the screen but the digitizer does not rotate with it automatically. This can render the portrait "tablet" configuration useless.

The wacom driver actually has the capability to rotate as well. A script has been developed to both rotate the display and the wacom driver:

http://www.thinkwiki.org/wiki/Wacom_Serial_Tablet_PC_Stylus

The last version of the script (for linuxwacom 8.1) appears to work on the x200, in 8.10, after using the other xorg display and wacom modifications above.

''However'' after a few days I have noticed some instability and odd behaviour with it. If anyone would like to have a look at it, please feel free to post a correction here.

Once you have copied the script to your local system, you can use the normal key binding facilities in gnome or kde to bind your rotation key to it.

If anyone has any idea how to receive and act automatically on signals from the sensor inside the x200 tablet's screen hinge, please post it!

==Fan==

'''WARNING: USE AT YOUR OWN RISK'''

Monitor the temperatures of harddisk, gpu and cpu when controlling fan speed.

Software fan control is dangerous, and can shorten the life of a laptop or even destroy it. For a detailed discussion and warning from the kernel maintainer, see [http://www.nabble.com/tpfand-configuration-for-an-X200s-td20777095.html this thread, which happens to be an X200s user asking for help].

As reported elsewhere, the fan seems to run constantly while the machine is on under 8.04 and 8.10 (though not at 100% speed).

The fan can be made less noisy by installing the tpfand packages.

* First add the tpfand repository. Instructions are [http://www.gambitchess.org/mediawiki/index.php/ThinkPad_Fan_Control here]

* Then install the packages.

sudo apt-get install tpfand tpfand-admin

There is currently no tpfand profile for the x200, but you can set the thresholds and power settings for all fans easily with the thinkpad fan control software. Here are the settings from my /etc/tpfand.conf as a starting point. Use the sensors applet to control and monitor temperatures of cpu, gpu and harddisk (see below)!

#...
0. CPU = 0:0 50:7
1. Mini PCI = 0:0 55:4
2. Sensor 2 = 0:255
3. GPU = 0:0 55:5
4. Bat0 = 0:0 35:3
5. Sensor 5 = 0:255
6. Bat1 = 0:0 35:3
7. Sensor 7 = 0:255
8. MB? = 0:0 45:2
9. MB? = 0:0 55:3
10. Sensor 10 = 0:255
11. Sensor 11 = 0:255
12. Sensor 12 = 0:255
13. Sensor 13 = 0:255
14. Sensor 14 = 0:255
15. Sensor 15 = 0:255
#...

These settings achieve the following:
* fan runs at 15% if the system is idle. This is very quiet, while still having airflow through the system
* if MB2>55° or BAT>35°, fan runs at 30%
* if MiniPCI>55° fan 45%
* if GPU>55 fan 60%
* if CPU>50 fan 90%
The net effect is that a busy system will run the fan between 45%-90% depending on load.

The above settings are for the X200 (without an s) as is all the information on this page. Don't know why somebody messes this page up with stuff about the X200s and sinister warnings.

(Warnings are cheap. New laptops are not. When you have a '''"sinister warning"''' about tpfand from [http://www.nabble.com/tpfand-configuration-for-an-X200s-td20777095.html the maintainer of the thinkpad fan code in the kernel himself], I don't know why this section is even here - it's not safe. Even so I say leave it, but just make sure there is a big warning.)

The sensor names were deduced by matching sensor readings between tpfand and acpi temperatures.

Thermal Sensors

2008-08-11T10:34:37Z

Lunatico: /* ThinkPad {{T61}} */

{| width="100%"
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__
|style="vertical-align:top" |
This page summarizes known information about the locations and properties of thermal sensors on ThinkPad laptops.
|}

==Accessing the sensors==

===Basic ACPI system temperature sensors===
The primary means of accessing the thermal sensors is through the [[ibm-acpi]] module. Up to Linux 2.6.19, ibm-acpi supported only 8 sensors, but since Linux 2.6.20-rc2, up to 16 sensors are supported. When the module is loaded, the sensors (some of which may be inactive) are shown in {{path|/proc/acpi/ibm/thermal}}:

:{{cmdroot|cat /proc/acpi/ibm/thermal}}
:{{cmdresult|temperatures: 44 41 33 42 33 -128 30 -128}}

A value of -128 (i.e., 0x80 hex) means the sensor is not connected. For example, above the two -128 values belong to the UltraBay battery, which is not plugged in.

If the ThinkPad supports the extended sensor set, eight more values will be displayed:

:{{cmdroot|cat /proc/acpi/ibm/thermal}}
:{{cmdresult|temperatures: 44 41 33 42 33 -128 30 -128 48 50 49 -128 -128 -128 -128 -128}}

====Patch for accessing the extra ACPI sensors through <tt>thermal</tt>====
If you don't use a recent-enough [[ibm-acpi]], you can patch it to make the extra 3 sensors show up on {{path|/proc/acpi/ibm/thermal}} just like the 8 basic sensors, apply the {{CodeRef|ibm_acpi-extra-thermal.patch}} kernel patch to [[ibm-acpi]].

Then:

:{{cmdroot|cat /proc/acpi/ibm/thermal}}
:{{cmdresult|temperatures: 44 41 33 42 33 -128 30 -128 40 48 43}}

If you apply this patch in conjunction with [[ACPI_fan_control_script#Comprehensive_bash_script_with_fine_control_over_fan_speed|tp-fancontrol]], you'll need tp-fancontrol 0.2.9 or newer.

===Accessing the thermal sensors through <tt>ecdump</tt>===
Load [[ibm-acpi]] with the <tt>experimental=1</tt> option, and parse {{path|/proc/acpi/ibm/ecdump}}. The 8 basic sensors are on offsets 0x78-0x7f, and the extended sensors (if supported) are on offsets 0xc0-0xc7.

To read the first three extended sensors:
:{{cmdroot|perl -ne 'm/^EC 0xc0: .(..) .(..) .(..) / or next; print hex($1)." ".hex($2)." ".hex($3)."\n"' < /proc/acpi/ibm/ecdump}}
:{{cmdresult|40 48 43}}

Future models might provide additional extra sensors beyond those three. To see all candidates:
:{{cmdroot|perl -ne 'print join(" ",map(hex,m/\w+/g))."\n" if s/^EC 0xc0://' < /proc/acpi/ibm/ecdump}}
:{{cmdresult|40 48 43 128 128 128 128 128 0 0 0 0 0 0 0 0}}

{{WARN|'''ecdump''' is not a playground, and even just reading it causes side-effects to the ThinkPad. The ibm-acpi maintainer wants to make it clear that he considers it a very dumb idea to use ecdump constantly in a script}}

===HDAPS temperature sensor===
The [[Active Protection System]] accelerometer also reports a temperature, which is identical to one of the ACPI sensors. The corresponding sensor is actually not inside the HDAPS chip, but fairly close.
:{{cmdroot|cat /sys/bus/platform/drivers/hdaps/hdaps/temp1}}
:{{cmdresult|41}}

===Harddisks SMART temperature sensor===
The system hard disk temperature can be read through the disk's SMART interface:
:{{cmdroot|<nowiki>smartctl -A /dev/hda | grep Temperature</nowiki>}}
:{{cmdresult|194 Temperature_Celsius 0x0022 145 097 000 Old_age Always - 31}}

Or, for SATA-equipped models running a recent Linux kernel (see [[Problems with SATA and Linux]]):

:{{cmdroot|<nowiki>smartctl -A -d ata /dev/sda | grep Temperature</nowiki>}}
:{{cmdresult|194 Temperature_Celsius 0x0022 145 097 000 Old_age Always - 31}}

When the [[UltraBay Slim HDD Adapter]] or [[UltraBay Slim SATA HDD Adapter]] are used, the second hard disk will typically provide another temperature readout via its SMART interface, analogously to the above.

Reading this sensor will typically cause a drive spin-up and head unload.

===Hitachi harddisks <tt>SENSE CONDITION</tt> temperature sensor===

Recent Hitachi disks provide a non-standard <tt>SENSE CONDITION</tt> command which reads the disk temperature without causing a spin-up or head load. The reported value is the same as when using SMART. This can be invoked, e.g., using {{cmdroot|hdparm -H}}, or the relevant code in {{CodeRef|tp-fancontrol}}. When using the <tt>libata</tt> driver, this requires kernel >= 2.6.19-rc1.

==Utilities for viewing temperatures==

The following utilities display the ThinkPad-specific thermal sensor readouts:
* The above shell commands.
* The "Sensors" builtin of [[GKrellM]] can show 6 specific ACPI sensors (out of up to 11).
* [http://www.elliptique.net/~ken/kima/ Kima] is a KDE applet that can display the 8 first ACPI sensors as well as the HDAPS sensor.
* [http://www.kraus.tk/projects/IBMDoK/ IBMDoK], another KDE applet. Shows 4 specific sensors (out of up to 11). So far only tested at the {{T60}}.
* There is an [http://munin.projects.linpro.no/wiki/plugin-ibm_acpi ibm_acpi plugin] for [http://munin.projects.linpro.no/ Munin].
* [http://sensors-applet.sourceforge.net/ GNOME Sensors Applet] supports ibm_acpi.

==Sensor locations==
This information is model specific.

===ThinkPad {{A31}}===
Found by Milos Popovic using cooling spray to cool down components on a completely removed, running motherboard, to locate the sensors. Also reported [http://forum.thinkpads.com/viewtopic.php?t=31837 here].
EC offset Index in "thermal" Location (estimated)
0x78 1 CPU
0x79 2 Battery (this one heats up when on battery power)
0x7A 3 Power (sensor near power diodes and CPU; heats up when high power consumption, has crosstalk from CPU)
0x7B 4 Ultrabay 2000 battery?
0x7C 5 Northbridge (sensor next to Northbridge, also somewhat near GPU)
0x7D 6 PCMCIA/ambient (sensor is a National Semiconductor LM75 Digital Temperature Sensor/Thermal Watchdog chip
next to the 9-pin VGA connector; sits right under PCMCIA slots but doesn't touch)
0x7E 7 Battery (this one stays near ambient temperature, even when on battery power)
0x7F 8 Ultrabay 2000 battery?
0xC0 none zero
0xC1 none zero
0xC2 none zero
The following photos (resolution reduced for server space) show the locations found for the listed temperature sensors.
{{gallery_start}}
{{thumb|A31_2652M3U_systemboardtop_DSCN6105_tempsensors_lores.jpg|ThinkPad A31 sensor locations on top of motherboard.}}
{{thumb|A31_2652M3U_systemboardbottom_DSCN6105_tempsensors_lores.jpg|ThinkPad A31 sensor locations on bottom of motherboard.}}
{{gallery_end}}
On this A31 systemboard (FRU 26P8398), there is a [http://www.maxim-ic.com/quick_view2.cfm/qv_pk/2313 Maxim MAX1668] 5-channel remote/local temperature sensor (4 remote + 1 self temperature) on top of the systemboard, and a [http://www.national.com/pf/LM/LM75.html National Semiconductor LM75] single-channel "digital temperature sensor and thermal watchdog" chip. It would appear that the LM75 has the ability to hard shutdown the processor (without software intervention) if its temperature exceeds a given threshold. I'm not sure if it is wired for this, nor whether the Thinkpad changes the threshold temperature from the chip's power-up default of 80Â°C. A software application with drivers on the LM75 webpage is available that claims to allow direct access to the thermal sensor chip (this hasn't been tried, but could be useful in other models to determine if this sensor is somewhere on the MB, and which register it corresponds to). The MAX1668's self-temperature reading does not appear anywhere in the above temperature registers; it's not clear whether it is read at all, and whether it is to be found elsewhere in the EC memory. These two chips (LM75 and MAX1668) account for some of the sensors.

===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 System battery
0x7D 6 UltraBay battery
0x7E 7 System battery
0x7F 8 UltraBay battery
0xC0 none ?
0xC1 none ?
0xC2 none ?

===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 {{T43}}, {{T43p}}===
Found by Shmidoax using cooling spray to cool down components and observe the effect on the sensors.
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 System battery (front left = charging circuit)
0x7D 6 UltraBay battery
0x7E 7 System battery (rear right)
0x7F 8 UltraBay battery
0xC0 none Bus between Northbridge and DRAM; Ethernet chip
0xC1 none Southbridge, WLAN and clock generator (under Mini-PCI card, under touchpad)
0xC2 none Power circuitry, on underside of system board under F2 key
{{gallery_start}}
{{thumb|T43-thermal-sensors.jpg|ThinkPad T43 sensor locations}}
{{thumb|T43-2668-thermal-sensors-zoom.jpg|ThinkPad T43 sensor locations detail}}
{{thumb|T43p-H8S2161.jpg|ThinkPad T43/p 26xx Embedded Controller Renesas H8S/2161BV}}
{{gallery_end}}

===ThinkPad {{T60}}===
Found by Marco Kraus for use in [http://www.kraus.tk/projects/IBMDoK/ IBMDok].
EC offset Index in "thermal" Location (estimated)
0x78 1 CPU 0
0x79 2 HDD
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 ?

The CPU thermal sensors seem to be exposed in both {{path|/proc/acpi/thermal_zone/THM0/temperature}} and {{path|/proc/acpi/thermal_zone/THM1/temperature}}, though the latter curiously seems to exist only in this file and nowhere in {{path|/proc/acpi/ibm/ecdump}}.

===ThinkPad {{T61}}===
Found By Daniel Castro. There are two sensors for the battery but I'm not sure of the difference or exact location of them. There are still 3 sensors that I couldn't figure out. If anyone can help please update it.

Index in "thermal" Location
1 CPU
2 MiniPCI
3 HDD
4 n/a (-128)
5 Battery 1
6 n/a (-128)
7 Battery 2
8 n/a (-128)
9 ?
10 ?
11 ?
12 n/a (-128)
13 n/a (-128)
14 n/a (-128)
15 n/a (-128)
16 n/a (-128)

The reading for Battery 1 is always 50C, even right after turning the computer on, and it never seems to change, so I monitor the other one.

--[[User:Lunatico|Lunatico]] 23:44, 10 August 2008 (CEST)

===ThinkPad {{X31}}===
I figured these out by myself ([[User:BDKMPSS|BDKMPSS]]), as there are just a few available, this wasn't a huge problem. I verified my presumptions with a contactless thermometer.
EC offset Index in "thermal" Location (estimated)
0x78 1 CPU
0x79 2 n/a
0x7A 3 GPU?
0x7B 4 near or the ICH4M Southbrige, on the back of the Motherboard
0x7C 5 Battery
0x7D 6 Extended-Life-Battery; may also UltraBay battery
0x7E 7 Battery
0x7F 8 Extended-Life-Battery; may also UltraBay battery
0xC0 none n/a
0xC1 none n/a
0xC2 none n/a

0x7A "GPU?" is pretty hot and seems like the GPU, but as the Chipset and the GPU are cooled with the same heatsink it is difficult to separate them without roasting the machine. However the left and GPU side of the heatsink is much closer to the shown value than the right Chipset side.

Thermal Sensors

2008-08-10T21:44:36Z

Lunatico: /* ThinkPad {{T60}} */

{| width="100%"
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__
|style="vertical-align:top" |
This page summarizes known information about the locations and properties of thermal sensors on ThinkPad laptops.
|}

==Accessing the sensors==

===Basic ACPI system temperature sensors===
The primary means of accessing the thermal sensors is through the [[ibm-acpi]] module. Up to Linux 2.6.19, ibm-acpi supported only 8 sensors, but since Linux 2.6.20-rc2, up to 16 sensors are supported. When the module is loaded, the sensors (some of which may be inactive) are shown in {{path|/proc/acpi/ibm/thermal}}:

:{{cmdroot|cat /proc/acpi/ibm/thermal}}
:{{cmdresult|temperatures: 44 41 33 42 33 -128 30 -128}}

A value of -128 (i.e., 0x80 hex) means the sensor is not connected. For example, above the two -128 values belong to the UltraBay battery, which is not plugged in.

If the ThinkPad supports the extended sensor set, eight more values will be displayed:

:{{cmdroot|cat /proc/acpi/ibm/thermal}}
:{{cmdresult|temperatures: 44 41 33 42 33 -128 30 -128 48 50 49 -128 -128 -128 -128 -128}}

====Patch for accessing the extra ACPI sensors through <tt>thermal</tt>====
If you don't use a recent-enough [[ibm-acpi]], you can patch it to make the extra 3 sensors show up on {{path|/proc/acpi/ibm/thermal}} just like the 8 basic sensors, apply the {{CodeRef|ibm_acpi-extra-thermal.patch}} kernel patch to [[ibm-acpi]].

Then:

:{{cmdroot|cat /proc/acpi/ibm/thermal}}
:{{cmdresult|temperatures: 44 41 33 42 33 -128 30 -128 40 48 43}}

If you apply this patch in conjunction with [[ACPI_fan_control_script#Comprehensive_bash_script_with_fine_control_over_fan_speed|tp-fancontrol]], you'll need tp-fancontrol 0.2.9 or newer.

===Accessing the thermal sensors through <tt>ecdump</tt>===
Load [[ibm-acpi]] with the <tt>experimental=1</tt> option, and parse {{path|/proc/acpi/ibm/ecdump}}. The 8 basic sensors are on offsets 0x78-0x7f, and the extended sensors (if supported) are on offsets 0xc0-0xc7.

To read the first three extended sensors:
:{{cmdroot|perl -ne 'm/^EC 0xc0: .(..) .(..) .(..) / or next; print hex($1)." ".hex($2)." ".hex($3)."\n"' < /proc/acpi/ibm/ecdump}}
:{{cmdresult|40 48 43}}

Future models might provide additional extra sensors beyond those three. To see all candidates:
:{{cmdroot|perl -ne 'print join(" ",map(hex,m/\w+/g))."\n" if s/^EC 0xc0://' < /proc/acpi/ibm/ecdump}}
:{{cmdresult|40 48 43 128 128 128 128 128 0 0 0 0 0 0 0 0}}

{{WARN|'''ecdump''' is not a playground, and even just reading it causes side-effects to the ThinkPad. The ibm-acpi maintainer wants to make it clear that he considers it a very dumb idea to use ecdump constantly in a script}}

===HDAPS temperature sensor===
The [[Active Protection System]] accelerometer also reports a temperature, which is identical to one of the ACPI sensors. The corresponding sensor is actually not inside the HDAPS chip, but fairly close.
:{{cmdroot|cat /sys/bus/platform/drivers/hdaps/hdaps/temp1}}
:{{cmdresult|41}}

===Harddisks SMART temperature sensor===
The system hard disk temperature can be read through the disk's SMART interface:
:{{cmdroot|<nowiki>smartctl -A /dev/hda | grep Temperature</nowiki>}}
:{{cmdresult|194 Temperature_Celsius 0x0022 145 097 000 Old_age Always - 31}}

Or, for SATA-equipped models running a recent Linux kernel (see [[Problems with SATA and Linux]]):

:{{cmdroot|<nowiki>smartctl -A -d ata /dev/sda | grep Temperature</nowiki>}}
:{{cmdresult|194 Temperature_Celsius 0x0022 145 097 000 Old_age Always - 31}}

When the [[UltraBay Slim HDD Adapter]] or [[UltraBay Slim SATA HDD Adapter]] are used, the second hard disk will typically provide another temperature readout via its SMART interface, analogously to the above.

Reading this sensor will typically cause a drive spin-up and head unload.

===Hitachi harddisks <tt>SENSE CONDITION</tt> temperature sensor===

Recent Hitachi disks provide a non-standard <tt>SENSE CONDITION</tt> command which reads the disk temperature without causing a spin-up or head load. The reported value is the same as when using SMART. This can be invoked, e.g., using {{cmdroot|hdparm -H}}, or the relevant code in {{CodeRef|tp-fancontrol}}. When using the <tt>libata</tt> driver, this requires kernel >= 2.6.19-rc1.

==Utilities for viewing temperatures==

The following utilities display the ThinkPad-specific thermal sensor readouts:
* The above shell commands.
* The "Sensors" builtin of [[GKrellM]] can show 6 specific ACPI sensors (out of up to 11).
* [http://www.elliptique.net/~ken/kima/ Kima] is a KDE applet that can display the 8 first ACPI sensors as well as the HDAPS sensor.
* [http://www.kraus.tk/projects/IBMDoK/ IBMDoK], another KDE applet. Shows 4 specific sensors (out of up to 11). So far only tested at the {{T60}}.
* There is an [http://munin.projects.linpro.no/wiki/plugin-ibm_acpi ibm_acpi plugin] for [http://munin.projects.linpro.no/ Munin].
* [http://sensors-applet.sourceforge.net/ GNOME Sensors Applet] supports ibm_acpi.

==Sensor locations==
This information is model specific.

===ThinkPad {{A31}}===
Found by Milos Popovic using cooling spray to cool down components on a completely removed, running motherboard, to locate the sensors. Also reported [http://forum.thinkpads.com/viewtopic.php?t=31837 here].
EC offset Index in "thermal" Location (estimated)
0x78 1 CPU
0x79 2 Battery (this one heats up when on battery power)
0x7A 3 Power (sensor near power diodes and CPU; heats up when high power consumption, has crosstalk from CPU)
0x7B 4 Ultrabay 2000 battery?
0x7C 5 Northbridge (sensor next to Northbridge, also somewhat near GPU)
0x7D 6 PCMCIA/ambient (sensor is a National Semiconductor LM75 Digital Temperature Sensor/Thermal Watchdog chip
next to the 9-pin VGA connector; sits right under PCMCIA slots but doesn't touch)
0x7E 7 Battery (this one stays near ambient temperature, even when on battery power)
0x7F 8 Ultrabay 2000 battery?
0xC0 none zero
0xC1 none zero
0xC2 none zero
The following photos (resolution reduced for server space) show the locations found for the listed temperature sensors.
{{gallery_start}}
{{thumb|A31_2652M3U_systemboardtop_DSCN6105_tempsensors_lores.jpg|ThinkPad A31 sensor locations on top of motherboard.}}
{{thumb|A31_2652M3U_systemboardbottom_DSCN6105_tempsensors_lores.jpg|ThinkPad A31 sensor locations on bottom of motherboard.}}
{{gallery_end}}
On this A31 systemboard (FRU 26P8398), there is a [http://www.maxim-ic.com/quick_view2.cfm/qv_pk/2313 Maxim MAX1668] 5-channel remote/local temperature sensor (4 remote + 1 self temperature) on top of the systemboard, and a [http://www.national.com/pf/LM/LM75.html National Semiconductor LM75] single-channel "digital temperature sensor and thermal watchdog" chip. It would appear that the LM75 has the ability to hard shutdown the processor (without software intervention) if its temperature exceeds a given threshold. I'm not sure if it is wired for this, nor whether the Thinkpad changes the threshold temperature from the chip's power-up default of 80Â°C. A software application with drivers on the LM75 webpage is available that claims to allow direct access to the thermal sensor chip (this hasn't been tried, but could be useful in other models to determine if this sensor is somewhere on the MB, and which register it corresponds to). The MAX1668's self-temperature reading does not appear anywhere in the above temperature registers; it's not clear whether it is read at all, and whether it is to be found elsewhere in the EC memory. These two chips (LM75 and MAX1668) account for some of the sensors.

===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 System battery
0x7D 6 UltraBay battery
0x7E 7 System battery
0x7F 8 UltraBay battery
0xC0 none ?
0xC1 none ?
0xC2 none ?

===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 {{T43}}, {{T43p}}===
Found by Shmidoax using cooling spray to cool down components and observe the effect on the sensors.
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 System battery (front left = charging circuit)
0x7D 6 UltraBay battery
0x7E 7 System battery (rear right)
0x7F 8 UltraBay battery
0xC0 none Bus between Northbridge and DRAM; Ethernet chip
0xC1 none Southbridge, WLAN and clock generator (under Mini-PCI card, under touchpad)
0xC2 none Power circuitry, on underside of system board under F2 key
{{gallery_start}}
{{thumb|T43-thermal-sensors.jpg|ThinkPad T43 sensor locations}}
{{thumb|T43-2668-thermal-sensors-zoom.jpg|ThinkPad T43 sensor locations detail}}
{{thumb|T43p-H8S2161.jpg|ThinkPad T43/p 26xx Embedded Controller Renesas H8S/2161BV}}
{{gallery_end}}

===ThinkPad {{T60}}===
Found by Marco Kraus for use in [http://www.kraus.tk/projects/IBMDoK/ IBMDok].
EC offset Index in "thermal" Location (estimated)
0x78 1 CPU 0
0x79 2 HDD
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 ?

The CPU thermal sensors seem to be exposed in both {{path|/proc/acpi/thermal_zone/THM0/temperature}} and {{path|/proc/acpi/thermal_zone/THM1/temperature}}, though the latter curiously seems to exist only in this file and nowhere in {{path|/proc/acpi/ibm/ecdump}}.

===ThinkPad {{T61}}===
Found By Daniel Castro. There are two sensors for the battery but I'm not sure of the difference or exact location of them. There are still 3 sensors that I couldn't figure out. If anyone can help please update it.

Index in "thermal" Location
1 CPU
2 MiniPCI
3 HDD
4 n/a (-128)
5 Battery 1
6 n/a (-128)
7 Battery 2
8 n/a (-128)
9 ?
10 ?
11 ?
12 n/a (-128)
13 n/a (-128)
14 n/a (-128)
15 n/a (-128)
16 n/a (-128)

--[[User:Lunatico|Lunatico]] 23:44, 10 August 2008 (CEST)

===ThinkPad {{X31}}===
I figured these out by myself ([[User:BDKMPSS|BDKMPSS]]), as there are just a few available, this wasn't a huge problem. I verified my presumptions with a contactless thermometer.
EC offset Index in "thermal" Location (estimated)
0x78 1 CPU
0x79 2 n/a
0x7A 3 GPU?
0x7B 4 near or the ICH4M Southbrige, on the back of the Motherboard
0x7C 5 Battery
0x7D 6 Extended-Life-Battery; may also UltraBay battery
0x7E 7 Battery
0x7F 8 Extended-Life-Battery; may also UltraBay battery
0xC0 none n/a
0xC1 none n/a
0xC2 none n/a

0x7A "GPU?" is pretty hot and seems like the GPU, but as the Chipset and the GPU are cooled with the same heatsink it is difficult to separate them without roasting the machine. However the left and GPU side of the heatsink is much closer to the shown value than the right Chipset side.

How to enable the integrated fingerprint reader with ThinkFinger

2008-08-01T17:56:54Z

Lunatico: /* Fix for the fingerprint reader getting too hot */

[[How to enable the fingerprint reader]] has a good explanation for using the fingerprint reader with the closed-source binary driver. But there is also an opensource project called [http://thinkfinger.sourceforge.net ThinkFinger] which does the same, but open.

However: The fingerprint reader is an INSECURE device and gives a false sense of security! There has been quite a bit of research by a hacker named Starbug, a member of the Chaos Computer Club, Berlin, Germany. He outlined in two very good talks how to forge each and every available fingerprint sensor available at the cost of a few euros, using materials from your local hardware store, a digicam and a laser printer! Here's some links:
* [http://www.ccc.de/updates/2007/umsonst-im-supermarkt?language=en Fingerprint recognition in supermarkets]
* [ftp://ftp.ccc.de/pub/video/Fingerabdruck_Hack/fingerabdruck.mpg?language=en Video tutorial for forging fingerprints]

== Installing ==
=== From source ===

Download thinkfinger-0.3.tar.gz from the [http://thinkfinger.sourceforge.net/ homepage] and unpack it somewhere, make sure you have the gcc compiler, libtool, pkg-config, libusb-dev and libpam0g-dev installed, then:

{{cmduser|cd thinkfinger-0.3}}

<code style="white-space:nowrap;color:#495988;background-color:white;"><nowiki>$</nowiki> ./configure --prefix=/usr --sysconfdir=/etc --with-securedir=/lib/security --with-birdir=/etc/pam_thinkfinger</code>

{{cmduser|make}}

{{cmdroot|make install}}

{{NOTE|/lib/security is the directory, where PAM assumes its modules on Debian and openSUSE, it may vary for your distro!}}

"make install" doesn't create the birdir we specified (where thinkfinger will store users' biometric info), so create it:

{{cmdroot|mkdir /etc/pam_thinkfinger}}

If everything went OK assert that you find pam_thinkfinger.so in /lib/security typing:

{{cmduser|ls /lib/security}}

=== From package ===

==== Debian ====
[http://packages.debian.org/source/experimental/thinkfinger Packages] arrived in Debian experimental on Aug 2nd, 2007 (cf. [http://bugs.debian.org/409563 bug #409563]). To access the experimental packages via apt, add the following lines to your sources.list:
<pre>
# experimental
deb ftp://mirrors.kernel.org/debian/ experimental main contrib non-free
deb-src ftp://mirrors.kernel.org/debian/ experimental main contrib non-free
</pre>
where of course you may replace mirrors.kernel.org with your mirror of choice. Just make sure that it hosts the experimental repositories.
<pre>
aptitude update
aptitude install libthinkfinger0 libpam-thinkfinger thinkfinger-tools
</pre>
should then get you up and running.

==== Ubuntu ====

===== Hardy =====

Hardy includes the latest thinkfinger and it is up to date with subversion. Install packages:

{{cmduser|sudo apt-get install thinkfinger-tools libpam-thinkfinger}}

Update the pam configuration files:

{{cmduser|sudo /usr/lib/pam-thinkfinger/pam-thinkfinger-enable}}

Enroll your fingerprint (creates $HOME/.thinkfinger.bir). If this gives an error about claiming the USB device then reboot. {{NOTE|Do not try to enroll using 'sudo' - it will cause hidden permission problems}}

{{cmduser|tf-tool --acquire}}

Check fingerprint enrollment

{{cmduser|tf-tool --verify}}

You can expect everything to work correctly. Note that you still have to enter your username if prompted but will be able
to swipe your finger instead of the password. The prompt will usually be "Password or swipe finger"

* Graphical login
* Text console login
* sudo
* screen lock/screen saver
* Administrative password prompt (eg for update or package managers). (Note no "or swipe finger" in prompt).

===== Gutsy =====

From https://wiki.ubuntu.com/ThinkFinger

Add PPA repositories to your sources.list:
<pre>
deb http://ppa.launchpad.net/jldugger/ubuntu gutsy main restricted universe multiverse
deb-src http://ppa.launchpad.net/jldugger/ubuntu gutsy main restricted universe multiverse
</pre>

Install necessary packages:

{{cmduser|sudo apt-get install thinkfinger-tools libpam-thinkfinger}}

==== Fedora/Fedora Core ====
*Packages for Fedora Core 6 are available in "extras" repository (# yum install thinkfinger).
*Packages for Fedora 7 are available in the "updates" repository (# yum install thinkfinger).

==== Gentoo ====
<pre>
emerge sys-auth/thinkfinger
</pre>

==== OpenSUSE ====
openSUSE 10.2 includes the package "libthinkfinger" (version 0.1-7) - you will find newer packages [http://beta1.suse.com/private/thoenig/10.2/thinkfinger/ here].

== Testing the driver ==

Now the driver is installed and should be working. You can try it (as root) with

{{cmdroot|tf-tool --acquire}}

and

{{cmdroot|tf-tool --verify}}

This will ask you to swipe your finger three times, save the fingerprint to /tmp/test.bir and then verify your fingerprint with the bir-file.

== Configuring PAM to use ThinkFinger ==
Now you can configure PAM to use ThinkFinger:

Open {{path|/etc/pam.d/common-auth}} (In FC6, F7, and Gentoo, this file is {{path|/etc/pam.d/system-auth}}):

{{cmdroot|nano -w /etc/pam.d/common-auth}}

Add this line before any pam_unix or pam_unix2 directives:
auth sufficient pam_thinkfinger.so

If your PAM uses the pam_unix and not the pam_unix2 module, you need to pass a specific argument in
the /etc/pam.d/common-auth directive to make it consider the password entered at the pam_thinkfinger prompt.
auth required pam_unix.so try_first_pass

For instance, {{path|/etc/pam.d/common-auth}} looks like this:
auth sufficient pam_thinkfinger.so
auth required pam_unix.so nullok_secure try_first_pass

On openSUSE 10.2, it looks like this now:
auth required pam_env.so
auth sufficient pam_thinkfinger.so
auth required pam_unix2.so

Now we are ready to add users to thinkfinger. You can add a fingerprint for a user with:

{{cmdroot|tf-tool --add-user $USERNAME}}

Now the user should be able to login with his finger instead of the password.

If you would like to use thinkfinger for su, you have to enroll the fingerprint for root user with:

{{cmdroot|tf-tool --add-user root}}

{{NOTE|You should see the "Password or swipe finger:" prompt when trying to sudo or su. If you don't, you probably do not have the "User level driver support" compiled into your kernel or the "uinput" module loaded!}}

== xscreensaver/gnome-screensaver ==
{{NOTE|In Fedora 7, the package has been modified in such a way as to make doing this unnecessary.}}

If you'd like to be able to unlock your screen using the fingerprint reader, you must have current versions of xscreesaver (>~5.03) or gnome-screensaver (>~2.18.2). Then you must give yourself access to the fingerprint reader and your bir-file, because unlike login/gdm/su/sudo, both gnome-screensaver and xscreensaver do not run as root. The following procedure will make the fingerprint reader accessible to members of the "fingerprint" group.

Make the group: {{cmdroot|groupadd fingerprint}}

Save the following as {{path|/etc/udev/rules.d/60-thinkfinger.rules}} and run {{cmdroot|sudo /sbin/udevtrigger}} (you may need to reboot for this to take effect if udev trigger does not work):
#
# udev rules file for the thinkfinger fingerprint scanner
#
# gives access to the fingerprint reader to those in the "fingerprint" group
#
# Taken from:
# http://www.thinkwiki.org/wiki/How_to_enable_the_fingerprint_reader_with_ThinkFinger
# which was taken and modified from:
# http://article.gmane.org/gmane.linux.drivers.thinkfinger/329
#

# SGS Thomson Microelectronics Fingerprint Reader
SYSFS{idVendor}=="0483", SYSFS{idProduct}=="2016", SYMLINK+="input/thinkfinger-%k", MODE="0660", GROUP="fingerprint"

# the also-needed uinput device
KERNEL=="uinput", MODE="0660", GROUP="fingerprint"

Finally, edit {{path|/etc/pam.d/gnome-screensaver}} so that it looks like this:
auth sufficient pam_thinkfinger.so
auth required pam_unix.so try_first_pass nullok_secure

Per user:

# Add him to the group: {{cmdroot|gpasswd -a $USERNAME fingerprint}}
# Make him owner of his bir-file: {{cmdroot|chown $USERNAME:root /etc/pam_thinkfinger/$USERNAME.bir}}
# Give him read-only access to his bir-file: {{cmdroot|chmod 400 /etc/pam_thinkfinger/$USERNAME.bir}}
# Give "execute only" access to everyone for the /etc/pam_thinkfinger/ directory: {{cmdroot|chmod o+x /etc/pam_thinkfinger}} (WARNING: this opens up security a little).

== GNOME ==

{{NOTE|1=This problem should be solved if you're using sudo >= 1.6.9p9. Links: [http://savannah.nongnu.org/bugs/?19132], [http://www.sudo.ws/bugs/show_bug.cgi?id=180], [https://bugs.launchpad.net/ubuntu/+source/gksu/+bug/86843]}}

gksu/gksudo doesn't work correctly. It just stays invisible. When starting a su privileged application such as synaptics you will not get prompted for the password. Nevertheless you can swipe your finger and it should authenticate you. Starting synaptics twice makes gksudo visible.

There are two possibilities to solve it:
* Changing the string "Password or swipe finger:" to a plain "Password:" (like sudo normally would do) in the file pam/pam_thinkfinger.c of the thinkfinger source directory. Of course, in the console you will then only see a "Password:" instead of "Password or swipe finger:" but this is still more usefull than having gksu/gksudo crashing everytime.
* Patching libgksu with the following patch. This is also a nasty hack until a better solution is implemented.
<pre>
--- libgksu-2.0.3/libgksu/libgksu.c.orig 2007-06-17 16:00:24.000000000 +0200
+++ libgksu-2.0.3/libgksu/libgksu.c 2007-06-17 16:00:47.000000000 +0200
@@ -2663,7 +2663,7 @@
*/
for (counter = 0; counter < 50; counter++)
{
- if (strncmp (buffer, "GNOME_SUDO_PASS", 15) == 0)
+ if (strncmp (buffer, "GNOME_SUDO_PASS", 15) == 0 || strncmp (buffer, "Password or swi", 15) == 0)
break;

read_line (parent_pipe[0], buffer, 256);
@@ -2675,7 +2675,7 @@
if (context->debug)
fprintf (stderr, "brute force GNOME_SUDO_PASS ended...\n");

- if (strncmp(buffer, "GNOME_SUDO_PASS", 15) == 0)
+ if (strncmp(buffer, "GNOME_SUDO_PASS", 15) == 0 || strncmp(buffer, "Password or swi", 15) == 0)
{
gchar *password = NULL;
gboolean prompt_grab;
</pre>

== KDE ==

Integration in KDE and kdm seems not to be easily possible now. There is a filed [https://bugs.kde.org/show_bug.cgi?id=116682 bug] at kde.org where you can vote for this.

Moreover, kdm in openSUSE 10.3 crashes when pam_thinkfinger is enabled. A possible "workaround" is downgrading to thinkfinger 0.2.2.

Another workaround is to use Fprint from [http://www.reactivated.net/fprint/wiki/Main_Page] which works quite nicely on my X61s and Kubuntu Hardy.

This Howto was copied from [[Installing Ubuntu 6.06 on a ThinkPad T43#Fingerprint_Reader]] and then slightly modified.

== Fix for the fingerprint reader getting too hot ==

If you notice that your fingerprint reader occasionally gets very hot then you might be interested in this section. Thanks to Tino Keitel, he actually gave me this solution through the linux-thinkpad mailing list.

First we need to determine if the reader is not on autosuspend mode.
Open a terminal and run:

for i in `find /sys/devices/*/*/usb* -name level` ; do echo -n "$i: " ; cat $i ; done

We care about the devices that are with "on" state and we need to determine if one of those is the reader. So for each of those run something like:

cat /sys/devices/pci0000\:00/0000\:00\:1a.0/usb1/1-2/idVendor
0483

cat /sys/devices/pci0000\:00/0000\:00\:1a.0/usb1/1-2/idProduct
2016

Use the corresponding path of the devices that you got with "on" state and then compare the output with the output of the lsusb command. An example:

lsusb output: Bus 001 Device 004: ID 0483:2016 SGS Thomson Microelectronics Fingerprint Reader

Which matches the output above (0483:2016). Once you have determined the path of your reader then become root with su - and:

echo "auto" > /sys/<path-to-device>/power/level

After this, the fingerprint reader should be in "autosuspend" and will not get hot anymore. And it will still work as normal.

This will only work for the current session. If you want to make this change persistent then:

sudo gedit /etc/init.d/ReaderNoMoreHot

Paste the following into it:

#!/bin/bash
#
echo "auto" > /sys/<path-to-device>/power/level

Save and close. Then:

sudo chmod 755 /etc/init.d/ReaderNoMoreHot
sudo update-rc.d ReaderNoMoreHot defaults 90

--[[User:Lunatico|Lunatico]] 19:19, 1 August 2008 (CEST)

How to enable the integrated fingerprint reader with ThinkFinger

2008-08-01T17:40:36Z

Lunatico: /* Fix for the fingerprint reader getting too hot */

[[How to enable the fingerprint reader]] has a good explanation for using the fingerprint reader with the closed-source binary driver. But there is also an opensource project called [http://thinkfinger.sourceforge.net ThinkFinger] which does the same, but open.

However: The fingerprint reader is an INSECURE device and gives a false sense of security! There has been quite a bit of research by a hacker named Starbug, a member of the Chaos Computer Club, Berlin, Germany. He outlined in two very good talks how to forge each and every available fingerprint sensor available at the cost of a few euros, using materials from your local hardware store, a digicam and a laser printer! Here's some links:
* [http://www.ccc.de/updates/2007/umsonst-im-supermarkt?language=en Fingerprint recognition in supermarkets]
* [ftp://ftp.ccc.de/pub/video/Fingerabdruck_Hack/fingerabdruck.mpg?language=en Video tutorial for forging fingerprints]

== Installing ==
=== From source ===

Download thinkfinger-0.3.tar.gz from the [http://thinkfinger.sourceforge.net/ homepage] and unpack it somewhere, make sure you have the gcc compiler, libtool, pkg-config, libusb-dev and libpam0g-dev installed, then:

{{cmduser|cd thinkfinger-0.3}}

<code style="white-space:nowrap;color:#495988;background-color:white;"><nowiki>$</nowiki> ./configure --prefix=/usr --sysconfdir=/etc --with-securedir=/lib/security --with-birdir=/etc/pam_thinkfinger</code>

{{cmduser|make}}

{{cmdroot|make install}}

{{NOTE|/lib/security is the directory, where PAM assumes its modules on Debian and openSUSE, it may vary for your distro!}}

"make install" doesn't create the birdir we specified (where thinkfinger will store users' biometric info), so create it:

{{cmdroot|mkdir /etc/pam_thinkfinger}}

If everything went OK assert that you find pam_thinkfinger.so in /lib/security typing:

{{cmduser|ls /lib/security}}

=== From package ===

==== Debian ====
[http://packages.debian.org/source/experimental/thinkfinger Packages] arrived in Debian experimental on Aug 2nd, 2007 (cf. [http://bugs.debian.org/409563 bug #409563]). To access the experimental packages via apt, add the following lines to your sources.list:
<pre>
# experimental
deb ftp://mirrors.kernel.org/debian/ experimental main contrib non-free
deb-src ftp://mirrors.kernel.org/debian/ experimental main contrib non-free
</pre>
where of course you may replace mirrors.kernel.org with your mirror of choice. Just make sure that it hosts the experimental repositories.
<pre>
aptitude update
aptitude install libthinkfinger0 libpam-thinkfinger thinkfinger-tools
</pre>
should then get you up and running.

==== Ubuntu ====

===== Hardy =====

Hardy includes the latest thinkfinger and it is up to date with subversion. Install packages:

{{cmduser|sudo apt-get install thinkfinger-tools libpam-thinkfinger}}

Update the pam configuration files:

{{cmduser|sudo /usr/lib/pam-thinkfinger/pam-thinkfinger-enable}}

Enroll your fingerprint (creates $HOME/.thinkfinger.bir). If this gives an error about claiming the USB device then reboot. {{NOTE|Do not try to enroll using 'sudo' - it will cause hidden permission problems}}

{{cmduser|tf-tool --acquire}}

Check fingerprint enrollment

{{cmduser|tf-tool --verify}}

You can expect everything to work correctly. Note that you still have to enter your username if prompted but will be able
to swipe your finger instead of the password. The prompt will usually be "Password or swipe finger"

* Graphical login
* Text console login
* sudo
* screen lock/screen saver
* Administrative password prompt (eg for update or package managers). (Note no "or swipe finger" in prompt).

===== Gutsy =====

From https://wiki.ubuntu.com/ThinkFinger

Add PPA repositories to your sources.list:
<pre>
deb http://ppa.launchpad.net/jldugger/ubuntu gutsy main restricted universe multiverse
deb-src http://ppa.launchpad.net/jldugger/ubuntu gutsy main restricted universe multiverse
</pre>

Install necessary packages:

{{cmduser|sudo apt-get install thinkfinger-tools libpam-thinkfinger}}

==== Fedora/Fedora Core ====
*Packages for Fedora Core 6 are available in "extras" repository (# yum install thinkfinger).
*Packages for Fedora 7 are available in the "updates" repository (# yum install thinkfinger).

==== Gentoo ====
<pre>
emerge sys-auth/thinkfinger
</pre>

==== OpenSUSE ====
openSUSE 10.2 includes the package "libthinkfinger" (version 0.1-7) - you will find newer packages [http://beta1.suse.com/private/thoenig/10.2/thinkfinger/ here].

== Testing the driver ==

Now the driver is installed and should be working. You can try it (as root) with

{{cmdroot|tf-tool --acquire}}

and

{{cmdroot|tf-tool --verify}}

This will ask you to swipe your finger three times, save the fingerprint to /tmp/test.bir and then verify your fingerprint with the bir-file.

== Configuring PAM to use ThinkFinger ==
Now you can configure PAM to use ThinkFinger:

Open {{path|/etc/pam.d/common-auth}} (In FC6, F7, and Gentoo, this file is {{path|/etc/pam.d/system-auth}}):

{{cmdroot|nano -w /etc/pam.d/common-auth}}

Add this line before any pam_unix or pam_unix2 directives:
auth sufficient pam_thinkfinger.so

If your PAM uses the pam_unix and not the pam_unix2 module, you need to pass a specific argument in
the /etc/pam.d/common-auth directive to make it consider the password entered at the pam_thinkfinger prompt.
auth required pam_unix.so try_first_pass

For instance, {{path|/etc/pam.d/common-auth}} looks like this:
auth sufficient pam_thinkfinger.so
auth required pam_unix.so nullok_secure try_first_pass

On openSUSE 10.2, it looks like this now:
auth required pam_env.so
auth sufficient pam_thinkfinger.so
auth required pam_unix2.so

Now we are ready to add users to thinkfinger. You can add a fingerprint for a user with:

{{cmdroot|tf-tool --add-user $USERNAME}}

Now the user should be able to login with his finger instead of the password.

If you would like to use thinkfinger for su, you have to enroll the fingerprint for root user with:

{{cmdroot|tf-tool --add-user root}}

{{NOTE|You should see the "Password or swipe finger:" prompt when trying to sudo or su. If you don't, you probably do not have the "User level driver support" compiled into your kernel or the "uinput" module loaded!}}

== xscreensaver/gnome-screensaver ==
{{NOTE|In Fedora 7, the package has been modified in such a way as to make doing this unnecessary.}}

If you'd like to be able to unlock your screen using the fingerprint reader, you must have current versions of xscreesaver (>~5.03) or gnome-screensaver (>~2.18.2). Then you must give yourself access to the fingerprint reader and your bir-file, because unlike login/gdm/su/sudo, both gnome-screensaver and xscreensaver do not run as root. The following procedure will make the fingerprint reader accessible to members of the "fingerprint" group.

Make the group: {{cmdroot|groupadd fingerprint}}

Save the following as {{path|/etc/udev/rules.d/60-thinkfinger.rules}} and run {{cmdroot|sudo /sbin/udevtrigger}} (you may need to reboot for this to take effect if udev trigger does not work):
#
# udev rules file for the thinkfinger fingerprint scanner
#
# gives access to the fingerprint reader to those in the "fingerprint" group
#
# Taken from:
# http://www.thinkwiki.org/wiki/How_to_enable_the_fingerprint_reader_with_ThinkFinger
# which was taken and modified from:
# http://article.gmane.org/gmane.linux.drivers.thinkfinger/329
#

# SGS Thomson Microelectronics Fingerprint Reader
SYSFS{idVendor}=="0483", SYSFS{idProduct}=="2016", SYMLINK+="input/thinkfinger-%k", MODE="0660", GROUP="fingerprint"

# the also-needed uinput device
KERNEL=="uinput", MODE="0660", GROUP="fingerprint"

Finally, edit {{path|/etc/pam.d/gnome-screensaver}} so that it looks like this:
auth sufficient pam_thinkfinger.so
auth required pam_unix.so try_first_pass nullok_secure

Per user:

# Add him to the group: {{cmdroot|gpasswd -a $USERNAME fingerprint}}
# Make him owner of his bir-file: {{cmdroot|chown $USERNAME:root /etc/pam_thinkfinger/$USERNAME.bir}}
# Give him read-only access to his bir-file: {{cmdroot|chmod 400 /etc/pam_thinkfinger/$USERNAME.bir}}
# Give "execute only" access to everyone for the /etc/pam_thinkfinger/ directory: {{cmdroot|chmod o+x /etc/pam_thinkfinger}} (WARNING: this opens up security a little).

== GNOME ==

{{NOTE|1=This problem should be solved if you're using sudo >= 1.6.9p9. Links: [http://savannah.nongnu.org/bugs/?19132], [http://www.sudo.ws/bugs/show_bug.cgi?id=180], [https://bugs.launchpad.net/ubuntu/+source/gksu/+bug/86843]}}

gksu/gksudo doesn't work correctly. It just stays invisible. When starting a su privileged application such as synaptics you will not get prompted for the password. Nevertheless you can swipe your finger and it should authenticate you. Starting synaptics twice makes gksudo visible.

There are two possibilities to solve it:
* Changing the string "Password or swipe finger:" to a plain "Password:" (like sudo normally would do) in the file pam/pam_thinkfinger.c of the thinkfinger source directory. Of course, in the console you will then only see a "Password:" instead of "Password or swipe finger:" but this is still more usefull than having gksu/gksudo crashing everytime.
* Patching libgksu with the following patch. This is also a nasty hack until a better solution is implemented.
<pre>
--- libgksu-2.0.3/libgksu/libgksu.c.orig 2007-06-17 16:00:24.000000000 +0200
+++ libgksu-2.0.3/libgksu/libgksu.c 2007-06-17 16:00:47.000000000 +0200
@@ -2663,7 +2663,7 @@
*/
for (counter = 0; counter < 50; counter++)
{
- if (strncmp (buffer, "GNOME_SUDO_PASS", 15) == 0)
+ if (strncmp (buffer, "GNOME_SUDO_PASS", 15) == 0 || strncmp (buffer, "Password or swi", 15) == 0)
break;

read_line (parent_pipe[0], buffer, 256);
@@ -2675,7 +2675,7 @@
if (context->debug)
fprintf (stderr, "brute force GNOME_SUDO_PASS ended...\n");

- if (strncmp(buffer, "GNOME_SUDO_PASS", 15) == 0)
+ if (strncmp(buffer, "GNOME_SUDO_PASS", 15) == 0 || strncmp(buffer, "Password or swi", 15) == 0)
{
gchar *password = NULL;
gboolean prompt_grab;
</pre>

== KDE ==

Integration in KDE and kdm seems not to be easily possible now. There is a filed [https://bugs.kde.org/show_bug.cgi?id=116682 bug] at kde.org where you can vote for this.

Moreover, kdm in openSUSE 10.3 crashes when pam_thinkfinger is enabled. A possible "workaround" is downgrading to thinkfinger 0.2.2.

Another workaround is to use Fprint from [http://www.reactivated.net/fprint/wiki/Main_Page] which works quite nicely on my X61s and Kubuntu Hardy.

This Howto was copied from [[Installing Ubuntu 6.06 on a ThinkPad T43#Fingerprint_Reader]] and then slightly modified.

== Fix for the fingerprint reader getting too hot ==

If you notice that you fingerprint reader occasionally gets very hot then you might be interested in this section. Thanks to Tino Keitel, he actually gave me this solution through the linux-thinkpad mailing list.

First we need to determine if the reader is not on autosuspend mode.
Open a terminal and run:

for i in `find /sys/devices/*/*/usb* -name level` ; do echo -n "$i: " ; cat $i ; done

We care about the devices that are with "on" state and we need to determine if one of those is the reader. So for each of those run something like:

cat /sys/devices/pci0000\:00/0000\:00\:1a.0/usb1/1-2/idVendor
0483

cat /sys/devices/pci0000\:00/0000\:00\:1a.0/usb1/1-2/idProduct
2016

Use the corresponding path of the devices that you got with "on" state and then compare the output with the output of the lsusb command. An example:

lsusb output: Bus 001 Device 004: ID 0483:2016 SGS Thomson Microelectronics Fingerprint Reader

Which matches the output above (0483:2016). Once you have determined the path of your reader then become root with su - and:

echo "auto" > /sys/<path-to-device>/power/level

After this, the fingerprint reader should be in "autosuspend" and will not get hot anymore. And it will still work as normal.

This will only work for the current session. If you want to make this change persistent then:

sudo gedit /etc/init.d/ReaderNoMoreHot

Paste the following into it:

#!/bin/bash
#
echo "auto" > /sys/<path-to-device>/power/level

Save and close gedit. Then:

sudo chmod 755 /etc/init.d/ReaderNoMoreHot
sudo update-rc.d ReaderNoMoreHot defaults 90

--[[User:Lunatico|Lunatico]] 19:19, 1 August 2008 (CEST)

How to enable the integrated fingerprint reader with ThinkFinger

2008-08-01T17:19:34Z

Lunatico: /* Fix for the fingerprint reader getting too hot */

[[How to enable the fingerprint reader]] has a good explanation for using the fingerprint reader with the closed-source binary driver. But there is also an opensource project called [http://thinkfinger.sourceforge.net ThinkFinger] which does the same, but open.

However: The fingerprint reader is an INSECURE device and gives a false sense of security! There has been quite a bit of research by a hacker named Starbug, a member of the Chaos Computer Club, Berlin, Germany. He outlined in two very good talks how to forge each and every available fingerprint sensor available at the cost of a few euros, using materials from your local hardware store, a digicam and a laser printer! Here's some links:
* [http://www.ccc.de/updates/2007/umsonst-im-supermarkt?language=en Fingerprint recognition in supermarkets]
* [ftp://ftp.ccc.de/pub/video/Fingerabdruck_Hack/fingerabdruck.mpg?language=en Video tutorial for forging fingerprints]

== Installing ==
=== From source ===

Download thinkfinger-0.3.tar.gz from the [http://thinkfinger.sourceforge.net/ homepage] and unpack it somewhere, make sure you have the gcc compiler, libtool, pkg-config, libusb-dev and libpam0g-dev installed, then:

{{cmduser|cd thinkfinger-0.3}}

<code style="white-space:nowrap;color:#495988;background-color:white;"><nowiki>$</nowiki> ./configure --prefix=/usr --sysconfdir=/etc --with-securedir=/lib/security --with-birdir=/etc/pam_thinkfinger</code>

{{cmduser|make}}

{{cmdroot|make install}}

{{NOTE|/lib/security is the directory, where PAM assumes its modules on Debian and openSUSE, it may vary for your distro!}}

"make install" doesn't create the birdir we specified (where thinkfinger will store users' biometric info), so create it:

{{cmdroot|mkdir /etc/pam_thinkfinger}}

If everything went OK assert that you find pam_thinkfinger.so in /lib/security typing:

{{cmduser|ls /lib/security}}

=== From package ===

==== Debian ====
[http://packages.debian.org/source/experimental/thinkfinger Packages] arrived in Debian experimental on Aug 2nd, 2007 (cf. [http://bugs.debian.org/409563 bug #409563]). To access the experimental packages via apt, add the following lines to your sources.list:
<pre>
# experimental
deb ftp://mirrors.kernel.org/debian/ experimental main contrib non-free
deb-src ftp://mirrors.kernel.org/debian/ experimental main contrib non-free
</pre>
where of course you may replace mirrors.kernel.org with your mirror of choice. Just make sure that it hosts the experimental repositories.
<pre>
aptitude update
aptitude install libthinkfinger0 libpam-thinkfinger thinkfinger-tools
</pre>
should then get you up and running.

==== Ubuntu ====

===== Hardy =====

Hardy includes the latest thinkfinger and it is up to date with subversion. Install packages:

{{cmduser|sudo apt-get install thinkfinger-tools libpam-thinkfinger}}

Update the pam configuration files:

{{cmduser|sudo /usr/lib/pam-thinkfinger/pam-thinkfinger-enable}}

Enroll your fingerprint (creates $HOME/.thinkfinger.bir). If this gives an error about claiming the USB device then reboot. {{NOTE|Do not try to enroll using 'sudo' - it will cause hidden permission problems}}

{{cmduser|tf-tool --acquire}}

Check fingerprint enrollment

{{cmduser|tf-tool --verify}}

You can expect everything to work correctly. Note that you still have to enter your username if prompted but will be able
to swipe your finger instead of the password. The prompt will usually be "Password or swipe finger"

* Graphical login
* Text console login
* sudo
* screen lock/screen saver
* Administrative password prompt (eg for update or package managers). (Note no "or swipe finger" in prompt).

===== Gutsy =====

From https://wiki.ubuntu.com/ThinkFinger

Add PPA repositories to your sources.list:
<pre>
deb http://ppa.launchpad.net/jldugger/ubuntu gutsy main restricted universe multiverse
deb-src http://ppa.launchpad.net/jldugger/ubuntu gutsy main restricted universe multiverse
</pre>

Install necessary packages:

{{cmduser|sudo apt-get install thinkfinger-tools libpam-thinkfinger}}

==== Fedora/Fedora Core ====
*Packages for Fedora Core 6 are available in "extras" repository (# yum install thinkfinger).
*Packages for Fedora 7 are available in the "updates" repository (# yum install thinkfinger).

==== Gentoo ====
<pre>
emerge sys-auth/thinkfinger
</pre>

==== OpenSUSE ====
openSUSE 10.2 includes the package "libthinkfinger" (version 0.1-7) - you will find newer packages [http://beta1.suse.com/private/thoenig/10.2/thinkfinger/ here].

== Testing the driver ==

Now the driver is installed and should be working. You can try it (as root) with

{{cmdroot|tf-tool --acquire}}

and

{{cmdroot|tf-tool --verify}}

This will ask you to swipe your finger three times, save the fingerprint to /tmp/test.bir and then verify your fingerprint with the bir-file.

== Configuring PAM to use ThinkFinger ==
Now you can configure PAM to use ThinkFinger:

Open {{path|/etc/pam.d/common-auth}} (In FC6, F7, and Gentoo, this file is {{path|/etc/pam.d/system-auth}}):

{{cmdroot|nano -w /etc/pam.d/common-auth}}

Add this line before any pam_unix or pam_unix2 directives:
auth sufficient pam_thinkfinger.so

If your PAM uses the pam_unix and not the pam_unix2 module, you need to pass a specific argument in
the /etc/pam.d/common-auth directive to make it consider the password entered at the pam_thinkfinger prompt.
auth required pam_unix.so try_first_pass

For instance, {{path|/etc/pam.d/common-auth}} looks like this:
auth sufficient pam_thinkfinger.so
auth required pam_unix.so nullok_secure try_first_pass

On openSUSE 10.2, it looks like this now:
auth required pam_env.so
auth sufficient pam_thinkfinger.so
auth required pam_unix2.so

Now we are ready to add users to thinkfinger. You can add a fingerprint for a user with:

{{cmdroot|tf-tool --add-user $USERNAME}}

Now the user should be able to login with his finger instead of the password.

If you would like to use thinkfinger for su, you have to enroll the fingerprint for root user with:

{{cmdroot|tf-tool --add-user root}}

{{NOTE|You should see the "Password or swipe finger:" prompt when trying to sudo or su. If you don't, you probably do not have the "User level driver support" compiled into your kernel or the "uinput" module loaded!}}

== xscreensaver/gnome-screensaver ==
{{NOTE|In Fedora 7, the package has been modified in such a way as to make doing this unnecessary.}}

If you'd like to be able to unlock your screen using the fingerprint reader, you must have current versions of xscreesaver (>~5.03) or gnome-screensaver (>~2.18.2). Then you must give yourself access to the fingerprint reader and your bir-file, because unlike login/gdm/su/sudo, both gnome-screensaver and xscreensaver do not run as root. The following procedure will make the fingerprint reader accessible to members of the "fingerprint" group.

Make the group: {{cmdroot|groupadd fingerprint}}

Save the following as {{path|/etc/udev/rules.d/60-thinkfinger.rules}} and run {{cmdroot|sudo /sbin/udevtrigger}} (you may need to reboot for this to take effect if udev trigger does not work):
#
# udev rules file for the thinkfinger fingerprint scanner
#
# gives access to the fingerprint reader to those in the "fingerprint" group
#
# Taken from:
# http://www.thinkwiki.org/wiki/How_to_enable_the_fingerprint_reader_with_ThinkFinger
# which was taken and modified from:
# http://article.gmane.org/gmane.linux.drivers.thinkfinger/329
#

# SGS Thomson Microelectronics Fingerprint Reader
SYSFS{idVendor}=="0483", SYSFS{idProduct}=="2016", SYMLINK+="input/thinkfinger-%k", MODE="0660", GROUP="fingerprint"

# the also-needed uinput device
KERNEL=="uinput", MODE="0660", GROUP="fingerprint"

Finally, edit {{path|/etc/pam.d/gnome-screensaver}} so that it looks like this:
auth sufficient pam_thinkfinger.so
auth required pam_unix.so try_first_pass nullok_secure

Per user:

# Add him to the group: {{cmdroot|gpasswd -a $USERNAME fingerprint}}
# Make him owner of his bir-file: {{cmdroot|chown $USERNAME:root /etc/pam_thinkfinger/$USERNAME.bir}}
# Give him read-only access to his bir-file: {{cmdroot|chmod 400 /etc/pam_thinkfinger/$USERNAME.bir}}
# Give "execute only" access to everyone for the /etc/pam_thinkfinger/ directory: {{cmdroot|chmod o+x /etc/pam_thinkfinger}} (WARNING: this opens up security a little).

== GNOME ==

{{NOTE|1=This problem should be solved if you're using sudo >= 1.6.9p9. Links: [http://savannah.nongnu.org/bugs/?19132], [http://www.sudo.ws/bugs/show_bug.cgi?id=180], [https://bugs.launchpad.net/ubuntu/+source/gksu/+bug/86843]}}

gksu/gksudo doesn't work correctly. It just stays invisible. When starting a su privileged application such as synaptics you will not get prompted for the password. Nevertheless you can swipe your finger and it should authenticate you. Starting synaptics twice makes gksudo visible.

There are two possibilities to solve it:
* Changing the string "Password or swipe finger:" to a plain "Password:" (like sudo normally would do) in the file pam/pam_thinkfinger.c of the thinkfinger source directory. Of course, in the console you will then only see a "Password:" instead of "Password or swipe finger:" but this is still more usefull than having gksu/gksudo crashing everytime.
* Patching libgksu with the following patch. This is also a nasty hack until a better solution is implemented.
<pre>
--- libgksu-2.0.3/libgksu/libgksu.c.orig 2007-06-17 16:00:24.000000000 +0200
+++ libgksu-2.0.3/libgksu/libgksu.c 2007-06-17 16:00:47.000000000 +0200
@@ -2663,7 +2663,7 @@
*/
for (counter = 0; counter < 50; counter++)
{
- if (strncmp (buffer, "GNOME_SUDO_PASS", 15) == 0)
+ if (strncmp (buffer, "GNOME_SUDO_PASS", 15) == 0 || strncmp (buffer, "Password or swi", 15) == 0)
break;

read_line (parent_pipe[0], buffer, 256);
@@ -2675,7 +2675,7 @@
if (context->debug)
fprintf (stderr, "brute force GNOME_SUDO_PASS ended...\n");

- if (strncmp(buffer, "GNOME_SUDO_PASS", 15) == 0)
+ if (strncmp(buffer, "GNOME_SUDO_PASS", 15) == 0 || strncmp(buffer, "Password or swi", 15) == 0)
{
gchar *password = NULL;
gboolean prompt_grab;
</pre>

== KDE ==

Integration in KDE and kdm seems not to be easily possible now. There is a filed [https://bugs.kde.org/show_bug.cgi?id=116682 bug] at kde.org where you can vote for this.

Moreover, kdm in openSUSE 10.3 crashes when pam_thinkfinger is enabled. A possible "workaround" is downgrading to thinkfinger 0.2.2.

Another workaround is to use Fprint from [http://www.reactivated.net/fprint/wiki/Main_Page] which works quite nicely on my X61s and Kubuntu Hardy.

This Howto was copied from [[Installing Ubuntu 6.06 on a ThinkPad T43#Fingerprint_Reader]] and then slightly modified.

== Fix for the fingerprint reader getting too hot ==

If you notice that you fingerprint reader occasionally gets very hot then you might be interested in this section. Thanks to Tino Keitel, he actually gave me this solution through the linux-thinkpad mailing list.

First we need to determine if the reader is not on autosuspend mode.
Open a terminal and run:

for i in `find /sys/devices/*/*/usb* -name level` ; do echo -n "$i: " ; cat $i ; done

We care about the devices that are with "on" state and we need to determine if one of those is the reader. So for each of those run something like:

cat /sys/devices/pci0000\:00/0000\:00\:1a.0/usb1/1-2/idVendor
0483

cat /sys/devices/pci0000\:00/0000\:00\:1a.0/usb1/1-2/idProduct
2016

Use the corresponding path of the devices that you got with "on" state and then compare the output with the output of the lsusb command. An example:

lsusb output: Bus 001 Device 004: ID 0483:2016 SGS Thomson Microelectronics Fingerprint Reader

Which matches the output above. Once you have determined the path of your reader then you can:

echo "auto" > /sys/<path-to-device>/power/level

After this, the fingerprint reader should be in "autosuspend" and will not get hot anymore. And it will still work as normal.

This will only work for the current session. If you want to make this change persistent then:

gedit ~/ReaderNoMoreHot

Paste the following into it (I'm using the path of the example above, replace with whatever matches your device):

#!/bin/bash
#
echo "auto" > echo "auto" > /sys/devices/pci0000\:00/0000\:00\:1a.0/usb1/1-2/power/level

Save and close gedit. Then make that file executable by:

chmod +x ~/ReaderNoMoreHot

And then put this script on the session login list. Go to System->Preferences->Sessions click Add and on the command field put:

~/ReaderNoMoreHot

--[[User:Lunatico|Lunatico]] 19:19, 1 August 2008 (CEST)

How to enable the integrated fingerprint reader with ThinkFinger

2008-08-01T16:09:16Z

Lunatico: /* Fix for the fingerprint getting too hot */

[[How to enable the fingerprint reader]] has a good explanation for using the fingerprint reader with the closed-source binary driver. But there is also an opensource project called [http://thinkfinger.sourceforge.net ThinkFinger] which does the same, but open.

However: The fingerprint reader is an INSECURE device and gives a false sense of security! There has been quite a bit of research by a hacker named Starbug, a member of the Chaos Computer Club, Berlin, Germany. He outlined in two very good talks how to forge each and every available fingerprint sensor available at the cost of a few euros, using materials from your local hardware store, a digicam and a laser printer! Here's some links:
* [http://www.ccc.de/updates/2007/umsonst-im-supermarkt?language=en Fingerprint recognition in supermarkets]
* [ftp://ftp.ccc.de/pub/video/Fingerabdruck_Hack/fingerabdruck.mpg?language=en Video tutorial for forging fingerprints]

== Installing ==
=== From source ===

Download thinkfinger-0.3.tar.gz from the [http://thinkfinger.sourceforge.net/ homepage] and unpack it somewhere, make sure you have the gcc compiler, libtool, pkg-config, libusb-dev and libpam0g-dev installed, then:

{{cmduser|cd thinkfinger-0.3}}

<code style="white-space:nowrap;color:#495988;background-color:white;"><nowiki>$</nowiki> ./configure --prefix=/usr --sysconfdir=/etc --with-securedir=/lib/security --with-birdir=/etc/pam_thinkfinger</code>

{{cmduser|make}}

{{cmdroot|make install}}

{{NOTE|/lib/security is the directory, where PAM assumes its modules on Debian and openSUSE, it may vary for your distro!}}

"make install" doesn't create the birdir we specified (where thinkfinger will store users' biometric info), so create it:

{{cmdroot|mkdir /etc/pam_thinkfinger}}

If everything went OK assert that you find pam_thinkfinger.so in /lib/security typing:

{{cmduser|ls /lib/security}}

=== From package ===

==== Debian ====
[http://packages.debian.org/source/experimental/thinkfinger Packages] arrived in Debian experimental on Aug 2nd, 2007 (cf. [http://bugs.debian.org/409563 bug #409563]). To access the experimental packages via apt, add the following lines to your sources.list:
<pre>
# experimental
deb ftp://mirrors.kernel.org/debian/ experimental main contrib non-free
deb-src ftp://mirrors.kernel.org/debian/ experimental main contrib non-free
</pre>
where of course you may replace mirrors.kernel.org with your mirror of choice. Just make sure that it hosts the experimental repositories.
<pre>
aptitude update
aptitude install libthinkfinger0 libpam-thinkfinger thinkfinger-tools
</pre>
should then get you up and running.

==== Ubuntu ====

===== Hardy =====

Hardy includes the latest thinkfinger and it is up to date with subversion. Install packages:

{{cmduser|sudo apt-get install thinkfinger-tools libpam-thinkfinger}}

Update the pam configuration files:

{{cmduser|sudo /usr/lib/pam-thinkfinger/pam-thinkfinger-enable}}

Enroll your fingerprint (creates $HOME/.thinkfinger.bir). If this gives an error about claiming the USB device then reboot. {{NOTE|Do not try to enroll using 'sudo' - it will cause hidden permission problems}}

{{cmduser|tf-tool --acquire}}

Check fingerprint enrollment

{{cmduser|tf-tool --verify}}

You can expect everything to work correctly. Note that you still have to enter your username if prompted but will be able
to swipe your finger instead of the password. The prompt will usually be "Password or swipe finger"

* Graphical login
* Text console login
* sudo
* screen lock/screen saver
* Administrative password prompt (eg for update or package managers). (Note no "or swipe finger" in prompt).

===== Gutsy =====

From https://wiki.ubuntu.com/ThinkFinger

Add PPA repositories to your sources.list:
<pre>
deb http://ppa.launchpad.net/jldugger/ubuntu gutsy main restricted universe multiverse
deb-src http://ppa.launchpad.net/jldugger/ubuntu gutsy main restricted universe multiverse
</pre>

Install necessary packages:

{{cmduser|sudo apt-get install thinkfinger-tools libpam-thinkfinger}}

==== Fedora/Fedora Core ====
*Packages for Fedora Core 6 are available in "extras" repository (# yum install thinkfinger).
*Packages for Fedora 7 are available in the "updates" repository (# yum install thinkfinger).

==== Gentoo ====
<pre>
emerge sys-auth/thinkfinger
</pre>

==== OpenSUSE ====
openSUSE 10.2 includes the package "libthinkfinger" (version 0.1-7) - you will find newer packages [http://beta1.suse.com/private/thoenig/10.2/thinkfinger/ here].

== Testing the driver ==

Now the driver is installed and should be working. You can try it (as root) with

{{cmdroot|tf-tool --acquire}}

and

{{cmdroot|tf-tool --verify}}

This will ask you to swipe your finger three times, save the fingerprint to /tmp/test.bir and then verify your fingerprint with the bir-file.

== Configuring PAM to use ThinkFinger ==
Now you can configure PAM to use ThinkFinger:

Open {{path|/etc/pam.d/common-auth}} (In FC6, F7, and Gentoo, this file is {{path|/etc/pam.d/system-auth}}):

{{cmdroot|nano -w /etc/pam.d/common-auth}}

Add this line before any pam_unix or pam_unix2 directives:
auth sufficient pam_thinkfinger.so

If your PAM uses the pam_unix and not the pam_unix2 module, you need to pass a specific argument in
the /etc/pam.d/common-auth directive to make it consider the password entered at the pam_thinkfinger prompt.
auth required pam_unix.so try_first_pass

For instance, {{path|/etc/pam.d/common-auth}} looks like this:
auth sufficient pam_thinkfinger.so
auth required pam_unix.so nullok_secure try_first_pass

On openSUSE 10.2, it looks like this now:
auth required pam_env.so
auth sufficient pam_thinkfinger.so
auth required pam_unix2.so

Now we are ready to add users to thinkfinger. You can add a fingerprint for a user with:

{{cmdroot|tf-tool --add-user $USERNAME}}

Now the user should be able to login with his finger instead of the password.

If you would like to use thinkfinger for su, you have to enroll the fingerprint for root user with:

{{cmdroot|tf-tool --add-user root}}

{{NOTE|You should see the "Password or swipe finger:" prompt when trying to sudo or su. If you don't, you probably do not have the "User level driver support" compiled into your kernel or the "uinput" module loaded!}}

== xscreensaver/gnome-screensaver ==
{{NOTE|In Fedora 7, the package has been modified in such a way as to make doing this unnecessary.}}

If you'd like to be able to unlock your screen using the fingerprint reader, you must have current versions of xscreesaver (>~5.03) or gnome-screensaver (>~2.18.2). Then you must give yourself access to the fingerprint reader and your bir-file, because unlike login/gdm/su/sudo, both gnome-screensaver and xscreensaver do not run as root. The following procedure will make the fingerprint reader accessible to members of the "fingerprint" group.

Make the group: {{cmdroot|groupadd fingerprint}}

Save the following as {{path|/etc/udev/rules.d/60-thinkfinger.rules}} and run {{cmdroot|sudo /sbin/udevtrigger}} (you may need to reboot for this to take effect if udev trigger does not work):
#
# udev rules file for the thinkfinger fingerprint scanner
#
# gives access to the fingerprint reader to those in the "fingerprint" group
#
# Taken from:
# http://www.thinkwiki.org/wiki/How_to_enable_the_fingerprint_reader_with_ThinkFinger
# which was taken and modified from:
# http://article.gmane.org/gmane.linux.drivers.thinkfinger/329
#

# SGS Thomson Microelectronics Fingerprint Reader
SYSFS{idVendor}=="0483", SYSFS{idProduct}=="2016", SYMLINK+="input/thinkfinger-%k", MODE="0660", GROUP="fingerprint"

# the also-needed uinput device
KERNEL=="uinput", MODE="0660", GROUP="fingerprint"

Finally, edit {{path|/etc/pam.d/gnome-screensaver}} so that it looks like this:
auth sufficient pam_thinkfinger.so
auth required pam_unix.so try_first_pass nullok_secure

Per user:

# Add him to the group: {{cmdroot|gpasswd -a $USERNAME fingerprint}}
# Make him owner of his bir-file: {{cmdroot|chown $USERNAME:root /etc/pam_thinkfinger/$USERNAME.bir}}
# Give him read-only access to his bir-file: {{cmdroot|chmod 400 /etc/pam_thinkfinger/$USERNAME.bir}}
# Give "execute only" access to everyone for the /etc/pam_thinkfinger/ directory: {{cmdroot|chmod o+x /etc/pam_thinkfinger}} (WARNING: this opens up security a little).

== GNOME ==

{{NOTE|1=This problem should be solved if you're using sudo >= 1.6.9p9. Links: [http://savannah.nongnu.org/bugs/?19132], [http://www.sudo.ws/bugs/show_bug.cgi?id=180], [https://bugs.launchpad.net/ubuntu/+source/gksu/+bug/86843]}}

gksu/gksudo doesn't work correctly. It just stays invisible. When starting a su privileged application such as synaptics you will not get prompted for the password. Nevertheless you can swipe your finger and it should authenticate you. Starting synaptics twice makes gksudo visible.

There are two possibilities to solve it:
* Changing the string "Password or swipe finger:" to a plain "Password:" (like sudo normally would do) in the file pam/pam_thinkfinger.c of the thinkfinger source directory. Of course, in the console you will then only see a "Password:" instead of "Password or swipe finger:" but this is still more usefull than having gksu/gksudo crashing everytime.
* Patching libgksu with the following patch. This is also a nasty hack until a better solution is implemented.
<pre>
--- libgksu-2.0.3/libgksu/libgksu.c.orig 2007-06-17 16:00:24.000000000 +0200
+++ libgksu-2.0.3/libgksu/libgksu.c 2007-06-17 16:00:47.000000000 +0200
@@ -2663,7 +2663,7 @@
*/
for (counter = 0; counter < 50; counter++)
{
- if (strncmp (buffer, "GNOME_SUDO_PASS", 15) == 0)
+ if (strncmp (buffer, "GNOME_SUDO_PASS", 15) == 0 || strncmp (buffer, "Password or swi", 15) == 0)
break;

read_line (parent_pipe[0], buffer, 256);
@@ -2675,7 +2675,7 @@
if (context->debug)
fprintf (stderr, "brute force GNOME_SUDO_PASS ended...\n");

- if (strncmp(buffer, "GNOME_SUDO_PASS", 15) == 0)
+ if (strncmp(buffer, "GNOME_SUDO_PASS", 15) == 0 || strncmp(buffer, "Password or swi", 15) == 0)
{
gchar *password = NULL;
gboolean prompt_grab;
</pre>

== KDE ==

Integration in KDE and kdm seems not to be easily possible now. There is a filed [https://bugs.kde.org/show_bug.cgi?id=116682 bug] at kde.org where you can vote for this.

Moreover, kdm in openSUSE 10.3 crashes when pam_thinkfinger is enabled. A possible "workaround" is downgrading to thinkfinger 0.2.2.

Another workaround is to use Fprint from [http://www.reactivated.net/fprint/wiki/Main_Page] which works quite nicely on my X61s and Kubuntu Hardy.

This Howto was copied from [[Installing Ubuntu 6.06 on a ThinkPad T43#Fingerprint_Reader]] and then slightly modified.

== Fix for the fingerprint reader getting too hot ==

If you notice that you fingerprint reader occasionally gets very hot then you might be interested in this section. Thanks to Tino Keitel, he actually gave me this solution through

First we need to

How to enable the integrated fingerprint reader with ThinkFinger

2008-08-01T16:06:47Z

Lunatico:

[[How to enable the fingerprint reader]] has a good explanation for using the fingerprint reader with the closed-source binary driver. But there is also an opensource project called [http://thinkfinger.sourceforge.net ThinkFinger] which does the same, but open.

However: The fingerprint reader is an INSECURE device and gives a false sense of security! There has been quite a bit of research by a hacker named Starbug, a member of the Chaos Computer Club, Berlin, Germany. He outlined in two very good talks how to forge each and every available fingerprint sensor available at the cost of a few euros, using materials from your local hardware store, a digicam and a laser printer! Here's some links:
* [http://www.ccc.de/updates/2007/umsonst-im-supermarkt?language=en Fingerprint recognition in supermarkets]
* [ftp://ftp.ccc.de/pub/video/Fingerabdruck_Hack/fingerabdruck.mpg?language=en Video tutorial for forging fingerprints]

== Installing ==
=== From source ===

Download thinkfinger-0.3.tar.gz from the [http://thinkfinger.sourceforge.net/ homepage] and unpack it somewhere, make sure you have the gcc compiler, libtool, pkg-config, libusb-dev and libpam0g-dev installed, then:

{{cmduser|cd thinkfinger-0.3}}

<code style="white-space:nowrap;color:#495988;background-color:white;"><nowiki>$</nowiki> ./configure --prefix=/usr --sysconfdir=/etc --with-securedir=/lib/security --with-birdir=/etc/pam_thinkfinger</code>

{{cmduser|make}}

{{cmdroot|make install}}

{{NOTE|/lib/security is the directory, where PAM assumes its modules on Debian and openSUSE, it may vary for your distro!}}

"make install" doesn't create the birdir we specified (where thinkfinger will store users' biometric info), so create it:

{{cmdroot|mkdir /etc/pam_thinkfinger}}

If everything went OK assert that you find pam_thinkfinger.so in /lib/security typing:

{{cmduser|ls /lib/security}}

=== From package ===

==== Debian ====
[http://packages.debian.org/source/experimental/thinkfinger Packages] arrived in Debian experimental on Aug 2nd, 2007 (cf. [http://bugs.debian.org/409563 bug #409563]). To access the experimental packages via apt, add the following lines to your sources.list:
<pre>
# experimental
deb ftp://mirrors.kernel.org/debian/ experimental main contrib non-free
deb-src ftp://mirrors.kernel.org/debian/ experimental main contrib non-free
</pre>
where of course you may replace mirrors.kernel.org with your mirror of choice. Just make sure that it hosts the experimental repositories.
<pre>
aptitude update
aptitude install libthinkfinger0 libpam-thinkfinger thinkfinger-tools
</pre>
should then get you up and running.

==== Ubuntu ====

===== Hardy =====

Hardy includes the latest thinkfinger and it is up to date with subversion. Install packages:

{{cmduser|sudo apt-get install thinkfinger-tools libpam-thinkfinger}}

Update the pam configuration files:

{{cmduser|sudo /usr/lib/pam-thinkfinger/pam-thinkfinger-enable}}

Enroll your fingerprint (creates $HOME/.thinkfinger.bir). If this gives an error about claiming the USB device then reboot. {{NOTE|Do not try to enroll using 'sudo' - it will cause hidden permission problems}}

{{cmduser|tf-tool --acquire}}

Check fingerprint enrollment

{{cmduser|tf-tool --verify}}

You can expect everything to work correctly. Note that you still have to enter your username if prompted but will be able
to swipe your finger instead of the password. The prompt will usually be "Password or swipe finger"

* Graphical login
* Text console login
* sudo
* screen lock/screen saver
* Administrative password prompt (eg for update or package managers). (Note no "or swipe finger" in prompt).

===== Gutsy =====

From https://wiki.ubuntu.com/ThinkFinger

Add PPA repositories to your sources.list:
<pre>
deb http://ppa.launchpad.net/jldugger/ubuntu gutsy main restricted universe multiverse
deb-src http://ppa.launchpad.net/jldugger/ubuntu gutsy main restricted universe multiverse
</pre>

Install necessary packages:

{{cmduser|sudo apt-get install thinkfinger-tools libpam-thinkfinger}}

==== Fedora/Fedora Core ====
*Packages for Fedora Core 6 are available in "extras" repository (# yum install thinkfinger).
*Packages for Fedora 7 are available in the "updates" repository (# yum install thinkfinger).

==== Gentoo ====
<pre>
emerge sys-auth/thinkfinger
</pre>

==== OpenSUSE ====
openSUSE 10.2 includes the package "libthinkfinger" (version 0.1-7) - you will find newer packages [http://beta1.suse.com/private/thoenig/10.2/thinkfinger/ here].

== Testing the driver ==

Now the driver is installed and should be working. You can try it (as root) with

{{cmdroot|tf-tool --acquire}}

and

{{cmdroot|tf-tool --verify}}

This will ask you to swipe your finger three times, save the fingerprint to /tmp/test.bir and then verify your fingerprint with the bir-file.

== Configuring PAM to use ThinkFinger ==
Now you can configure PAM to use ThinkFinger:

Open {{path|/etc/pam.d/common-auth}} (In FC6, F7, and Gentoo, this file is {{path|/etc/pam.d/system-auth}}):

{{cmdroot|nano -w /etc/pam.d/common-auth}}

Add this line before any pam_unix or pam_unix2 directives:
auth sufficient pam_thinkfinger.so

If your PAM uses the pam_unix and not the pam_unix2 module, you need to pass a specific argument in
the /etc/pam.d/common-auth directive to make it consider the password entered at the pam_thinkfinger prompt.
auth required pam_unix.so try_first_pass

For instance, {{path|/etc/pam.d/common-auth}} looks like this:
auth sufficient pam_thinkfinger.so
auth required pam_unix.so nullok_secure try_first_pass

On openSUSE 10.2, it looks like this now:
auth required pam_env.so
auth sufficient pam_thinkfinger.so
auth required pam_unix2.so

Now we are ready to add users to thinkfinger. You can add a fingerprint for a user with:

{{cmdroot|tf-tool --add-user $USERNAME}}

Now the user should be able to login with his finger instead of the password.

If you would like to use thinkfinger for su, you have to enroll the fingerprint for root user with:

{{cmdroot|tf-tool --add-user root}}

{{NOTE|You should see the "Password or swipe finger:" prompt when trying to sudo or su. If you don't, you probably do not have the "User level driver support" compiled into your kernel or the "uinput" module loaded!}}

== xscreensaver/gnome-screensaver ==
{{NOTE|In Fedora 7, the package has been modified in such a way as to make doing this unnecessary.}}

If you'd like to be able to unlock your screen using the fingerprint reader, you must have current versions of xscreesaver (>~5.03) or gnome-screensaver (>~2.18.2). Then you must give yourself access to the fingerprint reader and your bir-file, because unlike login/gdm/su/sudo, both gnome-screensaver and xscreensaver do not run as root. The following procedure will make the fingerprint reader accessible to members of the "fingerprint" group.

Make the group: {{cmdroot|groupadd fingerprint}}

Save the following as {{path|/etc/udev/rules.d/60-thinkfinger.rules}} and run {{cmdroot|sudo /sbin/udevtrigger}} (you may need to reboot for this to take effect if udev trigger does not work):
#
# udev rules file for the thinkfinger fingerprint scanner
#
# gives access to the fingerprint reader to those in the "fingerprint" group
#
# Taken from:
# http://www.thinkwiki.org/wiki/How_to_enable_the_fingerprint_reader_with_ThinkFinger
# which was taken and modified from:
# http://article.gmane.org/gmane.linux.drivers.thinkfinger/329
#

# SGS Thomson Microelectronics Fingerprint Reader
SYSFS{idVendor}=="0483", SYSFS{idProduct}=="2016", SYMLINK+="input/thinkfinger-%k", MODE="0660", GROUP="fingerprint"

# the also-needed uinput device
KERNEL=="uinput", MODE="0660", GROUP="fingerprint"

Finally, edit {{path|/etc/pam.d/gnome-screensaver}} so that it looks like this:
auth sufficient pam_thinkfinger.so
auth required pam_unix.so try_first_pass nullok_secure

Per user:

# Add him to the group: {{cmdroot|gpasswd -a $USERNAME fingerprint}}
# Make him owner of his bir-file: {{cmdroot|chown $USERNAME:root /etc/pam_thinkfinger/$USERNAME.bir}}
# Give him read-only access to his bir-file: {{cmdroot|chmod 400 /etc/pam_thinkfinger/$USERNAME.bir}}
# Give "execute only" access to everyone for the /etc/pam_thinkfinger/ directory: {{cmdroot|chmod o+x /etc/pam_thinkfinger}} (WARNING: this opens up security a little).

== GNOME ==

{{NOTE|1=This problem should be solved if you're using sudo >= 1.6.9p9. Links: [http://savannah.nongnu.org/bugs/?19132], [http://www.sudo.ws/bugs/show_bug.cgi?id=180], [https://bugs.launchpad.net/ubuntu/+source/gksu/+bug/86843]}}

gksu/gksudo doesn't work correctly. It just stays invisible. When starting a su privileged application such as synaptics you will not get prompted for the password. Nevertheless you can swipe your finger and it should authenticate you. Starting synaptics twice makes gksudo visible.

There are two possibilities to solve it:
* Changing the string "Password or swipe finger:" to a plain "Password:" (like sudo normally would do) in the file pam/pam_thinkfinger.c of the thinkfinger source directory. Of course, in the console you will then only see a "Password:" instead of "Password or swipe finger:" but this is still more usefull than having gksu/gksudo crashing everytime.
* Patching libgksu with the following patch. This is also a nasty hack until a better solution is implemented.
<pre>
--- libgksu-2.0.3/libgksu/libgksu.c.orig 2007-06-17 16:00:24.000000000 +0200
+++ libgksu-2.0.3/libgksu/libgksu.c 2007-06-17 16:00:47.000000000 +0200
@@ -2663,7 +2663,7 @@
*/
for (counter = 0; counter < 50; counter++)
{
- if (strncmp (buffer, "GNOME_SUDO_PASS", 15) == 0)
+ if (strncmp (buffer, "GNOME_SUDO_PASS", 15) == 0 || strncmp (buffer, "Password or swi", 15) == 0)
break;

read_line (parent_pipe[0], buffer, 256);
@@ -2675,7 +2675,7 @@
if (context->debug)
fprintf (stderr, "brute force GNOME_SUDO_PASS ended...\n");

- if (strncmp(buffer, "GNOME_SUDO_PASS", 15) == 0)
+ if (strncmp(buffer, "GNOME_SUDO_PASS", 15) == 0 || strncmp(buffer, "Password or swi", 15) == 0)
{
gchar *password = NULL;
gboolean prompt_grab;
</pre>

== KDE ==

Integration in KDE and kdm seems not to be easily possible now. There is a filed [https://bugs.kde.org/show_bug.cgi?id=116682 bug] at kde.org where you can vote for this.

Moreover, kdm in openSUSE 10.3 crashes when pam_thinkfinger is enabled. A possible "workaround" is downgrading to thinkfinger 0.2.2.

Another workaround is to use Fprint from [http://www.reactivated.net/fprint/wiki/Main_Page] which works quite nicely on my X61s and Kubuntu Hardy.

This Howto was copied from [[Installing Ubuntu 6.06 on a ThinkPad T43#Fingerprint_Reader]] and then slightly modified.

== Fix for the fingerprint getting too hot ==

If you notice that you fingerprint reader occasionally gets very hot then you might be interested in this section.

Installing Ubuntu 8.04 (Hardy Heron) on a ThinkPad T61

2008-07-26T12:50:12Z

Lunatico: /* To enable the Wifi LED with the Atheros cards */

== Items that work out of the box ==

'''Intel Video:''' 2D and 3D acceleration works

'''Nvidia Video:''' 2D and 3D acceleration works

'''Wireless:''' Intel cards tested. Atheros cards also works.

'''Wireless WAN:''' Cingular/AT&T card tested.

'''Network Card''' Intel 10/100/1000 tested

'''Wireless switch''' Tested (Only has an effect over the bluetooth, wifi is unaffected)

'''Webcam''' Tested with cheese and skype.

'''Headphones''' Works out of the box

'''Microphone''' Just needs to be activated, see section [[#Audio|below]]

'''Keyboard Shortcuts:''' Most of them work out of the box, some need to be activated, see section [[#Multimedia_Keys|below]]

== Items that need (some) tweaking to obtain full functionality ==

=== Open Source Intel Wifi Driver ===
The following information is important if you are upgrading from a previous version of Ubuntu to 8.04.

Intel has created a new Linux Wifi driver project for Intel Wireless cards, "[[Iwlwifi]]". This driver is Open Source and no longer requires the Intel daemon to run in addition. This project will support the [[:Category:T61 | T61]]'s Wifi [[Intel PRO/Wireless 3945ABG Mini-PCI Express Adapter | Intel 3945ABG network adapter]] and [[Intel PRO/Wireless 4965AGN Mini-PCI Express Adapter| Intel 4965AGN network adapter]].

An automatic migration will occur when upgrading from [[Installing Ubuntu 7.10 (Gutsy Gibbon) on a ThinkPad T61|Ubuntu 7.10]] to Ubuntu 8.04. However, there is a caveat to be aware of:
* The new driver wants to name the interface wlan0 (by default -- you can rename it to anything you want), and requires a different entry in {{path|/etc/udev/rules.d/70-persistent-net.rules}}, which handles the naming of interfaces. Simply edit this file and delete your old entry for the ipw3945 driver, then unload/reload the new driver, or simply reboot. A new entry will automatically be created that is appropriate for the new driver. Here's an example of the lines to delete:
<pre>
# PCI device 0x8086:0x4227 (ipw3945)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:1b:77:a4:0e:2f", NAME="eth1"
</pre>

If you need to perform a manual migration, the Ubuntu Help Community has written some [https://help.ubuntu.com/community/WifiDocs/Driver/iwlwifi_Intel_3945_4965/gutsy documentation] that will make this very easy to do.

=== Compiz and XV Playback on Intel GM965/GL960 ===

With Ubuntu 7.10 (Gutsy Gibbon) you currently have to choose between using Compiz and working video playback using XV. On 8.04 (Hardy Heron) alpha 5 you can play videos using XV under compiz, it works right out of the box using the Live-CD.

=== Suspend with Nv140m ===

** Update as of July 17th 2008 -- Using 8.04.1 with the newest nvidea drivers, I had no problems suspending without any additional configuration. **

Suspend may not work even after editing acpi-support. Enable bluetooth (Fn+F5) may result in a successful suspend. NOTE: that although the wifi led does not change when Fn+F5 is used, the wifi is still toggled by this key.

'''Hal "S3 BIOS" parameter issue!'''

After doing the changes to the /etc/default/acpi-support file (described [http://www.thinkwiki.org/wiki/Installing_Ubuntu_7.10_(Gutsy_Gibbon)_on_a_ThinkPad_T61#How_to_Suspend_with_nVidia_140m.2F570m here]), I for one, managed to have '''stable''' suspend support by creating a new file called: '''/etc/hal/fdi/information/lenovo.fdi''' with the following contents:
<pre>
<?xml version="1.0" encoding="ISO-8859-1"?> 
<deviceinfo version="0.2">
<device>
<match key="system.hardware.vendor" string="LENOVO">
<merge key="power_management.quirk.s3_bios" type="bool">false</merge>
</match>
</device>
</deviceinfo>
</pre>
{{NOTE|The problem (after reading the HAL and pm-utils documentations) is the fact that (as far as I can tell) the T61 Lenovo doesn't allow the S3 BIOS to be called *during* suspend/resume, which HAL seems to do by default (who knows, maybe there are T61s out there that do work with this default)!

This did not seem to be necessary for previous versions of Ubuntu. Also note that I have an NVIDIA card so I have no idea what to do for Intel versions.The change should also be resistant to HAL and pm-utils upgrades.}}

'''Still no suspend with nvs140m? Got Modell 6460?'''

Fix above didn't work for me on a 15.4 wide T61 Modell 6460 with nv140m. Bios is updated to 2.14 but didn't change anything, except the usb bug is fix. Suspend seems to work fine, but resume gives me a black screen (backlight off - no reaction to brightness up) and I can hear 2 beeps. Most of the time I can reboot with ctrl+alt+delete but the screen stays dark until bios.

follow the instructions above but create the new file called: '''/etc/hal/fdi/information/lenovo.fdi''' with the following contents instead:
<pre>
<?xml version="1.0" encoding="ISO-8859-1"?> 
<deviceinfo version="0.2">
<device>
<match key="system.hardware.vendor" string="LENOVO">
<merge key="power_management.quirk.s3_mode" type="bool">true</merge>
<merge key="power_management.quirk.s3_bios" type="bool">false</merge>
<merge key="power_management.quirk.save_pci" type="bool">true</merge>
</match>
</device>
</deviceinfo>
</pre>

Also you want to set the following parameter in

{{path|/etc/default/acpi-support}}
<pre>
SAVE_VIDEO_PCI_STATE=true
</pre>

{{NOTE|This works for me with mode 6460, except for one problem: You may get a white screen in xorg after resume when using compiz. If you don't have a 6460 with nvidia this file may break things for you because it doesn't care about the modell and sets the parameter for any lenovo product}}
{{HELP|Anyone with more knowledge of hal and acpi-support is welcome to clean this up. I also don't know why this setting can be done via hal and in acpi-support.
See below!}}

'''Working on hardy final'''

After trying out all these recipes on my 6457CTO waking up from suspend still did not work. Finally I came across a blog entry which pointed out the right way: [[http://david.goodlad.ca/2008/3/14/suspend-hibernate-on-lenovo-t61 David Goodlad's blog]]. I realized that all the fixes proposing editing the acpi-support file or adding a kernel parameter acpi_sleep=s3_mode must be wrong because since hardy gnome-power-manager gets its information solely from hal. So setting up correct hal information is the right way but the proposed solution (creating a /etc/hal/fdi/information/lenovo.fdi file) did not work for me. Ok, but now step by step:

# Revert ALL the proposed fixes from above. I found out that at least the lenovo.fdi solution is actually breaking the real fix. So for sure delete /etc/hal/fdi/information/lenovo.fdi
# Find out about the excact hal name of your machine: <pre>hal-device |grep 6457</pre> where 6457 is the model number of my t61, replace it with your own. In my case it spits out something like this: system.hardware.product = '6457CTO'. So now I know that hal identifies my machine as 6457CTO.
# <pre>sudo gedit /usr/share/hal/fdi/information/10freedesktop/20-video-quirk-pm-lenovo.fdi</pre> and add a section to the end of the file, just above the </device> tag and replace 6457CTO with your hal device name:
<pre>

<match key="system.hardware.product" string="6457CTO">

<merge key="power_management.quirk.s3_mode" type="bool">true</merge>
<merge key="power_management.quirk.s3_bios" type="bool">false</merge>
<merge key="power_management.quirk.save_pci" type="bool">true</merge>
</match>
</pre>

Now save and reboot. Now you might run into the problem of coming back from resume into a completely white screen where normally should be the password dialog. Entering your password blindly is not nice but at least you can resume.

{{NOTE|Somehow I couldn't make the wildcard matching work as they did in the lenovo.fdi solution, but that might be due to my shortcomings on that syntax. Anyway matching the device by its full name worked for me. Probably somebody who knows more about the matching could make that wildcard thing work to have a more general solution. Because hal also knows the xorg driver name (info.linux.driver) there should be a way to set up the quirks depending on the driver.}}

[[Category: T61]]

=== TrackPoint ===
The [[TrackPoint]] works out of the box, but does not scroll nor does the tap-clicking (press to select) feature work. Therefor see: [[#tap-to-click feature]] To enable using the middle mouse button to scroll, replace the "Configured Mouse" section in {{path|/etc/X11/xorg.conf}} with the following:
<pre>
Section "InputDevice"
Identifier "Trackpoint"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ImPS/2"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "true"
Option "EmulateWheel" "true"
Option "EmulateWheelButton" "2"
EndSection
</pre>

{{NOTE|However, if you need to use external usb mouse, the above configuration is wrong. It will cause odd behavior. Try the following configuration from [http://gentoo-wiki.com/HARDWARE_IBM_Specific_Laptop_Guide#TrackPoint Gentoo Wiki]:}}
<pre>
Section "InputDevice"
Identifier "UltraNav TrackPoint"
Driver "mouse"
Option "Device" "/dev/input/mouse1"
Option "Protocol" "ExplorerPS/2"
Option "Emulate3Buttons" "on"
Option "Emulate3TimeOut" "50"
Option "EmulateWheel" "on"
Option "EmulateWheelTimeOut" "200"
Option "EmulateWheelButton" "2"
Option "YAxisMapping" "4 5"
Option "XAxisMapping" "6 7"
Option "ZAxisMapping" "4 5"
EndSection
</pre>

=== Audio ===

Works great out of the box, just the microphone has to be activated, it is considered a generic capture source and is muted by default.

To unmute the microphone:

*Right Click on the volume icon next to the clock and click on "Open Volume Control"

*Click Edit -> Preferences. A list of devices will be displayed, you should check the following (Do not uncheck any existing items):

Input Source
Capture

*Click Close and there should be two additional tabs "Recording" and "Options". -

*Click Recording and click on the microphone under the Capture slider so that it no longer has a red line through it, and put the slider up as it may be deactivated.

*Click Options and under capture source select internal mic.

To test your mic using Sound Recorder select Capture as the sound source.

This solution has been tested with Sound Recorder and Skype.

To get the volume controls working:

*add the following line to /etc/modprobe.d/alsa-base, then reboot

options snd-hda-intel index=0 model=thinkpad

{{NOTE|The volume controls worked fine for me out of the box on a 6460.}}

=== Multimedia Keys ===

Most Multimedia Keys work out of the box, just the play, forward and stop buttons need to be adjusted, therefore, press alt + F2 and type in gnome-keybinding-properties. Then everything works as followed:

* Fn-PgUp activates/deactivates the thinklight
* Fn-Up will trigger stop on a media player
* Fn-Down will toggle pause and play on a media player
* Fn-Left/Right go to prev/next tracks on a media player
* Fn-F2 properly locks the screen
* Fn-F3 shows remaining battery >>does not work on all machines<<
* Fn-F4 suspends (to ram)
* Fn-F9 ejects cds >>does not work on all machines, I think this is supposed to eject from a "dock"<<
* Fn-F12 hibernates (to disk)
* PrtSc opens the screenshot dialog

To enable the back, forward, and the menu keys you'll need to teach XKB what they are.

* Check the '''XkbLayout''' option (under '''InputDevice''') in your {{path|/etc/X11/xorg.conf}} file to determine which keyboard layout Ubuntu is using (I'll use 'us' for the example).
* Navigate to {{path|/etc/X11/xkb/symbols}} and, as root, open the appropriate layout file (as determined above) in your favorite editor.
{{cmduser|cd /etc/X11/xkb/symbols}}
{{cmduser|sudo gedit us}}
* In the '''xkb_symbols "basic"''' section after the '''name[Group1]= "x";''' (where x is a country name, or similar) line add the following:
key <I63> { [ Menu ] };
key <I69> { [ XF86Forward ] };
key <I6A> { [ XF86Back ] };
* Now log out and back in and all three of the buttons should function.

=== Thinkpad Button ===

Paste the following into /usr/share/hotkey-setup/ibm.hk
setkeycodes e017 148 # thinkpad button
You can also just type this into a terminal, to test it for the time of the current session.

Paste the following into the right file in /usr/share/xmodmap (check your country code)
keycode 159 = XF86Terminal
For immediate availability of the button, reload the file by executing
xmodmap <xmodmap.file>

Then use the "Keyboard Shortcuts" tool under "Preferences".

== Items that don't work (a.k.a.: items that need more intense tweaking to get fixed)==

=== tap-to-click feature ===

For the tap-to-click feature (taping the stick instead of using the left mouse button) i used a configure trackpoint utility: [http://tpctl.sourceforge.net/configure-trackpoint.html] there is a package for ubuntu 7.04 i386, but i compiled it by myself (using amd64):

1.) download the .tar.gz file

2.) unpack it

3.) install libgnomeui-dev

{{cmduser|sudo aptitude install libgnomeui-dev}}

4.) in the folder, do:

{{cmduser|./configure}}

if everything worked fine:

{{cmduser|make}}

then install it:

{{cmduser|sudo make install}}

5.a) Gnome : Open it: System > configure trackpoint, and configure on your needs

5.b) Kde : K-menu > Prefences > configure trackpoint > right-click > edit entry, edit "command" to "kdesu configure-trackpoint"

Save & exit

Open it : K-menu > Prefences > configure trackpoint and configure on your needs

=== Hotswapping ===

{{HELP|We need someone who is able to get hotswaping to work properly, this is not the right was to do this!}}
With the new kernel, bay-drivers changed, so if you remove the ultrabay it will freeze your system! You can hack it with a simple comand, first you have to look where the device is:

{{cmduser|less /sys/class/scsi_device/(x)\:0\:0\:0/device/model}}

for (x) first put in 0, if it tells you DVD or the name of the model you want to hotswap youre right. if not, go on with 1, 2 or 3...

then, once you are sure (I deactivated my harddisk like that) you put in:

{{cmduser|echo 1 {{!}} sudo tee /sys/class/scsi_device/(x)\:0\:0\:0/device/delete}}

Now you should be able to remove the device.

{{WARN|Do not use it for harddisks, be sure you unmounted it before! This is just a bad hack, if anyone knows how to get it right --> publish!}}

If Ubuntu does not reactivate the device after putting it in again, do:

{{cmduser|echo 0 0 0 {{!}} sudo tee /sys/class/scsi_host/host1/scan}}

=== Wireless activity LED ===

The LED is not implemented at least in the IWL4965 driver. For the Atheros wifi cards look at the solution below.

A patch posted in this [http://bughost.org/bugzilla/show_bug.cgi?id=1209 thread] works for me on R61 with IWL4965 card.

{{HELP|A howto is needed showing the process of implementing the patch in Hardy Heron. If anyone knows how to do this, please create a quick howto and either put it here or link to it from this page. Please and thank you.}}

As an alternative, you can install a backported IWL4965 driver that ''may'' fix the LED problem on your system.

To active WiFi LED,

sudo apt-get install linux-backports-modules-hardy

{{NOTE|On some machines, (at least one running IWL3945 & IWL4965) applying the above turns on the LED permanently. It should flicker as data is being transmitted. Also, with the above modification, after turning off wireless and then turning it back on (via the switch on the front of the machine) wireless is not reactivated, so not very helpful}}

You can download a compatible [http://wireless.kernel.org/download/compat-wireless-2.6/compat-wireless-2.6.tar.bz2 driver] which supports WiFi led flicking and build it with modifying the {{path|config.mk}} by adding {{bootparm|CONFIG_IWL3945_LEDS|y}} and {{bootparm|CONFIG_IWLWIFI_LEDS|y}} these two options. For Ubuntu/Debian users, build-essential, linux-source-2.6.24 and linux-headers-generic packages are required.

{{HELP|I added the above lines to the config.mk file and it would not make or make install correctly. I received an error 2 at the end of the make. If you have had success, where did you put the items in the config.mk file for it to make and make install correctly? Thanks in advance.}}

==== To enable the Wifi LED with the Atheros cards ====

First check if this solution works on your computer. Open a terminal and run this commands:

sysctl dev.wifi0.ledpin=1
sysctl dev.wifi0.softled=3

Now connect to a wireless network and the LED should start working. If so and you want to make the changes permanent then:

1) Create a file ~/wifiLED and copy/paste the following into it:

#!/bin/bash
#
# Commands to enable the wireless LED
sysctl dev.wifi0.ledpin=1
sysctl dev.wifi0.softled=3

2) sudo cp ~/wifiLED /etc/init.d

3) sudo chmod 755 /etc/init.d/wifiLED

4) sudo update-rc.d wifiLED defaults 90

After you reboot your wireless led should be working.

--[[User:Lunatico|Lunatico]] 14:50, 26 July 2008 (CEST)

=== Hidden SSID ===
It has been reported that users wanting to access Hidden SSIDs have to enter the SSID and password manually in Network Manager to connect. Even after the SSID is saved in Network Manager, it will not reconnect automatically. The user has to connect manually by entering the information as previously described.
It appears that updating the driver by following the instructions [http://linuxwireless.org/en/users/Download here] resolves this issue.

=== Hard Disk Parking ===
Getting hard disk parking to work:

tp_smapi patch is not needed in [http://packages.ubuntu.com/search?keywords=linux-image-2.6.24-18&searchon=names&suite=hardy&section=all linux-image-2.6.24-18]

1. Patch your kernel with the 'protect' [http://www.thinkwiki.org/wiki/HDAPS#Kernel_patch patch].

2. Installing the hdapsd daemon which does the actual parking.

{{cmduser|sudo apt-get install hdapsd hdaps-utils}}

== some other tweaks ==

=== screenblank with {{key|Fn}} + {{key|F3}} ===

Its ok, and might be usefull to get the estimated batterytime when pressing {{key|Fn}}+{{key|F3}}, as it should be. But i dont need that, i find the earlier command for {{key|F3}}, to blank the screen, more useful to save batterylife better.

For that, you must edit {{path|/etc/acpi/thinkpad-lockbattery.sh}} and replace LENOVO by IBM, and IBM by LENOVO :). Do not forget to copy the file before you change it!

=== Enable normal User to Limit CPU Speed ===
To let user set the CPU limit you need to open a Terminal an type there
sudo dpkg-reconfigure gnome-applets
answer the question with yes

=== Fix bluish WSXGA+ displays ===
Many T61 owners complain about a very bluish color temperature: My T61 WSXGA+ was also way too blue. I came across a thread at the notebook review forum http://forum.notebookreview.com/showthread.php?t=174408 which provided two useful ICC profiles which fixed the situation for me. Just install xcalib
sudo apt-get install xcalib
and load one of these profiles.

[[Category: Ubuntu 8.04]]

Installing Ubuntu 8.04 (Hardy Heron) on a ThinkPad T61

2008-07-24T14:26:01Z

Lunatico: /* Items that work out of the box */

== Items that work out of the box ==

'''Intel Video:''' 2D and 3D acceleration works

'''Nvidia Video:''' 2D and 3D acceleration works

'''Wireless:''' Intel cards tested. Atheros cards also works.

'''Wireless WAN:''' Cingular/AT&T card tested.

'''Network Card''' Intel 10/100/1000 tested

'''Wireless switch''' Tested (Only has an effect over the bluetooth, wifi is unaffected)

'''Webcam''' Tested with cheese and skype.

'''Headphones''' Works out of the box

'''Microphone''' Just needs to be activated, see section [[#Audio|below]]

'''Keyboard Shortcuts:''' Most of them work out of the box, some need to be activated, see section [[#Multimedia_Keys|below]]

== Items that need (some) tweaking to obtain full functionality ==

=== Open Source Intel Wifi Driver ===
The following information is important if you are upgrading from a previous version of Ubuntu to 8.04.

Intel has created a new Linux Wifi driver project for Intel Wireless cards, "[[Iwlwifi]]". This driver is Open Source and no longer requires the Intel daemon to run in addition. This project will support the [[:Category:T61 | T61]]'s Wifi [[Intel PRO/Wireless 3945ABG Mini-PCI Express Adapter | Intel 3945ABG network adapter]] and [[Intel PRO/Wireless 4965AGN Mini-PCI Express Adapter| Intel 4965AGN network adapter]].

An automatic migration will occur when upgrading from [[Installing Ubuntu 7.10 (Gutsy Gibbon) on a ThinkPad T61|Ubuntu 7.10]] to Ubuntu 8.04. However, there is a caveat to be aware of:
* The new driver wants to name the interface wlan0 (by default -- you can rename it to anything you want), and requires a different entry in {{path|/etc/udev/rules.d/70-persistent-net.rules}}, which handles the naming of interfaces. Simply edit this file and delete your old entry for the ipw3945 driver, then unload/reload the new driver, or simply reboot. A new entry will automatically be created that is appropriate for the new driver. Here's an example of the lines to delete:
<pre>
# PCI device 0x8086:0x4227 (ipw3945)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:1b:77:a4:0e:2f", NAME="eth1"
</pre>

If you need to perform a manual migration, the Ubuntu Help Community has written some [https://help.ubuntu.com/community/WifiDocs/Driver/iwlwifi_Intel_3945_4965/gutsy documentation] that will make this very easy to do.

=== Compiz and XV Playback on Intel GM965/GL960 ===

With Ubuntu 7.10 (Gutsy Gibbon) you currently have to choose between using Compiz and working video playback using XV. On 8.04 (Hardy Heron) alpha 5 you can play videos using XV under compiz, it works right out of the box using the Live-CD.

=== Suspend with Nv140m ===

** Update as of July 17th 2008 -- Using 8.04.1 with the newest nvidea drivers, I had no problems suspending without any additional configuration. **

Suspend may not work even after editing acpi-support. Enable bluetooth (Fn+F5) may result in a successful suspend. NOTE: that although the wifi led does not change when Fn+F5 is used, the wifi is still toggled by this key.

'''Hal "S3 BIOS" parameter issue!'''

After doing the changes to the /etc/default/acpi-support file (described [http://www.thinkwiki.org/wiki/Installing_Ubuntu_7.10_(Gutsy_Gibbon)_on_a_ThinkPad_T61#How_to_Suspend_with_nVidia_140m.2F570m here]), I for one, managed to have '''stable''' suspend support by creating a new file called: '''/etc/hal/fdi/information/lenovo.fdi''' with the following contents:
<pre>
<?xml version="1.0" encoding="ISO-8859-1"?> 
<deviceinfo version="0.2">
<device>
<match key="system.hardware.vendor" string="LENOVO">
<merge key="power_management.quirk.s3_bios" type="bool">false</merge>
</match>
</device>
</deviceinfo>
</pre>
{{NOTE|The problem (after reading the HAL and pm-utils documentations) is the fact that (as far as I can tell) the T61 Lenovo doesn't allow the S3 BIOS to be called *during* suspend/resume, which HAL seems to do by default (who knows, maybe there are T61s out there that do work with this default)!

This did not seem to be necessary for previous versions of Ubuntu. Also note that I have an NVIDIA card so I have no idea what to do for Intel versions.The change should also be resistant to HAL and pm-utils upgrades.}}

'''Still no suspend with nvs140m? Got Modell 6460?'''

Fix above didn't work for me on a 15.4 wide T61 Modell 6460 with nv140m. Bios is updated to 2.14 but didn't change anything, except the usb bug is fix. Suspend seems to work fine, but resume gives me a black screen (backlight off - no reaction to brightness up) and I can hear 2 beeps. Most of the time I can reboot with ctrl+alt+delete but the screen stays dark until bios.

follow the instructions above but create the new file called: '''/etc/hal/fdi/information/lenovo.fdi''' with the following contents instead:
<pre>
<?xml version="1.0" encoding="ISO-8859-1"?> 
<deviceinfo version="0.2">
<device>
<match key="system.hardware.vendor" string="LENOVO">
<merge key="power_management.quirk.s3_mode" type="bool">true</merge>
<merge key="power_management.quirk.s3_bios" type="bool">false</merge>
<merge key="power_management.quirk.save_pci" type="bool">true</merge>
</match>
</device>
</deviceinfo>
</pre>

Also you want to set the following parameter in

{{path|/etc/default/acpi-support}}
<pre>
SAVE_VIDEO_PCI_STATE=true
</pre>

{{NOTE|This works for me with mode 6460, except for one problem: You may get a white screen in xorg after resume when using compiz. If you don't have a 6460 with nvidia this file may break things for you because it doesn't care about the modell and sets the parameter for any lenovo product}}
{{HELP|Anyone with more knowledge of hal and acpi-support is welcome to clean this up. I also don't know why this setting can be done via hal and in acpi-support.
See below!}}

'''Working on hardy final'''

After trying out all these recipes on my 6457CTO waking up from suspend still did not work. Finally I came across a blog entry which pointed out the right way: [[http://david.goodlad.ca/2008/3/14/suspend-hibernate-on-lenovo-t61 David Goodlad's blog]]. I realized that all the fixes proposing editing the acpi-support file or adding a kernel parameter acpi_sleep=s3_mode must be wrong because since hardy gnome-power-manager gets its information solely from hal. So setting up correct hal information is the right way but the proposed solution (creating a /etc/hal/fdi/information/lenovo.fdi file) did not work for me. Ok, but now step by step:

# Revert ALL the proposed fixes from above. I found out that at least the lenovo.fdi solution is actually breaking the real fix. So for sure delete /etc/hal/fdi/information/lenovo.fdi
# Find out about the excact hal name of your machine: <pre>hal-device |grep 6457</pre> where 6457 is the model number of my t61, replace it with your own. In my case it spits out something like this: system.hardware.product = '6457CTO'. So now I know that hal identifies my machine as 6457CTO.
# <pre>sudo gedit /usr/share/hal/fdi/information/10freedesktop/20-video-quirk-pm-lenovo.fdi</pre> and add a section to the end of the file, just above the </device> tag and replace 6457CTO with your hal device name:
<pre>

<match key="system.hardware.product" string="6457CTO">

<merge key="power_management.quirk.s3_mode" type="bool">true</merge>
<merge key="power_management.quirk.s3_bios" type="bool">false</merge>
<merge key="power_management.quirk.save_pci" type="bool">true</merge>
</match>
</pre>

Now save and reboot. Now you might run into the problem of coming back from resume into a completely white screen where normally should be the password dialog. Entering your password blindly is not nice but at least you can resume.

{{NOTE|Somehow I couldn't make the wildcard matching work as they did in the lenovo.fdi solution, but that might be due to my shortcomings on that syntax. Anyway matching the device by its full name worked for me. Probably somebody who knows more about the matching could make that wildcard thing work to have a more general solution. Because hal also knows the xorg driver name (info.linux.driver) there should be a way to set up the quirks depending on the driver.}}

[[Category: T61]]

=== TrackPoint ===
The [[TrackPoint]] works out of the box, but does not scroll nor does the tap-clicking (press to select) feature work. Therefor see: [[#tap-to-click feature]] To enable using the middle mouse button to scroll, replace the "Configured Mouse" section in {{path|/etc/X11/xorg.conf}} with the following:
<pre>
Section "InputDevice"
Identifier "Trackpoint"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ImPS/2"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "true"
Option "EmulateWheel" "true"
Option "EmulateWheelButton" "2"
EndSection
</pre>

{{NOTE|However, if you need to use external usb mouse, the above configuration is wrong. It will cause odd behavior. Try the following configuration from [http://gentoo-wiki.com/HARDWARE_IBM_Specific_Laptop_Guide#TrackPoint Gentoo Wiki]:}}
<pre>
Section "InputDevice"
Identifier "UltraNav TrackPoint"
Driver "mouse"
Option "Device" "/dev/input/mouse1"
Option "Protocol" "ExplorerPS/2"
Option "Emulate3Buttons" "on"
Option "Emulate3TimeOut" "50"
Option "EmulateWheel" "on"
Option "EmulateWheelTimeOut" "200"
Option "EmulateWheelButton" "2"
Option "YAxisMapping" "4 5"
Option "XAxisMapping" "6 7"
Option "ZAxisMapping" "4 5"
EndSection
</pre>

=== Audio ===

Works great out of the box, just the microphone has to be activated, it is considered a generic capture source and is muted by default.

To unmute the microphone:

*Right Click on the volume icon next to the clock and click on "Open Volume Control"

*Click Edit -> Preferences. A list of devices will be displayed, you should check the following (Do not uncheck any existing items):

Input Source
Capture

*Click Close and there should be two additional tabs "Recording" and "Options". -

*Click Recording and click on the microphone under the Capture slider so that it no longer has a red line through it, and put the slider up as it may be deactivated.

*Click Options and under capture source select internal mic.

To test your mic using Sound Recorder select Capture as the sound source.

This solution has been tested with Sound Recorder and Skype.

To get the volume controls working:

*add the following line to /etc/modprobe.d/alsa-base, then reboot

options snd-hda-intel index=0 model=thinkpad

{{NOTE|The volume controls worked fine for me out of the box on a 6460.}}

=== Multimedia Keys ===

Most Multimedia Keys work out of the box, just the play, forward and stop buttons need to be adjusted, therefore, press alt + F2 and type in gnome-keybinding-properties. Then everything works as followed:

* Fn-PgUp activates/deactivates the thinklight
* Fn-Up will trigger stop on a media player
* Fn-Down will toggle pause and play on a media player
* Fn-Left/Right go to prev/next tracks on a media player
* Fn-F2 properly locks the screen
* Fn-F3 shows remaining battery >>does not work on all machines<<
* Fn-F4 suspends (to ram)
* Fn-F9 ejects cds >>does not work on all machines, I think this is supposed to eject from a "dock"<<
* Fn-F12 hibernates (to disk)
* PrtSc opens the screenshot dialog

To enable the back, forward, and the menu keys you'll need to teach XKB what they are.

* Check the '''XkbLayout''' option (under '''InputDevice''') in your {{path|/etc/X11/xorg.conf}} file to determine which keyboard layout Ubuntu is using (I'll use 'us' for the example).
* Navigate to {{path|/etc/X11/xkb/symbols}} and, as root, open the appropriate layout file (as determined above) in your favorite editor.
{{cmduser|cd /etc/X11/xkb/symbols}}
{{cmduser|sudo gedit us}}
* In the '''xkb_symbols "basic"''' section after the '''name[Group1]= "x";''' (where x is a country name, or similar) line add the following:
key <I63> { [ Menu ] };
key <I69> { [ XF86Forward ] };
key <I6A> { [ XF86Back ] };
* Now log out and back in and all three of the buttons should function.

=== Thinkpad Button ===

Paste the following into /usr/share/hotkey-setup/ibm.hk
setkeycodes e017 148 # thinkpad button
You can also just type this into a terminal, to test it for the time of the current session.

Paste the following into the right file in /usr/share/xmodmap (check your country code)
keycode 159 = XF86Terminal
For immediate availability of the button, reload the file by executing
xmodmap <xmodmap.file>

Then use the "Keyboard Shortcuts" tool under "Preferences".

== Items that don't work (a.k.a.: items that need more intense tweaking to get fixed)==

=== tap-to-click feature ===

For the tap-to-click feature (taping the stick instead of using the left mouse button) i used a configure trackpoint utility: [http://tpctl.sourceforge.net/configure-trackpoint.html] there is a package for ubuntu 7.04 i386, but i compiled it by myself (using amd64):

1.) download the .tar.gz file

2.) unpack it

3.) install libgnomeui-dev

{{cmduser|sudo aptitude install libgnomeui-dev}}

4.) in the folder, do:

{{cmduser|./configure}}

if everything worked fine:

{{cmduser|make}}

then install it:

{{cmduser|sudo make install}}

5.a) Gnome : Open it: System > configure trackpoint, and configure on your needs

5.b) Kde : K-menu > Prefences > configure trackpoint > right-click > edit entry, edit "command" to "kdesu configure-trackpoint"

Save & exit

Open it : K-menu > Prefences > configure trackpoint and configure on your needs

=== Hotswapping ===

{{HELP|We need someone who is able to get hotswaping to work properly, this is not the right was to do this!}}
With the new kernel, bay-drivers changed, so if you remove the ultrabay it will freeze your system! You can hack it with a simple comand, first you have to look where the device is:

{{cmduser|less /sys/class/scsi_device/(x)\:0\:0\:0/device/model}}

for (x) first put in 0, if it tells you DVD or the name of the model you want to hotswap youre right. if not, go on with 1, 2 or 3...

then, once you are sure (I deactivated my harddisk like that) you put in:

{{cmduser|echo 1 {{!}} sudo tee /sys/class/scsi_device/(x)\:0\:0\:0/device/delete}}

Now you should be able to remove the device.

{{WARN|Do not use it for harddisks, be sure you unmounted it before! This is just a bad hack, if anyone knows how to get it right --> publish!}}

If Ubuntu does not reactivate the device after putting it in again, do:

{{cmduser|echo 0 0 0 {{!}} sudo tee /sys/class/scsi_host/host1/scan}}

=== Wireless activity LED ===

The LED is not implemented at least in the IWL4965 driver. For the Atheros wifi cards look at the solution below.

A patch posted in this [http://bughost.org/bugzilla/show_bug.cgi?id=1209 thread] works for me on R61 with IWL4965 card.

{{HELP|A howto is needed showing the process of implementing the patch in Hardy Heron. If anyone knows how to do this, please create a quick howto and either put it here or link to it from this page. Please and thank you.}}

As an alternative, you can install a backported IWL4965 driver that ''may'' fix the LED problem on your system.

To active WiFi LED,

sudo apt-get install linux-backports-modules-hardy

{{NOTE|On some machines, (at least one running IWL3945 & IWL4965) applying the above turns on the LED permanently. It should flicker as data is being transmitted. Also, with the above modification, after turning off wireless and then turning it back on (via the switch on the front of the machine) wireless is not reactivated, so not very helpful}}

You can download a compatible [http://wireless.kernel.org/download/compat-wireless-2.6/compat-wireless-2.6.tar.bz2 driver] which supports WiFi led flicking and build it with modifying the {{path|config.mk}} by adding {{bootparm|CONFIG_IWL3945_LEDS|y}} and {{bootparm|CONFIG_IWLWIFI_LEDS|y}} these two options. For Ubuntu/Debian users, build-essential, linux-source-2.6.24 and linux-headers-generic packages are required.

{{HELP|I added the above lines to the config.mk file and it would not make or make install correctly. I received an error 2 at the end of the make. If you have had success, where did you put the items in the config.mk file for it to make and make install correctly? Thanks in advance.}}

==== To enable the Wifi LED with the Atheros cards ====

First check if this solution works on your computer. Open a terminal and run this commands:

sysctl dev.wifi0.ledpin=1
sysctl dev.wifi0.softled=3

Now connect to a wireless network and the LED should start working. If so and you want to make the changes permanent then:

1) Create a file ~/wifiLED and copy/paste the following into it:

#!/bin/bash
#
# Commands to enable the wireless LED
sysctl dev.wifi0.ledpin=1
sysctl dev.wifi0.softled=3

2) sudo cp ~/wifiLED /etc/init.d

3) sudo chmod 755 /etc/init.d/wifiLED

4) sudo update-rc.d wifiLED defaults 90

After you reboot your wireless led should be working.

=== Hidden SSID ===
It has been reported that users wanting to access Hidden SSIDs have to enter the SSID and password manually in Network Manager to connect. Even after the SSID is saved in Network Manager, it will not reconnect automatically. The user has to connect manually by entering the information as previously described.
It appears that updating the driver by following the instructions [http://linuxwireless.org/en/users/Download here] resolves this issue.

=== Hard Disk Parking ===
Getting hard disk parking to work:

tp_smapi patch is not needed in [http://packages.ubuntu.com/search?keywords=linux-image-2.6.24-18&searchon=names&suite=hardy&section=all linux-image-2.6.24-18]

1. Patch your kernel with the 'protect' [http://www.thinkwiki.org/wiki/HDAPS#Kernel_patch patch].

2. Installing the hdapsd daemon which does the actual parking.

{{cmduser|sudo apt-get install hdapsd hdaps-utils}}

== some other tweaks ==

=== screenblank with {{key|Fn}} + {{key|F3}} ===

Its ok, and might be usefull to get the estimated batterytime when pressing {{key|Fn}}+{{key|F3}}, as it should be. But i dont need that, i find the earlier command for {{key|F3}}, to blank the screen, more useful to save batterylife better.

For that, you must edit {{path|/etc/acpi/thinkpad-lockbattery.sh}} and replace LENOVO by IBM, and IBM by LENOVO :). Do not forget to copy the file before you change it!

=== Enable normal User to Limit CPU Speed ===
To let user set the CPU limit you need to open a Terminal an type there
sudo dpkg-reconfigure gnome-applets
answer the question with yes

=== Fix bluish WSXGA+ displays ===
Many T61 owners complain about a very bluish color temperature: My T61 WSXGA+ was also way too blue. I came across a thread at the notebook review forum http://forum.notebookreview.com/showthread.php?t=174408 which provided two useful ICC profiles which fixed the situation for me. Just install xcalib
sudo apt-get install xcalib
and load one of these profiles.

[[Category: Ubuntu 8.04]]

Installing Ubuntu 8.04 (Hardy Heron) on a ThinkPad T61

2008-07-24T14:17:48Z

Lunatico: /* Wireless activity LED */

== Items that work out of the box ==

'''Intel Video:''' 2D and 3D acceleration works

'''Nvidia Video:''' 2D and 3D acceleration works

'''Wireless:''' Intel cards tested. Atheros cards also works.

'''Wireless WAN:''' Cingular/AT&T card tested.

'''Network Card''' Intel 10/100/1000 tested

'''Wireless switch''' Tested

'''Webcam''' Tested with cheese and skype.

'''Headphones''' Works out of the box

'''Microphone''' Just needs to be activated, see section [[#Audio|below]]

'''Keyboard Shortcuts:''' Most of them work out of the box, some need to be activated, see section [[#Multimedia_Keys|below]]

== Items that need (some) tweaking to obtain full functionality ==

=== Open Source Intel Wifi Driver ===
The following information is important if you are upgrading from a previous version of Ubuntu to 8.04.

Intel has created a new Linux Wifi driver project for Intel Wireless cards, "[[Iwlwifi]]". This driver is Open Source and no longer requires the Intel daemon to run in addition. This project will support the [[:Category:T61 | T61]]'s Wifi [[Intel PRO/Wireless 3945ABG Mini-PCI Express Adapter | Intel 3945ABG network adapter]] and [[Intel PRO/Wireless 4965AGN Mini-PCI Express Adapter| Intel 4965AGN network adapter]].

An automatic migration will occur when upgrading from [[Installing Ubuntu 7.10 (Gutsy Gibbon) on a ThinkPad T61|Ubuntu 7.10]] to Ubuntu 8.04. However, there is a caveat to be aware of:
* The new driver wants to name the interface wlan0 (by default -- you can rename it to anything you want), and requires a different entry in {{path|/etc/udev/rules.d/70-persistent-net.rules}}, which handles the naming of interfaces. Simply edit this file and delete your old entry for the ipw3945 driver, then unload/reload the new driver, or simply reboot. A new entry will automatically be created that is appropriate for the new driver. Here's an example of the lines to delete:
<pre>
# PCI device 0x8086:0x4227 (ipw3945)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:1b:77:a4:0e:2f", NAME="eth1"
</pre>

If you need to perform a manual migration, the Ubuntu Help Community has written some [https://help.ubuntu.com/community/WifiDocs/Driver/iwlwifi_Intel_3945_4965/gutsy documentation] that will make this very easy to do.

=== Compiz and XV Playback on Intel GM965/GL960 ===

With Ubuntu 7.10 (Gutsy Gibbon) you currently have to choose between using Compiz and working video playback using XV. On 8.04 (Hardy Heron) alpha 5 you can play videos using XV under compiz, it works right out of the box using the Live-CD.

=== Suspend with Nv140m ===

** Update as of July 17th 2008 -- Using 8.04.1 with the newest nvidea drivers, I had no problems suspending without any additional configuration. **

Suspend may not work even after editing acpi-support. Enable bluetooth (Fn+F5) may result in a successful suspend. NOTE: that although the wifi led does not change when Fn+F5 is used, the wifi is still toggled by this key.

'''Hal "S3 BIOS" parameter issue!'''

After doing the changes to the /etc/default/acpi-support file (described [http://www.thinkwiki.org/wiki/Installing_Ubuntu_7.10_(Gutsy_Gibbon)_on_a_ThinkPad_T61#How_to_Suspend_with_nVidia_140m.2F570m here]), I for one, managed to have '''stable''' suspend support by creating a new file called: '''/etc/hal/fdi/information/lenovo.fdi''' with the following contents:
<pre>
<?xml version="1.0" encoding="ISO-8859-1"?> 
<deviceinfo version="0.2">
<device>
<match key="system.hardware.vendor" string="LENOVO">
<merge key="power_management.quirk.s3_bios" type="bool">false</merge>
</match>
</device>
</deviceinfo>
</pre>
{{NOTE|The problem (after reading the HAL and pm-utils documentations) is the fact that (as far as I can tell) the T61 Lenovo doesn't allow the S3 BIOS to be called *during* suspend/resume, which HAL seems to do by default (who knows, maybe there are T61s out there that do work with this default)!

This did not seem to be necessary for previous versions of Ubuntu. Also note that I have an NVIDIA card so I have no idea what to do for Intel versions.The change should also be resistant to HAL and pm-utils upgrades.}}

'''Still no suspend with nvs140m? Got Modell 6460?'''

Fix above didn't work for me on a 15.4 wide T61 Modell 6460 with nv140m. Bios is updated to 2.14 but didn't change anything, except the usb bug is fix. Suspend seems to work fine, but resume gives me a black screen (backlight off - no reaction to brightness up) and I can hear 2 beeps. Most of the time I can reboot with ctrl+alt+delete but the screen stays dark until bios.

follow the instructions above but create the new file called: '''/etc/hal/fdi/information/lenovo.fdi''' with the following contents instead:
<pre>
<?xml version="1.0" encoding="ISO-8859-1"?> 
<deviceinfo version="0.2">
<device>
<match key="system.hardware.vendor" string="LENOVO">
<merge key="power_management.quirk.s3_mode" type="bool">true</merge>
<merge key="power_management.quirk.s3_bios" type="bool">false</merge>
<merge key="power_management.quirk.save_pci" type="bool">true</merge>
</match>
</device>
</deviceinfo>
</pre>

Also you want to set the following parameter in

{{path|/etc/default/acpi-support}}
<pre>
SAVE_VIDEO_PCI_STATE=true
</pre>

{{NOTE|This works for me with mode 6460, except for one problem: You may get a white screen in xorg after resume when using compiz. If you don't have a 6460 with nvidia this file may break things for you because it doesn't care about the modell and sets the parameter for any lenovo product}}
{{HELP|Anyone with more knowledge of hal and acpi-support is welcome to clean this up. I also don't know why this setting can be done via hal and in acpi-support.
See below!}}

'''Working on hardy final'''

After trying out all these recipes on my 6457CTO waking up from suspend still did not work. Finally I came across a blog entry which pointed out the right way: [[http://david.goodlad.ca/2008/3/14/suspend-hibernate-on-lenovo-t61 David Goodlad's blog]]. I realized that all the fixes proposing editing the acpi-support file or adding a kernel parameter acpi_sleep=s3_mode must be wrong because since hardy gnome-power-manager gets its information solely from hal. So setting up correct hal information is the right way but the proposed solution (creating a /etc/hal/fdi/information/lenovo.fdi file) did not work for me. Ok, but now step by step:

# Revert ALL the proposed fixes from above. I found out that at least the lenovo.fdi solution is actually breaking the real fix. So for sure delete /etc/hal/fdi/information/lenovo.fdi
# Find out about the excact hal name of your machine: <pre>hal-device |grep 6457</pre> where 6457 is the model number of my t61, replace it with your own. In my case it spits out something like this: system.hardware.product = '6457CTO'. So now I know that hal identifies my machine as 6457CTO.
# <pre>sudo gedit /usr/share/hal/fdi/information/10freedesktop/20-video-quirk-pm-lenovo.fdi</pre> and add a section to the end of the file, just above the </device> tag and replace 6457CTO with your hal device name:
<pre>

<match key="system.hardware.product" string="6457CTO">

<merge key="power_management.quirk.s3_mode" type="bool">true</merge>
<merge key="power_management.quirk.s3_bios" type="bool">false</merge>
<merge key="power_management.quirk.save_pci" type="bool">true</merge>
</match>
</pre>

Now save and reboot. Now you might run into the problem of coming back from resume into a completely white screen where normally should be the password dialog. Entering your password blindly is not nice but at least you can resume.

{{NOTE|Somehow I couldn't make the wildcard matching work as they did in the lenovo.fdi solution, but that might be due to my shortcomings on that syntax. Anyway matching the device by its full name worked for me. Probably somebody who knows more about the matching could make that wildcard thing work to have a more general solution. Because hal also knows the xorg driver name (info.linux.driver) there should be a way to set up the quirks depending on the driver.}}

[[Category: T61]]

=== TrackPoint ===
The [[TrackPoint]] works out of the box, but does not scroll nor does the tap-clicking (press to select) feature work. Therefor see: [[#tap-to-click feature]] To enable using the middle mouse button to scroll, replace the "Configured Mouse" section in {{path|/etc/X11/xorg.conf}} with the following:
<pre>
Section "InputDevice"
Identifier "Trackpoint"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ImPS/2"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "true"
Option "EmulateWheel" "true"
Option "EmulateWheelButton" "2"
EndSection
</pre>

{{NOTE|However, if you need to use external usb mouse, the above configuration is wrong. It will cause odd behavior. Try the following configuration from [http://gentoo-wiki.com/HARDWARE_IBM_Specific_Laptop_Guide#TrackPoint Gentoo Wiki]:}}
<pre>
Section "InputDevice"
Identifier "UltraNav TrackPoint"
Driver "mouse"
Option "Device" "/dev/input/mouse1"
Option "Protocol" "ExplorerPS/2"
Option "Emulate3Buttons" "on"
Option "Emulate3TimeOut" "50"
Option "EmulateWheel" "on"
Option "EmulateWheelTimeOut" "200"
Option "EmulateWheelButton" "2"
Option "YAxisMapping" "4 5"
Option "XAxisMapping" "6 7"
Option "ZAxisMapping" "4 5"
EndSection
</pre>

=== Audio ===

Works great out of the box, just the microphone has to be activated, it is considered a generic capture source and is muted by default.

To unmute the microphone:

*Right Click on the volume icon next to the clock and click on "Open Volume Control"

*Click Edit -> Preferences. A list of devices will be displayed, you should check the following (Do not uncheck any existing items):

Input Source
Capture

*Click Close and there should be two additional tabs "Recording" and "Options". -

*Click Recording and click on the microphone under the Capture slider so that it no longer has a red line through it, and put the slider up as it may be deactivated.

*Click Options and under capture source select internal mic.

To test your mic using Sound Recorder select Capture as the sound source.

This solution has been tested with Sound Recorder and Skype.

To get the volume controls working:

*add the following line to /etc/modprobe.d/alsa-base, then reboot

options snd-hda-intel index=0 model=thinkpad

{{NOTE|The volume controls worked fine for me out of the box on a 6460.}}

=== Multimedia Keys ===

Most Multimedia Keys work out of the box, just the play, forward and stop buttons need to be adjusted, therefore, press alt + F2 and type in gnome-keybinding-properties. Then everything works as followed:

* Fn-PgUp activates/deactivates the thinklight
* Fn-Up will trigger stop on a media player
* Fn-Down will toggle pause and play on a media player
* Fn-Left/Right go to prev/next tracks on a media player
* Fn-F2 properly locks the screen
* Fn-F3 shows remaining battery >>does not work on all machines<<
* Fn-F4 suspends (to ram)
* Fn-F9 ejects cds >>does not work on all machines, I think this is supposed to eject from a "dock"<<
* Fn-F12 hibernates (to disk)
* PrtSc opens the screenshot dialog

To enable the back, forward, and the menu keys you'll need to teach XKB what they are.

* Check the '''XkbLayout''' option (under '''InputDevice''') in your {{path|/etc/X11/xorg.conf}} file to determine which keyboard layout Ubuntu is using (I'll use 'us' for the example).
* Navigate to {{path|/etc/X11/xkb/symbols}} and, as root, open the appropriate layout file (as determined above) in your favorite editor.
{{cmduser|cd /etc/X11/xkb/symbols}}
{{cmduser|sudo gedit us}}
* In the '''xkb_symbols "basic"''' section after the '''name[Group1]= "x";''' (where x is a country name, or similar) line add the following:
key <I63> { [ Menu ] };
key <I69> { [ XF86Forward ] };
key <I6A> { [ XF86Back ] };
* Now log out and back in and all three of the buttons should function.

=== Thinkpad Button ===

Paste the following into /usr/share/hotkey-setup/ibm.hk
setkeycodes e017 148 # thinkpad button
You can also just type this into a terminal, to test it for the time of the current session.

Paste the following into the right file in /usr/share/xmodmap (check your country code)
keycode 159 = XF86Terminal
For immediate availability of the button, reload the file by executing
xmodmap <xmodmap.file>

Then use the "Keyboard Shortcuts" tool under "Preferences".

== Items that don't work (a.k.a.: items that need more intense tweaking to get fixed)==

=== tap-to-click feature ===

For the tap-to-click feature (taping the stick instead of using the left mouse button) i used a configure trackpoint utility: [http://tpctl.sourceforge.net/configure-trackpoint.html] there is a package for ubuntu 7.04 i386, but i compiled it by myself (using amd64):

1.) download the .tar.gz file

2.) unpack it

3.) install libgnomeui-dev

{{cmduser|sudo aptitude install libgnomeui-dev}}

4.) in the folder, do:

{{cmduser|./configure}}

if everything worked fine:

{{cmduser|make}}

then install it:

{{cmduser|sudo make install}}

5.a) Gnome : Open it: System > configure trackpoint, and configure on your needs

5.b) Kde : K-menu > Prefences > configure trackpoint > right-click > edit entry, edit "command" to "kdesu configure-trackpoint"

Save & exit

Open it : K-menu > Prefences > configure trackpoint and configure on your needs

=== Hotswapping ===

{{HELP|We need someone who is able to get hotswaping to work properly, this is not the right was to do this!}}
With the new kernel, bay-drivers changed, so if you remove the ultrabay it will freeze your system! You can hack it with a simple comand, first you have to look where the device is:

{{cmduser|less /sys/class/scsi_device/(x)\:0\:0\:0/device/model}}

for (x) first put in 0, if it tells you DVD or the name of the model you want to hotswap youre right. if not, go on with 1, 2 or 3...

then, once you are sure (I deactivated my harddisk like that) you put in:

{{cmduser|echo 1 {{!}} sudo tee /sys/class/scsi_device/(x)\:0\:0\:0/device/delete}}

Now you should be able to remove the device.

{{WARN|Do not use it for harddisks, be sure you unmounted it before! This is just a bad hack, if anyone knows how to get it right --> publish!}}

If Ubuntu does not reactivate the device after putting it in again, do:

{{cmduser|echo 0 0 0 {{!}} sudo tee /sys/class/scsi_host/host1/scan}}

=== Wireless activity LED ===

The LED is not implemented at least in the IWL4965 driver. For the Atheros wifi cards look at the solution below.

A patch posted in this [http://bughost.org/bugzilla/show_bug.cgi?id=1209 thread] works for me on R61 with IWL4965 card.

{{HELP|A howto is needed showing the process of implementing the patch in Hardy Heron. If anyone knows how to do this, please create a quick howto and either put it here or link to it from this page. Please and thank you.}}

As an alternative, you can install a backported IWL4965 driver that ''may'' fix the LED problem on your system.

To active WiFi LED,

sudo apt-get install linux-backports-modules-hardy

{{NOTE|On some machines, (at least one running IWL3945 & IWL4965) applying the above turns on the LED permanently. It should flicker as data is being transmitted. Also, with the above modification, after turning off wireless and then turning it back on (via the switch on the front of the machine) wireless is not reactivated, so not very helpful}}

You can download a compatible [http://wireless.kernel.org/download/compat-wireless-2.6/compat-wireless-2.6.tar.bz2 driver] which supports WiFi led flicking and build it with modifying the {{path|config.mk}} by adding {{bootparm|CONFIG_IWL3945_LEDS|y}} and {{bootparm|CONFIG_IWLWIFI_LEDS|y}} these two options. For Ubuntu/Debian users, build-essential, linux-source-2.6.24 and linux-headers-generic packages are required.

{{HELP|I added the above lines to the config.mk file and it would not make or make install correctly. I received an error 2 at the end of the make. If you have had success, where did you put the items in the config.mk file for it to make and make install correctly? Thanks in advance.}}

==== To enable the Wifi LED with the Atheros cards ====

First check if this solution works on your computer. Open a terminal and run this commands:

sysctl dev.wifi0.ledpin=1
sysctl dev.wifi0.softled=3

Now connect to a wireless network and the LED should start working. If so and you want to make the changes permanent then:

1) Create a file ~/wifiLED and copy/paste the following into it:

#!/bin/bash
#
# Commands to enable the wireless LED
sysctl dev.wifi0.ledpin=1
sysctl dev.wifi0.softled=3

2) sudo cp ~/wifiLED /etc/init.d

3) sudo chmod 755 /etc/init.d/wifiLED

4) sudo update-rc.d wifiLED defaults 90

After you reboot your wireless led should be working.

=== Hidden SSID ===
It has been reported that users wanting to access Hidden SSIDs have to enter the SSID and password manually in Network Manager to connect. Even after the SSID is saved in Network Manager, it will not reconnect automatically. The user has to connect manually by entering the information as previously described.
It appears that updating the driver by following the instructions [http://linuxwireless.org/en/users/Download here] resolves this issue.

=== Hard Disk Parking ===
Getting hard disk parking to work:

tp_smapi patch is not needed in [http://packages.ubuntu.com/search?keywords=linux-image-2.6.24-18&searchon=names&suite=hardy&section=all linux-image-2.6.24-18]

1. Patch your kernel with the 'protect' [http://www.thinkwiki.org/wiki/HDAPS#Kernel_patch patch].

2. Installing the hdapsd daemon which does the actual parking.

{{cmduser|sudo apt-get install hdapsd hdaps-utils}}

== some other tweaks ==

=== screenblank with {{key|Fn}} + {{key|F3}} ===

Its ok, and might be usefull to get the estimated batterytime when pressing {{key|Fn}}+{{key|F3}}, as it should be. But i dont need that, i find the earlier command for {{key|F3}}, to blank the screen, more useful to save batterylife better.

For that, you must edit {{path|/etc/acpi/thinkpad-lockbattery.sh}} and replace LENOVO by IBM, and IBM by LENOVO :). Do not forget to copy the file before you change it!

=== Enable normal User to Limit CPU Speed ===
To let user set the CPU limit you need to open a Terminal an type there
sudo dpkg-reconfigure gnome-applets
answer the question with yes

=== Fix bluish WSXGA+ displays ===
Many T61 owners complain about a very bluish color temperature: My T61 WSXGA+ was also way too blue. I came across a thread at the notebook review forum http://forum.notebookreview.com/showthread.php?t=174408 which provided two useful ICC profiles which fixed the situation for me. Just install xcalib
sudo apt-get install xcalib
and load one of these profiles.

[[Category: Ubuntu 8.04]]

Installing Ubuntu 8.04 (Hardy Heron) on a ThinkPad T61

2008-07-24T14:15:07Z

Lunatico: /* Wireless activity LED */

== Items that work out of the box ==

'''Intel Video:''' 2D and 3D acceleration works

'''Nvidia Video:''' 2D and 3D acceleration works

'''Wireless:''' Intel cards tested. Atheros cards also works.

'''Wireless WAN:''' Cingular/AT&T card tested.

'''Network Card''' Intel 10/100/1000 tested

'''Wireless switch''' Tested

'''Webcam''' Tested with cheese and skype.

'''Headphones''' Works out of the box

'''Microphone''' Just needs to be activated, see section [[#Audio|below]]

'''Keyboard Shortcuts:''' Most of them work out of the box, some need to be activated, see section [[#Multimedia_Keys|below]]

== Items that need (some) tweaking to obtain full functionality ==

=== Open Source Intel Wifi Driver ===
The following information is important if you are upgrading from a previous version of Ubuntu to 8.04.

Intel has created a new Linux Wifi driver project for Intel Wireless cards, "[[Iwlwifi]]". This driver is Open Source and no longer requires the Intel daemon to run in addition. This project will support the [[:Category:T61 | T61]]'s Wifi [[Intel PRO/Wireless 3945ABG Mini-PCI Express Adapter | Intel 3945ABG network adapter]] and [[Intel PRO/Wireless 4965AGN Mini-PCI Express Adapter| Intel 4965AGN network adapter]].

An automatic migration will occur when upgrading from [[Installing Ubuntu 7.10 (Gutsy Gibbon) on a ThinkPad T61|Ubuntu 7.10]] to Ubuntu 8.04. However, there is a caveat to be aware of:
* The new driver wants to name the interface wlan0 (by default -- you can rename it to anything you want), and requires a different entry in {{path|/etc/udev/rules.d/70-persistent-net.rules}}, which handles the naming of interfaces. Simply edit this file and delete your old entry for the ipw3945 driver, then unload/reload the new driver, or simply reboot. A new entry will automatically be created that is appropriate for the new driver. Here's an example of the lines to delete:
<pre>
# PCI device 0x8086:0x4227 (ipw3945)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:1b:77:a4:0e:2f", NAME="eth1"
</pre>

If you need to perform a manual migration, the Ubuntu Help Community has written some [https://help.ubuntu.com/community/WifiDocs/Driver/iwlwifi_Intel_3945_4965/gutsy documentation] that will make this very easy to do.

=== Compiz and XV Playback on Intel GM965/GL960 ===

With Ubuntu 7.10 (Gutsy Gibbon) you currently have to choose between using Compiz and working video playback using XV. On 8.04 (Hardy Heron) alpha 5 you can play videos using XV under compiz, it works right out of the box using the Live-CD.

=== Suspend with Nv140m ===

** Update as of July 17th 2008 -- Using 8.04.1 with the newest nvidea drivers, I had no problems suspending without any additional configuration. **

Suspend may not work even after editing acpi-support. Enable bluetooth (Fn+F5) may result in a successful suspend. NOTE: that although the wifi led does not change when Fn+F5 is used, the wifi is still toggled by this key.

'''Hal "S3 BIOS" parameter issue!'''

After doing the changes to the /etc/default/acpi-support file (described [http://www.thinkwiki.org/wiki/Installing_Ubuntu_7.10_(Gutsy_Gibbon)_on_a_ThinkPad_T61#How_to_Suspend_with_nVidia_140m.2F570m here]), I for one, managed to have '''stable''' suspend support by creating a new file called: '''/etc/hal/fdi/information/lenovo.fdi''' with the following contents:
<pre>
<?xml version="1.0" encoding="ISO-8859-1"?> 
<deviceinfo version="0.2">
<device>
<match key="system.hardware.vendor" string="LENOVO">
<merge key="power_management.quirk.s3_bios" type="bool">false</merge>
</match>
</device>
</deviceinfo>
</pre>
{{NOTE|The problem (after reading the HAL and pm-utils documentations) is the fact that (as far as I can tell) the T61 Lenovo doesn't allow the S3 BIOS to be called *during* suspend/resume, which HAL seems to do by default (who knows, maybe there are T61s out there that do work with this default)!

This did not seem to be necessary for previous versions of Ubuntu. Also note that I have an NVIDIA card so I have no idea what to do for Intel versions.The change should also be resistant to HAL and pm-utils upgrades.}}

'''Still no suspend with nvs140m? Got Modell 6460?'''

Fix above didn't work for me on a 15.4 wide T61 Modell 6460 with nv140m. Bios is updated to 2.14 but didn't change anything, except the usb bug is fix. Suspend seems to work fine, but resume gives me a black screen (backlight off - no reaction to brightness up) and I can hear 2 beeps. Most of the time I can reboot with ctrl+alt+delete but the screen stays dark until bios.

follow the instructions above but create the new file called: '''/etc/hal/fdi/information/lenovo.fdi''' with the following contents instead:
<pre>
<?xml version="1.0" encoding="ISO-8859-1"?> 
<deviceinfo version="0.2">
<device>
<match key="system.hardware.vendor" string="LENOVO">
<merge key="power_management.quirk.s3_mode" type="bool">true</merge>
<merge key="power_management.quirk.s3_bios" type="bool">false</merge>
<merge key="power_management.quirk.save_pci" type="bool">true</merge>
</match>
</device>
</deviceinfo>
</pre>

Also you want to set the following parameter in

{{path|/etc/default/acpi-support}}
<pre>
SAVE_VIDEO_PCI_STATE=true
</pre>

{{NOTE|This works for me with mode 6460, except for one problem: You may get a white screen in xorg after resume when using compiz. If you don't have a 6460 with nvidia this file may break things for you because it doesn't care about the modell and sets the parameter for any lenovo product}}
{{HELP|Anyone with more knowledge of hal and acpi-support is welcome to clean this up. I also don't know why this setting can be done via hal and in acpi-support.
See below!}}

'''Working on hardy final'''

After trying out all these recipes on my 6457CTO waking up from suspend still did not work. Finally I came across a blog entry which pointed out the right way: [[http://david.goodlad.ca/2008/3/14/suspend-hibernate-on-lenovo-t61 David Goodlad's blog]]. I realized that all the fixes proposing editing the acpi-support file or adding a kernel parameter acpi_sleep=s3_mode must be wrong because since hardy gnome-power-manager gets its information solely from hal. So setting up correct hal information is the right way but the proposed solution (creating a /etc/hal/fdi/information/lenovo.fdi file) did not work for me. Ok, but now step by step:

# Revert ALL the proposed fixes from above. I found out that at least the lenovo.fdi solution is actually breaking the real fix. So for sure delete /etc/hal/fdi/information/lenovo.fdi
# Find out about the excact hal name of your machine: <pre>hal-device |grep 6457</pre> where 6457 is the model number of my t61, replace it with your own. In my case it spits out something like this: system.hardware.product = '6457CTO'. So now I know that hal identifies my machine as 6457CTO.
# <pre>sudo gedit /usr/share/hal/fdi/information/10freedesktop/20-video-quirk-pm-lenovo.fdi</pre> and add a section to the end of the file, just above the </device> tag and replace 6457CTO with your hal device name:
<pre>

<match key="system.hardware.product" string="6457CTO">

<merge key="power_management.quirk.s3_mode" type="bool">true</merge>
<merge key="power_management.quirk.s3_bios" type="bool">false</merge>
<merge key="power_management.quirk.save_pci" type="bool">true</merge>
</match>
</pre>

Now save and reboot. Now you might run into the problem of coming back from resume into a completely white screen where normally should be the password dialog. Entering your password blindly is not nice but at least you can resume.

{{NOTE|Somehow I couldn't make the wildcard matching work as they did in the lenovo.fdi solution, but that might be due to my shortcomings on that syntax. Anyway matching the device by its full name worked for me. Probably somebody who knows more about the matching could make that wildcard thing work to have a more general solution. Because hal also knows the xorg driver name (info.linux.driver) there should be a way to set up the quirks depending on the driver.}}

[[Category: T61]]

=== TrackPoint ===
The [[TrackPoint]] works out of the box, but does not scroll nor does the tap-clicking (press to select) feature work. Therefor see: [[#tap-to-click feature]] To enable using the middle mouse button to scroll, replace the "Configured Mouse" section in {{path|/etc/X11/xorg.conf}} with the following:
<pre>
Section "InputDevice"
Identifier "Trackpoint"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ImPS/2"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "true"
Option "EmulateWheel" "true"
Option "EmulateWheelButton" "2"
EndSection
</pre>

{{NOTE|However, if you need to use external usb mouse, the above configuration is wrong. It will cause odd behavior. Try the following configuration from [http://gentoo-wiki.com/HARDWARE_IBM_Specific_Laptop_Guide#TrackPoint Gentoo Wiki]:}}
<pre>
Section "InputDevice"
Identifier "UltraNav TrackPoint"
Driver "mouse"
Option "Device" "/dev/input/mouse1"
Option "Protocol" "ExplorerPS/2"
Option "Emulate3Buttons" "on"
Option "Emulate3TimeOut" "50"
Option "EmulateWheel" "on"
Option "EmulateWheelTimeOut" "200"
Option "EmulateWheelButton" "2"
Option "YAxisMapping" "4 5"
Option "XAxisMapping" "6 7"
Option "ZAxisMapping" "4 5"
EndSection
</pre>

=== Audio ===

Works great out of the box, just the microphone has to be activated, it is considered a generic capture source and is muted by default.

To unmute the microphone:

*Right Click on the volume icon next to the clock and click on "Open Volume Control"

*Click Edit -> Preferences. A list of devices will be displayed, you should check the following (Do not uncheck any existing items):

Input Source
Capture

*Click Close and there should be two additional tabs "Recording" and "Options". -

*Click Recording and click on the microphone under the Capture slider so that it no longer has a red line through it, and put the slider up as it may be deactivated.

*Click Options and under capture source select internal mic.

To test your mic using Sound Recorder select Capture as the sound source.

This solution has been tested with Sound Recorder and Skype.

To get the volume controls working:

*add the following line to /etc/modprobe.d/alsa-base, then reboot

options snd-hda-intel index=0 model=thinkpad

{{NOTE|The volume controls worked fine for me out of the box on a 6460.}}

=== Multimedia Keys ===

Most Multimedia Keys work out of the box, just the play, forward and stop buttons need to be adjusted, therefore, press alt + F2 and type in gnome-keybinding-properties. Then everything works as followed:

* Fn-PgUp activates/deactivates the thinklight
* Fn-Up will trigger stop on a media player
* Fn-Down will toggle pause and play on a media player
* Fn-Left/Right go to prev/next tracks on a media player
* Fn-F2 properly locks the screen
* Fn-F3 shows remaining battery >>does not work on all machines<<
* Fn-F4 suspends (to ram)
* Fn-F9 ejects cds >>does not work on all machines, I think this is supposed to eject from a "dock"<<
* Fn-F12 hibernates (to disk)
* PrtSc opens the screenshot dialog

To enable the back, forward, and the menu keys you'll need to teach XKB what they are.

* Check the '''XkbLayout''' option (under '''InputDevice''') in your {{path|/etc/X11/xorg.conf}} file to determine which keyboard layout Ubuntu is using (I'll use 'us' for the example).
* Navigate to {{path|/etc/X11/xkb/symbols}} and, as root, open the appropriate layout file (as determined above) in your favorite editor.
{{cmduser|cd /etc/X11/xkb/symbols}}
{{cmduser|sudo gedit us}}
* In the '''xkb_symbols "basic"''' section after the '''name[Group1]= "x";''' (where x is a country name, or similar) line add the following:
key <I63> { [ Menu ] };
key <I69> { [ XF86Forward ] };
key <I6A> { [ XF86Back ] };
* Now log out and back in and all three of the buttons should function.

=== Thinkpad Button ===

Paste the following into /usr/share/hotkey-setup/ibm.hk
setkeycodes e017 148 # thinkpad button
You can also just type this into a terminal, to test it for the time of the current session.

Paste the following into the right file in /usr/share/xmodmap (check your country code)
keycode 159 = XF86Terminal
For immediate availability of the button, reload the file by executing
xmodmap <xmodmap.file>

Then use the "Keyboard Shortcuts" tool under "Preferences".

== Items that don't work (a.k.a.: items that need more intense tweaking to get fixed)==

=== tap-to-click feature ===

For the tap-to-click feature (taping the stick instead of using the left mouse button) i used a configure trackpoint utility: [http://tpctl.sourceforge.net/configure-trackpoint.html] there is a package for ubuntu 7.04 i386, but i compiled it by myself (using amd64):

1.) download the .tar.gz file

2.) unpack it

3.) install libgnomeui-dev

{{cmduser|sudo aptitude install libgnomeui-dev}}

4.) in the folder, do:

{{cmduser|./configure}}

if everything worked fine:

{{cmduser|make}}

then install it:

{{cmduser|sudo make install}}

5.a) Gnome : Open it: System > configure trackpoint, and configure on your needs

5.b) Kde : K-menu > Prefences > configure trackpoint > right-click > edit entry, edit "command" to "kdesu configure-trackpoint"

Save & exit

Open it : K-menu > Prefences > configure trackpoint and configure on your needs

=== Hotswapping ===

{{HELP|We need someone who is able to get hotswaping to work properly, this is not the right was to do this!}}
With the new kernel, bay-drivers changed, so if you remove the ultrabay it will freeze your system! You can hack it with a simple comand, first you have to look where the device is:

{{cmduser|less /sys/class/scsi_device/(x)\:0\:0\:0/device/model}}

for (x) first put in 0, if it tells you DVD or the name of the model you want to hotswap youre right. if not, go on with 1, 2 or 3...

then, once you are sure (I deactivated my harddisk like that) you put in:

{{cmduser|echo 1 {{!}} sudo tee /sys/class/scsi_device/(x)\:0\:0\:0/device/delete}}

Now you should be able to remove the device.

{{WARN|Do not use it for harddisks, be sure you unmounted it before! This is just a bad hack, if anyone knows how to get it right --> publish!}}

If Ubuntu does not reactivate the device after putting it in again, do:

{{cmduser|echo 0 0 0 {{!}} sudo tee /sys/class/scsi_host/host1/scan}}

=== Wireless activity LED ===

The LED is not implemented at least in the IWL4965 driver. For the Atheros wifi cards look at the solution [[below]].

A patch posted in this [http://bughost.org/bugzilla/show_bug.cgi?id=1209 thread] works for me on R61 with IWL4965 card.

{{HELP|A howto is needed showing the process of implementing the patch in Hardy Heron. If anyone knows how to do this, please create a quick howto and either put it here or link to it from this page. Please and thank you.}}

As an alternative, you can install a backported IWL4965 driver that ''may'' fix the LED problem on your system.

To active WiFi LED,

sudo apt-get install linux-backports-modules-hardy

{{NOTE|On some machines, (at least one running IWL3945 & IWL4965) applying the above turns on the LED permanently. It should flicker as data is being transmitted. Also, with the above modification, after turning off wireless and then turning it back on (via the switch on the front of the machine) wireless is not reactivated, so not very helpful}}

You can download a compatible [http://wireless.kernel.org/download/compat-wireless-2.6/compat-wireless-2.6.tar.bz2 driver] which supports WiFi led flicking and build it with modifying the {{path|config.mk}} by adding {{bootparm|CONFIG_IWL3945_LEDS|y}} and {{bootparm|CONFIG_IWLWIFI_LEDS|y}} these two options. For Ubuntu/Debian users, build-essential, linux-source-2.6.24 and linux-headers-generic packages are required.

{{HELP|I added the above lines to the config.mk file and it would not make or make install correctly. I received an error 2 at the end of the make. If you have had success, where did you put the items in the config.mk file for it to make and make install correctly? Thanks in advance.}}

==== To enable the Wifi LED with the Atheros cards ====

First check if this solution works on your computer. Open a terminal and run this commands:

sysctl dev.wifi0.ledpin=1
sysctl dev.wifi0.softled=3

Now connect to a wireless network and the LED should start working. If so and you want to make the changes permanent then:

1) Create a file ~/wifiLED and copy/paste the following into it:

#!/bin/bash
#
# Commands to enable the wireless LED
sysctl dev.wifi0.ledpin=1
sysctl dev.wifi0.softled=3

2) sudo cp ~/wifiLED /etc/init.d

3) sudo chmod 755 /etc/init.d/wifiLED

4) sudo update-rc.d wifiLED defaults 90

After you reboot your wireless led should be working.

=== Hidden SSID ===
It has been reported that users wanting to access Hidden SSIDs have to enter the SSID and password manually in Network Manager to connect. Even after the SSID is saved in Network Manager, it will not reconnect automatically. The user has to connect manually by entering the information as previously described.
It appears that updating the driver by following the instructions [http://linuxwireless.org/en/users/Download here] resolves this issue.

=== Hard Disk Parking ===
Getting hard disk parking to work:

tp_smapi patch is not needed in [http://packages.ubuntu.com/search?keywords=linux-image-2.6.24-18&searchon=names&suite=hardy&section=all linux-image-2.6.24-18]

1. Patch your kernel with the 'protect' [http://www.thinkwiki.org/wiki/HDAPS#Kernel_patch patch].

2. Installing the hdapsd daemon which does the actual parking.

{{cmduser|sudo apt-get install hdapsd hdaps-utils}}

== some other tweaks ==

=== screenblank with {{key|Fn}} + {{key|F3}} ===

Its ok, and might be usefull to get the estimated batterytime when pressing {{key|Fn}}+{{key|F3}}, as it should be. But i dont need that, i find the earlier command for {{key|F3}}, to blank the screen, more useful to save batterylife better.

For that, you must edit {{path|/etc/acpi/thinkpad-lockbattery.sh}} and replace LENOVO by IBM, and IBM by LENOVO :). Do not forget to copy the file before you change it!

=== Enable normal User to Limit CPU Speed ===
To let user set the CPU limit you need to open a Terminal an type there
sudo dpkg-reconfigure gnome-applets
answer the question with yes

=== Fix bluish WSXGA+ displays ===
Many T61 owners complain about a very bluish color temperature: My T61 WSXGA+ was also way too blue. I came across a thread at the notebook review forum http://forum.notebookreview.com/showthread.php?t=174408 which provided two useful ICC profiles which fixed the situation for me. Just install xcalib
sudo apt-get install xcalib
and load one of these profiles.

[[Category: Ubuntu 8.04]]

Installing Ubuntu 8.04 (Hardy Heron) on a ThinkPad T61

2008-07-24T14:14:45Z

Lunatico: /* Wireless activity LED */

== Items that work out of the box ==

'''Intel Video:''' 2D and 3D acceleration works

'''Nvidia Video:''' 2D and 3D acceleration works

'''Wireless:''' Intel cards tested. Atheros cards also works.

'''Wireless WAN:''' Cingular/AT&T card tested.

'''Network Card''' Intel 10/100/1000 tested

'''Wireless switch''' Tested

'''Webcam''' Tested with cheese and skype.

'''Headphones''' Works out of the box

'''Microphone''' Just needs to be activated, see section [[#Audio|below]]

'''Keyboard Shortcuts:''' Most of them work out of the box, some need to be activated, see section [[#Multimedia_Keys|below]]

== Items that need (some) tweaking to obtain full functionality ==

=== Open Source Intel Wifi Driver ===
The following information is important if you are upgrading from a previous version of Ubuntu to 8.04.

Intel has created a new Linux Wifi driver project for Intel Wireless cards, "[[Iwlwifi]]". This driver is Open Source and no longer requires the Intel daemon to run in addition. This project will support the [[:Category:T61 | T61]]'s Wifi [[Intel PRO/Wireless 3945ABG Mini-PCI Express Adapter | Intel 3945ABG network adapter]] and [[Intel PRO/Wireless 4965AGN Mini-PCI Express Adapter| Intel 4965AGN network adapter]].

An automatic migration will occur when upgrading from [[Installing Ubuntu 7.10 (Gutsy Gibbon) on a ThinkPad T61|Ubuntu 7.10]] to Ubuntu 8.04. However, there is a caveat to be aware of:
* The new driver wants to name the interface wlan0 (by default -- you can rename it to anything you want), and requires a different entry in {{path|/etc/udev/rules.d/70-persistent-net.rules}}, which handles the naming of interfaces. Simply edit this file and delete your old entry for the ipw3945 driver, then unload/reload the new driver, or simply reboot. A new entry will automatically be created that is appropriate for the new driver. Here's an example of the lines to delete:
<pre>
# PCI device 0x8086:0x4227 (ipw3945)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:1b:77:a4:0e:2f", NAME="eth1"
</pre>

If you need to perform a manual migration, the Ubuntu Help Community has written some [https://help.ubuntu.com/community/WifiDocs/Driver/iwlwifi_Intel_3945_4965/gutsy documentation] that will make this very easy to do.

=== Compiz and XV Playback on Intel GM965/GL960 ===

With Ubuntu 7.10 (Gutsy Gibbon) you currently have to choose between using Compiz and working video playback using XV. On 8.04 (Hardy Heron) alpha 5 you can play videos using XV under compiz, it works right out of the box using the Live-CD.

=== Suspend with Nv140m ===

** Update as of July 17th 2008 -- Using 8.04.1 with the newest nvidea drivers, I had no problems suspending without any additional configuration. **

Suspend may not work even after editing acpi-support. Enable bluetooth (Fn+F5) may result in a successful suspend. NOTE: that although the wifi led does not change when Fn+F5 is used, the wifi is still toggled by this key.

'''Hal "S3 BIOS" parameter issue!'''

After doing the changes to the /etc/default/acpi-support file (described [http://www.thinkwiki.org/wiki/Installing_Ubuntu_7.10_(Gutsy_Gibbon)_on_a_ThinkPad_T61#How_to_Suspend_with_nVidia_140m.2F570m here]), I for one, managed to have '''stable''' suspend support by creating a new file called: '''/etc/hal/fdi/information/lenovo.fdi''' with the following contents:
<pre>
<?xml version="1.0" encoding="ISO-8859-1"?> 
<deviceinfo version="0.2">
<device>
<match key="system.hardware.vendor" string="LENOVO">
<merge key="power_management.quirk.s3_bios" type="bool">false</merge>
</match>
</device>
</deviceinfo>
</pre>
{{NOTE|The problem (after reading the HAL and pm-utils documentations) is the fact that (as far as I can tell) the T61 Lenovo doesn't allow the S3 BIOS to be called *during* suspend/resume, which HAL seems to do by default (who knows, maybe there are T61s out there that do work with this default)!

This did not seem to be necessary for previous versions of Ubuntu. Also note that I have an NVIDIA card so I have no idea what to do for Intel versions.The change should also be resistant to HAL and pm-utils upgrades.}}

'''Still no suspend with nvs140m? Got Modell 6460?'''

Fix above didn't work for me on a 15.4 wide T61 Modell 6460 with nv140m. Bios is updated to 2.14 but didn't change anything, except the usb bug is fix. Suspend seems to work fine, but resume gives me a black screen (backlight off - no reaction to brightness up) and I can hear 2 beeps. Most of the time I can reboot with ctrl+alt+delete but the screen stays dark until bios.

follow the instructions above but create the new file called: '''/etc/hal/fdi/information/lenovo.fdi''' with the following contents instead:
<pre>
<?xml version="1.0" encoding="ISO-8859-1"?> 
<deviceinfo version="0.2">
<device>
<match key="system.hardware.vendor" string="LENOVO">
<merge key="power_management.quirk.s3_mode" type="bool">true</merge>
<merge key="power_management.quirk.s3_bios" type="bool">false</merge>
<merge key="power_management.quirk.save_pci" type="bool">true</merge>
</match>
</device>
</deviceinfo>
</pre>

Also you want to set the following parameter in

{{path|/etc/default/acpi-support}}
<pre>
SAVE_VIDEO_PCI_STATE=true
</pre>

{{NOTE|This works for me with mode 6460, except for one problem: You may get a white screen in xorg after resume when using compiz. If you don't have a 6460 with nvidia this file may break things for you because it doesn't care about the modell and sets the parameter for any lenovo product}}
{{HELP|Anyone with more knowledge of hal and acpi-support is welcome to clean this up. I also don't know why this setting can be done via hal and in acpi-support.
See below!}}

'''Working on hardy final'''

After trying out all these recipes on my 6457CTO waking up from suspend still did not work. Finally I came across a blog entry which pointed out the right way: [[http://david.goodlad.ca/2008/3/14/suspend-hibernate-on-lenovo-t61 David Goodlad's blog]]. I realized that all the fixes proposing editing the acpi-support file or adding a kernel parameter acpi_sleep=s3_mode must be wrong because since hardy gnome-power-manager gets its information solely from hal. So setting up correct hal information is the right way but the proposed solution (creating a /etc/hal/fdi/information/lenovo.fdi file) did not work for me. Ok, but now step by step:

# Revert ALL the proposed fixes from above. I found out that at least the lenovo.fdi solution is actually breaking the real fix. So for sure delete /etc/hal/fdi/information/lenovo.fdi
# Find out about the excact hal name of your machine: <pre>hal-device |grep 6457</pre> where 6457 is the model number of my t61, replace it with your own. In my case it spits out something like this: system.hardware.product = '6457CTO'. So now I know that hal identifies my machine as 6457CTO.
# <pre>sudo gedit /usr/share/hal/fdi/information/10freedesktop/20-video-quirk-pm-lenovo.fdi</pre> and add a section to the end of the file, just above the </device> tag and replace 6457CTO with your hal device name:
<pre>

<match key="system.hardware.product" string="6457CTO">

<merge key="power_management.quirk.s3_mode" type="bool">true</merge>
<merge key="power_management.quirk.s3_bios" type="bool">false</merge>
<merge key="power_management.quirk.save_pci" type="bool">true</merge>
</match>
</pre>

Now save and reboot. Now you might run into the problem of coming back from resume into a completely white screen where normally should be the password dialog. Entering your password blindly is not nice but at least you can resume.

{{NOTE|Somehow I couldn't make the wildcard matching work as they did in the lenovo.fdi solution, but that might be due to my shortcomings on that syntax. Anyway matching the device by its full name worked for me. Probably somebody who knows more about the matching could make that wildcard thing work to have a more general solution. Because hal also knows the xorg driver name (info.linux.driver) there should be a way to set up the quirks depending on the driver.}}

[[Category: T61]]

=== TrackPoint ===
The [[TrackPoint]] works out of the box, but does not scroll nor does the tap-clicking (press to select) feature work. Therefor see: [[#tap-to-click feature]] To enable using the middle mouse button to scroll, replace the "Configured Mouse" section in {{path|/etc/X11/xorg.conf}} with the following:
<pre>
Section "InputDevice"
Identifier "Trackpoint"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ImPS/2"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "true"
Option "EmulateWheel" "true"
Option "EmulateWheelButton" "2"
EndSection
</pre>

{{NOTE|However, if you need to use external usb mouse, the above configuration is wrong. It will cause odd behavior. Try the following configuration from [http://gentoo-wiki.com/HARDWARE_IBM_Specific_Laptop_Guide#TrackPoint Gentoo Wiki]:}}
<pre>
Section "InputDevice"
Identifier "UltraNav TrackPoint"
Driver "mouse"
Option "Device" "/dev/input/mouse1"
Option "Protocol" "ExplorerPS/2"
Option "Emulate3Buttons" "on"
Option "Emulate3TimeOut" "50"
Option "EmulateWheel" "on"
Option "EmulateWheelTimeOut" "200"
Option "EmulateWheelButton" "2"
Option "YAxisMapping" "4 5"
Option "XAxisMapping" "6 7"
Option "ZAxisMapping" "4 5"
EndSection
</pre>

=== Audio ===

Works great out of the box, just the microphone has to be activated, it is considered a generic capture source and is muted by default.

To unmute the microphone:

*Right Click on the volume icon next to the clock and click on "Open Volume Control"

*Click Edit -> Preferences. A list of devices will be displayed, you should check the following (Do not uncheck any existing items):

Input Source
Capture

*Click Close and there should be two additional tabs "Recording" and "Options". -

*Click Recording and click on the microphone under the Capture slider so that it no longer has a red line through it, and put the slider up as it may be deactivated.

*Click Options and under capture source select internal mic.

To test your mic using Sound Recorder select Capture as the sound source.

This solution has been tested with Sound Recorder and Skype.

To get the volume controls working:

*add the following line to /etc/modprobe.d/alsa-base, then reboot

options snd-hda-intel index=0 model=thinkpad

{{NOTE|The volume controls worked fine for me out of the box on a 6460.}}

=== Multimedia Keys ===

Most Multimedia Keys work out of the box, just the play, forward and stop buttons need to be adjusted, therefore, press alt + F2 and type in gnome-keybinding-properties. Then everything works as followed:

* Fn-PgUp activates/deactivates the thinklight
* Fn-Up will trigger stop on a media player
* Fn-Down will toggle pause and play on a media player
* Fn-Left/Right go to prev/next tracks on a media player
* Fn-F2 properly locks the screen
* Fn-F3 shows remaining battery >>does not work on all machines<<
* Fn-F4 suspends (to ram)
* Fn-F9 ejects cds >>does not work on all machines, I think this is supposed to eject from a "dock"<<
* Fn-F12 hibernates (to disk)
* PrtSc opens the screenshot dialog

To enable the back, forward, and the menu keys you'll need to teach XKB what they are.

* Check the '''XkbLayout''' option (under '''InputDevice''') in your {{path|/etc/X11/xorg.conf}} file to determine which keyboard layout Ubuntu is using (I'll use 'us' for the example).
* Navigate to {{path|/etc/X11/xkb/symbols}} and, as root, open the appropriate layout file (as determined above) in your favorite editor.
{{cmduser|cd /etc/X11/xkb/symbols}}
{{cmduser|sudo gedit us}}
* In the '''xkb_symbols "basic"''' section after the '''name[Group1]= "x";''' (where x is a country name, or similar) line add the following:
key <I63> { [ Menu ] };
key <I69> { [ XF86Forward ] };
key <I6A> { [ XF86Back ] };
* Now log out and back in and all three of the buttons should function.

=== Thinkpad Button ===

Paste the following into /usr/share/hotkey-setup/ibm.hk
setkeycodes e017 148 # thinkpad button
You can also just type this into a terminal, to test it for the time of the current session.

Paste the following into the right file in /usr/share/xmodmap (check your country code)
keycode 159 = XF86Terminal
For immediate availability of the button, reload the file by executing
xmodmap <xmodmap.file>

Then use the "Keyboard Shortcuts" tool under "Preferences".

== Items that don't work (a.k.a.: items that need more intense tweaking to get fixed)==

=== tap-to-click feature ===

For the tap-to-click feature (taping the stick instead of using the left mouse button) i used a configure trackpoint utility: [http://tpctl.sourceforge.net/configure-trackpoint.html] there is a package for ubuntu 7.04 i386, but i compiled it by myself (using amd64):

1.) download the .tar.gz file

2.) unpack it

3.) install libgnomeui-dev

{{cmduser|sudo aptitude install libgnomeui-dev}}

4.) in the folder, do:

{{cmduser|./configure}}

if everything worked fine:

{{cmduser|make}}

then install it:

{{cmduser|sudo make install}}

5.a) Gnome : Open it: System > configure trackpoint, and configure on your needs

5.b) Kde : K-menu > Prefences > configure trackpoint > right-click > edit entry, edit "command" to "kdesu configure-trackpoint"

Save & exit

Open it : K-menu > Prefences > configure trackpoint and configure on your needs

=== Hotswapping ===

{{HELP|We need someone who is able to get hotswaping to work properly, this is not the right was to do this!}}
With the new kernel, bay-drivers changed, so if you remove the ultrabay it will freeze your system! You can hack it with a simple comand, first you have to look where the device is:

{{cmduser|less /sys/class/scsi_device/(x)\:0\:0\:0/device/model}}

for (x) first put in 0, if it tells you DVD or the name of the model you want to hotswap youre right. if not, go on with 1, 2 or 3...

then, once you are sure (I deactivated my harddisk like that) you put in:

{{cmduser|echo 1 {{!}} sudo tee /sys/class/scsi_device/(x)\:0\:0\:0/device/delete}}

Now you should be able to remove the device.

{{WARN|Do not use it for harddisks, be sure you unmounted it before! This is just a bad hack, if anyone knows how to get it right --> publish!}}

If Ubuntu does not reactivate the device after putting it in again, do:

{{cmduser|echo 0 0 0 {{!}} sudo tee /sys/class/scsi_host/host1/scan}}

=== Wireless activity LED ===

The LED is not implemented at least in the IWL4965 driver. For the Atheros wifi cards look at the solution below.

A patch posted in this [http://bughost.org/bugzilla/show_bug.cgi?id=1209 thread] works for me on R61 with IWL4965 card.

{{HELP|A howto is needed showing the process of implementing the patch in Hardy Heron. If anyone knows how to do this, please create a quick howto and either put it here or link to it from this page. Please and thank you.}}

As an alternative, you can install a backported IWL4965 driver that ''may'' fix the LED problem on your system.

To active WiFi LED,

sudo apt-get install linux-backports-modules-hardy

{{NOTE|On some machines, (at least one running IWL3945 & IWL4965) applying the above turns on the LED permanently. It should flicker as data is being transmitted. Also, with the above modification, after turning off wireless and then turning it back on (via the switch on the front of the machine) wireless is not reactivated, so not very helpful}}

You can download a compatible [http://wireless.kernel.org/download/compat-wireless-2.6/compat-wireless-2.6.tar.bz2 driver] which supports WiFi led flicking and build it with modifying the {{path|config.mk}} by adding {{bootparm|CONFIG_IWL3945_LEDS|y}} and {{bootparm|CONFIG_IWLWIFI_LEDS|y}} these two options. For Ubuntu/Debian users, build-essential, linux-source-2.6.24 and linux-headers-generic packages are required.

{{HELP|I added the above lines to the config.mk file and it would not make or make install correctly. I received an error 2 at the end of the make. If you have had success, where did you put the items in the config.mk file for it to make and make install correctly? Thanks in advance.}}

==== To enable the Wifi LED with the Atheros cards ====

First check if this solution works on your computer. Open a terminal and run this commands:

sysctl dev.wifi0.ledpin=1
sysctl dev.wifi0.softled=3

Now connect to a wireless network and the LED should start working. If so and you want to make the changes permanent then:

1) Create a file ~/wifiLED and copy/paste the following into it:

#!/bin/bash
#
# Commands to enable the wireless LED
sysctl dev.wifi0.ledpin=1
sysctl dev.wifi0.softled=3

2) sudo cp ~/wifiLED /etc/init.d

3) sudo chmod 755 /etc/init.d/wifiLED

4) sudo update-rc.d wifiLED defaults 90

After you reboot your wireless led should be working.

=== Hidden SSID ===
It has been reported that users wanting to access Hidden SSIDs have to enter the SSID and password manually in Network Manager to connect. Even after the SSID is saved in Network Manager, it will not reconnect automatically. The user has to connect manually by entering the information as previously described.
It appears that updating the driver by following the instructions [http://linuxwireless.org/en/users/Download here] resolves this issue.

=== Hard Disk Parking ===
Getting hard disk parking to work:

tp_smapi patch is not needed in [http://packages.ubuntu.com/search?keywords=linux-image-2.6.24-18&searchon=names&suite=hardy&section=all linux-image-2.6.24-18]

1. Patch your kernel with the 'protect' [http://www.thinkwiki.org/wiki/HDAPS#Kernel_patch patch].

2. Installing the hdapsd daemon which does the actual parking.

{{cmduser|sudo apt-get install hdapsd hdaps-utils}}

== some other tweaks ==

=== screenblank with {{key|Fn}} + {{key|F3}} ===

Its ok, and might be usefull to get the estimated batterytime when pressing {{key|Fn}}+{{key|F3}}, as it should be. But i dont need that, i find the earlier command for {{key|F3}}, to blank the screen, more useful to save batterylife better.

For that, you must edit {{path|/etc/acpi/thinkpad-lockbattery.sh}} and replace LENOVO by IBM, and IBM by LENOVO :). Do not forget to copy the file before you change it!

=== Enable normal User to Limit CPU Speed ===
To let user set the CPU limit you need to open a Terminal an type there
sudo dpkg-reconfigure gnome-applets
answer the question with yes

=== Fix bluish WSXGA+ displays ===
Many T61 owners complain about a very bluish color temperature: My T61 WSXGA+ was also way too blue. I came across a thread at the notebook review forum http://forum.notebookreview.com/showthread.php?t=174408 which provided two useful ICC profiles which fixed the situation for me. Just install xcalib
sudo apt-get install xcalib
and load one of these profiles.

[[Category: Ubuntu 8.04]]

Installing Ubuntu 8.04 (Hardy Heron) on a ThinkPad T61

2008-07-24T14:12:52Z

Lunatico: /* Wireless activity LED */

== Items that work out of the box ==

'''Intel Video:''' 2D and 3D acceleration works

'''Nvidia Video:''' 2D and 3D acceleration works

'''Wireless:''' Intel cards tested. Atheros cards also works.

'''Wireless WAN:''' Cingular/AT&T card tested.

'''Network Card''' Intel 10/100/1000 tested

'''Wireless switch''' Tested

'''Webcam''' Tested with cheese and skype.

'''Headphones''' Works out of the box

'''Microphone''' Just needs to be activated, see section [[#Audio|below]]

'''Keyboard Shortcuts:''' Most of them work out of the box, some need to be activated, see section [[#Multimedia_Keys|below]]

== Items that need (some) tweaking to obtain full functionality ==

=== Open Source Intel Wifi Driver ===
The following information is important if you are upgrading from a previous version of Ubuntu to 8.04.

Intel has created a new Linux Wifi driver project for Intel Wireless cards, "[[Iwlwifi]]". This driver is Open Source and no longer requires the Intel daemon to run in addition. This project will support the [[:Category:T61 | T61]]'s Wifi [[Intel PRO/Wireless 3945ABG Mini-PCI Express Adapter | Intel 3945ABG network adapter]] and [[Intel PRO/Wireless 4965AGN Mini-PCI Express Adapter| Intel 4965AGN network adapter]].

An automatic migration will occur when upgrading from [[Installing Ubuntu 7.10 (Gutsy Gibbon) on a ThinkPad T61|Ubuntu 7.10]] to Ubuntu 8.04. However, there is a caveat to be aware of:
* The new driver wants to name the interface wlan0 (by default -- you can rename it to anything you want), and requires a different entry in {{path|/etc/udev/rules.d/70-persistent-net.rules}}, which handles the naming of interfaces. Simply edit this file and delete your old entry for the ipw3945 driver, then unload/reload the new driver, or simply reboot. A new entry will automatically be created that is appropriate for the new driver. Here's an example of the lines to delete:
<pre>
# PCI device 0x8086:0x4227 (ipw3945)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:1b:77:a4:0e:2f", NAME="eth1"
</pre>

If you need to perform a manual migration, the Ubuntu Help Community has written some [https://help.ubuntu.com/community/WifiDocs/Driver/iwlwifi_Intel_3945_4965/gutsy documentation] that will make this very easy to do.

=== Compiz and XV Playback on Intel GM965/GL960 ===

With Ubuntu 7.10 (Gutsy Gibbon) you currently have to choose between using Compiz and working video playback using XV. On 8.04 (Hardy Heron) alpha 5 you can play videos using XV under compiz, it works right out of the box using the Live-CD.

=== Suspend with Nv140m ===

** Update as of July 17th 2008 -- Using 8.04.1 with the newest nvidea drivers, I had no problems suspending without any additional configuration. **

Suspend may not work even after editing acpi-support. Enable bluetooth (Fn+F5) may result in a successful suspend. NOTE: that although the wifi led does not change when Fn+F5 is used, the wifi is still toggled by this key.

'''Hal "S3 BIOS" parameter issue!'''

After doing the changes to the /etc/default/acpi-support file (described [http://www.thinkwiki.org/wiki/Installing_Ubuntu_7.10_(Gutsy_Gibbon)_on_a_ThinkPad_T61#How_to_Suspend_with_nVidia_140m.2F570m here]), I for one, managed to have '''stable''' suspend support by creating a new file called: '''/etc/hal/fdi/information/lenovo.fdi''' with the following contents:
<pre>
<?xml version="1.0" encoding="ISO-8859-1"?> 
<deviceinfo version="0.2">
<device>
<match key="system.hardware.vendor" string="LENOVO">
<merge key="power_management.quirk.s3_bios" type="bool">false</merge>
</match>
</device>
</deviceinfo>
</pre>
{{NOTE|The problem (after reading the HAL and pm-utils documentations) is the fact that (as far as I can tell) the T61 Lenovo doesn't allow the S3 BIOS to be called *during* suspend/resume, which HAL seems to do by default (who knows, maybe there are T61s out there that do work with this default)!

This did not seem to be necessary for previous versions of Ubuntu. Also note that I have an NVIDIA card so I have no idea what to do for Intel versions.The change should also be resistant to HAL and pm-utils upgrades.}}

'''Still no suspend with nvs140m? Got Modell 6460?'''

Fix above didn't work for me on a 15.4 wide T61 Modell 6460 with nv140m. Bios is updated to 2.14 but didn't change anything, except the usb bug is fix. Suspend seems to work fine, but resume gives me a black screen (backlight off - no reaction to brightness up) and I can hear 2 beeps. Most of the time I can reboot with ctrl+alt+delete but the screen stays dark until bios.

follow the instructions above but create the new file called: '''/etc/hal/fdi/information/lenovo.fdi''' with the following contents instead:
<pre>
<?xml version="1.0" encoding="ISO-8859-1"?> 
<deviceinfo version="0.2">
<device>
<match key="system.hardware.vendor" string="LENOVO">
<merge key="power_management.quirk.s3_mode" type="bool">true</merge>
<merge key="power_management.quirk.s3_bios" type="bool">false</merge>
<merge key="power_management.quirk.save_pci" type="bool">true</merge>
</match>
</device>
</deviceinfo>
</pre>

Also you want to set the following parameter in

{{path|/etc/default/acpi-support}}
<pre>
SAVE_VIDEO_PCI_STATE=true
</pre>

{{NOTE|This works for me with mode 6460, except for one problem: You may get a white screen in xorg after resume when using compiz. If you don't have a 6460 with nvidia this file may break things for you because it doesn't care about the modell and sets the parameter for any lenovo product}}
{{HELP|Anyone with more knowledge of hal and acpi-support is welcome to clean this up. I also don't know why this setting can be done via hal and in acpi-support.
See below!}}

'''Working on hardy final'''

After trying out all these recipes on my 6457CTO waking up from suspend still did not work. Finally I came across a blog entry which pointed out the right way: [[http://david.goodlad.ca/2008/3/14/suspend-hibernate-on-lenovo-t61 David Goodlad's blog]]. I realized that all the fixes proposing editing the acpi-support file or adding a kernel parameter acpi_sleep=s3_mode must be wrong because since hardy gnome-power-manager gets its information solely from hal. So setting up correct hal information is the right way but the proposed solution (creating a /etc/hal/fdi/information/lenovo.fdi file) did not work for me. Ok, but now step by step:

# Revert ALL the proposed fixes from above. I found out that at least the lenovo.fdi solution is actually breaking the real fix. So for sure delete /etc/hal/fdi/information/lenovo.fdi
# Find out about the excact hal name of your machine: <pre>hal-device |grep 6457</pre> where 6457 is the model number of my t61, replace it with your own. In my case it spits out something like this: system.hardware.product = '6457CTO'. So now I know that hal identifies my machine as 6457CTO.
# <pre>sudo gedit /usr/share/hal/fdi/information/10freedesktop/20-video-quirk-pm-lenovo.fdi</pre> and add a section to the end of the file, just above the </device> tag and replace 6457CTO with your hal device name:
<pre>

<match key="system.hardware.product" string="6457CTO">

<merge key="power_management.quirk.s3_mode" type="bool">true</merge>
<merge key="power_management.quirk.s3_bios" type="bool">false</merge>
<merge key="power_management.quirk.save_pci" type="bool">true</merge>
</match>
</pre>

Now save and reboot. Now you might run into the problem of coming back from resume into a completely white screen where normally should be the password dialog. Entering your password blindly is not nice but at least you can resume.

{{NOTE|Somehow I couldn't make the wildcard matching work as they did in the lenovo.fdi solution, but that might be due to my shortcomings on that syntax. Anyway matching the device by its full name worked for me. Probably somebody who knows more about the matching could make that wildcard thing work to have a more general solution. Because hal also knows the xorg driver name (info.linux.driver) there should be a way to set up the quirks depending on the driver.}}

[[Category: T61]]

=== TrackPoint ===
The [[TrackPoint]] works out of the box, but does not scroll nor does the tap-clicking (press to select) feature work. Therefor see: [[#tap-to-click feature]] To enable using the middle mouse button to scroll, replace the "Configured Mouse" section in {{path|/etc/X11/xorg.conf}} with the following:
<pre>
Section "InputDevice"
Identifier "Trackpoint"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ImPS/2"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "true"
Option "EmulateWheel" "true"
Option "EmulateWheelButton" "2"
EndSection
</pre>

{{NOTE|However, if you need to use external usb mouse, the above configuration is wrong. It will cause odd behavior. Try the following configuration from [http://gentoo-wiki.com/HARDWARE_IBM_Specific_Laptop_Guide#TrackPoint Gentoo Wiki]:}}
<pre>
Section "InputDevice"
Identifier "UltraNav TrackPoint"
Driver "mouse"
Option "Device" "/dev/input/mouse1"
Option "Protocol" "ExplorerPS/2"
Option "Emulate3Buttons" "on"
Option "Emulate3TimeOut" "50"
Option "EmulateWheel" "on"
Option "EmulateWheelTimeOut" "200"
Option "EmulateWheelButton" "2"
Option "YAxisMapping" "4 5"
Option "XAxisMapping" "6 7"
Option "ZAxisMapping" "4 5"
EndSection
</pre>

=== Audio ===

Works great out of the box, just the microphone has to be activated, it is considered a generic capture source and is muted by default.

To unmute the microphone:

*Right Click on the volume icon next to the clock and click on "Open Volume Control"

*Click Edit -> Preferences. A list of devices will be displayed, you should check the following (Do not uncheck any existing items):

Input Source
Capture

*Click Close and there should be two additional tabs "Recording" and "Options". -

*Click Recording and click on the microphone under the Capture slider so that it no longer has a red line through it, and put the slider up as it may be deactivated.

*Click Options and under capture source select internal mic.

To test your mic using Sound Recorder select Capture as the sound source.

This solution has been tested with Sound Recorder and Skype.

To get the volume controls working:

*add the following line to /etc/modprobe.d/alsa-base, then reboot

options snd-hda-intel index=0 model=thinkpad

{{NOTE|The volume controls worked fine for me out of the box on a 6460.}}

=== Multimedia Keys ===

Most Multimedia Keys work out of the box, just the play, forward and stop buttons need to be adjusted, therefore, press alt + F2 and type in gnome-keybinding-properties. Then everything works as followed:

* Fn-PgUp activates/deactivates the thinklight
* Fn-Up will trigger stop on a media player
* Fn-Down will toggle pause and play on a media player
* Fn-Left/Right go to prev/next tracks on a media player
* Fn-F2 properly locks the screen
* Fn-F3 shows remaining battery >>does not work on all machines<<
* Fn-F4 suspends (to ram)
* Fn-F9 ejects cds >>does not work on all machines, I think this is supposed to eject from a "dock"<<
* Fn-F12 hibernates (to disk)
* PrtSc opens the screenshot dialog

To enable the back, forward, and the menu keys you'll need to teach XKB what they are.

* Check the '''XkbLayout''' option (under '''InputDevice''') in your {{path|/etc/X11/xorg.conf}} file to determine which keyboard layout Ubuntu is using (I'll use 'us' for the example).
* Navigate to {{path|/etc/X11/xkb/symbols}} and, as root, open the appropriate layout file (as determined above) in your favorite editor.
{{cmduser|cd /etc/X11/xkb/symbols}}
{{cmduser|sudo gedit us}}
* In the '''xkb_symbols "basic"''' section after the '''name[Group1]= "x";''' (where x is a country name, or similar) line add the following:
key <I63> { [ Menu ] };
key <I69> { [ XF86Forward ] };
key <I6A> { [ XF86Back ] };
* Now log out and back in and all three of the buttons should function.

=== Thinkpad Button ===

Paste the following into /usr/share/hotkey-setup/ibm.hk
setkeycodes e017 148 # thinkpad button
You can also just type this into a terminal, to test it for the time of the current session.

Paste the following into the right file in /usr/share/xmodmap (check your country code)
keycode 159 = XF86Terminal
For immediate availability of the button, reload the file by executing
xmodmap <xmodmap.file>

Then use the "Keyboard Shortcuts" tool under "Preferences".

== Items that don't work (a.k.a.: items that need more intense tweaking to get fixed)==

=== tap-to-click feature ===

For the tap-to-click feature (taping the stick instead of using the left mouse button) i used a configure trackpoint utility: [http://tpctl.sourceforge.net/configure-trackpoint.html] there is a package for ubuntu 7.04 i386, but i compiled it by myself (using amd64):

1.) download the .tar.gz file

2.) unpack it

3.) install libgnomeui-dev

{{cmduser|sudo aptitude install libgnomeui-dev}}

4.) in the folder, do:

{{cmduser|./configure}}

if everything worked fine:

{{cmduser|make}}

then install it:

{{cmduser|sudo make install}}

5.a) Gnome : Open it: System > configure trackpoint, and configure on your needs

5.b) Kde : K-menu > Prefences > configure trackpoint > right-click > edit entry, edit "command" to "kdesu configure-trackpoint"

Save & exit

Open it : K-menu > Prefences > configure trackpoint and configure on your needs

=== Hotswapping ===

{{HELP|We need someone who is able to get hotswaping to work properly, this is not the right was to do this!}}
With the new kernel, bay-drivers changed, so if you remove the ultrabay it will freeze your system! You can hack it with a simple comand, first you have to look where the device is:

{{cmduser|less /sys/class/scsi_device/(x)\:0\:0\:0/device/model}}

for (x) first put in 0, if it tells you DVD or the name of the model you want to hotswap youre right. if not, go on with 1, 2 or 3...

then, once you are sure (I deactivated my harddisk like that) you put in:

{{cmduser|echo 1 {{!}} sudo tee /sys/class/scsi_device/(x)\:0\:0\:0/device/delete}}

Now you should be able to remove the device.

{{WARN|Do not use it for harddisks, be sure you unmounted it before! This is just a bad hack, if anyone knows how to get it right --> publish!}}

If Ubuntu does not reactivate the device after putting it in again, do:

{{cmduser|echo 0 0 0 {{!}} sudo tee /sys/class/scsi_host/host1/scan}}

=== Wireless activity LED ===

The LED is not implemented at least in the IWL4965 driver. For the Atheros wifi cards look at the solution [#To_enable_the_Wifi_LED_with_the_Atheros_cards|below]]

A patch posted in this [http://bughost.org/bugzilla/show_bug.cgi?id=1209 thread] works for me on R61 with IWL4965 card.

{{HELP|A howto is needed showing the process of implementing the patch in Hardy Heron. If anyone knows how to do this, please create a quick howto and either put it here or link to it from this page. Please and thank you.}}

As an alternative, you can install a backported IWL4965 driver that ''may'' fix the LED problem on your system.

To active WiFi LED,

sudo apt-get install linux-backports-modules-hardy

{{NOTE|On some machines, (at least one running IWL3945 & IWL4965) applying the above turns on the LED permanently. It should flicker as data is being transmitted. Also, with the above modification, after turning off wireless and then turning it back on (via the switch on the front of the machine) wireless is not reactivated, so not very helpful}}

You can download a compatible [http://wireless.kernel.org/download/compat-wireless-2.6/compat-wireless-2.6.tar.bz2 driver] which supports WiFi led flicking and build it with modifying the {{path|config.mk}} by adding {{bootparm|CONFIG_IWL3945_LEDS|y}} and {{bootparm|CONFIG_IWLWIFI_LEDS|y}} these two options. For Ubuntu/Debian users, build-essential, linux-source-2.6.24 and linux-headers-generic packages are required.

{{HELP|I added the above lines to the config.mk file and it would not make or make install correctly. I received an error 2 at the end of the make. If you have had success, where did you put the items in the config.mk file for it to make and make install correctly? Thanks in advance.}}

==== To enable the Wifi LED with the Atheros cards ====

First check if this solution works on your computer. Open a terminal and run this commands:

sysctl dev.wifi0.ledpin=1
sysctl dev.wifi0.softled=3

Now connect to a wireless network and the LED should start working. If so and you want to make the changes permanent then:

1) Create a file ~/wifiLED and copy/paste the following into it:

#!/bin/bash
#
# Commands to enable the wireless LED
sysctl dev.wifi0.ledpin=1
sysctl dev.wifi0.softled=3

2) sudo cp ~/wifiLED /etc/init.d

3) sudo chmod 755 /etc/init.d/wifiLED

4) sudo update-rc.d wifiLED defaults 90

After you reboot your wireless led should be working.

=== Hidden SSID ===
It has been reported that users wanting to access Hidden SSIDs have to enter the SSID and password manually in Network Manager to connect. Even after the SSID is saved in Network Manager, it will not reconnect automatically. The user has to connect manually by entering the information as previously described.
It appears that updating the driver by following the instructions [http://linuxwireless.org/en/users/Download here] resolves this issue.

=== Hard Disk Parking ===
Getting hard disk parking to work:

tp_smapi patch is not needed in [http://packages.ubuntu.com/search?keywords=linux-image-2.6.24-18&searchon=names&suite=hardy&section=all linux-image-2.6.24-18]

1. Patch your kernel with the 'protect' [http://www.thinkwiki.org/wiki/HDAPS#Kernel_patch patch].

2. Installing the hdapsd daemon which does the actual parking.

{{cmduser|sudo apt-get install hdapsd hdaps-utils}}

== some other tweaks ==

=== screenblank with {{key|Fn}} + {{key|F3}} ===

Its ok, and might be usefull to get the estimated batterytime when pressing {{key|Fn}}+{{key|F3}}, as it should be. But i dont need that, i find the earlier command for {{key|F3}}, to blank the screen, more useful to save batterylife better.

For that, you must edit {{path|/etc/acpi/thinkpad-lockbattery.sh}} and replace LENOVO by IBM, and IBM by LENOVO :). Do not forget to copy the file before you change it!

=== Enable normal User to Limit CPU Speed ===
To let user set the CPU limit you need to open a Terminal an type there
sudo dpkg-reconfigure gnome-applets
answer the question with yes

=== Fix bluish WSXGA+ displays ===
Many T61 owners complain about a very bluish color temperature: My T61 WSXGA+ was also way too blue. I came across a thread at the notebook review forum http://forum.notebookreview.com/showthread.php?t=174408 which provided two useful ICC profiles which fixed the situation for me. Just install xcalib
sudo apt-get install xcalib
and load one of these profiles.

[[Category: Ubuntu 8.04]]

Installing Ubuntu 8.04 (Hardy Heron) on a ThinkPad T61

2008-07-24T14:12:20Z

Lunatico: /* Wireless activity LED */

== Items that work out of the box ==

'''Intel Video:''' 2D and 3D acceleration works

'''Nvidia Video:''' 2D and 3D acceleration works

'''Wireless:''' Intel cards tested. Atheros cards also works.

'''Wireless WAN:''' Cingular/AT&T card tested.

'''Network Card''' Intel 10/100/1000 tested

'''Wireless switch''' Tested

'''Webcam''' Tested with cheese and skype.

'''Headphones''' Works out of the box

'''Microphone''' Just needs to be activated, see section [[#Audio|below]]

'''Keyboard Shortcuts:''' Most of them work out of the box, some need to be activated, see section [[#Multimedia_Keys|below]]

== Items that need (some) tweaking to obtain full functionality ==

=== Open Source Intel Wifi Driver ===
The following information is important if you are upgrading from a previous version of Ubuntu to 8.04.

Intel has created a new Linux Wifi driver project for Intel Wireless cards, "[[Iwlwifi]]". This driver is Open Source and no longer requires the Intel daemon to run in addition. This project will support the [[:Category:T61 | T61]]'s Wifi [[Intel PRO/Wireless 3945ABG Mini-PCI Express Adapter | Intel 3945ABG network adapter]] and [[Intel PRO/Wireless 4965AGN Mini-PCI Express Adapter| Intel 4965AGN network adapter]].

An automatic migration will occur when upgrading from [[Installing Ubuntu 7.10 (Gutsy Gibbon) on a ThinkPad T61|Ubuntu 7.10]] to Ubuntu 8.04. However, there is a caveat to be aware of:
* The new driver wants to name the interface wlan0 (by default -- you can rename it to anything you want), and requires a different entry in {{path|/etc/udev/rules.d/70-persistent-net.rules}}, which handles the naming of interfaces. Simply edit this file and delete your old entry for the ipw3945 driver, then unload/reload the new driver, or simply reboot. A new entry will automatically be created that is appropriate for the new driver. Here's an example of the lines to delete:
<pre>
# PCI device 0x8086:0x4227 (ipw3945)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:1b:77:a4:0e:2f", NAME="eth1"
</pre>

If you need to perform a manual migration, the Ubuntu Help Community has written some [https://help.ubuntu.com/community/WifiDocs/Driver/iwlwifi_Intel_3945_4965/gutsy documentation] that will make this very easy to do.

=== Compiz and XV Playback on Intel GM965/GL960 ===

With Ubuntu 7.10 (Gutsy Gibbon) you currently have to choose between using Compiz and working video playback using XV. On 8.04 (Hardy Heron) alpha 5 you can play videos using XV under compiz, it works right out of the box using the Live-CD.

=== Suspend with Nv140m ===

** Update as of July 17th 2008 -- Using 8.04.1 with the newest nvidea drivers, I had no problems suspending without any additional configuration. **

Suspend may not work even after editing acpi-support. Enable bluetooth (Fn+F5) may result in a successful suspend. NOTE: that although the wifi led does not change when Fn+F5 is used, the wifi is still toggled by this key.

'''Hal "S3 BIOS" parameter issue!'''

After doing the changes to the /etc/default/acpi-support file (described [http://www.thinkwiki.org/wiki/Installing_Ubuntu_7.10_(Gutsy_Gibbon)_on_a_ThinkPad_T61#How_to_Suspend_with_nVidia_140m.2F570m here]), I for one, managed to have '''stable''' suspend support by creating a new file called: '''/etc/hal/fdi/information/lenovo.fdi''' with the following contents:
<pre>
<?xml version="1.0" encoding="ISO-8859-1"?> 
<deviceinfo version="0.2">
<device>
<match key="system.hardware.vendor" string="LENOVO">
<merge key="power_management.quirk.s3_bios" type="bool">false</merge>
</match>
</device>
</deviceinfo>
</pre>
{{NOTE|The problem (after reading the HAL and pm-utils documentations) is the fact that (as far as I can tell) the T61 Lenovo doesn't allow the S3 BIOS to be called *during* suspend/resume, which HAL seems to do by default (who knows, maybe there are T61s out there that do work with this default)!

This did not seem to be necessary for previous versions of Ubuntu. Also note that I have an NVIDIA card so I have no idea what to do for Intel versions.The change should also be resistant to HAL and pm-utils upgrades.}}

'''Still no suspend with nvs140m? Got Modell 6460?'''

Fix above didn't work for me on a 15.4 wide T61 Modell 6460 with nv140m. Bios is updated to 2.14 but didn't change anything, except the usb bug is fix. Suspend seems to work fine, but resume gives me a black screen (backlight off - no reaction to brightness up) and I can hear 2 beeps. Most of the time I can reboot with ctrl+alt+delete but the screen stays dark until bios.

follow the instructions above but create the new file called: '''/etc/hal/fdi/information/lenovo.fdi''' with the following contents instead:
<pre>
<?xml version="1.0" encoding="ISO-8859-1"?> 
<deviceinfo version="0.2">
<device>
<match key="system.hardware.vendor" string="LENOVO">
<merge key="power_management.quirk.s3_mode" type="bool">true</merge>
<merge key="power_management.quirk.s3_bios" type="bool">false</merge>
<merge key="power_management.quirk.save_pci" type="bool">true</merge>
</match>
</device>
</deviceinfo>
</pre>

Also you want to set the following parameter in

{{path|/etc/default/acpi-support}}
<pre>
SAVE_VIDEO_PCI_STATE=true
</pre>

{{NOTE|This works for me with mode 6460, except for one problem: You may get a white screen in xorg after resume when using compiz. If you don't have a 6460 with nvidia this file may break things for you because it doesn't care about the modell and sets the parameter for any lenovo product}}
{{HELP|Anyone with more knowledge of hal and acpi-support is welcome to clean this up. I also don't know why this setting can be done via hal and in acpi-support.
See below!}}

'''Working on hardy final'''

After trying out all these recipes on my 6457CTO waking up from suspend still did not work. Finally I came across a blog entry which pointed out the right way: [[http://david.goodlad.ca/2008/3/14/suspend-hibernate-on-lenovo-t61 David Goodlad's blog]]. I realized that all the fixes proposing editing the acpi-support file or adding a kernel parameter acpi_sleep=s3_mode must be wrong because since hardy gnome-power-manager gets its information solely from hal. So setting up correct hal information is the right way but the proposed solution (creating a /etc/hal/fdi/information/lenovo.fdi file) did not work for me. Ok, but now step by step:

# Revert ALL the proposed fixes from above. I found out that at least the lenovo.fdi solution is actually breaking the real fix. So for sure delete /etc/hal/fdi/information/lenovo.fdi
# Find out about the excact hal name of your machine: <pre>hal-device |grep 6457</pre> where 6457 is the model number of my t61, replace it with your own. In my case it spits out something like this: system.hardware.product = '6457CTO'. So now I know that hal identifies my machine as 6457CTO.
# <pre>sudo gedit /usr/share/hal/fdi/information/10freedesktop/20-video-quirk-pm-lenovo.fdi</pre> and add a section to the end of the file, just above the </device> tag and replace 6457CTO with your hal device name:
<pre>

<match key="system.hardware.product" string="6457CTO">

<merge key="power_management.quirk.s3_mode" type="bool">true</merge>
<merge key="power_management.quirk.s3_bios" type="bool">false</merge>
<merge key="power_management.quirk.save_pci" type="bool">true</merge>
</match>
</pre>

Now save and reboot. Now you might run into the problem of coming back from resume into a completely white screen where normally should be the password dialog. Entering your password blindly is not nice but at least you can resume.

{{NOTE|Somehow I couldn't make the wildcard matching work as they did in the lenovo.fdi solution, but that might be due to my shortcomings on that syntax. Anyway matching the device by its full name worked for me. Probably somebody who knows more about the matching could make that wildcard thing work to have a more general solution. Because hal also knows the xorg driver name (info.linux.driver) there should be a way to set up the quirks depending on the driver.}}

[[Category: T61]]

=== TrackPoint ===
The [[TrackPoint]] works out of the box, but does not scroll nor does the tap-clicking (press to select) feature work. Therefor see: [[#tap-to-click feature]] To enable using the middle mouse button to scroll, replace the "Configured Mouse" section in {{path|/etc/X11/xorg.conf}} with the following:
<pre>
Section "InputDevice"
Identifier "Trackpoint"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ImPS/2"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "true"
Option "EmulateWheel" "true"
Option "EmulateWheelButton" "2"
EndSection
</pre>

{{NOTE|However, if you need to use external usb mouse, the above configuration is wrong. It will cause odd behavior. Try the following configuration from [http://gentoo-wiki.com/HARDWARE_IBM_Specific_Laptop_Guide#TrackPoint Gentoo Wiki]:}}
<pre>
Section "InputDevice"
Identifier "UltraNav TrackPoint"
Driver "mouse"
Option "Device" "/dev/input/mouse1"
Option "Protocol" "ExplorerPS/2"
Option "Emulate3Buttons" "on"
Option "Emulate3TimeOut" "50"
Option "EmulateWheel" "on"
Option "EmulateWheelTimeOut" "200"
Option "EmulateWheelButton" "2"
Option "YAxisMapping" "4 5"
Option "XAxisMapping" "6 7"
Option "ZAxisMapping" "4 5"
EndSection
</pre>

=== Audio ===

Works great out of the box, just the microphone has to be activated, it is considered a generic capture source and is muted by default.

To unmute the microphone:

*Right Click on the volume icon next to the clock and click on "Open Volume Control"

*Click Edit -> Preferences. A list of devices will be displayed, you should check the following (Do not uncheck any existing items):

Input Source
Capture

*Click Close and there should be two additional tabs "Recording" and "Options". -

*Click Recording and click on the microphone under the Capture slider so that it no longer has a red line through it, and put the slider up as it may be deactivated.

*Click Options and under capture source select internal mic.

To test your mic using Sound Recorder select Capture as the sound source.

This solution has been tested with Sound Recorder and Skype.

To get the volume controls working:

*add the following line to /etc/modprobe.d/alsa-base, then reboot

options snd-hda-intel index=0 model=thinkpad

{{NOTE|The volume controls worked fine for me out of the box on a 6460.}}

=== Multimedia Keys ===

Most Multimedia Keys work out of the box, just the play, forward and stop buttons need to be adjusted, therefore, press alt + F2 and type in gnome-keybinding-properties. Then everything works as followed:

* Fn-PgUp activates/deactivates the thinklight
* Fn-Up will trigger stop on a media player
* Fn-Down will toggle pause and play on a media player
* Fn-Left/Right go to prev/next tracks on a media player
* Fn-F2 properly locks the screen
* Fn-F3 shows remaining battery >>does not work on all machines<<
* Fn-F4 suspends (to ram)
* Fn-F9 ejects cds >>does not work on all machines, I think this is supposed to eject from a "dock"<<
* Fn-F12 hibernates (to disk)
* PrtSc opens the screenshot dialog

To enable the back, forward, and the menu keys you'll need to teach XKB what they are.

* Check the '''XkbLayout''' option (under '''InputDevice''') in your {{path|/etc/X11/xorg.conf}} file to determine which keyboard layout Ubuntu is using (I'll use 'us' for the example).
* Navigate to {{path|/etc/X11/xkb/symbols}} and, as root, open the appropriate layout file (as determined above) in your favorite editor.
{{cmduser|cd /etc/X11/xkb/symbols}}
{{cmduser|sudo gedit us}}
* In the '''xkb_symbols "basic"''' section after the '''name[Group1]= "x";''' (where x is a country name, or similar) line add the following:
key <I63> { [ Menu ] };
key <I69> { [ XF86Forward ] };
key <I6A> { [ XF86Back ] };
* Now log out and back in and all three of the buttons should function.

=== Thinkpad Button ===

Paste the following into /usr/share/hotkey-setup/ibm.hk
setkeycodes e017 148 # thinkpad button
You can also just type this into a terminal, to test it for the time of the current session.

Paste the following into the right file in /usr/share/xmodmap (check your country code)
keycode 159 = XF86Terminal
For immediate availability of the button, reload the file by executing
xmodmap <xmodmap.file>

Then use the "Keyboard Shortcuts" tool under "Preferences".

== Items that don't work (a.k.a.: items that need more intense tweaking to get fixed)==

=== tap-to-click feature ===

For the tap-to-click feature (taping the stick instead of using the left mouse button) i used a configure trackpoint utility: [http://tpctl.sourceforge.net/configure-trackpoint.html] there is a package for ubuntu 7.04 i386, but i compiled it by myself (using amd64):

1.) download the .tar.gz file

2.) unpack it

3.) install libgnomeui-dev

{{cmduser|sudo aptitude install libgnomeui-dev}}

4.) in the folder, do:

{{cmduser|./configure}}

if everything worked fine:

{{cmduser|make}}

then install it:

{{cmduser|sudo make install}}

5.a) Gnome : Open it: System > configure trackpoint, and configure on your needs

5.b) Kde : K-menu > Prefences > configure trackpoint > right-click > edit entry, edit "command" to "kdesu configure-trackpoint"

Save & exit

Open it : K-menu > Prefences > configure trackpoint and configure on your needs

=== Hotswapping ===

{{HELP|We need someone who is able to get hotswaping to work properly, this is not the right was to do this!}}
With the new kernel, bay-drivers changed, so if you remove the ultrabay it will freeze your system! You can hack it with a simple comand, first you have to look where the device is:

{{cmduser|less /sys/class/scsi_device/(x)\:0\:0\:0/device/model}}

for (x) first put in 0, if it tells you DVD or the name of the model you want to hotswap youre right. if not, go on with 1, 2 or 3...

then, once you are sure (I deactivated my harddisk like that) you put in:

{{cmduser|echo 1 {{!}} sudo tee /sys/class/scsi_device/(x)\:0\:0\:0/device/delete}}

Now you should be able to remove the device.

{{WARN|Do not use it for harddisks, be sure you unmounted it before! This is just a bad hack, if anyone knows how to get it right --> publish!}}

If Ubuntu does not reactivate the device after putting it in again, do:

{{cmduser|echo 0 0 0 {{!}} sudo tee /sys/class/scsi_host/host1/scan}}

=== Wireless activity LED ===

The LED is not implemented at least in the IWL4965 driver. For the Atheros wifi cards look at the solution [#To_enable_the_Wifi_LED_with_the_Atheros_cards|below]].

A patch posted in this [http://bughost.org/bugzilla/show_bug.cgi?id=1209 thread] works for me on R61 with IWL4965 card.

{{HELP|A howto is needed showing the process of implementing the patch in Hardy Heron. If anyone knows how to do this, please create a quick howto and either put it here or link to it from this page. Please and thank you.}}

As an alternative, you can install a backported IWL4965 driver that ''may'' fix the LED problem on your system.

To active WiFi LED,

sudo apt-get install linux-backports-modules-hardy

{{NOTE|On some machines, (at least one running IWL3945 & IWL4965) applying the above turns on the LED permanently. It should flicker as data is being transmitted. Also, with the above modification, after turning off wireless and then turning it back on (via the switch on the front of the machine) wireless is not reactivated, so not very helpful}}

You can download a compatible [http://wireless.kernel.org/download/compat-wireless-2.6/compat-wireless-2.6.tar.bz2 driver] which supports WiFi led flicking and build it with modifying the {{path|config.mk}} by adding {{bootparm|CONFIG_IWL3945_LEDS|y}} and {{bootparm|CONFIG_IWLWIFI_LEDS|y}} these two options. For Ubuntu/Debian users, build-essential, linux-source-2.6.24 and linux-headers-generic packages are required.

{{HELP|I added the above lines to the config.mk file and it would not make or make install correctly. I received an error 2 at the end of the make. If you have had success, where did you put the items in the config.mk file for it to make and make install correctly? Thanks in advance.}}

==== To enable the Wifi LED with the Atheros cards ====

First check if this solution works on your computer. Open a terminal and run this commands:

sysctl dev.wifi0.ledpin=1
sysctl dev.wifi0.softled=3

Now connect to a wireless network and the LED should start working. If so and you want to make the changes permanent then:

1) Create a file ~/wifiLED and copy/paste the following into it:

#!/bin/bash
#
# Commands to enable the wireless LED
sysctl dev.wifi0.ledpin=1
sysctl dev.wifi0.softled=3

2) sudo cp ~/wifiLED /etc/init.d

3) sudo chmod 755 /etc/init.d/wifiLED

4) sudo update-rc.d wifiLED defaults 90

After you reboot your wireless led should be working.

=== Hidden SSID ===
It has been reported that users wanting to access Hidden SSIDs have to enter the SSID and password manually in Network Manager to connect. Even after the SSID is saved in Network Manager, it will not reconnect automatically. The user has to connect manually by entering the information as previously described.
It appears that updating the driver by following the instructions [http://linuxwireless.org/en/users/Download here] resolves this issue.

=== Hard Disk Parking ===
Getting hard disk parking to work:

tp_smapi patch is not needed in [http://packages.ubuntu.com/search?keywords=linux-image-2.6.24-18&searchon=names&suite=hardy&section=all linux-image-2.6.24-18]

1. Patch your kernel with the 'protect' [http://www.thinkwiki.org/wiki/HDAPS#Kernel_patch patch].

2. Installing the hdapsd daemon which does the actual parking.

{{cmduser|sudo apt-get install hdapsd hdaps-utils}}

== some other tweaks ==

=== screenblank with {{key|Fn}} + {{key|F3}} ===

Its ok, and might be usefull to get the estimated batterytime when pressing {{key|Fn}}+{{key|F3}}, as it should be. But i dont need that, i find the earlier command for {{key|F3}}, to blank the screen, more useful to save batterylife better.

For that, you must edit {{path|/etc/acpi/thinkpad-lockbattery.sh}} and replace LENOVO by IBM, and IBM by LENOVO :). Do not forget to copy the file before you change it!

=== Enable normal User to Limit CPU Speed ===
To let user set the CPU limit you need to open a Terminal an type there
sudo dpkg-reconfigure gnome-applets
answer the question with yes

=== Fix bluish WSXGA+ displays ===
Many T61 owners complain about a very bluish color temperature: My T61 WSXGA+ was also way too blue. I came across a thread at the notebook review forum http://forum.notebookreview.com/showthread.php?t=174408 which provided two useful ICC profiles which fixed the situation for me. Just install xcalib
sudo apt-get install xcalib
and load one of these profiles.

[[Category: Ubuntu 8.04]]

Installing Ubuntu 8.04 (Hardy Heron) on a ThinkPad T61

2008-07-24T14:09:29Z

Lunatico: /* Wireless activity LED */

== Items that work out of the box ==

'''Intel Video:''' 2D and 3D acceleration works

'''Nvidia Video:''' 2D and 3D acceleration works

'''Wireless:''' Intel cards tested. Atheros cards also works.

'''Wireless WAN:''' Cingular/AT&T card tested.

'''Network Card''' Intel 10/100/1000 tested

'''Wireless switch''' Tested

'''Webcam''' Tested with cheese and skype.

'''Headphones''' Works out of the box

'''Microphone''' Just needs to be activated, see section [[#Audio|below]]

'''Keyboard Shortcuts:''' Most of them work out of the box, some need to be activated, see section [[#Multimedia_Keys|below]]

== Items that need (some) tweaking to obtain full functionality ==

=== Open Source Intel Wifi Driver ===
The following information is important if you are upgrading from a previous version of Ubuntu to 8.04.

Intel has created a new Linux Wifi driver project for Intel Wireless cards, "[[Iwlwifi]]". This driver is Open Source and no longer requires the Intel daemon to run in addition. This project will support the [[:Category:T61 | T61]]'s Wifi [[Intel PRO/Wireless 3945ABG Mini-PCI Express Adapter | Intel 3945ABG network adapter]] and [[Intel PRO/Wireless 4965AGN Mini-PCI Express Adapter| Intel 4965AGN network adapter]].

An automatic migration will occur when upgrading from [[Installing Ubuntu 7.10 (Gutsy Gibbon) on a ThinkPad T61|Ubuntu 7.10]] to Ubuntu 8.04. However, there is a caveat to be aware of:
* The new driver wants to name the interface wlan0 (by default -- you can rename it to anything you want), and requires a different entry in {{path|/etc/udev/rules.d/70-persistent-net.rules}}, which handles the naming of interfaces. Simply edit this file and delete your old entry for the ipw3945 driver, then unload/reload the new driver, or simply reboot. A new entry will automatically be created that is appropriate for the new driver. Here's an example of the lines to delete:
<pre>
# PCI device 0x8086:0x4227 (ipw3945)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:1b:77:a4:0e:2f", NAME="eth1"
</pre>

If you need to perform a manual migration, the Ubuntu Help Community has written some [https://help.ubuntu.com/community/WifiDocs/Driver/iwlwifi_Intel_3945_4965/gutsy documentation] that will make this very easy to do.

=== Compiz and XV Playback on Intel GM965/GL960 ===

With Ubuntu 7.10 (Gutsy Gibbon) you currently have to choose between using Compiz and working video playback using XV. On 8.04 (Hardy Heron) alpha 5 you can play videos using XV under compiz, it works right out of the box using the Live-CD.

=== Suspend with Nv140m ===

** Update as of July 17th 2008 -- Using 8.04.1 with the newest nvidea drivers, I had no problems suspending without any additional configuration. **

Suspend may not work even after editing acpi-support. Enable bluetooth (Fn+F5) may result in a successful suspend. NOTE: that although the wifi led does not change when Fn+F5 is used, the wifi is still toggled by this key.

'''Hal "S3 BIOS" parameter issue!'''

After doing the changes to the /etc/default/acpi-support file (described [http://www.thinkwiki.org/wiki/Installing_Ubuntu_7.10_(Gutsy_Gibbon)_on_a_ThinkPad_T61#How_to_Suspend_with_nVidia_140m.2F570m here]), I for one, managed to have '''stable''' suspend support by creating a new file called: '''/etc/hal/fdi/information/lenovo.fdi''' with the following contents:
<pre>
<?xml version="1.0" encoding="ISO-8859-1"?> 
<deviceinfo version="0.2">
<device>
<match key="system.hardware.vendor" string="LENOVO">
<merge key="power_management.quirk.s3_bios" type="bool">false</merge>
</match>
</device>
</deviceinfo>
</pre>
{{NOTE|The problem (after reading the HAL and pm-utils documentations) is the fact that (as far as I can tell) the T61 Lenovo doesn't allow the S3 BIOS to be called *during* suspend/resume, which HAL seems to do by default (who knows, maybe there are T61s out there that do work with this default)!

This did not seem to be necessary for previous versions of Ubuntu. Also note that I have an NVIDIA card so I have no idea what to do for Intel versions.The change should also be resistant to HAL and pm-utils upgrades.}}

'''Still no suspend with nvs140m? Got Modell 6460?'''

Fix above didn't work for me on a 15.4 wide T61 Modell 6460 with nv140m. Bios is updated to 2.14 but didn't change anything, except the usb bug is fix. Suspend seems to work fine, but resume gives me a black screen (backlight off - no reaction to brightness up) and I can hear 2 beeps. Most of the time I can reboot with ctrl+alt+delete but the screen stays dark until bios.

follow the instructions above but create the new file called: '''/etc/hal/fdi/information/lenovo.fdi''' with the following contents instead:
<pre>
<?xml version="1.0" encoding="ISO-8859-1"?> 
<deviceinfo version="0.2">
<device>
<match key="system.hardware.vendor" string="LENOVO">
<merge key="power_management.quirk.s3_mode" type="bool">true</merge>
<merge key="power_management.quirk.s3_bios" type="bool">false</merge>
<merge key="power_management.quirk.save_pci" type="bool">true</merge>
</match>
</device>
</deviceinfo>
</pre>

Also you want to set the following parameter in

{{path|/etc/default/acpi-support}}
<pre>
SAVE_VIDEO_PCI_STATE=true
</pre>

{{NOTE|This works for me with mode 6460, except for one problem: You may get a white screen in xorg after resume when using compiz. If you don't have a 6460 with nvidia this file may break things for you because it doesn't care about the modell and sets the parameter for any lenovo product}}
{{HELP|Anyone with more knowledge of hal and acpi-support is welcome to clean this up. I also don't know why this setting can be done via hal and in acpi-support.
See below!}}

'''Working on hardy final'''

After trying out all these recipes on my 6457CTO waking up from suspend still did not work. Finally I came across a blog entry which pointed out the right way: [[http://david.goodlad.ca/2008/3/14/suspend-hibernate-on-lenovo-t61 David Goodlad's blog]]. I realized that all the fixes proposing editing the acpi-support file or adding a kernel parameter acpi_sleep=s3_mode must be wrong because since hardy gnome-power-manager gets its information solely from hal. So setting up correct hal information is the right way but the proposed solution (creating a /etc/hal/fdi/information/lenovo.fdi file) did not work for me. Ok, but now step by step:

# Revert ALL the proposed fixes from above. I found out that at least the lenovo.fdi solution is actually breaking the real fix. So for sure delete /etc/hal/fdi/information/lenovo.fdi
# Find out about the excact hal name of your machine: <pre>hal-device |grep 6457</pre> where 6457 is the model number of my t61, replace it with your own. In my case it spits out something like this: system.hardware.product = '6457CTO'. So now I know that hal identifies my machine as 6457CTO.
# <pre>sudo gedit /usr/share/hal/fdi/information/10freedesktop/20-video-quirk-pm-lenovo.fdi</pre> and add a section to the end of the file, just above the </device> tag and replace 6457CTO with your hal device name:
<pre>

<match key="system.hardware.product" string="6457CTO">

<merge key="power_management.quirk.s3_mode" type="bool">true</merge>
<merge key="power_management.quirk.s3_bios" type="bool">false</merge>
<merge key="power_management.quirk.save_pci" type="bool">true</merge>
</match>
</pre>

Now save and reboot. Now you might run into the problem of coming back from resume into a completely white screen where normally should be the password dialog. Entering your password blindly is not nice but at least you can resume.

{{NOTE|Somehow I couldn't make the wildcard matching work as they did in the lenovo.fdi solution, but that might be due to my shortcomings on that syntax. Anyway matching the device by its full name worked for me. Probably somebody who knows more about the matching could make that wildcard thing work to have a more general solution. Because hal also knows the xorg driver name (info.linux.driver) there should be a way to set up the quirks depending on the driver.}}

[[Category: T61]]

=== TrackPoint ===
The [[TrackPoint]] works out of the box, but does not scroll nor does the tap-clicking (press to select) feature work. Therefor see: [[#tap-to-click feature]] To enable using the middle mouse button to scroll, replace the "Configured Mouse" section in {{path|/etc/X11/xorg.conf}} with the following:
<pre>
Section "InputDevice"
Identifier "Trackpoint"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ImPS/2"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "true"
Option "EmulateWheel" "true"
Option "EmulateWheelButton" "2"
EndSection
</pre>

{{NOTE|However, if you need to use external usb mouse, the above configuration is wrong. It will cause odd behavior. Try the following configuration from [http://gentoo-wiki.com/HARDWARE_IBM_Specific_Laptop_Guide#TrackPoint Gentoo Wiki]:}}
<pre>
Section "InputDevice"
Identifier "UltraNav TrackPoint"
Driver "mouse"
Option "Device" "/dev/input/mouse1"
Option "Protocol" "ExplorerPS/2"
Option "Emulate3Buttons" "on"
Option "Emulate3TimeOut" "50"
Option "EmulateWheel" "on"
Option "EmulateWheelTimeOut" "200"
Option "EmulateWheelButton" "2"
Option "YAxisMapping" "4 5"
Option "XAxisMapping" "6 7"
Option "ZAxisMapping" "4 5"
EndSection
</pre>

=== Audio ===

Works great out of the box, just the microphone has to be activated, it is considered a generic capture source and is muted by default.

To unmute the microphone:

*Right Click on the volume icon next to the clock and click on "Open Volume Control"

*Click Edit -> Preferences. A list of devices will be displayed, you should check the following (Do not uncheck any existing items):

Input Source
Capture

*Click Close and there should be two additional tabs "Recording" and "Options". -

*Click Recording and click on the microphone under the Capture slider so that it no longer has a red line through it, and put the slider up as it may be deactivated.

*Click Options and under capture source select internal mic.

To test your mic using Sound Recorder select Capture as the sound source.

This solution has been tested with Sound Recorder and Skype.

To get the volume controls working:

*add the following line to /etc/modprobe.d/alsa-base, then reboot

options snd-hda-intel index=0 model=thinkpad

{{NOTE|The volume controls worked fine for me out of the box on a 6460.}}

=== Multimedia Keys ===

Most Multimedia Keys work out of the box, just the play, forward and stop buttons need to be adjusted, therefore, press alt + F2 and type in gnome-keybinding-properties. Then everything works as followed:

* Fn-PgUp activates/deactivates the thinklight
* Fn-Up will trigger stop on a media player
* Fn-Down will toggle pause and play on a media player
* Fn-Left/Right go to prev/next tracks on a media player
* Fn-F2 properly locks the screen
* Fn-F3 shows remaining battery >>does not work on all machines<<
* Fn-F4 suspends (to ram)
* Fn-F9 ejects cds >>does not work on all machines, I think this is supposed to eject from a "dock"<<
* Fn-F12 hibernates (to disk)
* PrtSc opens the screenshot dialog

To enable the back, forward, and the menu keys you'll need to teach XKB what they are.

* Check the '''XkbLayout''' option (under '''InputDevice''') in your {{path|/etc/X11/xorg.conf}} file to determine which keyboard layout Ubuntu is using (I'll use 'us' for the example).
* Navigate to {{path|/etc/X11/xkb/symbols}} and, as root, open the appropriate layout file (as determined above) in your favorite editor.
{{cmduser|cd /etc/X11/xkb/symbols}}
{{cmduser|sudo gedit us}}
* In the '''xkb_symbols "basic"''' section after the '''name[Group1]= "x";''' (where x is a country name, or similar) line add the following:
key <I63> { [ Menu ] };
key <I69> { [ XF86Forward ] };
key <I6A> { [ XF86Back ] };
* Now log out and back in and all three of the buttons should function.

=== Thinkpad Button ===

Paste the following into /usr/share/hotkey-setup/ibm.hk
setkeycodes e017 148 # thinkpad button
You can also just type this into a terminal, to test it for the time of the current session.

Paste the following into the right file in /usr/share/xmodmap (check your country code)
keycode 159 = XF86Terminal
For immediate availability of the button, reload the file by executing
xmodmap <xmodmap.file>

Then use the "Keyboard Shortcuts" tool under "Preferences".

== Items that don't work (a.k.a.: items that need more intense tweaking to get fixed)==

=== tap-to-click feature ===

For the tap-to-click feature (taping the stick instead of using the left mouse button) i used a configure trackpoint utility: [http://tpctl.sourceforge.net/configure-trackpoint.html] there is a package for ubuntu 7.04 i386, but i compiled it by myself (using amd64):

1.) download the .tar.gz file

2.) unpack it

3.) install libgnomeui-dev

{{cmduser|sudo aptitude install libgnomeui-dev}}

4.) in the folder, do:

{{cmduser|./configure}}

if everything worked fine:

{{cmduser|make}}

then install it:

{{cmduser|sudo make install}}

5.a) Gnome : Open it: System > configure trackpoint, and configure on your needs

5.b) Kde : K-menu > Prefences > configure trackpoint > right-click > edit entry, edit "command" to "kdesu configure-trackpoint"

Save & exit

Open it : K-menu > Prefences > configure trackpoint and configure on your needs

=== Hotswapping ===

{{HELP|We need someone who is able to get hotswaping to work properly, this is not the right was to do this!}}
With the new kernel, bay-drivers changed, so if you remove the ultrabay it will freeze your system! You can hack it with a simple comand, first you have to look where the device is:

{{cmduser|less /sys/class/scsi_device/(x)\:0\:0\:0/device/model}}

for (x) first put in 0, if it tells you DVD or the name of the model you want to hotswap youre right. if not, go on with 1, 2 or 3...

then, once you are sure (I deactivated my harddisk like that) you put in:

{{cmduser|echo 1 {{!}} sudo tee /sys/class/scsi_device/(x)\:0\:0\:0/device/delete}}

Now you should be able to remove the device.

{{WARN|Do not use it for harddisks, be sure you unmounted it before! This is just a bad hack, if anyone knows how to get it right --> publish!}}

If Ubuntu does not reactivate the device after putting it in again, do:

{{cmduser|echo 0 0 0 {{!}} sudo tee /sys/class/scsi_host/host1/scan}}

=== Wireless activity LED ===

The LED is not implemented at least in the IWL4965 driver. For the Atheros wifi cards look at the solution [#To enable the Wifi LED with the Atheros cards|below]].

A patch posted in this [http://bughost.org/bugzilla/show_bug.cgi?id=1209 thread] works for me on R61 with IWL4965 card.

{{HELP|A howto is needed showing the process of implementing the patch in Hardy Heron. If anyone knows how to do this, please create a quick howto and either put it here or link to it from this page. Please and thank you.}}

As an alternative, you can install a backported IWL4965 driver that ''may'' fix the LED problem on your system.

To active WiFi LED,

sudo apt-get install linux-backports-modules-hardy

{{NOTE|On some machines, (at least one running IWL3945 & IWL4965) applying the above turns on the LED permanently. It should flicker as data is being transmitted. Also, with the above modification, after turning off wireless and then turning it back on (via the switch on the front of the machine) wireless is not reactivated, so not very helpful}}

You can download a compatible [http://wireless.kernel.org/download/compat-wireless-2.6/compat-wireless-2.6.tar.bz2 driver] which supports WiFi led flicking and build it with modifying the {{path|config.mk}} by adding {{bootparm|CONFIG_IWL3945_LEDS|y}} and {{bootparm|CONFIG_IWLWIFI_LEDS|y}} these two options. For Ubuntu/Debian users, build-essential, linux-source-2.6.24 and linux-headers-generic packages are required.

{{HELP|I added the above lines to the config.mk file and it would not make or make install correctly. I received an error 2 at the end of the make. If you have had success, where did you put the items in the config.mk file for it to make and make install correctly? Thanks in advance.}}

==== To enable the Wifi LED with the Atheros cards ====

First check if this solution works on your computer. Open a terminal and run this commands:

sysctl dev.wifi0.ledpin=1
sysctl dev.wifi0.softled=3

Now connect to a wireless network and the LED should start working. If so and you want to make the changes permanent then:

1) Create a file ~/wifiLED and copy/paste the following into it:

#!/bin/bash
#
# Commands to enable the wireless LED
sysctl dev.wifi0.ledpin=1
sysctl dev.wifi0.softled=3

2) sudo cp ~/wifiLED /etc/init.d

3) sudo chmod 755 /etc/init.d/wifiLED

4) sudo update-rc.d wifiLED defaults 90

After you reboot your wireless led should be working.

=== Hidden SSID ===
It has been reported that users wanting to access Hidden SSIDs have to enter the SSID and password manually in Network Manager to connect. Even after the SSID is saved in Network Manager, it will not reconnect automatically. The user has to connect manually by entering the information as previously described.
It appears that updating the driver by following the instructions [http://linuxwireless.org/en/users/Download here] resolves this issue.

=== Hard Disk Parking ===
Getting hard disk parking to work:

tp_smapi patch is not needed in [http://packages.ubuntu.com/search?keywords=linux-image-2.6.24-18&searchon=names&suite=hardy&section=all linux-image-2.6.24-18]

1. Patch your kernel with the 'protect' [http://www.thinkwiki.org/wiki/HDAPS#Kernel_patch patch].

2. Installing the hdapsd daemon which does the actual parking.

{{cmduser|sudo apt-get install hdapsd hdaps-utils}}

== some other tweaks ==

=== screenblank with {{key|Fn}} + {{key|F3}} ===

Its ok, and might be usefull to get the estimated batterytime when pressing {{key|Fn}}+{{key|F3}}, as it should be. But i dont need that, i find the earlier command for {{key|F3}}, to blank the screen, more useful to save batterylife better.

For that, you must edit {{path|/etc/acpi/thinkpad-lockbattery.sh}} and replace LENOVO by IBM, and IBM by LENOVO :). Do not forget to copy the file before you change it!

=== Enable normal User to Limit CPU Speed ===
To let user set the CPU limit you need to open a Terminal an type there
sudo dpkg-reconfigure gnome-applets
answer the question with yes

=== Fix bluish WSXGA+ displays ===
Many T61 owners complain about a very bluish color temperature: My T61 WSXGA+ was also way too blue. I came across a thread at the notebook review forum http://forum.notebookreview.com/showthread.php?t=174408 which provided two useful ICC profiles which fixed the situation for me. Just install xcalib
sudo apt-get install xcalib
and load one of these profiles.

[[Category: Ubuntu 8.04]]

Installing Ubuntu 8.04 (Hardy Heron) on a ThinkPad T61

2008-07-24T14:07:39Z

Lunatico: /* '''To enable the Wifi LED with the Atheros cards''' */

== Items that work out of the box ==

'''Intel Video:''' 2D and 3D acceleration works

'''Nvidia Video:''' 2D and 3D acceleration works

'''Wireless:''' Intel cards tested. Atheros cards also works.

'''Wireless WAN:''' Cingular/AT&T card tested.

'''Network Card''' Intel 10/100/1000 tested

'''Wireless switch''' Tested

'''Webcam''' Tested with cheese and skype.

'''Headphones''' Works out of the box

'''Microphone''' Just needs to be activated, see section [[#Audio|below]]

'''Keyboard Shortcuts:''' Most of them work out of the box, some need to be activated, see section [[#Multimedia_Keys|below]]

== Items that need (some) tweaking to obtain full functionality ==

=== Open Source Intel Wifi Driver ===
The following information is important if you are upgrading from a previous version of Ubuntu to 8.04.

Intel has created a new Linux Wifi driver project for Intel Wireless cards, "[[Iwlwifi]]". This driver is Open Source and no longer requires the Intel daemon to run in addition. This project will support the [[:Category:T61 | T61]]'s Wifi [[Intel PRO/Wireless 3945ABG Mini-PCI Express Adapter | Intel 3945ABG network adapter]] and [[Intel PRO/Wireless 4965AGN Mini-PCI Express Adapter| Intel 4965AGN network adapter]].

An automatic migration will occur when upgrading from [[Installing Ubuntu 7.10 (Gutsy Gibbon) on a ThinkPad T61|Ubuntu 7.10]] to Ubuntu 8.04. However, there is a caveat to be aware of:
* The new driver wants to name the interface wlan0 (by default -- you can rename it to anything you want), and requires a different entry in {{path|/etc/udev/rules.d/70-persistent-net.rules}}, which handles the naming of interfaces. Simply edit this file and delete your old entry for the ipw3945 driver, then unload/reload the new driver, or simply reboot. A new entry will automatically be created that is appropriate for the new driver. Here's an example of the lines to delete:
<pre>
# PCI device 0x8086:0x4227 (ipw3945)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:1b:77:a4:0e:2f", NAME="eth1"
</pre>

If you need to perform a manual migration, the Ubuntu Help Community has written some [https://help.ubuntu.com/community/WifiDocs/Driver/iwlwifi_Intel_3945_4965/gutsy documentation] that will make this very easy to do.

=== Compiz and XV Playback on Intel GM965/GL960 ===

With Ubuntu 7.10 (Gutsy Gibbon) you currently have to choose between using Compiz and working video playback using XV. On 8.04 (Hardy Heron) alpha 5 you can play videos using XV under compiz, it works right out of the box using the Live-CD.

=== Suspend with Nv140m ===

** Update as of July 17th 2008 -- Using 8.04.1 with the newest nvidea drivers, I had no problems suspending without any additional configuration. **

Suspend may not work even after editing acpi-support. Enable bluetooth (Fn+F5) may result in a successful suspend. NOTE: that although the wifi led does not change when Fn+F5 is used, the wifi is still toggled by this key.

'''Hal "S3 BIOS" parameter issue!'''

After doing the changes to the /etc/default/acpi-support file (described [http://www.thinkwiki.org/wiki/Installing_Ubuntu_7.10_(Gutsy_Gibbon)_on_a_ThinkPad_T61#How_to_Suspend_with_nVidia_140m.2F570m here]), I for one, managed to have '''stable''' suspend support by creating a new file called: '''/etc/hal/fdi/information/lenovo.fdi''' with the following contents:
<pre>
<?xml version="1.0" encoding="ISO-8859-1"?> 
<deviceinfo version="0.2">
<device>
<match key="system.hardware.vendor" string="LENOVO">
<merge key="power_management.quirk.s3_bios" type="bool">false</merge>
</match>
</device>
</deviceinfo>
</pre>
{{NOTE|The problem (after reading the HAL and pm-utils documentations) is the fact that (as far as I can tell) the T61 Lenovo doesn't allow the S3 BIOS to be called *during* suspend/resume, which HAL seems to do by default (who knows, maybe there are T61s out there that do work with this default)!

This did not seem to be necessary for previous versions of Ubuntu. Also note that I have an NVIDIA card so I have no idea what to do for Intel versions.The change should also be resistant to HAL and pm-utils upgrades.}}

'''Still no suspend with nvs140m? Got Modell 6460?'''

Fix above didn't work for me on a 15.4 wide T61 Modell 6460 with nv140m. Bios is updated to 2.14 but didn't change anything, except the usb bug is fix. Suspend seems to work fine, but resume gives me a black screen (backlight off - no reaction to brightness up) and I can hear 2 beeps. Most of the time I can reboot with ctrl+alt+delete but the screen stays dark until bios.

follow the instructions above but create the new file called: '''/etc/hal/fdi/information/lenovo.fdi''' with the following contents instead:
<pre>
<?xml version="1.0" encoding="ISO-8859-1"?> 
<deviceinfo version="0.2">
<device>
<match key="system.hardware.vendor" string="LENOVO">
<merge key="power_management.quirk.s3_mode" type="bool">true</merge>
<merge key="power_management.quirk.s3_bios" type="bool">false</merge>
<merge key="power_management.quirk.save_pci" type="bool">true</merge>
</match>
</device>
</deviceinfo>
</pre>

Also you want to set the following parameter in

{{path|/etc/default/acpi-support}}
<pre>
SAVE_VIDEO_PCI_STATE=true
</pre>

{{NOTE|This works for me with mode 6460, except for one problem: You may get a white screen in xorg after resume when using compiz. If you don't have a 6460 with nvidia this file may break things for you because it doesn't care about the modell and sets the parameter for any lenovo product}}
{{HELP|Anyone with more knowledge of hal and acpi-support is welcome to clean this up. I also don't know why this setting can be done via hal and in acpi-support.
See below!}}

'''Working on hardy final'''

After trying out all these recipes on my 6457CTO waking up from suspend still did not work. Finally I came across a blog entry which pointed out the right way: [[http://david.goodlad.ca/2008/3/14/suspend-hibernate-on-lenovo-t61 David Goodlad's blog]]. I realized that all the fixes proposing editing the acpi-support file or adding a kernel parameter acpi_sleep=s3_mode must be wrong because since hardy gnome-power-manager gets its information solely from hal. So setting up correct hal information is the right way but the proposed solution (creating a /etc/hal/fdi/information/lenovo.fdi file) did not work for me. Ok, but now step by step:

# Revert ALL the proposed fixes from above. I found out that at least the lenovo.fdi solution is actually breaking the real fix. So for sure delete /etc/hal/fdi/information/lenovo.fdi
# Find out about the excact hal name of your machine: <pre>hal-device |grep 6457</pre> where 6457 is the model number of my t61, replace it with your own. In my case it spits out something like this: system.hardware.product = '6457CTO'. So now I know that hal identifies my machine as 6457CTO.
# <pre>sudo gedit /usr/share/hal/fdi/information/10freedesktop/20-video-quirk-pm-lenovo.fdi</pre> and add a section to the end of the file, just above the </device> tag and replace 6457CTO with your hal device name:
<pre>

<match key="system.hardware.product" string="6457CTO">

<merge key="power_management.quirk.s3_mode" type="bool">true</merge>
<merge key="power_management.quirk.s3_bios" type="bool">false</merge>
<merge key="power_management.quirk.save_pci" type="bool">true</merge>
</match>
</pre>

Now save and reboot. Now you might run into the problem of coming back from resume into a completely white screen where normally should be the password dialog. Entering your password blindly is not nice but at least you can resume.

{{NOTE|Somehow I couldn't make the wildcard matching work as they did in the lenovo.fdi solution, but that might be due to my shortcomings on that syntax. Anyway matching the device by its full name worked for me. Probably somebody who knows more about the matching could make that wildcard thing work to have a more general solution. Because hal also knows the xorg driver name (info.linux.driver) there should be a way to set up the quirks depending on the driver.}}

[[Category: T61]]

=== TrackPoint ===
The [[TrackPoint]] works out of the box, but does not scroll nor does the tap-clicking (press to select) feature work. Therefor see: [[#tap-to-click feature]] To enable using the middle mouse button to scroll, replace the "Configured Mouse" section in {{path|/etc/X11/xorg.conf}} with the following:
<pre>
Section "InputDevice"
Identifier "Trackpoint"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ImPS/2"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "true"
Option "EmulateWheel" "true"
Option "EmulateWheelButton" "2"
EndSection
</pre>

{{NOTE|However, if you need to use external usb mouse, the above configuration is wrong. It will cause odd behavior. Try the following configuration from [http://gentoo-wiki.com/HARDWARE_IBM_Specific_Laptop_Guide#TrackPoint Gentoo Wiki]:}}
<pre>
Section "InputDevice"
Identifier "UltraNav TrackPoint"
Driver "mouse"
Option "Device" "/dev/input/mouse1"
Option "Protocol" "ExplorerPS/2"
Option "Emulate3Buttons" "on"
Option "Emulate3TimeOut" "50"
Option "EmulateWheel" "on"
Option "EmulateWheelTimeOut" "200"
Option "EmulateWheelButton" "2"
Option "YAxisMapping" "4 5"
Option "XAxisMapping" "6 7"
Option "ZAxisMapping" "4 5"
EndSection
</pre>

=== Audio ===

Works great out of the box, just the microphone has to be activated, it is considered a generic capture source and is muted by default.

To unmute the microphone:

*Right Click on the volume icon next to the clock and click on "Open Volume Control"

*Click Edit -> Preferences. A list of devices will be displayed, you should check the following (Do not uncheck any existing items):

Input Source
Capture

*Click Close and there should be two additional tabs "Recording" and "Options". -

*Click Recording and click on the microphone under the Capture slider so that it no longer has a red line through it, and put the slider up as it may be deactivated.

*Click Options and under capture source select internal mic.

To test your mic using Sound Recorder select Capture as the sound source.

This solution has been tested with Sound Recorder and Skype.

To get the volume controls working:

*add the following line to /etc/modprobe.d/alsa-base, then reboot

options snd-hda-intel index=0 model=thinkpad

{{NOTE|The volume controls worked fine for me out of the box on a 6460.}}

=== Multimedia Keys ===

Most Multimedia Keys work out of the box, just the play, forward and stop buttons need to be adjusted, therefore, press alt + F2 and type in gnome-keybinding-properties. Then everything works as followed:

* Fn-PgUp activates/deactivates the thinklight
* Fn-Up will trigger stop on a media player
* Fn-Down will toggle pause and play on a media player
* Fn-Left/Right go to prev/next tracks on a media player
* Fn-F2 properly locks the screen
* Fn-F3 shows remaining battery >>does not work on all machines<<
* Fn-F4 suspends (to ram)
* Fn-F9 ejects cds >>does not work on all machines, I think this is supposed to eject from a "dock"<<
* Fn-F12 hibernates (to disk)
* PrtSc opens the screenshot dialog

To enable the back, forward, and the menu keys you'll need to teach XKB what they are.

* Check the '''XkbLayout''' option (under '''InputDevice''') in your {{path|/etc/X11/xorg.conf}} file to determine which keyboard layout Ubuntu is using (I'll use 'us' for the example).
* Navigate to {{path|/etc/X11/xkb/symbols}} and, as root, open the appropriate layout file (as determined above) in your favorite editor.
{{cmduser|cd /etc/X11/xkb/symbols}}
{{cmduser|sudo gedit us}}
* In the '''xkb_symbols "basic"''' section after the '''name[Group1]= "x";''' (where x is a country name, or similar) line add the following:
key <I63> { [ Menu ] };
key <I69> { [ XF86Forward ] };
key <I6A> { [ XF86Back ] };
* Now log out and back in and all three of the buttons should function.

=== Thinkpad Button ===

Paste the following into /usr/share/hotkey-setup/ibm.hk
setkeycodes e017 148 # thinkpad button
You can also just type this into a terminal, to test it for the time of the current session.

Paste the following into the right file in /usr/share/xmodmap (check your country code)
keycode 159 = XF86Terminal
For immediate availability of the button, reload the file by executing
xmodmap <xmodmap.file>

Then use the "Keyboard Shortcuts" tool under "Preferences".

== Items that don't work (a.k.a.: items that need more intense tweaking to get fixed)==

=== tap-to-click feature ===

For the tap-to-click feature (taping the stick instead of using the left mouse button) i used a configure trackpoint utility: [http://tpctl.sourceforge.net/configure-trackpoint.html] there is a package for ubuntu 7.04 i386, but i compiled it by myself (using amd64):

1.) download the .tar.gz file

2.) unpack it

3.) install libgnomeui-dev

{{cmduser|sudo aptitude install libgnomeui-dev}}

4.) in the folder, do:

{{cmduser|./configure}}

if everything worked fine:

{{cmduser|make}}

then install it:

{{cmduser|sudo make install}}

5.a) Gnome : Open it: System > configure trackpoint, and configure on your needs

5.b) Kde : K-menu > Prefences > configure trackpoint > right-click > edit entry, edit "command" to "kdesu configure-trackpoint"

Save & exit

Open it : K-menu > Prefences > configure trackpoint and configure on your needs

=== Hotswapping ===

{{HELP|We need someone who is able to get hotswaping to work properly, this is not the right was to do this!}}
With the new kernel, bay-drivers changed, so if you remove the ultrabay it will freeze your system! You can hack it with a simple comand, first you have to look where the device is:

{{cmduser|less /sys/class/scsi_device/(x)\:0\:0\:0/device/model}}

for (x) first put in 0, if it tells you DVD or the name of the model you want to hotswap youre right. if not, go on with 1, 2 or 3...

then, once you are sure (I deactivated my harddisk like that) you put in:

{{cmduser|echo 1 {{!}} sudo tee /sys/class/scsi_device/(x)\:0\:0\:0/device/delete}}

Now you should be able to remove the device.

{{WARN|Do not use it for harddisks, be sure you unmounted it before! This is just a bad hack, if anyone knows how to get it right --> publish!}}

If Ubuntu does not reactivate the device after putting it in again, do:

{{cmduser|echo 0 0 0 {{!}} sudo tee /sys/class/scsi_host/host1/scan}}

=== Wireless activity LED ===

The LED is not implemented at least in the IWL4965 driver. For the Atheros wifi cards look at the solution below.

A patch posted in this [http://bughost.org/bugzilla/show_bug.cgi?id=1209 thread] works for me on R61 with IWL4965 card.

{{HELP|A howto is needed showing the process of implementing the patch in Hardy Heron. If anyone knows how to do this, please create a quick howto and either put it here or link to it from this page. Please and thank you.}}

As an alternative, you can install a backported IWL4965 driver that ''may'' fix the LED problem on your system.

To active WiFi LED,

sudo apt-get install linux-backports-modules-hardy

{{NOTE|On some machines, (at least one running IWL3945 & IWL4965) applying the above turns on the LED permanently. It should flicker as data is being transmitted. Also, with the above modification, after turning off wireless and then turning it back on (via the switch on the front of the machine) wireless is not reactivated, so not very helpful}}

You can download a compatible [http://wireless.kernel.org/download/compat-wireless-2.6/compat-wireless-2.6.tar.bz2 driver] which supports WiFi led flicking and build it with modifying the {{path|config.mk}} by adding {{bootparm|CONFIG_IWL3945_LEDS|y}} and {{bootparm|CONFIG_IWLWIFI_LEDS|y}} these two options. For Ubuntu/Debian users, build-essential, linux-source-2.6.24 and linux-headers-generic packages are required.

{{HELP|I added the above lines to the config.mk file and it would not make or make install correctly. I received an error 2 at the end of the make. If you have had success, where did you put the items in the config.mk file for it to make and make install correctly? Thanks in advance.}}

==== To enable the Wifi LED with the Atheros cards ====

First check if this solution works on your computer. Open a terminal and run this commands:

sysctl dev.wifi0.ledpin=1
sysctl dev.wifi0.softled=3

Now connect to a wireless network and the LED should start working. If so and you want to make the changes permanent then:

1) Create a file ~/wifiLED and copy/paste the following into it:

#!/bin/bash
#
# Commands to enable the wireless LED
sysctl dev.wifi0.ledpin=1
sysctl dev.wifi0.softled=3

2) sudo cp ~/wifiLED /etc/init.d

3) sudo chmod 755 /etc/init.d/wifiLED

4) sudo update-rc.d wifiLED defaults 90

After you reboot your wireless led should be working.

=== Hidden SSID ===
It has been reported that users wanting to access Hidden SSIDs have to enter the SSID and password manually in Network Manager to connect. Even after the SSID is saved in Network Manager, it will not reconnect automatically. The user has to connect manually by entering the information as previously described.
It appears that updating the driver by following the instructions [http://linuxwireless.org/en/users/Download here] resolves this issue.

=== Hard Disk Parking ===
Getting hard disk parking to work:

tp_smapi patch is not needed in [http://packages.ubuntu.com/search?keywords=linux-image-2.6.24-18&searchon=names&suite=hardy&section=all linux-image-2.6.24-18]

1. Patch your kernel with the 'protect' [http://www.thinkwiki.org/wiki/HDAPS#Kernel_patch patch].

2. Installing the hdapsd daemon which does the actual parking.

{{cmduser|sudo apt-get install hdapsd hdaps-utils}}

== some other tweaks ==

=== screenblank with {{key|Fn}} + {{key|F3}} ===

Its ok, and might be usefull to get the estimated batterytime when pressing {{key|Fn}}+{{key|F3}}, as it should be. But i dont need that, i find the earlier command for {{key|F3}}, to blank the screen, more useful to save batterylife better.

For that, you must edit {{path|/etc/acpi/thinkpad-lockbattery.sh}} and replace LENOVO by IBM, and IBM by LENOVO :). Do not forget to copy the file before you change it!

=== Enable normal User to Limit CPU Speed ===
To let user set the CPU limit you need to open a Terminal an type there
sudo dpkg-reconfigure gnome-applets
answer the question with yes

=== Fix bluish WSXGA+ displays ===
Many T61 owners complain about a very bluish color temperature: My T61 WSXGA+ was also way too blue. I came across a thread at the notebook review forum http://forum.notebookreview.com/showthread.php?t=174408 which provided two useful ICC profiles which fixed the situation for me. Just install xcalib
sudo apt-get install xcalib
and load one of these profiles.

[[Category: Ubuntu 8.04]]

Installing Ubuntu 8.04 (Hardy Heron) on a ThinkPad T61

2008-07-24T14:07:02Z

Lunatico: /* Wireless activity LED */

== Items that work out of the box ==

'''Intel Video:''' 2D and 3D acceleration works

'''Nvidia Video:''' 2D and 3D acceleration works

'''Wireless:''' Intel cards tested. Atheros cards also works.

'''Wireless WAN:''' Cingular/AT&T card tested.

'''Network Card''' Intel 10/100/1000 tested

'''Wireless switch''' Tested

'''Webcam''' Tested with cheese and skype.

'''Headphones''' Works out of the box

'''Microphone''' Just needs to be activated, see section [[#Audio|below]]

'''Keyboard Shortcuts:''' Most of them work out of the box, some need to be activated, see section [[#Multimedia_Keys|below]]

== Items that need (some) tweaking to obtain full functionality ==

=== Open Source Intel Wifi Driver ===
The following information is important if you are upgrading from a previous version of Ubuntu to 8.04.

Intel has created a new Linux Wifi driver project for Intel Wireless cards, "[[Iwlwifi]]". This driver is Open Source and no longer requires the Intel daemon to run in addition. This project will support the [[:Category:T61 | T61]]'s Wifi [[Intel PRO/Wireless 3945ABG Mini-PCI Express Adapter | Intel 3945ABG network adapter]] and [[Intel PRO/Wireless 4965AGN Mini-PCI Express Adapter| Intel 4965AGN network adapter]].

An automatic migration will occur when upgrading from [[Installing Ubuntu 7.10 (Gutsy Gibbon) on a ThinkPad T61|Ubuntu 7.10]] to Ubuntu 8.04. However, there is a caveat to be aware of:
* The new driver wants to name the interface wlan0 (by default -- you can rename it to anything you want), and requires a different entry in {{path|/etc/udev/rules.d/70-persistent-net.rules}}, which handles the naming of interfaces. Simply edit this file and delete your old entry for the ipw3945 driver, then unload/reload the new driver, or simply reboot. A new entry will automatically be created that is appropriate for the new driver. Here's an example of the lines to delete:
<pre>
# PCI device 0x8086:0x4227 (ipw3945)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:1b:77:a4:0e:2f", NAME="eth1"
</pre>

If you need to perform a manual migration, the Ubuntu Help Community has written some [https://help.ubuntu.com/community/WifiDocs/Driver/iwlwifi_Intel_3945_4965/gutsy documentation] that will make this very easy to do.

=== Compiz and XV Playback on Intel GM965/GL960 ===

With Ubuntu 7.10 (Gutsy Gibbon) you currently have to choose between using Compiz and working video playback using XV. On 8.04 (Hardy Heron) alpha 5 you can play videos using XV under compiz, it works right out of the box using the Live-CD.

=== Suspend with Nv140m ===

** Update as of July 17th 2008 -- Using 8.04.1 with the newest nvidea drivers, I had no problems suspending without any additional configuration. **

Suspend may not work even after editing acpi-support. Enable bluetooth (Fn+F5) may result in a successful suspend. NOTE: that although the wifi led does not change when Fn+F5 is used, the wifi is still toggled by this key.

'''Hal "S3 BIOS" parameter issue!'''

After doing the changes to the /etc/default/acpi-support file (described [http://www.thinkwiki.org/wiki/Installing_Ubuntu_7.10_(Gutsy_Gibbon)_on_a_ThinkPad_T61#How_to_Suspend_with_nVidia_140m.2F570m here]), I for one, managed to have '''stable''' suspend support by creating a new file called: '''/etc/hal/fdi/information/lenovo.fdi''' with the following contents:
<pre>
<?xml version="1.0" encoding="ISO-8859-1"?> 
<deviceinfo version="0.2">
<device>
<match key="system.hardware.vendor" string="LENOVO">
<merge key="power_management.quirk.s3_bios" type="bool">false</merge>
</match>
</device>
</deviceinfo>
</pre>
{{NOTE|The problem (after reading the HAL and pm-utils documentations) is the fact that (as far as I can tell) the T61 Lenovo doesn't allow the S3 BIOS to be called *during* suspend/resume, which HAL seems to do by default (who knows, maybe there are T61s out there that do work with this default)!

This did not seem to be necessary for previous versions of Ubuntu. Also note that I have an NVIDIA card so I have no idea what to do for Intel versions.The change should also be resistant to HAL and pm-utils upgrades.}}

'''Still no suspend with nvs140m? Got Modell 6460?'''

Fix above didn't work for me on a 15.4 wide T61 Modell 6460 with nv140m. Bios is updated to 2.14 but didn't change anything, except the usb bug is fix. Suspend seems to work fine, but resume gives me a black screen (backlight off - no reaction to brightness up) and I can hear 2 beeps. Most of the time I can reboot with ctrl+alt+delete but the screen stays dark until bios.

follow the instructions above but create the new file called: '''/etc/hal/fdi/information/lenovo.fdi''' with the following contents instead:
<pre>
<?xml version="1.0" encoding="ISO-8859-1"?> 
<deviceinfo version="0.2">
<device>
<match key="system.hardware.vendor" string="LENOVO">
<merge key="power_management.quirk.s3_mode" type="bool">true</merge>
<merge key="power_management.quirk.s3_bios" type="bool">false</merge>
<merge key="power_management.quirk.save_pci" type="bool">true</merge>
</match>
</device>
</deviceinfo>
</pre>

Also you want to set the following parameter in

{{path|/etc/default/acpi-support}}
<pre>
SAVE_VIDEO_PCI_STATE=true
</pre>

{{NOTE|This works for me with mode 6460, except for one problem: You may get a white screen in xorg after resume when using compiz. If you don't have a 6460 with nvidia this file may break things for you because it doesn't care about the modell and sets the parameter for any lenovo product}}
{{HELP|Anyone with more knowledge of hal and acpi-support is welcome to clean this up. I also don't know why this setting can be done via hal and in acpi-support.
See below!}}

'''Working on hardy final'''

After trying out all these recipes on my 6457CTO waking up from suspend still did not work. Finally I came across a blog entry which pointed out the right way: [[http://david.goodlad.ca/2008/3/14/suspend-hibernate-on-lenovo-t61 David Goodlad's blog]]. I realized that all the fixes proposing editing the acpi-support file or adding a kernel parameter acpi_sleep=s3_mode must be wrong because since hardy gnome-power-manager gets its information solely from hal. So setting up correct hal information is the right way but the proposed solution (creating a /etc/hal/fdi/information/lenovo.fdi file) did not work for me. Ok, but now step by step:

# Revert ALL the proposed fixes from above. I found out that at least the lenovo.fdi solution is actually breaking the real fix. So for sure delete /etc/hal/fdi/information/lenovo.fdi
# Find out about the excact hal name of your machine: <pre>hal-device |grep 6457</pre> where 6457 is the model number of my t61, replace it with your own. In my case it spits out something like this: system.hardware.product = '6457CTO'. So now I know that hal identifies my machine as 6457CTO.
# <pre>sudo gedit /usr/share/hal/fdi/information/10freedesktop/20-video-quirk-pm-lenovo.fdi</pre> and add a section to the end of the file, just above the </device> tag and replace 6457CTO with your hal device name:
<pre>

<match key="system.hardware.product" string="6457CTO">

<merge key="power_management.quirk.s3_mode" type="bool">true</merge>
<merge key="power_management.quirk.s3_bios" type="bool">false</merge>
<merge key="power_management.quirk.save_pci" type="bool">true</merge>
</match>
</pre>

Now save and reboot. Now you might run into the problem of coming back from resume into a completely white screen where normally should be the password dialog. Entering your password blindly is not nice but at least you can resume.

{{NOTE|Somehow I couldn't make the wildcard matching work as they did in the lenovo.fdi solution, but that might be due to my shortcomings on that syntax. Anyway matching the device by its full name worked for me. Probably somebody who knows more about the matching could make that wildcard thing work to have a more general solution. Because hal also knows the xorg driver name (info.linux.driver) there should be a way to set up the quirks depending on the driver.}}

[[Category: T61]]

=== TrackPoint ===
The [[TrackPoint]] works out of the box, but does not scroll nor does the tap-clicking (press to select) feature work. Therefor see: [[#tap-to-click feature]] To enable using the middle mouse button to scroll, replace the "Configured Mouse" section in {{path|/etc/X11/xorg.conf}} with the following:
<pre>
Section "InputDevice"
Identifier "Trackpoint"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ImPS/2"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "true"
Option "EmulateWheel" "true"
Option "EmulateWheelButton" "2"
EndSection
</pre>

{{NOTE|However, if you need to use external usb mouse, the above configuration is wrong. It will cause odd behavior. Try the following configuration from [http://gentoo-wiki.com/HARDWARE_IBM_Specific_Laptop_Guide#TrackPoint Gentoo Wiki]:}}
<pre>
Section "InputDevice"
Identifier "UltraNav TrackPoint"
Driver "mouse"
Option "Device" "/dev/input/mouse1"
Option "Protocol" "ExplorerPS/2"
Option "Emulate3Buttons" "on"
Option "Emulate3TimeOut" "50"
Option "EmulateWheel" "on"
Option "EmulateWheelTimeOut" "200"
Option "EmulateWheelButton" "2"
Option "YAxisMapping" "4 5"
Option "XAxisMapping" "6 7"
Option "ZAxisMapping" "4 5"
EndSection
</pre>

=== Audio ===

Works great out of the box, just the microphone has to be activated, it is considered a generic capture source and is muted by default.

To unmute the microphone:

*Right Click on the volume icon next to the clock and click on "Open Volume Control"

*Click Edit -> Preferences. A list of devices will be displayed, you should check the following (Do not uncheck any existing items):

Input Source
Capture

*Click Close and there should be two additional tabs "Recording" and "Options". -

*Click Recording and click on the microphone under the Capture slider so that it no longer has a red line through it, and put the slider up as it may be deactivated.

*Click Options and under capture source select internal mic.

To test your mic using Sound Recorder select Capture as the sound source.

This solution has been tested with Sound Recorder and Skype.

To get the volume controls working:

*add the following line to /etc/modprobe.d/alsa-base, then reboot

options snd-hda-intel index=0 model=thinkpad

{{NOTE|The volume controls worked fine for me out of the box on a 6460.}}

=== Multimedia Keys ===

Most Multimedia Keys work out of the box, just the play, forward and stop buttons need to be adjusted, therefore, press alt + F2 and type in gnome-keybinding-properties. Then everything works as followed:

* Fn-PgUp activates/deactivates the thinklight
* Fn-Up will trigger stop on a media player
* Fn-Down will toggle pause and play on a media player
* Fn-Left/Right go to prev/next tracks on a media player
* Fn-F2 properly locks the screen
* Fn-F3 shows remaining battery >>does not work on all machines<<
* Fn-F4 suspends (to ram)
* Fn-F9 ejects cds >>does not work on all machines, I think this is supposed to eject from a "dock"<<
* Fn-F12 hibernates (to disk)
* PrtSc opens the screenshot dialog

To enable the back, forward, and the menu keys you'll need to teach XKB what they are.

* Check the '''XkbLayout''' option (under '''InputDevice''') in your {{path|/etc/X11/xorg.conf}} file to determine which keyboard layout Ubuntu is using (I'll use 'us' for the example).
* Navigate to {{path|/etc/X11/xkb/symbols}} and, as root, open the appropriate layout file (as determined above) in your favorite editor.
{{cmduser|cd /etc/X11/xkb/symbols}}
{{cmduser|sudo gedit us}}
* In the '''xkb_symbols "basic"''' section after the '''name[Group1]= "x";''' (where x is a country name, or similar) line add the following:
key <I63> { [ Menu ] };
key <I69> { [ XF86Forward ] };
key <I6A> { [ XF86Back ] };
* Now log out and back in and all three of the buttons should function.

=== Thinkpad Button ===

Paste the following into /usr/share/hotkey-setup/ibm.hk
setkeycodes e017 148 # thinkpad button
You can also just type this into a terminal, to test it for the time of the current session.

Paste the following into the right file in /usr/share/xmodmap (check your country code)
keycode 159 = XF86Terminal
For immediate availability of the button, reload the file by executing
xmodmap <xmodmap.file>

Then use the "Keyboard Shortcuts" tool under "Preferences".

== Items that don't work (a.k.a.: items that need more intense tweaking to get fixed)==

=== tap-to-click feature ===

For the tap-to-click feature (taping the stick instead of using the left mouse button) i used a configure trackpoint utility: [http://tpctl.sourceforge.net/configure-trackpoint.html] there is a package for ubuntu 7.04 i386, but i compiled it by myself (using amd64):

1.) download the .tar.gz file

2.) unpack it

3.) install libgnomeui-dev

{{cmduser|sudo aptitude install libgnomeui-dev}}

4.) in the folder, do:

{{cmduser|./configure}}

if everything worked fine:

{{cmduser|make}}

then install it:

{{cmduser|sudo make install}}

5.a) Gnome : Open it: System > configure trackpoint, and configure on your needs

5.b) Kde : K-menu > Prefences > configure trackpoint > right-click > edit entry, edit "command" to "kdesu configure-trackpoint"

Save & exit

Open it : K-menu > Prefences > configure trackpoint and configure on your needs

=== Hotswapping ===

{{HELP|We need someone who is able to get hotswaping to work properly, this is not the right was to do this!}}
With the new kernel, bay-drivers changed, so if you remove the ultrabay it will freeze your system! You can hack it with a simple comand, first you have to look where the device is:

{{cmduser|less /sys/class/scsi_device/(x)\:0\:0\:0/device/model}}

for (x) first put in 0, if it tells you DVD or the name of the model you want to hotswap youre right. if not, go on with 1, 2 or 3...

then, once you are sure (I deactivated my harddisk like that) you put in:

{{cmduser|echo 1 {{!}} sudo tee /sys/class/scsi_device/(x)\:0\:0\:0/device/delete}}

Now you should be able to remove the device.

{{WARN|Do not use it for harddisks, be sure you unmounted it before! This is just a bad hack, if anyone knows how to get it right --> publish!}}

If Ubuntu does not reactivate the device after putting it in again, do:

{{cmduser|echo 0 0 0 {{!}} sudo tee /sys/class/scsi_host/host1/scan}}

=== Wireless activity LED ===

The LED is not implemented at least in the IWL4965 driver. For the Atheros wifi cards look at the solution below.

A patch posted in this [http://bughost.org/bugzilla/show_bug.cgi?id=1209 thread] works for me on R61 with IWL4965 card.

{{HELP|A howto is needed showing the process of implementing the patch in Hardy Heron. If anyone knows how to do this, please create a quick howto and either put it here or link to it from this page. Please and thank you.}}

As an alternative, you can install a backported IWL4965 driver that ''may'' fix the LED problem on your system.

To active WiFi LED,

sudo apt-get install linux-backports-modules-hardy

{{NOTE|On some machines, (at least one running IWL3945 & IWL4965) applying the above turns on the LED permanently. It should flicker as data is being transmitted. Also, with the above modification, after turning off wireless and then turning it back on (via the switch on the front of the machine) wireless is not reactivated, so not very helpful}}

You can download a compatible [http://wireless.kernel.org/download/compat-wireless-2.6/compat-wireless-2.6.tar.bz2 driver] which supports WiFi led flicking and build it with modifying the {{path|config.mk}} by adding {{bootparm|CONFIG_IWL3945_LEDS|y}} and {{bootparm|CONFIG_IWLWIFI_LEDS|y}} these two options. For Ubuntu/Debian users, build-essential, linux-source-2.6.24 and linux-headers-generic packages are required.

{{HELP|I added the above lines to the config.mk file and it would not make or make install correctly. I received an error 2 at the end of the make. If you have had success, where did you put the items in the config.mk file for it to make and make install correctly? Thanks in advance.}}

==== '''To enable the Wifi LED with the Atheros cards''' ====

First check if this solution works on your computer. Open a terminal and run this commands:

sysctl dev.wifi0.ledpin=1
sysctl dev.wifi0.softled=3

Now connect to a wireless network and the LED should start working. If so and you want to make the changes permanent then:

1) Create a file ~/wifiLED and copy/paste the following into it:

#!/bin/bash
#
# Commands to enable the wireless LED
sysctl dev.wifi0.ledpin=1
sysctl dev.wifi0.softled=3

2) sudo cp ~/wifiLED /etc/init.d

3) sudo chmod 755 /etc/init.d/wifiLED

4) sudo update-rc.d wifiLED defaults 90

After you reboot your wireless led should be working.

=== Hidden SSID ===
It has been reported that users wanting to access Hidden SSIDs have to enter the SSID and password manually in Network Manager to connect. Even after the SSID is saved in Network Manager, it will not reconnect automatically. The user has to connect manually by entering the information as previously described.
It appears that updating the driver by following the instructions [http://linuxwireless.org/en/users/Download here] resolves this issue.

=== Hard Disk Parking ===
Getting hard disk parking to work:

tp_smapi patch is not needed in [http://packages.ubuntu.com/search?keywords=linux-image-2.6.24-18&searchon=names&suite=hardy&section=all linux-image-2.6.24-18]

1. Patch your kernel with the 'protect' [http://www.thinkwiki.org/wiki/HDAPS#Kernel_patch patch].

2. Installing the hdapsd daemon which does the actual parking.

{{cmduser|sudo apt-get install hdapsd hdaps-utils}}

== some other tweaks ==

=== screenblank with {{key|Fn}} + {{key|F3}} ===

Its ok, and might be usefull to get the estimated batterytime when pressing {{key|Fn}}+{{key|F3}}, as it should be. But i dont need that, i find the earlier command for {{key|F3}}, to blank the screen, more useful to save batterylife better.

For that, you must edit {{path|/etc/acpi/thinkpad-lockbattery.sh}} and replace LENOVO by IBM, and IBM by LENOVO :). Do not forget to copy the file before you change it!

=== Enable normal User to Limit CPU Speed ===
To let user set the CPU limit you need to open a Terminal an type there
sudo dpkg-reconfigure gnome-applets
answer the question with yes

=== Fix bluish WSXGA+ displays ===
Many T61 owners complain about a very bluish color temperature: My T61 WSXGA+ was also way too blue. I came across a thread at the notebook review forum http://forum.notebookreview.com/showthread.php?t=174408 which provided two useful ICC profiles which fixed the situation for me. Just install xcalib
sudo apt-get install xcalib
and load one of these profiles.

[[Category: Ubuntu 8.04]]

Installing Ubuntu 8.04 (Hardy Heron) on a ThinkPad T61

2008-07-24T14:03:15Z

Lunatico: /* Wireless activity LED */

== Items that work out of the box ==

'''Intel Video:''' 2D and 3D acceleration works

'''Nvidia Video:''' 2D and 3D acceleration works

'''Wireless:''' Intel cards tested. Atheros cards also works.

'''Wireless WAN:''' Cingular/AT&T card tested.

'''Network Card''' Intel 10/100/1000 tested

'''Wireless switch''' Tested

'''Webcam''' Tested with cheese and skype.

'''Headphones''' Works out of the box

'''Microphone''' Just needs to be activated, see section [[#Audio|below]]

'''Keyboard Shortcuts:''' Most of them work out of the box, some need to be activated, see section [[#Multimedia_Keys|below]]

== Items that need (some) tweaking to obtain full functionality ==

=== Open Source Intel Wifi Driver ===
The following information is important if you are upgrading from a previous version of Ubuntu to 8.04.

Intel has created a new Linux Wifi driver project for Intel Wireless cards, "[[Iwlwifi]]". This driver is Open Source and no longer requires the Intel daemon to run in addition. This project will support the [[:Category:T61 | T61]]'s Wifi [[Intel PRO/Wireless 3945ABG Mini-PCI Express Adapter | Intel 3945ABG network adapter]] and [[Intel PRO/Wireless 4965AGN Mini-PCI Express Adapter| Intel 4965AGN network adapter]].

An automatic migration will occur when upgrading from [[Installing Ubuntu 7.10 (Gutsy Gibbon) on a ThinkPad T61|Ubuntu 7.10]] to Ubuntu 8.04. However, there is a caveat to be aware of:
* The new driver wants to name the interface wlan0 (by default -- you can rename it to anything you want), and requires a different entry in {{path|/etc/udev/rules.d/70-persistent-net.rules}}, which handles the naming of interfaces. Simply edit this file and delete your old entry for the ipw3945 driver, then unload/reload the new driver, or simply reboot. A new entry will automatically be created that is appropriate for the new driver. Here's an example of the lines to delete:
<pre>
# PCI device 0x8086:0x4227 (ipw3945)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:1b:77:a4:0e:2f", NAME="eth1"
</pre>

If you need to perform a manual migration, the Ubuntu Help Community has written some [https://help.ubuntu.com/community/WifiDocs/Driver/iwlwifi_Intel_3945_4965/gutsy documentation] that will make this very easy to do.

=== Compiz and XV Playback on Intel GM965/GL960 ===

With Ubuntu 7.10 (Gutsy Gibbon) you currently have to choose between using Compiz and working video playback using XV. On 8.04 (Hardy Heron) alpha 5 you can play videos using XV under compiz, it works right out of the box using the Live-CD.

=== Suspend with Nv140m ===

** Update as of July 17th 2008 -- Using 8.04.1 with the newest nvidea drivers, I had no problems suspending without any additional configuration. **

Suspend may not work even after editing acpi-support. Enable bluetooth (Fn+F5) may result in a successful suspend. NOTE: that although the wifi led does not change when Fn+F5 is used, the wifi is still toggled by this key.

'''Hal "S3 BIOS" parameter issue!'''

After doing the changes to the /etc/default/acpi-support file (described [http://www.thinkwiki.org/wiki/Installing_Ubuntu_7.10_(Gutsy_Gibbon)_on_a_ThinkPad_T61#How_to_Suspend_with_nVidia_140m.2F570m here]), I for one, managed to have '''stable''' suspend support by creating a new file called: '''/etc/hal/fdi/information/lenovo.fdi''' with the following contents:
<pre>
<?xml version="1.0" encoding="ISO-8859-1"?> 
<deviceinfo version="0.2">
<device>
<match key="system.hardware.vendor" string="LENOVO">
<merge key="power_management.quirk.s3_bios" type="bool">false</merge>
</match>
</device>
</deviceinfo>
</pre>
{{NOTE|The problem (after reading the HAL and pm-utils documentations) is the fact that (as far as I can tell) the T61 Lenovo doesn't allow the S3 BIOS to be called *during* suspend/resume, which HAL seems to do by default (who knows, maybe there are T61s out there that do work with this default)!

This did not seem to be necessary for previous versions of Ubuntu. Also note that I have an NVIDIA card so I have no idea what to do for Intel versions.The change should also be resistant to HAL and pm-utils upgrades.}}

'''Still no suspend with nvs140m? Got Modell 6460?'''

Fix above didn't work for me on a 15.4 wide T61 Modell 6460 with nv140m. Bios is updated to 2.14 but didn't change anything, except the usb bug is fix. Suspend seems to work fine, but resume gives me a black screen (backlight off - no reaction to brightness up) and I can hear 2 beeps. Most of the time I can reboot with ctrl+alt+delete but the screen stays dark until bios.

follow the instructions above but create the new file called: '''/etc/hal/fdi/information/lenovo.fdi''' with the following contents instead:
<pre>
<?xml version="1.0" encoding="ISO-8859-1"?> 
<deviceinfo version="0.2">
<device>
<match key="system.hardware.vendor" string="LENOVO">
<merge key="power_management.quirk.s3_mode" type="bool">true</merge>
<merge key="power_management.quirk.s3_bios" type="bool">false</merge>
<merge key="power_management.quirk.save_pci" type="bool">true</merge>
</match>
</device>
</deviceinfo>
</pre>

Also you want to set the following parameter in

{{path|/etc/default/acpi-support}}
<pre>
SAVE_VIDEO_PCI_STATE=true
</pre>

{{NOTE|This works for me with mode 6460, except for one problem: You may get a white screen in xorg after resume when using compiz. If you don't have a 6460 with nvidia this file may break things for you because it doesn't care about the modell and sets the parameter for any lenovo product}}
{{HELP|Anyone with more knowledge of hal and acpi-support is welcome to clean this up. I also don't know why this setting can be done via hal and in acpi-support.
See below!}}

'''Working on hardy final'''

After trying out all these recipes on my 6457CTO waking up from suspend still did not work. Finally I came across a blog entry which pointed out the right way: [[http://david.goodlad.ca/2008/3/14/suspend-hibernate-on-lenovo-t61 David Goodlad's blog]]. I realized that all the fixes proposing editing the acpi-support file or adding a kernel parameter acpi_sleep=s3_mode must be wrong because since hardy gnome-power-manager gets its information solely from hal. So setting up correct hal information is the right way but the proposed solution (creating a /etc/hal/fdi/information/lenovo.fdi file) did not work for me. Ok, but now step by step:

# Revert ALL the proposed fixes from above. I found out that at least the lenovo.fdi solution is actually breaking the real fix. So for sure delete /etc/hal/fdi/information/lenovo.fdi
# Find out about the excact hal name of your machine: <pre>hal-device |grep 6457</pre> where 6457 is the model number of my t61, replace it with your own. In my case it spits out something like this: system.hardware.product = '6457CTO'. So now I know that hal identifies my machine as 6457CTO.
# <pre>sudo gedit /usr/share/hal/fdi/information/10freedesktop/20-video-quirk-pm-lenovo.fdi</pre> and add a section to the end of the file, just above the </device> tag and replace 6457CTO with your hal device name:
<pre>

<match key="system.hardware.product" string="6457CTO">

<merge key="power_management.quirk.s3_mode" type="bool">true</merge>
<merge key="power_management.quirk.s3_bios" type="bool">false</merge>
<merge key="power_management.quirk.save_pci" type="bool">true</merge>
</match>
</pre>

Now save and reboot. Now you might run into the problem of coming back from resume into a completely white screen where normally should be the password dialog. Entering your password blindly is not nice but at least you can resume.

{{NOTE|Somehow I couldn't make the wildcard matching work as they did in the lenovo.fdi solution, but that might be due to my shortcomings on that syntax. Anyway matching the device by its full name worked for me. Probably somebody who knows more about the matching could make that wildcard thing work to have a more general solution. Because hal also knows the xorg driver name (info.linux.driver) there should be a way to set up the quirks depending on the driver.}}

[[Category: T61]]

=== TrackPoint ===
The [[TrackPoint]] works out of the box, but does not scroll nor does the tap-clicking (press to select) feature work. Therefor see: [[#tap-to-click feature]] To enable using the middle mouse button to scroll, replace the "Configured Mouse" section in {{path|/etc/X11/xorg.conf}} with the following:
<pre>
Section "InputDevice"
Identifier "Trackpoint"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ImPS/2"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "true"
Option "EmulateWheel" "true"
Option "EmulateWheelButton" "2"
EndSection
</pre>

{{NOTE|However, if you need to use external usb mouse, the above configuration is wrong. It will cause odd behavior. Try the following configuration from [http://gentoo-wiki.com/HARDWARE_IBM_Specific_Laptop_Guide#TrackPoint Gentoo Wiki]:}}
<pre>
Section "InputDevice"
Identifier "UltraNav TrackPoint"
Driver "mouse"
Option "Device" "/dev/input/mouse1"
Option "Protocol" "ExplorerPS/2"
Option "Emulate3Buttons" "on"
Option "Emulate3TimeOut" "50"
Option "EmulateWheel" "on"
Option "EmulateWheelTimeOut" "200"
Option "EmulateWheelButton" "2"
Option "YAxisMapping" "4 5"
Option "XAxisMapping" "6 7"
Option "ZAxisMapping" "4 5"
EndSection
</pre>

=== Audio ===

Works great out of the box, just the microphone has to be activated, it is considered a generic capture source and is muted by default.

To unmute the microphone:

*Right Click on the volume icon next to the clock and click on "Open Volume Control"

*Click Edit -> Preferences. A list of devices will be displayed, you should check the following (Do not uncheck any existing items):

Input Source
Capture

*Click Close and there should be two additional tabs "Recording" and "Options". -

*Click Recording and click on the microphone under the Capture slider so that it no longer has a red line through it, and put the slider up as it may be deactivated.

*Click Options and under capture source select internal mic.

To test your mic using Sound Recorder select Capture as the sound source.

This solution has been tested with Sound Recorder and Skype.

To get the volume controls working:

*add the following line to /etc/modprobe.d/alsa-base, then reboot

options snd-hda-intel index=0 model=thinkpad

{{NOTE|The volume controls worked fine for me out of the box on a 6460.}}

=== Multimedia Keys ===

Most Multimedia Keys work out of the box, just the play, forward and stop buttons need to be adjusted, therefore, press alt + F2 and type in gnome-keybinding-properties. Then everything works as followed:

* Fn-PgUp activates/deactivates the thinklight
* Fn-Up will trigger stop on a media player
* Fn-Down will toggle pause and play on a media player
* Fn-Left/Right go to prev/next tracks on a media player
* Fn-F2 properly locks the screen
* Fn-F3 shows remaining battery >>does not work on all machines<<
* Fn-F4 suspends (to ram)
* Fn-F9 ejects cds >>does not work on all machines, I think this is supposed to eject from a "dock"<<
* Fn-F12 hibernates (to disk)
* PrtSc opens the screenshot dialog

To enable the back, forward, and the menu keys you'll need to teach XKB what they are.

* Check the '''XkbLayout''' option (under '''InputDevice''') in your {{path|/etc/X11/xorg.conf}} file to determine which keyboard layout Ubuntu is using (I'll use 'us' for the example).
* Navigate to {{path|/etc/X11/xkb/symbols}} and, as root, open the appropriate layout file (as determined above) in your favorite editor.
{{cmduser|cd /etc/X11/xkb/symbols}}
{{cmduser|sudo gedit us}}
* In the '''xkb_symbols "basic"''' section after the '''name[Group1]= "x";''' (where x is a country name, or similar) line add the following:
key <I63> { [ Menu ] };
key <I69> { [ XF86Forward ] };
key <I6A> { [ XF86Back ] };
* Now log out and back in and all three of the buttons should function.

=== Thinkpad Button ===

Paste the following into /usr/share/hotkey-setup/ibm.hk
setkeycodes e017 148 # thinkpad button
You can also just type this into a terminal, to test it for the time of the current session.

Paste the following into the right file in /usr/share/xmodmap (check your country code)
keycode 159 = XF86Terminal
For immediate availability of the button, reload the file by executing
xmodmap <xmodmap.file>

Then use the "Keyboard Shortcuts" tool under "Preferences".

== Items that don't work (a.k.a.: items that need more intense tweaking to get fixed)==

=== tap-to-click feature ===

For the tap-to-click feature (taping the stick instead of using the left mouse button) i used a configure trackpoint utility: [http://tpctl.sourceforge.net/configure-trackpoint.html] there is a package for ubuntu 7.04 i386, but i compiled it by myself (using amd64):

1.) download the .tar.gz file

2.) unpack it

3.) install libgnomeui-dev

{{cmduser|sudo aptitude install libgnomeui-dev}}

4.) in the folder, do:

{{cmduser|./configure}}

if everything worked fine:

{{cmduser|make}}

then install it:

{{cmduser|sudo make install}}

5.a) Gnome : Open it: System > configure trackpoint, and configure on your needs

5.b) Kde : K-menu > Prefences > configure trackpoint > right-click > edit entry, edit "command" to "kdesu configure-trackpoint"

Save & exit

Open it : K-menu > Prefences > configure trackpoint and configure on your needs

=== Hotswapping ===

{{HELP|We need someone who is able to get hotswaping to work properly, this is not the right was to do this!}}
With the new kernel, bay-drivers changed, so if you remove the ultrabay it will freeze your system! You can hack it with a simple comand, first you have to look where the device is:

{{cmduser|less /sys/class/scsi_device/(x)\:0\:0\:0/device/model}}

for (x) first put in 0, if it tells you DVD or the name of the model you want to hotswap youre right. if not, go on with 1, 2 or 3...

then, once you are sure (I deactivated my harddisk like that) you put in:

{{cmduser|echo 1 {{!}} sudo tee /sys/class/scsi_device/(x)\:0\:0\:0/device/delete}}

Now you should be able to remove the device.

{{WARN|Do not use it for harddisks, be sure you unmounted it before! This is just a bad hack, if anyone knows how to get it right --> publish!}}

If Ubuntu does not reactivate the device after putting it in again, do:

{{cmduser|echo 0 0 0 {{!}} sudo tee /sys/class/scsi_host/host1/scan}}

=== Wireless activity LED ===

The LED is not implemented at least in the IWL4965 driver. For the Atheros wifi cards look at the solution below.

A patch posted in this [http://bughost.org/bugzilla/show_bug.cgi?id=1209 thread] works for me on R61 with IWL4965 card.

{{HELP|A howto is needed showing the process of implementing the patch in Hardy Heron. If anyone knows how to do this, please create a quick howto and either put it here or link to it from this page. Please and thank you.}}

As an alternative, you can install a backported IWL4965 driver that ''may'' fix the LED problem on your system.

To active WiFi LED,

sudo apt-get install linux-backports-modules-hardy

{{NOTE|On some machines, (at least one running IWL3945 & IWL4965) applying the above turns on the LED permanently. It should flicker as data is being transmitted. Also, with the above modification, after turning off wireless and then turning it back on (via the switch on the front of the machine) wireless is not reactivated, so not very helpful}}

You can download a compatible [http://wireless.kernel.org/download/compat-wireless-2.6/compat-wireless-2.6.tar.bz2 driver] which supports WiFi led flicking and build it with modifying the {{path|config.mk}} by adding {{bootparm|CONFIG_IWL3945_LEDS|y}} and {{bootparm|CONFIG_IWLWIFI_LEDS|y}} these two options. For Ubuntu/Debian users, build-essential, linux-source-2.6.24 and linux-headers-generic packages are required.

{{HELP|I added the above lines to the config.mk file and it would not make or make install correctly. I received an error 2 at the end of the make. If you have had success, where did you put the items in the config.mk file for it to make and make install correctly? Thanks in advance.}}

'''To enable the Wifi LED with the Atheros cards'''

First check if this solution works on your computer. Open a terminal and run this commands:

sysctl dev.wifi0.ledpin=1
sysctl dev.wifi0.softled=3

Now connect to a wireless network and the LED should start working. If so and you want to make the changes permanent then:

1) Create a file ~/wifiLED and copy/paste the following into it:

#!/bin/bash
#
# Commands to enable the wireless LED
sysctl dev.wifi0.ledpin=1
sysctl dev.wifi0.softled=3

2) sudo cp ~/wifiLED /etc/init.d

3) sudo chmod 755 /etc/init.d/wifiLED

4) sudo update-rc.d wifiLED defaults 90

After you reboot your wireless led should be working.

=== Hidden SSID ===
It has been reported that users wanting to access Hidden SSIDs have to enter the SSID and password manually in Network Manager to connect. Even after the SSID is saved in Network Manager, it will not reconnect automatically. The user has to connect manually by entering the information as previously described.
It appears that updating the driver by following the instructions [http://linuxwireless.org/en/users/Download here] resolves this issue.

=== Hard Disk Parking ===
Getting hard disk parking to work:

tp_smapi patch is not needed in [http://packages.ubuntu.com/search?keywords=linux-image-2.6.24-18&searchon=names&suite=hardy&section=all linux-image-2.6.24-18]

1. Patch your kernel with the 'protect' [http://www.thinkwiki.org/wiki/HDAPS#Kernel_patch patch].

2. Installing the hdapsd daemon which does the actual parking.

{{cmduser|sudo apt-get install hdapsd hdaps-utils}}

== some other tweaks ==

=== screenblank with {{key|Fn}} + {{key|F3}} ===

Its ok, and might be usefull to get the estimated batterytime when pressing {{key|Fn}}+{{key|F3}}, as it should be. But i dont need that, i find the earlier command for {{key|F3}}, to blank the screen, more useful to save batterylife better.

For that, you must edit {{path|/etc/acpi/thinkpad-lockbattery.sh}} and replace LENOVO by IBM, and IBM by LENOVO :). Do not forget to copy the file before you change it!

=== Enable normal User to Limit CPU Speed ===
To let user set the CPU limit you need to open a Terminal an type there
sudo dpkg-reconfigure gnome-applets
answer the question with yes

=== Fix bluish WSXGA+ displays ===
Many T61 owners complain about a very bluish color temperature: My T61 WSXGA+ was also way too blue. I came across a thread at the notebook review forum http://forum.notebookreview.com/showthread.php?t=174408 which provided two useful ICC profiles which fixed the situation for me. Just install xcalib
sudo apt-get install xcalib
and load one of these profiles.

[[Category: Ubuntu 8.04]]

Installing Ubuntu 8.04 (Hardy Heron) on a ThinkPad T61

2008-07-24T14:02:38Z

Lunatico: /* Wireless activity LED */

== Items that work out of the box ==

'''Intel Video:''' 2D and 3D acceleration works

'''Nvidia Video:''' 2D and 3D acceleration works

'''Wireless:''' Intel cards tested. Atheros cards also works.

'''Wireless WAN:''' Cingular/AT&T card tested.

'''Network Card''' Intel 10/100/1000 tested

'''Wireless switch''' Tested

'''Webcam''' Tested with cheese and skype.

'''Headphones''' Works out of the box

'''Microphone''' Just needs to be activated, see section [[#Audio|below]]

'''Keyboard Shortcuts:''' Most of them work out of the box, some need to be activated, see section [[#Multimedia_Keys|below]]

== Items that need (some) tweaking to obtain full functionality ==

=== Open Source Intel Wifi Driver ===
The following information is important if you are upgrading from a previous version of Ubuntu to 8.04.

Intel has created a new Linux Wifi driver project for Intel Wireless cards, "[[Iwlwifi]]". This driver is Open Source and no longer requires the Intel daemon to run in addition. This project will support the [[:Category:T61 | T61]]'s Wifi [[Intel PRO/Wireless 3945ABG Mini-PCI Express Adapter | Intel 3945ABG network adapter]] and [[Intel PRO/Wireless 4965AGN Mini-PCI Express Adapter| Intel 4965AGN network adapter]].

An automatic migration will occur when upgrading from [[Installing Ubuntu 7.10 (Gutsy Gibbon) on a ThinkPad T61|Ubuntu 7.10]] to Ubuntu 8.04. However, there is a caveat to be aware of:
* The new driver wants to name the interface wlan0 (by default -- you can rename it to anything you want), and requires a different entry in {{path|/etc/udev/rules.d/70-persistent-net.rules}}, which handles the naming of interfaces. Simply edit this file and delete your old entry for the ipw3945 driver, then unload/reload the new driver, or simply reboot. A new entry will automatically be created that is appropriate for the new driver. Here's an example of the lines to delete:
<pre>
# PCI device 0x8086:0x4227 (ipw3945)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:1b:77:a4:0e:2f", NAME="eth1"
</pre>

If you need to perform a manual migration, the Ubuntu Help Community has written some [https://help.ubuntu.com/community/WifiDocs/Driver/iwlwifi_Intel_3945_4965/gutsy documentation] that will make this very easy to do.

=== Compiz and XV Playback on Intel GM965/GL960 ===

With Ubuntu 7.10 (Gutsy Gibbon) you currently have to choose between using Compiz and working video playback using XV. On 8.04 (Hardy Heron) alpha 5 you can play videos using XV under compiz, it works right out of the box using the Live-CD.

=== Suspend with Nv140m ===

** Update as of July 17th 2008 -- Using 8.04.1 with the newest nvidea drivers, I had no problems suspending without any additional configuration. **

Suspend may not work even after editing acpi-support. Enable bluetooth (Fn+F5) may result in a successful suspend. NOTE: that although the wifi led does not change when Fn+F5 is used, the wifi is still toggled by this key.

'''Hal "S3 BIOS" parameter issue!'''

After doing the changes to the /etc/default/acpi-support file (described [http://www.thinkwiki.org/wiki/Installing_Ubuntu_7.10_(Gutsy_Gibbon)_on_a_ThinkPad_T61#How_to_Suspend_with_nVidia_140m.2F570m here]), I for one, managed to have '''stable''' suspend support by creating a new file called: '''/etc/hal/fdi/information/lenovo.fdi''' with the following contents:
<pre>
<?xml version="1.0" encoding="ISO-8859-1"?> 
<deviceinfo version="0.2">
<device>
<match key="system.hardware.vendor" string="LENOVO">
<merge key="power_management.quirk.s3_bios" type="bool">false</merge>
</match>
</device>
</deviceinfo>
</pre>
{{NOTE|The problem (after reading the HAL and pm-utils documentations) is the fact that (as far as I can tell) the T61 Lenovo doesn't allow the S3 BIOS to be called *during* suspend/resume, which HAL seems to do by default (who knows, maybe there are T61s out there that do work with this default)!

This did not seem to be necessary for previous versions of Ubuntu. Also note that I have an NVIDIA card so I have no idea what to do for Intel versions.The change should also be resistant to HAL and pm-utils upgrades.}}

'''Still no suspend with nvs140m? Got Modell 6460?'''

Fix above didn't work for me on a 15.4 wide T61 Modell 6460 with nv140m. Bios is updated to 2.14 but didn't change anything, except the usb bug is fix. Suspend seems to work fine, but resume gives me a black screen (backlight off - no reaction to brightness up) and I can hear 2 beeps. Most of the time I can reboot with ctrl+alt+delete but the screen stays dark until bios.

follow the instructions above but create the new file called: '''/etc/hal/fdi/information/lenovo.fdi''' with the following contents instead:
<pre>
<?xml version="1.0" encoding="ISO-8859-1"?> 
<deviceinfo version="0.2">
<device>
<match key="system.hardware.vendor" string="LENOVO">
<merge key="power_management.quirk.s3_mode" type="bool">true</merge>
<merge key="power_management.quirk.s3_bios" type="bool">false</merge>
<merge key="power_management.quirk.save_pci" type="bool">true</merge>
</match>
</device>
</deviceinfo>
</pre>

Also you want to set the following parameter in

{{path|/etc/default/acpi-support}}
<pre>
SAVE_VIDEO_PCI_STATE=true
</pre>

{{NOTE|This works for me with mode 6460, except for one problem: You may get a white screen in xorg after resume when using compiz. If you don't have a 6460 with nvidia this file may break things for you because it doesn't care about the modell and sets the parameter for any lenovo product}}
{{HELP|Anyone with more knowledge of hal and acpi-support is welcome to clean this up. I also don't know why this setting can be done via hal and in acpi-support.
See below!}}

'''Working on hardy final'''

After trying out all these recipes on my 6457CTO waking up from suspend still did not work. Finally I came across a blog entry which pointed out the right way: [[http://david.goodlad.ca/2008/3/14/suspend-hibernate-on-lenovo-t61 David Goodlad's blog]]. I realized that all the fixes proposing editing the acpi-support file or adding a kernel parameter acpi_sleep=s3_mode must be wrong because since hardy gnome-power-manager gets its information solely from hal. So setting up correct hal information is the right way but the proposed solution (creating a /etc/hal/fdi/information/lenovo.fdi file) did not work for me. Ok, but now step by step:

# Revert ALL the proposed fixes from above. I found out that at least the lenovo.fdi solution is actually breaking the real fix. So for sure delete /etc/hal/fdi/information/lenovo.fdi
# Find out about the excact hal name of your machine: <pre>hal-device |grep 6457</pre> where 6457 is the model number of my t61, replace it with your own. In my case it spits out something like this: system.hardware.product = '6457CTO'. So now I know that hal identifies my machine as 6457CTO.
# <pre>sudo gedit /usr/share/hal/fdi/information/10freedesktop/20-video-quirk-pm-lenovo.fdi</pre> and add a section to the end of the file, just above the </device> tag and replace 6457CTO with your hal device name:
<pre>

<match key="system.hardware.product" string="6457CTO">

<merge key="power_management.quirk.s3_mode" type="bool">true</merge>
<merge key="power_management.quirk.s3_bios" type="bool">false</merge>
<merge key="power_management.quirk.save_pci" type="bool">true</merge>
</match>
</pre>

Now save and reboot. Now you might run into the problem of coming back from resume into a completely white screen where normally should be the password dialog. Entering your password blindly is not nice but at least you can resume.

{{NOTE|Somehow I couldn't make the wildcard matching work as they did in the lenovo.fdi solution, but that might be due to my shortcomings on that syntax. Anyway matching the device by its full name worked for me. Probably somebody who knows more about the matching could make that wildcard thing work to have a more general solution. Because hal also knows the xorg driver name (info.linux.driver) there should be a way to set up the quirks depending on the driver.}}

[[Category: T61]]

=== TrackPoint ===
The [[TrackPoint]] works out of the box, but does not scroll nor does the tap-clicking (press to select) feature work. Therefor see: [[#tap-to-click feature]] To enable using the middle mouse button to scroll, replace the "Configured Mouse" section in {{path|/etc/X11/xorg.conf}} with the following:
<pre>
Section "InputDevice"
Identifier "Trackpoint"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ImPS/2"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "true"
Option "EmulateWheel" "true"
Option "EmulateWheelButton" "2"
EndSection
</pre>

{{NOTE|However, if you need to use external usb mouse, the above configuration is wrong. It will cause odd behavior. Try the following configuration from [http://gentoo-wiki.com/HARDWARE_IBM_Specific_Laptop_Guide#TrackPoint Gentoo Wiki]:}}
<pre>
Section "InputDevice"
Identifier "UltraNav TrackPoint"
Driver "mouse"
Option "Device" "/dev/input/mouse1"
Option "Protocol" "ExplorerPS/2"
Option "Emulate3Buttons" "on"
Option "Emulate3TimeOut" "50"
Option "EmulateWheel" "on"
Option "EmulateWheelTimeOut" "200"
Option "EmulateWheelButton" "2"
Option "YAxisMapping" "4 5"
Option "XAxisMapping" "6 7"
Option "ZAxisMapping" "4 5"
EndSection
</pre>

=== Audio ===

Works great out of the box, just the microphone has to be activated, it is considered a generic capture source and is muted by default.

To unmute the microphone:

*Right Click on the volume icon next to the clock and click on "Open Volume Control"

*Click Edit -> Preferences. A list of devices will be displayed, you should check the following (Do not uncheck any existing items):

Input Source
Capture

*Click Close and there should be two additional tabs "Recording" and "Options". -

*Click Recording and click on the microphone under the Capture slider so that it no longer has a red line through it, and put the slider up as it may be deactivated.

*Click Options and under capture source select internal mic.

To test your mic using Sound Recorder select Capture as the sound source.

This solution has been tested with Sound Recorder and Skype.

To get the volume controls working:

*add the following line to /etc/modprobe.d/alsa-base, then reboot

options snd-hda-intel index=0 model=thinkpad

{{NOTE|The volume controls worked fine for me out of the box on a 6460.}}

=== Multimedia Keys ===

Most Multimedia Keys work out of the box, just the play, forward and stop buttons need to be adjusted, therefore, press alt + F2 and type in gnome-keybinding-properties. Then everything works as followed:

* Fn-PgUp activates/deactivates the thinklight
* Fn-Up will trigger stop on a media player
* Fn-Down will toggle pause and play on a media player
* Fn-Left/Right go to prev/next tracks on a media player
* Fn-F2 properly locks the screen
* Fn-F3 shows remaining battery >>does not work on all machines<<
* Fn-F4 suspends (to ram)
* Fn-F9 ejects cds >>does not work on all machines, I think this is supposed to eject from a "dock"<<
* Fn-F12 hibernates (to disk)
* PrtSc opens the screenshot dialog

To enable the back, forward, and the menu keys you'll need to teach XKB what they are.

* Check the '''XkbLayout''' option (under '''InputDevice''') in your {{path|/etc/X11/xorg.conf}} file to determine which keyboard layout Ubuntu is using (I'll use 'us' for the example).
* Navigate to {{path|/etc/X11/xkb/symbols}} and, as root, open the appropriate layout file (as determined above) in your favorite editor.
{{cmduser|cd /etc/X11/xkb/symbols}}
{{cmduser|sudo gedit us}}
* In the '''xkb_symbols "basic"''' section after the '''name[Group1]= "x";''' (where x is a country name, or similar) line add the following:
key <I63> { [ Menu ] };
key <I69> { [ XF86Forward ] };
key <I6A> { [ XF86Back ] };
* Now log out and back in and all three of the buttons should function.

=== Thinkpad Button ===

Paste the following into /usr/share/hotkey-setup/ibm.hk
setkeycodes e017 148 # thinkpad button
You can also just type this into a terminal, to test it for the time of the current session.

Paste the following into the right file in /usr/share/xmodmap (check your country code)
keycode 159 = XF86Terminal
For immediate availability of the button, reload the file by executing
xmodmap <xmodmap.file>

Then use the "Keyboard Shortcuts" tool under "Preferences".

== Items that don't work (a.k.a.: items that need more intense tweaking to get fixed)==

=== tap-to-click feature ===

For the tap-to-click feature (taping the stick instead of using the left mouse button) i used a configure trackpoint utility: [http://tpctl.sourceforge.net/configure-trackpoint.html] there is a package for ubuntu 7.04 i386, but i compiled it by myself (using amd64):

1.) download the .tar.gz file

2.) unpack it

3.) install libgnomeui-dev

{{cmduser|sudo aptitude install libgnomeui-dev}}

4.) in the folder, do:

{{cmduser|./configure}}

if everything worked fine:

{{cmduser|make}}

then install it:

{{cmduser|sudo make install}}

5.a) Gnome : Open it: System > configure trackpoint, and configure on your needs

5.b) Kde : K-menu > Prefences > configure trackpoint > right-click > edit entry, edit "command" to "kdesu configure-trackpoint"

Save & exit

Open it : K-menu > Prefences > configure trackpoint and configure on your needs

=== Hotswapping ===

{{HELP|We need someone who is able to get hotswaping to work properly, this is not the right was to do this!}}
With the new kernel, bay-drivers changed, so if you remove the ultrabay it will freeze your system! You can hack it with a simple comand, first you have to look where the device is:

{{cmduser|less /sys/class/scsi_device/(x)\:0\:0\:0/device/model}}

for (x) first put in 0, if it tells you DVD or the name of the model you want to hotswap youre right. if not, go on with 1, 2 or 3...

then, once you are sure (I deactivated my harddisk like that) you put in:

{{cmduser|echo 1 {{!}} sudo tee /sys/class/scsi_device/(x)\:0\:0\:0/device/delete}}

Now you should be able to remove the device.

{{WARN|Do not use it for harddisks, be sure you unmounted it before! This is just a bad hack, if anyone knows how to get it right --> publish!}}

If Ubuntu does not reactivate the device after putting it in again, do:

{{cmduser|echo 0 0 0 {{!}} sudo tee /sys/class/scsi_host/host1/scan}}

=== Wireless activity LED ===

The LED is not implemented at least in the IWL4965 driver. For the Atheros wifi cards look at the solution below.

A patch posted in this [http://bughost.org/bugzilla/show_bug.cgi?id=1209 thread] works for me on R61 with IWL4965 card.

{{HELP|A howto is needed showing the process of implementing the patch in Hardy Heron. If anyone knows how to do this, please create a quick howto and either put it here or link to it from this page. Please and thank you.}}

As an alternative, you can install a backported IWL4965 driver that ''may'' fix the LED problem on your system.

To active WiFi LED,

sudo apt-get install linux-backports-modules-hardy

{{NOTE|On some machines, (at least one running IWL3945 & IWL4965) applying the above turns on the LED permanently. It should flicker as data is being transmitted. Also, with the above modification, after turning off wireless and then turning it back on (via the switch on the front of the machine) wireless is not reactivated, so not very helpful}}

You can download a compatible [http://wireless.kernel.org/download/compat-wireless-2.6/compat-wireless-2.6.tar.bz2 driver] which supports WiFi led flicking and build it with modifying the {{path|config.mk}} by adding {{bootparm|CONFIG_IWL3945_LEDS|y}} and {{bootparm|CONFIG_IWLWIFI_LEDS|y}} these two options. For Ubuntu/Debian users, build-essential, linux-source-2.6.24 and linux-headers-generic packages are required.

{{HELP|I added the above lines to the config.mk file and it would not make or make install correctly. I received an error 2 at the end of the make. If you have had success, where did you put the items in the config.mk file for it to make and make install correctly? Thanks in advance.}}

'''To enable the Wifi LED with the Atheros cards'''

First check is this solution will work on your computer. Open a terminal and run this commands:

sysctl dev.wifi0.ledpin=1
sysctl dev.wifi0.softled=3

Now connect to a wireless network and the LED should start working. If so and you want to make the changes permanent then:

1) Create a file ~/wifiLED and copy/paste the following into it:

#!/bin/bash
#
# Commands to enable the wireless LED
sysctl dev.wifi0.ledpin=1
sysctl dev.wifi0.softled=3

2) sudo cp ~/wifiLED /etc/init.d

3) sudo chmod 755 /etc/init.d/wifiLED

4) sudo update-rc.d wifiLED defaults 90

After you reboot your wireless led should be working.

=== Hidden SSID ===
It has been reported that users wanting to access Hidden SSIDs have to enter the SSID and password manually in Network Manager to connect. Even after the SSID is saved in Network Manager, it will not reconnect automatically. The user has to connect manually by entering the information as previously described.
It appears that updating the driver by following the instructions [http://linuxwireless.org/en/users/Download here] resolves this issue.

=== Hard Disk Parking ===
Getting hard disk parking to work:

tp_smapi patch is not needed in [http://packages.ubuntu.com/search?keywords=linux-image-2.6.24-18&searchon=names&suite=hardy&section=all linux-image-2.6.24-18]

1. Patch your kernel with the 'protect' [http://www.thinkwiki.org/wiki/HDAPS#Kernel_patch patch].

2. Installing the hdapsd daemon which does the actual parking.

{{cmduser|sudo apt-get install hdapsd hdaps-utils}}

== some other tweaks ==

=== screenblank with {{key|Fn}} + {{key|F3}} ===

Its ok, and might be usefull to get the estimated batterytime when pressing {{key|Fn}}+{{key|F3}}, as it should be. But i dont need that, i find the earlier command for {{key|F3}}, to blank the screen, more useful to save batterylife better.

For that, you must edit {{path|/etc/acpi/thinkpad-lockbattery.sh}} and replace LENOVO by IBM, and IBM by LENOVO :). Do not forget to copy the file before you change it!

=== Enable normal User to Limit CPU Speed ===
To let user set the CPU limit you need to open a Terminal an type there
sudo dpkg-reconfigure gnome-applets
answer the question with yes

=== Fix bluish WSXGA+ displays ===
Many T61 owners complain about a very bluish color temperature: My T61 WSXGA+ was also way too blue. I came across a thread at the notebook review forum http://forum.notebookreview.com/showthread.php?t=174408 which provided two useful ICC profiles which fixed the situation for me. Just install xcalib
sudo apt-get install xcalib
and load one of these profiles.

[[Category: Ubuntu 8.04]]

Installing Ubuntu 8.04 (Hardy Heron) on a ThinkPad T61

2008-07-24T12:39:02Z

Lunatico: /* Wireless activity LED */

== Items that work out of the box ==

'''Intel Video:''' 2D and 3D acceleration works

'''Nvidia Video:''' 2D and 3D acceleration works

'''Wireless:''' Intel cards tested. Atheros cards also works.

'''Wireless WAN:''' Cingular/AT&T card tested.

'''Network Card''' Intel 10/100/1000 tested

'''Wireless switch''' Tested

'''Webcam''' Tested with cheese and skype.

'''Headphones''' Works out of the box

'''Microphone''' Just needs to be activated, see section [[#Audio|below]]

'''Keyboard Shortcuts:''' Most of them work out of the box, some need to be activated, see section [[#Multimedia_Keys|below]]

== Items that need (some) tweaking to obtain full functionality ==

=== Open Source Intel Wifi Driver ===
The following information is important if you are upgrading from a previous version of Ubuntu to 8.04.

Intel has created a new Linux Wifi driver project for Intel Wireless cards, "[[Iwlwifi]]". This driver is Open Source and no longer requires the Intel daemon to run in addition. This project will support the [[:Category:T61 | T61]]'s Wifi [[Intel PRO/Wireless 3945ABG Mini-PCI Express Adapter | Intel 3945ABG network adapter]] and [[Intel PRO/Wireless 4965AGN Mini-PCI Express Adapter| Intel 4965AGN network adapter]].

An automatic migration will occur when upgrading from [[Installing Ubuntu 7.10 (Gutsy Gibbon) on a ThinkPad T61|Ubuntu 7.10]] to Ubuntu 8.04. However, there is a caveat to be aware of:
* The new driver wants to name the interface wlan0 (by default -- you can rename it to anything you want), and requires a different entry in {{path|/etc/udev/rules.d/70-persistent-net.rules}}, which handles the naming of interfaces. Simply edit this file and delete your old entry for the ipw3945 driver, then unload/reload the new driver, or simply reboot. A new entry will automatically be created that is appropriate for the new driver. Here's an example of the lines to delete:
<pre>
# PCI device 0x8086:0x4227 (ipw3945)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:1b:77:a4:0e:2f", NAME="eth1"
</pre>

If you need to perform a manual migration, the Ubuntu Help Community has written some [https://help.ubuntu.com/community/WifiDocs/Driver/iwlwifi_Intel_3945_4965/gutsy documentation] that will make this very easy to do.

=== Compiz and XV Playback on Intel GM965/GL960 ===

With Ubuntu 7.10 (Gutsy Gibbon) you currently have to choose between using Compiz and working video playback using XV. On 8.04 (Hardy Heron) alpha 5 you can play videos using XV under compiz, it works right out of the box using the Live-CD.

=== Suspend with Nv140m ===

** Update as of July 17th 2008 -- Using 8.04.1 with the newest nvidea drivers, I had no problems suspending without any additional configuration. **

Suspend may not work even after editing acpi-support. Enable bluetooth (Fn+F5) may result in a successful suspend. NOTE: that although the wifi led does not change when Fn+F5 is used, the wifi is still toggled by this key.

'''Hal "S3 BIOS" parameter issue!'''

After doing the changes to the /etc/default/acpi-support file (described [http://www.thinkwiki.org/wiki/Installing_Ubuntu_7.10_(Gutsy_Gibbon)_on_a_ThinkPad_T61#How_to_Suspend_with_nVidia_140m.2F570m here]), I for one, managed to have '''stable''' suspend support by creating a new file called: '''/etc/hal/fdi/information/lenovo.fdi''' with the following contents:
<pre>
<?xml version="1.0" encoding="ISO-8859-1"?> 
<deviceinfo version="0.2">
<device>
<match key="system.hardware.vendor" string="LENOVO">
<merge key="power_management.quirk.s3_bios" type="bool">false</merge>
</match>
</device>
</deviceinfo>
</pre>
{{NOTE|The problem (after reading the HAL and pm-utils documentations) is the fact that (as far as I can tell) the T61 Lenovo doesn't allow the S3 BIOS to be called *during* suspend/resume, which HAL seems to do by default (who knows, maybe there are T61s out there that do work with this default)!

This did not seem to be necessary for previous versions of Ubuntu. Also note that I have an NVIDIA card so I have no idea what to do for Intel versions.The change should also be resistant to HAL and pm-utils upgrades.}}

'''Still no suspend with nvs140m? Got Modell 6460?'''

Fix above didn't work for me on a 15.4 wide T61 Modell 6460 with nv140m. Bios is updated to 2.14 but didn't change anything, except the usb bug is fix. Suspend seems to work fine, but resume gives me a black screen (backlight off - no reaction to brightness up) and I can hear 2 beeps. Most of the time I can reboot with ctrl+alt+delete but the screen stays dark until bios.

follow the instructions above but create the new file called: '''/etc/hal/fdi/information/lenovo.fdi''' with the following contents instead:
<pre>
<?xml version="1.0" encoding="ISO-8859-1"?> 
<deviceinfo version="0.2">
<device>
<match key="system.hardware.vendor" string="LENOVO">
<merge key="power_management.quirk.s3_mode" type="bool">true</merge>
<merge key="power_management.quirk.s3_bios" type="bool">false</merge>
<merge key="power_management.quirk.save_pci" type="bool">true</merge>
</match>
</device>
</deviceinfo>
</pre>

Also you want to set the following parameter in

{{path|/etc/default/acpi-support}}
<pre>
SAVE_VIDEO_PCI_STATE=true
</pre>

{{NOTE|This works for me with mode 6460, except for one problem: You may get a white screen in xorg after resume when using compiz. If you don't have a 6460 with nvidia this file may break things for you because it doesn't care about the modell and sets the parameter for any lenovo product}}
{{HELP|Anyone with more knowledge of hal and acpi-support is welcome to clean this up. I also don't know why this setting can be done via hal and in acpi-support.
See below!}}

'''Working on hardy final'''

After trying out all these recipes on my 6457CTO waking up from suspend still did not work. Finally I came across a blog entry which pointed out the right way: [[http://david.goodlad.ca/2008/3/14/suspend-hibernate-on-lenovo-t61 David Goodlad's blog]]. I realized that all the fixes proposing editing the acpi-support file or adding a kernel parameter acpi_sleep=s3_mode must be wrong because since hardy gnome-power-manager gets its information solely from hal. So setting up correct hal information is the right way but the proposed solution (creating a /etc/hal/fdi/information/lenovo.fdi file) did not work for me. Ok, but now step by step:

# Revert ALL the proposed fixes from above. I found out that at least the lenovo.fdi solution is actually breaking the real fix. So for sure delete /etc/hal/fdi/information/lenovo.fdi
# Find out about the excact hal name of your machine: <pre>hal-device |grep 6457</pre> where 6457 is the model number of my t61, replace it with your own. In my case it spits out something like this: system.hardware.product = '6457CTO'. So now I know that hal identifies my machine as 6457CTO.
# <pre>sudo gedit /usr/share/hal/fdi/information/10freedesktop/20-video-quirk-pm-lenovo.fdi</pre> and add a section to the end of the file, just above the </device> tag and replace 6457CTO with your hal device name:
<pre>

<match key="system.hardware.product" string="6457CTO">

<merge key="power_management.quirk.s3_mode" type="bool">true</merge>
<merge key="power_management.quirk.s3_bios" type="bool">false</merge>
<merge key="power_management.quirk.save_pci" type="bool">true</merge>
</match>
</pre>

Now save and reboot. Now you might run into the problem of coming back from resume into a completely white screen where normally should be the password dialog. Entering your password blindly is not nice but at least you can resume.

{{NOTE|Somehow I couldn't make the wildcard matching work as they did in the lenovo.fdi solution, but that might be due to my shortcomings on that syntax. Anyway matching the device by its full name worked for me. Probably somebody who knows more about the matching could make that wildcard thing work to have a more general solution. Because hal also knows the xorg driver name (info.linux.driver) there should be a way to set up the quirks depending on the driver.}}

[[Category: T61]]

=== TrackPoint ===
The [[TrackPoint]] works out of the box, but does not scroll nor does the tap-clicking (press to select) feature work. Therefor see: [[#tap-to-click feature]] To enable using the middle mouse button to scroll, replace the "Configured Mouse" section in {{path|/etc/X11/xorg.conf}} with the following:
<pre>
Section "InputDevice"
Identifier "Trackpoint"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ImPS/2"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "true"
Option "EmulateWheel" "true"
Option "EmulateWheelButton" "2"
EndSection
</pre>

{{NOTE|However, if you need to use external usb mouse, the above configuration is wrong. It will cause odd behavior. Try the following configuration from [http://gentoo-wiki.com/HARDWARE_IBM_Specific_Laptop_Guide#TrackPoint Gentoo Wiki]:}}
<pre>
Section "InputDevice"
Identifier "UltraNav TrackPoint"
Driver "mouse"
Option "Device" "/dev/input/mouse1"
Option "Protocol" "ExplorerPS/2"
Option "Emulate3Buttons" "on"
Option "Emulate3TimeOut" "50"
Option "EmulateWheel" "on"
Option "EmulateWheelTimeOut" "200"
Option "EmulateWheelButton" "2"
Option "YAxisMapping" "4 5"
Option "XAxisMapping" "6 7"
Option "ZAxisMapping" "4 5"
EndSection
</pre>

=== Audio ===

Works great out of the box, just the microphone has to be activated, it is considered a generic capture source and is muted by default.

To unmute the microphone:

*Right Click on the volume icon next to the clock and click on "Open Volume Control"

*Click Edit -> Preferences. A list of devices will be displayed, you should check the following (Do not uncheck any existing items):

Input Source
Capture

*Click Close and there should be two additional tabs "Recording" and "Options". -

*Click Recording and click on the microphone under the Capture slider so that it no longer has a red line through it, and put the slider up as it may be deactivated.

*Click Options and under capture source select internal mic.

To test your mic using Sound Recorder select Capture as the sound source.

This solution has been tested with Sound Recorder and Skype.

To get the volume controls working:

*add the following line to /etc/modprobe.d/alsa-base, then reboot

options snd-hda-intel index=0 model=thinkpad

{{NOTE|The volume controls worked fine for me out of the box on a 6460.}}

=== Multimedia Keys ===

Most Multimedia Keys work out of the box, just the play, forward and stop buttons need to be adjusted, therefore, press alt + F2 and type in gnome-keybinding-properties. Then everything works as followed:

* Fn-PgUp activates/deactivates the thinklight
* Fn-Up will trigger stop on a media player
* Fn-Down will toggle pause and play on a media player
* Fn-Left/Right go to prev/next tracks on a media player
* Fn-F2 properly locks the screen
* Fn-F3 shows remaining battery >>does not work on all machines<<
* Fn-F4 suspends (to ram)
* Fn-F9 ejects cds >>does not work on all machines, I think this is supposed to eject from a "dock"<<
* Fn-F12 hibernates (to disk)
* PrtSc opens the screenshot dialog

To enable the back, forward, and the menu keys you'll need to teach XKB what they are.

* Check the '''XkbLayout''' option (under '''InputDevice''') in your {{path|/etc/X11/xorg.conf}} file to determine which keyboard layout Ubuntu is using (I'll use 'us' for the example).
* Navigate to {{path|/etc/X11/xkb/symbols}} and, as root, open the appropriate layout file (as determined above) in your favorite editor.
{{cmduser|cd /etc/X11/xkb/symbols}}
{{cmduser|sudo gedit us}}
* In the '''xkb_symbols "basic"''' section after the '''name[Group1]= "x";''' (where x is a country name, or similar) line add the following:
key <I63> { [ Menu ] };
key <I69> { [ XF86Forward ] };
key <I6A> { [ XF86Back ] };
* Now log out and back in and all three of the buttons should function.

=== Thinkpad Button ===

Paste the following into /usr/share/hotkey-setup/ibm.hk
setkeycodes e017 148 # thinkpad button
You can also just type this into a terminal, to test it for the time of the current session.

Paste the following into the right file in /usr/share/xmodmap (check your country code)
keycode 159 = XF86Terminal
For immediate availability of the button, reload the file by executing
xmodmap <xmodmap.file>

Then use the "Keyboard Shortcuts" tool under "Preferences".

== Items that don't work (a.k.a.: items that need more intense tweaking to get fixed)==

=== tap-to-click feature ===

For the tap-to-click feature (taping the stick instead of using the left mouse button) i used a configure trackpoint utility: [http://tpctl.sourceforge.net/configure-trackpoint.html] there is a package for ubuntu 7.04 i386, but i compiled it by myself (using amd64):

1.) download the .tar.gz file

2.) unpack it

3.) install libgnomeui-dev

{{cmduser|sudo aptitude install libgnomeui-dev}}

4.) in the folder, do:

{{cmduser|./configure}}

if everything worked fine:

{{cmduser|make}}

then install it:

{{cmduser|sudo make install}}

5.a) Gnome : Open it: System > configure trackpoint, and configure on your needs

5.b) Kde : K-menu > Prefences > configure trackpoint > right-click > edit entry, edit "command" to "kdesu configure-trackpoint"

Save & exit

Open it : K-menu > Prefences > configure trackpoint and configure on your needs

=== Hotswapping ===

{{HELP|We need someone who is able to get hotswaping to work properly, this is not the right was to do this!}}
With the new kernel, bay-drivers changed, so if you remove the ultrabay it will freeze your system! You can hack it with a simple comand, first you have to look where the device is:

{{cmduser|less /sys/class/scsi_device/(x)\:0\:0\:0/device/model}}

for (x) first put in 0, if it tells you DVD or the name of the model you want to hotswap youre right. if not, go on with 1, 2 or 3...

then, once you are sure (I deactivated my harddisk like that) you put in:

{{cmduser|echo 1 {{!}} sudo tee /sys/class/scsi_device/(x)\:0\:0\:0/device/delete}}

Now you should be able to remove the device.

{{WARN|Do not use it for harddisks, be sure you unmounted it before! This is just a bad hack, if anyone knows how to get it right --> publish!}}

If Ubuntu does not reactivate the device after putting it in again, do:

{{cmduser|echo 0 0 0 {{!}} sudo tee /sys/class/scsi_host/host1/scan}}

=== Wireless activity LED ===

The LED is not implemented at least in the IWL4965 driver. For the Atheros wifi cards look at the solution below.

A patch posted in this [http://bughost.org/bugzilla/show_bug.cgi?id=1209 thread] works for me on R61 with IWL4965 card.

{{HELP|A howto is needed showing the process of implementing the patch in Hardy Heron. If anyone knows how to do this, please create a quick howto and either put it here or link to it from this page. Please and thank you.}}

As an alternative, you can install a backported IWL4965 driver that ''may'' fix the LED problem on your system.

To active WiFi LED,

sudo apt-get install linux-backports-modules-hardy

{{NOTE|On some machines, (at least one running IWL3945 & IWL4965) applying the above turns on the LED permanently. It should flicker as data is being transmitted. Also, with the above modification, after turning off wireless and then turning it back on (via the switch on the front of the machine) wireless is not reactivated, so not very helpful}}

You can download a compatible [http://wireless.kernel.org/download/compat-wireless-2.6/compat-wireless-2.6.tar.bz2 driver] which supports WiFi led flicking and build it with modifying the {{path|config.mk}} by adding {{bootparm|CONFIG_IWL3945_LEDS|y}} and {{bootparm|CONFIG_IWLWIFI_LEDS|y}} these two options. For Ubuntu/Debian users, build-essential, linux-source-2.6.24 and linux-headers-generic packages are required.

{{HELP|I added the above lines to the config.mk file and it would not make or make install correctly. I received an error 2 at the end of the make. If you have had success, where did you put the items in the config.mk file for it to make and make install correctly? Thanks in advance.}}

'''To enable the Wifi LED with the Atheros cards'''

1) Create a file ~/wifiLED and copy/paste the following into it:

#!/bin/bash
#
# Commands to enable the wireless LED
sysctl dev.wifi0.ledpin=1
sysctl dev.wifi0.softled=3

2) sudo cp ~/wifiLED /etc/init.d

3) sudo chmod 755 /etc/init.d/wifiLED

4) sudo update-rc.d wifiLED defaults 90

After you reboot your wireless led should be working.

=== Hidden SSID ===
It has been reported that users wanting to access Hidden SSIDs have to enter the SSID and password manually in Network Manager to connect. Even after the SSID is saved in Network Manager, it will not reconnect automatically. The user has to connect manually by entering the information as previously described.
It appears that updating the driver by following the instructions [http://linuxwireless.org/en/users/Download here] resolves this issue.

=== Hard Disk Parking ===
Getting hard disk parking to work:

tp_smapi patch is not needed in [http://packages.ubuntu.com/search?keywords=linux-image-2.6.24-18&searchon=names&suite=hardy&section=all linux-image-2.6.24-18]

1. Patch your kernel with the 'protect' [http://www.thinkwiki.org/wiki/HDAPS#Kernel_patch patch].

2. Installing the hdapsd daemon which does the actual parking.

{{cmduser|sudo apt-get install hdapsd hdaps-utils}}

== some other tweaks ==

=== screenblank with {{key|Fn}} + {{key|F3}} ===

Its ok, and might be usefull to get the estimated batterytime when pressing {{key|Fn}}+{{key|F3}}, as it should be. But i dont need that, i find the earlier command for {{key|F3}}, to blank the screen, more useful to save batterylife better.

For that, you must edit {{path|/etc/acpi/thinkpad-lockbattery.sh}} and replace LENOVO by IBM, and IBM by LENOVO :). Do not forget to copy the file before you change it!

=== Enable normal User to Limit CPU Speed ===
To let user set the CPU limit you need to open a Terminal an type there
sudo dpkg-reconfigure gnome-applets
answer the question with yes

=== Fix bluish WSXGA+ displays ===
Many T61 owners complain about a very bluish color temperature: My T61 WSXGA+ was also way too blue. I came across a thread at the notebook review forum http://forum.notebookreview.com/showthread.php?t=174408 which provided two useful ICC profiles which fixed the situation for me. Just install xcalib
sudo apt-get install xcalib
and load one of these profiles.

[[Category: Ubuntu 8.04]]

Installing Ubuntu 8.04 (Hardy Heron) on a ThinkPad T61

2008-07-24T12:38:08Z

Lunatico: /* Wireless activity LED */

== Items that work out of the box ==

'''Intel Video:''' 2D and 3D acceleration works

'''Nvidia Video:''' 2D and 3D acceleration works

'''Wireless:''' Intel cards tested. Atheros cards also works.

'''Wireless WAN:''' Cingular/AT&T card tested.

'''Network Card''' Intel 10/100/1000 tested

'''Wireless switch''' Tested

'''Webcam''' Tested with cheese and skype.

'''Headphones''' Works out of the box

'''Microphone''' Just needs to be activated, see section [[#Audio|below]]

'''Keyboard Shortcuts:''' Most of them work out of the box, some need to be activated, see section [[#Multimedia_Keys|below]]

== Items that need (some) tweaking to obtain full functionality ==

=== Open Source Intel Wifi Driver ===
The following information is important if you are upgrading from a previous version of Ubuntu to 8.04.

Intel has created a new Linux Wifi driver project for Intel Wireless cards, "[[Iwlwifi]]". This driver is Open Source and no longer requires the Intel daemon to run in addition. This project will support the [[:Category:T61 | T61]]'s Wifi [[Intel PRO/Wireless 3945ABG Mini-PCI Express Adapter | Intel 3945ABG network adapter]] and [[Intel PRO/Wireless 4965AGN Mini-PCI Express Adapter| Intel 4965AGN network adapter]].

An automatic migration will occur when upgrading from [[Installing Ubuntu 7.10 (Gutsy Gibbon) on a ThinkPad T61|Ubuntu 7.10]] to Ubuntu 8.04. However, there is a caveat to be aware of:
* The new driver wants to name the interface wlan0 (by default -- you can rename it to anything you want), and requires a different entry in {{path|/etc/udev/rules.d/70-persistent-net.rules}}, which handles the naming of interfaces. Simply edit this file and delete your old entry for the ipw3945 driver, then unload/reload the new driver, or simply reboot. A new entry will automatically be created that is appropriate for the new driver. Here's an example of the lines to delete:
<pre>
# PCI device 0x8086:0x4227 (ipw3945)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:1b:77:a4:0e:2f", NAME="eth1"
</pre>

If you need to perform a manual migration, the Ubuntu Help Community has written some [https://help.ubuntu.com/community/WifiDocs/Driver/iwlwifi_Intel_3945_4965/gutsy documentation] that will make this very easy to do.

=== Compiz and XV Playback on Intel GM965/GL960 ===

With Ubuntu 7.10 (Gutsy Gibbon) you currently have to choose between using Compiz and working video playback using XV. On 8.04 (Hardy Heron) alpha 5 you can play videos using XV under compiz, it works right out of the box using the Live-CD.

=== Suspend with Nv140m ===

** Update as of July 17th 2008 -- Using 8.04.1 with the newest nvidea drivers, I had no problems suspending without any additional configuration. **

Suspend may not work even after editing acpi-support. Enable bluetooth (Fn+F5) may result in a successful suspend. NOTE: that although the wifi led does not change when Fn+F5 is used, the wifi is still toggled by this key.

'''Hal "S3 BIOS" parameter issue!'''

After doing the changes to the /etc/default/acpi-support file (described [http://www.thinkwiki.org/wiki/Installing_Ubuntu_7.10_(Gutsy_Gibbon)_on_a_ThinkPad_T61#How_to_Suspend_with_nVidia_140m.2F570m here]), I for one, managed to have '''stable''' suspend support by creating a new file called: '''/etc/hal/fdi/information/lenovo.fdi''' with the following contents:
<pre>
<?xml version="1.0" encoding="ISO-8859-1"?> 
<deviceinfo version="0.2">
<device>
<match key="system.hardware.vendor" string="LENOVO">
<merge key="power_management.quirk.s3_bios" type="bool">false</merge>
</match>
</device>
</deviceinfo>
</pre>
{{NOTE|The problem (after reading the HAL and pm-utils documentations) is the fact that (as far as I can tell) the T61 Lenovo doesn't allow the S3 BIOS to be called *during* suspend/resume, which HAL seems to do by default (who knows, maybe there are T61s out there that do work with this default)!

This did not seem to be necessary for previous versions of Ubuntu. Also note that I have an NVIDIA card so I have no idea what to do for Intel versions.The change should also be resistant to HAL and pm-utils upgrades.}}

'''Still no suspend with nvs140m? Got Modell 6460?'''

Fix above didn't work for me on a 15.4 wide T61 Modell 6460 with nv140m. Bios is updated to 2.14 but didn't change anything, except the usb bug is fix. Suspend seems to work fine, but resume gives me a black screen (backlight off - no reaction to brightness up) and I can hear 2 beeps. Most of the time I can reboot with ctrl+alt+delete but the screen stays dark until bios.

follow the instructions above but create the new file called: '''/etc/hal/fdi/information/lenovo.fdi''' with the following contents instead:
<pre>
<?xml version="1.0" encoding="ISO-8859-1"?> 
<deviceinfo version="0.2">
<device>
<match key="system.hardware.vendor" string="LENOVO">
<merge key="power_management.quirk.s3_mode" type="bool">true</merge>
<merge key="power_management.quirk.s3_bios" type="bool">false</merge>
<merge key="power_management.quirk.save_pci" type="bool">true</merge>
</match>
</device>
</deviceinfo>
</pre>

Also you want to set the following parameter in

{{path|/etc/default/acpi-support}}
<pre>
SAVE_VIDEO_PCI_STATE=true
</pre>

{{NOTE|This works for me with mode 6460, except for one problem: You may get a white screen in xorg after resume when using compiz. If you don't have a 6460 with nvidia this file may break things for you because it doesn't care about the modell and sets the parameter for any lenovo product}}
{{HELP|Anyone with more knowledge of hal and acpi-support is welcome to clean this up. I also don't know why this setting can be done via hal and in acpi-support.
See below!}}

'''Working on hardy final'''

After trying out all these recipes on my 6457CTO waking up from suspend still did not work. Finally I came across a blog entry which pointed out the right way: [[http://david.goodlad.ca/2008/3/14/suspend-hibernate-on-lenovo-t61 David Goodlad's blog]]. I realized that all the fixes proposing editing the acpi-support file or adding a kernel parameter acpi_sleep=s3_mode must be wrong because since hardy gnome-power-manager gets its information solely from hal. So setting up correct hal information is the right way but the proposed solution (creating a /etc/hal/fdi/information/lenovo.fdi file) did not work for me. Ok, but now step by step:

# Revert ALL the proposed fixes from above. I found out that at least the lenovo.fdi solution is actually breaking the real fix. So for sure delete /etc/hal/fdi/information/lenovo.fdi
# Find out about the excact hal name of your machine: <pre>hal-device |grep 6457</pre> where 6457 is the model number of my t61, replace it with your own. In my case it spits out something like this: system.hardware.product = '6457CTO'. So now I know that hal identifies my machine as 6457CTO.
# <pre>sudo gedit /usr/share/hal/fdi/information/10freedesktop/20-video-quirk-pm-lenovo.fdi</pre> and add a section to the end of the file, just above the </device> tag and replace 6457CTO with your hal device name:
<pre>

<match key="system.hardware.product" string="6457CTO">

<merge key="power_management.quirk.s3_mode" type="bool">true</merge>
<merge key="power_management.quirk.s3_bios" type="bool">false</merge>
<merge key="power_management.quirk.save_pci" type="bool">true</merge>
</match>
</pre>

Now save and reboot. Now you might run into the problem of coming back from resume into a completely white screen where normally should be the password dialog. Entering your password blindly is not nice but at least you can resume.

{{NOTE|Somehow I couldn't make the wildcard matching work as they did in the lenovo.fdi solution, but that might be due to my shortcomings on that syntax. Anyway matching the device by its full name worked for me. Probably somebody who knows more about the matching could make that wildcard thing work to have a more general solution. Because hal also knows the xorg driver name (info.linux.driver) there should be a way to set up the quirks depending on the driver.}}

[[Category: T61]]

=== TrackPoint ===
The [[TrackPoint]] works out of the box, but does not scroll nor does the tap-clicking (press to select) feature work. Therefor see: [[#tap-to-click feature]] To enable using the middle mouse button to scroll, replace the "Configured Mouse" section in {{path|/etc/X11/xorg.conf}} with the following:
<pre>
Section "InputDevice"
Identifier "Trackpoint"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ImPS/2"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "true"
Option "EmulateWheel" "true"
Option "EmulateWheelButton" "2"
EndSection
</pre>

{{NOTE|However, if you need to use external usb mouse, the above configuration is wrong. It will cause odd behavior. Try the following configuration from [http://gentoo-wiki.com/HARDWARE_IBM_Specific_Laptop_Guide#TrackPoint Gentoo Wiki]:}}
<pre>
Section "InputDevice"
Identifier "UltraNav TrackPoint"
Driver "mouse"
Option "Device" "/dev/input/mouse1"
Option "Protocol" "ExplorerPS/2"
Option "Emulate3Buttons" "on"
Option "Emulate3TimeOut" "50"
Option "EmulateWheel" "on"
Option "EmulateWheelTimeOut" "200"
Option "EmulateWheelButton" "2"
Option "YAxisMapping" "4 5"
Option "XAxisMapping" "6 7"
Option "ZAxisMapping" "4 5"
EndSection
</pre>

=== Audio ===

Works great out of the box, just the microphone has to be activated, it is considered a generic capture source and is muted by default.

To unmute the microphone:

*Right Click on the volume icon next to the clock and click on "Open Volume Control"

*Click Edit -> Preferences. A list of devices will be displayed, you should check the following (Do not uncheck any existing items):

Input Source
Capture

*Click Close and there should be two additional tabs "Recording" and "Options". -

*Click Recording and click on the microphone under the Capture slider so that it no longer has a red line through it, and put the slider up as it may be deactivated.

*Click Options and under capture source select internal mic.

To test your mic using Sound Recorder select Capture as the sound source.

This solution has been tested with Sound Recorder and Skype.

To get the volume controls working:

*add the following line to /etc/modprobe.d/alsa-base, then reboot

options snd-hda-intel index=0 model=thinkpad

{{NOTE|The volume controls worked fine for me out of the box on a 6460.}}

=== Multimedia Keys ===

Most Multimedia Keys work out of the box, just the play, forward and stop buttons need to be adjusted, therefore, press alt + F2 and type in gnome-keybinding-properties. Then everything works as followed:

* Fn-PgUp activates/deactivates the thinklight
* Fn-Up will trigger stop on a media player
* Fn-Down will toggle pause and play on a media player
* Fn-Left/Right go to prev/next tracks on a media player
* Fn-F2 properly locks the screen
* Fn-F3 shows remaining battery >>does not work on all machines<<
* Fn-F4 suspends (to ram)
* Fn-F9 ejects cds >>does not work on all machines, I think this is supposed to eject from a "dock"<<
* Fn-F12 hibernates (to disk)
* PrtSc opens the screenshot dialog

To enable the back, forward, and the menu keys you'll need to teach XKB what they are.

* Check the '''XkbLayout''' option (under '''InputDevice''') in your {{path|/etc/X11/xorg.conf}} file to determine which keyboard layout Ubuntu is using (I'll use 'us' for the example).
* Navigate to {{path|/etc/X11/xkb/symbols}} and, as root, open the appropriate layout file (as determined above) in your favorite editor.
{{cmduser|cd /etc/X11/xkb/symbols}}
{{cmduser|sudo gedit us}}
* In the '''xkb_symbols "basic"''' section after the '''name[Group1]= "x";''' (where x is a country name, or similar) line add the following:
key <I63> { [ Menu ] };
key <I69> { [ XF86Forward ] };
key <I6A> { [ XF86Back ] };
* Now log out and back in and all three of the buttons should function.

=== Thinkpad Button ===

Paste the following into /usr/share/hotkey-setup/ibm.hk
setkeycodes e017 148 # thinkpad button
You can also just type this into a terminal, to test it for the time of the current session.

Paste the following into the right file in /usr/share/xmodmap (check your country code)
keycode 159 = XF86Terminal
For immediate availability of the button, reload the file by executing
xmodmap <xmodmap.file>

Then use the "Keyboard Shortcuts" tool under "Preferences".

== Items that don't work (a.k.a.: items that need more intense tweaking to get fixed)==

=== tap-to-click feature ===

For the tap-to-click feature (taping the stick instead of using the left mouse button) i used a configure trackpoint utility: [http://tpctl.sourceforge.net/configure-trackpoint.html] there is a package for ubuntu 7.04 i386, but i compiled it by myself (using amd64):

1.) download the .tar.gz file

2.) unpack it

3.) install libgnomeui-dev

{{cmduser|sudo aptitude install libgnomeui-dev}}

4.) in the folder, do:

{{cmduser|./configure}}

if everything worked fine:

{{cmduser|make}}

then install it:

{{cmduser|sudo make install}}

5.a) Gnome : Open it: System > configure trackpoint, and configure on your needs

5.b) Kde : K-menu > Prefences > configure trackpoint > right-click > edit entry, edit "command" to "kdesu configure-trackpoint"

Save & exit

Open it : K-menu > Prefences > configure trackpoint and configure on your needs

=== Hotswapping ===

{{HELP|We need someone who is able to get hotswaping to work properly, this is not the right was to do this!}}
With the new kernel, bay-drivers changed, so if you remove the ultrabay it will freeze your system! You can hack it with a simple comand, first you have to look where the device is:

{{cmduser|less /sys/class/scsi_device/(x)\:0\:0\:0/device/model}}

for (x) first put in 0, if it tells you DVD or the name of the model you want to hotswap youre right. if not, go on with 1, 2 or 3...

then, once you are sure (I deactivated my harddisk like that) you put in:

{{cmduser|echo 1 {{!}} sudo tee /sys/class/scsi_device/(x)\:0\:0\:0/device/delete}}

Now you should be able to remove the device.

{{WARN|Do not use it for harddisks, be sure you unmounted it before! This is just a bad hack, if anyone knows how to get it right --> publish!}}

If Ubuntu does not reactivate the device after putting it in again, do:

{{cmduser|echo 0 0 0 {{!}} sudo tee /sys/class/scsi_host/host1/scan}}

=== Wireless activity LED ===

The LED is not implemented at least in the IWL4965 driver. For the Atheros wifi cards look at the solution below.

A patch posted in this [http://bughost.org/bugzilla/show_bug.cgi?id=1209 thread] works for me on R61 with IWL4965 card.

{{HELP|A howto is needed showing the process of implementing the patch in Hardy Heron. If anyone knows how to do this, please create a quick howto and either put it here or link to it from this page. Please and thank you.}}

As an alternative, you can install a backported IWL4965 driver that ''may'' fix the LED problem on your system.

To active WiFi LED,

sudo apt-get install linux-backports-modules-hardy

{{NOTE|On some machines, (at least one running IWL3945 & IWL4965) applying the above turns on the LED permanently. It should flicker as data is being transmitted. Also, with the above modification, after turning off wireless and then turning it back on (via the switch on the front of the machine) wireless is not reactivated, so not very helpful}}

You can download a compatible [http://wireless.kernel.org/download/compat-wireless-2.6/compat-wireless-2.6.tar.bz2 driver] which supports WiFi led flicking and build it with modifying the {{path|config.mk}} by adding {{bootparm|CONFIG_IWL3945_LEDS|y}} and {{bootparm|CONFIG_IWLWIFI_LEDS|y}} these two options. For Ubuntu/Debian users, build-essential, linux-source-2.6.24 and linux-headers-generic packages are required.

{{HELP|I added the above lines to the config.mk file and it would not make or make install correctly. I received an error 2 at the end of the make. If you have had success, where did you put the items in the config.mk file for it to make and make install correctly? Thanks in advance.}}

'''To enable the Wifi LED with the Atheros cards'''

1) Create a file ~/wifiLED and copy/paste the following into it:

#!/bin/bash
#
# Commands to enable the wireless LED
sysctl dev.wifi0.ledpin=1
sysctl dev.wifi0.softled=3

2) sudo cp ~/wifiLED /etc/init.d

3) sudo chmod 755 /etc/init.d/wifiLED

4) sudo update-rc.d wifiLED defaults 90

=== Hidden SSID ===
It has been reported that users wanting to access Hidden SSIDs have to enter the SSID and password manually in Network Manager to connect. Even after the SSID is saved in Network Manager, it will not reconnect automatically. The user has to connect manually by entering the information as previously described.
It appears that updating the driver by following the instructions [http://linuxwireless.org/en/users/Download here] resolves this issue.

=== Hard Disk Parking ===
Getting hard disk parking to work:

tp_smapi patch is not needed in [http://packages.ubuntu.com/search?keywords=linux-image-2.6.24-18&searchon=names&suite=hardy&section=all linux-image-2.6.24-18]

1. Patch your kernel with the 'protect' [http://www.thinkwiki.org/wiki/HDAPS#Kernel_patch patch].

2. Installing the hdapsd daemon which does the actual parking.

{{cmduser|sudo apt-get install hdapsd hdaps-utils}}

== some other tweaks ==

=== screenblank with {{key|Fn}} + {{key|F3}} ===

Its ok, and might be usefull to get the estimated batterytime when pressing {{key|Fn}}+{{key|F3}}, as it should be. But i dont need that, i find the earlier command for {{key|F3}}, to blank the screen, more useful to save batterylife better.

For that, you must edit {{path|/etc/acpi/thinkpad-lockbattery.sh}} and replace LENOVO by IBM, and IBM by LENOVO :). Do not forget to copy the file before you change it!

=== Enable normal User to Limit CPU Speed ===
To let user set the CPU limit you need to open a Terminal an type there
sudo dpkg-reconfigure gnome-applets
answer the question with yes

=== Fix bluish WSXGA+ displays ===
Many T61 owners complain about a very bluish color temperature: My T61 WSXGA+ was also way too blue. I came across a thread at the notebook review forum http://forum.notebookreview.com/showthread.php?t=174408 which provided two useful ICC profiles which fixed the situation for me. Just install xcalib
sudo apt-get install xcalib
and load one of these profiles.

[[Category: Ubuntu 8.04]]

Installing Ubuntu 8.04 (Hardy Heron) on a ThinkPad T61

2008-07-24T12:37:27Z

Lunatico: /* To enable the Wifi LED with the Atheros cards */

== Items that work out of the box ==

'''Intel Video:''' 2D and 3D acceleration works

'''Nvidia Video:''' 2D and 3D acceleration works

'''Wireless:''' Intel cards tested. Atheros cards also works.

'''Wireless WAN:''' Cingular/AT&T card tested.

'''Network Card''' Intel 10/100/1000 tested

'''Wireless switch''' Tested

'''Webcam''' Tested with cheese and skype.

'''Headphones''' Works out of the box

'''Microphone''' Just needs to be activated, see section [[#Audio|below]]

'''Keyboard Shortcuts:''' Most of them work out of the box, some need to be activated, see section [[#Multimedia_Keys|below]]

== Items that need (some) tweaking to obtain full functionality ==

=== Open Source Intel Wifi Driver ===
The following information is important if you are upgrading from a previous version of Ubuntu to 8.04.

Intel has created a new Linux Wifi driver project for Intel Wireless cards, "[[Iwlwifi]]". This driver is Open Source and no longer requires the Intel daemon to run in addition. This project will support the [[:Category:T61 | T61]]'s Wifi [[Intel PRO/Wireless 3945ABG Mini-PCI Express Adapter | Intel 3945ABG network adapter]] and [[Intel PRO/Wireless 4965AGN Mini-PCI Express Adapter| Intel 4965AGN network adapter]].

An automatic migration will occur when upgrading from [[Installing Ubuntu 7.10 (Gutsy Gibbon) on a ThinkPad T61|Ubuntu 7.10]] to Ubuntu 8.04. However, there is a caveat to be aware of:
* The new driver wants to name the interface wlan0 (by default -- you can rename it to anything you want), and requires a different entry in {{path|/etc/udev/rules.d/70-persistent-net.rules}}, which handles the naming of interfaces. Simply edit this file and delete your old entry for the ipw3945 driver, then unload/reload the new driver, or simply reboot. A new entry will automatically be created that is appropriate for the new driver. Here's an example of the lines to delete:
<pre>
# PCI device 0x8086:0x4227 (ipw3945)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:1b:77:a4:0e:2f", NAME="eth1"
</pre>

If you need to perform a manual migration, the Ubuntu Help Community has written some [https://help.ubuntu.com/community/WifiDocs/Driver/iwlwifi_Intel_3945_4965/gutsy documentation] that will make this very easy to do.

=== Compiz and XV Playback on Intel GM965/GL960 ===

With Ubuntu 7.10 (Gutsy Gibbon) you currently have to choose between using Compiz and working video playback using XV. On 8.04 (Hardy Heron) alpha 5 you can play videos using XV under compiz, it works right out of the box using the Live-CD.

=== Suspend with Nv140m ===

** Update as of July 17th 2008 -- Using 8.04.1 with the newest nvidea drivers, I had no problems suspending without any additional configuration. **

Suspend may not work even after editing acpi-support. Enable bluetooth (Fn+F5) may result in a successful suspend. NOTE: that although the wifi led does not change when Fn+F5 is used, the wifi is still toggled by this key.

'''Hal "S3 BIOS" parameter issue!'''

After doing the changes to the /etc/default/acpi-support file (described [http://www.thinkwiki.org/wiki/Installing_Ubuntu_7.10_(Gutsy_Gibbon)_on_a_ThinkPad_T61#How_to_Suspend_with_nVidia_140m.2F570m here]), I for one, managed to have '''stable''' suspend support by creating a new file called: '''/etc/hal/fdi/information/lenovo.fdi''' with the following contents:
<pre>
<?xml version="1.0" encoding="ISO-8859-1"?> 
<deviceinfo version="0.2">
<device>
<match key="system.hardware.vendor" string="LENOVO">
<merge key="power_management.quirk.s3_bios" type="bool">false</merge>
</match>
</device>
</deviceinfo>
</pre>
{{NOTE|The problem (after reading the HAL and pm-utils documentations) is the fact that (as far as I can tell) the T61 Lenovo doesn't allow the S3 BIOS to be called *during* suspend/resume, which HAL seems to do by default (who knows, maybe there are T61s out there that do work with this default)!

This did not seem to be necessary for previous versions of Ubuntu. Also note that I have an NVIDIA card so I have no idea what to do for Intel versions.The change should also be resistant to HAL and pm-utils upgrades.}}

'''Still no suspend with nvs140m? Got Modell 6460?'''

Fix above didn't work for me on a 15.4 wide T61 Modell 6460 with nv140m. Bios is updated to 2.14 but didn't change anything, except the usb bug is fix. Suspend seems to work fine, but resume gives me a black screen (backlight off - no reaction to brightness up) and I can hear 2 beeps. Most of the time I can reboot with ctrl+alt+delete but the screen stays dark until bios.

follow the instructions above but create the new file called: '''/etc/hal/fdi/information/lenovo.fdi''' with the following contents instead:
<pre>
<?xml version="1.0" encoding="ISO-8859-1"?> 
<deviceinfo version="0.2">
<device>
<match key="system.hardware.vendor" string="LENOVO">
<merge key="power_management.quirk.s3_mode" type="bool">true</merge>
<merge key="power_management.quirk.s3_bios" type="bool">false</merge>
<merge key="power_management.quirk.save_pci" type="bool">true</merge>
</match>
</device>
</deviceinfo>
</pre>

Also you want to set the following parameter in

{{path|/etc/default/acpi-support}}
<pre>
SAVE_VIDEO_PCI_STATE=true
</pre>

{{NOTE|This works for me with mode 6460, except for one problem: You may get a white screen in xorg after resume when using compiz. If you don't have a 6460 with nvidia this file may break things for you because it doesn't care about the modell and sets the parameter for any lenovo product}}
{{HELP|Anyone with more knowledge of hal and acpi-support is welcome to clean this up. I also don't know why this setting can be done via hal and in acpi-support.
See below!}}

'''Working on hardy final'''

After trying out all these recipes on my 6457CTO waking up from suspend still did not work. Finally I came across a blog entry which pointed out the right way: [[http://david.goodlad.ca/2008/3/14/suspend-hibernate-on-lenovo-t61 David Goodlad's blog]]. I realized that all the fixes proposing editing the acpi-support file or adding a kernel parameter acpi_sleep=s3_mode must be wrong because since hardy gnome-power-manager gets its information solely from hal. So setting up correct hal information is the right way but the proposed solution (creating a /etc/hal/fdi/information/lenovo.fdi file) did not work for me. Ok, but now step by step:

# Revert ALL the proposed fixes from above. I found out that at least the lenovo.fdi solution is actually breaking the real fix. So for sure delete /etc/hal/fdi/information/lenovo.fdi
# Find out about the excact hal name of your machine: <pre>hal-device |grep 6457</pre> where 6457 is the model number of my t61, replace it with your own. In my case it spits out something like this: system.hardware.product = '6457CTO'. So now I know that hal identifies my machine as 6457CTO.
# <pre>sudo gedit /usr/share/hal/fdi/information/10freedesktop/20-video-quirk-pm-lenovo.fdi</pre> and add a section to the end of the file, just above the </device> tag and replace 6457CTO with your hal device name:
<pre>

<match key="system.hardware.product" string="6457CTO">

<merge key="power_management.quirk.s3_mode" type="bool">true</merge>
<merge key="power_management.quirk.s3_bios" type="bool">false</merge>
<merge key="power_management.quirk.save_pci" type="bool">true</merge>
</match>
</pre>

Now save and reboot. Now you might run into the problem of coming back from resume into a completely white screen where normally should be the password dialog. Entering your password blindly is not nice but at least you can resume.

{{NOTE|Somehow I couldn't make the wildcard matching work as they did in the lenovo.fdi solution, but that might be due to my shortcomings on that syntax. Anyway matching the device by its full name worked for me. Probably somebody who knows more about the matching could make that wildcard thing work to have a more general solution. Because hal also knows the xorg driver name (info.linux.driver) there should be a way to set up the quirks depending on the driver.}}

[[Category: T61]]

=== TrackPoint ===
The [[TrackPoint]] works out of the box, but does not scroll nor does the tap-clicking (press to select) feature work. Therefor see: [[#tap-to-click feature]] To enable using the middle mouse button to scroll, replace the "Configured Mouse" section in {{path|/etc/X11/xorg.conf}} with the following:
<pre>
Section "InputDevice"
Identifier "Trackpoint"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ImPS/2"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "true"
Option "EmulateWheel" "true"
Option "EmulateWheelButton" "2"
EndSection
</pre>

{{NOTE|However, if you need to use external usb mouse, the above configuration is wrong. It will cause odd behavior. Try the following configuration from [http://gentoo-wiki.com/HARDWARE_IBM_Specific_Laptop_Guide#TrackPoint Gentoo Wiki]:}}
<pre>
Section "InputDevice"
Identifier "UltraNav TrackPoint"
Driver "mouse"
Option "Device" "/dev/input/mouse1"
Option "Protocol" "ExplorerPS/2"
Option "Emulate3Buttons" "on"
Option "Emulate3TimeOut" "50"
Option "EmulateWheel" "on"
Option "EmulateWheelTimeOut" "200"
Option "EmulateWheelButton" "2"
Option "YAxisMapping" "4 5"
Option "XAxisMapping" "6 7"
Option "ZAxisMapping" "4 5"
EndSection
</pre>

=== Audio ===

Works great out of the box, just the microphone has to be activated, it is considered a generic capture source and is muted by default.

To unmute the microphone:

*Right Click on the volume icon next to the clock and click on "Open Volume Control"

*Click Edit -> Preferences. A list of devices will be displayed, you should check the following (Do not uncheck any existing items):

Input Source
Capture

*Click Close and there should be two additional tabs "Recording" and "Options". -

*Click Recording and click on the microphone under the Capture slider so that it no longer has a red line through it, and put the slider up as it may be deactivated.

*Click Options and under capture source select internal mic.

To test your mic using Sound Recorder select Capture as the sound source.

This solution has been tested with Sound Recorder and Skype.

To get the volume controls working:

*add the following line to /etc/modprobe.d/alsa-base, then reboot

options snd-hda-intel index=0 model=thinkpad

{{NOTE|The volume controls worked fine for me out of the box on a 6460.}}

=== Multimedia Keys ===

Most Multimedia Keys work out of the box, just the play, forward and stop buttons need to be adjusted, therefore, press alt + F2 and type in gnome-keybinding-properties. Then everything works as followed:

* Fn-PgUp activates/deactivates the thinklight
* Fn-Up will trigger stop on a media player
* Fn-Down will toggle pause and play on a media player
* Fn-Left/Right go to prev/next tracks on a media player
* Fn-F2 properly locks the screen
* Fn-F3 shows remaining battery >>does not work on all machines<<
* Fn-F4 suspends (to ram)
* Fn-F9 ejects cds >>does not work on all machines, I think this is supposed to eject from a "dock"<<
* Fn-F12 hibernates (to disk)
* PrtSc opens the screenshot dialog

To enable the back, forward, and the menu keys you'll need to teach XKB what they are.

* Check the '''XkbLayout''' option (under '''InputDevice''') in your {{path|/etc/X11/xorg.conf}} file to determine which keyboard layout Ubuntu is using (I'll use 'us' for the example).
* Navigate to {{path|/etc/X11/xkb/symbols}} and, as root, open the appropriate layout file (as determined above) in your favorite editor.
{{cmduser|cd /etc/X11/xkb/symbols}}
{{cmduser|sudo gedit us}}
* In the '''xkb_symbols "basic"''' section after the '''name[Group1]= "x";''' (where x is a country name, or similar) line add the following:
key <I63> { [ Menu ] };
key <I69> { [ XF86Forward ] };
key <I6A> { [ XF86Back ] };
* Now log out and back in and all three of the buttons should function.

=== Thinkpad Button ===

Paste the following into /usr/share/hotkey-setup/ibm.hk
setkeycodes e017 148 # thinkpad button
You can also just type this into a terminal, to test it for the time of the current session.

Paste the following into the right file in /usr/share/xmodmap (check your country code)
keycode 159 = XF86Terminal
For immediate availability of the button, reload the file by executing
xmodmap <xmodmap.file>

Then use the "Keyboard Shortcuts" tool under "Preferences".

== Items that don't work (a.k.a.: items that need more intense tweaking to get fixed)==

=== tap-to-click feature ===

For the tap-to-click feature (taping the stick instead of using the left mouse button) i used a configure trackpoint utility: [http://tpctl.sourceforge.net/configure-trackpoint.html] there is a package for ubuntu 7.04 i386, but i compiled it by myself (using amd64):

1.) download the .tar.gz file

2.) unpack it

3.) install libgnomeui-dev

{{cmduser|sudo aptitude install libgnomeui-dev}}

4.) in the folder, do:

{{cmduser|./configure}}

if everything worked fine:

{{cmduser|make}}

then install it:

{{cmduser|sudo make install}}

5.a) Gnome : Open it: System > configure trackpoint, and configure on your needs

5.b) Kde : K-menu > Prefences > configure trackpoint > right-click > edit entry, edit "command" to "kdesu configure-trackpoint"

Save & exit

Open it : K-menu > Prefences > configure trackpoint and configure on your needs

=== Hotswapping ===

{{HELP|We need someone who is able to get hotswaping to work properly, this is not the right was to do this!}}
With the new kernel, bay-drivers changed, so if you remove the ultrabay it will freeze your system! You can hack it with a simple comand, first you have to look where the device is:

{{cmduser|less /sys/class/scsi_device/(x)\:0\:0\:0/device/model}}

for (x) first put in 0, if it tells you DVD or the name of the model you want to hotswap youre right. if not, go on with 1, 2 or 3...

then, once you are sure (I deactivated my harddisk like that) you put in:

{{cmduser|echo 1 {{!}} sudo tee /sys/class/scsi_device/(x)\:0\:0\:0/device/delete}}

Now you should be able to remove the device.

{{WARN|Do not use it for harddisks, be sure you unmounted it before! This is just a bad hack, if anyone knows how to get it right --> publish!}}

If Ubuntu does not reactivate the device after putting it in again, do:

{{cmduser|echo 0 0 0 {{!}} sudo tee /sys/class/scsi_host/host1/scan}}

=== Wireless activity LED ===

The LED is not implemented at least in the IWL4965 driver. For the Atheros wifi cards look at the solution below.

A patch posted in this [http://bughost.org/bugzilla/show_bug.cgi?id=1209 thread] works for me on R61 with IWL4965 card.

{{HELP|A howto is needed showing the process of implementing the patch in Hardy Heron. If anyone knows how to do this, please create a quick howto and either put it here or link to it from this page. Please and thank you.}}

As an alternative, you can install a backported IWL4965 driver that ''may'' fix the LED problem on your system.

To active WiFi LED,

sudo apt-get install linux-backports-modules-hardy

{{NOTE|On some machines, (at least one running IWL3945 & IWL4965) applying the above turns on the LED permanently. It should flicker as data is being transmitted. Also, with the above modification, after turning off wireless and then turning it back on (via the switch on the front of the machine) wireless is not reactivated, so not very helpful}}

You can download a compatible [http://wireless.kernel.org/download/compat-wireless-2.6/compat-wireless-2.6.tar.bz2 driver] which supports WiFi led flicking and build it with modifying the {{path|config.mk}} by adding {{bootparm|CONFIG_IWL3945_LEDS|y}} and {{bootparm|CONFIG_IWLWIFI_LEDS|y}} these two options. For Ubuntu/Debian users, build-essential, linux-source-2.6.24 and linux-headers-generic packages are required.

{{HELP|I added the above lines to the config.mk file and it would not make or make install correctly. I received an error 2 at the end of the make. If you have had success, where did you put the items in the config.mk file for it to make and make install correctly? Thanks in advance.}}

=== Hidden SSID ===
It has been reported that users wanting to access Hidden SSIDs have to enter the SSID and password manually in Network Manager to connect. Even after the SSID is saved in Network Manager, it will not reconnect automatically. The user has to connect manually by entering the information as previously described.
It appears that updating the driver by following the instructions [http://linuxwireless.org/en/users/Download here] resolves this issue.

=== Hard Disk Parking ===
Getting hard disk parking to work:

tp_smapi patch is not needed in [http://packages.ubuntu.com/search?keywords=linux-image-2.6.24-18&searchon=names&suite=hardy&section=all linux-image-2.6.24-18]

1. Patch your kernel with the 'protect' [http://www.thinkwiki.org/wiki/HDAPS#Kernel_patch patch].

2. Installing the hdapsd daemon which does the actual parking.

{{cmduser|sudo apt-get install hdapsd hdaps-utils}}

== some other tweaks ==

=== screenblank with {{key|Fn}} + {{key|F3}} ===

Its ok, and might be usefull to get the estimated batterytime when pressing {{key|Fn}}+{{key|F3}}, as it should be. But i dont need that, i find the earlier command for {{key|F3}}, to blank the screen, more useful to save batterylife better.

For that, you must edit {{path|/etc/acpi/thinkpad-lockbattery.sh}} and replace LENOVO by IBM, and IBM by LENOVO :). Do not forget to copy the file before you change it!

=== Enable normal User to Limit CPU Speed ===
To let user set the CPU limit you need to open a Terminal an type there
sudo dpkg-reconfigure gnome-applets
answer the question with yes

=== Fix bluish WSXGA+ displays ===
Many T61 owners complain about a very bluish color temperature: My T61 WSXGA+ was also way too blue. I came across a thread at the notebook review forum http://forum.notebookreview.com/showthread.php?t=174408 which provided two useful ICC profiles which fixed the situation for me. Just install xcalib
sudo apt-get install xcalib
and load one of these profiles.

[[Category: Ubuntu 8.04]]

Installing Ubuntu 8.04 (Hardy Heron) on a ThinkPad T61

2008-07-24T12:36:26Z

Lunatico: /* Wireless activity LED */

== Items that work out of the box ==

'''Intel Video:''' 2D and 3D acceleration works

'''Nvidia Video:''' 2D and 3D acceleration works

'''Wireless:''' Intel cards tested. Atheros cards also works.

'''Wireless WAN:''' Cingular/AT&T card tested.

'''Network Card''' Intel 10/100/1000 tested

'''Wireless switch''' Tested

'''Webcam''' Tested with cheese and skype.

'''Headphones''' Works out of the box

'''Microphone''' Just needs to be activated, see section [[#Audio|below]]

'''Keyboard Shortcuts:''' Most of them work out of the box, some need to be activated, see section [[#Multimedia_Keys|below]]

== Items that need (some) tweaking to obtain full functionality ==

=== Open Source Intel Wifi Driver ===
The following information is important if you are upgrading from a previous version of Ubuntu to 8.04.

Intel has created a new Linux Wifi driver project for Intel Wireless cards, "[[Iwlwifi]]". This driver is Open Source and no longer requires the Intel daemon to run in addition. This project will support the [[:Category:T61 | T61]]'s Wifi [[Intel PRO/Wireless 3945ABG Mini-PCI Express Adapter | Intel 3945ABG network adapter]] and [[Intel PRO/Wireless 4965AGN Mini-PCI Express Adapter| Intel 4965AGN network adapter]].

An automatic migration will occur when upgrading from [[Installing Ubuntu 7.10 (Gutsy Gibbon) on a ThinkPad T61|Ubuntu 7.10]] to Ubuntu 8.04. However, there is a caveat to be aware of:
* The new driver wants to name the interface wlan0 (by default -- you can rename it to anything you want), and requires a different entry in {{path|/etc/udev/rules.d/70-persistent-net.rules}}, which handles the naming of interfaces. Simply edit this file and delete your old entry for the ipw3945 driver, then unload/reload the new driver, or simply reboot. A new entry will automatically be created that is appropriate for the new driver. Here's an example of the lines to delete:
<pre>
# PCI device 0x8086:0x4227 (ipw3945)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:1b:77:a4:0e:2f", NAME="eth1"
</pre>

If you need to perform a manual migration, the Ubuntu Help Community has written some [https://help.ubuntu.com/community/WifiDocs/Driver/iwlwifi_Intel_3945_4965/gutsy documentation] that will make this very easy to do.

=== Compiz and XV Playback on Intel GM965/GL960 ===

With Ubuntu 7.10 (Gutsy Gibbon) you currently have to choose between using Compiz and working video playback using XV. On 8.04 (Hardy Heron) alpha 5 you can play videos using XV under compiz, it works right out of the box using the Live-CD.

=== Suspend with Nv140m ===

** Update as of July 17th 2008 -- Using 8.04.1 with the newest nvidea drivers, I had no problems suspending without any additional configuration. **

Suspend may not work even after editing acpi-support. Enable bluetooth (Fn+F5) may result in a successful suspend. NOTE: that although the wifi led does not change when Fn+F5 is used, the wifi is still toggled by this key.

'''Hal "S3 BIOS" parameter issue!'''

After doing the changes to the /etc/default/acpi-support file (described [http://www.thinkwiki.org/wiki/Installing_Ubuntu_7.10_(Gutsy_Gibbon)_on_a_ThinkPad_T61#How_to_Suspend_with_nVidia_140m.2F570m here]), I for one, managed to have '''stable''' suspend support by creating a new file called: '''/etc/hal/fdi/information/lenovo.fdi''' with the following contents:
<pre>
<?xml version="1.0" encoding="ISO-8859-1"?> 
<deviceinfo version="0.2">
<device>
<match key="system.hardware.vendor" string="LENOVO">
<merge key="power_management.quirk.s3_bios" type="bool">false</merge>
</match>
</device>
</deviceinfo>
</pre>
{{NOTE|The problem (after reading the HAL and pm-utils documentations) is the fact that (as far as I can tell) the T61 Lenovo doesn't allow the S3 BIOS to be called *during* suspend/resume, which HAL seems to do by default (who knows, maybe there are T61s out there that do work with this default)!

This did not seem to be necessary for previous versions of Ubuntu. Also note that I have an NVIDIA card so I have no idea what to do for Intel versions.The change should also be resistant to HAL and pm-utils upgrades.}}

'''Still no suspend with nvs140m? Got Modell 6460?'''

Fix above didn't work for me on a 15.4 wide T61 Modell 6460 with nv140m. Bios is updated to 2.14 but didn't change anything, except the usb bug is fix. Suspend seems to work fine, but resume gives me a black screen (backlight off - no reaction to brightness up) and I can hear 2 beeps. Most of the time I can reboot with ctrl+alt+delete but the screen stays dark until bios.

follow the instructions above but create the new file called: '''/etc/hal/fdi/information/lenovo.fdi''' with the following contents instead:
<pre>
<?xml version="1.0" encoding="ISO-8859-1"?> 
<deviceinfo version="0.2">
<device>
<match key="system.hardware.vendor" string="LENOVO">
<merge key="power_management.quirk.s3_mode" type="bool">true</merge>
<merge key="power_management.quirk.s3_bios" type="bool">false</merge>
<merge key="power_management.quirk.save_pci" type="bool">true</merge>
</match>
</device>
</deviceinfo>
</pre>

Also you want to set the following parameter in

{{path|/etc/default/acpi-support}}
<pre>
SAVE_VIDEO_PCI_STATE=true
</pre>

{{NOTE|This works for me with mode 6460, except for one problem: You may get a white screen in xorg after resume when using compiz. If you don't have a 6460 with nvidia this file may break things for you because it doesn't care about the modell and sets the parameter for any lenovo product}}
{{HELP|Anyone with more knowledge of hal and acpi-support is welcome to clean this up. I also don't know why this setting can be done via hal and in acpi-support.
See below!}}

'''Working on hardy final'''

After trying out all these recipes on my 6457CTO waking up from suspend still did not work. Finally I came across a blog entry which pointed out the right way: [[http://david.goodlad.ca/2008/3/14/suspend-hibernate-on-lenovo-t61 David Goodlad's blog]]. I realized that all the fixes proposing editing the acpi-support file or adding a kernel parameter acpi_sleep=s3_mode must be wrong because since hardy gnome-power-manager gets its information solely from hal. So setting up correct hal information is the right way but the proposed solution (creating a /etc/hal/fdi/information/lenovo.fdi file) did not work for me. Ok, but now step by step:

# Revert ALL the proposed fixes from above. I found out that at least the lenovo.fdi solution is actually breaking the real fix. So for sure delete /etc/hal/fdi/information/lenovo.fdi
# Find out about the excact hal name of your machine: <pre>hal-device |grep 6457</pre> where 6457 is the model number of my t61, replace it with your own. In my case it spits out something like this: system.hardware.product = '6457CTO'. So now I know that hal identifies my machine as 6457CTO.
# <pre>sudo gedit /usr/share/hal/fdi/information/10freedesktop/20-video-quirk-pm-lenovo.fdi</pre> and add a section to the end of the file, just above the </device> tag and replace 6457CTO with your hal device name:
<pre>

<match key="system.hardware.product" string="6457CTO">

<merge key="power_management.quirk.s3_mode" type="bool">true</merge>
<merge key="power_management.quirk.s3_bios" type="bool">false</merge>
<merge key="power_management.quirk.save_pci" type="bool">true</merge>
</match>
</pre>

Now save and reboot. Now you might run into the problem of coming back from resume into a completely white screen where normally should be the password dialog. Entering your password blindly is not nice but at least you can resume.

{{NOTE|Somehow I couldn't make the wildcard matching work as they did in the lenovo.fdi solution, but that might be due to my shortcomings on that syntax. Anyway matching the device by its full name worked for me. Probably somebody who knows more about the matching could make that wildcard thing work to have a more general solution. Because hal also knows the xorg driver name (info.linux.driver) there should be a way to set up the quirks depending on the driver.}}

[[Category: T61]]

=== TrackPoint ===
The [[TrackPoint]] works out of the box, but does not scroll nor does the tap-clicking (press to select) feature work. Therefor see: [[#tap-to-click feature]] To enable using the middle mouse button to scroll, replace the "Configured Mouse" section in {{path|/etc/X11/xorg.conf}} with the following:
<pre>
Section "InputDevice"
Identifier "Trackpoint"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ImPS/2"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "true"
Option "EmulateWheel" "true"
Option "EmulateWheelButton" "2"
EndSection
</pre>

{{NOTE|However, if you need to use external usb mouse, the above configuration is wrong. It will cause odd behavior. Try the following configuration from [http://gentoo-wiki.com/HARDWARE_IBM_Specific_Laptop_Guide#TrackPoint Gentoo Wiki]:}}
<pre>
Section "InputDevice"
Identifier "UltraNav TrackPoint"
Driver "mouse"
Option "Device" "/dev/input/mouse1"
Option "Protocol" "ExplorerPS/2"
Option "Emulate3Buttons" "on"
Option "Emulate3TimeOut" "50"
Option "EmulateWheel" "on"
Option "EmulateWheelTimeOut" "200"
Option "EmulateWheelButton" "2"
Option "YAxisMapping" "4 5"
Option "XAxisMapping" "6 7"
Option "ZAxisMapping" "4 5"
EndSection
</pre>

=== Audio ===

Works great out of the box, just the microphone has to be activated, it is considered a generic capture source and is muted by default.

To unmute the microphone:

*Right Click on the volume icon next to the clock and click on "Open Volume Control"

*Click Edit -> Preferences. A list of devices will be displayed, you should check the following (Do not uncheck any existing items):

Input Source
Capture

*Click Close and there should be two additional tabs "Recording" and "Options". -

*Click Recording and click on the microphone under the Capture slider so that it no longer has a red line through it, and put the slider up as it may be deactivated.

*Click Options and under capture source select internal mic.

To test your mic using Sound Recorder select Capture as the sound source.

This solution has been tested with Sound Recorder and Skype.

To get the volume controls working:

*add the following line to /etc/modprobe.d/alsa-base, then reboot

options snd-hda-intel index=0 model=thinkpad

{{NOTE|The volume controls worked fine for me out of the box on a 6460.}}

=== Multimedia Keys ===

Most Multimedia Keys work out of the box, just the play, forward and stop buttons need to be adjusted, therefore, press alt + F2 and type in gnome-keybinding-properties. Then everything works as followed:

* Fn-PgUp activates/deactivates the thinklight
* Fn-Up will trigger stop on a media player
* Fn-Down will toggle pause and play on a media player
* Fn-Left/Right go to prev/next tracks on a media player
* Fn-F2 properly locks the screen
* Fn-F3 shows remaining battery >>does not work on all machines<<
* Fn-F4 suspends (to ram)
* Fn-F9 ejects cds >>does not work on all machines, I think this is supposed to eject from a "dock"<<
* Fn-F12 hibernates (to disk)
* PrtSc opens the screenshot dialog

To enable the back, forward, and the menu keys you'll need to teach XKB what they are.

* Check the '''XkbLayout''' option (under '''InputDevice''') in your {{path|/etc/X11/xorg.conf}} file to determine which keyboard layout Ubuntu is using (I'll use 'us' for the example).
* Navigate to {{path|/etc/X11/xkb/symbols}} and, as root, open the appropriate layout file (as determined above) in your favorite editor.
{{cmduser|cd /etc/X11/xkb/symbols}}
{{cmduser|sudo gedit us}}
* In the '''xkb_symbols "basic"''' section after the '''name[Group1]= "x";''' (where x is a country name, or similar) line add the following:
key <I63> { [ Menu ] };
key <I69> { [ XF86Forward ] };
key <I6A> { [ XF86Back ] };
* Now log out and back in and all three of the buttons should function.

=== Thinkpad Button ===

Paste the following into /usr/share/hotkey-setup/ibm.hk
setkeycodes e017 148 # thinkpad button
You can also just type this into a terminal, to test it for the time of the current session.

Paste the following into the right file in /usr/share/xmodmap (check your country code)
keycode 159 = XF86Terminal
For immediate availability of the button, reload the file by executing
xmodmap <xmodmap.file>

Then use the "Keyboard Shortcuts" tool under "Preferences".

== Items that don't work (a.k.a.: items that need more intense tweaking to get fixed)==

=== tap-to-click feature ===

For the tap-to-click feature (taping the stick instead of using the left mouse button) i used a configure trackpoint utility: [http://tpctl.sourceforge.net/configure-trackpoint.html] there is a package for ubuntu 7.04 i386, but i compiled it by myself (using amd64):

1.) download the .tar.gz file

2.) unpack it

3.) install libgnomeui-dev

{{cmduser|sudo aptitude install libgnomeui-dev}}

4.) in the folder, do:

{{cmduser|./configure}}

if everything worked fine:

{{cmduser|make}}

then install it:

{{cmduser|sudo make install}}

5.a) Gnome : Open it: System > configure trackpoint, and configure on your needs

5.b) Kde : K-menu > Prefences > configure trackpoint > right-click > edit entry, edit "command" to "kdesu configure-trackpoint"

Save & exit

Open it : K-menu > Prefences > configure trackpoint and configure on your needs

=== Hotswapping ===

{{HELP|We need someone who is able to get hotswaping to work properly, this is not the right was to do this!}}
With the new kernel, bay-drivers changed, so if you remove the ultrabay it will freeze your system! You can hack it with a simple comand, first you have to look where the device is:

{{cmduser|less /sys/class/scsi_device/(x)\:0\:0\:0/device/model}}

for (x) first put in 0, if it tells you DVD or the name of the model you want to hotswap youre right. if not, go on with 1, 2 or 3...

then, once you are sure (I deactivated my harddisk like that) you put in:

{{cmduser|echo 1 {{!}} sudo tee /sys/class/scsi_device/(x)\:0\:0\:0/device/delete}}

Now you should be able to remove the device.

{{WARN|Do not use it for harddisks, be sure you unmounted it before! This is just a bad hack, if anyone knows how to get it right --> publish!}}

If Ubuntu does not reactivate the device after putting it in again, do:

{{cmduser|echo 0 0 0 {{!}} sudo tee /sys/class/scsi_host/host1/scan}}

=== Wireless activity LED ===

The LED is not implemented at least in the IWL4965 driver. For the Atheros wifi cards look at the solution below.

A patch posted in this [http://bughost.org/bugzilla/show_bug.cgi?id=1209 thread] works for me on R61 with IWL4965 card.

{{HELP|A howto is needed showing the process of implementing the patch in Hardy Heron. If anyone knows how to do this, please create a quick howto and either put it here or link to it from this page. Please and thank you.}}

As an alternative, you can install a backported IWL4965 driver that ''may'' fix the LED problem on your system.

To active WiFi LED,

sudo apt-get install linux-backports-modules-hardy

{{NOTE|On some machines, (at least one running IWL3945 & IWL4965) applying the above turns on the LED permanently. It should flicker as data is being transmitted. Also, with the above modification, after turning off wireless and then turning it back on (via the switch on the front of the machine) wireless is not reactivated, so not very helpful}}

You can download a compatible [http://wireless.kernel.org/download/compat-wireless-2.6/compat-wireless-2.6.tar.bz2 driver] which supports WiFi led flicking and build it with modifying the {{path|config.mk}} by adding {{bootparm|CONFIG_IWL3945_LEDS|y}} and {{bootparm|CONFIG_IWLWIFI_LEDS|y}} these two options. For Ubuntu/Debian users, build-essential, linux-source-2.6.24 and linux-headers-generic packages are required.

{{HELP|I added the above lines to the config.mk file and it would not make or make install correctly. I received an error 2 at the end of the make. If you have had success, where did you put the items in the config.mk file for it to make and make install correctly? Thanks in advance.}}

== To enable the Wifi LED with the Atheros cards ==

1) Create a file ~/wifiLED and copy/paste the following into it:

#!/bin/bash
#
# Commands to enable the wireless LED
sysctl dev.wifi0.ledpin=1
sysctl dev.wifi0.softled=3

2) sudo cp ~/wifiLED /etc/init.d

3) sudo chmod 755 /etc/init.d/wifiLED

4) sudo update-rc.d wifiLED defaults 90

=== Hidden SSID ===
It has been reported that users wanting to access Hidden SSIDs have to enter the SSID and password manually in Network Manager to connect. Even after the SSID is saved in Network Manager, it will not reconnect automatically. The user has to connect manually by entering the information as previously described.
It appears that updating the driver by following the instructions [http://linuxwireless.org/en/users/Download here] resolves this issue.

=== Hard Disk Parking ===
Getting hard disk parking to work:

tp_smapi patch is not needed in [http://packages.ubuntu.com/search?keywords=linux-image-2.6.24-18&searchon=names&suite=hardy&section=all linux-image-2.6.24-18]

1. Patch your kernel with the 'protect' [http://www.thinkwiki.org/wiki/HDAPS#Kernel_patch patch].

2. Installing the hdapsd daemon which does the actual parking.

{{cmduser|sudo apt-get install hdapsd hdaps-utils}}

== some other tweaks ==

=== screenblank with {{key|Fn}} + {{key|F3}} ===

Its ok, and might be usefull to get the estimated batterytime when pressing {{key|Fn}}+{{key|F3}}, as it should be. But i dont need that, i find the earlier command for {{key|F3}}, to blank the screen, more useful to save batterylife better.

For that, you must edit {{path|/etc/acpi/thinkpad-lockbattery.sh}} and replace LENOVO by IBM, and IBM by LENOVO :). Do not forget to copy the file before you change it!

=== Enable normal User to Limit CPU Speed ===
To let user set the CPU limit you need to open a Terminal an type there
sudo dpkg-reconfigure gnome-applets
answer the question with yes

=== Fix bluish WSXGA+ displays ===
Many T61 owners complain about a very bluish color temperature: My T61 WSXGA+ was also way too blue. I came across a thread at the notebook review forum http://forum.notebookreview.com/showthread.php?t=174408 which provided two useful ICC profiles which fixed the situation for me. Just install xcalib
sudo apt-get install xcalib
and load one of these profiles.

[[Category: Ubuntu 8.04]]

Installing Ubuntu 8.04 (Hardy Heron) on a ThinkPad T61

2008-07-24T12:35:00Z

Lunatico: /* Wireless activity LED */

== Items that work out of the box ==

'''Intel Video:''' 2D and 3D acceleration works

'''Nvidia Video:''' 2D and 3D acceleration works

'''Wireless:''' Intel cards tested. Atheros cards also works.

'''Wireless WAN:''' Cingular/AT&T card tested.

'''Network Card''' Intel 10/100/1000 tested

'''Wireless switch''' Tested

'''Webcam''' Tested with cheese and skype.

'''Headphones''' Works out of the box

'''Microphone''' Just needs to be activated, see section [[#Audio|below]]

'''Keyboard Shortcuts:''' Most of them work out of the box, some need to be activated, see section [[#Multimedia_Keys|below]]

== Items that need (some) tweaking to obtain full functionality ==

=== Open Source Intel Wifi Driver ===
The following information is important if you are upgrading from a previous version of Ubuntu to 8.04.

Intel has created a new Linux Wifi driver project for Intel Wireless cards, "[[Iwlwifi]]". This driver is Open Source and no longer requires the Intel daemon to run in addition. This project will support the [[:Category:T61 | T61]]'s Wifi [[Intel PRO/Wireless 3945ABG Mini-PCI Express Adapter | Intel 3945ABG network adapter]] and [[Intel PRO/Wireless 4965AGN Mini-PCI Express Adapter| Intel 4965AGN network adapter]].

An automatic migration will occur when upgrading from [[Installing Ubuntu 7.10 (Gutsy Gibbon) on a ThinkPad T61|Ubuntu 7.10]] to Ubuntu 8.04. However, there is a caveat to be aware of:
* The new driver wants to name the interface wlan0 (by default -- you can rename it to anything you want), and requires a different entry in {{path|/etc/udev/rules.d/70-persistent-net.rules}}, which handles the naming of interfaces. Simply edit this file and delete your old entry for the ipw3945 driver, then unload/reload the new driver, or simply reboot. A new entry will automatically be created that is appropriate for the new driver. Here's an example of the lines to delete:
<pre>
# PCI device 0x8086:0x4227 (ipw3945)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:1b:77:a4:0e:2f", NAME="eth1"
</pre>

If you need to perform a manual migration, the Ubuntu Help Community has written some [https://help.ubuntu.com/community/WifiDocs/Driver/iwlwifi_Intel_3945_4965/gutsy documentation] that will make this very easy to do.

=== Compiz and XV Playback on Intel GM965/GL960 ===

With Ubuntu 7.10 (Gutsy Gibbon) you currently have to choose between using Compiz and working video playback using XV. On 8.04 (Hardy Heron) alpha 5 you can play videos using XV under compiz, it works right out of the box using the Live-CD.

=== Suspend with Nv140m ===

** Update as of July 17th 2008 -- Using 8.04.1 with the newest nvidea drivers, I had no problems suspending without any additional configuration. **

Suspend may not work even after editing acpi-support. Enable bluetooth (Fn+F5) may result in a successful suspend. NOTE: that although the wifi led does not change when Fn+F5 is used, the wifi is still toggled by this key.

'''Hal "S3 BIOS" parameter issue!'''

After doing the changes to the /etc/default/acpi-support file (described [http://www.thinkwiki.org/wiki/Installing_Ubuntu_7.10_(Gutsy_Gibbon)_on_a_ThinkPad_T61#How_to_Suspend_with_nVidia_140m.2F570m here]), I for one, managed to have '''stable''' suspend support by creating a new file called: '''/etc/hal/fdi/information/lenovo.fdi''' with the following contents:
<pre>
<?xml version="1.0" encoding="ISO-8859-1"?> 
<deviceinfo version="0.2">
<device>
<match key="system.hardware.vendor" string="LENOVO">
<merge key="power_management.quirk.s3_bios" type="bool">false</merge>
</match>
</device>
</deviceinfo>
</pre>
{{NOTE|The problem (after reading the HAL and pm-utils documentations) is the fact that (as far as I can tell) the T61 Lenovo doesn't allow the S3 BIOS to be called *during* suspend/resume, which HAL seems to do by default (who knows, maybe there are T61s out there that do work with this default)!

This did not seem to be necessary for previous versions of Ubuntu. Also note that I have an NVIDIA card so I have no idea what to do for Intel versions.The change should also be resistant to HAL and pm-utils upgrades.}}

'''Still no suspend with nvs140m? Got Modell 6460?'''

Fix above didn't work for me on a 15.4 wide T61 Modell 6460 with nv140m. Bios is updated to 2.14 but didn't change anything, except the usb bug is fix. Suspend seems to work fine, but resume gives me a black screen (backlight off - no reaction to brightness up) and I can hear 2 beeps. Most of the time I can reboot with ctrl+alt+delete but the screen stays dark until bios.

follow the instructions above but create the new file called: '''/etc/hal/fdi/information/lenovo.fdi''' with the following contents instead:
<pre>
<?xml version="1.0" encoding="ISO-8859-1"?> 
<deviceinfo version="0.2">
<device>
<match key="system.hardware.vendor" string="LENOVO">
<merge key="power_management.quirk.s3_mode" type="bool">true</merge>
<merge key="power_management.quirk.s3_bios" type="bool">false</merge>
<merge key="power_management.quirk.save_pci" type="bool">true</merge>
</match>
</device>
</deviceinfo>
</pre>

Also you want to set the following parameter in

{{path|/etc/default/acpi-support}}
<pre>
SAVE_VIDEO_PCI_STATE=true
</pre>

{{NOTE|This works for me with mode 6460, except for one problem: You may get a white screen in xorg after resume when using compiz. If you don't have a 6460 with nvidia this file may break things for you because it doesn't care about the modell and sets the parameter for any lenovo product}}
{{HELP|Anyone with more knowledge of hal and acpi-support is welcome to clean this up. I also don't know why this setting can be done via hal and in acpi-support.
See below!}}

'''Working on hardy final'''

After trying out all these recipes on my 6457CTO waking up from suspend still did not work. Finally I came across a blog entry which pointed out the right way: [[http://david.goodlad.ca/2008/3/14/suspend-hibernate-on-lenovo-t61 David Goodlad's blog]]. I realized that all the fixes proposing editing the acpi-support file or adding a kernel parameter acpi_sleep=s3_mode must be wrong because since hardy gnome-power-manager gets its information solely from hal. So setting up correct hal information is the right way but the proposed solution (creating a /etc/hal/fdi/information/lenovo.fdi file) did not work for me. Ok, but now step by step:

# Revert ALL the proposed fixes from above. I found out that at least the lenovo.fdi solution is actually breaking the real fix. So for sure delete /etc/hal/fdi/information/lenovo.fdi
# Find out about the excact hal name of your machine: <pre>hal-device |grep 6457</pre> where 6457 is the model number of my t61, replace it with your own. In my case it spits out something like this: system.hardware.product = '6457CTO'. So now I know that hal identifies my machine as 6457CTO.
# <pre>sudo gedit /usr/share/hal/fdi/information/10freedesktop/20-video-quirk-pm-lenovo.fdi</pre> and add a section to the end of the file, just above the </device> tag and replace 6457CTO with your hal device name:
<pre>

<match key="system.hardware.product" string="6457CTO">

<merge key="power_management.quirk.s3_mode" type="bool">true</merge>
<merge key="power_management.quirk.s3_bios" type="bool">false</merge>
<merge key="power_management.quirk.save_pci" type="bool">true</merge>
</match>
</pre>

Now save and reboot. Now you might run into the problem of coming back from resume into a completely white screen where normally should be the password dialog. Entering your password blindly is not nice but at least you can resume.

{{NOTE|Somehow I couldn't make the wildcard matching work as they did in the lenovo.fdi solution, but that might be due to my shortcomings on that syntax. Anyway matching the device by its full name worked for me. Probably somebody who knows more about the matching could make that wildcard thing work to have a more general solution. Because hal also knows the xorg driver name (info.linux.driver) there should be a way to set up the quirks depending on the driver.}}

[[Category: T61]]

=== TrackPoint ===
The [[TrackPoint]] works out of the box, but does not scroll nor does the tap-clicking (press to select) feature work. Therefor see: [[#tap-to-click feature]] To enable using the middle mouse button to scroll, replace the "Configured Mouse" section in {{path|/etc/X11/xorg.conf}} with the following:
<pre>
Section "InputDevice"
Identifier "Trackpoint"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ImPS/2"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "true"
Option "EmulateWheel" "true"
Option "EmulateWheelButton" "2"
EndSection
</pre>

{{NOTE|However, if you need to use external usb mouse, the above configuration is wrong. It will cause odd behavior. Try the following configuration from [http://gentoo-wiki.com/HARDWARE_IBM_Specific_Laptop_Guide#TrackPoint Gentoo Wiki]:}}
<pre>
Section "InputDevice"
Identifier "UltraNav TrackPoint"
Driver "mouse"
Option "Device" "/dev/input/mouse1"
Option "Protocol" "ExplorerPS/2"
Option "Emulate3Buttons" "on"
Option "Emulate3TimeOut" "50"
Option "EmulateWheel" "on"
Option "EmulateWheelTimeOut" "200"
Option "EmulateWheelButton" "2"
Option "YAxisMapping" "4 5"
Option "XAxisMapping" "6 7"
Option "ZAxisMapping" "4 5"
EndSection
</pre>

=== Audio ===

Works great out of the box, just the microphone has to be activated, it is considered a generic capture source and is muted by default.

To unmute the microphone:

*Right Click on the volume icon next to the clock and click on "Open Volume Control"

*Click Edit -> Preferences. A list of devices will be displayed, you should check the following (Do not uncheck any existing items):

Input Source
Capture

*Click Close and there should be two additional tabs "Recording" and "Options". -

*Click Recording and click on the microphone under the Capture slider so that it no longer has a red line through it, and put the slider up as it may be deactivated.

*Click Options and under capture source select internal mic.

To test your mic using Sound Recorder select Capture as the sound source.

This solution has been tested with Sound Recorder and Skype.

To get the volume controls working:

*add the following line to /etc/modprobe.d/alsa-base, then reboot

options snd-hda-intel index=0 model=thinkpad

{{NOTE|The volume controls worked fine for me out of the box on a 6460.}}

=== Multimedia Keys ===

Most Multimedia Keys work out of the box, just the play, forward and stop buttons need to be adjusted, therefore, press alt + F2 and type in gnome-keybinding-properties. Then everything works as followed:

* Fn-PgUp activates/deactivates the thinklight
* Fn-Up will trigger stop on a media player
* Fn-Down will toggle pause and play on a media player
* Fn-Left/Right go to prev/next tracks on a media player
* Fn-F2 properly locks the screen
* Fn-F3 shows remaining battery >>does not work on all machines<<
* Fn-F4 suspends (to ram)
* Fn-F9 ejects cds >>does not work on all machines, I think this is supposed to eject from a "dock"<<
* Fn-F12 hibernates (to disk)
* PrtSc opens the screenshot dialog

To enable the back, forward, and the menu keys you'll need to teach XKB what they are.

* Check the '''XkbLayout''' option (under '''InputDevice''') in your {{path|/etc/X11/xorg.conf}} file to determine which keyboard layout Ubuntu is using (I'll use 'us' for the example).
* Navigate to {{path|/etc/X11/xkb/symbols}} and, as root, open the appropriate layout file (as determined above) in your favorite editor.
{{cmduser|cd /etc/X11/xkb/symbols}}
{{cmduser|sudo gedit us}}
* In the '''xkb_symbols "basic"''' section after the '''name[Group1]= "x";''' (where x is a country name, or similar) line add the following:
key <I63> { [ Menu ] };
key <I69> { [ XF86Forward ] };
key <I6A> { [ XF86Back ] };
* Now log out and back in and all three of the buttons should function.

=== Thinkpad Button ===

Paste the following into /usr/share/hotkey-setup/ibm.hk
setkeycodes e017 148 # thinkpad button
You can also just type this into a terminal, to test it for the time of the current session.

Paste the following into the right file in /usr/share/xmodmap (check your country code)
keycode 159 = XF86Terminal
For immediate availability of the button, reload the file by executing
xmodmap <xmodmap.file>

Then use the "Keyboard Shortcuts" tool under "Preferences".

== Items that don't work (a.k.a.: items that need more intense tweaking to get fixed)==

=== tap-to-click feature ===

For the tap-to-click feature (taping the stick instead of using the left mouse button) i used a configure trackpoint utility: [http://tpctl.sourceforge.net/configure-trackpoint.html] there is a package for ubuntu 7.04 i386, but i compiled it by myself (using amd64):

1.) download the .tar.gz file

2.) unpack it

3.) install libgnomeui-dev

{{cmduser|sudo aptitude install libgnomeui-dev}}

4.) in the folder, do:

{{cmduser|./configure}}

if everything worked fine:

{{cmduser|make}}

then install it:

{{cmduser|sudo make install}}

5.a) Gnome : Open it: System > configure trackpoint, and configure on your needs

5.b) Kde : K-menu > Prefences > configure trackpoint > right-click > edit entry, edit "command" to "kdesu configure-trackpoint"

Save & exit

Open it : K-menu > Prefences > configure trackpoint and configure on your needs

=== Hotswapping ===

{{HELP|We need someone who is able to get hotswaping to work properly, this is not the right was to do this!}}
With the new kernel, bay-drivers changed, so if you remove the ultrabay it will freeze your system! You can hack it with a simple comand, first you have to look where the device is:

{{cmduser|less /sys/class/scsi_device/(x)\:0\:0\:0/device/model}}

for (x) first put in 0, if it tells you DVD or the name of the model you want to hotswap youre right. if not, go on with 1, 2 or 3...

then, once you are sure (I deactivated my harddisk like that) you put in:

{{cmduser|echo 1 {{!}} sudo tee /sys/class/scsi_device/(x)\:0\:0\:0/device/delete}}

Now you should be able to remove the device.

{{WARN|Do not use it for harddisks, be sure you unmounted it before! This is just a bad hack, if anyone knows how to get it right --> publish!}}

If Ubuntu does not reactivate the device after putting it in again, do:

{{cmduser|echo 0 0 0 {{!}} sudo tee /sys/class/scsi_host/host1/scan}}

=== Wireless activity LED ===

The LED is not implemented at least in the IWL4965 driver. For the Atheros wifi cards look at the solution below.

A patch posted in this [http://bughost.org/bugzilla/show_bug.cgi?id=1209 thread] works for me on R61 with IWL4965 card.

{{HELP|A howto is needed showing the process of implementing the patch in Hardy Heron. If anyone knows how to do this, please create a quick howto and either put it here or link to it from this page. Please and thank you.}}

As an alternative, you can install a backported IWL4965 driver that ''may'' fix the LED problem on your system.

To active WiFi LED,

sudo apt-get install linux-backports-modules-hardy

{{NOTE|On some machines, (at least one running IWL3945 & IWL4965) applying the above turns on the LED permanently. It should flicker as data is being transmitted. Also, with the above modification, after turning off wireless and then turning it back on (via the switch on the front of the machine) wireless is not reactivated, so not very helpful}}

You can download a compatible [http://wireless.kernel.org/download/compat-wireless-2.6/compat-wireless-2.6.tar.bz2 driver] which supports WiFi led flicking and build it with modifying the {{path|config.mk}} by adding {{bootparm|CONFIG_IWL3945_LEDS|y}} and {{bootparm|CONFIG_IWLWIFI_LEDS|y}} these two options. For Ubuntu/Debian users, build-essential, linux-source-2.6.24 and linux-headers-generic packages are required.

{{HELP|I added the above lines to the config.mk file and it would not make or make install correctly. I received an error 2 at the end of the make. If you have had success, where did you put the items in the config.mk file for it to make and make install correctly? Thanks in advance.}}

'''To enable the Wifi LED with the Atheros cards'''

1) Create a file ~/wifiLED and copy/paste the following into it:

#!/bin/bash
#
# Commands to enable the wireless LED
sysctl dev.wifi0.ledpin=1
sysctl dev.wifi0.softled=3

2) sudo cp ~/wifiLED /etc/init.d
3) sudo chmod 755 /etc/init.d/wifiLED
4) sudo update-rc.d wifiLED defaults 90

=== Hidden SSID ===
It has been reported that users wanting to access Hidden SSIDs have to enter the SSID and password manually in Network Manager to connect. Even after the SSID is saved in Network Manager, it will not reconnect automatically. The user has to connect manually by entering the information as previously described.
It appears that updating the driver by following the instructions [http://linuxwireless.org/en/users/Download here] resolves this issue.

=== Hard Disk Parking ===
Getting hard disk parking to work:

tp_smapi patch is not needed in [http://packages.ubuntu.com/search?keywords=linux-image-2.6.24-18&searchon=names&suite=hardy&section=all linux-image-2.6.24-18]

1. Patch your kernel with the 'protect' [http://www.thinkwiki.org/wiki/HDAPS#Kernel_patch patch].

2. Installing the hdapsd daemon which does the actual parking.

{{cmduser|sudo apt-get install hdapsd hdaps-utils}}

== some other tweaks ==

=== screenblank with {{key|Fn}} + {{key|F3}} ===

Its ok, and might be usefull to get the estimated batterytime when pressing {{key|Fn}}+{{key|F3}}, as it should be. But i dont need that, i find the earlier command for {{key|F3}}, to blank the screen, more useful to save batterylife better.

For that, you must edit {{path|/etc/acpi/thinkpad-lockbattery.sh}} and replace LENOVO by IBM, and IBM by LENOVO :). Do not forget to copy the file before you change it!

=== Enable normal User to Limit CPU Speed ===
To let user set the CPU limit you need to open a Terminal an type there
sudo dpkg-reconfigure gnome-applets
answer the question with yes

=== Fix bluish WSXGA+ displays ===
Many T61 owners complain about a very bluish color temperature: My T61 WSXGA+ was also way too blue. I came across a thread at the notebook review forum http://forum.notebookreview.com/showthread.php?t=174408 which provided two useful ICC profiles which fixed the situation for me. Just install xcalib
sudo apt-get install xcalib
and load one of these profiles.

[[Category: Ubuntu 8.04]]

Installing Ubuntu 8.04 (Hardy Heron) on a ThinkPad T61

2008-07-24T12:33:55Z

Lunatico: /* Enable normal User to Limit CPU Speed */

== Items that work out of the box ==

'''Intel Video:''' 2D and 3D acceleration works

'''Nvidia Video:''' 2D and 3D acceleration works

'''Wireless:''' Intel cards tested. Atheros cards also works.

'''Wireless WAN:''' Cingular/AT&T card tested.

'''Network Card''' Intel 10/100/1000 tested

'''Wireless switch''' Tested

'''Webcam''' Tested with cheese and skype.

'''Headphones''' Works out of the box

'''Microphone''' Just needs to be activated, see section [[#Audio|below]]

'''Keyboard Shortcuts:''' Most of them work out of the box, some need to be activated, see section [[#Multimedia_Keys|below]]

== Items that need (some) tweaking to obtain full functionality ==

=== Open Source Intel Wifi Driver ===
The following information is important if you are upgrading from a previous version of Ubuntu to 8.04.

Intel has created a new Linux Wifi driver project for Intel Wireless cards, "[[Iwlwifi]]". This driver is Open Source and no longer requires the Intel daemon to run in addition. This project will support the [[:Category:T61 | T61]]'s Wifi [[Intel PRO/Wireless 3945ABG Mini-PCI Express Adapter | Intel 3945ABG network adapter]] and [[Intel PRO/Wireless 4965AGN Mini-PCI Express Adapter| Intel 4965AGN network adapter]].

An automatic migration will occur when upgrading from [[Installing Ubuntu 7.10 (Gutsy Gibbon) on a ThinkPad T61|Ubuntu 7.10]] to Ubuntu 8.04. However, there is a caveat to be aware of:
* The new driver wants to name the interface wlan0 (by default -- you can rename it to anything you want), and requires a different entry in {{path|/etc/udev/rules.d/70-persistent-net.rules}}, which handles the naming of interfaces. Simply edit this file and delete your old entry for the ipw3945 driver, then unload/reload the new driver, or simply reboot. A new entry will automatically be created that is appropriate for the new driver. Here's an example of the lines to delete:
<pre>
# PCI device 0x8086:0x4227 (ipw3945)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:1b:77:a4:0e:2f", NAME="eth1"
</pre>

If you need to perform a manual migration, the Ubuntu Help Community has written some [https://help.ubuntu.com/community/WifiDocs/Driver/iwlwifi_Intel_3945_4965/gutsy documentation] that will make this very easy to do.

=== Compiz and XV Playback on Intel GM965/GL960 ===

With Ubuntu 7.10 (Gutsy Gibbon) you currently have to choose between using Compiz and working video playback using XV. On 8.04 (Hardy Heron) alpha 5 you can play videos using XV under compiz, it works right out of the box using the Live-CD.

=== Suspend with Nv140m ===

** Update as of July 17th 2008 -- Using 8.04.1 with the newest nvidea drivers, I had no problems suspending without any additional configuration. **

Suspend may not work even after editing acpi-support. Enable bluetooth (Fn+F5) may result in a successful suspend. NOTE: that although the wifi led does not change when Fn+F5 is used, the wifi is still toggled by this key.

'''Hal "S3 BIOS" parameter issue!'''

After doing the changes to the /etc/default/acpi-support file (described [http://www.thinkwiki.org/wiki/Installing_Ubuntu_7.10_(Gutsy_Gibbon)_on_a_ThinkPad_T61#How_to_Suspend_with_nVidia_140m.2F570m here]), I for one, managed to have '''stable''' suspend support by creating a new file called: '''/etc/hal/fdi/information/lenovo.fdi''' with the following contents:
<pre>
<?xml version="1.0" encoding="ISO-8859-1"?> 
<deviceinfo version="0.2">
<device>
<match key="system.hardware.vendor" string="LENOVO">
<merge key="power_management.quirk.s3_bios" type="bool">false</merge>
</match>
</device>
</deviceinfo>
</pre>
{{NOTE|The problem (after reading the HAL and pm-utils documentations) is the fact that (as far as I can tell) the T61 Lenovo doesn't allow the S3 BIOS to be called *during* suspend/resume, which HAL seems to do by default (who knows, maybe there are T61s out there that do work with this default)!

This did not seem to be necessary for previous versions of Ubuntu. Also note that I have an NVIDIA card so I have no idea what to do for Intel versions.The change should also be resistant to HAL and pm-utils upgrades.}}

'''Still no suspend with nvs140m? Got Modell 6460?'''

Fix above didn't work for me on a 15.4 wide T61 Modell 6460 with nv140m. Bios is updated to 2.14 but didn't change anything, except the usb bug is fix. Suspend seems to work fine, but resume gives me a black screen (backlight off - no reaction to brightness up) and I can hear 2 beeps. Most of the time I can reboot with ctrl+alt+delete but the screen stays dark until bios.

follow the instructions above but create the new file called: '''/etc/hal/fdi/information/lenovo.fdi''' with the following contents instead:
<pre>
<?xml version="1.0" encoding="ISO-8859-1"?> 
<deviceinfo version="0.2">
<device>
<match key="system.hardware.vendor" string="LENOVO">
<merge key="power_management.quirk.s3_mode" type="bool">true</merge>
<merge key="power_management.quirk.s3_bios" type="bool">false</merge>
<merge key="power_management.quirk.save_pci" type="bool">true</merge>
</match>
</device>
</deviceinfo>
</pre>

Also you want to set the following parameter in

{{path|/etc/default/acpi-support}}
<pre>
SAVE_VIDEO_PCI_STATE=true
</pre>

{{NOTE|This works for me with mode 6460, except for one problem: You may get a white screen in xorg after resume when using compiz. If you don't have a 6460 with nvidia this file may break things for you because it doesn't care about the modell and sets the parameter for any lenovo product}}
{{HELP|Anyone with more knowledge of hal and acpi-support is welcome to clean this up. I also don't know why this setting can be done via hal and in acpi-support.
See below!}}

'''Working on hardy final'''

After trying out all these recipes on my 6457CTO waking up from suspend still did not work. Finally I came across a blog entry which pointed out the right way: [[http://david.goodlad.ca/2008/3/14/suspend-hibernate-on-lenovo-t61 David Goodlad's blog]]. I realized that all the fixes proposing editing the acpi-support file or adding a kernel parameter acpi_sleep=s3_mode must be wrong because since hardy gnome-power-manager gets its information solely from hal. So setting up correct hal information is the right way but the proposed solution (creating a /etc/hal/fdi/information/lenovo.fdi file) did not work for me. Ok, but now step by step:

# Revert ALL the proposed fixes from above. I found out that at least the lenovo.fdi solution is actually breaking the real fix. So for sure delete /etc/hal/fdi/information/lenovo.fdi
# Find out about the excact hal name of your machine: <pre>hal-device |grep 6457</pre> where 6457 is the model number of my t61, replace it with your own. In my case it spits out something like this: system.hardware.product = '6457CTO'. So now I know that hal identifies my machine as 6457CTO.
# <pre>sudo gedit /usr/share/hal/fdi/information/10freedesktop/20-video-quirk-pm-lenovo.fdi</pre> and add a section to the end of the file, just above the </device> tag and replace 6457CTO with your hal device name:
<pre>

<match key="system.hardware.product" string="6457CTO">

<merge key="power_management.quirk.s3_mode" type="bool">true</merge>
<merge key="power_management.quirk.s3_bios" type="bool">false</merge>
<merge key="power_management.quirk.save_pci" type="bool">true</merge>
</match>
</pre>

Now save and reboot. Now you might run into the problem of coming back from resume into a completely white screen where normally should be the password dialog. Entering your password blindly is not nice but at least you can resume.

{{NOTE|Somehow I couldn't make the wildcard matching work as they did in the lenovo.fdi solution, but that might be due to my shortcomings on that syntax. Anyway matching the device by its full name worked for me. Probably somebody who knows more about the matching could make that wildcard thing work to have a more general solution. Because hal also knows the xorg driver name (info.linux.driver) there should be a way to set up the quirks depending on the driver.}}

[[Category: T61]]

=== TrackPoint ===
The [[TrackPoint]] works out of the box, but does not scroll nor does the tap-clicking (press to select) feature work. Therefor see: [[#tap-to-click feature]] To enable using the middle mouse button to scroll, replace the "Configured Mouse" section in {{path|/etc/X11/xorg.conf}} with the following:
<pre>
Section "InputDevice"
Identifier "Trackpoint"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ImPS/2"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "true"
Option "EmulateWheel" "true"
Option "EmulateWheelButton" "2"
EndSection
</pre>

{{NOTE|However, if you need to use external usb mouse, the above configuration is wrong. It will cause odd behavior. Try the following configuration from [http://gentoo-wiki.com/HARDWARE_IBM_Specific_Laptop_Guide#TrackPoint Gentoo Wiki]:}}
<pre>
Section "InputDevice"
Identifier "UltraNav TrackPoint"
Driver "mouse"
Option "Device" "/dev/input/mouse1"
Option "Protocol" "ExplorerPS/2"
Option "Emulate3Buttons" "on"
Option "Emulate3TimeOut" "50"
Option "EmulateWheel" "on"
Option "EmulateWheelTimeOut" "200"
Option "EmulateWheelButton" "2"
Option "YAxisMapping" "4 5"
Option "XAxisMapping" "6 7"
Option "ZAxisMapping" "4 5"
EndSection
</pre>

=== Audio ===

Works great out of the box, just the microphone has to be activated, it is considered a generic capture source and is muted by default.

To unmute the microphone:

*Right Click on the volume icon next to the clock and click on "Open Volume Control"

*Click Edit -> Preferences. A list of devices will be displayed, you should check the following (Do not uncheck any existing items):

Input Source
Capture

*Click Close and there should be two additional tabs "Recording" and "Options". -

*Click Recording and click on the microphone under the Capture slider so that it no longer has a red line through it, and put the slider up as it may be deactivated.

*Click Options and under capture source select internal mic.

To test your mic using Sound Recorder select Capture as the sound source.

This solution has been tested with Sound Recorder and Skype.

To get the volume controls working:

*add the following line to /etc/modprobe.d/alsa-base, then reboot

options snd-hda-intel index=0 model=thinkpad

{{NOTE|The volume controls worked fine for me out of the box on a 6460.}}

=== Multimedia Keys ===

Most Multimedia Keys work out of the box, just the play, forward and stop buttons need to be adjusted, therefore, press alt + F2 and type in gnome-keybinding-properties. Then everything works as followed:

* Fn-PgUp activates/deactivates the thinklight
* Fn-Up will trigger stop on a media player
* Fn-Down will toggle pause and play on a media player
* Fn-Left/Right go to prev/next tracks on a media player
* Fn-F2 properly locks the screen
* Fn-F3 shows remaining battery >>does not work on all machines<<
* Fn-F4 suspends (to ram)
* Fn-F9 ejects cds >>does not work on all machines, I think this is supposed to eject from a "dock"<<
* Fn-F12 hibernates (to disk)
* PrtSc opens the screenshot dialog

To enable the back, forward, and the menu keys you'll need to teach XKB what they are.

* Check the '''XkbLayout''' option (under '''InputDevice''') in your {{path|/etc/X11/xorg.conf}} file to determine which keyboard layout Ubuntu is using (I'll use 'us' for the example).
* Navigate to {{path|/etc/X11/xkb/symbols}} and, as root, open the appropriate layout file (as determined above) in your favorite editor.
{{cmduser|cd /etc/X11/xkb/symbols}}
{{cmduser|sudo gedit us}}
* In the '''xkb_symbols "basic"''' section after the '''name[Group1]= "x";''' (where x is a country name, or similar) line add the following:
key <I63> { [ Menu ] };
key <I69> { [ XF86Forward ] };
key <I6A> { [ XF86Back ] };
* Now log out and back in and all three of the buttons should function.

=== Thinkpad Button ===

Paste the following into /usr/share/hotkey-setup/ibm.hk
setkeycodes e017 148 # thinkpad button
You can also just type this into a terminal, to test it for the time of the current session.

Paste the following into the right file in /usr/share/xmodmap (check your country code)
keycode 159 = XF86Terminal
For immediate availability of the button, reload the file by executing
xmodmap <xmodmap.file>

Then use the "Keyboard Shortcuts" tool under "Preferences".

== Items that don't work (a.k.a.: items that need more intense tweaking to get fixed)==

=== tap-to-click feature ===

For the tap-to-click feature (taping the stick instead of using the left mouse button) i used a configure trackpoint utility: [http://tpctl.sourceforge.net/configure-trackpoint.html] there is a package for ubuntu 7.04 i386, but i compiled it by myself (using amd64):

1.) download the .tar.gz file

2.) unpack it

3.) install libgnomeui-dev

{{cmduser|sudo aptitude install libgnomeui-dev}}

4.) in the folder, do:

{{cmduser|./configure}}

if everything worked fine:

{{cmduser|make}}

then install it:

{{cmduser|sudo make install}}

5.a) Gnome : Open it: System > configure trackpoint, and configure on your needs

5.b) Kde : K-menu > Prefences > configure trackpoint > right-click > edit entry, edit "command" to "kdesu configure-trackpoint"

Save & exit

Open it : K-menu > Prefences > configure trackpoint and configure on your needs

=== Hotswapping ===

{{HELP|We need someone who is able to get hotswaping to work properly, this is not the right was to do this!}}
With the new kernel, bay-drivers changed, so if you remove the ultrabay it will freeze your system! You can hack it with a simple comand, first you have to look where the device is:

{{cmduser|less /sys/class/scsi_device/(x)\:0\:0\:0/device/model}}

for (x) first put in 0, if it tells you DVD or the name of the model you want to hotswap youre right. if not, go on with 1, 2 or 3...

then, once you are sure (I deactivated my harddisk like that) you put in:

{{cmduser|echo 1 {{!}} sudo tee /sys/class/scsi_device/(x)\:0\:0\:0/device/delete}}

Now you should be able to remove the device.

{{WARN|Do not use it for harddisks, be sure you unmounted it before! This is just a bad hack, if anyone knows how to get it right --> publish!}}

If Ubuntu does not reactivate the device after putting it in again, do:

{{cmduser|echo 0 0 0 {{!}} sudo tee /sys/class/scsi_host/host1/scan}}

=== Wireless activity LED ===

The LED is not implemented at least in the IWL4965 driver. For the Atheros wifi cards look at the solution below.

A patch posted in this [http://bughost.org/bugzilla/show_bug.cgi?id=1209 thread] works for me on R61 with IWL4965 card.

{{HELP|A howto is needed showing the process of implementing the patch in Hardy Heron. If anyone knows how to do this, please create a quick howto and either put it here or link to it from this page. Please and thank you.}}

As an alternative, you can install a backported IWL4965 driver that ''may'' fix the LED problem on your system.

To active WiFi LED,

sudo apt-get install linux-backports-modules-hardy

{{NOTE|On some machines, (at least one running IWL3945 & IWL4965) applying the above turns on the LED permanently. It should flicker as data is being transmitted. Also, with the above modification, after turning off wireless and then turning it back on (via the switch on the front of the machine) wireless is not reactivated, so not very helpful}}

You can download a compatible [http://wireless.kernel.org/download/compat-wireless-2.6/compat-wireless-2.6.tar.bz2 driver] which supports WiFi led flicking and build it with modifying the {{path|config.mk}} by adding {{bootparm|CONFIG_IWL3945_LEDS|y}} and {{bootparm|CONFIG_IWLWIFI_LEDS|y}} these two options. For Ubuntu/Debian users, build-essential, linux-source-2.6.24 and linux-headers-generic packages are required.

{{HELP|I added the above lines to the config.mk file and it would not make or make install correctly. I received an error 2 at the end of the make. If you have had success, where did you put the items in the config.mk file for it to make and make install correctly? Thanks in advance.}}

'''To enable the Wifi LED with the Atheros cards'''

1) Create a file ~/wifiLED and copy/paste the following into it:
#!/bin/bash
#
# Commands to enable the wireless LED
sysctl dev.wifi0.ledpin=1
sysctl dev.wifi0.softled=3
2) sudo cp ~/wifiLED /etc/init.d
3) sudo chmod 755 /etc/init.d/wifiLED
4) sudo update-rc.d wifiLED defaults 90

=== Hidden SSID ===
It has been reported that users wanting to access Hidden SSIDs have to enter the SSID and password manually in Network Manager to connect. Even after the SSID is saved in Network Manager, it will not reconnect automatically. The user has to connect manually by entering the information as previously described.
It appears that updating the driver by following the instructions [http://linuxwireless.org/en/users/Download here] resolves this issue.

=== Hard Disk Parking ===
Getting hard disk parking to work:

tp_smapi patch is not needed in [http://packages.ubuntu.com/search?keywords=linux-image-2.6.24-18&searchon=names&suite=hardy&section=all linux-image-2.6.24-18]

1. Patch your kernel with the 'protect' [http://www.thinkwiki.org/wiki/HDAPS#Kernel_patch patch].

2. Installing the hdapsd daemon which does the actual parking.

{{cmduser|sudo apt-get install hdapsd hdaps-utils}}

== some other tweaks ==

=== screenblank with {{key|Fn}} + {{key|F3}} ===

Its ok, and might be usefull to get the estimated batterytime when pressing {{key|Fn}}+{{key|F3}}, as it should be. But i dont need that, i find the earlier command for {{key|F3}}, to blank the screen, more useful to save batterylife better.

For that, you must edit {{path|/etc/acpi/thinkpad-lockbattery.sh}} and replace LENOVO by IBM, and IBM by LENOVO :). Do not forget to copy the file before you change it!

=== Enable normal User to Limit CPU Speed ===
To let user set the CPU limit you need to open a Terminal an type there
sudo dpkg-reconfigure gnome-applets
answer the question with yes

=== Fix bluish WSXGA+ displays ===
Many T61 owners complain about a very bluish color temperature: My T61 WSXGA+ was also way too blue. I came across a thread at the notebook review forum http://forum.notebookreview.com/showthread.php?t=174408 which provided two useful ICC profiles which fixed the situation for me. Just install xcalib
sudo apt-get install xcalib
and load one of these profiles.

[[Category: Ubuntu 8.04]]

Installing Ubuntu 8.04 (Hardy Heron) on a ThinkPad T61

2008-07-24T12:32:40Z

Lunatico: /* Wireless activity LED */

== Items that work out of the box ==

'''Intel Video:''' 2D and 3D acceleration works

'''Nvidia Video:''' 2D and 3D acceleration works

'''Wireless:''' Intel cards tested. Atheros cards also works.

'''Wireless WAN:''' Cingular/AT&T card tested.

'''Network Card''' Intel 10/100/1000 tested

'''Wireless switch''' Tested

'''Webcam''' Tested with cheese and skype.

'''Headphones''' Works out of the box

'''Microphone''' Just needs to be activated, see section [[#Audio|below]]

'''Keyboard Shortcuts:''' Most of them work out of the box, some need to be activated, see section [[#Multimedia_Keys|below]]

== Items that need (some) tweaking to obtain full functionality ==

=== Open Source Intel Wifi Driver ===
The following information is important if you are upgrading from a previous version of Ubuntu to 8.04.

Intel has created a new Linux Wifi driver project for Intel Wireless cards, "[[Iwlwifi]]". This driver is Open Source and no longer requires the Intel daemon to run in addition. This project will support the [[:Category:T61 | T61]]'s Wifi [[Intel PRO/Wireless 3945ABG Mini-PCI Express Adapter | Intel 3945ABG network adapter]] and [[Intel PRO/Wireless 4965AGN Mini-PCI Express Adapter| Intel 4965AGN network adapter]].

An automatic migration will occur when upgrading from [[Installing Ubuntu 7.10 (Gutsy Gibbon) on a ThinkPad T61|Ubuntu 7.10]] to Ubuntu 8.04. However, there is a caveat to be aware of:
* The new driver wants to name the interface wlan0 (by default -- you can rename it to anything you want), and requires a different entry in {{path|/etc/udev/rules.d/70-persistent-net.rules}}, which handles the naming of interfaces. Simply edit this file and delete your old entry for the ipw3945 driver, then unload/reload the new driver, or simply reboot. A new entry will automatically be created that is appropriate for the new driver. Here's an example of the lines to delete:
<pre>
# PCI device 0x8086:0x4227 (ipw3945)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:1b:77:a4:0e:2f", NAME="eth1"
</pre>

If you need to perform a manual migration, the Ubuntu Help Community has written some [https://help.ubuntu.com/community/WifiDocs/Driver/iwlwifi_Intel_3945_4965/gutsy documentation] that will make this very easy to do.

=== Compiz and XV Playback on Intel GM965/GL960 ===

With Ubuntu 7.10 (Gutsy Gibbon) you currently have to choose between using Compiz and working video playback using XV. On 8.04 (Hardy Heron) alpha 5 you can play videos using XV under compiz, it works right out of the box using the Live-CD.

=== Suspend with Nv140m ===

** Update as of July 17th 2008 -- Using 8.04.1 with the newest nvidea drivers, I had no problems suspending without any additional configuration. **

Suspend may not work even after editing acpi-support. Enable bluetooth (Fn+F5) may result in a successful suspend. NOTE: that although the wifi led does not change when Fn+F5 is used, the wifi is still toggled by this key.

'''Hal "S3 BIOS" parameter issue!'''

After doing the changes to the /etc/default/acpi-support file (described [http://www.thinkwiki.org/wiki/Installing_Ubuntu_7.10_(Gutsy_Gibbon)_on_a_ThinkPad_T61#How_to_Suspend_with_nVidia_140m.2F570m here]), I for one, managed to have '''stable''' suspend support by creating a new file called: '''/etc/hal/fdi/information/lenovo.fdi''' with the following contents:
<pre>
<?xml version="1.0" encoding="ISO-8859-1"?> 
<deviceinfo version="0.2">
<device>
<match key="system.hardware.vendor" string="LENOVO">
<merge key="power_management.quirk.s3_bios" type="bool">false</merge>
</match>
</device>
</deviceinfo>
</pre>
{{NOTE|The problem (after reading the HAL and pm-utils documentations) is the fact that (as far as I can tell) the T61 Lenovo doesn't allow the S3 BIOS to be called *during* suspend/resume, which HAL seems to do by default (who knows, maybe there are T61s out there that do work with this default)!

This did not seem to be necessary for previous versions of Ubuntu. Also note that I have an NVIDIA card so I have no idea what to do for Intel versions.The change should also be resistant to HAL and pm-utils upgrades.}}

'''Still no suspend with nvs140m? Got Modell 6460?'''

Fix above didn't work for me on a 15.4 wide T61 Modell 6460 with nv140m. Bios is updated to 2.14 but didn't change anything, except the usb bug is fix. Suspend seems to work fine, but resume gives me a black screen (backlight off - no reaction to brightness up) and I can hear 2 beeps. Most of the time I can reboot with ctrl+alt+delete but the screen stays dark until bios.

follow the instructions above but create the new file called: '''/etc/hal/fdi/information/lenovo.fdi''' with the following contents instead:
<pre>
<?xml version="1.0" encoding="ISO-8859-1"?> 
<deviceinfo version="0.2">
<device>
<match key="system.hardware.vendor" string="LENOVO">
<merge key="power_management.quirk.s3_mode" type="bool">true</merge>
<merge key="power_management.quirk.s3_bios" type="bool">false</merge>
<merge key="power_management.quirk.save_pci" type="bool">true</merge>
</match>
</device>
</deviceinfo>
</pre>

Also you want to set the following parameter in

{{path|/etc/default/acpi-support}}
<pre>
SAVE_VIDEO_PCI_STATE=true
</pre>

{{NOTE|This works for me with mode 6460, except for one problem: You may get a white screen in xorg after resume when using compiz. If you don't have a 6460 with nvidia this file may break things for you because it doesn't care about the modell and sets the parameter for any lenovo product}}
{{HELP|Anyone with more knowledge of hal and acpi-support is welcome to clean this up. I also don't know why this setting can be done via hal and in acpi-support.
See below!}}

'''Working on hardy final'''

After trying out all these recipes on my 6457CTO waking up from suspend still did not work. Finally I came across a blog entry which pointed out the right way: [[http://david.goodlad.ca/2008/3/14/suspend-hibernate-on-lenovo-t61 David Goodlad's blog]]. I realized that all the fixes proposing editing the acpi-support file or adding a kernel parameter acpi_sleep=s3_mode must be wrong because since hardy gnome-power-manager gets its information solely from hal. So setting up correct hal information is the right way but the proposed solution (creating a /etc/hal/fdi/information/lenovo.fdi file) did not work for me. Ok, but now step by step:

# Revert ALL the proposed fixes from above. I found out that at least the lenovo.fdi solution is actually breaking the real fix. So for sure delete /etc/hal/fdi/information/lenovo.fdi
# Find out about the excact hal name of your machine: <pre>hal-device |grep 6457</pre> where 6457 is the model number of my t61, replace it with your own. In my case it spits out something like this: system.hardware.product = '6457CTO'. So now I know that hal identifies my machine as 6457CTO.
# <pre>sudo gedit /usr/share/hal/fdi/information/10freedesktop/20-video-quirk-pm-lenovo.fdi</pre> and add a section to the end of the file, just above the </device> tag and replace 6457CTO with your hal device name:
<pre>

<match key="system.hardware.product" string="6457CTO">

<merge key="power_management.quirk.s3_mode" type="bool">true</merge>
<merge key="power_management.quirk.s3_bios" type="bool">false</merge>
<merge key="power_management.quirk.save_pci" type="bool">true</merge>
</match>
</pre>

Now save and reboot. Now you might run into the problem of coming back from resume into a completely white screen where normally should be the password dialog. Entering your password blindly is not nice but at least you can resume.

{{NOTE|Somehow I couldn't make the wildcard matching work as they did in the lenovo.fdi solution, but that might be due to my shortcomings on that syntax. Anyway matching the device by its full name worked for me. Probably somebody who knows more about the matching could make that wildcard thing work to have a more general solution. Because hal also knows the xorg driver name (info.linux.driver) there should be a way to set up the quirks depending on the driver.}}

[[Category: T61]]

=== TrackPoint ===
The [[TrackPoint]] works out of the box, but does not scroll nor does the tap-clicking (press to select) feature work. Therefor see: [[#tap-to-click feature]] To enable using the middle mouse button to scroll, replace the "Configured Mouse" section in {{path|/etc/X11/xorg.conf}} with the following:
<pre>
Section "InputDevice"
Identifier "Trackpoint"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ImPS/2"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "true"
Option "EmulateWheel" "true"
Option "EmulateWheelButton" "2"
EndSection
</pre>

{{NOTE|However, if you need to use external usb mouse, the above configuration is wrong. It will cause odd behavior. Try the following configuration from [http://gentoo-wiki.com/HARDWARE_IBM_Specific_Laptop_Guide#TrackPoint Gentoo Wiki]:}}
<pre>
Section "InputDevice"
Identifier "UltraNav TrackPoint"
Driver "mouse"
Option "Device" "/dev/input/mouse1"
Option "Protocol" "ExplorerPS/2"
Option "Emulate3Buttons" "on"
Option "Emulate3TimeOut" "50"
Option "EmulateWheel" "on"
Option "EmulateWheelTimeOut" "200"
Option "EmulateWheelButton" "2"
Option "YAxisMapping" "4 5"
Option "XAxisMapping" "6 7"
Option "ZAxisMapping" "4 5"
EndSection
</pre>

=== Audio ===

Works great out of the box, just the microphone has to be activated, it is considered a generic capture source and is muted by default.

To unmute the microphone:

*Right Click on the volume icon next to the clock and click on "Open Volume Control"

*Click Edit -> Preferences. A list of devices will be displayed, you should check the following (Do not uncheck any existing items):

Input Source
Capture

*Click Close and there should be two additional tabs "Recording" and "Options". -

*Click Recording and click on the microphone under the Capture slider so that it no longer has a red line through it, and put the slider up as it may be deactivated.

*Click Options and under capture source select internal mic.

To test your mic using Sound Recorder select Capture as the sound source.

This solution has been tested with Sound Recorder and Skype.

To get the volume controls working:

*add the following line to /etc/modprobe.d/alsa-base, then reboot

options snd-hda-intel index=0 model=thinkpad

{{NOTE|The volume controls worked fine for me out of the box on a 6460.}}

=== Multimedia Keys ===

Most Multimedia Keys work out of the box, just the play, forward and stop buttons need to be adjusted, therefore, press alt + F2 and type in gnome-keybinding-properties. Then everything works as followed:

* Fn-PgUp activates/deactivates the thinklight
* Fn-Up will trigger stop on a media player
* Fn-Down will toggle pause and play on a media player
* Fn-Left/Right go to prev/next tracks on a media player
* Fn-F2 properly locks the screen
* Fn-F3 shows remaining battery >>does not work on all machines<<
* Fn-F4 suspends (to ram)
* Fn-F9 ejects cds >>does not work on all machines, I think this is supposed to eject from a "dock"<<
* Fn-F12 hibernates (to disk)
* PrtSc opens the screenshot dialog

To enable the back, forward, and the menu keys you'll need to teach XKB what they are.

* Check the '''XkbLayout''' option (under '''InputDevice''') in your {{path|/etc/X11/xorg.conf}} file to determine which keyboard layout Ubuntu is using (I'll use 'us' for the example).
* Navigate to {{path|/etc/X11/xkb/symbols}} and, as root, open the appropriate layout file (as determined above) in your favorite editor.
{{cmduser|cd /etc/X11/xkb/symbols}}
{{cmduser|sudo gedit us}}
* In the '''xkb_symbols "basic"''' section after the '''name[Group1]= "x";''' (where x is a country name, or similar) line add the following:
key <I63> { [ Menu ] };
key <I69> { [ XF86Forward ] };
key <I6A> { [ XF86Back ] };
* Now log out and back in and all three of the buttons should function.

=== Thinkpad Button ===

Paste the following into /usr/share/hotkey-setup/ibm.hk
setkeycodes e017 148 # thinkpad button
You can also just type this into a terminal, to test it for the time of the current session.

Paste the following into the right file in /usr/share/xmodmap (check your country code)
keycode 159 = XF86Terminal
For immediate availability of the button, reload the file by executing
xmodmap <xmodmap.file>

Then use the "Keyboard Shortcuts" tool under "Preferences".

== Items that don't work (a.k.a.: items that need more intense tweaking to get fixed)==

=== tap-to-click feature ===

For the tap-to-click feature (taping the stick instead of using the left mouse button) i used a configure trackpoint utility: [http://tpctl.sourceforge.net/configure-trackpoint.html] there is a package for ubuntu 7.04 i386, but i compiled it by myself (using amd64):

1.) download the .tar.gz file

2.) unpack it

3.) install libgnomeui-dev

{{cmduser|sudo aptitude install libgnomeui-dev}}

4.) in the folder, do:

{{cmduser|./configure}}

if everything worked fine:

{{cmduser|make}}

then install it:

{{cmduser|sudo make install}}

5.a) Gnome : Open it: System > configure trackpoint, and configure on your needs

5.b) Kde : K-menu > Prefences > configure trackpoint > right-click > edit entry, edit "command" to "kdesu configure-trackpoint"

Save & exit

Open it : K-menu > Prefences > configure trackpoint and configure on your needs

=== Hotswapping ===

{{HELP|We need someone who is able to get hotswaping to work properly, this is not the right was to do this!}}
With the new kernel, bay-drivers changed, so if you remove the ultrabay it will freeze your system! You can hack it with a simple comand, first you have to look where the device is:

{{cmduser|less /sys/class/scsi_device/(x)\:0\:0\:0/device/model}}

for (x) first put in 0, if it tells you DVD or the name of the model you want to hotswap youre right. if not, go on with 1, 2 or 3...

then, once you are sure (I deactivated my harddisk like that) you put in:

{{cmduser|echo 1 {{!}} sudo tee /sys/class/scsi_device/(x)\:0\:0\:0/device/delete}}

Now you should be able to remove the device.

{{WARN|Do not use it for harddisks, be sure you unmounted it before! This is just a bad hack, if anyone knows how to get it right --> publish!}}

If Ubuntu does not reactivate the device after putting it in again, do:

{{cmduser|echo 0 0 0 {{!}} sudo tee /sys/class/scsi_host/host1/scan}}

=== Wireless activity LED ===

The LED is not implemented at least in the IWL4965 driver. For the Atheros wifi cards look at the solution below.

A patch posted in this [http://bughost.org/bugzilla/show_bug.cgi?id=1209 thread] works for me on R61 with IWL4965 card.

{{HELP|A howto is needed showing the process of implementing the patch in Hardy Heron. If anyone knows how to do this, please create a quick howto and either put it here or link to it from this page. Please and thank you.}}

As an alternative, you can install a backported IWL4965 driver that ''may'' fix the LED problem on your system.

To active WiFi LED,

sudo apt-get install linux-backports-modules-hardy

{{NOTE|On some machines, (at least one running IWL3945 & IWL4965) applying the above turns on the LED permanently. It should flicker as data is being transmitted. Also, with the above modification, after turning off wireless and then turning it back on (via the switch on the front of the machine) wireless is not reactivated, so not very helpful}}

You can download a compatible [http://wireless.kernel.org/download/compat-wireless-2.6/compat-wireless-2.6.tar.bz2 driver] which supports WiFi led flicking and build it with modifying the {{path|config.mk}} by adding {{bootparm|CONFIG_IWL3945_LEDS|y}} and {{bootparm|CONFIG_IWLWIFI_LEDS|y}} these two options. For Ubuntu/Debian users, build-essential, linux-source-2.6.24 and linux-headers-generic packages are required.

{{HELP|I added the above lines to the config.mk file and it would not make or make install correctly. I received an error 2 at the end of the make. If you have had success, where did you put the items in the config.mk file for it to make and make install correctly? Thanks in advance.}}

'''To enable the Wifi LED with the Atheros cards'''

1) Create a file ~/wifiLED and copy/paste the following into it:
#!/bin/bash
#
# Commands to enable the wireless LED
sysctl dev.wifi0.ledpin=1
sysctl dev.wifi0.softled=3
2) sudo cp ~/wifiLED /etc/init.d
3) sudo chmod 755 /etc/init.d/wifiLED
4) sudo update-rc.d wifiLED defaults 90

=== Hidden SSID ===
It has been reported that users wanting to access Hidden SSIDs have to enter the SSID and password manually in Network Manager to connect. Even after the SSID is saved in Network Manager, it will not reconnect automatically. The user has to connect manually by entering the information as previously described.
It appears that updating the driver by following the instructions [http://linuxwireless.org/en/users/Download here] resolves this issue.

=== Hard Disk Parking ===
Getting hard disk parking to work:

tp_smapi patch is not needed in [http://packages.ubuntu.com/search?keywords=linux-image-2.6.24-18&searchon=names&suite=hardy&section=all linux-image-2.6.24-18]

1. Patch your kernel with the 'protect' [http://www.thinkwiki.org/wiki/HDAPS#Kernel_patch patch].

2. Installing the hdapsd daemon which does the actual parking.

{{cmduser|sudo apt-get install hdapsd hdaps-utils}}

== some other tweaks ==

=== screenblank with {{key|Fn}} + {{key|F3}} ===

Its ok, and might be usefull to get the estimated batterytime when pressing {{key|Fn}}+{{key|F3}}, as it should be. But i dont need that, i find the earlier command for {{key|F3}}, to blank the screen, more useful to save batterylife better.

For that, you must edit {{path|/etc/acpi/thinkpad-lockbattery.sh}} and replace LENOVO by IBM, and IBM by LENOVO :). Do not forget to copy the file before you change it!

=== Enable normal User to Limit CPU Speed ===
To let user set the CPU limit you need to open a Terminal an type there
sudo dpkg-reconfigure gnome-applets
anser the question with yes

=== Fix bluish WSXGA+ displays ===
Many T61 owners complain about a very bluish color temperature: My T61 WSXGA+ was also way too blue. I came across a thread at the notebook review forum http://forum.notebookreview.com/showthread.php?t=174408 which provided two useful ICC profiles which fixed the situation for me. Just install xcalib
sudo apt-get install xcalib
and load one of these profiles.

[[Category: Ubuntu 8.04]]

Installing Ubuntu 8.04 (Hardy Heron) on a ThinkPad T61

2008-07-24T12:29:26Z

Lunatico: /* Wireless activity LED */

== Items that work out of the box ==

'''Intel Video:''' 2D and 3D acceleration works

'''Nvidia Video:''' 2D and 3D acceleration works

'''Wireless:''' Intel cards tested. Atheros cards also works.

'''Wireless WAN:''' Cingular/AT&T card tested.

'''Network Card''' Intel 10/100/1000 tested

'''Wireless switch''' Tested

'''Webcam''' Tested with cheese and skype.

'''Headphones''' Works out of the box

'''Microphone''' Just needs to be activated, see section [[#Audio|below]]

'''Keyboard Shortcuts:''' Most of them work out of the box, some need to be activated, see section [[#Multimedia_Keys|below]]

== Items that need (some) tweaking to obtain full functionality ==

=== Open Source Intel Wifi Driver ===
The following information is important if you are upgrading from a previous version of Ubuntu to 8.04.

Intel has created a new Linux Wifi driver project for Intel Wireless cards, "[[Iwlwifi]]". This driver is Open Source and no longer requires the Intel daemon to run in addition. This project will support the [[:Category:T61 | T61]]'s Wifi [[Intel PRO/Wireless 3945ABG Mini-PCI Express Adapter | Intel 3945ABG network adapter]] and [[Intel PRO/Wireless 4965AGN Mini-PCI Express Adapter| Intel 4965AGN network adapter]].

An automatic migration will occur when upgrading from [[Installing Ubuntu 7.10 (Gutsy Gibbon) on a ThinkPad T61|Ubuntu 7.10]] to Ubuntu 8.04. However, there is a caveat to be aware of:
* The new driver wants to name the interface wlan0 (by default -- you can rename it to anything you want), and requires a different entry in {{path|/etc/udev/rules.d/70-persistent-net.rules}}, which handles the naming of interfaces. Simply edit this file and delete your old entry for the ipw3945 driver, then unload/reload the new driver, or simply reboot. A new entry will automatically be created that is appropriate for the new driver. Here's an example of the lines to delete:
<pre>
# PCI device 0x8086:0x4227 (ipw3945)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:1b:77:a4:0e:2f", NAME="eth1"
</pre>

If you need to perform a manual migration, the Ubuntu Help Community has written some [https://help.ubuntu.com/community/WifiDocs/Driver/iwlwifi_Intel_3945_4965/gutsy documentation] that will make this very easy to do.

=== Compiz and XV Playback on Intel GM965/GL960 ===

With Ubuntu 7.10 (Gutsy Gibbon) you currently have to choose between using Compiz and working video playback using XV. On 8.04 (Hardy Heron) alpha 5 you can play videos using XV under compiz, it works right out of the box using the Live-CD.

=== Suspend with Nv140m ===

** Update as of July 17th 2008 -- Using 8.04.1 with the newest nvidea drivers, I had no problems suspending without any additional configuration. **

Suspend may not work even after editing acpi-support. Enable bluetooth (Fn+F5) may result in a successful suspend. NOTE: that although the wifi led does not change when Fn+F5 is used, the wifi is still toggled by this key.

'''Hal "S3 BIOS" parameter issue!'''

After doing the changes to the /etc/default/acpi-support file (described [http://www.thinkwiki.org/wiki/Installing_Ubuntu_7.10_(Gutsy_Gibbon)_on_a_ThinkPad_T61#How_to_Suspend_with_nVidia_140m.2F570m here]), I for one, managed to have '''stable''' suspend support by creating a new file called: '''/etc/hal/fdi/information/lenovo.fdi''' with the following contents:
<pre>
<?xml version="1.0" encoding="ISO-8859-1"?> 
<deviceinfo version="0.2">
<device>
<match key="system.hardware.vendor" string="LENOVO">
<merge key="power_management.quirk.s3_bios" type="bool">false</merge>
</match>
</device>
</deviceinfo>
</pre>
{{NOTE|The problem (after reading the HAL and pm-utils documentations) is the fact that (as far as I can tell) the T61 Lenovo doesn't allow the S3 BIOS to be called *during* suspend/resume, which HAL seems to do by default (who knows, maybe there are T61s out there that do work with this default)!

This did not seem to be necessary for previous versions of Ubuntu. Also note that I have an NVIDIA card so I have no idea what to do for Intel versions.The change should also be resistant to HAL and pm-utils upgrades.}}

'''Still no suspend with nvs140m? Got Modell 6460?'''

Fix above didn't work for me on a 15.4 wide T61 Modell 6460 with nv140m. Bios is updated to 2.14 but didn't change anything, except the usb bug is fix. Suspend seems to work fine, but resume gives me a black screen (backlight off - no reaction to brightness up) and I can hear 2 beeps. Most of the time I can reboot with ctrl+alt+delete but the screen stays dark until bios.

follow the instructions above but create the new file called: '''/etc/hal/fdi/information/lenovo.fdi''' with the following contents instead:
<pre>
<?xml version="1.0" encoding="ISO-8859-1"?> 
<deviceinfo version="0.2">
<device>
<match key="system.hardware.vendor" string="LENOVO">
<merge key="power_management.quirk.s3_mode" type="bool">true</merge>
<merge key="power_management.quirk.s3_bios" type="bool">false</merge>
<merge key="power_management.quirk.save_pci" type="bool">true</merge>
</match>
</device>
</deviceinfo>
</pre>

Also you want to set the following parameter in

{{path|/etc/default/acpi-support}}
<pre>
SAVE_VIDEO_PCI_STATE=true
</pre>

{{NOTE|This works for me with mode 6460, except for one problem: You may get a white screen in xorg after resume when using compiz. If you don't have a 6460 with nvidia this file may break things for you because it doesn't care about the modell and sets the parameter for any lenovo product}}
{{HELP|Anyone with more knowledge of hal and acpi-support is welcome to clean this up. I also don't know why this setting can be done via hal and in acpi-support.
See below!}}

'''Working on hardy final'''

After trying out all these recipes on my 6457CTO waking up from suspend still did not work. Finally I came across a blog entry which pointed out the right way: [[http://david.goodlad.ca/2008/3/14/suspend-hibernate-on-lenovo-t61 David Goodlad's blog]]. I realized that all the fixes proposing editing the acpi-support file or adding a kernel parameter acpi_sleep=s3_mode must be wrong because since hardy gnome-power-manager gets its information solely from hal. So setting up correct hal information is the right way but the proposed solution (creating a /etc/hal/fdi/information/lenovo.fdi file) did not work for me. Ok, but now step by step:

# Revert ALL the proposed fixes from above. I found out that at least the lenovo.fdi solution is actually breaking the real fix. So for sure delete /etc/hal/fdi/information/lenovo.fdi
# Find out about the excact hal name of your machine: <pre>hal-device |grep 6457</pre> where 6457 is the model number of my t61, replace it with your own. In my case it spits out something like this: system.hardware.product = '6457CTO'. So now I know that hal identifies my machine as 6457CTO.
# <pre>sudo gedit /usr/share/hal/fdi/information/10freedesktop/20-video-quirk-pm-lenovo.fdi</pre> and add a section to the end of the file, just above the </device> tag and replace 6457CTO with your hal device name:
<pre>

<match key="system.hardware.product" string="6457CTO">

<merge key="power_management.quirk.s3_mode" type="bool">true</merge>
<merge key="power_management.quirk.s3_bios" type="bool">false</merge>
<merge key="power_management.quirk.save_pci" type="bool">true</merge>
</match>
</pre>

Now save and reboot. Now you might run into the problem of coming back from resume into a completely white screen where normally should be the password dialog. Entering your password blindly is not nice but at least you can resume.

{{NOTE|Somehow I couldn't make the wildcard matching work as they did in the lenovo.fdi solution, but that might be due to my shortcomings on that syntax. Anyway matching the device by its full name worked for me. Probably somebody who knows more about the matching could make that wildcard thing work to have a more general solution. Because hal also knows the xorg driver name (info.linux.driver) there should be a way to set up the quirks depending on the driver.}}

[[Category: T61]]

=== TrackPoint ===
The [[TrackPoint]] works out of the box, but does not scroll nor does the tap-clicking (press to select) feature work. Therefor see: [[#tap-to-click feature]] To enable using the middle mouse button to scroll, replace the "Configured Mouse" section in {{path|/etc/X11/xorg.conf}} with the following:
<pre>
Section "InputDevice"
Identifier "Trackpoint"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ImPS/2"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "true"
Option "EmulateWheel" "true"
Option "EmulateWheelButton" "2"
EndSection
</pre>

{{NOTE|However, if you need to use external usb mouse, the above configuration is wrong. It will cause odd behavior. Try the following configuration from [http://gentoo-wiki.com/HARDWARE_IBM_Specific_Laptop_Guide#TrackPoint Gentoo Wiki]:}}
<pre>
Section "InputDevice"
Identifier "UltraNav TrackPoint"
Driver "mouse"
Option "Device" "/dev/input/mouse1"
Option "Protocol" "ExplorerPS/2"
Option "Emulate3Buttons" "on"
Option "Emulate3TimeOut" "50"
Option "EmulateWheel" "on"
Option "EmulateWheelTimeOut" "200"
Option "EmulateWheelButton" "2"
Option "YAxisMapping" "4 5"
Option "XAxisMapping" "6 7"
Option "ZAxisMapping" "4 5"
EndSection
</pre>

=== Audio ===

Works great out of the box, just the microphone has to be activated, it is considered a generic capture source and is muted by default.

To unmute the microphone:

*Right Click on the volume icon next to the clock and click on "Open Volume Control"

*Click Edit -> Preferences. A list of devices will be displayed, you should check the following (Do not uncheck any existing items):

Input Source
Capture

*Click Close and there should be two additional tabs "Recording" and "Options". -

*Click Recording and click on the microphone under the Capture slider so that it no longer has a red line through it, and put the slider up as it may be deactivated.

*Click Options and under capture source select internal mic.

To test your mic using Sound Recorder select Capture as the sound source.

This solution has been tested with Sound Recorder and Skype.

To get the volume controls working:

*add the following line to /etc/modprobe.d/alsa-base, then reboot

options snd-hda-intel index=0 model=thinkpad

{{NOTE|The volume controls worked fine for me out of the box on a 6460.}}

=== Multimedia Keys ===

Most Multimedia Keys work out of the box, just the play, forward and stop buttons need to be adjusted, therefore, press alt + F2 and type in gnome-keybinding-properties. Then everything works as followed:

* Fn-PgUp activates/deactivates the thinklight
* Fn-Up will trigger stop on a media player
* Fn-Down will toggle pause and play on a media player
* Fn-Left/Right go to prev/next tracks on a media player
* Fn-F2 properly locks the screen
* Fn-F3 shows remaining battery >>does not work on all machines<<
* Fn-F4 suspends (to ram)
* Fn-F9 ejects cds >>does not work on all machines, I think this is supposed to eject from a "dock"<<
* Fn-F12 hibernates (to disk)
* PrtSc opens the screenshot dialog

To enable the back, forward, and the menu keys you'll need to teach XKB what they are.

* Check the '''XkbLayout''' option (under '''InputDevice''') in your {{path|/etc/X11/xorg.conf}} file to determine which keyboard layout Ubuntu is using (I'll use 'us' for the example).
* Navigate to {{path|/etc/X11/xkb/symbols}} and, as root, open the appropriate layout file (as determined above) in your favorite editor.
{{cmduser|cd /etc/X11/xkb/symbols}}
{{cmduser|sudo gedit us}}
* In the '''xkb_symbols "basic"''' section after the '''name[Group1]= "x";''' (where x is a country name, or similar) line add the following:
key <I63> { [ Menu ] };
key <I69> { [ XF86Forward ] };
key <I6A> { [ XF86Back ] };
* Now log out and back in and all three of the buttons should function.

=== Thinkpad Button ===

Paste the following into /usr/share/hotkey-setup/ibm.hk
setkeycodes e017 148 # thinkpad button
You can also just type this into a terminal, to test it for the time of the current session.

Paste the following into the right file in /usr/share/xmodmap (check your country code)
keycode 159 = XF86Terminal
For immediate availability of the button, reload the file by executing
xmodmap <xmodmap.file>

Then use the "Keyboard Shortcuts" tool under "Preferences".

== Items that don't work (a.k.a.: items that need more intense tweaking to get fixed)==

=== tap-to-click feature ===

For the tap-to-click feature (taping the stick instead of using the left mouse button) i used a configure trackpoint utility: [http://tpctl.sourceforge.net/configure-trackpoint.html] there is a package for ubuntu 7.04 i386, but i compiled it by myself (using amd64):

1.) download the .tar.gz file

2.) unpack it

3.) install libgnomeui-dev

{{cmduser|sudo aptitude install libgnomeui-dev}}

4.) in the folder, do:

{{cmduser|./configure}}

if everything worked fine:

{{cmduser|make}}

then install it:

{{cmduser|sudo make install}}

5.a) Gnome : Open it: System > configure trackpoint, and configure on your needs

5.b) Kde : K-menu > Prefences > configure trackpoint > right-click > edit entry, edit "command" to "kdesu configure-trackpoint"

Save & exit

Open it : K-menu > Prefences > configure trackpoint and configure on your needs

=== Hotswapping ===

{{HELP|We need someone who is able to get hotswaping to work properly, this is not the right was to do this!}}
With the new kernel, bay-drivers changed, so if you remove the ultrabay it will freeze your system! You can hack it with a simple comand, first you have to look where the device is:

{{cmduser|less /sys/class/scsi_device/(x)\:0\:0\:0/device/model}}

for (x) first put in 0, if it tells you DVD or the name of the model you want to hotswap youre right. if not, go on with 1, 2 or 3...

then, once you are sure (I deactivated my harddisk like that) you put in:

{{cmduser|echo 1 {{!}} sudo tee /sys/class/scsi_device/(x)\:0\:0\:0/device/delete}}

Now you should be able to remove the device.

{{WARN|Do not use it for harddisks, be sure you unmounted it before! This is just a bad hack, if anyone knows how to get it right --> publish!}}

If Ubuntu does not reactivate the device after putting it in again, do:

{{cmduser|echo 0 0 0 {{!}} sudo tee /sys/class/scsi_host/host1/scan}}

=== Wireless activity LED ===

The LED is not implemented at least in the IWL4965 driver. For the Atheros wifi cards look at the solution below.

A patch posted in this [http://bughost.org/bugzilla/show_bug.cgi?id=1209 thread] works for me on R61 with IWL4965 card.

{{HELP|A howto is needed showing the process of implementing the patch in Hardy Heron. If anyone knows how to do this, please create a quick howto and either put it here or link to it from this page. Please and thank you.}}

As an alternative, you can install a backported IWL4965 driver that ''may'' fix the LED problem on your system.

To active WiFi LED,

sudo apt-get install linux-backports-modules-hardy

{{NOTE|On some machines, (at least one running IWL3945 & IWL4965) applying the above turns on the LED permanently. It should flicker as data is being transmitted. Also, with the above modification, after turning off wireless and then turning it back on (via the switch on the front of the machine) wireless is not reactivated, so not very helpful}}

You can download a compatible [http://wireless.kernel.org/download/compat-wireless-2.6/compat-wireless-2.6.tar.bz2 driver] which supports WiFi led flicking and build it with modifying the {{path|config.mk}} by adding {{bootparm|CONFIG_IWL3945_LEDS|y}} and {{bootparm|CONFIG_IWLWIFI_LEDS|y}} these two options. For Ubuntu/Debian users, build-essential, linux-source-2.6.24 and linux-headers-generic packages are required.

{{HELP|I added the above lines to the config.mk file and it would not make or make install correctly. I received an error 2 at the end of the make. If you have had success, where did you put the items in the config.mk file for it to make and make install correctly? Thanks in advance.}}

To enable the LED with the Atheros cards

=== Hidden SSID ===
It has been reported that users wanting to access Hidden SSIDs have to enter the SSID and password manually in Network Manager to connect. Even after the SSID is saved in Network Manager, it will not reconnect automatically. The user has to connect manually by entering the information as previously described.
It appears that updating the driver by following the instructions [http://linuxwireless.org/en/users/Download here] resolves this issue.

=== Hard Disk Parking ===
Getting hard disk parking to work:

tp_smapi patch is not needed in [http://packages.ubuntu.com/search?keywords=linux-image-2.6.24-18&searchon=names&suite=hardy&section=all linux-image-2.6.24-18]

1. Patch your kernel with the 'protect' [http://www.thinkwiki.org/wiki/HDAPS#Kernel_patch patch].

2. Installing the hdapsd daemon which does the actual parking.

{{cmduser|sudo apt-get install hdapsd hdaps-utils}}

== some other tweaks ==

=== screenblank with {{key|Fn}} + {{key|F3}} ===

Its ok, and might be usefull to get the estimated batterytime when pressing {{key|Fn}}+{{key|F3}}, as it should be. But i dont need that, i find the earlier command for {{key|F3}}, to blank the screen, more useful to save batterylife better.

For that, you must edit {{path|/etc/acpi/thinkpad-lockbattery.sh}} and replace LENOVO by IBM, and IBM by LENOVO :). Do not forget to copy the file before you change it!

=== Enable normal User to Limit CPU Speed ===
To let user set the CPU limit you need to open a Terminal an type there
sudo dpkg-reconfigure gnome-applets
anser the question with yes

=== Fix bluish WSXGA+ displays ===
Many T61 owners complain about a very bluish color temperature: My T61 WSXGA+ was also way too blue. I came across a thread at the notebook review forum http://forum.notebookreview.com/showthread.php?t=174408 which provided two useful ICC profiles which fixed the situation for me. Just install xcalib
sudo apt-get install xcalib
and load one of these profiles.

[[Category: Ubuntu 8.04]]

Installing Ubuntu 8.04 (Hardy Heron) on a ThinkPad T61

2008-07-24T12:26:11Z

Lunatico: /* Wireless activity LED */

== Items that work out of the box ==

'''Intel Video:''' 2D and 3D acceleration works

'''Nvidia Video:''' 2D and 3D acceleration works

'''Wireless:''' Intel cards tested. Atheros cards also works.

'''Wireless WAN:''' Cingular/AT&T card tested.

'''Network Card''' Intel 10/100/1000 tested

'''Wireless switch''' Tested

'''Webcam''' Tested with cheese and skype.

'''Headphones''' Works out of the box

'''Microphone''' Just needs to be activated, see section [[#Audio|below]]

'''Keyboard Shortcuts:''' Most of them work out of the box, some need to be activated, see section [[#Multimedia_Keys|below]]

== Items that need (some) tweaking to obtain full functionality ==

=== Open Source Intel Wifi Driver ===
The following information is important if you are upgrading from a previous version of Ubuntu to 8.04.

Intel has created a new Linux Wifi driver project for Intel Wireless cards, "[[Iwlwifi]]". This driver is Open Source and no longer requires the Intel daemon to run in addition. This project will support the [[:Category:T61 | T61]]'s Wifi [[Intel PRO/Wireless 3945ABG Mini-PCI Express Adapter | Intel 3945ABG network adapter]] and [[Intel PRO/Wireless 4965AGN Mini-PCI Express Adapter| Intel 4965AGN network adapter]].

An automatic migration will occur when upgrading from [[Installing Ubuntu 7.10 (Gutsy Gibbon) on a ThinkPad T61|Ubuntu 7.10]] to Ubuntu 8.04. However, there is a caveat to be aware of:
* The new driver wants to name the interface wlan0 (by default -- you can rename it to anything you want), and requires a different entry in {{path|/etc/udev/rules.d/70-persistent-net.rules}}, which handles the naming of interfaces. Simply edit this file and delete your old entry for the ipw3945 driver, then unload/reload the new driver, or simply reboot. A new entry will automatically be created that is appropriate for the new driver. Here's an example of the lines to delete:
<pre>
# PCI device 0x8086:0x4227 (ipw3945)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:1b:77:a4:0e:2f", NAME="eth1"
</pre>

If you need to perform a manual migration, the Ubuntu Help Community has written some [https://help.ubuntu.com/community/WifiDocs/Driver/iwlwifi_Intel_3945_4965/gutsy documentation] that will make this very easy to do.

=== Compiz and XV Playback on Intel GM965/GL960 ===

With Ubuntu 7.10 (Gutsy Gibbon) you currently have to choose between using Compiz and working video playback using XV. On 8.04 (Hardy Heron) alpha 5 you can play videos using XV under compiz, it works right out of the box using the Live-CD.

=== Suspend with Nv140m ===

** Update as of July 17th 2008 -- Using 8.04.1 with the newest nvidea drivers, I had no problems suspending without any additional configuration. **

Suspend may not work even after editing acpi-support. Enable bluetooth (Fn+F5) may result in a successful suspend. NOTE: that although the wifi led does not change when Fn+F5 is used, the wifi is still toggled by this key.

'''Hal "S3 BIOS" parameter issue!'''

After doing the changes to the /etc/default/acpi-support file (described [http://www.thinkwiki.org/wiki/Installing_Ubuntu_7.10_(Gutsy_Gibbon)_on_a_ThinkPad_T61#How_to_Suspend_with_nVidia_140m.2F570m here]), I for one, managed to have '''stable''' suspend support by creating a new file called: '''/etc/hal/fdi/information/lenovo.fdi''' with the following contents:
<pre>
<?xml version="1.0" encoding="ISO-8859-1"?> 
<deviceinfo version="0.2">
<device>
<match key="system.hardware.vendor" string="LENOVO">
<merge key="power_management.quirk.s3_bios" type="bool">false</merge>
</match>
</device>
</deviceinfo>
</pre>
{{NOTE|The problem (after reading the HAL and pm-utils documentations) is the fact that (as far as I can tell) the T61 Lenovo doesn't allow the S3 BIOS to be called *during* suspend/resume, which HAL seems to do by default (who knows, maybe there are T61s out there that do work with this default)!

This did not seem to be necessary for previous versions of Ubuntu. Also note that I have an NVIDIA card so I have no idea what to do for Intel versions.The change should also be resistant to HAL and pm-utils upgrades.}}

'''Still no suspend with nvs140m? Got Modell 6460?'''

Fix above didn't work for me on a 15.4 wide T61 Modell 6460 with nv140m. Bios is updated to 2.14 but didn't change anything, except the usb bug is fix. Suspend seems to work fine, but resume gives me a black screen (backlight off - no reaction to brightness up) and I can hear 2 beeps. Most of the time I can reboot with ctrl+alt+delete but the screen stays dark until bios.

follow the instructions above but create the new file called: '''/etc/hal/fdi/information/lenovo.fdi''' with the following contents instead:
<pre>
<?xml version="1.0" encoding="ISO-8859-1"?> 
<deviceinfo version="0.2">
<device>
<match key="system.hardware.vendor" string="LENOVO">
<merge key="power_management.quirk.s3_mode" type="bool">true</merge>
<merge key="power_management.quirk.s3_bios" type="bool">false</merge>
<merge key="power_management.quirk.save_pci" type="bool">true</merge>
</match>
</device>
</deviceinfo>
</pre>

Also you want to set the following parameter in

{{path|/etc/default/acpi-support}}
<pre>
SAVE_VIDEO_PCI_STATE=true
</pre>

{{NOTE|This works for me with mode 6460, except for one problem: You may get a white screen in xorg after resume when using compiz. If you don't have a 6460 with nvidia this file may break things for you because it doesn't care about the modell and sets the parameter for any lenovo product}}
{{HELP|Anyone with more knowledge of hal and acpi-support is welcome to clean this up. I also don't know why this setting can be done via hal and in acpi-support.
See below!}}

'''Working on hardy final'''

After trying out all these recipes on my 6457CTO waking up from suspend still did not work. Finally I came across a blog entry which pointed out the right way: [[http://david.goodlad.ca/2008/3/14/suspend-hibernate-on-lenovo-t61 David Goodlad's blog]]. I realized that all the fixes proposing editing the acpi-support file or adding a kernel parameter acpi_sleep=s3_mode must be wrong because since hardy gnome-power-manager gets its information solely from hal. So setting up correct hal information is the right way but the proposed solution (creating a /etc/hal/fdi/information/lenovo.fdi file) did not work for me. Ok, but now step by step:

# Revert ALL the proposed fixes from above. I found out that at least the lenovo.fdi solution is actually breaking the real fix. So for sure delete /etc/hal/fdi/information/lenovo.fdi
# Find out about the excact hal name of your machine: <pre>hal-device |grep 6457</pre> where 6457 is the model number of my t61, replace it with your own. In my case it spits out something like this: system.hardware.product = '6457CTO'. So now I know that hal identifies my machine as 6457CTO.
# <pre>sudo gedit /usr/share/hal/fdi/information/10freedesktop/20-video-quirk-pm-lenovo.fdi</pre> and add a section to the end of the file, just above the </device> tag and replace 6457CTO with your hal device name:
<pre>

<match key="system.hardware.product" string="6457CTO">

<merge key="power_management.quirk.s3_mode" type="bool">true</merge>
<merge key="power_management.quirk.s3_bios" type="bool">false</merge>
<merge key="power_management.quirk.save_pci" type="bool">true</merge>
</match>
</pre>

Now save and reboot. Now you might run into the problem of coming back from resume into a completely white screen where normally should be the password dialog. Entering your password blindly is not nice but at least you can resume.

{{NOTE|Somehow I couldn't make the wildcard matching work as they did in the lenovo.fdi solution, but that might be due to my shortcomings on that syntax. Anyway matching the device by its full name worked for me. Probably somebody who knows more about the matching could make that wildcard thing work to have a more general solution. Because hal also knows the xorg driver name (info.linux.driver) there should be a way to set up the quirks depending on the driver.}}

[[Category: T61]]

=== TrackPoint ===
The [[TrackPoint]] works out of the box, but does not scroll nor does the tap-clicking (press to select) feature work. Therefor see: [[#tap-to-click feature]] To enable using the middle mouse button to scroll, replace the "Configured Mouse" section in {{path|/etc/X11/xorg.conf}} with the following:
<pre>
Section "InputDevice"
Identifier "Trackpoint"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ImPS/2"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "true"
Option "EmulateWheel" "true"
Option "EmulateWheelButton" "2"
EndSection
</pre>

{{NOTE|However, if you need to use external usb mouse, the above configuration is wrong. It will cause odd behavior. Try the following configuration from [http://gentoo-wiki.com/HARDWARE_IBM_Specific_Laptop_Guide#TrackPoint Gentoo Wiki]:}}
<pre>
Section "InputDevice"
Identifier "UltraNav TrackPoint"
Driver "mouse"
Option "Device" "/dev/input/mouse1"
Option "Protocol" "ExplorerPS/2"
Option "Emulate3Buttons" "on"
Option "Emulate3TimeOut" "50"
Option "EmulateWheel" "on"
Option "EmulateWheelTimeOut" "200"
Option "EmulateWheelButton" "2"
Option "YAxisMapping" "4 5"
Option "XAxisMapping" "6 7"
Option "ZAxisMapping" "4 5"
EndSection
</pre>

=== Audio ===

Works great out of the box, just the microphone has to be activated, it is considered a generic capture source and is muted by default.

To unmute the microphone:

*Right Click on the volume icon next to the clock and click on "Open Volume Control"

*Click Edit -> Preferences. A list of devices will be displayed, you should check the following (Do not uncheck any existing items):

Input Source
Capture

*Click Close and there should be two additional tabs "Recording" and "Options". -

*Click Recording and click on the microphone under the Capture slider so that it no longer has a red line through it, and put the slider up as it may be deactivated.

*Click Options and under capture source select internal mic.

To test your mic using Sound Recorder select Capture as the sound source.

This solution has been tested with Sound Recorder and Skype.

To get the volume controls working:

*add the following line to /etc/modprobe.d/alsa-base, then reboot

options snd-hda-intel index=0 model=thinkpad

{{NOTE|The volume controls worked fine for me out of the box on a 6460.}}

=== Multimedia Keys ===

Most Multimedia Keys work out of the box, just the play, forward and stop buttons need to be adjusted, therefore, press alt + F2 and type in gnome-keybinding-properties. Then everything works as followed:

* Fn-PgUp activates/deactivates the thinklight
* Fn-Up will trigger stop on a media player
* Fn-Down will toggle pause and play on a media player
* Fn-Left/Right go to prev/next tracks on a media player
* Fn-F2 properly locks the screen
* Fn-F3 shows remaining battery >>does not work on all machines<<
* Fn-F4 suspends (to ram)
* Fn-F9 ejects cds >>does not work on all machines, I think this is supposed to eject from a "dock"<<
* Fn-F12 hibernates (to disk)
* PrtSc opens the screenshot dialog

To enable the back, forward, and the menu keys you'll need to teach XKB what they are.

* Check the '''XkbLayout''' option (under '''InputDevice''') in your {{path|/etc/X11/xorg.conf}} file to determine which keyboard layout Ubuntu is using (I'll use 'us' for the example).
* Navigate to {{path|/etc/X11/xkb/symbols}} and, as root, open the appropriate layout file (as determined above) in your favorite editor.
{{cmduser|cd /etc/X11/xkb/symbols}}
{{cmduser|sudo gedit us}}
* In the '''xkb_symbols "basic"''' section after the '''name[Group1]= "x";''' (where x is a country name, or similar) line add the following:
key <I63> { [ Menu ] };
key <I69> { [ XF86Forward ] };
key <I6A> { [ XF86Back ] };
* Now log out and back in and all three of the buttons should function.

=== Thinkpad Button ===

Paste the following into /usr/share/hotkey-setup/ibm.hk
setkeycodes e017 148 # thinkpad button
You can also just type this into a terminal, to test it for the time of the current session.

Paste the following into the right file in /usr/share/xmodmap (check your country code)
keycode 159 = XF86Terminal
For immediate availability of the button, reload the file by executing
xmodmap <xmodmap.file>

Then use the "Keyboard Shortcuts" tool under "Preferences".

== Items that don't work (a.k.a.: items that need more intense tweaking to get fixed)==

=== tap-to-click feature ===

For the tap-to-click feature (taping the stick instead of using the left mouse button) i used a configure trackpoint utility: [http://tpctl.sourceforge.net/configure-trackpoint.html] there is a package for ubuntu 7.04 i386, but i compiled it by myself (using amd64):

1.) download the .tar.gz file

2.) unpack it

3.) install libgnomeui-dev

{{cmduser|sudo aptitude install libgnomeui-dev}}

4.) in the folder, do:

{{cmduser|./configure}}

if everything worked fine:

{{cmduser|make}}

then install it:

{{cmduser|sudo make install}}

5.a) Gnome : Open it: System > configure trackpoint, and configure on your needs

5.b) Kde : K-menu > Prefences > configure trackpoint > right-click > edit entry, edit "command" to "kdesu configure-trackpoint"

Save & exit

Open it : K-menu > Prefences > configure trackpoint and configure on your needs

=== Hotswapping ===

{{HELP|We need someone who is able to get hotswaping to work properly, this is not the right was to do this!}}
With the new kernel, bay-drivers changed, so if you remove the ultrabay it will freeze your system! You can hack it with a simple comand, first you have to look where the device is:

{{cmduser|less /sys/class/scsi_device/(x)\:0\:0\:0/device/model}}

for (x) first put in 0, if it tells you DVD or the name of the model you want to hotswap youre right. if not, go on with 1, 2 or 3...

then, once you are sure (I deactivated my harddisk like that) you put in:

{{cmduser|echo 1 {{!}} sudo tee /sys/class/scsi_device/(x)\:0\:0\:0/device/delete}}

Now you should be able to remove the device.

{{WARN|Do not use it for harddisks, be sure you unmounted it before! This is just a bad hack, if anyone knows how to get it right --> publish!}}

If Ubuntu does not reactivate the device after putting it in again, do:

{{cmduser|echo 0 0 0 {{!}} sudo tee /sys/class/scsi_host/host1/scan}}

=== Wireless activity LED ===

The LED is not implemented at least in the IWL4965 driver. For the Atheros wifi cards look at this solution.

A patch posted in this [http://bughost.org/bugzilla/show_bug.cgi?id=1209 thread] works for me on R61 with IWL4965 card.

{{HELP|A howto is needed showing the process of implementing the patch in Hardy Heron. If anyone knows how to do this, please create a quick howto and either put it here or link to it from this page. Please and thank you.}}

As an alternative, you can install a backported IWL4965 driver that ''may'' fix the LED problem on your system.

To active WiFi LED,

sudo apt-get install linux-backports-modules-hardy

{{NOTE|On some machines, (at least one running IWL3945 & IWL4965) applying the above turns on the LED permanently. It should flicker as data is being transmitted. Also, with the above modification, after turning off wireless and then turning it back on (via the switch on the front of the machine) wireless is not reactivated, so not very helpful}}

You can download a compatible [http://wireless.kernel.org/download/compat-wireless-2.6/compat-wireless-2.6.tar.bz2 driver] which supports WiFi led flicking and build it with modifying the {{path|config.mk}} by adding {{bootparm|CONFIG_IWL3945_LEDS|y}} and {{bootparm|CONFIG_IWLWIFI_LEDS|y}} these two options. For Ubuntu/Debian users, build-essential, linux-source-2.6.24 and linux-headers-generic packages are required.

{{HELP|I added the above lines to the config.mk file and it would not make or make install correctly. I received an error 2 at the end of the make. If you have had success, where did you put the items in the config.mk file for it to make and make install correctly? Thanks in advance.}}

=== Hidden SSID ===
It has been reported that users wanting to access Hidden SSIDs have to enter the SSID and password manually in Network Manager to connect. Even after the SSID is saved in Network Manager, it will not reconnect automatically. The user has to connect manually by entering the information as previously described.
It appears that updating the driver by following the instructions [http://linuxwireless.org/en/users/Download here] resolves this issue.

=== Hard Disk Parking ===
Getting hard disk parking to work:

tp_smapi patch is not needed in [http://packages.ubuntu.com/search?keywords=linux-image-2.6.24-18&searchon=names&suite=hardy&section=all linux-image-2.6.24-18]

1. Patch your kernel with the 'protect' [http://www.thinkwiki.org/wiki/HDAPS#Kernel_patch patch].

2. Installing the hdapsd daemon which does the actual parking.

{{cmduser|sudo apt-get install hdapsd hdaps-utils}}

== some other tweaks ==

=== screenblank with {{key|Fn}} + {{key|F3}} ===

Its ok, and might be usefull to get the estimated batterytime when pressing {{key|Fn}}+{{key|F3}}, as it should be. But i dont need that, i find the earlier command for {{key|F3}}, to blank the screen, more useful to save batterylife better.

For that, you must edit {{path|/etc/acpi/thinkpad-lockbattery.sh}} and replace LENOVO by IBM, and IBM by LENOVO :). Do not forget to copy the file before you change it!

=== Enable normal User to Limit CPU Speed ===
To let user set the CPU limit you need to open a Terminal an type there
sudo dpkg-reconfigure gnome-applets
anser the question with yes

=== Fix bluish WSXGA+ displays ===
Many T61 owners complain about a very bluish color temperature: My T61 WSXGA+ was also way too blue. I came across a thread at the notebook review forum http://forum.notebookreview.com/showthread.php?t=174408 which provided two useful ICC profiles which fixed the situation for me. Just install xcalib
sudo apt-get install xcalib
and load one of these profiles.

[[Category: Ubuntu 8.04]]