ThinkWiki - User contributions [en]

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

2007-10-20T08:12:24Z

Jankit: /* Still annoying */

==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.

'''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.

==Twinview?==

This was on the wiki so I moved it here for discussion:

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 possible to do set up Twinview with movies that don't span screens in the Applications->System Tools->Nvidia Settings?

== 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)

==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]]

==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]]

==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

=== 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.

==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?

Installing Ubuntu 7.10 (Gutsy Gibbon) on a ThinkPad T61

2007-10-13T09:05:40Z

Jankit: /* Bluetooth */

==Installation Notes ==

*If booting with the default options gives you a blank screen you should select the "Safe Graphics" menu choice when booting from the live CD.

*If you are doing a text mode install such as PXE/network then your screen will be corrupted during the process, a fix was released on September 28th either use a daily iso or one of the workarounds outlined at: https://bugs.launchpad.net/ubuntu/+source/xresprobe/+bug/127008

== Display/Video ==

=== Accelerated Video and Desktop Effects ===
'''Intel''' 2D and 3D accelerated video work out of the box.

Due to [https://bugs.launchpad.net/xorg-server/+bug/111257 | bug 111257], compiz is disabled on the Intel i965 based video cards. To fix it, download this file[http://www.fileden.com/files/2007/9/28/1467484/compizubuntuintel.zip], unzip it, and follow the instructions in "description and README."

''Note: If you enable Compiz on an Intel card there will be issues with viewing media files, please see the bug report above for details''

'''Nvidia''' 2D video works out of the box, to enable accelerated 3D support click System->Administration->Restricted Drivers Manager

===Installing Nvidia drivers manually===

{{WARN| Installing the drivers via Synaptic or the Restricted Drivers Manager are the only supported methods of installing the Nvidia driver, the method below (while it works for most people) is not supported}}

Download the drivers from http://www.nvidia.com/object/linux_display_ia32_100.14.19.html and save it to your Desktop.
Exit to a virtual terminal by pressing [CTRL]+[ALT]+[F2]

Stop the X server:

$ sudo /etc/init.d/gdm stop (stopping the X server)

Remove nvidia-glx-new

$ sudo apt-get remove nvidia-glx-new

Install the drivers:

$ sudo sh NVIDIA-Linux-x86-100.14.19-pkg1.run (depending on the version that will be online)

Follow instructions in the installer, when complete restart the X-Server with:

$ sudo /etc/init.d/gdm restart (restarting the X server)

===Multiple Monitors===

'''Nvidia N140m:'''

When using the default drivers (The open source "nv" drivers) you can use Administration->"Screens and Graphics" to setup the second monitor

Using the proprietary drivers you must use the Nvidia tool located at Applications->System Tools-> Nvidia X Server Settings.

It has been reported that the NVIDIA drivers tend to crash with xinerama enabled. 2 displays with xinerama off has been stable.

Twinview works but a movie will span both the laptop screen and second monitor or projector.
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 possible to do set up Twinview with movies that don't span screens in the Applications->System Tools->Nvidia Settings?

'''Intel X3100:'''

Plugging in an external monitor works, but is a clone of the built-in LCD by default. Following the instructions on [http://www.thinkwiki.org/wiki/Intel_Graphics_Media_Accelerator_X3100 this page] to extend your desktop to the second monitor does *not* work; it results in the crash described [http://lists.freedesktop.org/archives/xorg/2007-April/023326.html here]. According to [http://lists.freedesktop.org/archives/xorg/2007-April/023335.html this post] and [https://bugs.freedesktop.org/show_bug.cgi?id=10706 this bug report], the problem is a new Xinerama implementation and an old config file.

To extend your desktop to the second monitor, you'll want to do what [http://wiki.debian.org/XStrikeForce/ReleaseNotes this page] suggests (under "Dual-Head config breakage with xserver-xorg-video-intel").

Below is an example for a 1680x1050 built-in LCD and a 1600x1200 external LCD:
Add a "Virtual 3280 1200" line in the Display SubSection of the Screen Section in your xorg.conf:
{{Fixme|If someone could include an example of the change described above it would be greatly appreciated}}
Exit to a virtual terminal (press: ctrl-alt-F1), login and type the following:

{{cmdroot|sudo /etc/init.d/gdm stop}}

{{cmdroot|xrandr --output LVDS --auto}}

To set the built-in LCD to ouput 1680x1050

{{cmdroot|xrandr --output VGA --right-of LVDS}}

To extend the desktop

=== Fonts on High-Res Screens ===

On high-res screens (e.g. 15" 1680x1050), the default fonts are too big ([https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/99145 Launchpad bug report]). You can fix this by following these steps:

# Open System->Preferences->Appearance
# Select the "Fonts" tab
# Click the "Details" button (lower right)
# Adjust the Resolution down to 96dpi
# Make sure you have Subpixel (LCD) Smoothing enabled
# Save the preferences

If you also want small fonts on the GDM login window, you can do this:

# Open System->Administration->Login Window
# Select the 'Security' tab
# Click the 'Configure X-Server' button
# Append '-dpi 96' (without quotes) to the text in the 'Command' field
# Reboot the computer.

=== Brightness ===
====Intel X3100:====
The brightness controls do not work out of the box, but they should work once you apply all of the system updates.

However, there now appears to be a bug where the brightness controls stop working after you resume from a suspend.

Until the brightness bugs are finally worked out, you can install "xbacklight" (Applications -> Accessories -> Terminal, type "sudo apt-get install xbacklight" without the quotation marks and hit enter), which allows you to set the brightness from the command line and provides a greater range of brightness values.

To set brightness, go back to the terminal and type "xbacklight =VALUE" where VALUE is a number from 0 to 100 for how bright you want your display to be.

=====Creating brightness shortcuts=====
If you don't want to use the terminal you can set up shortcuts to pre-defined brightness levels:

1) Right-click on the desktop and select Create Launcher...

2) Make it look like this: 
[[Image:XBacklight launcher 50.png]] 
The 50 means that the backlight will be at 50% brightness. If you want your shortcut to set the brightness to 100% then simply replace 50 with 100 when you create your launcher (Shortcuts in Windows are analogous to Launchers in Ubuntu). Many people use at least two brightness levels (for example, 100% when on AC power, 50% when on battery power) so it's a good idea to make a launcher for each commonly used brightness level. I also suggest adding them to the upper panel (Linux for menu bar) so that they're easily accessible. If you want, you can use your own custom icons by right-clicking the launcher, selecting Properties, and then clicking on the picture in the Properties window and browsing for your own.

====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

switching back to X (ctrl+alt+7) may freeze your computer with a black screen.

== Audio ==

=== Inextricably Linked to the Modem ===
Make sure that you have the modem enabled in the BIOS. If it is disabled, you may discover (with much consternation) that your audio is also disabled. In this situation, your drivers may still load, but you will get an error message whenever you try to play audio.

After trying all of the ALSA related fixes for this machine, with no love, I remembered what a colleague had said about his T60, and tried this on a hunch. Blammo, it worked!

===Enabling Audio controls===

By default, the sound may be disabled and the volume control buttons on the laptop (up by the ThinkVantage button) and the volume control applet (up by the clock) will not control the speaker volume (they actually control the microphone!). https://bugs.launchpad.net/ubuntu/+bug/136287
this bug report links to a fixed version from an Ubuntu dev a fixed version is available
To fix this:

# Right-click on the volume control applet (by the clock) and select "Open Volume Control"
# In the "Switches" tab, make sure "Headphone" and "Speaker" are both checked.
# Close the Volume control.
# Right-click on the volume control applet again and select "Preferences".
# Make sure the device is set to "HDA Intel (Alsa mixer)" and highlight the "PCM" option.
# Close the preferences.
# Select System->Preferences->Sound.
# In the "Default Mixer Tracks" section, make sure "PCM" is highlighted.
# Close the sound preferences.

You should now hear sound and be able to control the volume using the laptop buttons or volume applet.

The mute button on the laptop does not work.

===Microphone===
'''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.

