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
"Jasper Mackenzie" <[EMAIL PROTECTED]> writes:
> Good Day Ross,
> I'me using debian unstable and kernel 2.6.21.1 (not debian) but cant even
> get resume to begin. Can you please tell me how you've got thus far so I can
> also confirm (or otherwise) this behaviour with debian unstable.
> I assume
Good Day Ross,
I'me using debian unstable and kernel 2.6.21.1 (not debian) but cant even
get resume to begin. Can you please tell me how you've got thus far so I can
also confirm (or otherwise) this behaviour with debian unstable.
I assume your are using the uswsusp package.
cheers
Jasper
_
On Tue, May 08, 2007 at 07:23:08PM +0200, Markus Pöschl wrote:
> This machine can be identified by:
> sys_vendor = "VIA Technologies, Inc."
> sys_product = "VT8623-8235"
> sys_version = " "
> bios_version = "6.00 PG"
>
> The first setting in the list which are working are
> s2r
Good day,
I have managed to get a Clevo D470K working with s2ram under the following
conditions:
Bios, OS set to "other", not Win9x/xp
Video driver using radeon from xorg NOT fglrx
vga=0
I have additionaly got acpi_sleep=s3_bios in lilo, but i assume its actualy
unescesary.
sys_vendor = "VIA"
On Mon, May 07, 2007 at 10:42:37AM -0500, Dhananjaya Rao wrote:
> Hi,
>
> My machine isn't listed in the whitelist, but s2ram -f appears to work
> fine from both X and the console. The options -s, -a2 and -a3 also work.
> The output of s2ram -i is:
>
> # s2ram -i
> This machine can be identified
It works fine in both cases. I just use the -f option.
++
Stefan Seyfried wrote:
> On Wed, May 09, 2007 at 11:45:07AM +0200, Benoit Thiell wrote:
>> Hi,
>>
>> thanks for the great work ! :)
>>
>> Output of "s2ram -i" is :
>>
>> This machine can be identified by:
>> sys_vendor = "NEC COMPUT
On Thu, May 10, 2007 at 04:13:39PM -0700, Benjamin Cherian wrote:
> Hi,
>
> I recently tried s2ram and it said my computer wasn't supported. However,
> running s2ram -f (without any other options) worked for me. I've attached
> the output of s2ram -i.
>
> If you need any other information feel fr
On Wed, May 09, 2007 at 01:58:17AM +0700, VAnhTu1987 wrote:
> This machine can be identified by:
> sys_vendor = "Acer, inc."
> sys_product = "Aspire 5580 "
> sys_version = "Not Applicable"
> bios_version = "v1.3206"
>
> I'm running Ubuntu Feisty server (kernel 2.6.20). I've
On Tue, May 15, 2007 at 02:53:09PM +0200, dlugilin wrote:
> s2ram -i
> This machine can be identified by:
> sys_vendor = "TOSHIBA"
> sys_product = "Satellite A50"
> sys_version = "PSA50E-07202VPL"
> bios_version = "Version 1.30"
> See http://en.opensuse.org/S2ram for details.
>
On Wed, May 09, 2007 at 11:45:07AM +0200, Benoit Thiell wrote:
> Hi,
>
> thanks for the great work ! :)
>
> Output of "s2ram -i" is :
>
> This machine can be identified by:
> sys_vendor = "NEC COMPUTERS INTERNATIONAL"
> sys_product = "NEC Versa Premium"
> sys_version = "FAB-2"
On Mon, May 07, 2007 at 11:42:48AM +0100, Neil Burgess wrote:
> Hiya - my laptop was not directly supported by s2ram - however I seem to have
> found a working setting.
>
> The machine (with NVIDIA drivers installed):
>
> NBurgess07Linux:~ # s2ram -i
> This machine can be identified by:
> sy
On Mon, May 14, 2007 at 10:39:06PM +0200, Ralph Thormann wrote:
> hello,
>
> i'm using s2ram from the ubuntu package:
>
> uswsusp 0.3~cvs20060928-6ubuntu3
>
> s2ram -i tells me:
>
> s2ram -i
> This machine can be identified by:
> sys_vendor = "IBM"
> sys_product = " "
>
On Tue, May 08, 2007 at 01:09:05PM +0200, Per Waagø wrote:
> s2ram -f simply works on my computer.
>
> s2ram -i gives this output:
> This machine can be identified by:
> sys_vendor = "Packard Bell NEC"
> sys_product = "000"
> sys_version = "P820008416"
> bio
Hi,
On Sat, May 12, 2007 at 10:18:36PM +0200, Tim Dijkstra wrote:
> Hi,
>
> OK, it turns out that my last patch for adding comments to usage had a
> horrible bug. Although (struct option_descr) would yield a (struct option),
> as anticipated, the increment of the pointers of these structs ofcour
On Sun, May 13, 2007 at 11:08:42PM +0200, Robert Lange wrote:
> Dear All,
>
> Just want to inform you that s2ram is working in my system without any
> further options and problems, just t"s2ram -f" does the trick.
>
> sudo s2ram -i
> This machine can be identified by:
> sys_vendor = "System
On Sun, May 06, 2007 at 10:13:03PM +0200, Ulf Lange wrote:
> Hello,
>
> you can add this PC to your whitelist. I used the build in VGA card (Fujitsu
> Siemens i845).
>
> # uname -r
> 2.6.18.8-0.3-default
> # s2ram -i
> This machine can be identified by:
> sys_vendor = "FUJITSU SIEMENS"
>
On Fri, May 04, 2007 at 11:56:44PM -0500, [EMAIL PROTECTED] wrote:
> My machine works perfectly with "sudo s2ram -f" from terminal,
> so I assume it's safe to add to the whitelist.
>
> sudo s2ram -i:
>
> This machine can be identified by:
> sys_vendor = "ASUSTeK Computer Inc. "
> sys_pr
On Thu, May 03, 2007 at 06:36:24PM -0400, David Zeuthen wrote:
> On Thu, 2007-05-03 at 23:24 +0200, Danny Kukawka wrote:
> > On Donnerstag, 3. Mai 2007, Richard Hughes wrote:
> > > On Thu, 2007-05-03 at 13:40 -0400, David Zeuthen wrote:
> > > > Ugh.. Hope I didn't start a flamewar here... I'm just
On Thu, May 03, 2007 at 06:20:16PM +0200, Sven Foerster wrote:
> s2ram works fine on my maschine
> but it is on the blacklist
There is no blacklist.
> This machine can be identified by:
> sys_vendor = "Acer, inc."
> sys_product = "TravelMate C200 "
> sys_version = "Not Applicable
On Sat, May 05, 2007 at 09:23:41AM -0400, Michael Kimsal wrote:
> This machine can be identified by:
>sys_vendor = "Hewlett-Packard"
>sys_product = "Presario V5000 (ET826UA#ABA) "
>sys_version = "F.33"
>bios_version = "F.33"
>
>
> This combination works, with one exceptio
On Wed, May 02, 2007 at 03:57:34PM +0200, Jörn Dreyer wrote:
> I can report partial success with
>
> ~$ sudo s2ram -i
> This machine can be identified by:
> sys_vendor = "FUJITSU SIEMENS"
> sys_product = "CELSIUS H240"
> sys_version = " "
> bios_version = "Version 1.11 "
>
> m
On Fri, May 04, 2007 at 09:13:40PM +0200, Martin Heimes wrote:
> Hello,
>
> > My machine is not in the whitelist (...)
>
> all S3 options in BIOS set to enabled
>
>
> revo:~# s2ram -i
> This machine can be identified by:
> sys_vendor = "Compaq"
> sys_product = "Evo D510 USDT"
>
On Thu, May 03, 2007 at 01:47:32AM +0200, Ole Tange wrote:
> Machine is unknown.
> This machine can be identified by:
> sys_vendor = "TOSHIBA"
> sys_product = "PORTEGE M400"
> sys_version = "PPM40E-1S702LED"
> bios_version = "Version 2.10"
> See http://en.opensuse.org/S2ram for
Hi Michele,
> Basically I have an Asus M2NPV-VM board and I was not able to make suspend to
> ram working and I posted a message sometime ago.
hmm, lucky for me I did not had to do anything. It really worked out of
the box - which caught my by (pleasant) surprise.
> I am interested in your exper
On Mon, Apr 30, 2007 at 11:36:49AM +0200, root hhj wrote:
> This machine can be identified by:
> sys_vendor = "TOSHIBA"
> sys_product = "Portable PC"
> sys_version = "Version 1.0"
> bios_version = "Version 1.20"
>
> after installing latest version of
> "http://software.opensus
On Sat, Apr 28, 2007 at 09:14:43AM -0700, Mario Nigrovic wrote:
> I've found that
>
> s2ram -f -a 1
>
> works for
>
> s2ram -i:
>
> This machine can be identified by:
> sys_vendor = "Gateway "
> sys_product = "MT6707 "
> sys_versi
On Sun, Apr 29, 2007 at 02:46:27AM -0400, Lathan Bidwell wrote:
> My Dell Inspiron 9400 has the following s2ram -i information:
>
> This machine can be identified by:
> sys_vendor = "Dell Inc."
> sys_product = "MP061 "
> sys_version = ""
> bios_version
On Sun, Apr 29, 2007 at 01:43:16PM +0200, [EMAIL PROTECTED] wrote:
> Hi,
>
> This is a report of working s2ram:
>
> This machine can be identified by:
> sys_vendor = "MSI."
> sys_product = "MS-7207PV"
> sys_version = "100"
> bios_version = "080012 "
>
> I simply used "s2ram -
On Fri, Apr 27, 2007 at 10:54:33AM -0400, Sergei Serdyuk wrote:
> Hi,
>
> You may want to add this to the whitelist. s2ram works perfectly for my
> on Ubuntu 7.04
>
> [EMAIL PROTECTED]:~$ sudo s2ram -i
> This machine can be identified by:
> sys_vendor = "Acer"
> sys_product = "Aspire 3
On Wed, May 02, 2007 at 06:18:17PM +0300, Noam Raphael wrote:
> On 02/05/07, Pavel Machek <[EMAIL PROTECTED]> wrote:
> > On Fri 2007-04-27 18:06:06, Noam Raphael wrote:
> > > Hello,
> > >
> > > I tried s2ram, and wasn't on the whitelist, but it seems to work fine.
> > > Hurray! The first time suspe
On Wed, Apr 25, 2007 at 10:25:00PM +0200, Ulf wrote:
> Hello,
>
> just tested "s2ram -f" from suspend-0.50.20070328-6.1 with WoL.
> lmc:~ # s2ram -f
> Switching from vt7 to vt1
> # Sending Magic WoL => Back again
> switching back to vt7
> lmc:~ # s2ram -i
> This machine can be identified by:
>
On Wed, Apr 25, 2007 at 06:05:25AM +0300, Baruch Even wrote:
> Hi,
>
> As per the s2ram instructions on http://en.opensuse.org/S2ram I email
> you the report for my MSI S420, I got it to work with the options of:
> s2ram -f -p -s
>
> This only worked without framebuffer, and it works for console
On Sat, Apr 28, 2007 at 02:51:33PM +0300, [EMAIL PROTECTED] wrote:
> Hi,
>
> I just bought a new portable.
>
> I added the force option in /etc/pm/config and suspend to ram started working
> just fine.
>
> But here is the output:
> Machine is unknown.
> This machine can be identified by:
>
On Tue, Apr 24, 2007 at 11:33:43PM -0300, Cristian S. Rocha wrote:
> Hello,
>
> I test "s2ram -f" in my Notebook and it works fine. Could you append it
> into the whitelist? The "s2ram -i" output is:
>
> gator:~# s2ram -i
> This machine can be identified by:
> sys_vendor = "Hewlett-Packard"
On Sat, Apr 21, 2007 at 04:47:54PM +0100, Armindo Silva wrote:
> Hi!
>
>
> On this machine the s2ram -f just works!
>
>
> orbiting:~ # s2ram -i
> This machine can be identified by:
>sys_vendor = "Sony Corporation"
>sys_product = "VGN-FE31M"
>sys_version = "C3LMR93D"
>bios_ve
On Sun, Apr 22, 2007 at 10:35:35AM +0200, Tom wrote:
> Hello
>
> I just tried s2ram on my machine (using s2ram -f only), and it just worked
> without problems (I tried from within X (KDE in Kubuntu)).
> According to the Debian "README.s2ram-whitelist" I'm writing to this list to
> report my mach
On Fri, Apr 20, 2007 at 09:37:15AM +0200, Frank wrote:
> Hi,
>
> I finally got suspend-to-ram working on my Hewlett-Packard/Compaq tc4200. I
> basically only had a distribution problem (Ubuntu Feisty), but s2ram seems
> not to work without -f (I'm using it with powersaved). So maybe these
> inf
Stefan Seyfried wrote:
> [forgot to cc the list on the first try, sorry]
>
> On Wed, Apr 18, 2007 at 10:29:22PM +0200, Guenther Schwarz wrote:
>> xxx:~ # s2ram -i
>> This machine can be identified by:
>> sys_vendor = "ASUSTeK Computer Inc."
>> sys_product = "M2N "
>> s
[forgot to cc the list on the first try, sorry]
On Wed, Apr 18, 2007 at 10:29:22PM +0200, Guenther Schwarz wrote:
> xxx:~ # s2ram -i
> This machine can be identified by:
> sys_vendor = "ASUSTeK Computer Inc."
> sys_product = "M2N "
> sys_version = "1.0 "
> b
40 matches
Mail list logo
