ThinkWiki - User contributions [en]

ATI Mobility FireGL V5200

2010-03-31T20:28:47Z

Dave abrahams: /* Linux X.Org driver */

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

'''NewsFlash:''' recent open source drivers support 3D fully. I'm running compiz fusion on my T60p with the Ubuntu 10.04 beta, and it's slick! I still wish for a low-power mode. --[[User:Dave abrahams|Dave abrahams]] 20:28, 31 March 2010 (UTC)

Initial support included in the stable branch of the Xorg [[radeon]] driver (2D only). XVideo acceleration and 3D support have been added by the xorg driver developers and the driver is used by all majos distributions. The driver can be considered stable and fully supports Suspend-To-Disk and Suspend-To-RAM as well as XVideo acceleration in combination with composite extensions (compiz).

In addition to the radeon driver the card is also supported by the [[radeonhd]] driver. A Debian package already exists in the experimental branch. 3d is still under development and does not work satisfactorily on the T60p.

Recent releases of the ATI proprietary driver do not support this card anymore. Ever since ATI has been bought by AMD the specs for this card have been released to driver developers.

==== ThinkPad LCD ====

All current distributions offer full support for the 1600x1200 resolution of the screen.

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

==== SVideo port ====
No

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

=== Proprietary ATI driver ===

'''The following information is outdated only relevant if you use an older distribution.
'''

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

:'''NOTE:''' I also had success doing nothing more than setting <code>POST_VIDEO=false</code> (step 3). Using a T60p (2007-83U) with fglrx 8.3 (8.47.3-3~bpo40 from Debian's etch-backports) --[[User:sihde|Steve Ihde]] 31 May 2008

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.

=== Ubuntu Hardy ===
Suspend/hibernate seems to work in Hardy with latest Catalyst driver out of box (no need to edit any conf files!). The only confusing thing is that it goes to sleep and hibernate pretty fast, but it takes a long time to resume from both, especially from hibernate. The first impression that it hangs, but it's not.

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

=== Ubuntu 8.10 (Intrepid) using RadeonHD driver ===

The RadeonHD driver is coming along and is very usable for 2D graphics, and now with the v1.2.3 release of the driver (not yet in the Intrepid repos), 3D support is there (XVideo extenstion works)! I have experienced no suspend/resume issues at all with this driver, so no caveats there.

The package you need to install is xserver-xorg-video-radeonhd. You probably have this installed already if you've installed Intrepid. However, as of this writing, the version included is 1.2.1 of the driver which doesn't have the 3D support in it. I have a '''[http://www.acmeps.com/kernel/debs/xserver-xorg-video-radeonhd_1.2.3-1~pre1_i386.deb build of v1.2.3 available]''' (actually git commit 29cd7382, built by dropping the latest bits into the xserver-xorg-video-radeon source package and building) to use until Intrepid has updated packages.

['''Update 30-Apr-09''': Keeping pace with new development, I have a '''[http://www.acmeps.com/kernel/debs/xserver-xorg-video-radeonhd_1.2.5-1~pre1_i386.deb build of v1.2.5 available]''' which seems to be more stable than 1.2.3 with recent xorg 1.5.2 updates, under which I've started having spurious hangs using xv apps and crashes on resume from suspend. v1.2.5 seems to fix these, so far...]

Just a few configuration nits.

/etc/X11/xorg.conf snippet:

Section "Device"
Identifier "LCD ATI Radeon Graphics Adapter"
Driver "radeonhd"
Option "AccelMethod" "exa"
Option "DRI" "true"
BusID "PCI:1:0:0"
EndSection

You have to at least turn on DRI so the right plumbing gets hooked up for the 3D graphics. DRI in the driver is still off by default. And you can choose to not include the AccelMethod option, I've just found EXA to be faster than XAA (the default).

In previous versions of the driver you had to turn off both Composite and AIGLX. It appears you no longer need to do that, so if you have those in your Extensions or ServerFlags sections of xorg.conf, you can remove them.

There is a caveat, however, to get the kernel (2.6.27) to behave properly with a graphics console (i.e., what you get if you hit CTRL-ALT-F1). Similar to the above comment about using a framebuffer, you have to edit /boot/grub/menu.lst and change the defoptions line to something like:

# defoptions=video=vesafb vga=835

Then you type "update-grub" as root to update the kernel boot params with this new info. Mode 835 is 1400x1050 at 256 color depth. There are lots of other options, use "vga=ask" instead and reboot to find out what they are for your specific screen.

Note that you can't have "splash" on this line as the splash boot screen will mess up the console so that it becomes unusable, that is, a blank screen if you switch to any console. (Other suggestions for ways to deal with the boot console welcome.)

=== Ubuntu 9.04 (Jaunty) using RadeonHD driver ===

Version 1.2.4 of the radeonhd driver is included in the Jaunty release and should work fine.

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

[[Category:Components]]

Installing Ubuntu 7.04 (Feisty Fawn) on a ThinkPad X40

2008-12-14T01:16:45Z

Dave abrahams: /* Installation Notes for Ubuntu 8.10 (Intrepid Ibex) */

==Executive summary==
Ubuntu Linux 7.04 -and probably any modern distro- "just works" out-of-the-box on this machine.

No manual configuration was required. Even network, wifi, xorg (with 3D acceleration), sound and suspend-to-ram were properly configured and functional, all with opensource drivers only, at the end of the default Ubuntu installation. I've no problem with fan noises either.

But there's still some room for fine tuning:
* To improve energy efficiency and battery life (8 cell bat gives 4h with default install, 6h after [[How to reduce power consumption|tuning]])
* To access some special features (like some [[Default meanings of special keys|Thinkpad special keys]])
* To better use resources (memory, CPU, power, ...)

==The machine==
This an "all Intel" machine: differing from most other Thinkpad models because even the network, wireless and graphic controllers uses Intel chipsets. Note that some X40 models use atheros for wifi, or tg3 for ethernet (but not mine). That's why I opted for this one (beside the 1.2 Kg ultraportable form factor).

* IBM Thinkpad {{X40}} (model 2371Y29), Centrino platform
* 1 Go DDR SDRAM (333MHz [[PC2700]])
* CPU: [[Intel Pentium M (Dothan)]] 738 at 1.4 GHz -32KB L1 - 2Mo cache L2 - 90 nm - LV (low voltage) - 400MHz FSB (4 x 100) - MMX - SSE - SSE2 - no NX/XD bit, no hyperthreading, no 64bits - socket 479 - (Enhanced) EIST SpeedStep - CPUID : 6D6 (cpu family: 6 / model: 13 / stepping: 6)
* Southbridge chipset ICH4-M ([[Intel 82801DBM]]) : PCI, USB, IDE
* [[E1000|Intel gigabit ethernet]] controller (linux kernel module: e1000) 82541GI MT mobile (support PXE boot :)
* Wifi controller: [[Intel PRO/Wireless 2200BG Mini-PCI Adapter]] on a [[MiniPCI slot]]
* Northbridge / Graphic chipset : [[Intel Extreme Graphics 2]] ([[Intel 855GME]])
* [[Ricoh R5C511]] [[PCMCIA]] controller ([[CardBus slot]])
* [[IrDA]]
* [[TFT display]]: 12" screen, @1024x768 nominal resolution
* [[Harddisk Drives|Hard Drive]] : 1.8" - PATA - 40 Go - 4200 RPM - Hitachi DK13FA-40B
* ATA controler : [[Intel 82801DBM]] Ultra ATA storage controller 24CA
* Audio controller: [[AD1981B]] AC'97 (linux kernel module: i810_audio)
* Weigth / size: 1.24 Kg / 26.8 cm x 23.7 cm x 2.4 cm
* [[UltraBase X4]] with broken DVDROM
* Batteries :
** default small one: 4 cells, Li-Ion, 1900mAh (about 27.4W) ~ 3h00
** new one : 8 cells, Li-Ion, 4400 mAh (about 63W), 0.4 kg, ref (FRU) : IBM-92P1083 ~5h30
* BIOS version : 1UETD3WW (2.08 ), built on 2006-12-21, released on 2007/01/31
* IBM ThinkPad Embedded Controller version : 1UHTA6WW (1.56)
* FW model : TP-1U

==Installation==
The {{X40}} is a very small ultraportable, and doesn't have builtin CDROM or floppy drive. I own an IBM [[UltraBase X4]] dock station, but her DVDrom is dead. So I went for PXE (network boot) installation for the first time ; I just applied instructions from [http://wiki.koeln.ccc.de/index.php/Ubuntu_PXE_Install this web page] : this was unexpectedly simple and worked flawlessly. Everything got installed from network, "over the air".

I kept the 4Go [[Hidden Protected Area|IBM recovery]] partition at the end of the drive, by superstition and for [[Rescue and Recovery]]. Afterwards, I compiled my own 2.6.22 kernel, patched with high resolution timers, to improve the battery life, and applied tips from the ''[[How to reduce power consumption]]''.

==Small glitches==
===Distribution (Ubuntu Feisty Fawn 7.04)===
Even if everything was supported, there was some small things where Ubuntu (or Gnome, or Linux kernel) could have done better:
* Suspend-to-ram works out-of-the-box, no special tricks are needed. But sometimes, not always, for an unknown reason, the Gnome "logout" screen hides the s2ram and s2disk (hibernate) options. Whatever, we still can suspend thanks to the thinkpad's special keys (or just with an "echo mem > /sys/power/state").
* Ubuntu installs the "special keys" handler from the "hotkey-setup" package. This is suboptimal, since hotkey-setup supports less special keys than [[tpb]], and consumes a lot of battery (see for instance this [https://bugs.launchpad.net/ubuntu/+source/hotkey-setup/+bug/45404 bug report]).
* More generally, the whole Ubuntu system needs work to become power efficient on laptops: switch to a 2.6.21 or more kernel, use in kernel "ondemand" governor rather than userland powernowd+hald-addon-cpufreq, activate AC97 power saving features when on battery, etc.
* The default Ubuntu install left me with a lot processes related to printing (cupsd, gnome-cups-icon, hpiod, hpssd (this one is a python script!)) while I have no printer configured nor attached. Bad. They shouldn't start this until hald find something plugged or until I try to configure a printer. It also left the bluetooth "hcid" daemon, while I've no bluetooth controller. evolution-alarm-notify is running while I've never launched (let alone configured) Evolution.

===Hardware and BIOS limitations===
The hardware is fine for me, even if a bit old by nowadays standards (I'd prefer have an Intel AHCI chipset with SATA drive on it, for power efficiency reason, and I'd prefer a Core2Duo CPU....). It lacks also some options available on some other Thinkpads models, like the fingerprint reader (but seriously, I prefer give this up to keep my "all Intel" chipsets). It lacks a Firewire controler. The BIOS is also somehow suboptimal, in some aspects.

For an unknown reason, the BIOS disable by default the deeper power saving c-states (C3 and C4). There's two option for this that you need to turn on, despite the the misleading BIOS online help that says "usualy not needed". Type "F1" during boot to access the BIOS, then enable:
<code>
CPU power management
PCI bus power management
</code>

The BIOS, as in many laptops, hides the HPET hardware timer to the system. Windows XP don't support HPET and when enabled, it displays a yellow exclamation mark on his device manager list, hence the common vendor choice to disable it. That's a bit odd since Linux can make a great use of it: other available timers (PIC/LAPIC) can't schedule timer events more than a few milliseconds away, so they causes about 20 to 40 CPU wakeups per second. This impact the power consumption greatly. Yet, thanks to the Udo A. Steinberg and Venki Pallipadi, we have a way to force enable HPET on chipsets known to support it (this include ICH3-M, ICH4-M, ICH5-M etc.). So I applied their patch, part of the [http://www.tglx.de/projects/hrtimers/|High Resolution Timer patchset] on top of my hand compiled 2.6.22-rc5 kernel, and all worked fine: <code>dmesg | grep hpet</code>:

<code>
[ 3.740522] hpet clockevent registered
[ 3.740527] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0
[ 3.740532] hpet0: 3 64-bit timers, 14318180 Hz
[ 5.080000] Time: hpet clocksource has been installed.
</code>

==Not tested yet==
* [[Embedded Security Subsystem|TCPA chipset]]: Trusted Computing controller. Should be supported by [[tpm]] and [[tpmdd]] but who need this, really ?
* [[HDAPS]] (Hard Drive protection mechanism): this should work out of the box, we have a kernel module for that but I disable it because it's known to suck power
* [[IrDA]] (Infrared controller) : is known to work too, and looks supported by my kernel, but I've no other IrDA device to test with
* [[SD Card slot]] : I've no SD cards to test this
* [[IBM Integrated 56K Modem (MDC-2)|56K Modem]]: I've no use of this

==System informations==
'''dmesg | grep states'''
<code>
[ 5.280003] ACPI: CPU0 (power states: C1[C1] C2[C2] C3[C3] C4[C4])
[ 5.280009] ACPI: Processor [CPU] (supports 8 throttling states)
</code>

'''lspci''' :
<code>
00:00.0 Host bridge: Intel Corporation 82852/82855 GM/GME/PM/GMV Processor to I/O Controller (rev 02)
00:00.1 System peripheral: Intel Corporation 82852/82855 GM/GME/PM/GMV Processor to I/O Controller (rev 02)
00:00.3 System peripheral: Intel Corporation 82852/82855 GM/GME/PM/GMV Processor to I/O Controller (rev 02)
00:02.0 VGA compatible controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02)
00:02.1 Display controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02)
00:1d.0 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 (rev 01)
00:1d.1 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2 (rev 01)
00:1d.2 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3 (rev 01)
00:1d.7 USB Controller: Intel Corporation 82801DB/DBM (ICH4/ICH4-M) USB2 EHCI Controller (rev 01)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 81)
00:1f.0 ISA bridge: Intel Corporation 82801DBM (ICH4-M) LPC Interface Bridge (rev 01)
00:1f.1 IDE interface: Intel Corporation 82801DBM (ICH4-M) IDE Controller (rev 01)
00:1f.3 SMBus: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) SMBus Controller (rev 01)
00:1f.5 Multimedia audio controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller (rev 01)
00:1f.6 Modem: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Modem Controller (rev 01)
02:00.0 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev 8d)
02:00.1 Generic system peripheral [0805]: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 13)
02:01.0 Ethernet controller: Intel Corporation 82541GI Gigabit Ethernet Controller
02:02.0 Network controller: Intel Corporation PRO/Wireless 2200BG Network Connection (rev 05)
</code>

'''cat /proc/cpuinfo'''

<code>
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 13
model name : Intel(R) Pentium(R) M processor 1.40GHz
stepping : 6
cpu MHz : 600.000
cache size : 2048 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 2
wp : yes
flags : fpu vme de pse tsc msr mce cx8 apic sep mtrr pge mca cmov pat clflush dts acpi mmx fxsr sse sse2 ss tm pbe up est tm2
bogomips : 1196.93
clflush size : 64
</code>

==Other Linux installation reports on Thinkpad X40==
Don't forget that the X40 line included different ethernet (tg3 or e1000) and wireless (atheros or Intel) chipsets, and that Linux support involved over time. So there may be some difference between your experience with X40 and others reports. Some reports are quite old too, and Linux involve at fast pace.

'''Thinkwiki internal notes about installing Linux on X40'''
*{{Install|Gentoo||X40}}
*{{Install|Debian||X40}}
*{{Install|Fedora| Core|X40}}

'''Exernal links to notes about installing linux, OpenBSD and FreeBSD on X40'''