===Sound Cracking===
The sound may be cracking if ALSA is used, try to switch to the OSS driver in system => preference => sound => devices => Music and movies, select OSS - Open sound system (instead of ALSA)

The above does not appear to work for everyone.

Another thing to check is to see if this issue is only occurring for Rhythmbox (which is where i noticed this issue). If this is the case, go to Edit > Preferences > Playback > and Check "Use Crossfading Backend"
Restart Rhythmbox and you should have better audio quality.

===Hissing===
Once sound started working, it produced a lot of hissing during playback, and even when idle. Here's how I fixed it:

# Run "alsamixer".
# Arrow over to "Mic", and hit "M" to mute.
# Arrow over to the first "Docking", and hit "M" to mute.
# Arrow to the first "Internal", and hit "M" to mute.

Now, make sure that "Headphon" and/or "Speaker" are _not_ muted, and that "PCM" is at a reasonable level (say ~70) so you don't make your ears bleed, and try playing something back. ''(<Esc> will exit alsamixer)''

== Webcam ==
Webcam works now with kopete after installing all updates.

== Modem ==

The modem works with the Linuxant drivers available at http://www.linuxant.com

==Bluetooth==
Bluettoth works out of the box. No need for the following script, '''Fn-F5''' key would do the job. Remember pressing Fn-F5 once would enable bluetooth, disable wireless, pressing again, enable both and pressing one more time would disable bluetooth.

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:

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.

== Fingerprint Reader ==

