Installing openSUSE 10.2 on a ThinkPad X60 - Revision history

McCoy-Tyner: /* Kernel upgrade procedure */

2008-01-08T09:46:02Z

‎Kernel upgrade procedure

McCoy-Tyner: /* Activating the fingerprint reader */

2007-08-12T18:47:27Z

‎Activating the fingerprint reader

McCoy-Tyner: /* lscpi */

2007-08-12T17:50:41Z

‎lscpi

McCoy-Tyner: /* Automatic power switching for ipw3495 */

2007-07-11T14:28:15Z

‎Automatic power switching for ipw3495

McCoy-Tyner: /* Power consumption when running on battery */

2007-07-09T14:19:17Z

‎Power consumption when running on battery

McCoy-Tyner: /* Automatic power switching for ipw3495 */

2007-07-09T10:28:41Z

‎Automatic power switching for ipw3495

McCoy-Tyner: /* Automatic power switching for ipw3495 */

2007-07-09T06:23:55Z

‎Automatic power switching for ipw3495

McCoy-Tyner: /* Automatic power switching for ipw3495 */

2007-07-08T20:07:34Z

‎Automatic power switching for ipw3495

McCoy-Tyner: /* Automatic power switching for ipw3495 */

2007-07-08T20:06:59Z

‎Automatic power switching for ipw3495

McCoy-Tyner: /* Power consumption when running on battery */

2007-07-08T19:51:21Z

‎Power consumption when running on battery

← Older revision		Revision as of 09:46, 8 January 2008
Line 835:		Line 835:

	This is nothing but a plaster, however, this works for me.		This is nothing but a plaster, however, this works for me.
		+
		+	==== Autoloading of card reader module issue ====
		+	The module for the PC-Card reader is not autoloaded any more after the kernel upgrade. Therefore it is neccessary to either load it manually or let /etc/init.d/boot.local do the job.
		+
		+	The modified script /etc/init.d/boot.local is listed below:
		+
		+	#! /bin/sh
		+	#
		+	# Copyright (c) 2002 SuSE Linux AG Nuernberg, Germany. All rights reserved.
		+	#
		+	# Author: Werner Fink <werner@suse.de>, 1996
		+	# Burchard Steinbild, 1996
		+	#
		+	# /etc/init.d/boot.local
		+	#
		+	# script with local commands to be executed from init on system startup
		+	#
		+	# Here you should add things, that should happen directly after booting
		+	# before we're going to the first run level.
		+	#
		+	. /etc/rc.status
		+
		+	echo -n "Load SD/MC-Card controller ..."
		+	modprobe sdhci
		+	rc_status -v
		+
		+	This measure ensures that the module gets loaded and the card reader becomes usable.

	=== Power consumption when running on battery ===		=== Power consumption when running on battery ===

@@ Line 551: / Line 551: @@
 </code>
 in /etc/sysconfig/displaymanager.
 === Eject / reinsert the ULTRA-Bay ===

@@ Line 996: / Line 996: @@
 * Maximum battery life
-== lscpi ==
+== lspci ==
 <pre>&gt; lspci
 :00.0 Host bridge: Intel Corporation Mobile 945GM/PM/GMS/940GML and 945GT Express Memory Controller Hub (rev 03)

@@ Line 128: / Line 128: @@
 </code>
 Two lines have to be modified "on top" of this to make powersaved aware of it. The file that should be changed is /etc/sysconfig/powersave/events:
@@ Line 196: / Line 195: @@
 </code>
-The reason for this is simply explained. There are two other cases when you will need the power status checking. Given you perform a suspend2disk or suspend2ram with AC applied and you unplug the power after that, the corresponding event will not be recognized by powersaved. Therefore it is suggested to enter a reference to /usr/bin/ipw3945pwr in /etc/pm/hooks
+The script tries to detect the wireless interface automatically. Nevertheless, it is not designed to cope with more than one wireless network interface, if you add another one to your X60 unwanted side effects should be expected.
 <code>

@@ Line 843: / Line 843: @@
   CONFIG_HIGH_RES_TIMERS=y
   CONFIG_USB_SUSPEND=y
-  CONFIG_TIMER_STATS=y /* openSUSE default */
+  CONFIG_TIMER_STATS=y
   CONFIG_HPET_TIMER=y /* openSUSE default */
   CONFIG_HPET=y /* openSUSE default */

