ThinkWiki - User contributions [en]

How to reduce power consumption

2007-10-10T17:57:29Z

Mrunge: /* External resources */ + www.lesswatts.org

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

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

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

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

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

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

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

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

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

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

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

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

==Kernel settings and patches==

===General settings===
The 2.6.21 kernel brought some very effective changes (like dynticks). If
it's not already on your distribution and you value power efficiency, you
may think about compiling it (or a more recent one) yourself.

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

<code>
# From PowerTOP's FAQ:
CONFIG_NO_HZ
CONFIG_HIGH_RES_TIMERS
CONFIG_HPET
CONFIG_CPU_FREQ_GOV_ONDEMAND
CONFIG_USB_SUSPEND
CONFIG_SND_AC97_POWER_SAVE
CONFIG_TIMER_STATS
CONFIG_ACPI_BATTERY
CONFIG_CPU_FREQ_STAT
# Not from the PowerTOP FAQ:
CONFIG_BLK_DEV_IO_TRACE
CONFIG_X86_ACPI_CPUFREQ
CONFIG_X86_SPEEDSTEP_CENTRINO
CONFIG_X86_SPEEDSTEP_ICH
CONFIG_X86_SPEEDSTEP_SMI
CONFIG_X86_ACPI_CPUFREQ
</code>

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

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

===Useful Patchs===

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

Kristen Carlson Accardi from Intel has a patchset to turn on "Aggressive
Link Power Management" (ALPM) for the AHCI driver (for SATA bus). See:
http://www.kernel.org/pub/linux/kernel/people/kristen/patches/SATA/alpm/

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

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

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

The "link_power_management_policy" tunable won't be available unless you
run Kirsten patchset, have an Intel AHCI compatible chipset, and use SATA drives.

<code>
echo 5 > /proc/sys/vm/laptop_mode
echo 0 > /proc/sys/kernel/nmi_watchdog
echo Y > /sys/module/snd_ac97_codec/parameters/power_save
echo 1 > /sys/devices/system/cpu/sched_mc_power_savings
echo ondemand > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
echo min_power > /sys/class/scsi_host/host0/link_power_management_policy
echo min_power > /sys/class/scsi_host/host1/link_power_management_policy
echo 1500 > /proc/sys/vm/dirty_writeback_centisecs
</code>

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

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

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

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

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

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

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

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

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

Some power saving hard drives features can be activated with hdparm.
For more details look at [[How to make use of Power Management features]] :

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

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

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

The hald daemon polling tends to maintain the ATA buses out of power saving
modes, and to wakeup CDROM drive. If you have a recent hald version, you
can stop this polling when on battery:

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

If your hald is not recent enough, consider stopping it on battery.

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

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

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

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

<code>
Option "NoDRI"
</code>

Also be sure that DPMS is working: <code>grep DPMS /var/log/Xorg.0.log</code>
should output "DPMS enabled". If not, put <code>Option "DPMS"</code> in your config.

