ThinkWiki - User contributions [en]

PreDesktop Area

2005-06-30T17:40:23Z

67.177.199.20: /* How to remove it */

{| width="100%"
|style="vertical-align:top;padding-right:20px;width:10px;" | [[Image:hpa.jpg|IBM PreDesktop Area]] __NOTOC__
|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;">
=== The PreDesktop Area ===
The Predesktop Area is part of the HPA (generally known as the "Host Protected Area", but called "Hidden Protected Area" by IBM). The HPA is a special area on your harddisk, usually hidden to partitioning tools. It includes all the software and data needed to recover the preloaded state of the ThinkPad. The HPA also includes some diagnostic tools and a (MS Windows only) backup tool.

The Predesktop area was introduced with the R/T/X 40 series of ThinkPads and is present on the preinstalled harddisks of all ThinkPads shipped by IBM since then.
</div>
|}
==General information about the HPA==
The HPA seems to be using [http://www.phoenix.com/en/Products/Trusted+Applications/Phoenix+FirstWare/default.htm Phoenix FirstWare]. FirstWare is (in short) an implementation of two technologies: BEER and PARTIES. (Yes, those names are correct!) BEER (Boot Engineering Extension Record) and PARTIES (Protected Area Run Time Interface Extension Services) are described in [http://www.t13.org/project/d1367r3-PARTIES.pdf this T13 working draft]. There is a more general introduction to PARTIES on the [http://www-1.ibm.com/support/docview.wss?rs=0&uid=psg1MIGR-51248&loc=en_US IBM site].

Basically, what seems to be going on is that the Phoenix BIOS hides the last few gigabytes of the harddisk (that is the HPA) to the OS. Note that this is just a setting in the BIOS and can be disabled. The HPA can be accessed by pressing the [[Access IBM Button]] at boot time. The BIOS will then parse the BEER (128 bytes, situated in the last sector of 512 bytes of the harddisk) and the "Directory of Services" (consisting of directory entries of 64 bytes each, starting in the last sector and spilling over into the previous sectors) to see what part of the HPA should be launched. In (most?) ThinkPads the BEER tells the BIOS to launch the Access IBM Predesktop Area. The system will then actually be booting into a (minimal) DOS which is able to launch a graphical shell (called Phoenix FirstSight). IBM has simply rebranded this graphical shell to the Access IBM Predesktop Area. From this graphical shell one can launch several tools (BIOS Setup Utility, diagnostic tools, recovery tools).

==Three BIOS options==
The BIOS has three settings for the "IBM Predesktop Area" (in the Security category):
*Secure: No user or SW-initiated changes
*Normal: Change allowed; Contents hidden from OS
*Disabled: Not Usable. Visible and Reclaimable

Normal and secure seem to behave identical when using GNU/Linux. Maybe changes are possible in "Normal" mode using an MS Windows application. With "Disabled" you can even remove the HPA.

==Details of the HPA==
Fabrice Bellet describes a [http://bellet.info/laptop/t40.html#the_predesktop_area technique he used] to explore the HPA of his ThinkPad T40, using GNU/Linux tools. This technique is only for the more curious or more careless people. It uses "dd" to copy the sectors on the harddisk containing the HPA from "/dev/hda" to a new file: when using "dd" on "/dev/hda" you are only one small typo away from an unrecoverable disaster!

Here follows a more detailed description of the HPA on a ThinkPad T41 (60 GB harddisk) to contrast his findings.

On this ThinkPad T41 the HPA is 3,4 GB in size. It contains 8 consecutive PSAs (Protected Service Areas). Six of those start with an x86 boot sector.

* The first PSA is 3,2 GB in size. The OEM-ID of the boot sector is: "IBM 7.1". It seems to hold a copy of the preloaded OS and everything needed to generate a bootable DVD-ROM for it, even an El Torito boot image and a boot catalog: see [[Backing up the preloaded OS]].

* The second PSA is exactly 2 MB in size. According to its entry in the Directory of Service it's the "BIOSWORKAREA".

* The third PSA is only 7,4 MB in size. The OEM-ID of the boot sector is: "MSWIN4.1". It seems to be an image of a 1,44 MB bootable floppy disk (with MS DOS) and a directory containig 6 MB of FirstWare tools. It will be launched by the "Recover to factory contents" tool of the Predesktop Area. Those "factory contents" should be the data on the first PSA.

* The fourth PSA is only 1,4 MB in size. The OEM-ID of the boot sector is: "IBM 7.1". It too seems to be an image of a (sort of) 1,44 MB bootable floppy disk. It will be launched by the "Restore your backups" tool of the Predesktop Area.

* The fifth PSA is again 7,4 MB in size. The OEM-ID of the boot sector is: "IBM 7.0". It will be launched by the "Run diagnostics" tool of the Predesktop Area.

* The sixth PSA is also 7,4 MB in size and the OEM-ID of the boot sector also is: "IBM 7.0". It will be launched by the "Create diagnostic disks" tool of the Predesktop Area. It contains a copy of a (sort of) bootable 1,44 MB floppy disk, some tools and compressed copies of the diagnostic disks.

* The seventh PSA is only 1,4 MB in size. The OEM-ID of the boot sector is "PHOENIX". It seems to be a copy of a (sort of) 1.44 MB bootable floppy disk too and only contains a (minimal) DOS and the FirstSight application. Basically, this is the Access IBM Predesktop Area.

* The eigth PSA is 101 MB in size. It doesn't have a boot sector. It contains the FirstWare Reserved Area. That probably is some sort of swap space for the FirstWare system.

==How to remove it==
There's a BIOS setting in my T42p. After disabling the Predesktop Area, it's possible to remove the partition with standard tools. i.e. fdisk, mkfs, ...

'''WARNING'''
Removing the HPA is simple to effect, but may result in your not being able to access the machine's BIOS. After removing the HPA on my x40, I can still dual boot into Windows and Linux without incident, but attempting to access the BIOS yields only a message "Missing operating system." So tread carefully.

==Alternative uses?==
It might be possible to use the FirstWare tools included in the HPA to make the HPA more useful for GNU/Linux purposes. For instance, the copy of the preloaded OS could be replaced with an emergency backup of your GNU/Linux distribution. Maybe the Predesktop area could be even used to boot into a GNU/Linux rescue system. Whether the Phoenix propietary tools really allow alternative uses and whether those tools do not make it too hard to accomplish those cannot yet be said. It seems realistic to assume that the benefits of those alternative uses aren't worth the effort to accomplish them. Still, it might be fun (altough possibly hazardous to your system) to try ...

==Related links==
*[http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-46023 Predesktop Area white paper]
*[http://www-3.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-46025 Predesktop Aministrator Utility (DOS)]
*[http://webstore.ansi.org/ansidocstore/product.asp?sku=ANSI+INCITS+346-2001 Protected Area Run Time Interface Extension Services (PARTIES) ANSI INCITS 346-2001 ($18)]
*[http://www.phoenix.com/NR/rdonlyres/7465D3CF-B0E3-4F64-9122-47D9C83028D0/0/cme_firstware_wp.pdf Phoenix FirstWare White Paper]
*[http://www.win.tue.nl/~aeb/linux/Large-Disk-11.html Section 11 of the Large Disk HOWTO (Clipped disks)]

==Models featuring this Technology==
*ThinkPad {{R40}}, {{R50}}, {{R50e}}, {{R50p}}, {{R51}}, {{R52}}
*ThinkPad {{T40}}, {{T40p}}, {{T41}}, {{T41p}}, {{T42}}, {{T42p}}, {{T43}}, {{T43p}}
*ThinkPad {{X31}}, {{X32}}, {{X40}}, {{X41}}

[[Category:Glossary]]

PreDesktop Area

2005-06-30T17:39:43Z

67.177.199.20: /* How to remove it */

{| width="100%"
|style="vertical-align:top;padding-right:20px;width:10px;" | [[Image:hpa.jpg|IBM PreDesktop Area]] __NOTOC__
|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;">
=== The PreDesktop Area ===
The Predesktop Area is part of the HPA (generally known as the "Host Protected Area", but called "Hidden Protected Area" by IBM). The HPA is a special area on your harddisk, usually hidden to partitioning tools. It includes all the software and data needed to recover the preloaded state of the ThinkPad. The HPA also includes some diagnostic tools and a (MS Windows only) backup tool.

The Predesktop area was introduced with the R/T/X 40 series of ThinkPads and is present on the preinstalled harddisks of all ThinkPads shipped by IBM since then.
</div>
|}
==General information about the HPA==
The HPA seems to be using [http://www.phoenix.com/en/Products/Trusted+Applications/Phoenix+FirstWare/default.htm Phoenix FirstWare]. FirstWare is (in short) an implementation of two technologies: BEER and PARTIES. (Yes, those names are correct!) BEER (Boot Engineering Extension Record) and PARTIES (Protected Area Run Time Interface Extension Services) are described in [http://www.t13.org/project/d1367r3-PARTIES.pdf this T13 working draft]. There is a more general introduction to PARTIES on the [http://www-1.ibm.com/support/docview.wss?rs=0&uid=psg1MIGR-51248&loc=en_US IBM site].

Basically, what seems to be going on is that the Phoenix BIOS hides the last few gigabytes of the harddisk (that is the HPA) to the OS. Note that this is just a setting in the BIOS and can be disabled. The HPA can be accessed by pressing the [[Access IBM Button]] at boot time. The BIOS will then parse the BEER (128 bytes, situated in the last sector of 512 bytes of the harddisk) and the "Directory of Services" (consisting of directory entries of 64 bytes each, starting in the last sector and spilling over into the previous sectors) to see what part of the HPA should be launched. In (most?) ThinkPads the BEER tells the BIOS to launch the Access IBM Predesktop Area. The system will then actually be booting into a (minimal) DOS which is able to launch a graphical shell (called Phoenix FirstSight). IBM has simply rebranded this graphical shell to the Access IBM Predesktop Area. From this graphical shell one can launch several tools (BIOS Setup Utility, diagnostic tools, recovery tools).

==Three BIOS options==
The BIOS has three settings for the "IBM Predesktop Area" (in the Security category):
*Secure: No user or SW-initiated changes
*Normal: Change allowed; Contents hidden from OS
*Disabled: Not Usable. Visible and Reclaimable

Normal and secure seem to behave identical when using GNU/Linux. Maybe changes are possible in "Normal" mode using an MS Windows application. With "Disabled" you can even remove the HPA.

==Details of the HPA==
Fabrice Bellet describes a [http://bellet.info/laptop/t40.html#the_predesktop_area technique he used] to explore the HPA of his ThinkPad T40, using GNU/Linux tools. This technique is only for the more curious or more careless people. It uses "dd" to copy the sectors on the harddisk containing the HPA from "/dev/hda" to a new file: when using "dd" on "/dev/hda" you are only one small typo away from an unrecoverable disaster!

Here follows a more detailed description of the HPA on a ThinkPad T41 (60 GB harddisk) to contrast his findings.

On this ThinkPad T41 the HPA is 3,4 GB in size. It contains 8 consecutive PSAs (Protected Service Areas). Six of those start with an x86 boot sector.

* The first PSA is 3,2 GB in size. The OEM-ID of the boot sector is: "IBM 7.1". It seems to hold a copy of the preloaded OS and everything needed to generate a bootable DVD-ROM for it, even an El Torito boot image and a boot catalog: see [[Backing up the preloaded OS]].

* The second PSA is exactly 2 MB in size. According to its entry in the Directory of Service it's the "BIOSWORKAREA".

* The third PSA is only 7,4 MB in size. The OEM-ID of the boot sector is: "MSWIN4.1". It seems to be an image of a 1,44 MB bootable floppy disk (with MS DOS) and a directory containig 6 MB of FirstWare tools. It will be launched by the "Recover to factory contents" tool of the Predesktop Area. Those "factory contents" should be the data on the first PSA.

* The fourth PSA is only 1,4 MB in size. The OEM-ID of the boot sector is: "IBM 7.1". It too seems to be an image of a (sort of) 1,44 MB bootable floppy disk. It will be launched by the "Restore your backups" tool of the Predesktop Area.

* The fifth PSA is again 7,4 MB in size. The OEM-ID of the boot sector is: "IBM 7.0". It will be launched by the "Run diagnostics" tool of the Predesktop Area.

* The sixth PSA is also 7,4 MB in size and the OEM-ID of the boot sector also is: "IBM 7.0". It will be launched by the "Create diagnostic disks" tool of the Predesktop Area. It contains a copy of a (sort of) bootable 1,44 MB floppy disk, some tools and compressed copies of the diagnostic disks.

* The seventh PSA is only 1,4 MB in size. The OEM-ID of the boot sector is "PHOENIX". It seems to be a copy of a (sort of) 1.44 MB bootable floppy disk too and only contains a (minimal) DOS and the FirstSight application. Basically, this is the Access IBM Predesktop Area.

* The eigth PSA is 101 MB in size. It doesn't have a boot sector. It contains the FirstWare Reserved Area. That probably is some sort of swap space for the FirstWare system.

==How to remove it==
There's a BIOS setting in my T42p. After disabling the Predesktop Area, it's possible to remove the partition with standard tools. i.e. fdisk, mkfs, ...

**WARNING**
Removing the HPA is simple to effect, but may result in your not being able to access the machine's BIOS. After removing the HPA on my x40, I can still dual boot into Windows and Linux without incident, but attempting to access the BIOS yields only a message "Missing operating system." So tread carefully.

==Alternative uses?==
It might be possible to use the FirstWare tools included in the HPA to make the HPA more useful for GNU/Linux purposes. For instance, the copy of the preloaded OS could be replaced with an emergency backup of your GNU/Linux distribution. Maybe the Predesktop area could be even used to boot into a GNU/Linux rescue system. Whether the Phoenix propietary tools really allow alternative uses and whether those tools do not make it too hard to accomplish those cannot yet be said. It seems realistic to assume that the benefits of those alternative uses aren't worth the effort to accomplish them. Still, it might be fun (altough possibly hazardous to your system) to try ...

==Related links==
*[http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-46023 Predesktop Area white paper]
*[http://www-3.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-46025 Predesktop Aministrator Utility (DOS)]
*[http://webstore.ansi.org/ansidocstore/product.asp?sku=ANSI+INCITS+346-2001 Protected Area Run Time Interface Extension Services (PARTIES) ANSI INCITS 346-2001 ($18)]
*[http://www.phoenix.com/NR/rdonlyres/7465D3CF-B0E3-4F64-9122-47D9C83028D0/0/cme_firstware_wp.pdf Phoenix FirstWare White Paper]
*[http://www.win.tue.nl/~aeb/linux/Large-Disk-11.html Section 11 of the Large Disk HOWTO (Clipped disks)]

==Models featuring this Technology==
*ThinkPad {{R40}}, {{R50}}, {{R50e}}, {{R50p}}, {{R51}}, {{R52}}
*ThinkPad {{T40}}, {{T40p}}, {{T41}}, {{T41p}}, {{T42}}, {{T42p}}, {{T43}}, {{T43p}}
*ThinkPad {{X31}}, {{X32}}, {{X40}}, {{X41}}

[[Category:Glossary]]

IBM Integrated Bluetooth III with 56K Modem (BMDC-2)

2005-06-19T07:35:05Z

67.177.199.20: /* 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 III with 56K Modem (BMDC-2) ===
This is a combination Bluetooth and Modem Adapter that is installed in a CDC slot.
=== Bluetooth Features ===
* Chipset: <br>
* USB ID: 1668:2441

=== Modem Features ===
* Chipset: Conexant
* AC'97 Modem
</div>
|}
=== IBM Partnumbers ===
IBM FRU PN: 91P7319

=== Also known (in IBM literature) as.... ===
* Integrated Bluetooth III with 56K Modem
* Integrated Bluetooth III with 56K Modem, Actiontec

=== Linux Bluetooth driver ===

This card will work with the standard Linux Bluetooth drivers as part of any recent 2.4 or 2.6 kernel; the HCI USB driver in particular is known to work.

This device is implemented as a USB device, which can be enabled or disabled with the {{key|Fn}}{{key|F5}} key combination

=== 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 ===
* {{R51}}
* {{T42}}, {{T42p}}
* {{X40}}

[[Category:Components]]

How to make ACPI work

2005-06-17T21:49:58Z

67.177.199.20: /* 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, go to <code>Power management options</code>, enable <code>Power Management support</code>, go to <code>ACPI</code> and enable the needed options. You'd most likely want to enable <code>Sleep States</code>, <code>AC Adapter</code>, <code>Battery</code>, <code>Fan</code>, <code>Processor</code> and <code>Thermal Zone</code>. Then recompile your kernel.

If you prefer editing your .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

===IBM specific ACPI driver===
Unfortunately, special drivers for ACPI on ThinkPads were not included with kernels prior 2.6.10.<br />
So you'll have to compile one yourself or get it as precompiled module for your kernel.<br />
You have the choice between [[thinkpad-acpi]] and [[ibm-acpi]], with the latter being the recommended one.<br />
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.<br />
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 XF86Config/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:
* With a 2.6.9 or 2.6.10 kernel, when resuming from a suspend-to-ram the display might remain black (the system is still rebootable via ctrl-alt-del). This can be fixed by adding <tt>acpi_sleep=s3_bios</tt> to the kernel boot parameters. It seems this problem is solved in 2.6.11-rc1.
* 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.
* 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].
* If your suspend is failing, and a tail of /var/log/acpid shows "Permission denied" errors, be sure that your new ACPI event and action scripts have the appropriate permissions

==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 it, go to <tt>Power management options</tt> and enable <tt>Power management support</tt> and <tt>Software Suspend</tt> in the kernel config menu. You'll also want to give the swap partition to suspend to in <tt>Default resume partition</tt>.

In case you prefer to edit your config file directly, you should have the following three entries look like here...
CONFIG_PM=y
CONFIG_SOFTWARE_SUSPEND=y
CONFIG_PM_STD_PARTITION="/dev/resume_partition"
...where <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 <tt>resume=/dev/resume_partition</tt> as kernel boot parameter.
Also, in case you suspended, but want to boot up normally (without resuming from the saved image - loosing all data that was unsaved at suspend time), you can give the <tt>noresume</tt> kernel boot parameter.

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 <tt>/etc/acpi/actions/hibernate.sh</tt>. 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://softwaresuspend.berlios.de/ if they are not already in your kernel. I am running 2.6.11-rc4-nitro in a Thinkpad T30 2366.

Be sure to also read the http://softwaresuspend.berlios.de/HOWTO.html

These are the options for the kernel. You can change the <tt>/dev/hda5</tt> to your swap partition

# 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/hda5"
# 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 <tt>resume2=swap:/dev/hda5</tt>. Again change <tt>/dev/hda5</tt> to your swap partition.

Install the hibernation script

For [[:Category:Gentoo | Gentoo]] users: emerge hibernate-script<br />
For [[:Category:Fedora_Core | Fedora Core]] 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://softwaresuspend.berlios.de/

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 /etc/mkinitrd/scripts directory before creating initrd image.

Restart using the new kernel and run the script to test it out.
/usr/sbin/hibernate

[[Category:570]] [[Category:570E]] [[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:X32]] [[Category:X40]] [[Category:X41]]