Greetings glorious s2ram developers,
I got a Lenovo 3000 v100 for christmas, expecting suspend would work
well based on other people's reports. Turns out there are many
sub-models of 3000 v100, and mine is the 0763-4CU which has a core2duo
7200 processor.
I've run s2ram -f to get it to suspend,
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 details.
-f -a 1 - works even for X.
/Ole
--
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 suspend to ram worked for me on linux!
> >
> > Here's the output of s2ram -i:
>
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 "
most of the time "s2ram -f" / "s2disk -f" just works. Unfortunately, I
do not know
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 suspend to ram worked for me on linux!
>
> Here's the output of s2ram -i:
> This machine can be identified by:
> sys_vendor = "IBM"
>
Hi!
> Sorry, it should probably not go in the white list yet. I once
> suspended to ram and the display was problematic - it had problems
> with repaint and moving, so things looked really strange. It went away
> when I suspended to disk again. In all other times, it worked fine.
It is probably "
