Hi!
> I've already sent a similar post to the linux-acpi list some time ago, but
> since I didn't get a response yet maybe this is the more appropriate place to
> post. (Suggestions on where else to post are very welcome...).
>
>
> Here's a summary of my problem:
>
> After doing a s2ram cycle
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:
[EMAIL PROTECTED]:~ $ sudo s2ram -i
This machine can be identified by:
sys_vendor = "System manufacturer"
sys_product = "System Product Name"
sys_ver
On Sun, Mar 25, 2007 at 11:06:03AM +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:
I also have a dell X200 which works with the -p and -s workarounds. The
output of s2ram -i o
On Sunday, 25 March 2007 01:14, Tim Dijkstra wrote:
> On Sun, 25 Mar 2007 00:17:22 +0100
> "Cédric Boutillier" <[EMAIL PROTECTED]> wrote:
>
> > > Which kernel are you using? Could you try to catch the error code that
> > > s2both returns? Or just add two printf's that print out the error code?
> >
Hi !
> Could you print out `blkdev'? Just to be sure, could you send the output of
> ls -l /dev/hda3 ?
I didn't know exactly how to print blkdev, but I finally managed to
write something.
error = ioctl(dev, SNAPSHOT_SET_SWAP_AREA, &swap);
printf("Error: errno = %d\n", errno);
if
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 /dev/hda3 ?
>
> I didn't know exactly how to print blkdev, but I finally managed to
> write something.
>
> error = ioctl(dev, SNAPSHOT_SET_S
On 3/25/07, Rafael J. Wysocki <[EMAIL PROTECTED]> wrote:
> Hm, this shouldn't be 0:0 in any case.
>
> Can you please post your suspend.conf?
>
> Rafael
>
Here is the content of the file:
% cat /etc/uswsusp.conf
# /etc/uswsusp.conf(8) -- Configuration file for s2disk/s2both
resume device = /dev/hd
On Sunday, 25 March 2007 21:08, Cédric Boutillier wrote:
> On 3/25/07, Rafael J. Wysocki <[EMAIL PROTECTED]> wrote:
> > Hm, this shouldn't be 0:0 in any case.
> >
> > Can you please post your suspend.conf?
> >
> > Rafael
> >
> Here is the content of the file:
>
> % cat /etc/uswsusp.conf
>
> # /et
Hi,
[sorry for the delay]
On Monday, 19 March 2007 22:07, Couriousous wrote:
> Hello
>
> When I use the compression with uswsusp, the suspend step take longer than
> without. This is in fact because uswsusp write the data synchronously to the
> disk. So while it take time to compress the data
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 /dev/hda3 ?
> >
> > I didn't know exactly how to print blkdev, but I
Dear Matt,
I was very interested to see you say that
> I also have a dell X200 which works with the -p and -s workarounds. The
> output of s2ram -i on that is:
>
> [EMAIL PROTECTED]:~ $ sudo s2ram -i
> This machine can be identified by:
> sys_vendor = "Dell Computer Corporation"
> sys_
On Sun, Mar 25, 2007 at 09:05:32PM -0400, Marten van Kerkwijk wrote:
> I just tried again, and s2ram -f -p -s just kills my system (like all
> other combinations): it suspends fine, but on resume, it starts but
> then dies, screen remaining dark, CAPS LOCK not working, etc. This
> both from X an
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 have a dell X200 which works with the -p and -s workarounds. The
> > output of s2ram -i on that is:
Hmm... Maybe I don't have working s2ram. I now have rea
On Thu, Mar 22, 2007 at 02:58:09PM +0100, Reiner Herrmann wrote:
> Am Donnerstag, 22. März 2007 schrieb Stefan Seyfried:
> > On Tue, Mar 20, 2007 at 07:48:03PM +0100, Reiner Herrmann wrote:
> > > Hi,
> > >
> > > the following notebook works with "s2ram -f -s":
> > > sys_vendor = "FUJITSU SIE
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.
>
> [EMAIL PROTECTED]:/usr/share/doc/uswsusp$ sudo s2ram -i
> This machine can be identifi
On Fri, Mar 23, 2007 at 06:50:06PM +0100, Christoph Wiesmeyr wrote:
> Dear Developers!
>
>
> I have tried to use s2ram on my laptop though it was not on the list with the
> supported models. it tourned out that the suspend works rightaway
> with "s2ram -f"
Thanks for reporting. Does it work fr
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 both X and from text console?
> [EMAIL PROTECTED]:~ $ sudo s2ram -i
> Th
On Sun, Mar 25, 2007 at 11:15:14AM +0100, Matthew Johnson wrote:
> On Sun, Mar 25, 2007 at 11:06:03AM +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:
>
> I also have a del
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 have a dell X200 which works with the -p and -s workarounds. The
> > > output o
19 matches
Mail list logo