@@ Line 128: / Line 128: @@
 </code>
-The script tries to detect your wireless interface automatically. Nevertheless, it is not designed to cope with more than one wireless network interface, if you add another one, unwanted side effects should be expected.
+The script tries to detect the wireless interface automatically. Nevertheless, it is not designed to cope with more than one wireless network interface, if you add another one to your X60 unwanted side effects should be expected.
 Two lines have to be modified "on top" of this to make powersaved aware of it. The file that should be changed is /etc/sysconfig/powersave/events:
@@ Line 139: / Line 139: @@
 </code>
-"switch_wireless_mode" should be added to the EVENT_ACADAPTER_ONLINE and EVENT_ACADAPTER_OFFLINE as shown above. Given this, the x60 will switch to low power mode when running on battery and back to high power mode when running on mains automatically.
+"switch_wireless_mode" should be added to the EVENT_ACADAPTER_ONLINE and EVENT_ACADAPTER_OFFLINE as shown above. Given this, the ipw3945 will switch to low power mode when running on battery and back to high power mode when running on mains automatically.
-In addition it refers to another script actually doing the work that is called ipw3945pwr and is located in /usr/bin (in this example) that actually does the switching. The corresponding code is listed in the following paragraph. The file should be made executable in order to work.
+It refers to another script actually doing the work that is called ipw3945pwr and is located in /usr/bin (in this example) that actually does the switching. Scripts that are to be accessed from different locations should be reached within the path - therefore /usr/lib/powersave/scripts is not the right location. The corresponding code is listed in the following paragraph. The file should be made executable in order to work.
 <code>
@@ Line 222: / Line 222: @@
 </code>
-or
+or using the new script itself
 <code>
@@ Line 230: / Line 230: @@
 should make it clear whether everything works as expected, the return values should differ between mains plugged and mains unplugged. And unplugging after suspend and resuming should also work.
-One hint remains. On the X60 all of this has been tested sometimes the power unplug events do not work. Probably there is a bug in powersaved, the acpid creates an event, dbus catches it but it does not call powersaved accordingly. So, if you experience from time to time that the power switching of your wireless card does not work, you might consider the following scriptlett on top:
+One issue remains. On the X60 all of this has been tested sometimes the power plug/unplug events do not work. Probably there is a bug in powersaved, probably in dbus. Acpid creates an event, dbus catches it but it does not call powersaved accordingly. This can be seen from the logfiles. So, if you experience from time to time that the power switching of your wireless card does not work, you might consider the following scriptlett on top:
 <code>
@@ Line 274: / Line 274: @@
   done
 </code>
 This should be started in the background in /etc/init.d/boot.local and will check every 15 seconds whether the power settings are appropriate. Not the most elegant way, but it is functional.
 === Activating FN-F2 and FN-F7 ===

@@ Line 77: / Line 77: @@
 === Automatic power switching for ipw3495 ===
 This procedure can be automatized:
@@ Line 130: / Line 128: @@
 </code>
-The script tries to detect your wireless interface automatically. Nevertheless, it is not designed to cope with more than one wireless network interface, if you add another one, unwanted side effects could happen.
+The script tries to detect your wireless interface automatically. Nevertheless, it is not designed to cope with more than one wireless network interface, if you add another one, unwanted side effects should be expected.
 Two lines have to be modified "on top" of this to make powersaved aware of it. The file that should be changed is /etc/sysconfig/powersave/events:
@@ Line 143: / Line 141: @@
 "switch_wireless_mode" should be added to the EVENT_ACADAPTER_ONLINE and EVENT_ACADAPTER_OFFLINE as shown above. Given this, the x60 will switch to low power mode when running on battery and back to high power mode when running on mains automatically.
-In addition it refers to another script actually doing the work that is called ipw3945pwr and is located in /usr/bin (in this example) that actually does the switching. The corresponding code is listed here:
+In addition it refers to another script actually doing the work that is called ipw3945pwr and is located in /usr/bin (in this example) that actually does the switching. The corresponding code is listed in the following paragraph. The file should be made executable in order to work.
 <code>
@@ Line 198: / Line 196: @@
 </code>
