ThinkWiki - User contributions [en]

Dynticks

2008-04-04T15:29:31Z

Jaskiern: â†Created page with '== External links == * [http://lwn.net/Articles/223185/ Release article]'

== External links ==
* [http://lwn.net/Articles/223185/ Release article]

Installing Gentoo 2007.0 on a ThinkPad R61

2008-04-04T15:28:11Z

Jaskiern: /* Power saving */

== Model ==
Lenovo Thinkpad {{R61}} 7743-Y1B

== General ==
This installation instruction describes the steps after a Gentoo 2007.0 base installation.
Please read the gentoo handbook for installation instructions

====Working:====

* Keyboard, UltraNav input (Touchpad and NavPoint)
* Drives
* X11 with nVidia including acceleration
* Network, wireless network and bluetooth
* Sound
* Suspend to RAM
* Suspend to Disk (Hibernate)
* ThinkLight
* PCMCIA
* ACPI (Battery, CPU Frequency, Fan, Temperature, ...)
* Fingerprint scanner (includes login and screen lock)
* Fn Key combinations
* Hot swapping of optical drive (UltraBay)
* HDD Acceleration Meter (can be used as an input device)
* Harddisk protection (kernel patched with [http://www.fuchsnet.ch/files/hdaps-2.6.24.patch this])

====Not tested:====

* Firewire (should work as it is recognized, no devices for testing)
* Express Card Slot (should work, no devices for testing)
* Docking Station (should work according to several sources, no devices for testing)

== Graphics: NVIDIA Quadro NVS 140M ==

To install and configure the nVidia driver, just emerge nvidia-driver.
Tested with nvidia-driver-100.14.19 up to 169.12, everything works fine, games run smooth.

Framebuffer works fine with vga=869 which will set the resolution to 1440x900.
hwinfo --framebufer displays all supported resolutions.

The brightness can be changed with newer nvidia drivers (>=169.04)
Does not work with older drivers, only known workaround
is to either use vesa / nv driver or to change the
brightness on a vt.

Using 169.12 or newer is recommended, as brightness control works there and some powermizer issues, which caused bad perfomance in applications like compiz-fusion, had been fixed.

== Sound: AD1984 ==
Did not work with older Versions of ALSA driver, works fine with ALSA 1.0.15 and should work
with ALSA 1.0.14 as well. The in-kernel ALSA works since 2.6.23.

The mute button is hardwired and works, the volume up and volume down buttons
work as well but you need to configure them first. You can use xmodmap to bind a key to them and then either bind a amixer command to them, or set them as hotkeys in your mixer application (kmix, gnome-mixer, ...)
Please note that some mixer applications take the wrong mixer (the microphone) as the default, so you have to change the default / primary mixer in order to use things like kmilo.

Note: After muting you have to press a volume up or down button to unmute,
and the mute status is not displayed in any mixer application.

'''Note for Kernel 2.6.24:'''
Due to changes in thinkpad acpi the mute button does not longer work out of the box,
but it does generate a key event. So you have to bind it to a script which mutes
the headphone and speaker via amixer toggle <mixer>.
This is a known problem to the thinkpad-acpi developers and probably will
be resolved in the near future.

I recommend using alsa-drivers 1.0.16, as there is a new master mixer,
which has mute capabilities to mute headphones and speaker.
So you can either bind the key in a mixer application or you only have
to use one amixer command.

== Network: Intel E1000 NIC, IPW4965abgn WNIC, Bluetooth==

The integrated e1000 LAN NIC works out of the box.

For wireless you have to unmask and emerge the iwlwifi package
with the ipw4965 USEFlag enabled.

Don't forget that the interface (wlan0) has to be set as up
(ifconfig wlan0 up) before scanning and associating works.

Bluetooth works out of the box with blueZ.
You can disable / enable bluetooth via proc,
with a script similar to this one:

<bash>
#!/bin/sh
bluetooth=`head -n 1 /proc/acpi/ibm/bluetooth | awk '{print $2}'`
case "$bluetooth" in
disabled)
echo "enable" > /proc/acpi/ibm/bluetooth
;;
enabled)
echo "disable" > /proc/acpi/ibm/bluetooth
;;
esac
exit 0
</bash>

or directly with the proc interface. This script helps you
to bind it to the Fn+F5 key combination.

Note that the hardware killswitch on the front works as well,
but disables both bluetooth and WLAN

If you desperately want the wireless LED to work you can use
[http://bughost.org/bugzilla/attachment.cgi?id=1263 this] patch for a 2.6.24 kernel.
Make sure to enable LED Triggers and LED groups in your kernel configuration,
then there is a new option in the iwlwifi submenu. Works here, however,
it doesn't blink on activity as it would with windows.

== Ports: PCMCIA, USB, IEEE 1394 Firewire ==

PCMCIA port works out of the box, tested with an audigy pcmcia.
I have no express slot cards available for testing.

The left hand usb ports generate an IRQ nobody cared error from time to time,
Try to boot with irqpoll in your kernel line as suggested.

A BIOS Update might help as well, it is recommended to use the
ThinkVantage Software Updater for windows for a BIOS Update.
The error disappeared here and USB works fine.

Firewire is untested but should work, as the port is
recognized and the module loaded.

== Drives ==

The optical drive and hard drive work out of the box,
with AHCI disabled or enabled in the BIOS.

If you run a dualboot system with windows <= 5.1 (XP) you probably want to disable AHCI anyway,
at least until you have installed the ahci driver for Windows.

== Input ==

=== TouchPad ===
Works out of the box here, with scrolling.
Have a look at my Xorg.conf section at the end

Can be disabled via synclient when using the synaptics driver,
a possible solution is this script:

<bash>
#!/bin/sh
touchpad=`synclient -l | grep TouchpadOff | awk '{print $3}'`
case "$touchpad" in
1)
synclient TouchpadOff=0;
echo "Touchpad Enabled" | osd_cat -d 1 -c cyan --font="-*-times-bold-r-*--34-240-*-*-p-*-*-*" -A center -p bottom
;;
0)
synclient TouchpadOff=1;
echo "Touchpad Disabled" | osd_cat -d 1 -c cyan --font="-*-times-bold-r-*--34-240-*-*-p-*-*-*" -A center -p bottom
;;
esac
exit 0
</bash>

which needs xosd to display the current state.
You can make it excecutable and map it to the fn+f8 button.

=== Trackpoint ===
Works out of the box as well, with no scrolling however.
Can be configured via xorg.conf, I prefer using the middle button as mouse3.

=== Keyboard ===
Works out of the box, most of the Fn Keys work.

Hardwired: Mute, Thinklight, Brightness

Generates a keycode and can be configured: Volume Down, Volume Up, Fn+F2, Fn+F3, Fn+F4, Fn+F5, Fn+F7, Fn+F8, Fn+Arrows

Does not generate a key event: Fn+F9, Fn+F12, Fn+Space
Those keys do produce an acpi event, so you can modifiy your
acpi configuration to bind them to commands.

It is also possible to translate the acpi events to keyevents, have a look at the following configuration file:

[[Installing_Gentoo_2007.0_on_a_ThinkPad_R61#default.sh_.28acpid.29|My example default.sh file for the missing keys is here]]
and there is a good, more complete howto
here: [http://gentoo-wiki.com/HARDWARE_Lenovo_Thinkpad_T61#Usage_of_acpid Gentoo Wiki]

Try whether echo "0xffffffff" > /proc/acpi/ibm/hotkey
enables additional fn+fx keys to produce a key event
instead of only an acpi event.
Take a look at the ibm-acpi section as well to do this on module load.

== Suspend ==
Suspend to RAM worked out of the box here, echo 3 > /proc/acpi/sleep
puts the machine in suspend mode, opening it or pressing the power button wakes it up.
Worked with nvidia driver and in X11. All devices came back without problems,
wlan might have disconnected, but by using networkmanager, wicd or a good configuration
it should reconnect after waking up. Works here with wicd.

Suspend to Disk is more complicated.
Emerge a tux on ice kernel and try the configuration file
linked at the end of this page. Disable intel-agp in the kernel.
Make sure to load the nvidia module with NVreg_NvAGP=1 option.

This is my /etc/hibernate/common.conf file.
Note that all options not mentioned here are commented (#)

<pre>

Verbosity 0
LogFile /var/log/hibernate.log
LogVerbosity 3
HibernateVT 11
Distribution gentoo
# XDisplay :0

### clock
SaveClock restore-only

### hardware_tweaks
IbmAcpi yes
FullSpeedCPU yes

### modules
# UnloadBlacklistedModules yes
LoadModules auto

### xhacks
SwitchToTextMode yes
UseDummyXServer yes
# DummyXServerConfig xorg-dummy.conf

</pre>

Note that the extra_pages_allowance might be too low.
In current TuxOnIce versions the option to raise this value
did not work anymore, that's why I put

echo 1000 > /sys/power/tuxonice/extra_pages_allowance

in my local.startup.

You can get the correct value by trying to suspend
without it and reading /var/log/hibernate.log afterwards.

The machine can now be suspended to disk with the hibernate command.

== Integrated Fingerprint Reader ==
Emerge the thinkfinger package, add a user with the tf-tool.
Then you have to edit the /etc/pam.d/system-auth file by adding

auth sufficient pam_thinkfinger.so

between pam.unix and pam.env.

Read the Gentoo-Wiki to use it with xscreensaver,
there is a good solution over [http://gentoo-wiki.com/HOWTO_Thinkfinger there]

Note: kdm has problems with thinkfinger auth and might crash.
There are patches, but I didn't test them yet. gdm works fine here.

== Hard Drive Active Protection ==

The integrated harddrive active protection
acceleration meter can be used as a joystick or
to get information about movements of your thinkpad.

Emerge the hdapsd (which includes a kernel module
you have to load) which will generate a joystick
and an event device.

It can be used for protecting your harddisk as well.
You first need to patch your kernel with [http://www.fuchsnet.ch/files/hdaps-2.6.24.patch this patch] and then rebuild it. Make sure to diable the kernel internal hdaps module, emerge hdapsd and tp_smapi with the hdaps flag enabled, rc-update add hdapsd boot and then reboot.

When shaking your notebook you should receive a message via dmesg that the hdd head has been parked.
You can also use a frontend like khdaps.

Heads will only be parked with this method. However, in some situations and with some disk there will be a full spindown, which should be avoided as this might damage your harddisk when used too much.

== Thinklight ==

The thinklight works out of the box with the
Fn+PgUp key, but it can be controlled as well via the proc interface.

So you can write a nice script, which you can bind to events,
such as incoming emails, to let the light flash.

A possible solution is this small script:

<bash>
#!/bin/sh

if [ -z "$1" ]
then
echo "IBM ThinkLight Control script."
echo "2007 by Christian \"Fuchs\" Loosli."
echo ""
echo "usage: lightctl on | off | toggle | blink"
echo "blink takes two arguments: times and time"
echo "defaults (5 times, 0.5 seconds) are used if not specified"

else
if [ $1 = "on" ]
then
echo on > /proc/acpi/ibm/light
fi
if [ $1 = "off" ]
then
echo off > /proc/acpi/ibm/light
fi

if [ $1 = "toggle" ]
then
status=`cat /proc/acpi/ibm/light | grep status | awk '{print $2}'`

if [ $status = "on" ]
then
echo off > /proc/acpi/ibm/light
else
echo on > /proc/acpi/ibm/light
fi
fi

if [ $1 = "blink" ]
then

times=$2
time=$3

if [ -z "$2" ]
then
times=4
fi

if [ -z "$3" ]
then
time=0.5
fi

for i in `seq 1 $times`;
do
$0 toggle;
sleep $time;
$0 toggle;
sleep $time
done
fi
fi
exit 0

</bash>
which can be called to let the light blink or switch it off or on.
The blink part is nice for setting to events such as incoming
messages or emails.

There is a version slightly modified by a friend of mine
[http://www.fuchsnet.ch/files/thinklight.sh here] which has a lockfile and is slightly optimized.

(note: the thinklight is a LED, so it should not care on
how fast and often you let it blink. But I am not responsible
if this script damages your thinklight. Use at own risk.

== Power saving ==

First of all, turn off all things you are not using,
most of all bluetooth and W-LAN.
You can use the killswitch on the front, it works out of the box.

You can use the application [http://www.lesswatts.org/projects/powertop/ powertop]
by Intel to look for processes which prevent the CPU from longer sleep states.

It also gives you some recommendations on services to turn off. Do _not_ turn off the optical drive polling by HAL.

Dimming the display also saves lots of power.

Since 2.6.24 [[dynticks]] are available for x86_64.

I managed to get powerconsumption down to:

* 20W running normal with compiz, wlan & bluetooth enabled

* 16.7W running a normal windowmanager

* 14.5W with bluetooth and wlan disabled (killswitch)

I had between 195 and 600 wakeups per second.

Also hda-intel and s-ata power consumption was reduced in 2.6.24

You can achieve about 2 - 3 hours of working time
(no compiling or other heavy CPU / GPU usage applications)
with the standard battery like this.

== ibm-acpi ==

I have ibm-acpi configured as a module in my kernel, as I load it with

options thinkpad_acpi hotkey=enable,0xffffffff brightness_enable=1 fan_control=1

to enable brightness controll via /proc/acpi/ibm on newer kernels and fan control.
The hotkey=enable,<mask> option is used instead of writing to /proc/acpi/ibm/hotkey.

The default file permissions in /proc/acpi/ibm/* do not grant write access for users. I created the group "ibm", added my users to it and now I chown root:ibm and chmod 0774 the files in /proc/acpi/ibm/ on startup. If you don't want to do this you might use sudo sh -c "echo "foo" > /proc/acpi/ibm/whatever", but you need to install sudo and modify your sudoers file.

== Configuration Files ==

=== xorg.conf ===
Note that I use the XFont Server, you might have
to change the font path.

You also might want to change the keyboard layout.

'
Note: in this configuration here nvidia wont read out
sane refresh and sync values out of your flat panel.

In this configuration the modes given don't affect
the modes available and you will have all screen resolutions available,
but it might fail on other display devices.

If you get a blank screen or strange refresh values, add # in front of the marked line to disable
this behaviour, so the nvidia driver will still read out sane resolutions.

<pre>

Section "ServerLayout"
Identifier "single head configuration"
Screen 0 "Screen0" 0 0
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "Mouse0" "CorePointer"
inputDevice "Touchpad" "SendCoreEvents"
EndSection

Section "Files"
FontPath "unix/:-1"
EndSection

Section "Module"
Load "dbe"
Load "extmod"
Load "glx"
Load "freetype"
Load "type1"
EndSection

Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
Option "XkbModel" "pc102"
Option "XkbLayout" "ch"
EndSection

## The following settings can be changed on the fly
## by using synclient. Note that shm has to be enabled for this.
## All options are documented in the synaptics driver documentation.

Section "InputDevice"
Identifier "Touchpad"
Driver "synaptics"
Option "Protocol" "auto-dev"
Option "Device" "/dev/input/mouse0"
Option "Emulate3Buttons" "no"
Option "ZAxisMapping" "4 5"
Option "LeftEdge" "1700"
Option "RightEdge" "5300"
Option "TopEdge" "1700"
Option "BottomEdge" "4200"
Option "FingerLow" "25"
Option "FingerHigh" "30"
Option "MaxTapTime" "180"
Option "MaxTapMove" "220"
Option "VertScrollDelta" "100"
Option "MinSpeed" "0.02"
Option "MaxSpeed" "0.28"
Option "AccelFactor" "0.0010"
Option "SHMConfig" "on"
Option "UseSHM" "true"
EndSection

Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "ExplorerPS/2"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "6 7"
Option "buttons" "7"
Option "Emulate3Buttons" "yes"
EndSection

Section "Monitor"
Identifier "Monitor0"
VendorName "Lenovo"
ModelName "Lenovo R61 Flat Panel 1400x950"
Option "DPMS"
HorizSync 28.0 - 61.0
VertRefresh 43.0 - 62.0
EndSection

## Some of the following options are set by default in newer nvidia drivers
## are are kept for compatibility reasons. Please read the Appendix in the
## README of your current nvidia driver for further information

Section "Device"
Identifier "Videocard0"
Driver "nvidia"
VendorName "NVIDIA"
BoardName "NVIDIA Quadro NVS 140M"
Option "Coolbits" "1"
Option "AllowGLXWithComposite" "true"
Option "RenderAccel" "true"
Option "UseEvents" "false"
Option "TripleBuffer" "1"
Option "DamageEvents" "1"
Option "BackingStore" "1"
Option "RandRRotation" "true"
Option "NvAGP" "1"

## The following option enables using frequencies not specified in the EDID.
## In this case several additional screen resolutions will be possible.
## Make sure that HorizSync and VertRefresh fit to your monitor,
## As nvidia wont read out allowed values anymore

Option "UseEdidFreqs" "false"

EndSection

Section "Screen"
Identifier "Screen0"
Device "Videocard0"
Monitor "Monitor0"
DefaultDepth 24
Option "AddARGBGLXVisuals" "true"
Option "UseCompositeWrapper" "true"
SubSection "Display"
Viewport 0 0
Depth 24
Modes "1440x900" "1024x768" "800x600"
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 16
Modes "1440x900" "1024x768" "800x600"
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 8
Modes "1440x900" "1024x768" "800x600"
EndSubSection
EndSection

Section "Extensions"
Option "Composite" "Enable"
EndSection

Section "DRI"
Group 0
Mode 0666
EndSection

</pre>

=== xmodmap ===

Note: you have to xmodmap /path/to/file
this file in your autostart. You might have different keycodes, use the application xev to display them.
It is highly recommended to use the XF86foobar buttons, as some applications will be preconfigured to them.
If you want to map them by yourself use Fxx, while xx > 12.

<pre>

! additional Arrow keys

keycode 233 = XF86Forward
keycode 234 = XF86Back

! Fn+arrow keys

keycode 144 = XF86AudioPrev
keycode 162 = XF86AudioPlay
keycode 153 = XF86AudioNext
keycode 164 = XF86AudioStop

! Fn+Fx keys F2, F3, F4, F5, F7, F8, F9, F12 in this order

keycode 146 = XF86ScreenSaver
keycode 241 = XF86Display
keycode 223 = XF86Sleep
keycode 243 = XF86Send
keycode 214 = XF86Video
keycode 196 = XF86iTouch
keycode 197 = XF86Eject
keycode 165 = XF86Standby

! Space bar

keycode 148 = XF86ZoomIn

! volume control (mute is hardwired)

keycode 174 = XF86AudioLowerVolume
keycode 176 = XF86AudioRaiseVolume

</pre>

=== default.sh (acpid) ===

This is my slightly modified default.sh file to handle ibm hotbutton events.
Of course you can add the other buttons as well, however, as they produce key events there are easier ways for configuring the actions. However, an acpi solution is window manager / X independent.

You can read out the key events, as they might differ on your model,
with the acpi_listen application.

<bash>
#!/bin/sh
# /etc/acpi/default.sh

set $*

group=${1%%/*}
action=${1#*/}
device=$2
id=$3
value=$4

if [ "$group" = "ibm" ]; then
key="$2"\ "$3"\ "$4"
fi

log_unhandled() {
logger "ACPI event unhandled: $*"
}

case "$group" in
button)
case "$action" in
power)
/sbin/init 0
;;

*) log_unhandled $*
;;
esac
;;

ibm)
case "$action" in
hotkey)
case "$key" in
"HKEY 00000080 00001008")
/usr/bin/acpi_fakekey 220
;;
"HKEY 00000080 00001009")
/usr/bin/acpi_fakekey 221
;;
"HKEY 00000080 00001014")
/usr/bin/acpi_fakekey 222
;;
*)
logger "acpid: $group/$action $key is not defined"
;;

esac
;;
*)
;;
esac
;;

*) log_unhandled $*
;;
esac
</bash>

Note that I use acpi_fakekey to translate acpi to key events.

=== ACPI Fakekey ===

With this nice app you can translate acpi events into key codes.

I borrowed it from gentoos acpi-support, which borrowed it from Ubuntu people.

You can it out of the sunrise overlay, I recommend only getting the
acpi-fakekey.c file and compile it.

For the lazy guys:

There is an explanation and the source code,
which I wont copy and paste here, on this page:

