Hi Matt, Stefan,
OK, so I finally have a working s2ram on my Dell X200!! I first
thought it was related to the fact that Matt used intelfb while I did
not, but it turned out the trick is to have vga=792 (=0x318) as a boot
option (with or without intelfb; surprisingly vga=773, which should be
the
On Monday, 26 March 2007 00:29, Luca Tettamanti wrote:
> On 3/25/07, Rafael J. Wysocki <[EMAIL PROTECTED]> wrote:
> > On Sunday, 25 March 2007 18:13, Cédric Boutillier wrote:
> > > Hi !
> > >
> > > > Could you print out `blkdev'? Just to be sure, could you send the
> > > > output of
> > > > ls -l
On Monday, 26 March 2007 15:40, Stefan Seyfried wrote:
> On Mon, Mar 26, 2007 at 12:36:09PM +0200, Rafael J. Wysocki wrote:
> > On Monday, 26 March 2007 11:07, Stefan Seyfried wrote:
> > > Hi,
> > >
> > > after reading this thread, i got the impression that we do not report
> > > errors verbosely
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):
s2ram -f -a 1
s2ram -f -a 2
s2ram -f -a 3
s2ram -f -p -m
s2ram -f -p -s
s2ram -f -m
s2ram -f -s
s2ram -f -p
s2ram -f -a 1 -m
s2ram -f -a 1 -s
and
On Mon, Mar 26, 2007 at 05:20:58PM +0200, Tim Dijkstra wrote:
> On Thu, 22 Mar 2007 13:29:15 +0100
> Stefan Seyfried <[EMAIL PROTECTED]> wrote:
>
> > Hi,
> >
> > (sending a new mail, so that it does not get lost in the old thread)
> >
> > If nobody objects, i will rip out the libx86 build option
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
> > -f"
> > without having to provide additional parameters.
> >
> > [E
On Mon, Mar 26, 2007 at 05:21:39PM +0200, Stefan Seyfried wrote:
> On Mon, Mar 26, 2007 at 03:17:29PM +0100, Matthew Johnson wrote:
> > On Mon, Mar 26, 2007 at 09:02:19AM +0200, Stefan Seyfried wrote:
> > > On Mon, Mar 26, 2007 at 04:18:13AM +0100, Matthew Johnson wrote:
> > > > On Sun, Mar 25, 200
On Mon, Mar 26, 2007 at 03:17:29PM +0100, Matthew Johnson wrote:
> On Mon, Mar 26, 2007 at 09:02:19AM +0200, Stefan Seyfried wrote:
> > On Mon, Mar 26, 2007 at 04:18:13AM +0100, Matthew Johnson wrote:
> > > On Sun, Mar 25, 2007 at 09:05:32PM -0400, Marten van Kerkwijk wrote:
> > > > Dear Matt,
> >
On Thu, 22 Mar 2007 13:29:15 +0100
Stefan Seyfried <[EMAIL PROTECTED]> wrote:
> Hi,
>
> (sending a new mail, so that it does not get lost in the old thread)
>
> If nobody objects, i will rip out the libx86 build option from the
> Makefile. I will not do this today or tomorrow, but as time permit
On Mon, Mar 26, 2007 at 09:02:19AM +0200, Stefan Seyfried wrote:
> On Mon, Mar 26, 2007 at 04:18:13AM +0100, Matthew Johnson wrote:
> > On Sun, Mar 25, 2007 at 09:05:32PM -0400, Marten van Kerkwijk wrote:
> > > Dear Matt,
> > >
> > > I was very interested to see you say that
> > >
> > > > I also
On Mon, Mar 26, 2007 at 08:59:10AM +0200, Stefan Seyfried wrote:
> On Sun, Mar 25, 2007 at 11:06:04AM +0100, Matthew Johnson wrote:
> > I have an Asus M2V which I tried using s2ram on. It works fine with no
> > workarounds, but is listed as unknown. The output of s2ram -i is:
>
> Does it work from
On Mon, Mar 26, 2007 at 12:36:09PM +0200, Rafael J. Wysocki wrote:
> On Monday, 26 March 2007 11:07, Stefan Seyfried wrote:
> > Hi,
> >
> > after reading this thread, i got the impression that we do not report
> > errors verbosely enough. I mean - we normally never see those messages,
> > but if w
On Mon 2007-03-26 12:36:09, Rafael J. Wysocki wrote:
> On Monday, 26 March 2007 11:07, Stefan Seyfried wrote:
> > Hi,
> >
> > after reading this thread, i got the impression that we do not report
> > errors verbosely enough. I mean - we normally never see those messages,
> > but if we do, due to a
Hi,
(i re-added suspend-devel to cc)
On Mon, Mar 26, 2007 at 01:00:21PM +0200, Christoph Wiesmeyr wrote:
> Unfortunately it only works from the console. If I use the KDE menu for
good.
> suspend the only thing that happens is that the current user is locked. Same
> with the hotkey on the keyb
On Mon, 26 Mar 2007 11:07:59 +0200
Stefan Seyfried <[EMAIL PROTECTED]> wrote:
> Hi,
>
> after reading this thread, i got the impression that we do not report
> errors verbosely enough. I mean - we normally never see those messages,
> but if we do, due to an error having happened, we always need t
On Monday, 26 March 2007 11:07, Stefan Seyfried wrote:
> Hi,
>
> after reading this thread, i got the impression that we do not report
> errors verbosely enough. I mean - we normally never see those messages,
> but if we do, due to an error having happened, we always need to start
> adding more de
Hi,
after reading this thread, i got the impression that we do not report
errors verbosely enough. I mean - we normally never see those messages,
but if we do, due to an error having happened, we always need to start
adding more debugging printf's before we know what happened.
Oh, yes, and pm-ops
17 matches
Mail list logo