-The reason for this is simply explained. There are two other cases when you will need the status checking. Given you perform a suspend2disk or suspend2ram with AC applied and you unplug the power after that, the corresponding event will not be recognized. Therefore it is suggested to enter a reference to /usr/bin/ipw3945pwr in /etc/pm/scripts
+The reason for this is simply explained. There are two other cases when you will need the power status checking. Given you perform a suspend2disk or suspend2ram with AC applied and you unplug the power after that, the corresponding event will not be recognized by powersaved. Therefore it is suggested to enter a reference to /usr/bin/ipw3945pwr in /etc/pm/hooks
-UNDER CONSTRUCTION
 Given that eth0 is the wireless interface, a test
@@ Line 206: / Line 222: @@
 </code>
-should make it clear whether everything works as expected, the return values should differ between mains plugged and mains unplugged. This does not work if you suspend your computer when connected to mains, unplug mains and wake it up again. But, I guess that this is not what I would call a characteristic or typical mode of operation.
+or
 === Activating FN-F2 and FN-F7 ===

← Older revision		Revision as of 20:07, 8 July 2007
Line 77:		Line 77:

	=== Automatic power switching for ipw3495 ===		=== Automatic power switching for ipw3495 ===
		+	UNDER CONSTRUCTION
		+
	This procedure can be automatized:		This procedure can be automatized:

@@ Line 108: / Line 108: @@
   # currently the interface name needs to be set manually.
+  #
+ # we call the script ipw3945pwr in order to set the power accordingly
-  IWPRIV="/usr/sbin/iwpriv"
+  # This is where all the main work is done:
-  IWCONFIG="/usr/sbin/iwconfig"
+  IPW3945PWR=/usr/bin/ipw3945pwr
   . ${0%/*}/helper_functions
-  if [ $EVENT_TYPE != ACADAPTER ]; then
+  if [ $EVENT_TYPE != "ACADAPTER" ]; then
       DEBUG "switch_wireless_mode only makes sense for acadapter events ;-)" WARN
   else
-      if [ "$1" = "acadapter.online" ]; then
+      # $1 can be acadapter.online or acadapter.offline, see $IPW3945PWR
-         ${IWPRIV} ${IF} ${MODEPARAM} ${POWERSCHEME}
+     # ${IPW3945PWR} "acadapter.test"
-     fi
+     ${IPW3945PWR} "$1"
   fi
   $SCRIPT_RETURN $EV_ID 0 "switch_wireless_mode finished"
   EXIT 0
 </code>
-Finally only two lines have to be modified "on top" of this to make powersaved aware of this script. The file that should be changed is /etc/sysconfig/powersave/events:
+The script tries to detect your wireless interface automatically. Nevertheless, it is not designed to cope with more than one wireless network interface, if you add another one, unwanted side effects could happen.
 <code>
@@ Line 145: / Line 141: @@
 "switch_wireless_mode" should be added to the EVENT_ACADAPTER_ONLINE and EVENT_ACADAPTER_OFFLINE as shown above. Given this, the x60 will switch to low power mode when running on battery and back to high power mode when running on mains automatically.
-The script tries to detect your wireless interface automatically. Nevertheless, it is not designed to cope with more than one wireless network interface, if you add another one, unwanted side effects could happen.
+In addition it refers to another script actually doing the work that is called ipw3945pwr and is located in /usr/bin (in this example) that actually does the switching. The corresponding code is listed here:
 Given that eth0 is the wireless interface, a test

@@ Line 737: / Line 737: @@
 To keep the power consumption low it is a good idea to uninstall the hsf-modem driver as it generates many wakeup events and hence a decent amount of power consumption. Moreover though zen is disabled there is one zen-updater Process creating regular wakeup events, killing it may also be beneficial with regard to the total power consumption of the device. Even if you disable novell-zmd in the system configuration this process keeps being started. You will recognize a red square with a cross in it after each and every restart of the desktop - wether you finalize it and store the session or you don't. This is something suse should consider fixing, this behaviour is annoying.
-To get rid of this one can uninstall the related rpm: rpm -e zen-updater will make opensuseupdater to take it's place. Apparently it is less power consuming, but one may simply uninstall this probram, too. rpm -e opensuse-updater (the dash  is neccessary) will remove this.
+To get rid of this one can uninstall the related rpm: rpm -e zen-updater will make opensuseupdater to take it's place. Apparently it is less power consuming, but one may simply uninstall this program, too. rpm -e opensuse-updater (the dash  is neccessary) will remove this.
 Emacs is a bad boy in this regard, too. It creates wakeup-events for the CPU. Therefore if you do not use it constantly it may be a good idea to turn it off.