[http://gentoo-wiki.com/HARDWARE_Asus_F3SV#ACPI_.26_Hotkeys Gentoo Wiki on Hotkeys]

I use this in the file above to generate keycodes for Fn+F8, Fn+F9 and Fn+Space.

=== Kernel configuration ===

[http://www.fuchsnet.ch/files/config 2.6.24 TOI Kernel config]

Please note: this configuration works for my setup,
it might not for yours.

I use ext3 as my file system, make sure to compile in the support for the file system you are using, at least for the root partition.

I also use external ALSA drivers.
But I use lots of stuff you probably will never use, such as several gamepads,
acl support for ext3, some ipv4 / ipv6 filters ...
You might want to remove those.

This is the configuration for a 2.6.24 Kernel, it differs a little bit from the configuration of earlier kernels.

How to reduce power consumption

2008-04-04T15:27:56Z

Jaskiern: /* General settings */

Reducing system power consumption will extend battery life, reduce system
temperature and (on some models) reduce system fan noise.
Power consumption can be greatly improved from a stock distribution configuration
to a fine tuned system. The general rules are :
* Unload drivers for unused devices (ie. USB 1.1, Yenta/PCMCIA, Wireless, IRDA, Bluetooth, ...)
* Reduce polling on devices (drives, USB subsystem, nvram, use SATA AN, ...)
* Reduce hard drive activity
* Reduce LCD brightness to the minimum you can stand
* Reduce CPU wakeups, so it can stay longer in deep power saving c-states
* Make use of every hardware devices availables power saving features (AHCI ALPM, USB autosuspend, Alsa and Wireless powersaving modes, HPET timers, ...)

==Tools==
Arjan van de Ven's [[PowerTOP]] utility
is a gold mine to improve energy efficiency, but is almost only CPU-oriented. This tool helps to easily detect
the top power offenders, both userland and kernel modules, which prevent the use of CPU power saving mechanisms and sometime suggest
fixes accordingly.
PowerTOP users collected some [http://www.linuxpowertop.org/known.php tips & tricks]
and an informative [http://www.linuxpowertop.org/faq.php faq].

Alternatively (or complementary) to PowerTOP, running <code>strace -p $(pidof yourapp)</code>
for all your favorite or background running applications while they are expected to be
idle, will show the misbehaviors.

Beside CPU wakeups, disks spins are also power hungry. To detect what make your disk spinning,

<code>
sysctl vm.block_dump=1
</code>

will list all applications causing disks wakeups on the kernel's dmesg.
Other useful tools for this purpose are blktrace, iostat and lm-profiler
(from laptop-mode-tools suite).

See also [[#Misbehaving Userland]].

==BIOS settings==
Some Thinkpad BIOS (like 2.08 BIOS on {{X40}}) offer two very lame options,
with a very misleading online help (saying "Usually not needed"). That's

<code>
CPU power management: (default disabled)
PCI bus power management: (default disabled)
</code>

You should indeed ''enable'' them, else the deepest C3 and C4 ACPI C-states
are disabled.

==CPU==
Look at:
* [[How to make use of Dynamic Frequency Scaling]]
* [[Pentium M undervolting and underclocking]]

A good thing to keep in mind is that every CPU wakeup, even if it's for
a trivial light job, reduce the time the CPU stays on a deep power
saving C-state (like C3 or C4). Therefore you should ensure your applications
stay really idle when they meant to be idle (track shorts select timeouts
in loop, etc. with [[PowerTOP]]).

Also note that manually locking the CPU in the lowest P-state (frequency)
available is '''not''' an efficient way to improve battery lifetime. This will
cause the CPU to stay longer in C0 (power hungry C-state) doing hard work when
there is something to do, while it could have done this work faster by augmenting
the CPU freq, and returned back faster to a deeper, economic, C-state and to a
lower frequency (P-state).
The best is to let the kernel select the appropriates CPU frequencies by itself
with the help of in kernel CPU governors.
Have a look at [http://www.bughost.org/pipermail/power/2007-May/000166.html this explanation]
from Intel's kernel developer Arjan van de Ven.

==Kernel settings and patches==

===General settings===
The 2.6.21 kernel brought some very effective changes (like [[dynticks]]).
Later, 2.6.24-rc2 brought a lot of other power efficiency improvements.
If it's not already on your distribution and you value power efficiency,
you may think about compiling a recent kernel yourself.

Here are a few options (beside the ACPI and APM related one) that matter to
reduce power consumption or to help diagnosing consumers:

<code>
# From PowerTOP's FAQ:
CONFIG_NO_HZ
CONFIG_HIGH_RES_TIMERS
CONFIG_HPET
CONFIG_HPET_TIMER
CONFIG_CPU_FREQ_GOV_ONDEMAND
CONFIG_USB_SUSPEND
CONFIG_SND_AC97_POWER_SAVE
CONFIG_SND_HDA_POWER_SAVE
CONFIG_SND_HDA_POWER_SAVE_DEFAULT=3
CONFIG_TIMER_STATS
CONFIG_ACPI_BATTERY
CONFIG_CPU_FREQ_STAT
CONFIG_INOTIFY

# Not from the PowerTOP FAQ:
CONFIG_BLK_DEV_IO_TRACE
CONFIG_X86_ACPI_CPUFREQ
CONFIG_X86_SPEEDSTEP_CENTRINO depreciated as of kernel 2.6.24, use CONFIG_X86_CPUFREQ
CONFIG_X86_SPEEDSTEP_ICH
CONFIG_X86_SPEEDSTEP_SMI
CONFIG_CPU_IDLE
CONFIG_CPU_IDLE_GOV_LADDER
CONFIG_CPU_IDLE_GOV_MENU
</code>

Those options are already in Fedora Core 7 and Ubuntu Gutsy (not Feisty) default i686 kernels.
PowerTOP FAQ also suggest to '''disable'''
CONFIG_IRQBALANCE and CONFIG_ACPI_DEBUG.

Also, you need to properly set APM and ACPI. Look at:
* [[Power Management]]
* [[How to make use of Power Management features]]

=== Kernel boot and module loading options ===
If you have an Intel chipset > ICH3 (cf. lspci output), as in most modern Thinpads, you should
be using the integrated HPET timer (saves about 30 CPU wake ups per second). To see if
hpet is enabled on your laptop :

<code>
grep hpet /proc/timer_list
</code>

If this does not display "Clock Event Device: hpet", then add

<code>
hpet=force
</code>

to your kernel boot options (usualy in /boot/grub/menu.lst or lilo.conf).
Note that "hpet=force" is only available by default in 2.6.24-rc2 and above
(or as a separated patch for 2.6.22 and 2.6.23, see below).

===Useful Patches===

Thomas Gleixner High Resolution Timers (hrt) patchset brings many improvements,
like the cpuidle work and Udo A. Steinberg and Venki Pallipadi "force
enable HPET" patches (non HPET timers causes about 20-40 CPU wakeups/second, but
HPET is often hidden by the BIOS due to Windows XP deficiencies). Those are
fully merged in 2.6.24-rc1 vanilla kernel.
See http://www.tglx.de/projects/hrtimers/

Kristen Carlson Accardi from Intel has a patchset to turn on "Aggressive
Link Power Management" (ALPM) for the AHCI driver (for SATA bus). Also from
Accardi, SATA Asynchronous Notification (SATA AN), alows SATA link to notify
media insertions (thus avoid hal polling the cdrom). Those patches were merged
in 2.6.24-rc2 kernel (AN needs also support in hal to be used).
See: http://www.kernel.org/pub/linux/kernel/people/kristen/patches/SATA/alpm/

As of now (2.6.24-rc8), the linux kernel doesn't support PCI Express power
management (aka PCIe ASPM, aka PCIe LPM). Shaohua Li from Intel submited a
patch on LKML (http://lkml.org/lkml/2008/1/17/544 ) though, and reported it
to reduce power consumption by 1.3 watts for a system with three PCIe links.

The [[HDAPS]] disk protection systems can reduce battery life.
Matthew Garrett provides [http://www.linuxpowertop.org/patches/hdaps.patch a patch]
that prevents hdaps kernel module to generate interrupts when
this feature isn't used.

===Useful sysctls===
The meaning of those settings is explained case by case on the relevant
sections of this document. But for convenience sake, we group them here too.

Note that the "ondemand" scaling governor is recommended by Intel developers
for energy efficiency: it's expected to be more efficient than the "powersave"
governor, or than userspace daemons (like cpufreq-utils, cpufreqd, powernowd...).
Look [http://www.bughost.org/pipermail/power/2007-May/000071.html here],
[http://www.bughost.org/pipermail/power/2007-May/000073.html here], or
[http://www.bughost.org/pipermail/power/2007-May/000166.html here] for a
kernel developer explanation about "ondemand" being better on modern Intel CPUs.

The "link_power_management_policy" tunable won't be available unless you
run a 2.6.24-rc2 or more kernel, or applied Kirsten patchset, have an Intel
AHCI compatible chipset, and use SATA drives.

<code>
echo 5 > /proc/sys/vm/laptop_mode
echo 0 > /proc/sys/kernel/nmi_watchdog
echo Y > /sys/module/snd_ac97_codec/parameters/power_save
echo 1 > /sys/devices/system/cpu/sched_mc_power_savings
echo ondemand > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
echo 1500 > /proc/sys/vm/dirty_writeback_centisecs
for i in /sys/bus/usb/devices/*/power/autosuspend; do echo 1 > $i; done
# those sysctl's are only available if you have an AHCI compatible SATA
# controler and use kernel > 2.6.24-rc2 (or use Kristen ALPM patchset) :
echo min_power > /sys/class/scsi_host/host0/link_power_management_policy
echo min_power > /sys/class/scsi_host/host1/link_power_management_policy
</code>

If you're running a kernel older than 2.6.22 do this. Not needed for kernels 2.6.22 onward:

<code>
cd /sys/devices/system/cpu/cpu0/cpufreq
cat ondemand/sampling_rate_max > ondemand/sampling_rate
</code>

==ATA drives==
Hard drives and CDRom drives spinning is very costly. To improve battery
lifetime, you should reduce disks access (or devices polling) the more you
can.

===Hard Drives===
The files access time update, while mandated by POSIX, is causing lots of
disks access; even accessing files on disk cache may wake the ATA or USB
bus. If you don't use this feature, disable it via:

<code>
mount -o remount,noatime / # and so on for all mounted fs
</code>

The laptop_mode reduce disk usage by regrouping writes. You should enable
it, at least while on battery. See [[Laptop-mode]] for more details:

<code>
echo 5 > /proc/sys/vm/laptop_mode
</code>

The default kernel dirty page writeback frequency is very conservative. On
a laptop running on battery, one might find more appropriate to reduce it:

<code>
echo 1500 > /proc/sys/vm/dirty_writeback_centisecs
</code>

Some power saving hard drives features can be activated with hdparm (beware
that "-B 1" may reduce your drive lifetime, if you have lot of intermittent
disk activity causing lots of heads load/unloads: so reduce I/O activity first,
as explained above, in order to get longer disks idling periods).
For more details look at [[How to make use of Power Management features]] :

<code>
hdparm -B 1 -S 12 /dev/sda # and/or any other disk device
</code>

===Optical drive===
The optical drive is reported to consume power even when not accessed. See

* [[How to hotswap UltraBay devices|Eject the UltraBay optical drive]], or just turn off its power supply (i.e., run the appropriate eject script but leave the drive inserted).
* [[How to set optical drive speed|Reduce the spinning speed of the optical drive]].

The hald daemon polling tends to maintain the ATA buses out of power saving
modes, and to wakeup CDROM drive (except if you have a kernel >= 2.6.24, hal >= 0.5.10,
and SATA AN compatible devices). If you have a recent hald version, you
can stop this polling when on battery:

<code>
hal-disable-polling --device /dev/scd0 # or whatever your CD drive is
</code>

start polling again when on ac:
<code>
hal-disable-polling --enable-polling --device /dev/scd0 # or whatever your CD drive is
</code>

If your hald is not recent enough, consider suspending it when running on battery. Some moderns SATA buses and drivers supports a notification mechanism (SATA AN - Asynchronous Events Notifications) that obsolete the need for polling on modern hardware; support for this feature had been merged in Linux 2.6.24-rc1 and HAL 0.5.10.

==LCD Backlight/Brightness==
The LCD backlight is one of the very major power drain.
Reducing brightness to the lowest readable
level will save a lot of battery lifetime. Also, don't forget to configure
your screen saver to shutdown the screen backlight (rather than displaying some
eye candy), when no activity for a few minutes.

You can also let the system [[automatically reduce brightness]] after a
period of inactivity.

If you're choosing your Thinkpad laptop model, keep in mind that the screen
size affect the battery time greatly: more power needed for larger screens.

The very recent, but xorg standard way to control backlight from CLI is
using xbacklight. ie. to set backlight at half the brightness:

<code>
xbacklight -set 50
</code>

You should configure the DPMS to shutdown the screen when idle (rather than
displaying a fancy but power consuming screensaver). ie. to turn off the
display after 5mn of idling:

<code>
xset +dpms
xset dpms 0 0 300
</code>

==Graphic controllers==
All xorg Thinkpad graphics chipsets drivers (ati, radeon, fglrx, i810) have
the same bug causing very frequent CPU wakeups when DRI is activated, even
when you don't use any 3D application.
This problem is partly fixed on xorg git tree but not released as of xorg
7.2. If you value more battery than 3D, you should disable DRI: put this on
the /etc/X11/xorg.conf "Device" of you graphic controller:

<code>
Option "NoDRI"
</code>

Also be sure that DPMS is working: <code>grep DPMS /var/log/Xorg.0.log</code>
should output "DPMS enabled". If not, put <code>Option "DPMS"</code> in your config.
See the section above about how to enable dpms driven display power saving.

On recent xrandr/xorg versions, you can disable the TV output (or any other detected
as connected but not used outputs) when you're not using it: it's known to consume power.

<code>
xrandr # see all displays listed here, but that you don't actually use and disable them.
xrandr --output TV -off # for instance (if "xrandr" above listed a connected output named "TV" that you don't use)
</code>

When you don't have an external monitor plugged, disable CRT and DVI output
(for some, this can make a difference in power usage) :
<code>
echo crt_disable > /proc/acpi/ibm/video
echo dvi_disable > /proc/acpi/ibm/video
</code>

Some drivers have specials power saving mode, and/or allows underclocking the GPU. See also:
* [[How to make use of Graphics Chips Power Management features]], or with [[Rovclock]] on ATI.
* [[Problem with high power drain in ACPI sleep]]

==USB Subsystem==
The kernel support an efficient USB 2.0 power saving feature if you enabled
CONFIG_USB_SUSPEND. This may not trigger in when you have an USB device
plugged (and beside, USB devices tends to suck power on their own), so avoid
using such devices when on battery. To enable it by default, you must add the line
<code>
options usbcore autosuspend=1
</code>
to your <tt>/etc/modprobe.conf</tt> or add it to (and create if necessary) the file <tt>/etc/modprobe.d/usbcore</tt> depending on how your distribution organises modprobe configuratoin.

If on the other hand, you have <tt>usbcore</tt> built into your kernel, you can add this in the kernel boot options (ie. in grub's menu.lst):

<code>
usbcore.autosuspend=1
</code>

or at runtime, per device, with:

<code>
for i in /sys/bus/usb/devices/%s/power/autosuspend; do echo 1 > $i; done
</code>

USB 1.1 is worst. It needs polling the bus frequently, hence can't really go
in a low power mode when you enabled it, even if you don't have any device
plugged. You'd better remove it when you don't use a 1.1 device:

<code>
rmmod uhci_hcd
</code>

If you don't intend to use any device needing USB 1.1 (unfortunately, the built-in bluetooth and fingerprint-reader are USB 1.1 devices), the USB 1.1 support can also be totally avoided. On Debian and derivatives, just do:

<code>
echo "blacklist uhci_hcd" >> /etc/modprobe.d/blacklist
</code>

Same for PCMCIA/Cardbus. Some users experiences interrupts clouds (sometime up to
several thousands interrupts/second) causing CPU wakeups, thus totally preventing
the CPU to reach lower C-states.
If you don't use PCMCIA, you may disable it the same way (unloading seems insufficient
to restore the system properly, you have to boot without it):

<code>
echo "blacklist pcmcia" >> /etc/modprobe.d/blacklist
echo "blacklist yenta_socket" >> /etc/modprobe.d/blacklist
</code>

==Sound==
ALSA has a power saving feature that should be enabled on your kernel
(CONFIG_SND_AC97_POWER_SAVE). Note that this low power mode won't trigger in
unless you muted all sound inputs (micro, line in etc.). This feature has
to be activated with:

<code>
amixer set Line mute nocap
amixer set Mic mute nocap
echo Y > /sys/module/snd_ac97_codec/parameters/power_save
</code>

More radical: you can unload all sound related modules when you are on
battery, or mute the sound system (echo mute > /proc/acpi/ibm/volume).

See also [[How to enable audio codec power saving]].

==Wireless Interface==
===intel wireless===
Wireless network consume a lot of power.
To save power, you can kill the Wi-Fi radio when it's not in use:

<code>
echo 1 > /sys/bus/pci/devices/*/rf_kill
</code>

If you need Wi-Fi, you can also reduce power consumption (at the price of
performances) by activating the power saving modes:

<code>
iwpriv eth1 set_power 5
</code>

For drivers using the new Wi-Fi kernel framework (mac80211/cfg80211),
the canonical way to do this is now:

<code>
for i in /sys/bus/pci/devices/*/power_level ; do echo 5 > $i ; done
</code>

Most drivers, like ipw2200, that don't use the new mac80211 framework place the
interfaces in aggressive scanning mode when they are not associated with any
Access Point, even when the interface is down (more info about this on Intel's
[http://www.lesswatts.org/tips/wireless.php LessWatts] website).
This behavior consumes a lot of power, even more than when the interface
is plain active and in use. But this can disabled at module's load time :

<code>
rmmod ipw2200
modprobe ipw2200 associate=0
</code>

You can fix this setting by placing the following in /etc/modprobe.d/options
(Debian/Ubuntu) or in /etc/modprobe.conf (Red Hat/Fedora):

<code>
options ipw2200 associate=0
</code>

Reducing beacon intervals on your Access Point to 1 per second will also
reduce network card interrupts, therefore power savings. This shouldn't have
negatives side effects.

See also, to activate power saving on the wireless network card:
* For [[Intel PRO/Wireless 2200BG Mini-PCI Adapter]] and [[Intel PRO/Wireless 2915ABG Mini-PCI Adapter]], see instructions for the [[ipw2200]] driver.
* For [[Intel PRO/Wireless 3945ABG Mini-PCI Express Adapter]], see the [http://ipw3945.sourceforge.net/README.ipw3945 ipw3945 driver README]

==Ethernet Controler==
If you don't use Wake-on-LAN, you should disable it for your network card,
because it sucks a lot of power:

<code>
ethtool -s eth0 wol d
</code>

If you can, try to reduce useless network activity on your ethernet
segment, coming to your NIC (ie. uneeded broadcasts), those cause
interrupts and CPU wakeups.

Forcing 100Mbps full-duplex speed on a gigabit ethernet NIC can also save a lot of power (~1W) on most network workloads. This also reduces components temperature (e.g., [[Thermal Sensors|thermal sensor]] 0xC0 on the {{T43}} cools down by 5 degree between 1000Mbps and 100Mbps, and another 1 degree for 10Mbps).

<code>
ethtool -s eth0 autoneg off speed 100
</code>

Note, however, that if the network device on the other side has auto-negotiation enabled (which is very common) and you turn auto-negotiation off, the other side will assume half-duplex mode and you will experience a significant loss of performance.

==Bluetooth==
When you don't need bluetooth, disable it. Because of its radio,
bluetooth is not power friendly.

<code>
hciconfig hci0 down ; rmmod hci_usb
echo disable > /proc/acpi/ibm/bluetooth
</code>

==Modem==
When was the last time you used your analog modem? If you can't remember, you probably just don't need it. If it is on a separate module in your laptop, simply remove it. Store it in a ESD safe place (like the bag in which your last addon card or hard drive was packed), in case you should need it again. This won't save you a lot of power and weight, but why carry something around you never use.

==System Fans==
Fans consumes power when running, so you may look at the [[ACPI fan control script]].

==Misbehaving Userland==
You should avoid using Beagle, Compiz, Beryl, XMMS, gnome-power-manager
and Evolution while on battery.
Look at the PowerTOP's [http://www.linuxpowertop.org/known.php known problems]
list.

Deactivate desktop animations (blinking cursor on the terms, animated wallpapers, ...): they cause regular X (therefore kernel and CPU) wakeups.

In short, while on battery, you should stop all applications that don't really stay idle when you're not using them. This means applications that:
* Wakes up the CPU too often (by polling something, because of too short select() timeouts, ...)
* Access the disks at regular intervals
* Access an hardware bus (USB, ATA, ...) at regular intervals
To find those offenders run:
* <code>strace -p $(pidof yourapp)</code> # for all your running applications
* <code>powertop</code>
* <code>sysctl vm.block_dump=1</code> # and look at dmesg
* <code>ps aux | awk '{print$10,$11}' | sort -n</code> # will list all running softs sorted by used cpu time
Please, don't forget to fill a bug when you find such a misbehaving software.
{{NOTE|Not all software is evil, buggy or badly written. Some produce regular activity because they have to, in order to provide their intented functionality. Think twice before filling bugs about this.}}

==See Also==
* [[How to measure power consumption]]
* [[Script for monitoring power consumption]]
* Battery [[maintenance]]

==External resources==
* [http://www.free-it.de/archiv/talks_2005/paper-11017/paper-11017.html ''Current trends in Linux Kernel Power Management''], Dominik Brodowski, 2005
* [http://www.linuxpowertop.org PowerTOP] website
* [http://www.gentoo.org/doc/en/power-management-guide.xml Power Management Guide] from the Gentoo Linux documentation
* [http://mailman.linux-thinkpad.org/pipermail/linux-thinkpad/2005-November/030478.html When/where/what for low power consumption?] (thread on Linux-Thinkpad)
* Intel's [http://www.lesswatts.org/ LessWatts] "''Saving power on Linux''" website
* ''8 hours of battery life on your lap(top)'' ([http://atrey.karlin.mff.cuni.cz/~pavel/swsusp/8hours.odp ODP]/[http://atrey.karlin.mff.cuni.cz/~pavel/swsusp/8hours.pdf PDF]), a presentation by Pavel Machek

[[Category:600X]] [[Category:A20m]] [[Category:A20p]] [[Category:A21e]] [[Category:A21m]] [[Category:A21p]] [[Category:A22e]] [[Category:A22m]] [[Category:A22p]] [[Category:A30]] [[Category:A30p]] [[Category:A31]] [[Category:A31p]] [[Category:i1200]] [[Category:i1300]] [[Category:i1620]] [[Category:G40]] [[Category:G41]] [[Category:R30]] [[Category:R31]] [[Category:R32]] [[Category:R40]] [[Category:R40e]] [[Category:R50]] [[Category:R50e]] [[Category:R50p]] [[Category:R51]] [[Category:R52]] [[Category:R60]] [[Category:R60e]] [[Category:T20]] [[Category:T21]] [[Category:T22]] [[Category:T23]] [[Category:T30]] [[Category:T40]] [[Category:T40p]] [[Category:T41]] [[Category:T41p]] [[Category:T42]] [[Category:T42p]] [[Category:T43]] [[Category:T43p]] [[Category:T60]] [[Category:T60p]] [[Category:T61]] [[Category:X20]] [[Category:X21]] [[Category:X22]] [[Category:X23]] [[Category:X24]] [[Category:X30]] [[Category:X31]] [[Category:X32]] [[Category:X40]] [[Category:X41]] [[Category:X41 Tablet]] [[Category:X60]] [[Category:X60s]] [[Category:Z60m]] [[Category:Z60t]] [[Category:Z61t]] [[Category:Z61e]] [[Category:TransNote]]

How to make use of Dynamic Frequency Scaling

2008-04-04T15:27:40Z

Jaskiern: /* A note about CPU throttling */

==General==
Linux supports dynamic frequency scaling for systems with the following processors:
*[[Intel Mobile Pentium III]]
*[[Intel Mobile Pentium III-M]]
*[[Intel Mobile Pentium 4]]
*[[Intel Mobile Pentium 4-M]]
*[[Intel Pentium M (Banias)]]
*[[Intel Pentium M (Dothan)]]
*[[Intel Core Solo (Yonah)]]
*[[Intel Core Duo (Yonah)]]
*[[Intel Core 2 Duo]]
*Mobile Athlon
*AMD64
*Opteron

==Configuring the Kernel==
===2.4 Kernels===
There were various frequency scaling implementations in the 2.4 series of kernels. They all were preliminary and a standard was raised with the introduction of the sysfs filesystem in 2.6 kernels. It is recommended to use a 2.6 kernel, if possible.

===2.6 Kernels===
You need to enable the CPU frequency scaling for your kernel (usually your distros kernel will have this enabled), under {{kernelconf||||CPU Frequency scaling|Power management options (ACPI, APM)|||}}: {{kernelconf|CONFIG_CPU_FREQ|<*>|||||}}

If you own a Dothan processor, you need to enable Enhanced SpeedStep functionalities.
:{{kernelconf|CONFIG_X86_SPEEDSTEP_CENTRINO|<*>|||||}}

Alternatively, there seems to be some advocacy of a switch over to
:{{kernelconf|CONFIG_X86_ACPI_CPUFREQ|<*>|||||}}
for controlling speedstep technology. Apparently this newer kernel option is more aware of acpi powersaving that's done in the BIOS. In any case, both {{kernelconf|CONFIG_X86_SPEEDSTEP_CENTRINO|<*>|||||}} and {{kernelconf|CCONFIG_X86_ACPI_CPUFREQ|<*>|||||}} were found to work on a Menrom (Core 2).

You also need to enable governors, if not already done in your distros default kernel:
:{{kernelconf|CONFIG_CPU_FREQ_GOV_PERFORMANCE|<*>|||||}}

The '''performance''' CPU governor lets your CPU frequency always to the highest available.

:{{kernelconf|CONFIG_CPU_FREQ_GOV_POWERSAVE|<*>|||||}}

The '''powersave''' governor sets the frequency to the lowest available. That's not the best choice for battery lifetime on modern Intel CPU, though (see above).

:{{kernelconf|CONFIG_CPU_FREQ_GOV_USERSPACE|<*>|||||}}

The '''userspace''' governor allows you to set the frequency manually, unlike the others. Some [[#Using Frequency Scaling Daemons|frequency scaling daemons]] require this governor to operate correctly. This is typically the recommended option with older processors like A30p's pIIIm-1200.

:{{kernelconf|CONFIG_CPU_FREQ_GOV_ONDEMAND|<*>|||||}}
:{{kernelconf|CONFIG_CPU_FREQ_GOV_CONSERVATIVE|<*>|||||}}

The '''ondemand''' (available since 2.6.10) and '''conservative''' (since 2.6.12) are governors based on in kernel implementations of CPU scaling algorithms: they scale the CPU frequencies according to the needs (like does the userspace frequency scaling daemons, but in kernel). They differs in the way they scale up and down. The ondemand governor switches to the highest frequency immediately when there is load, while the conservative governor increases frequency step by step. Likewise they behave the other way round for stepping down frequency when the CPU is idle. The conservative governor is good for battery powered environments on AMD64 (but may not work on older ThinkPads like the T21). Ondemand may not work on older laptops without Enhanced SpeedStep due to [http://lists.debian.org/debian-powerpc/2005/05/msg00542.html latency reasons]. Anyway, for recent enough Intel CPU, ondemand is the one recommended for power efficiency (over userspace, and even over "powersave") by the Intel's kernel developer Arjan van de Ven (see [http://www.bughost.org/pipermail/power/2007-May/000166.html], [http://www.bughost.org/pipermail/power/2007-May/000073.html], [http://www.bughost.org/pipermail/power/2007-May/000071.html])

=== 2.6 doing it with modules ===
With the Debian flavour of 2.6.21 and possibly earlier versions as well as other distros, all of the above kernel options are compiled as modules out of the box. You'll have to load them yourself to get speedstep functionality. This can be done simply enough in an /etc/modules file with the lines
<pre>
acpi-cpufreq
cpufreq_ondemand
cpufreq_userspace
cpufreq_conservative
cpufreq_powersave
</pre>
of course, this is a bit excessive if you're only going to use one governor (see below), you only need to load the modules for the governor(s) you are going to use. It seems that "performance" is not a loadable module in my case. Probably because it's built into the kernel as the default. Finally if you're a fan of useless statistics, you can load cpufreq_stats so that you can see how long your processor spends in each state and how many times it transitions with
<pre>
cat /sys/devices/system/cpu/cpu0/cpufreq/stats/total_trans
cat /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state
</pre>

{{NOTE| "acpi-cpufreq" does not work on a T43. Use the module called "speedstep-centrino" instead!}}

==Using the Sys Interface==
The files in {{path|/sys/devices/system/cpu/cpu0/cpufreq/}} provide information and a means of controlling the frequency scaling subsystem.
Seed values are given in Khz. You need to be root to access the /sys filesystem.

Your max speed is at {{path|/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq}}.
:{{cmdroot|cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq}}
:{{cmdresult|700000}}
Your min speed is at {{path|/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_min_freq}}.
:{{cmdroot|cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_min_freq}}
:{{cmdresult|500000}}
If you are using the userspace governor, you can write to {{path|/sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed}} to change the current speed.
:{{cmdroot|echo 700000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed}}
:{{cmdroot|cat /proc/cpuinfo | grep "cpu MHz"}}
:{{cmdresult|cpu MHz : 697.252}}
:{{cmdroot|echo 900000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed}}
:{{cmdroot|cat /proc/cpuinfo | grep "cpu MHz"}}
:{{cmdresult|cpu MHz : 976.152}}

==Using Frequency Scaling Governors==
You can get a list of available governors with (as root):
:{{cmdroot|cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors}}
:{{cmdresult|conservative ondemand powersave userspace performance}}

Note: If the governors are compiled as modules, load them first:
:{{cmdroot|modprobe cpufreq_performance cpufreq_ondemand cpufreq_conservative cpufreq_powersave cpufreq_userspace}}

Now we set our governor:
What is our current governor?
:{{cmdroot|cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor}}
:{{cmdresult|userspace}}
Set new governor and watch if it has changed
:{{cmdroot|echo conservative > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor}}
:{{cmdroot|cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor}}
:{{cmdresult|conservative}}

Congrats! Your governor is active.

You may set the governor in your rc.local, to make it used on every boot.

==Using Frequency Scaling Daemons==
Frequency Scaling Daemons adapt the frequency policy to different situations. A typical configuration would be to use the ondemand governor running off batteries and performance otherwise, or combining powersave with conservative on laptops with heat problems. More sophisticated setups adapt to battery level, CPU temperature or even running programs. Some daemons are able to control other power management features like hard disks or graphic cards.

{{NOTE|Daemons are optional. If you don't plan to change policies depending on the situation, you don't need one and you can stick to the <tt>ondemand</tt> or <tt>conservative</tt> frequency scaling governors, available in kernels after 2.6.10 or 2.6.12 respectively. See [[#Using Frequency Scaling Governors|above]]. They require less configuration and have generally been experienced to flawlessly adapt to the situations at hand.}}

Some daemons use the kernel governors (see above), others implement the functionality on their own. In the latter case you have to enable the userspace governor. If it is built as module, load it as <tt>cpufreq-userspace</tt>.

There are plenty of userspace frequency scaling daemons available:

*[[How to configure cpudynd | cpudynd]]
*[[How to configure cpufreqd | cpufreqd]]
*[[How to use cpufrequtils | cpufrequtils]]
*[[How to configure powernowd | powernowd]]
*[[How to configure powersaved | powersaved]]
*[[How to configure speedfreqd | speedfreqd]]
*[[laptop-mode-tools]] can also be configured to switch governors when the laptop is plugged in and unplugged

==Debian notes==
Instead of compiling your own kernel, you can use the {{Debian}} "stock" kernel. In Debian/Etch the 2.6.18 kernel image with an {{path|/etc/modules}} file that includes:

battery
ac
thermal
processor
acpi-cpufreq
cpufreq-userspace

With the powernowd package and you should be setup.

{{Debian}} Etch now has {{path|rc.local}} (see package initscripts).

However, a better alternative for Debian, rather than modifying bootscripts, is to install the [http://packages.debian.org/cgi-bin/search_packages.pl?searchon=names&version=all&exact=1&keywords=sysfsutils sysfsutils package]. Then edit {{path|/etc/sysfs.conf}} (as root), where you can setup values to sysfs entries that you want to be modified automatically on boot.

==Troubleshooting==
*If you have a Coppermine-piix-smi based ThinkPads like from the A2x, X2x and T2x series you need to enable the <tt>speedstep-smi</tt> driver in the kernel and load it if it's built as module. You might want to look at [[How to get SpeedStep working on Coppermine-piix4-smi based ThinkPads | this page]].

*If you have a p4-class celeron based ThinkPad like the R40e you might want to look at [[How to get SpeedStep working on P4-class-Celeron based ThinkPads | this page]]

*You may need to set your BIOS to "maximum performance" if you are using Linux to set the CPU speed. This is necessary to prevent odd behaviour (cpufreq 'freezing' at certain frequencies) with the T4x series.

*You will need to have the cpufreq-selector applet installed at SUID root to use the gnome cpufreq applet. See [http://ubuntu.wordpress.com/2005/11/04/enabling-cpu-frequency-scaling/ this page] for info.

==Finetuning voltages and available frequencies==
See [[Pentium M undervolting and underclocking]].

==A note about CPU throttling==

Throttling the CPU through ACPI "T" states is generally useless for power consumption reduction nowadays. It is an artifact of the past, when there was no clock frequency scaling and ACPI "C" states were mostly not implemented or didn't exist.

Throttling does not decrease clock frequency at all, and it can even increase power consumption in a modern CPU capable of ACPI "C" states, as it can interfere with the CPU reaching the higher C states (such as C2).

On a T43, setting a CPU to a ACPI Throttle state different than T0 (no throttling) can cause it to draw more than 100mW extra power, as it will reach C2 less often.

In case your BIOS offers "cpu power management" and "pci bus power management" disabled by default (that's the case in X40 with the 2.08 BIOS), you should turn them on (or choose "automatic"). Despite what the BIOS online documentation says ("rarely needed"), this is quite useful, since it make the deepests (C3 and C4) ACPI C-states avaibles. On a kernel more with [[dynticks]] (2.6.21 and over), this should save about 2W or more.

==External links==
* [http://kernel.org/pub/linux/kernel/people/lenb/acpi/doc/OLS2006-ondemand-presentation.pdf ''The Ondemand Governor''], Intel Open Source Technology Center (Venkatesh Pallipadi, Alexey Starikovskiy, Len Brown), presentation at Ottawa Linux Symposium, July 19 2006

[[Category:600X]] [[Category:A20m]] [[Category:A20p]] [[Category:A21e]] [[Category:A21m]] [[Category:A21p]] [[Category:A22e]] [[Category:A22m]] [[Category:A22p]] [[Category:A30]] [[Category:A30p]] [[Category:A31]] [[Category:A31p]] [[Category:i1200]] [[Category:i1300]] [[Category:i1620]] [[Category:G40]] [[Category:G41]] [[Category:R30]] [[Category:R31]] [[Category:R32]] [[Category:R40]] [[Category:R40e]] [[Category:R50]] [[Category:R50e]] [[Category:R50p]] [[Category:R51]] [[Category:R52]] [[Category:R60]] [[Category:R60e]] [[Category:T20]] [[Category:T21]] [[Category:T22]] [[Category:T23]] [[Category:T30]] [[Category:T40]] [[Category:T40p]] [[Category:T41]] [[Category:T41p]] [[Category:T42]] [[Category:T42p]] [[Category:T43]] [[Category:T43p]] [[Category:T60]] [[Category:T60p]] [[Category:T61]] [[Category:X20]] [[Category:X21]] [[Category:X22]] [[Category:X23]] [[Category:X24]] [[Category:X30]] [[Category:X31]] [[Category:X32]] [[Category:X40]] [[Category:X41]] [[Category:X41 Tablet]] [[Category:X60]] [[Category:X60s]] [[Category:Z60m]] [[Category:Z60t]] [[Category:Z61t]] [[Category:Z61e]] [[Category:TransNote]]

Installing Ubuntu 8.04 (Hardy Heron) on a ThinkPad T60

2008-04-04T15:25:55Z

Jaskiern: /* Features */

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

It is not verified that an automatic migration will occur when upgrading from [[Installing Ubuntu 7.10 (Gutsy Gibbon) on a Thinkpad T60 | Ubuntu 7.10]] to Ubuntu 8.04 will occur. If it does not and a migration is desired, Ubuntu Help Community has written some [https://help.ubuntu.com/community/WifiDocs/Driver/iwlwifi_Intel_3945_4965/gutsy documentation] that will make this very easy to do.

=== Increased power savings ===
This release includes Linux-2.6.24, which has [[dynticks]] support. The power savings that have been available to 32-bit systems are now brought to 64-bit systems. This will have an effect on those T60 laptops with an [[Intel Core 2 Duo (Merom)]].

== Installation ==

my thinkpad: T60 with [[Intel Graphics Media Accelerator 950]] (WXSGA 1680x1050 display), atheros wireless card, 2GHz [[Intel Core 2 Duo (Merom)]].
poliahu $ lspci
00:00.0 Host bridge: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 945GT Express Memory Controller Hub (rev 03)
00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller (rev 03)
00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03)
00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 02)
00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 02)
00:1c.1 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 2 (rev 02)
00:1c.2 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 3 (rev 02)
00:1c.3 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 4 (rev 02)
00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #1 (rev 02)
00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #2 (rev 02)
00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #3 (rev 02)
00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #4 (rev 02)
00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2)
00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 02)
00:1f.1 IDE interface: Intel Corporation 82801G (ICH7 Family) IDE Controller (rev 02)
00:1f.2 SATA controller: Intel Corporation 82801GBM/GHM (ICH7 Family) SATA AHCI Controller (rev 02)
00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller (rev 02)
02:00.0 Ethernet controller: Intel Corporation 82573L Gigabit Ethernet Controller
03:00.0 Ethernet controller: Atheros Communications, Inc. AR5212 802.11abg NIC (rev 01)
15:00.0 CardBus bridge: Texas Instruments PCI1510 PC card Cardbus Controller
poliahu $

I booted on the Hardy Heron alpha 4 liveCD and installed from there on a 5GB primary ext3 partition.
No problem whatsoever during liveCD session and install. Everything went smooth. I have my home on a separate partition of course, and I created a "hardy" user just to play around.

=== Known Issues ===

====EXA issues with intel graphic card driver (945, 965)====

Hardy comes with the newest Xorg:

root@poliahu:/# Xorg -version
This is a pre-release version of the X server from The X.Org Foundation.
It is not supported in any way.
Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/.
Select the "xorg" product for bugs you find in this release.
Before reporting bugs in pre-release versions please check the
latest version in the X.Org Foundation git repository.
See http://wiki.x.org/wiki/GitPage for git access instructions.
X.Org X Server 1.4.0.90
Release Date: 5 September 2007
X Protocol Version 11, Revision 0
Build Operating System: Linux Ubuntu (xorg-server 2:1.4.1~git20080131-1ubuntu3)
Current Operating System: Linux poliahu 2.6.22-14-generic #1 SMP Tue Feb 12 07:42:25 UTC 2008 i686
Build Date: 19 February 2008 04:52:29PM
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Module Loader present
root@poliahu:/#

and with X autoconfiguration (as far as I understand). So hardy installs a xorg.conf, but it is barebones. Most of the config is handled internally by the new server, and is handled fairly well. My screen and card were recognized, it configured it with the correct driver and resolution. I had 3D accel out of the box too, so that compiz was working without any tinkering. All good up to there.

The only problems I encountered in X (once more, this is only applicable to intel graphic hardware) were

(1) the trackpad was working but the scroll function was not (in previous version of ubuntu, moving your finger up and down in the right part of the trackpad would provide this functionality, here not). This is apparently a known regression (can't find the reference, but read it in some launchpad or ubuntu forum post). As it is a known regression, I assume it will be fixed for the final hardy release (?).

(2) The intel driver config adopted by default by the new xorg uses EXA acceleration, which is newer and performs overall better than the XAA. The problem is that on some intel hardware, it performs quite poorly for text processing. I noticed that immediately: when I had no window, or only a terminal around, compiz would be its usual smooth (e.g. when rotating cube or moving windows). With a few windows open, with text (e.g. firefox), compiz would be very jumpy / choppy. Copying over the xorg.conf form my gutsy installation and adding:
Option "AccelMethod" "XAA"
in the "Device" section (where the video intel driver is specified) solved the problem, and now I'm back to the old smooth compiz animations.

Using this -otherwise unmodified xorg.conf- had the side effect of killing my trackpad entirely. Now It's not responsive at all. Again, I expect these things will be ironed out for the final release. Another possibility would be to only add the XAA AccelMethod in the existing xorg.conf (hardy default), but I did not know nor researched how to do that.

[update 2008feb23: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/177492 describe the above problem. It turns out that there is another solution, keeping EXA. Keep the stock xorg.conf (the barebone one installed by default with hardy -clean install-. Just add:
Option "AccelMethod" "EXA"
Option "ExaNoComposite" "false"
Option "MigrationHeuristic" "greedy"

in the Section "Device" (so don't put XAA). With these settings, acceleration is smooth across the board (including wiht fonts) and compiz works like a charm. Cherry on the pie: you'll have XV (hardware video), so this means nice and smooth DVD and movie playing, much lighter cpu load, etc... compared to the x11 (software) video driver. As an extra, you can also use the INTEL_BATCH flag, which was reported by the vast majority of intel users to speed up graphical performance significantly (30%+). Put
INTEL_BATCH="1"
in your /etc/environment (I read you can also put it in your .bashrc, but I didn't try that). end update 2008feb23]

==== Multimedia keys don't work with Exaile ====

Another problem I noticed was that the multimedia keys were not operating in exaile. I haven't tested them in rythmbox or other apps.

Apart from that, everything I tested was fine: display, network (wired and wireless), sound (pulseaudio sounds noticeably better, but may be it's self induced), suspend (which worked for a couple of tests, and then I installed uswsusp -s2ram- 0.8, which has always been more reliable for me), haven't tried hibernate, nor bluetooth.

== Post-Installation Setup ==

== Notes ==

== See also ==

== References ==
* [[Installing Ubuntu 7.10 (Gutsy Gibbon) on a Thinkpad T60]]

== External links ==

[[Category: T60]] [[Category: Ubuntu 8.04]]

Installing Ubuntu 7.10 (Gutsy Gibbon) on a Thinkpad T60

2008-03-15T01:51:37Z

Jaskiern: /* Install Active Protection System */

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

Make sure that you are using the ATI restricted driver under 'System - Administration - Restricted Drivers.'

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

Edit---[[User:Rperkins|Rperkins]] 09:51, 16 February 2008 (CET)
I think the second command listed above( the one that starts with cat ) should be as follows:
{{cmduser|cat debian/config/i386/config debian/config/i386/config.thinkpad > ../src-copy/.config}}
Basically the redirection was left out. the purpose of this step is to cat the split config files
into a single config file so it can be tweaked with menuconfig. notice if you dont put the redirection
in there ( the arrow) , you will get an error on the command because the 3rd file doesnt exist.-----end Edit

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 ==
* [[Installing Ubuntu 8.04 (Hardy Heron) on a Thinkpad T60]]
* [[How to reduce power consumption]]
* [[How to get special keys to work]]

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

== External links ==
* [https://wiki.ubuntu.com/ThinkFinger Ubuntu ThinkFinger Wiki]
* [https://help.ubuntu.com/community/SynapticsTouchpad Ubuntu Synaptics Touchpad Help]

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

Iwl3945

2008-03-05T00:47:07Z

Jaskiern: Defined the purpose of the driver.

The '''iwl3945''' driver is part of the [[iwlwifi]] project to provide support for the [[Intel PRO/Wireless 3945ABG Mini-PCI Express Adapter]].

== See also ==
* [[Ipw3945]]

[[Category:Iwlwifi]]

Iwl4965

2008-03-05T00:45:56Z

Jaskiern:

The '''iwl4965''' driver is part of the [[iwlwifi]] project to provide support for the [[Intel PRO/Wireless 4965AGN Mini-PCI Express Adapter]].

== See also ==
* [[Ipw4965]]

[[Category:Iwlwifi]]

Iwlwifi

2008-03-05T00:44:45Z

Jaskiern:

Intel Wireless WiFi Link drivers for Linux, or '''iwlwifi''', which provides official, Open support for wireless Intel adapters. Initially, it only supported [[Intel PRO/Wireless 3945ABG Mini-PCI Express Adapter]] and [[Intel PRO/Wireless 4965AGN Mini-PCI Express Adapter]]. More wireless projects are planned to move to this project in the future.

The driver works out of the box '''with''' a hardware firmware replacement. Full documentation and source is available on this newer driver.

== Notes ==
The previous Intel Wifi driver was named "[[ipw]]".

== Availability ==
The [[iwl3945]] driver  was integrated into Linux-2.6.24.

== External links ==
* [http://intellinuxwireless.org/ Official website]

Iwl4965

2008-03-04T17:06:29Z

Jaskiern: Added link to Ipw project.

== See also ==
* [[Ipw4965]]

[[Category:Iwlwifi]]

Iwl3945

2008-03-04T17:06:15Z

Jaskiern: Added link to Ipw project.

== See also ==
* [[Ipw3945]]

[[Category:Iwlwifi]]

Installing Ubuntu 7.04 (Feisty Fawn) on a ThinkPad T61

2008-03-04T17:04:40Z

Jaskiern: /* WiFi */

On the T61, [[Installing_Ubuntu_7.10_(Gutsy_Gibbon)_Release_Candidate_on_a_ThinkPad_T61|Ubuntu 7.10 (Gutsy Gibbon)]] is recommended instead of 7.04 because video drivers and wifi, among other issues, work by default.
recomended

===My DVD drive/CD burner/DVD burner doesn't work (Solved)===

Follow these instructions to enable your [http://en.wikipedia.org/wiki/Optical_drive optical drive]:<br>
1) Reboot your T61. Press the ThinkVantage button quickly when you see the ThinkPad screen and then press F1 enter [http://en.wikipedia.org/wiki/BIOS BIOS].<br>
2) In BIOS, select Configure -> Serial ATA.<br>
3) Now, select Compatibility instead of AHCI.<br>
4) Exit BIOS and start your computer normally.<br>
5) Go to Places -> Computer, right-click your CD-ROM/DVD/etc. drive, and select Properties. Then, go to Drive -> Settings. Set the mount point to ''cdrom'' (regardless of whether it's a CD-ROM drive, DVD drive, etc.).

----

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

----

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

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

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

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

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

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

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

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

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

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

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

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

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

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

# your addition
deb http://archive.ubuntu.com/ubuntu gutsy main restricted universe multiverse
deb-src http://security.ubuntu.com/ubuntu gutsy main restricted universe multiverse
</pre>
* Now run:
<pre>
sudo apt-get update
</pre>
{{HINT|If you get an error while trying to update, it may be because your apt cache is too small. To fix this add the following to your "/etc/apt/apt.conf.d/70debconf":
<pre>
APT::Cache-Limit "118388608";
</pre>--[[User:Thefekete|Thefekete]] 04:14, 19 September 2007 (UTC)}}
*Then Run:
<pre>
sudo apt-get -t gutsy install xserver-xorg-video-intel
sudo apt-get -t gutsy install linux
sudo apt-get -t gutsy install libgl1-mesa-dri
</pre>
* Now reboot.

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

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

{{HINT|If you experience problems with totem or other gstreamer apps crashing, try this:
<pre>
$ gstreamer-properties
</pre>
* Then under the "Video" tab, change the Output Plugin to "X Window System (No Xv)"
This will run the video through you processor, but won't crash gstreamer. --[[User:Thefekete|Thefekete]] 04:14, 19 September 2007 (UTC)}}

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

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

Create the data directory and set your fingerprint:
<pre>
sudo mkdir /etc/pam_thinkfinger
sudo tf-tool --add-user <username>
</pre>

To get be asked to swipe your finger when logging in or sudoing
<pre>
sudo modprobe uinput
</pre>
To make sure it works after reboot add "uinput" to the list in /etc/modules.

It will all be setup. (I found this somewhere on the web, I wish I could give a source but I'm afraid I cant find it, thank you Anonymous!).

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

Assuming that the (improved) hdaps code bundled with tp_smapi is being used, editing the transform_axis function in tp_smapi-0.32/hdaps.c will allow for the proper operation of the accelerometer. Assuming that the accelerometer is rotated 90 degrees from its proper orientation (as it is with the X61), the following code will suffice:

<pre>
static void transform_axes(int *x, int *y)
{
int temp = *x;
*x = -*y;
*y = temp;
}
</pre>

For those paying attention in linear algebra, this corresponds to a linear transformation that rotates a 2D coordinate system 90 degrees.
--[[User:Mbsullivan|Mbsullivan]] 04:21, 27 August 2007 (UTC)

Instead of editing the code, you can just pass the invert=1 parameter when loading the module; modprobe hdaps invert=1
--[[User:Vegar|Vegar]] 14:40, 17 September 2007 (UTC)

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

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

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

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

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

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

===Keyboard/Apostrophe issues (Solved)===
When installing with the alternate CD, Ubuntu asks you if your keyboard as a character that appears to be a quotation mark (this character: "). If you're using a US English keyboard, say no; the character is actually an umlaut. [[User:SteveSims|SteveSims]] 02:15, 19 August 2007 (UTC)

My apostrophe key outputs ´ instead of '. I went to System -> Preferences -> Keyboard and could not figure out how to fix it. [[User:SteveSims|SteveSims]] 21:50, 11 August 2007 (UTC)

:Try switching your keyboard layout to US-Classic, and putting it on the top of the list. After you do that, it works perfectly. --[[User:Adamacious|Adamacious]] 04:29, 13 August 2007 (UTC)

::There is no "US Classic" option. Here's what I have:<br>
[[Image:Keyboard_options.png]]<br>
[[User:SteveSims|SteveSims]] 02:17, 15 August 2007 (UTC)

:::It started working, even though I changed nothing. I'm running it as a Macintosh US English keyboard. [[User:SteveSims|SteveSims]] 17:20, 15 August 2007 (UTC)

::::Sorry Steve, what you had to do (and what you did) is select US English, as in the header in the list. It doesn't look selectable, but it is.--[[User:Adamacious|Adamacious]] 20:02, 22 August 2007 (UTC)

===Audio===
====Fixed in Gutsy====
As of 29 August 2007 and [https://bugs.launchpad.net/bugs/122560 this issue], the 2.6.22-10 kernel in Gutsy Gibbon supports audio out-of-the-box (as well as WiFi and other things). Installing the Gutsy kernel via apt and rebooting fixed audio for me, both speakers and headphones. Remaining issues:

* The mute button mutes audio, but doesn't unmute. Pressing volume up or down does unmute it, but has no effect on volume.
* KMix's system tray volume control has no effect because it thinks it's setting the headphones while both outputs are using the speaker settings, but opening KMix and setting the PCM volume works. --lgarfiel

====Python script fix (slightly easier fix)====
First, you have to download the source for the [http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.22.5.tar.gz latest Linux kernel] (2.6.22-5 as of August 26th, 2007) and compile it, something most users cannot do. However, you won't have to compile ALSA and its modules from source if you do it this way.

1) Download the [http://launchpadlibrarian.net/8899521/t61_audio_hack.py T61 audio hack] from [[Launchpad]]. Move it to a convenient folder (e.g., not your desktop).<br>
2) Go to System -> Preferences -> Sessions -> Startup Programs -> Add.<br>
3) Name it whatever you want. Choose something simple like "Python audio fix."<br>
4) Go to Command, and enter the following (with quotation marks):
<pre>gksudo <nowiki>"[THE FOLDER THAT T61_AUDIO_HACK.PY IS IN]</nowiki>/t61_audio_hack.py"</pre>
For example, on my computer, I put t61_audio_hack.py into the /fixes folder in my home folder, so I entered:
<pre>sksudo "/home/sims/fixes/t61_audio_hack.py"</pre> into the Command textbox.<br>
5) Log out, log back in, and type your password quickly when prompted the second time.

References:
[https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/122560 Launchpad Bug #122560]
[https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/133105 Launchpad Bug #133105]

====ALSA driver update (hard fix, recommended for advanced users)====

:'''''Note: This section assumes a high level of technical proficiency. Please fix it.'''''
::*<s>At [http://www.alsa-project.org www.asla-project.org], did you download only alsa-driver-1.0.14? That and alsa-lib-1.0.14a?</s>
:::Download alsa-driver, alsa-kernel, alsa-lib, and alsa-utils, according to [http://alsa.opensrc.org/index.php/AlsaCVS http://alsa.opensrc.org/index.php/AlsaCVS]. Other sources, however, say only the driver is necessary. Perhaps alsa-project.org simply recommends the other two?
::*''How'' did you compile it from source? ''How'' did you add the patch?
::*In short, please explain ''how'' you did these things in addition to just telling us ''what'' you did. I´m not trying to be rude but seriously, not all Linux users are programmers ;). Thanks. [[User:SteveSims|SteveSims]] 22:19, 11 August 2007 (UTC)
After upgrading to 1.0.14 I still had no sound, and this took about a week to solved (though it was so sadly obvious though). Just upgrading to alsa 1.0.14 will not be enough, there were a few patches released right after the release that fix the Thinkpad's. The reason I missed this was because it was the same day so the release of 1.0.14!

---------------------------------------------------------------------------
VERY SIMPLE METHOD OF MAKING SOUND WORK
http://forums.fedoraforum.org/showthread.php?t=159516&page=1&pp=15
Just follow the instructions step by step, except for two small things:
When doing "cp ../patch_analog.c alsa-driver-1.0.14/alsa-kernel/pci/hda/" use "cp ../patch_analog.c alsa-kernel/pci/hda/" instead
Also, when you get to the part about modifying the modprobe.conf file, it doesn't exist in ubuntu. Adding "options snd-hda-intel index=0 model=thinkpad" to any file (even one you make yourself) inside etc/modprobe.d should work. I personally added it to the options file, and it works fine.

-credit for the guide goes to ciphermonk, and credit to the small changes needed to make this work on ubuntu go to my friend John.

-hotkeys control mic volume, not speaker volume for some reason. I do not know how to fix this
-- If you're using Gnome, from the System menu, click Preferences -> Sound, and in the Default Mixer Tracks field, choose PCM.

-this fix should provide sound for both headphones and speakers.

-this edit by fatalchaos
---------------------------------------------------------------------------------------

First make sure these packages are installed (System -> Administration -> Synaptic Package Manager) : automake, autoconfig, cvs, libtool, python-dev, build-essential

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

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

'''Please use CVS version of ALSA instead. All of these patches are committed'''. The link to the CVS version of ALSA is dead[http://alsa.opensrc.org/index.php/AlsaCVS].

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

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

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

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

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

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

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

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

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

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

#!/bin/sh

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

# remove USB 1.1 driver
rmmod uhci_hcd
rmmod ehci_hcd

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

# switch to console
FGCONSOLE=`fgconsole`
chvt 6

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

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

# reload USB 1.1 driver
modprobe uhci_hcd
modprobe ehci_hcd

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

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

{{HINT| "The problem with this suspend script is, that after resuming, the laptop is incredibly slow. Applications start about 20 seconds, Firefox is lagging." Solution: Use latest nvidia drivers (.19)}}

This X-slow-after-resume is still here (T61p, nVidia Quadro FX 570 M, bleeding edge Gutsy 2.6.22-10-generic kernel). However, I found an official OpenSuSE 10.3 for this problem:
[https://bugzilla.novell.com/show_bug.cgi?id=290385]
--[[User:Lech|Lech]] 21:20, 2 September 2007 (UTC)

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

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

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

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

----
We are having similar discussions in Ubunutu's Launchpad, and we found kind of a solution which rules out any 2D/3D graphics acceleration but allows to suspend/resume, at least on my 3 weeks old T61p and some other recent T6x/R6x models:

With thinkpad_acpi 0.16 (!) patches applied to 2.6.22 kernel, and with VESA driver only, it works perfectly so far for us.

The discussion and some links can be found at:
https://bugs.launchpad.net/ubuntu/+bug/139089
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/129125

I know it's not eye candy not to have satisfying GLX etc., but I consider working suspend/resume much more important than say playing with GoogleEarth.

--[[User:Lech|Lech]] 14:48, 16 September 2007 (UTC)

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

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

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

It works fine on mine and I have built-in graphics on my motherboard. [[User:SteveSims|SteveSims]] 02:19, 15 August 2007 (UTC)

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

=== yet another idea ===

You can add the Gnome power manager brightness applet to the gnome panel, which gives you a GUI tool to do the job, rather than hardware buttons. I don't know about KDE or other window managers. --[[User:Atoponce|Atoponce]] 13:07 22, Aug 2007

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

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

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

Next, install xbacklight.

sudo apt-get install xbacklight

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

To automate brightness changes, first enable laptop-mode

sudo nano /etc/default/acpi-support

Scroll to the bottom and change ENABLE_LAPTOP_MODE to true

ENABLE_LAPTOP_MODE=true

Set laptop mode to start automatically

sudo update-rc.d laptop-mode multiuser

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

CONTROL_BRIGHTNESS=1

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

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

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

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

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

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

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

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

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

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

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

==Bluetooth==
works for me (TM)

==USB==
A short time after the system has booted, I get a message on the console of every window indicating IRQ# 23 has fired but noone is expecting it. After this message, the USB ports on the right side fail to work anymore. It was suggested on a forum that they will work, its just it takes it a long time to discover there is a new device. I looked in /proc and determined that the bluetooth device is using IRQ23, so it may be involved, but there may be sharing so it could be something else. Regardless, there are USB bus problems with the T61 and linux.

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

==Discussion==
In case you missed it the discussion page (for questions/responses) is right here: [[Talk: Installing Ubuntu 7.04 (Feisty Fawn) on a ThinkPad T61]]

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

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

Installing Fedora 7 on a ThinkPad T60

2008-03-04T17:02:50Z

Jaskiern: /* Wireless LAN */

Created by: [[User:spot|TomCallaway]] 09:45, March 20, 2007

===Abstract===

This article describes how I got Fedora 7 installed on my IBM/Lenovo ThinkPad T60. Now, I know that Fedora 7 isn't out yet, so this information is specific to the test releases. When Fedora 7 comes out, I'll update this page to reflect any changes.

===My ThinkPad===

These are the specifications of my machine.

* Lenovo ThinkPad T60 (6369-CTO)
* [[Intel Core 2 Duo (Merom)]] T7200 @ 2.00GHz
* [[Intel Graphics Media Accelerator 950]]
* [[Ethernet Controllers#Intel Gigabit (10/100/1000)|Intel Gigabit Ethernet Controller]]
* [[Intel PRO/Wireless 3945ABG Mini-PCI Express Adapter]]
* Integrated Bluetooth.
* [[Integrated Fingerprint Reader]]
* 100 GB - Serial ATA-150 Hard Drive.
* 15.4" TFT display with 1680x1050 resolution (widescreen)
* Intel 82801G (ICH7 Family) High Definition Audio Controller (rev 02)

===What Works?===

* Fedora
* Most of the function keys, except the ones mentioned below
* The fingerprint reader.
* Video, 2D and 3D.
* Brightness, Volume and Mute with OSD (On-Screen Display).
* ThinkLight, TrackPoint II and the touchpad.
* Bluetooth
* Infrared
* Suspend

===What Doesn't Work? (Known Issues)===

* Modem
* Hibernate

===Kernel Drivers===

The laptop uses the following hardware specific kernel drivers:

* [[iwl3945]] (wireless)
* e1000 (ethernet)
* snd_hda_intel (sound)
* nsc_ircc (infrared)

===Installing Fedora===

I really have no interest in dual-booting my laptop. There are plenty of good guides to setting up a computer for dual-boot on the internet. I burned a copy of the FC 6.91 DVD iso, booted off of it, and told the installer to delete all existing partitions. The install went off without a hitch. After installation, I ran yum update, and rebooted into the new kernel.

If you have problem booting up the fedora 7 DVD, and getting a blue screen at the start. Then install by text mode and update as root. "yum update" - And remember to change the line: "d:3:initdefault:" in the fil /etc/inittab into: "d:5:initdefault:" if you like to boot into an grafic mode.

===Post Install===
The Fedora repositories have some useful packages for ThinkPads. After I installed the OS, I used yum to install the following packages:

* thinkfinger: Support for the Fingerprint Reader
* tpb: ThinkPad button support utility and onscreen display
* beryl-gnome: Eyecandy!
* iwlwifi-firmware: The firmware for the new intel wireless driver
* xbindkeys: A utility to help us bind the "special" thinkpad keys
* xorg-x11-drv-i810: Driver for the Intel Graphics Chipsets

===Wireless LAN===
The latest Fedora 7 kernels include a new driver for the Intel 3945 chipset, called [[iwl3945]] ([[iwlwifi]]). This driver works, but it is a bit new, so you must be patient with it. If you didn't install the iwlwifi-firmware package, do so now. The kernel should have detected the wireless device, and configured iwlwifi for you.

Step 1: Turn on the radio
Make sure the switch on the front is pushed to the right (you should be able to see green on the left). Then, as root, run:

: {{cmdroot| /sbin/ifconfig wlan0 up}}

Step 2: Scan for access points
Even if you know the ESSID, the iwlwifi driver needs to also be told the frequency and access point that you want to connect to. Hopefully, this will be fixed in a later revision of the driver.

As root, run:
: {{cmdroot| /sbin/iwlist wlan0 scanning}}

You should see something like:

<pre>
Cell 03 - Address: 00:01:02:03:04:05
ESSID:"freewifi"
Mode:Master
Frequency:2.462 GHz
Signal level=-80 dBm
Encryption key:on
Extra:tsf=000000deadb33fabc
Extra:bcn_int=100
Extra:rssi=-80
Extra:capab=0x0411
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s
</pre>

Assuming that's the AP we want to connect to, note the Frequency, Address, and ESSID.

Step 3: Tell wlan0 about our AP
Now, we just need to configure wlan0 to find our AP:
As root, run:

: {{cmdroot| /sbin/iwconfig wlan0 freq 2.462G}}
: {{cmdroot| /sbin/iwconfig wlan0 ap 00:01:02:03:04:05}}
: {{cmdroot| /sbin/iwconfig wlan0 essid "freewifi"}}

Step 4: Get an IP Address
Assuming the wireless network is DHCP, as root, run:

: {{cmdroot| /sbin/dhclient wlan0}}

Now your wireless is up and running!
(Note: Your mileage may vary. There are lots of bug reports against iwlwifi. Maybe it is only a problem with NetworkManager, but my experience is that Fedora 7 test 4 (6.93) has unworkable wifi out of the box, at least on a T60p with an ipw3945.)
As of 15 June 2007, NetworkManager still doesn't work very well with the iwlwifi device.
There is a discussion on this on the fedora test list, starting with
https://www.redhat.com/archives/fedora-test-list/2007-April/msg00539.html

===Bluetooth===
Bluetooth works out of the box, but Gnome GUI only provides limited functionality (like Obex file transfers).
To configure bluetooth serial ports (those are used to connect to internet via Your bluetooth enabled mobile phone, to use bluetooth GPS devices etc), You have to manually tweak {{path|/etc/bluetooth/rfcomm.conf}} file.

At first run:
: {{cmduser| hcitool scan}}

The output should be something like
<pre>
Scanning ...
00:0A:D9:ED:89:4E Anttix P900
</pre>

Note the MAC address of Your phone, then run:
: {{cmduser| sdptool browse MAC_ADDRESS_OF_YOUR_PHONE}}

Find modem channel by looking for an entry like this:
<pre>
Service Name: Dial-up Networking
Service Description: Dial-up Networking
Service Provider: Sony Ericsson
Service RecHandle: 0x10001
Service Class ID List:
"Dialup Networking" (0x1103)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 7
Language Base Attr List:
code_ISO639: 0x656e
encoding: 0x6a
base_offset: 0x100
Profile Descriptor List:
"Dialup Networking" (0x1103)
Version: 0x0100
</pre>

Now edit {{path|/etc/bluetooth/rfcomm.conf}}.
Uncomment the lines for rfcomm0 and replace MAC and channel numbers with the ones from Your phone.
Also make sure to turn on automatic binding on startup.
The final config will look like this:
<pre>
rfcomm0 {
# Automatically bind the device at startup
bind yes;

# Bluetooth address of the device
device 00:0A:D9:ED:89:4E;

# RFCOMM channel for the connection
channel 7;

# Description of the connection
comment "My GSM Dialup Networking";
}
</pre>

Restart bluetooth subsystem:

{{cmdroot|service bluetooth restart}}

Now run network configuration tool, add a new modem to device {{path|/dev/rfcomm0}} and configure an internet connection as usual. The phone number depends on Your phone make, but most of the time it's <code>*99#</code>. You might also need to add additional modem initialization string <code>AT+cgdcont=1,"IP","internet",,0,0</code> to configure Your GPRS service name.

Make sure that Gnome bluetooth applet is running. If not, run it by typing bluetooth-applet.

Activate the connection. You should be prompted for PIN by both: the phone and the applet. Enter the same number on both sides to pair the connection.

===Infrared===
T60 has an NSC FIR chip. The driver needs to know a Dongle ID so it must be manually configured.

Edit {{path|/etc/modprobe.conf}}, add the following two lines:
<pre>
alias irda0 nsc-ircc
options nsc-ircc dongle_id=0x09
</pre>

Edit {{path|/etc/sysconfig/irda}}:
<pre>
IRDA=yes
DEVICE=irda0
DISCOVERY=yes
</pre>

Start IRDA

{{cmdroot|service irda start}}

If You want IRDA to be enabled during system boot, turn it on like this:

{{cmdroot|chkconfig irda on}}

===Getting the ThinkVantage Buttons to work===

Fedora does not recognize all the ThinkVantage buttons correctly by default. This can be fixed quite easily. Just edit /etc/X11/Xmodmap.

Then paste the following in the file:

<pre>
keycode 234 = XF86Back
keycode 233 = XF86Forward
keycode 159 = XF86Start
keycode 162 = XF86AudioPlay
keycode 164 = XF86AudioStop
keycode 153 = XF86AudioNext
keycode 144 = XF86AudioPrev
keycode 227 = XF86LaunchF
keycode 249 = XF86ZoomIn
</pre>

Save and close the file, then logout and back in again. You can now assign the buttons to do anything you want. For example, use the Back and Forward buttons (next the cursor keys) to flip desktops using the cube effect in Beryl (set this using the Beryl settings manager). You can set most of the other keys using Gnome vis System - Preferences - Keyboard Shortcuts.

For the ThinkVantage and Zoom buttons, I used xbindkeys. Open a terminal and type:

: {{cmduser| xbindkeys --defaults > ~/.xbindkeysrc}}
: {{cmduser| xbindkeys-config}}

Click "New" and assign a remark to the new shortcut. Then press "Grab" and press the combination you want (ex: The ThinkVantage button). You can then set the action you want executed in the "Action" field.

=== Video Drivers ===

====Intel Graphics Media Accelerator 950 (GMA950)====
Since the Fedora installer didn't detect the graphics device properly, it uses the Vesa driver. Which works, but that's not really what we want to use. After installing the xorg-x11-drv-i810 package, I edited the /etc/X11/xorg.conf, and changed the driver from "vesa" to "intel". Then, restart X. That's it.

====ATI Mobility Radeon X1300 (M52) & X1400 (M54)====
ATI's drivers did not work with Fedora 7 because they couldn't handle the xorg version there. Version 8.39.4, and above, are compatible with Fedora 7. Matching kernel modules are provided by the livna repository.

: {{cmdroot| rpm -i http://rpm.livna.org/livna-release-7.rpm}}
: {{cmdroot| yum install kmod-fglrx}}
: at least for teh X1400, an aticonfig --overlay-type=Xv was necessary to prevent a number of odd display issues.

===The Fingerprint Reader===

Thanks to the efforts of the ThinkFinger guys, the fingerprint reader works very well in Linux using entirely Free Software. After installing thinkfinger, you need to edit /etc/pam.d/system-auth as root (be careful!):

Above the line that reads:

<pre>
auth sufficient pam_unix.so nullok try_first_pass
</pre>

Add a new line that reads:

<pre>
auth sufficient pam_thinkfinger.so
</pre>

So, the auth section of your /etc/pam.d/system-auth file should look like:

<pre>
auth required pam_env.so
auth sufficient pam_thinkfinger.so
auth sufficient pam_unix.so nullok try_first_pass
auth requisite pam_succeed_if.so uid >= 500 quiet
auth required pam_deny.so
</pre>

Save the updated /etc/pam.d/system-auth, then as root, run:

: {{cmdroot| /usr/sbin/tf-tool --add-user spot}}

Of course, if your username isn't spot, change it! It will prompt you to swipe your finger over the reader three times.

Thats it! Now, you can login using either a password or a fingerprint.

===Beryl - eyecandy===
Beryl is shiny desktop eyecandy. To get it running, you can follow the steps here:
http://wiki.beryl-project.org/wiki/Install/Fedora_Core

===Suspend===
Create a new file {{path|/etc/rc.modules}} and put the following lines into it:
<pre>
# Turn on correct suspend flags for T60
echo 3 > /proc/sys/kernel/acpi_video_flags
</pre>
Then make it executable:

{{cmdroot|chmod 755 /etc/rc.modules}}

After reboot the machine should suspend and wake up fine.

NOTE: I have tried the above with FC7 and T60p and still have not gotten suspend to work. It worked out of the box on FC6. I have also added the following lines to the kernel parameters but with no luck. pci=noacpi acpi_sleep=s3_bios,s3_mode.
Note: as of 2.6.22.9-91.fc7, with the ATI M1400 the suspend or hibernate crash just after the suspending console's message.

===Thanks===
Much credit goes to [[User:Keithvassallo|Keithvassallo]] for his [http://thinkwiki.org/wiki/Installing_Ubuntu_6.10_%28Edgy_Eft%29_on_a_ThinkPad_T60 Installing Ubuntu Edgy Eft on the Thinkpad T60] page.

==References==
* This guide is listed at the [http://tuxmobil.org/ibm.html TuxMobil Linux laptop and notebook installation guides survey (IBM/Lenovo)].

[[Category:T60]]
[[Category:Fedora]]

Installing Debian Lenny on a ThinkPad T61

2008-03-04T17:01:36Z

Jaskiern: /* WiFi: Intel 4965AGN */

== Hardware ==

ThinkPad T61 7663-13G

== Overview ==

== Kernel Configuration ==
* Version: 2.6.22

=== SATA Issues ===
Currently, SATA mode is set to "Compatibility" in the BIOS and I'm using the ATA_PIIX driver, which finds both the hard and the cdrom drive. In AHCI mode, the cdrom is not found. I haven't found any information on that, yet.

Running in the AHCI mode worked for me - the hard drive showed up as /dev/sda and the cdrom as /dev/hda. K3b finds it and uses it fine.

=== IRQ Issues ===
Occasionally, I get messages like
<pre>
irq 23: nobody cared (try booting with the "irqpoll" option)
[<c>] __report_bad_irq+0x24/0x80
[<c0156b11>] note_interrupt+0x251/0x290
[<c0155d65>] handle_IRQ_event+0x25/0x50
[<c015725b>] handle_fasteoi_irq+0xbb/0xf0
[<c0106bfb>] do_IRQ+0x3b/0x70
[<c0104b53>] common_interrupt+0x23/0x28
[<f>] acpi_processor_idle+0x21e/0x3e2 [processor]
[<f>] acpi_processor_idle+0x0/0x3e2 [processor]
[<c>] cpu_idle+0x84/0xe0
[<c0387a3f>] start_kernel+0x2ef/0x370
[<c03871f0>] unknown_bootoption+0x0/0x260
=======================
handlers:
[<f888b530>] (usb_hcd_irq+0x0/0x60 [usbcore])
Disabling IRQ #23
</pre>

Unfortunately, adding irqpoll to the boot command line only leads to frequent losses of Ethernet connectivity.

==== Temporary Workaround ====
When the message appears, USB devices will start to behave weird (USB keyboards & mice lag etc). Unloading and loading ehci-hcd fixes this problem, for now.

==== Temporary Workaround 2 ====
Adding noirqdebug to the kernel commandline at least removes the messages. Let's hope for a BIOS update from Lenovo.

==== Eventual Solution ====
With the BIOS version 2.07-1.08, the IRQ handling issues are gone, the "noirqdebug" commandline options can be removed.

=== Custom Patches ===
ThinkPad ACPI Extras v0.15-20070723 ([http://ibm-acpi.sf.net/]). With the latest version, brightness control works under X11.

== Sound: AD1984 ==
I checked out both alsa-driver and alsa-kernel from the repositories ([http://www.alsa-project.org/download.php]) and built the modules for my kernel. After installation, sound (both headphone jack & internal speakers) works just fine. Haven't checked the MIC yet.

Debian users (both Stable/Etch and Testing) can use the small script [http://www.klabs.be/~fpiat/linux/debian/Lenny_on_Thinkpad_T61/#Sound 2] i wrote to patch and build an alsa module package (with module-assistant). --Fpiat 00:52,20 August 2007 (UTC)

With kernel 2.6.23, the workarounds above are not needed any more. --[[User:TorstenMarek|TorstenMarek]] 11:17, 27 September 2007 (UTC)

== Graphics: ==
===NVidia Quadro NVS 140M ===
* Driver: nvidia
* Version: 100.14.11

The Debian packages work just fine. There seem to be some (known) issues with framebuffers console. OpenGL applications and games work just fine, Darwinia ([http://darwinia.co.uk Darwinia] and Defcon ([http://www.everybody-dies.com]) run smoothly at 1440x900.

I installed the drivers using ENVY. It worked, just download the latest package at http://www.albertomilone.com/nvidia_scripts1.html, and run it, the driver's installation it's quite easy.

==== Problems ====

With 100.14.09 and RenderAccel/Compositing, I occasionally got hard locks after a couple of minutes, not even SysRq can reboot the machine. Only the NumLock LED is blinking, and no suspicious entries are in the logs. With 100.14.11 and no RenderAccel, the lockups are less frequently. I'm still trying to figure out which configuration makes them go away.

* I've tried to pci=nommcconf on the kernel commandline, didn't help.

With 100.14.19, the lockups seem to be a thing of the past.

===Intel 965GM===
* Driver: intel

For versions of the intel driver earlier than 2.1.1, the following is required for proper display scaling:

<pre>
Section "Monitor"
Identifier "TV"
Option "Ignore" "true"
EndSection

Section "Monitor"
Identifier "Generic Monitor"
Option "DPMS"
DisplaySize 332 207
EndSection
</pre>

This bug was fixed in xf86-video-intel 2.1.1.

== WiFi: Intel 4965AGN ==

With kernel 2.6.24RC3 the driver comes part of the kernel and does not need manual installation. You still have to copy and install the firmware though.

* Driver: [[iwl4965]]
* Version: 0.0.34

Since mac80211 is already a part of 2.6.22, only the [http://intellinuxwireless.org/?p=iwlwifi iwlwifi module] needs to be compiled. Following the instructions in the source package was sufficient. The module loads & finds some hardware and I can successfully scan for networks. Connecting to our local WiFi access point using WPA works just fine.

:How did you get this to work? I am following the INSTALL file to the letter, and I'm getting errors. Thanks. Aug 21, 2007 02:38 UTC [[user:Atoponce|Atoponce]]

Installation of linux-image-2.6.22-2-686 along with linux-headers-2.6.22-2-686 works with mac80211 8.0.2 patched in (from the mac80211-8.0.2 directory: ln -s /lib/modules/$(uname -r)/build /lib/modules/$(uname -r)/source; make patch_kernel), iwlwifi-4965-ucode-4.44.17 and iwlwifi-0.0.42. Steps for installation are given below.

If you haven't installed the unstable 2.6.22-2-686 kernel yet that needs to be done and reboot into it. Remember to add unstable or sid to your sources.list.

{{cmdroot|aptitude install linux-image-2.6.22-2-686}}

{{cmdroot|reboot}}

Now install the headers and build/install the driver.

{{cmdroot|aptitude install linux-headers-2.6.22-2-686}}

{{cmdroot|ln -s /lib/modules/$(uname -r)/build /lib/modules/$(uname -r)/source}}

{{cmdroot|cd}}

{{cmdroot|wget http://intellinuxwireless.org/mac80211/downloads/mac80211-8.0.2.tgz}}

{{cmdroot|wget http://intellinuxwireless.org/iwlwifi/downloads/iwlwifi-4965-ucode-4.44.17.tgz}}

{{cmdroot|wget http://intellinuxwireless.org/iwlwifi/downloads/iwlwifi-0.0.42.tgz}}

{{cmdroot|tar xzf mac80211-8.0.2.tgz}}

{{cmdroot|tar xzf iwlwifi-4965-ucode-4.44.17.tgz}}

{{cmdroot|iwlwifi-0.0.42.tgz}}

{{cmdroot|cd mac80211-8.0.2}}

{{cmdroot|make; make patch_kernel}}

{{cmdroot|cd ../iwlwifi-0.0.42.tgz}}

{{cmdroot|make; make install}}

{{cmdroot|cp iwlwifi-4965-ucode-4.44.17/*.ucode /lib/firmware}}

{{cmdroot|modprobe iwl4965}}

This same procedure should work with amd64 kernels with the obvious change to the linux-image and linux-header package installations above. The procedure should also work for the 3945 card provided you've removed the ipw3945 drivers before running the modprobe line.

== WiFi: ThinkPad 11a/b/g Wi-Fi wireless LAN Mini-PCIe US/EMEA/LA/ANZ (Atheros) ==

Using madwifi which is very easy or downloading the modules from the page and usig ndviswrapper(not recommended, uncharted waters). Just add
"deb ftp://ftp.au.debian.org/debian unstable main contrib non-free"
"deb-src ftp://ftp.au.debian.org/debian unstable main contrib non-free"
to the repositories in /etc/apt/sources.list and;

then as root:
# apt-get update
# apt-get install madwifi-source
# apt-get install madwifi-tools
# m-a prepare
# m-a a-i madwifi

then its all done, worked for me. For more information http://madwifi.org/

== Bluetooth ==
My Logitech Bluetooth mouse works.

== Fingerprint Sensor ==
Works with [http://thinkfinger.sourceforge.net ThinkFinger].

==References==
* This guide is listed at the [http://tuxmobil.org/ibm.html TuxMobil Linux laptop and notebook installation guides survey (IBM/Lenovo)].

{{T61}}

Fglrx

2008-03-03T02:49:36Z

Jaskiern: r300 is not a graphics driver.

{| width="100%"
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__
|style="vertical-align:top" |

'''Fglrx''' is a proprietary, Linux binary-only driver for ATI graphic chips with support for 3D acceleration.

<adsense></adsense>
|}

== Packages ==
The ATI drivers have explicit permission for repackaging and redistribution of the Linux drivers. Many distributions are supported within the installer, and many more repackaged by external developers. Please visit the [http://wiki.cchtml.com/index.php/Category:Distributions Distribution Page at the Unofficial ATI driver Wiki]

*{{Debian}}
** These packages have been added to Debian unstable as <tt>fglrx-driver</tt>, so you can now apt-get them and use module-assistant to install.
** If you are on stable sarge with backport's kernel 2.6.15, download ATI's installer, let it build Debian packages and proceed as usual. There's a [http://jroller.com/page/erAck?entry=lot_day_6_2_fglrx detailed description] available.
** [http://wiki.cchtml.com/index.php/Debian_Installation_Guide Debian Howto]
*{{SUSE}} packages: http://www.suse.de/~sndirsch/ati-installer-HOWTO.html
*{{Gentoo}} {{cmdroot|emerge ati-drivers}}
*{{Fedora}} 4 packages: http://rpm.livna.org
** For stock Fedora kernels: {{cmdroot|yum install kernel-module-fglrx-$(uname -r) ati-fglrx }}
** For custom-compiled kernels: see [[How to build custom packages for fglrx]]
*{{Fedora}} 5 packages: http://rpm.livna.org
** For stock Fedora kernels: {{cmdroot|yum install xorg-x11-drv-fglrx}}
** For custom-compiled kernels: see [[How to build custom packages for fglrx]]
*{{Fedora}} 7 packages: http://rpm.livna.org
** The newest version of the driver (8.39.4) is supposed to work with Fedora 7, and is available from Livna.
*{{Arch Linux}}
:{{cmdroot|pacman -S ati-fglrx}} (kernel module for 2.6.15-ARCH)
:{{cmdroot|pacman -S ati-fglrx-archck}} (kernel module for 2.6.15-archck)
:{{cmdroot|pacman -S ati-fglrx-utils}} (xorg7 stuff and tools)
*{{Ubuntu}}
**[http://wiki.cchtml.com/index.php/Ubuntu_Dapper_Installation_Guide Dapper Drake Howto]
**[http://wiki.cchtml.com/index.php/Ubuntu_Breezy_Installation_Guide Breezy Badger Howto]
**[http://wiki.cchtml.com/index.php/Ubuntu_Edgy_Installation_Guide Edgy Eft Howto]
**[http://wiki.cchtml.com/index.php/Ubuntu_Feisty_Installation_Guide Feisty Fawn Howto]
**[http://wiki.cchtml.com/index.php/Ubuntu_Gutsy_Installation_Guide Gutsy Howto]
**[http://wiki.cchtml.com/index.php?title=Ubuntu_Hardy_Installation_Guide Hardy Howto]

== Building for Xorg 7.0==
To compile fglrx versions <= 8.24.8 for Xorg 7.0.0, fake Xorg 6.9.0 by
:{{cmdroot|1=export X_VERSION=x690; sh ati-driver-installer-8.24.8-x86.run}}
Next, move the various resulting libraries and modules from /usr/X11R6 to /usr/lib/xorg

In {{path|/usr/src/ATI}} additional sources are installed for fireglcontrol and fgl_glxgears

== Status ==
Current version: 8.1 (8.454) (18st January 2008).
Major changes:
* [https://a248.e.akamai.net/f/674/9206/0/www2.ati.com/drivers/linux/catalyst_81_linux.html 8.1]: Fixed suspending on kernel version 2.6.23 or later. Custom code in xorg.conf will no longer be ignored.
* [http://www2.ati.com/drivers/linux/catalyst_712_linux.html 7-12]: FireGL support, fixed memory leak when running OpenGL applications, X -configure no longer results in a segmentation fault. Connecting a display device that supports 1680x1050 may result in a maximum display resolution of 1280x1024 only being available.
* [http://www2.ati.com/drivers/linux/catalyst_711_linux.html 7-11]: new versioning scheme, kernel 2.6.23 support. Required for Xorg server 1.4, but does not support FireGL cards. So don't upgrade to Xorg 1.4 if you have one!
* 8.42.3: Composite support added enabling AIGLX and Beryl/Compiz on the desktop. Support for (most?) FireGl cards dropped (should be restored in upcoming versions)
* 8.41.7: increased OpenGL performance on some Radeon Cards, size/position TV-out adjustments work for Radeon X1900 or higher, X crash when connecting external DFP display fixed
* 8.40.4: some new TV out control options in CCC, another (non-exciting) maintenance release (see [http://www.phoronix.com/scan.php?page=article&item=804&num=1 Phoronix])
* 8.39.4: kernel 2.6.22 support, TexturedVideo fix, aticonfig segfault fix (see 8.38.7 hotfix), to get rid of the "AMD Testing use only" logo, use [http://www.phoronix.com/forums/showpost.php?p=10641&postcount=44 this] workaround.
* 8.38.7: hotfix release for "Using aticonfig --initial segfaults destroying xorg.conf file when run in X with Vesa driver.", search for "737-28261" on the ATI website.
* 8.38.6: RedHat Enterprise Linux 5 support, Xserver crashes on moving video window between two monitors fixed, corruption when playing multiple vodeps with textured video fixed
* 8.37.6: Xorg Server 1.3 support, CCC 1.0, crash when logging off from X fixed, Xv cropping bug fixed
* 8.36.5: Kernel 2.6.20 support, CCC Beta 0.9 with localization
* 8.35.5: Beta AMD Catalyst Control Center, X-Server termination from console does not result in a blank screen. Kernel 2.6.20 requires some patching (see [[Problems_with_fglrx#fglrx_8.35.5|fglrx patches section]]).
* 8.34.8: Radeon Xpress 1250 support, X-Video on x86_64 fix, hibernation mode fix. Kernel 2.6.20 requires some patching (see [[Problems_with_fglrx#fglrx_8.34.8|fglrx patches section]]).

== Known problems and solutions ==
See [[Problems with fglrx]].

== User experience ==
=== Speed ===
How much is the speed gain versus the opensource drivers?

Compared to the old drivers, approximately 40% speed gain have been noticed with fglrx. However, there are issues with freezing/garbage after suspend, garbage when resizing desktop (via {{key|ctrl}}{{key|alt}}{{key|plus}}, {{key|ctrl}}{{key|alt}}{{key|minus}}), and garbage while using VMware. The current 8.14.13 has shown 400% improvement over using the open source radeon driver: 1200 FPS for glxgears{{footnote|1}}!

However the situation seems to be changing significantly as time goes on. With recent x11-drm-20060608 driver (gentoo) and thinkpad t42 (ati 9600) the speed is confirmed as 1900fps and stable. As of October 2007 there is dramatic improvement in the open source 3d drivers in speed and stability.

=== 3D acceleration ===

According to [http://xoomer.alice.it/flavio.stanchina/debian/fglrx-installer.html#configure Flavio's page] you need these options:

Section "Module"
...
Load "GLcore"
Load "glx"
Load "dri"
...
EndSection

# Of course you need to activate the driver
Section "Device"
...
Driver "fglrx"
EndSection

Don't forget to load the module <tt>fglrx</tt> (<tt>modprobe fglrx</tt>). Under Debian the module can be placed in <tt>/etc/modules</tt>.

With fglrx drivers prior to 8.42.3 will need to disable composite to enable 3D DRI acceleration. To do this, add an extra Extensions section (if necessary) containing:

Section "Extensions"
Option "Composite" "Disable" #make DRI work with fglrx.
EndSection

If you are unsure whether you have DRI running, issue <tt>glxinfo | grep -i direct</tt> after disabling composite. Note, this

{{NOTE|1=Video overlay acceleration may be disabled when 3D acceleration is enabled. The following comment from the xorg.conf file bundled with the fglrx driver indicates that:
# === OpenGL Overlay ===
# Note: When OpenGL Overlay is enabled, Video Overlay
# will be disabled automatically
Option "OpenGLOverlay" "1"
However, you can use either regular Xv video overlay or make the video an opengl texture and let the OpenGL engine scale your video. This has nothing to do with the acceleration of 2D drawing primitives. Further, your mileage on performance may vary depending on what card you have. The open source drivers don't support newer cards, while the ATI drivers don't support older cards.

You may be able to preserve VideoOverlay acceleration if you explicitly remove the OpenGLOverlay using:

Option "VideoOverlay" "True" and Option "OpenGLOverlay" "False". See [http://xoomer.alice.it/flavio.stanchina/debian/fglrx-installer.html#configure Flavio's page] for detail.}}

=== Power saving ===
Power saving is much better than with the <tt>radeon</tt> driver, but doesn't work in dual-screen configuration (see [[How to make use of Graphics Chips Power Management features]]).

=== Suspending with fglrx ===

On a ThinkPad T42 with Kernel 2.6.19 with Software Suspend 2 and R60 with Kernel 2.6.18-suspend2-r1 (Gentoo) , the following addition to <tt>/etc/hibernate/suspend2.conf</tt> is required:

# For fglrx
ProcSetting extra_pages_allowance 20000

=== Display Switching (Dynamic Display Management) ===

Version 8.25.18 introduces a new feature: Dynamic Display Management. It allows display switching on-the-fly.

To list all connected and enabled monitors:
:{{cmdroot|1=aticonfig --query-monitor}}

To switch displays:
:{{cmdroot|1=aticonfig --enable-monitor=STRING,STRING}}, where STRING can be: none, lvds, crt1, crt2, tv, tdms1, tdms2

Only 2 displays can be enabled at the same time. Any displays that are not on the list will be disabled.

Using an [[Script for Dynamic Display Management with fglrx|ACPI script]], aticonfig can be used to switch displays on a key press.

The '''Catalyst Control Center''', which comes with the driver (at least from Livna in Fedora Core 6) can be used to do this switching. It also does various other kinds of display managements. However, the version that comes with 8.39.4 doesn't seem to handle switching into Big Desktop mode, does anyone know how to get this to work? The control center also complains a lot about rebooting, but rebooting doesn't seem to be required. Does anyone have decent documentation for the control center?

== Useful links ==
* [http://www.ati.com/products/catalyst/linux.html ATI Linux Driver FAQ]
* [http://www.rage3d.com/content/articles/atilinuxhowto/ ATI Radeon Linux How-To]
* [http://www.rage3d.com/board/forumdisplay.php?f=61&daysprune=30&order=asc&sort=title Rage3D Linux Discussion Forum]
* [http://www.driverheaven.net/forumdisplay.php?f=103 Radeon Driver Forum at Driverheaven]
* [http://odin.prohosting.com/wedge01/gentoo-radeon-faq.html Gentoo ATI Radeon FAQ]
* [http://forums.gentoo.org/viewtopic-t-374745-highlight-t42+ati+dri.html Gentoo T42 ATI. DRI + xorg driver]
* [http://ati.cchtml.com/ Unofficial community ATI bugzilla] - tracks bugs in the driver. Might be monitored by ATI ([http://www.rage3d.com/board/showpost.php?p=1333438751&postcount=386], [http://www.rage3d.com/board/showpost.php?p=1333439009&postcount=390]).

== ThinkPads that may be supported ==
Supported chips, as found in select IBM ThinkPads:
{{NOTE|fglrx version 8.29.6 discontinued support for Radeon 9200 and earlier.}}
* [[ATI Mobility FireGL 9000]]
** {{T40p}}
* [[ATI Mobility FireGL T2]]
** {{R50p}}
** {{T41p}}, {{T42p}}
* [[ATI Mobility FireGL V3200]]
** {{T43p}}
* [[ATI Mobility Radeon 9000]]
** {{R50}}, {{R51}}
** {{T40}}, {{T41}}, {{T42}}
* [[ATI Mobility Radeon 9600]]
** {{T42}}
* [[ATI Mobility Radeon X300]]
** {{R52}}
** {{T43}}
** {{Z60m}}
* [[ATI Mobility Radeon Xpress 200M]]
** {{R51e}}
* [[ATI Mobility Radeon X600]]
** {{Z60m}}
* [[ATI Mobility Radeon X1400]]
** {{T60}}, {{R60}}, {{Z61m}}
* [[ATI Mobility FireGL V5200]]
** {{T60p}}, {{Z61p}}

== ThinkPads that are NOT supported by fglrx==
Unsupported chips, as found in select IBM ThinkPads:
* [[ATI Mobility Radeon 7500]]
** {{R40}}
** {{T30}}
** {{T41}}
** {{T42}}

{{footnotes|
#Note that glxgears isn't a benchmark tool, it's so simple that its FPS values is without any meaning... you can only compare glxgears using the same drivers/machine, if you change any of then you can have higher/lower values and in real life programs/games happen to have the opposite effects. Think in terms of a car engines rpms: higher rpms in the same car usually means a faster car, change anything and it's meaningless, ie: gears, truck, wheel size, etc. make it useless.
}}

== See also ==
* [[radeon]]

== External links ==
* [http://ati.amd.com/support/drivers/linux/linux-radeon.html Official website]

[[Category:Drivers]]

TurboCache

2008-03-02T09:41:59Z

Jaskiern:

nVidia's product name for their GPUs that utilize a combination of shared (system memory) and dedicated (onboard the video card) memory.

== See also ==
* [[HyperMemory]]

HyperMemory

2008-03-02T09:40:52Z

Jaskiern:

ATI's product name for their GPUs that utilize a combination of shared (system memory) and dedicated (onboard the video card) memory.

== See also ==
* [[TurboCache]]

ATI Mobility Radeon X300

2008-03-02T09:39:19Z

Jaskiern: Rewording.

__NOTOC__
{| width="100%"
|style="vertical-align:top" |
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;">

This is an ATI video adapter

== Features ==
* Chipset: ATI M22
* PCI ID: 1002:5460
* PCI Express x16
* 32 or 64MB GDDR1 on-chip video memory
* [[HyperMemory]] can use system memory for graphics processing - 128MB or 256MB, depending on driver version. The original Windows driver used 128MB;later versions use up to 256MB. This may depend on the amount of RAM installed in the Thinkpad.
* "PowerPlay 4.0" technology for dynamic engine clock, memory clock and core voltage, refresh rate reduction and thermal status reporting.
</div>
|style="vertical-align:top" |
|}

== X.org drivers ==

The X.org [[radeon]] driver works well and support 2D acceleration and some other functionality such as basic power amangement. In conjunction with the [[r300]] DRI driver, [[radeon]] also provides 3D acceleration (the latter is not yet stable). ATI provides [[fglrx]], a closed-source Linux-only alternative which adds some functionality such as TV output and advanced power amangement (but has its own stability issues).

=== ThinkPad LCD ===
Display on the internal LCD works as long as you set the monitor settings correct.

=== External VGA port ===
There are known problems. Both the [[radeon]] and [[fglrx]] drivers turn off the switching between internal and external port.

==== <tt>vesa</tt> driver ====
Using the [[vesa]] driver built into X.org, mode switching modes. However, this loses acceleration and some capabilities.

==== <tt>radeon</tt> driver ====
On-the-fly swiching doesn't work. To activate both ports in clone mode with a reasonable CRT refresh rate, use the following in {{path|/etc/X11/xorg.conf}}:

Section "Device"
Identifier "Videocard0"
VendorName "Videocard vendor"
BoardName "ATI Radeon Mobility X300"

Driver "radeon"
Option "DynamicClocks" "on"

Option "MergedFB" "on"
Option "MonitorLayout" "LVDS, CRT"
Option "CRT2Hsync" "50-75"
Option "CRT2VRefresh" "50-82"
EndSection

Note that without the <tt>MonitorLayout</tt> option, if the external monitor is connected when X starts then the LCD will be deactivated and you will need to restart X.

(Tested wth Fedora Core 4 on ThinkPad {{T43}}).

See also the related discussion about [[Additional options for the radeon driver]].

==== [[fglrx]] driver ====
On-the-fly works with <tt>aticonfig</tt> in the newest Drivers, see [[Fglrx#Display_Switching_.28Dynamic_Display_Management.29|Display Switching]]. Additionally, to use both ports there is the possibility to either have the monitor connected during X startup, or force activation of both ports by adding
Option "ForceMonitors" "lvds,crt1"
to the <tt>Device</tt> section in your {{path|/etc/X11/xorg.conf}}. Powering the CRT port consumes 400-500mW, regardless of whether a CRT is attached.

=== S-Video port (TV-out) ===

Works with the <b>proprietary</b> [[fglrx]] driver (as of version 8.19.10). To activate, add
Option "ForceMonitors" "lvds,tv"
to the <tt>Device</tt> section in your {{path|/etc/X11/xorg.conf}} and restart X.

<s>It also might work with <b>opensource</b> [[R300]] and the [http://bugs.gentoo.org/show_bug.cgi?id=127642 following] patch </s><br>
Use xorg opensource [[R300]] driver version 6.7 and later in order to enable S-Video.

=== DVI port ===
Works fine with the [[RandR 1.2]] [[radeon]] driver. The DVI connector is available only through a docking station or port replicator.

== 3D acceleration ==
OpenGL 3D acceleration is provided by the proprietary [[fglrx]] driver (when DRI is enabled). Note that performance is affected by the power saving mode.

The open source <tt>r300</tt> [[DRM]] module also aims to provide 3D acceleration. This currently requires the CVS/GIT versions of [[X.org]], [[DRM]] and [[Mesa]], and has been observed to occasionally crash (e.g., when running Google Earth or <tt>ppracer</tt>on a {{T43}}). You can [[How to compile an experimental X server|install it experimentally]] for testing.

== Linux kernel Framebuffer driver ==

radeonfb might cause problems with hardware acceleration under X on some systems, vesafb and vesafb-tng on the other hand has been reported to work just fine.

== Clock rates, voltage and power==
{| border="1" cellspacing="0" cellpadding="2"
|+ Clock rates, voltages and power {{footnote|1}}
! Mode !! core freq !! memory freq !! voltage !! idle !! 3DMarks (Windows, 1600x1200, LCD only)
|-
| Performance || 300 || 230 MHz || 1.15V || 2.98 W || 8.28 W
|-
| Balanced || 183 || 210 MHz || 1.00V || 1.71 W || 3.88 W
|-
| Battery || 120 || 105 MHz || 1.00V || 1.61 W || 2.74 W
|}

{| border="1" cellspacing="0" cellpadding="2"
|+ ATI drivers for Windows {{footnote|2}} and [[fglrx]]
! Mode !! core freq !! memory freq
|-
| Performance || 297.00 || 229.50
|-
| Balanced || 209.25 || 182.25
|-
| Battery || 104.63 || 121.50
|}

Experimentally, the difference between the Performance and Battery settings under Linux with the <tt>radeon</tt> driver and <tt>DynamicClocks</tt> enabled is roughly 0.3W and 3-4 degrees in GPU temperature on a ThinkPad {{T43}}. Further frequency reduction leads to display flickering or corruption.

See [[How to make use of Graphics Chips Power Management features]] for details on how to control this using [[Rovclock]], [[How to make use of Graphics Chips Power Management features|<tt>DynamicClocks</tt> option to the <tt>radeon</tt> driver]] and or the [[fglrx]] driver.

Presently the lowest idle-mode power consumption is achieved using the proprietary [[fglrx]] driver and
# aticonfig --set-powerstate=1 --effective=now

== ThinkPads this chip may be found in ==
* {{R52}}
* {{T43}}
* {{Z60m}}

== External links ==
* [http://www.ati.com/products/radeonx300/specs.html ATI X300 specifications] from ATI
* [http://www.ati.com/products/embedded/mobilityradeonx300/M22-CSP64_Product_Snapshot.pdf "snapshot" data sheet] (refers to the 32MB on-chip, 128MB "HyperMemory" version).

{{footnotes|
#according to the [http://www.ati.com/products/embedded/mobilityradeonx300/M22-CSP64_Product_Snapshot.pdf "Snapshot" data sheet] (which refers to the 32MB on-chip, 128MB "HyperMemory" version)
#inspected using [http://www.pbus-167.com/chc.htm Notebook Hardware Control]
}}

[[Category:Components]]

ATI Mobility Radeon Xpress 200M

2008-03-02T09:37:12Z

Jaskiern: Reformatting.

__NOTOC__
{| width="100%"
|style="vertical-align:top" |
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;">

This is a ATI North Bridge with integrated video adapter

== Features ==
* Video Chipset: ATI ?
* Video PCI ID: 1002:5a62
* Video Memory: uses main memory (32MB up to 511MB main memory; 64MB over 511MB)
</div>
|style="vertical-align:top" |
|}

== Linux driver - OpenSource ==
The VESA driver in Xorg 6.8.2 works. When configured in Fedora Core 4, the hardware discovery did not work, therefore the screen was configured for 800x600 only. 

The "ati" driver in Xorg 7.0 worked fine under Gentoo Linux.

The [[radeon]] module works fine in X.Org 7.2 under openSUSE Linux 10.2.

Direct rendering (i.e., 3D acceleration) does not work, and is disabled explicitly in the driver. Look for this line in Xorg.0.log:

(II) RADEON(0): Direct rendering broken on XPRESS 200 and 200M

== Linux driver - Proprietary ==
{{Todo|?}}

The following combination of software is almost working for me:
* gentoo-sources-2.6.14-r2
* ati-drivers-8.19.10
* xorg-x11-6.8.2-r6

Xorg hangs up sometimes unless I disable glx and dri modules in xorg.conf .

Linux kernel 2.6.15 and ati drivers 8.20.8 work flawlessly. DRI is enabled and graphics is fast (for this videocard). fglrxconfig puts "GammaCorrection" options in xorg.conf and it sometimes messes up colors so it is better to comment them out. If colors are messed up for some reason anyway run fireglcontrol and click on TvOut tab, it should cure the problem. 

===For Fedora Core 5===
With GUI install
boot: linux vesa

Install kmod-fglrx from livna
#yum update kmod-fglrx

Install offical driver[Fake 690]
#X_VERSION=x690 ./ati-driver-installer-8.24.8-i386.run

Initial fglrx
#aticonfig --initial

Reboot
#reboot

== ThinkPads this chip may be found in ==
* {{R51e}}

[[Category:Components]]

ATI Mobility Radeon X1400

2008-03-02T09:25:58Z

Jaskiern:

Radeonhd

2008-03-02T09:24:45Z

Jaskiern: /* External links */

== External links ==
* [http://gitweb.freedesktop.org/?p=xorg/driver/xf86-video-radeonhd;a=summary Freedesktop summary]

Radeonhd

2008-03-02T09:24:19Z

Jaskiern: â†Created page with '== External links == * [http://gitweb.freedesktop.org/?p=xorg/driver/xf86-video-radeonhd;a=summary]'

== External links ==
* [http://gitweb.freedesktop.org/?p=xorg/driver/xf86-video-radeonhd;a=summary]

ATI Mobility Radeon X1300

2008-03-02T09:22:16Z

Jaskiern: /* Linux X.Org driver */

== Features ==
* Chipset: ATI M52
* PCI ID: 1002:7149
* PCI Express x16
* 64MB GDDR1 video memory

== Linux X.Org driver ==
Should be supported by the new (as of 2007-10-22) [[radeonhd]] driver. A Debian package already exists in the experimental branch. 3d is still under development.

== ThinkPad LCD ==
Display on the internal LCD works as long as you set the monitor settings correct.

== External VGA port ==
??

== SVideo port ==
??

== DVI port ==
DVI port is enabled in T60.

Using the proprietary driver the Dell 2405FPW works at 1920x1200 pixels via Advanced Mini Dock.

== Proprietary ATI driver ==
[[Fglrx]] supports this card since release 8.24.8.

driver by ATI

https://support.ati.com/ics/support/KBAnswer.asp?questionID=18875

== Linux kernel Framebuffer driver ==
* OS: RHEL4-U3
* Kernel: 2.6.9-34
* X Version: 6.8.2-1
* Result: ''Failure''
** Driver can't find a compatible card

== ThinkPads this chip may be found in ==
* {{T60}}

[[Category:Components]]

ATI Mobility Radeon 9600

2008-03-02T09:21:41Z

Jaskiern: Typo.

ATI Mobility Radeon 9600

2008-03-02T09:20:02Z

Jaskiern: Reformatting.

ATI Mobility Radeon 9000

2008-03-02T09:18:19Z

Jaskiern: Reformatting.

ATI Mobility Radeon 7500

2008-03-02T09:16:22Z

Jaskiern: Reformatting.

ATI Mobility Radeon 7000

2008-03-02T09:14:30Z

Jaskiern: Reformatting.

ATI Mobility FireGL V3200

2008-03-02T09:12:13Z

Jaskiern: Reformatting.

ATI Mobility FireGL T2

2008-03-02T09:10:06Z

Jaskiern: Reformatting and interwiki-linking.

__NOTOC__
{| width="100%"
|style="vertical-align:top" |
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;">

This is a ATI video adapter
== Features ==
* Chipset: ATI RV350 (M10) - Similar to [[ATI_Mobility_Radeon_9600|Radeon 9600]]
* PCI ID: 1002:4e54
* AGP 4X
* 128 MB DDR-SDRAM video memory
* External VGA up to: 2048x1536x16.7M at 75Hz
</div>
|style="vertical-align:top" |
|}

== Linux driver - OpenSource ==
This adapter is supported by recent versions of the [[radeon]] driver as found in X.Org and XFree86.

The Xorg 6.8.1 driver works (including suspend), but dualscreen is not working on some models. The Xorg 6.8.2 release has quite a few fixes for the driver, allowing dualscreen for example on a {{T42p}}.

External (VGA, DVI, SVideo) ??

== Linux driver - Proprietary ==
The [[fglrx]] driver adds 3D acceleration.

== ThinkPads this chip may be found in ==
* {{R50p}}
* {{T41p}}, {{T42p}}

[[Category:Components]]

ATI Mobility FireGL 9000

2008-03-02T09:08:50Z

Jaskiern: Interwiki link.

ATI Mobility FireGL 9000

2008-03-02T09:08:13Z

Jaskiern: Reformatting and interwiki-linking.

ATI Mobility FireGL 7800

2008-03-02T09:06:41Z

Jaskiern: Reformatting.

Installing Fedora 8 on a ThinkPad T60

2008-03-02T09:00:54Z

Jaskiern:

Meaning to get to this, but don't wait for me. Anyone doing a clean install should go ahead and fill this space. Here's the very short version:

I recently upgraded my T60 from F7 to F8, and that went smoothly.

Things mostly work when using the vesa driver for video. You can use the ATI driver if you want 3D, and that works great, but then suspend and resume stops working. I get a hang on suspend.

The free Intel WiFi driver works, but the status LED does not work.

What's your experience? --[[User:Whizkid|Whizkid]] 19:52, 16 November 2007 (UTC)

== Fresh install ==

I did a fresh install on my T60p, which I previously had Fedora Core 6 on.

Things worked quite well. The vesa driver is working OK over my ATI graphics card. The [[iwl3945]] module is working acceptably (and much less of a pain to keep up to date than the old ipw3945). However, sometimes I'm getting lost connections. I'll try to investigate.

Hibernate works, but is very slow. I haven't tried suspending. [[User:Pfps|Pfps]] 01:28, 5 February 2008 (CET)

--

I found that I was able to speed up suspending considerably in the 2.6.23.14-107_1.cubbi_tuxonice.fc8 kernel by adding the following line to my hibernate.conf:

ProcSetting no_multithreaded_io 1

I don't know why multithreaded i/o is so much slower, but this option helped dramatically. The only other snag is that the [[fglrx]] driver causes a temporary cpu lockup of about 11s. --[[User:Noahf|noah]] 04:25, 6 February 2008 (CET)

[[Category:T60]]
[[Category:Fedora Core 8]]

Installing Fedora 8 on a ThinkPad T60

2008-03-02T08:59:45Z

Jaskiern: /* Fresh install */

AD1981HD

2008-03-02T08:57:29Z

Jaskiern: Reformatting.

__NOTOC__
{| width="100%"
|style="vertical-align:top" |
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;">

This is a Analog Devices High-Definition Audio 1.0 controller

== Features ==
* Chipset: AD1981HD
* Interface: HD Audio 1.0
</div>
|style="vertical-align:top" |
|}
{{HINT|By default, the volume buttons on the laptop control the volume of the hardware while software mixers like alsamixer and aumix increase or decrease the volume relative to the hardware volume.}}
== Linux ALSA driver ==
=== Installation on Debian GNU/Linux ===
The AD1981HD installs by default in Debian. To get it to work type 'alsaconf' on the command line as the root user.

{{ cmdroot| alsaconf }}
{{HINT|To become root, type su at the command line.}}
=== Problems ===
* As of kernel 2.6.17, some users report a missing master volume control (e.g., with the T60p and Z60m), as described in this thread: http://www.mail-archive.com/alsa-user@lists.sourceforge.net/msg17089.html
: As of ALSA 1.0.13 the master volume has returned. Download the latest modules from your distrobution to fix this problem. Otherwise as a temporary fix add model=hp to the snd-hda-intel module option. This will return the master volume control to your control.
{{HINT|If you use Debian, edit /etc/modprobe.d/sound to change ALSA module options. }}
* If you experience crackling noises, this can be avoided by adding the position_fix=2 optional argument for the module.

* If you have problems recording audio, try selecting "Front Mic" as the capture device.
{{ NOTE | There have been reported problems using arecord while debugging, it's recommended to instead use Audacity. }}

* According to a bug in the BIOS, the modem disables the audio device too. If you are having problems with your soundcard and have disabled your modem, try re-enabling it. On some systems disabling the modem results in fixing some problems, so if you haven't disabled the modem, try it. On the T60p model, the in-kernel ALSA system will report "azx_get_response timeout"; re-enabling the modem fixed this issue and brought audio back. This also works for the X60s.
* Another bug seems to also exist when the Wireless LAN (sierra wireless card) is disabled in the BIOS. Re-enabling the Wireless LAN will enable sound.

* external / internal microphone does not work for me. see
https://bugtrack.alsa-project.org/alsa-bug/view.php?id=2449
https://bugtrack.alsa-project.org/alsa-bug/view.php?id=2736
(different laptops but same sound chip)

{{NOTE | This problem was fixed for me by specifying the model option to 'ref' for the snd-hda-intel module (see first problem). }}

== ThinkPads this chip may be found in ==
* {{R60}}, {{R60e}}
* {{T60}}, {{T60p}}
* {{X60}}, {{X60s}}
* {{Z60m}}, {{Z60t}}
* {{Z61m}}, {{Z61e}}

== Datasheets ==
* [http://www.analog.com/en/prod/0,2877,AD1981HD,00.html Analog Devices page for the AD1981HD]
* [http://www.analog.com/UploadedFiles/Data_Sheets/338118709AD1981HD_0.pdf Direct link to the AD1981HD datasheet]

[[Category:Components]]

Installing Fedora on a ThinkPad T60

2008-03-02T07:04:00Z

Jaskiern: /* ATI X1300 and ATI X1400 */

Creation timestamp: [[User:Whizkid|Whizkid]] 05:00, 6 February 2008 (CET)

This document is meant to be the definitive resource to getting the latest current release of Fedora running on a ThinkPad T60. I welcome improvements to the page, especially for hardware I don't have (video chips, WiFi cards, WWAN devices).

This document is current for Fedora 8. Fedora 9 Alhpa 1 has just been released, but we have a few months before that goes gold.

== Installation Methods ==
Every T60 has a drive that can read DVDs. Nothing else is needed during the install, and it's the method I'm documenting first. Other methods of installation are detailed on the Fedora web site. For a smaller download, you can use the LiveCD, but fewer packages are available until you connect to the Internet.

== Pre-installation ==
Fedora 8 does not have a method to shrink NTFS partitions during installation. You can use Knoppix or other LiveCD's to do that if you want to dual-boot. Links to pages on how to do that would be nice right about.... here.

Installation tips:
*Set the optical drive mode to High Performance during the installation to speed it up a little. To do that: Get into the BIOS. Select Config->Power->CDROM Speed->High.

== Installation Steps ==
For any disc, I recommend completing the media test at least once on each disc you burn. Anaconda is the name of Fedora's installer program.
=== Installation DVD ===
*Boot the DVD. Skip ahead to '''Anaconda'''.
=== Live CD ===
*Boot the CD. After some initialization, you are eventually presented with the login screen. Click '''Fedora Live''' or wait 60 seconds. You are presented with the GNOME desktop. Double-click the icon titled '''Install to Hard Drive'''. Continue to the next section.
=== Anaconda ===
*You are presented with a title screen and no instructions. (That's what we're here for!) Click Next.
*Select the installation language. Click Next. (Not presented if using LiveCD. It uses the current language.)
*Select your keyboard language. Click Next. The installer looks for existing installations. You are prompted to choose a clean installation or upgrade. I'm documenting a clean install. Click Next.
*You are asked how to partition your drive. The default is to remove existing Linux partitions. That's a fine choice. Turn on the Review check box to see how it will partition the drive if you're curious. Click Next.
*Confirm that you want to delete partitions.
If you checked the Review box above, you are presented with the new disk layout. Edit as you please then click Next.
*The installer looks for other installed operating systems. You are asked where the boot loader will be installed. If you want to keep ThinkVantage functionality, check '''Configure advanced boot loader options'''. You can change the label of the other operating systems on the drive and select a default OS. Click Next.
If you selected advanced option configuration, you are asked where the boot loader should be installed. Select the first sector of the boot partition, not the MBR, if you want ThinkVantage to work at startup, or if you want another OS to manage the boot process. Click Next.
*You are asked whether the wired Ethernet controller should be active on boot. Since I use mine with WiFi most of the time, I turn that off and set the hostname manually. Click Next. Click Continue to confirm no network devices at boot if asked.
*Select your time zone, choose whether or not the clock uses UTC and click Next.
*Enter your root password. Do it again. Click Next.
*If using the DVD, the installer looks for common installation packages. Since everything is out of date already, I turn off all options and customize later. Click Next. The installer checks dependencies.
*You are asked one last time to confirm installation. Nothing has yet been written to the disk and this is the last point you can abort installation without changing anything on the drive. Click Next.

The partition table is written, partitions are formatted, the install image is copied and packages are installed. The disc is ejected and you are asked to reboot the machine. The process took 17 minutes on my T60 with a 2.0GHz Core Duo and 5400RPM hard drive with the DVD, or about 6 minutes using the LiveCD.

== First Boot ==
During the first boot, the system may wait a long time while trying to connect to a WiFi access point, even though your WiFi card may not have been detected by the installer.
*A welcome screen is presented. Your screen should now be in its native resolution. Click Forward.
*A license information screen is presented. Click Forward.
*Firewall configuration is presented. Configure as you like. Click Forward.
*SELinux setting is presented. Click Forward.
*Set your local date and time. Click Forward.
*Your hardware profile is shown. If you opt in and send your profile, your machine is counted by the Fedora team to get an idea of the population on which Fedora runs. Consider opting in to let them know we have these machines and want Fedora to run well on them. Click Forward.
*Create a user. Click Finish. Done!

== Get Updates ==
Get a network connection going and get all recent updates. Reboot if a new kernel is installed. I like to use NetworkManager.

=== Configuring NetworkManager ===
This section does not apply if you login using network authentication. NetworkManager is not perfect, and requires you to enter a keyring password at times, but it's a convenient way to connect to different networks, especially wireless networks.
*First make sure neither network device is enabled at boot time. Network devices that are enabled at boot time will attempt to get an IP address using DHCP by default. If you are near a secured WiFi hotspot, you will not get an IP address and the system will wait until it times out. Select System->Administration->Network. For each device listed, double-click it and turn off '''Activate device when computer starts'''. You may wish to enable '''Allow all users to enable and disable the device'''. Save changes and quit.
*Select System->Administration->Services. Check NetworkManager and NetworkManagerDispatcher and start each one. Save the configuration.
Your wired network will automatically connect and your wireless networks should now be visible.
To connect to a wireless network, click the NetworkManager notification icon and click the network to join.

Shortly after you connect to the internet, you should be notified that there are updates available. If you are asked for the install media, you can disable that repository.

== Device Configuration ==
=== Audio ===
The [[Intel 82801G HDA]] (ICH7 chipset) High Definition Audio Controller is identified and enabled automatically. The AD198x Analog PCM device works for audio. The Digital PCM device does not seem to work. Could it be that it only works in a dock?

=== Video Chip ===
==== ATI X1300 and ATI X1400 ====
Currently, Fedora does not include a driver specific to this card. It selects the '''vesa''' driver, which works fine, but performance is slow. The RadeonHD driver is in progress but also has no accelerated video modes, so is not a recommended option at this time.
ATI's proprietary [[fglrx]] driver now works very well for the T60. The easiest way to get the driver and have automatic updates is to use the Livna repository.
* Click the Fedora 8 repository from the front page of [http://rpm.livna.org].
* Let the Fedora package installer install the RPM package.
* Select Applications->Add/Remove Software.
* Under RPM Fusion - Nonfree, check Hardware Support.
* Click Optional packages.
* Check '''xorg-x11-drv-fglrx''', close and Apply.
* Reboot the machine and log in. (Logging out is not sufficient.)
At this point, you should have 2D and 3D acceleration working. This is while using the vesa driver:
$glxinfo | grep direct
direct rendering: No (...)
OpenGL renderer string: Mesa GLX Indirect
And while using the fglrx driver:
$glxinfo | grep direct
direct rendering: Yes
To disable the '''fglrx''' driver and use '''vesa''':
/usr/sbin/fglrx-config-display disable
and reboot. Use '''enable''' to switch back to the fglrx driver.
Fedora does not install any 3D software by default, but several titles are available in the repositories. Other third-party applications work well too, including Google Earth.

==== Intel video ====
=== WiFi ===
==== Intel PRO/Wireless 3945ABG ====
The [[Intel PRO/Wireless 3945ABG Mini-PCI Express Adapter]] is detected and enabled automatically. The activity indicator LED doesn't work with the standard driver. That appears to have been fixed in the latest version of the driver, but that is not yet in Fedora.

=== Pointing Devices ===
==== TrackPoint ====
The TrackPoint pointing device works automatically. Information on getting the middle button to act as a scroll wheel goes here.
==== Touch Pad ====
The touch pad is enabled and works automatically. Press-to-select is enabled by default.

=== Bluetooth ===
=== Fingerprint Reader ===
=== WWAN ===
==== Verizon EVDO ====
=== Special Keys ===
==== Fn+F2 Lock Screen ====
==== Fn+F3 Sleep ====
==== Fn+F4 Suspend to RAM (Standby) ====
Suspend to RAM works automatically. Closing the lid also put the machine into the same standby mode.

==== Fn+F5 Radio Control ====
==== Fn+F7 Display Selection ====
==== Fn+F8 Pointing Devices ====
==== Fn+F9 Eject ====
==== Fn+F12 Suspend to Disk (Hibernate) ====
Suspend to disk works automatically.

==== Fn+Home/End Brightness ====
Brightness control works automatically. GNOME's on-screen display for brightness works. When on AC, brightness is dimmed by default. To disable this, click System->Preferences->System->Power Management. Click the On Battery Power tab, and set the Dim display brightness by: slider to the desired amount.
==== Volume ====
Volume up, volume down and volume mute work automatically, as does the on-screen display.
==== ThinkVantage ====
This button doesn't do anything by default, and it's not obvious what it should do when running Linux, if anything.

=== Infrared ===

== Tuning ==
This section details how to tune your system for performance or battery life. These are the numbers I got from PowerTop (yum install powertop to install this handy tool).
{| border="1"
|+My power consumption
|-
!Description!!Wakes per second!!Wattage!!Estimated Time
|-
|Default - No changes||45000||27.8W||2.6Hr
|-
|Enable USB suspend||45000||27.8W||2.6Hr
|-
|Kill hald-addon-storage||45000||27.8W||2.6Hr
|-
|Increase writeback time||45000||27.8W||2.6Hr
|-
|Enable USB suspend||45000||27.8W||2.6Hr
|-
|Turn Bluetooth off||45000||27.8W||2.6Hr
|-
|Enable laptop mode||45000||27.8W||2.6Hr
|}
PowerTop didn't help at all this time. I was pretty sure it helped a lot when I installed from DVD. FIXME.

[[User:Pfps|Pfps]] 01:30, 28 February 2008 (CET) This very high number of wakeups is a problem that has been reported elsewhere, but I am not aware of any fix. My T60p does this sometimes. Sometimes it doesn't. I don't know why. Does anyone have any ideas?

[[Category:T60]]
[[Category:Fedora Core 8]]

ATI Mobility FireGL V5200

2008-03-02T07:02:32Z

Jaskiern: Add Wiki links.

__NOTOC__
{| width="100%"
|style="vertical-align:top" |
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;">

This is an ATI video adapter

== Features ==
* Chipset: ATI M56 - Similar to Radeon X1600
* PCI ID: 1002:71c4
* PCI Express x16
* 256 MB GDDR3-SDRAM video memory
</div>
|style="vertical-align:top" |
|}

=== Linux X.Org driver ===
Not supported by the Xorg [[radeon]] driver.

Should be supported by the new (as of 2007-10-22) [[radeonhd]] driver. A Debian package already exists in the experimental branch. 3d is still under development.
There is also a Gentoo ebuild recently added to the tree (x11-drivers/xf86-video-radeonhd), which seems to be working without any problems.

==== ThinkPad LCD ====
Display on the internal LCD works as long as you set the monitor settings correctly. Changing the driver from "ati" to "vesa" in xorg.conf will start X but with a lower resolution than expected.

Full resolution can be achieved when all modelines are removed and mode 1600x1200 with depth 24 is selected.

==== External VGA port ====
Yes

==== SVideo port ====
No

==== DVI port ====
No (yes on Docking Station, working with [[fglrx]] driver

=== Proprietary ATI driver ===
Proprietary [[fglrx]] driver works since version 8.25.18, version 8.24.8 works by adding "ChipID 0x71c5" to the xorg.conf "Device" statement and fooling it into thinking it's a X1600 mobility (do this only as a last resort or if you're sure you have an older driver; it is fatal to version 8.25.18).

The new driver 8.25.18 seems to support the card, see
https://support.ati.com/ics/support/KBAnswer.asp?questionID=1643
(successfully tested with the provided autorun installation script on OpenSuSE 10.1, T60p with 15" display).

(K)ubuntu 6.06 comes with this driver and it works out of the box. However, it seems to have problems with VT Switching (Alt+Fn). Instead of switching to a console, X resets and goes back to the log in screen (This doesn't happen when using the [[vesa]] driver). The switching issue might be resolvable by setting ENABLE_LAPTOP_MODE=true in /etc/default/acpi-support, but it doesn't seem to help on all systems.

Note: On Ubuntu 6.10 (Edgy) with 'splash' on the command line, you cannot switch to VTs. This is a Thinkpad T60. The screen remains graphical, but is very badly garbled. There is no text. X does not reset, and you can switch back to your X session. The solution is to include 'vga=791' or to remove 'splash' from the grub/lilo command line. You don't need to do both. (It's been a few days, so I don't remember where I found this...I just chanced upon this wiki page for the video card I'm trying to get working with xgl/AIGLX and Beryl).

Also, the pointer gets garbled sometimes in X, but this is only a minor annoyance. Dual Head (Xinerama) also works with this driver, but don't use KDE control center to enable it (use the ATi tool or edit xorg.conf manually)

I have a feeling that this card gets in the way when trying to suspend to RAM (resuming with a complete blank screen, lights are blinking, but that's it), but this can also be caused by other means.

=== Proprietary ATI driver on Ubuntu Feisty ===
I had a hard time getting resume from suspend-to-ram to work with Feisty on a Thinkpad T60p. When resuming, the screen just went black with X hanging.

It works like this:
# In <code>/etc/acpi/sleep.sh</code>, as second line, add the line <code>sudo chvt 1</code>. This forces a switch to the text console before standby.
# Likewise, in add to the very end of the file <code>/etc/acpi/resume.sh</code> the line <code>sudo chvt 7</code>.
# Finally, the perhaps most important change goes into <code>/etc/default/acpi-support</code>. Change the line <code>POST_VIDEO=true</code> to read <code>POST_VIDEO=</code>. This was the point when it started working on my system.

:'''NOTE:''' Step 3. above was the only change '''I''' needed to make. YMMV. --[[User:Brianfinley|Brian E. Finley]] 23:26, 30 March 2007 (CEST)

:'''NOTE:''' With only Step 3. above, my T60p would not even suspend when docked. Step 3. above was sufficient to make resume work for me when my laptop was not in its docking station. However, when I subsequently docked the machine I saw something I thought was banished with my upgrade to a 2.6.20 kernel: it uncermoniously powered off the instant it was docked, almost as though someone threw a hardware switch. --[[User:dave_abrahams|Dave Abrahams]] Thu Apr 12 11:18:22 EDT 2007

:'''UPDATE:''' The problems mentioned above related to docking seem to happen when I use the gnome-power-manager applet menu but not when I use the suspend function in the window that results from clicking the "Log Out Button" applet. When I use the latter, suspend-to-RAM seems to work right, consistently. I'm [https://bugs.launchpad.net/ubuntu/+bug/107674 following up with Ubuntu] on this point. --[[User:dave_abrahams|Dave Abrahams]] Thu Apr 19 11:53 GMT 2007

:'''NOTE:''' Editing <code>/etc/acpi/sleep.sh</code> and <code>/etc/acpi/resume.sh</code> is not necessary, as there is an option in <code>/etc/default/acpi-support</code> for ''that very feature'': Just set the commented out DOUBLE_CONSOLE_SWITCH=true, and it will do the console switch suggested automatically. --[[User:Webograph|Webograph]] 12:43, 29 August 2007 (UTC)

For completeness, here are the complete settings of this file:
<ol>
<li>ACPI_SLEEP=true</li>
<li>ACPI_HIBERNATE=true</li>
<li>ACPI_SLEEP_MODE=mem</li>
<li>MODULES=""</li>
<li>MODULE_WHITELIST=""</li>
<li>SAVE_VBE_STATE=true</li>
<li>VBE_STATE=/var/lib/acpi_support/vbestate</li>
<li>POST_VIDEO=</li>
<li>USE_DPMS=true</li>
<li># RADEON_LIGHT=true</li>
<li># DOUBLE_CONSOLE_SWITCH=true</li>
<li>HIBERNATE_MODE=shutdown</li>
<li>LOCK_SCREEN=true</li>
<li># DISABLE_DMA=true</li>
<li># RESET_DRIVE=true</li>
<li>STOP_SERVICES="mysql "</li>
<li>RESTART_IRDA=false</li>
<li>ENABLE_LAPTOP_MODE=true</li>
</ol>

Point 11 may eventually replace the chvt settings above, but I didn't try.

=== Linux kernel Framebuffer driver ===

Supported by the [http://dev.gentoo.org/~spock/projects/vesafb-tng/ vesafb-tng] project, but requires the boot parameter {{bootparm|video|vesafb:nocrtc}}.

Alternatively, you may use classic vesafb with {{bootparm|vga|838}} for a 1400x1050 screen with 32 bit color depth.

{{NOTE|The [[fglrx]] driver may cause distortion/corruption of the framebuffer after use at high resolutions, making the text difficult to read.}}

=== ThinkPads this chip may be found in ===
* {{T60p}}
* {{Z61p}}

[[Category:Components]]

Installing Fedora on a ThinkPad T60

2008-03-02T06:58:24Z

Jaskiern: Added a Wiki link.

Creation timestamp: [[User:Whizkid|Whizkid]] 05:00, 6 February 2008 (CET)

This document is meant to be the definitive resource to getting the latest current release of Fedora running on a ThinkPad T60. I welcome improvements to the page, especially for hardware I don't have (video chips, WiFi cards, WWAN devices).

This document is current for Fedora 8. Fedora 9 Alhpa 1 has just been released, but we have a few months before that goes gold.

== Installation Methods ==
Every T60 has a drive that can read DVDs. Nothing else is needed during the install, and it's the method I'm documenting first. Other methods of installation are detailed on the Fedora web site. For a smaller download, you can use the LiveCD, but fewer packages are available until you connect to the Internet.

== Pre-installation ==
Fedora 8 does not have a method to shrink NTFS partitions during installation. You can use Knoppix or other LiveCD's to do that if you want to dual-boot. Links to pages on how to do that would be nice right about.... here.

Installation tips:
*Set the optical drive mode to High Performance during the installation to speed it up a little. To do that: Get into the BIOS. Select Config->Power->CDROM Speed->High.

== Installation Steps ==
For any disc, I recommend completing the media test at least once on each disc you burn. Anaconda is the name of Fedora's installer program.
=== Installation DVD ===
*Boot the DVD. Skip ahead to '''Anaconda'''.
=== Live CD ===
*Boot the CD. After some initialization, you are eventually presented with the login screen. Click '''Fedora Live''' or wait 60 seconds. You are presented with the GNOME desktop. Double-click the icon titled '''Install to Hard Drive'''. Continue to the next section.
=== Anaconda ===
*You are presented with a title screen and no instructions. (That's what we're here for!) Click Next.
*Select the installation language. Click Next. (Not presented if using LiveCD. It uses the current language.)
*Select your keyboard language. Click Next. The installer looks for existing installations. You are prompted to choose a clean installation or upgrade. I'm documenting a clean install. Click Next.
*You are asked how to partition your drive. The default is to remove existing Linux partitions. That's a fine choice. Turn on the Review check box to see how it will partition the drive if you're curious. Click Next.
*Confirm that you want to delete partitions.
If you checked the Review box above, you are presented with the new disk layout. Edit as you please then click Next.
*The installer looks for other installed operating systems. You are asked where the boot loader will be installed. If you want to keep ThinkVantage functionality, check '''Configure advanced boot loader options'''. You can change the label of the other operating systems on the drive and select a default OS. Click Next.
If you selected advanced option configuration, you are asked where the boot loader should be installed. Select the first sector of the boot partition, not the MBR, if you want ThinkVantage to work at startup, or if you want another OS to manage the boot process. Click Next.
*You are asked whether the wired Ethernet controller should be active on boot. Since I use mine with WiFi most of the time, I turn that off and set the hostname manually. Click Next. Click Continue to confirm no network devices at boot if asked.
*Select your time zone, choose whether or not the clock uses UTC and click Next.
*Enter your root password. Do it again. Click Next.
*If using the DVD, the installer looks for common installation packages. Since everything is out of date already, I turn off all options and customize later. Click Next. The installer checks dependencies.
*You are asked one last time to confirm installation. Nothing has yet been written to the disk and this is the last point you can abort installation without changing anything on the drive. Click Next.

The partition table is written, partitions are formatted, the install image is copied and packages are installed. The disc is ejected and you are asked to reboot the machine. The process took 17 minutes on my T60 with a 2.0GHz Core Duo and 5400RPM hard drive with the DVD, or about 6 minutes using the LiveCD.

== First Boot ==
During the first boot, the system may wait a long time while trying to connect to a WiFi access point, even though your WiFi card may not have been detected by the installer.
*A welcome screen is presented. Your screen should now be in its native resolution. Click Forward.
*A license information screen is presented. Click Forward.
*Firewall configuration is presented. Configure as you like. Click Forward.
*SELinux setting is presented. Click Forward.
*Set your local date and time. Click Forward.
*Your hardware profile is shown. If you opt in and send your profile, your machine is counted by the Fedora team to get an idea of the population on which Fedora runs. Consider opting in to let them know we have these machines and want Fedora to run well on them. Click Forward.
*Create a user. Click Finish. Done!

== Get Updates ==
Get a network connection going and get all recent updates. Reboot if a new kernel is installed. I like to use NetworkManager.

=== Configuring NetworkManager ===
This section does not apply if you login using network authentication. NetworkManager is not perfect, and requires you to enter a keyring password at times, but it's a convenient way to connect to different networks, especially wireless networks.
*First make sure neither network device is enabled at boot time. Network devices that are enabled at boot time will attempt to get an IP address using DHCP by default. If you are near a secured WiFi hotspot, you will not get an IP address and the system will wait until it times out. Select System->Administration->Network. For each device listed, double-click it and turn off '''Activate device when computer starts'''. You may wish to enable '''Allow all users to enable and disable the device'''. Save changes and quit.
*Select System->Administration->Services. Check NetworkManager and NetworkManagerDispatcher and start each one. Save the configuration.
Your wired network will automatically connect and your wireless networks should now be visible.
To connect to a wireless network, click the NetworkManager notification icon and click the network to join.

Shortly after you connect to the internet, you should be notified that there are updates available. If you are asked for the install media, you can disable that repository.

== Device Configuration ==
=== Audio ===
The [[Intel 82801G HDA]] (ICH7 chipset) High Definition Audio Controller is identified and enabled automatically. The AD198x Analog PCM device works for audio. The Digital PCM device does not seem to work. Could it be that it only works in a dock?

=== Video Chip ===
==== ATI X1300 and ATI X1400 ====
Currently, Fedora does not include a driver specific to this card. It selects the '''vesa''' driver, which works fine, but performance is slow. The RadeonHD driver is in progress but also has no accelerated video modes, so is not a recommended option at this time.
ATI's proprietary '''fglrx''' driver now works very well for the T60. The easiest way to get the driver and have automatic updates is to use the Livna repository.
* Click the Fedora 8 repository from the front page of [http://rpm.livna.org].
* Let the Fedora package installer install the RPM package.
* Select Applications->Add/Remove Software.
* Under RPM Fusion - Nonfree, check Hardware Support.
* Click Optional packages.
* Check '''xorg-x11-drv-fglrx''', close and Apply.
* Reboot the machine and log in. (Logging out is not sufficient.)
At this point, you should have 2D and 3D acceleration working. This is while using the vesa driver:
$glxinfo | grep direct
direct rendering: No (...)
OpenGL renderer string: Mesa GLX Indirect
And while using the fglrx driver:
$glxinfo | grep direct
direct rendering: Yes
To disable the '''fglrx''' driver and use '''vesa''':
/usr/sbin/fglrx-config-display disable
and reboot. Use '''enable''' to switch back to the fglrx driver.
Fedora does not install any 3D software by default, but several titles are available in the repositories. Other third-party applications work well too, including Google Earth.

==== Intel video ====
=== WiFi ===
==== Intel PRO/Wireless 3945ABG ====
The [[Intel PRO/Wireless 3945ABG Mini-PCI Express Adapter]] is detected and enabled automatically. The activity indicator LED doesn't work with the standard driver. That appears to have been fixed in the latest version of the driver, but that is not yet in Fedora.

=== Pointing Devices ===
==== TrackPoint ====
The TrackPoint pointing device works automatically. Information on getting the middle button to act as a scroll wheel goes here.
==== Touch Pad ====
The touch pad is enabled and works automatically. Press-to-select is enabled by default.

=== Bluetooth ===
=== Fingerprint Reader ===
=== WWAN ===
==== Verizon EVDO ====
=== Special Keys ===
==== Fn+F2 Lock Screen ====
==== Fn+F3 Sleep ====
==== Fn+F4 Suspend to RAM (Standby) ====
Suspend to RAM works automatically. Closing the lid also put the machine into the same standby mode.

==== Fn+F5 Radio Control ====
==== Fn+F7 Display Selection ====
==== Fn+F8 Pointing Devices ====
==== Fn+F9 Eject ====
==== Fn+F12 Suspend to Disk (Hibernate) ====
Suspend to disk works automatically.

==== Fn+Home/End Brightness ====
Brightness control works automatically. GNOME's on-screen display for brightness works. When on AC, brightness is dimmed by default. To disable this, click System->Preferences->System->Power Management. Click the On Battery Power tab, and set the Dim display brightness by: slider to the desired amount.
==== Volume ====
Volume up, volume down and volume mute work automatically, as does the on-screen display.
==== ThinkVantage ====
This button doesn't do anything by default, and it's not obvious what it should do when running Linux, if anything.

=== Infrared ===

== Tuning ==
This section details how to tune your system for performance or battery life. These are the numbers I got from PowerTop (yum install powertop to install this handy tool).
{| border="1"
|+My power consumption
|-
!Description!!Wakes per second!!Wattage!!Estimated Time
|-
|Default - No changes||45000||27.8W||2.6Hr
|-
|Enable USB suspend||45000||27.8W||2.6Hr
|-
|Kill hald-addon-storage||45000||27.8W||2.6Hr
|-
|Increase writeback time||45000||27.8W||2.6Hr
|-
|Enable USB suspend||45000||27.8W||2.6Hr
|-
|Turn Bluetooth off||45000||27.8W||2.6Hr
|-
|Enable laptop mode||45000||27.8W||2.6Hr
|}
PowerTop didn't help at all this time. I was pretty sure it helped a lot when I installed from DVD. FIXME.

[[User:Pfps|Pfps]] 01:30, 28 February 2008 (CET) This very high number of wakeups is a problem that has been reported elsewhere, but I am not aware of any fix. My T60p does this sometimes. Sometimes it doesn't. I don't know why. Does anyone have any ideas?

[[Category:T60]]
[[Category:Fedora Core 8]]

Installing Fedora on a ThinkPad T60

2008-03-02T06:52:37Z

Jaskiern: Formatting.

Creation timestamp: [[User:Whizkid|Whizkid]] 05:00, 6 February 2008 (CET)

This document is meant to be the definitive resource to getting the latest current release of Fedora running on a ThinkPad T60. I welcome improvements to the page, especially for hardware I don't have (video chips, WiFi cards, WWAN devices).

This document is current for Fedora 8. Fedora 9 Alhpa 1 has just been released, but we have a few months before that goes gold.

== Installation Methods ==
Every T60 has a drive that can read DVDs. Nothing else is needed during the install, and it's the method I'm documenting first. Other methods of installation are detailed on the Fedora web site. For a smaller download, you can use the LiveCD, but fewer packages are available until you connect to the Internet.

== Pre-installation ==
Fedora 8 does not have a method to shrink NTFS partitions during installation. You can use Knoppix or other LiveCD's to do that if you want to dual-boot. Links to pages on how to do that would be nice right about.... here.

Installation tips:
*Set the optical drive mode to High Performance during the installation to speed it up a little. To do that: Get into the BIOS. Select Config->Power->CDROM Speed->High.

== Installation Steps ==
For any disc, I recommend completing the media test at least once on each disc you burn. Anaconda is the name of Fedora's installer program.
=== Installation DVD ===
*Boot the DVD. Skip ahead to '''Anaconda'''.
=== Live CD ===
*Boot the CD. After some initialization, you are eventually presented with the login screen. Click '''Fedora Live''' or wait 60 seconds. You are presented with the GNOME desktop. Double-click the icon titled '''Install to Hard Drive'''. Continue to the next section.
=== Anaconda ===
*You are presented with a title screen and no instructions. (That's what we're here for!) Click Next.
*Select the installation language. Click Next. (Not presented if using LiveCD. It uses the current language.)
*Select your keyboard language. Click Next. The installer looks for existing installations. You are prompted to choose a clean installation or upgrade. I'm documenting a clean install. Click Next.
*You are asked how to partition your drive. The default is to remove existing Linux partitions. That's a fine choice. Turn on the Review check box to see how it will partition the drive if you're curious. Click Next.
*Confirm that you want to delete partitions.
If you checked the Review box above, you are presented with the new disk layout. Edit as you please then click Next.
*The installer looks for other installed operating systems. You are asked where the boot loader will be installed. If you want to keep ThinkVantage functionality, check '''Configure advanced boot loader options'''. You can change the label of the other operating systems on the drive and select a default OS. Click Next.
If you selected advanced option configuration, you are asked where the boot loader should be installed. Select the first sector of the boot partition, not the MBR, if you want ThinkVantage to work at startup, or if you want another OS to manage the boot process. Click Next.
*You are asked whether the wired Ethernet controller should be active on boot. Since I use mine with WiFi most of the time, I turn that off and set the hostname manually. Click Next. Click Continue to confirm no network devices at boot if asked.
*Select your time zone, choose whether or not the clock uses UTC and click Next.
*Enter your root password. Do it again. Click Next.
*If using the DVD, the installer looks for common installation packages. Since everything is out of date already, I turn off all options and customize later. Click Next. The installer checks dependencies.
*You are asked one last time to confirm installation. Nothing has yet been written to the disk and this is the last point you can abort installation without changing anything on the drive. Click Next.

The partition table is written, partitions are formatted, the install image is copied and packages are installed. The disc is ejected and you are asked to reboot the machine. The process took 17 minutes on my T60 with a 2.0GHz Core Duo and 5400RPM hard drive with the DVD, or about 6 minutes using the LiveCD.

== First Boot ==
During the first boot, the system may wait a long time while trying to connect to a WiFi access point, even though your WiFi card may not have been detected by the installer.
*A welcome screen is presented. Your screen should now be in its native resolution. Click Forward.
*A license information screen is presented. Click Forward.
*Firewall configuration is presented. Configure as you like. Click Forward.
*SELinux setting is presented. Click Forward.
*Set your local date and time. Click Forward.
*Your hardware profile is shown. If you opt in and send your profile, your machine is counted by the Fedora team to get an idea of the population on which Fedora runs. Consider opting in to let them know we have these machines and want Fedora to run well on them. Click Forward.
*Create a user. Click Finish. Done!

== Get Updates ==
Get a network connection going and get all recent updates. Reboot if a new kernel is installed. I like to use NetworkManager.

=== Configuring NetworkManager ===
This section does not apply if you login using network authentication. NetworkManager is not perfect, and requires you to enter a keyring password at times, but it's a convenient way to connect to different networks, especially wireless networks.
*First make sure neither network device is enabled at boot time. Network devices that are enabled at boot time will attempt to get an IP address using DHCP by default. If you are near a secured WiFi hotspot, you will not get an IP address and the system will wait until it times out. Select System->Administration->Network. For each device listed, double-click it and turn off '''Activate device when computer starts'''. You may wish to enable '''Allow all users to enable and disable the device'''. Save changes and quit.
*Select System->Administration->Services. Check NetworkManager and NetworkManagerDispatcher and start each one. Save the configuration.
Your wired network will automatically connect and your wireless networks should now be visible.
To connect to a wireless network, click the NetworkManager notification icon and click the network to join.

Shortly after you connect to the internet, you should be notified that there are updates available. If you are asked for the install media, you can disable that repository.

== Device Configuration ==
=== Audio ===
The Intel 82801G (ICH7) High Definition Audio Controller is identified and enabled automatically. The AD198x Analog PCM device works for audio. The Digital PCM device does not seem to work. Could it be that it only works in a dock?
=== Video Chip ===
==== ATI X1300 and ATI X1400 ====
Currently, Fedora does not include a driver specific to this card. It selects the '''vesa''' driver, which works fine, but performance is slow. The RadeonHD driver is in progress but also has no accelerated video modes, so is not a recommended option at this time.
ATI's proprietary '''fglrx''' driver now works very well for the T60. The easiest way to get the driver and have automatic updates is to use the Livna repository.
* Click the Fedora 8 repository from the front page of [http://rpm.livna.org].
* Let the Fedora package installer install the RPM package.
* Select Applications->Add/Remove Software.
* Under RPM Fusion - Nonfree, check Hardware Support.
* Click Optional packages.
* Check '''xorg-x11-drv-fglrx''', close and Apply.
* Reboot the machine and log in. (Logging out is not sufficient.)
At this point, you should have 2D and 3D acceleration working. This is while using the vesa driver:
$glxinfo | grep direct
direct rendering: No (...)
OpenGL renderer string: Mesa GLX Indirect
And while using the fglrx driver:
$glxinfo | grep direct
direct rendering: Yes
To disable the '''fglrx''' driver and use '''vesa''':
/usr/sbin/fglrx-config-display disable
and reboot. Use '''enable''' to switch back to the fglrx driver.
Fedora does not install any 3D software by default, but several titles are available in the repositories. Other third-party applications work well too, including Google Earth.

==== Intel video ====
=== WiFi ===
==== Intel PRO/Wireless 3945ABG ====
The [[Intel PRO/Wireless 3945ABG Mini-PCI Express Adapter]] is detected and enabled automatically. The activity indicator LED doesn't work with the standard driver. That appears to have been fixed in the latest version of the driver, but that is not yet in Fedora.

=== Pointing Devices ===
==== TrackPoint ====
The TrackPoint pointing device works automatically. Information on getting the middle button to act as a scroll wheel goes here.
==== Touch Pad ====
The touch pad is enabled and works automatically. Press-to-select is enabled by default.

=== Bluetooth ===
=== Fingerprint Reader ===
=== WWAN ===
==== Verizon EVDO ====
=== Special Keys ===
==== Fn+F2 Lock Screen ====
==== Fn+F3 Sleep ====
==== Fn+F4 Suspend to RAM (Standby) ====
Suspend to RAM works automatically. Closing the lid also put the machine into the same standby mode.

==== Fn+F5 Radio Control ====
==== Fn+F7 Display Selection ====
==== Fn+F8 Pointing Devices ====
==== Fn+F9 Eject ====
==== Fn+F12 Suspend to Disk (Hibernate) ====
Suspend to disk works automatically.

==== Fn+Home/End Brightness ====
Brightness control works automatically. GNOME's on-screen display for brightness works. When on AC, brightness is dimmed by default. To disable this, click System->Preferences->System->Power Management. Click the On Battery Power tab, and set the Dim display brightness by: slider to the desired amount.
==== Volume ====
Volume up, volume down and volume mute work automatically, as does the on-screen display.
==== ThinkVantage ====
This button doesn't do anything by default, and it's not obvious what it should do when running Linux, if anything.

=== Infrared ===

== Tuning ==
This section details how to tune your system for performance or battery life. These are the numbers I got from PowerTop (yum install powertop to install this handy tool).
{| border="1"
|+My power consumption
|-
!Description!!Wakes per second!!Wattage!!Estimated Time
|-
|Default - No changes||45000||27.8W||2.6Hr
|-
|Enable USB suspend||45000||27.8W||2.6Hr
|-
|Kill hald-addon-storage||45000||27.8W||2.6Hr
|-
|Increase writeback time||45000||27.8W||2.6Hr
|-
|Enable USB suspend||45000||27.8W||2.6Hr
|-
|Turn Bluetooth off||45000||27.8W||2.6Hr
|-
|Enable laptop mode||45000||27.8W||2.6Hr
|}
PowerTop didn't help at all this time. I was pretty sure it helped a lot when I installed from DVD. FIXME.

[[User:Pfps|Pfps]] 01:30, 28 February 2008 (CET) This very high number of wakeups is a problem that has been reported elsewhere, but I am not aware of any fix. My T60p does this sometimes. Sometimes it doesn't. I don't know why. Does anyone have any ideas?

[[Category:T60]]
[[Category:Fedora Core 8]]

Installing Fedora on a ThinkPad T60

2008-03-02T06:44:21Z

Jaskiern: /* Intel PRO/Wireless 3945ABG */

Creation timestamp: [[User:Whizkid|Whizkid]] 05:00, 6 February 2008 (CET)

This document is meant to be the definitive resource to getting the latest current release of Fedora running on a ThinkPad T60. I welcome improvements to the page, especially for hardware I don't have (video chips, WiFi cards, WWAN devices).

This document is current for Fedora 8. Fedora 9 Alhpa 1 has just been released, but we have a few months before that goes gold.

=Installation Methods=
Every T60 has a drive that can read DVDs. Nothing else is needed during the install, and it's the method I'm documenting first. Other methods of installation are detailed on the Fedora web site. For a smaller download, you can use the LiveCD, but fewer packages are available until you connect to the Internet.

=Pre-installation=
Fedora 8 does not have a method to shrink NTFS partitions during installation. You can use Knoppix or other LiveCD's to do that if you want to dual-boot. Links to pages on how to do that would be nice right about.... here.

Installation tips:
*Set the optical drive mode to High Performance during the installation to speed it up a little. To do that: Get into the BIOS. Select Config->Power->CDROM Speed->High.

=Installation Steps=
For any disc, I recommend completing the media test at least once on each disc you burn. Anaconda is the name of Fedora's installer program.
==Installation DVD==
*Boot the DVD. Skip ahead to '''Anaconda'''.
==Live CD==
*Boot the CD. After some initialization, you are eventually presented with the login screen. Click '''Fedora Live''' or wait 60 seconds. You are presented with the GNOME desktop. Double-click the icon titled '''Install to Hard Drive'''. Continue to the next section.
==Anaconda==
*You are presented with a title screen and no instructions. (That's what we're here for!) Click Next.
*Select the installation language. Click Next. (Not presented if using LiveCD. It uses the current language.)
*Select your keyboard language. Click Next. The installer looks for existing installations. You are prompted to choose a clean installation or upgrade. I'm documenting a clean install. Click Next.
*You are asked how to partition your drive. The default is to remove existing Linux partitions. That's a fine choice. Turn on the Review check box to see how it will partition the drive if you're curious. Click Next.
*Confirm that you want to delete partitions.
If you checked the Review box above, you are presented with the new disk layout. Edit as you please then click Next.
*The installer looks for other installed operating systems. You are asked where the boot loader will be installed. If you want to keep ThinkVantage functionality, check '''Configure advanced boot loader options'''. You can change the label of the other operating systems on the drive and select a default OS. Click Next.
If you selected advanced option configuration, you are asked where the boot loader should be installed. Select the first sector of the boot partition, not the MBR, if you want ThinkVantage to work at startup, or if you want another OS to manage the boot process. Click Next.
*You are asked whether the wired Ethernet controller should be active on boot. Since I use mine with WiFi most of the time, I turn that off and set the hostname manually. Click Next. Click Continue to confirm no network devices at boot if asked.
*Select your time zone, choose whether or not the clock uses UTC and click Next.
*Enter your root password. Do it again. Click Next.
*If using the DVD, the installer looks for common installation packages. Since everything is out of date already, I turn off all options and customize later. Click Next. The installer checks dependencies.
*You are asked one last time to confirm installation. Nothing has yet been written to the disk and this is the last point you can abort installation without changing anything on the drive. Click Next.

The partition table is written, partitions are formatted, the install image is copied and packages are installed. The disc is ejected and you are asked to reboot the machine. The process took 17 minutes on my T60 with a 2.0GHz Core Duo and 5400RPM hard drive with the DVD, or about 6 minutes using the LiveCD.

=First Boot=
During the first boot, the system may wait a long time while trying to connect to a WiFi access point, even though your WiFi card may not have been detected by the installer.
*A welcome screen is presented. Your screen should now be in its native resolution. Click Forward.
*A license information screen is presented. Click Forward.
*Firewall configuration is presented. Configure as you like. Click Forward.
*SELinux setting is presented. Click Forward.
*Set your local date and time. Click Forward.
*Your hardware profile is shown. If you opt in and send your profile, your machine is counted by the Fedora team to get an idea of the population on which Fedora runs. Consider opting in to let them know we have these machines and want Fedora to run well on them. Click Forward.
*Create a user. Click Finish. Done!

=Get Updates=
Get a network connection going and get all recent updates. Reboot if a new kernel is installed. I like to use NetworkManager.
==Configuring NetworkManager==
This section does not apply if you login using network authentication. NetworkManager is not perfect, and requires you to enter a keyring password at times, but it's a convenient way to connect to different networks, especially wireless networks.
*First make sure neither network device is enabled at boot time. Network devices that are enabled at boot time will attempt to get an IP address using DHCP by default. If you are near a secured WiFi hotspot, you will not get an IP address and the system will wait until it times out. Select System->Administration->Network. For each device listed, double-click it and turn off '''Activate device when computer starts'''. You may wish to enable '''Allow all users to enable and disable the device'''. Save changes and quit.
*Select System->Administration->Services. Check NetworkManager and NetworkManagerDispatcher and start each one. Save the configuration.
Your wired network will automatically connect and your wireless networks should now be visible.
To connect to a wireless network, click the NetworkManager notification icon and click the network to join.

Shortly after you connect to the internet, you should be notified that there are updates available. If you are asked for the install media, you can disable that repository.

=Device Configuration=
==Audio==
The Intel 82801G (ICH7) High Definition Audio Controller is identified and enabled automatically. The AD198x Analog PCM device works for audio. The Digital PCM device does not seem to work. Could it be that it only works in a dock?
==Video Chip==
===ATI X1300 and ATI X1400===
Currently, Fedora does not include a driver specific to this card. It selects the '''vesa''' driver, which works fine, but performance is slow. The RadeonHD driver is in progress but also has no accelerated video modes, so is not a recommended option at this time.
ATI's proprietary '''fglrx''' driver now works very well for the T60. The easiest way to get the driver and have automatic updates is to use the Livna repository.
* Click the Fedora 8 repository from the front page of [http://rpm.livna.org].
* Let the Fedora package installer install the RPM package.
* Select Applications->Add/Remove Software.
* Under RPM Fusion - Nonfree, check Hardware Support.
* Click Optional packages.
* Check '''xorg-x11-drv-fglrx''', close and Apply.
* Reboot the machine and log in. (Logging out is not sufficient.)
At this point, you should have 2D and 3D acceleration working. This is while using the vesa driver:
$glxinfo | grep direct
direct rendering: No (...)
OpenGL renderer string: Mesa GLX Indirect
And while using the fglrx driver:
$glxinfo | grep direct
direct rendering: Yes
To disable the '''fglrx''' driver and use '''vesa''':
/usr/sbin/fglrx-config-display disable
and reboot. Use '''enable''' to switch back to the fglrx driver.
Fedora does not install any 3D software by default, but several titles are available in the repositories. Other third-party applications work well too, including Google Earth.

===Intel video===
==WiFi==
===Intel PRO/Wireless 3945ABG===
The [[Intel PRO/Wireless 3945ABG Mini-PCI Express Adapter]] is detected and enabled automatically. The activity indicator LED doesn't work with the standard driver. That appears to have been fixed in the latest version of the driver, but that is not yet in Fedora.

==Pointing Devices==
===TrackPoint===
The TrackPoint pointing device works automatically. Information on getting the middle button to act as a scroll wheel goes here.
===Touch Pad===
The touch pad is enabled and works automatically. Press-to-select is enabled by default.

==Bluetooth==
==Fingerprint Reader==
==WWAN==
===Verizon EVDO===
==Special Keys==
===Fn+F2 Lock Screen===
===Fn+F3 Sleep===
===Fn+F4 Suspend to RAM (Standby) ===
Suspend to RAM works automatically. Closing the lid also put the machine into the same standby mode.

===Fn+F5 Radio Control===
===Fn+F7 Display Selection===
===Fn+F8 Pointing Devices===
===Fn+F9 Eject===
===Fn+F12 Suspend to Disk (Hibernate)===
Suspend to disk works automatically.

===Fn+Home/End Brightness===
Brightness control works automatically. GNOME's on-screen display for brightness works. When on AC, brightness is dimmed by default. To disable this, click System->Preferences->System->Power Management. Click the On Battery Power tab, and set the Dim display brightness by: slider to the desired amount.
===Volume===
Volume up, volume down and volume mute work automatically, as does the on-screen display.
===ThinkVantage===
This button doesn't do anything by default, and it's not obvious what it should do when running Linux, if anything.

==Infrared==

=Tuning=
This section details how to tune your system for performance or battery life. These are the numbers I got from PowerTop (yum install powertop to install this handy tool).
{| border="1"
|+My power consumption
|-
!Description!!Wakes per second!!Wattage!!Estimated Time
|-
|Default - No changes||45000||27.8W||2.6Hr
|-
|Enable USB suspend||45000||27.8W||2.6Hr
|-
|Kill hald-addon-storage||45000||27.8W||2.6Hr
|-
|Increase writeback time||45000||27.8W||2.6Hr
|-
|Enable USB suspend||45000||27.8W||2.6Hr
|-
|Turn Bluetooth off||45000||27.8W||2.6Hr
|-
|Enable laptop mode||45000||27.8W||2.6Hr
|}
PowerTop didn't help at all this time. I was pretty sure it helped a lot when I installed from DVD. FIXME.

[[User:Pfps|Pfps]] 01:30, 28 February 2008 (CET) This very high number of wakeups is a problem that has been reported elsewhere, but I am not aware of any fix. My T60p does this sometimes. Sometimes it doesn't. I don't know why. Does anyone have any ideas?

[[Category:T60]]
[[Category:Fedora Core 8]]

Installing Fedora on a ThinkPad T60

2008-03-02T06:31:34Z

Jaskiern: Change category from Fedora to Fedora Core 8.

Creation timestamp: [[User:Whizkid|Whizkid]] 05:00, 6 February 2008 (CET)

This document is meant to be the definitive resource to getting the latest current release of Fedora running on a ThinkPad T60. I welcome improvements to the page, especially for hardware I don't have (video chips, WiFi cards, WWAN devices).

This document is current for Fedora 8. Fedora 9 Alhpa 1 has just been released, but we have a few months before that goes gold.

=Installation Methods=
Every T60 has a drive that can read DVDs. Nothing else is needed during the install, and it's the method I'm documenting first. Other methods of installation are detailed on the Fedora web site. For a smaller download, you can use the LiveCD, but fewer packages are available until you connect to the Internet.

=Pre-installation=
Fedora 8 does not have a method to shrink NTFS partitions during installation. You can use Knoppix or other LiveCD's to do that if you want to dual-boot. Links to pages on how to do that would be nice right about.... here.

Installation tips:
*Set the optical drive mode to High Performance during the installation to speed it up a little. To do that: Get into the BIOS. Select Config->Power->CDROM Speed->High.

=Installation Steps=
For any disc, I recommend completing the media test at least once on each disc you burn. Anaconda is the name of Fedora's installer program.
==Installation DVD==
*Boot the DVD. Skip ahead to '''Anaconda'''.
==Live CD==
*Boot the CD. After some initialization, you are eventually presented with the login screen. Click '''Fedora Live''' or wait 60 seconds. You are presented with the GNOME desktop. Double-click the icon titled '''Install to Hard Drive'''. Continue to the next section.
==Anaconda==
*You are presented with a title screen and no instructions. (That's what we're here for!) Click Next.
*Select the installation language. Click Next. (Not presented if using LiveCD. It uses the current language.)
*Select your keyboard language. Click Next. The installer looks for existing installations. You are prompted to choose a clean installation or upgrade. I'm documenting a clean install. Click Next.
*You are asked how to partition your drive. The default is to remove existing Linux partitions. That's a fine choice. Turn on the Review check box to see how it will partition the drive if you're curious. Click Next.
*Confirm that you want to delete partitions.
If you checked the Review box above, you are presented with the new disk layout. Edit as you please then click Next.
*The installer looks for other installed operating systems. You are asked where the boot loader will be installed. If you want to keep ThinkVantage functionality, check '''Configure advanced boot loader options'''. You can change the label of the other operating systems on the drive and select a default OS. Click Next.
If you selected advanced option configuration, you are asked where the boot loader should be installed. Select the first sector of the boot partition, not the MBR, if you want ThinkVantage to work at startup, or if you want another OS to manage the boot process. Click Next.
*You are asked whether the wired Ethernet controller should be active on boot. Since I use mine with WiFi most of the time, I turn that off and set the hostname manually. Click Next. Click Continue to confirm no network devices at boot if asked.
*Select your time zone, choose whether or not the clock uses UTC and click Next.
*Enter your root password. Do it again. Click Next.
*If using the DVD, the installer looks for common installation packages. Since everything is out of date already, I turn off all options and customize later. Click Next. The installer checks dependencies.
*You are asked one last time to confirm installation. Nothing has yet been written to the disk and this is the last point you can abort installation without changing anything on the drive. Click Next.

The partition table is written, partitions are formatted, the install image is copied and packages are installed. The disc is ejected and you are asked to reboot the machine. The process took 17 minutes on my T60 with a 2.0GHz Core Duo and 5400RPM hard drive with the DVD, or about 6 minutes using the LiveCD.

=First Boot=
During the first boot, the system may wait a long time while trying to connect to a WiFi access point, even though your WiFi card may not have been detected by the installer.
*A welcome screen is presented. Your screen should now be in its native resolution. Click Forward.
*A license information screen is presented. Click Forward.
*Firewall configuration is presented. Configure as you like. Click Forward.
*SELinux setting is presented. Click Forward.
*Set your local date and time. Click Forward.
*Your hardware profile is shown. If you opt in and send your profile, your machine is counted by the Fedora team to get an idea of the population on which Fedora runs. Consider opting in to let them know we have these machines and want Fedora to run well on them. Click Forward.
*Create a user. Click Finish. Done!

=Get Updates=
Get a network connection going and get all recent updates. Reboot if a new kernel is installed. I like to use NetworkManager.
==Configuring NetworkManager==
This section does not apply if you login using network authentication. NetworkManager is not perfect, and requires you to enter a keyring password at times, but it's a convenient way to connect to different networks, especially wireless networks.
*First make sure neither network device is enabled at boot time. Network devices that are enabled at boot time will attempt to get an IP address using DHCP by default. If you are near a secured WiFi hotspot, you will not get an IP address and the system will wait until it times out. Select System->Administration->Network. For each device listed, double-click it and turn off '''Activate device when computer starts'''. You may wish to enable '''Allow all users to enable and disable the device'''. Save changes and quit.
*Select System->Administration->Services. Check NetworkManager and NetworkManagerDispatcher and start each one. Save the configuration.
Your wired network will automatically connect and your wireless networks should now be visible.
To connect to a wireless network, click the NetworkManager notification icon and click the network to join.

Shortly after you connect to the internet, you should be notified that there are updates available. If you are asked for the install media, you can disable that repository.

=Device Configuration=
==Audio==
The Intel 82801G (ICH7) High Definition Audio Controller is identified and enabled automatically. The AD198x Analog PCM device works for audio. The Digital PCM device does not seem to work. Could it be that it only works in a dock?
==Video Chip==
===ATI X1300 and ATI X1400===
Currently, Fedora does not include a driver specific to this card. It selects the '''vesa''' driver, which works fine, but performance is slow. The RadeonHD driver is in progress but also has no accelerated video modes, so is not a recommended option at this time.
ATI's proprietary '''fglrx''' driver now works very well for the T60. The easiest way to get the driver and have automatic updates is to use the Livna repository.
* Click the Fedora 8 repository from the front page of [http://rpm.livna.org].
* Let the Fedora package installer install the RPM package.
* Select Applications->Add/Remove Software.
* Under RPM Fusion - Nonfree, check Hardware Support.
* Click Optional packages.
* Check '''xorg-x11-drv-fglrx''', close and Apply.
* Reboot the machine and log in. (Logging out is not sufficient.)
At this point, you should have 2D and 3D acceleration working. This is while using the vesa driver:
$glxinfo | grep direct
direct rendering: No (...)
OpenGL renderer string: Mesa GLX Indirect
And while using the fglrx driver:
$glxinfo | grep direct
direct rendering: Yes
To disable the '''fglrx''' driver and use '''vesa''':
/usr/sbin/fglrx-config-display disable
and reboot. Use '''enable''' to switch back to the fglrx driver.
Fedora does not install any 3D software by default, but several titles are available in the repositories. Other third-party applications work well too, including Google Earth.

===Intel video===
==WiFi==
===Intel PRO/Wireless 3945ABG===
This card is detected and enabled automatically. The activity indicator LED doesn't work with the standard driver. That appears to have been fixed in the latest version of the driver, but that is not yet in Fedora.

==Pointing Devices==
===TrackPoint===
The TrackPoint pointing device works automatically. Information on getting the middle button to act as a scroll wheel goes here.
===Touch Pad===
The touch pad is enabled and works automatically. Press-to-select is enabled by default.

==Bluetooth==
==Fingerprint Reader==
==WWAN==
===Verizon EVDO===
==Special Keys==
===Fn+F2 Lock Screen===
===Fn+F3 Sleep===
===Fn+F4 Suspend to RAM (Standby) ===
Suspend to RAM works automatically. Closing the lid also put the machine into the same standby mode.

===Fn+F5 Radio Control===
===Fn+F7 Display Selection===
===Fn+F8 Pointing Devices===
===Fn+F9 Eject===
===Fn+F12 Suspend to Disk (Hibernate)===
Suspend to disk works automatically.

===Fn+Home/End Brightness===
Brightness control works automatically. GNOME's on-screen display for brightness works. When on AC, brightness is dimmed by default. To disable this, click System->Preferences->System->Power Management. Click the On Battery Power tab, and set the Dim display brightness by: slider to the desired amount.
===Volume===
Volume up, volume down and volume mute work automatically, as does the on-screen display.
===ThinkVantage===
This button doesn't do anything by default, and it's not obvious what it should do when running Linux, if anything.

==Infrared==

=Tuning=
This section details how to tune your system for performance or battery life. These are the numbers I got from PowerTop (yum install powertop to install this handy tool).
{| border="1"
|+My power consumption
|-
!Description!!Wakes per second!!Wattage!!Estimated Time
|-
|Default - No changes||45000||27.8W||2.6Hr
|-
|Enable USB suspend||45000||27.8W||2.6Hr
|-
|Kill hald-addon-storage||45000||27.8W||2.6Hr
|-
|Increase writeback time||45000||27.8W||2.6Hr
|-
|Enable USB suspend||45000||27.8W||2.6Hr
|-
|Turn Bluetooth off||45000||27.8W||2.6Hr
|-
|Enable laptop mode||45000||27.8W||2.6Hr
|}
PowerTop didn't help at all this time. I was pretty sure it helped a lot when I installed from DVD. FIXME.

[[User:Pfps|Pfps]] 01:30, 28 February 2008 (CET) This very high number of wakeups is a problem that has been reported elsewhere, but I am not aware of any fix. My T60p does this sometimes. Sometimes it doesn't. I don't know why. Does anyone have any ideas?

[[Category:T60]]
[[Category:Fedora Core 8]]

Category:Ubuntu 8.04

2008-03-02T06:08:26Z

Jaskiern:

'''Ubuntu 8.04''', Hardy Heron, is scheduled for release April 24, 2008.

== External links ==
* [https://launchpad.net/ubuntu/hardy/ Ubuntu Hardy Heron Launchpad project page]
* Reading the [https://wiki.ubuntu.com/HardyHeron/Alpha5#Caveats "Caveats"] of the latest release for major OS issues is highly recommended before performing a pre-release installation.
* [https://bugs.launchpad.net/ubuntu/hardy Bugs in the Hardy Heron]

[[Category:Ubuntu]]

Category:Ubuntu

2008-03-02T06:06:56Z

Jaskiern:

{| width="100%"
|style="vertical-align:middle;padding-left:20px;padding-right:20px;width:10px;" | [[Image:Ubuntu_logo.png]]
|style="vertical-align:top" |
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;">

This page gives an introduction to Ubuntu and an overview of related articles.
</div>
|}
{| style="margin-left:20px;margin-right:20px;"
|
__NOTOC__
== What is Ubuntu? ==

Ubuntu is a Linux distribution that starts with the breadth of [[:Category:Debian | Debian]] and adds regular releases (every six months), a clear focus on the user and usability (it should "Just Work", TM) and a commitment to security updates with 18 months of support for every release.

== External links ==
* [http://www.ubuntulinux.org www.ubuntulinux.org] Official Ubuntu Homepage
* [http://www.ubuntuforums.org www.ubuntuforums.org] Ubuntu forums
* [http://www.ubuntuguide.org www.ubuntuguide.org] Ubuntu guide
|}

[[Category:Distributions]]

Category:Ubuntu 7.10

2008-03-02T06:04:43Z

Jaskiern:

'''Ubuntu 7.10''', Gutsy Gibbon, was released October 18, 2007.

== External links ==
* [https://help.ubuntu.com/ Ubuntu release documentation]
* [http://www.ubuntu.com/getubuntu/releasenotes/710tour Ubuntu Feature list]
* [http://cdimage.ubuntu.com/releases/7.10/release/ Download Gutsy Gibbon]
* [https://bugs.launchpad.net/ubuntu/gutsy/+bugs?search=Search&field.status=New&field.status=Incomplete&field.status=Confirmed&field.status=Triaged&field.status=In+Progress&field.status=Fix+Committed Open Gutsy Gibbon Bugs]
* [https://launchpad.net/ubuntu/gutsy/ Ubuntu Gutsy Gibbon Launchpad project page]
* [https://launchpad.net/tp-fan/ Thinkpad GTK GUI Fancontrol Tool]

[[Category:Ubuntu]]

Category:Ubuntu 8.04

2008-03-02T06:01:26Z

Jaskiern:

Ubuntu Hardy Heron, 8.04, is scheduled for release April 24, 2008.

== Features ==

== External links ==
* [https://launchpad.net/ubuntu/hardy/ Ubuntu Hardy Heron Launchpad project page]
* Reading the [https://wiki.ubuntu.com/HardyHeron/Alpha5#Caveats "Caveats"] of the latest release for major OS issues is highly recommended before performing a pre-release installation.
* [https://bugs.launchpad.net/ubuntu/hardy Bugs in the Hardy Heron]

[[Category:Ubuntu]]

Installing Ubuntu 7.10 (Gutsy Gibbon) on a ThinkPad T43

2008-03-01T08:25:33Z

Jaskiern:

== Features ==
=== Graphical Configuration Tool ===
Some Thinkpad laptops ship with ATI video cards. Previously in Ubuntu 7.04, Open Source video drivers could be graphically configured with a minimal utility that allowed to 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.

=== Compiz Fusion ===
Compiz Fusion is now enabled by default for supported video cards. Compiz effects were previously exclusive to Nvidia video cards, leaving T43 users out in the cold. Compiz Fusion features are now available to T43 users with ATI video cards (at least).

== Installation ==
No installation issues found.

== Post-Installation Setup ==

== References ==
* [[Installing Ubuntu 7.04 on a ThinkPad T43]]

== See also ==
* [[Installing Ubuntu 8.04 (Hardy Heron) on a Thinkpad T43]]

== External links ==

[[Category: Ubuntu 7.10]] [[Category: T43]]

Installing Ubuntu 6.10 on a ThinkPad T43

2008-03-01T08:19:46Z

Jaskiern:

Installation Log of Kubuntu 6.10 on a {{T43}}

__TOC__

==Overview==
Worked right out of the box
* 1400*1050 resolution
* Battery Management
* Ultra Nav (Trackpoint and synaptic touchpad) 3rd button scroll did not work
* WLAN (Atheros, IBM 11a/b/g Wireless LAN Mini PCI Adapter II)
* Hibernate and Standby
* Audio Keys
* ThinkLight

Was easy or required some work
* middle key of Ultra Nav (Trackpoint)
* ATI 3D Acceleration (Mobility Radeon X300)

Still TODO
* Beryl

Untested
* Bluetooth (light indicates working)
* Modem
* IrDA

==Installation==

===Recovery copy of data===

Before installing a new OS you should create a security copy of your old system. As the IBM Rescue and Recovery tool quit with an error message I used the Ubuntu live CD, mounted and cd'ed into my external hard drive and ran the following command:

$ cmduser|sudo dd if=/dev/sda1 | gzip | dd of=./sda1.img

where /dev/sda1 is the device with my windows partition and sda1.img the gzipped security copy.
In case of problems one can now restore lost information using

$ sudo dd if=./sda1.img | gzip -d | dd of=/dev/sda1

After creating the recovery copy we are ready to resize the existing windows partition. This article assumes you want to keep your IBM Rescue and Recovery Partition, shrink in size, but keep your windows partition and create a new partition for Dapper Drake.

===Resizing Partitions===

I used Partition Magic, but others have done the following...

Probably the best choice is now to boot from the alternate CD (read [http://gawrysiak.org/corvus/?p=4] to know why) and use it to resize the existing NTFS partition. Unfortionately in my case it didn't work. So I booted the Live CD, but gparted and parted refused to resize my Windows, too. If the same happens to you, use the example [http://crashrecovery.org/CrashRecoveryKit/iso/2.4.21/HOWTO.ntfs.html here] to know how to resize it "manually" using ntfsresize and fdisk.

After resizing your windows partition you should reboot window to check everything's in order. It probably will run checkdisk and reboot two times - according to experieces you can read in the web, you should better let windows do that.

===Installation of Ubuntu===

Now it's the time to install Ubuntu. I used the alternate CD for that because I chose to install grub into the Linux partition and not into the Master Boot Record ([http://gawrysiak.org/corvus/?p=4 read why]). The graphical LiveCD installer automatically installs grub to the MBR. If you want to use grub in the MBR read [[Rescue and Recovery]]. There is a description of what you have to do in order to still be able to use the IBM R'n'R partition.

* remember that you're installing GRUB to an '''sda''' mount, not an hda mount like the GRUB installer will prompt you for what you should enter after you tell GRUB not to install in the MBR will be something like this:

/dev/sda3

After the installation is finshed it will reboot your system. Now windows should start. In my case it didn't, but playing around, booting into the R'n'R partition, starting PC Doctor and doing some Diagnostics (no changes) somehow and surprisingly made windows boot again.

To boot you freshly installed Linux you have to reboot the LiveCD one last time. Use

$ sudo dd if=/dev/sda5 of=ubuntu.img bs=512 count=1

to copy the first block of grub into an image file and use e.g. an usb flash drive to transfer it to your newly booted windows. Copy paste the image to C:\ and add the following line to your C:\boot.ini:

C:\ubuntu.img="Ubuntu Dapper Drake"

At the next restart the windows boot manager should now welcome you with the choice to boot windows or ubuntu. Choose ubuntu to (finally ;-) boot your newly installed linux for the first time.

==Configuration==

===3D Acceleration and Xgl/Compiz===

If you have an ATI Radeon X300, use [http://wiki.cchtml.com/index.php/Ubuntu_Edgy_Installation_Guide this explanation] to make your hardware 3d acceleration work.

To test if it works type

$ glxinfo | grep rendering

The answer should be: "direct rendering: Yes". If it says "No", you don't have 3D acceleration.

If you have another card you might find a good explanation [http://ubuntuforums.org/showthread.php?t=148351 here].

===3D Acceleration using open-source radeon driver and AIGLX/Beryl===
From my experience it was better to use "radeon" driver, the open source one, on top of "drm" driver,
also part of the kernel, instead of fglrx. I get direct rendering and similar performance---maybe fglrx
driver gives 50-100 more fps. The most annoying thing about fglrx driver is that it can cause hard locks
every now and then and your suspend doesn't work properly...believe me I tried the ones that the Thinkwiki
says supposed to work.

$ glxinfo | grep rendering
direct rendering: Yes
OpenGL renderer string: Mesa DRI R300 20060815 TCL

Use the directions in the previous section to install fglrx driver, library. (I just installed them from shell
rather than making them into packages, I found the uninstall script in /usr/share/fglrx to work properly).
FYI, I used the version 8.26.18-x86.

If you don't get rendering use ''LIBGL_DEBUG=verbose glxinfo'' to diagnose the problem. The most common problem
is that xorg looks for DRI library files in ''/usr/X11R6/lib/dri'', which didn't exist for me. A simple way to
solve this is creating a symlink to where those files are located (/usr/lib/dri/):
$ cd /usr/X11R6/lib/
$ ln -s /usr/lib/dri/ .

Open your ''/etc/modules'' file and add these lines and comment 'fglrx' if there is any:
intel-agp
drm
radeon

Also, from my experience, it was better to use '''AIGLX''' than Xgl and '''Beryl''' instead of Compiz
in terms of performance and integration---things like suspend and hibernate. And you can use nice
start/shutdown scripts to disable beryl-manager since it can cause hang when you resume from suspension.
For more information about suspend/resume scripts, [http://ubuntuforums.org/showthread.php?p=1656484 here].
For more information about installing aiglx and beryl, see [http://wiki.beryl-project.org/index.php/Install/Ubuntu/Dapper/AiGLX here]).

ATI X300 is pretty pitiful though...I get around ~570 average FPS when running AIGLX/beryl
$ glxgears
2850 frames in 5.0 seconds = 569.997 FPS
2925 frames in 5.0 seconds = 584.925 FPS
2904 frames in 5.0 seconds = 580.741 FPS
2923 frames in 5.0 seconds = 584.524 FPS...
With metacity (default Gnome window manager) I get around slightly over 1000 FPS
$ glxgears
5073 frames in 5.0 seconds = 1014.423 FPS
5073 frames in 5.0 seconds = 1014.531 FPS
5252 frames in 5.0 seconds = 1049.326 FPS
5803 frames in 5.0 seconds = 1160.502 FPS...

I added the following options under ati Device section of ''/etc/X11/xorg.conf''
Option "EnablePageFlip" "True"
Option "ColorTiling" "True"
Then after that the performance boosted by quite a bit:
7026 frames in 5.0 seconds = 1405.147 FPS
7058 frames in 5.0 seconds = 1411.493 FPS
7062 frames in 5.0 seconds = 1412.393 FPS...

===Active Protection System===

See end of this chapter if you have ubuntu edgy eft.

The T43 has a great system to protect your hard disk, the Active Protection System APS. [[How to protect the harddisk through APS]] describes how you can use it.

{{WARN|Only follow these instructions if you know what you are doing!}}

If you didn't until now you will have to install make, libc, gcc, ... Best is you use

$ sudo apt-get install build-essential

Determine your kernel version using

$ uname -a

You should see somthing like

Linux ibm 2.6.15-26-386 #1 PREEMPT Thu Aug 3 02:52:00 UTC 2006 i686 GNU/Linux

Install the kernel sources "linux-source" e.g. using Synaptic.
Download the right kernel patch from [[HDAPS#Applications]] according to your kernel version and system (I chose "sata/ide disk protection patch for 2.6.15")
adapt following steps to your needs:

$ cd /usr/src/
$ sudo su
# bunzip2 linux-source-2.6.15.tar.bz2
# tar -xf linux-source-2.6.15.tar
# cd linux-source-2.6.15
# patch -p1 -l < /home/silvan/hdaps_protect.20060118.patch

You should see several lines with the word "suceeded". If you see many "failed" instead you probably chose the wrong patch for your kernel. You can use the --dry-run option to try it out first. If you get errors in the following steps you should better stop unless you know what you are doing.

# make clean
# make oldconfig # use old config, ask for new items, only
# make clean
# make # takes quite a long time, several minutes
# make modules
# make modules_install

Afterwards use the debian sources mentioned in [[How to protect the harddisk through APS]] to install the user space deamon hdapsd and the gnome applet gnome-hdaps-applet, e.g. using Synaptic.

If this worked for you, you can find some nice applications at [[HDAPS#Applications]] which make use of the APS.

{{HELP|For me unfortunately it didn't work as making the patched kernel failed. Please update ths section if you have different experiences and a better, more detailed working explanation.}}

{{NOTE|After I updated to edgy eft hdaps works without further work: edgy comes with hdaps built in. You can check if it is working by installing hdaps-utils

# sudo apt-get install hdaps-utils

and calling

# hdaps-gl

for a nice 3D show. If it is not, load the kernel module using

# sudo modprobe hdaps

and it should work. But if you want to use hdaps for disk protection, you have to recompile your kernel in edgy, too. Follow this post for an howto:

}}
[http://ubuntuforums.org/showthread.php?t=122863 Howto for edgy]

===Track Point Middle Key Scrolling===

In my case the track point worked out of the box, but the middle mouse button for scrolling did not. [[How to configure the TrackPoint]] explains how to solve this. The steps you need to follow are in section "Using the X server (kernel 2.6.11+)".
However you don't need to follow the steps in "EmulateWheelTimeout temporarily broken (-> fix for Ubuntu Dapper)" as this is fixed already if you have all your packages up-to-date.

Follow the instructions in the sections "Configure firefox for using trackpoint horizontal scrolling" and "Configure Opera for using trackpoint horizontal scrolling" as well, if you are using one of the two browsers.

===Fingerprint Reader===
{{Todo|Needs editing}}
Look at [[How to enable the fingerprint reader]] if you want to use your fingerprint reader.

An alternative way can be found at [[Installing Ubuntu 6.06 on a ThinkPad T43#Fingerprint_Reader]].

===Spezial keys ===

If the following standard settings are not enough for you, you'll find more info here: [[How to get special keys to work]]

===={{ibmkey|Access IBM|#495988}} to start application====
The {{ibmkey|Access IBM|#495988}} works out of the box. Just go to your shortcut configuration dialog and choose what actionyou want to connect with pressing this button, e.g. opening your home folder/terminal, switching o fullscreen, opening help...

===={{key|CAPS}} to substitute {{key|Win}}/{{key|Super}}====
For using your {{key|CAPS}} key as a replacement for the lacking {{key|Win}}/{{key|Super}} key, add following to your {{path|~/.Xmodmap}}

! No Caps Lock
clear lock
! Caps Lock as Win key
add mod4 = Caps_Lock

To avoid restarting X type {{cmduser|xmodmap ~/.Xmodmap}}

===={{ibmkey|Forward|#494949}}/{{ibmkey|Backward|#494949}} in browsers====

=====Firefox=====
For using the {{ibmkey|Forward|#494949}}/{{ibmkey|Backward|#494949}} Keys in your browser add also these lines to your {{path|~/.Xmodmap}} as at least Firefox gets confused with their original setting as XF86Back/XF86Forward.

! back and forward browser keys
keycode 234 = F19
keycode 233 = F20

For Firefox add these lines to your {{path|/usr/share/firefox/chrome/browser/content/browser/browser.xul}}

<key id="goBackKb3" keycode="VK_F19" command="Browser:Back" />
<key id="goForwardKb3" keycode="VK_F20" command="Browser:Forward" />

directly after these lines:

<key id="goBackKb" keycode="VK_LEFT" command="Browser:Back" modifiers="alt"/>
<key id="goForwardKb" keycode="VK_RIGHT" command="Browser:Forward" modifiers="alt"/>

=====Opera=====
For Opera add these pairs in Tool->Preferences->Advanced->Shortcuts->Keyboard setup->Edit->Browser Window->New
* If you did the Firefox Xmodmap entry: F20-Forward, F19-Back
* If you didn't add the lines: XF86Forward-Forward, XF86Back-Back

=====Konqueror=====
In Konqueror it's working out of the box. But if you did the Xmodmap settings you have to adjust Konqueror, too. Just go to Settings->Configure Shortcuts, look for Back and Forward and set the alternative shortcut in the custom dialog by pressing the respective key. If you are using KDE you'll be probable prefering to do that in the Configuration Center to make these changes visible to all KDE Apps.

===IrDA===
{{Todo|Needs editing}}
Find information here: [[How to make use of IrDA]]

===VGA out ===
{{Todo|Needs editing}}
I didn't try it, but it looks easy: [http://help.nceas.ucsb.edu/index.php/Enable_vga_out_on_ATI_Thinkpads How to enable VGA out]

==References==
* [[Installing Ubuntu 6.06 on a ThinkPad T43]]
* [http://gawrysiak.org/corvus/?p=4 Dapper Drake on T42]

== See also ==
* [[Installing Ubuntu 7.04 on a ThinkPad T43]]

==External Sources==
* This guide is listed at the [http://tuxmobil.org/ibm.html TuxMobil Linux laptop and notebook installation survey (IBM/Lenovo)].

Hope this helped somehow :-)
tec

[[Category: Kubuntu 6.10]] [[Category: Ubuntu 6.10]]

Installing Ubuntu 6.06 on a ThinkPad T43

2008-03-01T08:17:35Z

Jaskiern:

Installation Log of {{Ubuntu 6.06}} on a {{T43}}

__TOC__

==Overview==
Worked right out of the box
* 1400*1050 resolution
* Battery Management
* Ultra Nav (Trackpoint and synaptic touchpad)
* WLAN (Atheros, IBM 11a/b/g Wireless LAN Mini PCI Adapter II)
* Hibernate and Standby
* Fn keys (switch between monitors untested)
* Audio Keys
* ThinkLight

Was easy or required some work
* easy ubuntu (includes skype and some codecs)
* middle key of Ultra Nav (Trackpoint)
* ATI 3D Acceleration (Mobility Radeon X300)
* Xgl / Compiz
* Fingerprint reader
* Forward/Backward keys, Access IBM Key

Untested
* Bluetooth (light indicates working)
* Modem
* IrDA
* TV out, VGA out

Failed / still requires work
* Active Protection System (acceleration sensor works 'out of the box' in edgy, but hard disk parking needs kernel recompile)

==Installation==

===Recovery copy of data===

Before installing a new OS you should create a security copy of your old system. As the IBM Rescue and Recovery tool quit with an error message I used the Ubuntu live CD, mounted and cd'ed into my external hard drive and ran the following command:

$ cmduser|sudo dd if=/dev/sda1 | gzip | dd of=./sda1.img

where /dev/sda1 is the device with my windows partition and sda1.img the gzipped security copy.
In case of problems one can now restore lost information using

$ sudo dd if=./sda1.img | gzip -d | dd of=/dev/sda1

After creating the recovery copy we are ready to resize the existing windows partition. This article assumes you want to keep your IBM Rescue and Recovery Partition, shrink in size, but keep your windows partition and create a new partition for Dapper Drake.

===Resizing Partitions===

Probably the best choice is now to boot from the alternate CD (read [http://gawrysiak.org/corvus/?p=4] to know why) and use it to resize the existing NTFS partition. Unfortionately in my case it didn't work. So I booted the Live CD, but gparted and parted refused to resize my Windows, too. If the same happens to you, use the example [http://crashrecovery.org/CrashRecoveryKit/iso/2.4.21/HOWTO.ntfs.html here] to know how to resize it "manually" using ntfsresize and fdisk.

After resizing your windows partition you should reboot window to check everything's in order. It probably will run checkdisk and reboot two times - according to experieces you can read in the web, you should better let windows do that.

===Installation of Ubuntu===

Now it's the time to install Ubuntu. I used the alternate CD for that because I chose to install grub into the Linux partition and not into the Master Boot Record ([http://gawrysiak.org/corvus/?p=4 read why]). The graphical LiveCD installer automatically installs grub to the MBR. If you want to use grub in the MBR read [[Rescue and Recovery]]. There is a description of what you have to do in order to still be able to use the IBM R'n'R partition.

* remember that you're installing GRUB to an '''sda''' mount, not an hda mount like the GRUB installer will prompt you for what you should enter after you tell GRUB not to install in the MBR will be something like this:

/dev/sda3

After the installation is finshed it will reboot your system. Now windows should start. In my case it didn't, but playing around, booting into the R'n'R partition, starting PC Doctor and doing some Diagnostics (no changes) somehow and surprisingly made windows boot again.

To boot you freshly installed Linux you have to reboot the LiveCD one last time. Use

$ sudo dd if=/dev/sda5 of=ubuntu.img bs=512 count=1

to copy the first block of grub into an image file and use e.g. an usb flash drive to transfer it to your newly booted windows. Copy paste the image to C:\ and add the following line to your C:\boot.ini:

C:\ubuntu.img="Ubuntu Dapper Drake"

At the next restart the windows boot manager should now welcome you with the choice to boot windows or ubuntu. Choose ubuntu to (finally ;-) boot your newly installed linux for the first time.

==Configuration==

===Easyubuntu===

[http://easyubuntu.freecontrib.org/ Easyubuntu] is a helpful tool to install Skype, codecs, ATi 3D drivers and further things that can make your live easier.

===Keyboard Layout===

My T43 has a German keyboard layout. Most worked just fine, but some keys (in my case the "at" and the "tilde" among others) just didn't. If the same happens to you, just go to the Gnome System Preferences menu and choose the right layout for your keyboard (probably named after your language and something like eliminate-dead-keys or no-dead-keys)

===3D Acceleration and Xgl/Compiz===

If you have an ATI Radeon X300, use [http://wiki.cchtml.com/index.php/Ubuntu_Dapper_Installation_Guide this explanation] to make your hardware 3d acceleration work.

To test if it works type

$ glxinfo | grep rendering

The answer should be: "direct rendering: Yes". If it says "No", you don't have 3D acceleration.

If you want to install Xgl/Compiz like me, [http://www.compiz.net/viewtopic.php?id=389 here] is a great installation help for ATI cards (use way two.)

If you have another card you might find a good explanation [http://ubuntuforums.org/showthread.php?t=148351 here].

===3D Acceleration using open-source radeon driver and AIGLX/Beryl===
From my experience it was better to use "radeon" driver, the open source one, on top of "drm" driver,
also part of the kernel, instead of fglrx. I get direct rendering and similar performance---maybe fglrx
driver gives 50-100 more fps. The most annoying thing about fglrx driver is that it can cause hard locks
every now and then and your suspend doesn't work properly...believe me I tried the ones that the Thinkwiki
says supposed to work.

$ glxinfo | grep rendering
direct rendering: Yes
OpenGL renderer string: Mesa DRI R300 20060815 TCL

Use the directions in the previous section to install fglrx driver, library. (I just installed them from shell
rather than making them into packages, I found the uninstall script in /usr/share/fglrx to work properly).
FYI, I used the version 8.26.18-x86.

If you don't get rendering use ''LIBGL_DEBUG=verbose glxinfo'' to diagnose the problem. The most common problem
is that xorg looks for DRI library files in ''/usr/X11R6/lib/dri'', which didn't exist for me. A simple way to
solve this is creating a symlink to where those files are located (/usr/lib/dri/):
$ cd /usr/X11R6/lib/
$ ln -s /usr/lib/dri/ .

Open your ''/etc/modules'' file and add these lines and comment 'fglrx' if there is any:
intel-agp
drm
radeon

Also, from my experience, it was better to use '''AIGLX''' than Xgl and '''Beryl''' instead of Compiz
in terms of performance and integration---things like suspend and hibernate. And you can use nice
start/shutdown scripts to disable beryl-manager since it can cause hang when you resume from suspension.
For more information about suspend/resume scripts, [http://ubuntuforums.org/showthread.php?p=1656484 here].
On T43s suspend seems to work great with [http://ubuntuforums.org/showthread.php?p=2092657#post2092657 this script].

For more information about installing aiglx and beryl, see [http://wiki.beryl-project.org/index.php/Install/Ubuntu/Dapper/AiGLX here].

ATI X300 is pretty pitiful though...I get around ~570 average FPS when running AIGLX/beryl
$ glxgears
2850 frames in 5.0 seconds = 569.997 FPS
2925 frames in 5.0 seconds = 584.925 FPS
2904 frames in 5.0 seconds = 580.741 FPS
2923 frames in 5.0 seconds = 584.524 FPS...
With metacity (default Gnome window manager) I get around slightly over 1000 FPS
$ glxgears
5073 frames in 5.0 seconds = 1014.423 FPS
5073 frames in 5.0 seconds = 1014.531 FPS
5252 frames in 5.0 seconds = 1049.326 FPS
5803 frames in 5.0 seconds = 1160.502 FPS...

If anyone know how to get rid of the weird warning, I would really appreciate it:
libGL warning: 3D driver claims to not support visual 0x4b
Seems to be a unresolved bug: [https://bugs.freedesktop.org/show_bug.cgi?id=6624 freedesktop]

I added the following options under ati Device section of ''/etc/X11/xorg.conf''
Option "EnablePageFlip" "True"
Option "ColorTiling" "True"
Then after that the performance boosted by quite a bit:
7026 frames in 5.0 seconds = 1405.147 FPS
7058 frames in 5.0 seconds = 1411.493 FPS
7062 frames in 5.0 seconds = 1412.393 FPS...

===Active Protection System===

See end of this chapter if you have ubuntu edgy eft.

The T43 has a great system to protect your hard disk, the Active Protection System APS. [[How to protect the harddisk through APS]] describes how you can use it.

{{WARN|Only follow these instructions if you know what you are doing!}}

If you didn't until now you will have to install make, libc, gcc, ... Best is you use

$ sudo apt-get install build-essentials

Determine your kernel version using

$ uname -a

You should see somthing like

Linux ibm 2.6.15-26-386 #1 PREEMPT Thu Aug 3 02:52:00 UTC 2006 i686 GNU/Linux

Install the kernel sources "linux-source" e.g. using Synaptic.
Download the right kernel patch from [[HDAPS#Applications]] according to your kernel version and system (I chose "sata/ide disk protection patch for 2.6.15")
adapt following steps to your needs:

$ cd /usr/src/
$ sudo su
# bunzip2 linux-source-2.6.15.tar.bz2
# tar -xf linux-source-2.6.15.tar
# cd linux-source-2.6.15
# patch -p1 -l < /home/silvan/hdaps_protect.20060118.patch

You should see several lines with the word "suceeded". If you see many "failed" instead you probably chose the wrong patch for your kernel. You can use the --dry-run option to try it out first. If you get errors in the following steps you should better stop unless you know what you are doing.

# make clean
# make oldconfig # use old config, ask for new items, only
# make clean
# make # takes quite a long time, several minutes
# make modules
# make modules_install

Afterwards use the debian sources mentioned in [[How to protect the harddisk through APS]] to install the user space deamon hdapsd and the gnome applet gnome-hdaps-applet, e.g. using Synaptic.

If this worked for you, you can find some nice applications at [[HDAPS#Applications]] which make use of the APS.

{{HELP|For me unfortunately it didn't work as making the patched kernel failed. Please update ths section if you have different experiences and a better, more detailed working explanation.}}

{{NOTE|After I updated to edgy eft hdaps works without further work: edgy comes with hdaps built in. You can check if it is working by installing hdaps-utils

# sudo apt-get install hdaps-utils

and calling

# hdaps-gl

for a nice 3D show. If it is not, load the kernel module using

# sudo modprobe hdaps

and it should work. But if you want to use hdaps for disk protection, you have to recompile your kernel in edgy, too. Follow this post for an howto:

}}
[http://ubuntuforums.org/showthread.php?t=122863 Howto for edgy]

===Track Point Middle Key Scrolling===

In my case the track point worked out of the box, but the middle mouse button for scrolling did not. [[How to configure the TrackPoint]] explains how to solve this. The steps you need to follow are in section "Using the X server (kernel 2.6.11+)".
However you don't need to follow the steps in "EmulateWheelTimeout temporarily broken (-> fix for Ubuntu Dapper)" as this is fixed already if you have all your packages up-to-date.

Follow the instructions in the sections "Configure firefox for using trackpoint horizontal scrolling" and "Configure Opera for using trackpoint horizontal scrolling" as well, if you are using one of the two browsers.

===Fingerprint Reader===

[[How to enable the fingerprint reader]] has a good explanation for a very complicated way of activating your fingerprint reader.

An alternative to this is available at [http://thinkfinger.sourceforge.net]:
Follow these steps if you want to trust and use this software.
[[How to enable the fingerprint reader with ThinkFinger]] might provide even more details.

Build and install:
Download the tar.gz and unpack it in your home folder then execute the steps:
$ cd thinkfinger-0.2.2
$ ./configure --with-securedir=/lib/security
$ make
$ sudo checkinstall

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

These steps will activate the fingerprint reader:
Open /etc/pam.d/common-auth:
$ sudo gedit /etc/pam.d/common-auth

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

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

For instance my /etc/pam.d/common-auth looks like this:
# before adding the fingerprint reader work there was only this line:
# auth required pam_unix.so nullok_secure
auth sufficient pam_thinkfinger.so
auth required pam_unix.so try_first_pass

Now we are ready to add users to thinkfinger. In my case checkinstall did not create the /usr/local/etc/pam_thinkfinger
directory, so first create it, if it is the same in your case, then add you user replacing bob with your username:
sudo mkdir /usr/local/etc/pam_thinkfinger
sudo tf-tool --add-user bob

Open a new Terminal and try some command where you need sudo rights like sudo apt-get update, you should be promted now with
Password or swipe finger:

Try both, just to be sure everything works, before you logg off ;-)

I did not test kdm, but gdm (gnome login promt) worked with the fingerprint reader, too, prompting the same line "Password or swipe finger".

{{HELP|This doesn't seem to work with kdm. An explanation can be found at the URL given below. Same goes for kscreensaver. If anybody succeeds in solving this problem, pls note it here! Thx!}}
[http://bbs.archlinux.org/viewtopic.php?id=29310&p=2 Information on ThinkFinger not working with kdm at the moment.]

gksu/gksudo work as well, although its not obvious: If you are prompted for the password, swipe your finger and hit OK, It should authenticate you.

gnome-screensav seems not to work. Anybody any hints on that?

===Forward / Backward Keys, Access IBM===
Just follow this HowTo for the configuration you prefer: [[How to get special keys to work]]

A standard setup is described in [[Installing_Ubuntu_7.04_on_a_ThinkPad_T43#Spezial_keys]]

===IrDA===
{{Todo|Needs editing}}
Find information here: [[How to make use of IrDA]]

===VGA out ===
{{Todo|Needs editing}}
I didn't try it, but it looks easy: [http://help.nceas.ucsb.edu/index.php/Enable_vga_out_on_ATI_Thinkpads How to enable VGA out]

==References==
* [http://gawrysiak.org/corvus/?p=4 Dapper Drake on T42]

== See also ==
* [[Installing Ubuntu 6.10 on a ThinkPad T43]]

==External Sources==
* This guide is listed at the [http://tuxmobil.org/ibm.html TuxMobil Linux laptop and notebook installation survey (IBM/Lenovo)].

Hope this helped somehow :-)
tec

Installing Ubuntu 7.04 (Feisty Fawn) on a ThinkPad T60

2008-03-01T08:15:52Z

Jaskiern:

Ubuntu 7.04 Feisty Fawn is the current release and works fine on:
* T60 UT-049GE and 2007-72U.
* [[Installing Ubuntu 7.04 Feisty Fawn on a ThinkPad T60p|T60p]]

This is a distribution to watch for Thinkpad users.

== Features ==

The new Network Manager is great and now supports a useful roaming mode.

The system includes the new [[Linux]] kernel 2.6.20 which provides almost-perfect ACPI functionality.

Feisty polishes Thinkpad support for media buttons (ACPI), and gives a much more usable machine immediately following installation than Edgy.

== Installation ==

The installation has no problems.

== Known Problems ==
(Please note that these fixes will not help with Ubuntu 7.10. Problems with Suspend/Resume on that version of Ubuntu are due to yet another ATI driver problem with the kernel used in 7.10, so we are at their mercy for releasing a bugfix)
=== Suspend to RAM ===

Suspend to RAM fails during suspend, leaving the Moon blinking indefinitely.

*At one point, the Ubuntu apt-installed fglrx packages had the driver version 8.33.6, which is one of the versions that supposedly "breaks" suspend to RAM. Resuming from an otherwise successful suspend will cause the machine to resume with a blank screen without the fix below. That said, the current version in Feisty is now 8.34.8, whose release notes say "A system hang no longer occurs when attempting to resume from hibernation mode," so if you simply allow Ubuntu to update itself from the internet you can skip that step. Note however if you install the 64-bit version of Ubuntu, you may have problems with suspend to RAM not coming back on wakeup, at least with the ATI graphics option on a recent (mid-2007) T60P.
*The optional Intel Pro Wireless 3945 wireless card will often stop working even after a successful suspend, requiring a restart.
* FR, 2007may9: Actually, I have a different experience with suspend and hibernate, with a T60 15.4" (core 2 duo 2GHz, intel graphic chip 945GM): Both suspend and hibernate work for me. Initially, I had an issue with a slightly corrupted video after resume from suspend (a couple of lines near the bottom right of the screen), that I fixed by using the intel X driver instead of the i810 (that comes stock with ubuntu feisty fawn). Just load xserver-xorg-driver-intel, that will uninstall xserver-xorg-driver-i810. No other modifications necessary, stock acpi-support and xorg.conf. I can also hibernate, but I loose sound when resuming. Restarting alsa does not restore it. UPDATE: I had trouble with the video getting corrupted during the vt switch (vt 7->1) that occurs during the suspend to RAM (or hibernate). These were solved by : (1) using uswsusp (s2ram and s2disk) as s2ram -f -a 3 (forces s3_bios and s3_mode), appending acpi_sleep=s3_bios,s3_mode vga=0 to the kernel boot parameters (/boot/grub/menu.lst) and removing splash from the same kernel options. I have done that 8 days ago, and gone through 3 countries, around 50 s2ram and 4-5 s2disk without a hinch (note: I'm still using the intel video drivers)

==== Solution ====
===== Disable powernowd during suspend =====
This solution will disable the powernowd when going into Suspend, and re-enable it upon resume. For whatever reason, powernowd causes intermittent suspend problems.
# Open a terminal and type: <code>sudo gedit /etc/acpi/suspend.d/10-thinkpad-standby-led.sh</code>
# Add to the bottom of the file: <code>/etc/init.d/powernowd stop</code>
# Save the file and go back to the terminal.
# Type: <code>sudo gedit /etc/acpi/resume.d/90-thinkpad-unstandby-led.sh</code>
# Add to the bottom of the file: <code>/etc/init.d/powernowd start</code>

===== Unload IPW3945 module =====
If the Intel Pro Wireless card is installed, prevent it from disappearing during Suspend.

# Open a terminal and type: <code>sudo gedit /etc/default/acpi-support</code>
# Find the line <code>MODULES=""</code> and change it to <code>MODULES="ipw3945"</code>.
# Save the file.

===== Disable video card warm boot =====
Prevent blank screen on Resume.
# Open a terminal and type: <code>sudo gedit /etc/default/acpi-support</code>
# Next, find the line <code>POST_VIDEO=true</code> and change it to <code>POST_VIDEO=false</code>.
# Save the file.

If running the 64-bit version of Ubuntu on a T60P with the ATI graphics option, and suspend problems persist, consider installing the 32-bit version.

=== Related Ubuntu bugs ===
* [https://bugs.launchpad.net/ubuntu/+source/xresprobe/+bug/106395 Flat panel resolution 1680x1050 not detected for laptop with ATI X1400]

== Tips dist-upgrading from Ubuntu 6.10 ==
=== fglrx ===

If you have an ATI graphics card, Mesa may be active, by default, despite your xorg.conf configuration in Ubuntu 6.10.
Check whether there is hardware acceleration:

{{cmduser|fglrxinfo}}

The above should print "OpenGL vendor string: ATI Technologies Inc", among other output. If "Mesa" is present, then reinstall the fglrx driver:

{{cmduser|sudo apt-get remove xorg-driver-fglrx fglrx-control}}

{{cmduser|sudo apt-get install xorg-driver-fglrx fglrx-control}}

{{cmduser|sudo depmod -a}}

Then logout, kill the X server with control+alt+delete, and login again. Now the command 'fglrxinfo' will print the proper vendor string.

If the error persists and there is no 3D acceleration: comment out the line involving 'fglrx' in /etc/modprobe.d/lrm-video , then

{{cmduser|sudo modprobe -v fglrx}}

and restart the X server (control+alt+del). Check that the driver is loaded:

{{cmduser|lsmod}}
fglrx 540004 11
agpgart 35400 2 fglrx,intel_agp

The driver fglrx should be listed.

If this error is reported in the Xorg logs (under System / Administration / System Logs):

(EE) AIGLX error: dlsym for __driCreateNewScreen_20050727 failed (/usr/lib/dri/fglrx_dri.so: undefined symbol: __driCreateNewScreen_20050727)
(EE) AIGLX: reverting to software rendering

Turn off AIGLX by adding the following to /etc/X11/xorg.conf:

Section "ServerFlags"
Option "AIGLX" "off"
EndSection

To avoid the garbled display problem, remember that /etc/X11/xorg.conf should have the Composite option disabled. It should only be enabled for Compiz, which is not ready for Ubuntu 7.04 with ATI cards.

Section "Extensions"
Option "Composite" "0"
EndSection

== Metacity window manager==

If an unofficial compiz beta was installed at some point, then there will be two disruptive settings files under your home directory. These will prevent Metacity from displaying window decorations.

<pre>
.gnomerc
.dmrc
</pre>

Look at .gnomerc , which may contain a line specifying a window manager listed under .gnome-compiz-manager/openbox .
The second file, .dmrc, may be pointing to a Compiz desktop session that no longer exists in the system.
Remove both files.

== Resources ==
* [https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/104903 Gnome-compiz-manager thrusts itself into .gnomerc]

== References ==
* [[Installing Ubuntu 6.10 (Edgy Eft) on a ThinkPad T60|Ubuntu 6.10 Edgy Eft Installation Guide]]

== See also ==
* [[Ubuntu 7.10 on a Thinkpad T60]]

[[Category:Ubuntu 7.04]] [[Category:T60]]