ThinkWiki - User contributions [en]

Problem with display remaining black after resume

2006-06-22T17:56:47Z

BrianTung: /* Solution for ThinkPads with ATI graphic chips (or Intel 915GM) */ (the cited HAL workaround does not work on all machines)

There has been a problem encountered where the display stays black on resuming from suspend.

The symptom might have you think first that your system hang up, but you will realize that your ThinkPad works and you can even reset it via {{key|Ctrl}}{{key|Alt}}{{key|Del}}.

==Affected Models==
*ThinkPad {{T41p}}, {{T42}}, {{T42p}}, {{T43}}, {{T43p}}
*Thinkpad {{T23}}
*ThinkPad {{X21}}, {{X30}}, {{X31}}, {{X40}}, {{X41}}
*ThinkPad {{R31}}, {{R50e}}{{footnote|1}}, {{R50p}}, {{R51}} (with BIOS 1.11), {{R52}}
*ThinkPad {{A30p}}
*ThinkPad {{390X}} (doesn't wake up; LCD backlight on, harddrive light remains on)
*ThinkPad {{Z60t}}, {{Z60m}}

==Affected Operating Systems==
*Linux (it's a kernel issue)

==Solutions==
===Solution for ThinkPads with 1400x1050 internal LCD and Intel 915GM ===
see [[1400x1050 on Intel 915GM]].
===Solution for ThinkPads with ATI graphic chips (or Intel 915GM)===
One solution may be to provide the {{bootparm|acpi_sleep|s3_bios}} kernel parameter in your kernel parameter line.

For grub this would look like this:

title Linux, kernel 2.6.11-1-686
root (hd0,0)
kernel /boot/vmlinuz-2.6.11-1-686 root=/dev/hda1 ro acpi_sleep=s3_bios
initrd /boot/initrd.img-2.6.11-1-686
savedefault
boot

For lilo it would look like this:

image=/boot/vmlinuz
append="acpi_sleep=s3_bios"

The actual process of going to sleep is then managed through a sleep script; as a start, see the {{path|sleep.sh}} script in the Extreme Graphics 2 section below, but note the following comments:

In [[:Category:OpenSUSE|OpenSUSE]] 10.1 (at least on a T43p), it's necessary to override the default options for s2ram if you're using the newer ATI driver. This can be done putting {{bootparm|SUSPEND2RAM_FORCE|"yes"}} and {{bootparm|SUSPEND2RAM_ACPI_SLEEP|"3"}} in {{path|/etc/powersave/sleep}}.

In {{Ubuntu}} or {{Kubuntu}}, it may be necessary to modify {{path|/etc/default/acpi-support}}. In that file, make sure that {{path|ACPI_SLEEP}} is uncommented and set to true. With ATI chips, also make sure that {{path|SAVE_VBE_STATE}} is uncommented and set to true; with Intel chips, on the other hand, ensure that nothing is done with respect to VBE--no reposts, no state saves.

In {{Fedora}}, it may be necessary with the Intel chips to edit the {{path|resume_video()}} function in {{path|/etc/pm/functions-intel}} to comment out the VBE post and restore. Also, the laptop, after waking up, may go back to sleep immediately or whenever the AC adapter is disconnected. When this happens, it's caused by a bug in the HAL daemon that incorrectly reports certain ACPI events. This is a known problem and a simple workaround is described [http://live.gnome.org/GnomePowerManager/Faq#head-b8b1280115b0a51c2cc27b13a57121130ebf36cb here].

{{NOTE|It is possible this method will not work if the laptop is docked. It is also possible that the cited workaround for the HAL daemon bug will not work on some machines. A kludgier workaround in this event is to kill the HAL daemon on suspend. This necessitates the resuscitation of GPM upon resume.}}

Another solution is to use vbetool. If you are using {{Debian}} with the hibernate package, uncomment "EnableVbetool yes" in {{path|/etc/hibernate/hibernate.conf}} (or {{path|/etc/hibernate/ram.conf}}).

===Solution for ThinkPads with Intel Extreme Graphics 2===
{{NOTE|
On [[:Category:X40|X40]]s/[[:Category:X41|X41]]s - even with Intel Extreme Graphics - and for [[:Category:R52|R52]]s with Intel Graphics Media Accelerator 900 the [[Problem with display remaining black after resume#Solution for ThinkPads with ATI graphic chips|solution for ATI graphics chips]] above is reported to work. In this case, make sure no changes to VBE are made, especially no state saves and no reposts.}}

The following solution should work on 865G, 865GV, 855GM, 855GME, 852GME chipsets.
*First of all, '''do not''' use the {{bootparm|acpi_sleep|s3_bios}} kernel parameter.
*Second, completely remove framebuffer support from your kernel. If it's built as modules, it is important that they do not get loaded at all.
*Before suspending, change to a console and safe the video state with {{cmdroot|cat /proc/bus/pci/00/02.0 > /tmp/video_state}}.
*On resume, restore the video state with {{cmdroot|cat /tmp/video_state > /proc/bus/pci/00/02.0}} and change back to X.
*For a R50e the only thing needed to make suspend to ram work in Ubuntu 6.06 is adding
Option "VBERestore" "yes"
to the <tt>Device</tt> section in your {{path|/etc/X11/xorg.conf}}, and the example script below.

The following example {{path|/etc/acpi/actions/sleep.sh}} script shows how to integrate the according lines.

#!/bin/bash

# change to console 1
FGCONSOLE=`fgconsole`
chvt 6

# safe video state
cat /proc/bus/pci/00/02.0 > /tmp/video_state

# sync filesystem
sync

# sync hardware clock with system time
hwclock --systohc

# go to sleep
echo -n 3 > /proc/acpi/sleep

# waking up
# restore system clock
hwclock --hctosys

# restore video state
cat /tmp/video_state > /proc/bus/pci/00/02.0

# change back to X
chvt $FGCONSOLE

# clean up behind us
rm /tmp/video_state

===Solution for ThinkPads with Intel I830 Chipset===
The following solution worked for me on an X30 with I830M chipset with kernel >= 2.6.16.
*this works with vesafb and also with intelfb frambuffer support.
The following example {{path|/etc/acpi/actions/sleep.sh}} script shows how to integrate the according lines.

#!/bin/bash

FGCONSOLE=`fgconsole`
chvt 8
sync
hwclock --systohc

echo -n "mem" > /sys/power/state

hwclock --hctosys
vbetool post

if [ "$FGCONSOLE" -ge "7" ] ; then
chvt $FGCONSOLE
else
chvt 7
chvt $FGCONSOLE
fi

{{footnotes|
#If you have this problem with R50e and the above solution doesn't work, try switching to console first. An example sleep script can be found [[How to configure acpid|here]].
}}

Talk:Problem with display remaining black after resume

2006-06-22T17:54:22Z

BrianTung: /* X41 with an Intel 915GM Integrated Graphics Device */

== T43 with Intel Graphics Media Accelerator ==

My T43 (1871-FYG) with Intel 915GM is also affected by the problem and the 'ATI' sollution with
acpi_sleep=s3_bios works. Please consider updating the page (I don't dare to do it myself).

== From my experience, this does not work with TP R50e. ==

If you want to be able to resume, you need :
* To start from a VT
* No option acpi_sleep
* to save the PCI state like:
cat /proc/bus/pci/00/02.0 > /var/cache/video.config
* Once you get back, restore it:
cat /var/cache/video.config > /proc/bus/pci/00/02.0

However, the X screen is not clean after the restore, so this is not very useable...

== The comment on R50e ==

There is a comment at the end of the page on R50e, saying that you should switch to console first, and look at a page to learn how to do this.

However. it seems to me that the given script already does it. Should the comment be removed?
----
The scripts are different. However, if you can approve that the solution provided on this page resolves the problem, please remove the footnote.

[[User:Wyrfel|Wyrfel]] 14:46, 17 Oct 2005 (CEST)
----
On my R50e, the script on this page works fine, while the one linked in the footnote quickly wakes up from sleep.

[[User:Thisnukes4u|Thisnukes4u]] 19:39, 1 Jan 2006 (CET)

== Problems with R51 and Intel Graphics ==

The problems described on the page occur intermittently
with an Intel Graphics card on an R51. Here is what happens:

1. One some occassions everything seems to work fine.

2. On other occassions the screen looks OK but the some plane seems to have vanished. New text on the screen overwrites instead of replaces prior text. The "standard" pattern disappears from the X background.

3. On yet other occassions the X server dies and comes out "blank" in the mode (2) above.

4. The above problems appear only with the "i810" driver. The "vesa" driver works fine. Moreover, if the machine is "suspend-to-disk"ed then the problem disappears on resumption once the X server is killed and re-started.

But for 1 and 4 above I would have given up and either avoided suspend to ram altogether or used vesa mode---as it stands the problem is tantalising.

Kapil kapil at imsc dot res dot in

== X40 with an Intel 855GM Integrated Graphics Device ==

I used the {{bootparm|acpi_sleep|s3_bios}} boot parameter and the following ACPI script:

#!/bin/sh
set -e

vt=`fgconsole`
chvt 12
echo mem >/sys/power/state
vbetool post
chvt $vt

The {{bootparm|acpi_sleep|s3_bios}} boot parameter alone did not fix things, and neither did saving and restoring the information from {{path|/proc/bus/pci/00/02.0}}.

== X41 with an Intel 915GM Integrated Graphics Device ==

It works with the {{bootparm|acpi_sleep|s3_bios,s3_mode}} boot parameter. Resume works great, both on the VESA console and in X.

:Interesting--that didn't work for me. I needed to do several things to get it to work. First, I used s3_bios, but not s3_mode. Secondly, I had to edit resume_video() in /etc/pm/functions-intel to comment out the VBE post and restore. Those two changes made it functional, but the improper lid state in the HAL daemon caused it to go back to sleep just as soon as it resumed upon the lid opening, so I added a HAL restart to the front end of /etc/acpi/actions/sleep.sh. This means that I have to restart gnome-power-manager, too. I haven't yet figured out a way to do that in sleep.sh; currently I do it manually. I'll post this to the main page soon, unless I hear comments to the contrary. [[User:BrianTung|BrianTung]] 19:52, 30 April 2006 (CEST) (fixed a little)

:(gsaito): I used the {{bootparm|acpi_sleep|s3_bios,s3_mode}} boot parameter and it worked perfectly, entering Suspend to RAM and resuming perfectly. No more blank screens after resuming. No need for any other change as described above, at least in my case. I also have an X41 with Intel 915GM graphics adapter. I use OpenSUSE v.10.0.

I read the edit by Uberpenguin and tried the stated fix. No go: The next time I pulled out the adapter after a resume--boom, the machine goes straight back to sleep again. Evidently, the suggested workaround does not work on all machines. [[User:BrianTung|BrianTung]] 19:54, 22 June 2006 (CEST)

== Z60t with an Intel 915GM Integrated Graphics Device (PCI Express) ==

It works with the {{bootparm|acpi_sleep|s3_bios}} boot parameter. Here is the script I use (gentoo). Note: stopping and starting WiFi is not necessary to resume, but it is dead on resume until restarted and the module is reloaded. This is on a 2.6.15.4 kernel with framebuffer console support. The blinking led thing is a nice touch I got from the hibernate-scripts package - it blinks the sleep led (moon icon) until the sleep or resume cycle is finished.

The 'vbetool vbemode get/set' commands are for saving and restoring the console text mode - otherwise the screen becomes garbled.

#!/bin/bash

# blink sleep led (if ibm_acpi is installed)
echo 7 blink > /proc/acpi/ibm/led

# change to console 10 (unused?)
FGCONSOLE=`fgconsole`
chvt 10

# save video state
VBEMODE=`vbetool vbemode get`
cat /proc/bus/pci/00/02.0 > /tmp/video_state

# sync filesystem
sync

# sync hardware clock with system time
hwclock --systohc

# stop networking (atheros chipset)
/etc/init.d/net.ath0 stop
rmmod ath_pci

# go to sleep
sleep 2 ; echo -n 3 > /proc/acpi/sleep

# blink sleep led
echo 7 blink > /proc/acpi/ibm/led

# restore system clock
hwclock --hctosys

# restore video state
vbetool vbemode set $VBEMODE
cat /tmp/video_state > /proc/bus/pci/00/02.0

# change back to X
chvt $FGCONSOLE

# restart networking
modprobe ath_pci
/etc/init.d/net.ath0 start

# clean up behind us
rm /tmp/video_state
echo 7 off > /proc/acpi/ibm/led

== Fedora Core 5 ==

The vbetool on the article page worked great for me, but NetworkManager would not bring the wireless interface back up. I had to add "ath_pci" to the SUSPEND_MODULES variable in /etc/sysconfig/pm.

Talk:How to configure the TrackPoint

2006-06-03T23:17:03Z

BrianTung: Directory structure in FC5 (2.6.15+) at variance with description in article

On {{Fedora}} 5, with kernels 2.6.15 and forward, the path does not include {{path|serio2}}; it stops at {{path|serio0}}.

2005-11-07
OpenSuSE 10.0 has a kernel based on 2.6.13 (probably heavily patched), but the directory /sys/devices/platform/i8042/serio0/serio2 does not exist.
instead, it looks like this:
hoppetosse:/sys/devices/platform/i8042/serio0 # ls -l
total 0
-rw-r--r-- 1 root root 4096 Nov 7 18:38 bind_mode
lrwxrwxrwx 1 root root 0 Nov 7 18:38 bus -> ../../../../bus/serio
-r--r--r-- 1 root root 4096 Nov 7 18:38 description
lrwxrwxrwx 1 root root 0 Nov 7 18:38 driver -> ../../../../bus/serio/drivers/psmouse
--w------- 1 root root 4096 Nov 7 18:38 drvctl
drwxr-xr-x 2 root root 0 Nov 7 18:38 id
-r--r--r-- 1 root root 4096 Nov 7 18:38 modalias
drwxr-xr-x 2 root root 0 Nov 7 18:38 power
-rw-r--r-- 1 root root 4096 Nov 7 18:38 protocol
-rw-r--r-- 1 root root 4096 Nov 7 18:38 rate
-rw-r--r-- 1 root root 4096 Nov 7 18:38 resetafter
-rw-r--r-- 1 root root 4096 Nov 7 18:38 resolution
"description" says it's an "i8042 Aux Port". The page [[Patch to enable advanced trackpoint control]] seems to imply that a kernel patch is needed in order to get those features... this needs clarification.
hmm. where can i find out whether "drvctrl" is what i'm looking for and what options it takes? guess it's back to RTFS...

2005-10-06
It seems that new version of the patch ( 2.6.12 at least ), the press to select entry in /sys is named "press_to_select" and not "ptson". I changed the page accordingly so that it complies with the [[Patch to enable advanced trackpoint configuration]] page.
If you use an older version try :

===Press to Select===
Press to Select allows you to tap the control stick which will simulate a left click. You can enable this feature by typing the following in to a terminal (you may need to be root):

:{{cmdroot|echo 1 > /sys/devices/platform/i8042/serio0/ptson}}

Press to Select should now be enabled. You can disable it in a similar manner:

:{{cmdroot|echo 0 > /sys/devices/platform/i8042/serio0/ptson}}

Problem with display remaining black after resume

2006-05-19T17:52:17Z

BrianTung: typo

There has been a problem encountered where the display stays black on resuming from suspend.

The symptom might have you think first that your system hang up, but you will realize that your ThinkPad works and you can even reset it via {{key|Ctrl}}{{key|Alt}}{{key|Del}}.

==Affected Models==
*ThinkPad {{T41p}}, {{T42}}, {{T42p}}, {{T43}}, {{T43p}}
*Thinkpad {{T23}}
*ThinkPad {{X21}}, {{X30}}, {{X31}}, {{X40}}, {{X41}}
*ThinkPad {{R31}}, {{R50e}}{{footnote|1}}, {{R50p}}, {{R51}} (with BIOS 1.11), {{R52}}
*ThinkPad {{A30p}}
*ThinkPad {{390X}} (doesn't wake up; LCD backlight on, harddrive light remains on)
*ThinkPad {{Z60t}}, {{Z60m}}

==Affected Operating Systems==
*Linux (it's a kernel issue)

==Solutions==
===Solution for ThinkPads with 1400x1050 internal LCD and Intel 915GM ===
see [[1400x1050 on Intel 915GM]].
===Solution for ThinkPads with ATI graphic chips (or Intel 915GM)===
One solution may be to provide the {{bootparm|acpi_sleep|s3_bios}} kernel parameter in your kernel parameter line.

For grub this would look like this:

title Linux, kernel 2.6.11-1-686
root (hd0,0)
kernel /boot/vmlinuz-2.6.11-1-686 root=/dev/hda1 ro acpi_sleep=s3_bios
initrd /boot/initrd.img-2.6.11-1-686
savedefault
boot

For lilo it would look like this:

image=/boot/vmlinuz
append="acpi_sleep=s3_bios"

The actual process of going to sleep is then managed through a sleep script; as a start, see the {{path|sleep.sh}} script in the Extreme Graphics 2 section below, but note the following comments:

In [[:Category:OpenSUSE|OpenSUSE]] 10.1 (at least on a T43p), it's necessary to override the default options for s2ram if you're using the newer ATI driver. This can be done putting {{bootparm|SUSPEND2RAM_FORCE|"yes"}} and {{bootparm|SUSPEND2RAM_ACPI_SLEEP|"3"}} in {{path|/etc/powersave/sleep}}.

In {{Ubuntu}} or {{Kubuntu}}, it may be necessary to modify {{path|/etc/default/acpi-support}}. In that file, make sure that {{path|ACPI_SLEEP}} is uncommented and set to true. With ATI chips, also make sure that {{path|SAVE_VBE_STATE}} is uncommented and set to true; with Intel chips, on the other hand, ensure that nothing is done with respect to VBE--no reposts, no state saves.

In {{Fedora}}, it may be necessary with the Intel chips to edit the {{path|resume_video()}} function in {{path|/etc/pm/functions-intel}} to comment out the VBE post and restore. Also, the laptop, after waking up, may go back to sleep whenever the AC adapter is disconnected. When this happens, it's caused by a bug in the HAL daemon that incorrectly reports the lid as closed ({{path|lshal}} returns {{bootparm|button.state.value|true}}, among other things). The simplest way to resolve this is to add a line to the sleep script to restart the HAL daemon ''before'' sleeping the machine:

# restart the HAL daemon
service haldaemon restart

If you use {{path|gnome-power-manager}}, restarting HAL will kill it, unfortunately, so you'll have to restart it.

{{NOTE|It is possible this method will not work if the laptop is docked.}}

Another solution is to use vbetool. If you are using {{Debian}} with the hibernate package, uncomment "EnableVbetool yes" in {{path|/etc/hibernate/hibernate.conf}} (or {{path|/etc/hibernate/ram.conf}}).

===Solution for ThinkPads with Intel Extreme Graphics 2===
{{NOTE|
On [[:Category:X40|X40]]s/[[:Category:X41|X41]]s - even with Intel Extreme Graphics - and for [[:Category:R52|R52]]s with Intel Graphics Media Accelerator 900 the [[Problem with display remaining black after resume#Solution for ThinkPads with ATI graphic chips|solution for ATI graphics chips]] above is reported to work. In this case, make sure no changes to VBE are made, especially no state saves and no reposts.}}

The following solution should work on 865G, 865GV, 855GM, 855GME, 852GME chipsets.
*First of all, '''do not''' use the {{bootparm|acpi_sleep|s3_bios}} kernel parameter.
*Second, completely remove framebuffer support from your kernel. If it's built as modules, it is important that they do not get loaded at all.
*Before suspending, change to a console and safe the video state with {{cmdroot|cat /proc/bus/pci/00/02.0 > /tmp/video_state}}.
*On resume, restore the video state with {{cmdroot|cat /tmp/video_state > /proc/bus/pci/00/02.0}} and change back to X.
The following example {{path|/etc/acpi/actions/sleep.sh}} script shows how to integrate the according lines.

#!/bin/bash

# change to console 1
FGCONSOLE=`fgconsole`
chvt 6

# safe video state
cat /proc/bus/pci/00/02.0 > /tmp/video_state

# sync filesystem
sync

# sync hardware clock with system time
hwclock --systohc

# go to sleep
echo -n 3 > /proc/acpi/sleep

# waking up
# restore system clock
hwclock --hctosys

# restore video state
cat /tmp/video_state > /proc/bus/pci/00/02.0

# change back to X
chvt $FGCONSOLE

# clean up behind us
rm /tmp/video_state

===Solution for ThinkPads with Intel I830 Chipset===
The following solution worked for me on an X30 with I830M chipset with kernel >= 2.6.16.
*this works with vesafb and also with intelfb frambuffer support.
The following example {{path|/etc/acpi/actions/sleep.sh}} script shows how to integrate the according lines.

#!/bin/bash

FGCONSOLE=`fgconsole`
chvt 8
sync
hwclock --systohc

echo -n "mem" > /sys/power/state

hwclock --hctosys
vbetool post

if [ "$FGCONSOLE" -ge "7" ] ; then
chvt $FGCONSOLE
else
chvt 7
chvt $FGCONSOLE
fi

{{footnotes|
#If you have this problem with R50e and the above solution doesn't work, try switching to console first. An example sleep script can be found [[How to configure acpid|here]].
}}

Problem with display remaining black after resume

2006-05-19T17:50:02Z

BrianTung: more text cleanup in ATI/Intel 915 section

There has been a problem encountered where the display stays black on resuming from suspend.

The symptom might have you think first that your system hang up, but you will realize that your ThinkPad works and you can even reset it via {{key|Ctrl}}{{key|Alt}}{{key|Del}}.

==Affected Models==
*ThinkPad {{T41p}}, {{T42}}, {{T42p}}, {{T43}}, {{T43p}}
*Thinkpad {{T23}}
*ThinkPad {{X21}}, {{X30}}, {{X31}}, {{X40}}, {{X41}}
*ThinkPad {{R31}}, {{R50e}}{{footnote|1}}, {{R50p}}, {{R51}} (with BIOS 1.11), {{R52}}
*ThinkPad {{A30p}}
*ThinkPad {{390X}} (doesn't wake up; LCD backlight on, harddrive light remains on)
*ThinkPad {{Z60t}}, {{Z60m}}

==Affected Operating Systems==
*Linux (it's a kernel issue)

==Solutions==
===Solution for ThinkPads with 1400x1050 internal LCD and Intel 915GM ===
see [[1400x1050 on Intel 915GM]].
===Solution for ThinkPads with ATI graphic chips (or Intel 915GM)===
One solution may be to provide the {{bootparm|acpi_sleep|s3_bios}} kernel parameter in your kernel parameter line.

For grub this would look like this:

title Linux, kernel 2.6.11-1-686
root (hd0,0)
kernel /boot/vmlinuz-2.6.11-1-686 root=/dev/hda1 ro acpi_sleep=s3_bios
initrd /boot/initrd.img-2.6.11-1-686
savedefault
boot

For lilo it would look like this:

image=/boot/vmlinuz
append="acpi_sleep=s3_bios"

The actual process of going to sleep is then managed through a sleep script; as a start, see the {{path|sleep.sh}} script in the Extreme Graphics 2 section below, but note the following comments:

In [[:Category:OpenSUSE|OpenSUSE]] 10.1 (at least on a T43p), it's necessary to override the default options for s2ram if you're using the newer ATI driver. This can be done putting {{bootparm|SUSPEND2RAM_FORCE|"yes"}} and {{bootparm|SUSPEND2RAM_ACPI_SLEEP|"3"} in {{path|/etc/powersave/sleep}}.

In {{Ubuntu}} or {{Kubuntu}}, it may be necessary to modify {{path|/etc/default/acpi-support}}. In that file, make sure that {{path|ACPI_SLEEP}} is uncommented and set to true. With ATI chips, also make sure that {{path|SAVE_VBE_STATE}} is uncommented and set to true; with Intel chips, on the other hand, ensure that nothing is done with respect to VBE--no reposts, no state saves.

In {{Fedora}}, it may be necessary with the Intel chips to edit the {{path|resume_video()}} function in {{path|/etc/pm/functions-intel}} to comment out the VBE post and restore. Also, the laptop, after waking up, may go back to sleep whenever the AC adapter is disconnected. When this happens, it's caused by a bug in the HAL daemon that incorrectly reports the lid as closed ({{path|lshal}} returns {{bootparm|button.state.value|true}}, among other things). The simplest way to resolve this is to add a line to the sleep script to restart the HAL daemon ''before'' sleeping the machine:

# restart the HAL daemon
service haldaemon restart

If you use {{path|gnome-power-manager}}, restarting HAL will kill it, unfortunately, so you'll have to restart it.

{{NOTE|It is possible this method will not work if the laptop is docked.}}

Another solution is to use vbetool. If you are using {{Debian}} with the hibernate package, uncomment "EnableVbetool yes" in {{path|/etc/hibernate/hibernate.conf}} (or {{path|/etc/hibernate/ram.conf}}).

===Solution for ThinkPads with Intel Extreme Graphics 2===
{{NOTE|
On [[:Category:X40|X40]]s/[[:Category:X41|X41]]s - even with Intel Extreme Graphics - and for [[:Category:R52|R52]]s with Intel Graphics Media Accelerator 900 the [[Problem with display remaining black after resume#Solution for ThinkPads with ATI graphic chips|solution for ATI graphics chips]] above is reported to work. In this case, make sure no changes to VBE are made, especially no state saves and no reposts.}}

The following solution should work on 865G, 865GV, 855GM, 855GME, 852GME chipsets.
*First of all, '''do not''' use the {{bootparm|acpi_sleep|s3_bios}} kernel parameter.
*Second, completely remove framebuffer support from your kernel. If it's built as modules, it is important that they do not get loaded at all.
*Before suspending, change to a console and safe the video state with {{cmdroot|cat /proc/bus/pci/00/02.0 > /tmp/video_state}}.
*On resume, restore the video state with {{cmdroot|cat /tmp/video_state > /proc/bus/pci/00/02.0}} and change back to X.
The following example {{path|/etc/acpi/actions/sleep.sh}} script shows how to integrate the according lines.

#!/bin/bash

# change to console 1
FGCONSOLE=`fgconsole`
chvt 6

# safe video state
cat /proc/bus/pci/00/02.0 > /tmp/video_state

# sync filesystem
sync

# sync hardware clock with system time
hwclock --systohc

# go to sleep
echo -n 3 > /proc/acpi/sleep

# waking up
# restore system clock
hwclock --hctosys

# restore video state
cat /tmp/video_state > /proc/bus/pci/00/02.0

# change back to X
chvt $FGCONSOLE

# clean up behind us
rm /tmp/video_state

===Solution for ThinkPads with Intel I830 Chipset===
The following solution worked for me on an X30 with I830M chipset with kernel >= 2.6.16.
*this works with vesafb and also with intelfb frambuffer support.
The following example {{path|/etc/acpi/actions/sleep.sh}} script shows how to integrate the according lines.

#!/bin/bash

FGCONSOLE=`fgconsole`
chvt 8
sync
hwclock --systohc

echo -n "mem" > /sys/power/state

hwclock --hctosys
vbetool post

if [ "$FGCONSOLE" -ge "7" ] ; then
chvt $FGCONSOLE
else
chvt 7
chvt $FGCONSOLE
fi

{{footnotes|
#If you have this problem with R50e and the above solution doesn't work, try switching to console first. An example sleep script can be found [[How to configure acpid|here]].
}}

Problem with display remaining black after resume

2006-05-19T17:47:09Z

BrianTung: cleaned up text in ATI/Intel 915 section

There has been a problem encountered where the display stays black on resuming from suspend.

The symptom might have you think first that your system hang up, but you will realize that your ThinkPad works and you can even reset it via {{key|Ctrl}}{{key|Alt}}{{key|Del}}.

==Affected Models==
*ThinkPad {{T41p}}, {{T42}}, {{T42p}}, {{T43}}, {{T43p}}
*Thinkpad {{T23}}
*ThinkPad {{X21}}, {{X30}}, {{X31}}, {{X40}}, {{X41}}
*ThinkPad {{R31}}, {{R50e}}{{footnote|1}}, {{R50p}}, {{R51}} (with BIOS 1.11), {{R52}}
*ThinkPad {{A30p}}
*ThinkPad {{390X}} (doesn't wake up; LCD backlight on, harddrive light remains on)
*ThinkPad {{Z60t}}, {{Z60m}}

==Affected Operating Systems==
*Linux (it's a kernel issue)

==Solutions==
===Solution for ThinkPads with 1400x1050 internal LCD and Intel 915GM ===
see [[1400x1050 on Intel 915GM]].
===Solution for ThinkPads with ATI graphic chips (or Intel 915GM)===
One solution may be to provide the {{bootparm|acpi_sleep|s3_bios}} kernel parameter in your kernel parameter line.

For grub this would look like this:

title Linux, kernel 2.6.11-1-686
root (hd0,0)
kernel /boot/vmlinuz-2.6.11-1-686 root=/dev/hda1 ro acpi_sleep=s3_bios
initrd /boot/initrd.img-2.6.11-1-686
savedefault
boot

For lilo it would look like this:

image=/boot/vmlinuz
append="acpi_sleep=s3_bios"

The actual process of going to sleep is then managed through a sleep script; as a start, see the {{path|sleep.sh}} script in the Extreme Graphics 2 section below, but note the following comments:

In [[:Category:OpenSUSE|OpenSUSE]] 10.1 (at least on a T43p) it's needed to override default options of s2ram if you use the newer ATI driver. It can be done putting SUSPEND2RAM_FORCE="yes" and SUSPEND2RAM_ACPI_SLEEP="3" in /etc/powersave/sleep.

In {{Ubuntu}} or {{Kubuntu}}, it may be necessary to modify {{path|/etc/default/acpi-support}}. In that file, make sure that {{path|ACPI_SLEEP}} is uncommented and set to true. With ATI chips, also make sure that {{path|SAVE_VBE_STATE}} is uncommented and set to true; with Intel chips, on the other hand, ensure that nothing is done with respect to VBE--no reposts, no state saves.

In {{Fedora}}, it may be necessary with the Intel chips to edit the {{path|resume_video()}} function in {{path|/etc/pm/functions-intel}} to comment out the VBE post and restore. Also, the laptop, after waking up, may go back to sleep whenever the AC adapter is disconnected. When this happens, it's caused by a bug in the HAL daemon that incorrectly reports the lid as closed ({{path|lshal}} returns {{bootparm|button.state.value|true}}, among other things). The simplest way to resolve this is to add a line to the sleep script to restart the HAL daemon ''before'' sleeping the machine:

# restart the HAL daemon
service haldaemon restart

If you use {{path|gnome-power-manager}}, restarting HAL will kill it, unfortunately, so you'll have to restart it.

{{NOTE|It is possible this method will not work if the laptop is docked.}}

Another solution is to use vbetool. If you are using {{Debian}} with the hibernate package, uncomment "EnableVbetool yes" in {{path|/etc/hibernate/hibernate.conf}} (or {{path|/etc/hibernate/ram.conf}}).

===Solution for ThinkPads with Intel Extreme Graphics 2===
{{NOTE|
On [[:Category:X40|X40]]s/[[:Category:X41|X41]]s - even with Intel Extreme Graphics - and for [[:Category:R52|R52]]s with Intel Graphics Media Accelerator 900 the [[Problem with display remaining black after resume#Solution for ThinkPads with ATI graphic chips|solution for ATI graphics chips]] above is reported to work. In this case, make sure no changes to VBE are made, especially no state saves and no reposts.}}

The following solution should work on 865G, 865GV, 855GM, 855GME, 852GME chipsets.
*First of all, '''do not''' use the {{bootparm|acpi_sleep|s3_bios}} kernel parameter.
*Second, completely remove framebuffer support from your kernel. If it's built as modules, it is important that they do not get loaded at all.
*Before suspending, change to a console and safe the video state with {{cmdroot|cat /proc/bus/pci/00/02.0 > /tmp/video_state}}.
*On resume, restore the video state with {{cmdroot|cat /tmp/video_state > /proc/bus/pci/00/02.0}} and change back to X.
The following example {{path|/etc/acpi/actions/sleep.sh}} script shows how to integrate the according lines.

#!/bin/bash

# change to console 1
FGCONSOLE=`fgconsole`
chvt 6

# safe video state
cat /proc/bus/pci/00/02.0 > /tmp/video_state

# sync filesystem
sync

# sync hardware clock with system time
hwclock --systohc

# go to sleep
echo -n 3 > /proc/acpi/sleep

# waking up
# restore system clock
hwclock --hctosys

# restore video state
cat /tmp/video_state > /proc/bus/pci/00/02.0

# change back to X
chvt $FGCONSOLE

# clean up behind us
rm /tmp/video_state

===Solution for ThinkPads with Intel I830 Chipset===
The following solution worked for me on an X30 with I830M chipset with kernel >= 2.6.16.
*this works with vesafb and also with intelfb frambuffer support.
The following example {{path|/etc/acpi/actions/sleep.sh}} script shows how to integrate the according lines.

#!/bin/bash

FGCONSOLE=`fgconsole`
chvt 8
sync
hwclock --systohc

echo -n "mem" > /sys/power/state

hwclock --hctosys
vbetool post

if [ "$FGCONSOLE" -ge "7" ] ; then
chvt $FGCONSOLE
else
chvt 7
chvt $FGCONSOLE
fi

{{footnotes|
#If you have this problem with R50e and the above solution doesn't work, try switching to console first. An example sleep script can be found [[How to configure acpid|here]].
}}

Ultrabay Slim Battery II

2006-05-19T02:18:32Z

BrianTung: removed spam from Lpkserj

__NOTOC__
{| 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 Advanced Ultrabay Battery ===
This is a battery that slides into a supported Ultrabay Slim or Ultrabay Enhanced slot

=== Features ===
* 10.8V Lithium-Ion
* Capacity: 2.7Ah
* Weight: 235g (0.52 lbs)
* Up to 8.5 hours of battery life on select systems in combination with main battery

</div>
|style="vertical-align:top" |
[[image:Advanced Ultrabay Battery.jpg|Advanced Ultrabay Battery]]
|}

=== IBM Partnumbers ===
*Order PN: 40Y6789
*FRU PN: 40Y6790

=== Usage and Linux support ===
See [[How to use UltraBay batteries]].

=== Supported with ===
*ThinkPad {{T60}}, {{T60p}}
*ThinkPad {{Z60t}}, {{Z60m}}
*[[UltraBase X6]]

[[Category:Components]]

Category:365C

2006-05-19T02:17:23Z

BrianTung: removed spam from Lpkserj

{| 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 365C ===
This page gives an overview of all ThinkPad 365CS related topics.
==== Features ====
* [[Cyrix Cx486|Cyrix Cx486DX4]] 75MHz CPU
* [[CT-65545]] video controller with 1MB
* 10.4" TFT display with 640x480 resolution
* 8MB memory standard
* 540MB HDD
* 1.44MB FDD (non-removable)
* [[IrDA]] 1.0
* (2) Type II, or (1) Type III [[PCMCIA slot]]
</div>
* [ftp://ftp.software.ibm.com/pc/pccbbs/mobiles/tpvol3.pdf ThinkPad HMM - Volume 3 (March 1997)]
|style="vertical-align:top" |
[[image:ThinkPad365e.jpg|ThinkPad 365C]]
|}
[[Category:Models]]

ThinkPad Monitor Stand 2001

2006-05-19T00:59:02Z

BrianTung: removed spam of Lpkserj

{| cellspacing="0" cellpadding="2" border="0"
| style="vertical-align:top;" | __TOC__
[[image:ThinkPad Monitor Stand 2001.jpg|300px|ThinkPad Monitor Stand 2001]]
| 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 Monitor Stand 2001 ==
ThinkPad Monitor Stand 2001 is made out of steel-reinforced molded plastic, supporting monitors up to 125lb

</div>
|}
* [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-4T9RG3 ThinkPad Monitor Stand 2001 - Overview]

==IBM part numbers==
* Order PN: 22P5265 (withdrawn)
* Monitor Stand FRU PN: 22P5268
* Monitor Stand Accessories FRU PN: 19K4490

== Supported ThinkPads ==
* {{A Series}}
* {{R Series}}
* {{T20}}, {{T21}}, {{T22}}, {{T23}}, {{T30}}, {{T40}}, {{T40p}}, {{T41}}, {{T41p}}, {{T42}}, {{T42p}}
* {{X Series}}

CS4236

2006-05-18T02:45:29Z

BrianTung: removed spam from Lpkserj

__NOTOC__
{| 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;">
=== CS4236 ===
This is a Cirrus Logic Audio controller

=== Features ===
* Chipset: CS4236B
* Interface: ISA 16bit
</div>
|style="vertical-align:top" |
|}

=== Linux OSS driver ===
This sound chip is supported by the cs4232 kernel module. Use the following options line when loading this module:

options cs4232 io=0x530 irq=5 dma=1 dma2=0

or try this from the commandline:

modprobe cs4232 io=0x530 irq=5 dma=1 dma2=0 mpuio=0x330 mpuirq=7 synthio=0x330 synthirq=7

(to get your soundcard working properly: disable QUICKSTART in the BIOS and dont INITIALIZE !)

=== Linux ALSA driver ===
This sound chip is supported by the snd-cs4236 kernel module. Use the following options line when loading this module:

options snd-cs4236 snd_index=0 snd_port=0x530 snd_cport=0x538 snd_isapnp=0 snd_dma1=1 snd_dma2=0 snd_irq=5

=== ThinkPads this chip may be found in ===
* {{380}}, {{380D}}, {{380E}}, {{380ED}}
* {{385D}}, {{385ED}}

[[Category:Components]]

Ultrabay Plus Device Carrier

2006-05-15T06:44:02Z

BrianTung: removed spam from Vyerus (get it?)

__NOTOC__
{| width="100%"
|style="vertical-align:top" | [[Image:ultrabaypluscarrier.jpg|UltraBay Plus Device Carrier]]
|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;">
=== UltraBay Plus Device Carrier ===
The UltraBay Plus Device Carrier converts the UltraBay Interface to a USB 1.1 interface and provides a mechanical base unit for supported devices.

=== Features ===
*USB 1.1 interface with PM extensions
*weight: 265g (0.58lbs)

</div>
|}

=== IBM Partnumbers ===
*Marketig Part Nr.: 27P5737
*FRU Part Nr.: 26P9388

=== Supported with ===
*ThinkPad {{A30}}, {{A30p}}, {{A31}}, {{A31p}}
*ThinkPad {{R30}}, {{R31}}, {{R32}}, {{R40}}
*ThinkPad {{T23}}, {{T30}}

[[Category:Components]]

Problem with display remaining black after resume

2006-05-14T18:38:11Z

BrianTung: /* Solution for ThinkPads with ATI graphic chips (or Intel 915GM) */

There has been a problem encountered where the display stays black on resuming from suspend.

The symptom might have you think first that your system hang up, but you will realize that your ThinkPad works and you can even reset it via {{key|Ctrl}}{{key|Alt}}{{key|Del}}.

==Affected Models==
*ThinkPad {{T41p}}, {{T42}}, {{T42p}}, {{T43}}, {{T43p}}
*Thinkpad {{T23}}
*ThinkPad {{X21}}, {{X30}}, {{X31}}, {{X40}}, {{X41}}
*ThinkPad {{R31}}, {{R50e}}{{footnote|1}}, {{R50p}}, {{R51}} (with BIOS 1.11), {{R52}}
*ThinkPad {{A30p}}
*ThinkPad {{390X}} (doesn't wake up; LCD backlight on, harddrive light remains on)
*ThinkPad {{Z60t}}, {{Z60m}}

==Affected Operating Systems==
*Linux (it's a kernel issue)

==Solutions==
===Solution for ThinkPads with 1400x1050 internal LCD and Intel 915GM ===
see [[1400x1050 on Intel 915GM]].
===Solution for ThinkPads with ATI graphic chips (or Intel 915GM)===
One solution may be to provide the {{bootparm|acpi_sleep|s3_bios}} kernel parameter in your kernel parameter line.

For grub this can look like this:

title Linux, kernel 2.6.11-1-686
root (hd0,0)
kernel /boot/vmlinuz-2.6.11-1-686 root=/dev/hda1 ro acpi_sleep=s3_bios
initrd /boot/initrd.img-2.6.11-1-686
savedefault
boot

For lilo it can look like this:

image=/boot/vmlinuz
append="acpi_sleep=s3_bios"

The actual process of going to sleep is then managed through a sleep script; as a start, see the {{path|sleep.sh}} script in the Extreme Graphics 2 section below, but note the following comments:

In {{Ubuntu}} or {{Kubuntu}}, it may be necessary to modify {{path|/etc/default/acpi-support}}. In that file, make sure that {{path|ACPI_SLEEP}} is uncommented and set to true. With ATI chips, also make sure that {{path|SAVE_VBE_STATE}} is uncommented and set to true; with Intel chips, on the other hand, ensure that nothing is done with respect to VBE--no reposts, no state saves.

In {{Fedora}}, it may be necessary with Intel chips to edit the {{path|resume_video()}} function in {{path|/etc/pm/functions-intel}}, by commenting out the VBE post and restore. Furthermore, the laptop, after waking up, may go back to sleep whenever the AC adapter is disconnected. When this happens, it is caused by a bug in the HAL daemon that incorrectly reports the lid as closed ({{path|lshal}} returns {{bootparm|button.state.value|true}}, among other things). The simplest way to resolve this is to add a line to the sleep script to restart the HAL daemon ''before'' sleeping the machine:

# restart the HAL daemon
service haldaemon restart

If you do this, it will unfortunately crash {{path|gnome-power-manager}}, if you use that, though it can be restarted manually.

{{NOTE|It is possible this method will not work if the laptop is docked.}}

Another solution is to use vbetool. If you are using {{Debian}} with the hibernate package, uncomment "EnableVbetool yes" in {{path|/etc/hibernate/hibernate.conf}} (or {{path|/etc/hibernate/ram.conf}}).

===Solution for ThinkPads with Intel Extreme Graphics 2===
{{NOTE|
On [[:Category:X40|X40]]s/[[:Category:X41|X41]]s - even with Intel Extreme Graphics - and for [[:Category:R52|R52]]s with Intel Graphics Media Accelerator 900 the [[Problem with display remaining black after resume#Solution for ThinkPads with ATI graphic chips|solution for ATI graphics chips]] above is reported to work. In this case, make sure no changes to VBE are made, especially no state saves and no reposts.}}

The following solution should work on 865G, 865GV, 855GM, 855GME, 852GME chipsets.
*First of all, '''do not''' use the {{bootparm|acpi_sleep|s3_bios}} kernel parameter.
*Second, completely remove framebuffer support from your kernel. If it's built as modules, it is important that they do not get loaded at all.
*Before suspending, change to a console and safe the video state with {{cmdroot|cat /proc/bus/pci/00/02.0 > /tmp/video_state}}.
*On resume, restore the video state with {{cmdroot|cat /tmp/video_state > /proc/bus/pci/00/02.0}} and change back to X.
The following example {{path|/etc/acpi/actions/sleep.sh}} script shows how to integrate the according lines.

#!/bin/bash

# change to console 1
FGCONSOLE=`fgconsole`
chvt 6

# safe video state
cat /proc/bus/pci/00/02.0 > /tmp/video_state

# sync filesystem
sync

# sync hardware clock with system time
hwclock --systohc

# go to sleep
echo -n 3 > /proc/acpi/sleep

# waking up
# restore system clock
hwclock --hctosys

# restore video state
cat /tmp/video_state > /proc/bus/pci/00/02.0

# change back to X
chvt $FGCONSOLE

# clean up behind us
rm /tmp/video_state

===Solution for ThinkPads with Intel I830 Chipset===
The following solution worked for me on an X30 with I830M chipset with kernel >= 2.6.16.
*this works with vesafb and also with intelfb frambuffer support.
The following example {{path|/etc/acpi/actions/sleep.sh}} script shows how to integrate the according lines.

#!/bin/bash

FGCONSOLE=`fgconsole`
chvt 8
sync
hwclock --systohc

echo -n "mem" > /sys/power/state

hwclock --hctosys
vbetool post

if [ "$FGCONSOLE" -ge "7" ] ; then
chvt $FGCONSOLE
else
chvt 7
chvt $FGCONSOLE
fi

{{footnotes|
#If you have this problem with R50e and the above solution doesn't work, try switching to console first. An example sleep script can be found [[How to configure acpid|here]].
}}

Talk:Installing Fedora Core 5 on a ThinkPad 600X

2006-05-10T08:00:58Z

BrianTung: /* FC5 installation problems on 600x */

OK people, I'd like some help here. At this point, FC5 is running, but some devices are not working.

Here are my choices:

Option 1: Try to get things working with the current packages. On the plus side, the guide will always for FC5 on the 600X because the FC5 distribution is fixed. On the minus side, a lot of work may already have been done for me.

Option 2: Get on the net, yum update ''then'' get things working. Plus: Some things might just work. (I think sound will work, for example.) Work saver. Minus: This guide is a snapshot of the latest FC5 updates as of right now... meaning the guide requires maintenance or is out of date.

Opinions welcome. --[[User:Whizkid|Whizkid]] 16:24, 26 April 2006 (CEST)

After installing on a 570, and updating the packages, sound worked just fine, so I'll do an update and go from there. --[[User:Whizkid|Whizkid]] 16:29, 30 April 2006 (CEST)

== Updating it is ==

I decided to update the packages and go from there. The sound started working immediately... so I got that going for me. :) --[[User:Whizkid|Whizkid]] 14:06, 3 May 2006 (CEST)

== FC5 installation problems on 600x ==

I am trying to get FC5 onto my 600x, but I'm getting a "Fedora Core CD was not found" error. I've unsuccessfully tried a few install options (acpi=off, apm=off and others). I've installed fc4 and other flavours of unix on several Thinkpads till now, but this is stumping me.
--Cheers,
Miguel

:Have you tried using turning off DMA? Try the ide=nodma install option. [[User:BrianTung|BrianTung]] 10:00, 10 May 2006 (CEST)

Intel Mobile Celeron (3)

2006-05-09T08:41:37Z

BrianTung: removed spam from Rebbel (= Grimp?)

{| width="100%"
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__
|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;">
===Intel Mobile Celeron (3) ===
The third Celeron line was based on the [[Intel Mobile Pentium III-M|Tualatin]] core and the performance gap towards it's [[Intel Mobile Pentium III-M|Pentium partner]] at same frequency was the lowest of all Celerons generations.

===Features===
*650-1333 MHz tact
*100 or 133 MHz FSB (100 on some of the lv and ulv models)
*44 Million Transistors
*0.13µm fabrication process
*1.45 VCore
*2x 16 KB L1-Cache
*256 KB L2-Cache
*QuickStart, Deeper Sleep
*[[SIMD|MMX]], [[SIMD|SSE]] instruction sets
</div>
|}

==Available Types and ThinkPads featuring them==
{| border=1 cellspacing=0 cellpadding=2
|- style="background:#ffdead;"
! Frequency (MHz) !! Bus Speed (MHz) !! VCore (V) !! TDP (W) !! ThinkPad Models
|- style="background:#efefef;"
! colspan=5 | Mobile Celeron
|-
| 1333 || 133 || 1.50 || 19.0 ||
|-
| 1200 || 133 || 1.45 || 24.4 || {{R31}}
|-
| 1133 || 133 || 1.45 || 23.8 || {{R31}}
|-
| 1066 || 133 || 1.45 || 23.2 || {{R31}}
|-
| 1000 || 133 || 1.40 || 22.0 ||
|- style="background:#efefef;"
! colspan=5 | Mobile Celeron (Low Voltage)
|-
| 866 || 133 || 1.15 || 9.6 ||
|-
| 733 || 133 || 1.15 || 11.2 ||
|-
| 667 || 133 || 1.15 || 10.7 ||
|-
| 650 || 100 || 1.15 || 10.6 ||
|- style="background:#efefef;"
! colspan=5 | Mobile Celeron (Ultra Low Voltage)
|-
| 800 || 133 || 1.10 || 7.0 ||
|-
| 733 || 133 || 1.10 || 7.0 ||
|-
| 700 || 100 || 1.10 || 7.0 ||
|-
| 667 || 133 || 1.10 || 7.0 ||
|-
| 650 || 100 || 1.15 || 7.0 ||
|}

==Thermal Specifications==

==GCC Optimization Flags==
You should use the following if you have a Mobile Celeron 3:
-O2 -march=pentium3 -fomit-frame-pointer -pipe

[[Category:Components]]

CS4236

2006-05-09T08:38:31Z

BrianTung: removed spam from Rebbel (= Grimp?)

__NOTOC__
{| 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;">
=== CS4236 ===
This is a Cirrus Logic Audio controller

=== Features ===
* Chipset: CS4236B
* Interface: ISA 16bit
</div>
|style="vertical-align:top" |
|}

=== Linux OSS driver ===
This sound chip is supported by the cs4232 kernel module. Use the following options line when loading this module:

options cs4232 io=0x530 irq=5 dma=1 dma2=0

or try this from the commandline:

modprobe cs4232 io=0x530 irq=5 dma=1 dma2=0 mpuio=0x330 mpuirq=7 synthio=0x330 synthirq=7

(to get your soundcard working properly: disable QUICKSTART in the BIOS and dont INITIALIZE !)

=== Linux ALSA driver ===
This sound chip is supported by the snd-cs4236 kernel module. Use the following options line when loading this module:

options snd-cs4236 snd_index=0 snd_port=0x530 snd_cport=0x538 snd_isapnp=0 snd_dma1=1 snd_dma2=0 snd_irq=5

=== ThinkPads this chip may be found in ===
* {{380}}, {{380D}}, {{380E}}, {{380ED}}
* {{385D}}, {{385ED}}

[[Category:Components]]

CS4236

2006-05-08T02:32:11Z

BrianTung: removed Grimp's spam

__NOTOC__
{| 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;">
=== CS4236 ===
This is a Cirrus Logic Audio controller

=== Features ===
* Chipset: CS4236B
* Interface: ISA 16bit
</div>
|style="vertical-align:top" |
|}

=== Linux OSS driver ===
This sound chip is supported by the cs4232 kernel module. Use the following options line when loading this module:

options cs4232 io=0x530 irq=5 dma=1 dma2=0

or try this from the commandline:

modprobe cs4232 io=0x530 irq=5 dma=1 dma2=0 mpuio=0x330 mpuirq=7 synthio=0x330 synthirq=7

(to get your soundcard working properly: disable QUICKSTART in the BIOS and dont INITIALIZE !)

=== Linux ALSA driver ===
This sound chip is supported by the snd-cs4236 kernel module. Use the following options line when loading this module:

options snd-cs4236 snd_index=0 snd_port=0x530 snd_cport=0x538 snd_isapnp=0 snd_dma1=1 snd_dma2=0 snd_irq=5

=== ThinkPads this chip may be found in ===
* {{380}}, {{380D}}, {{380E}}, {{380ED}}
* {{385D}}, {{385ED}}

[[Category:Components]]

User:BrianTung

2006-05-07T15:54:47Z

BrianTung: initialized personal page

Greetings. I own a Thinkpad {{X41}} running {{Fedora}} 5 (at the moment). As of now, I have most of what I want running; one small exception is that I don't have suspend-to-RAM working when the laptop is docked (it works fine without the dock).

See you 'round!

Problem with display remaining black after resume

2006-05-07T00:09:59Z

BrianTung: grammar nit in ATI/915GM section

There has been a problem encountered where the display stays black on resuming from suspend.

The symptom might have you think first that your system hang up, but you will realize that your ThinkPad works and you can even reset it via {{key|Ctrl}}{{key|Alt}}{{key|Del}}.

==Affected Models==
*ThinkPad {{T41p}}, {{T42}}, {{T42p}}, {{T43p}}
*Thinkpad {{T23}}
*ThinkPad {{X21}}, {{X30}}, {{X31}}, {{X40}}, {{X41}}
*ThinkPad {{R31}}, {{R50e}}{{footnote|1}}, {{R50p}}, {{R51}} (with BIOS 1.11), {{R52}}
*ThinkPad {{A30p}}
*ThinkPad {{390X}} (doesn't wake up; LCD backlight on, harddrive light remains on)
*ThinkPad {{Z60t}}

==Affected Operating Systems==
*Linux (it's a kernel issue)

==Solutions==
===Solution for ThinkPads with 1400x1050 internal LCD and Intel 915GM ===
see [[1400x1050 on Intel 915GM]].
===Solution for ThinkPads with ATI graphic chips (or Intel 915GM)===
One solution may be to provide the {{bootparm|acpi_sleep|s3_bios}} kernel parameter in your kernel parameter line.

For grub this can look like this:

title Linux, kernel 2.6.11-1-686
root (hd0,0)
kernel /boot/vmlinuz-2.6.11-1-686 root=/dev/hda1 ro acpi_sleep=s3_bios
initrd /boot/initrd.img-2.6.11-1-686
savedefault
boot

For lilo it can look like this:

image=/boot/vmlinuz
append="acpi_sleep=s3_bios"

The actual process of going to sleep is then managed through a sleep script; as a start, see the {{path|sleep.sh}} script in the Extreme Graphics 2 section below, but note the following comments:

In {{Ubuntu}} or {{Kubuntu}}, it may be necessary to modify {{path|/etc/default/acpi-support}}. In that file, make sure that {{path|ACPI_SLEEP}} is uncommented and set to true. With ATI chips, also make sure that {{path|SAVE_VBE_STATE}} is uncommented and set to true; with Intel chips, on the other hand, ensure that nothing is done with respect to VBE--no reposts, no state saves.

In {{Fedora}}, it may be necessary with Intel chips to edit the {{path|resume_video()}} function in {{path|/etc/pm/functions-intel}}, by commenting out the VBE post and restore. Furthermore, you may experience a problem where the laptop, after it wakes up, goes back to sleep whenever the AC adapter is disconnected. When this happens, it is caused by a bug in the HAL daemon that incorrectly reports the lid as closed ({{path|lshal}} returns {{bootparm|button.state.value|true}}, among other things). The simplest way to resolve this is to add a line to the sleep script to restart the HAL daemon:

# restart the HAL daemon
service haldaemon restart

If you do this, it will unfortunately crash {{path|gnome-power-manager}}, if you use that, though it can be restarted manually.

{{NOTE|It is possible this method will not work if the laptop is docked.}}

Another solution is to use vbetool. If you are using {{Debian}} with the hibernate package, uncomment "EnableVbetool yes" in {{path|/etc/hibernate/hibernate.conf}} (or {{path|/etc/hibernate/ram.conf}}).

===Solution for ThinkPads with Intel Extreme Graphics 2===
{{NOTE|
On [[:Category:X40|X40]]s/[[:Category:X41|X41]]s - even with Intel Extreme Graphics - and for [[:Category:R52|R52]]s with Intel Graphics Media Accelerator 900 the [[Problem with display remaining black after resume#Solution for ThinkPads with ATI graphic chips|solution for ATI graphics chips]] above is reported to work. In this case, make sure no changes to VBE are made, especially no state saves and no reposts.}}

The following solution should work on 865G, 865GV, 855GM, 855GME, 852GME chipsets.
*First of all, '''do not''' use the {{bootparm|acpi_sleep|s3_bios}} kernel parameter.
*Second, completely remove framebuffer support from your kernel. If it's built as modules, it is important that they do not get loaded at all.
*Before suspending, change to a console and safe the video state with {{cmdroot|cat /proc/bus/pci/00/02.0 > /tmp/video_state}}.
*On resume, restore the video state with {{cmdroot|cat /tmp/video_state > /proc/bus/pci/00/02.0}} and change back to X.
The following example {{path|/etc/acpi/actions/sleep.sh}} script shows how to integrate the according lines.

#!/bin/bash

# change to console 1
FGCONSOLE=`fgconsole`
chvt 6

# safe video state
cat /proc/bus/pci/00/02.0 > /tmp/video_state

# sync filesystem
sync

# sync hardware clock with system time
hwclock --systohc

# go to sleep
echo -n 3 > /proc/acpi/sleep

# waking up
# restore system clock
hwclock --hctosys

# restore video state
cat /tmp/video_state > /proc/bus/pci/00/02.0

# change back to X
chvt $FGCONSOLE

# clean up behind us
rm /tmp/video_state

===Solution for ThinkPads with Intel I830 Chipset===
The following solution worked for me on an X30 with I830M chipset with kernel >= 2.6.16.
*this works with vesafb and also with intelfb frambuffer support.
The following example {{path|/etc/acpi/actions/sleep.sh}} script shows how to integrate the according lines.

#!/bin/bash

FGCONSOLE=`fgconsole`
chvt 8
sync
hwclock --systohc

echo -n "mem" > /sys/power/state

hwclock --hctosys
vbetool post

if [ "$FGCONSOLE" -ge "7" ] ; then
chvt $FGCONSOLE
else
chvt 7
chvt $FGCONSOLE
fi

{{footnotes|
#If you have this problem with R50e and the above solution doesn't work, try switching to console first. An example sleep script can be found [[How to configure acpid|here]].
}}

Problem with display remaining black after resume

2006-05-05T20:46:42Z

BrianTung: refactored ATI chip section; added tips for Fedora; added 915GM to title

There has been a problem encountered where the display stays black on resuming from suspend.

The symptom might have you think first that your system hang up, but you will realize that your ThinkPad works and you can even reset it via {{key|Ctrl}}{{key|Alt}}{{key|Del}}.

==Affected Models==
*ThinkPad {{T41p}}, {{T42}}, {{T42p}}, {{T43p}}
*Thinkpad {{T23}}
*ThinkPad {{X21}}, {{X30}}, {{X31}}, {{X40}}, {{X41}}
*ThinkPad {{R31}}, {{R50e}}{{footnote|1}}, {{R50p}}, {{R51}} (with BIOS 1.11), {{R52}}
*ThinkPad {{A30p}}
*ThinkPad {{390X}} (doesn't wake up; LCD backlight on, harddrive light remains on)
*ThinkPad {{Z60t}}

==Affected Operating Systems==
*Linux (it's a kernel issue)

==Solutions==
===Solution for ThinkPads with ATI graphic chips (or Intel 915GM)===
One solution may be to provide the {{bootparm|acpi_sleep|s3_bios}} kernel parameter in your kernel parameter line.

For grub this can look like this:

title Linux, kernel 2.6.11-1-686
root (hd0,0)
kernel /boot/vmlinuz-2.6.11-1-686 root=/dev/hda1 ro acpi_sleep=s3_bios
initrd /boot/initrd.img-2.6.11-1-686
savedefault
boot

For lilo it can look like this:

image=/boot/vmlinuz
append="acpi_sleep=s3_bios"

The actual process of going to sleep is then managed through a sleep script; as a start, see the {{path|sleep.sh}} script in the Extreme Graphics 2 section below, but note the following comments:

In {{Ubuntu}} or {{Kubuntu}}, it may be necessary to modify {{path|/etc/default/acpi-support}}. In that file, make sure that {{path|ACPI_SLEEP}} is uncommented and set to true. With ATI chips, also make sure that {{path|SAVE_VBE_STATE}} is uncommented and set to true; with Intel chips, on the other hand, ensure that nothing is done with respect to VBE--no reposts, no state saves.

In {{Fedora}}, it may be necessary with Intel chips to edit the {{path|resume_video()}} function in {{path|/etc/pm/functions-intel}}, by commenting out the VBE post and restore. Furthermore, you may experience a problem where the laptop, after it wakes up, goes back to sleep whenever the AC adapter is disconnected. When this happens, it is caused by a bug in the HAL daemon that incorrectly reports the lid as closed ({{path|lshal}} return {{bootparm|button.state.value|true}}, among other things). The simplest way to resolve this is to add a line to the sleep script to restart the HAL daemon:

# restart the HAL daemon
service haldaemon restart

If you do this, it will unfortunately crash {{path|gnome-power-manager}}, if you use that, though it can be restarted manually.

{{NOTE|It is possible this method will not work if the laptop is docked.}}

Another solution is to use vbetool. If you are using {{Debian}} with the hibernate package, uncomment "EnableVbetool yes" in {{path|/etc/hibernate/hibernate.conf}} (or {{path|/etc/hibernate/ram.conf}}).

===Solution for ThinkPads with Intel Extreme Graphics 2===
{{NOTE|
On [[:Category:X40|X40]]s/[[:Category:X41|X41]]s - even with Intel Extreme Graphics - and for [[:Category:R52|R52]]s with Intel Graphics Media Accelerator 900 the [[Problem with display remaining black after resume#Solution for ThinkPads with ATI graphic chips|solution for ATI graphics chips]] above is reported to work. In this case, make sure no changes to VBE are made, especially no state saves and no reposts.}}

The following solution should work on 865G, 865GV, 855GM, 855GME, 852GME chipsets.
*First of all, '''do not''' use the {{bootparm|acpi_sleep|s3_bios}} kernel parameter.
*Second, completely remove framebuffer support from your kernel. If it's built as modules, it is important that they do not get loaded at all.
*Before suspending, change to a console and safe the video state with {{cmdroot|cat /proc/bus/pci/00/02.0 > /tmp/video_state}}.
*On resume, restore the video state with {{cmdroot|cat /tmp/video_state > /proc/bus/pci/00/02.0}} and change back to X.
The following example {{path|/etc/acpi/actions/sleep.sh}} script shows how to integrate the according lines.

#!/bin/bash

# change to console 1
FGCONSOLE=`fgconsole`
chvt 6

# safe video state
cat /proc/bus/pci/00/02.0 > /tmp/video_state

# sync filesystem
sync

# sync hardware clock with system time
hwclock --systohc

# go to sleep
echo -n 3 > /proc/acpi/sleep

# waking up
# restore system clock
hwclock --hctosys

# restore video state
cat /tmp/video_state > /proc/bus/pci/00/02.0

# change back to X
chvt $FGCONSOLE

# clean up behind us
rm /tmp/video_state

===Solution for ThinkPads with Intel I830 Chipset===
The following solution worked for me on an X30 with I830M chipset with kernel >= 2.6.16.
*this works with vesafb and also with intelfb frambuffer support.
The following example {{path|/etc/acpi/actions/sleep.sh}} script shows how to integrate the according lines.

#!/bin/bash

FGCONSOLE=`fgconsole`
chvt 8
sync
hwclock --systohc

echo -n "mem" > /sys/power/state

hwclock --hctosys
vbetool post

if [ "$FGCONSOLE" -ge "7" ] ; then
chvt $FGCONSOLE
else
chvt 7
chvt $FGCONSOLE
fi

{{footnotes|
#If you have this problem with R50e and the above solution doesn't work, try switching to console first. An example sleep script can be found [[How to configure acpid|here]].
}}

Talk:Problem with display remaining black after resume

2006-04-30T17:52:53Z

BrianTung: /* X41 with an Intel 915GM Integrated Graphics Device */

== T43 with Intel Graphics Media Accelerator ==

My T43 (1871-FYG) with Intel 915GM is also affected by the problem and the 'ATI' sollution with
acpi_sleep=s3_bios works. Please consider updating the page (I don't dare to do it myself).

== From my experience, this does not work with TP R50e. ==

If you want to be able to resume, you need :
* To start from a VT
* No option acpi_sleep
* to save the PCI state like:
cat /proc/bus/pci/00/02.0 > /var/cache/video.config
* Once you get back, restore it:
cat /var/cache/video.config > /proc/bus/pci/00/02.0

However, the X screen is not clean after the restore, so this is not very useable...

== The comment on R50e ==

There is a comment at the end of the page on R50e, saying that you should switch to console first, and look at a page to learn how to do this.

However. it seems to me that the given script already does it. Should the comment be removed?
----
The scripts are different. However, if you can approve that the solution provided on this page resolves the problem, please remove the footnote.

[[User:Wyrfel|Wyrfel]] 14:46, 17 Oct 2005 (CEST)
----
On my R50e, the script on this page works fine, while the one linked in the footnote quickly wakes up from sleep.

[[User:Thisnukes4u|Thisnukes4u]] 19:39, 1 Jan 2006 (CET)

== Problems with R51 and Intel Graphics ==

The problems described on the page occur intermittently
with an Intel Graphics card on an R51. Here is what happens:

1. One some occassions everything seems to work fine.

2. On other occassions the screen looks OK but the some plane seems to have vanished. New text on the screen overwrites instead of replaces prior text. The "standard" pattern disappears from the X background.

3. On yet other occassions the X server dies and comes out "blank" in the mode (2) above.

4. The above problems appear only with the "i810" driver. The "vesa" driver works fine. Moreover, if the machine is "suspend-to-disk"ed then the problem disappears on resumption once the X server is killed and re-started.

But for 1 and 4 above I would have given up and either avoided suspend to ram altogether or used vesa mode---as it stands the problem is tantalising.

Kapil kapil at imsc dot res dot in

== X40 with an Intel 855GM Integrated Graphics Device ==

I used the {{bootparm|acpi_sleep|s3_bios}} boot parameter and the following ACPI script:

#!/bin/sh
set -e

vt=`fgconsole`
chvt 12
echo mem >/sys/power/state
vbetool post
chvt $vt

The {{bootparm|acpi_sleep|s3_bios}} boot parameter alone did not fix things, and neither did saving and restoring the information from {{path|/proc/bus/pci/00/02.0}}.

== X41 with an Intel 915GM Integrated Graphics Device ==

It works with the {{bootparm|acpi_sleep|s3_bios,s3_mode}} boot parameter. Resume works great, both on the VESA console and in X.

:Interesting--that didn't work for me. I needed to do several things to get it to work. First, I used s3_bios, but not s3_mode. Secondly, I had to edit resume_video() in /etc/pm/functions-intel to comment out the VBE post and restore. Those two changes made it functional, but the improper lid state in the HAL daemon caused it to go back to sleep just as soon as it resumed upon the lid opening, so I added a HAL restart to the front end of /etc/acpi/actions/sleep.sh. This means that I have to restart gnome-power-manager, too. I haven't yet figured out a way to do that in sleep.sh; currently I do it manually. I'll post this to the main page soon, unless I hear comments to the contrary. [[User:BrianTung|BrianTung]] 19:52, 30 April 2006 (CEST) (fixed a little)

== Z60t with an Intel 915GM Integrated Graphics Device (PCI Express) ==

It works with the {{bootparm|acpi_sleep|s3_bios}} boot parameter. Here is the script I use (gentoo). Note: stopping and starting WiFi is not necessary to resume, but it is dead on resume until restarted and the module is reloaded. This is on a 2.6.15.4 kernel with framebuffer console support. The blinking led thing is a nice touch I got from the hibernate-scripts package - it blinks the sleep led (moon icon) until the sleep or resume cycle is finished.

The 'vbetool vbemode get/set' commands are for saving and restoring the console text mode - otherwise the screen becomes garbled.

#!/bin/bash

# blink sleep led (if ibm_acpi is installed)
echo 7 blink > /proc/acpi/ibm/led

# change to console 10 (unused?)
FGCONSOLE=`fgconsole`
chvt 10

# save video state
VBEMODE=`vbetool vbemode get`
cat /proc/bus/pci/00/02.0 > /tmp/video_state

# sync filesystem
sync

# sync hardware clock with system time
hwclock --systohc

# stop networking (atheros chipset)
/etc/init.d/net.ath0 stop
rmmod ath_pci

# go to sleep
sleep 2 ; echo -n 3 > /proc/acpi/sleep

# blink sleep led
echo 7 blink > /proc/acpi/ibm/led

# restore system clock
hwclock --hctosys

# restore video state
vbetool vbemode set $VBEMODE
cat /tmp/video_state > /proc/bus/pci/00/02.0

# change back to X
chvt $FGCONSOLE

# restart networking
modprobe ath_pci
/etc/init.d/net.ath0 start

# clean up behind us
rm /tmp/video_state
echo 7 off > /proc/acpi/ibm/led

Talk:Problem with display remaining black after resume

2006-04-30T03:47:58Z

BrianTung: /* X41 with an Intel 915GM Integrated Graphics Device */

== T43 with Intel Graphics Media Accelerator ==

My T43 (1871-FYG) with Intel 915GM is also affected by the problem and the 'ATI' sollution with
acpi_sleep=s3_bios works. Please consider updating the page (I don't dare to do it myself).

== From my experience, this does not work with TP R50e. ==

If you want to be able to resume, you need :
* To start from a VT
* No option acpi_sleep
* to save the PCI state like:
cat /proc/bus/pci/00/02.0 > /var/cache/video.config
* Once you get back, restore it:
cat /var/cache/video.config > /proc/bus/pci/00/02.0

However, the X screen is not clean after the restore, so this is not very useable...

== The comment on R50e ==

There is a comment at the end of the page on R50e, saying that you should switch to console first, and look at a page to learn how to do this.

However. it seems to me that the given script already does it. Should the comment be removed?
----
The scripts are different. However, if you can approve that the solution provided on this page resolves the problem, please remove the footnote.

[[User:Wyrfel|Wyrfel]] 14:46, 17 Oct 2005 (CEST)
----
On my R50e, the script on this page works fine, while the one linked in the footnote quickly wakes up from sleep.

[[User:Thisnukes4u|Thisnukes4u]] 19:39, 1 Jan 2006 (CET)

== Problems with R51 and Intel Graphics ==

The problems described on the page occur intermittently
with an Intel Graphics card on an R51. Here is what happens:

1. One some occassions everything seems to work fine.

2. On other occassions the screen looks OK but the some plane seems to have vanished. New text on the screen overwrites instead of replaces prior text. The "standard" pattern disappears from the X background.

3. On yet other occassions the X server dies and comes out "blank" in the mode (2) above.

4. The above problems appear only with the "i810" driver. The "vesa" driver works fine. Moreover, if the machine is "suspend-to-disk"ed then the problem disappears on resumption once the X server is killed and re-started.

But for 1 and 4 above I would have given up and either avoided suspend to ram altogether or used vesa mode---as it stands the problem is tantalising.

Kapil kapil at imsc dot res dot in

== X40 with an Intel 855GM Integrated Graphics Device ==

I used the {{bootparm|acpi_sleep|s3_bios}} boot parameter and the following ACPI script:

#!/bin/sh
set -e

vt=`fgconsole`
chvt 12
echo mem >/sys/power/state
vbetool post
chvt $vt

The {{bootparm|acpi_sleep|s3_bios}} boot parameter alone did not fix things, and neither did saving and restoring the information from {{path|/proc/bus/pci/00/02.0}}.

== X41 with an Intel 915GM Integrated Graphics Device ==

It works with the {{bootparm|acpi_sleep|s3_bios,s3_mode}} boot parameter. Resume works great, both on the VESA console and in X.

:Interesting--that didn't work for me. I needed to do several things to get it to work. First, I used s3_bios, but not s3_mode. Secondly, I had to edit resume_video() in /etc/pm/functions-intel to get rid of the VBE post and restore. Those two made it functional, but the improper state in the HAL daemon caused it to go back to sleep just as soon as it resumed, so I added a HAL restart to the front end of /etc/acpi/actions/sleep.sh; this means that I have to restart gnome-power-manager, too. I haven't yet figured out a way to do that in the sleep.sh script, though. [[User:BrianTung|BrianTung]] 05:47, 30 April 2006 (CEST)

== Z60t with an Intel 915GM Integrated Graphics Device (PCI Express) ==

It works with the {{bootparm|acpi_sleep|s3_bios}} boot parameter. Here is the script I use (gentoo). Note: stopping and starting WiFi is not necessary to resume, but it is dead on resume until restarted and the module is reloaded. This is on a 2.6.15.4 kernel with framebuffer console support. The blinking led thing is a nice touch I got from the hibernate-scripts package - it blinks the sleep led (moon icon) until the sleep or resume cycle is finished.

The 'vbetool vbemode get/set' commands are for saving and restoring the console text mode - otherwise the screen becomes garbled.

#!/bin/bash

# blink sleep led (if ibm_acpi is installed)
echo 7 blink > /proc/acpi/ibm/led

# change to console 10 (unused?)
FGCONSOLE=`fgconsole`
chvt 10

# save video state
VBEMODE=`vbetool vbemode get`
cat /proc/bus/pci/00/02.0 > /tmp/video_state

# sync filesystem
sync

# sync hardware clock with system time
hwclock --systohc

# stop networking (atheros chipset)
/etc/init.d/net.ath0 stop
rmmod ath_pci

# go to sleep
sleep 2 ; echo -n 3 > /proc/acpi/sleep

# blink sleep led
echo 7 blink > /proc/acpi/ibm/led

# restore system clock
hwclock --hctosys

# restore video state
vbetool vbemode set $VBEMODE
cat /tmp/video_state > /proc/bus/pci/00/02.0

# change back to X
chvt $FGCONSOLE

# restart networking
modprobe ath_pci
/etc/init.d/net.ath0 start

# clean up behind us
rm /tmp/video_state
echo 7 off > /proc/acpi/ibm/led