ThinkWiki - User contributions [en]

Installing Ubuntu 7.10 (Gutsy Gibbon) on a ThinkPad T61

2008-03-16T13:17:43Z

Fabian gebert: Updated the suspend section for Nvidia to make it easier for new users

==Introduction==

This document outlines configuring Ubuntu 7.10 (Gutsy Gibbon) on your Thinkpad T61. Most items will work out of the box and a base install should provide you with a 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 ==

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

== 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. All systems updated after 11/24/2007 should be fixed.

'''Nvidia''' 2D video works out of the box, to enable accelerated 3D support click System->Administration->Restricted Drivers Manager {{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 Synaptics and the Restricted Drivers Manager}}

===Multiple Monitors===

If you previously used Xinerama this is no longer a supported option, you should use one of the tools described below to configure dual displays.

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

Note:
Twinview 'works' but doing 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.

If you experience problems getting a working Twinview setup using nvidia-settings, please see [http://www.nvnews.net/vbulletin/showthread.php?t=101780 this thread]

==== Intel GM965/GL960 ====
If you experience a blank screen and perpetual gui reset when using heavy GLX (3D) applications such as scorched3d, try upgrading to the hardy 2.6.24-3 kernel along with the matching modules:

add these 2 lines to /etc/apt/sources.list:
deb http://us.archive.ubuntu.com/ubuntu/ hardy main restricted
deb-src http://us.archive.ubuntu.com/ubuntu/ hardy restricted main multiverse universe
run:
sudo apt-get update
sudo apt-get install linux-restricted-modules-2.6.24-3-generic linux-image-2.6.24-3-generic linux-ubuntu-modules-2.6.24-3-generic

Comment out the 2 new lines from sources.list (put a # in front) and run apt-get update again.

reboot.

IMPORTANT: You must comment out the lines from sources.list and run apt-get update again, or you will auto-upgrade to hardy which you do not want to do yet!

NOTE: the 2.6.24 kernel uses the new fully open iwl3945 driver for wifi, instead of the old restricted ipw3945. you may need to tweak your wifi settings after rebooting.

====Intel X3100====

Plugging in an external monitor works, but is a clone of the built-in LCD by default. Using the Screens and Graphics tool located under Administration you can setup the second monitor as an extension of the existing screen or a clone for presentations, but it does not let you enable a second display on a second monitor.

'''Setting up dual monitors via the command line'''

If you like doing it via the command line and are using the Intel drivers or the open-source "nv" driver you can use this example (''Note all this should be possible using the Screens and Graphics tool so only make this change if you prefer the command line method''):

This 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:

Go to Applications -> Accessories -> Terminal 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

To enable Compiz Fusion. refer to http://temporaryland.wordpress.com/2007/12/06/finding-the-right-distro-for-my-thinkpad-followup/ and follow the instructions as per for Linux Mint 4.0.

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

On high-res screens (e.g. 15" 1680x1050), some users consider the default fonts too be too large ([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 should work out of the box on a fresh install.

====Nvidia Quadro N140 and 570M:====
With Nvidia Driver 169.07 (2007/12/20) the brightness controls work properly on a Thinkpad T61 with Nvidia Quadro NVS 140M. Please see the section above on installing drivers with the Envy tool above.

Previous Driver:
The brightness controls do not work out of the box, 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 (You should save anything open just to be safe). There is a new from nvidia that fixes the brightness-controls. To install this driver use the Envy tool described above.

If brightness buttons do not work (after installing the latest nvidia drivers) you can edit /etc/acpi/thinkpad-brightness-up.sh and /etc/acpi/thinkpad-brightness-down.sh:

Add this line before "exit" in {{path|/etc/acpi/thinkpad-brightness-up.sh}}
echo 4 > /proc/acpi/ibm/cmos

Also insert this line before "exit" in {{path|/etc/acpi/thinkpad-brightness-down.sh}}
echo 5 > /proc/acpi/ibm/cmos

== Audio ==

=== Inextricably Linked to the Modem ===
Make sure that you have the modem enabled in the BIOS. If it is disabled, you may discover 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.

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

A recent BIOS update [http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=MIGR-67989] fixes the mute button, you can then configure it to mute/unmute audio in Keyboard Shortcuts.

===Microphone===
The internal microphone is considered a generic capture source and is muted by default. To unmute the microphone:

*Right Click on the volume icon next to the clock and click on "Open Volume Control"

*Click Edit -> Preferences. A list of devices will be displayed, you should check the following (Do not uncheck any existing items):
Internal Mic
Input Source
Capture

*Click Close and there should be two additional tabs "Recording" and "Options". -

*Click Recording and click on the microphone under the Capture slider so that it no longer has a red line through it.

*Click Options and under capture source select internal mic (This step may not be necessary).

To test your mic using Sound Recorder select Capture as the sound source.

This solution has been tested with Sound Recorder, Akiga, Skype, and OpenWengo.

===Sound Cracking===

There have been intermittent reports of users experiencing cracking when listening to audio. Here are a few possible solutions:

* Try to switch to the OSS driver in system => preference => sound => devices => Music and movies, select OSS - Open sound system (instead of ALSA)

* If this issue is only occurring for Rhythmbox go to Edit > Preferences > Playback > and Check "Use Crossfading Backend". Restart Rhythmbox and you should have better audio quality.

* Check that the microphone is muted and modify your mixer settings by moving items like PCM down halfway and see if the cracking goes away.

===Hissing===
Some users experience hissing during playback, and even when idle. To solve this mute the microphone when it is not in use:

# Run "alsamixer" in the terminal.
# 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 "Headphone" 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)''

== Modem ==

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

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

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

Note that ThinkFinger in it's current version does not work with KDE and Kubuntu in any way (it crashes KDM and is not integrated at all).

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 edit {{path|/etc/pam.d/common-auth}} and replace the line

auth required pam_unix.so nullok_secure

with

auth sufficient pam_thinkfinger.so
auth required pam_unix.so try_first_pass nullok_secure

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.

When resuming from suspend or hibernate, the screen will be black until you switch to a console (ex: Ctrl-Alt-F1) and then back to X (Ctrl-Alt-F7). ([https://bugs.launchpad.net/ubuntu/+bug/134391 Launchpad bug report]). To fix this, open (as sudo) /etc/default/acpi-support and find the line:

<pre># DOUBLE_CONSOLE_SWITCH=true</pre>

uncomment it so that it says:

<pre>DOUBLE_CONSOLE_SWITCH=true</pre>

and then save and close the file. You may then reboot or just restart ACPI:

<pre>sudo /etc/init.d/acpi-support restart
sudo /etc/init.d/acpid restart</pre>

afterward, the screen should come back properly on resume.

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

Add the s3_mode option to kernel boot parameters (according to [https://bugs.launchpad.net/ubuntu/+source/acpi/+bug/139089 Launchpad BUG 139089])

{{path|/boot/grub/menu.lst}}
## Add acpi_sleep=s3_mode to kernel boot parameters
# defoptions=quiet splash acpi_sleep=s3_mode

Rebuild menu.lst using

<pre>$ sudo update-grub</pre>

Remove hibernate and uswsusp packages in case they are installed

<pre>$ sudo apt-get remove hibernate uswsusp --purge</pre>

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

If the system has been left in suspend off for a while, wireless might not reconnect at all (Thinkpad T61 8892-02U). Restarting netapplet
solves the problem.

{{path|/etc/default/acpi-support}}
# Add services to this list to stop them before suspend and restart them in
# the resume process.
STOP_SERVICES="netapplet"

/*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.*/ -- also not with s3_mode?

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

'''Webcam'''

'''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:'''
* 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 ==

=== Interrupt problem (PROBABLY SOLVED) ===
This bug is supposed to be solved by updating the system BIOS to the [http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=MIGR-67989 2.09]-Version (with 1.08 AMT). Still testing...
* https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/126369
* USB ports can end up temporarily disabled
* Wifi can break
* integrated cardreader can be disabled
* bluetooth can be disabled
* Setting IRQ's to "Auto" from factory default of "11" in the BIOS seems to help some people.
* The two USB ports on the left side of the computer may fail to connect storage devices during a session but will load them at boot up. (SOLVED! with BIOS update 2.09)
* booting with the "irqpoll" option seems to work for some people against the problem that usb-ports stop working.
* GLX (3d graphics) on intel 965 video card is broken: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/120834 (SOLVED! - see section above)

=== Wireless activity LED ===

The LED is not implemented in either the IWL4965 or Atheros drivers.

patch posted in this [http://bughost.org/bugzilla/show_bug.cgi?id=1209 thread] works for me on R61 with IWL4965 card.

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

== See also ==
* [[Installing Ubuntu 8.04 (Hardy Heron) on a ThinkPad T61]]

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

Installing Ubuntu 7.10 (Gutsy Gibbon) on a ThinkPad T61

2007-10-13T11:17:30Z

Fabian gebert: /* How to Suspend with nVidia 140m/570m */

==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 "uswsusp" 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, uswsusp resp.)

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

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

2007-10-12T19:40:27Z

Fabian gebert: Power Consumption

==Renamed the page==

I renamed the page since we are now at "Beta" and not Tribe.

==New Nvidia Driver released==

http://www.nvidia.com/object/linux_display_ia32_100.14.19.html

Time to test, supposedly it stabilizes compiz. When I get home tonight I will write up install instructions and what it fixes if someone doesn't beat me to it.

: The new NVIDIA driver doesn't fix the compiz+3d accel bug, causing X to crash, at least not on my system. I have the NVIDIA Quadro FX570M. I've removed compiz from my system since I value a buggy NVIDIA driver more than cheesy desktop effects. [[User:Rybu|Rybu]]

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

==Update 2007-10-11 works fine==
Announcement. [[User:SteveSims|SteveSims]] 05:15, 2 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?

Installing Ubuntu 7.10 (Gutsy Gibbon) on a ThinkPad T61

2007-10-12T19:32:07Z

Fabian gebert: /* Remove the hibernate-package */

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

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

== 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.04 (Feisty Fawn) on a ThinkPad T61

2007-08-02T20:15:51Z

Fabian gebert: /* WiFi */

We'll I got it basically working, so far (will update as i get more thing working).

===SATA Issues===
At first, the Ubuntu Live CD would not start at all, this seems to be a problem with the SATA AHCI driver. I had to go into the BIOS and change the SATA driver from ACHI to compatibility (What is the difference? Am I loosing performance?).

----

After you've installed and booted, try the advice from [[Problems_with_SATA_and_Linux]]. Do this:
'''# echo options libata atapi_enabled=1>/etc/modprobe.d/atapienable && update-initramfs -u'''
Then try turning AHCI back on in the BIOS. On a custom-built 2.6.21.5 kernel, my DVD drive appears as /dev/hda and DMA works.
--[[User:Kc8tbe|Kc8tbe]] 12:45, 1 July 2007 (UTC)

If your DVD drive does not appear, modprobe pata-jmicron and ide-generic.
--[[User:Antikristian|Antikristian]] 01:23, 30 July 2007 (UTC)

===NVIDIA Quadro NVS 140M (Solved)===
After initial issues like those explained above in the SATA Issues, I received the xorg error 'fatal error: no screens found'. I was able to boot into Safe Graphics Mode and run the installer, though I had to move both window manager bars to see enough of the install window to use it.

Alternatively, you can download the drivers via wget in a console. Take care to follow the instructions in
[http://www.nvnews.net/vbulletin/showthread.php?t=72490 the NVidia Forum] and uninstall all the packages wit apt-get remove, as descirbed.
Then run the nvidia installer.

Remember that, after you upgrade the kernel, you also have to re-install the drivers.

After installing the NVIDIA drivers, your laptop may not wake after suspend or hibernation. I followed these instructions to fix it [https://help.ubuntu.com/community/NvidiaLaptopBinaryDriverSuspend Ubuntu Community Help].

====Alternative NVIDIA driver installation====
Instead of installing the NVIDIA drivers manually as described above, you can try using [http://www.albertomilone.com/nvidia_scripts1.html Envy]. It automatically installs the latest NVIDIA drivers, and cleans up any previous installations.

=== Intel Graphics Media Accelerator X3100 (Chipset GM965) (Solved)===
After that the CD seemed to boot but the screen was just garbage [http://shadowarts.nonlogic.org/projects/thinkpad/screen_garbage.jpg Picture]. In order to get around that issue I had to go back and download the Alternate CD, which allows you to install in text only mode. From here, the text-only install went okay. Changing the VGA settings on the regular CD worked for me.

When I booted up after the installation, I was still getting the same garbage on the screen. To resolve this I edited my [http://shadowarts.nonlogic.org/projects/thinkpad/xorg.conf xorg.conf] file as shown. I also had to install the latest kernel for Feisty, as the one off of the install disk did have have /dev/agpgart. And I could then use X11. There were still some issues however. The screen seemed somewhat fuzzy. This was a little more challenging of a fix... I found [http://www.spinics.net/lists/xorg/msg25099.html this] mailing list posting, according to it, there was a small glitch in the driver. To fix it:
<pre>
apt-get source xserver-xorg-video-intel
cd xserver-xorg-video-intel-1.9.94/
vim src/i830_lvds.c
Goto line 230 and delete (PFIT_ENABLE | VERT_AUTSCALE ....);, replacing it with 0; then quit vim
dpkg-buildpackage -rfakeroot -uc -b
cd ..
dpkg -i xserver-xorg-video-intel_1.9.94-lubuntu3_amd64.deb (wont be amd64 with a 32-bit install)
</pre>
Now reboot your computer, and it should work. **NOTE: For some reason just restarting X didn't fix it, seems like you must reboot.** At this point you should have a nice, crisp display.

I am still working on aiglx and compiz (switching desktops on a cube doesnt seem to work, though I have some ideas...). There are some issues with OpenGL apps freezing Xorg as well, but the standard 2D desktop works flawlessly.
----
It doesn't seem to be necessary to modify the soruce of xserver-xorg-video-intel anymore, but 3D-acceleration doesn't seem to be stable yet and kdm occasionally needs to be restarted after a login attempt.--[[User:Kc8tbe|Kc8tbe]] 12:49, 1 July 2007 (UTC)

----
I was able to use the normal feisty install disk by changing the SATA setting in BIOS, then change the resolution to 800x600 prior to install, then sudo apt-get update and upgrade, and then sudo apt-get install xserver-xorg-video-intel, then change xorg.conf to match link above and 2D graphics work fine. Jul 18, 2008 - John E
----

It seems that everything works fine when using "apt pinning" and updating the xserver-xorg-video-intel, mesa and other packages to the versions provided by Gutsy. I did the following and the resolution and Compiz Fusion are working fine at the moment. The original source of the steps described below can be found here: [http://techreport.com/forums/viewtopic.php?p=714998#714998]

'''Instructions:'''
* Make a new file /etc/apt/preferences
* In the preferences file, put:
<pre>
Package: *
Pin: release a=feisty
Pin-Priority: 700

Package: *
Pin: release a=gutsy
Pin-Priority: 200
</pre>
* Now, edit your sources.list and copy the main and restricted (and others if you want) repo lines replacing feisty with gutsy:
<pre>
# original
deb http://archive.ubuntu.com/ubuntu feisty main restricted universe multiverse
deb-src http://security.ubuntu.com/ubuntu feisty main restricted universe multiverse

# your addition
deb http://archive.ubuntu.com/ubuntu gutsy main restricted universe multiverse
deb-src http://security.ubuntu.com/ubuntu gutsy main restricted universe multiverse
</pre>
* Now run:
<pre>
sudo apt-get update
sudo apt-get -t gutsy install xserver-xorg-video-intel
sudo apt-get -t gutsy install linux
sudo apt-get -t gutsy install libgl1-mesa-dri
</pre>
* Now reboot.

Probably now you have the weird effect that your GUI is scaled wrong and doesn't fill the full width of the monitor. To fix that, open your xorg.conf and make the following changes:
* Add the following section to your xorg.conf
<pre>
Section "Monitor"
Identifier "TVOutput"
Option "Disable" "true"
EndSection
</pre>
* Then in the "Device" section add the following line:
<pre>
Option "monitor-TV" "TVOutput"
</pre>

That should fix the scaling problem and now everything should work fine.
--[[User:Shuk|Shuk]] 02:26, 10 July 2007 (UTC)

===ThinkFinger===
Ubuntu does not come with a package for thinkfinger. Downloading the most recent source and building it was simple enough: Download most recent version (0.3 at time of writing)
<pre>
sudo apt-get install libpam0g-dev libusb-dev
tar xvzf thinkfinger-0.3.tar.gz
cd thinkfinger-0.3/
./configure --with-securedir=/lib/security --with-birdir=/etc/pam_thinkfinger
make -j5 (hey its dual core!)
sudo make install
</pre>

Configuring it is easy as well, open /etc/pam.d/common-auth:
<pre>
auth sufficient pam_thinkfinger.so
auth required pam_unix.so try_first_pass nullok_secure
</pre>

Create the data directory and set your fingerprint:
<pre>
subo mkdir /etc/pam_thinkfinger
sudo tf-tool --add-user <username>
</pre>
It will all be setup. (I found this somewhere on the web, I wish I could give a source but I'm afraid I cant find it, thank you Anonymous!).

===HDAPS===
This seems to be working fine now, I just follow the step on [[How_to_protect_the_harddisk_through_APS]]. Using hdaps-gl does the inverse of the accelerometer, though it's not really a big deal, the harddrive protection should still work.

===WiFi===
If you have Intel 4965AGN WiFi card, you have to use ndiswrapper OR use backported kernel from Ubuntu Gutsy (Anybody have howto?) and use following:
http://kuscsik.blogspot.com/2007/06/how-to-install-intel-4965-wireless.html

'''Note:'''
Do not use the latest versions of iwlwifi and mac80211. For me with Gutsy mac80211-8.0.2 and iwlwifi-0.0.42 work with the latest firmware. No further modification needed.

If you have the Atheros card, Ubuntu should automatically install madwifi, which works out of the box
----
Works for me with iwlwifi-4965-ucode-4.44.15, iwlwifi-0.0.34, and mac80211-8.0.1. The catch is, you need to patch your kernel with mac80211, which will fail at compile time with the stock Ubuntu sources. Worked for me with vanilla 2.6.21.5 sources patched for tp_smapi and hdaps protect. Make sure to disable CONFIG_NET_WIRELESS_RTNETLINK in your kernel config.

You can download what you need for for iwlwifi and mac80211 from
http://intellinuxwireless.org .--[[User:Kc8tbe|Kc8tbe]] 13:00, 1 July 2007 (UTC)

Works for me with vanilla kernel v2.6.22.1, ucode 4.44.17, iwlwifi 0.1.2 and mac80211 9.0.2. --[[User:Mbsullivan|Mbsullivan]] 13:40, 24 July 2007 (UTC)

You can also use Kernel 2.6.22.9 and Ubuntu Modules 2.6.22.9 from Gutsy and you will not need to compile anything! Works very well.

===Can you hear me now?.... What? (Solved!)===
After upgrading to 1.0.14 I still had no sound, and this took about a week to solved (though it was so sadly obvious though). Just upgrading to alsa 1.0.14 will not be enough, there were a few patches released right after the release that fix the Thinkpad's. The reason I missed this was because it was the same day so the release of 1.0.14!

Anyway download the source code to the alsa-driver and apply these patches: (links to the revisions)

* [http://hg.alsa-project.org/alsa-kernel/rev/958b39f3e8dd Fix Oops with AD1984 thinkpad model]
* [http://hg.alsa-project.org/alsa-kernel/rev/47ca87407c84 Fix AD1984 basic model]
* [http://hg.alsa-project.org/alsa-kernel/rev/ca37aeeeb0ea Fix Thinkpad X61/T61 outputs]

'''Please use CVS version of ALSA instead. All of these patches are commited'''.

After doing a make and make install reboot your computer (or rrmmod snd-hda-intel && modprobe snd-hda-intel). And run alsamixer (for me it only works as root atm). You will have to play with the settings a bit. Make sure the speaker option is not muted and leave the Internal Mic Boost at 0, other wise you will have a really loud microphone feedback sort of sound constantly.

I had to chmod -R 777 /dev/snd/ to get everything work for now. (THIS IS NOT THE CORRECT WAY TO DO IT, IT WILL NOT STAY BETWEEN REBOOTS!).

Audio playback should then work, audio capture (microphone) doesn't seem to work, but I am probably not going to try and fix it, I don't use the capture so I am not concerned with that at the moment.
'''Update:''' With ALSA CVS, microphone seems to work

If you can't hear the mic boost mic settings. Here are my settings at KMix
Output
Mic - low
Mic Boost - full
Input
Mic boost [enable] - medium
capture [enable] - medium

works great with Skype. Also you can use the 'mic level meter' on KRecord to check the mic

In Gnome, default channel mapped to thinkpad volume buttons is MIC, which is bad. Go to ''System->Preferences->Sound->Default mixer tracks'' to change it

'''Please note''' that internal speakers doesn't work with ALSA CVS. Use the headphone jack. Solution?

----
When starting alsamixer over the terminal I couldn't activate the speakers and only had sound over the headphone. However, I figured out how to easily activate the speakers:
* Right-click on your microphone icon in the top panel.
* (If "Mute" is activated, deactivate it. I had that at the beginning and was confused since in alsa you don't really realize it.)
* Click on "Open Volume Control"
* Change to the tab "Switches" and activate the option for speaker.
That should be enough to make it work.
--[[User:Shuk|Shuk]] 02:51, 11 July 2007 (UTC)

I tried those patches, it didnt work for me. But this python script did: http://www.klabs.be/~fpiat/linux/debian/Etch_on_Thinkpad_T61.html#Sound .. apparently if you make the PC speaker play constantly, you cant hear it but you can then hear sound. Hopefully gutsy will fix this :/ --[[User:Rubin|Rubin]] 07:18, 14 July 2007 (UTC)

==Suspend==
Suspending doesn't work by default. It succesfully suspends, but after resuming, Kernel panic occurs. I didn't test hibernate.
I managed to get suspend to ram to work by using this script:

#!/bin/sh

# if launched through a lid event and lid is open, do nothing
echo "$1" | grep "button/lid" && grep -q open /proc/acpi/button/lid/LID/state && exit 0

# remove USB 1.1 driver
rmmod uhci_hcd
rmmod ehci_hcd

# sync filesystem and clock
sync
/sbin/hwclock --systohc

# switch to console
FGCONSOLE=`fgconsole`
chvt 6

# go to sleep
sleep 5 && echo -n "mem" > /sys/power/state

# readjust the clock (it might be off a bit after suspend)
/sbin/hwclock --adjust
/sbin/hwclock --hctosys

# reload USB 1.1 driver
modprobe uhci_hcd
modprobe ehci_hcd

# turn on the backlight and switch back to X
chvt $FGCONSOLE

It's very similar to script posted on thinkwiki, but I had to add ehci_hcd to removed modules and remove some radeon stuff (when using Nvidia)

'''Problems''' the problem with this suspend script is, that after resuming, the laptop is incredibly slow. Applications start about 20 seconds, Firefox is lagging. But processor doesn't run at highest frequency, nothing seems unusual. '''Suggestions?'''

When using this script, my USB ports are 'dead' after resume (i.e. nothing connected to it gets any power). I have commented out 'rmmod ehci_hcd' and 'modprobe ehci_hcd' lines, to make the USB ports active after a suspend/resume cycle. (this is using nvidia card)

----
Suspend and hibernate work out-of-the-box for me with the 2.6.21.5 kernel, except that you need to put acpi_sleep=s3_bios in the kernel command line (i.e. at the end of each kernel line in /boot/grub/menu.lst).
--[[User:Kc8tbe|Kc8tbe]] 13:03, 1 July 2007 (UTC)

Hmm, with 2.6.21.5 + acpi_sleep=s3_bios, laptop suspends, but resume fails - machine locks up. This is with nvidia 140. Same result when doing it at console. When I resume, I hear a beep and the machine hangs. Have to hard-reset. Suggestions?

Some things seem to break after suspend for me, like network connections time out randomly, cdrom stops working etc. Running 'sudo /etc/init.d/dbus restart' seems to solve it for the most part.

==Brightness==
Changing brightness doesn't work at all. There are many issues. I tried Gutsy and still the same (even worse)

Not a real solution, but if using the vesa driver, brightness control works. ''--Daniel06'' 11:58, 4 July 2007

doesnt work for me with vesa or intel --[[User:Rubin|Rubin]] 06:19, 14 July 2007 (UTC)

=== one idea ===
echo "up" >/proc/acpi/ibm/brightness
...works. as does 'down' and 'level x' where x is 1-7. But how to tie that into the buttons? Seems they are currently using something else in /proc that doesnt exist for us. --[[User:Rubin|Rubin]] 06:19, 14 July 2007 (UTC)

=== Another solution for Brightness, using xbacklight and laptop-mode ===

While the hardware buttons still don't work, I have a solution that will automatically raise and lower the backlight when plugged in or on battery.

First, make sure Gnome isn't trying to set the brightness, by going to System > Preferences > Power Management. In the On Battery Power tab, set "Dim display brightness by" to 0%.

Next, install xbacklight.

sudo apt-get install xbacklight

You can manually set the backlight by using "xbacklight -set <number from 1-100>". Note that by using xbacklight, you can make the backlight go brighter or dimmer than normally allowed by Windows or Ubuntu.

To automate brightness changes, first enable laptop-mode

sudo nano /etc/default/acpi-support

Scroll to the bottom and change ENABLE_LAPTOP_MODE to true

ENABLE_LAPTOP_MODE=true

Set laptop mode to start automatically

sudo update-rc.d laptop-mode multiuser

Edit laptop-mode.conf to automate brightness changes. Scroll down to LCD brightness settings. Modify the section to read as follows:

CONTROL_BRIGHTNESS=1

BATT_BRIGHTNESS_COMMAND="xbacklight -set 20"
LM_AC_BRIGHTNESS_COMMAND="xbacklight -set 100"
NOLM_AC_BRIGHTNESS_COMMAND="xbacklight -set 100"
BRIGHTNESS_OUTPUT="/dev/null"

Note: You can use any value from 1 to 100 after -set, I used 20 and 100 as examples. After this, start the laptop-mode daemon, and test if it works. You may have to restart acpid as well.

sudo /etc/init.d/laptop-mode start
sudo /etc/init.d/acpid restart

==Webcam==
The webcam in T61 is some sort of UVC camera: Found UVC 1.00 device Integrated Camera (17ef:1004). The module loads out of the box. I tested the camera using:
Luvcview: http://mxhaard.free.fr/spca50x/Investigation/uvc/luvcview-20070512.tar.gz
Just compile and run using ./luvcview -f yuv (JPG format doesn't work)

I also tried gqcam and webcam, but both doesn't work (first SEGFAULTs, second prints Invalid argument)

luvcview has a button to take pictures. Place your mouse over the buttons at the bottom of the window, and their function is revealed in the title bar. Unfortunately, the button for avi capture does not seem to work (although it does tell you what the video framerate is, which is helpful).

To capture a video stream, run ./luvcview -f yuv -S
To play back the video stream, run mplayer -demuxer rawvideo -rawvideo fps=7:w=320:h=240:yuy2 stream.raw

==64bit systems issues==
If you are running 64bit Ubuntu, you will face some problems wit 32bit only proprietary applications. Most of them can be solved.

===Firefox & Flash===
You can use 32bit version of Firefox (see google), or use http://gwenole.beauchesne.info/projects/nspluginwrapper/ nspluginwrapper] which i prefer:
sudo apt-get install ia32-libs ia32-libs-gtk linux32 lib32asound2 alien
Now download both nspluginwrapper rpms (Plugin + Viewer) and convert them:
sudo alien nspluginwrapper*.rpm
sudo dpkg -i nspluginwrapper*.deb

Download Adobe Flash Player: http://fpdownload.macromedia.com/get/flashplayer/current/install_flash_player_9_linux.tar.gz
tar -xvzf install_flash_player_9_linux.tar.gz
cd install_flash_player_9_linux
sudo install libflashplayer.so flashplayer.xpt /usr/lib/firefox/plugins
nspluginwrapper -i /usr/lib/firefox/plugins/libflashplayer.so
cd ~/.mozilla/plugins/
sudo install npwrapper.libflashplayer.so /usr/lib/mozilla-firefox/plugins/
This howto is taken from [http://webzine.smehlik.net/64bit-ubuntu-adobe-flash-plugin-pomoci-nspluginwrapper/ Smehlik Webzine (in Czech)]

===Skype===
Download Skype for Ubuntu Feisty
Use this commandlibdbus, libqt4-core, libqt4-gui, libsigc++ to determine missing libraries:
ldd /usr/bin/skype | grep not
It should be these:
libdbus, libqt4-core, libqt4-gui, libsigc++ (2.0 version)
Download them from http://packages.ubuntu.com (32bit versions!)
mkdir testlibs
dpkg-deb --extract <deb file> testlibs
Now copy everything from testlibs to /usr/lib32
cp -r testlibs/usr/lib/* /usr/lib32
Freedom lovers are advised to avoid proprietary systems like Skype, however. Centralized directories and signalling architectures can't be good for your health.

==Overall==
I initially had some big problems getting this working, but now its working quite well. The wifi card worked at startup (uses madwifi) and I am happy because I don't seem to need any proprietary software to run this system.

==Discussion==
In case you missed it the discussion page (for questions/responses) is right here:
http://www.thinkwiki.org/wiki/Talk:Installing_Ubuntu_7.04_%28Feisty_Fawn%29_on_a_ThinkPad_T61

==References==
* This guide is listed at the [http://tuxmobil.org/ibm.html TuxMobil Linux laptop and notebook installation guides survey (IBM/Lenovo)].
* Many other suggestions and references can be found in the following ubuntu forum: http://ubuntuforums.org/showthread.php?t=471563

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