Difference between revisions of "Installing Mandriva 2008 x86-64 Powerpack on a Thinkpad T61"

From ThinkWiki
Jump to: navigation, search
m (Suspend to RAM)
(Suspend to RAM)
 
(One intermediate revision by the same user not shown)
Line 1: Line 1:
I don't like the dual booting since I have have seen myself and others more often booting into MS Windows. So, I made the Rescue & Recovery CDs for Windows Vista Home Basic that came bundled with the system and installed Mandriva Powerpack x86-64 successfully on my Lenovo Thinkpad T61 6465-CTO.
+
Mandriva Powerpack x86-64 installs successfully on Lenovo Thinkpad T61.
  
Using the GNOME desktop environment, The problems I am facing are:
+
== Suspend to RAM ==
* Unable to successfully control the brightness using the brightness keys (Fn + Home/End)
+
If suspend to RAM does not work out of the box, then you need to install the pm-utils package if it wasn't already installed.
* After suspending & resuming successfully, the screen is blank. I have to switch to a virtual terminal (Ctrl+Alt+F12) and then switch back to X (Ctrl+Alt+F7)
+
 
* The wireless LED seems to shiver. I think it is constantly scanning for wireless networks. Having had Thinkpads with Linux in the past, I don't think this is normal.
+
To resolve the annoying issue of not being able to see the X session on VT 7 after a resume, Update the following file {{path|/usr/share/hal/fdi/information/10freedesktop/20-video-quirk-pm-lenovo.fdi}}
 +
<pre>
 +
      <!-- T60*, T61*, Z61* -->
 +
      <match key="system.hardware.version" prefix="ThinkPad ">
 +
        <match key="system.hardware.version" suffix="T60">
 +
          <merge key="power_management.quirk.s3_bios" type="bool">true</merge>
 +
          <merge key="power_management.quirk.s3_mode" type="bool">true</merge>
 +
        </match>
 +
        <match key="system.hardware.version" contains_outof="T60p;T61;Z61m;Z61t;Z60m">
 +
          <merge key="power_management.quirk.s3_bios" type="bool">true</merge>
 +
          <merge key="power_management.quirk.s3_mode" type="bool">true</merge>
 +
        </match>
 +
      </match>
 +
 
 +
</pre>
 +
 
 +
And restart HAL daemon to pick up the new configuration changes:
 +
{{cmdroot|service haldaemon restart}}
 +
 
 +
You can also query the HAL daemon to get more info about your system:
 +
<pre>
 +
lshal -l | grep system.hardware.vendor
 +
  system.hardware.vendor = 'LENOVO'  (string)
 +
lshal -l | grep system.hardware.version
 +
  system.hardware.version = 'ThinkPad T61'  (string)
 +
lshal -l | grep system.hardware.product
 +
  system.hardware.product = '6465CTO'  (string)
 +
</pre>
 +
 
 +
My system was taking forever to boot at startup and also resume from a suspend. In both cases, the culprit seemed to be the service 'network-up'. It looks for several keys in the network configuration files {{path|/etc/sysconfig/network-scripts/ifcfg-*}}. Update these as follows to speed things up and prevent seeing the "Waiting for network to be up    [FAILED]" message:
  
I also have Windows XP Professional installed inside VMWare Workstation 6
+
<pre>MII_NOT_SUPPORTED=no to MII_NOT_SUPPORTED=yes</pre>
  
----
+
I always wondered how Microsoft Windows could quickly suspend and resume instantaneously as I opened the laptop lid! Make the following change to {{path|/usr/share/pm-utils/functions}} to be able to resume just as quick in Linux.
The following is written by:--[[User:Gslt|Gslt]] 17:37, 13 January 2008 (CET)
 
  
== Suspend to RAM ==
 
On our Thinkpad T61 with the Intel GMA X3100 GM965 Intel and Mandriva 2008 Free, we needed to add the following into {{path|/usr/share/hal/fdi/information/10freedesktop/20-video-quirk-pm-lenovo.fdi}}
 
 
<pre>
 
<pre>
<match key="system.hardware.product" string="765912G">
+
pm_main()
  <merge key="power_management.quirk.s3_bios" type="bool">true</merge>
+
{
</match>
+
        if [ -n "$PM_LOGFILE" ]; then
 +
                [ -f "$PM_LOGFILE" ] && rm -f "$PM_LOGFILE"
 +
                exec > "$PM_LOGFILE" 2>&1
 +
        fi
 +
        take_suspend_lock || exit 1
 +
 
 +
        rm -f "$INHIBIT"
 +
 
 +
        run_hooks "$1"
 +
 
 +
        if [ ! -e "$INHIBIT" -a "$(type -t "do_$1")" == "function" ]; then
 +
                sync ; sync ; sync
 +
                "do_$1"
 +
        fi
 +
        remove_suspend_lock 200
 +
        run_hooks "$2" reverse
 +
 
 +
#      remove_suspend_lock 200                                                                                                                                                                                                             
 +
 
 +
        return 0
 +
}
 
