On Tuesday, 27 March 2007 22:41, Tim Dijkstra wrote:
> On Tue, 27 Mar 2007 21:18:17 +0200
> "Cédric Boutillier" <[EMAIL PROTECTED]> wrote:
>
> > Hi !
> >
> > Tim said:
> > > Apparently it should be an `unsigned long long', which would make
> > > printf("blkdev: %llu \n", blkdev); the correct way
On 3/27/07, Stefan Seyfried <[EMAIL PROTECTED]> wrote:
> Hehe, i replied on the wrong list :-)
>
> > With this patch people can at least compile and give us some feedback.
>
> ok, some comments inlined.
>
> > int s2ram_prepare(void)
> > {
> > +#ifdef CONFIG_PPC
> > + return 0;
> > +#else
> >
On Tue, 27 Mar 2007 21:18:17 +0200
"Cédric Boutillier" <[EMAIL PROTECTED]> wrote:
> Hi !
>
> Tim said:
> > Apparently it should be an `unsigned long long', which would make
> > printf("blkdev: %llu \n", blkdev); the correct way to print it.
>
> héhé ! I got a non zero result !!! Thanks Tim ! (Sh
Hi,
On Tuesday, 27 March 2007 15:03, Tim Dijkstra wrote:
> Hi,
>
> I was just adding some command line options to s2both when I noticed
> that in fact it didn't went to s3 anymore. I noticed this before, but
> thought that my experimentation with pm-utils was to blams.
>
> Debugging a bit if fou
Hi,
On Tuesday, 27 March 2007 15:18, Tim Dijkstra wrote:
> Hi,
>
> I think we agree that it would be nice for s2both to have the same
> commandline options as s2ram. Well, here is a patch;) A few comments:
>
> The logic I choose for s2both is to continue with suspend-to-disk
> in case of an erro
Hi !
Tim said:
> Apparently it should be an `unsigned long long', which would make
> printf("blkdev: %llu \n", blkdev); the correct way to print it.
héhé ! I got a non zero result !!! Thanks Tim ! (Should I be happy ? :) )
$sudo s2both
suspend: resume_dev = 268462812
blkdev: 771
suspend: Could n
On Tuesday 27 of March 2007, Tim Dijkstra wrote:
> On Tue, 27 Mar 2007 11:55:03 +0200
>
> "Luca Tettamanti" <[EMAIL PROTECTED]> wrote:
> > On 3/27/07, Tim Dijkstra <[EMAIL PROTECTED]> wrote:
> > > This is a first cut at supporting powerpc for s2*. For the s2ram bit it
> > > basically removes the vb
A COLD WINTER STORM WILL BRING SNOW AND LOCALLY GUSTY WINDS TO THE WESTERN
SLOPES OF THE NORTHERN SIERRA NEVADA MOUNTAINS THROUGH TUESDAY MORNING.
SUSTAINED WIND SPEEDS OF AT LEAST 40 MPH OR GUSTS OF 58 MPH OR MORE CAN LEAD TO
PROPERTY DAMAGE.
SNOW LEVELS WILL DROP TO ALL VALLEY FLOORS BY MIDNI
On Tue, Mar 27, 2007 at 02:43:28PM +0100, Matthew Johnson wrote:
> On Tue, Mar 27, 2007 at 12:48:29PM +0200, Stefan Seyfried wrote:
> > And when you pressed enter, did you get a readable prompt or was it
> > all fscked up until you switched to X?
>
> If I suspend from X with -p it works (since it
On Tue, Mar 27, 2007 at 12:48:29PM +0200, Stefan Seyfried wrote:
> On Mon, Mar 26, 2007 at 04:24:58PM +0100, Matthew Johnson wrote:
> > On Mon, Mar 26, 2007 at 05:21:39PM +0200, Stefan Seyfried wrote:
> > >
> > > did -p -m leave the console totally dark, or was it just empty, (but
> > > pressing
On Tue, 27 Mar 2007 13:23:44 +0200
"Cédric Boutillier" <[EMAIL PROTECTED]> wrote:
> Hi !
>
> > Apparently, resume_dev = 268462812 before calling set_swap_file().
> > I've no idea where these 0:0 come from, but I do have idea why it doesn't
> > work. I don't know how to fix that right now, though
On Mon, Mar 26, 2007 at 10:16:19PM -0400, Marten van Kerkwijk wrote:
> Hi Matt, Stefan,
>
> Note that I do not need an additional "-s" as suggested by Matt
> (though that works too). I think that suggestion might be related to
> something I noted while trying different variations, that after "-p"
> > > did -p -m leave the console totally dark, or was it just empty, (but
> > > pressing
> > > enter gave you a new prompt)? I'm asking because the console being empty
> > > is
> > > not a bug but working as expected (this is documented, and somebody who
> > > really cares should probably fix it
Hi,
I think we agree that it would be nice for s2both to have the same
commandline options as s2ram. Well, here is a patch;) A few comments:
The logic I choose for s2both is to continue with suspend-to-disk
in case of an error in the s2ram part. Even if the problem is with cli
options. This is ho
Hi Stefan,
> > Otherwise, I'm mostly curious whether the fact that vga=0 does *not*
> > work for a Dell X200 is unique to this machine. Perhaps the web site
> > should mention it as yet something else to try...
>
> It should actually also work with vga=0. Note that "only garbage on console
> aft
On Mon, Mar 26, 2007 at 05:52:38PM +0200, Bram Senders wrote:
> On Mon, Mar 26, 2007 at 08:45:59AM +0200, Stefan Seyfried wrote:
> > On Fri, Mar 23, 2007 at 01:53:41PM +0100, Bram Senders wrote:
> > > Hi there,
> > >
> > > My machine is not listed in the uswsusp whitelist. It works using "s2ram
On Tue, Mar 27, 2007 at 11:51:15AM +0200, Tim Dijkstra wrote:
> Hi.
>
> Sometimes it seems relevant for the thing calling s2both to know what
> route we took in the end, be it s2ram or s2disk.
>
> Would you think returning a value is a suitable way of communicating
> that to the user? Would some
Hi,
I was just adding some command line options to s2both when I noticed
that in fact it didn't went to s3 anymore. I noticed this before, but
thought that my experimentation with pm-utils was to blams.
Debugging a bit if found out that
ioctl(dev, SNAPSHOT_S2RAM, 0);
sets errno to EBUSY
Hehe, i replied on the wrong list :-)
> With this patch people can at least compile and give us some feedback.
ok, some comments inlined.
> int s2ram_prepare(void)
> {
> +#ifdef CONFIG_PPC
> + return 0;
> +#else
> int ret, id;
>
> dmi_scan();
how about:
#ifdef CONFIG_PPC
#d
Hi Stefan,
Thanks for the comments, I'll integrate them and try to minimize the
number of ifdefs.
On Tue, 27 Mar 2007 13:23:03 +0200
Stefan Seyfried <[EMAIL PROTECTED]> wrote:
> > +#endif
> > + case '?':
>
> Will probably not work, since it is not in options[] above?
getopts return
Hi !
> Apparently, resume_dev = 268462812 before calling set_swap_file().
> I've no idea where these 0:0 come from, but I do have idea why it doesn't
> work. I don't know how to fix that right now, though.
>
> Greetings,
> Rafael
The fact that I got 0:0 might come from the fact that I am far fro
On Mon, Mar 26, 2007 at 04:24:58PM +0100, Matthew Johnson wrote:
> On Mon, Mar 26, 2007 at 05:21:39PM +0200, Stefan Seyfried wrote:
> >
> > did -p -m leave the console totally dark, or was it just empty, (but
> > pressing
> > enter gave you a new prompt)? I'm asking because the console being empt
On Mon, Mar 26, 2007 at 10:16:19PM -0400, Marten van Kerkwijk wrote:
> Hi Matt, Stefan,
>
> OK, so I finally have a working s2ram on my Dell X200!! I first
good :-)
> So, Matt, perhaps you can:
> * confirm that -p -m is sufficient after starting up the machine?
> * check that somewhere or othe
On Mon, Mar 26, 2007 at 08:38:29PM +0200, TRex2003 wrote:
> Hi,
>
> I have a Compaq N610c with debian testing installed. s2disk is working
> fine, but s2ram...i don´t get it working.
>
> Tested (with init=/bin/bash):
[ all combinations ]
> and
>
> > ATI Graphics Chipsets
> > Lately many mach
On Tuesday, 27 March 2007 12:17, Tim Dijkstra wrote:
> On Tue, 27 Mar 2007 12:11:34 +0200
> "Rafael J. Wysocki" <[EMAIL PROTECTED]> wrote:
>
> > On Tuesday, 27 March 2007 11:51, Tim Dijkstra wrote:
> > > Hi.
> > >
> > > Sometimes it seems relevant for the thing calling s2both to know what
> > > r
On Tuesday, 27 March 2007 12:09, Tim Dijkstra wrote:
> On Tue, 27 Mar 2007 11:55:03 +0200
> "Luca Tettamanti" <[EMAIL PROTECTED]> wrote:
>
> > On 3/27/07, Tim Dijkstra <[EMAIL PROTECTED]> wrote:
> > > This is a first cut at supporting powerpc for s2*. For the s2ram bit it
> > > basically removes t
On Tue, 27 Mar 2007 12:11:34 +0200
"Rafael J. Wysocki" <[EMAIL PROTECTED]> wrote:
> On Tuesday, 27 March 2007 11:51, Tim Dijkstra wrote:
> > Hi.
> >
> > Sometimes it seems relevant for the thing calling s2both to know what
> > route we took in the end, be it s2ram or s2disk.
> >
> > Would you th
On Tue, 27 Mar 2007 11:55:03 +0200
"Luca Tettamanti" <[EMAIL PROTECTED]> wrote:
> On 3/27/07, Tim Dijkstra <[EMAIL PROTECTED]> wrote:
> > This is a first cut at supporting powerpc for s2*. For the s2ram bit it
> > basically removes the vbetool code. This has two reasons. First, there
> > isn't a p
On Tuesday, 27 March 2007 11:51, Tim Dijkstra wrote:
> Hi.
>
> Sometimes it seems relevant for the thing calling s2both to know what
> route we took in the end, be it s2ram or s2disk.
>
> Would you think returning a value is a suitable way of communicating
> that to the user? Would some scripts m
On 3/27/07, Tim Dijkstra <[EMAIL PROTECTED]> wrote:
> This is a first cut at supporting powerpc for s2*. For the s2ram bit it
> basically removes the vbetool code. This has two reasons. First, there
> isn't a powerpc version of libx86 yet. Second, the machines that have
> support for s2ram in the k
Hi.
Sometimes it seems relevant for the thing calling s2both to know what
route we took in the end, be it s2ram or s2disk.
Would you think returning a value is a suitable way of communicating
that to the user? Would some scripts maybe break, because they only
expect 0 in case of success?
grts Ti
Hi,
This is a first cut at supporting powerpc for s2*. For the s2ram bit it
basically removes the vbetool code. This has two reasons. First, there
isn't a powerpc version of libx86 yet. Second, the machines that have
support for s2ram in the kernel don't need those hacks.
As you noticed, I've ask
32 matches
Mail list logo
