On Thursday 03 August 2006 12:36, Stefan Seyfried wrote: > On Thu, Aug 03, 2006 at 03:06:00PM +0530, Kapil Hari Paranjape wrote: > Content-Description: message > > Hello, > > > > I am using a Debian etch system: > > > > kernel: linux-image-2.6.17-1-686 Debian version 2.6.17-5 > > s2ram: uswsusp Debian version 0.2-1 > > > > kernel command line: kernel /vmlinuz-2.6.17-1-686 > > root=/dev/mapper/store-root rw quiet init=/bin/bash > > (kernel uses Debian built initramfs which uses a standard test console). > > > > This machine can be identified by: > > sys_vendor = "IBM" > > sys_product = "2887NQ9" > > sys_version = "ThinkPad R51" > > bios_version = "1VET66WW (1.24 )" > > > > lspci -v output is attached. > > > > I tried each command in succession: > > > > s2ram -f > > s2ram -f -a 1 > > s2ram -f -a 2 > > s2ram -f -a 3 > > s2ram -f -p -s > > s2ram -f -s > > s2ram -f -p > > s2ram -f -a 1 -s > > > > None of these "worked". For each of them the system went into suspend > > mode. One resuming with the power button or the "function Fn key", > > the system came up the state where it had the message about "stopping > > tasks" with "======|" at the top of the screen. After this the screen > > did not show anything and keyboard activity produced apparently no > > effect. However, I managed to use Alt-Sysrq to Sync and Unmount > > disks but power-Off did not work---system did not power-off. > > > > 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 > > 404 > > > 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. > > This is known to some extents, for R50e we have this in the whitelist: > /* R50e needs not yet implemented save_video_pci_state :-( > { "IBM", "1834*", "", "", > UNSURE }, > { "IBM", "1842*", "", "", > UNSURE }, > { "IBM", "2670*", "", "", > UNSURE }, > */ > > and your machine probably also falls into the same category. > However, _i_ consider this to be either a driver or a pci-subsystem kernel > bug which really should be solved there. > > If somebody really thinks we should work around this in userspace, he has > to either use a custom script and wrap this around "s2ram -f" or send a > patch that implements this cleanly in s2ram. At least this is my opinion > on the matter :-)
This is a kernel problem, apparently, and kernel problems should be solved in the kernel. Greetings, Rafael ------------------------------------------------------------------------- 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
