<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://www.thinkwiki.org/w/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Graham</id>
	<title>ThinkWiki - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://www.thinkwiki.org/w/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Graham"/>
	<link rel="alternate" type="text/html" href="https://www.thinkwiki.org/wiki/Special:Contributions/Graham"/>
	<updated>2026-04-04T04:59:06Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.31.12</generator>
	<entry>
		<id>https://www.thinkwiki.org/w/index.php?title=Talk:Problem_with_display_remaining_black_after_resume&amp;diff=18785</id>
		<title>Talk:Problem with display remaining black after resume</title>
		<link rel="alternate" type="text/html" href="https://www.thinkwiki.org/w/index.php?title=Talk:Problem_with_display_remaining_black_after_resume&amp;diff=18785"/>
		<updated>2006-01-23T04:44:15Z</updated>

		<summary type="html">&lt;p&gt;Graham: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== T43 with Intel Graphics Media Accelerator ==&lt;br /&gt;
&lt;br /&gt;
My T43 (1871-FYG) with Intel 915GM is also affected by the problem and the 'ATI' sollution with&lt;br /&gt;
acpi_sleep=s3_bios works. Please consider updating the page (I don't dare to do it myself).&lt;br /&gt;
&lt;br /&gt;
== From my experience, this does not work with TP R50e. ==&lt;br /&gt;
&lt;br /&gt;
If you want to be able to resume, you need :&lt;br /&gt;
* To start from a VT&lt;br /&gt;
* No option acpi_sleep&lt;br /&gt;
* to save the PCI state like:&lt;br /&gt;
 cat /proc/bus/pci/00/02.0 &amp;gt; /var/cache/video.config&lt;br /&gt;
* Once you get back, restore it:&lt;br /&gt;
 cat /var/cache/video.config &amp;gt; /proc/bus/pci/00/02.0&lt;br /&gt;
&lt;br /&gt;
However, the X screen is not clean after the restore, so this is not very useable...&lt;br /&gt;
&lt;br /&gt;
== The comment on R50e ==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
However. it seems to me that the given script already does it. Should the comment be removed?&lt;br /&gt;
----&lt;br /&gt;
The scripts are different. However, if you can approve that the solution provided on this page resolves the problem, please remove the footnote.&lt;br /&gt;
&lt;br /&gt;
[[User:Wyrfel|Wyrfel]] 14:46, 17 Oct 2005 (CEST)&lt;br /&gt;
----&lt;br /&gt;
On my R50e, the script on this page works fine, while the one linked in the footnote quickly wakes up from sleep.&lt;br /&gt;
&lt;br /&gt;
[[User:Thisnukes4u|Thisnukes4u]] 19:39, 1 Jan 2006 (CET)&lt;br /&gt;
&lt;br /&gt;
== Problems with R51 and Intel Graphics ==&lt;br /&gt;
&lt;br /&gt;
The problems described on the page occur intermittently&lt;br /&gt;
with an Intel Graphics card on an R51. Here is what happens:&lt;br /&gt;
&lt;br /&gt;
1. One some occassions everything seems to work fine.&lt;br /&gt;
&lt;br /&gt;
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 &amp;quot;standard&amp;quot; pattern disappears from the X background.&lt;br /&gt;
&lt;br /&gt;
3. On yet other occassions the X server dies and comes out &amp;quot;blank&amp;quot; in the mode (2) above.&lt;br /&gt;
&lt;br /&gt;
4. The above problems appear only with the &amp;quot;i810&amp;quot; driver. The &amp;quot;vesa&amp;quot; driver works fine. Moreover, if the machine is &amp;quot;suspend-to-disk&amp;quot;ed then the problem disappears on resumption once the X server is killed and re-started.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
Kapil kapil at imsc dot res dot in&lt;br /&gt;
&lt;br /&gt;
== X40 with an Intel 855GM Integrated Graphics Device ==&lt;br /&gt;
&lt;br /&gt;
I used the {{bootparm|acpi_sleep|s3_bios}} boot parameter and the following ACPI script:&lt;br /&gt;
&lt;br /&gt;
 #!/bin/sh&lt;br /&gt;
 set -e&lt;br /&gt;
 &lt;br /&gt;
 vt=`fgconsole`&lt;br /&gt;
 chvt 12&lt;br /&gt;
 echo mem &amp;gt;/sys/power/state&lt;br /&gt;
 vbetool post&lt;br /&gt;
 chvt $vt&lt;br /&gt;
&lt;br /&gt;
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}}.&lt;/div&gt;</summary>
		<author><name>Graham</name></author>
		
	</entry>
</feed>