ThinkWiki - User contributions [en]

Talk:Installing Ubuntu 7.10 (Gutsy Gibbon) on a Thinkpad T60

2008-02-07T01:49:15Z

SteveSims: /* 2007-02-06: Update: Speakers no longer detected, mute and ThinkVantage buttons no longer work */ deleted section... error in /boot/grub/menu.lst

Installing Ubuntu 7.10 (Gutsy Gibbon) on a Thinkpad T60

2008-02-07T01:48:53Z

SteveSims: /* 2007-02-06: Update: Speakers no longer detected, mute and ThinkVantage buttons no longer work */ deleted section

== Features ==
=== Graphical Configuration Tool ===
Some Thinkpad {{T60}}s laptops ship with ATI video cards. Previously [[:Category:Ubuntu 7.04|Ubtuntu 7.04]] Open Source video drivers could be graphically configured with a minimal utility that allowed to choose a single resolution. However, users could be compelled to use the non-free ATI video driver ([[Fglrx]]) because ATI shipped a more featureful utility, Catalyst Control Center. Gusty Gibbon now ships a more fully-featured utility, making the Open Source video drivers a more attractive choice.

=== Desktop 3D effects ===
[[Xgl|Compiz Fusion]] is enabled by default and will bring 3D desktop visual effects that improve the usability and visual appeal of the system. Ubuntu 7.10 automatically detects whether the hardware is capable of running compiz; if not, it falls back to normal desktop.

== Installation ==
Installation of Gutsy Gibbon on the ThinkPad T60 went without a hitch.

=== Dual booting ===
I was able to resize an existing ext3 partition and perform a new install of Ubuntu 7.10 without removing Feisty Fawn. If you are resizing or installing Gutsy Gibbon on a clean partition while maintaining other operating system partitions, I would suggest reinstalling the Grub boot loader so a fresh partition is created with Gutsy Gibbon and other existing OSes like Feisty Fawn or Fedora.