</pre>
 
</pre>
{{cmdroot|service haldaemon restart}}
 
  
Replace the ''765912G'' with your product no, which can be obtained by doing
+
Notice that we are removing the suspend lock well before we run the suspend/resume scripts from {{path|/usr/share/pm-utils/sleep.d}}
<pre>lshal | grep system.hardware.product</pre>
+
 
 +
----
 +
 
 +
The following is written by:--Gslt 17:37, 13 January 2008 (CET)
 
We also tried to use {{bootparm|key|power_management.quirk.s3_mode}} but then the the backlight would be set to zero (0) when resuming from suspend.
 
We also tried to use {{bootparm|key|power_management.quirk.s3_mode}} but then the the backlight would be set to zero (0) when resuming from suspend.
  

Latest revision as of 13:49, 28 April 2008

Mandriva Powerpack x86-64 installs successfully on Lenovo Thinkpad T61.

Suspend to RAM

If suspend to RAM does not work out of the box, then you need to install the pm-utils package if it wasn't already installed.

To resolve the annoying issue of not being able to see the X session on VT 7 after a resume, Update the following file /usr/share/hal/fdi/information/10freedesktop/20-video-quirk-pm-lenovo.fdi

      <!-- T60*, T61*, Z61* -->
      <match key="system.hardware.version" prefix="ThinkPad ">
        <match key="system.hardware.version" suffix="T60">
          <merge key="power_management.quirk.s3_bios" type="bool">true</merge>
          <merge key="power_management.quirk.s3_mode" type="bool">true</merge>
        </match>
        <match key="system.hardware.version" contains_outof="T60p;T61;Z61m;Z61t;Z60m">
          <merge key="power_management.quirk.s3_bios" type="bool">true</merge>
          <merge key="power_management.quirk.s3_mode" type="bool">true</merge>
        </match>
      </match>

And restart HAL daemon to pick up the new configuration changes: # service haldaemon restart

You can also query the HAL daemon to get more info about your system:

lshal -l | grep system.hardware.vendor 
  system.hardware.vendor = 'LENOVO'  (string)
lshal -l | grep system.hardware.version
  system.hardware.version = 'ThinkPad T61'  (string)
lshal -l | grep system.hardware.product
  system.hardware.product = '6465CTO'  (string)

My system was taking forever to boot at startup and also resume from a suspend. In both cases, the culprit seemed to be the service 'network-up'. It looks for several keys in the network configuration files /etc/sysconfig/network-scripts/ifcfg-*. Update these as follows to speed things up and prevent seeing the "Waiting for network to be up [FAILED]" message:

MII_NOT_SUPPORTED=no to MII_NOT_SUPPORTED=yes

I always wondered how Microsoft Windows could quickly suspend and resume instantaneously as I opened the laptop lid! Make the following change to /usr/share/pm-utils/functions to be able to resume just as quick in Linux.

pm_main()
{
        if [ -n "$PM_LOGFILE" ]; then
                [ -f "$PM_LOGFILE" ] && rm -f "$PM_LOGFILE"
                exec > "$PM_LOGFILE" 2>&1
        fi
        take_suspend_lock || exit 1

        rm -f "$INHIBIT"

        run_hooks "$1"

        if [ ! -e "$INHIBIT" -a "$(type -t "do_$1")" == "function" ]; then
                sync ; sync ; sync
                "do_$1"
        fi
        remove_suspend_lock 200
        run_hooks "$2" reverse

#       remove_suspend_lock 200                                                                                                                                                                                                              

        return 0
}

Notice that we are removing the suspend lock well before we run the suspend/resume scripts from /usr/share/pm-utils/sleep.d


The following is written by:--Gslt 17:37, 13 January 2008 (CET) We also tried to use key=power_management.quirk.s3_mode but then the the backlight would be set to zero (0) when resuming from suspend.

A crude way to fix the backlight issue is to create a file /etc/pm/sleep.d/00crudebacklightfix with the following

#!/bin/bash
case $1 in
    hibernate)
        ;;
    suspend)
        ;;
    thaw)
        /usr/bin/chvt 1
        sleep 1
        /usr/bin/chvt 7
        ;;
    resume)
        /usr/bin/chvt 1
        sleep 1
        /usr/bin/chvt 7
        ;;
    *)  echo "somebody is calling me totally wrong."
        ;;
esac

# chmod +x /etc/pm/sleep.d/00crudebacklightfix