On Fri, Jul 27, 2007 at 05:24:09PM +0200, Sławomir Skrzyniarz wrote:
> > On Thu, Jul 19, 2007 at 08:33:12PM +0200, Sławomir Skrzyniarz wrote:
> > > > Yes, but does it also work on the text console? (i doubt it, and i'd
> > > > guess that you need to add "-f -p -m" to the s2ram options. Look at
> > > > http://en.opensuse.org/S2ram to find out how to get the best options
> > > > for your machine.
> > >
> > > It work. See below:
> > > -------------------------------------------------
> > > [EMAIL PROTECTED] ~]$ s2ram -f -p -m
> > > Switching from vt7 to vt1
> > > Calling get_mode
> > > Calling do_post
> > > Calling INT 0x15 (F000:F859)
> > > EAX is 10005F00
> > > Leaving interrupt call.
> > > Calling INT 0x10 (C000:0014)
> > > EAX is 3
> > > Leaving interrupt call.
> > > Calling set_vbe_mode
> > > switching back to vt7
> > > -------------------------------------------------
> >
> > This is still from X and not from the Text console. Please switch to VT1,
> > log in and try it from there.
>
> In Text console s2ram works almost properly only with -f option.
> --------------------------
> [EMAIL PROTECTED] ~]$ s2ram -f
> Switching from vt1 to vt1
> switching back to vt1
> --------------------------
> after this I have black screen, but when I put Ctrl+Alt+F7 I see ma KDE
> session, and Ctrl+Alt+F1 I see above log in terminal.
Yes, this is what i had expected. So it does not work from console withot X :-)
> But when I use -f -p -m options fistly KDE after wake up was logout. I had
> plugged USB printer.
Hm, if this is reproducible, we'd need to investigate what it is that your X
server does not like :-(
> Second time all work properly. Terminal appaears after wake up. KDE session
> work. I unplugged printer before. (logs below)
> Third time all work properly too. Terminal appaears after wake up. KDE
> session
> work. I had plugged USB printer. (logs below)
> --------------------------
> [EMAIL PROTECTED] ~]$ s2ram -f -p -m
> Switching from vt1 to vt1
> Calling get_mode
> Calling do_post
> Calling INT 0x15 (F000:F859)
> EAX is 10005F00
> Leaving interupt call
> Calling INT 0x10 (C000:0014)
> EAX is 3
> Leaving interupt call
> Calling set_vbe_mode
> switching back to vt1
> -------------------------
> [EMAIL PROTECTED] slawek]# s2ram -i
> This machine can be identified by:
> sys_vendor = "Hewlett-Packard"
> sys_product = "HP Compaq nx7400 (RH412EA#AKD)"
> sys_version = "F.0B"
> bios_version = "68YGU Ver. F.0B"
Ok, added to the whitelist with "-p -m" for now.
Just out of curiosity: what does "s2ram -n" show on your machine? Because
since 27-Nov-06 we have the following line in the whitelist, which _should_
have also matched your machine:
{ "Hewlett-Packard", "", "", "68YGU*", VBE_POST },
--
Stefan Seyfried
QA / R&D Team Mobile Devices | "Any ideas, John?"
SUSE LINUX Products GmbH, Nürnberg | "Well, surrounding them's out."
This footer brought to you by insane German lawmakers:
SUSE Linux Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Suspend-devel mailing list
Suspend-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/suspend-devel