* [http://gentoo-wiki.com/HARDWARE_IBM_ThinkPad_X40 HARDWARE IBM ThinkPad X40] on the Gentoo wiki
* [http://www.srcf.ucam.org/~mjg59/thinkpad/x40acpi.html ''Linux and ACPI on an IBM Thinkpad X40''], by Matthew Garrett
* [http://littlesvr.ca/linux-stuff/articles/x40slack/x40slack.php Slackware 10.1 and 10.2] on X40, by Andrew Smith
* [http://people.bath.ac.uk/masrjb/x40.html SuSE 9.1] on X40, by Russell Bradford
* [http://www.sun.com/bigadmin/hcl/data/systems/details/1454.html Solaris] on X40, on Sun's BigAdmin database
* [http://www.cl.cam.ac.uk/~pb22/TPX40/ Red Hat 9] on X40, by Piete Brooks
* [http://blog.tarotoast.com/2007/01/13/333/ PC-BSD] on X40, by Tarotoast
* [http://www.roe.ch/FreeBSD_on_the_IBM_ThinkPad_X40 FreeBSD 5.4] on X40, by Daniel Roethlisberger
* [http://www.iosn.net/Members/kaeru/articles/freebsd/x40 FreeBSD 5.3] on X40, by Khairil Yusof
* [http://lowerca.se/laptops/ OpenBSD] on X40, by Joshua Stein
* [http://www.openbsd.org/i386-laptop.html OpenBSD], OpenBSD official site, i386-laptops page
* [http://www.citi.umich.edu/u/rees/openbsd/tpx40.html OpenBSD 3.9, 4.0 and 4.1] on X40, by Jim Rees
* [http://www.catb.org/~esr/faqs/Fedora-Core-on-Thinkpad-X40/ Fedora Core] on X40, by the infamous Eric S. Raymond
* [http://johnleach.co.uk/documents/thinkpadx40/index.html Fedora] on X40, by John Leach
* [http://www.mrc-cbu.cam.ac.uk/~matthew/linuxiste/10p1/x40_mandrake_10p1.html Mandrake 10.1] on X40, by Matthew Brett
* [http://soft.zoneo.net/Linux/x40.php Mandriva 10.1] on X40, by ZoneO
* [http://soft.zoneo.net/Linux/x40_2006.php Mandriva 2006] on X40, by Zone0
* [http://www.linux-on-laptops.com/hosted/ubuntu-thinkpad-x40.html Ubuntu Feisty 7.04], by Chris Cartledge
* [http://www.tenshu.net/archives/2006/08/08/ubuntu-dapper-606-lts-on-an-ibmlenovo-thinkpad-x40/ Ubuntu Dapper 6.06] on X40, by cmsj
* [http://www.noapparentmotive.org/topics/ubuntuX40.html Ubuntu Breezy 5.04] on X40, by John Schmitt
* [http://www.leopold.dk/~martin/IBMx40UbuntuInstall.html Ubuntu Breezy 5.04] on X40, by Martin Leopold
* [http://martin.wuertele.net/x40/ Debian] on X40, by Martin Würtele
* [http://www.chronox.de/x40_linux/linux_on_x40.html Debian] on X40, by Stephan Müller;
* [http://steffenpingel.de/news/archive/2005/apr/22/linux-debian-on-ibm-thinkpad-x40/ Debian] on X40, by Sebastian Schmieg
* [http://m.ash.to/@/@/Linux/DebianOnThinkpadX40 Debian/GNU Linux 3.1 (Sarge)], by Michael Aschauer
* [http://www.mathematik.uni-marburg.de/~dfinke/html/howto.html Debian GNU/Linux Unstable with ACPI on an IBM Thinkpad X40], by madn3ss
* [http://grapevine.net.au/~striggs/thinkpad-x40.html Debian] on X40 (with example PXE network install), by Mark Triggs

==Installation Notes for Ubuntu 8.04 LTS (Hardy Heron)==

Support for the Thinkpad X40 has improved even more in Hardy Heron. A few things to consider that have changed:

1) hotkey-setup has matured to the point that it no longer drains power, so it is now superior to tpb. My X40 has a nice little GUI that pops up when you change the volume/brightness using hotkeys.

2) Although powersaved is still used, laptop-mode-tools is also installed by default. You can go to /etc/laptop-mode/laptop-mode.conf to use the ondemand kernel governor.

3) hpet is now in the ubuntu sources. However, you have to boot with hpet=force to get it work.

4) CPU undervolting is very well supported by the X40. http://ubuntuforums.org/showthread.php?t=786402 has all the information you need. I use the following set of phc values with perfectly stable results:
12:15 11:12 10:9 9:6 8:4 6:1

5) To enable middle-wheel scrolling, go to /etc/X11/xorg.conf and add the following to the "configured mouse" section:
<pre>Option "EmulateWheel" "true"
Option "EmulateWheelButton" "2"</pre>

6) To make the NumLock (Shift+ScrLk) and the Back/Forward buttons near the arrow keys work, add the following to ~/.Xmodmap:
<pre>keycode 77 = Num_Lock
keycode 234 = XF86Back
keycode 233 = XF86Forward</pre>

7) NOTE: THE BELOW METHOD STILL RESULTS IN SYSTEM FREEZES FOR ME (Thinkpad X40, 1.2 Ghz Banias)

For at least kernel 2.6.24, [[UltraBase X4]] actions are detected by ACPI's <tt>dock</tt> driver. By default, [[UltraBay]] devices are not accounted for by the event handlers. This leads to system freezing when ejecting and undetected peripherals on docking. The <tt>ultrabay_insert</tt> and <tt>ultrabay_eject</tt> scripts from [[How to hotswap UltraBay devices]] can be used to achieve safe (un)docking.

Edit {{path|/etc/modprobe.d/options}}:
<pre>
options dock immediate_undock=0
</pre>

Create {{path|/usr/local/sbin/ultrabase_dock}} with permissions 755:
<pre>
#!/bin/sh

/usr/local/sbin/ultrabay_insert
# Anything else that you want executed on docking goes here.
</pre>

Create {{path|/usr/local/sbin/ultrabase_eject}} with permissions 755:
<pre>
#!/bin/sh

/usr/local/sbin/ultrabay_eject
# Anything else that you want executed on ejection goes here.

echo 1 > /sys/devices/platform/dock.0/undock
</pre>

Create {{path|/etc/udev/rules.d/50-ibm-ultrabase.rules}}:
<pre>
ENV{EVENT}=="undock", KERNEL=="dock.0", SUBSYSTEM=="platform", RUN+="/usr/local/sbin/ultrabase_eject"
ENV{EVENT}=="dock", KERNEL=="dock.0", SUBSYSTEM=="platform", RUN+="/usr/local/sbin/ultrabase_insert"
</pre>

Restart <tt>udev</tt>.

Now, the system will remove the [[UltraBay]] device when the undock button is pressed. The laptop can be removed when the dock's LED turns off. When docking, the [[UltraBay]] devices will be scanned and should be detected automatically.

==Installation Notes for Ubuntu 8.10 (Intrepid Ibex)==

"options dock immediate_undock=0" worked great in Hardy but no longer seems to work in Intrepid. See https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/307801 --[[User:Dave abrahams|Dave abrahams]] 02:16, 14 December 2008 (CET)

Using the older 8.04 the VGA-out works well. You could plug in an external monitor and Fn-F7 to switch on VGA-out. It will auto-detect the external monitor, and change desktop resolution.

However VGA-out does not work as well with 8.10. Currently it seems the X-server needs to be restarted after the external monitor is connected.

Also, the back-light-brightness applet does not work with 8.10, though hardware control still works.

edit: I wrote too soon. NetworkManager and suspend have reliability problems on the X40 in 8.10. Best to stick with 8.04 until these are fixed.

[[Category:X40]] [[Category:Ubuntu 7.04]] [[Category:Ubuntu 8.04]] [[Category:Ubuntu 8.10]]

Suspend/Resume Support For SATA Link Power Management

2008-05-05T00:18:53Z

Dave abrahams: â†Created page with '== Synopsys == One good way to save power with a dynticks-enabled kernel is to set [http://www.lesswatts.org/tips/disks.php SATA link power management] to minimum pow...'

== Synopsys ==

One good way to save power with a [[dynticks]]-enabled kernel is to set [http://www.lesswatts.org/tips/disks.php SATA link power management] to minimum power. However, if you do that you will probably experience long delays when resuming from suspend-to-disk. If, like {{Ubuntu}} Hardy, your distribution uses <tt>pm-suspend</tt>, the following script placed in <tt>/etc/pm/sleep.d/99sata</tt> will set the link power to maximum performance just before suspending, and restore it to whatever it was upon resume.

<pre>
#!/bin/bash

[ -d /sys/class/scsi_host/ ] || exit 0

. /usr/lib/pm-utils/functions

suspend_sata()
{
pushd /sys/class/scsi_host/ > /dev/null 2>&1
local host
for host in $(ls -1); do
if [ -e ${host}/link_power_management_policy ]; then
local policy=$(cat ${host}/link_power_management_policy)
savestate ${host}_link_power_management_policy "${policy}"
echo max_performance > ${host}/link_power_management_policy
fi
done
popd
}

resume_sata()
{
pushd /sys/class/scsi_host/ > /dev/null 2>&1
local host
for host in $(ls -1); do
if [ -e ${host}/link_power_management_policy ]; then
local policy=$(restorestate $(echo ${host}_link_power_management_policy))
echo ${policy} > ${host}/link_power_management_policy
fi
done
popd
}

case "$1" in
suspend|hibernate)
suspend_sata
;;
resume|thaw)
resume_sata
;;
*)
;;
esac

exit $?
</pre>

Installing Ubuntu 8.04 (Hardy Heron) on a ThinkPad T60

2008-05-05T00:05:17Z

Dave abrahams: SATA Link Power Management support for Suspend/Resume

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

You may have trouble connecting to some access points as described in [https://bugs.launchpad.net/ubuntu/+source/linux-ubuntu-modules-2.6.22/+bug/176602 this bug report]. I was connecting with WPA2 just fine at home and then went away on a trip and couldn't connect to an ''unencrypted'' network! The fix as described there is to install the linux-backports-modules-hardy package, which contains an updated driver.

=== 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)]]. To get the most of [[dynticks]] it is a good idea to install powertop with {{cmduser|sudo aptitude install powertop}} and take the advice it gives when you invoke it. Powertop may recommend that you use [http://www.lesswatts.org/tips/disks.php SATA Link Power Management], in which case you'll want [[Suspend/Resume_Support_For_SATA_Link_Power_Management|this script]] to avoid long delays when resuming from suspend.

More information on power saving is available at http://www.lesswatts.org.

== 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 8.04 (Hardy Heron) on a ThinkPad T60

2008-05-03T23:33:12Z

Dave abrahams: /* Open Source Intel Wifi Driver */

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

You may have trouble connecting to some access points as described in [https://bugs.launchpad.net/ubuntu/+source/linux-ubuntu-modules-2.6.22/+bug/176602 this bug report]. I was connecting with WPA2 just fine at home and then went away on a trip and couldn't connect to an ''unencrypted'' network! The fix as described there is to install the linux-backports-modules-hardy package, which contains an updated driver.

=== 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 8.04 (Hardy Heron) on a ThinkPad T60

2008-05-03T23:31:06Z

Dave abrahams: Note updated driver availability

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

You may have trouble connecting to some access points as described in [[https://bugs.launchpad.net/ubuntu/+source/linux-ubuntu-modules-2.6.22/+bug/176602|this bug report]. I was connecting with WPA2 just fine at home and then went away on a trip and couldn't connect to an ''unencrypted'' network! The fix as described there is to install the linux-backports-modules-hardy package, which contains an updated driver.

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

Problems with fglrx

2008-04-30T10:46:55Z

Dave abrahams: /* Troubles using software suspend */

This page discusses issues with the ATI proprietary [[fglrx]] display driver.

== Known Troubles and Solutions ==

=== X-specific issues ===

==== upgrading xserver-xorg ====
ATI proprietary drivers version 8.21.7 and later work with x.org 6.9.

If you are running an older version (8.20.8) under Debian sid and you upgrade your xserver-xorg, apt will force you to remove any debian-packaged fglrx drivers (package fglrx-driver depends on x.org << 6.8.99). You can just download the driver from the ATI site and install after modifying the Debian packager script to allow dependencies to be satisfied by x.org 6.9, or just download 8.21.7 and install manually. See talk page for step-by-step commands.

After installing the fglrx driver, you can use module-assist to build the appropriate kernel module.

==== new Xorg ID Scheme ====
ATI proprietary drivers <=8.36.5 with xorg >=7.1.0-18 (==1.3.0.0) in Debian Sid and Fedora ([http://www.sidux.com/PNphpBB2-viewtopic-t-3162-postdays-0-postorder-asc.html Debian] and [http://www.phoronix.net/forums/showthread.php?t=2382 Fedora] Forum Entries)

Ubuntu feisty made their own xorg with the standard id of 7.2, to work around this issue.

Xorg has changed its ID Scheme in newer Versions, and fglrx cannot cope with that (Error message saying "[...] X version mismatch - detected X.org 1.3.-1.905, required X.org 7.1.0.0 [...]").

A binary hack solves the Problem [http://rage3d.com/board/showthread.php?s=4638d94143536f6acacbccd8f0443472&t=33889029 (rage3d.com Forum Entry)]. This is a very '''dirty''' solution, and is probably violating the ATI driver license.

Simply using the open source ati driver (or holding back the xorg upgrades) until a new driver is released, is suggested.

As of version 8.37.6, this issue is solved. No more binary hacking needed.

=== Kernel-specific troubles ===

Using ATI drivers <=8.21.7 with kernel >=2.6.15 needs a [http://marc.theaimsgroup.com/?l=linux-kernel&m=113429835515001&w=2 patch]. (see table below for detail.) If you can't compile the driver modules with 2.6.15 or later, you should apply this [http://www.ksp.sk/~rasto/fglrx_with_2.6.15.patch patch] instead.

If you do not use one of these patches, you may experience peculiar lockups of X. Try {{cmduser|fglrxinfo}} - if your shell hangs at the end of this command, you may have an issue and should try the patch or upgrade.

Although unproven, there is a substantial amount of user / developer concern that the above patches prevent hard lockups but do not provide full reliability with 2.6.15 and there are larger / redisgn issues preventing compatibility. These issues have been fixed with later ATI drivers (> 8.21.7) so you can simply upgrade if you are running a more modern kernel.

==== 2.6.23 ====
In 2.6.23 release cycle, config option CONFIG_SUSPEND_SMP got renamed to CONFIG_PM_SLEEP_SMP. fglrx uses this variable for disabling power management on older kernels. As a result, SMP users running 2.6.23 weren't able to resume properly (almost instant lockup in that rare case fglrx managed to show a few usable pixels. A [http://linux.derkeiler.com/Mailing-Lists/Kernel/2007-10/msg03437.html quick patch] is available.

=== No hardware acceleration ===

====Acceleration lost after driver update====
If you lose hardware acceleration after a driver update this can be caused by an old fglrx kernel module being loaded.

Check out {{path|1=/var/log/Xorg.0.log}} for a message like:
:<code>(WW) fglrx(0): Kernel Module version does *not* match driver.</code>
:<code>(EE) fglrx(0): incompatible kernel module detected - HW accelerated OpenGL will not work</code>

You can verify this yourself by looking at the version message some lines above. It should read something not matching the installed version like:
:<code>(II) fglrx(0): Kernel Module Version Information:</code>
:<code>(II) fglrx(0): Name: fglrx</code>
:<code>(II) fglrx(0): Version: 8.10.19</code>

The cause for this trouble might be that there resist multiple versions of the fglrx module within the kernel module search path.<br>
Go to {{path|1=/lib/modules/<your linux kernel version>/}} and type {{cmdroot|1=grep fglrx modules.dep}}.<br>
If grep finds multiple lines you nailed down the problem. All you have to do now is to delete any versions of the module (look at the filedate) but the most current one. Then run {{cmdroot|1=depmod}} and you are done.

{{HINT|Newer versions (8.21.7) of the fglrx module seem to be installed in the <code>extra/</code> subdirectory.<br>
Older versions (8.19.10) used to be located in the <code>kernel/drivers/char/drm/</code> subdirectory.}}

====GCC 3.4====
If the ATI driver works only without the hardware acceleration, take into consideration that {{path|fglrx_dri.so}} was linked against libstdc++.so.5 which may not be present if your system uses gcc-3.4.

To fix this, compile gcc-3.3.5 and copy <tt>libstdc++.so.5*</tt> to {{path|/usr/lib}} and update the dynamic linker cache via {{cmdroot|ldconfig}}.

Or install a compat package for your favorite distro. FC4 users can do:
:{{cmdroot|yum install libstdc++.so.5}}

====radeonfb framebuffer====
Another possible cause for broken hardware acceleration (2D and 3D) is the radeonfb framebuffer: Switching to vesafb or vesafb-tng is reported to solve the problem on some systems. Also it has proven helpful to not perform {{cmdroot|modprobe fglrx}} after boot but to have the module loaded via {{path|/etc/modules.autoload/kernel2.x}} at boottime instead.

====Perpetual Mesa GLX Indirect on Debian====
If you've done everything right and you're still seeing:

:{{cmduser|fglrxinfo}}
:{{cmdresult|display: :0.0 screen: 0}}
:{{cmdresult|OpenGL vendor string: Mesa project: www.mesa3d.org}}
:{{cmdresult|OpenGL renderer string: Mesa GLX Indirect}}
:{{cmdresult|OpenGL version string: 1.2 (1.5 Mesa 6.4.1)}}

try this:

:{{cmdroot|mkdir -p /usr/X11R6/lib/modules/dri}}
:{{cmdroot|ln -s /usr/lib/dri/fglrx_dri.so /usr/X11R6/lib/modules/dri}}

Thanks to Maciej Matysiak for the clear debug [http://lists.debian.org/debian-amd64/2006/02/msg00217.html here] and solution [http://lists.debian.org/debian-amd64/2006/02/msg00311.html here].

More generally, use LIBGL_DEBUG=verbose fglrxinfo, to see what's happening, and whether you get this:
:{{cmduser|<nowiki>LIBGL_DEBUG=verbose</nowiki> fglrxinfo}}
:{{cmdresult|libGL: XF86DRIGetClientDriverName: 8.26.18 fglrx (screen 0)}}
:{{cmdresult|libGL: OpenDriver: trying /usr/X11R6/lib/modules/dri/fglrx_dri.so}}
:{{cmdresult|libGL error: dlopen /usr/X11R6/lib/modules/dri/fglrx_dri.so failed (/usr/X11R6/lib/modules/dri/fglrx_dri.so: cannot open shared object file: No such file or directory)}}
:{{cmdresult|libGL error: unable to find driver: fglrx_dri.so}}
:{{cmdresult|display: :0.0 screen: 0}}
:{{cmdresult|OpenGL vendor string: Mesa project: www.mesa3d.org}}
:{{cmdresult|OpenGL renderer string: Mesa GLX Indirect}}
:{{cmdresult|OpenGL version string: 1.2 (1.5 Mesa 6.4.2)}}

instead of that:
:{{cmduser|<nowiki>LIBGL_DEBUG=verbose</nowiki> fglrxinfo}}
:{{cmdresult|libGL: XF86DRIGetClientDriverName: 8.26.18 fglrx (screen 0)}}
:{{cmdresult|libGL: OpenDriver: trying /usr/X11R6/lib/modules/dri/fglrx_dri.so}}
:{{cmdresult|libGL: XF86DRIGetClientDriverName: 8.26.18 fglrx (screen 0)}}
:{{cmdresult|drmOpenByBusid: busid is PCI:1:0:0}}
:{{cmdresult|drmOpenDevice: minor is 0}}
:{{cmdresult|drmOpenDevice: node name is /dev/dri/card0}}
:{{cmdresult|drmOpenDevice: open result is 4, (OK)}}
:{{cmdresult|drmOpenByBusid: drmOpenMinor returns 4}}
:{{cmdresult|drmOpenByBusid: drmGetBusid reports PCI:1:0:0}}
:{{cmdresult|Can't open configuration file /home/merlin/.drirc: No such file or directory.}}
:{{cmdresult|fglrx: DPD supported.}}
:{{cmdresult|display: :0.0 screen: 0}}
:{{cmdresult|OpenGL vendor string: ATI Technologies Inc.}}
:{{cmdresult|OpenGL renderer string: MOBILITY FIREGL T2 Pentium 4 (SSE2) (FireGL) (GNU_ICD)}}
:{{cmdresult|OpenGL version string: 2.0.5879 (8.26.18)}}

I have contacted ATI to add that info by default, the mesa guys to do that in glxinfo too, as well as the debian packager to fix the debian packaging bug (2006/07/22), so hopefully the situation will improve soon

You may have to run fglrxinfo as root to get this detail rather than a useless message.

==== Where to look for fglrx_dri.so (gentoo and general)====
After installing a new kernel (linux-2.6.20-gentoo-r7) with gentoo I again was not able to get the ATI driver working
correctly. But now I found out what the problem was:

I tried
:{{cmduser|<nowiki>LIBGL_DEBUG=verbose</nowiki> fglrxinfo}}
:{{cmdresult|libGL: XF86DRIGetClientDriverName: 8.35.5 fglrx (screen 0)}}
:{{cmdresult|libGL: OpenDriver: trying /usr/lib32/dri/fglrx_dri.so}}
:{{cmdresult|libGL error: dlopen /usr/lib32/dri/fglrx_dri.so failed (/usr/lib32/dri/fglrx_dri.so: wrong ELF class: ELFCLASS32)}}
:{{cmdresult|libGL error: unable to find driver: fglrx_dri.so}}

The error itself makes sense, because I am running a 64-Bit linux on AMD. The question was, why libGL tries to look
in /usr/lib32 only...

After some digging around I found out, that apparently 8.35.5 version of the driver uses the environment variable
'''LIBGL_DRIVERS_PATH''' to find out where it should look for the "fglrx_dri.so" driver.

Now in my case this environment variable pointed to "/usr/lib32/dri" and that was what caused the problem.
So doing
:{{cmduser|<nowiki>export LIBGL_DRIVERS_PATH='/usr/lib64/dri:/usr/lib32/dri'</nowiki>}}
solved the problem in my case.

As mentioned I use gentoo. After some more digging around I found out, that it is apparently necessary to call
:{{cmduser|env-update}}
after a re-install of the ATI driver. To be more specific, it seems that "eselect opengl set ati" sometimes
does something wrong. "env-update" seems to repair the problem so that afterwards the '''LIBGL_DRIVERS_PATH'''
environment variable is set correctly when you log in.

If you want to check, look in <code>/etc/profile.env</code> and <code>/etc/profile.csh</code>. This is the
place where the '''LIBGL_DRIVERS_PATH''' environment variable gets set.

=== Softlink hell ===
The [[fglrx]] installer replaces the standard X.org OpenGL implementation (Mesa) with its own files, potentially causing collisions with the distribution's file and package management. It is best to install the driver via a package built for your distribution, which will typically include the necessary kludges to make things work. See the [[fglrx]] page for pointers.

====Discussion====
If using {{cmduser|fglrxinfo}} after installing [[fglrx]] indicates that you are still using the mesa indirect software GL renderer, you likely have some misplaced softlinks. It seems like it has to do with an apt-get upgrade that sometimes replaces these links. Anyway, go to
:{{cmdroot|cd /usr/X11R6/lib}}
and list your GL libraries and links
:{{cmdroot|ls -la *GL*}}
You should see something like the following two lines amoung others:
:{{cmdresult|libGL.so -> libGL.so.1.2}}
:{{cmdresult|libGL.so.1 -> libGL.so.1.2}}
If you see a link to a mesa library (something like {{cmdresult|... -> libGL.mesa.1.2}}), then that's your problem! Restore the softlink like this (use your actual library version, though):
:{{cmdroot|ln -s libGL.so.1.2 libGL.so.1}}

For some reason, this link might "break" later, giving you the software rendering once more. Even after renaming the mesa library to something like <tt>mesa.bkup</tt>, the system might still find it and link to it despite the name change. If you have to do this a lot, you could write a restoreGL script.

=====Gentoo=====
{{Gentoo}} has built in tools for managing the OpenGL symlinks.
:{{cmdroot|eselect opengl set ati}}
If <tt>eselect opengl ati</tt> doesn't fix it for you, you should probably tell [http://bugs.gentoo.org Gentoo Bugzilla] (assuming they don't know yet).

If {{cmdroot|ldd /usr/X11R6/bin/glxinfo}} shows that your system still uses the xorg-x11 mesa libs after trying one of the above commands, i.e. a line like this:
:{{cmdresult|1=libGL.so.1 => /usr/lib/opengl/xorg-x11/lib/libGL.so.1 (0x400a8000)}}
you will also need to relink {{path|libGl.so.1.2}}:
:{{cmdroot|cd /usr/lib/opengl/xorg-x11/lib/}}
:{{cmdroot|mv libGL.so.1.2 libGL.so.1.2_backup}}
:{{cmdroot|ln -s /usr/lib/libGL.so.1.2 libGL.so.1.2}}
After another restart of X {{cmduser|fglrxinfo}} should show that it's using the right libs now.

=====Debian=====

:{{cmdroot|rm /usr/lib/libGL.so*}}
:{{cmdroot|rm /usr/X11R6/lib/libGL.so*}}
:{{cmdroot|cd /usr/X11R6/lib}}
:{{cmdroot|cp /usr/lib/fglrx/diversions/lib/libGL.so.1.2 .}}
:{{cmdroot|ln -s libGL.so.1.2 libGL.so.1}}
:{{cmdroot|ldconfig}}

=== Troubles using software suspend ===

Resume doesn't work when any AIGLX clients are active. See https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-2.6.24/+bug/197209 for details and a workaround.

Resume doesn't work with any USB devices plugged into an attached dock. See https://bugs.launchpad.net/ubuntu/+bug/218760 for details and a workaround.

Suspend won't work on any distribution which has activated the new SLUB allocator with fglrx < 8.42. This affects e.g. Ubuntu 7.10 Gutsy (see https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/121653/). The only workaround is currently to compile a custom kernel with SLAB support!

When the computer resumes from suspend, X only displays a garbled image and the computer is frozen.
The problem is acknowledged in ATI's release notes and in knowledge base entry <strike>[https://support.ati.com/ics/support/KBResult.asp?searchFor=Search+Words&search.x=0&search.y=0&searchOption=id&questionID=737-218+&task=knowledge&searchTime=-1&productID=&folderID=-1&resultLimit=50 737-218]</strike> [https://support.ati.com/ics/support/KBAnswer.asp?questionID=218 737-218]. Driver version 8.19.10 has "initial support for Suspend and Resume" but is working very nicely for most people (verified on T43, T43p and T42) without vbetool.

If you are using an older version of fglrx, using [http://www.srcf.ucam.org/~mjg59/vbetool/ vbetool] to save/restore the video card state before/after suspend worked for some people. If you use [[Software Suspend 2|Software Suspend 2 (suspend2)]] scripts, you can simply uncomment <tt>EnableVbetool yes</tt> in {{path|/etc/hibernate/hibernate.conf}}. Be aware though that it breaks suspend/resume for drivers beginning with version 8.19.10, so remember to disable it again when upgrading.

{| cellspacing="0" cellpadding="2" border="1"
|+ tested with the following configurations
!model!!distro||kernel!!fglrx!!PM!!success!!comments
|-
|{{T42}}||SUSE 9.3||2.6.11||8.14.13||swsusp||yes||
|-
|{{T41p}}||???||2.6.14||8.19.10||suspend2 2.2-rc9||yes||needs a small [http://mailman.linux-thinkpad.org/pipermail/linux-thinkpad/2005-November/030381.html patch]
|-
|{{T42p}}||Debian||2.6.10||Debian packaged||suspend2||yes||
|-
|{{T43}}||Debian sid||2.6.14.2||8.19.10||swsusp||yes||works perfectly with 8.19.10 (but not earlier versions!)
|-
|{{T43}}||Debian etch||2.6.14.2||8.19.10||swsusp||yes||works perfectly with 8.19.10 and without vbetool
|-
|{{T43}}||Ubuntu Breezy||2.6.12-10||8.19.10||swsusp||yes||Perfect. (Finally.)
|-
|{{T43}}||FC4||2.6.14.1||8.19.10||suspend2 2.2-rc9||yes||needs a small [http://mailman.linux-thinkpad.org/pipermail/linux-thinkpad/2005-November/030381.html patch], requires DRI disabled in {{path|xorg.conf}} (hence no 3D acceleration)
|-
|{{T43}}||FC4||2.6.14.2||8.19.10||suspend2 2.2-rc11||yes||requires DRI disabled in {{path|xorg.conf}} (hence no 3D acceleration)
|-
|{{T43}}||FC4||2.6.14.3||8.19.10||suspend2 2.2-rc13||no||DRI enabled
|-
|{{T43}}||FC4||2.6.14.3||8.20.8||suspend2 2.2-rc13||no||DRI enabled
|-
|{{T43p}}||FC6||2.6.20-1.2933||8.34.8||swsusp, STR||yes||DRI enabled, occasionally fails, reason unknown.
|-
|{{R50p}}||???||???||8.19.10||swsusp||yes||
|-
|{{T43p}}||Debian sid||2.6.14||8.19.10||Suspend to RAM||yes||without vbetool or UseDummyXServer, those two ''break'' the resume process here, with DRI enabled
|-
|{{T43p}}||Debian sid||2.6.14.3||8.20.8||Suspend to RAM||yes||without vbetool or UseDummyXServer, with DRI enabled
|-
|{{R52}}||Debian sid||2.6.15-rc5||8.20.8||swsup||yes||both vbetool and UseDummyXServer disabled, DRI enabled, needs [http://marc.theaimsgroup.com/?l=linux-kernel&m=113429835515001&w=2 patch]
|-
|{{T43p}}||Gentoo||[http://packages.gentoo.org/ebuilds/?suspend2-sources-2.6.15-r6 2.6.15]||8.22.5||Suspend to RAM||yes||without vbetool or UseDummyXServer, with DRI enabled - console is garbled until switching back from X
|-
|{{T43p}}||Gentoo||[http://packages.gentoo.org/ebuilds/?suspend2-sources-2.6.15-r6 2.6.15]||8.22.5||suspend2 2.2||yes||without vbetool or UseDummyXServer, with DRI enabled
|-
|{{T43}}||SUSE 10.1||2.6.16||8.25.18||swsusp||yes||without vbetool or UseDummyXServer, with DRI enabled
|-
|{{T43}}||SUSE 10.1||2.6.16||8.25.18||Suspend to RAM||yes||without vbetool or UseDummyXServer, with DRI enabled
|-
|{{T60}}||Gentoo 2006.1||2.6.19-suspend2||8.31.5||Suspend2||yes||Everything works: 3D, suspend-to-disk, suspend-to-ram, suspend in X.org, switching to VT's at any moment. Never needed to unload any modules manually, worked immediately. Fglrx driver 8.32.5 totally broke suspend for me, so i'm sticking with 8.31.5. T60 2008-B62 model.
|-
|{{T60p}}||Kubuntu 6.06||2.6.15||8.25.18||swsusp||no||Switching to VT to suspend: no resume, X restarts; Not switching: suspend works, garbled X display on resume, later X restarts
|-
|{{T60p}}||Kubuntu 6.06 Text Mode||2.6.15||---||swsusp||yes||suspend works in textmode after rmmod fglrx.
|-
|{{T60p}}||Debian/unstable/experimental||2.6.18||8.31.5-1 (from debian experimental)||susptoram hibernate debian packages||yes||suspend and resume works with X, 3D acc., Xv overlay...
|-
|{{T60p}}||Fedora Core 6 x86_64||2.6.20-1.2962_1.fc6.cubbi_suspend2|| 8.38.6||suspend2 hibernate||yes||suspend2 hibernate and resume working with libata driver (ahci not tested). Xv still broken since 8.35.5. Have not needed to set extra_pages_allowance thus far.
|-
|{{Z61m}}||Debian Sid||2.6.20.7||8.35.5-1||Suspend to RAM||yes||works without any problems, justs needs the usual acpi_sleep hacks
|-
|{{Z61m}}||Debian Sid||2.6.20.7||8.35.5-1||Suspend to Disk (Software Suspend)||yes||works without any problems
|-
|{{Z61m}}||Debian Sid||2.6.21||8.35.5-1||Suspend to RAM||yes||fglrx module must not be loaded into the kernel, or it won't resume
|-
|{{Z61m}}||openSUSE 10.2||2.6.21.5||8.37.6||suspend2 2.2.10||yes||/sys/power/suspend2/extra_pages_allowance must be set to 20000
|-
|{{Z61p}}||ARCH Linux||2.6.20||8.35.5-1||Suspend to RAM||yes||works with KDE suspend
|-
|{{T60p}}||Gentoo||2.6.22-r8 gentoo-sources||8.39.4||Suspend to RAM,swsusp||yes||swsusp works without hibernate-script installed (installing breaks it), s-to-RAM works only with CONFIG_FB ''disabled'' in kernel. No acpi_sleep=... parameter, no special script, no vbetool.
|}

=== Troubles with large RAM ===
Version 8.14.13 (and probably earlier versions) of the driver does not seem to be able to cope with large amounts of RAM: with 512 MB it works, with 1.5 GB it crashes the machine as soon as X is started. The problem is present only if the <tt>fglrx</tt> kernel module is loaded, but independently of whether {{kernelconf|CONFIG_HIGHMEM||||||}} is enabled. A workaround is to limit RAM by adding the {{bootparm|mem|864m}} kernel parameter.

Version 8.16.20 fixes the problem.

===Display switching ===
The switching between internal and external display doesn't work with fglrx versions <= 8.24.8, because the driver blocks messing around with the chipset via ACPI. If you want to use this feature (i.e. during presentations), you should use the <tt>vesa</tt> server instead (experienced with a R52, Kernel 2.6.11, xorg 6.8.2, fglrx 8.16.20). Or boot notebook with CRT connected, it will automatically detect it and display on both.

===Composite Support===
ATI, as of fglrx 8.42.3 added composite windowing (alpha channel), enabling hardware accelerated translucent windows (primarily for 'eye candy.') This has not been tested yet, and reports will be added here as users evaluate this versus the R300 open source drivers.

For reference, some discussion of current status of drivers can be found in the Rage3d forums' (http://rage3d.com/board) Linux area.

Composite support is also supported with recent Mesa and Xorg > 7 with the open source 3d radeon / R300 drivers found in the linux kernel or debian's driver repository. It works with the [[R300]] / FireGL T2 series as found on the T43p extremely well. This has made rapid progress in speed with the latest few releases, and as of kernel 2.6.23 runs perfectly well with an R300 based card.

===Hardlock on X logout===
Up from driver version 8.19.10 you will experience a system hard lock when logging out from X, if the session manager (kdm/gdm) is not properly configured. You have to tell the session manager to restart X.

In the kdm config file (gentoo: {{path|/usr/kde/<VERSION>/share/config/kdm/kdmrc}}) you have to add following to the section <code>[X-:*-Core]</code>:
TerminateServer=true

In the gdm config (/etc/gdm/gdm.conf) file add the following to the daemon-section:
AlwaysRestartServer=true

Information from the ATI bugtracker: http://ati.cchtml.com/show_bug.cgi?id=239

Another reason of hardlock my be using the wrong AGP driver. Make sure that you have proper drivers for your motherboard loaded before fglrx: (gentoo: {{path|/etc/modules.autoload.d/kernel-2.6}}):
intel-agp
fglrx

A common problem seems to be mistakenly using ATI Chipset drivers instead of Intel.

Information from gentoo bugtracker: <s>[http://bugs.gentoo.org/show_bug.cgi?id=113685 113685]</s>. Fixed in 8.25.18

===Cannot switch to VT===

With usplash boot enabled, it may not be possible to switch to a VT from X (Using Alt+Fn). Tested on T60p (Mobility Fire GLV5200) on Ubuntu 6.06 / 6.10 and fglrx 8.25.18 / 8.28.8. Display may become garbled and system might freeze. Solution (testet on Ubuntu 6.10) is to either remove the "splash" kernel boot parameter or add "vga=791" parameter ("vga=794" can be used on 1400x1050 panel).

http://ati.cchtml.com/show_bug.cgi?id=37 <br>
https://launchpad.net/distros/ubuntu/+source/usplash/+bug/63558

===Flickering Display===

Some people have reported problems with their display flickering when using ati-drivers newer than 8.14.13. The problem is unclear
(possibly associated with an incorrect modeline setting) and no known solution exists except to use the open source radeon drivers.
You can follow this problem here: http://ati.cchtml.com/show_bug.cgi?id=248

===Error messages in system log===

If you find something like the following in {{path|/var/log/messages}}:

:{{cmdresult|kernel: mtrr: base(0xc0000000) is not aligned on a size(0x7ff0000) boundary}}
:{{cmdresult|kernel: [fglrx:firegl_addmap] *ERROR* mtrr allocation failed (-22)}}
:{{cmdresult|kernel: [fglrx:firegl_unlock] *ERROR* Process 5132 using kernel context 0}}

try to execute the following line and reload the fglrx module:

:{{cmdroot|1=echo "base=0xd0000000 size=0x8000000 type=write-combining" > /proc/mtrr}}

More detailed instructions can be found [http://ubuntuforums.org/showthread.php?t=115104 here].

===Hang when logging out===

A common problem is that when logging out from X, instead of gettign the KDM or GDM prompt, the system hangs.

This is discussed, including workarounds here: http://ati.cchtml.com/show_bug.cgi?id=239

===No power saving when CRT in use===

When both CRT and LCD are in use, power saving cannot be enabled.

This is reported here: http://ati.cchtml.com/show_bug.cgi?id=304

===WineX / Cedega Installs Software But Errors on Loading Games===

Some users may experience problems with certain FIREGL cards (in my case an ibm t43p laptop with a v3200 ati firegl) whereby projects such as cedega and wine refuse to work with 3d graphics, but native binaries (e.g. quake 4) work fine. A possible workaround is to add the following line in the drivers section of your /etc/X11/xorg.conf

Option "UseFastTLS" "2"

This option used to be configured with the older ati drivers when you ran "fglrxconfig". I have not yet found a way to get it to appear with "aticonfig", hence the manual insertion. This option is good for several linux distros I have tried, fedora core 5, ubuntu dapper and suse 10.1. It does not appear to effect performance on natively run programs.

{{NOTE|This may cause problems on machines with a Linux kernel version of 2.6.20 or higher (observed choppy video and video color inversion on T60p with both 2.6.20 and 2.6.21).}}

===Line Appears Below Mouse Cursor===

Some users have reported seeing a line approximately 1 mouse height below the bottom edge of the cursor, which follows the mouse and appears to change color based on the image below the cursor. This has been seen to happen using fglrx without the kernel module installed (in 2D mode) and additionally on external displays or multiple X servers. To work around the problem, try disabling the DGA extension by making the following changes to your XFree86.conf or xorg.conf file. Replace (or comment-out)
Load "extmod"
with
SubSection "extmod"
Option "omit xfree86-dga"
EndSubSection

===Freeze while using OpenGL Apps===

Some OpenGL applications such as screensavers or games (SecondLife) cause freezes. The cursor still moves, but otherwise the machine is unresponsive. This is the case with Xorg 7.1 and fglrx 8.29.6 using an x1400 and other cards. The solution is to add the following options to the video Device section in xorg.conf:
Option "Capabilities" "0x00000800"
Option "KernelModuleParm" "locked-userpages=0"

===Xv doesn't work correctly with drivers >= 8.36 and Xyyyy-cards===

See [http://ati.cchtml.com/show_bug.cgi?id=677] for further information. It seems as if only Xyyyy-cards are affected. Problem: graphical glitches with mplayer, programs like xine and totem might not start up at all. 8.35 doesn't seem to be affected

===Floating Point Exception with various X apps===

When the X server is left to autodetect the DPI, the fglrx driver may fail to supply the monitor dimensions. Video output switching may contribute to this bug.

Problems were experienced on T42p with Ubuntu 7.04, xorg-driver-fglrx 7.1.0-8.34.8+2.6.20.5-16.29.

This can be observed with xdpyinfo

:{{cmduser|xdpyinfo | grep dimensions}}
:{{cmdresult|dimensions: 1280x1024 pixels (0x0 millimeters)}}

Many applications will use the screen size and attempt to calculate DPI, resulting in a divide by zero operation and a SIGFPE.

A work around is to supply the dimensions in /etc/X11/xorg.conf. Use the DisplaySize parameter within your monitor's configuration. For example:

Section "Monitor"
Identifier "Generic Monitor"
HorizSync 28.0 - 64.0
VertRefresh 43.0 - 60.0
Option "DPMS"
DisplaySize 433 351
EndSection

=== Corrupted 3D display ===
With driver version 7-12 or later, you may experience a corrupted 3D display, if your horizontal screen resolution is not a multiple of 64. This is a known bug[http://support.ati.com/ics/support/default.asp?deptID=894&task=knowledge&questionID=31720] but ATI support does not have a solution to it yet.

There are two possible workarounds for this bug:

1/ Open the Catalyst Control Center and force the anti-aliasing to at least 2x for all applications. This surprisingly fixes the problem, at the expense of framerate.

2/ As suggested by ATI support, edit the /etc/X11/xorg.conf and find the section "Display". Add the following line into the "Display" section:
Virtual <width> <height>
where <width> is the width of your screen in pixels rounded up to the next multiple of 64 and <height> is the height of your screen in pixels.
For example, if your native resolution is 1400x1050, use
Virtual 1408 1050

After starting the X server you can run {{cmdresult|xrandr -s 0}} to restore the X server to a native display resolution, and 3D rendering will still work.

== Patches ==
The following patches might be needed for certain versions of fglrx. Before you apply any of these, make sure that you really need them, as some distributions include all the necessary patches with the appropriate package (e.g. ati-drivers in gentoo).

===fglrx 8.37.6===
* For kernel 2.6.22 you need this patch from a [http://www.phoronix.com/forums/showthread.php?t=2849 Phoronix thread].

===fglrx 8.35.5===
* [http://whoopie.gmxhome.de/linux/patches/2.6.20/fglrx-8.35.5-for-2.6.20.patch For kernel 2.6.20], part of the Fedora packaging scripts in the ATI installer

===fglrx 8.34.8===
* [http://whoopie.gmxhome.de/linux/patches/2.6.20/fglrx-8.34.8-for-2.6.20.patch For kernel 2.6.20]

===fglrx 8.32.5===
* [http://whoopie.gmxhome.de/linux/patches/2.6.19/fglrx-8.32.5-for-2.6.19.patch For kernel 2.6.19]

===fglrx 8.23.7===
* For kernel 2.6.16: [http://mirror.espri.arizona.edu/gentoo/rsync/x11-drivers/ati-drivers/files/ati-drivers-8.22.5-intermodule.patch <tt>intermodule</tt> patch] and [http://mirror.espri.arizona.edu/gentoo/rsync/x11-drivers/ati-drivers/files/ati-drivers-8.23.7-noiommu.patch <tt>noiommu</tt> patch]

===fglrx 8.21.7===

* [http://www.ksp.sk/~rasto/fglrx_with_2.6.15.patch for kernels >= 2.6.15]

===fglrx 8.20.8===

* [http://marc.theaimsgroup.com/?l=linux-kernel&m=113429835515001&w=2 for kernel 2.6.15]
or
* [http://www.ksp.sk/~rasto/fglrx_with_2.6.15.patch for kernels >= 2.6.15]

===fglrx (problem met at least with version 8.18.8)===
* [http://lkml.org/lkml/2005/9/22/183 for kernel >= 2.6.13 ] Missing verify_area bug

===fglrx 8.8.25 ===
* [http://www.rage3d.com/board/showthread.php?t=33798874 for kernels >= 2.6.10]
* [http://www.gehirn.org.uk/wiki/images/8.8.25-kernel-2.6.11+.patch For kernels >= 2.6.11-rc1]

===Links ===
* [http://gentoo-wiki.com/HOWTO_ATI_Drivers Gentoo HOWTO ATI]

Talk:ThinkPad Advanced Mini-Dock

2008-04-30T10:42:57Z

Dave abrahams: /* Mini-dock power problem */

We do have 8 Advanced Mini Dock in our company, but none of my collegues can manage to dock in properly. To do so you have to press very hard in the middle of the edge on your notebook, I cannot imagine that the display will survive this for a longer time.
You control to have connected properly by lifting your notebook - if connected properly, it will not disconnect.
In all cases, ours do disconnect, even when locked with the key.
Our unsatisfying solution: We place a mouse-pad under each Mini-Dock - now connecting is no problem any more.

Lenovo is unable to reproduce this problem with their own hardware - the support asked me to send one notebook and one Mini-Dock to them to schottland so that they can investigate in that case. That means one collegue will have to survive without his comuter for I don't know how many weeks. Lenovo cannot send somebody to confirm the problem inside our house. This kind of Support is very poor!
And, of course, I am wondering: I am the one who bought exactly this 8 notebooks together with this 8 Mini-Docks, which don't want to fit together.

Are all the others connecting without problems ?

Please tell me your experiences.

I have the same problem. I put some rubber feet on the bottom of the dock, but it's still pretty hard to dock the computer reliably and it requires lots of force. I'll try the mousepad trick, for what that's worth. --[[User:Dave abrahams|Dave abrahams]] 17:20, 25 April 2007 (CEST)

It seems to be a problem with T60 models manufactured in August 2006 (?) (S/N L3-FL??? 06/08), I do have some other T60 now without this problem. Meanwhile IBM/Lenovo has confirmed the problem (to me), but this was a long way. I sent my T60 and Minidock to them in 5 Feb. 07, today we have 22 May and it is still not back. At least IBM/Lenovo has given me another T60 for this time.
If I had this choice again, I wouldn't complain to IBM/Lenovo, I'd just try to buy some "rubber-feet" for my Minidock. --[[User:Holzbein]] 16:40, 22 May 2007 (CEST)

== Mini-dock power problem ==

'''Note:''' see http://www-307.ibm.com/pc/support/site.wss/MIGR-67382.html for the solution to this problem

I have a T60p, and if I place the machine onto the Advanced Mini Dock when it is asleep, it turns off. The only way I can prevent this from happening is to wake the machine up before I put it on the dock. Does anyone else have this problem? --[[User:Sridhar|Sridhar]] 14:38, 2 January 2007 (CET)

I have the problem about half the time even when the machine is already awake. --[[User:Dave abrahams|Dave abrahams]] 17:17, 25 April 2007 (CEST)

We also have another problem with Keyboards connected to the Minidock's PS/2-Port. Sometimes it is behaving like the SHIFT key is held permanently, and to escape from this situation you have to press SHIFT many times (or reboot). This happens with different PS/2 Keyboards of different manufacturers, but it happens not every day, maybe once a week. So how should I complain about this ? How can I demonstrate the problem ? I don't expect it to be solved, only to cost my nerves. So I better buy some new USB-Keyboards and stop using the Minidock's PS/2-Port. --[[User:Holzbein]] 16:45, 22 May 2007 (CEST)

I have this problem as well. It wreaks havoc when I'm in vi. I'm thinking this model dock might just be a lemon. [[User:Sridhar|Sridhar]] 13:57, 24 October 2007 (UTC)

== IBM Thinkpad Z60t with Advanced mini Dock - Dual Video Out ==

I wanted to know if anyone has any solution for getting dual video out using the Z60t with the Advanced Mini Dock. Since the Z60t doesn't have an ATI built in video card like the Z60m, IBM/Lenovo say it doesn't support using the DVI out when docked. Unfortunately I found this out after purchasing it (2 years ago).

I just started using my laptop as my primary machine. And now I really would like to get the dual video setup as I have a very nice 2nd LCD sitting here powered off :(

There was a very similar conversation under the Thinkpad Advanced Dock, but I didn't understand the answer.

Anyway, please help me out, would really like to get this working. Thanks Much!

ThinkPad Advanced Mini-Dock

2008-04-30T10:22:22Z

Dave abrahams:

{| cellspacing="0" cellpadding="2" border="0"
| style="vertical-align:top;" | __TOC__
[[image:thinkpad-advanced-mini-dock.gif|ThinkPad Advanced Mini Dock]]
| 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;">
== ThinkPad Advanced Mini Dock ==
The ThinkPad Advanced Mini Dock (Model # 250410U) contains basic pass-through connections for notebook ports, including power pass-through. It comes without integrated power supply but provides the same power jack as found in a ThinkPad, an AC-Adapter is included. Besides all the pass-through ports the ThinkPad Advanced Mini Dock comes with an On/Off switch, Key lock and a slot for a cable lock.

=== Fix for Poweroff on Docking ===
http://www-307.ibm.com/pc/support/site.wss/MIGR-67382.html

=== Features ===
* Passthrough ports:
** Ethernet (RJ45)
** Modem (RJ11)
** [[VGA Port|VGA]]
** DVI-D (Dual Link DVI-D supported for certain nVidia / ATI video cards for high resolution monitors)
*** A 30" display at 2560x1600 is [http://forums.lenovo.com/lnv/board/message?board.id=T_Series_Thinkpads&message.id=786 confirmed] to work with a {{T61p}}
** [[Serial Port|Serial (DB9-M)]]
** [[Parallel Port|Parallel (DB25-F)]]
** [[PS/2 Port|Combined PS/2 Mouse + Keyboard]]
** Audio Microphone-in
** Audio Headphone-out
* USB (4-ports)
* Kensington Lock connector
* Key lock
* Power button
* AC-Adapter (same as with the TP)
</div>
|}

==IBM part numbers==
* order part number: P/N 250410U
* FRU part number: 26R9063

== Supported ThinkPads ==
* ThinkPad {{R61}}
* ThinkPad {{T60}}, {{T60p}}, {{T61}}, {{T61p}}
* ThinkPad {{Z60m}}, {{Z60t}}

== Links ==
Manufacturers page: [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-61297 http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-61297]

ThinkPad Essential Port Replicator

2008-04-30T10:21:15Z

Dave abrahams: /* ThinkPad Essential Port Replicator */

{| cellspacing="0" cellpadding="2" border="0"
| style="vertical-align:top;" | __TOC__
[[image:thinkpad-essential-port-replicator.gif|ThinkPad Essential Port Replicator]]
| 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;">
== ThinkPad Essential Port Replicator ==
The ThinkPad Essential Port Replicator (Model # 250510W) contains basic pass-through connections for notebook ports, including power pass-through. It comes without integrated power supply but provides the same power jack as found in a ThinkPad, so you need to use either your Thinkpad AC adapter or another IBM AC adapter. Besides all the pass-through ports the ThinkPad Essential Port Replicator comes with an On/Off switch and a slot for a cable lock (only for the dock though).

=== Fix for Poweroff on Docking ===
http://www-307.ibm.com/pc/support/site.wss/MIGR-67382.html

=== Features ===
* Passthrough ports:
** Ethernet (RJ45)
** Modem (RJ11)
** [[VGA Port|VGA]]
** [[PS/2 Port|Combined PS/2 Mouse + Keyboard]]
* USB (4-ports)
* Kensington Lock connector
* Power button
</div>
|}

==IBM part numbers==
* Order part number: 250510W
* FRU part number: 26R9065

== Supported ThinkPads ==
* ThinkPad {{R61}}
* ThinkPad {{T60}}, {{T60p}}, {{T61}}
* ThinkPad {{Z60m}}, {{Z60t}}

ThinkPad Advanced Dock

2008-04-30T10:20:00Z

Dave abrahams: /* Fix for Poweroff on Docking */

{| cellspacing="0" cellpadding="2" border="0"
| style="vertical-align:top;" | __TOC__
[[image:thinkpad-advanced-dock.gif|ThinkPad Advanced Dock]]
| 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;">
== ThinkPad Advanced Dock ==
The ThinkPad Advanced Dock (Model # 250310U) contains basic pass-through connections for notebook ports, including power pass-through. It comes with an integrated power supply. Besides all the pass-through ports the ThinkPad Advanced Dock comes with an UltraBay, PCI Express slot, 6-in-1 media card reader, On/Off switch, key lock and a slot for a cable lock.

=== Fix for Poweroff on Docking ===
http://www-307.ibm.com/pc/support/site.wss/MIGR-67382.html

=== Features ===
* Passthrough ports:
** Ethernet (RJ45)
** Modem (RJ11)
** [[VGA Port|VGA]]
** DVI-D
** [[Serial Port|Serial (DB9-M)]]
** [[Parallel Port|Parallel (DB25-F)]]
** [[PS/2 Port|Combined PS/2 Mouse + Keyboard]]
** Audio Microphone-in
** Audio Headphone-out
** Digital Audio (S/PDIF)
* USB (5-ports)
* [[UltraBay|Ultrabay Enhanced]]
* PCI-Express slot
{{NOTE|
Only 1x speed, but 16x graphics cards will work. Speeds of the interface will be between PCI and AGP bus speeds
standard length - i.e. about an inch longer than the connector. Only thin cards will fit. Many performance video cards with heat sink/fans are too thick.

Validated Cards:
* <Insert Cards here>
}}

* 6-in-1 media card reader
** [[xD Card slot|xD-Picture]]
** [[SD Card slot|SD]]
** [[CF Card slot|Compact Flash]]
** [[SD Card slot|MultiMedia Card]]
** [[SmartMedia Card slot|SmartMedia]]
** [[MS Card slot|Sony Memory Stick]]
* Kensington Lock connector
* Key lock
* Power button
* Integrated power supply
</div>
|}
* [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-61393 ThinkPad Advanced Dock - Publications]

==IBM part numbers==
* order part number: P/N 250410U
* FRU part number: 26R9061

== Supported ThinkPads ==
* ThinkPad {{R61}}
* ThinkPad {{T60}}, {{T60p}}, {{T61}}, {{T61p}}
* ThinkPad {{Z60m}}, {{Z60t}}, {{Z61p}}

ThinkPad Advanced Dock

2008-04-30T10:19:42Z

Dave abrahams:

{| cellspacing="0" cellpadding="2" border="0"
| style="vertical-align:top;" | __TOC__
[[image:thinkpad-advanced-dock.gif|ThinkPad Advanced Dock]]
| 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;">
== ThinkPad Advanced Dock ==
The ThinkPad Advanced Dock (Model # 250310U) contains basic pass-through connections for notebook ports, including power pass-through. It comes with an integrated power supply. Besides all the pass-through ports the ThinkPad Advanced Dock comes with an UltraBay, PCI Express slot, 6-in-1 media card reader, On/Off switch, key lock and a slot for a cable lock.

== Fix for Poweroff on Docking ==
http://www-307.ibm.com/pc/support/site.wss/MIGR-67382.html

=== Features ===
* Passthrough ports:
** Ethernet (RJ45)
** Modem (RJ11)
** [[VGA Port|VGA]]
** DVI-D
** [[Serial Port|Serial (DB9-M)]]
** [[Parallel Port|Parallel (DB25-F)]]
** [[PS/2 Port|Combined PS/2 Mouse + Keyboard]]
** Audio Microphone-in
** Audio Headphone-out
** Digital Audio (S/PDIF)
* USB (5-ports)
* [[UltraBay|Ultrabay Enhanced]]
* PCI-Express slot
{{NOTE|
Only 1x speed, but 16x graphics cards will work. Speeds of the interface will be between PCI and AGP bus speeds
standard length - i.e. about an inch longer than the connector. Only thin cards will fit. Many performance video cards with heat sink/fans are too thick.

Validated Cards:
* <Insert Cards here>
}}

* 6-in-1 media card reader
** [[xD Card slot|xD-Picture]]
** [[SD Card slot|SD]]
** [[CF Card slot|Compact Flash]]
** [[SD Card slot|MultiMedia Card]]
** [[SmartMedia Card slot|SmartMedia]]
** [[MS Card slot|Sony Memory Stick]]
* Kensington Lock connector
* Key lock
* Power button
* Integrated power supply
</div>
|}
* [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-61393 ThinkPad Advanced Dock - Publications]

==IBM part numbers==
* order part number: P/N 250410U
* FRU part number: 26R9061

== Supported ThinkPads ==
* ThinkPad {{R61}}
* ThinkPad {{T60}}, {{T60p}}, {{T61}}, {{T61p}}
* ThinkPad {{Z60m}}, {{Z60t}}, {{Z61p}}

ThinkPad Advanced Mini-Dock

2008-04-30T10:17:05Z

Dave abrahams: /* Links */

{| cellspacing="0" cellpadding="2" border="0"
| style="vertical-align:top;" | __TOC__
[[image:thinkpad-advanced-mini-dock.gif|ThinkPad Advanced Mini Dock]]
| 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;">
== ThinkPad Advanced Mini Dock ==
The ThinkPad Advanced Mini Dock (Model # 250410U) contains basic pass-through connections for notebook ports, including power pass-through. It comes without integrated power supply but provides the same power jack as found in a ThinkPad, an AC-Adapter is included. Besides all the pass-through ports the ThinkPad Advanced Mini Dock comes with an On/Off switch, Key lock and a slot for a cable lock.

=== Features ===
* Passthrough ports:
** Ethernet (RJ45)
** Modem (RJ11)
** [[VGA Port|VGA]]
** DVI-D (Dual Link DVI-D supported for certain nVidia / ATI video cards for high resolution monitors)
*** A 30" display at 2560x1600 is [http://forums.lenovo.com/lnv/board/message?board.id=T_Series_Thinkpads&message.id=786 confirmed] to work with a {{T61p}}
** [[Serial Port|Serial (DB9-M)]]
** [[Parallel Port|Parallel (DB25-F)]]
** [[PS/2 Port|Combined PS/2 Mouse + Keyboard]]
** Audio Microphone-in
** Audio Headphone-out
* USB (4-ports)
* Kensington Lock connector
* Key lock
* Power button
* AC-Adapter (same as with the TP)
</div>
|}

==IBM part numbers==
* order part number: P/N 250410U
* FRU part number: 26R9063

== Supported ThinkPads ==
* ThinkPad {{R61}}
* ThinkPad {{T60}}, {{T60p}}, {{T61}}, {{T61p}}
* ThinkPad {{Z60m}}, {{Z60t}}

== Links ==
Manufacturers page: [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-61297 http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-61297]

== Fix for poweroff-on-docking design defect ==
http://www-307.ibm.com/pc/support/site.wss/MIGR-67382.html

ThinkPad Advanced Mini-Dock

2008-04-30T10:16:09Z

Dave abrahams:

{| cellspacing="0" cellpadding="2" border="0"
| style="vertical-align:top;" | __TOC__
[[image:thinkpad-advanced-mini-dock.gif|ThinkPad Advanced Mini Dock]]
| 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;">
== ThinkPad Advanced Mini Dock ==
The ThinkPad Advanced Mini Dock (Model # 250410U) contains basic pass-through connections for notebook ports, including power pass-through. It comes without integrated power supply but provides the same power jack as found in a ThinkPad, an AC-Adapter is included. Besides all the pass-through ports the ThinkPad Advanced Mini Dock comes with an On/Off switch, Key lock and a slot for a cable lock.

=== Features ===
* Passthrough ports:
** Ethernet (RJ45)
** Modem (RJ11)
** [[VGA Port|VGA]]
** DVI-D (Dual Link DVI-D supported for certain nVidia / ATI video cards for high resolution monitors)
*** A 30" display at 2560x1600 is [http://forums.lenovo.com/lnv/board/message?board.id=T_Series_Thinkpads&message.id=786 confirmed] to work with a {{T61p}}
** [[Serial Port|Serial (DB9-M)]]
** [[Parallel Port|Parallel (DB25-F)]]
** [[PS/2 Port|Combined PS/2 Mouse + Keyboard]]
** Audio Microphone-in
** Audio Headphone-out
* USB (4-ports)
* Kensington Lock connector
* Key lock
* Power button
* AC-Adapter (same as with the TP)
</div>
|}

==IBM part numbers==
* order part number: P/N 250410U
* FRU part number: 26R9063

== Supported ThinkPads ==
* ThinkPad {{R61}}
* ThinkPad {{T60}}, {{T60p}}, {{T61}}, {{T61p}}
* ThinkPad {{Z60m}}, {{Z60t}}

== Links ==
Manufacturers page: [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-61297 http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-61297]

'''Fix for poweroff-on-docking design defect:''' http://www-307.ibm.com/pc/support/site.wss/MIGR-67382.html

Problems with fglrx

2008-04-29T20:49:24Z

Dave abrahams: /* Troubles using software suspend */

This page discusses issues with the ATI proprietary [[fglrx]] display driver.

== Known Troubles and Solutions ==

=== X-specific issues ===

==== upgrading xserver-xorg ====
ATI proprietary drivers version 8.21.7 and later work with x.org 6.9.

If you are running an older version (8.20.8) under Debian sid and you upgrade your xserver-xorg, apt will force you to remove any debian-packaged fglrx drivers (package fglrx-driver depends on x.org << 6.8.99). You can just download the driver from the ATI site and install after modifying the Debian packager script to allow dependencies to be satisfied by x.org 6.9, or just download 8.21.7 and install manually. See talk page for step-by-step commands.

After installing the fglrx driver, you can use module-assist to build the appropriate kernel module.

==== new Xorg ID Scheme ====
ATI proprietary drivers <=8.36.5 with xorg >=7.1.0-18 (==1.3.0.0) in Debian Sid and Fedora ([http://www.sidux.com/PNphpBB2-viewtopic-t-3162-postdays-0-postorder-asc.html Debian] and [http://www.phoronix.net/forums/showthread.php?t=2382 Fedora] Forum Entries)

Ubuntu feisty made their own xorg with the standard id of 7.2, to work around this issue.

Xorg has changed its ID Scheme in newer Versions, and fglrx cannot cope with that (Error message saying "[...] X version mismatch - detected X.org 1.3.-1.905, required X.org 7.1.0.0 [...]").

A binary hack solves the Problem [http://rage3d.com/board/showthread.php?s=4638d94143536f6acacbccd8f0443472&t=33889029 (rage3d.com Forum Entry)]. This is a very '''dirty''' solution, and is probably violating the ATI driver license.

Simply using the open source ati driver (or holding back the xorg upgrades) until a new driver is released, is suggested.

As of version 8.37.6, this issue is solved. No more binary hacking needed.

=== Kernel-specific troubles ===

Using ATI drivers <=8.21.7 with kernel >=2.6.15 needs a [http://marc.theaimsgroup.com/?l=linux-kernel&m=113429835515001&w=2 patch]. (see table below for detail.) If you can't compile the driver modules with 2.6.15 or later, you should apply this [http://www.ksp.sk/~rasto/fglrx_with_2.6.15.patch patch] instead.

If you do not use one of these patches, you may experience peculiar lockups of X. Try {{cmduser|fglrxinfo}} - if your shell hangs at the end of this command, you may have an issue and should try the patch or upgrade.

Although unproven, there is a substantial amount of user / developer concern that the above patches prevent hard lockups but do not provide full reliability with 2.6.15 and there are larger / redisgn issues preventing compatibility. These issues have been fixed with later ATI drivers (> 8.21.7) so you can simply upgrade if you are running a more modern kernel.

==== 2.6.23 ====
In 2.6.23 release cycle, config option CONFIG_SUSPEND_SMP got renamed to CONFIG_PM_SLEEP_SMP. fglrx uses this variable for disabling power management on older kernels. As a result, SMP users running 2.6.23 weren't able to resume properly (almost instant lockup in that rare case fglrx managed to show a few usable pixels. A [http://linux.derkeiler.com/Mailing-Lists/Kernel/2007-10/msg03437.html quick patch] is available.

=== No hardware acceleration ===

====Acceleration lost after driver update====
If you lose hardware acceleration after a driver update this can be caused by an old fglrx kernel module being loaded.

Check out {{path|1=/var/log/Xorg.0.log}} for a message like:
:<code>(WW) fglrx(0): Kernel Module version does *not* match driver.</code>
:<code>(EE) fglrx(0): incompatible kernel module detected - HW accelerated OpenGL will not work</code>

You can verify this yourself by looking at the version message some lines above. It should read something not matching the installed version like:
:<code>(II) fglrx(0): Kernel Module Version Information:</code>
:<code>(II) fglrx(0): Name: fglrx</code>
:<code>(II) fglrx(0): Version: 8.10.19</code>

The cause for this trouble might be that there resist multiple versions of the fglrx module within the kernel module search path.<br>
Go to {{path|1=/lib/modules/<your linux kernel version>/}} and type {{cmdroot|1=grep fglrx modules.dep}}.<br>
If grep finds multiple lines you nailed down the problem. All you have to do now is to delete any versions of the module (look at the filedate) but the most current one. Then run {{cmdroot|1=depmod}} and you are done.

{{HINT|Newer versions (8.21.7) of the fglrx module seem to be installed in the <code>extra/</code> subdirectory.<br>
Older versions (8.19.10) used to be located in the <code>kernel/drivers/char/drm/</code> subdirectory.}}

====GCC 3.4====
If the ATI driver works only without the hardware acceleration, take into consideration that {{path|fglrx_dri.so}} was linked against libstdc++.so.5 which may not be present if your system uses gcc-3.4.

To fix this, compile gcc-3.3.5 and copy <tt>libstdc++.so.5*</tt> to {{path|/usr/lib}} and update the dynamic linker cache via {{cmdroot|ldconfig}}.

Or install a compat package for your favorite distro. FC4 users can do:
:{{cmdroot|yum install libstdc++.so.5}}

====radeonfb framebuffer====
Another possible cause for broken hardware acceleration (2D and 3D) is the radeonfb framebuffer: Switching to vesafb or vesafb-tng is reported to solve the problem on some systems. Also it has proven helpful to not perform {{cmdroot|modprobe fglrx}} after boot but to have the module loaded via {{path|/etc/modules.autoload/kernel2.x}} at boottime instead.

====Perpetual Mesa GLX Indirect on Debian====
If you've done everything right and you're still seeing:

:{{cmduser|fglrxinfo}}
:{{cmdresult|display: :0.0 screen: 0}}
:{{cmdresult|OpenGL vendor string: Mesa project: www.mesa3d.org}}
:{{cmdresult|OpenGL renderer string: Mesa GLX Indirect}}
:{{cmdresult|OpenGL version string: 1.2 (1.5 Mesa 6.4.1)}}

try this:

:{{cmdroot|mkdir -p /usr/X11R6/lib/modules/dri}}
:{{cmdroot|ln -s /usr/lib/dri/fglrx_dri.so /usr/X11R6/lib/modules/dri}}

Thanks to Maciej Matysiak for the clear debug [http://lists.debian.org/debian-amd64/2006/02/msg00217.html here] and solution [http://lists.debian.org/debian-amd64/2006/02/msg00311.html here].

More generally, use LIBGL_DEBUG=verbose fglrxinfo, to see what's happening, and whether you get this:
:{{cmduser|<nowiki>LIBGL_DEBUG=verbose</nowiki> fglrxinfo}}
:{{cmdresult|libGL: XF86DRIGetClientDriverName: 8.26.18 fglrx (screen 0)}}
:{{cmdresult|libGL: OpenDriver: trying /usr/X11R6/lib/modules/dri/fglrx_dri.so}}
:{{cmdresult|libGL error: dlopen /usr/X11R6/lib/modules/dri/fglrx_dri.so failed (/usr/X11R6/lib/modules/dri/fglrx_dri.so: cannot open shared object file: No such file or directory)}}
:{{cmdresult|libGL error: unable to find driver: fglrx_dri.so}}
:{{cmdresult|display: :0.0 screen: 0}}
:{{cmdresult|OpenGL vendor string: Mesa project: www.mesa3d.org}}
:{{cmdresult|OpenGL renderer string: Mesa GLX Indirect}}
:{{cmdresult|OpenGL version string: 1.2 (1.5 Mesa 6.4.2)}}

instead of that:
:{{cmduser|<nowiki>LIBGL_DEBUG=verbose</nowiki> fglrxinfo}}
:{{cmdresult|libGL: XF86DRIGetClientDriverName: 8.26.18 fglrx (screen 0)}}
:{{cmdresult|libGL: OpenDriver: trying /usr/X11R6/lib/modules/dri/fglrx_dri.so}}
:{{cmdresult|libGL: XF86DRIGetClientDriverName: 8.26.18 fglrx (screen 0)}}
:{{cmdresult|drmOpenByBusid: busid is PCI:1:0:0}}
:{{cmdresult|drmOpenDevice: minor is 0}}
:{{cmdresult|drmOpenDevice: node name is /dev/dri/card0}}
:{{cmdresult|drmOpenDevice: open result is 4, (OK)}}
:{{cmdresult|drmOpenByBusid: drmOpenMinor returns 4}}
:{{cmdresult|drmOpenByBusid: drmGetBusid reports PCI:1:0:0}}
:{{cmdresult|Can't open configuration file /home/merlin/.drirc: No such file or directory.}}
:{{cmdresult|fglrx: DPD supported.}}
:{{cmdresult|display: :0.0 screen: 0}}
:{{cmdresult|OpenGL vendor string: ATI Technologies Inc.}}
:{{cmdresult|OpenGL renderer string: MOBILITY FIREGL T2 Pentium 4 (SSE2) (FireGL) (GNU_ICD)}}
:{{cmdresult|OpenGL version string: 2.0.5879 (8.26.18)}}

I have contacted ATI to add that info by default, the mesa guys to do that in glxinfo too, as well as the debian packager to fix the debian packaging bug (2006/07/22), so hopefully the situation will improve soon

You may have to run fglrxinfo as root to get this detail rather than a useless message.

==== Where to look for fglrx_dri.so (gentoo and general)====
After installing a new kernel (linux-2.6.20-gentoo-r7) with gentoo I again was not able to get the ATI driver working
correctly. But now I found out what the problem was:

I tried
:{{cmduser|<nowiki>LIBGL_DEBUG=verbose</nowiki> fglrxinfo}}
:{{cmdresult|libGL: XF86DRIGetClientDriverName: 8.35.5 fglrx (screen 0)}}
:{{cmdresult|libGL: OpenDriver: trying /usr/lib32/dri/fglrx_dri.so}}
:{{cmdresult|libGL error: dlopen /usr/lib32/dri/fglrx_dri.so failed (/usr/lib32/dri/fglrx_dri.so: wrong ELF class: ELFCLASS32)}}
:{{cmdresult|libGL error: unable to find driver: fglrx_dri.so}}

The error itself makes sense, because I am running a 64-Bit linux on AMD. The question was, why libGL tries to look
in /usr/lib32 only...

After some digging around I found out, that apparently 8.35.5 version of the driver uses the environment variable
'''LIBGL_DRIVERS_PATH''' to find out where it should look for the "fglrx_dri.so" driver.

Now in my case this environment variable pointed to "/usr/lib32/dri" and that was what caused the problem.
So doing
:{{cmduser|<nowiki>export LIBGL_DRIVERS_PATH='/usr/lib64/dri:/usr/lib32/dri'</nowiki>}}
solved the problem in my case.

As mentioned I use gentoo. After some more digging around I found out, that it is apparently necessary to call
:{{cmduser|env-update}}
after a re-install of the ATI driver. To be more specific, it seems that "eselect opengl set ati" sometimes
does something wrong. "env-update" seems to repair the problem so that afterwards the '''LIBGL_DRIVERS_PATH'''
environment variable is set correctly when you log in.

If you want to check, look in <code>/etc/profile.env</code> and <code>/etc/profile.csh</code>. This is the
place where the '''LIBGL_DRIVERS_PATH''' environment variable gets set.

=== Softlink hell ===
The [[fglrx]] installer replaces the standard X.org OpenGL implementation (Mesa) with its own files, potentially causing collisions with the distribution's file and package management. It is best to install the driver via a package built for your distribution, which will typically include the necessary kludges to make things work. See the [[fglrx]] page for pointers.

====Discussion====
If using {{cmduser|fglrxinfo}} after installing [[fglrx]] indicates that you are still using the mesa indirect software GL renderer, you likely have some misplaced softlinks. It seems like it has to do with an apt-get upgrade that sometimes replaces these links. Anyway, go to
:{{cmdroot|cd /usr/X11R6/lib}}
and list your GL libraries and links
:{{cmdroot|ls -la *GL*}}
You should see something like the following two lines amoung others:
:{{cmdresult|libGL.so -> libGL.so.1.2}}
:{{cmdresult|libGL.so.1 -> libGL.so.1.2}}
If you see a link to a mesa library (something like {{cmdresult|... -> libGL.mesa.1.2}}), then that's your problem! Restore the softlink like this (use your actual library version, though):
:{{cmdroot|ln -s libGL.so.1.2 libGL.so.1}}

For some reason, this link might "break" later, giving you the software rendering once more. Even after renaming the mesa library to something like <tt>mesa.bkup</tt>, the system might still find it and link to it despite the name change. If you have to do this a lot, you could write a restoreGL script.

=====Gentoo=====
{{Gentoo}} has built in tools for managing the OpenGL symlinks.
:{{cmdroot|eselect opengl set ati}}
If <tt>eselect opengl ati</tt> doesn't fix it for you, you should probably tell [http://bugs.gentoo.org Gentoo Bugzilla] (assuming they don't know yet).

If {{cmdroot|ldd /usr/X11R6/bin/glxinfo}} shows that your system still uses the xorg-x11 mesa libs after trying one of the above commands, i.e. a line like this:
:{{cmdresult|1=libGL.so.1 => /usr/lib/opengl/xorg-x11/lib/libGL.so.1 (0x400a8000)}}
you will also need to relink {{path|libGl.so.1.2}}:
:{{cmdroot|cd /usr/lib/opengl/xorg-x11/lib/}}
:{{cmdroot|mv libGL.so.1.2 libGL.so.1.2_backup}}
:{{cmdroot|ln -s /usr/lib/libGL.so.1.2 libGL.so.1.2}}
After another restart of X {{cmduser|fglrxinfo}} should show that it's using the right libs now.

=====Debian=====

:{{cmdroot|rm /usr/lib/libGL.so*}}
:{{cmdroot|rm /usr/X11R6/lib/libGL.so*}}
:{{cmdroot|cd /usr/X11R6/lib}}
:{{cmdroot|cp /usr/lib/fglrx/diversions/lib/libGL.so.1.2 .}}
:{{cmdroot|ln -s libGL.so.1.2 libGL.so.1}}
:{{cmdroot|ldconfig}}

=== Troubles using software suspend ===

Resume doesn't work when any AIGLX clients are active. See https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-2.6.24/+bug/197209 for details and a workaround.

Suspend won't work on any distribution which has activated the new SLUB allocator with fglrx < 8.42. This affects e.g. Ubuntu 7.10 Gutsy (see https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/121653/). The only workaround is currently to compile a custom kernel with SLAB support!

When the computer resumes from suspend, X only displays a garbled image and the computer is frozen.
The problem is acknowledged in ATI's release notes and in knowledge base entry <strike>[https://support.ati.com/ics/support/KBResult.asp?searchFor=Search+Words&search.x=0&search.y=0&searchOption=id&questionID=737-218+&task=knowledge&searchTime=-1&productID=&folderID=-1&resultLimit=50 737-218]</strike> [https://support.ati.com/ics/support/KBAnswer.asp?questionID=218 737-218]. Driver version 8.19.10 has "initial support for Suspend and Resume" but is working very nicely for most people (verified on T43, T43p and T42) without vbetool.

If you are using an older version of fglrx, using [http://www.srcf.ucam.org/~mjg59/vbetool/ vbetool] to save/restore the video card state before/after suspend worked for some people. If you use [[Software Suspend 2|Software Suspend 2 (suspend2)]] scripts, you can simply uncomment <tt>EnableVbetool yes</tt> in {{path|/etc/hibernate/hibernate.conf}}. Be aware though that it breaks suspend/resume for drivers beginning with version 8.19.10, so remember to disable it again when upgrading.

{| cellspacing="0" cellpadding="2" border="1"
|+ tested with the following configurations
!model!!distro||kernel!!fglrx!!PM!!success!!comments
|-
|{{T42}}||SUSE 9.3||2.6.11||8.14.13||swsusp||yes||
|-
|{{T41p}}||???||2.6.14||8.19.10||suspend2 2.2-rc9||yes||needs a small [http://mailman.linux-thinkpad.org/pipermail/linux-thinkpad/2005-November/030381.html patch]
|-
|{{T42p}}||Debian||2.6.10||Debian packaged||suspend2||yes||
|-
|{{T43}}||Debian sid||2.6.14.2||8.19.10||swsusp||yes||works perfectly with 8.19.10 (but not earlier versions!)
|-
|{{T43}}||Debian etch||2.6.14.2||8.19.10||swsusp||yes||works perfectly with 8.19.10 and without vbetool
|-
|{{T43}}||Ubuntu Breezy||2.6.12-10||8.19.10||swsusp||yes||Perfect. (Finally.)
|-
|{{T43}}||FC4||2.6.14.1||8.19.10||suspend2 2.2-rc9||yes||needs a small [http://mailman.linux-thinkpad.org/pipermail/linux-thinkpad/2005-November/030381.html patch], requires DRI disabled in {{path|xorg.conf}} (hence no 3D acceleration)
|-
|{{T43}}||FC4||2.6.14.2||8.19.10||suspend2 2.2-rc11||yes||requires DRI disabled in {{path|xorg.conf}} (hence no 3D acceleration)
|-
|{{T43}}||FC4||2.6.14.3||8.19.10||suspend2 2.2-rc13||no||DRI enabled
|-
|{{T43}}||FC4||2.6.14.3||8.20.8||suspend2 2.2-rc13||no||DRI enabled
|-
|{{T43p}}||FC6||2.6.20-1.2933||8.34.8||swsusp, STR||yes||DRI enabled, occasionally fails, reason unknown.
|-
|{{R50p}}||???||???||8.19.10||swsusp||yes||
|-
|{{T43p}}||Debian sid||2.6.14||8.19.10||Suspend to RAM||yes||without vbetool or UseDummyXServer, those two ''break'' the resume process here, with DRI enabled
|-
|{{T43p}}||Debian sid||2.6.14.3||8.20.8||Suspend to RAM||yes||without vbetool or UseDummyXServer, with DRI enabled
|-
|{{R52}}||Debian sid||2.6.15-rc5||8.20.8||swsup||yes||both vbetool and UseDummyXServer disabled, DRI enabled, needs [http://marc.theaimsgroup.com/?l=linux-kernel&m=113429835515001&w=2 patch]
|-
|{{T43p}}||Gentoo||[http://packages.gentoo.org/ebuilds/?suspend2-sources-2.6.15-r6 2.6.15]||8.22.5||Suspend to RAM||yes||without vbetool or UseDummyXServer, with DRI enabled - console is garbled until switching back from X
|-
|{{T43p}}||Gentoo||[http://packages.gentoo.org/ebuilds/?suspend2-sources-2.6.15-r6 2.6.15]||8.22.5||suspend2 2.2||yes||without vbetool or UseDummyXServer, with DRI enabled
|-
|{{T43}}||SUSE 10.1||2.6.16||8.25.18||swsusp||yes||without vbetool or UseDummyXServer, with DRI enabled
|-
|{{T43}}||SUSE 10.1||2.6.16||8.25.18||Suspend to RAM||yes||without vbetool or UseDummyXServer, with DRI enabled
|-
|{{T60}}||Gentoo 2006.1||2.6.19-suspend2||8.31.5||Suspend2||yes||Everything works: 3D, suspend-to-disk, suspend-to-ram, suspend in X.org, switching to VT's at any moment. Never needed to unload any modules manually, worked immediately. Fglrx driver 8.32.5 totally broke suspend for me, so i'm sticking with 8.31.5. T60 2008-B62 model.
|-
|{{T60p}}||Kubuntu 6.06||2.6.15||8.25.18||swsusp||no||Switching to VT to suspend: no resume, X restarts; Not switching: suspend works, garbled X display on resume, later X restarts
|-
|{{T60p}}||Kubuntu 6.06 Text Mode||2.6.15||---||swsusp||yes||suspend works in textmode after rmmod fglrx.
|-
|{{T60p}}||Debian/unstable/experimental||2.6.18||8.31.5-1 (from debian experimental)||susptoram hibernate debian packages||yes||suspend and resume works with X, 3D acc., Xv overlay...
|-
|{{T60p}}||Fedora Core 6 x86_64||2.6.20-1.2962_1.fc6.cubbi_suspend2|| 8.38.6||suspend2 hibernate||yes||suspend2 hibernate and resume working with libata driver (ahci not tested). Xv still broken since 8.35.5. Have not needed to set extra_pages_allowance thus far.
|-
|{{Z61m}}||Debian Sid||2.6.20.7||8.35.5-1||Suspend to RAM||yes||works without any problems, justs needs the usual acpi_sleep hacks
|-
|{{Z61m}}||Debian Sid||2.6.20.7||8.35.5-1||Suspend to Disk (Software Suspend)||yes||works without any problems
|-
|{{Z61m}}||Debian Sid||2.6.21||8.35.5-1||Suspend to RAM||yes||fglrx module must not be loaded into the kernel, or it won't resume
|-
|{{Z61m}}||openSUSE 10.2||2.6.21.5||8.37.6||suspend2 2.2.10||yes||/sys/power/suspend2/extra_pages_allowance must be set to 20000
|-
|{{Z61p}}||ARCH Linux||2.6.20||8.35.5-1||Suspend to RAM||yes||works with KDE suspend
|-
|{{T60p}}||Gentoo||2.6.22-r8 gentoo-sources||8.39.4||Suspend to RAM,swsusp||yes||swsusp works without hibernate-script installed (installing breaks it), s-to-RAM works only with CONFIG_FB ''disabled'' in kernel. No acpi_sleep=... parameter, no special script, no vbetool.
|}

=== Troubles with large RAM ===
Version 8.14.13 (and probably earlier versions) of the driver does not seem to be able to cope with large amounts of RAM: with 512 MB it works, with 1.5 GB it crashes the machine as soon as X is started. The problem is present only if the <tt>fglrx</tt> kernel module is loaded, but independently of whether {{kernelconf|CONFIG_HIGHMEM||||||}} is enabled. A workaround is to limit RAM by adding the {{bootparm|mem|864m}} kernel parameter.

Version 8.16.20 fixes the problem.

===Display switching ===
The switching between internal and external display doesn't work with fglrx versions <= 8.24.8, because the driver blocks messing around with the chipset via ACPI. If you want to use this feature (i.e. during presentations), you should use the <tt>vesa</tt> server instead (experienced with a R52, Kernel 2.6.11, xorg 6.8.2, fglrx 8.16.20). Or boot notebook with CRT connected, it will automatically detect it and display on both.

===Composite Support===
ATI, as of fglrx 8.42.3 added composite windowing (alpha channel), enabling hardware accelerated translucent windows (primarily for 'eye candy.') This has not been tested yet, and reports will be added here as users evaluate this versus the R300 open source drivers.

For reference, some discussion of current status of drivers can be found in the Rage3d forums' (http://rage3d.com/board) Linux area.

Composite support is also supported with recent Mesa and Xorg > 7 with the open source 3d radeon / R300 drivers found in the linux kernel or debian's driver repository. It works with the [[R300]] / FireGL T2 series as found on the T43p extremely well. This has made rapid progress in speed with the latest few releases, and as of kernel 2.6.23 runs perfectly well with an R300 based card.

===Hardlock on X logout===
Up from driver version 8.19.10 you will experience a system hard lock when logging out from X, if the session manager (kdm/gdm) is not properly configured. You have to tell the session manager to restart X.

In the kdm config file (gentoo: {{path|/usr/kde/<VERSION>/share/config/kdm/kdmrc}}) you have to add following to the section <code>[X-:*-Core]</code>:
TerminateServer=true

In the gdm config (/etc/gdm/gdm.conf) file add the following to the daemon-section:
AlwaysRestartServer=true

Information from the ATI bugtracker: http://ati.cchtml.com/show_bug.cgi?id=239

Another reason of hardlock my be using the wrong AGP driver. Make sure that you have proper drivers for your motherboard loaded before fglrx: (gentoo: {{path|/etc/modules.autoload.d/kernel-2.6}}):
intel-agp
fglrx

A common problem seems to be mistakenly using ATI Chipset drivers instead of Intel.

Information from gentoo bugtracker: <s>[http://bugs.gentoo.org/show_bug.cgi?id=113685 113685]</s>. Fixed in 8.25.18

===Cannot switch to VT===

With usplash boot enabled, it may not be possible to switch to a VT from X (Using Alt+Fn). Tested on T60p (Mobility Fire GLV5200) on Ubuntu 6.06 / 6.10 and fglrx 8.25.18 / 8.28.8. Display may become garbled and system might freeze. Solution (testet on Ubuntu 6.10) is to either remove the "splash" kernel boot parameter or add "vga=791" parameter ("vga=794" can be used on 1400x1050 panel).

http://ati.cchtml.com/show_bug.cgi?id=37 <br>
https://launchpad.net/distros/ubuntu/+source/usplash/+bug/63558

===Flickering Display===

Some people have reported problems with their display flickering when using ati-drivers newer than 8.14.13. The problem is unclear
(possibly associated with an incorrect modeline setting) and no known solution exists except to use the open source radeon drivers.
You can follow this problem here: http://ati.cchtml.com/show_bug.cgi?id=248

===Error messages in system log===

If you find something like the following in {{path|/var/log/messages}}:

:{{cmdresult|kernel: mtrr: base(0xc0000000) is not aligned on a size(0x7ff0000) boundary}}
:{{cmdresult|kernel: [fglrx:firegl_addmap] *ERROR* mtrr allocation failed (-22)}}
:{{cmdresult|kernel: [fglrx:firegl_unlock] *ERROR* Process 5132 using kernel context 0}}

try to execute the following line and reload the fglrx module:

:{{cmdroot|1=echo "base=0xd0000000 size=0x8000000 type=write-combining" > /proc/mtrr}}

More detailed instructions can be found [http://ubuntuforums.org/showthread.php?t=115104 here].

===Hang when logging out===

A common problem is that when logging out from X, instead of gettign the KDM or GDM prompt, the system hangs.

This is discussed, including workarounds here: http://ati.cchtml.com/show_bug.cgi?id=239

===No power saving when CRT in use===

When both CRT and LCD are in use, power saving cannot be enabled.

This is reported here: http://ati.cchtml.com/show_bug.cgi?id=304

===WineX / Cedega Installs Software But Errors on Loading Games===

Some users may experience problems with certain FIREGL cards (in my case an ibm t43p laptop with a v3200 ati firegl) whereby projects such as cedega and wine refuse to work with 3d graphics, but native binaries (e.g. quake 4) work fine. A possible workaround is to add the following line in the drivers section of your /etc/X11/xorg.conf

Option "UseFastTLS" "2"

This option used to be configured with the older ati drivers when you ran "fglrxconfig". I have not yet found a way to get it to appear with "aticonfig", hence the manual insertion. This option is good for several linux distros I have tried, fedora core 5, ubuntu dapper and suse 10.1. It does not appear to effect performance on natively run programs.

{{NOTE|This may cause problems on machines with a Linux kernel version of 2.6.20 or higher (observed choppy video and video color inversion on T60p with both 2.6.20 and 2.6.21).}}

===Line Appears Below Mouse Cursor===

Some users have reported seeing a line approximately 1 mouse height below the bottom edge of the cursor, which follows the mouse and appears to change color based on the image below the cursor. This has been seen to happen using fglrx without the kernel module installed (in 2D mode) and additionally on external displays or multiple X servers. To work around the problem, try disabling the DGA extension by making the following changes to your XFree86.conf or xorg.conf file. Replace (or comment-out)
Load "extmod"
with
SubSection "extmod"
Option "omit xfree86-dga"
EndSubSection

===Freeze while using OpenGL Apps===

Some OpenGL applications such as screensavers or games (SecondLife) cause freezes. The cursor still moves, but otherwise the machine is unresponsive. This is the case with Xorg 7.1 and fglrx 8.29.6 using an x1400 and other cards. The solution is to add the following options to the video Device section in xorg.conf:
Option "Capabilities" "0x00000800"
Option "KernelModuleParm" "locked-userpages=0"

===Xv doesn't work correctly with drivers >= 8.36 and Xyyyy-cards===

See [http://ati.cchtml.com/show_bug.cgi?id=677] for further information. It seems as if only Xyyyy-cards are affected. Problem: graphical glitches with mplayer, programs like xine and totem might not start up at all. 8.35 doesn't seem to be affected

===Floating Point Exception with various X apps===

When the X server is left to autodetect the DPI, the fglrx driver may fail to supply the monitor dimensions. Video output switching may contribute to this bug.

Problems were experienced on T42p with Ubuntu 7.04, xorg-driver-fglrx 7.1.0-8.34.8+2.6.20.5-16.29.

This can be observed with xdpyinfo

:{{cmduser|xdpyinfo | grep dimensions}}
:{{cmdresult|dimensions: 1280x1024 pixels (0x0 millimeters)}}

Many applications will use the screen size and attempt to calculate DPI, resulting in a divide by zero operation and a SIGFPE.

A work around is to supply the dimensions in /etc/X11/xorg.conf. Use the DisplaySize parameter within your monitor's configuration. For example:

Section "Monitor"
Identifier "Generic Monitor"
HorizSync 28.0 - 64.0
VertRefresh 43.0 - 60.0
Option "DPMS"
DisplaySize 433 351
EndSection

=== Corrupted 3D display ===
With driver version 7-12 or later, you may experience a corrupted 3D display, if your horizontal screen resolution is not a multiple of 64. This is a known bug[http://support.ati.com/ics/support/default.asp?deptID=894&task=knowledge&questionID=31720] but ATI support does not have a solution to it yet.

There are two possible workarounds for this bug:

1/ Open the Catalyst Control Center and force the anti-aliasing to at least 2x for all applications. This surprisingly fixes the problem, at the expense of framerate.

2/ As suggested by ATI support, edit the /etc/X11/xorg.conf and find the section "Display". Add the following line into the "Display" section:
Virtual <width> <height>
where <width> is the width of your screen in pixels rounded up to the next multiple of 64 and <height> is the height of your screen in pixels.
For example, if your native resolution is 1400x1050, use
Virtual 1408 1050

After starting the X server you can run {{cmdresult|xrandr -s 0}} to restore the X server to a native display resolution, and 3D rendering will still work.

== Patches ==
The following patches might be needed for certain versions of fglrx. Before you apply any of these, make sure that you really need them, as some distributions include all the necessary patches with the appropriate package (e.g. ati-drivers in gentoo).

===fglrx 8.37.6===
* For kernel 2.6.22 you need this patch from a [http://www.phoronix.com/forums/showthread.php?t=2849 Phoronix thread].

===fglrx 8.35.5===
* [http://whoopie.gmxhome.de/linux/patches/2.6.20/fglrx-8.35.5-for-2.6.20.patch For kernel 2.6.20], part of the Fedora packaging scripts in the ATI installer

===fglrx 8.34.8===
* [http://whoopie.gmxhome.de/linux/patches/2.6.20/fglrx-8.34.8-for-2.6.20.patch For kernel 2.6.20]

===fglrx 8.32.5===
* [http://whoopie.gmxhome.de/linux/patches/2.6.19/fglrx-8.32.5-for-2.6.19.patch For kernel 2.6.19]

===fglrx 8.23.7===
* For kernel 2.6.16: [http://mirror.espri.arizona.edu/gentoo/rsync/x11-drivers/ati-drivers/files/ati-drivers-8.22.5-intermodule.patch <tt>intermodule</tt> patch] and [http://mirror.espri.arizona.edu/gentoo/rsync/x11-drivers/ati-drivers/files/ati-drivers-8.23.7-noiommu.patch <tt>noiommu</tt> patch]

===fglrx 8.21.7===

* [http://www.ksp.sk/~rasto/fglrx_with_2.6.15.patch for kernels >= 2.6.15]

===fglrx 8.20.8===

* [http://marc.theaimsgroup.com/?l=linux-kernel&m=113429835515001&w=2 for kernel 2.6.15]
or
* [http://www.ksp.sk/~rasto/fglrx_with_2.6.15.patch for kernels >= 2.6.15]

===fglrx (problem met at least with version 8.18.8)===
* [http://lkml.org/lkml/2005/9/22/183 for kernel >= 2.6.13 ] Missing verify_area bug

===fglrx 8.8.25 ===
* [http://www.rage3d.com/board/showthread.php?t=33798874 for kernels >= 2.6.10]
* [http://www.gehirn.org.uk/wiki/images/8.8.25-kernel-2.6.11+.patch For kernels >= 2.6.11-rc1]

===Links ===
* [http://gentoo-wiki.com/HOWTO_ATI_Drivers Gentoo HOWTO ATI]

Problems with ACPI suspend-to-ram

2008-04-28T15:45:08Z

Dave abrahams: /* Troubles on resume */

The following glitches may or may not occur in relation to suspending to RAM:

==Troubles on suspend==
;Permissions:If your suspend is failing, and a {{cmdroot|tail /var/log/acpid}} shows "Permission denied" errors, be sure that your new ACPI event and action scripts have the appropriate permissions.

;Write error:If {{cmdroot|echo mem > /sys/power/state}} shows "write error: Operation not permitted", verify that CONFIG_HOTPLUG_CPU option is enabled in the kernel. [[Software_Suspend_2|Suspend2]] automatically selects this option.

;Broken sysfs interface:You may experience problems when using {{cmdroot|echo standby > /sys/power/state}} or {{cmdroot|echo mem > /sys/power/state}} (machine goes to sleep and wakes up immediately). This can be avoided by using {{cmdroot|echo -n 3 >/proc/acpi/sleep}} to get it to sleep. This can be also happen if hotplug daemon is still running or if the usb hcd modules are still loaded.

;Immediate Resume after Suspend:If a resume starts a few seconds after suspend a reason might be the USB modules. Unload the modules uhci_hcd and ehci_hcd before you suspend. Users of hibernate-scripts add "UnloadModules uhci_hcd ehci_hcd" to {{path|/etc/hibernate/common.conf}}.

;Hangs on "switching to UP code":You may be using a [[How to make use of Dynamic Frequency Scaling|frequency scaling governor]] such as "conservative" or "ondemand", which sometimes have problems with suspending. Switching to a governor such as "powersave" or "performance" before suspending may solve this problem.

;MySQL daemon running:If you're running MySQL, sleep may also not work, so stop MySQL first, then sleep. Remember to restart MySQL when you wakeup.

;LCD backlight remains on during sleep:When your system is equiped with a Radeon Mobility graphic controller your [[Problem with LCD backlight remaining on during ACPI sleep|LCD backlight may not turn off automatically]]. Use [[radeontool]] to switch off your backlight prior suspend in your sleep action script.

;High power drain during sleep:Also, you might want to take note of the [[Problem with high power drain in ACPI sleep]].

;Built-in MMC reader:If you have an MMC reader, and the computer hangs when attempting suspend then remove sdhci, mmc_block, and mmc_core modules before suspending.

;Could not power down device <NULL>: error -22:If you have the acpi_cpufreq kernel module loaded, this prevents suspension.

;Immediate Resume, but Suspend "moon" light continues to flash:???

;Hard system lock up:If you are using savagefb, make sure to [[Problem_with_unusable_console|disable the "Console Acceleration" option]] (CONFIG_FB_SAVAGE_ACCEL) in the kernel config. Otherwise, susped-to-RAM may lock up your system such that you must remove the AC adapter and battery to get it to boot again.

==Troubles on resume==
;Blank display on resume:
:When resuming from a suspend-to-ram the display might remain black (on {{X60}}) or might only show the pre-suspend output (the system is still rebootable via {{key|ctrl}}{{key|alt}}{{key|del}}). See [[Problem with display remaining black after resume]] for solutions. See also '''System hang on resume''' on this page - which may be potentially mismatched with this one.

;No mouse cursor on resume:
:When resuming from a suspend-to-ram your X cursor might be invisible(on {{X40}}) when using {{path|/sys/power/state}} directly to suspend, they way to fix this is to rerun the post bios code after returning for suspending.
:{{cmdroot|FGCONSOLE<nowiki>=</nowiki>`fgconsole\`}}
:{{cmdroot|chvt 1 && echo -n mem >/sys/power/state}}
:{{cmdroot|vbetool post && chvt 7 && chvt $FGCONSOLE}}

;Garbage on text consoles on resume:When resuming from suspend-to-ram the text console displays may show garbage instead of actual text. The machine is otherwise still responsive and X displays fine. If all of this is true, then adding the kernel option {{bootparm|acpi_sleep|s3_bios,s3_mode}} in your menu.lst or lilo.conf may solve the problem.

;Broken hardware support after resume:
:*The '''serial port''' of the port replicator might not work after resume.
:*The '''parallel port''' might not work after resume. A possible fix is to unload and reload the parallel port drivers: {{cmdroot|rmmod lp parport_pc parport; modprobe lp}}.
:*Problems with the '''CD-RW/DVD drive''' after wake up from ram have been experienced.
:*There is a known Problem regarding '''battery info''' after suspend to RAM. A [http://www.ussg.iu.edu/hypermail/linux/kernel/0511.0/2429.html small patch] exists for kernels 2.6.14/2.6.15.
:*On {{X20}} and {{X21}} (and possibly other) models, the '''sleep LED''' is not reset properly on resume and will keep blinking. If you have the [[ibm-acpi]] kernel module loaded with the {{bootparm|ibm-acpi.experimental|1}} option, you can switch it off on resume by appending the following line to your suspend script: {{cmdroot|echo 7 off > /proc/acpi/ibm/led}}

;Crash on resume:
:*When using '''older ATI proprietary drivers''' a crash on resume can be solved by using [http://freshmeat.net/projects/vbetool/ vbetool]. See the example suspend script [[Problem with display remaining black after resume#Solution for ThinkPads with Intel I830 Chipset]]. This is no longer necessary with recent revisions of the ATI proprietary driver.
:*A crash could also be caused by having '''apic support''' enabled in the kernel config. Try disabling it (in the "Processor type and features" section).
:*On machines with Savage chipsets, the '''savagefb framebuffer driver''' might crash the machine on resume. Make sure it is disabled in your kernel config and use the standard vesafb driver instead.
:*SATA-based laptops utilize the '''libata layer for disk access''' which does not have fully-working power-management support before Linux kernel 2.6.16 (ata_piix) and 2.6.19 (ahci). Suspend to RAM crashes these machines on resume. See the [[Problems with SATA and Linux#Hang on resume from suspend to RAM|relevant section]] on the [[Problems with SATA and Linux]] page.
:*Using [[HDAPS]] as a module causes a crash on resume with the Linux kernel 2.6.19 (possibly even earlier versions). This was observed on a {{X41}}. Try unloading the module before suspending.
:*Gnome-power-manager might be using the wrong backend. If you are able to suspend from the commandline with a certain method, make sure the others are not available so that g-p-m doesn't choose the wrong one. For example, if you suspend with {{cmdroot|echo mem > /sys/power/state}}, make sure '''uswsusp''' and '''hibernate''' are uninstalled.

;System hang on resume:
:System hangs immediately upon attempted resume if suspended with USB devices attached to dock. Try using the laptop's own USB ports instead. That fixed the problem for me. Details: https://bugs.launchpad.net/ubuntu/+bug/218760 --[[User:Dave abrahams|Dave abrahams]] 17:45, 28 April 2008 (CEST)
:When system resumes it hangs right after restarting tasks. Strange thing is, that you may be even able to restart your ThinkPad using {{key|ctrl}}{{key|alt}}{{key|del}}, but if you try to blindly exec a command, it will not work, (eg. touch FILE) so it's not only the problem of videocard. This may be fixed by passing {{bootparm|ec_intr|0}} on kernel cmdline. Affected models: {{T20}}, {{T21}} (at least [[2648-46U]] (T20),[[2647-8AG]] (T21)).
:'''Note:''' ''this is resolved in kernel 2.6.20, there is no need to pass the {{bootparm|ec_intr|0}} bootparam anymore (moreover, you are discouraged to use it) See [http://bugzilla.kernel.org/show_bug.cgi?id=6749 revelant kernel bug report]''
:See also [https://bugs.launchpad.net/ubuntu/+source/acpi/+bug/73546 this bug report], I can confirm some strange problems on resume with Bluetooth enabled - my T61 may freeze in a couple of minutes after resuming. This problem is gone as soon as I disable Bluetooth (stop all bluetooth related services and `echo "disable" > /proc/acpi/ibm/bluetooth`).

;Shutdown on resume:
:If your system immediately begins to shut down right after resume, make sure you don't have acpid running with the power button tied to shutdown. The system is simply sensing the power button event and shutting down. This issue has been reported as a bug against the kernel ACPI subsystem, refer to [http://bugzilla.kernel.org/show_bug.cgi?id=6612 kernel.org bugzilla bug #6612].

;Immediate suspend on resume:
:When running GNOME, sometimes gnome-power-manager will put the system back into suspend immediately after resuming. This is caused by a known bug in HAL that causes some ACPI events to be reported incorrectly after a suspend-to-ram. A simple workaround can be found [http://live.gnome.org/GnomePowerManager/Faq?action=recall&rev=28#head-b8b1280115b0a51c2cc27b13a57121130ebf36cb here].
:Note that suspend being triggered by unrelated ACPI events such as disconnecting the AC adapter may also be fixed by the above method.

;Power Off when suspended laptop is docked
:When T60p is suspended, docking laptop into Advanced Dock immediately turns off laptop and crescent moon sleep indicator LED. Pressing power button initiates cold boot. Also reported by multiple people on thinkpads.com.

;SectorIdNotFound disk errors when laptop is resumed
:The errors look like this:
Oct 14 17:35:02 cacharro kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Oct 14 17:35:02 cacharro kernel: hda: dma_intr: error=0x10 { SectorIdNotFound }, LBAsect=115896900, sector=115896900
Oct 14 17:35:02 cacharro kernel: ide: failed opcode was: unknown

:This happens when you have [[Hidden Protected Area]] (HPA) enabled on the hard drive. There is a [http://bugzilla.kernel.org/show_bug.cgi?id=6840 kernel bug report with an unfinished patch] to fix this. This is not fixed as of kernel 2.16.18.

User:Dave abrahams

2008-04-25T15:02:36Z

Dave abrahams: â†Created page with 'You can reach Dave at dave AT boost-consulting.com'

You can reach Dave at dave AT boost-consulting.com

Talk:Fan control scripts

2008-04-25T15:01:27Z

Dave abrahams: New section: Improvements for t60-fancontrold

Wyrfel, are you sure the recent (19:54, 27 Oct 2005) cosmetic change was a good idea? The extensive chunks of code make it hard to grok the structure of the article in the absense of separator lines (which "===" doesn't have). --[[User:Thinker|Thinker]] 22:10, 27 Oct 2005 (CEST)
----
We can discuss this. From my point of view, the chunks of code distinguish themselves from each other quite well, because they are each in one code block.

I do not like the <nowiki>=</nowiki> section level - and so far we avoided them on all pages - because
* it generates H1 headings, which is the same as the page heading,
* having more than one level with the hbars is confusing/less readable, because they are not very well distinguishable. This way i.e. the "Other" section looked like a separate empty secion.

I think the way it's now, the separator lines make it possible to easily distinguish the different main sections, while when you have both levels with separator lines, an additional task of distinguishing H1 and H2 separators is necessary.

However, i see your point as well and would like to hear more opinions/arguments.

[[User:Wyrfel|Wyrfel]] 22:31, 27 Oct 2005 (CEST)
----

===<tt>bash</tt> script with fine control over fan speed (for unpatched kernels)===
Moved to the [[ACPI fan control script|article page]], after joint development by [[User:Spiney|Spiney]] and [[User:Thinker|Thinker]].

----

''Note that the fan levels, thresholds and anti-pulsing hacks are system-specific, so you may need to adjust them.''

I think it'd probably be nice to have a table of the suggested values here. Those in the "unpatched kernels" script seems to work fine on my R52, but the other scripts all have different values.

--[[User:Micampe|Micampe]] 08:19, 12 Nov 2005 (CET)

== Sensor-specific variable-speed script ==

Here's a new variable-speed control script that lets you define the temperature range separately for each sensor. To keep things simple, it auto-computes the trip points (unlike the current script). Works well on a {{T43}}, and (just barely) keeps the fan off most of the time with CPU undervolting and [[fglrx]] set to maximum power saving. Feedback on other machines would be appreciated.

Any idea what are the sensors at EC offsets 0x79, 0x7A, 0xC0, 0xC1, 0xC2? On the T43, 0x79 seems to be the same as the HDAPS sensor (it never deviates by more than one degree from what the HDAPS sensor tells directly), but I don't know where it's located. Sensor 0x7A is uncorrelated with disk temperature and activity, so it can't be HDD like reported ofor R52. Sensor 0xC1 seems to be under the palm-rest (see discussion in [[Talk:Problem_with_fan_noise]]).

This version also lets the EC read the RPM sensor every few minutes even when the anti-pulsing hack (which normally prevents this) is in use.

<i><b>Script moved to the [[ACPI fan control script#Variable speed control scripts|article page]]</b></i>.
{{HINT|If you followed a link here looking for thermal sensor information, see the [[ACPI fan control script#Variable speed control scripts|article page]] and the page on [[thermal sensors]].}}

Feedback very much welcome.

--[[User:Thinker|Thinker]] 23:08, 27 Nov 2005 (CET)

:I use the script on my T41 and it works great, it doesn't crash like the windows fancontrol (check sourceforge).
:Some remarks: I removed the anti pulsing section because it didn't do anything useful on my laptop. I also raised some temperatures and removed the speed '1', because it barely cools my laptop and makes only slightly less noise than speed '3', which now replaces speed '1'. [[User:SirB|SirB]] 18:55, 20 July 2006 (CEST)
----

== Fan enable/disable scripts ==

We currently have two types of scripts -- the old ones which only enable/disable the fan, and the new ones which control the fan speed. Do the latter supercede the former, or do we know of models on which only enable/disable works? Maybe eventually the enable/disable scripts should be "archived" in the talk page to reduce clutter in the article?

--[[User:Thinker|Thinker]] 00:08, 28 Nov 2005 (CET)
----

Things seem pretty stable for the variable-speed script and the [[Patch_for_controlling_fan_speed#Models_on_which_this_patch_works|list of working models]] looks good. Since it is superior to the enable/disable scripts in regard to both the annoyance and the impact on hardware, I'll change the organization of the page to put that script first (unless someone objects)..

--[[User:Thinker|Thinker]] 16:07, 7 Dec 2005 (CET)
----

I don't see the point in having the enable/disable scripts when the variable speed one works fine. I'd vote for moving the old scripts here and only keep the better ones in the article, unless somebody has a sane use case for which those are bettere than the new scripts.

--[[User:Micampe|Micampe]] 16:19, 7 Dec 2005 (CET)

== working on a thinkpad X20? ==

hello!
my /proc/acpi/ibm directory looks like this:

m@homebase:/proc/acpi/ibm$ ls
bay bluetooth dock driver hotkey light video

so the scripts donÂ´t work, because i do not hat a /proc/acpi/ibm/thermal or a /proc/acpi/ibm/fan directory!
do you have any ideas whats wrong?

--Manfreeed

What version of ibm_acpi are you using ("cat /proc/acpi/ibm/driver")? Did you load it with the "experimental=1" module parameter?

--[[User:Thinker|Thinker]] 19:30, 26 Dec 2005 (CET)
:hallo agian, i use IBM ThinkPad ACPI Extras version:0.8 on a Ubuntu Linux with kernel: 2.6.12-10-386. i didnÂ´t change any module parameter. how can i do this? thanks for your help! --[[User:Manfreeed|Manfreeed]] 22:14, 27 Dec 2005 (CET)

You need a newer kernel 2.6.14 or newer, or to manually install ibm_api 0.12. It's all explained in [[ibm-acpi]].

--[[User:Thinker|Thinker]] 06:43, 28 Dec 2005 (CET)

There is no 0.12 available as a separate download, it is only included in 2.6.14. But 0.11 from the website works just fine for me with the stock Ubuntu kernel.

--[[User:Micampe|Micampe]] 11:11, 28 Dec 2005 (CET)

----

== Question on temperatures ==

I've been testing the 'script with fine control over fan speed' on my r50e, kernel 2.6.15, which still contains version 0.12a of the ibm_acpi module. The script works fine but I notice two things:

1. The seven speed levels don't seem to correspond with seven actual speeds but rather with only three. I also notice that only 3 levels, 2, 4 and 7 are actually used in the script.

2. The given range of temperatures - 52, 60, 68 - causes the fan in my Thinkpad to run even more often than under embedded control, so I would naturally like to raise them. As the maximum core temperature is 100Â°C, I wonder why I shouldn't use, say 72, 80, 88 instead. - How (im)precise are the temperature data in /proc/acpi/ibm/thermal?

antonix
----

1. On all models I'm aware of, some of the levels are equivelent. So the script only bothers with the different ones. You can test your model manually using [[How to control fan speed]].

2. Yes, in the script you used (the "simple" one), the threshold for highest fan speed is set fairly low, because the same threshold is used for all components and some are more sensitive than others. The "comprehensive" script, also on the article page, lets you control each component separately, so you can raise the threshold for the CPU and GPU without risking burning something else. But note that the thresholds listed there were chosen for a T43, which probably has different [[thermal sensors]] than your R50e.

--[[User:Thinker|Thinker]] 10:00, 14 March 2006 (CET)
----

== Comprehensive script - OFF_THRESH_DELTA doesn't work ==

No matter to what value I set the OFF_THRESH_DELTA, fan always turns off at 10 degrees below min temperature. Is there any way to make it work properly? I have a R50e with Gentoo Linux, kernel 2.6.17.
Regards
Caleb9

Please run the '''unmodified''' tp-fancontrol in non-daemon non-quiet mode (so you'll see all the verbose status reports), and post examples of the status lines when it does the wrong thing.
--[[User:Thinker|Thinker]] 15:50, 21 October 2006 (CEST)

== t60-fancontrold script ==

Hi all,

since I wasn't entirely satisfied with how tp-fancontrol worked on my T60, I decided to write an alternative script derived from t60-fancontrol (but differing in some respects). It is meant to run as a daemon by default and the main changes are

- different fan level stepping/calculation algorithm

- no perl dependency

- proper config file parsing

- changed/differently behaving command line options

- support for docked and undocked status (different thermal ranges)

- more standard init.d start script

- different temperature values (optimized for my T60)

Get it at

http://www.hobbes.gmxhome.de/t60-fancontrold/0.1.4.1/t60-fancontrold-0.1.4.1.tar.gz (source)

and

http://www.hobbes.gmxhome.de/t60-fancontrold/0.1.4.1/t60-fancontrold-0.1.4.1-1.noarch.rpm (built for SuSE Linux 10.1)

I developed it on SuSE Linux 10.1 and tested it on my T60 (2007-FSG, Core Duo T2400, ATI X1400 128 MB). Since I don't have any experience with other ThinkPad's, I can only recommend it for the T60 series, but it might work just as well on other models (with adapted temperature ranges). It works fine for me, but I surely didn't catch all bugs.

Although I must emphasize that the script comes without any warranty (see also README), I'd be happy if you'd test it and give me feedback. Please read the README for general and installation information.

Best regards, Nick.
----

Can you summarize the difference in the algorithm, and its motivation?

--[[User:Thinker|Thinker]] 23:59, 2 December 2006 (CET)
----

The stepping down from a certain level when all sensor temperatures were long below the respective thresholds didn't seems to work for me. I played around with the temperature ranges and other control parameters, but that didn't help much.

When I looked into the tp-fancontrol routines, the coding in the script appeared - please, no offense - a bit dense ;-) Apart from that, a proper config file with respective parsing in the script was missing. Also I didn't see the necessity of using perl.

Besides the fact that I enjoyed the bit of coding, the fan is now controlled better on my T60. My post was just to let you know about t60-fancontrold and not meant offensive in any way.

To better see what I've done I recommend that you look at the code itself, which presumably tells you a lot more than I can illustrate in my posting.

All the best

--[[User:Narend|nick]] 00:25, 3 December 2006 (CET)
----

No offence taken, I'm just curious since it worked great for me. About lowering levels, there are two (intentional) hysteresis effects involved: first, the temperature at which it steps down is lower than the temperature at which it steps up. Second, once it entered a given level, it will not step down before $MIN_WAIT seconds have passed. Both are important so I hope your script does them too (in which case, I guess its code is just as dense...).

--[[User:Thinker|Thinker]] 00:47, 3 December 2006 (CET)
----

My script has something like the MIN_WAIT time loop, but it's implemented in a different way: the passed time is not measured absolutely in seconds and then checked against the current time, but in terms of how many INTERVAL cycles where all sensor temperatures are below the threshold-DELTA_T limit have since passed. The respective parameter in my script is called MIN_WAIT_INTERVALS.

Besides the temperature/stepping algorithm, t60-fancontrold has a more standardized init.d start script (for SuSE 10.1, which is a good choice for the T60) and all options can be set in the config file now, which is actually parsed, not just sourced by tp-fancontrol.init. Also I found that I needed different temperature levels when working docked or undocked.

But all other ThinkPad users seem to be getting along with tp-fancontrol quite well, so I guess the fun when writing t60-fancontrold was another factor ;-)

Thank you very much for your comments, if you have more, please let me known them!

Regards,

--[[User:Narend|nick]] 09:52, 3 December 2006 (CET)

----

Would anybody object if I added an entry for t60-fancontrold under "Other" on the "ACPI fan control script" article page?
Did somebody try t60-fancontrold or are there any comments on the code?

Best,

--[[User:Narend|nick]] 12:04, 5 December 2006 (CET)

Sure, go ahead. You can give it an informative subsection of its own.

--[[User:Thinker|Thinker]] 21:03, 5 December 2006 (CET)
----

Nick, I'd be interested in knowing the temperature ranges you have defined for your T60. Unfortunately, your scripts aren't available (anymore) at the links you have provided.

--[[User:Gunnar|Gunnar]] 23:35, 9 January 2007 (CET)
----

== cat: /sys/block/hda/device/model: No such file or directory ==

Every 15 seconds, I get this error message when running <code>tp-fancontrol -q</code> on Ubuntu Edgy on my T60.

I don't quite understand since <code>/dev/hda</code> is my optical drive. The hard disk is <code>/dev/sda</code>.

--[[User:Gunnar|Gunnar]] 11:32, 8 January 2007 (CET)

== same problem with cat: /sys/block... ==

hi Gunnar,

does your tp-fancontrol also quit after a few minutes when running in daemon mode?

--[[User:Nilsja|Nilsja]] 01:20, 30 January 2007 (CET)

----
No, the deamon runs fine.

--[[User:Gunnar|Gunnar]] 13:43, 5 February 2007 (CET)
----

== Script errors out ==

I tried using the fancontrol script, but it errored out on line 201:

<code>
tp-fancontrol.orig: line 201: syntax error near unexpected token `<'
tp-fancontrol.orig: line 201: ` read X Y1 Y2 Y3 Y4 Y5 Y6 Y7 Y8 Z1 Z2 Z3 JNK < <(echo "$THERMAL") '
</code>

I searched the revision history, and taking out a previous change made the script work again:

<code>
--- tp-fancontrol.orig 2007-02-01 13:33:25.000000000 +0100
+++ tp-fancontrol 2007-02-01 13:35:25.000000000 +0100
@@ -197,9 +197,15 @@
thermometer() { # output list of temperatures
# 8 basic temperatures from ibm-acpi:
[[ -r $IBM_ACPI/thermal ]] || { echo "$0: Cannot read $IBM_ACPI/thermal" 2>&1 ; exit 1; }
- read THERMAL < $IBM_ACPI/thermal
- read X Y1 Y2 Y3 Y4 Y5 Y6 Y7 Y8 Z1 Z2 Z3 JNK < <(echo "$THERMAL")
- [[ "$X" == "temperatures:" ]] || { echo "$0: Bad readout: \"$THERMAL\"" >&2; exit 1; }
+## Newer code, that did not seem to work here...
+# read THERMAL < $IBM_ACPI/thermal
+# read X Y1 Y2 Y3 Y4 Y5 Y6 Y7 Y8 Z1 Z2 Z3 JNK < echo "$THERMAL"
+# [[ "$X" == "temperatures:" ]] || { echo "$0: Bad readout: \"$THERMAL\"" >&2; exit 1; }
+
+## Older code...
+ read X Y1 Y2 Y3 Y4 Y5 Y6 Y7 Y8 Z1 Z2 Z3 JNK < $IBM_ACPI/thermal
+ [[ "$X" == "temperatures:" ]] || { echo "$0: Bad temperatures: $X $Y $Z" >&2; exit 1; }
+
echo -n "$Y1 $Y2 $Y3 $Y4 $Y5 $Y6 $Y7 $Y8 ";
# 3 extra temperatures from ibm_acpi:
if [[ -n "$Z1" && -n "$Z2" && -n "$Z3" ]]; then
@@ -422,4 +428,4 @@
[ -e "$PID_FILE" ] && echo "WARNING: daemon already running"
set_priority
control_fan
</code>

By the way, I tested this script using glxgears, so cpu went to 100% (kernel 2.6.18.6, fglrx driver, t43p), and saw gpu-temperature go up to 86 degrees, at which point I quit glxgears. I thought this was a bit high...

--[[User:PJBrs|PJBrs]] 13:47, 01 February 2007 (CET)

== T60 temperature thresholds? ==

Does someone have reasonable thresholds for T60 with T5600 / X1400?

--[[User:Burp|Burp]] 15:18, 23 February 2007 (CET)

== Am I doing something wrong? ==

I just tried version 3.02 of the tp-fancontrol script, but I still get:

# sh Packages/tp-fancontrol-3.02
Packages/tp-fancontrol-3.02: line 201: syntax error near unexpected token `<'
Packages/tp-fancontrol-3.02: line 201: ` read X Y1 Y2 Y3 Y4 Y5 Y6 Y7 Y8 Z1 Z2 Z3 JNK < <(echo "$THERMAL") '

I'm not good enough at scripting to figure out why it's erroring out. This is on Slackware 11. Any suggestions?

--[[User:PJBrs|PJBrs]] - 19 March 2007
----

Probably your {{path|/bin/bash}} is too old.

--[[User:Thinker|Thinker]] 15:49, 19 March 2007 (CET)
----

Hi Thinker, I just checked, and as of this morning I'm running bash 3.2.015, which seems to be the newest version, and I had the same error. Still, the script is running very nice by reverting one change around line 201 (see the above patch). Unfortunately I have only the faintest idea of what line 201 tries to accomplish, and no idea how to change it. Anyone else have the same problem?

--[[User:PJBrs|PJBrs]] - 26 March 2007
----

That line tells the <tt>read</tt> command to read its input from the file descriptor which serves as the output of the <tt>echo</tt> command. In other words, it's similar to "<tt>echo ... | read ...</tt>", except that the latter forgets the read data (because they way bash forking works).

Anyway, try this on your bash:
read X < <(echo foo); echo $X
On bash 3.1.17 it says <tt>foo</tt>.

--[[User:Thinker|Thinker]] 01:57, 27 March 2007 (CEST)
----

It says <tt>foo</tt> for me (using the bash 3.1.17 too (on debian testing), but the script brakes at line 201 anyway...

I also have no /sys/block/hda/device/model even my harddrive is hda.
"hdparm -i /dev/hda" shows the model and "hdparm -H" works without a problem.
Model is HTS421212H9AT00

--[[User:BDKMPSS|BDKMPSS]] May 26 2007
----
As of today I switched to the libata driver and get a /sys/block/sda/device/model "file"
I hacked my script to read the HDD-temp if it found my model (see above) and everything works without any problem.

the script also runs fine without braking at line 201, but I really can't figure out why. Still the same bash, most library's unchanged... some debian-testing update should have fixed this...

--[[User:BDKMPSS|BDKMPSS]] July 02 2007
----

== Update t60-fancontrold ==

Hi,

I updated t60-fancontrold to work with ibm_acpi 0.13 (kernel >= 2.6.20) and supported the new level and watchdog command features. You can download t60-fancontrold-0.1.6.1 from http://hobbes.gmxhome.de (.tar.gz and SuSE .rpm). All changes seem to work fine for me, if you find any bugs, please report them (see file README).

Cheers,

--[[User:Narend|nick]] 19:33, 1 May 2007 (CEST)

== Limiting/lowering CPU clock during temperature emergency ==

Recently I had to have my T41's mainboard replaced. This fixed a number of problems, but since then I've been experiencing system overheating. Basically, anything that pegs the CPU overheats the machine, and the kernel shuts it down. This can be a kernel compile, an overzealous java application, or even just Debian regenerating a font cache. The fan runs fine, I have cleared out any dust, and the heatsink appears to be on properly. Since my machine is out of warranty, I just have to make do.

I've discovered that if I throttle my cpufreq governor, I don't have this problem. That is, my 1.6GHz machine has a second frequency of 1.2GHz. If I run at 1.2GHz, I don't overheat. However, it does make everything a little slower. I would like to have 1.6GHz when Firefox wants to spike, but 1.2GHz when my compile is threatening to overheat the machine.

I have modified tp-fancontrol to do this. I grabbed 0.3.02, the latest on this page. I then taught it the -H option. You pass the throttling frequency in KHz, because that's what all the cpufreq knobs use. If you do not provide the -H option, tp-fancontrol does not touch the cpu frequencies.

Here's how it works. When tp-fancontrol decides the system needs the maximum fan speed, it also sets the governor's maximum frequency to the throttle frequency. The governor is free to act as it always does, but it will not use a frequency higher than the throttle frequency. When the fan speed is reduced, the governor's maximum frequence will be set back to the hardware's maximum. Upon exit, the hardware maximum will be restored as well.

I have also modifed tp-fancontrol.conf to allow specifying the throttle frequency and tp-fancontrol.init to pass the frequency on to tp-fancontrol. I'm running this on my Debian machine right now.

The scripts are at http://jlbec.org/software/misc/tp-fancontrol-cpu-throttle.tar.gz

I realize that most machines will have no trouble cooling themselves at their maximum frequency. I just wanted to put this out there in case anyone else had a similar problem, or if folks wanted to help their system cool down from maximum temperature.

-- jlbec 2007.05.10 @ 18:06 PDT

I changed the title to some other phrasing to avoid confusion with the ACPI T-states.

Also, you might want to buy some extremely high quality thermal compound (but not that one that corrodes aluminium!), remove your fan assembly and heatsink assembly, clean it up (and also all chipsets it touches) completely, and apply the new compound in a very thin and smooth layer. Make extremely sure the heatsink assembly is sitting '''very''' tightly over the new thermal compound. That might well fix your overheating problems for good...

I am not an user of tp-fancontrol, so maybe it already does this but still, check it to make sure it is setting the fan to the disengaged/full-speed fan level when you hit the emergency threshold, as that is '''much''' faster than the normal highest speed of the fan.

--[[User:Hmh|hmh]] 09:14, 12 May 2007 (CEST)

No problem on the title change.

I've pulled off the heatsink and checked the thermal compound looks good. I've tested with disengaged, still doesn't keep the laptop from overheating :-(

-- jlbec 2007.05.11 @ 00:35 PDT

== fan pulsing noise on X31 despite tp-fancontrol ==

Hi everybody. I use tp-fancontrol to run my fan on my X31, but the noise when the fan pulses every 4 seconds is still here. However, the ACPI fan control script webpage on Thinkwiki says that I can adapt the script to my X31 : ''Note that the fan levels, thresholds and anti-pulsing hacks are system-specific, so you may need to adjust them.'' I have looked everywhere, even through the scripts to try to discover what I could modify myself, but I did not find anything. Could someone tell me what I could do to solve this issue concerning my fan pulsing noise ? Thanks in advance.

-- MetallicDuck, 28 July 2007 @ 6:05 PM (CEST)

absolutely the same fault here...
I tried some hours to make this work, even changing the actual code, but also have no solution.
Maybe the embedded controler is not so foolish like "the other ones"...

-- [[User:BDKMPSS|BDKMPSS]], 29 July 2007

Happy to know that I m not alone :) . My Thinkpad X31 have a BIOS v. 3.02 and an embedded controller v. 1.03. Does anyone who has upgraded the BIOS or the embedded controller has noticed some better behavior of the fan concerning the pulsing noise ?

-- MetallicDuck, 29 July 2007 @ 1:22 PM (CEST)

No I use (like always) the latest greatest (3.02/1.08), which fixed some other long forgotten problems, but not the fan pulsing.

-- [[User:BDKMPSS|BDKMPSS]], 29 July 2007

== patch for tp-fancontrol to monitor thermal_zone ==

tp-fancontrol does not monitor acpi/thermal_zone which is no problem on most thinkpads, but on a T60 THM1 is the real CPU temp, which is not available via IBM/thermal.

So this patch does also monitor these two.

<pre>
--- tp-fancontrol 2007-11-12 16:39:41.000000000 +0100
+++ tp-fancontrol.new 2007-11-12 16:45:57.000000000 +0100
@@ -47,6 +47,9 @@

47 58 # HDD -> -> -> Hard disk internal sensor
47 60 # HDAPS -> -> -> HDAPS readout (same as EC 0x79)
+
+ 45 60 # THERMAL0
+ 55 70 # THERMAL1
)

@@ -216,7 +219,17 @@
if [ -r $HDAPS_TEMP ]; then
Y="`cat $HDAPS_TEMP`"
(( "$Y" > 100 )) || echo -n "$Y " # the HDAPS readouts are nonsensical right after resume
+ else
+ echo -n "-128 "
fi
+
+ # thermal_zone
+ echo -n "$SEP "
+ for THM in 0 1; do
+ cat $IBM_ACPI/../thermal_zone/THM${THM}/temperature | perl -ne 'm/(\d+)/; print $1'
+ echo -n " "
+ done
+
return 0
}

</pre>
[[User:Urandom|Urandom]] 17:07, 13 November 2007 (UTC)

== Improvements for t60-fancontrold ==

Hi Nick,

I made one simple improvement, which allows the fan to run disengaged (fastest) when the temperature is really critical. I need that because whenever I start a really heavy multithreaded compilation my machine eventually shuts down to protect itself, with this in the log. and I think I may have corrected a small bug in the code where it tries to disengage briefly.

<pre>
--- ../t60-fancontrold 2008-04-25 10:21:09.462753198 -0400
+++ t60-fancontrold 2008-04-25 10:21:57.679070003 -0400
@@ -60,9 +60,9 @@
HAVE_WATCHDOG_CMD=
WATCHDOG_DELAY=15

-FAN_LEVELS=(0 2 4 7)
-ANTIPULSE=( 0 1 1 0 ) # Prevent fan pulsing noise at this level
- # (reduces frequency of fan RPM updates)
+FAN_LEVELS=(0 2 4 7 8)
+ANTIPULSE=( 0 1 1 0 0 ) # Prevent fan pulsing noise at this level
+ # (reduces frequency of fan RPM updates)

NUMBER_FAN_LEVELS=${#FAN_LEVELS[@]}

@@ -873,11 +873,17 @@

if ! ${DRY_RUN} && ! ${EXIT_SIGNALLED} ; then
if ${HAVE_LEVEL_CMD} ; then
+ if [ ${arg} -eq 8 ]; then
+ arg=disengaged
+ fi
if ! echo "level ${arg}" > ${ACPI_FAN} ; then
log "ERROR: Setting fan level failed."
exit 1
fi
else
+ if [ ${arg} -eq 8 ]; then
+ arg=0x40
+ fi
if ! echo 0x2F ${arg} > ${ACPI_ECDUMP} ; then
log "ERROR: Writing to ${ACPI_ECDUMP} failed."
exit 1
@@ -1111,7 +1117,7 @@
if [ ${SETTLE_LEFT} -ge 0 ]; then
SETTLE_LEFT=$(( SETTLE_LEFT-INTERVAL ))
else
- set_fan_level 0x40 # disengage briefly to fool embedded controller
+ set_fan_level 8 # disengage briefly to fool embedded controller
sleep 0.5
RESETTLE_LEFT=$(( RESETTLE_LEFT-INTERVAL ))
fi
</pre>

One problem I'm having is that my T60p seems to have different thermal zones than your T60, since my fan immediately maxes out due to BAT0. With no particularly great load, I am seeing

t60-fancontrold: INFO: Temperatures at startup are: 58 40 36 78 50 -128 27 -128
t60-fancontrold: INFO: Additional thermal sensors found. Temperature values are: 41 56 56 -128 -128 -128 -128 -128

So I need to figure out how to account for that.

Some further improvements I would really like to see:

* set the frequencyc scaling governor to powersave or conservative before the temperature becomes truly critical
* adjust for the new kernel docking station support, since /proc/acpi/ibm/dock is no longer supported

I'd be more than happy to work with you on any of these.
--[[User:Dave abrahams|Dave abrahams]] 17:01, 25 April 2008 (CEST)

Installing Ubuntu 7.10 (Gutsy Gibbon) on a Thinkpad T60

2008-01-10T02:51:32Z

Dave abrahams: /* Upgrading to FGLRX-8.443.1 */

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Reboot...

=== Active Protection System (Reduced Power Version) ===

We will need a patched kernel (see [[#Building a custom kernel]]), tp-smapi kernel modules >= 0.32 and hdapsd userspace daemon newer than 2007-05-24.

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.32-3_all.deb}}
{{cmduser|sudo dpkg -i tp-smapi-source_0.32-3_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.32-3+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}}

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

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

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

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

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

Installing Ubuntu 7.10 (Gutsy Gibbon) on a Thinkpad T60

2008-01-10T02:48:03Z

Dave abrahams: I don't know what my problem was. Hard to understand this code, but bash doesn't seem to have a problem with it.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Reboot...

=== Active Protection System (Reduced Power Version) ===

We will need a patched kernel (see [[#Building a custom kernel]]), tp-smapi kernel modules >= 0.32 and hdapsd userspace daemon newer than 2007-05-24.

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.32-3_all.deb}}
{{cmduser|sudo dpkg -i tp-smapi-source_0.32-3_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.32-3+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}}

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

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

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

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

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

Installing Ubuntu 7.10 (Gutsy Gibbon) on a Thinkpad T60

2008-01-06T18:45:34Z

Dave abrahams: Add info about how to customize the kernel using menuconfig. There's probably a more elegant way than copying, but doing it in-place causes debian/rules to issue an error.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Get restricted modules source:
{{cmduser|sudo apt-get build-dep linux-restricted-modules-common}}
{{cmduser|apt-get source linux-restricted-modules-common}}
{{cmduser|cd linux-restricted-modules-2.6.22-2.6.22.4}}
Create a dummy control file entry:
{{cmduser|mv debian/control.stub.in debian/control.stub.in.orig}}
{{cmduser|sed s/-@@ABIVER@@-generic/-@@ABIVER@@-thinkpad/ debian/control.stub.in.orig > debian/control.stub.in}}
{{cmduser|debian/rules debian/control}}
Fix debian/rules (not required for me --[[User:Sascha|Sascha]] In fact bash tells me it's not even valid syntax --[[User:bewst|Dave]]):
{{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...

=== Active Protection System (Reduced Power Version) ===

We will need a patched kernel (see [[#Building a custom kernel]]), tp-smapi kernel modules >= 0.32 and hdapsd userspace daemon newer than 2007-05-24.

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.32-3_all.deb}}
{{cmduser|sudo dpkg -i tp-smapi-source_0.32-3_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.32-3+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}}

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

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

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

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

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

Installing Ubuntu 7.10 (Gutsy Gibbon) on a Thinkpad T60

2008-01-05T22:54:59Z

Dave abrahams: /* Active Protection System (Reduced Power Version) */

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

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

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

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

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

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

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

=== Building 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>}}
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]] In fact bash tells me it's not even valid syntax --[[User:bewst|Dave]]):
{{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...

=== Active Protection System (Reduced Power Version) ===

We will need a patched kernel (see [[#Building a custom kernel]]), tp-smapi kernel modules >= 0.32 and hdapsd userspace daemon newer than 2007-05-24.

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.32-3_all.deb}}
{{cmduser|sudo dpkg -i tp-smapi-source_0.32-3_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.32-3+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}}

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

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

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

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

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

Installing Ubuntu 7.10 (Gutsy Gibbon) on a Thinkpad T60

2008-01-05T21:53:09Z

Dave abrahams: /* Building a custom kernel */

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

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

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

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

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

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

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

=== Building 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>}}
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]] In fact bash tells me it's not even valid syntax --[[User:bewst|Dave]]):
{{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...

=== Active Protection System (Reduced Power Version) ===

We will need a patched kernel (see [[#Building a custom kernel]]), tp-smapi kernel modules >= 0.32 and hdapsd userspace daemon newer than 2007-05-24.

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.32-3_all.deb}}
{{cmduser|sudo dpkg -i tp-smapi-source_0.32-3_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.32-3+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}}

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

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

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

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

Installing Ubuntu 7.04 (Feisty Fawn) on a ThinkPad T60

2007-05-08T13:36:54Z

Dave abrahams: /* ATI Driver, Intel Pro Wireless, and Powernowd Suspend to RAM Fixes */

Ubuntu 7.04 Feisty Fawn is the current release and works fine on:
* T60 UT-049GE and 2007-72U.
* T60p

The installation worked without any problems. The new network manager is great as it now supports a useful roaming mode. The system includes the new Linux kernel 2.6.20 which provides almost perfect acpi functionality.

Most of the tips in the [[Installing Ubuntu 6.10 (Edgy Eft) on a ThinkPad T60|Ubuntu 6.10 Edgy Eft Guide]], like installing the ATI driver, apply to Feisty as well.

Feisty polishes up Thinkpad support for media buttons (acpi), and gives a much more usable machine immediately following installation than Edgy. This is a distribution to watch for Thinkpad users.

== ATI Driver, Intel Pro Wireless, and Powernowd Suspend to RAM Fixes ==

'''"Out of the box:"'''
*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.
*The Intel Pro Wireless 3945 wireless card will often stop working even after a successful suspend, requiring a restart.

=== Fixing Suspend to RAM ===

I'm assuming you have the optional Intel Pro Wireless; ignore the line that mentions ipw3945 if you don't have that wireless card.

#'''Disable powernowd during suspend'''
#:''These two edits will disable the powernowd when you suspend, and re-enable it when you 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>
#'''Edit /etc/acpi-support file to unload wireless module during suspend and disable video card warm boot'''
#:''These edits will fix the disappearing wireless card and the blank screen on resume problems.''
#:*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> so that your wireless card module won't disappear after you resume.
#:*Next, find the line <code>POST_VIDEO=true</code> and change it to <code>POST_VIDEO=false</code> to eliminate the blank-screen-resume problem.
#:*Save the file.

=== Tips for those dist-upgrading from Edgy ===

'''Repair fglrx to a working state:'''

If you have an ATI graphics card, now by default Mesa may be active despite your xorg.conf configuration in edgy.
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 you need to 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 you find this error 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 in your /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 (you only need it enabled for Compiz, which is not ready for feisty with ATI cards):

Section "Extensions"
Option "Composite" "0"
EndSection

'''Fix broken metacity window manager:'''

If you had installed a non-official compiz beta at some point, then you will have two disruptive settings files under your home directory.

<pre>
.gnomerc
.dmrc
</pre>

Have a look particularly 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 your system.
Just get rid of both files (see bug https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/104903 )

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

Installation instructions for the ThinkPad T60p

2007-05-08T13:27:50Z

Dave abrahams:

[[Category:T60p]]
Specific installation notes for the ThinkPad {{T60p}}.

'''Note:''' you may want to look at [[Installation_instructions_for_the_ThinkPad_T60]] as the two models have lots in common, especially if your distro/version don't appear here.

==Distribution-specific instructions==

=== Ubuntu / Kubuntu ===

*[[Installing_Ubuntu_6.06_Kubuntu_6.06_Gentoo_2006.0_on_a_ThinkPad_T60p|Ubuntu and Kubuntu 6.06 Dapper Drake]]

=== Red Hat Enterprise Linux / CentOS ===

*{{Install |Red Hat Enterprise Linux| 4| T60p}}

===Red Hat Fedora Core===
No articles so far.

=== Gentoo ===

*[[Installing_Ubuntu_6.06_Kubuntu_6.06_Gentoo_2006.0_on_a_ThinkPad_T60p|Gentoo 2006.0]]

Installing Ubuntu 7.04 (Feisty Fawn) on a ThinkPad T60

2007-05-08T13:00:11Z

Dave abrahams: /* ATI Driver, Intel Pro Wireless, and Powernowd Suspend to RAM Fixes */

Ubuntu 7.04 Feisty Fawn is the current release and works fine on:
* T60 UT-049GE and 2007-72U.
* T60p

The installation worked without any problems. The new network manager is great as it now supports a useful roaming mode. The system includes the new Linux kernel 2.6.20 which provides almost perfect acpi functionality.

Most of the tips in the [[Installing Ubuntu 6.10 (Edgy Eft) on a ThinkPad T60|Ubuntu 6.10 Edgy Eft Guide]], like installing the ATI driver, apply to Feisty as well.

Feisty polishes up Thinkpad support for media buttons (acpi), and gives a much more usable machine immediately following installation than Edgy. This is a distribution to watch for Thinkpad users.

== ATI Driver, Intel Pro Wireless, and Powernowd Suspend to RAM Fixes ==

'''"Out of the box:"'''
*Suspend to RAM fails during suspend, leaving the moon blinking indefinitely.
*The Ubuntu apt-installed fglrx packages give 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. [''Actually the version in Feisty is now 8.34.8. I'm not sure if that has the same problems'' --[[User:Dave abrahams|Dave abrahams]] 15:00, 8 May 2007 (CEST)]
*The Intel Pro Wireless 3945 wireless card will often stop working even after a successful suspend, requiring a restart.

=== Fixing Suspend to RAM ===

I'm assuming you have the optional Intel Pro Wireless; ignore the line that mentions ipw3945 if you don't have that wireless card.

#'''Disable powernowd during suspend'''
#:''These two edits will disable the powernowd when you suspend, and re-enable it when you 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>
#'''Edit /etc/acpi-support file to unload wireless module during suspend and disable video card warm boot'''
#:''These edits will fix the disappearing wireless card and the blank screen on resume problems.''
#:*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> so that your wireless card module won't disappear after you resume.
#:*Next, find the line <code>POST_VIDEO=true</code> and change it to <code>POST_VIDEO=false</code> to eliminate the blank-screen-resume problem.
#:*Save the file.

=== Tips for those dist-upgrading from Edgy ===

'''Repair fglrx to a working state:'''

If you have an ATI graphics card, now by default Mesa may be active despite your xorg.conf configuration in edgy.
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 you need to 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 you find this error 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 in your /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 (you only need it enabled for Compiz, which is not ready for feisty with ATI cards):

Section "Extensions"
Option "Composite" "0"
EndSection

'''Fix broken metacity window manager:'''

If you had installed a non-official compiz beta at some point, then you will have two disruptive settings files under your home directory.

<pre>
.gnomerc
.dmrc
</pre>

Have a look particularly 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 your system.
Just get rid of both files (see bug https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/104903 )

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

Talk:ThinkPad Advanced Mini-Dock

2007-04-25T15:20:14Z

Dave abrahams:

Talk:ThinkPad Advanced Mini-Dock

2007-04-25T15:17:54Z

Dave abrahams: /* Mini-dock power problem */

ATI Mobility FireGL V5200

2007-04-19T11:32:25Z