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
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_product = "W3J "
sys_version = "1.0 "
bios_version =
Few things changed here, but that is not problem. I have tested things only
in "init=/bin/bash", not runlevel 5. Suspend and resume still works
in "init=/bin/bash".
I think this problem has some sonnection to vesafb or ... Anyway, solution is
to use "-f -s" option. This way suspend goes little
On Tue, Mar 20, 2007 at 07:31:10PM +0100, Aleksandar Markovic wrote:
> I have new version of suspend and my machine is in the whitelist. With
> default
> option machine allways come back from suspend (let say I have done it about
> 100 times). But, console (text console) is, after resume, unusab
I have new version of suspend and my machine is in the whitelist. With default
option machine allways come back from suspend (let say I have done it about
100 times). But, console (text console) is, after resume, unusable.
This is description of the console unusability: it is possible to switch
On Mon, Feb 05, 2007 at 03:52:29AM +0100, Aleksandar Markovic wrote:
> s2ram -i
>
> This machine can be identified by:
> sys_vendor = "FUJITSU SIEMENS"
> sys_product = "AMILO PRO V2030"
> sys_version = "20"
> bios_version = "1.0I-2309-8A20"
>
> Test results, after booting with
s2ram -i
This machine can be identified by:
sys_vendor = "FUJITSU SIEMENS"
sys_product = "AMILO PRO V2030"
sys_version = "20"
bios_version = "1.0I-2309-8A20"
Test results, after booting with “init=/bin/bash” and “mount /proc”
and “mount /sys”:
Legend:
O = option used with “s