=== Known Issues ===
==== ATI Fglrx breaks over suspend resume ====
If your laptop uses the ATI Fglrx driver and you have a perfectly fine Ubuntu Feisty 7.04 installation, Fglrx breaks on a suspend/resume after an upgrade to 7.10. The Open Source driver is available as an alternative; else it is recommended to not upgrade until [https://launchpad.net/bugs/121653 Ubuntu bug 121653] is fixed or either:
* Manually upgrade to fglrx-8.443.1 where it has been recently fixed (see [[#Upgrading to FGLRX-8.443.1]]).
* Build a SLAB-enabled kernel (see [[#Building a custom kernel]]).

==== Failure to display usplash during boot ====
If you see a black screen during the boot process in the internal panel, edit the file {{path|/etc/usplash.conf}} and check that the resolution is OK:

# Usplash configuration file
xres=1024
yres=768

After that, issue the command:
{{cmduser|sudo update-initramfs -u}}

And reboot..

==== Failure to auto-detect resolution on ATI Fglrx ====
{{NOTE|I cannot reproduce this failure. Tested on
- T60 with ATI Mobility Radeon X1400 at 1400x1050 (Flexview)
- T60p with ATI Mobility FireGL V5250 at 1400x1050 (Flexview)}}

It is possible to have a fresh install of Gutsy, however, you will have to type several commands to load the ATI restricted drivers. The trick is two-fold.

# Gutsy will auto attempt to set the resolution. When it fails, it will give you an error message saying that it will try again in two minutes. This means you have small windows of opportunity (2 minutes each) to type in your needed commands.
# The resolution will be stretched such that the command prompt will be off the screen (bottom). You will have to hit Enter about 10-14 times in order to see what was at the bottom of the screen.

With that said, this is how you can install Gutsy:

# Boot off Live CD - highlight Install with Safe Mode Graphics, then press F6 for additional options.
# In the command line at the end, delete "quiet" and change "splash" to "nosplash"
# Start the install. After awhile, your screen will start flashing as Gutsy tries to find a resolution. Just let it go until you get a blue screen saying that it will try again in two minutes. Press Enter to exit.
# Press enter about 10-14 times until you can see a command prompt.
# {{cmduser|sudo apt-get update}}
# {{cmduser|sudo apt-get install -y xorg-driver-fglrx}}
# {{cmduser|sudo depmod -a}}

You may need to hit enter a few times to see what's going on.

Then Enter:
# {{cmduser|sudo aticonfig --initial}}
# {{cmduser|sudo aticonfig --overlay-Type=Xv}}

Hopefully you'll get all of this typed in under 2 minutes. But if not, don't worry. If the screen starts flashing, just let it go until you see the blue screen with the error message saying that it will try again in 2 minutes.

When you're finished, let the 2 minute timer run out by just waiting. This time, however, when the screen starts flashing, it will start the X server.

# Install Ubuntu.
# Reboot.
# When you boot for the first time, you will have to REPEAT THE PROCESS. However, you may need to login as well as confirm your sudo password, which will be tricky since you may not be able to see the prompt off screen. One alternative is to:

Hit {{Key|CTRL}} + {{Key|ALT}} + {{Key|F2}} which will take you to a login screen. Login, and repeat the process, ignoring the flashing screens that will appear every 2 minutes. When you are finished with your typing:
# {{cmduser|startx}}

Then once you're in Ubuntu, immediately click on the restricted drivers icon and enable ATI's fglrx. Then reboot.

== Post-Installation Setup ==
=== ATI Fglrx with Compiz ===

ATI Fglrx users need to manually install the Xgl X server to run Compiz:
{{cmduser|sudo apt-get install xserver-xgl}}
And reboot...

=== Fix suspend/resume ===
If you suffer from [https://launchpad.net/bugs/121653 Ubuntu bug 121653] and you choose to fix it via the two following methods, first you need to make a few changes to /etc/default/acpi-support:
POST_VIDEO=false
RADEON_LIGHT=true
ENABLE_LAPTOP_MODE=true

=== Upgrading to FGLRX-8.443.1 ===
This driver fixes the issues with suspend/resume. Uses the new codebase so, if you want stabillity, stick to 8.40.1
It is not recommended to use it with AIGLX yet, but works perfectly with XGL. (That's not my experience; I installed 8.443.1 with Envy and saw lots of graphic garbage on the screen. For my FireGL 5200, 8.40.4 with a cucstom kernel as described below works much better --[[User:bewst|Dave]])

Install dkms:
{{cmduser|sudo apt-get install debhelper build-essential dkms}}

Download ati-driver-installer-8.443.1-x86.x86_64.run from an [https://a248.e.akamai.net/f/674/9206/0/www2.ati.com/drivers/linux/ati-driver-installer-8.443.1-x86.x86_64.run ATI].

Run:
{{cmduser|chmod a+x ati-driver-installer-8.443.1-x86.x86_64.run}}

Build the packages:
{{cmduser|./ati-driver-installer-$VER-x86.x86_64.run --buildpkg Ubuntu/gutsy}}

Install:
{{cmduser|sudo dpkg -i *.deb}}

Disable 8.37.1 from the restricted modules. Edit /etc/default/linux-restricted-modules-common and add to the list:
DISABLED_MODULES=fglrx

=== Active Protection System (Reduced Power Version) ===
==== Build a custom kernel ====
{{NOTE|There are several options, e.g.:
# Without any package manager (''make'' and ''make install'')
# The debian way (''make-kpkg'' and ''module-assistent''): one package per module
# The ubuntu way (see below): most of the modules in two packages: ''linux-restricted-modules'' and ''linux-ubuntu-modules''}}

The following commands will generate these files (2007-12-23):
linux-headers-2.6.22-14-thinkpad_2.6.22-14.47_i386.deb
linux-image-2.6.22-14-thinkpad_2.6.22-14.47_i386.deb
linux-image-debug-2.6.22-14-thinkpad_2.6.22-14.47_i386.deb
linux-restricted-modules-2.6.22-14-thinkpad_2.6.22.4-14.10_i386.deb
linux-ubuntu-modules-2.6.22-14-thinkpad_2.6.22-14.37_i386.deb

First you need to get the hdapsd disk-protect patch (disk-protect-2.6.22.9-2.patch) at [http://sourceforge.net/mailarchive/forum.php?thread_name=87ir5lk12l.fsf%40denkblock.local&forum_name=hdaps-devel].

Then get the kernel source:
{{cmduser|sudo apt-get build-dep linux-source-2.6.22}}
{{cmduser|apt-get source linux-source-2.6.22}}
{{cmduser|cd linux-source-2.6.22-2.6.22}}
Patch the kernel (optional, required for Active Protection System (hdapsd)):
{{cmduser|patch -p1 < ../disk-protect-2.6.22.9-2.patch}}
Rename the kernel flavour: generic -> thinkpad
{{cmduser|mv debian/config/i386/config.generic debian/config/i386/config.thinkpad}}
{{cmduser|mv debian/abi/2.6.22-14.46/i386/generic debian/abi/2.6.22-14.46/i386/thinkpad}}
{{cmduser|mv debian/abi/2.6.22-14.46/i386/generic.modules debian/abi/2.6.22-14.46/i386/thinkpad.modules}}
Create a dummy control file entry:
{{cmduser|mv debian/control debian/control.orig}}
{{cmduser|sed s/-2.6.22-14-generic/-2.6.22-14-thinkpad/ debian/control.orig > debian/control}}
Change kernel config: SLUB -> SLAB (optional, workaround for ATI Fglrx and suspend/resume failure)
{{cmduser|<nowiki>echo CONFIG_SLAB=y >> debian/config/i386/config.thinkpad</nowiki>}}
Make further changes to the kernel config (optional):
{{cmduser|cp -r . ../src-copy}}
{{cmduser|cat debian/config/i386/config debian/config/i386/config.thinkpad ../src-copy/.config}}
{{cmduser|pushd ../src-copy}}
{{cmduser|make menuconfig}}
{{cmduser|popd}}
{{cmduser|rm debian/config/i386/*}}
{{cmduser|cp ../src-copy/.config debian/config/i386/config.thinkpad}}

Rebuild kernel config:
{{cmduser|chmod 755 debian/scripts/misc/splitconfig.pl}}
{{cmduser|chmod 755 debian/scripts/misc/oldconfig}}
{{cmduser|debian/scripts/misc/oldconfig i386}}

Now build the kernel:
{{cmduser|<nowiki>AUTOBUILD=1 NOEXTRAS=1 fakeroot debian/rules binary-thinkpad</nowiki>}}
{{cmduser|cd ..}}
And install the kernel headers:
{{cmduser|sudo dpkg -i linux-headers-2.6.22-14-thinkpad_2.6.22-14.47_i386.deb}}

Get ubuntu modules source:
{{cmduser|sudo apt-get build-dep linux-ubuntu-modules-2.6.22}}
{{cmduser|apt-get source linux-ubuntu-modules-2.6.22}}
{{cmduser|cd linux-ubuntu-modules-2.6.22-2.6.22}}
Create a dummy control file entry:
{{cmduser|mv debian/control debian/control.orig}}
{{cmduser|sed s/-2.6.22-14-generic/-2.6.22-14-thinkpad/ debian/control.orig > debian/control}}
Build the ubuntu modules:
{{cmduser|<nowiki>fakeroot debian/rules binary-debs flavours=thinkpad</nowiki>}}
{{cmduser|cd ..}}

Get restricted modules source:
{{cmduser|sudo apt-get build-dep linux-restricted-modules-common}}
{{cmduser|apt-get source linux-restricted-modules-common}}
{{cmduser|cd linux-restricted-modules-2.6.22-2.6.22.4}}
Create a dummy control file entry:
{{cmduser|mv debian/control.stub.in debian/control.stub.in.orig}}
{{cmduser|sed s/-@@ABIVER@@-generic/-@@ABIVER@@-thinkpad/ debian/control.stub.in.orig > debian/control.stub.in}}
{{cmduser|debian/rules debian/control}}
Fix debian/rules (not required for me --[[User:Sascha|Sascha]] worked out for me --[[User:tbo|Tobi]]):
{{cmduser|<nowiki>mv debian/rules debian/rules.orig</nowiki>}}
{{cmduser|<nowiki>cat debian/rules.orig | sed 's/patch\ \-p0/TEMP=\/tmp\ patch\ \-p0/g' \
| sed 's/dh_installdirs\ \-pfglrx\-control/chmod\ \-R\ u\+w\ \.\ \;\ dh_installdirs\ \-pfglrx\-control/g' \
> debian/rules</nowiki>}}
{{cmduser|chmod u+x debian/rules}}

Build the restricted modules:
{{cmduser|<nowiki>fakeroot debian/rules binary-debs flavours=2.6.22-14-thinkpad ati_flavours=2.6.22-14-thinkpad nv_flavours=2.6.22-14-thinkpad</nowiki>}}
{{cmduser|cd ..}}

Install the kernel and the modules:
{{cmduser|sudo dpkg -i \}}
linux-restricted-modules-2.6.22-14-thinkpad_2.6.22.4-14.10_i386.deb \
linux-ubuntu-modules-2.6.22-14-thinkpad_2.6.22-14.37_i386.deb \
linux-image-2.6.22-14-thinkpad_2.6.22-14.47_i386.deb

Reboot to load the kernel.

==== Install Active Protection System ====
A [#Build a custom kernel|patched kernel]]), tp-smapi kernel modules >= 0.32 and hdapsd userspace daemon newer than 2007-05-24 are needed.

First get tp-smapi modules (no ubuntu package available, so get debian's tp-smapi-source package at [http://packages.debian.org/sid/tp-smapi-source]):
{{cmduser|wget http://ftp.de.debian.org/debian/pool/main/t/tp-smapi/tp-smapi-source_0.34-1_all.deb}}
{{cmduser|sudo dpkg -i tp-smapi-source_0.34-1_all.deb}}
Build tp-smapi modules:
{{cmduser|m-a -u . -t build tp-smapi}}
And install tp-smapi-modules:
{{cmduser|sudo dpkg -i tp-smapi-modules-2.6.22-14-thinkpad_0.34-1+2.6.22-14.47_i386.deb}}
First test:
{{cmduser|sudo rmmod hdaps}}
{{cmduser|sudo modprobe -a tp_smapi hdaps}}

Now get and install hdapsd userspace daemon (Ubuntu Gibbon's hdapsd package is too old, so get Hardy's version at [http://packages.ubuntu.com/hardy/misc/hdapsd]):
{{cmduser|wget http://mirrors.kernel.org/ubuntu/pool/universe/h/hdapsd/hdapsd_0.0.20070803-1_i386.deb}}
{{cmduser|sudo dpkg -i hdapsd_0.0.20070803-1_i386.deb}}

You need to update the udev rules:
{{cmduser|sudo udevtrigger}}

Check /etc/default/hdapsd to make sure it is trying to protect your internal hard drive. Laptops with SATA drives (like my T60p) will need an edit for sure.

Reboot... and check your syslog for scsi_protect_queue() and scsi_unprotect_queue() log messages...

== See also ==
* [[How to reduce power consumption]]
* [[How to get special keys to work]]
* https://wiki.ubuntu.com/ThinkFinger
* https://help.ubuntu.com/community/SynapticsTouchpad

== References ==
* [[Installing Ubuntu 7.04 (Feisty Fawn) on a ThinkPad T60]]

[[Category: T60]] [[Category: Ubuntu 7.10]]

Installing Ubuntu 7.10 (Gutsy Gibbon) on a Thinkpad T60

2008-02-07T01:21:06Z

SteveSims: /* 2007-02-06: Update: Speakers no longer detected, mute and ThinkVantage buttons no longer work */

== Features ==
=== Graphical Configuration Tool ===
Some Thinkpad {{T60}}s laptops ship with ATI video cards. Previously [[:Category:Ubuntu 7.04|Ubtuntu 7.04]] Open Source video drivers could be graphically configured with a minimal utility that allowed to choose a single resolution. However, users could be compelled to use the non-free ATI video driver ([[Fglrx]]) because ATI shipped a more featureful utility, Catalyst Control Center. Gusty Gibbon now ships a more fully-featured utility, making the Open Source video drivers a more attractive choice.

=== Desktop 3D effects ===
[[Xgl|Compiz Fusion]] is enabled by default and will bring 3D desktop visual effects that improve the usability and visual appeal of the system. Ubuntu 7.10 automatically detects whether the hardware is capable of running compiz; if not, it falls back to normal desktop.

== Installation ==
Installation of Gutsy Gibbon on the ThinkPad T60 went without a hitch.

=== Dual booting ===
I was able to resize an existing ext3 partition and perform a new install of Ubuntu 7.10 without removing Feisty Fawn. If you are resizing or installing Gutsy Gibbon on a clean partition while maintaining other operating system partitions, I would suggest reinstalling the Grub boot loader so a fresh partition is created with Gutsy Gibbon and other existing OSes like Feisty Fawn or Fedora.

=== Known Issues ===
===2007-02-06: Update: Speakers no longer detected, mute and ThinkVantage buttons no longer work===

The update happened around February 5th. The mute and ThinkVantage buttons now do nothing, and the up and down volume buttons just bring up the volume indicator but don't change it.

Ubuntu detects the volume buttons and accepts them as shortcuts in Keyboard Shortcuts, but it does not detect the ThinkVantage or the mute buttons. Also, after the update and subsequent reboot, the volume appears to be off but is really on at a very low volume. The up and down sounds are heard when the volume buttons are pressed, but volume doesn't change.

Opening Volume Control displays the dialog: "No volume control GStreamer plugins and/or devices were found."

Right-clicking on the speaker icon in the upper right panel and selecting Preferences displays this dialog:

[[Image:The volume control did not find any.png]]

Headphones don't work either.

[[User:SteveSims|SteveSims]] 01:45, 7 February 2008 (CET)

==== ATI Fglrx breaks over suspend resume ====
If your laptop uses the ATI Fglrx driver and you have a perfectly fine Ubuntu Feisty 7.04 installation, Fglrx breaks on a suspend/resume after an upgrade to 7.10. The Open Source driver is available as an alternative; else it is recommended to not upgrade until [https://launchpad.net/bugs/121653 Ubuntu bug 121653] is fixed or either:
* Manually upgrade to fglrx-8.443.1 where it has been recently fixed (see [[#Upgrading to FGLRX-8.443.1]]).
* Build a SLAB-enabled kernel (see [[#Building a custom kernel]]).

==== Failure to display usplash during boot ====
If you see a black screen during the boot process in the internal panel, edit the file {{path|/etc/usplash.conf}} and check that the resolution is OK:

# Usplash configuration file
xres=1024
yres=768

After that, issue the command:
{{cmduser|sudo update-initramfs -u}}

And reboot..

==== Failure to auto-detect resolution on ATI Fglrx ====
{{NOTE|I cannot reproduce this failure. Tested on
- T60 with ATI Mobility Radeon X1400 at 1400x1050 (Flexview)
- T60p with ATI Mobility FireGL V5250 at 1400x1050 (Flexview)}}

It is possible to have a fresh install of Gutsy, however, you will have to type several commands to load the ATI restricted drivers. The trick is two-fold.

# Gutsy will auto attempt to set the resolution. When it fails, it will give you an error message saying that it will try again in two minutes. This means you have small windows of opportunity (2 minutes each) to type in your needed commands.
# The resolution will be stretched such that the command prompt will be off the screen (bottom). You will have to hit Enter about 10-14 times in order to see what was at the bottom of the screen.

With that said, this is how you can install Gutsy:

# Boot off Live CD - highlight Install with Safe Mode Graphics, then press F6 for additional options.
# In the command line at the end, delete "quiet" and change "splash" to "nosplash"
# Start the install. After awhile, your screen will start flashing as Gutsy tries to find a resolution. Just let it go until you get a blue screen saying that it will try again in two minutes. Press Enter to exit.
# Press enter about 10-14 times until you can see a command prompt.
# {{cmduser|sudo apt-get update}}
# {{cmduser|sudo apt-get install -y xorg-driver-fglrx}}
# {{cmduser|sudo depmod -a}}

You may need to hit enter a few times to see what's going on.

Then Enter:
# {{cmduser|sudo aticonfig --initial}}
# {{cmduser|sudo aticonfig --overlay-Type=Xv}}

Hopefully you'll get all of this typed in under 2 minutes. But if not, don't worry. If the screen starts flashing, just let it go until you see the blue screen with the error message saying that it will try again in 2 minutes.

When you're finished, let the 2 minute timer run out by just waiting. This time, however, when the screen starts flashing, it will start the X server.

# Install Ubuntu.
# Reboot.
# When you boot for the first time, you will have to REPEAT THE PROCESS. However, you may need to login as well as confirm your sudo password, which will be tricky since you may not be able to see the prompt off screen. One alternative is to:

Hit {{Key|CTRL}} + {{Key|ALT}} + {{Key|F2}} which will take you to a login screen. Login, and repeat the process, ignoring the flashing screens that will appear every 2 minutes. When you are finished with your typing:
# {{cmduser|startx}}

Then once you're in Ubuntu, immediately click on the restricted drivers icon and enable ATI's fglrx. Then reboot.

== Post-Installation Setup ==
=== ATI Fglrx with Compiz ===

ATI Fglrx users need to manually install the Xgl X server to run Compiz:
{{cmduser|sudo apt-get install xserver-xgl}}
And reboot...

=== Fix suspend/resume ===
If you suffer from [https://launchpad.net/bugs/121653 Ubuntu bug 121653] and you choose to fix it via the two following methods, first you need to make a few changes to /etc/default/acpi-support:
POST_VIDEO=false
RADEON_LIGHT=true
ENABLE_LAPTOP_MODE=true

=== Upgrading to FGLRX-8.443.1 ===
This driver fixes the issues with suspend/resume. Uses the new codebase so, if you want stabillity, stick to 8.40.1
It is not recommended to use it with AIGLX yet, but works perfectly with XGL. (That's not my experience; I installed 8.443.1 with Envy and saw lots of graphic garbage on the screen. For my FireGL 5200, 8.40.4 with a cucstom kernel as described below works much better --[[User:bewst|Dave]])

Install dkms:
{{cmduser|sudo apt-get install debhelper build-essential dkms}}

Download ati-driver-installer-8.443.1-x86.x86_64.run from an [https://a248.e.akamai.net/f/674/9206/0/www2.ati.com/drivers/linux/ati-driver-installer-8.443.1-x86.x86_64.run ATI].

Run:
{{cmduser|chmod a+x ati-driver-installer-8.443.1-x86.x86_64.run}}

Build the packages:
{{cmduser|./ati-driver-installer-$VER-x86.x86_64.run --buildpkg Ubuntu/gutsy}}

Install:
{{cmduser|sudo dpkg -i *.deb}}

Disable 8.37.1 from the restricted modules. Edit /etc/default/linux-restricted-modules-common and add to the list:
DISABLED_MODULES=fglrx

=== Active Protection System (Reduced Power Version) ===
==== Build a custom kernel ====
{{NOTE|There are several options, e.g.:
# Without any package manager (''make'' and ''make install'')
# The debian way (''make-kpkg'' and ''module-assistent''): one package per module
# The ubuntu way (see below): most of the modules in two packages: ''linux-restricted-modules'' and ''linux-ubuntu-modules''}}

The following commands will generate these files (2007-12-23):
linux-headers-2.6.22-14-thinkpad_2.6.22-14.47_i386.deb
linux-image-2.6.22-14-thinkpad_2.6.22-14.47_i386.deb
linux-image-debug-2.6.22-14-thinkpad_2.6.22-14.47_i386.deb
linux-restricted-modules-2.6.22-14-thinkpad_2.6.22.4-14.10_i386.deb
linux-ubuntu-modules-2.6.22-14-thinkpad_2.6.22-14.37_i386.deb

First you need to get the hdapsd disk-protect patch (disk-protect-2.6.22.9-2.patch) at [http://sourceforge.net/mailarchive/forum.php?thread_name=87ir5lk12l.fsf%40denkblock.local&forum_name=hdaps-devel].

Then get the kernel source:
{{cmduser|sudo apt-get build-dep linux-source-2.6.22}}
{{cmduser|apt-get source linux-source-2.6.22}}
{{cmduser|cd linux-source-2.6.22-2.6.22}}
Patch the kernel (optional, required for Active Protection System (hdapsd)):
{{cmduser|patch -p1 < ../disk-protect-2.6.22.9-2.patch}}
Rename the kernel flavour: generic -> thinkpad
{{cmduser|mv debian/config/i386/config.generic debian/config/i386/config.thinkpad}}
{{cmduser|mv debian/abi/2.6.22-14.46/i386/generic debian/abi/2.6.22-14.46/i386/thinkpad}}
{{cmduser|mv debian/abi/2.6.22-14.46/i386/generic.modules debian/abi/2.6.22-14.46/i386/thinkpad.modules}}
Create a dummy control file entry:
{{cmduser|mv debian/control debian/control.orig}}
{{cmduser|sed s/-2.6.22-14-generic/-2.6.22-14-thinkpad/ debian/control.orig > debian/control}}
Change kernel config: SLUB -> SLAB (optional, workaround for ATI Fglrx and suspend/resume failure)
{{cmduser|<nowiki>echo CONFIG_SLAB=y >> debian/config/i386/config.thinkpad</nowiki>}}
Make further changes to the kernel config (optional):
{{cmduser|cp -r . ../src-copy}}
{{cmduser|cat debian/config/i386/config debian/config/i386/config.thinkpad ../src-copy/.config}}
{{cmduser|pushd ../src-copy}}
{{cmduser|make menuconfig}}
{{cmduser|popd}}
{{cmduser|rm debian/config/i386/*}}
{{cmduser|cp ../src-copy/.config debian/config/i386/config.thinkpad}}

Rebuild kernel config:
{{cmduser|chmod 755 debian/scripts/misc/splitconfig.pl}}
{{cmduser|chmod 755 debian/scripts/misc/oldconfig}}
{{cmduser|debian/scripts/misc/oldconfig i386}}

Now build the kernel:
{{cmduser|<nowiki>AUTOBUILD=1 NOEXTRAS=1 fakeroot debian/rules binary-thinkpad</nowiki>}}
{{cmduser|cd ..}}
And install the kernel headers:
{{cmduser|sudo dpkg -i linux-headers-2.6.22-14-thinkpad_2.6.22-14.47_i386.deb}}

Get ubuntu modules source:
{{cmduser|sudo apt-get build-dep linux-ubuntu-modules-2.6.22}}
{{cmduser|apt-get source linux-ubuntu-modules-2.6.22}}
{{cmduser|cd linux-ubuntu-modules-2.6.22-2.6.22}}
Create a dummy control file entry:
{{cmduser|mv debian/control debian/control.orig}}
{{cmduser|sed s/-2.6.22-14-generic/-2.6.22-14-thinkpad/ debian/control.orig > debian/control}}
Build the ubuntu modules:
{{cmduser|<nowiki>fakeroot debian/rules binary-debs flavours=thinkpad</nowiki>}}
{{cmduser|cd ..}}

Get restricted modules source:
{{cmduser|sudo apt-get build-dep linux-restricted-modules-common}}
{{cmduser|apt-get source linux-restricted-modules-common}}
{{cmduser|cd linux-restricted-modules-2.6.22-2.6.22.4}}
Create a dummy control file entry:
{{cmduser|mv debian/control.stub.in debian/control.stub.in.orig}}
{{cmduser|sed s/-@@ABIVER@@-generic/-@@ABIVER@@-thinkpad/ debian/control.stub.in.orig > debian/control.stub.in}}
{{cmduser|debian/rules debian/control}}
Fix debian/rules (not required for me --[[User:Sascha|Sascha]] worked out for me --[[User:tbo|Tobi]]):
{{cmduser|<nowiki>mv debian/rules debian/rules.orig</nowiki>}}
{{cmduser|<nowiki>cat debian/rules.orig | sed 's/patch\ \-p0/TEMP=\/tmp\ patch\ \-p0/g' \
| sed 's/dh_installdirs\ \-pfglrx\-control/chmod\ \-R\ u\+w\ \.\ \;\ dh_installdirs\ \-pfglrx\-control/g' \
> debian/rules</nowiki>}}
{{cmduser|chmod u+x debian/rules}}

Build the restricted modules:
{{cmduser|<nowiki>fakeroot debian/rules binary-debs flavours=2.6.22-14-thinkpad ati_flavours=2.6.22-14-thinkpad nv_flavours=2.6.22-14-thinkpad</nowiki>}}
{{cmduser|cd ..}}

Install the kernel and the modules:
{{cmduser|sudo dpkg -i \}}
linux-restricted-modules-2.6.22-14-thinkpad_2.6.22.4-14.10_i386.deb \
linux-ubuntu-modules-2.6.22-14-thinkpad_2.6.22-14.37_i386.deb \
linux-image-2.6.22-14-thinkpad_2.6.22-14.47_i386.deb

Reboot to load the kernel.

==== Install Active Protection System ====
A [#Build a custom kernel|patched kernel]]), tp-smapi kernel modules >= 0.32 and hdapsd userspace daemon newer than 2007-05-24 are needed.

First get tp-smapi modules (no ubuntu package available, so get debian's tp-smapi-source package at [http://packages.debian.org/sid/tp-smapi-source]):
{{cmduser|wget http://ftp.de.debian.org/debian/pool/main/t/tp-smapi/tp-smapi-source_0.34-1_all.deb}}
{{cmduser|sudo dpkg -i tp-smapi-source_0.34-1_all.deb}}
Build tp-smapi modules:
{{cmduser|m-a -u . -t build tp-smapi}}
And install tp-smapi-modules:
{{cmduser|sudo dpkg -i tp-smapi-modules-2.6.22-14-thinkpad_0.34-1+2.6.22-14.47_i386.deb}}
First test:
{{cmduser|sudo rmmod hdaps}}
{{cmduser|sudo modprobe -a tp_smapi hdaps}}

Now get and install hdapsd userspace daemon (Ubuntu Gibbon's hdapsd package is too old, so get Hardy's version at [http://packages.ubuntu.com/hardy/misc/hdapsd]):
{{cmduser|wget http://mirrors.kernel.org/ubuntu/pool/universe/h/hdapsd/hdapsd_0.0.20070803-1_i386.deb}}
{{cmduser|sudo dpkg -i hdapsd_0.0.20070803-1_i386.deb}}

You need to update the udev rules:
{{cmduser|sudo udevtrigger}}

Check /etc/default/hdapsd to make sure it is trying to protect your internal hard drive. Laptops with SATA drives (like my T60p) will need an edit for sure.

Reboot... and check your syslog for scsi_protect_queue() and scsi_unprotect_queue() log messages...

== See also ==
* [[How to reduce power consumption]]
* [[How to get special keys to work]]
* https://wiki.ubuntu.com/ThinkFinger
* https://help.ubuntu.com/community/SynapticsTouchpad

== References ==
* [[Installing Ubuntu 7.04 (Feisty Fawn) on a ThinkPad T60]]

[[Category: T60]] [[Category: Ubuntu 7.10]]

Installing Ubuntu 7.10 (Gutsy Gibbon) on a Thinkpad T60

2008-02-07T01:20:45Z

SteveSims: /* 2007-02-06: Update: Speakers no longer detected, mute and ThinkVantage buttons no longer work */

== Features ==
=== Graphical Configuration Tool ===
Some Thinkpad {{T60}}s laptops ship with ATI video cards. Previously [[:Category:Ubuntu 7.04|Ubtuntu 7.04]] Open Source video drivers could be graphically configured with a minimal utility that allowed to choose a single resolution. However, users could be compelled to use the non-free ATI video driver ([[Fglrx]]) because ATI shipped a more featureful utility, Catalyst Control Center. Gusty Gibbon now ships a more fully-featured utility, making the Open Source video drivers a more attractive choice.

=== Desktop 3D effects ===
[[Xgl|Compiz Fusion]] is enabled by default and will bring 3D desktop visual effects that improve the usability and visual appeal of the system. Ubuntu 7.10 automatically detects whether the hardware is capable of running compiz; if not, it falls back to normal desktop.

== Installation ==
Installation of Gutsy Gibbon on the ThinkPad T60 went without a hitch.

=== Dual booting ===
I was able to resize an existing ext3 partition and perform a new install of Ubuntu 7.10 without removing Feisty Fawn. If you are resizing or installing Gutsy Gibbon on a clean partition while maintaining other operating system partitions, I would suggest reinstalling the Grub boot loader so a fresh partition is created with Gutsy Gibbon and other existing OSes like Feisty Fawn or Fedora.

=== Known Issues ===
===2007-02-06: Update: Speakers no longer detected, mute and ThinkVantage buttons no longer work===

The update happened around February 5th. The mute and ThinkVantage buttons now do nothing, and the up and down volume buttons just bring up the volume indicator but don't change it.

Ubuntu detects the volume buttons and accepts them as shortcuts in Keyboard Shortcuts, but it does not detect the ThinkVantage or the mute buttons. Also, after the update and subsequent reboot, the volume appears to be off but is really on at a very low volume. The up and down sounds are heard when the volume buttons are pressed, but volume doesn't change.

Opening Volume Control displays the dialog: "No volume control GStreamer plugins and/or devices were found."

Right-clicking on the speaker icon in the upper right panel and selecting Preferences displays this dialog:

[[Image:The volume control did not find any.png]]

[[User:SteveSims|SteveSims]] 01:45, 7 February 2008 (CET)

==== ATI Fglrx breaks over suspend resume ====
If your laptop uses the ATI Fglrx driver and you have a perfectly fine Ubuntu Feisty 7.04 installation, Fglrx breaks on a suspend/resume after an upgrade to 7.10. The Open Source driver is available as an alternative; else it is recommended to not upgrade until [https://launchpad.net/bugs/121653 Ubuntu bug 121653] is fixed or either:
* Manually upgrade to fglrx-8.443.1 where it has been recently fixed (see [[#Upgrading to FGLRX-8.443.1]]).
* Build a SLAB-enabled kernel (see [[#Building a custom kernel]]).

==== Failure to display usplash during boot ====
If you see a black screen during the boot process in the internal panel, edit the file {{path|/etc/usplash.conf}} and check that the resolution is OK:

# Usplash configuration file
xres=1024
yres=768

After that, issue the command:
{{cmduser|sudo update-initramfs -u}}

And reboot..

==== Failure to auto-detect resolution on ATI Fglrx ====
{{NOTE|I cannot reproduce this failure. Tested on
- T60 with ATI Mobility Radeon X1400 at 1400x1050 (Flexview)
- T60p with ATI Mobility FireGL V5250 at 1400x1050 (Flexview)}}

It is possible to have a fresh install of Gutsy, however, you will have to type several commands to load the ATI restricted drivers. The trick is two-fold.

# Gutsy will auto attempt to set the resolution. When it fails, it will give you an error message saying that it will try again in two minutes. This means you have small windows of opportunity (2 minutes each) to type in your needed commands.
# The resolution will be stretched such that the command prompt will be off the screen (bottom). You will have to hit Enter about 10-14 times in order to see what was at the bottom of the screen.

With that said, this is how you can install Gutsy:

# Boot off Live CD - highlight Install with Safe Mode Graphics, then press F6 for additional options.
# In the command line at the end, delete "quiet" and change "splash" to "nosplash"
# Start the install. After awhile, your screen will start flashing as Gutsy tries to find a resolution. Just let it go until you get a blue screen saying that it will try again in two minutes. Press Enter to exit.
# Press enter about 10-14 times until you can see a command prompt.
# {{cmduser|sudo apt-get update}}
# {{cmduser|sudo apt-get install -y xorg-driver-fglrx}}
# {{cmduser|sudo depmod -a}}

You may need to hit enter a few times to see what's going on.

Then Enter:
# {{cmduser|sudo aticonfig --initial}}
# {{cmduser|sudo aticonfig --overlay-Type=Xv}}

Hopefully you'll get all of this typed in under 2 minutes. But if not, don't worry. If the screen starts flashing, just let it go until you see the blue screen with the error message saying that it will try again in 2 minutes.

When you're finished, let the 2 minute timer run out by just waiting. This time, however, when the screen starts flashing, it will start the X server.

# Install Ubuntu.
# Reboot.
# When you boot for the first time, you will have to REPEAT THE PROCESS. However, you may need to login as well as confirm your sudo password, which will be tricky since you may not be able to see the prompt off screen. One alternative is to:

Hit {{Key|CTRL}} + {{Key|ALT}} + {{Key|F2}} which will take you to a login screen. Login, and repeat the process, ignoring the flashing screens that will appear every 2 minutes. When you are finished with your typing:
# {{cmduser|startx}}

Then once you're in Ubuntu, immediately click on the restricted drivers icon and enable ATI's fglrx. Then reboot.

== Post-Installation Setup ==
=== ATI Fglrx with Compiz ===

ATI Fglrx users need to manually install the Xgl X server to run Compiz:
{{cmduser|sudo apt-get install xserver-xgl}}
And reboot...

=== Fix suspend/resume ===
If you suffer from [https://launchpad.net/bugs/121653 Ubuntu bug 121653] and you choose to fix it via the two following methods, first you need to make a few changes to /etc/default/acpi-support:
POST_VIDEO=false
RADEON_LIGHT=true
ENABLE_LAPTOP_MODE=true

=== Upgrading to FGLRX-8.443.1 ===
This driver fixes the issues with suspend/resume. Uses the new codebase so, if you want stabillity, stick to 8.40.1
It is not recommended to use it with AIGLX yet, but works perfectly with XGL. (That's not my experience; I installed 8.443.1 with Envy and saw lots of graphic garbage on the screen. For my FireGL 5200, 8.40.4 with a cucstom kernel as described below works much better --[[User:bewst|Dave]])

Install dkms:
{{cmduser|sudo apt-get install debhelper build-essential dkms}}

Download ati-driver-installer-8.443.1-x86.x86_64.run from an [https://a248.e.akamai.net/f/674/9206/0/www2.ati.com/drivers/linux/ati-driver-installer-8.443.1-x86.x86_64.run ATI].

Run:
{{cmduser|chmod a+x ati-driver-installer-8.443.1-x86.x86_64.run}}

Build the packages:
{{cmduser|./ati-driver-installer-$VER-x86.x86_64.run --buildpkg Ubuntu/gutsy}}

Install:
{{cmduser|sudo dpkg -i *.deb}}

Disable 8.37.1 from the restricted modules. Edit /etc/default/linux-restricted-modules-common and add to the list:
DISABLED_MODULES=fglrx

=== Active Protection System (Reduced Power Version) ===
==== Build a custom kernel ====
{{NOTE|There are several options, e.g.:
# Without any package manager (''make'' and ''make install'')
# The debian way (''make-kpkg'' and ''module-assistent''): one package per module
# The ubuntu way (see below): most of the modules in two packages: ''linux-restricted-modules'' and ''linux-ubuntu-modules''}}

The following commands will generate these files (2007-12-23):
linux-headers-2.6.22-14-thinkpad_2.6.22-14.47_i386.deb
linux-image-2.6.22-14-thinkpad_2.6.22-14.47_i386.deb
linux-image-debug-2.6.22-14-thinkpad_2.6.22-14.47_i386.deb
linux-restricted-modules-2.6.22-14-thinkpad_2.6.22.4-14.10_i386.deb
linux-ubuntu-modules-2.6.22-14-thinkpad_2.6.22-14.37_i386.deb

First you need to get the hdapsd disk-protect patch (disk-protect-2.6.22.9-2.patch) at [http://sourceforge.net/mailarchive/forum.php?thread_name=87ir5lk12l.fsf%40denkblock.local&forum_name=hdaps-devel].

Then get the kernel source:
{{cmduser|sudo apt-get build-dep linux-source-2.6.22}}
{{cmduser|apt-get source linux-source-2.6.22}}
{{cmduser|cd linux-source-2.6.22-2.6.22}}
Patch the kernel (optional, required for Active Protection System (hdapsd)):
{{cmduser|patch -p1 < ../disk-protect-2.6.22.9-2.patch}}
Rename the kernel flavour: generic -> thinkpad
{{cmduser|mv debian/config/i386/config.generic debian/config/i386/config.thinkpad}}
{{cmduser|mv debian/abi/2.6.22-14.46/i386/generic debian/abi/2.6.22-14.46/i386/thinkpad}}
{{cmduser|mv debian/abi/2.6.22-14.46/i386/generic.modules debian/abi/2.6.22-14.46/i386/thinkpad.modules}}
Create a dummy control file entry:
{{cmduser|mv debian/control debian/control.orig}}
{{cmduser|sed s/-2.6.22-14-generic/-2.6.22-14-thinkpad/ debian/control.orig > debian/control}}
Change kernel config: SLUB -> SLAB (optional, workaround for ATI Fglrx and suspend/resume failure)
{{cmduser|<nowiki>echo CONFIG_SLAB=y >> debian/config/i386/config.thinkpad</nowiki>}}
Make further changes to the kernel config (optional):
{{cmduser|cp -r . ../src-copy}}
{{cmduser|cat debian/config/i386/config debian/config/i386/config.thinkpad ../src-copy/.config}}
{{cmduser|pushd ../src-copy}}
{{cmduser|make menuconfig}}
{{cmduser|popd}}
{{cmduser|rm debian/config/i386/*}}
{{cmduser|cp ../src-copy/.config debian/config/i386/config.thinkpad}}

Rebuild kernel config:
{{cmduser|chmod 755 debian/scripts/misc/splitconfig.pl}}
{{cmduser|chmod 755 debian/scripts/misc/oldconfig}}
{{cmduser|debian/scripts/misc/oldconfig i386}}

Now build the kernel:
{{cmduser|<nowiki>AUTOBUILD=1 NOEXTRAS=1 fakeroot debian/rules binary-thinkpad</nowiki>}}
{{cmduser|cd ..}}
And install the kernel headers:
{{cmduser|sudo dpkg -i linux-headers-2.6.22-14-thinkpad_2.6.22-14.47_i386.deb}}

Get ubuntu modules source:
{{cmduser|sudo apt-get build-dep linux-ubuntu-modules-2.6.22}}
{{cmduser|apt-get source linux-ubuntu-modules-2.6.22}}
{{cmduser|cd linux-ubuntu-modules-2.6.22-2.6.22}}
Create a dummy control file entry:
{{cmduser|mv debian/control debian/control.orig}}
{{cmduser|sed s/-2.6.22-14-generic/-2.6.22-14-thinkpad/ debian/control.orig > debian/control}}
Build the ubuntu modules:
{{cmduser|<nowiki>fakeroot debian/rules binary-debs flavours=thinkpad</nowiki>}}
{{cmduser|cd ..}}

Get restricted modules source:
{{cmduser|sudo apt-get build-dep linux-restricted-modules-common}}
{{cmduser|apt-get source linux-restricted-modules-common}}
{{cmduser|cd linux-restricted-modules-2.6.22-2.6.22.4}}
Create a dummy control file entry:
{{cmduser|mv debian/control.stub.in debian/control.stub.in.orig}}
{{cmduser|sed s/-@@ABIVER@@-generic/-@@ABIVER@@-thinkpad/ debian/control.stub.in.orig > debian/control.stub.in}}
{{cmduser|debian/rules debian/control}}
Fix debian/rules (not required for me --[[User:Sascha|Sascha]] worked out for me --[[User:tbo|Tobi]]):
{{cmduser|<nowiki>mv debian/rules debian/rules.orig</nowiki>}}
{{cmduser|<nowiki>cat debian/rules.orig | sed 's/patch\ \-p0/TEMP=\/tmp\ patch\ \-p0/g' \
| sed 's/dh_installdirs\ \-pfglrx\-control/chmod\ \-R\ u\+w\ \.\ \;\ dh_installdirs\ \-pfglrx\-control/g' \
> debian/rules</nowiki>}}
{{cmduser|chmod u+x debian/rules}}

Build the restricted modules:
{{cmduser|<nowiki>fakeroot debian/rules binary-debs flavours=2.6.22-14-thinkpad ati_flavours=2.6.22-14-thinkpad nv_flavours=2.6.22-14-thinkpad</nowiki>}}
{{cmduser|cd ..}}

Install the kernel and the modules:
{{cmduser|sudo dpkg -i \}}
linux-restricted-modules-2.6.22-14-thinkpad_2.6.22.4-14.10_i386.deb \
linux-ubuntu-modules-2.6.22-14-thinkpad_2.6.22-14.37_i386.deb \
linux-image-2.6.22-14-thinkpad_2.6.22-14.47_i386.deb

Reboot to load the kernel.

==== Install Active Protection System ====
A [#Build a custom kernel|patched kernel]]), tp-smapi kernel modules >= 0.32 and hdapsd userspace daemon newer than 2007-05-24 are needed.

First get tp-smapi modules (no ubuntu package available, so get debian's tp-smapi-source package at [http://packages.debian.org/sid/tp-smapi-source]):
{{cmduser|wget http://ftp.de.debian.org/debian/pool/main/t/tp-smapi/tp-smapi-source_0.34-1_all.deb}}
{{cmduser|sudo dpkg -i tp-smapi-source_0.34-1_all.deb}}
Build tp-smapi modules:
{{cmduser|m-a -u . -t build tp-smapi}}
And install tp-smapi-modules:
{{cmduser|sudo dpkg -i tp-smapi-modules-2.6.22-14-thinkpad_0.34-1+2.6.22-14.47_i386.deb}}
First test:
{{cmduser|sudo rmmod hdaps}}
{{cmduser|sudo modprobe -a tp_smapi hdaps}}

Now get and install hdapsd userspace daemon (Ubuntu Gibbon's hdapsd package is too old, so get Hardy's version at [http://packages.ubuntu.com/hardy/misc/hdapsd]):
{{cmduser|wget http://mirrors.kernel.org/ubuntu/pool/universe/h/hdapsd/hdapsd_0.0.20070803-1_i386.deb}}
{{cmduser|sudo dpkg -i hdapsd_0.0.20070803-1_i386.deb}}

You need to update the udev rules:
{{cmduser|sudo udevtrigger}}

Check /etc/default/hdapsd to make sure it is trying to protect your internal hard drive. Laptops with SATA drives (like my T60p) will need an edit for sure.

Reboot... and check your syslog for scsi_protect_queue() and scsi_unprotect_queue() log messages...

== See also ==
* [[How to reduce power consumption]]
* [[How to get special keys to work]]
* https://wiki.ubuntu.com/ThinkFinger
* https://help.ubuntu.com/community/SynapticsTouchpad

== References ==
* [[Installing Ubuntu 7.04 (Feisty Fawn) on a ThinkPad T60]]

[[Category: T60]] [[Category: Ubuntu 7.10]]

Talk:Installing Ubuntu 7.10 (Gutsy Gibbon) on a Thinkpad T60

2008-02-07T00:59:06Z

SteveSims: /* 2007-02-06: Update: Volume buttons no longer work */

== Update: ATI Fglrx no longer breaks over suspend resume ==

The Catalyst 8.01 drivers (fglrx 8.45.2) are SLUB-enabled and no longer break Suspend/Resume on Gutsy. The outstanding issues for Suspend/Resume under Gutsy 7.10 for this driver are essentially the same as previously experienced on Feisty 7.04.

==2007-02-06: Update: Speakers no longer detected, mute and ThinkVantage buttons no longer work==

The update happened around February 5th. The mute and ThinkVantage buttons now do nothing, and the up and down volume buttons just bring up the volume indicator but don't change it.

Ubuntu detects the volume buttons and accepts them as shortcuts in Keyboard Shortcuts, but it does not detect the ThinkVantage or the mute buttons. Also, after the update and subsequent reboot, the volume appears to be off but is really on at a very low volume. The up and down sounds are heard when the volume buttons are pressed, but volume doesn't change.

Opening Volume Control displays the dialog: "No volume control GStreamer plugins and/or devices were found."

Right-clicking on the speaker icon in the upper right panel and selecting Preferences displays this dialog:

[[Image:The volume control did not find any.png]]

[[User:SteveSims|SteveSims]] 01:45, 7 February 2008 (CET)

Installing Ubuntu 7.10 (Gutsy Gibbon) on a Thinkpad T60

2008-02-07T00:58:29Z

SteveSims: /* 2007-02-06: Update: Volume buttons no longer work */

== Features ==
=== Graphical Configuration Tool ===
Some Thinkpad {{T60}}s laptops ship with ATI video cards. Previously [[:Category:Ubuntu 7.04|Ubtuntu 7.04]] Open Source video drivers could be graphically configured with a minimal utility that allowed to choose a single resolution. However, users could be compelled to use the non-free ATI video driver ([[Fglrx]]) because ATI shipped a more featureful utility, Catalyst Control Center. Gusty Gibbon now ships a more fully-featured utility, making the Open Source video drivers a more attractive choice.

=== Desktop 3D effects ===
[[Xgl|Compiz Fusion]] is enabled by default and will bring 3D desktop visual effects that improve the usability and visual appeal of the system. Ubuntu 7.10 automatically detects whether the hardware is capable of running compiz; if not, it falls back to normal desktop.

== Installation ==
Installation of Gutsy Gibbon on the ThinkPad T60 went without a hitch.

=== Dual booting ===
I was able to resize an existing ext3 partition and perform a new install of Ubuntu 7.10 without removing Feisty Fawn. If you are resizing or installing Gutsy Gibbon on a clean partition while maintaining other operating system partitions, I would suggest reinstalling the Grub boot loader so a fresh partition is created with Gutsy Gibbon and other existing OSes like Feisty Fawn or Fedora.

=== Known Issues ===
==2007-02-06: Update: Speakers no longer detected, mute and ThinkVantage buttons no longer work==

The update happened around February 5th. The mute and ThinkVantage buttons now do nothing, and the up and down volume buttons just bring up the volume indicator but don't change it.

Ubuntu detects the volume buttons and accepts them as shortcuts in Keyboard Shortcuts, but it does not detect the ThinkVantage or the mute buttons. Also, after the update and subsequent reboot, the volume appears to be off but is really on at a very low volume. The up and down sounds are heard when the volume buttons are pressed, but volume doesn't change.

Opening Volume Control displays the dialog: "No volume control GStreamer plugins and/or devices were found."

Right-clicking on the speaker icon in the upper right panel and selecting Preferences displays this dialog:

[[Image:The volume control did not find any.png]]

[[User:SteveSims|SteveSims]] 01:45, 7 February 2008 (CET)

==== ATI Fglrx breaks over suspend resume ====
If your laptop uses the ATI Fglrx driver and you have a perfectly fine Ubuntu Feisty 7.04 installation, Fglrx breaks on a suspend/resume after an upgrade to 7.10. The Open Source driver is available as an alternative; else it is recommended to not upgrade until [https://launchpad.net/bugs/121653 Ubuntu bug 121653] is fixed or either:
* Manually upgrade to fglrx-8.443.1 where it has been recently fixed (see [[#Upgrading to FGLRX-8.443.1]]).
* Build a SLAB-enabled kernel (see [[#Building a custom kernel]]).

==== Failure to display usplash during boot ====
If you see a black screen during the boot process in the internal panel, edit the file {{path|/etc/usplash.conf}} and check that the resolution is OK:

# Usplash configuration file
xres=1024
yres=768

After that, issue the command:
{{cmduser|sudo update-initramfs -u}}

And reboot..

==== Failure to auto-detect resolution on ATI Fglrx ====
{{NOTE|I cannot reproduce this failure. Tested on
- T60 with ATI Mobility Radeon X1400 at 1400x1050 (Flexview)
- T60p with ATI Mobility FireGL V5250 at 1400x1050 (Flexview)}}

It is possible to have a fresh install of Gutsy, however, you will have to type several commands to load the ATI restricted drivers. The trick is two-fold.

# Gutsy will auto attempt to set the resolution. When it fails, it will give you an error message saying that it will try again in two minutes. This means you have small windows of opportunity (2 minutes each) to type in your needed commands.
# The resolution will be stretched such that the command prompt will be off the screen (bottom). You will have to hit Enter about 10-14 times in order to see what was at the bottom of the screen.

With that said, this is how you can install Gutsy:

# Boot off Live CD - highlight Install with Safe Mode Graphics, then press F6 for additional options.
# In the command line at the end, delete "quiet" and change "splash" to "nosplash"
# Start the install. After awhile, your screen will start flashing as Gutsy tries to find a resolution. Just let it go until you get a blue screen saying that it will try again in two minutes. Press Enter to exit.
# Press enter about 10-14 times until you can see a command prompt.
# {{cmduser|sudo apt-get update}}
# {{cmduser|sudo apt-get install -y xorg-driver-fglrx}}
# {{cmduser|sudo depmod -a}}

You may need to hit enter a few times to see what's going on.

Then Enter:
# {{cmduser|sudo aticonfig --initial}}
# {{cmduser|sudo aticonfig --overlay-Type=Xv}}

Hopefully you'll get all of this typed in under 2 minutes. But if not, don't worry. If the screen starts flashing, just let it go until you see the blue screen with the error message saying that it will try again in 2 minutes.

When you're finished, let the 2 minute timer run out by just waiting. This time, however, when the screen starts flashing, it will start the X server.

# Install Ubuntu.
# Reboot.
# When you boot for the first time, you will have to REPEAT THE PROCESS. However, you may need to login as well as confirm your sudo password, which will be tricky since you may not be able to see the prompt off screen. One alternative is to:

Hit {{Key|CTRL}} + {{Key|ALT}} + {{Key|F2}} which will take you to a login screen. Login, and repeat the process, ignoring the flashing screens that will appear every 2 minutes. When you are finished with your typing:
# {{cmduser|startx}}

Then once you're in Ubuntu, immediately click on the restricted drivers icon and enable ATI's fglrx. Then reboot.

== Post-Installation Setup ==
=== ATI Fglrx with Compiz ===

ATI Fglrx users need to manually install the Xgl X server to run Compiz:
{{cmduser|sudo apt-get install xserver-xgl}}
And reboot...

=== Fix suspend/resume ===
If you suffer from [https://launchpad.net/bugs/121653 Ubuntu bug 121653] and you choose to fix it via the two following methods, first you need to make a few changes to /etc/default/acpi-support:
POST_VIDEO=false
RADEON_LIGHT=true
ENABLE_LAPTOP_MODE=true

=== Upgrading to FGLRX-8.443.1 ===
This driver fixes the issues with suspend/resume. Uses the new codebase so, if you want stabillity, stick to 8.40.1
It is not recommended to use it with AIGLX yet, but works perfectly with XGL. (That's not my experience; I installed 8.443.1 with Envy and saw lots of graphic garbage on the screen. For my FireGL 5200, 8.40.4 with a cucstom kernel as described below works much better --[[User:bewst|Dave]])

Install dkms:
{{cmduser|sudo apt-get install debhelper build-essential dkms}}

Download ati-driver-installer-8.443.1-x86.x86_64.run from an [https://a248.e.akamai.net/f/674/9206/0/www2.ati.com/drivers/linux/ati-driver-installer-8.443.1-x86.x86_64.run ATI].

Run:
{{cmduser|chmod a+x ati-driver-installer-8.443.1-x86.x86_64.run}}

Build the packages:
{{cmduser|./ati-driver-installer-$VER-x86.x86_64.run --buildpkg Ubuntu/gutsy}}

Install:
{{cmduser|sudo dpkg -i *.deb}}

Disable 8.37.1 from the restricted modules. Edit /etc/default/linux-restricted-modules-common and add to the list:
DISABLED_MODULES=fglrx

=== Active Protection System (Reduced Power Version) ===
==== Build a custom kernel ====
{{NOTE|There are several options, e.g.:
# Without any package manager (''make'' and ''make install'')
# The debian way (''make-kpkg'' and ''module-assistent''): one package per module
# The ubuntu way (see below): most of the modules in two packages: ''linux-restricted-modules'' and ''linux-ubuntu-modules''}}

The following commands will generate these files (2007-12-23):
linux-headers-2.6.22-14-thinkpad_2.6.22-14.47_i386.deb
linux-image-2.6.22-14-thinkpad_2.6.22-14.47_i386.deb
linux-image-debug-2.6.22-14-thinkpad_2.6.22-14.47_i386.deb
linux-restricted-modules-2.6.22-14-thinkpad_2.6.22.4-14.10_i386.deb
linux-ubuntu-modules-2.6.22-14-thinkpad_2.6.22-14.37_i386.deb

First you need to get the hdapsd disk-protect patch (disk-protect-2.6.22.9-2.patch) at [http://sourceforge.net/mailarchive/forum.php?thread_name=87ir5lk12l.fsf%40denkblock.local&forum_name=hdaps-devel].

Then get the kernel source:
{{cmduser|sudo apt-get build-dep linux-source-2.6.22}}
{{cmduser|apt-get source linux-source-2.6.22}}
{{cmduser|cd linux-source-2.6.22-2.6.22}}
Patch the kernel (optional, required for Active Protection System (hdapsd)):
{{cmduser|patch -p1 < ../disk-protect-2.6.22.9-2.patch}}
Rename the kernel flavour: generic -> thinkpad
{{cmduser|mv debian/config/i386/config.generic debian/config/i386/config.thinkpad}}
{{cmduser|mv debian/abi/2.6.22-14.46/i386/generic debian/abi/2.6.22-14.46/i386/thinkpad}}
{{cmduser|mv debian/abi/2.6.22-14.46/i386/generic.modules debian/abi/2.6.22-14.46/i386/thinkpad.modules}}
Create a dummy control file entry:
{{cmduser|mv debian/control debian/control.orig}}
{{cmduser|sed s/-2.6.22-14-generic/-2.6.22-14-thinkpad/ debian/control.orig > debian/control}}
Change kernel config: SLUB -> SLAB (optional, workaround for ATI Fglrx and suspend/resume failure)
{{cmduser|<nowiki>echo CONFIG_SLAB=y >> debian/config/i386/config.thinkpad</nowiki>}}
Make further changes to the kernel config (optional):
{{cmduser|cp -r . ../src-copy}}
{{cmduser|cat debian/config/i386/config debian/config/i386/config.thinkpad ../src-copy/.config}}
{{cmduser|pushd ../src-copy}}
{{cmduser|make menuconfig}}
{{cmduser|popd}}
{{cmduser|rm debian/config/i386/*}}
{{cmduser|cp ../src-copy/.config debian/config/i386/config.thinkpad}}

Rebuild kernel config:
{{cmduser|chmod 755 debian/scripts/misc/splitconfig.pl}}
{{cmduser|chmod 755 debian/scripts/misc/oldconfig}}
{{cmduser|debian/scripts/misc/oldconfig i386}}

Now build the kernel:
{{cmduser|<nowiki>AUTOBUILD=1 NOEXTRAS=1 fakeroot debian/rules binary-thinkpad</nowiki>}}
{{cmduser|cd ..}}
And install the kernel headers:
{{cmduser|sudo dpkg -i linux-headers-2.6.22-14-thinkpad_2.6.22-14.47_i386.deb}}

Get ubuntu modules source:
{{cmduser|sudo apt-get build-dep linux-ubuntu-modules-2.6.22}}
{{cmduser|apt-get source linux-ubuntu-modules-2.6.22}}
{{cmduser|cd linux-ubuntu-modules-2.6.22-2.6.22}}
Create a dummy control file entry:
{{cmduser|mv debian/control debian/control.orig}}
{{cmduser|sed s/-2.6.22-14-generic/-2.6.22-14-thinkpad/ debian/control.orig > debian/control}}
Build the ubuntu modules:
{{cmduser|<nowiki>fakeroot debian/rules binary-debs flavours=thinkpad</nowiki>}}
{{cmduser|cd ..}}

Get restricted modules source:
{{cmduser|sudo apt-get build-dep linux-restricted-modules-common}}
{{cmduser|apt-get source linux-restricted-modules-common}}
{{cmduser|cd linux-restricted-modules-2.6.22-2.6.22.4}}
Create a dummy control file entry:
{{cmduser|mv debian/control.stub.in debian/control.stub.in.orig}}
{{cmduser|sed s/-@@ABIVER@@-generic/-@@ABIVER@@-thinkpad/ debian/control.stub.in.orig > debian/control.stub.in}}
{{cmduser|debian/rules debian/control}}
Fix debian/rules (not required for me --[[User:Sascha|Sascha]] worked out for me --[[User:tbo|Tobi]]):
{{cmduser|<nowiki>mv debian/rules debian/rules.orig</nowiki>}}
{{cmduser|<nowiki>cat debian/rules.orig | sed 's/patch\ \-p0/TEMP=\/tmp\ patch\ \-p0/g' \
| sed 's/dh_installdirs\ \-pfglrx\-control/chmod\ \-R\ u\+w\ \.\ \;\ dh_installdirs\ \-pfglrx\-control/g' \
> debian/rules</nowiki>}}
{{cmduser|chmod u+x debian/rules}}

Build the restricted modules:
{{cmduser|<nowiki>fakeroot debian/rules binary-debs flavours=2.6.22-14-thinkpad ati_flavours=2.6.22-14-thinkpad nv_flavours=2.6.22-14-thinkpad</nowiki>}}
{{cmduser|cd ..}}

Install the kernel and the modules:
{{cmduser|sudo dpkg -i \}}
linux-restricted-modules-2.6.22-14-thinkpad_2.6.22.4-14.10_i386.deb \
linux-ubuntu-modules-2.6.22-14-thinkpad_2.6.22-14.37_i386.deb \
linux-image-2.6.22-14-thinkpad_2.6.22-14.47_i386.deb

Reboot to load the kernel.

==== Install Active Protection System ====
A [#Build a custom kernel|patched kernel]]), tp-smapi kernel modules >= 0.32 and hdapsd userspace daemon newer than 2007-05-24 are needed.

First get tp-smapi modules (no ubuntu package available, so get debian's tp-smapi-source package at [http://packages.debian.org/sid/tp-smapi-source]):
{{cmduser|wget http://ftp.de.debian.org/debian/pool/main/t/tp-smapi/tp-smapi-source_0.34-1_all.deb}}
{{cmduser|sudo dpkg -i tp-smapi-source_0.34-1_all.deb}}
Build tp-smapi modules:
{{cmduser|m-a -u . -t build tp-smapi}}
And install tp-smapi-modules:
{{cmduser|sudo dpkg -i tp-smapi-modules-2.6.22-14-thinkpad_0.34-1+2.6.22-14.47_i386.deb}}
First test:
{{cmduser|sudo rmmod hdaps}}
{{cmduser|sudo modprobe -a tp_smapi hdaps}}

Now get and install hdapsd userspace daemon (Ubuntu Gibbon's hdapsd package is too old, so get Hardy's version at [http://packages.ubuntu.com/hardy/misc/hdapsd]):
{{cmduser|wget http://mirrors.kernel.org/ubuntu/pool/universe/h/hdapsd/hdapsd_0.0.20070803-1_i386.deb}}
{{cmduser|sudo dpkg -i hdapsd_0.0.20070803-1_i386.deb}}

You need to update the udev rules:
{{cmduser|sudo udevtrigger}}

Check /etc/default/hdapsd to make sure it is trying to protect your internal hard drive. Laptops with SATA drives (like my T60p) will need an edit for sure.

Reboot... and check your syslog for scsi_protect_queue() and scsi_unprotect_queue() log messages...

== See also ==
* [[How to reduce power consumption]]
* [[How to get special keys to work]]
* https://wiki.ubuntu.com/ThinkFinger
* https://help.ubuntu.com/community/SynapticsTouchpad

== References ==
* [[Installing Ubuntu 7.04 (Feisty Fawn) on a ThinkPad T60]]

[[Category: T60]] [[Category: Ubuntu 7.10]]

Installing Ubuntu 7.10 (Gutsy Gibbon) on a Thinkpad T60

2008-02-07T00:56:58Z

SteveSims: /* Sound buttons */

== Features ==
=== Graphical Configuration Tool ===
Some Thinkpad {{T60}}s laptops ship with ATI video cards. Previously [[:Category:Ubuntu 7.04|Ubtuntu 7.04]] Open Source video drivers could be graphically configured with a minimal utility that allowed to choose a single resolution. However, users could be compelled to use the non-free ATI video driver ([[Fglrx]]) because ATI shipped a more featureful utility, Catalyst Control Center. Gusty Gibbon now ships a more fully-featured utility, making the Open Source video drivers a more attractive choice.

=== Desktop 3D effects ===
[[Xgl|Compiz Fusion]] is enabled by default and will bring 3D desktop visual effects that improve the usability and visual appeal of the system. Ubuntu 7.10 automatically detects whether the hardware is capable of running compiz; if not, it falls back to normal desktop.

== Installation ==
Installation of Gutsy Gibbon on the ThinkPad T60 went without a hitch.

=== Dual booting ===
I was able to resize an existing ext3 partition and perform a new install of Ubuntu 7.10 without removing Feisty Fawn. If you are resizing or installing Gutsy Gibbon on a clean partition while maintaining other operating system partitions, I would suggest reinstalling the Grub boot loader so a fresh partition is created with Gutsy Gibbon and other existing OSes like Feisty Fawn or Fedora.

=== Known Issues ===
==2007-02-06: Update: Volume buttons no longer work==

The update happened around February 5th. The mute and ThinkVantage buttons now do nothing, and the up and down volume buttons just bring up the volume indicator but don't change it.

Ubuntu detects the volume buttons and accepts them as shortcuts in Keyboard Shortcuts, but it does not detect the ThinkVantage or the mute buttons. Also, after the update and subsequent reboot, the volume appears to be off but is really on at a very low volume. The up and down sounds are heard when the volume buttons are pressed, but volume doesn't change.

Opening Volume Control displays the dialog: "No volume control GStreamer plugins and/or devices were found."

Right-clicking on the speaker icon in the upper right panel and selecting Preferences displays this dialog:

[[Image:The volume control did not find any.png]]

[[User:SteveSims|SteveSims]] 01:45, 7 February 2008 (CET)

==== ATI Fglrx breaks over suspend resume ====
If your laptop uses the ATI Fglrx driver and you have a perfectly fine Ubuntu Feisty 7.04 installation, Fglrx breaks on a suspend/resume after an upgrade to 7.10. The Open Source driver is available as an alternative; else it is recommended to not upgrade until [https://launchpad.net/bugs/121653 Ubuntu bug 121653] is fixed or either:
* Manually upgrade to fglrx-8.443.1 where it has been recently fixed (see [[#Upgrading to FGLRX-8.443.1]]).
* Build a SLAB-enabled kernel (see [[#Building a custom kernel]]).

==== Failure to display usplash during boot ====
If you see a black screen during the boot process in the internal panel, edit the file {{path|/etc/usplash.conf}} and check that the resolution is OK:

# Usplash configuration file
xres=1024
yres=768

After that, issue the command:
{{cmduser|sudo update-initramfs -u}}

And reboot..

==== Failure to auto-detect resolution on ATI Fglrx ====
{{NOTE|I cannot reproduce this failure. Tested on
- T60 with ATI Mobility Radeon X1400 at 1400x1050 (Flexview)
- T60p with ATI Mobility FireGL V5250 at 1400x1050 (Flexview)}}

It is possible to have a fresh install of Gutsy, however, you will have to type several commands to load the ATI restricted drivers. The trick is two-fold.

# Gutsy will auto attempt to set the resolution. When it fails, it will give you an error message saying that it will try again in two minutes. This means you have small windows of opportunity (2 minutes each) to type in your needed commands.
# The resolution will be stretched such that the command prompt will be off the screen (bottom). You will have to hit Enter about 10-14 times in order to see what was at the bottom of the screen.

With that said, this is how you can install Gutsy:

# Boot off Live CD - highlight Install with Safe Mode Graphics, then press F6 for additional options.
# In the command line at the end, delete "quiet" and change "splash" to "nosplash"
# Start the install. After awhile, your screen will start flashing as Gutsy tries to find a resolution. Just let it go until you get a blue screen saying that it will try again in two minutes. Press Enter to exit.
# Press enter about 10-14 times until you can see a command prompt.
# {{cmduser|sudo apt-get update}}
# {{cmduser|sudo apt-get install -y xorg-driver-fglrx}}
# {{cmduser|sudo depmod -a}}

You may need to hit enter a few times to see what's going on.

Then Enter:
# {{cmduser|sudo aticonfig --initial}}
# {{cmduser|sudo aticonfig --overlay-Type=Xv}}

Hopefully you'll get all of this typed in under 2 minutes. But if not, don't worry. If the screen starts flashing, just let it go until you see the blue screen with the error message saying that it will try again in 2 minutes.

When you're finished, let the 2 minute timer run out by just waiting. This time, however, when the screen starts flashing, it will start the X server.

# Install Ubuntu.
# Reboot.
# When you boot for the first time, you will have to REPEAT THE PROCESS. However, you may need to login as well as confirm your sudo password, which will be tricky since you may not be able to see the prompt off screen. One alternative is to:

Hit {{Key|CTRL}} + {{Key|ALT}} + {{Key|F2}} which will take you to a login screen. Login, and repeat the process, ignoring the flashing screens that will appear every 2 minutes. When you are finished with your typing:
# {{cmduser|startx}}

Then once you're in Ubuntu, immediately click on the restricted drivers icon and enable ATI's fglrx. Then reboot.

== Post-Installation Setup ==
=== ATI Fglrx with Compiz ===

ATI Fglrx users need to manually install the Xgl X server to run Compiz:
{{cmduser|sudo apt-get install xserver-xgl}}
And reboot...

=== Fix suspend/resume ===
If you suffer from [https://launchpad.net/bugs/121653 Ubuntu bug 121653] and you choose to fix it via the two following methods, first you need to make a few changes to /etc/default/acpi-support:
POST_VIDEO=false
RADEON_LIGHT=true
ENABLE_LAPTOP_MODE=true

=== Upgrading to FGLRX-8.443.1 ===
This driver fixes the issues with suspend/resume. Uses the new codebase so, if you want stabillity, stick to 8.40.1
It is not recommended to use it with AIGLX yet, but works perfectly with XGL. (That's not my experience; I installed 8.443.1 with Envy and saw lots of graphic garbage on the screen. For my FireGL 5200, 8.40.4 with a cucstom kernel as described below works much better --[[User:bewst|Dave]])

Install dkms:
{{cmduser|sudo apt-get install debhelper build-essential dkms}}

Download ati-driver-installer-8.443.1-x86.x86_64.run from an [https://a248.e.akamai.net/f/674/9206/0/www2.ati.com/drivers/linux/ati-driver-installer-8.443.1-x86.x86_64.run ATI].

Run:
{{cmduser|chmod a+x ati-driver-installer-8.443.1-x86.x86_64.run}}

Build the packages:
{{cmduser|./ati-driver-installer-$VER-x86.x86_64.run --buildpkg Ubuntu/gutsy}}

Install:
{{cmduser|sudo dpkg -i *.deb}}

Disable 8.37.1 from the restricted modules. Edit /etc/default/linux-restricted-modules-common and add to the list:
DISABLED_MODULES=fglrx

=== Active Protection System (Reduced Power Version) ===
==== Build a custom kernel ====
{{NOTE|There are several options, e.g.:
# Without any package manager (''make'' and ''make install'')
# The debian way (''make-kpkg'' and ''module-assistent''): one package per module
# The ubuntu way (see below): most of the modules in two packages: ''linux-restricted-modules'' and ''linux-ubuntu-modules''}}

The following commands will generate these files (2007-12-23):
linux-headers-2.6.22-14-thinkpad_2.6.22-14.47_i386.deb
linux-image-2.6.22-14-thinkpad_2.6.22-14.47_i386.deb
linux-image-debug-2.6.22-14-thinkpad_2.6.22-14.47_i386.deb
linux-restricted-modules-2.6.22-14-thinkpad_2.6.22.4-14.10_i386.deb
linux-ubuntu-modules-2.6.22-14-thinkpad_2.6.22-14.37_i386.deb

First you need to get the hdapsd disk-protect patch (disk-protect-2.6.22.9-2.patch) at [http://sourceforge.net/mailarchive/forum.php?thread_name=87ir5lk12l.fsf%40denkblock.local&forum_name=hdaps-devel].

Then get the kernel source:
{{cmduser|sudo apt-get build-dep linux-source-2.6.22}}
{{cmduser|apt-get source linux-source-2.6.22}}
{{cmduser|cd linux-source-2.6.22-2.6.22}}
Patch the kernel (optional, required for Active Protection System (hdapsd)):
{{cmduser|patch -p1 < ../disk-protect-2.6.22.9-2.patch}}
Rename the kernel flavour: generic -> thinkpad
{{cmduser|mv debian/config/i386/config.generic debian/config/i386/config.thinkpad}}
{{cmduser|mv debian/abi/2.6.22-14.46/i386/generic debian/abi/2.6.22-14.46/i386/thinkpad}}
{{cmduser|mv debian/abi/2.6.22-14.46/i386/generic.modules debian/abi/2.6.22-14.46/i386/thinkpad.modules}}
Create a dummy control file entry:
{{cmduser|mv debian/control debian/control.orig}}
{{cmduser|sed s/-2.6.22-14-generic/-2.6.22-14-thinkpad/ debian/control.orig > debian/control}}
Change kernel config: SLUB -> SLAB (optional, workaround for ATI Fglrx and suspend/resume failure)
{{cmduser|<nowiki>echo CONFIG_SLAB=y >> debian/config/i386/config.thinkpad</nowiki>}}
Make further changes to the kernel config (optional):
{{cmduser|cp -r . ../src-copy}}
{{cmduser|cat debian/config/i386/config debian/config/i386/config.thinkpad ../src-copy/.config}}
{{cmduser|pushd ../src-copy}}
{{cmduser|make menuconfig}}
{{cmduser|popd}}
{{cmduser|rm debian/config/i386/*}}
{{cmduser|cp ../src-copy/.config debian/config/i386/config.thinkpad}}

Rebuild kernel config:
{{cmduser|chmod 755 debian/scripts/misc/splitconfig.pl}}
{{cmduser|chmod 755 debian/scripts/misc/oldconfig}}
{{cmduser|debian/scripts/misc/oldconfig i386}}

Now build the kernel:
{{cmduser|<nowiki>AUTOBUILD=1 NOEXTRAS=1 fakeroot debian/rules binary-thinkpad</nowiki>}}
{{cmduser|cd ..}}
And install the kernel headers:
{{cmduser|sudo dpkg -i linux-headers-2.6.22-14-thinkpad_2.6.22-14.47_i386.deb}}

Get ubuntu modules source:
{{cmduser|sudo apt-get build-dep linux-ubuntu-modules-2.6.22}}
{{cmduser|apt-get source linux-ubuntu-modules-2.6.22}}
{{cmduser|cd linux-ubuntu-modules-2.6.22-2.6.22}}
Create a dummy control file entry:
{{cmduser|mv debian/control debian/control.orig}}
{{cmduser|sed s/-2.6.22-14-generic/-2.6.22-14-thinkpad/ debian/control.orig > debian/control}}
Build the ubuntu modules:
{{cmduser|<nowiki>fakeroot debian/rules binary-debs flavours=thinkpad</nowiki>}}
{{cmduser|cd ..}}

Get restricted modules source:
{{cmduser|sudo apt-get build-dep linux-restricted-modules-common}}
{{cmduser|apt-get source linux-restricted-modules-common}}
{{cmduser|cd linux-restricted-modules-2.6.22-2.6.22.4}}
Create a dummy control file entry:
{{cmduser|mv debian/control.stub.in debian/control.stub.in.orig}}
{{cmduser|sed s/-@@ABIVER@@-generic/-@@ABIVER@@-thinkpad/ debian/control.stub.in.orig > debian/control.stub.in}}
{{cmduser|debian/rules debian/control}}
Fix debian/rules (not required for me --[[User:Sascha|Sascha]] worked out for me --[[User:tbo|Tobi]]):
{{cmduser|<nowiki>mv debian/rules debian/rules.orig</nowiki>}}
{{cmduser|<nowiki>cat debian/rules.orig | sed 's/patch\ \-p0/TEMP=\/tmp\ patch\ \-p0/g' \
| sed 's/dh_installdirs\ \-pfglrx\-control/chmod\ \-R\ u\+w\ \.\ \;\ dh_installdirs\ \-pfglrx\-control/g' \
> debian/rules</nowiki>}}
{{cmduser|chmod u+x debian/rules}}

Build the restricted modules:
{{cmduser|<nowiki>fakeroot debian/rules binary-debs flavours=2.6.22-14-thinkpad ati_flavours=2.6.22-14-thinkpad nv_flavours=2.6.22-14-thinkpad</nowiki>}}
{{cmduser|cd ..}}

Install the kernel and the modules:
{{cmduser|sudo dpkg -i \}}
linux-restricted-modules-2.6.22-14-thinkpad_2.6.22.4-14.10_i386.deb \
linux-ubuntu-modules-2.6.22-14-thinkpad_2.6.22-14.37_i386.deb \
linux-image-2.6.22-14-thinkpad_2.6.22-14.47_i386.deb

Reboot to load the kernel.

==== Install Active Protection System ====
A [#Build a custom kernel|patched kernel]]), tp-smapi kernel modules >= 0.32 and hdapsd userspace daemon newer than 2007-05-24 are needed.

First get tp-smapi modules (no ubuntu package available, so get debian's tp-smapi-source package at [http://packages.debian.org/sid/tp-smapi-source]):
{{cmduser|wget http://ftp.de.debian.org/debian/pool/main/t/tp-smapi/tp-smapi-source_0.34-1_all.deb}}
{{cmduser|sudo dpkg -i tp-smapi-source_0.34-1_all.deb}}
Build tp-smapi modules:
{{cmduser|m-a -u . -t build tp-smapi}}
And install tp-smapi-modules:
{{cmduser|sudo dpkg -i tp-smapi-modules-2.6.22-14-thinkpad_0.34-1+2.6.22-14.47_i386.deb}}
First test:
{{cmduser|sudo rmmod hdaps}}
{{cmduser|sudo modprobe -a tp_smapi hdaps}}

Now get and install hdapsd userspace daemon (Ubuntu Gibbon's hdapsd package is too old, so get Hardy's version at [http://packages.ubuntu.com/hardy/misc/hdapsd]):
{{cmduser|wget http://mirrors.kernel.org/ubuntu/pool/universe/h/hdapsd/hdapsd_0.0.20070803-1_i386.deb}}
{{cmduser|sudo dpkg -i hdapsd_0.0.20070803-1_i386.deb}}

You need to update the udev rules:
{{cmduser|sudo udevtrigger}}

Check /etc/default/hdapsd to make sure it is trying to protect your internal hard drive. Laptops with SATA drives (like my T60p) will need an edit for sure.

Reboot... and check your syslog for scsi_protect_queue() and scsi_unprotect_queue() log messages...

== See also ==
* [[How to reduce power consumption]]
* [[How to get special keys to work]]
* https://wiki.ubuntu.com/ThinkFinger
* https://help.ubuntu.com/community/SynapticsTouchpad

== References ==
* [[Installing Ubuntu 7.04 (Feisty Fawn) on a ThinkPad T60]]

[[Category: T60]] [[Category: Ubuntu 7.10]]

Talk:Installing Ubuntu 7.10 (Gutsy Gibbon) on a Thinkpad T60

2008-02-07T00:56:30Z

SteveSims: /* 2007-02-06: Update: Volume buttons no longer work */

== Update: ATI Fglrx no longer breaks over suspend resume ==

The Catalyst 8.01 drivers (fglrx 8.45.2) are SLUB-enabled and no longer break Suspend/Resume on Gutsy. The outstanding issues for Suspend/Resume under Gutsy 7.10 for this driver are essentially the same as previously experienced on Feisty 7.04.

==2007-02-06: Update: Volume buttons no longer work==

The update happened around February 5th. The mute and ThinkVantage buttons now do nothing, and the up and down volume buttons just bring up the volume indicator but don't change it.

Ubuntu detects the volume buttons and accepts them as shortcuts in Keyboard Shortcuts, but it does not detect the ThinkVantage or the mute buttons. Also, after the update and subsequent reboot, the volume appears to be off but is really on at a very low volume. The up and down sounds are heard when the volume buttons are pressed, but volume doesn't change.

Opening Volume Control displays the dialog: "No volume control GStreamer plugins and/or devices were found."

Right-clicking on the speaker icon in the upper right panel and selecting Preferences displays this dialog:

[[Image:The volume control did not find any.png]]

[[User:SteveSims|SteveSims]] 01:45, 7 February 2008 (CET)

File:The volume control did not find any.png

2008-02-07T00:56:14Z

SteveSims: This happened to my T61 after an update on Feb. 6th.

This happened to my T61 after an update on Feb. 6th.

Talk:Installing Ubuntu 7.10 (Gutsy Gibbon) on a Thinkpad T60

2008-02-07T00:56:04Z

SteveSims: /* 2007-02-06: Update: Volume buttons no longer work */

== Update: ATI Fglrx no longer breaks over suspend resume ==

The Catalyst 8.01 drivers (fglrx 8.45.2) are SLUB-enabled and no longer break Suspend/Resume on Gutsy. The outstanding issues for Suspend/Resume under Gutsy 7.10 for this driver are essentially the same as previously experienced on Feisty 7.04.

==2007-02-06: Update: Volume buttons no longer work==

The update happened around February 5th. The mute and ThinkVantage buttons now do nothing, and the up and down volume buttons just bring up the volume indicator but don't change it.

Ubuntu detects the volume buttons and accepts them as shortcuts in Keyboard Shortcuts, but it does not detect the ThinkVantage or the mute buttons. Also, after the update and subsequent reboot, the volume appears to be off but is really on at a very low volume. The up and down sounds are heard when the volume buttons are pressed, but volume doesn't change.

Opening Volume Control displays the dialog: "No volume control GStreamer plugins and/or devices were found."

Right-clicking on the speaker icon in the upper right panel and selecting Preferences displays this dialog:

[[Image|thumb|The volume control did not find any.png]]

[[User:SteveSims|SteveSims]] 01:45, 7 February 2008 (CET)

Talk:Installing Ubuntu 7.10 (Gutsy Gibbon) on a Thinkpad T60

2008-02-07T00:52:31Z

SteveSims: /* 2007-02-06: Update: Volume buttons no longer work */

== Update: ATI Fglrx no longer breaks over suspend resume ==

The Catalyst 8.01 drivers (fglrx 8.45.2) are SLUB-enabled and no longer break Suspend/Resume on Gutsy. The outstanding issues for Suspend/Resume under Gutsy 7.10 for this driver are essentially the same as previously experienced on Feisty 7.04.

==2007-02-06: Update: Volume buttons no longer work==

The update happened around February 5th. The mute and ThinkVantage buttons now do nothing, and the up and down volume buttons just bring up the volume indicator but don't change it.

Ubuntu detects the volume buttons and accepts them as shortcuts in Keyboard Shortcuts, but it does not detect the ThinkVantage or the mute buttons. Also, after the update and subsequent reboot, the volume appears to be off but is really on at a very low volume. The up and down sounds are heard when the volume buttons are pressed, but volume doesn't change.

Opening Volume Control displays the dialog: "No volume control GStreamer plugins and/or devices were found." [[User:SteveSims|SteveSims]] 01:45, 7 February 2008 (CET)

Talk:Installing Ubuntu 7.10 (Gutsy Gibbon) on a Thinkpad T60

2008-02-07T00:51:22Z

SteveSims: /* 2007-02-06: Update: Volume buttons no longer work */

== Update: ATI Fglrx no longer breaks over suspend resume ==

The Catalyst 8.01 drivers (fglrx 8.45.2) are SLUB-enabled and no longer break Suspend/Resume on Gutsy. The outstanding issues for Suspend/Resume under Gutsy 7.10 for this driver are essentially the same as previously experienced on Feisty 7.04.

==2007-02-06: Update: Volume buttons no longer work==

The update happened around February 5th. The mute and ThinkVantage buttons now do nothing, and the up and down volume buttons just bring up the volume indicator but don't change it.

Ubuntu detects the volume buttons and accepts them as shortcuts in Keyboard Shortcuts, but it does not detect the ThinkVantage or the mute buttons. Also, after the update and subsequent reboot, the volume appears to be off but is really on at a very low volume. The up and down sounds are heard when the volume buttons are pressed, but volume doesn't change. [[User:SteveSims|SteveSims]] 01:45, 7 February 2008 (CET)

Installing Ubuntu 7.10 (Gutsy Gibbon) on a Thinkpad T60

2008-02-07T00:46:41Z

SteveSims: /* Known Issues */

== Features ==
=== Graphical Configuration Tool ===
Some Thinkpad {{T60}}s laptops ship with ATI video cards. Previously [[:Category:Ubuntu 7.04|Ubtuntu 7.04]] Open Source video drivers could be graphically configured with a minimal utility that allowed to choose a single resolution. However, users could be compelled to use the non-free ATI video driver ([[Fglrx]]) because ATI shipped a more featureful utility, Catalyst Control Center. Gusty Gibbon now ships a more fully-featured utility, making the Open Source video drivers a more attractive choice.

=== Desktop 3D effects ===
[[Xgl|Compiz Fusion]] is enabled by default and will bring 3D desktop visual effects that improve the usability and visual appeal of the system. Ubuntu 7.10 automatically detects whether the hardware is capable of running compiz; if not, it falls back to normal desktop.

== Installation ==
Installation of Gutsy Gibbon on the ThinkPad T60 went without a hitch.

=== Dual booting ===
I was able to resize an existing ext3 partition and perform a new install of Ubuntu 7.10 without removing Feisty Fawn. If you are resizing or installing Gutsy Gibbon on a clean partition while maintaining other operating system partitions, I would suggest reinstalling the Grub boot loader so a fresh partition is created with Gutsy Gibbon and other existing OSes like Feisty Fawn or Fedora.

=== Known Issues ===
==== Sound buttons ====
After the update on February 5th, the mute and ThinkVantage buttons do not work at all. The up and down volume buttons show the current volume level but do not change it.
==== ATI Fglrx breaks over suspend resume ====
If your laptop uses the ATI Fglrx driver and you have a perfectly fine Ubuntu Feisty 7.04 installation, Fglrx breaks on a suspend/resume after an upgrade to 7.10. The Open Source driver is available as an alternative; else it is recommended to not upgrade until [https://launchpad.net/bugs/121653 Ubuntu bug 121653] is fixed or either:
* Manually upgrade to fglrx-8.443.1 where it has been recently fixed (see [[#Upgrading to FGLRX-8.443.1]]).
* Build a SLAB-enabled kernel (see [[#Building a custom kernel]]).

==== Failure to display usplash during boot ====
If you see a black screen during the boot process in the internal panel, edit the file {{path|/etc/usplash.conf}} and check that the resolution is OK:

# Usplash configuration file
xres=1024
yres=768

After that, issue the command:
{{cmduser|sudo update-initramfs -u}}

And reboot..

==== Failure to auto-detect resolution on ATI Fglrx ====
{{NOTE|I cannot reproduce this failure. Tested on
- T60 with ATI Mobility Radeon X1400 at 1400x1050 (Flexview)
- T60p with ATI Mobility FireGL V5250 at 1400x1050 (Flexview)}}

It is possible to have a fresh install of Gutsy, however, you will have to type several commands to load the ATI restricted drivers. The trick is two-fold.

# Gutsy will auto attempt to set the resolution. When it fails, it will give you an error message saying that it will try again in two minutes. This means you have small windows of opportunity (2 minutes each) to type in your needed commands.
# The resolution will be stretched such that the command prompt will be off the screen (bottom). You will have to hit Enter about 10-14 times in order to see what was at the bottom of the screen.

With that said, this is how you can install Gutsy:

# Boot off Live CD - highlight Install with Safe Mode Graphics, then press F6 for additional options.
# In the command line at the end, delete "quiet" and change "splash" to "nosplash"
# Start the install. After awhile, your screen will start flashing as Gutsy tries to find a resolution. Just let it go until you get a blue screen saying that it will try again in two minutes. Press Enter to exit.
# Press enter about 10-14 times until you can see a command prompt.
# {{cmduser|sudo apt-get update}}
# {{cmduser|sudo apt-get install -y xorg-driver-fglrx}}
# {{cmduser|sudo depmod -a}}

You may need to hit enter a few times to see what's going on.

Then Enter:
# {{cmduser|sudo aticonfig --initial}}
# {{cmduser|sudo aticonfig --overlay-Type=Xv}}

Hopefully you'll get all of this typed in under 2 minutes. But if not, don't worry. If the screen starts flashing, just let it go until you see the blue screen with the error message saying that it will try again in 2 minutes.

When you're finished, let the 2 minute timer run out by just waiting. This time, however, when the screen starts flashing, it will start the X server.

# Install Ubuntu.
# Reboot.
# When you boot for the first time, you will have to REPEAT THE PROCESS. However, you may need to login as well as confirm your sudo password, which will be tricky since you may not be able to see the prompt off screen. One alternative is to:

Hit {{Key|CTRL}} + {{Key|ALT}} + {{Key|F2}} which will take you to a login screen. Login, and repeat the process, ignoring the flashing screens that will appear every 2 minutes. When you are finished with your typing:
# {{cmduser|startx}}

Then once you're in Ubuntu, immediately click on the restricted drivers icon and enable ATI's fglrx. Then reboot.

== Post-Installation Setup ==
=== ATI Fglrx with Compiz ===

ATI Fglrx users need to manually install the Xgl X server to run Compiz:
{{cmduser|sudo apt-get install xserver-xgl}}
And reboot...

=== Fix suspend/resume ===
If you suffer from [https://launchpad.net/bugs/121653 Ubuntu bug 121653] and you choose to fix it via the two following methods, first you need to make a few changes to /etc/default/acpi-support:
POST_VIDEO=false
RADEON_LIGHT=true
ENABLE_LAPTOP_MODE=true

=== Upgrading to FGLRX-8.443.1 ===
This driver fixes the issues with suspend/resume. Uses the new codebase so, if you want stabillity, stick to 8.40.1
It is not recommended to use it with AIGLX yet, but works perfectly with XGL. (That's not my experience; I installed 8.443.1 with Envy and saw lots of graphic garbage on the screen. For my FireGL 5200, 8.40.4 with a cucstom kernel as described below works much better --[[User:bewst|Dave]])

Install dkms:
{{cmduser|sudo apt-get install debhelper build-essential dkms}}

Download ati-driver-installer-8.443.1-x86.x86_64.run from an [https://a248.e.akamai.net/f/674/9206/0/www2.ati.com/drivers/linux/ati-driver-installer-8.443.1-x86.x86_64.run ATI].

Run:
{{cmduser|chmod a+x ati-driver-installer-8.443.1-x86.x86_64.run}}

Build the packages:
{{cmduser|./ati-driver-installer-$VER-x86.x86_64.run --buildpkg Ubuntu/gutsy}}

Install:
{{cmduser|sudo dpkg -i *.deb}}

Disable 8.37.1 from the restricted modules. Edit /etc/default/linux-restricted-modules-common and add to the list:
DISABLED_MODULES=fglrx

=== Active Protection System (Reduced Power Version) ===
==== Build a custom kernel ====
{{NOTE|There are several options, e.g.:
# Without any package manager (''make'' and ''make install'')
# The debian way (''make-kpkg'' and ''module-assistent''): one package per module
# The ubuntu way (see below): most of the modules in two packages: ''linux-restricted-modules'' and ''linux-ubuntu-modules''}}

The following commands will generate these files (2007-12-23):
linux-headers-2.6.22-14-thinkpad_2.6.22-14.47_i386.deb
linux-image-2.6.22-14-thinkpad_2.6.22-14.47_i386.deb
linux-image-debug-2.6.22-14-thinkpad_2.6.22-14.47_i386.deb
linux-restricted-modules-2.6.22-14-thinkpad_2.6.22.4-14.10_i386.deb
linux-ubuntu-modules-2.6.22-14-thinkpad_2.6.22-14.37_i386.deb

First you need to get the hdapsd disk-protect patch (disk-protect-2.6.22.9-2.patch) at [http://sourceforge.net/mailarchive/forum.php?thread_name=87ir5lk12l.fsf%40denkblock.local&forum_name=hdaps-devel].

Then get the kernel source:
{{cmduser|sudo apt-get build-dep linux-source-2.6.22}}
{{cmduser|apt-get source linux-source-2.6.22}}
{{cmduser|cd linux-source-2.6.22-2.6.22}}
Patch the kernel (optional, required for Active Protection System (hdapsd)):
{{cmduser|patch -p1 < ../disk-protect-2.6.22.9-2.patch}}
Rename the kernel flavour: generic -> thinkpad
{{cmduser|mv debian/config/i386/config.generic debian/config/i386/config.thinkpad}}
{{cmduser|mv debian/abi/2.6.22-14.46/i386/generic debian/abi/2.6.22-14.46/i386/thinkpad}}
{{cmduser|mv debian/abi/2.6.22-14.46/i386/generic.modules debian/abi/2.6.22-14.46/i386/thinkpad.modules}}
Create a dummy control file entry:
{{cmduser|mv debian/control debian/control.orig}}
{{cmduser|sed s/-2.6.22-14-generic/-2.6.22-14-thinkpad/ debian/control.orig > debian/control}}
Change kernel config: SLUB -> SLAB (optional, workaround for ATI Fglrx and suspend/resume failure)
{{cmduser|<nowiki>echo CONFIG_SLAB=y >> debian/config/i386/config.thinkpad</nowiki>}}
Make further changes to the kernel config (optional):
{{cmduser|cp -r . ../src-copy}}
{{cmduser|cat debian/config/i386/config debian/config/i386/config.thinkpad ../src-copy/.config}}
{{cmduser|pushd ../src-copy}}
{{cmduser|make menuconfig}}
{{cmduser|popd}}
{{cmduser|rm debian/config/i386/*}}
{{cmduser|cp ../src-copy/.config debian/config/i386/config.thinkpad}}

Rebuild kernel config:
{{cmduser|chmod 755 debian/scripts/misc/splitconfig.pl}}
{{cmduser|chmod 755 debian/scripts/misc/oldconfig}}
{{cmduser|debian/scripts/misc/oldconfig i386}}

Now build the kernel:
{{cmduser|<nowiki>AUTOBUILD=1 NOEXTRAS=1 fakeroot debian/rules binary-thinkpad</nowiki>}}
{{cmduser|cd ..}}
And install the kernel headers:
{{cmduser|sudo dpkg -i linux-headers-2.6.22-14-thinkpad_2.6.22-14.47_i386.deb}}

Get ubuntu modules source:
{{cmduser|sudo apt-get build-dep linux-ubuntu-modules-2.6.22}}
{{cmduser|apt-get source linux-ubuntu-modules-2.6.22}}
{{cmduser|cd linux-ubuntu-modules-2.6.22-2.6.22}}
Create a dummy control file entry:
{{cmduser|mv debian/control debian/control.orig}}
{{cmduser|sed s/-2.6.22-14-generic/-2.6.22-14-thinkpad/ debian/control.orig > debian/control}}
Build the ubuntu modules:
{{cmduser|<nowiki>fakeroot debian/rules binary-debs flavours=thinkpad</nowiki>}}
{{cmduser|cd ..}}

Get restricted modules source:
{{cmduser|sudo apt-get build-dep linux-restricted-modules-common}}
{{cmduser|apt-get source linux-restricted-modules-common}}
{{cmduser|cd linux-restricted-modules-2.6.22-2.6.22.4}}
Create a dummy control file entry:
{{cmduser|mv debian/control.stub.in debian/control.stub.in.orig}}
{{cmduser|sed s/-@@ABIVER@@-generic/-@@ABIVER@@-thinkpad/ debian/control.stub.in.orig > debian/control.stub.in}}
{{cmduser|debian/rules debian/control}}
Fix debian/rules (not required for me --[[User:Sascha|Sascha]] worked out for me --[[User:tbo|Tobi]]):
{{cmduser|<nowiki>mv debian/rules debian/rules.orig</nowiki>}}
{{cmduser|<nowiki>cat debian/rules.orig | sed 's/patch\ \-p0/TEMP=\/tmp\ patch\ \-p0/g' \
| sed 's/dh_installdirs\ \-pfglrx\-control/chmod\ \-R\ u\+w\ \.\ \;\ dh_installdirs\ \-pfglrx\-control/g' \
> debian/rules</nowiki>}}
{{cmduser|chmod u+x debian/rules}}

Build the restricted modules:
{{cmduser|<nowiki>fakeroot debian/rules binary-debs flavours=2.6.22-14-thinkpad ati_flavours=2.6.22-14-thinkpad nv_flavours=2.6.22-14-thinkpad</nowiki>}}
{{cmduser|cd ..}}

Install the kernel and the modules:
{{cmduser|sudo dpkg -i \}}
linux-restricted-modules-2.6.22-14-thinkpad_2.6.22.4-14.10_i386.deb \
linux-ubuntu-modules-2.6.22-14-thinkpad_2.6.22-14.37_i386.deb \
linux-image-2.6.22-14-thinkpad_2.6.22-14.47_i386.deb

Reboot to load the kernel.

==== Install Active Protection System ====
A [#Build a custom kernel|patched kernel]]), tp-smapi kernel modules >= 0.32 and hdapsd userspace daemon newer than 2007-05-24 are needed.

First get tp-smapi modules (no ubuntu package available, so get debian's tp-smapi-source package at [http://packages.debian.org/sid/tp-smapi-source]):
{{cmduser|wget http://ftp.de.debian.org/debian/pool/main/t/tp-smapi/tp-smapi-source_0.34-1_all.deb}}
{{cmduser|sudo dpkg -i tp-smapi-source_0.34-1_all.deb}}
Build tp-smapi modules:
{{cmduser|m-a -u . -t build tp-smapi}}
And install tp-smapi-modules:
{{cmduser|sudo dpkg -i tp-smapi-modules-2.6.22-14-thinkpad_0.34-1+2.6.22-14.47_i386.deb}}
First test:
{{cmduser|sudo rmmod hdaps}}
{{cmduser|sudo modprobe -a tp_smapi hdaps}}

Now get and install hdapsd userspace daemon (Ubuntu Gibbon's hdapsd package is too old, so get Hardy's version at [http://packages.ubuntu.com/hardy/misc/hdapsd]):
{{cmduser|wget http://mirrors.kernel.org/ubuntu/pool/universe/h/hdapsd/hdapsd_0.0.20070803-1_i386.deb}}
{{cmduser|sudo dpkg -i hdapsd_0.0.20070803-1_i386.deb}}

You need to update the udev rules:
{{cmduser|sudo udevtrigger}}

Check /etc/default/hdapsd to make sure it is trying to protect your internal hard drive. Laptops with SATA drives (like my T60p) will need an edit for sure.

Reboot... and check your syslog for scsi_protect_queue() and scsi_unprotect_queue() log messages...

== See also ==
* [[How to reduce power consumption]]
* [[How to get special keys to work]]
* https://wiki.ubuntu.com/ThinkFinger
* https://help.ubuntu.com/community/SynapticsTouchpad

== References ==
* [[Installing Ubuntu 7.04 (Feisty Fawn) on a ThinkPad T60]]

[[Category: T60]] [[Category: Ubuntu 7.10]]

Talk:Installing Ubuntu 7.10 (Gutsy Gibbon) on a Thinkpad T60

2008-02-07T00:45:07Z

SteveSims:

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

2007-11-25T04:54:01Z

SteveSims: /* GM965 instead of X3100 Intel graphics? */

==Nvidia==

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

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

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

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

Has anyone found a fix for this?

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

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

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

==Microphone==

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

This problem does still exist.

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

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

---

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

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

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

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

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

For those that find the above instructions vague:

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

==Volume/Sound Buttons==

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

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

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

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

[Data_4Conditions]
Comment=
ConditionsCount=0

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

[Data_4_1Actions]
ActionsCount=1

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

[Data_4_1Conditions]
Comment=
ConditionsCount=0

[Data_4_1Triggers]
Comment=Simple_action
TriggersCount=1

[Data_4_1Triggers0]
Key=XF86AudioRaiseVolume
Type=SHORTCUT

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

[Data_4_2Actions]
ActionsCount=1

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

[Data_4_2Conditions]
Comment=
ConditionsCount=0

[Data_4_2Triggers]
Comment=Simple_action
TriggersCount=1

[Data_4_2Triggers0]
Key=XF86AudioLowerVolume
Type=SHORTCUT

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

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

==Brightness buttons==

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

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

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

==Compiling existing information==

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

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

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

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

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

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

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

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

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

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

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

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

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

Removed the following packages:
totem-gstreamer

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

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

What to choose? Why, why not?

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

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

== Black screen at boot ==

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

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

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

=== Still annoying ===

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

--Do you have 'vga=' enabled as a kernel parameter? If yes then remove that.

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

== Power Consumption ==

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

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

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

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

<pre>Cannot install 'kolourpaint'

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

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

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

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

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

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

== Networking craps out ==

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

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

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

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

== Rotate Display when docked ==

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

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

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

== Bluetooth script error ==

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

should be:

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

right?

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

File:GM965 X3100.png

2007-11-25T04:48:44Z

SteveSims: My T61 should have an X3100 instead.

My T61 should have an X3100 instead.

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

2007-11-25T04:48:06Z

SteveSims: GM965 instead of X3100 Intel graphics?

==Nvidia==

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

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

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

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

Has anyone found a fix for this?

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

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

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

==Microphone==

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

This problem does still exist.

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

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

---

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

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

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

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

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

For those that find the above instructions vague:

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

==Volume/Sound Buttons==

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

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

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

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

[Data_4Conditions]
Comment=
ConditionsCount=0

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

[Data_4_1Actions]
ActionsCount=1

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

[Data_4_1Conditions]
Comment=
ConditionsCount=0

[Data_4_1Triggers]
Comment=Simple_action
TriggersCount=1

[Data_4_1Triggers0]
Key=XF86AudioRaiseVolume
Type=SHORTCUT

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

[Data_4_2Actions]
ActionsCount=1

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

[Data_4_2Conditions]
Comment=
ConditionsCount=0

[Data_4_2Triggers]
Comment=Simple_action
TriggersCount=1

[Data_4_2Triggers0]
Key=XF86AudioLowerVolume
Type=SHORTCUT

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

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

==Brightness buttons==

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

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

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

==Compiling existing information==

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

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

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

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

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

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

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

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

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

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

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

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

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

Removed the following packages:
totem-gstreamer

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

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

What to choose? Why, why not?

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

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

== Black screen at boot ==

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

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

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

=== Still annoying ===

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

--Do you have 'vga=' enabled as a kernel parameter? If yes then remove that.

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

== Power Consumption ==

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

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

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

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

<pre>Cannot install 'kolourpaint'

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

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

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

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

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

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

== Networking craps out ==

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

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

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

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

== Rotate Display when docked ==

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

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

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

== Bluetooth script error ==

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

should be:

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

right?

==GM965 instead of X3100 Intel graphics?==
My device manager shows this:
[[Image:GM965_X3100.png]]

The T61 should have an X3100, and both are integrated onto the motherboard, so is Linux treating my X3100 like a GM965?

Installing Ubuntu 7.10 (Gutsy Gibbon) on a ThinkPad T61

2007-11-25T01:20:32Z

SteveSims: /* Nvidia N140m: */

==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. 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 video files in Totem, 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 {{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 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

=== 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:====
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 [http://www.nvidia.com/object/linux_display_ia32_169.04.html beta-driver (version 169.04)] by nvidia that fixes the brightness-controls but unfortunately there is currently no ubuntu-package for this driver so you will have to install it manually (which is normally not the preferred way of doing things).

-->please post a "howto install beta drivers" link here

{{QUOTE|Mike Kershaw|linux-thinkpad@linux-thinkpad.org|This problem was solved (for me) with the latest IBM bios release,
October 18, bios 1.26, 7KET56WW. In-X brightness works now via the hw
keys and acpi/ibm/brightness.}}

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

There have been reports that the microphone may not work, please add your input to the talk page [http://www.thinkwiki.org/wiki/Talk:Installing_Ubuntu_7.10_%28Gutsy_Gibbon%29_on_a_ThinkPad_T61#Microphone] and update this section when a consensus on the problem and solution has been reached.

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

== 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 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]). To fix this:

1) Go to the in Applications -> Accessories -> Terminal

2) Enter "sudo nautilus" without the quotation marks.

3) Go to {{path|/boot/grub/}}, backup and then edit {{path|menu.lst}} by 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'''

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

<pre>sudo update-grub</pre>

in the terminal.

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). (Note: I am using KDE. I would think these fixes would work for gnome as well, but someone else would have to test them.)

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

The instructions for Intel video card recommends adding "acpi_sleep=s3_bios" to the kernel parameters in Grub configuration. According to a comment on [https://bugs.launchpad.net/ubuntu/+source/acpi/+bug/139089 Launchpad BUG 139089], the correct setting for Nvidia is "acpi_sleep=s3_mode". Once I changed this, Suspend to ram worked. I have the T61 6459-CTO.

== 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 ===
* 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.
* booting with the "irqpoll" option seems to work for some people against the problem that usb-ports stop working.

=== Wireless activity LED ===

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

== Power consumption ==

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

$ sudo apt-get install powertop
$ sudo powertop

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

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

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

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

Adding the Nvidia card increases the laptops power requirements.

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

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

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

Installing Ubuntu 7.10 (Gutsy Gibbon) on a ThinkPad T61

2007-11-25T01:19:59Z

SteveSims: /* Multiple Monitors */

==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. 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 video files in Totem, 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 {{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 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

=== 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:====
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 [http://www.nvidia.com/object/linux_display_ia32_169.04.html beta-driver (version 169.04)] by nvidia that fixes the brightness-controls but unfortunately there is currently no ubuntu-package for this driver so you will have to install it manually (which is normally not the preferred way of doing things).

-->please post a "howto install beta drivers" link here

{{QUOTE|Mike Kershaw|linux-thinkpad@linux-thinkpad.org|This problem was solved (for me) with the latest IBM bios release,
October 18, bios 1.26, 7KET56WW. In-X brightness works now via the hw
keys and acpi/ibm/brightness.}}

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

There have been reports that the microphone may not work, please add your input to the talk page [http://www.thinkwiki.org/wiki/Talk:Installing_Ubuntu_7.10_%28Gutsy_Gibbon%29_on_a_ThinkPad_T61#Microphone] and update this section when a consensus on the problem and solution has been reached.

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

== 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 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]). To fix this:

1) Go to the in Applications -> Accessories -> Terminal

2) Enter "sudo nautilus" without the quotation marks.

3) Go to {{path|/boot/grub/}}, backup and then edit {{path|menu.lst}} by 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'''

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

<pre>sudo update-grub</pre>

in the terminal.

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). (Note: I am using KDE. I would think these fixes would work for gnome as well, but someone else would have to test them.)

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

The instructions for Intel video card recommends adding "acpi_sleep=s3_bios" to the kernel parameters in Grub configuration. According to a comment on [https://bugs.launchpad.net/ubuntu/+source/acpi/+bug/139089 Launchpad BUG 139089], the correct setting for Nvidia is "acpi_sleep=s3_mode". Once I changed this, Suspend to ram worked. I have the T61 6459-CTO.

== 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 ===
* 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.
* booting with the "irqpoll" option seems to work for some people against the problem that usb-ports stop working.

=== Wireless activity LED ===

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

== Power consumption ==

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

$ sudo apt-get install powertop
$ sudo powertop

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

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

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

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

Adding the Nvidia card increases the laptops power requirements.

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

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

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

Installing Ubuntu 7.10 (Gutsy Gibbon) on a ThinkPad T61

2007-11-25T01:11:47Z

SteveSims: /* Multiple Monitors */

==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. 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 video files in Totem, 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 {{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 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.

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

=== 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:====
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 [http://www.nvidia.com/object/linux_display_ia32_169.04.html beta-driver (version 169.04)] by nvidia that fixes the brightness-controls but unfortunately there is currently no ubuntu-package for this driver so you will have to install it manually (which is normally not the preferred way of doing things).

-->please post a "howto install beta drivers" link here

{{QUOTE|Mike Kershaw|linux-thinkpad@linux-thinkpad.org|This problem was solved (for me) with the latest IBM bios release,
October 18, bios 1.26, 7KET56WW. In-X brightness works now via the hw
keys and acpi/ibm/brightness.}}

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

There have been reports that the microphone may not work, please add your input to the talk page [http://www.thinkwiki.org/wiki/Talk:Installing_Ubuntu_7.10_%28Gutsy_Gibbon%29_on_a_ThinkPad_T61#Microphone] and update this section when a consensus on the problem and solution has been reached.

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

== 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 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]). To fix this:

1) Go to the in Applications -> Accessories -> Terminal

2) Enter "sudo nautilus" without the quotation marks.

3) Go to {{path|/boot/grub/}}, backup and then edit {{path|menu.lst}} by 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'''

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

<pre>sudo update-grub</pre>

in the terminal.

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). (Note: I am using KDE. I would think these fixes would work for gnome as well, but someone else would have to test them.)

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

The instructions for Intel video card recommends adding "acpi_sleep=s3_bios" to the kernel parameters in Grub configuration. According to a comment on [https://bugs.launchpad.net/ubuntu/+source/acpi/+bug/139089 Launchpad BUG 139089], the correct setting for Nvidia is "acpi_sleep=s3_mode". Once I changed this, Suspend to ram worked. I have the T61 6459-CTO.

== 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 ===
* 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.
* booting with the "irqpoll" option seems to work for some people against the problem that usb-ports stop working.

=== Wireless activity LED ===

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

== 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:BIOS Upgrade

2007-11-05T19:36:42Z

SteveSims:

== Dead link ==

The link to the FreeDOS floppy (http://www.ankreuzen.de/freedos/files/fd9sr1/fdos1440.zip), which is needed to upgrade the BIOS from a CD, is dead. Is the information still valid? And is there a different source for the floppy image? [[User:Jamesavery|Jamesavery]] 05:49, 18 February 2007 (CET)

== BIOS upgrade using WINE ==

Does anyone think this would be possible? [[User:Mcalwell|Mcalwell]] 08:58, 28 January 2007 (CET)

: No this is not possible. [[User:Mcalwell|Mcalwell]] 16:01, 12 February 2007 (CET)

== BIOS upgrade without battery ==

Concerning the known problem with 600 series with batteries dead too soon, it is impossible to upgrade the bios without the battery because the original ibm update program doesn't allow this. I bought an old 600E without the battery. There was one workaround, but i think for the older releases of the bios, where you just extracted files and upgraded manualy, bypassing the ibm install program. The page that describes this (i lost the link) has a list of different files, that the ones found in current release so i never did figure out what to do? I would like to upgrade because i have really old bios, where ACPI doesn't cooperate so well with the operating system, either windows or linux.

If somebody finds a workaround please help. Thanks

//Edit

I've found the page on Vim's bios upgrade forum.. I don't know if it exactly for my model, since the files differ.. '''Is it possible, to upgrade bios in linux without the battery?'''

''I have found a working solution WOW on the other forum:

*** This is NOT a safe way to update the bios (disclaimer) ***

* First you need to make a BIOS update floppy disk (from the bios file from IBM - place disk in a: drive, run app and answer Y to the agreement) and then format another disk by right clicking on A: - format - make system bootdisk (assuming you have another machine spare)

* Copy all the files from the IBM Boot disk - in my case
$0029000.fl1
$0029000.fl2
FLASH2.EXE
PROD.DAT
UPDTFLSH.EXE
updtrom.exe
USERINT.EXE
UTILINFO.EXE
to the other clean bootdisk.

* Ensure that there is no config.sys and autoexec.bat so it just runs straight into DOS.

* Place the disk into the Laptop, reboot and allow the machine to load via the floppy

* At the command prompt, type "FLASH2.EXE /U" with no quotes then press enter.

The program will automatically search for the files *.FL1 & *.FL2 and load the bios first then the platform file.

The program will automatically update and perform erasing on the rom and then finish with "Update complete".

* Now reboot.

* Hold F1 down as you turn the laptop back on and go into Easy Setup under "Config" click on Initialize to ensure defaults and settings are error free.

* Save and exit...''

// EDIT

This worked on my machine.. I make no guarantees it will work on others.

The above procedure did not work on my T23 using the 1.20 bios; it kept returning error 14 (Low Battery). However, following those instructions and running "qkflash" rather than flash2 did work for the main bios, and later for the embedded controller.

--grythumn

== Bios upgrade & hidden partition ==

I have disabled the hidden partition to make more space for linux (24G). I still have Windows on the 14G partition. Is it safe to upgrade the BIOS without the hidden partition? I want to get a newer BIOS to fix the annoying fan issue. Thanks

- yes don't worry about it. bios upgrades have nothing to do with whats inside the harddrive.

== BIOS upgrade over PXE ==

Hi,

I have a Thinkpad X20 with a very early BIOS and Embedded Controller Program which I'd like to update. Currently, the only feasible way of doing this is over the network using PXE. I already have a fully functional PXE server using SYSLINUX, and have so far been able to boot the BIOS diskette image using MEMDISK, although I have not attempted to flash anything yet due to the warnings given on the page. Is there any safe way I can update both the Controller Program and the BIOS in the same session over the network in this manner? If not, what other methods would be suitable? I have a USB CD-ROM drive and could probably get hold of a USB floppy drive.

Thanks.

Update: I ended up burning CDs as described and successfully updated everything. I'd still like to know if there is a way I could do it entirely over the network, though.

== RE: grub initrd ==

"Another possibility which works even without a CD-drive or network is to boot the disk image via the grub initrd mechanism."

0) Interesting suggestion. Might be better of in its own section.

1) Could you please elaborate?

2) My first guess (pending your elaboration) would be to "chainload" the first block of the diskimage using the grub commandline, like:
blocklist (''path'')/''to''/''diskimage''
chainloader ''blockvalue''+1

But that's just a guess!

[[user:Pebolle|Paul Bolle]] Fri Jul 15 12:20:47 CEST 2005

== bios/controller update sequence ==

The article says:
"If you go through the readme's on the IBM site they'll cleary state that you must update the Control Program first, then imediately update the BIOS"

When I look at the IBM udpate instructions for the T23, it says:
"If you need to update the BIOS as well as the Embedded Controller Program, update the BIOS first."

Comments?

> I would first contact IBM for clarification, but you should probably be following instructions specific to your model.

>> I did it following IBM's instructions to upgrade the BIOS first. Everything worked out great!

== Firmware upgrade for Intel minipci combo card ==

I just purchased an [[Intel 10/100 Ethernet Mini-PCI Adapter with 56K Modem]] that has an ancient (2.0.6) firmware version. I Downloaded the update file intlbtag.EXE but cabextract was unable to find any cabfiles inside it. I tried running the program via wine and that didn't work either.

Finally I ran the program on a windows machine and created a boot floppy. Then I went through the the process of converting the floppy to a bootable cd via linux and that worked like a charm. The cd successfully updated the minipc card's firmware.

Everything worked but I ended up needing a windows box to do it. Could this have been done without windows?

== Firmware upgrade for Wireless LAN MiniPCI COMBO Card using prism2_srec ==

The appropriate firmware installation program for the wlan card in my R32 can be extracted using cabextract as described in the article. It contains (besides some installation programs) a disk image (1awg06ww.IMG) that seems to be a simple dos boot disk. This image contains 3 .hex files (id010001.hex, pk010100.hex, sf010402.hex) that are recognized by prism2_srec to be "srec"-files. Trying to load them to RAM yields:

{{cmdroot|prism2_srec -v -r wlan0 sf010402.hex}}
S3 CRC-16 generation record: start=0x007E1800 len=65642 prog=1
Start address 0x00000000
srec summary for sf010402.hex
Component: 0x001f 1.4.2 (station firmware)
<snip>
Interface compatibility information:
role=Supplier variant=2 range=1-9 iface=Station Firmware-Driver (4)
role=Actor variant=1 range=1-1 iface=Modem-Firmware (1)
role=Actor variant=2 range=1-1 iface=Controller-Firmware (2)
role=Actor variant=1 range=4-4 iface=Primary Firmware-Driver (3)
<snip>
Wireless LAN card information:
Components:
NICID: 0x8013 v1.0.0
PRIID: 0x0015 v1.0.7
STAID: 0x001f v1.3.6
Interface compatibility information:
PRI role=Supplier variant=1 range=1-1 iface=Modem-Firmware (1)
PRI role=Supplier variant=2 range=1-1 iface=Controller-Firmware (2)
PRI role=Supplier variant=1 range=4-4 iface=Primary Firmware-Driver (3)
STA role=Supplier variant=1 range=1-9 iface=Station Firmware-Driver (4)
PRI role=Actor variant=2 range=1-1 iface=Controller-Firmware (2)
STA role=Actor variant=2 range=1-1 iface=Controller-Firmware (2)
STA role=Actor variant=1 range=1-1 iface=Modem-Firmware (1)
<snip>
This image is not meant to be downloaded to volatile memory.
Incompatible update data.

Has anyone tried to flash this device using prism2_srec yet?
What bothers me is, that the upgrade is for many different parts of the combo card. Does anyone have an opinion on whether this could work?

OK, I took the risk and successfully upgraded my station firmware, BUT when I tried to upgrade the primary firmware the system froze!!! The thinkpad won't start up with the miniPCI card inserted and all efforts to reflash it using the original DOS boot image failed!!!

I'm quite sure the system freeze was not caused directly by prism2_srec, because I have noticed rare system freezes since I have been using my PCMCIA wireless card.
Anyway, if anyone should own a TP R32, I'd be glad if he could tell me the base address of the Wlan card, or it's PCI address.

Thinkpad r32 owner here. I want to upgrade the firmware as well. If you need any information just send an email to haftbar[a]gmail.com [[User:Quickie|Quickie]] 02:12, 1 February 2006 (CET)

==Reorganization suggestion==
The Downloads section is rather long. Would it be an idea to put it on a separate, new page (say: BIOS_Downloads) and link to that new page from this page?

[[User:Pebolle|Paul Bolle]] 21:27, 15 Oct 2005 (CEST)

> I agree with this suggestion.

== Upgrading BIOS and Embedded Control Program from Win XP ==

I'm trying to upgrade the BIOS and Embedded Controller Program from Windows XP following the instructions on the Lenovo website. The problem is the instructions are not very clear about this. The instructions basically state that I must upgrade them at the same time because the Control Program does not work with the older BIOS and the BIOS does not work with the older Control Program. They also state that I should upgrade the Control Program first.

But that means I must boot into XP after having upgraded the Control Program but with the older BIOS in order to then update the BIOS. But if this works then they are actually compatible and there's a contradiction. Am I missing something? I just want to make sure I don't end up with a non-functioning unit.

I have an X23 and want the latest BIOS (v 1.32) and Control Program (v 1.30).

Maybe there should be a note about this in the article? Or maybe I'm the only one who is this stupid :)

Update: I talked to Lenovo support. The situation apparently is that though the description says that the newer control program is not compatible with the older BIOS, they are not so incompatible as to cause the machine to stop working so it is actually possible to use incompatible versions of BIOS and control program. In fact according to the support person it makes no difference if the BIOS is upgraded before the control program or vice versa. So I upgraded the control program using the executable running in Windows XP, which rebooted the computer to perform the upgrade and then I booted Windows again to upgrade the BIOS in the same manner and it all worked fine. If anyone reading this finds it useful maybe you can put it in the article? Or if you find it superfluous just delete this section.

--[[User:xphinx|xphinx]] 12 March 2007

I have an X22 with BIOS version 1.21 and Embedded Controller version 1.17 and using the steps described by you, I succesfully updated my bios to the lastest versions from WindowsXP (BIOS v1.32 / EC v1.30)
Thanks!

== BIOS upgrade for T21 with T20 BIOS ==

Hi, I bought a used T21 recently (type 2647-8AU), and would like to update the BIOS to the latest version, but there's a problem: this T21 appears to have a T20 BIOS (IYET50WW, a/k/a T20 BIOS version 1.11). When I try updating this BIOS using one of IBM's T21 updaters - I tried KZET34WW/v1.16 (the latest one) and KZET16WW/v1.01 (the earliest one) - I get the following message:

<blockquote>
''The diskette in the default drive will not run on this system. Your system is now locked. To restart your system, press Ctrl+Alt+Del.''
</blockquote>

I suspect this message appears because the existing BIOS is a T20 BIOS.

There would appear to be two options: either use the most recent T20 updater (IYET61WW, a/k/a T20 v1.22), or find a way to defeat the block in the KZET34WW/v1.16 T21 updater. Obviously either option is risky in the absence of more information and/or detective work. And I don't know enough about T2x-series hardware to hazard a guess (i.e., were early T21s just T20s with a speed bump, did some T21s get T20 BIOSes by mistake due to factory error, or are the T20 and T21 similar enough that it doesn't matter whether a T20 or T21 BIOS is used).

Some relevant data gleaned from the stickers on the case bottom and the current BIOS:

<blockquote>
* '''Type:''' 2647-8AU (T21 with 800-MHz processor)
* '''S/N:''' 78-0GL1Z (zero-G-L-one-zed)
* '''Manufacture date:''' 03/2001
* '''BIOS version:''' IYET50WW (T20 BIOS v1.11)
* '''System unit S/N:''' (appears to be blank)
* '''System board S/N:''' J1HHS15CL5C
* '''System board P/N:''' 08K3747 (printed on motherboard)
</blockquote>

Thanks for any help anyone can provide.

-Linux Spice

P.S. At first I thought this might be a Frankenstein ThinkPad with a T21 case and a T20 logic board - I did buy it used, after all - but it does have an 800-MHz processor, which was never an option for the T20 (both the BIOS and Linux report it as such), and all the other equipment checks out (except for the hard drive, which was replaced with a 40-GB model).

== BIOS format ==

Not sure if this is the right place, but...
Does anybody know what the formats for the various files are in the bios package (or, even better, the bios.bak file that gets dumped on your disk before updating)? I'm getting progressivel lower and lower level in figuring out just what happens when the computer boots, and the BIOS is the last step... (BTW, I have an x60s)

-- Unknown

Yes. It is a binary dump. Sometimes, there is junk in the start of the file. This should be data enough for you to figure out what you need.

--[[User:Hmh|hmh]] 13:30, 26 February 2007 (CET)

== BIOS update gone bad ==

I tried to flash my [[:Category:600|ThinkPad 600]]'s bios with catastrophalic outcome; now the machine is unable to boot. I, being overly stupid and too self-confident, ignored all warnings about the media containing the bios image not being write-protected (I used one partition of the disk, in which I had installed FreeDOS). During the updating process, the machine started to write screens full of random characters in cyan coloured background. At that point I knew it was b0rked. I asked my friend about what to do now, he said I could open the machine up, locate the bios chip and use EPROM programmer/burner to write the bios image to the chip. He also said that because my machine is very old, there are probably not safeguards like dual bios or emergency bios update from floppy disk on boot. He continued by saying that the bios update file images from IBM/Lenovo website might not be actual , "pure" binaries which could be burned directly to the chip, instead they may contain some vendor-specific checksums which must be taken into account. In ThinkWiki there seems to be no page about bios flashing gone bad and restoring the machine to working condition. Or is there? I really need your help with this; I think I'm able to locate the bios, take it off and find a working EPROM burner, but where can I get a clean BIOS image without the vendor checksums? I'd be grateful for any references.

--[[User:Usv|Usv]] 12:45, 31 March 2007 (CEST)

== BIOS upgrade using USB flash drive ==

I flashed my Thinkpad X41 succesfully with 2.09 BIOS using bootable USB flash drive with DOS 6.22 system files. (I guess Freedos would work aswell). I had such key laying around so I can't help you with making one (i used windows HP USB key format utility to make it long long time ago)
Everything is quite simple once you have USB key and are able to boot DOS from it.

I downloaded the non-diskette ThinkPad BIOS update utility (74uj15us.exe) from lenovo support site and extracted the disk image from it using cabextract:
{{cmduser|cabextract -F "*.IMG" 74uj15us.exe}}

I mounted the image file (74UJ15US.IMG):
{{cmdroot|mkdir /tmp/mnt}}
{{cmdroot|mount -loop o 74UJ15US.IMG /tmp/mnt}}

I mounted the usb key and made a directory for ibm flash utility files under it:
{{cmdroot|mount /dev/sdb1 /mnt/usbflash}}
{{cmdroot|mkdir /mnt/usbflash/ibm}}

I copied the contents of /tmp/mnt to /mnt/usbflash/ibm:
{{cmdroot|cp /tmp/mnt/*.* /mnt/usbflash/ibm}}

Then I unmounted the USB stick and rebooted from it to DOS (F12 during boot -> USB HDD). 
In the DOS Prompt: 
C:\cd ibm
C:\IBM\flash2 /U
I waited for about 1 minute, then my thinkpad made two beeps to signal that the flashing was complete.

PS. Because lacking reliable guide on how to make bootable DOS USB stick for ThinkPads I decided to leave this into discussion section. Please feel free to move/edit all the necessary stuff into the BIOS upgrade article if you know/figure out how to make bootable DOS USB stick in linux. I tried various tutorials including http://gentoo-wiki.com/HOWTO_Create_a_DOS_boot_USB_flash_drive, but didn't manage to boot into the Freedos prompt.
--[[User:ladoga|ladoga]] 04:56 17 Apr 2007

==Reserving RAM for my X3100 graphics card==
Is there any way in the BIOS to reserve memory for my graphics card? I have 2 GB of RAM, which is more than enough for general system processes so I'd like to allocate some to my Intel graphics card. [[User:SteveSims|SteveSims]] 19:36, 5 November 2007 (UTC)

Installing Ubuntu 7.10 (Gutsy Gibbon) on a ThinkPad T61

2007-11-05T19:33:46Z

SteveSims: /* Hissing */

==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. 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 video files in Totem, 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 {{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 a movie will span both the laptop screen and second monitor or projector.

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

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

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), 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:====
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 (You should save anything open just to be safe).

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

There have been reports that the microphone may not work, please add your input to the talk page [http://www.thinkwiki.org/wiki/Talk:Installing_Ubuntu_7.10_%28Gutsy_Gibbon%29_on_a_ThinkPad_T61#Microphone] and update this section when a consensus on the problem and solution has been reached.

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

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

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 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]). To fix this:

1) Go to the in Applications -> Accessories -> Terminal

2) Enter "sudo nautilus" without the quotation marks.

3) Go to {{path|/boot/grub/}}, backup and then edit {{path|menu.lst}} by 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'''

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

<pre>sudo update-grub</pre>

in the terminal.

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). (Note: I am using KDE. I would think these fixes would work for gnome as well, but someone else would have to test them.)

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

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

=== Wireless activity LED ===

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

== Power consumption ==

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

$ sudo apt-get install powertop
$ sudo powertop

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

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

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

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

Adding the Nvidia card increases the laptops power requirements.

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

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

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

Installing Ubuntu 7.10 (Gutsy Gibbon) on a ThinkPad T61

2007-11-03T22:48:04Z

SteveSims: /* Blank screen fix for intel graphics cards */

==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. 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 video files in Totem, 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 {{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 a movie will span both the laptop screen and second monitor or projector.

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

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

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), 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:====
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 (You should save anything open just to be safe).

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

There have been reports that the microphone may not work, please add your input to the talk page [http://www.thinkwiki.org/wiki/Talk:Installing_Ubuntu_7.10_%28Gutsy_Gibbon%29_on_a_ThinkPad_T61#Microphone] and update this section when a consensus on the problem and solution has been reached.

===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".
# 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:

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

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 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]). To fix this:

1) Go to the in Applications -> Accessories -> Terminal

2) Enter "sudo nautilus" without the quotation marks.

3) Go to {{path|/boot/grub/}}, backup and then edit {{path|menu.lst}} by 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'''

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

<pre>sudo update-grub</pre>

in the terminal.

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). (Note: I am using KDE. I would think these fixes would work for gnome as well, but someone else would have to test them.)

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

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

=== Wireless activity LED ===

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

== Power consumption ==

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

$ sudo apt-get install powertop
$ sudo powertop

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

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

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

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

Adding the Nvidia card increases the laptops power requirements.

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

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

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

Installing Ubuntu 7.10 (Gutsy Gibbon) on a ThinkPad T61

2007-11-03T22:45:52Z

SteveSims: /* Blank screen fix for intel graphics cards */ made even easier to do (by using the GUI to edit menu.lst)

==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. 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 video files in Totem, 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 {{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 a movie will span both the laptop screen and second monitor or projector.

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

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

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), 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:====
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 (You should save anything open just to be safe).

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

There have been reports that the microphone may not work, please add your input to the talk page [http://www.thinkwiki.org/wiki/Talk:Installing_Ubuntu_7.10_%28Gutsy_Gibbon%29_on_a_ThinkPad_T61#Microphone] and update this section when a consensus on the problem and solution has been reached.

===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".
# 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:

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

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 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]). To fix this:

1) Go to the in Applications -> Accessories -> Terminal

2) Type "sudo nautilus" without the quotation marks.

3) Find /boot/grub/, and backup and edit {{path|menu.lst}} by 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'''

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

<pre>sudo update-grub</pre>

in the terminal.

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). (Note: I am using KDE. I would think these fixes would work for gnome as well, but someone else would have to test them.)

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

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

=== Wireless activity LED ===

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

== Power consumption ==

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

$ sudo apt-get install powertop
$ sudo powertop

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

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

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

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

Adding the Nvidia card increases the laptops power requirements.

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

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

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

Installing Ubuntu 7.10 (Gutsy Gibbon) on a ThinkPad T61

2007-10-31T06:55:15Z

SteveSims: /* Accelerated Video and Desktop Effects */

==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. 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. However, Rhythembox Music Player and VLC Media Player now handle '''audio''' fine on Intel-graphics T61's with accelerated graphics.''

'''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 a movie will span both the laptop screen and second monitor or projector.

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

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

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

How? the brightness buttons aren't working for me in the virtual terminal either --Pascal 27-10-2007

This should be asked in the talk page, but are you hitting Ctrl-Alt-F1 and are you running the nv driver or nvidia driver? --[[User:Darrena|Darrena]] 17:46, 27 October 2007 (UTC)

Try this. It worked before backlight controls worked in the beta version of Ubuntu 7.10 for Intel graphics.

Install xbacklight:
<pre>sudo apt-get install xbacklight</pre>
Then, set your backlight intensity:
<pre>xbacklight set Y</pre>

Y is a percentage of your backlight's intensity, without the % sign. You can do this from a virtual terminal via Application -> Accessories --> Terminal.

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

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

There have been reports that the microphone may not work, please add your input to the talk page [http://www.thinkwiki.org/wiki/Talk:Installing_Ubuntu_7.10_%28Gutsy_Gibbon%29_on_a_ThinkPad_T61#Microphone] and update this section when a consensus on the problem and solution has been reached.

===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".
# 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:

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

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 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). (Note: I am using KDE. I would think these fixes would work for gnome as well, but someone else would have to test them.)

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

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

=== Wireless USB/UWB ===

The two USB ports on the left side of the computer fail to connect storage devices during a session but will load them at boot up.

The one USB port on the right side consistently works.

I do not have this problem and nobody else has reported it that I have seen, you may have a bad set of ports. Maybe we should move this to the talk page to attempt to troubleshoot it? --[[User:Darrena|Darrena]] 02:49, 26 October 2007 (UTC)

I also have this problem. It seems to be the bug mentioned in the section below. This is not even about wireless USB --Pascal, 27-10-2007

Good point, if there are no objections I will remove this section and note this problem in the section below. --[[User:Darrena|Darrena]] 17:50, 27 October 2007 (UTC)

I do not have this problem. Plus, T61's have one USB on the left and two on the right (at least my 15.4" ThinkPad does). Are you sure your ThinkPad is a T61? [[User:SteveSims|SteveSims]] 22:53, 28 October 2007 (UTC)

I had the same problem, but it disappeared after one reboot with an USB device attached to the left side USB slots. (Thinkpad T61 7663-13G) --[[User:Think felix|Think felix]] 09:11, 29 October 2007 (UTC)

=== Interrupt problem ===
* 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.

=== Volume keys ===

* mute is inconsistent
1. sometimes fails to work at all
2. sometimes works but doesn't display the volume box on the screen
* unmute does not work --to unmute one must use the volume up or down buttons
* Control mic instead of speakers by default
* https://bugs.launchpad.net/ubuntu/+bug/136287

=== Wireless activity LED ===

does not turn on at all

doesn't seem to flicker properly.

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

How to change the BIOS bootsplash screen

2007-10-28T23:00:35Z

SteveSims: /* Method 1: Using a Non-Diskette-File and cabextract */ 7luj09uc.iso

{| width="100%"
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__
|style="vertical-align:top" |
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#efefef; align:right;">
This page describes how to replace the standard IBM BIOS Bootsplash (The one with the ThinkPad- and Pentium M-Logo), without access to Microsoft Windows or a floppy drive.

Windows users who want to have a custom splash image when they start up should try [[How to change the BIOS bootsplash screen (under Windows) | this guide]] instead.
</div>
|}
== Getting the Files ==
You'll need the bios upgrade file from the IBM website.

=== Method 1: Using a Non-Diskette-File and cabextract ===

For ThinkPads {{R50}}, {{R50p}}, {{R51}} (1829, 1830, 1831, 1836), {{R52}}, {{T40}}, {{T40p}}, {{T41}}, {{T41p}}, {{T42}}, {{T42p}}, {{T43}}, {{T43p}} this file is suitable:
* [ftp://ftp.software.ibm.com/pc/pccbbs/mobiles/1ruj28us.exe 1ruj28us.exe]
* [ftp://ftp.software.ibm.com/pc/pccbbs/mobiles/1ruj29us.exe 1ruj29us.exe]
* [ftp://ftp.software.ibm.com/pc/pccbbs/mobiles/1ruj30us.exe 1ruj30us.exe]
* [ftp://ftp.software.ibm.com/pc/pccbbs/mobiles/1ruj33us.exe 1ruj33us.exe]
There may be a more recent file on the IBM website.
* [ftp://ftp.software.ibm.com/pc/pccbbs/mobiles/1ruj35us.exe 1ruj35us.exe]

For Thinkpads {{T61}}, {{R61}} 14.1 inch screen
* [ftp://ftp.software.ibm.com/pc/pccbbs/mobiles/7luj05us.exe 7luj05us.exe]

or

* [[http://www-307.ibm.com/pc/support/site.wss/license.do?filename=mobiles/7luj09uc.iso 7luj09uc.iso]]

For Thinkpad {{R60e}} the bios is available as an iso which can be edited before burning
See the readme file in the ISO for details of how to change the bootsplash.
* [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-64394 7euj18us.iso]

You need the cabextract tool to extract files from the exe:
:{{cmdroot|apt-get install cabextract}}

Do this to get the ibm file and extract the disk image from it:
:{{cmdroot|cd /tmp}}
:{{cmdroot|wget ftp://ftp.software.ibm.com/pc/pccbbs/mobiles/1ruj35us.exe}}
:{{cmdroot|cabextract -F "*.IMG" 1ruj35us.exe}}
:{{cmdroot|mv 1RUJ35US.IMG floppy.bin}}

=== Method 2: Using a Diskette-File and dosemu ===
Another option is to use the "Diskette BIOS file". 
For ThinkPads {{R50}}, {{R50p}}, {{R51}} (1829, 1830, 1831, 1836), {{R52}}, {{T40}}, {{T40p}}, {{T41}}, {{T41p}}, {{T42}}, {{T42p}}, {{T43}}, {{T43p}} this file is suitable:
* [ftp://ftp.software.ibm.com/pc/pccbbs/mobiles/1ruj28ud.exe 1ruj28ud.exe]
* [ftp://ftp.software.ibm.com/pc/pccbbs/mobiles/1ruj29ud.exe 1ruj29ud.exe]
* [ftp://ftp.software.ibm.com/pc/pccbbs/mobiles/1ruj30ud.exe 1ruj30ud.exe] Released 2005-05-26

For Thinkpads {{T61}}, {{R61}} 14.1 inch screens
* [ftp://ftp.software.ibm.com/pc/pccbbs/mobiles/7luj05us.exe 7luj05ud.exe] Released 2007-07-16 '''NEW!'''

The file is an OS/2 executables and don't run with wine, so you need to install dosemu to run it and create the image. 
:{{cmdroot|apt-get install dosemu dosemu-freedos}}
(for non-debian-users: Get dosemu and freedos somewhere and make it work somehow).

With dosemu, you can run this executable, but this program unfortunately
needs a floppy drive to write to. So use the loopback device, to create a virtual floppy.
:{{cmdroot|1=dd if=/dev/zero of=/tmp/floppy.bin bs=1024 count=1440}}
:{{cmdroot|losetup /dev/loop0 /tmp/floppy.bin}}
Put this block device ({{path|/dev/loop0}}) into the dosemu configuration as the floppy disk device.
Now you can run the extractor executable, which makes {{path|/tmp/floppy.bin}} the desired floppy image .
:{{cmdroot|dosemu 1ruj27ud.exe}}
:{{cmdroot|losetup -d /dev/loop0}}

For 2.6.12+ if you have dosemu error:
:{{cmdroot|echo 0 > /proc/sys/kernel/randomize_va_space}}

== Adding the custom image ==
Mount your floppy.bin as a loopback device.
:{{cmdroot|mkdir /tmp/mnt}}
:{{cmdroot|1=mount -o loop,umask=000 /tmp/floppy.bin /tmp/mnt}}
Create a 16 color 640x480 BMP (4 Bit/pixel VGA palette) (for example with Gimp) and save it to {{path|/tmp/mnt/logo.bmp}}.

When creating your image, keep in mind that on the T43p (and others??), regardless of your custom bootsplash screen there will be a superimposed black "Centrino" logo (~100x100 pixels) on the upper right of your display, so you might want to keep that area clear. You might also want to reserve the bottom 150 pixels for the "boot options" / "Entering BIOS setup" message(s) too, which will also be displayed.

Now prepare the image with <tt>prepare.exe</tt> using wine: (This does not work with dosemu!)
:{{cmdroot|wine prepare.exe logo.scr}}

The image must compress to <10k. If you receive an error, you can try reducing the number of colors in your image palette (step down to an 12 or 8 color palette for a very significant reduction in image size.) When successful, there should be a new {{path|logo.mod}} and your {{path|logo.bmp}}. If so, you are set, don't forget to unmount your loopback device:
:{{cmdroot|umount /tmp/mnt}}

== Fake a floppy ==
Now you need to put the image on a floppy and boot from it. Since recent ThinkPads don't have a
floppy drive, we can use a CD-R (or a CD-RW, actually, for the cheap ones, like me) and burn it with the following command:
:{{cmdroot|1=mkisofs -b floppy.bin floppy.bin <nowiki>|</nowiki> cdrecord dev=<device> - }}
(<tt><device></tt> being your cd writer device)

== The exciting part ==
After this worked, reboot your ThinkPad from the cdrom by pressing F12 while booting
and wait for the IBM tool to start.
Be sure to have your ThinkPad on AC power and say ''Yes'' to the questions the BIOS Upgrade Tool asks.
It will then flash the BIOS, which will take about a minute.

Suddenly the laptop turns itself off with two beeps.
When booting, you'll have your bootsplash picture.

Unfortunately, you won't see it really long, but it's better
than the standard one, so it was worth the action.

Have fun!

BTW next time you have to flash the BIOS the IBM BIOS updater will detect a custom boot splash and ask you if you want to preserve it or restore the original.

== Share your custom bootsplash image ==
If you've created your own bootsplash image and want to share it with other you can post it here.

* Schnappi bootsplash: Bow to the power of [http://folk.uio.no/igorr/t43/final.bmp Schnappi]. The BMP image compressed to about 6KB. Schni, schna, schnappi!
* IBM Tux: An image of [http://users.tkk.fi/~jpaalija/stuff/filestorage/ibm-tux.bmp Tux with the IBM logo] written on its tummy.
* [[Media:Eris.png|Eris]], the goddess of discordia. To use it as bios bootsplash convert it to bmp with just a few (<8) colors (thinkwiki does not allow bmp uploads).
* [[Media:simple_tux.png|Simple Tux]] - Just convert it to bmp.

Installing Ubuntu 7.10 (Gutsy Gibbon) on a ThinkPad T61

2007-10-28T22:57:42Z

SteveSims: /* Nvidia Quadro N140 and 570M: */

==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. 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 {{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 a movie will span both the laptop screen and second monitor or projector.

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

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

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

How? the brightness buttons aren't working for me in the virtual terminal either --Pascal 27-10-2007

This should be asked in the talk page, but are you hitting Ctrl-Alt-F1 and are you running the nv driver or nvidia driver? --[[User:Darrena|Darrena]] 17:46, 27 October 2007 (UTC)

Try this. It worked before backlight controls worked in the beta version of Ubuntu 7.10 for Intel graphics.

Install xbacklight:
<pre>sudo apt-get install xbacklight</pre>
Then, set your backlight intensity:
<pre>xbacklight set Y</pre>

Y is a percentage of your backlight's intensity, without the % sign. You can do this from a virtual terminal via Application -> Accessories --> Terminal.

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

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

There have been reports that the microphone may not work, please add your input to the talk page [http://www.thinkwiki.org/wiki/Talk:Installing_Ubuntu_7.10_%28Gutsy_Gibbon%29_on_a_ThinkPad_T61#Microphone] and update this section when a consensus on the problem and solution has been reached.

===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".
# 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:

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

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 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). (Note: I am using KDE. I would think these fixes would work for gnome as well, but someone else would have to test them.)

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

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

=== Wireless USB/UWB ===

The two USB ports on the left side of the computer fail to connect storage devices during a session but will load them at boot up.

The one USB port on the right side consistently works.

I do not have this problem and nobody else has reported it that I have seen, you may have a bad set of ports. Maybe we should move this to the talk page to attempt to troubleshoot it? --[[User:Darrena|Darrena]] 02:49, 26 October 2007 (UTC)

I also have this problem. It seems to be the bug mentioned in the section below. This is not even about wireless USB --Pascal, 27-10-2007

Good point, if there are no objections I will remove this section and note this problem in the section below. --[[User:Darrena|Darrena]] 17:50, 27 October 2007 (UTC)

I do not have this problem. Plus, T61's have one USB on the left and two on the right (at least my 15.4" ThinkPad does). Are you sure your ThinkPad is a T61? [[User:SteveSims|SteveSims]] 22:53, 28 October 2007 (UTC)

=== Interrupt problem ===
* 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.

=== Volume keys ===

* mute is inconsistent
1. sometimes fails to work at all
2. sometimes works but doesn't display the volume box on the screen
* unmute does not work --to unmute one must use the volume up or down buttons
* Control mic instead of speakers by default
* https://bugs.launchpad.net/ubuntu/+bug/136287

=== Wireless activity LED ===

does not turn on at all

doesn't seem to flicker properly.

== Power consumption ==

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

$ sudo apt-get install powertop
$ sudo powertop

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

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

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

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

Adding the Nvidia card increases the laptops power requirements.

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

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

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

Installing Ubuntu 7.10 (Gutsy Gibbon) on a ThinkPad T61

2007-10-28T22:53:12Z

SteveSims: /* Wireless USB/UWB */

==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. 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 {{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 a movie will span both the laptop screen and second monitor or projector.

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

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

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

How? the brightness buttons aren't working for me in the virtual terminal either --Pascal 27-10-2007

This should be asked in the talk page, but are you hitting Ctrl-Alt-F1 and are you running the nv driver or nvidia driver? --[[User:Darrena|Darrena]] 17:46, 27 October 2007 (UTC)

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

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

There have been reports that the microphone may not work, please add your input to the talk page [http://www.thinkwiki.org/wiki/Talk:Installing_Ubuntu_7.10_%28Gutsy_Gibbon%29_on_a_ThinkPad_T61#Microphone] and update this section when a consensus on the problem and solution has been reached.

===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".
# 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:

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

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 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). (Note: I am using KDE. I would think these fixes would work for gnome as well, but someone else would have to test them.)

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

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

=== Wireless USB/UWB ===

The two USB ports on the left side of the computer fail to connect storage devices during a session but will load them at boot up.

The one USB port on the right side consistently works.

I do not have this problem and nobody else has reported it that I have seen, you may have a bad set of ports. Maybe we should move this to the talk page to attempt to troubleshoot it? --[[User:Darrena|Darrena]] 02:49, 26 October 2007 (UTC)

I also have this problem. It seems to be the bug mentioned in the section below. This is not even about wireless USB --Pascal, 27-10-2007

Good point, if there are no objections I will remove this section and note this problem in the section below. --[[User:Darrena|Darrena]] 17:50, 27 October 2007 (UTC)

I do not have this problem. Plus, T61's have one USB on the left and two on the right (at least my 15.4" ThinkPad does). Are you sure your ThinkPad is a T61? [[User:SteveSims|SteveSims]] 22:53, 28 October 2007 (UTC)

=== Interrupt problem ===
* 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.

=== Volume keys ===

* mute is inconsistent
1. sometimes fails to work at all
2. sometimes works but doesn't display the volume box on the screen
* unmute does not work --to unmute one must use the volume up or down buttons
* Control mic instead of speakers by default
* https://bugs.launchpad.net/ubuntu/+bug/136287

=== Wireless activity LED ===

does not turn on at all

doesn't seem to flicker properly.

== 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-19T23:57:02Z

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

==Microphone==

This discussion was going on in the wiki and seems a bit confusing. If possible I think we should get a consensus on the problem (if it still exists as of the final release) and solutions.

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

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

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

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

For those that find the above instructions vague:

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

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

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

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

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

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

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

==Twinview?==

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

Has anyone found a fix for this?
Does the Ubuntu wiki <https://help.ubuntu.com/community/NvidiaTVOut> work?
What adjustments are needed for Gutsy and NVIDIA Quadro NVS 140M

Is it possible to do set up Twinview with movies that don't span screens in the Applications->System Tools->Nvidia Settings?

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

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

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

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

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

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

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

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

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

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

==Volume/Sound Buttons==

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

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

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

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

[Data_4Conditions]
Comment=
ConditionsCount=0

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

[Data_4_1Actions]
ActionsCount=1

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

[Data_4_1Conditions]
Comment=
ConditionsCount=0

[Data_4_1Triggers]
Comment=Simple_action
TriggersCount=1

[Data_4_1Triggers0]
Key=XF86AudioRaiseVolume
Type=SHORTCUT

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

[Data_4_2Actions]
ActionsCount=1

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

[Data_4_2Conditions]
Comment=
ConditionsCount=0

[Data_4_2Triggers]
Comment=Simple_action
TriggersCount=1

[Data_4_2Triggers0]
Key=XF86AudioLowerVolume
Type=SHORTCUT

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

==Brightness buttons==

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

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

==Compiling existing information==

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

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

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

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

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

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

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

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

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

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

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

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

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

Removed the following packages:
totem-gstreamer

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

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

What to choose? Why, why not?

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

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

== Black screen at boot ==

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

TURNS OUT I JUST NEED PATIENCE... sorry

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

== Power Consumption ==

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

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

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

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

<pre>Cannot install 'kolourpaint'

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

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

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

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

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

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

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

2007-10-19T23:53:59Z

SteveSims:

==Microphone==

This discussion was going on in the wiki and seems a bit confusing. If possible I think we should get a consensus on the problem (if it still exists as of the final release) and solutions.

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

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

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

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

For those that find the above instructions vague:

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

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

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

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

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

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

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

==Twinview?==

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

Has anyone found a fix for this?
Does the Ubuntu wiki <https://help.ubuntu.com/community/NvidiaTVOut> work?
What adjustments are needed for Gutsy and NVIDIA Quadro NVS 140M

Is it possible to do set up Twinview with movies that don't span screens in the Applications->System Tools->Nvidia Settings?

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

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

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

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

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

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

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

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

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

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

==Volume/Sound Buttons==

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

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

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

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

[Data_4Conditions]
Comment=
ConditionsCount=0

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

[Data_4_1Actions]
ActionsCount=1

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

[Data_4_1Conditions]
Comment=
ConditionsCount=0

[Data_4_1Triggers]
Comment=Simple_action
TriggersCount=1

[Data_4_1Triggers0]
Key=XF86AudioRaiseVolume
Type=SHORTCUT

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

[Data_4_2Actions]
ActionsCount=1

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

[Data_4_2Conditions]
Comment=
ConditionsCount=0

[Data_4_2Triggers]
Comment=Simple_action
TriggersCount=1

[Data_4_2Triggers0]
Key=XF86AudioLowerVolume
Type=SHORTCUT

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

==Brightness buttons==

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

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

==Compiling existing information==

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

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

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

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

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

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

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

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

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

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

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

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

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

Removed the following packages:
totem-gstreamer

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

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

What to choose? Why, why not?

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

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

== Black screen at boot ==

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

TURNS OUT I JUST NEED PATIENCE... sorry

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

== Power Consumption ==

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

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

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

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

<pre>Cannot install 'kolourpaint'

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

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

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

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

I just ran sudo apt-get update and I still can't install these things. [[User:SteveSims|SteveSims]] 23:53, 19 October 2007 (UTC)

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

2007-10-19T23:28:46Z

SteveSims: /* Most programs won't install in the 10-18 install of AMD64 version */

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

2007-10-19T23:28:24Z

SteveSims: /* Update 2007-10-11 works fine */

==Microphone==

This discussion was going on in the wiki and seems a bit confusing. If possible I think we should get a consensus on the problem (if it still exists as of the final release) and solutions.

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

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

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

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

For those that find the above instructions vague:

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

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

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

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

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

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

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

==Twinview?==

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

Has anyone found a fix for this?
Does the Ubuntu wiki <https://help.ubuntu.com/community/NvidiaTVOut> work?
What adjustments are needed for Gutsy and NVIDIA Quadro NVS 140M

Is it possible to do set up Twinview with movies that don't span screens in the Applications->System Tools->Nvidia Settings?

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

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

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

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

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

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

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

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

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

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

==Volume/Sound Buttons==

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

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

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

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

[Data_4Conditions]
Comment=
ConditionsCount=0

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

[Data_4_1Actions]
ActionsCount=1

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

[Data_4_1Conditions]
Comment=
ConditionsCount=0

[Data_4_1Triggers]
Comment=Simple_action
TriggersCount=1

[Data_4_1Triggers0]
Key=XF86AudioRaiseVolume
Type=SHORTCUT

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

[Data_4_2Actions]
ActionsCount=1

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

[Data_4_2Conditions]
Comment=
ConditionsCount=0

[Data_4_2Triggers]
Comment=Simple_action
TriggersCount=1

[Data_4_2Triggers0]
Key=XF86AudioLowerVolume
Type=SHORTCUT

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

==Brightness buttons==

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

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

==Compiling existing information==

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

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

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

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

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

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

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

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

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

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

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

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

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

Removed the following packages:
totem-gstreamer

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

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

What to choose? Why, why not?

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

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

== Black screen at boot ==

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

TURNS OUT I JUST NEED PATIENCE... sorry

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

== Power Consumption ==

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

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

== Most programs won't install in the 10-18 install of AMD64 version ==

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

<pre>Cannot install 'kolourpaint'

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

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

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

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

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

2007-10-19T23:28:03Z

SteveSims: /* Most programs won't install in the 10-18 install of AMD64 version */

==Microphone==

This discussion was going on in the wiki and seems a bit confusing. If possible I think we should get a consensus on the problem (if it still exists as of the final release) and solutions.

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

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

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

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

For those that find the above instructions vague:

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

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

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

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

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

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

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

==Twinview?==

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

Has anyone found a fix for this?
Does the Ubuntu wiki <https://help.ubuntu.com/community/NvidiaTVOut> work?
What adjustments are needed for Gutsy and NVIDIA Quadro NVS 140M

Is it possible to do set up Twinview with movies that don't span screens in the Applications->System Tools->Nvidia Settings?

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

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

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

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

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

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

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

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

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

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

==Volume/Sound Buttons==

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

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

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

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

[Data_4Conditions]
Comment=
ConditionsCount=0

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

[Data_4_1Actions]
ActionsCount=1

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

[Data_4_1Conditions]
Comment=
ConditionsCount=0

[Data_4_1Triggers]
Comment=Simple_action
TriggersCount=1

[Data_4_1Triggers0]
Key=XF86AudioRaiseVolume
Type=SHORTCUT

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

[Data_4_2Actions]
ActionsCount=1

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

[Data_4_2Conditions]
Comment=
ConditionsCount=0

[Data_4_2Triggers]
Comment=Simple_action
TriggersCount=1

[Data_4_2Triggers0]
Key=XF86AudioLowerVolume
Type=SHORTCUT

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

==Brightness buttons==

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

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

==Compiling existing information==

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

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

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

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

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

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

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

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

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

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

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

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

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

Removed the following packages:
totem-gstreamer

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

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

What to choose? Why, why not?

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

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

== Black screen at boot ==

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

TURNS OUT I JUST NEED PATIENCE... sorry

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

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

== Most programs won't install in the 10-18 install of AMD64 version ==

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

<pre>Cannot install 'kolourpaint'

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

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

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

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

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

2007-10-19T23:25:11Z

SteveSims: conflicting packages

==Microphone==

This discussion was going on in the wiki and seems a bit confusing. If possible I think we should get a consensus on the problem (if it still exists as of the final release) and solutions.

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

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

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

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

For those that find the above instructions vague:

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

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

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

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

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

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

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

==Twinview?==

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

Has anyone found a fix for this?
Does the Ubuntu wiki <https://help.ubuntu.com/community/NvidiaTVOut> work?
What adjustments are needed for Gutsy and NVIDIA Quadro NVS 140M

Is it possible to do set up Twinview with movies that don't span screens in the Applications->System Tools->Nvidia Settings?

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

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

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

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

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

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

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

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

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

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

==Volume/Sound Buttons==

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

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

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

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

[Data_4Conditions]
Comment=
ConditionsCount=0

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

[Data_4_1Actions]
ActionsCount=1

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

[Data_4_1Conditions]
Comment=
ConditionsCount=0

[Data_4_1Triggers]
Comment=Simple_action
TriggersCount=1

[Data_4_1Triggers0]
Key=XF86AudioRaiseVolume
Type=SHORTCUT

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

[Data_4_2Actions]
ActionsCount=1

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

[Data_4_2Conditions]
Comment=
ConditionsCount=0

[Data_4_2Triggers]
Comment=Simple_action
TriggersCount=1

[Data_4_2Triggers0]
Key=XF86AudioLowerVolume
Type=SHORTCUT

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

==Brightness buttons==

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

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

==Compiling existing information==

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

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

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

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

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

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

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

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

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

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

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

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

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

Removed the following packages:
totem-gstreamer

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

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

What to choose? Why, why not?

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

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

== Black screen at boot ==

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

TURNS OUT I JUST NEED PATIENCE... sorry

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

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

== Most programs won't install in the 10-18 install of AMD64 version ==

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

<pre>'''Cannot install 'kolourpaint''''

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

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

Of course, I don't know which packages conflict with it, so I can't use Synaptic to remove the conflicting packages. It did, however, successfully install Sysinfo.

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

2007-10-12T01:39:19Z

SteveSims: /* Update 2007-10-1 works fine */ today's update works too

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

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

2007-10-05T06:16:00Z

SteveSims: /* x86 vs 64bit on core 2 duo */

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

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

==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-1 works fine==
Announcement. [[User:SteveSims|SteveSims]] 05:15, 2 October 2007 (UTC)

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

2007-10-02T05:15:32Z

SteveSims:

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

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

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

== 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-1 works fine==
Announcement. [[User:SteveSims|SteveSims]] 05:15, 2 October 2007 (UTC)

Installing Ubuntu 7.10 (Gutsy Gibbon) on a ThinkPad T61

2007-09-29T02:32:02Z

SteveSims: /* Accelerated Video and Desktop Effects */

==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. Workaround and details
are 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.

As of September 19, compiz is disabled on the Intel 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."

'''If you cannot download it, follow these instructions:'''

To fix edit /usr/bin/compiz and around line 46 comment this portion out:

<nowiki>#T="$T 8086:2982 8086:2992 8086:29a2 8086:2a02 8086:2a12" # intel 965</nowiki>

This edit will need to be reapplied every time compiz is updated. A more permanent method is create a script named compiz.sh with the following in it:
#!/bin/sh
SKIP_CHECKS=yes compiz --replace
Then, make it executable by right-clicking the file, selecting Properties, then selecting Permissions, and checking Allow executing file as program.

Double-click on the script and select Run to start compiz. To have it start at boot, go to System -> Preferences -> Sessions. Click Add, name it something, and for Command, browse to and choose the compiz.sh you created. Click Ok and Close.

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

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

{{NOTE| If you have an issue with Gnome or KDE crashing please see [https://bugs.launchpad.net/bugs/98641 this bug report] or search the ubuntuforums for some solutions}}

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

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

====NVIDIA Quadro 570M:====
Brightness controls do not work out of the box. As in the N140 case, changing brightness in tty1, then switching back does work.

== Audio ==

Audio should work out of the box on a fresh Beta install.

Microphone may not work with applications (like sound recorder and skype) even though sound can be heard through the speakers or headphones.

===Enabling Sound and Fixing the Volume 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.

== Intel Wireless ==

Intel 4965 users will find that they have a very unstable connection with random disconnects within 30 to 60 minutes of association. Once a system update is performed an updated package of wpa_supplicant will resolve this issue.

== Modem ==

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

==Bluetooth==

To enable bluetooth you must have the thinkpad-acpi modules loaded:

{{cmdroot|sudo modprobe thinkpad-acpi}}

Then su to root (sudo doesn't work unless you put these commands into a script) to enable the root account so you can use su see [[http://ubuntuguide.org/wiki/Ubuntu:Feisty#How_to_set.2Fchange.2Fenable_root_user_password| This link]].

{{cmdroot|su }}

To enable bluetooth:

{{cmdroot|echo enable > /proc/acpi/ibm/bluetooth}}

To disable bluetooth:

{{cmdroot|echo disable > /proc/acpi/ibm/bluetooth}}

If you would like to set the keybindings put those commands into scripts such as:

{{cmdroot|sudo gedit /usr/bin/enablebt}}

Enter the following:
echo enable > /proc/acpi/ibm/bluetooth

Close/Save the file and mark it executable
{{cmdroot|sudo chmod +x /usr/bin/enablebt}}

{{cmdroot|sudo gedit /usr/bin/disablebt}}

enter the following

echo disable > /proc/acpi/ibm/bluetooth
Close/Save the file and mark it executable
{{cmdroot|sudo chmod +x /usr/bin/disablebt}}

Modify sudoers to permit those scripts to run as root (Possible security risk)

{{cmdroot|sudo visudo}}

Enter the following under the section "# User privilege specification" replacing enter_your_username_here with your username

enter_your_username_here ALL= NOPASSWD: /usr/bin/enablebt
enter_your_username_here ALL= NOPASSWD: /usr/bin/disablebt

Note: I need to lookup the keycodes to create the shortcuts, so this section is a work in progress.

: A comment - I've tried finding the keycode using all the methods mentioned here [https://wiki.ubuntu.com/LaptopTestingTeam/HotkeyResearch] but the three methods "keyboard shortcuts", "showkey" and "tail" give me nothing. Fn-F8 does produce an acpi event, maybe that would be a good alternative. "ibm/hotkey HKEY 00000080 00001008". On my computer that's already set-up to run the script /etc/acpi/thinkpad-stretchortouchpad.sh. So I might just turn that into a bluetooth trigger instead as I have no interest in turning keys into a number-pad (which I think is what thinkpad-stretchortouchpad.sh tries to do, but fails on my system).

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

Debian packages for i386 can be found at: http://www.rubixlinux.org/debian/thinkfinger/

If you prefer using apt-get, you can add thinkfinger package repository for gutsy 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 a 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

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.

{{HELP|'''Please try to apply a hint which follows this help request and consider if we still need to keep this help request here.'''

Today 14th of September 2007, after Gutsy's updates, Fingerprint is no longer prompted for login and sudo. Looks like a PAM problem. sudo tf-tools --acquire still works
Today 17th of September.. this issue is solved after updates..
19th of September.. this issue is back after updates
}}

{{HINT|ThinkFinger version 0.2.3 and higher requires support of uinput in the kernel. See FAQ section on [https://wiki.ubuntu.com/ThinkFinger Ubuntu ThinkFinger page].
To make it work, load module by
sudo modprobe uinput
and make sure that it will be loaded on boot by adding "uinput" (without quotes) line to /etc/modules. After that sudo should work, as well as gdm and login to console.
}}
28 Sept 2007: the above hint works on my T61. Thanks!

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

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

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.

== 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 cards work. Intel cards work properly after full updates.

'''Network Card'''

'''Firewire'''

'''Wireless switch'''

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

'''Headphones'''

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

== Power consumption ==

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

$ sudo apt-get install powertop
$ sudo powertop

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

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

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

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

Adding the Nvidia card increases the laptops power requirements.

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

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

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

Installing Ubuntu 7.10 (Gutsy Gibbon) on a ThinkPad T61

2007-09-29T02:30:16Z

SteveSims: /* Accelerated Video and Desktop Effects */

==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. Workaround and details
are 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.

As of September 19, compiz is disabled on the Intel video cards. To fix it, download this [http://www.fileden.com/files/2007/9/28/1467484/Enable Compiz on Ubuntu Gutsy Script.zip|this file], unzip it, and follow the instructions in "description and README."

'''If you cannot download it, follow these instructions:'''

To fix edit /usr/bin/compiz and around line 46 comment this portion out:

<nowiki>#T="$T 8086:2982 8086:2992 8086:29a2 8086:2a02 8086:2a12" # intel 965</nowiki>

This edit will need to be reapplied every time compiz is updated. A more permanent method is create a script named compiz.sh with the following in it:
#!/bin/sh
SKIP_CHECKS=yes compiz --replace
Then, make it executable by right-clicking the file, selecting Properties, then selecting Permissions, and checking Allow executing file as program.

Double-click on the script and select Run to start compiz. To have it start at boot, go to System -> Preferences -> Sessions. Click Add, name it something, and for Command, browse to and choose the compiz.sh you created. Click Ok and Close.

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

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

{{NOTE| If you have an issue with Gnome or KDE crashing please see [https://bugs.launchpad.net/bugs/98641 this bug report] or search the ubuntuforums for some solutions}}

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

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

====NVIDIA Quadro 570M:====
Brightness controls do not work out of the box. As in the N140 case, changing brightness in tty1, then switching back does work.

== Audio ==

Audio should work out of the box on a fresh Beta install.

Microphone may not work with applications (like sound recorder and skype) even though sound can be heard through the speakers or headphones.

===Enabling Sound and Fixing the Volume 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.

== Intel Wireless ==

Intel 4965 users will find that they have a very unstable connection with random disconnects within 30 to 60 minutes of association. Once a system update is performed an updated package of wpa_supplicant will resolve this issue.

== Modem ==

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

==Bluetooth==

To enable bluetooth you must have the thinkpad-acpi modules loaded:

{{cmdroot|sudo modprobe thinkpad-acpi}}

Then su to root (sudo doesn't work unless you put these commands into a script) to enable the root account so you can use su see [[http://ubuntuguide.org/wiki/Ubuntu:Feisty#How_to_set.2Fchange.2Fenable_root_user_password| This link]].

{{cmdroot|su }}

To enable bluetooth:

{{cmdroot|echo enable > /proc/acpi/ibm/bluetooth}}

To disable bluetooth:

{{cmdroot|echo disable > /proc/acpi/ibm/bluetooth}}

If you would like to set the keybindings put those commands into scripts such as:

{{cmdroot|sudo gedit /usr/bin/enablebt}}

Enter the following:
echo enable > /proc/acpi/ibm/bluetooth

Close/Save the file and mark it executable
{{cmdroot|sudo chmod +x /usr/bin/enablebt}}

{{cmdroot|sudo gedit /usr/bin/disablebt}}

enter the following

echo disable > /proc/acpi/ibm/bluetooth
Close/Save the file and mark it executable
{{cmdroot|sudo chmod +x /usr/bin/disablebt}}

Modify sudoers to permit those scripts to run as root (Possible security risk)

{{cmdroot|sudo visudo}}

Enter the following under the section "# User privilege specification" replacing enter_your_username_here with your username

enter_your_username_here ALL= NOPASSWD: /usr/bin/enablebt
enter_your_username_here ALL= NOPASSWD: /usr/bin/disablebt

Note: I need to lookup the keycodes to create the shortcuts, so this section is a work in progress.

: A comment - I've tried finding the keycode using all the methods mentioned here [https://wiki.ubuntu.com/LaptopTestingTeam/HotkeyResearch] but the three methods "keyboard shortcuts", "showkey" and "tail" give me nothing. Fn-F8 does produce an acpi event, maybe that would be a good alternative. "ibm/hotkey HKEY 00000080 00001008". On my computer that's already set-up to run the script /etc/acpi/thinkpad-stretchortouchpad.sh. So I might just turn that into a bluetooth trigger instead as I have no interest in turning keys into a number-pad (which I think is what thinkpad-stretchortouchpad.sh tries to do, but fails on my system).

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

Debian packages for i386 can be found at: http://www.rubixlinux.org/debian/thinkfinger/

If you prefer using apt-get, you can add thinkfinger package repository for gutsy 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 a 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

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.

{{HELP|'''Please try to apply a hint which follows this help request and consider if we still need to keep this help request here.'''

Today 14th of September 2007, after Gutsy's updates, Fingerprint is no longer prompted for login and sudo. Looks like a PAM problem. sudo tf-tools --acquire still works
Today 17th of September.. this issue is solved after updates..
19th of September.. this issue is back after updates
}}

{{HINT|ThinkFinger version 0.2.3 and higher requires support of uinput in the kernel. See FAQ section on [https://wiki.ubuntu.com/ThinkFinger Ubuntu ThinkFinger page].
To make it work, load module by
sudo modprobe uinput
and make sure that it will be loaded on boot by adding "uinput" (without quotes) line to /etc/modules. After that sudo should work, as well as gdm and login to console.
}}
28 Sept 2007: the above hint works on my T61. Thanks!

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

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

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.

== 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 cards work. Intel cards work properly after full updates.

'''Network Card'''

'''Firewire'''

'''Wireless switch'''

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

'''Headphones'''

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

== Power consumption ==

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

$ sudo apt-get install powertop
$ sudo powertop

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

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

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

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

Adding the Nvidia card increases the laptops power requirements.

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

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

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

Installing Ubuntu 7.10 (Gutsy Gibbon) on a ThinkPad T61

2007-09-29T02:27:14Z

SteveSims: /* Accelerated Video and Desktop Effects */

==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. Workaround and details
are 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.

As of September 19, compiz is disabled on the Intel video cards. To fix it, download this [http://www.fileden.com/files/2007/9/28/1467484/Enable%20Compiz%20on%20Ubuntu%20Gutsy%20Script.zip|this file], unzip it, and follow the instructions in "description and README."

'''If you cannot download it, follow these instructions:'''

To fix edit /usr/bin/compiz and around line 46 comment this portion out:

<nowiki>#T="$T 8086:2982 8086:2992 8086:29a2 8086:2a02 8086:2a12" # intel 965</nowiki>

This edit will need to be reapplied every time compiz is updated. A more permanent method is create a script named compiz.sh with the following in it:
#!/bin/sh
SKIP_CHECKS=yes compiz --replace
Then, make it executable by right-clicking the file, selecting Properties, then selecting Permissions, and checking Allow executing file as program.

Double-click on the script and select Run to start compiz. To have it start at boot, go to System -> Preferences -> Sessions. Click Add, name it something, and for Command, browse to and choose the compiz.sh you created. Click Ok and Close.

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

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

{{NOTE| If you have an issue with Gnome or KDE crashing please see [https://bugs.launchpad.net/bugs/98641 this bug report] or search the ubuntuforums for some solutions}}

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

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

====NVIDIA Quadro 570M:====
Brightness controls do not work out of the box. As in the N140 case, changing brightness in tty1, then switching back does work.

== Audio ==

Audio should work out of the box on a fresh Beta install.

Microphone may not work with applications (like sound recorder and skype) even though sound can be heard through the speakers or headphones.

===Enabling Sound and Fixing the Volume 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.

== Intel Wireless ==

Intel 4965 users will find that they have a very unstable connection with random disconnects within 30 to 60 minutes of association. Once a system update is performed an updated package of wpa_supplicant will resolve this issue.

== Modem ==

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

==Bluetooth==

To enable bluetooth you must have the thinkpad-acpi modules loaded:

{{cmdroot|sudo modprobe thinkpad-acpi}}

Then su to root (sudo doesn't work unless you put these commands into a script) to enable the root account so you can use su see [[http://ubuntuguide.org/wiki/Ubuntu:Feisty#How_to_set.2Fchange.2Fenable_root_user_password| This link]].

{{cmdroot|su }}

To enable bluetooth:

{{cmdroot|echo enable > /proc/acpi/ibm/bluetooth}}

To disable bluetooth:

{{cmdroot|echo disable > /proc/acpi/ibm/bluetooth}}

If you would like to set the keybindings put those commands into scripts such as:

{{cmdroot|sudo gedit /usr/bin/enablebt}}

Enter the following:
echo enable > /proc/acpi/ibm/bluetooth

Close/Save the file and mark it executable
{{cmdroot|sudo chmod +x /usr/bin/enablebt}}

{{cmdroot|sudo gedit /usr/bin/disablebt}}

enter the following

echo disable > /proc/acpi/ibm/bluetooth
Close/Save the file and mark it executable
{{cmdroot|sudo chmod +x /usr/bin/disablebt}}

Modify sudoers to permit those scripts to run as root (Possible security risk)

{{cmdroot|sudo visudo}}

Enter the following under the section "# User privilege specification" replacing enter_your_username_here with your username

enter_your_username_here ALL= NOPASSWD: /usr/bin/enablebt
enter_your_username_here ALL= NOPASSWD: /usr/bin/disablebt

Note: I need to lookup the keycodes to create the shortcuts, so this section is a work in progress.

: A comment - I've tried finding the keycode using all the methods mentioned here [https://wiki.ubuntu.com/LaptopTestingTeam/HotkeyResearch] but the three methods "keyboard shortcuts", "showkey" and "tail" give me nothing. Fn-F8 does produce an acpi event, maybe that would be a good alternative. "ibm/hotkey HKEY 00000080 00001008". On my computer that's already set-up to run the script /etc/acpi/thinkpad-stretchortouchpad.sh. So I might just turn that into a bluetooth trigger instead as I have no interest in turning keys into a number-pad (which I think is what thinkpad-stretchortouchpad.sh tries to do, but fails on my system).

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

Debian packages for i386 can be found at: http://www.rubixlinux.org/debian/thinkfinger/

If you prefer using apt-get, you can add thinkfinger package repository for gutsy 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 a 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

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.

{{HELP|'''Please try to apply a hint which follows this help request and consider if we still need to keep this help request here.'''

Today 14th of September 2007, after Gutsy's updates, Fingerprint is no longer prompted for login and sudo. Looks like a PAM problem. sudo tf-tools --acquire still works
Today 17th of September.. this issue is solved after updates..
19th of September.. this issue is back after updates
}}

{{HINT|ThinkFinger version 0.2.3 and higher requires support of uinput in the kernel. See FAQ section on [https://wiki.ubuntu.com/ThinkFinger Ubuntu ThinkFinger page].
To make it work, load module by
sudo modprobe uinput
and make sure that it will be loaded on boot by adding "uinput" (without quotes) line to /etc/modules. After that sudo should work, as well as gdm and login to console.
}}
28 Sept 2007: the above hint works on my T61. Thanks!

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

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

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.

== 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 cards work. Intel cards work properly after full updates.

'''Network Card'''

'''Firewire'''

'''Wireless switch'''

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

'''Headphones'''

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

== Power consumption ==

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

$ sudo apt-get install powertop
$ sudo powertop

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

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

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

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

Adding the Nvidia card increases the laptops power requirements.

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

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

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

Installing Ubuntu 7.10 (Gutsy Gibbon) on a ThinkPad T61

2007-09-29T02:26:53Z

SteveSims: /* Accelerated Video and Desktop Effects */

==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. Workaround and details
are 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.

As of September 19, compiz is disabled on the Intel video cards. To fix it, download this [http://www.fileden.com/files/2007/9/28/1467484/Enable%20Compiz%20on%20Ubuntu%20Gutsy%20Script.zip|this file], unzip it, and follow the instructions in "description and README."

'''If you cannot download it, follow these instructions:'''

To fix edit /usr/bin/compiz and around line 46 comment this portion out:

<nowiki>#T="$T 8086:2982 8086:2992 8086:29a2 8086:2a02 8086:2a12" # intel 965</nowiki>

This edit will need to be reapplied every time compiz is updated. A more permanent method is create a script named compiz.sh with the following in it:
#!/bin/sh
SKIP_CHECKS=yes compiz --replace
Then, make it executable by right-clicking the file, selecting Properties, then selecting Permissions, and checking Allow executing file as program.

Double-click on the script and select Run to start compiz. To have it start at boot, go to System -> Preferences -> Sessions. Click Add, name it something, and for Command, browse to and choose the compiz.sh you created. Click Ok and Close.

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

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

{{NOTE| If you have an issue with Gnome or KDE crashing please see [https://bugs.launchpad.net/bugs/98641 this bug report] or search the ubuntuforums for some solutions}}

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

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

====NVIDIA Quadro 570M:====
Brightness controls do not work out of the box. As in the N140 case, changing brightness in tty1, then switching back does work.

== Audio ==

Audio should work out of the box on a fresh Beta install.

Microphone may not work with applications (like sound recorder and skype) even though sound can be heard through the speakers or headphones.

===Enabling Sound and Fixing the Volume 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.

== Intel Wireless ==

Intel 4965 users will find that they have a very unstable connection with random disconnects within 30 to 60 minutes of association. Once a system update is performed an updated package of wpa_supplicant will resolve this issue.

== Modem ==

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

==Bluetooth==

To enable bluetooth you must have the thinkpad-acpi modules loaded:

{{cmdroot|sudo modprobe thinkpad-acpi}}

Then su to root (sudo doesn't work unless you put these commands into a script) to enable the root account so you can use su see [[http://ubuntuguide.org/wiki/Ubuntu:Feisty#How_to_set.2Fchange.2Fenable_root_user_password| This link]].

{{cmdroot|su }}

To enable bluetooth:

{{cmdroot|echo enable > /proc/acpi/ibm/bluetooth}}

To disable bluetooth:

{{cmdroot|echo disable > /proc/acpi/ibm/bluetooth}}

If you would like to set the keybindings put those commands into scripts such as:

{{cmdroot|sudo gedit /usr/bin/enablebt}}

Enter the following:
echo enable > /proc/acpi/ibm/bluetooth

Close/Save the file and mark it executable
{{cmdroot|sudo chmod +x /usr/bin/enablebt}}

{{cmdroot|sudo gedit /usr/bin/disablebt}}

enter the following

echo disable > /proc/acpi/ibm/bluetooth
Close/Save the file and mark it executable
{{cmdroot|sudo chmod +x /usr/bin/disablebt}}

Modify sudoers to permit those scripts to run as root (Possible security risk)

{{cmdroot|sudo visudo}}

Enter the following under the section "# User privilege specification" replacing enter_your_username_here with your username

enter_your_username_here ALL= NOPASSWD: /usr/bin/enablebt
enter_your_username_here ALL= NOPASSWD: /usr/bin/disablebt

Note: I need to lookup the keycodes to create the shortcuts, so this section is a work in progress.

: A comment - I've tried finding the keycode using all the methods mentioned here [https://wiki.ubuntu.com/LaptopTestingTeam/HotkeyResearch] but the three methods "keyboard shortcuts", "showkey" and "tail" give me nothing. Fn-F8 does produce an acpi event, maybe that would be a good alternative. "ibm/hotkey HKEY 00000080 00001008". On my computer that's already set-up to run the script /etc/acpi/thinkpad-stretchortouchpad.sh. So I might just turn that into a bluetooth trigger instead as I have no interest in turning keys into a number-pad (which I think is what thinkpad-stretchortouchpad.sh tries to do, but fails on my system).

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

Debian packages for i386 can be found at: http://www.rubixlinux.org/debian/thinkfinger/

If you prefer using apt-get, you can add thinkfinger package repository for gutsy 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 a 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

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.

{{HELP|'''Please try to apply a hint which follows this help request and consider if we still need to keep this help request here.'''

Today 14th of September 2007, after Gutsy's updates, Fingerprint is no longer prompted for login and sudo. Looks like a PAM problem. sudo tf-tools --acquire still works
Today 17th of September.. this issue is solved after updates..
19th of September.. this issue is back after updates
}}

{{HINT|ThinkFinger version 0.2.3 and higher requires support of uinput in the kernel. See FAQ section on [https://wiki.ubuntu.com/ThinkFinger Ubuntu ThinkFinger page].
To make it work, load module by
sudo modprobe uinput
and make sure that it will be loaded on boot by adding "uinput" (without quotes) line to /etc/modules. After that sudo should work, as well as gdm and login to console.
}}
28 Sept 2007: the above hint works on my T61. Thanks!

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

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

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.

== 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 cards work. Intel cards work properly after full updates.

'''Network Card'''

'''Firewire'''

'''Wireless switch'''

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

'''Headphones'''

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

== Power consumption ==

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

$ sudo apt-get install powertop
$ sudo powertop

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

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

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

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

Adding the Nvidia card increases the laptops power requirements.

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

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

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

Installing Ubuntu 7.10 (Gutsy Gibbon) on a ThinkPad T61

2007-09-29T02:25:59Z

SteveSims: /* Accelerated Video and Desktop Effects */ I uploaded compiz.sh onto a (rather addy) fileserver

==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. Workaround and details
are 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.

Download this [http://www.fileden.com/files/2007/9/28/1467484/Enable%20Compiz%20on%20Ubuntu%20Gutsy%20Script.zip|this file], unzip it, and follow the instructions in "description and README."

'''If you cannot download it, follow these instructions:'''

As of September 19, compiz is disabled on the intel video cards. To fix edit /usr/bin/compiz and around line 46 comment this portion out:

<nowiki>#T="$T 8086:2982 8086:2992 8086:29a2 8086:2a02 8086:2a12" # intel 965</nowiki>

This edit will need to be reapplied every time compiz is updated. A more permanent method is create a script named compiz.sh with the following in it:
#!/bin/sh
SKIP_CHECKS=yes compiz --replace
Then, make it executable by right-clicking the file, selecting Properties, then selecting Permissions, and checking Allow executing file as program.

Double-click on the script and select Run to start compiz. To have it start at boot, go to System -> Preferences -> Sessions. Click Add, name it something, and for Command, browse to and choose the compiz.sh you created. Click Ok and Close.

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

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

{{NOTE| If you have an issue with Gnome or KDE crashing please see [https://bugs.launchpad.net/bugs/98641 this bug report] or search the ubuntuforums for some solutions}}

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

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

====NVIDIA Quadro 570M:====
Brightness controls do not work out of the box. As in the N140 case, changing brightness in tty1, then switching back does work.

== Audio ==

Audio should work out of the box on a fresh Beta install.

Microphone may not work with applications (like sound recorder and skype) even though sound can be heard through the speakers or headphones.

===Enabling Sound and Fixing the Volume 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.

== Intel Wireless ==

Intel 4965 users will find that they have a very unstable connection with random disconnects within 30 to 60 minutes of association. Once a system update is performed an updated package of wpa_supplicant will resolve this issue.

== Modem ==

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

==Bluetooth==

To enable bluetooth you must have the thinkpad-acpi modules loaded:

{{cmdroot|sudo modprobe thinkpad-acpi}}

Then su to root (sudo doesn't work unless you put these commands into a script) to enable the root account so you can use su see [[http://ubuntuguide.org/wiki/Ubuntu:Feisty#How_to_set.2Fchange.2Fenable_root_user_password| This link]].

{{cmdroot|su }}

To enable bluetooth:

{{cmdroot|echo enable > /proc/acpi/ibm/bluetooth}}

To disable bluetooth:

{{cmdroot|echo disable > /proc/acpi/ibm/bluetooth}}

If you would like to set the keybindings put those commands into scripts such as:

{{cmdroot|sudo gedit /usr/bin/enablebt}}

Enter the following:
echo enable > /proc/acpi/ibm/bluetooth

Close/Save the file and mark it executable
{{cmdroot|sudo chmod +x /usr/bin/enablebt}}

{{cmdroot|sudo gedit /usr/bin/disablebt}}

enter the following

echo disable > /proc/acpi/ibm/bluetooth
Close/Save the file and mark it executable
{{cmdroot|sudo chmod +x /usr/bin/disablebt}}

Modify sudoers to permit those scripts to run as root (Possible security risk)

{{cmdroot|sudo visudo}}

Enter the following under the section "# User privilege specification" replacing enter_your_username_here with your username

enter_your_username_here ALL= NOPASSWD: /usr/bin/enablebt
enter_your_username_here ALL= NOPASSWD: /usr/bin/disablebt

Note: I need to lookup the keycodes to create the shortcuts, so this section is a work in progress.

: A comment - I've tried finding the keycode using all the methods mentioned here [https://wiki.ubuntu.com/LaptopTestingTeam/HotkeyResearch] but the three methods "keyboard shortcuts", "showkey" and "tail" give me nothing. Fn-F8 does produce an acpi event, maybe that would be a good alternative. "ibm/hotkey HKEY 00000080 00001008". On my computer that's already set-up to run the script /etc/acpi/thinkpad-stretchortouchpad.sh. So I might just turn that into a bluetooth trigger instead as I have no interest in turning keys into a number-pad (which I think is what thinkpad-stretchortouchpad.sh tries to do, but fails on my system).

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

Debian packages for i386 can be found at: http://www.rubixlinux.org/debian/thinkfinger/

If you prefer using apt-get, you can add thinkfinger package repository for gutsy 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 a 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

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.

{{HELP|'''Please try to apply a hint which follows this help request and consider if we still need to keep this help request here.'''

Today 14th of September 2007, after Gutsy's updates, Fingerprint is no longer prompted for login and sudo. Looks like a PAM problem. sudo tf-tools --acquire still works
Today 17th of September.. this issue is solved after updates..
19th of September.. this issue is back after updates
}}

{{HINT|ThinkFinger version 0.2.3 and higher requires support of uinput in the kernel. See FAQ section on [https://wiki.ubuntu.com/ThinkFinger Ubuntu ThinkFinger page].
To make it work, load module by
sudo modprobe uinput
and make sure that it will be loaded on boot by adding "uinput" (without quotes) line to /etc/modules. After that sudo should work, as well as gdm and login to console.
}}
28 Sept 2007: the above hint works on my T61. Thanks!

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

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

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.

== 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 cards work. Intel cards work properly after full updates.

'''Network Card'''

'''Firewire'''

'''Wireless switch'''

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

'''Headphones'''

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

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

User talk:Hmh

2007-09-28T05:03:59Z

SteveSims:

Sorry about leaving the comment on the wrong page. I'm an experienced Wikipedia editor and should not make that mistake. [[User:SteveSims|SteveSims]] 04:30, 28 September 2007 (UTC)

User talk:Hmh

2007-09-28T04:30:51Z

SteveSims: â†Created page with 'Sorry about that; I probably misidentified it. I'm an experienced Wikipedia editor and should not make that mistake. ~~~~'

Sorry about that; I probably misidentified it. I'm an experienced Wikipedia editor and should not make that mistake. [[User:SteveSims|SteveSims]] 04:30, 28 September 2007 (UTC)

Installing Ubuntu 7.10 (Gutsy Gibbon) on a ThinkPad T61

2007-09-26T01:44:40Z

SteveSims: /* Accelerated Video and Desktop Effects */ grammar

==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. Workaround and details
are 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.

As of September 19, compiz is disabled on the intel video cards. To fix edit /usr/bin/compiz and around line 46 comment this portion out:

<nowiki>#T="$T 8086:2982 8086:2992 8086:29a2 8086:2a02 8086:2a12" # intel 965</nowiki>

This edit will need to be reapplied every time compiz is updated. A more permanent method is create a script named compiz.sh with the following in it:
#!/bin/sh
SKIP_CHECKS=yes compiz --replace
Then, make it executable by right-clicking the file, selecting Properties, then selecting Permissions, and checking Allow executing file as program.

Double-click on the script and select Run to start compiz. To have it start at boot, go to System -> Preferences -> Sessions. Click Add, name it something, and for Command, browse to and choose the compiz.sh you created. Click Ok and Close.

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

Desktop Effects may be unstable with the proprietary driver installed by the Restricted Drivers Manager, installing version 100.14.19 as described below should resolve the problem. If you would rather stay with the version that ships with Ubuntu you can disable compiz by going to System -> Preferences -> Appearance -> Desktop effects and turn desktop effects off.

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

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

{{NOTE| If you have an issue with Gnome or KDE crashing please see [https://bugs.launchpad.net/bugs/98641 this bug report] or search the ubuntuforums for some solutions}}

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

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

====NVIDIA Quadro 570M:====
Brightness controls do not work out of the box. As in the N140 case, changing brightness in tty1, then switching back does work. At present my system does have keybindings for the brightness controls -- I enabled them somehow -- but there are problems with it. At present I have 2 displays running, and the brightness buttons do not work in this configuration. If I disable the 2nd monitor, the brightness buttons work fine. I will document this fully once I sort out the details. [[User:Rybu|Rybu]]

== Audio ==

Audio does not work out of the box, but will work once you apply all the updates.

Microphone may not work with applications (like sound recorder and skype) even though sound can be heard through the speakers or headphones.

===Enabling Sound and Fixing the Volume 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.

NOTE: As of Sep 20, 2007 the latest updates hoses the sound on my T61. FIXED: For some reason you have to physically hit your volume buttons on the laptop up or down to get the sound to run again and not on the rollbar or on any other volume control method (i.e. keyboard).

== Intel Wireless ==

Intel 4965 users will find that they have a very unstable connection with random disconnects within 30 to 60 minutes of association. The issue is described in [https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/138873 this] bug report. The problem is with wpa_Supplicant and Kees Cook (An Ubuntu Developer) has posted a fixed version [http://ppa.launchpad.net/keescook/ubuntu/pool/main/w/wpasupplicant/ here]. The fix should be available via a normal update soon.

== Modem ==

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

==Bluetooth==

To enable bluetooth you must have the thinkpad-acpi modules loaded:

{{cmdroot|sudo modprobe thinkpad-acpi}}

Then su to root (sudo doesn't work unless you put these commands into a script) to enable the root account so you can use su see [[http://ubuntuguide.org/wiki/Ubuntu:Feisty#How_to_set.2Fchange.2Fenable_root_user_password| This link]].

{{cmdroot|su }}

To enable bluetooth:

{{cmdroot|echo enable > /proc/acpi/ibm/bluetooth}}

To disable bluetooth:

{{cmdroot|echo disable > /proc/acpi/ibm/bluetooth}}

If you would like to set the keybindings put those commands into scripts such as:

{{cmdroot|sudo gedit /usr/bin/enablebt}}

Enter the following:
echo enable > /proc/acpi/ibm/bluetooth

Close/Save the file and mark it executable
{{cmdroot|sudo chmod +x /usr/bin/enablebt}}

{{cmdroot|sudo gedit /usr/bin/disablebt}}

enter the following

echo disable > /proc/acpi/ibm/bluetooth
Close/Save the file and mark it executable
{{cmdroot|sudo chmod +x /usr/bin/disablebt}}

Modify sudoers to permit those scripts to run as root (Possible security risk)

{{cmdroot|sudo visudo}}

Enter the following under the section "# User privilege specification" replacing enter_your_username_here with your username

enter_your_username_here ALL= NOPASSWD: /usr/bin/enablebt
enter_your_username_here ALL= NOPASSWD: /usr/bin/disablebt

Note: I need to lookup the keycodes to create the shortcuts, so this section is a work in progress.

: A comment - I've tried finding the keycode using all the methods mentioned here [https://wiki.ubuntu.com/LaptopTestingTeam/HotkeyResearch] but the three methods "keyboard shortcuts", "showkey" and "tail" give me nothing. Fn-F8 does produce an acpi event, maybe that would be a good alternative. "ibm/hotkey HKEY 00000080 00001008". On my computer that's already set-up to run the script /etc/acpi/thinkpad-stretchortouchpad.sh. So I might just turn that into a bluetooth trigger instead as I have no interest in turning keys into a number-pad (which I think is what thinkpad-stretchortouchpad.sh tries to do, but fails on my system).

== Fingerprint Reader ==

The reader works with ThinkFinger. General instructions available [http://www.thinkwiki.org/wiki/Integrated_Fingerprint_Reader here].

Debian packages for i386 can be found at: http://www.rubixlinux.org/debian/thinkfinger/

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

auth sufficient pam_thinkfinger.so
auth required pam_unix.so try_first_pass

Note: Instructions in French available at http://doc.ubuntu-fr.org/materiel/thinkfinger

* 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.
{{HELP|Today 14th of September 2007, after Gutsy's updates, Fingerprint is no longer prompted for login and sudo. Looks like a PAM problem. sudo tf-tools --acquire still works
Today 17th of September.. this issue is solved after updates..
19th of September.. this issue is back after updates
}}

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

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

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.

=== Intel 3495ABG Wireless ===

Works fine out of the box.e, the wireless card won't come back up. When the [[http://people.freedesktop.org/~hughsient/quirk/quirk-suspend-debug.html quirk checker script]] is run, it says:

CRITICAL ERROR: Use the mac80211 iwl3945 driver instead. ipw3945d is closed source sometimes hangs on resume.

The iwl3945 driver generally only works for about 30 minutes to an hour due to a bug with wpa_supplicant see the section above on the IWL4965 for instructions on fixing this issue

== 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 cards work, see [http://www.thinkwiki.org/index.php?title=Installing_Ubuntu_7.10_%28Gutsy_Gibbon%29_Tribe_5_on_a_ThinkPad_T61&action=edit&section=8 this] section for a note regarding Intel cards

'''Network Card'''

'''Firewire'''

'''Wireless switch'''

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

'''Headphones'''

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

== 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-09-26T00:48:11Z

SteveSims: /* I installed libdvdcss2, but DVD playback still doesn't work */ xine log

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

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

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

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

2007-09-26T00:32:33Z

SteveSims: /* I installed libdvdcss2, but DVD playback still doesn't work */ totem-xine doesn't work

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

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

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

File:Totem-xine no DVD playback.png

2007-09-26T00:31:35Z

SteveSims: ==Information== Talk:Installing_Ubuntu_7.10_%28Gutsy_Gibbon%29_Tribe_5_on_a_ThinkPad_T61#I_installed_libdvdcss2.2C_but_DVD_playback_still_doesn.27t_work

==Information==
[[Talk:Installing_Ubuntu_7.10_%28Gutsy_Gibbon%29_Tribe_5_on_a_ThinkPad_T61#I_installed_libdvdcss2.2C_but_DVD_playback_still_doesn.27t_work]]

User:SteveSims

2007-09-25T22:39:33Z

SteveSims:

[http://en.wikipedia.org/wiki/User:SteveSims My Wikipedia userpage]

Linux will never win if people don't start telling beginners ''how'' they do things, not just ''what'' they did. Fortunately, people are beginning to do this.

File:XBacklight launcher 50.png

2007-09-25T22:30:27Z

SteveSims:

==Information==
[[Installing_Ubuntu_7.10_%28Gutsy_Gibbon%29_Tribe_5_on_a_ThinkPad_T61#Creating_brightness_shortcuts|How to create an XBacklight launcher]] (shortcut) so you don't have to use the terminal.