ThinkWiki - User contributions [en]

Unofficial maximum memory specs

2010-03-06T20:02:24Z

A-j: added another entry for X41

Some ThinkPads are known to support more memory than their specs say. This page gathers information about those models, how much memory they can take and what special requirements that memory must fulfill.

Have a look at the [[Memory]] page for the official memory configs and partnumbers

==Working memory configurations==
The following table gives an overview of tested memory configurations that exceed the specified limits for that ThinkPad type.

{| border="1" cellspacing="0" cellpadding="2"
! ThinkPad !! Official Max !! Unoffical Max !! BIOS !! Embedded Controller !! Memory configuration successfully tested
|- style="vertical-align:top;"
| ThinkPad {{X61t}} 7764-CTO || 4 GB || 8 GB || 1.23 || ?.?? ||
2 x Generic 4GB 200-Pin DDR2.
|-
| ThinkPad {{X61t}} 7762-94G || 4 GB || 8 GB || 1.23 || 1.02 ||
2 x Kingston 4GB 200-Pin DDR2, KVR667D2S5/4G.
|-
| ThinkPad {{T61p}} 8889-3FG || 4 GB || 8 GB || TBA || TBA ||
2 x Kingston 4GB 200-Pin DDR2, KVR667D2S5/4G.
|-
| ThinkPad {{T61p}} 6457-5GG || 4 GB || 8 GB || 2.19 || 1.08 ||
2 x Kingston 4GB 200-Pin DDR2, Model# KTL-TP667/4GB.
|-
| ThinkPad {{T61p}} 6457-7XG || 4 GB || 8 GB || 2.26 || 1.08 ||
2 x Crucial 4GB 200-Pin DDR2, Model# CT51264AC800. (PC2-6400)
|-
| ThinkPad {{T61p}} 6459-CTO || 4 GB || 8 GB || 2.26 || 1.08 ||
2 x G.Skill 4GB 200-Pin DDR2, Model # F2-6400CL6D-8GBSQ
|-
| ThinkPad {{T61p}} 6460-8YG || 4 GB || 8 GB || 2.26 || 1.08 ||
2 x Crucial 4GB 200-Pin DDR2, Model# CT2KIT51264AC667 (2x CT51264AC667)
|-
| ThinkPad {{A31p}} 2653-R || 1 GB || || 1.09 || 1.05 ||
2 x Kingston 1GB 200-Pin DDR, Model# KTM - TP9828/1G
|-
| ThinkPad {{T30}} 2366-92U || 1 GB || || 2.08 || 1.06 ||
* 2 x Kingmax 1GB 200-Pin DDR SO-DIMM DDR333 PC2700, Model# MSAD42D-KI
but see [[problem with T30 not booting with 1 GiB memory module]].
* 2 x Generic Brand 1GB 200-pin DDR SO-DIMM PC2700 (p/n 89898E):
BIOS recognizes 2048MB, but Gentoo sees only 1024MB
|-
| ThinkPad {{T43p}} 2668-WTB || 2 GB || || 1.29 || 1.06 ||
* 2 x 1GB Kingston KTM TP3840/1G DDR2 533MHz
|-
| ThinkPad {{X31}} 2672-C2G || 1 GB || || 3.02 || 1.08 ||
* 2 x 1GB Kingston KVR400X64SC3A/1G DDR400MHz. Newer documentation also states 2GB, but original one did not.
* Boots with 1 bar.
|-
| ThinkPad {{X31}} 2673-C2G || 1 GB || || 3.02 || 1.08 ||
* 2 x 1GB (Team Group Inc. TSDR1024M400 DDR400MHz)
* Boots with 1 x TSDR1024M400
|-
| ThinkPad {{X41}} 2528-5FU || 1.5 GB || || 2.09 || 1.02 ||
* 1 x 2GB (Transcend TS2GIB3847 DDR2 667 MHz)
* 1 x 2GB (FRU 73P3846 DDR2 PC2-4200)
BIOS claims 2.5 GB. Diagnostic POST tests only 2 GB. Linux and XP recognize 2 GB.
|-
| ThinkPad {{X41}} 2525-F8G || 1.5 GB || 2 GB || 2.06 || 1.01 ||
* 1 x 2GB (Crucial CT25664AC667 DDR2 PC2-5300)
BIOS claims 2.5 GB. Diagnostic POST and memtest86+ both test only 2 GB. Linux and XP recognize 2 GB.
|-
| {{X41_Tablet}} 1866-6HU || 1.5 GB || || 2.03 || 1.02 ||
* 1 x 2GB (Transcend JM667QSU-2G DDR2 667 MHz)
BIOS claims 2.5GB. Diagnostic POST tests only 2GB, Linux and WindowsXP recognize 2GB.
|-
| ThinkPad {{240}} 2609-40U || 320MByte || || IRETWWW76 || n/a ||
* Any PC100 256MB memory in 16-chip configuration
|-
| ThinkPad {{240X}} || 256MByte || || unknown || n/a ||
* Some PC100 256MB memory in 16-chip configuration may work. Chipset cannot handle more than 256MB
|-
| ThinkPad {{570}} 2644-3AU || 320MB || || 1.16 IMET65WW 11/11/99 || n/a ||
* Kingston KTM-TP390X/256 256MB MODULE FRU 16P6327 - 16 chips, 8 each side
|-
| ThinkPad {{600}} ? || 288MB || || ? || ? ||
* 416MB = 256MB '''low density''' PC100 SODIMM + 128MB PC66 SODIMM + 32MB PC66 on-board. It matters which SODIMM you put in which slot. This was first reported working on the [http://zurich.csail.mit.edu/hypermail/thinkpad/2004-04/0797.html Thinkpad Mailing List], and it worked error-free for me.
The 600E (2645-8A0) with Bios INET36WW accept two modules
of 256MB.
The ram modules have 8 chips on each side.
That results in 544MB. (RAM Typ: Micron MT16LSDF3264HG-133E4 PC133 CL3 sync).
Processor is an Intel PII 366 PE, installed platform is Windows XP Pro with SP3.
|-
| ThinkPad {{770}}x 9549|| 448MB || || 1.11 IIET42WW 09/10/99 || n/a ||
* 448MB = 256MB PC100 + 128MB PC66 + internal 64MB using IBM 256MB MODULE FRU 33L3070 PC100 CL2 - 16 chips, 8 each side
* 512MB = 2 x 256MB PC100 + 64MB internal booted up as well. 512MB is due to 440LX-Chipset limitations, 64MB are overlapping or unused.
|-
|}

==Non-working memory configurations==
{| border="1" cellspacing="0" cellpadding="2"
! ThinkPad !! max. Specs !! BIOS !! Embedded Controller !! Memory configuration unsuccessfully tested
|- style="vertical-align:top;"
| ThinkPad {{A21m}} || 512MB || ? || ? ||
* 2 x Microx 144-pin 512MB PC133 SDRAM SODIMM 32x16 8C
* 1 x Microx 144-pin 512MB PC133 SDRAM SODIMM 32x16 8C
* 1 x Microx 144-pin 512MB PC133 SDRAM SODIMM 32x16 8C
:+ 1 x 144-pin 256MB PC133 SDRAM SODIMM
|-
|}

==External Sources==
* [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-55644 IBM's official Memory compatibility page]

Talk:Installing Ubuntu 7.10 (Gutsy Gibbon) on a ThinkPad T61

2008-01-29T00:13:27Z

A-j: /* Touchpad issues */

==Nvidia==

Would it be possible to clean up the "How to Suspend with nVidia 140m/570m" section? I was going to do it but after reading through i realized that my knowledge was too limited to do it well. but i think it could serously benifit from a good cleaning!

When trying to do anything with Twinview in fullscreen mode will cause it to span both monitors instead of just being on the second. This essencially kills the functionality of twinview.

eg 1 --> you are an office working bringing your notebook to work to show a presentation but you can't use full screen.

eg 2 --> you want take your notebook to a friends house to watch a movie on his/her projector and fullscreen mode gets half displayed on the projector and half on the notebook monitor.

Has anyone found a fix for this?

Does the Ubuntu wiki <https://help.ubuntu.com/community/NvidiaTVOut> work?
What adjustments are needed for Gutsy and NVIDIA Quadro NVS 140M?
Is it hotpluggable --like Twinview using 'nvidia-settings'?

Is it possible toset this up in Applications->System Tools->Nvidia Settings?

When i use Twinview with diffenent sizes of screens in 'clone' mode it crops my screen to match the smaller one. This makes my monitor pretty much useless. How do I get 'clone' to stretch (or shrink) instead of crop?

==Microphone==

This discussion was going on in the wiki and seems a bit confusing. If possible I think we should get a consensus on the problem (if it still exists as of the final release) and solutions. --[[User:Darrena|Darrena]] 18:19, 21 October 2007 (UTC)

This problem does still exist.

There are multiple fixes because the GUI can be a bit confusing and the microphone can be configured to work in multilple ways.

**If the microphone section was confusing it should have been cleaned up not removed!

---

We should focus on providing clear instructions in the article and not provide a dumping ground for various thoughts and ideas. Everyone should certainly share what worked for them no matter how complicated but all of that should happen in the talk page so less technical users are not confused by the instructions. So far one person has said that their mic worked out of the box on a Beta install. Notice that the change I made was to point to the talk page so that the information was not lost but it made people aware that the various items are still being looked at. Personally I have never been able to get the mic to work with sound recorder but it seems to work fine with Ekiga once I set the default source via alsamixer. Also I think that recommending that people switch to OSS from alsa is going to cause even more confusion among less experienced users. In general sound is in poor shape right now but we can all hope that Pulseaudio will resolve this in time for 8.10. My suggestion would be to instruct users how to select the default source in alsamixer and then all apps that use Alsa /should/ work. I tested with Ekiga, Wengophone and Skype (Shudder!) and those seem to be the important apps to people. So if most people agree then I will write up a quick description of setting the default source in alsamixer and unmuting the mic. I don't care which solution we present but it should be as simple as possible and not require users to make changes beyond the initial setup and using ALSA seems to meet that requirement IMO. --[[User:Darrena|Darrena]] 18:19, 21 October 2007 (UTC)

'''Attn:''' Microphone (both internal and external) seems to be working for me with all applications after applying all updates (No need to change device to OSS) Make sure the relevant things (internal microphone, mic boost) etc aren't muted either in alsamixer or gnome-volume-control.

Microphone may not work with applications (like sound recorder and skype) even though sound can be heard through the speakers or headphones. If you have success in using the built in microphone please update this section.

It worked for me after i followed the instructions in this thread for ALSA
http://ubuntuforums.org/showthread.php?p=2635174#post2635174

I had to tick the following tracks to make my mic work in Sound Recorder
PCM, Microphone, Capture, Capture1, Input Source, Input Source, Internal Mic, Speaker.

For those that find the above instructions vague:

The whole 'Volume Control Center' could be better labelled but here is what i believe to be true:
the microphone will work but only through the OSS mixer. the ALSA mixer is what causes the listed problem (not working with applications like skype) but the sound quality of alsa mixer is far better than the OSS mixer and it would be much more convenient to control so it would be hugely beneficial to get it working. Nonetheless here are more detailed instructions for getting sound working.

In the Playback tab you should have PCM, which is the only important one. If you have anything else there you should mute them. [On an X61 at least under playback was the option 'internal mic', unmute that and max it out, mute internal mic boost, make sure capture one is about 70% and thats all it took to get mine working]

In the 'recording' tab should be 'Capture' and 'Capture 1'(if they aren't you have to check them in Edit-->Preferences) 'Capture' controls the volume for the ALSA mic input and 'Capture 1' controls the volume for the OSS mic input. Mute 'Capture' and increase the volume of 'Capture 1'

The 'switches' tab should be as you set it up in the audio section of this wiki. headphones [check] and speakers [check].

The options tab (which i haven't quite figured out) should have a list of two 'Input Sources' I have mine set to 'Internal Mic' on the top and 'Mic' on the bottom. i don't know if that is correct but it is working for me.

Now go to File-->Change Device--> Analog Devices (OSS Mixer)
You should see a 'Playback' tab with 'Microphone', 'PCM-2' and 'In-gain'.
If you do not see these then open Edit-->Preferences and select them.
Place your microphone volume at your desired level (mine is at about 7/8ths) and mute it when you are not using it, otherwise you get the crackle. The 'PCM-2' seems to only go fully up or fully down, i leave it fully up. I haven't figured out what effect the 'In-gain' has yet. (you'll be the first to know when i do)

This should give you the ability to record sound or skype but it is tedious as you will have to mute and unmute the microphone in the Analog Devices OSS area. Maybe there is a way to simplfy this method but i haven't found it. Hopefully soon recording with the ALSA mixer will work.

== Core 2 Duo running at 800 mHz? ==
The applications Sysinfo and PowerTOP both say that my CPU is running at 800 MHz. When I first open Sysinfo, it says a number around 2 GHz but it then drops to 800 MHz. Sysinfo says something about laptop CPU frequency changing (being "dynamic"), but it remains static at 800 MHz. [[User:SteveSims|SteveSims]] 00:51, 13 September 2007 (UTC)

This is normal. This is the "frequency scaling" feature of the laptop. Whenever the processors aren't being used they drop down to 800MHz to conserve power. All you have to do is run some CPU-intensive task and you'll see them jump up to 2GHz. There's a little applet that you can add to the top panel called "CPU Frequency Scaling Monitor" that will let you watch the processor speed up and down in real time: Right-click on the top panel bar and select "Add to Panel" to find it; it's under "System and Hardware" --[[User:Mike Richards|Mike Richards]] 06:31, 13 September 2007 (UTC)

==Desktop_Applet crash on login after update (2007-09-16) with x86 and AMD64 versions (Fixed in daily build 20070918, reappears in 20070919.1)==
I found out that my Thinkpad T61 is a 64-bit machine so I installed the 64-bit version of Ubuntu 7.10 Tribe 5. I tried updating the machine, which worked fine until it had to configure and install my updates. With about 12 minutes remaining it hangs up and the terminal within the Update Manager says that some components must be restarted (and the update hangs) so I restart my computer. When I log in, I get an error message that says something about a Deskbar_Applet not working, and it asks me if I want to delete it. Regardless of my selection, I can no longer update the machine nor run Applications --> Add/Remove. I thought it must be a difference between AMD64 and Intel's x86-64 near-clone, so I re-installed the 32-bit version. When I updated, the same thing happened after I updated it. I'm guessing this is a bug withing the [http://en.wikipedia.org/wiki/GUI GUI] or the package manager.

However, I can load Firefox from my panel just fine. [[User:SteveSims|SteveSims]] 05:01, 17 September 2007 (UTC)

:I had a similar problem. I found if I just avoided updating the system until after a full reboot, things were fine. [[User:Rybu|Rybu]]

::The most recent update (9-18-2007) solves this problem.

:::The problem appears again in 20070919.1, at least the AMD64 version (I haven't tested the x86-32 version). [[User:SteveSims|SteveSims]] 21:49, 19 September 2007 (UTC)

::::And it still exists as of September 20th. [[User:SteveSims|SteveSims]] 04:53, 21 September 2007 (UTC)

==Touchpad issues==
After updating on September 18th from the original x86 Tribe 5, tapping the touchpad hard no longer clicks, and the right edge no longer scrolls. [[User:SteveSims|SteveSims]] 01:59, 19 September 2007 (UTC)
:Go to System -> Preferences -> Mouse. In the Touchpad tab you can activate tap to click and vertical scrolling. --[[User:Aerials|aerials]] 13:05, 21 September 2007 (UTC)

My touch pad is overly sensitive --sometimes opening applications or documents as I attempt to pass the pointer over their icon. I have tried adjusting it in the Prefs-->Mouse.
Are there any other ways to adjust the sensitivity?
Do others have this issue?

I don't have this issue but I have seen similar issues before on other distros, have you tried installing gsynaptic and see if editing the sensitivity there works? --[[User:Darrena|Darrena]] 01:29, 29 October 2007 (UTC)

Disabling "vertical scrolling" solved my erratic/over-sensitive touchpad.

==Daily build 20070918 AMD64 won't install==
Double-clicking on the Install icon in the LiveCD does nothing. No window loads, I can't install it from the LiveCD. [[User:SteveSims|SteveSims]] 01:59, 19 September 2007 (UTC)

==Volume/Sound Buttons==

In Kubuntu 7.10 beta work mute button but anything display on screen/desktop. When I press the volume up button, on the screen display a window and always write 11%, and the volume not hight (if mute is on then mute disabled). When I press the volume down button display 0% but the volume not down.

When the mute is enabled the kmix not display mute. [[User:Fitopaldi|Fitopaldi]]

If add this lines to ''~/.kde/share/config/khotkeysrc'' the volume up button and volume down button works perfectly with kmix with DCOP.

[Data_4]
Comment=
DataCount=2
Enabled=true
Name=Thinkpad
SystemGroup=0
Type=ACTION_DATA_GROUP

[Data_4Conditions]
Comment=
ConditionsCount=0

[Data_4_1]
Comment=
Enabled=true
Name=Volume up
Type=DCOP_SHORTCUT_ACTION_DATA

[Data_4_1Actions]
ActionsCount=1

[Data_4_1Actions0]
Arguments=1
Call=increaseVolume
RemoteApp=kmix
RemoteObj=Mixer0
Type=DCOP

[Data_4_1Conditions]
Comment=
ConditionsCount=0

[Data_4_1Triggers]
Comment=Simple_action
TriggersCount=1

[Data_4_1Triggers0]
Key=XF86AudioRaiseVolume
Type=SHORTCUT

[Data_4_2]
Comment=
Enabled=true
Name=Volume down
Type=DCOP_SHORTCUT_ACTION_DATA

[Data_4_2Actions]
ActionsCount=1

[Data_4_2Actions0]
Arguments=1
Call=decreaseVolume
RemoteApp=kmix
RemoteObj=Mixer0
Type=DCOP

[Data_4_2Conditions]
Comment=
ConditionsCount=0

[Data_4_2Triggers]
Comment=Simple_action
TriggersCount=1

[Data_4_2Triggers0]
Key=XF86AudioLowerVolume
Type=SHORTCUT

But this is a temporal solution. ;) With this solution not work the volume info screen. [[User:Fitopaldi|Fitopaldi]]

Don't know if this is of any interest: under Kubuntu 7.04 with the kernel from Gutsy the volume up/down buttons worked for me. --[[User:Rawk|Rawk]] 18:48, 23 October 2007 (UTC)

==Brightness buttons==

The brightness buttons used to work on my system. But now that I have 2 displays, they don't work anymore. When I first installed Ubuntu 7.10 the brightness buttons did not work but I found some tips on-line to enable them... unfortunately I don't remember what those tips were... silly me... I'll dig up the info and put it into the wiki, soon. [[User:Rybu|Rybu]]

In Kubuntu Gutsy don't work anymore. When I first installed Kubuntu 7.10 (tribe 5) yes work on console screen, but later the first update not work this. (NVIDIA GPU) [[User:Fitopaldi|Fitopaldi]]

I had the same problem and fixed it this way:
Edit {{path|/etc/acpi/thinkpad-brightness-up.sh}} and insert before <code><pre>exit</pre></code> (line 5) this:
<code><pre>echo 4 > /proc/acpi/ibm/cmos</pre></code>
Do the same with {{path|/etc/acpi/thinkpad-brightness-down.sh}} using <code><pre>echo 5 > /proc/acpi/ibm/cmos</pre></code>
The module thinkpad_acpi has to be loaded, but I think it's done automaticaly. If you use echo up/down > /proc/acpi/ibm/brightness it's not possible to use all levels (bug in thinkpad_acpi?). [[User:Rawk|Rawk]] 17:06, 17 November 2007 (UTC)

==Compiling existing information==

This [[http://gentoo-wiki.com/HARDWARE_Lenovo_Thinkpad_T61]] link has some useful information that is worthwhile compiling into the wiki here. [[User:Rybu|Rybu]]

==Desktop effects don't consistenly work==
I installed new themes and updated today and suddenly the new desktop effects that were added to 7.10 don't work.

However, Deskbar_Applet doesn't crash with the update, even though it does with today's most current LiveCD. [[User:SteveSims|SteveSims]] 06:37, 21 September 2007 (UTC)

==NetworkManger Intermittently Fails To Start, No Networking When It Fails==
After the most recent Kernel patch under Gutsy, NetworkManager doesn't always manage to run when I boot, and when it fails I have no networking. If I try init.d/networking restart, it fails with 'unknown device' for all devices. Looking through the logs, my best guess is ath0 isn't ready when NetworkManager starts, so it starts cycling through other devices until it crashes. Does anyone have any ideas? It seems to only work about 1-2 boots out of 10.

==I installed libdvdcss2, but DVD playback still doesn't work==
I have all the GStreamer plugins. When I insert a DVD movie, Movie Player loads and I hear sound but there's no video. If I try to open a video from a location, I get this dialog box: 
[[Image:totem no plugins.png|300px]]

:I always like the idea of using GStreamer instead of Xine, but the fact is, I've never really gotten DVDs to work very well without installing totem-xine. Maybe you don't want to do that, but if you haven't tried it, consider installing totem-xine? --[[User:Plumpy|Plumpy]] 23:32, 25 September 2007 (UTC)

:::Here's what I get when I install totem-xine from Synaptic:

:::[[Image:Totem-xine_no_DVD_playback.png]] [[User:SteveSims|SteveSims]] 00:32, 26 September 2007 (UTC)

:::::I decided to install some more xine plugins but now Totem closes immediately after opening if I insert a DVD. Here's a log of my xine package installations:
<pre>Commit Log for Tue Sep 25 17:25:49 2007

Installed the following packages:
libxine1-console (1.1.7-1ubuntu1)
libxine1-gnome (1.1.7-1ubuntu1)
libxine1-plugins (1.1.7-1ubuntu1)

Commit Log for Tue Sep 25 17:23:33 2007

Installed the following packages:
libpostproc1d (3:0.cvs20070307-5ubuntu4)
libxine1-ffmpeg (1.1.7-1ubuntu1)

Commit Log for Tue Sep 25 17:14:25 2007

Removed the following packages:
totem-gstreamer

Installed the following packages:
libmodplug0c2 (1:0.7-5.2ubuntu1)
libpulse0 (0.9.6-1ubuntu2)
libxcb-shape0 (1.0-3)
libxcb-shm0 (1.0-3)
libxcb-xv0 (1.0-3)
libxcb1 (1.0-3)
libxine1 (1.1.7-1ubuntu1)
libxvmc1 (2:1.0.4-2ubuntu1)
totem-xine (2.20.0-0ubuntu1)
</pre>

== x86 vs 64bit on core 2 duo ==

What to choose? Why, why not?

: In my case, I've installed the 64bit kernel. I develop some of my own software which has a fair amount of optimizations with the 64-bit architecture. [[User:Rybu|Rybu]]

:: 64-bit will run faster. I say install the AMD64 version. Don't let your new, fast 64-bit processor go to waste! [[User:SteveSims|SteveSims]] 06:16, 5 October 2007 (UTC)

== Black screen at boot ==

When try to boot gutsy-desktop-amd64 the screen turns black, even when i use "Safe Graphics" mode. Having a nVIDIA Quadro NVS 140M card

TURNS OUT I JUST NEED PATIENCE... sorry [[User:Zpon|Zpon]]

: Was doing a re-install, and got the problem again, have waited a loong time... [[User:Zpon|Zpon]] 09:58, 5 November 2007 (UTC)

I'm having a similar problem myself, except it started doing this only recently. Ubuntu will boot into low-graphics mode at first( and it will go through a bit of trouble to do that much, but then once it's up and running it seems to run fine. Here's a string of what the boot-up looks like. With the exception of the dialogue( second to last frame) I can just leave it and it'll boot, but it's still frustrating...
http://www.thinkwiki.org/wiki/Image:Ubuntu_T61_Boot_Errors.png
Gah, I don't know how to make it show up as a thumbnail. Sorry.

=== Still annoying ===

I still have this problem at boot up. I also have the nVIDIA card, and I get black screen instead of the splash screen. X eventually comes up, but I'd love to know how to fix this.

--Do you have 'vga=' enabled as a kernel parameter? If yes then remove that.
:I do not have 'vga=' but it still takes _very_ long time to boot and with a black screen (I also have a black screen when I am booting after successful installation)

==Update 2007-10-11 works fine==
Announcement. [[User:SteveSims|SteveSims]] 05:15, 11 October 2007 (UTC)

== Power Consumption ==

I have enabled laptop-mode (level 2) and also used PowerTOP to optimize the power consumption of my T61 with NVIDIA 140M.
But even though the brightness is set at minimum the power consumption just does not want to drop below 19W.
Is this a usual behaviour?

I used to get much lower power utilization but now I am seeing the same thing you do. I plan on doing some deeper looks soon and see why this change.

== Most programs won't install in the 10-18 install of AMD64 version; probably not a 64-bit issue ==

I tried installing the GStreamer plugins, VLC Media Player, and KolourPaint (a KDE application) from Add/Remove Programs and it told me the following:

<pre>Cannot install 'kolourpaint'

This application conflicts with other installed software. To install 'kolourpaint' the conflicting software must be removed first.

Switch to the 'synaptic' package manager to resolve this conflict.</pre>

I tried to install these programs/plugins one at a time, and got the same message (albeit with 'vlc', etc. instead of 'kolourpaint').

Of course, I don't know which packages conflict with them, so I can't use Synaptic to remove the conflicting packages. It did, however, successfully install Sysinfo. I went to Synaptic and found that there were no KDE packages installed. [[User:SteveSims|SteveSims]] 23:28, 19 October 2007 (UTC)

I just ran sudo apt-get update and I still can't install these things.

I also tried to install Battle for Wesnoth (at least the wesnoth-all package) and was told that it has unresolvable dependencies. "Depends: wesnoth but it is not going to be installed" and the same thing for about 9 or so other packages. [[User:SteveSims|SteveSims]] 23:53, 19 October 2007 (UTC)

== Networking craps out ==

The network on my T61 with Intel Corporation PRO/Wireless 4965 AG or AGN Network Connection (rev 61) card occasionally just goes away. If I

modprobe -r iwl4965
modprobe iwl4965
/etc/init.d/networking restart

it will come back, but this is annoying. Anybody have any ideas here?

There was a similar problem with an old version of wpa_supplicant a month ago but a fix has existed since Tribe 5. Can you post the relevent messages from /var/log/messages and /var/log/syslog? --[[User:Darrena|Darrena]] 12:00, 20 October 2007 (UTC)
: Logs /var/log/syslog http://pastebin.com/f29dcfc97 and /var/log/messages http://pastebin.com/m2a4e601b - hope this will help track down the problem...
: I get the same problems, several times a day, very annoying [[User:Zpon|Zpon]] 09:58, 5 November 2007 (UTC)

== Rotate Display when docked ==

I have a Thinkpad T61 running Windows Vista Ultimate (ick). I also have a minidock. Currently (when not crashing) I have it setup to use the wireless NIC when undocked. When I dock the laptop, it switches to the hardline NIC and rotates the display for my 19" portrait monitor. The resolution also changes, of course.

Is this possible with Ubuntu (or any distro) or will I have to do some manual fiddling everytime I dock/undock?

----
Yes it is possible but the how depends on your video card. If it is the intel card you can use xrandr to create a script to set the video up exactly how you want it and then bind that to a key. --[[User:Darrena|Darrena]] 21:04, 18 November 2007 (UTC)

== Bluetooth script error ==

cat /proc/acpi/ibm/bluetooth | awk '{ print $2 }' | while read line;
do
if [ $line == "enabled" ]; then
echo disable > /proc/acpi/ibm/bluetooth
else
echo enable > /proc/acpi/ibm/bluetooth
fi
break
done

should be:

cat /proc/acpi/ibm/bluetooth | awk '{ print $2 }' | while read line;
do
if [ $line = "enabled" ]; then
echo disable > /proc/acpi/ibm/bluetooth
else
echo enable > /proc/acpi/ibm/bluetooth
fi
break
done

right?

==GM965 instead of X3100 Intel graphics?==
My device manager shows this: 
[[Image:GM965_X3100.png|300px]]
 The T61 should have an X3100, and both are integrated onto the motherboard, so is Linux treating my X3100 like a GM965?

== Fn+F5 does not work by default ==

I have a 7664-18G with Bluetooth Version 2.0 + EDR, Intel 4965AGN. Using the script provided I can start Bluetooth, and wifi works also (without anything), but I can not use the function button to switch off/on wifi and/or bluetooth.

Could someone help me fixing this? [[User:Nagyv|Nagyv]] 10:47, 9 January 2008 (CET)

Install Ubuntu Gutsy Gibbon on a T61p

2008-01-28T23:47:41Z

A-j: /* Audio */

== Installing Gutsy Gibbon (7.10) on a T61p ==

== Introduction ==

This document outlines configuring Ubuntu 7.10 (Gutsy Gibbon) on your Thinkpad T61p. Most items will work out of the box and a base install will provide you with an almost completely working system. Due to the modular nature of the T61 there are many different configuration, please read carefully and only make the changes specific to your system.

Feel free to update this Wiki with your information however please ask questions on the Talk page.

== Installation Notes ==

<ol>
<li>install Ubuntu onto the laptop. The Live CD will boot in safe graphics mode for most users (but not all). However, the splash screen does not work for 64-bit users and perhaps 32-bit users as well. Be patient the system will boot, even though the screen is black. It may be faster to do the initial install using the alternate CD (text mode install).</li>

<li>After it is installed, fix issue: "no x session on first reboot after install" (see steps below)</li>
</ol>

Note: On lenovo t61p thinkpad with nVidia Corporation Quadro FX 570M graphics card the installer fails to create a usable xorg.conf file and the system reboots into an unusable black screen as X refuses to start. This is caused by the installer selecting the nv driver, which does not support this card. The vesa driver will allow X to start.

To fix this, you have to reboot into rescue mode and hand-edit xorg.conf to use vesa driver until the restricted nvidia driver is enabled.

Steps:
<ol>
<li>Choose Recovery Mode from the Grub boot menu.</li>
<li>Edit the xorg.conf file:
{{cmdroot|nano /etc/X11/xorg.conf}}</li>
<li>Scroll down until you see the section listed below and replace nv with vesa on the driver line:

<code>
Section "Device"
Identifier "nVidia Corporation G80 [Quadro FX 570M]"
Driver "nv"
BusID "PCI:1:0:0"
EndSection
</code></li>
<li>Hit {{key|Ctrl}}{{key|X}} to exit, {{key|Y}} then {{key|Enter}} to save.</li>
<li>Reboot: {{cmdroot|reboot}}</li>
</ol>

You should now get the GUI login, but all of the accelerated graphics eye candy will be disabled until you have updated the nvidia drivers as per the Display/Video Section.

If you have a Ubuntu 7.10 DVD, you could use the same to first launch a live CD version of Ubuntu. When the live CD boots up it asks for the installation of restricted nVidia drivers (internet connection required). Once the restricted drivers are installed. Use the "Install" option from the live CD session to start the installation of Ubuntu.

== Display/Video ==

The '''nv''' driver does not support the Nvidia 570M card at all. To enable accelerated 3D support click System->Administration->Restricted Drivers Manager. It will allow you to download and install an updated set of nvidia drivers. {{NOTE| If this is a fresh installation, you will get an error "can't get source for nvidia-glx-new", which means you need to update the package list: first, be sure that in System->Administration->Software Sources, the entry "Proprietary drivers for devices (restricted)" is checked. Then either click System->Administration->Update Manager->Check, or open a terminal and type "sudo apt-get update".}} On the next reboot you should get accelerated support and full graphics resolution (but still no splashscreen).{{NOTE| If the Restricted Drivers Manager fails to install the driver you can use the Envy tool from: http://albertomilone.com/nvidia_scripts1.html. This tool is unsupported and the only supported method of installing the Nvidia drivers is via Synaptic or the Restricted Drivers Manager}}
On the model with 1920x1200 video, the default fonts are very tiny. Change them with System->Preferences->Appearance->Fonts->Details.

== Brightness ==
source: [[ Installing Ubuntu 7.10 (Gutsy Gibbon) on a ThinkPad T61 ]]
====Nvidia Quadro N140 and 570M:====
The brightness controls do not work, however you can switch to a virtual terminal (ctrl+alt+F1) increase or decrease the brightness and then switch back to X (ctrl+alt+F7) without disrupting the running applications. In a few rare cases switching back to X (ctrl+alt+7) may freeze your computer with a black screen so save any open documents before switching out.

When using the '''vesa''' driver the brightness controls do work. So this problem seems to be related to the '''nvidia''' driver.

'''Update: Note that as of version 169.04 of the Nvidia driver brightness controls do work normally (with my 570M at least).'''

== Audio ==
*Fix ALSA:
Gutsy uses ALSA v1.0.14 by default. Unfortunately, the audio card is not supported using that version. The solution is to upgrade to v1.0.15 or above. At the time of this writing, there are no packages for this version; however, new users should search Synaptic because that will make the process much easier: search for alsa-base and determine whether the available version is at least v1.0.15. If there are no packages available, the driver must be compiled from source. Follow this guide http://ubuntuforums.org/showthread.php?t=612605 to install the alsa v1.0.15.
After restarting, open a terminal and run alsamixer. Use the left/right arrow keys to select the channels; make sure that PCM and headphone are not muted (use m key). Muting/unmuting input channels can cause interference, so experiment to produce the best sound quality.
--[[User:Jbrown96|Jbrown96]] 22:57, 24 December 2007 (UTC)

Everything except the mic works fine for me with ALSA 1.0.14. When I unmute the internal mic in alsamixer, it plays the mic sounds out the speakers.
--[[User:Chazchaz101|Chazchaz101]] 07:17, 28 December 2007 (UTC)

Same experience as Chazchaz101, but I could fix the microphone problem by adjusting the ALSA configuration as described in
source: [[Installing Ubuntu 7.10 (Gutsy_Gibbon) on a ThinkPad_T61#Microphone]].
--[[User:A-j|A-j]] 23:31, 28 January 2008 (UTC)

*fix sound buttons:
source: [[Installing Ubuntu 7.04 (Feisty Fawn) on a ThinkPad T61|Installing Ubuntu 7.04 (Feisty Fawn) on a ThinkPad T61]]

the volume control hotkeys are configured to control microphone volume out of the box.

fix: If you're using Gnome, from the System menu, click Preferences -> Sound, and in the Default Mixer Tracks field, choose PCM.

*fix volume control applet:

the volume control applet is configured to control microphone volume out of the box.

fix: If you're using Gnome, right-click the applet > preferences > Select the device and track to control

**do not change device (s/b HDA Intel)
**change track from Microphone to PCM

== Network/Internet ==

Some users report that IPv6 has large negative impact on internet connection speed (wired and wireless) on Ubuntu 7.10. If you are experiencing this, the following steps will allow you to disable IPv6 and restore your connection speed.
{{NOTE|There is a workaround to improve connectivity for Firefox. On the Firefox address bar type '''about:config''' and look for '''network.dns.disableIPv6''' and change its value to '''true'''[[Image:Ubuntu710_Firefox_Fix.png]].}}

Type the following in the terminal
{{cmduser|sudo gedit /etc/modprobe.d/aliases}}. The system may ask you to provide the Super User password. Once the file is opened, search for the following string, '''alias net-pf-10 ipv6'''.
Comment this line by prefixing a {{cmdresult|#}}. Now add a new line just below the commented line, '''alias net-pf-10 off'''.

[[Image:Update_to_Aliases.png]]

Now, save the file and restart Ubuntu.

Reference: Youtube video. [http://www.youtube.com/watch?v=Sd8nHsUevAY How-To: Fix a Slow Internet Connection in Ubuntu 7.10].

== Suspend with Nvidia Binary Driver ==

*Fix suspend with Nvidia binary drivers:

Follow the directions on the Ubuntu wiki. [https://help.ubuntu.com/community/NvidiaLaptopBinaryDriverSuspend Nvidia Binary Driver Suspend]

==Bluetooth==
Bluetooth works out of the box. Pressing Fn-F5 once will enable bluetooth, disable wireless, pressing again, enable both and pressing one more time will disable bluetooth.

If you would like to set bluetooth state independently the script below determines the current bluetooth state and toggles the device on or off.

First create a new file named bluetooth-toggle:
{{cmdroot|sudo touch /usr/sbin/bluetooth-toggle}}

Now open a editor:
{{cmdroot|sudo gedit /usr/sbin/bluetooth-toggle}}

Paste the following script:

#!/bin/bash
cat /proc/acpi/ibm/bluetooth | awk '{ print $2 }' | while read line;
do
if [ $line == "enabled" ]; then
echo disable > /proc/acpi/ibm/bluetooth
else
echo enable > /proc/acpi/ibm/bluetooth
fi
break
done

Now set the execute permissions:
{{cmdroot|sudo chmod +x /usr/sbin/bluetooth-toggle}}

You can invoke the script out of the console by typing sudo bluetooth-toggle or create a menu icon by using the menu editor under preferences using gksudo bluetooth-toggle as command line.

source: [[Installing Ubuntu 7.10 (Gutsy Gibbon) on a ThinkPad T61]]

You can also create a launcher for this script that you can stick in the GNOME panel.

==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. At least for me, the most recent (0.3) version used here works with sudo, gksudo and on the login page but not with the the screen saver. Also, you are still required to type your user name on the login screen.

There appears to be a method to make the reader work for the screensaver, but I haven't tested it yet.

1) Add the launchpad repository to your sources:
{{cmduser| sudo gedit /etc/apt/sources.lst}}
add the lines:
## LAUNCHPAD REPOSITORY
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

2) Install the following packages:

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

3) Test the package installation and connection to the reader:

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

A completed test 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:~$

4) Enable use of reader for authentication:

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

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

5) Add User(s):
For each user:
{{cmduser| sudo tf-tool --add-user your_user_name}}

You can safely ignore the error:
Unable to set ACL of aquired file: /etc/pam_thinkfinger/charlie.bir: Operation not supported

6) 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}}
add the line:
uinput

At this point, you should be ready to swipe!

Sources:
* Install ThinkFinger on Ubuntu: https://wiki.ubuntu.com/ThinkFinger
* [[Installing_Ubuntu_6.06_on_a_ThinkPad_T43#Fingerprint_Reader|Installing Ubuntu 6.06 on a ThinkPad T43]]

Install Ubuntu Gutsy Gibbon on a T61p

2008-01-24T16:15:14Z

A-j: /* Display/Video */

== Installing Gutsy Gibbon (7.10) on a T61p ==

== Introduction ==

This document outlines configuring Ubuntu 7.10 (Gutsy Gibbon) on your Thinkpad T61p. Most items will work out of the box and a base install will provide you with an almost completely working system. Due to the modular nature of the T61 there are many different configuration, please read carefully and only make the changes specific to your system.

Feel free to update this Wiki with your information however please ask questions on the Talk page.

== Installation Notes ==

<ol>
<li>install Ubuntu onto the laptop. The Live CD will boot in safe graphics mode for most users (but not all). However, the splash screen does not work for 64-bit users and perhaps 32-bit users as well. Be patient the system will boot, even though the screen is black. It may be faster to do the initial install using the alternate CD (text mode install).</li>

<li>After it is installed, fix issue: "no x session on first reboot after install" (see steps below)</li>
</ol>

Note: On lenovo t61p thinkpad with nVidia Corporation Quadro FX 570M graphics card the installer fails to create a usable xorg.conf file and the system reboots into an unusable black screen as X refuses to start. This is caused by the installer selecting the nv driver, which does not support this card. The vesa driver will allow X to start.

To fix this, you have to reboot into rescue mode and hand-edit xorg.conf to use vesa driver until the restricted nvidia driver is enabled.

Steps:
<ol>
<li>Choose Recovery Mode from the Grub boot menu.</li>
<li>Edit the xorg.conf file:
{{cmdroot|nano /etc/X11/xorg.conf}}</li>
<li>Scroll down until you see the section listed below and replace nv with vesa on the driver line:

<code>
Section "Device"
Identifier "nVidia Corporation G80 [Quadro FX 570M]"
Driver "nv"
BusID "PCI:1:0:0"
EndSection
</code></li>
<li>Hit {{key|Ctrl}}{{key|X}} to exit, {{key|Y}} then {{key|Enter}} to save.</li>
<li>Reboot: {{cmdroot|reboot}}</li>
</ol>

You should now get the GUI login, but all of the accelerated graphics eye candy will be disabled until you have updated the nvidia drivers as per the Display/Video Section.

If you have a Ubuntu 7.10 DVD, you could use the same to first launch a live CD version of Ubuntu. When the live CD boots up it asks for the installation of restricted nVidia drivers (internet connection required). Once the restricted drivers are installed. Use the "Install" option from the live CD session to start the installation of Ubuntu.

== Display/Video ==

The '''nv''' driver does not support the Nvidia 570M card at all. To enable accelerated 3D support click System->Administration->Restricted Drivers Manager. It will allow you to download and install an updated set of nvidia drivers. {{NOTE| If this is a fresh installation, you will get an error "can't get source for nvidia-glx-new", which means you need to update the package list: first, be sure that in System->Administration->Software Sources, the entry "Proprietary drivers for devices (restricted)" is checked. Then either click System->Administration->Update Manager->Check, or open a terminal and type "sudo apt-get update".}} On the next reboot you should get accelerated support and full graphics resolution (but still no splashscreen).{{NOTE| If the Restricted Drivers Manager fails to install the driver you can use the Envy tool from: http://albertomilone.com/nvidia_scripts1.html. This tool is unsupported and the only supported method of installing the Nvidia drivers is via Synaptic or the Restricted Drivers Manager}}
On the model with 1920x1200 video, the default fonts are very tiny. Change them with System->Preferences->Appearance->Fonts->Details.

== Brightness ==
source: [[ Installing Ubuntu 7.10 (Gutsy Gibbon) on a ThinkPad T61 ]]
====Nvidia Quadro N140 and 570M:====
The brightness controls do not work, however you can switch to a virtual terminal (ctrl+alt+F1) increase or decrease the brightness and then switch back to X (ctrl+alt+F7) without disrupting the running applications. In a few rare cases switching back to X (ctrl+alt+7) may freeze your computer with a black screen so save any open documents before switching out.

When using the '''vesa''' driver the brightness controls do work. So this problem seems to be related to the '''nvidia''' driver.

'''Update: Note that as of version 169.04 of the Nvidia driver brightness controls do work normally (with my 570M at least).'''

== Audio ==
*Fix ALSA:
Gutsy uses ALSA v1.0.14 by default. Unfortunately, the audio card is not supported using that version. The solution is to upgrade to v1.0.15 or above. At the time of this writing, there are no packages for this version; however, new users should search Synaptic because that will make the process much easier: search for alsa-base and determine whether the available version is at least v1.0.15. If there are no packages available, the driver must be compiled from source. Follow this guide http://ubuntuforums.org/showthread.php?t=612605 to install the alsa v1.0.15.
After restarting, open a terminal and run alsamixer. Use the left/right arrow keys to select the channels; make sure that PCM and headphone are not muted (use m key). Muting/unmuting input channels can cause interference, so experiment to produce the best sound quality.
--[[User:Jbrown96|Jbrown96]] 22:57, 24 December 2007 (UTC)

Everything except the mic works fine for me with ALSA 1.0.14. When I unmute the internal mic in alsamixer, it plays the mic sounds out the speakers.
--[[User:Chazchaz101|Chazchaz101]] 07:17, 28 December 2007 (UTC)

*fix sound buttons:
source: [[Installing Ubuntu 7.04 (Feisty Fawn) on a ThinkPad T61|Installing Ubuntu 7.04 (Feisty Fawn) on a ThinkPad T61]]

the volume control hotkeys are configured to control microphone volume out of the box.

fix: If you're using Gnome, from the System menu, click Preferences -> Sound, and in the Default Mixer Tracks field, choose PCM.

*fix volume control applet:

the volume control applet is configured to control microphone volume out of the box.

fix: If you're using Gnome, right-click the applet > preferences > Select the device and track to control

**do not change device (s/b HDA Intel)
**change track from Microphone to PCM

== Network/Internet ==

Some users report that IPv6 has large negative impact on internet connection speed (wired and wireless) on Ubuntu 7.10. If you are experiencing this, the following steps will allow you to disable IPv6 and restore your connection speed.
{{NOTE|There is a workaround to improve connectivity for Firefox. On the Firefox address bar type '''about:config''' and look for '''network.dns.disableIPv6''' and change its value to '''true'''[[Image:Ubuntu710_Firefox_Fix.png]].}}

Type the following in the terminal
{{cmduser|sudo gedit /etc/modprobe.d/aliases}}. The system may ask you to provide the Super User password. Once the file is opened, search for the following string, '''alias net-pf-10 ipv6'''.
Comment this line by prefixing a {{cmdresult|#}}. Now add a new line just below the commented line, '''alias net-pf-10 off'''.

[[Image:Update_to_Aliases.png]]

Now, save the file and restart Ubuntu.

Reference: Youtube video. [http://www.youtube.com/watch?v=Sd8nHsUevAY How-To: Fix a Slow Internet Connection in Ubuntu 7.10].

== Suspend with Nvidia Binary Driver ==

*Fix suspend with Nvidia binary drivers:

Follow the directions on the Ubuntu wiki. [https://help.ubuntu.com/community/NvidiaLaptopBinaryDriverSuspend Nvidia Binary Driver Suspend]

==Bluetooth==
Bluetooth works out of the box. Pressing Fn-F5 once will enable bluetooth, disable wireless, pressing again, enable both and pressing one more time will disable bluetooth.

If you would like to set bluetooth state independently the script below determines the current bluetooth state and toggles the device on or off.

First create a new file named bluetooth-toggle:
{{cmdroot|sudo touch /usr/sbin/bluetooth-toggle}}

Now open a editor:
{{cmdroot|sudo gedit /usr/sbin/bluetooth-toggle}}

Paste the following script:

#!/bin/bash
cat /proc/acpi/ibm/bluetooth | awk '{ print $2 }' | while read line;
do
if [ $line == "enabled" ]; then
echo disable > /proc/acpi/ibm/bluetooth
else
echo enable > /proc/acpi/ibm/bluetooth
fi
break
done

Now set the execute permissions:
{{cmdroot|sudo chmod +x /usr/sbin/bluetooth-toggle}}

You can invoke the script out of the console by typing sudo bluetooth-toggle or create a menu icon by using the menu editor under preferences using gksudo bluetooth-toggle as command line.

source: [[Installing Ubuntu 7.10 (Gutsy Gibbon) on a ThinkPad T61]]

You can also create a launcher for this script that you can stick in the GNOME panel.

==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. At least for me, the most recent (0.3) version used here works with sudo, gksudo and on the login page but not with the the screen saver. Also, you are still required to type your user name on the login screen.

There appears to be a method to make the reader work for the screensaver, but I haven't tested it yet.

1) Add the launchpad repository to your sources:
{{cmduser| sudo gedit /etc/apt/sources.lst}}
add the lines:
## LAUNCHPAD REPOSITORY
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

2) Install the following packages:

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

3) Test the package installation and connection to the reader:

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

A completed test 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:~$

4) Enable use of reader for authentication:

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

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

5) Add User(s):
For each user:
{{cmduser| sudo tf-tool --add-user your_user_name}}

You can safely ignore the error:
Unable to set ACL of aquired file: /etc/pam_thinkfinger/charlie.bir: Operation not supported

6) 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}}
add the line:
uinput

At this point, you should be ready to swipe!

Sources:
* Install ThinkFinger on Ubuntu: https://wiki.ubuntu.com/ThinkFinger
* [[Installing_Ubuntu_6.06_on_a_ThinkPad_T43#Fingerprint_Reader|Installing Ubuntu 6.06 on a ThinkPad T43]]