The reader works with ThinkFinger. General instructions available [http://www.thinkwiki.org/wiki/Integrated_Fingerprint_Reader here] and [https://wiki.ubuntu.com/ThinkFinger here].
Instructions in French available at http://doc.ubuntu-fr.org/materiel/thinkfinger

Prebuilt packages are available from jldugger using Launchpad's PPA:

Add the thinkfinger package repository by creating {{path|/etc/apt/sources.list.d/thinkfinger.list}} with these two lines:

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

Then update the package database and install packages:

{{cmduser|sudo apt-get update}}
{{cmduser|sudo apt-get install libpam-thinkfinger libthinkfinger-dev libthinkfinger-doc libthinkfinger0 thinkfinger-tools}}

After the package is installed add the following two lines to {{path|/etc/pam.d/common-auth}}

auth sufficient pam_thinkfinger.so
auth required pam_unix.so try_first_pass

Edit {{path|/etc/modules}} and add the following line:

uinput

Load the module manually for this session:

{{cmduser| sudo modprobe uinput}}

Summary:
* Recording fingerprints works
* Login works
* The password must be entered to unlock a locked screensaver
* sudo works
* gksu and gksudo hang : for example it is necessary to run synaptic twice and enter your password upon failure. To be able to use the Finger print reader in the session subsequently, kill the hanging gksu/gksudo process. A workaround is editing the Gnome System Menu (alacarte) to specify sudo instead of gksu/gksudo for the launching command and choose type "Application in Terminal" : this opens an extra terminal window for each superuser application you want to use though.

== Trackpad scrolling ==

Trackpad scrolling works out of the box in the standard thinkpad way: Slide your finger up and down the very right edge of the trackpad.
Note that /etc/X11/xorg.conf will be changed and the edge scrolling will be disabled after running nvidia-xconfig , copy the trackpad section from the backup of xorg.conf

To enable using the middle mouse button to scroll, add the following lines to the "Configured Mouse" section in
{{path|/etc/X11/xorg.conf}}:

Option "EmulateWheel" "true"
Option "EmulateWheelButton" "2"

== Hibernate/Suspend ==

=== Blank screen fix for intel graphics cards===

This fix is for Intel Graphics Cards only.

You may get a blank screen when resuming from suspend or hibernate ([https://bugs.launchpad.net/ubuntu/+bug/134391 Launchpad bug report]). If so, try editing {{path|/boot/grub/menu.lst}}, adding "acpi_sleep=s3_bios" (no quotes) to the "defoptions" list so that it looks something like this:

## additional options to use with the default boot option, but not with the
## alternatives
## e.g. defoptions=vga=791 resume=/dev/hda5
# defoptions=quiet splash '''acpi_sleep=s3_bios'''

Once you have edited the line and added the acpi_sleep parameter, you need to run

$ sudo update-grub

Note that if you get the blank screen upon resume, a quick-fix is to switch to a console (Ctrl-Alt-F1) and then back to X (Ctrl-Alt-F7). This will usually bring the display back to life. However, the long-term fix is to add the acpi_sleep parameter as shown above.

=== How to Suspend with nVidia 140m/570m ===

The suspend to RAM will work with the nVidia card and the proprietary drivers, but it requires some file editing. It did not work for me out of the box. Using the package manager, download and install the latest nVidia drivers (100.14.19+2.6.2.4-12.4 at time of writing). I also had to use the 2.6.22-12-generic kernel image (the 2.6.22-13 image did not work with this driver --- I'm assuming it has to match wit the nVidia version, but I am not an expert).

Once you have it installed and working, you have to make a change to {{path|/etc/default/acpi-support}}. Open the file in your favorite editor and change the following lines:

$ sudo nano /etc/default/acpi-support

{{path|/etc/default/acpi-support}}
# Should we save and restore state using the VESA BIOS Extensions?
SAVE_VBE_STATE=false
...
# Should we attempt to warm-boot the video hardware on resume?
POST_VIDEO=false
...
# Set the following to "platform" if you want to use ACPI to shut down
# your machine on hibernation
HIBERNATE_MODE=platform

This allowed me to suspend and resume, but after two suspends the wireless wouldn't work anymore. Theoretically, ACPI unloads the network drivers before suspending, but it doesn't seem to work correctly so I added these to the blacklist modules manually (in the same file as above:

{{path|/etc/default/acpi-support}}
# Add modules to this list to have them removed before suspend and reloaded
# on resume. An example would be MODULES="em8300 yenta_socket"
#
# Note that network cards and USB controllers will automatically be unloaded
# unless they're listed in MODULES_WHITELIST
MODULES="iwl4965 iwlwifi_mac80211 cfg80211"

Your wifi modules may be different. (I have the intel AGN wireless card -- I don't know if these modules are different for other cards.)

This allows me to suspend to ram; I haven't had any problems with it so far. I haven't gotten hibernate (suspend to disk) working, so there may be additional things you need to do for that. (I think part of my problem is that I don't have enough swap, but I don't care enough to actually fix it.)

/*The fix does not work for me. I have a T61 7664-17U(NVS 140m, 4965agn). The computers suspend, but when it wakes up it hangs up and I have to pull out the battery to restart it.*/

General hint: Do not install the package "hibernate" or the gnome-power-manager will fail to suspend/hibernate your computer. If you have installed the package don't forget to purge the configuration. (sudo apt-get remove hibernate --purge)

== Items that work out of the box ==

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

'''Nvidia:''' 2D works, 3D requires the installation of the proprietary drivers

'''Wireless:''' Atheros and Intel cards both tested.

'''Bluetooth:''' Tested with both a bluetooth headset and an HTC 8525

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

'''Firewire''' Tested with hard drive

'''Wireless switch'''

'''4-in-1 card reader'''

'''Headphones''' You may need to enable Headphone out: Right-click on the volume control and select open volume control. Click the switches tab and then check the headphones box.

'''Keyboard Shortcuts:'''
http://www.thinkwiki.org/index.php?title=Installing_Ubuntu_7.10_%28Gutsy_Gibbon%29_Tribe_5_on_a_ThinkPad_T61&action=edit&section=8
* 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-F12 hibernates (to disk)
* PrtSc opens the screenshot dialog

'''Docking Stations:'''

All docking station models should work and the following features have been tested:

* DVI or Analog video: You can switch to it using "Administration->Screens and Graphics", if you are using the proprietary Nvidia drivers you must use the Nvidia Control Panel.

* Network Pass-through

* Modem Pass-through

* USB ports: Connected upon docking

* PS/2 Ports

== Items that don't work ==

* Wireless USB/UWB - https://bugs.launchpad.net/ubuntu/+bug/136287
* USB ports can end up temporarily disabled - https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/126369
* Wireless activity LED

== Power consumption ==

Gutsy is the first version of Ubuntu to feature a tickless kernel (i386 only, not in AMD64 yet). Power consumption
can be monitored using the powertop tool under Ubuntu and using Lenovo battery monitor
under Windows.

$ sudo apt-get install powertop
$ sudo powertop

I couldn't find any difference in power consumption between the i386 tickless kernel (even with 70ms average sleep in C4)
and AMD64 kernel (2ms average sleep in C4). It would be expected that considerably less power would be consumed for the
i386 tickless kernel.

There is also a graph available by Right-clicking on the battery icon and selecting Power History.

These are the figures measured on a T61 15.4" 1680x1050 screen 7300 processor (2GHz) 2GB RAM, Intel X3100 graphics
with 4965 wifi, Bluetooth and UWB.

{| border=1 cellpadding=5
|-
| 12.3W
| Windows XP Pro, all radios on, about 50% brightness
|-
| 16.7W
| Gutsy, all radios on, 50% brightness
|-
| 19.6W
| Gutsy, all radios on, 100% brightness
|-
| 14.2W
| Gutsy, all radios on, 10% brightness
|-
| -1.0W
| Turning the physical radio switch to off on the front reduces power consumption by 1 watt.
|}

Adding the Nvidia card increases the laptops power requirements.

These are the figures measured on a T61 14" 1440x900 screen 2.2ghz Core2Duo 2GB RAM, Nvidia 140m video, IWL4965 wifi and Bluetooth (Disabled):

{| border=1 cellpadding=5
|-
| 18.3W
| Gutsy, all radios on, 50% brightness
|-
| 19.4W
| Gutsy, all radios on, 100% brightness
|-
| 16.0W
| Gutsy, all radios on, 10% brightness
|-
|}

[[Category: T61]] [[Category: Ubuntu 7.10]]

Installing Ubuntu 7.10 (Gutsy Gibbon) on a ThinkPad T61

2007-10-13T09:02:13Z

Jankit: /* Microphone */

==Installation Notes ==

*If booting with the default options gives you a blank screen you should select the "Safe Graphics" menu choice when booting from the live CD.

*If you are doing a text mode install such as PXE/network then your screen will be corrupted during the process, a fix was released on September 28th either use a daily iso or one of the workarounds outlined at: https://bugs.launchpad.net/ubuntu/+source/xresprobe/+bug/127008

== Display/Video ==

=== Accelerated Video and Desktop Effects ===
'''Intel''' 2D and 3D accelerated video work out of the box.

Due to [https://bugs.launchpad.net/xorg-server/+bug/111257 | bug 111257], compiz is disabled on the Intel i965 based video cards. To fix it, download this file[http://www.fileden.com/files/2007/9/28/1467484/compizubuntuintel.zip], unzip it, and follow the instructions in "description and README."

''Note: If you enable Compiz on an Intel card there will be issues with viewing media files, please see the bug report above for details''

'''Nvidia''' 2D video works out of the box, to enable accelerated 3D support click System->Administration->Restricted Drivers Manager

===Installing Nvidia drivers manually===

{{WARN| Installing the drivers via Synaptic or the Restricted Drivers Manager are the only supported methods of installing the Nvidia driver, the method below (while it works for most people) is not supported}}

Download the drivers from http://www.nvidia.com/object/linux_display_ia32_100.14.19.html and save it to your Desktop.
Exit to a virtual terminal by pressing [CTRL]+[ALT]+[F2]

Stop the X server:

$ sudo /etc/init.d/gdm stop (stopping the X server)

Remove nvidia-glx-new

$ sudo apt-get remove nvidia-glx-new

Install the drivers:

$ sudo sh NVIDIA-Linux-x86-100.14.19-pkg1.run (depending on the version that will be online)

Follow instructions in the installer, when complete restart the X-Server with:

$ sudo /etc/init.d/gdm restart (restarting the X server)

===Multiple Monitors===

'''Nvidia N140m:'''

When using the default drivers (The open source "nv" drivers) you can use Administration->"Screens and Graphics" to setup the second monitor

Using the proprietary drivers you must use the Nvidia tool located at Applications->System Tools-> Nvidia X Server Settings.

It has been reported that the NVIDIA drivers tend to crash with xinerama enabled. 2 displays with xinerama off has been stable.

Twinview works but a movie will span both the laptop screen and second monitor or projector.
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 possible to do set up Twinview with movies that don't span screens in the Applications->System Tools->Nvidia Settings?

'''Intel X3100:'''

Plugging in an external monitor works, but is a clone of the built-in LCD by default. Following the instructions on [http://www.thinkwiki.org/wiki/Intel_Graphics_Media_Accelerator_X3100 this page] to extend your desktop to the second monitor does *not* work; it results in the crash described [http://lists.freedesktop.org/archives/xorg/2007-April/023326.html here]. According to [http://lists.freedesktop.org/archives/xorg/2007-April/023335.html this post] and [https://bugs.freedesktop.org/show_bug.cgi?id=10706 this bug report], the problem is a new Xinerama implementation and an old config file.

To extend your desktop to the second monitor, you'll want to do what [http://wiki.debian.org/XStrikeForce/ReleaseNotes this page] suggests (under "Dual-Head config breakage with xserver-xorg-video-intel").

Below is an example for a 1680x1050 built-in LCD and a 1600x1200 external LCD:
Add a "Virtual 3280 1200" line in the Display SubSection of the Screen Section in your xorg.conf:
{{Fixme|If someone could include an example of the change described above it would be greatly appreciated}}
Exit to a virtual terminal (press: ctrl-alt-F1), login and type the following:

{{cmdroot|sudo /etc/init.d/gdm stop}}

{{cmdroot|xrandr --output LVDS --auto}}

To set the built-in LCD to ouput 1680x1050

{{cmdroot|xrandr --output VGA --right-of LVDS}}

To extend the desktop

=== Fonts on High-Res Screens ===

On high-res screens (e.g. 15" 1680x1050), the default fonts are too big ([https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/99145 Launchpad bug report]). You can fix this by following these steps:

# Open System->Preferences->Appearance
# Select the "Fonts" tab
# Click the "Details" button (lower right)
# Adjust the Resolution down to 96dpi
# Make sure you have Subpixel (LCD) Smoothing enabled
# Save the preferences

If you also want small fonts on the GDM login window, you can do this:

# Open System->Administration->Login Window
# Select the 'Security' tab
# Click the 'Configure X-Server' button
# Append '-dpi 96' (without quotes) to the text in the 'Command' field
# Reboot the computer.

=== Brightness ===
====Intel X3100:====
The brightness controls do not work out of the box, but they should work once you apply all of the system updates.

However, there now appears to be a bug where the brightness controls stop working after you resume from a suspend.

Until the brightness bugs are finally worked out, you can install "xbacklight" (Applications -> Accessories -> Terminal, type "sudo apt-get install xbacklight" without the quotation marks and hit enter), which allows you to set the brightness from the command line and provides a greater range of brightness values.

To set brightness, go back to the terminal and type "xbacklight =VALUE" where VALUE is a number from 0 to 100 for how bright you want your display to be.

=====Creating brightness shortcuts=====
If you don't want to use the terminal you can set up shortcuts to pre-defined brightness levels:

1) Right-click on the desktop and select Create Launcher...

2) Make it look like this: 
[[Image:XBacklight launcher 50.png]] 
The 50 means that the backlight will be at 50% brightness. If you want your shortcut to set the brightness to 100% then simply replace 50 with 100 when you create your launcher (Shortcuts in Windows are analogous to Launchers in Ubuntu). Many people use at least two brightness levels (for example, 100% when on AC power, 50% when on battery power) so it's a good idea to make a launcher for each commonly used brightness level. I also suggest adding them to the upper panel (Linux for menu bar) so that they're easily accessible. If you want, you can use your own custom icons by right-clicking the launcher, selecting Properties, and then clicking on the picture in the Properties window and browsing for your own.

====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

switching back to X (ctrl+alt+7) may freeze your computer with a black screen.

== Audio ==

=== Inextricably Linked to the Modem ===
Make sure that you have the modem enabled in the BIOS. If it is disabled, you may discover (with much consternation) that your audio is also disabled. In this situation, your drivers may still load, but you will get an error message whenever you try to play audio.

After trying all of the ALSA related fixes for this machine, with no love, I remembered what a colleague had said about his T60, and tried this on a hunch. Blammo, it worked!

===Enabling Audio controls===

By default, the sound may be disabled and the volume control buttons on the laptop (up by the ThinkVantage button) and the volume control applet (up by the clock) will not control the speaker volume (they actually control the microphone!). https://bugs.launchpad.net/ubuntu/+bug/136287
this bug report links to a fixed version from an Ubuntu dev a fixed version is available
To fix this:

# Right-click on the volume control applet (by the clock) and select "Open Volume Control"
# In the "Switches" tab, make sure "Headphone" and "Speaker" are both checked.
# Close the Volume control.
# Right-click on the volume control applet again and select "Preferences".
# Make sure the device is set to "HDA Intel (Alsa mixer)" and highlight the "PCM" option.
# Close the preferences.
# Select System->Preferences->Sound.
# In the "Default Mixer Tracks" section, make sure "PCM" is highlighted.
# Close the sound preferences.

You should now hear sound and be able to control the volume using the laptop buttons or volume applet.

The mute button on the laptop does not work.

===Microphone===
'''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.

===Sound Cracking===
The sound may be cracking if ALSA is used, try to switch to the OSS driver in system => preference => sound => devices => Music and movies, select OSS - Open sound system (instead of ALSA)

The above does not appear to work for everyone.

Another thing to check is to see if this issue is only occurring for Rhythmbox (which is where i noticed this issue). If this is the case, go to Edit > Preferences > Playback > and Check "Use Crossfading Backend"
Restart Rhythmbox and you should have better audio quality.

===Hissing===
Once sound started working, it produced a lot of hissing during playback, and even when idle. Here's how I fixed it:

# Run "alsamixer".
# Arrow over to "Mic", and hit "M" to mute.
# Arrow over to the first "Docking", and hit "M" to mute.
# Arrow to the first "Internal", and hit "M" to mute.

Now, make sure that "Headphon" and/or "Speaker" are _not_ muted, and that "PCM" is at a reasonable level (say ~70) so you don't make your ears bleed, and try playing something back. ''(<Esc> will exit alsamixer)''

== Webcam ==
Webcam works now with kopete after installing all updates.

== Modem ==

The modem works with the Linuxant drivers available at http://www.linuxant.com

==Bluetooth==

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:

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.

== Fingerprint Reader ==

The reader works with ThinkFinger. General instructions available [http://www.thinkwiki.org/wiki/Integrated_Fingerprint_Reader here] and [https://wiki.ubuntu.com/ThinkFinger here].
Instructions in French available at http://doc.ubuntu-fr.org/materiel/thinkfinger

Prebuilt packages are available from jldugger using Launchpad's PPA:

Add the thinkfinger package repository by creating {{path|/etc/apt/sources.list.d/thinkfinger.list}} with these two lines:

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

Then update the package database and install packages:

{{cmduser|sudo apt-get update}}
{{cmduser|sudo apt-get install libpam-thinkfinger libthinkfinger-dev libthinkfinger-doc libthinkfinger0 thinkfinger-tools}}

After the package is installed add the following two lines to {{path|/etc/pam.d/common-auth}}

auth sufficient pam_thinkfinger.so
auth required pam_unix.so try_first_pass

Edit {{path|/etc/modules}} and add the following line:

uinput

Load the module manually for this session:

{{cmduser| sudo modprobe uinput}}

Summary:
* Recording fingerprints works
* Login works
* The password must be entered to unlock a locked screensaver
* sudo works
* gksu and gksudo hang : for example it is necessary to run synaptic twice and enter your password upon failure. To be able to use the Finger print reader in the session subsequently, kill the hanging gksu/gksudo process. A workaround is editing the Gnome System Menu (alacarte) to specify sudo instead of gksu/gksudo for the launching command and choose type "Application in Terminal" : this opens an extra terminal window for each superuser application you want to use though.

== Trackpad scrolling ==

Trackpad scrolling works out of the box in the standard thinkpad way: Slide your finger up and down the very right edge of the trackpad.
Note that /etc/X11/xorg.conf will be changed and the edge scrolling will be disabled after running nvidia-xconfig , copy the trackpad section from the backup of xorg.conf

To enable using the middle mouse button to scroll, add the following lines to the "Configured Mouse" section in
{{path|/etc/X11/xorg.conf}}:

Option "EmulateWheel" "true"
Option "EmulateWheelButton" "2"

== Hibernate/Suspend ==

=== Blank screen fix for intel graphics cards===

This fix is for Intel Graphics Cards only.

You may get a blank screen when resuming from suspend or hibernate ([https://bugs.launchpad.net/ubuntu/+bug/134391 Launchpad bug report]). If so, try editing {{path|/boot/grub/menu.lst}}, adding "acpi_sleep=s3_bios" (no quotes) to the "defoptions" list so that it looks something like this:

## additional options to use with the default boot option, but not with the
## alternatives
## e.g. defoptions=vga=791 resume=/dev/hda5
# defoptions=quiet splash '''acpi_sleep=s3_bios'''

Once you have edited the line and added the acpi_sleep parameter, you need to run

$ sudo update-grub

Note that if you get the blank screen upon resume, a quick-fix is to switch to a console (Ctrl-Alt-F1) and then back to X (Ctrl-Alt-F7). This will usually bring the display back to life. However, the long-term fix is to add the acpi_sleep parameter as shown above.

=== How to Suspend with nVidia 140m/570m ===

The suspend to RAM will work with the nVidia card and the proprietary drivers, but it requires some file editing. It did not work for me out of the box. Using the package manager, download and install the latest nVidia drivers (100.14.19+2.6.2.4-12.4 at time of writing). I also had to use the 2.6.22-12-generic kernel image (the 2.6.22-13 image did not work with this driver --- I'm assuming it has to match wit the nVidia version, but I am not an expert).

Once you have it installed and working, you have to make a change to {{path|/etc/default/acpi-support}}. Open the file in your favorite editor and change the following lines:

$ sudo nano /etc/default/acpi-support

{{path|/etc/default/acpi-support}}
# Should we save and restore state using the VESA BIOS Extensions?
SAVE_VBE_STATE=false
...
# Should we attempt to warm-boot the video hardware on resume?
POST_VIDEO=false
...
# Set the following to "platform" if you want to use ACPI to shut down
# your machine on hibernation
HIBERNATE_MODE=platform

This allowed me to suspend and resume, but after two suspends the wireless wouldn't work anymore. Theoretically, ACPI unloads the network drivers before suspending, but it doesn't seem to work correctly so I added these to the blacklist modules manually (in the same file as above:

{{path|/etc/default/acpi-support}}
# Add modules to this list to have them removed before suspend and reloaded
# on resume. An example would be MODULES="em8300 yenta_socket"
#
# Note that network cards and USB controllers will automatically be unloaded
# unless they're listed in MODULES_WHITELIST
MODULES="iwl4965 iwlwifi_mac80211 cfg80211"

Your wifi modules may be different. (I have the intel AGN wireless card -- I don't know if these modules are different for other cards.)

This allows me to suspend to ram; I haven't had any problems with it so far. I haven't gotten hibernate (suspend to disk) working, so there may be additional things you need to do for that. (I think part of my problem is that I don't have enough swap, but I don't care enough to actually fix it.)

/*The fix does not work for me. I have a T61 7664-17U(NVS 140m, 4965agn). The computers suspend, but when it wakes up it hangs up and I have to pull out the battery to restart it.*/

General hint: Do not install the package "hibernate" or the gnome-power-manager will fail to suspend/hibernate your computer. If you have installed the package don't forget to purge the configuration. (sudo apt-get remove hibernate --purge)

== Items that work out of the box ==

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

'''Nvidia:''' 2D works, 3D requires the installation of the proprietary drivers

'''Wireless:''' Atheros and Intel cards both tested.

'''Bluetooth:''' Tested with both a bluetooth headset and an HTC 8525

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

'''Firewire''' Tested with hard drive

'''Wireless switch'''

'''4-in-1 card reader'''

'''Headphones''' You may need to enable Headphone out: Right-click on the volume control and select open volume control. Click the switches tab and then check the headphones box.

'''Keyboard Shortcuts:'''
http://www.thinkwiki.org/index.php?title=Installing_Ubuntu_7.10_%28Gutsy_Gibbon%29_Tribe_5_on_a_ThinkPad_T61&action=edit&section=8
* 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-F12 hibernates (to disk)
* PrtSc opens the screenshot dialog

'''Docking Stations:'''

All docking station models should work and the following features have been tested:

* DVI or Analog video: You can switch to it using "Administration->Screens and Graphics", if you are using the proprietary Nvidia drivers you must use the Nvidia Control Panel.

* Network Pass-through

* Modem Pass-through

* USB ports: Connected upon docking

* PS/2 Ports

== Items that don't work ==

* Wireless USB/UWB - https://bugs.launchpad.net/ubuntu/+bug/136287
* USB ports can end up temporarily disabled - https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/126369
* Wireless activity LED

== Power consumption ==

Gutsy is the first version of Ubuntu to feature a tickless kernel (i386 only, not in AMD64 yet). Power consumption
can be monitored using the powertop tool under Ubuntu and using Lenovo battery monitor
under Windows.

$ sudo apt-get install powertop
$ sudo powertop

I couldn't find any difference in power consumption between the i386 tickless kernel (even with 70ms average sleep in C4)
and AMD64 kernel (2ms average sleep in C4). It would be expected that considerably less power would be consumed for the
i386 tickless kernel.

There is also a graph available by Right-clicking on the battery icon and selecting Power History.

These are the figures measured on a T61 15.4" 1680x1050 screen 7300 processor (2GHz) 2GB RAM, Intel X3100 graphics
with 4965 wifi, Bluetooth and UWB.

{| border=1 cellpadding=5
|-
| 12.3W
| Windows XP Pro, all radios on, about 50% brightness
|-
| 16.7W
| Gutsy, all radios on, 50% brightness
|-
| 19.6W
| Gutsy, all radios on, 100% brightness
|-
| 14.2W
| Gutsy, all radios on, 10% brightness
|-
| -1.0W
| Turning the physical radio switch to off on the front reduces power consumption by 1 watt.
|}

Adding the Nvidia card increases the laptops power requirements.

These are the figures measured on a T61 14" 1440x900 screen 2.2ghz Core2Duo 2GB RAM, Nvidia 140m video, IWL4965 wifi and Bluetooth (Disabled):

{| border=1 cellpadding=5
|-
| 18.3W
| Gutsy, all radios on, 50% brightness
|-
| 19.4W
| Gutsy, all radios on, 100% brightness
|-
| 16.0W
| Gutsy, all radios on, 10% brightness
|-
|}

[[Category: T61]] [[Category: Ubuntu 7.10]]

Installing Ubuntu 7.10 (Gutsy Gibbon) on a ThinkPad T61

2007-10-13T08:58:52Z

Jankit:

==Installation Notes ==

*If booting with the default options gives you a blank screen you should select the "Safe Graphics" menu choice when booting from the live CD.

*If you are doing a text mode install such as PXE/network then your screen will be corrupted during the process, a fix was released on September 28th either use a daily iso or one of the workarounds outlined at: https://bugs.launchpad.net/ubuntu/+source/xresprobe/+bug/127008

== Display/Video ==

=== Accelerated Video and Desktop Effects ===
'''Intel''' 2D and 3D accelerated video work out of the box.

Due to [https://bugs.launchpad.net/xorg-server/+bug/111257 | bug 111257], compiz is disabled on the Intel i965 based video cards. To fix it, download this file[http://www.fileden.com/files/2007/9/28/1467484/compizubuntuintel.zip], unzip it, and follow the instructions in "description and README."

''Note: If you enable Compiz on an Intel card there will be issues with viewing media files, please see the bug report above for details''

'''Nvidia''' 2D video works out of the box, to enable accelerated 3D support click System->Administration->Restricted Drivers Manager

===Installing Nvidia drivers manually===

{{WARN| Installing the drivers via Synaptic or the Restricted Drivers Manager are the only supported methods of installing the Nvidia driver, the method below (while it works for most people) is not supported}}

Download the drivers from http://www.nvidia.com/object/linux_display_ia32_100.14.19.html and save it to your Desktop.
Exit to a virtual terminal by pressing [CTRL]+[ALT]+[F2]

Stop the X server:

$ sudo /etc/init.d/gdm stop (stopping the X server)

Remove nvidia-glx-new

$ sudo apt-get remove nvidia-glx-new

Install the drivers:

$ sudo sh NVIDIA-Linux-x86-100.14.19-pkg1.run (depending on the version that will be online)

Follow instructions in the installer, when complete restart the X-Server with:

$ sudo /etc/init.d/gdm restart (restarting the X server)

===Multiple Monitors===

'''Nvidia N140m:'''

When using the default drivers (The open source "nv" drivers) you can use Administration->"Screens and Graphics" to setup the second monitor

Using the proprietary drivers you must use the Nvidia tool located at Applications->System Tools-> Nvidia X Server Settings.

It has been reported that the NVIDIA drivers tend to crash with xinerama enabled. 2 displays with xinerama off has been stable.

Twinview works but a movie will span both the laptop screen and second monitor or projector.
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 possible to do set up Twinview with movies that don't span screens in the Applications->System Tools->Nvidia Settings?

'''Intel X3100:'''

Plugging in an external monitor works, but is a clone of the built-in LCD by default. Following the instructions on [http://www.thinkwiki.org/wiki/Intel_Graphics_Media_Accelerator_X3100 this page] to extend your desktop to the second monitor does *not* work; it results in the crash described [http://lists.freedesktop.org/archives/xorg/2007-April/023326.html here]. According to [http://lists.freedesktop.org/archives/xorg/2007-April/023335.html this post] and [https://bugs.freedesktop.org/show_bug.cgi?id=10706 this bug report], the problem is a new Xinerama implementation and an old config file.

To extend your desktop to the second monitor, you'll want to do what [http://wiki.debian.org/XStrikeForce/ReleaseNotes this page] suggests (under "Dual-Head config breakage with xserver-xorg-video-intel").

Below is an example for a 1680x1050 built-in LCD and a 1600x1200 external LCD:
Add a "Virtual 3280 1200" line in the Display SubSection of the Screen Section in your xorg.conf:
{{Fixme|If someone could include an example of the change described above it would be greatly appreciated}}
Exit to a virtual terminal (press: ctrl-alt-F1), login and type the following:

{{cmdroot|sudo /etc/init.d/gdm stop}}

{{cmdroot|xrandr --output LVDS --auto}}

To set the built-in LCD to ouput 1680x1050

{{cmdroot|xrandr --output VGA --right-of LVDS}}

To extend the desktop

=== Fonts on High-Res Screens ===

On high-res screens (e.g. 15" 1680x1050), the default fonts are too big ([https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/99145 Launchpad bug report]). You can fix this by following these steps:

# Open System->Preferences->Appearance
# Select the "Fonts" tab
# Click the "Details" button (lower right)
# Adjust the Resolution down to 96dpi
# Make sure you have Subpixel (LCD) Smoothing enabled
# Save the preferences

If you also want small fonts on the GDM login window, you can do this:

# Open System->Administration->Login Window
# Select the 'Security' tab
# Click the 'Configure X-Server' button
# Append '-dpi 96' (without quotes) to the text in the 'Command' field
# Reboot the computer.

=== Brightness ===
====Intel X3100:====
The brightness controls do not work out of the box, but they should work once you apply all of the system updates.

However, there now appears to be a bug where the brightness controls stop working after you resume from a suspend.

Until the brightness bugs are finally worked out, you can install "xbacklight" (Applications -> Accessories -> Terminal, type "sudo apt-get install xbacklight" without the quotation marks and hit enter), which allows you to set the brightness from the command line and provides a greater range of brightness values.

To set brightness, go back to the terminal and type "xbacklight =VALUE" where VALUE is a number from 0 to 100 for how bright you want your display to be.

=====Creating brightness shortcuts=====
If you don't want to use the terminal you can set up shortcuts to pre-defined brightness levels:

1) Right-click on the desktop and select Create Launcher...

2) Make it look like this: 
[[Image:XBacklight launcher 50.png]] 
The 50 means that the backlight will be at 50% brightness. If you want your shortcut to set the brightness to 100% then simply replace 50 with 100 when you create your launcher (Shortcuts in Windows are analogous to Launchers in Ubuntu). Many people use at least two brightness levels (for example, 100% when on AC power, 50% when on battery power) so it's a good idea to make a launcher for each commonly used brightness level. I also suggest adding them to the upper panel (Linux for menu bar) so that they're easily accessible. If you want, you can use your own custom icons by right-clicking the launcher, selecting Properties, and then clicking on the picture in the Properties window and browsing for your own.

====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

switching back to X (ctrl+alt+7) may freeze your computer with a black screen.

== Audio ==

=== Inextricably Linked to the Modem ===
Make sure that you have the modem enabled in the BIOS. If it is disabled, you may discover (with much consternation) that your audio is also disabled. In this situation, your drivers may still load, but you will get an error message whenever you try to play audio.

After trying all of the ALSA related fixes for this machine, with no love, I remembered what a colleague had said about his T60, and tried this on a hunch. Blammo, it worked!

===Enabling Audio controls===

By default, the sound may be disabled and the volume control buttons on the laptop (up by the ThinkVantage button) and the volume control applet (up by the clock) will not control the speaker volume (they actually control the microphone!). https://bugs.launchpad.net/ubuntu/+bug/136287
this bug report links to a fixed version from an Ubuntu dev a fixed version is available
To fix this:

# Right-click on the volume control applet (by the clock) and select "Open Volume Control"
# In the "Switches" tab, make sure "Headphone" and "Speaker" are both checked.
# Close the Volume control.
# Right-click on the volume control applet again and select "Preferences".
# Make sure the device is set to "HDA Intel (Alsa mixer)" and highlight the "PCM" option.
# Close the preferences.
# Select System->Preferences->Sound.
# In the "Default Mixer Tracks" section, make sure "PCM" is highlighted.
# Close the sound preferences.

You should now hear sound and be able to control the volume using the laptop buttons or volume applet.

The mute button on the laptop does not work.

===Microphone===
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.

===Sound Cracking===
The sound may be cracking if ALSA is used, try to switch to the OSS driver in system => preference => sound => devices => Music and movies, select OSS - Open sound system (instead of ALSA)

The above does not appear to work for everyone.

Another thing to check is to see if this issue is only occurring for Rhythmbox (which is where i noticed this issue). If this is the case, go to Edit > Preferences > Playback > and Check "Use Crossfading Backend"
Restart Rhythmbox and you should have better audio quality.

===Hissing===
Once sound started working, it produced a lot of hissing during playback, and even when idle. Here's how I fixed it:

# Run "alsamixer".
# Arrow over to "Mic", and hit "M" to mute.
# Arrow over to the first "Docking", and hit "M" to mute.
# Arrow to the first "Internal", and hit "M" to mute.

Now, make sure that "Headphon" and/or "Speaker" are _not_ muted, and that "PCM" is at a reasonable level (say ~70) so you don't make your ears bleed, and try playing something back. ''(<Esc> will exit alsamixer)''

== Webcam ==
Webcam works now with kopete after installing all updates.

== Modem ==

The modem works with the Linuxant drivers available at http://www.linuxant.com

==Bluetooth==

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:

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.

== Fingerprint Reader ==

The reader works with ThinkFinger. General instructions available [http://www.thinkwiki.org/wiki/Integrated_Fingerprint_Reader here] and [https://wiki.ubuntu.com/ThinkFinger here].
Instructions in French available at http://doc.ubuntu-fr.org/materiel/thinkfinger

Prebuilt packages are available from jldugger using Launchpad's PPA:

Add the thinkfinger package repository by creating {{path|/etc/apt/sources.list.d/thinkfinger.list}} with these two lines:

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

Then update the package database and install packages:

{{cmduser|sudo apt-get update}}
{{cmduser|sudo apt-get install libpam-thinkfinger libthinkfinger-dev libthinkfinger-doc libthinkfinger0 thinkfinger-tools}}

After the package is installed add the following two lines to {{path|/etc/pam.d/common-auth}}

auth sufficient pam_thinkfinger.so
auth required pam_unix.so try_first_pass

Edit {{path|/etc/modules}} and add the following line:

uinput

Load the module manually for this session:

{{cmduser| sudo modprobe uinput}}

Summary:
* Recording fingerprints works
* Login works
* The password must be entered to unlock a locked screensaver
* sudo works
* gksu and gksudo hang : for example it is necessary to run synaptic twice and enter your password upon failure. To be able to use the Finger print reader in the session subsequently, kill the hanging gksu/gksudo process. A workaround is editing the Gnome System Menu (alacarte) to specify sudo instead of gksu/gksudo for the launching command and choose type "Application in Terminal" : this opens an extra terminal window for each superuser application you want to use though.

== Trackpad scrolling ==

Trackpad scrolling works out of the box in the standard thinkpad way: Slide your finger up and down the very right edge of the trackpad.
Note that /etc/X11/xorg.conf will be changed and the edge scrolling will be disabled after running nvidia-xconfig , copy the trackpad section from the backup of xorg.conf

To enable using the middle mouse button to scroll, add the following lines to the "Configured Mouse" section in
{{path|/etc/X11/xorg.conf}}:

Option "EmulateWheel" "true"
Option "EmulateWheelButton" "2"

== Hibernate/Suspend ==

=== Blank screen fix for intel graphics cards===

This fix is for Intel Graphics Cards only.

You may get a blank screen when resuming from suspend or hibernate ([https://bugs.launchpad.net/ubuntu/+bug/134391 Launchpad bug report]). If so, try editing {{path|/boot/grub/menu.lst}}, adding "acpi_sleep=s3_bios" (no quotes) to the "defoptions" list so that it looks something like this:

## additional options to use with the default boot option, but not with the
## alternatives
## e.g. defoptions=vga=791 resume=/dev/hda5
# defoptions=quiet splash '''acpi_sleep=s3_bios'''

Once you have edited the line and added the acpi_sleep parameter, you need to run

$ sudo update-grub

Note that if you get the blank screen upon resume, a quick-fix is to switch to a console (Ctrl-Alt-F1) and then back to X (Ctrl-Alt-F7). This will usually bring the display back to life. However, the long-term fix is to add the acpi_sleep parameter as shown above.

=== How to Suspend with nVidia 140m/570m ===

The suspend to RAM will work with the nVidia card and the proprietary drivers, but it requires some file editing. It did not work for me out of the box. Using the package manager, download and install the latest nVidia drivers (100.14.19+2.6.2.4-12.4 at time of writing). I also had to use the 2.6.22-12-generic kernel image (the 2.6.22-13 image did not work with this driver --- I'm assuming it has to match wit the nVidia version, but I am not an expert).

Once you have it installed and working, you have to make a change to {{path|/etc/default/acpi-support}}. Open the file in your favorite editor and change the following lines:

$ sudo nano /etc/default/acpi-support

{{path|/etc/default/acpi-support}}
# Should we save and restore state using the VESA BIOS Extensions?
SAVE_VBE_STATE=false
...
# Should we attempt to warm-boot the video hardware on resume?
POST_VIDEO=false
...
# Set the following to "platform" if you want to use ACPI to shut down
# your machine on hibernation
HIBERNATE_MODE=platform

This allowed me to suspend and resume, but after two suspends the wireless wouldn't work anymore. Theoretically, ACPI unloads the network drivers before suspending, but it doesn't seem to work correctly so I added these to the blacklist modules manually (in the same file as above:

{{path|/etc/default/acpi-support}}
# Add modules to this list to have them removed before suspend and reloaded
# on resume. An example would be MODULES="em8300 yenta_socket"
#
# Note that network cards and USB controllers will automatically be unloaded
# unless they're listed in MODULES_WHITELIST
MODULES="iwl4965 iwlwifi_mac80211 cfg80211"

Your wifi modules may be different. (I have the intel AGN wireless card -- I don't know if these modules are different for other cards.)

This allows me to suspend to ram; I haven't had any problems with it so far. I haven't gotten hibernate (suspend to disk) working, so there may be additional things you need to do for that. (I think part of my problem is that I don't have enough swap, but I don't care enough to actually fix it.)

/*The fix does not work for me. I have a T61 7664-17U(NVS 140m, 4965agn). The computers suspend, but when it wakes up it hangs up and I have to pull out the battery to restart it.*/

General hint: Do not install the package "hibernate" or the gnome-power-manager will fail to suspend/hibernate your computer. If you have installed the package don't forget to purge the configuration. (sudo apt-get remove hibernate --purge)

== Items that work out of the box ==

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

'''Nvidia:''' 2D works, 3D requires the installation of the proprietary drivers

'''Wireless:''' Atheros and Intel cards both tested.

'''Bluetooth:''' Tested with both a bluetooth headset and an HTC 8525

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

'''Firewire''' Tested with hard drive

'''Wireless switch'''

'''4-in-1 card reader'''

'''Headphones''' You may need to enable Headphone out: Right-click on the volume control and select open volume control. Click the switches tab and then check the headphones box.

'''Keyboard Shortcuts:'''
http://www.thinkwiki.org/index.php?title=Installing_Ubuntu_7.10_%28Gutsy_Gibbon%29_Tribe_5_on_a_ThinkPad_T61&action=edit&section=8
* 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-F12 hibernates (to disk)
* PrtSc opens the screenshot dialog

'''Docking Stations:'''

All docking station models should work and the following features have been tested:

* DVI or Analog video: You can switch to it using "Administration->Screens and Graphics", if you are using the proprietary Nvidia drivers you must use the Nvidia Control Panel.

* Network Pass-through

* Modem Pass-through

* USB ports: Connected upon docking

* PS/2 Ports

== Items that don't work ==

* Wireless USB/UWB - https://bugs.launchpad.net/ubuntu/+bug/136287
* USB ports can end up temporarily disabled - https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/126369
* Wireless activity LED

== Power consumption ==

Gutsy is the first version of Ubuntu to feature a tickless kernel (i386 only, not in AMD64 yet). Power consumption
can be monitored using the powertop tool under Ubuntu and using Lenovo battery monitor
under Windows.

$ sudo apt-get install powertop
$ sudo powertop

I couldn't find any difference in power consumption between the i386 tickless kernel (even with 70ms average sleep in C4)
and AMD64 kernel (2ms average sleep in C4). It would be expected that considerably less power would be consumed for the
i386 tickless kernel.

There is also a graph available by Right-clicking on the battery icon and selecting Power History.

These are the figures measured on a T61 15.4" 1680x1050 screen 7300 processor (2GHz) 2GB RAM, Intel X3100 graphics
with 4965 wifi, Bluetooth and UWB.

{| border=1 cellpadding=5
|-
| 12.3W
| Windows XP Pro, all radios on, about 50% brightness
|-
| 16.7W
| Gutsy, all radios on, 50% brightness
|-
| 19.6W
| Gutsy, all radios on, 100% brightness
|-
| 14.2W
| Gutsy, all radios on, 10% brightness
|-
| -1.0W
| Turning the physical radio switch to off on the front reduces power consumption by 1 watt.
|}

Adding the Nvidia card increases the laptops power requirements.

These are the figures measured on a T61 14" 1440x900 screen 2.2ghz Core2Duo 2GB RAM, Nvidia 140m video, IWL4965 wifi and Bluetooth (Disabled):

{| border=1 cellpadding=5
|-
| 18.3W
| Gutsy, all radios on, 50% brightness
|-
| 19.4W
| Gutsy, all radios on, 100% brightness
|-
| 16.0W
| Gutsy, all radios on, 10% brightness
|-
|}

[[Category: T61]] [[Category: Ubuntu 7.10]]