Hi, i have taken the suspend-devel mailing list into CC, maybe somebody over there has an idea.
On Tue, Sep 19, 2006 at 12:06:58AM -0400, Benjamin A. Okopnik wrote: > Hi - > > Here's a record of my tests of 's2ram' - hope you find it useful! > > ------------------------------------------------------------------ > [EMAIL PROTECTED]:/tmp/suspend-0.2$ su -c ./s2ram > Password: > Machine is unknown. > This machine can be identified by: > sys_vendor = "Acer" > sys_product = "Aspire 2010" > sys_version = "Aspire" > bios_version = "V1.30" > See http://en.opensuse.org/S2ram for details. > > If you report a problem, please include the complete output above. > [EMAIL PROTECTED]:/tmp/suspend-0.2$ uname -a > Linux Fenrir 2.6.17.13 #3 Sun Sep 17 19:52:55 EDT 2006 i686 GNU/Linux > ------------------------------------------------------------------ > > Test results: > > ------------------------------------------------------------------ > Overall, no luck. :( > > "lilo" configuration: > "vga=0" turned out to be necessary; "noacpi" didn't. > > In all cases, suspending caused all lights except the power LED to > go out; after that, pushing any key or hitting the power button > made the WiFi light on the front of the laptop come on. > > Result categories: > {1} - After resuming, the HD light blinks once; after that, the > system responds to CLI commands (e.g., HD shows activity on > 'ls -lR /tmp') but the display stays dark > > {2} Resuming causes the screen to display shifting multi-color > columns; no response to keystrokes > > {3} - No response to keystrokes > ------------------------------------------------------------------- > > {1} > s2ram -f > s2ram -f -p > s2ram -f -p -s > s2ram -f -p -r > s2ram -f -p -s -r > s2ram -f -a 2 > s2ram -f -p -a 2 > s2ram -f -p -r -a 2 > s2ram -f -p -r -s -a 2 > > {2} > s2ram -f -s > s2ram -f -s -r > s2ram -f -s -a 2 > s2ram -f -s -r -a 2 > > {3} > s2ram -f -a 1 > s2ram -f -a 3 > s2ram -f -a 1 -s > s2ram -f -s -r -p -a 1 > s2ram -f -s -r -p -a 3 > ------------------------------------------------------------------- Ok, so "s3_bios" (-a1, -a3) lets the machine hang in the BIOS. Restoring the VBE state (-s) without posting first (! -p) lets the video chip go wild somehow (shifting color columns). VBE POSTing (-p) or doing just nothing lets the machine wake up properly, but video does not wake up. Recent s2ram versions (might be that you'd need to use the CVS version, i am not sure) also have an additional workaround, "VBE_MODE", switch "-m", but from your results i doubt that it would help significantly. "s2ram -f -p -m" would be the suggested combination. What video card does this machine have? Did you try if you actually works if you try it from X? (sometimes the X drivers are a bit more clever than we are about the restoring and reanimating of graphics chipsets). From the failure mode i'd guess it is an ATI card? > Thanks for your effort, and please let me know if I can help test this > in any other way. Don't give up and try it again from time to time :-) > > > Regards, > * Ben Okopnik * Editor-in-Chief, Linux Gazette * http://LinuxGazette.NET * Have fun, -- Stefan Seyfried QA / R&D Team Mobile Devices | "Any ideas, John?" SUSE LINUX Products GmbH, Nürnberg | "Well, surrounding them's out." ------------------------------------------------------------------------- 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
