Installing SUSE 10 on a ThinkPad TransNote - Revision history

Wehe: added references section and link to TuxMobil

2007-07-20T09:19:37Z

added references section and link to TuxMobil

Ddouthitt: /* Power Management */ first text fix

2007-07-15T00:27:33Z

‎Power Management: first text fix

Ddouthitt: /* TPB */ Reworked text

2007-07-15T00:21:47Z

‎TPB: Reworked text

Markov at 23:27, 28 January 2006

2006-01-28T23:27:38Z

Wyrfel: /* Power Management */

2006-01-06T11:29:13Z

‎Power Management

Wyrfel: /* Power Management */

2006-01-06T11:27:41Z

‎Power Management

Wyrfel: /* Power Management */

2006-01-06T11:27:11Z

‎Power Management

Wyrfel: /* Power Management */

2005-11-15T07:53:12Z

‎Power Management

Wyrfel: /* TPB */

2005-11-01T23:35:42Z

‎TPB

Wyrfel: /* Power Management */

2005-11-01T23:35:19Z

‎Power Management

← Older revision		Revision as of 09:19, 20 July 2007
Line 25:		Line 25:
	*Powersaved complains about missing cpufreq support on boot. It might be good to switch to userspace frequency scaling. In {{path\|/etc/sysconfig/powersave/cpufreq}} adjust the following line:		*Powersaved complains about missing cpufreq support on boot. It might be good to switch to userspace frequency scaling. In {{path\|/etc/sysconfig/powersave/cpufreq}} adjust the following line:
	CPUFREQ_CONTROL="userspace"		CPUFREQ_CONTROL="userspace"
		+
		+	==References==
		+	* This guide is listed at the [http://tuxmobil.org/ibm.html TuxMobil Linux laptop and notebook installation guides survey (IBM/Lenovo)].

@@ Line 7: / Line 7: @@
 ==Power Management==
-SUSE 10, like any other SUSE version, uses powersaved for power management. powersaved attaches itself to [[acpid]] via a file socket, [[acpid]] is only running to forward all events to powersaved.
+SUSE 10, like any other SUSE version, uses the <tt>powersaved</tt> daemon for power management.<!-- powersaved attaches itself to [[acpid]] via a file socket, [[acpid]] is only running to forward all events to powersaved. -->
-While the basic PM functionalities work out of the box, it gets a bit tricky when you want to enable [[ibm-acpi]] and [[tpb]].
+While the basic power management capabilities work out of the box, it gets a bit tricky when you want to enable [[ibm-acpi]] and [[tpb]].
-SUSE 10 comes with a modified kernel 2.6.13, and has the individual ACPI support options compiled as modules. Trying different modules loading orders or including part of the modules into the kernel, didn't help making ibm-acpi work reliably. Hence the conclusion was to try and built a vanilla kernel.
+SUSE 10 comes with a modified Linux kernel 2.6.13, and has the individual ACPI support options compiled as modules. Trying different modules loading orders or including part of the modules into the kernel, didn't help making ibm-acpi work reliably. Hence the conclusion was to try and built a vanilla kernel.
-While doing so, kernel 2.6.14 was used and the ACPI option modules were built into the kernel.
+While doing so, Linux kernel 2.6.14 was used and the ACPI option modules were built into the kernel.
 Unpack the kernel source into {{path|/usr/src/}}, relink {{path|/usr/src/linux}} to point to {{path|/usr/src/linux-2.6.14}}. Copy the {{path|.config}} file from the old kernels source dir. Change into the new kernels source dir and configure the kernel to include processor, ac, battery, fan, thermal and button support rather than having it compiled as modules. Compile the kernel and copy the appropriate kernel image to the {{path|/boot}} directory. You need to copy {{path|System.map}} as well. Then edit {{path|/etc/sysconfig/kernel}} and adjust the line:
   INITRD_MODULES="piix reiserfs"

@@ Line 3: / Line 3: @@
 ==TPB==
-The <tt>nvram</tt> module doesn't get loaded by default. Hence you have to add it into the boot process yourself. In {{path|/etc/sysconfig/kernel}} adjust the following line:
+The <tt>nvram</tt> module doesn't get loaded by default. To make the <tt>nvram</tt> module load at boot time, edit the {{path|/etc/sysconfig/kernel}} file to contain this line:
   MODULES_LOADED_ON_BOOT="nvram"

@@ Line 23: / Line 23: @@
   ACPI_MODULES_NOT_TO_UNLOAD="ibm_acpi"
-*Powersaved complains about missing cpufreq support on boot. It might be good to switch to userspace frequency scaling. In {{path|/etc/sysconfig/cpufreq}} adjust the following line:
+*Powersaved complains about missing cpufreq support on boot. It might be good to switch to userspace frequency scaling. In {{path|/etc/sysconfig/powersave/cpufreq}} adjust the following line:
   CPUFREQ_CONTROL="userspace"

@@ Line 11: / Line 11: @@
 While the basic PM functionalities work out of the box, it gets a bit tricky when you want to enable [[ibm-acpi]] and [[tpb]].
-SUSE comes with a modified kernel 2.6.13, and has the individual ACPI support options compiled as modules. Trying different modules loading orders or including part of the modules into the kernel, didn't help making ibm-acpi to work reliably. Hence the conclusion was to try and built a vanilla kernel.
+SUSE 10 comes with a modified kernel 2.6.13, and has the individual ACPI support options compiled as modules. Trying different modules loading orders or including part of the modules into the kernel, didn't help making ibm-acpi work reliably. Hence the conclusion was to try and built a vanilla kernel.
 While doing so, kernel 2.6.14 was used and the ACPI option modules were built into the kernel.

@@ Line 1: / Line 1: @@
 This page tells about installation of {{SUSE}} on a ThinkPad {{TransNote}}.
 {{Todo|Introduction, general installation notes}}
 ==Power Management==
 SUSE 10, like any other SUSE version, uses powersaved for power management. powersaved attaches himself to acpid via a file socket, acpid is only running to forward all events to powersaved.
-While the basic PM functionalities work out of the box, it gets a bit tricky when you want to enable [[ibm-acpi]] and [[tpb]]. Yes, tpb - the strange thing is that if something goes wrong with the ibm_acpi support, tpb will stop working.
+While the basic PM functionalities work out of the box, it gets a bit tricky when you want to enable [[ibm-acpi]] and [[tpb]].
-Since SUSE has the individual ACPI support options compiled as modules, it is important that these modules get loaded in the right order. To assure that, you will need to do the following changes to some files in {{path|/etc/sysconfig}}. You can either manually edit the files or use the YAST2 interface to set the variables.
+SUSE comes with a modified kernel 2.6.13, and has the individual ACPI support options compiled as modules. Trying different modules loading orders or including part of the modules into the kernel, didn't help making ibm-acpi to work reliably. Hence the conclusion was to try and built a vanilla kernel.
-*It is important to load ibm_acpi after battery and ac and nvram after ibm_acpi. Also, doing this in <tt>ACPI_MODULES</tt> doesn't work for some reason. Hence, in {{path|/etc/sysconfig/kernel}} adjust the following lines:
+While doing so, kernel 2.6.14 was used and the ACPI option modules were built into the kernel.
-  MODULES_LOADED_ON_BOOT="battery ac button ibm_acpi nvram"
+Unpack the kernel source into {{path|/usr/src/}}, relink {{path|/usr/src/linux}} to point to {{paht|/usr/src/linux-2.6.14}}. Copy the {{path|.config}} file from the old kernels source dir. Change into the new kernels source dir and configure the kernel to include processor, ac, battery, fan, thermal and button support rather than having it compiled as modules. Compile the kernel and copy the appropriate kernel image to the {{path|/boot}} directory. You need to copy {{path|System.map}} as well. Then edit {{path|/etc/sysconfig/kernel}} and adjust the line:
-*Also make sure that ibm_acpi is never unloaded, since it would cause trouble. In {{path|/etc/sysconfig/powersave/common}} adjust the following lines:
+*Also make sure that ibm_acpi is never unloaded, since it would cause trouble. In {{path|/etc/sysconfig/powersave/common}} adjust the following line:
-  ACPI_MODULES_NOT_TO_UNLOAD="ibm_acpi ac battery button fan processor thermal"
+  ACPI_MODULES_NOT_TO_UNLOAD="ibm_acpi"
 *Powersaved complains about missing cpufreq support on boot. It might be good to switch to userspace frequency scaling. In {{path|/etc/sysconfig/cpufreq}} adjust the following line:
   CPUFREQ_CONTROL="userspace"