On recent xrandr/xorg versions, you can disable the TV output when you're
not using it (it's known to consume power) :

<code>
xrandr --output TV -off
</code>

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

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

==USB Subsystem==
The kernel support an efficient USB 2.0 power saving feature if you enabled
CONFIG_USB_SUSPEND. This may not trigger in when you have an USB device
plugged (and beside, USB devices tends to suck power on their own), so avoid
using such devices when on battery.

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

<code>
rmmod uhci_hcd
</code>

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

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

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

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

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

Seel also [[How to enable AC97 power saving]].

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

<code>
echo 1 > /sys/bus/pci/drivers/ipw*/*/rf_kill
</code>

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

<code>
iwpriv eth1 set_power 5
</code>

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

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

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

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

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

Forcing 100Mbps full-duplex speed on a gigabit ethernet NIC can also save
a lot of power (~1W) on most network workloads.

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

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

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

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

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

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

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

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

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

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

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

Script for toggling bluetooth

2007-05-07T12:26:47Z

Mrunge: First version, ideas

The following code snipped may be useful to enable/disable bluetooth functionality on a thinkpad.

#!/bin/bash
INFO=/proc/acpi/ibm/bluetooth
STATE=`cat $INFO | grep status| awk '{print $2}'`
case "$STATE" in
enabled)
echo -n "disable" > $INFO
;;
disabled)
echo "enable" -n > $INFO
;;
*)
echo "usage: disable, enable"
esac

=== Further extensions ===
Using Windows the Fn-F5 buttons allows to switch on/off WLAN and bluetooth also. In the future the following features will be added
* include WLAN in switching
* show status on screen
[[Category:Scripts]]
[[Category:Bluetooth]]

How to disable the pc speaker (beep!)

2007-03-03T14:08:52Z

Mrunge: inputrc and beeps

Get rid of the annoying beeps in Linux (Xubuntu 6.10 Edgy Eft): Remove the pc speaker module "pcspkr".

Open a terminal and issue this command as root:
rmmod pcspkr

To prevent the "pcspkr" module from loading again at startup, open /etc/modprobe.d/blacklist with your favorite text editor (as root) and add following lines to the end of the file:
# disable the **** pc speaker
blacklist pcspkr

Another solution is to disable console beeps in /etc/inputrc (change with your favourite editor, should work on all distributions)
# do not bell on tab-completion
set bell-style none

==Re-enabling the pc speaker==
Temporarily activate it by loading the module (run this from a terminal with root privileges):
modprobe pcspkr

If you don't want to prevent the module from loading during startup, delete the lines from /etc/modprobe.d/blacklist described in the previous section.

Swsusp

2007-02-18T20:11:04Z

Mrunge: /* Model-specific Status */ +T43

{| width="100%"
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__
|style="vertical-align:top" |
===Software Suspend - swsusp===
Software Suspend (<tt>swsusp</tt>) is a suspend-to-disk implementation included in the 2.6 kernel series. See [[Software Suspend 2]] for an alternative implementation, which has some advantages.

Note that swsusp is not needed for suspend-to-RAM functionality.
|}

==Kernel configuration==
To enable software suspend change your kernel config as follows:
:{{kernelconf|CONFIG_PM|<*>|Power management support|Power management options|||}}
:{{kernelconf|CONFIG_SOFTWARE_SUSPEND|<*>|Software Suspend|Power management options|||}}
:{{kernelconf|CONFIG_PM_STD_PARTITION|[/dev/resume_partition]|Default resume partition|Power management options|||}}
<tt>/dev/resume_partition</tt> needs to be replaced by the swap partition you want to use for suspending. (Use {{cmdroot|fdisk -l /dev/hda}} if unsure.)

You can override the default resume partition anytime by giving {{bootparm|resume|/dev/resume_partition}} as kernel boot parameter.
Also, in case you suspended, but want to boot up normally (without resuming from the saved image - losing all data that was unsaved at suspend time), you can give the {{bootparm|noresume|}} kernel boot parameter.

{{NOTE|For some people suspending did not work if <tt>resume_partition</tt> was specified in the kernel config. In such case specify the resume partition as a kernel parameter instead.}}

{{NOTE|When using Debian Etch or Sid, you need to use <tt>initramfs-tools</tt> as yaird is currently (2006-05-18) not supporting swsusp. See [http://wiki.debian.org/InitrdReplacementOptions the Debian Wiki] for more details.}}

==Suspending==
To suspend you can either do a simple {{cmdroot|echo disk > /sys/power/state}} (recommended) or use the [http://softwaresuspend.berlios.de/old-site/swsusp/sysvinit-2.76-v2-for_swsusp-v5.tar.gz patched SysVInit] and call {{cmdroot|swsusp}} or {{cmdroot|shutdown -z now}}. As the {{path|/proc/acpi/sleep}} interface becomes deprecated in newer kernels you should NOT use the old {{cmdroot|echo -n 4 > /proc/acpi/sleep}} anymore.

Ideally, you would do this from a script like {{path|/etc/acpi/actions/hibernate.sh}}. It has proven to be a good idea to shutdown the following processes/drivers within the script before you do the actual suspend:
*any running mysql server
*the linuxant driver may require to be stopped as well ({{cmdroot|dldrstop}} does the trick).

Afterwards you might want to enable them again, as well as run a script that does necessary configurations according to the ac power state.
Furthermore, the system clock is not readjusted automatically, so you will probably also want the do that from that script (i.e. by restarting your systemclock bootup script).

If the sound output is silent after resume, the following commands might help to get sound to work again without reloading any modules:
amixer set Master mute >/dev/null 2>&1
amixer set PCM mute >/dev/null 2>&1
amixer set Master unmute >/dev/null 2>&1
amixer set PCM unmute >/dev/null 2>&1

==S5 vs. S4 state==
Finally you should take note that swsusp does not set the ACPI S4 state. Instead it goes to S5. This means that the machine itself doesn't know that it was suspend rather than shutdown. Hence you can i.e. boot a parallel installed other operating system and resume your linux session later, as long as you don't touch the swap partition the image was saved to.

==Model-specific Status==

{| align="center" cellpadding="2" width="100%" style="border:1px; background:grey;"
! style="background:#efefef;"| Thinkpad Model
! style="background:#efefef;"| Type
! style="background:#efefef;"| Operating System
! style="background:#efefef;"| Kernel Version
! style="background:#efefef;"| swsusp works
! style="background:#efefef;"| Note
|- style="background: white;"

|- style="background: white; color:black;"
|{{X60s}}
| 1702-55G
| Arch Linux
| 2.6.20
! style ="color:green;"| yes
|
|- style="background: white; color:black;"

|- style="background: white; color:black;"
|{{X60s}}
| 1702-5FG
| Debian Etch
| 2.6.18 with [[User:Profilek | Forest Zhao's AHCI patches]]
! style ="color:green;"| yes
|
|- style="background: white; color:black;"

|- style="background: white; color:black;"
|{{X60s}}
| 1702-5FG
| Debian Etch
| 2.6.19.2
! style ="color:green;"| yes
|
|- style="background: white; color:black;"

|{{R52}}
| 18299MG
| Debian sarge
| 2.6.17.9
! style ="color:green;"| yes
|

|- style="background: white; color:black;"
|{{T43}}
| 2668-74G
| [[:Category:Fedora|Fedora Core 6]]
| 2.6.19
! style ="color:green;"| yes
|
|}

Installing Fedora Core 6 on a ThinkPad T60

2006-11-08T07:33:00Z

Mrunge: +Cat, livna does not support mixing repositories!

== Installation ==

Installation of Fedora Core 6 (Zod) on a Thinkpad T60 (2623). The installation completes successfully but installs the i586 kernel instead of the required i686 kernel. The wrong kernel is due to a [https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=211941 known bug] in the Anaconda installer.

As of 11/06, most things are working well. There are still a few issues related to the proprietary ATi driver that still need to be ironed out. Stay tuned for updates.

== Works Out of the Box ==

; Dual Cores (SMP processing)
: As of Kernel 2.6.18, used in Fedora Core 6, there is no loger a single cpu and smp kernel image. SMP is now configured on-the-fly. FC6's kernel will automatically discover the T60's dual core cpu and bring up CPU0 and CPU1.

; Wired Networking
: Kernel recognizes eth0 and correctly loads the e1000 driver.

; Video at 1400x1050
: Fedora does not ship the proprietary ATi driver, as a reult the VESA driver is used. Installation of the ATi fgrlx driver is described later in this article.

; Touchpad / Mouse

; Sound
: The first-boot sound test fails to play the test sound. However, sound support is correctly configured and the snd-hda-intel driver is loaded at startup.

; Suspend to RAM
: Works out of the box under Gnome. Gnome power management intregrates with HAL (Linux's hardware abstraction layer) and DBUS, which correctly put this computer into a suspsend to RAM state and wake it up correctly.

== Requires Tweaking ==

* Wireless Networking (Requires ipw3945 driver)
* ATi OpenGL Direct Rendering
* Suspend to Disk / Hibernate

== Post Install ==

=== Getting Up to Date ===

Before completing installation, it's best to get up to date by running yum update as root or by using the new graphical updater, Pup, that ships with Fedora Core 6. After all updates are installed, reboot before continuing the post-install tasks.

=== Replacing the Kernel ===

As previously mentioned, the i586 kernel is installed on this machine instead of the i686 version. The i686 version is required to install the ATI video drivers and Intel Wireless drivers required to get this machine 100% operational.

Installing the new kernel can be done by various methods as documented on the [https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=211941 Red Hat Bugzilla bug]. However, the safest method is to use [[yum]] to do the kernel swap.

To swap kernels:
# Open up a terminal window are become root.
# Execute: yum remove kernel
# Make note of any other packages that will be removed due to dependency issues. The packages will have to be reinstalled in the next step.
# Install the kernel.i686 package and any other packages removed in the previous step.
# Fix your [[Grub]] configuration
# Reboot

On a minimal install, the only dependencies removed were gnome-session, compiz, gnome-volume-manager, and pcmciautils. Getting things back on track required:

# yum install kernel.i686 gnome-session compiz gnome-volume-manager pcmciautils

After [Yum] completes, you will have to fix the boot loader or you will be unable to boot after a restart.

Again as root, fire up your favorite text editor and add the following lines to your grub configuration (/boot/grub/grub.conf) just below the initial comments:

<pre>
title FC6 2.6.18-1.2798
kernel /vmlinuz-2.6.18-1.2798.fc6 ro root=LABEL=/ rhgb quiet
initrd /initrd-2.6.18-1.2798.fc6.img
</pre>

=== Setting Up Additional Repositories ===

In order to get the ATI driver and the Intel Wireless working, you will need to add two repositories to your computer; [http://rpm.livna.org/ Livna RPMs] and [http://atrpms.net/ AT-RPMs] repositories to your machine.
* AFAIK livna does not support mixing its repository with other sources than Fedora Core and Fedora Extras, so try adding software just from one repo.

; Enabling Livna's Repository
: As root, rpm -ivh http://rpm.livna.org/livna-release-6.rpm .

; Enabling AT-RPMs Repository
: As root, use your favorite editor to create /etc/yum.repos.d/atrpms.repo and type in:
<pre>
[atrpms]
name=Fedora Core $releasever - $basearch - ATrpms
baseurl=http://dl.atrpms.net/fc$releasever-$basearch/atrpms/stable
gpgkey=http://ATrpms.net/RPM-GPG-KEY.atrpms
gpgcheck=1
</pre>

== ATI Video Driver ==

I still haven't gotten this working. While the driver installs, X fails to use direct Open GL rendering. There appears to be a problem with the fglrx driver not supporting composite rendering used be default in Fedora Core 6.

Stay tuned for the fix once I get it working.

== Wireless Networking ==

To use the T60's built in wireless networking driver, you will need to install ipw3945 driver. The AT-RPMs repository, mentioned earlier in this article, provides the necessary packages. As root:

# yum install ipw3945d ipw3945-ucode ipw3945-kmdl-2.6.18-1.2798.fc6.i686

Once installed, you must add a startup script to have ipw3945d started at boot. Create the following script in a file named /etc/init.d/ipw3945d
<pre>
#! /bin/bash
#
# ipw3490d Load / unload Intel ipw3490 daemon
#
# chkconfig: 2345 09 90
# description: Load / unload Intel ipw3490 daemon
#
### BEGIN INIT INFO
# Provides: ipw3490d
### END INIT INFO

# Source function library.
. /etc/init.d/functions

if [ ! -f /etc/sysconfig/network ]; then
exit 0
fi

case "$1" in
start)
echo -n "Starting ipw3945d: "
/sbin/ipw3945d > /dev/null 2>&1
echo
;;
stop)
echo -n "Stopping ipw3945d: "
killproc ipw3945d
echo
;;
status)
status ipw3945d
;;
restart)
cd "$CWD"
$0 stop
$0 start
;;
*)
echo $"Usage: $0 {start|stop|restart|status}"
exit 1
esac

exit 0
</pre>

Now, make it executable and add the script with chkconfig to be started on boot:

# chmod 750 /etc/init.d/ipw3945d
# chkconfig --add ipw3945d

Make sure things are setup correctly by running chkconfig --list ipw345d. Your output should look something like:

# chkconfig --list ipw3945d
ipw3945d 0:off 1:off 2:on 3:on 4:on 5:on 6:off

If everything looks okay, reboot. Once restarted you should be able to run <code>ifconfig eth1</code> and see information about your wireless card.

[[Category:Fedora]]

Installing Fedora Core 5 on a ThinkPad T43 (2686)

2006-05-13T20:18:06Z

Mrunge: /* Configuration */

== Convert the FAT filesystem to NTFS. ==
Booted Windows XP - let it run the conversion from FAT to NTFS. When that is finished, reboot again into Windows
# Get and install the Windows updates.
# Restore settings from old laptop Windows account using the file and settings transfer wizard.
# Configure the fingerprint scanner for login (did not try using it for powerup yet) because it's so cool.
# Make a set of Rescue and Recovery CDs (6).
# Run the filesystem defragger.

Reboot - press F1 to get to BIOS settings; adjust boot order to be just CD and then HD.

== Resize NTFS [1] ==
Boot Knoppix 4.0.2 CD.

Run qtparted
# select sda
# select the NTFS partition
# Action->Resize, set size to 15G
# File->Commit to run the resize and save.

Reboot back to Windows XP to check the filesystem. At boot, it wanted to run a filesystem check - let it run. (after booting, it wanted to reboot again because it thought some device had changed - went along with it).

== Install FC5 ==
I used a single install from the DVD image - boot the FC5 DVD:
# Check media (takes a while).
# Select customized partition layout
## Deleted the IBM recovery partition {{footnote|1}}
## Create partitions:

/boot ext3 100M (default)
swap 5G (I have 2G RAM)
/xpshare vfat 1G (to mount to both OSs)
/ ext3 remaining space

Proceed with normal installation (I chose Gnome desktop and did not install KDE; root will use Gnome, but I use Xfce).

This installed kernel 2.6.15-1.2054_FC5

== Post-Install Setup ==

Log in as root.

Run 'yum update' to get updates since DVD was made.

=== Configure X resolution for LCD ===
# Select menu "System->Administration->Display"
# Hardware tab choose Generic LCD Panel->LCD 1400x1050
# Settings tab set resolution to 1400x1050
# Log out and restart X w/ ctl-alt-backspace, log in again

=== Switch to postfix mta (my personal preference): ===
{{cmdroot|yum install postfix}}

{{cmdroot|alternative --config mta}}

select postfix instead of sendmail

=== CPU Frequency Scaling ===
Set the ondemand governor by adding the following to /etc/rc.local:
modprobe cpufreq_ondemand
echo "ondemand" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor

=== Thinkpad Buttons ===

Get support for various special keys and buttons (volume, screen brightness), by installing [[Tpb]]:

{{cmdroot|yum install tpb xosd}}

See [[How_to_get_special_keys_to_work#tpb_configuration]] for how to reconfigure keys.

=== Set up suspend and hibernate ===

'''No kernel recompile needed!'''

Create scripts in {{path|/etc/acpi/actions}}:

{{path|nighty-night.sh}} (things to do when entering a sleep mode):
#!/bin/sh
/usr/bin/dbus-send --system --dest=org.freedesktop.NetworkManager \
--type=method_call /org/freedesktop/NetworkManager \
org.freedesktop.NetworkManager.sleep
/sbin/hwclock --systohc

{{path|wakey-wakey.sh}} (things to do when waking up):
#!/bin/sh
/sbin/hwclock --hctosys
/usr/bin/dbus-send --system --dest=org.freedesktop.NetworkManager \
--type=method_call /org/freedesktop/NetworkManager \
org.freedesktop.NetworkManager.wake

{{path|sleep.sh}} (enter and then leave suspend-to-ram mode):
#!/bin/sh
/etc/acpi/actions/nighty-night.sh
echo -n mem > /sys/power/state
/etc/acpi/actions/wakey-wakey.sh

{{path|hibernate.sh}} (enter and then leave suspend-to-disk):
#!/bin/sh
/etc/acpi/actions/nighty-night.sh
echo -n disk > /sys/power/state
/etc/acpi/actions/wakey-wakey.sh

Set the lid switch to trigger sleep (suspend-to-ram) by creating the file {{path|/etc/acpi/events/lid.conf}}:
event=button[/]lid
action=/etc/acpi/actions/sleep.sh

Set the "Access IBM" button to be hibernate by editing {{path|/etc/tpbrc}} and setting:

THINKPAD /etc/acpi/actions/hibernate.sh

== Wireless LAN Config ==
Fedora Core 5 comes with Network Manager, a new software to manage connections via wired and wireless networks. It utilizes wpa_supplicant for access to wpa-secured networks. Sadly, there exist some bugs in wpa_supplicant and in supplied madwifi-modules in the livna-repository. The following configuration enables connection to wpa-secured networks and the utilization of NetworkManager.

=== Compile and install Madwifi-NG ===
Get madwifi sources from SVN. First check, if subversion is installed:
rpm -qa subversion

should print something like
subversion-1.3.1-2.1

Check out madwifi-ng from the repository:
svn checkout http://svn.madwifi.org/trunk madwifi-ng

Change into the madwifi directory. Build the software and install by typing
make && make install

I changed the directory of the tools to /usr rather than /usr/local. A modification of tools/Makefile managed that.

Insert into your /etc/modprobe.conf (if not existing)
alias ath0 ath_pci
options ath_pci autocreate=sta
For further options, please consult [[http://madwifi.org/wiki/UserDocs | Madwifi user docs]].

=== Compile and install wpa-supplicant ===
Download latest version of wpa-supplicant source code, e.g. 0.5.3. Cd to the corresponding directory. Create and edit a .config file using a text editor, e.g. vi.
CONFIG_DRIVER_MADWIFI=y
CFLAGS += -I/path/to/madwifi-ng
CONFIG_CTRL_IFACE=y
CONFIG_DRIVER_WEXT=y
CONFIG_CTRL_IFACE_DBUS=y

Build and install it. Be sure to use /usr/sbin as installation path.

=== Configuration ===
Be sure to start NetworkManager in runlevel 5.
chkconfig --level 345 NetworkManager on

Wpa_supplicant is started by NetworkManager, so don't start it at boot:
chkconfig --level 345 wpa_supplicant off

Get a network address via dhcp:
chkconfig --level 345 dhcdbd on

Edit /etc/sysconfig/wpa_supplicat to
# wlan0 and wifi0
# INTERFACES="-iwlan0 -iwifi0"
INTERFACES="-iath0"
# ndiswrapper and prism
# DRIVERS="-Dndiswrapper -Dprism"
DRIVERS="-Dmadwifi"

Thats it. Reboot or start services manually.

== ToDo: ==

* Install laptop-mode

* Configure multi-head X server

* Build the fingerprint reader software and integrate into login and ssh-agent, maybe using [[Script for enabling the fingerprint reader]]

{{footnotes|

# I chose to just remove the IBM Recovery Partition - essentially rendering the "Access IBM" button useless at boot time, in order to get the ~4G of disk space. This may have been a higher risk choice, since apparently if I ever need to reinstall Windows from the Recovery CDs I made, the only choice will be to recreate the factory disk layout, destroying my Linux installation. Life is full of choices. There are [[Pre-Installation_steps#Moving_the_Recovery_partition_using_a_Linux_rescue_system|instructions on an alternate method of doing the disk layout that retains the useful recovery partition and the "Access IBM" button]]; use them if 4G is less important to you than being able to restore Windows without touching Linux.

Update: According to [http://www.thinkwiki.org/wiki/Recovering_from_Recovery_CDs the wiki post on Recovering from Recovery CDs], "''Recovery deletes the first partition and then installs to the first block of contiguous free space (which could be bigger than the original first partition if there was free space after it). Later partitions are safe. The partition must be at least 8GB or so or else the recovery will either fail or produce a corrupt Windows installation. You can save a little space if you intervene during some of the IBM software installs, reduce the swap size and disable hibernation, but you have to time this carefully''." That means that if you used the Recovery CD's, it would ignore the linux partition (s) (although you'd probably need to deal with MBR issues).

}}

[[Category:T43]]

Installing Fedora Core 5 on a ThinkPad T43 (2686)

2006-05-13T20:17:43Z

Mrunge: /* Configuration */

Installing Fedora Core 5 on a ThinkPad T43 (2686)

2006-05-13T19:38:17Z

Mrunge: WLAN Config

== Convert the FAT filesystem to NTFS. ==
Booted Windows XP - let it run the conversion from FAT to NTFS. When that is finished, reboot again into Windows
# Get and install the Windows updates.
# Restore settings from old laptop Windows account using the file and settings transfer wizard.
# Configure the fingerprint scanner for login (did not try using it for powerup yet) because it's so cool.
# Make a set of Rescue and Recovery CDs (6).
# Run the filesystem defragger.

Reboot - press F1 to get to BIOS settings; adjust boot order to be just CD and then HD.

== Resize NTFS [1] ==
Boot Knoppix 4.0.2 CD.

Run qtparted
# select sda
# select the NTFS partition
# Action->Resize, set size to 15G
# File->Commit to run the resize and save.

Reboot back to Windows XP to check the filesystem. At boot, it wanted to run a filesystem check - let it run. (after booting, it wanted to reboot again because it thought some device had changed - went along with it).

== Install FC5 ==
I used a single install from the DVD image - boot the FC5 DVD:
# Check media (takes a while).
# Select customized partition layout
## Deleted the IBM recovery partition {{footnote|1}}
## Create partitions:

/boot ext3 100M (default)
swap 5G (I have 2G RAM)
/xpshare vfat 1G (to mount to both OSs)
/ ext3 remaining space

Proceed with normal installation (I chose Gnome desktop and did not install KDE; root will use Gnome, but I use Xfce).

This installed kernel 2.6.15-1.2054_FC5

== Post-Install Setup ==

Log in as root.

Run 'yum update' to get updates since DVD was made.

=== Configure X resolution for LCD ===
# Select menu "System->Administration->Display"
# Hardware tab choose Generic LCD Panel->LCD 1400x1050
# Settings tab set resolution to 1400x1050
# Log out and restart X w/ ctl-alt-backspace, log in again

=== Switch to postfix mta (my personal preference): ===
{{cmdroot|yum install postfix}}

{{cmdroot|alternative --config mta}}

select postfix instead of sendmail

=== CPU Frequency Scaling ===
Set the ondemand governor by adding the following to /etc/rc.local:
modprobe cpufreq_ondemand
echo "ondemand" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor

=== Thinkpad Buttons ===

Get support for various special keys and buttons (volume, screen brightness), by installing [[Tpb]]:

{{cmdroot|yum install tpb xosd}}

See [[How_to_get_special_keys_to_work#tpb_configuration]] for how to reconfigure keys.

=== Set up suspend and hibernate ===

'''No kernel recompile needed!'''

Create scripts in {{path|/etc/acpi/actions}}:

{{path|nighty-night.sh}} (things to do when entering a sleep mode):
#!/bin/sh
/usr/bin/dbus-send --system --dest=org.freedesktop.NetworkManager \
--type=method_call /org/freedesktop/NetworkManager \
org.freedesktop.NetworkManager.sleep
/sbin/hwclock --systohc

{{path|wakey-wakey.sh}} (things to do when waking up):
#!/bin/sh
/sbin/hwclock --hctosys
/usr/bin/dbus-send --system --dest=org.freedesktop.NetworkManager \
--type=method_call /org/freedesktop/NetworkManager \
org.freedesktop.NetworkManager.wake

{{path|sleep.sh}} (enter and then leave suspend-to-ram mode):
#!/bin/sh
/etc/acpi/actions/nighty-night.sh
echo -n mem > /sys/power/state
/etc/acpi/actions/wakey-wakey.sh

{{path|hibernate.sh}} (enter and then leave suspend-to-disk):
#!/bin/sh
/etc/acpi/actions/nighty-night.sh
echo -n disk > /sys/power/state
/etc/acpi/actions/wakey-wakey.sh

Set the lid switch to trigger sleep (suspend-to-ram) by creating the file {{path|/etc/acpi/events/lid.conf}}:
event=button[/]lid
action=/etc/acpi/actions/sleep.sh

Set the "Access IBM" button to be hibernate by editing {{path|/etc/tpbrc}} and setting:

THINKPAD /etc/acpi/actions/hibernate.sh

== Wireless LAN Config ==
Fedora Core 5 comes with Network Manager, a new software to manage connections via wired and wireless networks. It utilizes wpa_supplicant for access to wpa-secured networks. Sadly, there exist some bugs in wpa_supplicant and in supplied madwifi-modules in the livna-repository. The following configuration enables connection to wpa-secured networks and the utilization of NetworkManager.

=== Compile and install Madwifi-NG ===
Get madwifi sources from SVN. First check, if subversion is installed:
rpm -qa subversion

should print something like
subversion-1.3.1-2.1

Check out madwifi-ng from the repository:
svn checkout http://svn.madwifi.org/trunk madwifi-ng

Change into the madwifi directory. Build the software and install by typing
make && make install

I changed the directory of the tools to /usr rather than /usr/local. A modification of tools/Makefile managed that.

Insert into your /etc/modprobe.conf (if not existing)
alias ath0 ath_pci
options ath_pci autocreate=sta
For further options, please consult [[http://madwifi.org/wiki/UserDocs | Madwifi user docs]].

=== Compile and install wpa-supplicant ===
Download latest version of wpa-supplicant source code, e.g. 0.5.3. Cd to the corresponding directory. Create and edit a .config file using a text editor, e.g. vi.
CONFIG_DRIVER_MADWIFI=y
CFLAGS += -I/path/to/madwifi-ng
CONFIG_CTRL_IFACE=y
CONFIG_DRIVER_WEXT=y
CONFIG_CTRL_IFACE_DBUS=y

Build and install it. Be sure to use /usr/sbin as installation path.

=== Configuration ===
Be sure to start NetworkManager in runlevel 5.
chkconfig --level 345 NetworkManager on

Wpa_supplicant is started by NetworkManager, so don't start it at boot:
chkconfig --level 345 wpa_supplicant off

Get a network address via dhcp:
chkconfig --level 345 dhcdbd on

Thats it. Reboot or start services manually.

== ToDo: ==

* Install laptop-mode

* Configure multi-head X server

* Build the fingerprint reader software and integrate into login and ssh-agent

{{footnotes|

# I chose to just remove the IBM Recovery Partition - essentially rendering the "Access IBM" button useless at boot time, in order to get the ~4G of disk space. This may have been a higher risk choice, since apparently if I ever need to reinstall Windows from the Recovery CDs I made, the only choice will be to recreate the factory disk layout, destroying my Linux installation. Life is full of choices. There are [[Pre-Installation_steps#Moving_the_Recovery_partition_using_a_Linux_rescue_system|instructions on an alternate method of doing the disk layout that retains the useful recovery partition and the "Access IBM" button]]; use them if 4G is less important to you than being able to restore Windows without touching Linux.

Update: According to [http://www.thinkwiki.org/wiki/Recovering_from_Recovery_CDs the wiki post on Recovering from Recovery CDs], "''Recovery deletes the first partition and then installs to the first block of contiguous free space (which could be bigger than the original first partition if there was free space after it). Later partitions are safe. The partition must be at least 8GB or so or else the recovery will either fail or produce a corrupt Windows installation. You can save a little space if you intervene during some of the IBM software installs, reduce the swap size and disable hibernation, but you have to time this carefully''." That means that if you used the Recovery CD's, it would ignore the linux partition (s) (although you'd probably need to deal with MBR issues).

}}

[[Category:T43]]

How to make ACPI work

2006-01-25T09:01:51Z

Mrunge: /* Suspend to RAM (Sleep) */

==general==
===Kernel configuration===
First of all you'll have to enable ACPI support in your kernel (if your distro doesn't already have an ACPI enabled kernel).
To do this open your kernel config and enable ACPI Power Management:
:{{kernelconf|CONFIG_PM|<*>|Power Management support|Power management options|||}}
:{{kernelconf|CONFIG_ACPI_SLEEP|<*>|ACPI|Power management options|||}}

You'd most likely want to enable the following ACPI options:
:{{kernelconf|CONFIG_ACPI_SLEEP|<*>|Sleep States|ACPI|Power management options||}}
:{{kernelconf|CONFIG_ACPI_AC|<*>|AC Adapter|ACPI|Power management options||}}
:{{kernelconf|CONFIG_ACPI_BATTERY|<*>|Battery|ACPI|Power management options||}}
:{{kernelconf|CONFIG_ACPI_FAN|<*>|Fan|ACPI|Power management options||}}
:{{kernelconf|CONFIG_ACPI_PROCESSOR|<*>|Processor|ACPI|Power management options||}}
:{{kernelconf|CONFIG_ACPI_THERMAL|<*>|Thermal Zone|ACPI|Power management options||}}

If you prefer editing your {{path|.config}} file directly, you should set at least the following variables:
CONFIG_PM=y
CONFIG_ACPI_BOOT=y
CONFIG_ACPI_INTERPRETER=y
CONFIG_ACPI_SLEEP=y
CONFIG_ACPI_SLEEP_PROC_FS=y
CONFIG_ACPI_AC=y
CONFIG_ACPI_BATTERY=y
CONFIG_ACPI_BUTTON=y
CONFIG_ACPI_FAN=y
CONFIG_ACPI_PROCESSOR=y
CONFIG_ACPI_THERMAL=y
CONFIG_ACPI_BUS=y
CONFIG_ACPI_EC=y
CONFIG_ACPI_POWER=y
CONFIG_ACPI_PCI=y
CONFIG_ACPI_SYSTEM=y

Then recompile your kernel.

===IBM specific ACPI driver===
Unfortunately, special drivers for ACPI on ThinkPads were not included with kernels prior 2.6.10. So you'll have to compile one yourself or get it as precompiled module for your kernel.

You have the choice between [[thinkpad-acpi]] and [[ibm-acpi]], with the latter being the recommended one.

If you use a post-2.6.10 kernel and you want to use [[ibm-acpi]], it is recommended to look on its projects page for a possibly newer version.

{{HINT|In general it is a good idea to read the README included with the driver.}}

===ACPI daemon===
Also you'll need to install [[acpid]], if it isn't present on your system. [[acpid]] is a daemon that handles the ACPI events generated by the system. Read [[How to configure acpid]].

==Screen blanking (Standby)==
Make sure you have
Option "DPMS"
in the Monitor section of your {{path|/etc/X11/XF86Config}} or {{path|/etc/X11/xorg.conf}}.

Running {{cmduser|xset +dpms}} and then {{cmduser|xset dpms force off}} will turn off the backlight on a laptop screen.<br />

Note that this may not work in combination with {{cmduser|echo -n "mem" > /sys/power/state}} because switching to console causes the backlight to come back on before sleeping.

==Suspend to RAM (Sleep)==
ACPI Sleep/suspend-to-ram with recent 2.6.x kernels usually works fine. Have a look at the [[How to configure acpid|acpid configuration HOWTO]]. It includes a specific example for going to sleep on lid close.

The following glitches may or may not occur in relation to suspending to RAM:
* 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.
* When resuming from a suspend-to-ram the display might remain black or might only show the pre-suspend output (the system is still rebootable via {{key|ctrl}}{{key|alt}}{{key|del}}). Look [[Problem with display remaining black after resume|here]] for solutions.
* 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.
* Also, you might want to take note of the [[Problem with high power drain in ACPI sleep]].
* 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.
* If you're running MySQL, sleep may also not work, so stop MySQL first, then sleep. Remember to restart MySQL when you wakeup.
* Problems with the serial port of the port replicator after the wake up from ram have also been experienced.
* Crash on resume
** ...when using ATI proprietary drivers can be solved by using [http://freshmeat.net/projects/vbetool/ vbetool]. Note that this is no longer necessary with recent revisions of the ATI proprietary driver.
** ...might be solved by disabling ''APIC'' (@Processor type and features) in the kernel configuration
** ...when using Savage chipset, might be solved by disabling savagefb (or compiling as a module) in favor of vesafb
* Due to the fact that Sonoma chipset based laptops ({{R52}}, {{T43}}, {{T43p}}, {{X41}}, {{X41T}}) utilize the SATA layer for disk access and SATA does not have power-management support yet Suspend to RAM does not work on these machines. See the [[Problems with SATA and Linux#Hang on resume from suspend to RAM|according section]] on the [[Problems with SATA and Linux]] page.

* There is a known Problem regarding battery info after suspend to RAM. A small patch exists for kernels 2.6.1[4|5] http://www.ussg.iu.edu/hypermail/linux/kernel/0511.0/2429.html

==Suspend to disk (Hibernate)==
There are two drivers for this available:
* swsusp, which is in the kernel and
* [http://developer.berlios.de/projects/softwaresuspend/ SoftwareSuspend2] which is more feature rich, but not yet in the kernel, so you have to patch it in yourself
Both are reported to work fine as long as you use open-source graphic drivers. A comparison of the features can be found on [http://softwaresuspend.berlios.de/features.html this page].

Just in case you are in doubt...yes, it is safe in both cases to use the same swap partition as active swap and as suspend partition.

===using swsusp===
Software Suspend (swsusp) is included in the 2.6 kernel series. It seems like no patches for 2.4 kernels are available.

To enable software suspend change your kernel config as follows:
:{{kernelconf|CONFIG_PM|<*>|Power management support|Power management options|||}}
:{{kernelconf|CONFIG_SOFTWARE_SUSPEND|<*>|Software Suspend|Power management options|||}}
:{{kernelconf|CONFIG_PM_STD_PARTITION|[/dev/resume_partition]|Default resume partition|Power management options|||}}

<tt>/dev/resume_partition</tt> needs to be replaced by the swap partition you want to use for suspending. (Use {{cmdroot|fdisk -l /dev/hda}} if unsure.)

You can override the default resume partition anytime by giving {{bootparm|resume|/dev/resume_partition}} as kernel boot parameter.
Also, in case you suspended, but want to boot up normally (without resuming from the saved image - losing all data that was unsaved at suspend time), you can give the {{bootparm|noresume|}} kernel boot parameter.

{{NOTE|For some people suspending did not work if resume_partition was specified in the kernel config. In such case specify the resume partition as a kernel parameter instead.}}

To suspend you can either do a simple {{cmdroot|echo disk > /sys/power/state}} (recommended) or use the [http://softwaresuspend.berlios.de/old-site/swsusp/sysvinit-2.76-v2-for_swsusp-v5.tar.gz patched SysVInit] and call {{cmdroot|swsusp}} or {{cmdroot|shutdown -z now}}. As the {{path|/proc/acpi/sleep}} interface becomes deprecated in newer kernels you should NOT use the old {{cmdroot|echo -n 4 > /proc/acpi/sleep}} anymore.

Ideally you would do this from a script like {{path|/etc/acpi/actions/hibernate.sh}}. It has proven to be a good idea to shutdown the following processes/drivers within the script before you do the actual suspend.
*any running mysql server
*the linuxant driver may require stopping in a acpi script as well. {{cmdroot|dldrstop}} does the trick.

Afterwards you might want to enable them again, as well as run a script that does necessary configurations according to the ac power state.
Furthermore, the system clock is not readjusted automatically, so you will probably also want the do that from that script (i.e. by restarting your systemclock bootup script).

If the sound output is silent after resume, these commands might help to get sound to work again without reloading any modules:

amixer set Master mute >/dev/null 2>&1
amixer set PCM mute >/dev/null 2>&1
amixer set Master unmute >/dev/null 2>&1
amixer set PCM unmute >/dev/null 2>&1

Finally you should take note that swsusp does not set the ACPI S4 state. Instead it goes to S5. This means that the machine itself doesn't know that it was suspend rather than shutdown. Hence you can i.e. boot a parallel installed other operating system and resume your linux session later, as long as you don't touch the swap partition the image was saved to.

===using SoftwareSuspend2===
First apply Software Suspend 2 patches from http://www.suspend2.net if they are not already in your kernel.

Be sure to also read the http://www.suspend2.net/HOWTO.html

These are the options for the kernel. Make sure to change the <tt>/dev/resume_partition</tt> to your swap partition, i.e. <tt>/dev/hda5</tt>.

# Software Suspend 2
CONFIG_SOFTWARE_SUSPEND2=y
CONFIG_SOFTWARE_SUSPEND2_BUILTIN=y
CONFIG_SOFTWARE_SUSPEND_SWAPWRITER=y
CONFIG_SOFTWARE_SUSPEND_LZF_COMPRESSION=y
CONFIG_SOFTWARE_SUSPEND_TEXT_MODE=y
CONFIG_SOFTWARE_SUSPEND_DEFAULT_RESUME2="/dev/resume_partition"
# CONFIG_SOFTWARE_SUSPEND_KEEP_IMAGE is not set
CONFIG_SOFTWARE_SUSPEND_CHECK_RESUME_SAFE=y
# CONFIG_SOFTWARE_SUSPEND_DEBUG is not set
# CONFIG_SOFTWARE_SUSPEND_DEVELOPER is not set

Next, compile and install the kernel.

In the meantime, add the following to the kernel parameters: {{bootparm|resume2|swap:/dev/resume_partition}}. Again change <tt>/dev/resume_partition</tt> to your swap partition.

Install the hibernation script:
*For {{Gentoo}} users: emerge hibernate-script<br />
*For {{Fedora}} users: kernel and hibernate RPMs are available at http://mhensler.de/swsusp/<br />
*For all other users, check the home page for packages (deb, i386 rpm, tgz, and source rpm) from http://www.suspend2.net
*{{Debian}} users using initrd image, make sure you copy [http://dagobah.ucc.asn.au/swsusp/2.0.0.102/swsusp-initrd.sh swsusp-initrd.sh] script to your {{path|/etc/mkinitrd/scripts}} directory before creating initrd image.

Restart using the new kernel and run the script to test it: {{cmdroot|/usr/sbin/hibernate}}

==ThinkPads on which it is recommended to use ACPI==
*ThinkPad {{770X}}, {{770Z}}
*ThinkPad {{A20m}}, {{A20p}}, {{A20m}}, {{A20p}}, {{A21e}}, {{A21m}}, {{A21p}}, {{A22e}}, {{A22m}}, {{A22p}}, {{A30}}, {{A30p}}, {{A31}}, {{A31p}}
*ThinkPad {{G40}}, {{G41}}
*ThinkPad {{R30}}, {{R31}}, {{R32}}, {{R40}}, {{R40e}}, {{R50}}, {{R50e}}, {{R50p}}, {{R51}}, {{R52}}
*ThinkPad {{T20}}, {{T21}}, {{T22}}, {{T23}}, {{T30}}, {{T40}}, {{T40p}}, {{T41}}, {{T41p}}, {{T42}}, {{T42p}}, {{T43}}, {{T43p}}
*ThinkPad {{X20}}, {{X21}}, {{X22}}, {{X23}}, {{X24}}, {{X30}}, {{X31}}, {{X32}}, {{X40}}, {{X41}}, {{X41T}}
*ThinkPad {{TransNote}}

Problems with SATA and Linux

2006-01-10T12:46:40Z

Mrunge: /* Patches */

{| width="100%"
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__
|style="vertical-align:top" |
Some ThinkPad models use a SATA controller for the system hard disk. This causes several complications for Linux installation. The following lists these problems and known workarounds. Note that the details are often version- and distribution-specific.

===Models using a SATA disk interface===
Models using a SATA controller and a SATA system disk:
*ThinkPad {{Z60t}}, {{Z60m}}
Models using a SATA controller and a PATA (IDE) system disk with a SATA-to-PATA bridge:
*ThinkPad {{T43}}, {{T43p}}
*ThinkPad {{R52}}
*ThinkPad {{X41}}, {{X41T}}

{{NOTE|Some of these problems (namely SMART support, power management and disk information) will be solved in Linux 2.6.15 with the inclusion of libata pass-through. See the SATA driver [http://linux.yyz.us/sata/features.html features], [http://linux.yyz.us/sata/software-status.html software status] and [http://linux.yyz.us/sata/sata-status.html hardware status].}}
|}

==Hang on resume from suspend to RAM==

Linux kernels (as of 2.6.15-rc3) do not support suspend and resume for SATA devices. As a result, the machine hangs upon the first disk access after resume. A kernel patch ([http://lkml.org/lkml/2005/5/2/46 LKML posting]) fixes this by adding SATA power management support.

===Patches===
* [http://shamrock.dyndns.org/~ln/linux/sata_pm.2.6.12.diff Patch for kernel 2.6.12]
* [http://shamrock.dyndns.org/~ln/linux/sata_pm.2.6.13-rc5.diff Patch for kernel 2.6.13-rc5]
* [http://lkml.org/lkml/2005/9/23/97 Patch for kernel 2.6.14]
* [http://www.xenotime.net/linux/SATA/2.6.15-rc/libata_suspend.patch Patch for kernel 2.6.15-rc4]
* [http://tpctl.sourceforge.net/tmp/sata_pm.2.6.15-rc6.patch Patch for kernels 2.6.15-rc6 to 2.6.15]

Some distributions already include this patch (e.g., {{Ubuntu}} Breezy), but some don't (e.g., {{Fedora}} 4).

Althoug the front page of the Wiki reports that 2.6.15 fixes this bug there are patches for 2.6.15. The required patch didn't make it into 2.6.15 final. [http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=9b847548663ef1039dd49f0eb4463d001e596bc3 Jens Axboes patch to support suspend for libATA]

===Links===
* RedHat Bugzilla [https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=169201 bug 169201: "SATA drives fail on laptop suspend"]

==Failed resume from suspend to disk==

Suspend to disk (using swsusp or [[Software Suspend 2]]) needs to load the memory image from the SATA disk. For this to work, you either need an initrd with all the necessary SATA modules, or the SATA drivers compiled into the kernel.

==DVD drive not recognized==

The <tt>ata_piix</tt> SATA driver grabs ownership over the IDE ports when it is loaded, but (by default) does not support PATA ATAPI devices such as the Ultrabay optical drives. Thus, if the <tt>ide</tt> driver is compiled as a module and loaded after <tt>ata_piix</tt>, the DVD drive will not be recognized by either driver.

Either of the following configurations will work:
* For kernel 2.6.14 and newer: enable ATAPI support in the SATA system using {{bootparm|libata.atapi_enabled|1}} (see below; this is experimental).
* Compile IDE into the kernel (non-module).
* Compile both IDE and SATA as modules and make sure IDE is loaded first (the module is called 'ide_generic').

Note that the optical drive must be in the Ultrabay during system boot (Ultrabay device swapping is currently unsupported).

==No DMA on DVD drive==

Using the IDE driver, DMA support cannot be enabled on an Ultrabay optical drive:

# hdparm -d1 /dev/hdc

/dev/hdc:
setting using_dma to 1 (on)
HDIO_SET_DMA failed: Operation not permitted
using_dma = 0 (off)

As a result, the optical drive is slow, and in particular, too slow to play video DVDs.

One workaround is to use employ the SATA driver (instead of the IDE driver) for the optical drive. This requires enabling two featues of the SATA driver, namely ATAPI support and PATA support, which are both in active development and far from stable. Using this will probably devour all your data and go on to eat all the food in your fridge. But if you have full backups and an empty fridge, do the following:

* Grab the latest kernel (must be 2.6.14 or newer; the relevant code is under active development).
* Do one of the following:
** Configure the SATA system (and in particular <tt>ata_piix</tt> and <tt>libata</tt>) as built-in and add {{bootparm|libata.atapi_enabled|1}} to your kernel command line (e.g., in in {{path|/boot/grub/menu.lst}}).
** Configure the SATA system as module (this is often the default) and add "<tt>options libata atapi_enabled=1</tt>" to your {{path|/etc/modprobe.conf}} (or the equivalent in your distribution).
* Do one of the following:
** Disable the IDE system.
** Build the IDE driver as built-in (this is often the default) and add the {{bootparm|hdc|noprobe}} kernel argument (e.g., in in {{path|/boot/grub/menu.lst}}).
** Build the IDE driver as module and add "<tt>options ide hdc=noprobe</tt>" to your {{path|/etc/modprobe.conf}} (or the equivalent in your distribution).
* If you chose to use modules above, regenerate your <tt>initrd</tt> file.

If this doesn't work, use {{cmd|lspci -vn|}} to check whether one of the following chipsets is used in the Thinkpad:
{| border="1" cellspacing="0" cellpadding="2"
|-
!PCI ID
!Name
|-
|8086:7111
|Intel 82371AB/EB/MB PIIX4 IDE
|-
|8086:24db
|Intel 82801EB/ER (ICH5/ICH5R) IDE Controller
|-
|8086:25a2
|Intel 6300ESB PATA Storage Controller
|}
If yes, enable support for these chipsets has to be enabled by setting
#define ATA_ENABLE_PATA
in {{path|include/linux/libata.h}} (and report your ThinkPad model in the discussion page).

There have been reports that DVD burning doesn't work under this configuration, but it seems to work with kernel 2.6.14 and later (tested on a ThinkPad {{T43}} and {{T43p}} with a [[UltraBay Slim DVD Multi-Burner Plus]]).

===Links===
* RedHat Bugzilla [https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=163418 bug 163418: "can't enable DMA on DVD drive"]

==No DMA on system hard disk==

In some Linux kernels, both the SATA driver and the IDE driver can handle the system hard disk. With the SATA driver, it shows as {{path|/dev/sda}} and DMA is enabled. With the IDE driver, it shows as {{path|/dev/hda}} and DMA is disabled.

The simplest way to enable DMA is to force the IDE driver to ignore the system hard disk by passing the {{bootparm|hda|noprobe}} kernel argument. The driver will then be handled by the SATA driver. Note that this will change its device name to {{path|/dev/sda}} (which may require changes in {{path|/etc/fstab}} and the boot loader) and may cause other problems as listed above.

(Observed on a ThinkPad T43 with Fedora Core kernel 2.6.13-1.1526_FC4.)

==No SMART support==

Prior to kernel 2.6.15, the Linux SATA system did not support SMART commands (e.g., via smartctl).

The necessary capability is "libata pass-through", which was incorporated into Linux 2.6.15-rc1 and later. A patch is available for older kernels:
* Kernel 2.6.12: http://rtr.ca/dell_i9300/kernel/kernel-2.6.12/03_libata_passthru.patch
* Kernel 2.6.13: http://rtr.ca/dell_i9300/kernel/kernel-2.6.13/02_libata_passthru.patch
* Kernel 2.6.14: http://www.foo.fh-furtwangen.de/~koenigr/02_libata_passthru.fixed.again.patch
* Kernel 2.6.14 with the above suspend-to-RAM patch: http://linux.spiney.org/system/files?file=02_libata_passthru.fixed.patch

After applying the patch, run smartctl with the "-d ata" parameter:
:{{cmdroot|smartctl -d ata -a /dev/sda}}

==No disk power management==

Prior to kernel 2.6.15, the Linux SATA system did not support power management commands on these models.

The above patches for SMART support resolves this, and in particular enables the following commands:
* {{cmdroot|hdparm -y}} (spin down)
* {{cmdroot|hdparm -S num}} (automatic spin down timeout)
* {{cmdroot|hdparm -B num}} (advanced power management level)
Note that this command is still rejected:
* {{cmdroot|hdparm -M num}} (acoustic management)
(Tested with patched kernels 2.6.13.1 and 2.6.12-4 and a 60GB 7200RPM disk model HTS726060M9AT00.)

Note that even when [[Laptop-mode]] is used, the "hddtemp" daemon (as shipped with Fedora Core 4) will wake up the disk every minute, and must thus be disabled for power management to be effective. Its accesses are not visibile through the {{path|/proc/sys/vm/block_dump}} facility. It is unclear whether disk temperature can be monitored without causing the disk to spin up (on the {{T43}}, none of the {{path|/proc/acpi/ibm/thermal}} values corresponds to the disk's built-in temperature sensor).

==No disk information==

Prior to kernel 2.6.15, on these models the disk information could not be read by the standard commands such as:
*{{cmdroot|hdparm -i /dev/sda}}
*{{cmdroot|hdparm -I /dev/sda}}
The latter is fixed by the above patch for SMART support.

==No swapping of UltraBay device==

The <tt>libata</tt> driver does not yet support hot-swapping (or warm-swapping) of PATA devices. If you use a DVD or 2nd PATA HDD via the <tt>libata</tt> (SATA) driver, to swap them in or out you must power down the machine.

If you use the <tt>ide</tt> driver for a PATA UltraBay device, hot-swapping might work using <tt>hdparm</tt>, <tt>idectl</tt> or <tt>hotswap</tt> (please report). However, DMA will be disabled on these models (see above).

If you use a SATA device in the UltraBay, <tt>libata</tt> hot-swapping might work (please report).

Swapping of the [[UltraBay Slim Battery]] does work.

==BIOS error 2010 on user-installed hard disk==

While not a Linux issue, note that there is an issue with installing alternative PATA (IDE) hard disks as the system drive. Unless the disk is one of the few approved disks listed inside the BIOS, you will get an BIOS error 2010 during system boot, and the disk may operate unreliably. See [[Problem with non-ThinkPad hard disks]].

How to save memory

2005-12-15T14:38:36Z

Mrunge: /* Window Manager */

{| width="100%"
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__
|style="vertical-align:top" |This page is meant as a collection of information on how to save memory to make Linux work reasonable on older system with limited amount of RAM.

Most distributions nowadays don't take much care about it anymore, so there are a lot of things you can do to save memory. To get a smoothly working linux environment on a low memory machine you will need to conciously choose a lot of aspects of your system, most importantly the graphical environment, desktop environment and applications. This page provides detailed information about these various optimization possibilities.
|}

==Alternative graphical environments==
{{Todo|...}}

==Streamlining the desktop environment==
The common Desktop environments GNOME and KDE are, in their modern state, focused more on features, integration, and beauty rather than on resource saving. Understandable, but running Linux on an older ThinkPad with limited RAM requires conscious and sensitive resource usage more than anything else. The good thing about Linux is that a lot of things stay adjustable and customizable. So lets see what we can do about desktops.

One of the most important things is to decide for one graphical widget library and stick with that when you are choosing your desktop environment and applications. Having several toolkits in use means more libraries being loaded and hence more memory being used by those. Possibilities are:
* [http://www.fltk.org/ FLTK]
* [http://www.fox-toolkit.org/ FOX toolkit]
* [http://www.gnustep.org GNUstep toolkit]
* [http://www.gtk.org/ GTK] <tt>(not recommended, use GTK 2 if possible)</tt>
* [http://www.gtk.org/ GTK 2]
* [http://www.lesstif.org/ Lesstif] / [http://www.openmotif.org/ OpenMotif]
* [http://www.trolltech.com/products/qt/index.html QT]
* [http://www.windowmaker.org/development-wings.html WINGs] <tt>(kind of a lightweight GNUstep toolkit, provided by the WindowMaker developers)</tt>
* [http://www.x.org/ X Toolkit]

Of those, at current state, there are enough applications for the X Toolkit, GTK, GTK 2 and QT to provide you with a solution for every task you should want.

===GNOME===
It's like with humans, the worst feature is in most cases also the best one. For GNOME it is probably the many little parts it consists of. Makes it hard to install, but enables one to customize the installation. So, the first thing you should do to streamline GNOME is not to launch it. Sound stupid? Well, lets have a look.

GNOME is basically a set of libraries built around the GTK+ libs and extending its functionality. Add some nice little applications, a session manager, a panel, beautiful icons, and some other stuff and you have GNOME as you know it. Reversing those additions is what you can do to use GNOME applications on a machine that this desktop environment would normally take your nerves on.

The GNOME panel, the session manager, the desktop manager and the window manager are all parts of GNOME that eat a lot of memory for something that others can do in a maybe little less beautiful but much more resource saving way.
So first off configure your login manager not to launch gnome-session at login. If you are using GDM this is quite straight forward, you just need to add a different session script, launching your favorite window manager. See the list below and pick one, lets say i.e. WindowMaker. WindowMaker uses a desktop menu, a dock and a notification area to provide you with an organized way of launching applications and iconfying running ones. So we don't need a panel anymore. Also, think if you really need icons on your desktop. If you do, think about using something like ROX filer instead of nautilus for that. In any case, tell nautilus not to manage the desktop by default by unchecking the according setting within gconf-editor. To keep GNOME applications happy we would need to have gconf and gnome-settings-manager running at every session start. One way to do this is to either include them in your new session script. They both need to be running to make GNOME applications realize their settings properly.

===KDE===
{{Todo|...}}

===Alternative Desktop Environments===
First of all, it is important to notice that GNOME and KDE are not the only Desktop Environments around.
Other complete (featuring most of: window management, session management, desktop management, file management and panel) desktop environments are:
*[http://xfce.org/ XFCE] <tt>uses GTK 2</tt>
*[http://ede.sourceforge.net Equinox Desktop Environment] <tt>uses eFLTK, a modified version of FLTK</tt>
*[http://www.nongnu.org/antiright/ AntiRight Desktop Environment] <tt>uses LessTif / OpenMotif</tt>
*[http://foxdesktop.sourceforge.net/ FOX Desktop Environment] <tt>uses FOX Toolkit</tt>
*[http://www.gnustep.org/ GNUstep] <tt>provides it's own toolkit</tt>

But also, some Window Managers exceed the task of managing windows towards providing a functional workbench. See below for a list.

===Building your own Desktop===

====Window Manager====
If you want to build your own customized desktop, a good start is choosing the window manager of your liking.

Here's a list of some of them:
*including basic Desktop Environment functionality
**the [[Wikipedia:NextStep|NextStep]] alike ones
***[http://www.windowmaker.org/ WindowMaker] <tt>(probably the most widespread NextStep like WM)</tt>
***[http://www.afterstep.org/ AfterStep] <tt>(another one of those)</tt>
***[http://blackboxwm.sourceforge.net/ BlackBox]
***[http://fluxbox.sourceforge.net/ FluxBox] <tt>(tabbed windows, lighweight)</tt>
***[http://www.pekwm.org PekWM] <tt>(kind of a one man show, but feature rich and extremely customizable)</tt>
**others
***[http://www.icewm.org/ IceWM] <tt>(lightweight, widespread)</tt>
*pure WindowManagers
**[http://golem.sourceforge.net/ Golem]
**[http://home.earthlink.net/~lab1701/larswm/ LarsWM] <tt>(unique tiling Window Manager)</tt>
**[http://www.nongnu.org/ratpoison/ ratpoison] <tt>(modeled after gnu screen)</tt>
**[http://fvwm.org/ fvwm] <tt>(small but powerful)</tt>
**[http://http://www.all-day-breakfast.com/wm2/ wm2] <tt>really small Window Manager</tt>

====Taskbar/Panel====
Another thing that especially users coming to Linux from the Windows world would probably like is a Panel or Taskbar.

Here's a collection of independant low resource panels:
*[http://www.chatjunkies.org/fspanel/ F***ing Small Panel] <tt>(doesn't use any toolkit)</tt>
*[http://freshmeat.net/projects/hpanel/ HPanel] <tt>(doesn't use any toolkit)</tt>
*[http://fbpanel.sourceforge.net/ fbpanel] <tt>(depends on GTK 2)</tt>
*[http://jodrell.net/projects/perlpanel Perl Panel] <tt>(depends on GTK 2, gnomevfs, perl)</tt>
*[http://www.gkrellm.net/ GKrellM] <tt>(depends on GTK 2, flexible plugin based skinable vertical panel)</tt>

====Desktop Pinboard====
Then, the next thing you might be looking for is how to get icons onto your desktop. Usually this is done by the file manager who displays the content of a special directory as icons on the desktop. See the File Manager section to follow this approach.

However, you might decide for a really lightwight file manager which doesn't offer this feature. In that case all hope is not lost, for there are also special programs specialized in desktop icon management. Such are:
* [http://idesk.sourceforge.net/ iDesk] <tt>(recent versions need imlib2 only)</tt>

====File Manager====
File Managers are the fourth really important compontent of a desktop environment. There are plenty out their ranging from resource hugs to really lightweight and slim ones.

File Managers come with three distinct general user interface approaches: the two pane gui, the spacial and the browser gui. The browser gui is the one the Windows Explorer starting from Windows 2000 uses as well as earlier versions of Nautilus. The spacial view is the one known from Windows 95 and more recent versions of Nautilus. The two pane view is know to many from Norten Commander, Directory Opus or your favorite FTP client.

The following list provides an overview.
*FLTK
** [http://www.oksid.ch/flfm/ Fast Light File Manager] <tt>(spacial gui)</tt>
* FOX toolkit
** [http://roland65.free.fr/xfe/ X File Explorer] <tt>(browser and two pane gui)</tt>
*GTK
** [http://www.kaisersite.de/dfm/ Desktop File Manager] <tt>(spacial gui, incl. desktop icon management)</tt>
** [http://www.uwyn.com/projects/fm/ FM] <tt>(spacial, MAC OS 9 like gui)</tt>
** [http://radekc.regnet.cz/ Seksi Commander] <tt>(two pane gui)</tt>
*GTK 2
** [http://rox.sourceforge.net/ ROX Filer] <tt>(highly productive spacial gui, incl. panel and desktop icon management)</tt>
** [http://blog.perldude.de/projects/filer/ Filer] <tt>(browser and two pane gui, requires Perl)</tt>
** [http://xffm.sourceforge.net/ XFFM] <tt>(browser and spacial gui, requires some XFCE libs)</tt>
** [http://logicaldesktop.sourceforge.net/ Logical Desktop] <tt>(browser gui, actually a very special approach)</tt>
** [http://tuxcmd.sourceforge.net/ Tux Commander] <tt>(two pane gui)</tt>
** [http://emelfm2.net/emelFM2/ emelFM2] <tt>(two pane gui with full customizable menu and toolbar, the best for power users)</tt>
** [http://thunar.xfce.org/index.xhtml Thunar] <tt>(requires some XFCE libs)</tt>
* OpenMotif
** [http://www.musikwissenschaft.uni-mainz.de/~ag/xplore/xplore.php Xplore] <tt>(browser gui with productive 4 pane concept)</tt>
* QT 2
** [http://www.hi-net.cz/blaza/bfcommander/en/index.html BF-Commander] <tt>(two pane gui)</tt>
* Tcl/Tk
** [http://users.tkk.fi/~mkivinie/X-Files/ X-Files] <tt>(two pane gui)</tt>
*X Toolkit
** [http://www.musikwissenschaft.uni-mainz.de/~ag/xfm/ X File Manager] <tt>(spacial gui)</tt>
** [http://www.boomerangsworld.de/worker/ Worker] <tt>(two pane gui, highly productive and configurable)</tt>
** [http://xnc.dubna.su/ X Northern Captain] <tt>(interesting flexible two pane gui)</tt>
*3D Filemanagers
** [http://www.determinate.net/webdata/seg/tdfsb.html TDFSB] <tt>(3D gui, the most impressing 3D file browser so far)</tt>
** [http://www.forchheimer.se/bfm/ Brutal File Manager] <tt>(3D gui more for fun than productivity)</tt>
** [http://turma.sourceforge.net/software/3dfile/ 3DFile] <tt>(3D gui)</tt>
** [http://orbis.sourceforge.net/ Orbis] <tt>(3D gui)</tt>

==Choosing applications==
===Web Browser===
This is highly dependend on the way you use your browser, it's often worth it to try out all and just track general
memory usage. Remember that <tt>top</tt> and <tt>ps</tt> don't report correct memory usage, track totals only.

====Firefox====
Firefox is graphical web browser. One can install features like AdBlock and FlashClicktoplay which will decrease memory and
processor usage by hiding Flash and Java -adverts.

====Opera====
Opera is graphical web browser. You can easily enable/disable plug-ins and java (press F12) and decrease memory usage.
Opera uses QT as toolkit, so you may shave off some Mbytes off memory usage by using dynamically linked version if you use KDE.

====Konqueror====
Konqueror is graphical web browser. It's integrated with KDE and has several advanced features (esp. ca. KDE 3.5).
You may save some megabytes by using it instead of other browsers when using KDE.
It's not necessarily heavy even when used without running KDE.

====Dillo====
Dillo is minimalistic and very small graphical web browser.

====Elinks/Lynx====
elinks/lynx are both text mode web browsers. <tt>elinks</tt> handles tables and formatting much nicer than <tt>lynx</tt>.
Both go very easy on memory footprint.

{{Todo|...}}

==Disabling unneeded system deamons==
Another thing you can do to improve performance is to get rid of unneaded system daemons launched from your init scripts. Disable them by using the according configuration interface of your distro or by deleting links in the according runlevel directories (usually in <code>/etc/rc.d/</code>).

Daemons you usually don't need:
* httpd <tt>(Apache web server)</tt>
* mysqld <tt>(MySQL database server)</tt>
* smbd <tt>(SMB windows filesharing server)</tt>
* pppd <tt>(PPP server for connections through modems and serial lines)</tt>

==Adjusting filesystems==
You can also try to optimize memory usage by making sure that you have as little as possible of your filesystem residing in RAM. To do this make sure that the following mount points are set to reside on your harddisk in {{path|/etc/fstab}}.
* /dev (not possible if you use udev)
* /tmp

==Other tips==
===Disk space===
When using Debian/Ubuntu/other derivative, use <tt>aptitude</tt> as package manager, and use it as soon as possible. Use it and only it to install and remove packages.

One of it's most usefull features is that it tracks packages you install and marks packages installed via dependency as such, so when you remove a package that is no longer used, or package updates and doesn't use a library anymore, that dependency will get uninstalled.

You can mark packages installed as automatically installed by hitting 'M' (uppercase m), it will be marked for deinstallation if it's not longer required.

Category:ThinkWiki

2005-10-08T17:26:21Z

Mrunge: Remove advertisements and revert to last version by 24.225....

{| 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;">
=== ThinkWiki Categories ===
This pages gives categorized information to specific thinkpad related topics.
</div>
|}
[[de:Kategorie:ThinkWiki]]

ThinkWiki:Sponsors

2005-10-08T17:24:22Z

Mrunge: Remove advertisements and revert to last version by wyrfel

=== There are no sponsors at the moment. :-( ===

The dedicated server is rather expensive, so '''please''' [[ThinkWiki:Support | support this project]] by making a small donation.

Thank you very much!

[http://www.thinkwiki.org/wiki/ThinkWiki:Support http://www.thinkwiki.org/skins/common/images/project-support.jpg]

ThinkWiki:Banner

2005-10-08T17:20:59Z

Mrunge: Remove destructins by vova and revert to last version

[[Image:ThinkWiki-Button-Banner.png|ThinkWiki: Linux Thinkpad Wiki]]

This is our banner image crafted by [[User:Wyrfel|Wyrfel]]. Its size is 486x60 pixels (standard banner size).

Please feel free to setup our banner on your website and link it to www.thinkwiki.org.
You can do this by adding this html code to your site:

<nowiki><a href="http://www.thinkwiki.org/"></nowiki>
<nowiki><img src="http://www.thinkwiki.org/graphics/thinkwiki_banner.png"</nowiki>
border="0" width="486" height="60"
alt="ThinkWiki - The Linux Thinkpad Wiki"></a>

We also provide three different sized buttons which you can add to your site:

[[Image:ThinkWiki-Logo_140.png|ThinkWiki: Linux Thinkpad Wiki]]
[[Image:ThinkWiki-Logo_200.png|ThinkWiki: Linux Thinkpad Wiki]]
[[Image:ThinkWiki-Logo_230.png|ThinkWiki: Linux Thinkpad Wiki]]

ThinkWiki Logo (140x55 pixel):
<nowiki><a href="http://www.thinkwiki.org/"></nowiki>
<nowiki><img src="http://www.thinkwiki.org/graphics/thinkwiki_logo_140x55.png"</nowiki>
border="0" width="140" height="55"
alt="ThinkWiki - The Linux Thinkpad Wiki"></a>

ThinkWiki Logo (200x80 pixel):
<nowiki><a href="http://www.thinkwiki.org/"></nowiki>
<nowiki><img src="http://www.thinkwiki.org/graphics/thinkwiki_logo_200x80.png"</nowiki>
border="0" width="200" height="80"
alt="ThinkWiki - The Linux Thinkpad Wiki"></a>

ThinkWiki Logo (230x90 pixel):
<nowiki><a href="http://www.thinkwiki.org/"></nowiki>
<nowiki><img src="http://www.thinkwiki.org/graphics/thinkwiki_logo_230x90.png"</nowiki>
border="0" width="230" height="90"
alt="ThinkWiki - The Linux Thinkpad Wiki"></a>

Please go to [http://www.thinkwiki.org/graphics/ http://www.thinkwiki.org/graphics/] to download an archive of these images and for further instructions.

[[Category:ThinkWiki]]

User:Akw

2005-10-08T17:19:03Z

Mrunge: Revert multiple destroying edits to last version by Tonko

=== Hello! ===
My name is Arno Willig, I was born in Oldenburg, Germany on 21.11.1977.<br />
I am student at the C.v.O.-University Oldenburg, studying computer science and biology.<br />
My diploma's thesis is work-in-progress. It's about ''Secure Linux'', if you're interested, visit my [http://www.informatik.uni-oldenburg.de/~akw university homepage] (german language).<br />
I have got two [http://www.moonflower.de/arnowillig/kategorie/leonie-und-emma/ baby daughters], Leonie and Emma, who were born on 13.04.2005.
</div>
|style="vertical-align:top" |
[[image:Arno.jpg|Arno Willig]]
|}

Category:Models

2005-10-08T17:18:09Z

Mrunge: Revert multiple destroying edits to last version by Tonko

{| 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;">
=== ThinkPad Models ===
This page offers information about the various models published throughout the [[ThinkPad History|history of ThinkPad computers]].<br />
You can also read about the [[ThinkPad|origin of the ThinkPad branch]].<br />
If you need more specific information about a precise model, try to find it within the [[Hardware Specifications]].
</div>
|}

The following is a list of various [[Thinkpad series|series of Thinkpad computers]]:
=== Current Series ===
* '''Thinkpad G''': Desktop replacement machines built on desktop processors, large and heavy with limited battery runtime.
* '''Thinkpad R''': Traditionally the budget laptop line, there are 'mobile workstation' configurations to replace the discontinued A-series.
* '''Thinkpad T''': Slimline Notebook, two drives internal, light and thin with one swappable bay.
* '''Thinkpad X''': Subnotebook, very small and light, hard drive internal, no internal optical drive, small screen.
=== Withdrawn Series ===
* '''Thinkpad A''': All in One Notebooks, heavy, large, three spindle machines, all drives internal, two swappable drive bays.
* '''Thinkpad S''': Subnotebook, extremely small and light, produced for Japanese and Hong Kong market only.
* '''ThinkPad 130''': Japanese version of the i1300
* '''ThinkPad 2xx''': Classic 10"-sub-notebook models.
* '''ThinkPad 3xx''': Classic mid-range models.
* '''ThinkPad 5xx''': Classic sub-notebook models.
* '''ThinkPad 6xx''': Classic Slimline models.
* '''ThinkPad 7xx''': Classic high-end models.
* '''ThinkPad 8xx''': Classic PowerPC models.
* '''ThinkPad i Series''': Classic budget models manufactured by Acer under license from IBM.
* '''ThinkPad TransNote''': Classic model.
* '''PC110''': Classic Palm-Top model.

The subcategories below are collections of all information regarding specific models of ThinkPads.

[[Category:ThinkWiki]][[de:Kategorie:Modelle]]

ThinkWiki:About

2005-10-08T17:16:17Z

Mrunge: Revert changes to last version by wyrfel

== About ThinkWiki ==

'''ThinkWiki''' aims to provide enough information to help you running your favourite [[Linux]] [[:Category:Distributions|distribution]] on [[:Category:Models|your ThinkPad]] computer. Of course this includes comprehensive information about [[:Category:Models|ThinkPad Hardware]] and [[Thinkpad Technologies]]. And even though ThinkWikis focus clearly lies on [[Linux]], you can find some [[:Category:Windows|Windows]] related information well.

All information found on this wiki is published under the GNU FDL ([[Wikipedia:GNU Free Documentation License|GNU Free Documentation License]]).

* If you don't know what a wiki is and want to learn about it, read an [[Wikipedia:Wiki|article about wikis]] in the great [[Wikipedia:Mainpage|Wikipedia]].
* If you are interested in this wiki's server's [[ThinkWiki:Server|hardware]], follow [[ThinkWiki:Server|this link]].
* We would be very happy if you decide to [[ThinkWiki:Support|support this project]].

Madwifi

2005-10-08T17:14:51Z

Mrunge: Revert changes to last version by wyrfel

== Multiband Atheros Driver for WiFi ==
Linux driver for 802.11a/b/g universal NIC cards - Cardbus, PCI, or miniPCI - using Atheros chip sets.

The following adapters sold by IBM use the Atheros chips:
* [[IBM Dual-Band 11a/b Wi-Fi Wireless Mini PCI Adapter]]
* [[IBM 11b/g Wireless LAN Mini PCI Adapter]]
* [[IBM 11a/b/g Wireless LAN Mini PCI Adapter]]
* [[IBM 11a/b/g Wireless LAN Mini PCI Adapter II]]
* [[ThinkPad 11a/b/g Wireless LAN Mini Express Adapter]]
* IBM 802.11a Wireless LAN Cardbus Adapter
* IBM 11 a/b/g Wireless Cardbus Adapter

=== Project Homepage ===
http://sourceforge.net/projects/madwifi

=== Packages ===
*daily cvs snapshots: http://madwifi.otaku42.de
*{{Debian}} Packages: http://www.marlow.dk/site.php/tech/madwifi
*{{Debian}} Packages: http://www.users.tpg.com.au/sigm/misc/madwiki.txt
*{{Fedora}} Packages(1): http://rpm.livna.org
*{{Fedora}} Packages(2): http://www.atrpms.net/name/madwifi/

=== CVS ===
:{{cmd|cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/madwifi co madwifi}}

=== Installation ===

*Make sure that you've got sysctl support and the net/radio enabled (wireless extensions) in your kernel. Install the driver with make & make install
* further more you like to install the wireless tools from [http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Tools.html wireless tools]. Make sure the versions fit together by
:{{cmd|iwconfig --version}}

Setting up [[wpa_supplicant]] with wpa-psk.

=== Status ===
in development, usable

=== OpenSource HAL ===
The "official" driver consists of an opensource wrapper with binary HAL (Hardware Abstraction Layer). This HAL is not a binary firmware like with the Intel Wireless chips, but a piece of code that needs to runs in the Linux kernel.
The vendors reasoning behind this is, that since the Atheros chip could be tuned to any frequency, and hence interfere with systems operating in those frequencies, that we simply need to accept this binary module.<br>
Obviously this binary HAL is unacceptable to the Linux kernel developers, and the Atheros driver in this state will never become part of the official kernel.<br>
Some OpenBSD developers facing the same issue, reverse engineered the binary HAL and have produced an OpenSource version. Hopefully a driver based on this might be included with the Linux kernel at some point in time, and picked up by the mainstream distributions.

=== Related links ===
* [http://madwifi.sourceforge.net/dokuwiki/doku.php MadWiFi Wiki]
* [http://team.vantronix.net/ar5k/ OpenSource Atheros HAL]

[[Category:Drivers]]

Ibm-acpi

2005-10-08T17:13:36Z

Mrunge: Revert to last version of tonko

== ibm-acpi - IBM ThinkPad ACPI Extras Driver ==

This is a Linux ACPI driver for the IBM ThinkPad laptops written by Borislav Deianov. It aims to support various features of these laptops which are accessible through the ACPI framework but not otherwise supported by the generic Linux ACPI drivers. As a kernel module, ibm-acpi works as a bridge to deliver information about certain hardware events like key presses or control the state of certain hardware features by software.

=== Features ===
*triggers ACPI Events for
** Fn key combinations ({{key|Fn}}{{key|F1}}, {{key|Fn}}{{key|F2}}, {{key|Fn}}{{key|F3}}, {{key|Fn}}{{key|F4}}, {{key|Fn}}{{key|F5}}, {{key|Fn}}{{key|F6}}, {{key|Fn}}{{key|F7}}, {{key|Fn}}{{key|F8}}, {{key|Fn}}{{key|F9}}, {{key|Fn}}{{key|F10}}, {{key|Fn}}{{key|F11}}, {{key|Fn}}{{key|F12}})
** [[UltraBay]] device eject
** Display lid, Power button, Undock button
*enables software control of
** Bluetooth
** Video output switching, video expansion control
** Docking and undocking (limited)
** Fan
** Volume
** LCD Brightness
** [[ThinkLight]]
** LEDs
** [[Error Codes and Beep Codes|beep]] codes
** several CMOS states
* can show values of
** five temperature sensors
** Embedded Controler registers

=== Project Homepage / Availability ===
http://ibm-acpi.sourceforge.net/

Included with the Linux kernel since 2.6.10. (Keep in mind, however, that the version included with the official kernel, or with some particular distribution, is not always the latest one.)

Probably Kernel 2.6.14 will include version 0.12 (versus version 0.8 in prior kernels).

=== Status ===
in development, usable, very much alive

=== Packages ===
*[[:Category:Debian | Debian]] Packages: http://debian.isg.ee.ethz.ch/public/
*[[:Category:Gentoo | Gentoo]] ebuild: http://packages.gentoo.org/packages/?category=app-laptop;name=ibm-acpi

=== Application support===
* [http://www.gkrellm.net GKrellM] supports fan and thermal information
* [http://www.joachim-breitner.de/blog/archives/38-Created-gaim-thinklight.html gaim-thinklight] is a gaim plugin which makes the [[ThinkLight]] blink, when a message arrives.

=== Interesting links related to this project ===
* [http://ibm-acpi.sf.net ibm-acpi Sourceforge project summary]
* [http://mailman.linux-thinkpad.org/mailman/listinfo/linux-thinkpad Linux-Thinkpad Mailinglist]
* [http://acpi.sourceforge.net acpi.sourceforge.net]
* [http://www.kernel.org www.kernel.org]

[[Category:Drivers]]
[[Category:770X]] [[Category:770Z]] [[Category:A20m]] [[Category:A20p]] [[Category:A20m]] [[Category:A20p]] [[Category:A21e]] [[Category:A21m]] [[Category:A21p]] [[Category:A22e]] [[Category:A22m]] [[Category:A22p]] [[Category:G40]] [[Category:G41]] [[Category:R30]] [[Category:R31]] [[Category:R32]] [[Category:R40]] [[Category:R40e]] [[Category:R50]] [[Category:R50p]] [[Category:R51]] [[Category:R52]] [[Category:T20]] [[Category:T21]] [[Category:T22]] [[Category:T23]] [[Category:T30]] [[Category:T40]] [[Category:T40p]] [[Category:T41]] [[Category:T41p]] [[Category:T42]] [[Category:T42p]] [[Category:T43]] [[Category:T43p]] [[Category:X20]] [[Category:X21]] [[Category:X22]] [[Category:X23]] [[Category:X24]] [[Category:X30]] [[Category:X31]] [[Category:X40]] [[Category:X41]] [[Category:X41 Tablet]] [[Category:TransNote]]
[[de:ibm-acpi]]

How to make ACPI work

2005-09-26T08:14:49Z

Mrunge: /* Suspend to RAM (Sleep) */

==general==
===Kernel configuration===
First of all you'll have to enable ACPI support in your kernel (if your distro doesn't already have an ACPI enabled kernel).
To do this open your kernel config and enable ACPI Power Management:
:{{kernelconf||||Power management options|Power Management support|<*>|CONFIG_PM}}
:{{kernelconf||||Power management options|ACPI|<*>|CONFIG_ACPI_SLEEP}}

You'd most likely want to enable the following ACPI options:
:{{kernelconf|||Power management options|ACPI|Sleep States|<*>|CONFIG_ACPI_SLEEP}}
:{{kernelconf|||Power management options|ACPI|AC Adapter|<*>|CONFIG_ACPI_AC}}
:{{kernelconf|||Power management options|ACPI|Battery|<*>|CONFIG_ACPI_BATTERY}}
:{{kernelconf|||Power management options|ACPI|Fan|<*>|CONFIG_ACPI_FAN}}
:{{kernelconf|||Power management options|ACPI|Processor|<*>|CONFIG_ACPI_PROCESSOR}}
:{{kernelconf|||Power management options|ACPI|Thermal Zone|<*>|CONFIG_ACPI_THERMAL}}

If you prefer editing your {{path|.config}} file directly, you should set at least the following variables:
CONFIG_PM=y
CONFIG_ACPI_BOOT=y
CONFIG_ACPI_INTERPRETER=y
CONFIG_ACPI_SLEEP=y
CONFIG_ACPI_SLEEP_PROC_FS=y
CONFIG_ACPI_AC=y
CONFIG_ACPI_BATTERY=y
CONFIG_ACPI_BUTTON=y
CONFIG_ACPI_FAN=y
CONFIG_ACPI_PROCESSOR=y
CONFIG_ACPI_THERMAL=y
CONFIG_ACPI_BUS=y
CONFIG_ACPI_EC=y
CONFIG_ACPI_POWER=y
CONFIG_ACPI_PCI=y
CONFIG_ACPI_SYSTEM=y

Then recompile your kernel.

===IBM specific ACPI driver===
Unfortunately, special drivers for ACPI on ThinkPads were not included with kernels prior 2.6.10. So you'll have to compile one yourself or get it as precompiled module for your kernel.

You have the choice between [[thinkpad-acpi]] and [[ibm-acpi]], with the latter being the recommended one.

If you use a post-2.6.10 kernel and you want to use [[ibm-acpi]], it is recommended to look on its projects page for a possibly newer version.

{{HINT|In general it is a good idea to read the README included with the driver.}}

===ACPI daemon===
Also you'll need to install [[acpid]], if it isn't present on your system. [[acpid]] is a daemon that handles the ACPI events generated by the system. Read [[How to configure acpid]].

==Screen blanking (Standby)==
Make sure you have
Option "DPMS"
in the Monitor section of your {{path|/etc/X11/XF86Config}} or {{path|/etc/X11/xorg.conf}}.

Running {{cmd|xset +dpms}} and then {{cmd|xset dpms force off}} will turn off the backlight on a laptop screen.<br />

Note that this may not work in combination with {{cmd|echo -n "mem" > /sys/power/state}} because switching to console causes the backlight to come back on before sleeping.

==Suspend to RAM (Sleep)==
ACPI Sleep/suspend-to-ram with recent 2.6.x kernels usually works fine. Have a look at the [[How to configure acpid|acpid configuration HOWTO]]. It includes a specific example for going to sleep on lid close.

The following glitches may or may not occur in relation to suspending to RAM:
* 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.
* When resuming from a suspend-to-ram the display might remain black or might only show the pre-suspend output (the system is still rebootable via {{key|ctrl}}{{key|alt}}{{key|del}}). Look [[Problem with display remaining black after resume|here]] for solutions.
* 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.
* Also, you might want to take note of the [[Problem with high power drain in ACPI sleep]].
* You may experience problems when using {{cmdroot|echo standby > /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.
* If you're running MySQL, sleep may also not work, so stop MySQL first, then sleep. Remember to restart MySQL when you wakeup.
* Problems with the serial port of the port replicator after the wake up from ram have also been experienced.
* Crash on resume
** ...when using ATI proprietary drivers can be solved by using [http://freshmeat.net/projects/vbetool/ vbetool].
** ...might be solved by disabling ''APIC'' (@Processor type and features) in the kernel configuration
* Due to the fact that Sonoma chipset based laptops (T43, T43p) utilize the SATA layer for disk access and SATA does not have power-management support yet Suspend to RAM does not work on these machines. However, Jens Axboe's patch ([http://marc.theaimsgroup.com/?l=linux-kernel&m=111504542402455&w=2] LKML posting) provides SATA power-management support and makes Suspend to RAM work on the T43 at least. (Tested on 2.6.12rc6 which the patch applies to with some offsets. T43p not tested but should work as well. X41: uses SATA also and works with ACPI sleep after this patch applied (with acpi_sleep=s3_bios), but still hung with APM sleep (acpi=off) when recovering from suspend. R52 uses SATA and sleep doesn't work, so it is probably affected too). Ubuntu Breezy includes this patch, so you don't need to apply it and build the kernel.
** [http://shamrock.dyndns.org/~ln/linux/sata_pm.2.6.12.diff 2.6.12 patch]
** [http://shamrock.dyndns.org/~ln/linux/sata_pm.2.6.13-rc5.diff 2.6.13-rc5 patch]
** [http://lkml.org/lkml/2005/9/23/97 Post on how to patch later (2.6.14-rc) kernels]

==Suspend to disk (Hibernate)==
There are two drivers for this available:
* swsusp, which is in the kernel and
* [http://developer.berlios.de/projects/softwaresuspend/ SoftwareSuspend2] which is more feature rich, but not yet in the kernel, so you have to patch it in yourself
Both are reported to work fine as long as you use open-source graphic drivers. A comparison of the features can be found on [http://softwaresuspend.berlios.de/features.html this page].

Just in case you are in doubt...yes, it is safe in both cases to use the same swap partition as active swap and as suspend partition.

===using swsusp===
Software Suspend (swsusp) is included in the 2.6 kernel series. It seems like no patches for 2.4 kernels are available.

To enable software suspend change your kernel config as follows:
:{{kernelconf||||Power management options|Power management support|<*>|CONFIG_PM}}
:{{kernelconf||||Power management options|Software Suspend|<*>|CONFIG_SOFTWARE_SUSPEND}}
:{{kernelconf||||Power management options|Default resume partition|[/dev/resume_partition]|CONFIG_PM_STD_PARTITION}}

<tt>/dev/resume_partition</tt> needs to be replaced by the swap partition you want to use for suspending. (Use {{cmdroot|fdisk -l /dev/hda}} if unsure.)

You can override the default resume partition anytime by giving {{bootparm|resume|/dev/resume_partition}} as kernel boot parameter.
Also, in case you suspended, but want to boot up normally (without resuming from the saved image - losing all data that was unsaved at suspend time), you can give the <tt>noresume</tt> kernel boot parameter.

(In my case, and according to reports from several people, suspending does not work if resume_partition is specified in the kernel config (my version is 2.6.12-3 from kernel.org). It works as a charm if one specifies the resume partition as a kernel parameter instead.)

To suspend you can either do a simple {{cmdroot|echo -n 4 > /proc/acpi/sleep}} (recommended) or use the [http://softwaresuspend.berlios.de/old-site/swsusp/sysvinit-2.76-v2-for_swsusp-v5.tar.gz patched SysVInit] and call {{cmdroot|swsusp}} or {{cmdroot|shutdown -z now}}.

Ideally you would do this from a script like {{path|/etc/acpi/actions/hibernate.sh}}. It has proven to be a good idea to shutdown the following processes/drivers within the script before you do the actual suspend.
*any running mysql server
*the linuxant driver may require stopping in a acpi script as well. {{cmdroot|dldrstop}} does the trick.

Afterwards you might want to enable them again, as well as run a script that does necessary configurations according to the ac power state.
Furthermore, the system clock is not readjusted automatically, so you will probably also want the do that from that script (i.e. by restarting your systemclock bootup script).

If the sound output is silent after resume, these commands might help to get sound to work again without reloading any modules:

amixer set Master mute >/dev/null 2>&1
amixer set PCM mute >/dev/null 2>&1
amixer set Master unmute >/dev/null 2>&1
amixer set PCM unmute >/dev/null 2>&1

Finally you should take note that swsusp does not set the ACPI S4 state. Instead it goes to S5. This means that the machine itself doesn't know that it was suspend rather than shutdown. Hence you can i.e. boot a parallel installed other operating system and resume your linux session later, as long as you don't touch the swap partition the image was saved to.

===using SoftwareSuspend2===
First apply Software Suspend 2 patches from http://www.suspend2.net if they are not already in your kernel.

Be sure to also read the http://www.suspend2.net/HOWTO.html

These are the options for the kernel. Make sure to change the <tt>/dev/resume_partition</tt> to your swap partition, i.e. <tt>/dev/hda5</tt>.

# Software Suspend 2
CONFIG_SOFTWARE_SUSPEND2=y
CONFIG_SOFTWARE_SUSPEND2_BUILTIN=y
CONFIG_SOFTWARE_SUSPEND_SWAPWRITER=y
CONFIG_SOFTWARE_SUSPEND_LZF_COMPRESSION=y
CONFIG_SOFTWARE_SUSPEND_TEXT_MODE=y
CONFIG_SOFTWARE_SUSPEND_DEFAULT_RESUME2="/dev/resume_partition"
# CONFIG_SOFTWARE_SUSPEND_KEEP_IMAGE is not set
CONFIG_SOFTWARE_SUSPEND_CHECK_RESUME_SAFE=y
# CONFIG_SOFTWARE_SUSPEND_DEBUG is not set
# CONFIG_SOFTWARE_SUSPEND_DEVELOPER is not set

Next, compile and install the kernel.

In the meantime, add the following to the kernel parameters: {{bootparm|resume2|swap:/dev/resume_partition}}. Again change <tt>/dev/resume_partition</tt> to your swap partition.

Install the hibernation script:
*For {{Gentoo}} users: emerge hibernate-script<br />
*For {{Fedora}} users: kernel and hibernate RPMs are available at http://mhensler.de/swsusp/<br />
*For all other users, check the home page for packages (deb, i386 rpm, tgz, and source rpm) from http://www.suspend2.net
*{{Debian}} users using initrd image, make sure you copy [http://dagobah.ucc.asn.au/swsusp/2.0.0.102/swsusp-initrd.sh swsusp-initrd.sh] script to your {{path|/etc/mkinitrd/scripts}} directory before creating initrd image.

Restart using the new kernel and run the script to test it: {{cmdroot|/usr/sbin/hibernate}}

==ThinkPads on which it is recommended to use ACPI==
*ThinkPad {{770X}}, {{770Z}}
*ThinkPad {{A20m}}, {{A20p}}, {{A20m}}, {{A20p}}, {{A21e}}, {{A21m}}, {{A21p}}, {{A22e}}, {{A22m}}, {{A22p}}, {{A30}}, {{A30p}}, {{A31}}, {{A31p}}
*ThinkPad {{G40}}, {{G41}}
*ThinkPad {{R30}}, {{R31}}, {{R32}}, {{R40}}, {{R40e}}, {{R50}}, {{R50p}}, {{R51}}, {{R52}}
*ThinkPad {{T20}}, {{T21}}, {{T22}}, {{T23}}, {{T30}}, {{T40}}, {{T40p}}, {{T41}}, {{T41p}}, {{T42}}, {{T42p}}, {{T43}}, {{T43p}}
*ThinkPad {{X20}}, {{X21}}, {{X22}}, {{X23}}, {{X24}}, {{X30}}, {{X31}}, {{X32}}, {{X40}}, {{X41}}, {{X41T}}
*ThinkPad {{TransNote}}

User:Mrunge

2005-09-21T14:55:18Z

Mrunge: Typo

'''Mrunge'''

currently owns a TP43 (Model 2668) running ([[Installing_Fedora_Core_4_on_a_ThinkPad_T43_(2668)|Fedora Core 4]]).
His first Thinkpad computer was a [[:Category:T23|T23]] supplied by his (former) employer. Being impressed by the superior quality (compared to a somewhat cheaper no-name device) it was naturally clear to buy a Thinkpad as next laptop computer.

===contribution(s):===
* [[Installing_Fedora_Core_4_on_a_ThinkPad_T43_(2668)]]

===problems/interests===
* [[How to configure Madwifi driver and wpa2]]

User:Mrunge

2005-09-21T14:53:39Z

Mrunge:

'''Mrunge'''

currently owns a TP43 (Model 2668) running ([[Installing_Fedora_Core_4_on_a_ThinkPad_T43_(2668)|Fedora Core 4]]).
His first Thinkpad computer was a [[T23]] supplied by his (former) employer. Being impressed by the superior quality (compared to a somewhat cheaper no-name device) it was naturally clear to buy a Thinkpad as next laptop computer.

===contribution(s):===
* [[Installing_Fedora_Core_4_on_a_ThinkPad_T43_(2668)]]

===problems/interests===
* [[How to configure Madwifi driver and wpa2]]

User:Mrunge

2005-09-16T07:49:56Z

Mrunge: First version: *Hello thinkpad-friends!*

'''Mrunge'''

currently owns a TP43 (Model 2668) running ([[Installing_Fedora_Core_4_on_a_ThinkPad_T43_(2668)|Fedora Core 4]]).
His first Thinkpad computer was a [[Category:T23|T23]] supplied by his (former) employer. Being impressed by the superior quality (compared to a somewhat cheaper no-name device) it was naturally clear to buy a Thinkpad as next laptop computer.

===contribution(s):===
* Installing_Fedora_Core_4_on_a_ThinkPad_T43_(2668)

===problems/interests===
* [[How to configure Madwifi driver and wpa2]]

Ibm-acpi

2005-09-06T14:22:57Z

Mrunge: /* Project Homepage / Availability */

Installing Fedora Core 4 on a ThinkPad T43 (2668)

2005-08-25T11:31:33Z

Mrunge: +Cat

Installation is quite smooth, but requires some work by hand. I enlist only the changes

== X-Windows ==
Add the dynamic clock option in the xorg.conf. It aims to provide a moderate boost in battery life. You find the file at
/etc/X11/xorg.conf
The device section should contain a videocard section like the folowing one:
Section "Device"
Identifier "Videocard0"
Driver "radeon"
VendorName "Videocard vendor"
BoardName "ATI Radeon Mobility M300"
'''Option "DynamicClocks" "on"'''
EndSection

==Network Installation==

lspci shows
04:02.0 Ethernet controller: Atheros Communications, Inc. AR5212 802.11abg NIC (rev 01)

I got the madwifi source code from [http://madwifi.sf.net MadWifi Home Page]. Compile after downloading
tar xzf madwifi-cvs-current.tar.gz
cd madwifi
make
su
make install

==IBM ACPI Module==

The module version included in current kernels (2.6.12) is 0.8, but the current version of the module is 0.11. It has some advantages. For directions on how to install this driver, please refer to [[Ibm-acpi]].
After compilation, edit /etc/rc.local:
#!/bin/sh
#
# This script will be executed *after* all the other init scripts.
# You can put your own initialization stuff in here if you don't
# want to do the full Sys V style init stuff.

touch /var/lock/subsys/local

modprobe ibm_acpi experimental=1
echo enable > /proc/acpi/ibm/hotkey

The last line enables hotkeys. To utilize supsend to RAM or to disk, the acpid has to be configured.

==Suspend to disk==

To get suspend to disk working, fetch a recent kernel and recompile. For further instructions, take a look at the swsusp-Section in [[How to make ACPI work]]. Especially configure the kernel to suspend to the swap partition. If you're not sure, take a look at the partitition list output by issuing in command line
fdisk -l

Don't forget to compile SCSI and the Intel SATA into the kernel. Do a
make && make install
Check the boot loader (ususally grub) to include the new kernel.

Reboot and do a
echo -n 4 > /proc/acpi/sleep
If everything works, the system will be shut down to disk.

[[Category:T43]]

Installing Fedora Core 4 on a ThinkPad T43 (2668)

2005-08-22T15:02:31Z

Mrunge:

Installation is quite smooth, but requires some work by hand. I enlist only the changes

== X-Windows ==
Add the dynamic clock option in the xorg.conf. You find the file at
/etc/X11/xorg.conf
The device section should contain a videocard section like the folowing one:
Section "Device"
Identifier "Videocard0"
Driver "radeon"
VendorName "Videocard vendor"
BoardName "ATI Radeon Mobility M300"
'''Option "DynamicClocks" "on"'''
EndSection

==Network Installation==

lspci shows
04:02.0 Ethernet controller: Atheros Communications, Inc. AR5212 802.11abg NIC (rev 01)

I got the madwifi source code from [http://madwifi.sf.net MadWifi Home Page]. Compile after downloading
tar xzf madwifi-cvs-current.tar.gz
cd madwifi
make
su
make install

==IBM ACPI Module==

The module version included in current kernels (2.6.12) is 0.8, but the current version of the module is 0.11. It has some advantages. For directions on how to install this driver, please refer to [[Ibm-acpi]].
After compilation, edit /etc/rc.local:
#!/bin/sh
#
# This script will be executed *after* all the other init scripts.
# You can put your own initialization stuff in here if you don't
# want to do the full Sys V style init stuff.

touch /var/lock/subsys/local

modprobe ibm_acpi experimental=1
echo enable > /proc/acpi/ibm/hotkey

The last line enables hotkeys. To utilize supsend to RAM or to disk, the acpid has to be configured.

==Suspend to disk==

To get suspend to disk working, fetch a recent kernel and recompile. For further instructions, take a look at the swsusp-Section in [[How to make ACPI work]]. Especially configure the kernel to suspend to the swap partition. If you're not sure, take a look at the partitition list output by issuing in command line
fdisk -l

Don't forget to compile SCSI and the Intel SATA into the kernel. Do a
make && make install
Check the boot loader (ususally grub) to include the new kernel.

Reboot and do a
echo -n 4 > /proc/acpi/sleep
If everything works, the system will be shut down to disk.

Buyers Guide

2005-08-22T15:00:57Z

Mrunge:

This page is dedicated to hints about buying used or new ThinkPad models. You can find notes about typical weaknesses of used ThinkPads here and other things you should care about when choosing a ThinkPad and where to buy it.

...

Talk:Installing Fedora Core 4 on a ThinkPad T43

2005-07-21T11:23:03Z

Mrunge:

I have IMB Thinkpad T42 and I am trying to install IPW2200 but I am unsucessfully complete the installation process. Had any one had it to work? Could you please give me some instruction on how to install firmware onto my Fedora Core 4?

Thanks

----

Did you try it after installing the ipw2200 firmware from rpm.livna.org?

IBM Integrated Bluetooth IV with 56K Modem (BMDC-3)

2005-07-20T14:36:45Z

Mrunge: /* Linux Bluetooth driver */

__NOTOC__
{| width="100%"
|style="vertical-align:top" |[[Image:Logo_bluetooth.jpg|Bluetooth Logo]]
|style="vertical-align:top" |
<div style="margin:0px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;">
=== IBM Integrated Bluetooth IV with 56K Modem (BMDC-3) ===
This is a combination Bluetooth and Modem Adapter that is installed in a CDC slot.
=== Bluetooth Features ===
* Chipset: Broadcom
* USB VID/PID: 0A5C:201E
=== Modem Features ===
* Chipset: Conexant
* AC'97 Modem
</div>
|}
=== IBM Partnumbers ===
IBM FRU PN: 39T0022 ($37.50 in July 2005)

This part takes the place of the 56K Modem board.
It requires a Bluetooth antenna, and some ThinkPads built without Bluetooth already have the antenna installed -- the antenna wire may be found disconnected and taped under the Modem board.

In addition to the Modem/BT module, a Bluetooth Thinkpad also uses an extra indicator LED below the LCD display, and another indicator LED on the top of the lid. To see these two LEDs, two new clear plates are required. The entire set of replacement sticker plates can be ordered as FRU 26R8409 ($12 as of July 2005). (formerly FRU: 13R2455)

=== Also known (in IBM literature) as.... ===
*

=== Linux Bluetooth driver ===
??

The Bluetooth device is implemented using USB and can be enabled or disabled with the {{key|Fn}}{{key|F5}} key combination

Bluethooth is supported by [[ibm-acpi]].

=== Linux Modem driver ===
Although, the [http://www.smlink.com/ Smartlink] driver for Agere modems is able to communicate with the modem via AT commands, it cannot dial out (contradicting reports welcome!).

If your favourite distribution does not include a hsfmodem driver (search for "hsfmodem" or "Conexant"), you can try the one from Linuxant: http://www.linuxant.com/drivers (14k free as in beer, 56k+Fax license 15$, they explain this policy under: http://www.linuxant.com/store/faq.php )

=== ThinkPad's this card may be found in ===
* {{R52}}
* {{T43}}, {{T43p}}
* {{X32}}
* {{X41}}, {{X41T}}

===External Sources===
*[http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-51427 IBMs page about configuring Bluetooth under Linux]

[[Category:Components]]

Installing Fedora Core 4 on a ThinkPad T43 (2668)

2005-07-20T12:48:48Z

Mrunge: /* Suspend to disk */

Installation is quite smooth, but requires some work by hand. I enlist only the changes

== X-Windows ==
Add the dynamic clock option in the xorg.conf. You find the file at
/etc/X11/xorg.conf
The device section should contain a videocard section like the folowing one:
Section "Device"
Identifier "Videocard0"
Driver "radeon"
VendorName "Videocard vendor"
BoardName "ATI Radeon Mobility M300"
'''Option "DynamicClocks" "on"'''
EndSection

==Network Installation==

lspci shows
04:02.0 Ethernet controller: Atheros Communications, Inc. AR5212 802.11abg NIC (rev 01)

I got the madwifi source code from [http://madwifi.sf.net MadWifi Home Page]. Compile after downloading
tar xzf madwifi-cvs-current.tar.gz
cd madwifi
make
su
make install

==IBM ACPI Module==

The included module version in current kernels (2.6.12) is 0.8, but the current version of the module is 0.11. It has some advantages. For directions on how to install this driver, please refer to [[Ibm-acpi]].
After compilation, edit /etc/rc.local:
#!/bin/sh
#
# This script will be executed *after* all the other init scripts.
# You can put your own initialization stuff in here if you don't
# want to do the full Sys V style init stuff.

touch /var/lock/subsys/local

modprobe ibm_acpi experimental=1
echo enable > /proc/acpi/ibm/hotkey

The last line enables hotkeys. To utilize supsend to RAM or to disk, the acpid has to be configured.

==Suspend to disk==

To get suspend to disk working, fetch a recent kernel and recompile. For further instructions, take a look at the swsusp-Section in [[How to make ACPI work]]. Especially configure the kernel to suspend to the swap partition. If you're not sure, take a look at the partitition list output by issuing in command line
fdisk -l

Don't forget to compile SCSI and the Intel SATA into the kernel. Do a
make && make install
Check the boot loader (ususally grub) to include the new kernel.

Reboot and do a
echo -n 4 > /proc/acpi/sleep
If everything works, the system will be shut down to disk.

Installing Fedora Core 4 on a ThinkPad T43 (2668)

2005-07-16T21:11:41Z

Mrunge:

Installation is quite smooth, but requires some work by hand. I enlist only the changes

== X-Windows ==
Add the dynamic clock option in the xorg.conf. You find the file at
/etc/X11/xorg.conf
The device section should contain a videocard section like the folowing one:
Section "Device"
Identifier "Videocard0"
Driver "radeon"
VendorName "Videocard vendor"
BoardName "ATI Radeon Mobility M300"
'''Option "DynamicClocks" "on"'''
EndSection

==Network Installation==

lspci shows
04:02.0 Ethernet controller: Atheros Communications, Inc. AR5212 802.11abg NIC (rev 01)

I got the madwifi source code from [http://madwifi.sf.net MadWifi Home Page]. Compile after downloading
tar xzf madwifi-cvs-current.tar.gz
cd madwifi
make
su
make install

==IBM ACPI Module==

The included module version in current kernels (2.6.12) is 0.8, but the current version of the module is 0.11. It has some advantages. For directions on how to install this driver, please refer to [[Ibm-acpi]].
After compilation, edit /etc/rc.local:
#!/bin/sh
#
# This script will be executed *after* all the other init scripts.
# You can put your own initialization stuff in here if you don't
# want to do the full Sys V style init stuff.

touch /var/lock/subsys/local

modprobe ibm_acpi experimental=1
echo enable > /proc/acpi/ibm/hotkey

The last line enables hotkeys. To utilize supsend to RAM or to disk, the acpid has to be configured.

==Suspend to disk==

To get suspend to disk working, fetch a recent kernel and recompile. For further instructions, take a look at the swsusp-Section in [[How to make ACPI work]]. Especially configure the kernel to suspend to the swap partition. If you're not sure, take a look at the partitition list output by
fdisk -l

Don't forget to compile SCSI and the Intel SATA into the kernel. Do a
make && make install
Check the boot loader (ususally grub) to include the new kernel.

Reboot and do a
echo -n 4 > /proc/acpi/sleep
If everything works, the system will be shut down to disk.

Installing Fedora Core 4 on a ThinkPad T43 (2668)

2005-07-16T20:59:15Z

Mrunge:

Installation is quite smooth, but requires some work by hand. I enlist only the changes

== X-Windows ==
Add the dynamic clock option in the xorg.conf. You find the file at
/etc/X11/xorg.conf
The device section should contain a videocard section like the folowing one:
Section "Device"
Identifier "Videocard0"
Driver "radeon"
VendorName "Videocard vendor"
BoardName "ATI Radeon Mobility M300"
'''Option "DynamicClocks" "on"'''
EndSection

==Network Installation==

lspci shows
04:02.0 Ethernet controller: Atheros Communications, Inc. AR5212 802.11abg NIC (rev 01)

I got the madwifi source code from [http://madwifi.sf.net MadWifi Home Page]. Compile after downloading
tar xzf madwifi-cvs-current.tar.gz
cd madwifi
make
su
make install

==IBM ACPI Module==

The included module version in current kernels (2.6.12) is 0.8, but the current version of the module is 0.11. It has some advantages. For directions on how to install this driver, please refer to [[Ibm-acpi]].
After compilation, edit /etc/rc.local:
#!/bin/sh
#
# This script will be executed *after* all the other init scripts.
# You can put your own initialization stuff in here if you don't
# want to do the full Sys V style init stuff.

touch /var/lock/subsys/local

modprobe ibm_acpi experimental=1
echo enable > /proc/acpi/ibm/hotkey

==Suspend to disk==

To get suspend to disk working, fetch a recent kernel and recompile. For further instructions, take a look at the swsusp-Section in [[How to make ACPI work]].

Don't forget to compile SCSI and the Intel SATA into the kernel. Do a
make && make install
Check the boot loader (ususally grub) to include the new kernel.

Installing Fedora Core 4 on a ThinkPad T43 (2668)

2005-07-16T17:40:28Z

Mrunge: /* Network Installation */

Installing Fedora Core 4 on a ThinkPad T43 (2668)

2005-07-16T17:39:34Z

Mrunge:

Installation instructions for the ThinkPad T43

2005-07-16T17:14:26Z

Mrunge:

*[[:Category:Debian | Debian/Sarge]] [[Installing Debian/Sarge on a Thinkpad T43 | Installation]]
*[[:Category:Debian | Debian/Sid]] [[Installing Debian/Sid on a Thinkpad T43 | Installation]]
*[[:Category:Fedora | Fedora Core 4]] [[Installing Fedora Core 4 on a Thinkpad T43 | Installation]]
*[[:Category:Fedora | Fedora Core 4]] [[Installing Fedora Core 4 on a Thinkpad T43 (2668) | Installation]]

[[Category:T43]]