On Thu, Aug 03, 2006 at 03:06:00PM +0530, Kapil Hari Paranjape wrote: > I do however *have* a working suspend-to-ram configuration that I learnt > from > > http://www.thinkwiki.org/Problem_with_display_remaining_black_after_resume#Solution_for_ThinkPads_with_Intel_Extreme_Graphics_2 > > This involves saving the contents of /proc/bus/pci/00/02.0 before > suspending and restoring it after suspending. I am attaching the > relevant script.
Just because i have read this in the script: | # Strange Intel graphics requires this | # state to be saved | cat $VID_DEV > $VID_SAV | cat $VID_DEV1 > $VID_SAV1 This is nothing about "strange intel graphics". The same "Strange Intel graphics" work just fine on other machines. So it is either something IBM has done wrong (probably in their BIOS) or they are doing something particularly clever, which the kernel does not handle correctly. Also, i see that you are using VBE_POST|VBE_SAVE. In your report you said that "s2ram -f" alone brings the display back, so it looks that the vbetool usage on this machine is superfluous? -- Stefan Seyfried | "Please, just tell people QA / R&D Team Mobile Devices | to use KDE." SUSE LINUX Products GmbH, Nürnberg | -- Linus Torvalds ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Suspend-devel mailing list Suspend-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/suspend-devel
