On Thursday, 17 May 2007 12:50, Tim Dijkstra wrote:
> On Thu, 17 May 2007 11:59:37 +0200
> "Rafael J. Wysocki" <[EMAIL PROTECTED]> wrote:
>
> > On Thursday, 17 May 2007 00:14, Tim Dijkstra wrote:
> > > Hi,
> > >
> > > I've got an report of a laptop that works with
> > > s2ram --vbe_save --vbe_
On Thu, 17 May 2007 11:59:37 +0200
"Rafael J. Wysocki" <[EMAIL PROTECTED]> wrote:
> On Thursday, 17 May 2007 00:14, Tim Dijkstra wrote:
> > Hi,
> >
> > I've got an report of a laptop that works with
> > s2ram --vbe_save --vbe_post
> >
> > But doesn't for s2both with the same options.
> >
>
On Thursday, 17 May 2007 00:14, Tim Dijkstra wrote:
> Hi,
>
> I've got an report of a laptop that works with
> s2ram --vbe_save --vbe_post
>
> But doesn't for s2both with the same options.
>
> What does work however is
> s2both -a 1
>
> Somehow the difference in code path in s2both
Hi,
I've got an report of a laptop that works with
s2ram --vbe_save --vbe_post
But doesn't for s2both with the same options.
What does work however is
s2both -a 1
Somehow the difference in code path in s2both is significant from that of
s2ram (which basically does echo mem > /s
