Hi, sorry for the late reply, i am still catching up with my inbox :-)
On Wed, Jul 12, 2006 at 01:03:29PM +0200, Felix Homann wrote: > Hi, > > here's some information about my machine. It is an Acer Extensa 4100 with a > ATI X600 graphics card: > > ================ > # s2ram -i > This machine can be identified by: > sys_vendor = "Acer, inc." > sys_product = "Extensa 4100 " > sys_version = "Not Applicable" > bios_version = "3C29" > See http://en.opensuse.org/S2ram for details. > > If you report a problem, please include the complete output above. > ================== > > I've tested several s2ram options with a 2.6.17.4 kernel. > > In short resume only works fine with an X server running (preferrably ATI's > fglrx). > > Here are the details: > > 1. Suspending with X running (fglrx 8.26.18), vga=0 or vga=791: > > 1.1. Suspending from X: > Everything's working fine with 's2ram -f' good. > 1.2 Suspending from a VT: > 's2ram -f' is working partially fine, i.e. the display stays black > until > switching to X, then everything's fine bad. > 2. Suspending with X running (x.org driver), vga=0 or vga=791: > > Like 1. but VTs are corrupted! bad. > 3. Suspending without X running > > I'll be using the following abbreviations for the state after resume: > > B = Display stays black, machine is running fine Does this also mean the backlight stays off? (Hard to see, but should be a difference between "just" black and "black with backlight off"). > F = Display stays black, machine shows permanent disk activity, > doesn't > react, no network etc. > C = Display wakes up, shows moving coloured stripes, like F in every > other > aspect. Ok, so "B" is something to work on from, C and F are unusable :-) > 3.1 vga=791 > > Only F states after resume. > > 3.2 vga=0 > > No combination actually works: > > -a 1 : F > -a 2 : B > -a 3 : F > -p -s : B > -s : C > -p : B With the latest CVS (as of yesterday), you could try the brand new "-p -m" combination, which is not yet documented, but i do not really believe that it will help much here :-( Another thing you could try is just "s2ram -f -r" or "s2ram -f -p -r", maybe the radeontool code can switch your light back on after resume. > -a 1 -s : F > -a 2 -s : C > -a 3 -s : F > -a 1 -p : F > -a 2 -p : B > -a 3 -p : F > -a 1 -s -p : F > -a 2 -s -p : B > -a 3 -s -p : F > > I don't know if this qualifies my notebook to be added to the whitelist in > any Not really, sorry :-) > way. If not I would like to see a way to suspend-to-both with manually giving > the appropriate s2ram options. It doesn't seem to be possible at the moment > if the machine is not in the whitelist (tried with 's2both' from Debian's > uswsusp package which seems to be the same as 'suspend' from upstream.). Yes, we will work on that (giving s2ram options to s2both) as we will need it anyway. -- 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
