Stefan Seyfried wrote:
> On Fri, Jul 27, 2007 at 11:08:26AM +0300, George Tellalov wrote:
>> Hello,
>>
>> I have a Thinkpad 600e and I've found that s2ram sort of works. It needs "-f
>> -p -m" or otherwise the vga mode is messed up.
>
> Does it also work with "-a 3"? Most of the slightly newe
using -a 3 reinitializes the screen/(video adapter) badly, showing white
and then slowly and unevenly fading to black: probably the melting screen
you mentioned
It does respond to stuff in that state (no crash), like sysRq commands, or
rebooting with ctrl-alt del (after switching to a vt)
Stefan Seyfried wrote:
> On Mon, Jul 23, 2007 at 02:37:08PM +0200, Joel Schaerer wrote:
>> Hi there,
>>
>> my machine is identified as follows:
>>
>> This machine can be identified by:
>> sys_vendor = "Compaq "
>> sys_product = "Evo N800w "
>> sys_version
On 7/30/07, Stefan Seyfried <[EMAIL PROTECTED]> wrote:
>> Why do you forward people to suse URLs on whitelist?
>> I would have expected all be forwarded to suspend.sf.net...
>> http://en.opensuse.org/S2ram belongs to the project site... not
>> distribution specific site.
> Ok, so i'm going to take
hello,
I found a commandline that works for my laptop (I'm using ubuntu feisty)
s2ram -f -a3
s2ram --test
Machine is unknown.
This machine can be identified by:
sys_vendor = "TOSHIBA"
sys_product = "Satellite P200"
sys_version = "PSPB0E-01900JG3"
bios_version = "V1.40"
can
On Mon, Jul 30, 2007 at 02:45:53PM +0300, Antti Laine wrote:
> Stefan Seyfried wrote:
> >># s2ram -i
> >>This machine can be identified by:
> >> sys_vendor = "Hewlett-Packard"
> >> sys_product = "HP Compaq nc4400 (EY605EA#AK8)"
> >> sys_version = "F.09"
> >> bios_version = "68YH
On Monday, 30 July 2007 08:56, Stefan Seyfried wrote:
> On Fri, Jul 27, 2007 at 08:45:41PM +0200, Rafael J. Wysocki wrote:
> > On Friday, 27 July 2007 18:33, Stefan Seyfried wrote:
> > > On Fri, Jul 27, 2007 at 05:18:45PM +0200, Rafael J. Wysocki wrote:
> > >
> > > > > (yes, i think i know what it
On Mon, Jul 30, 2007 at 10:20:10AM +0200, Hendrik-Jan Heins wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hello Stefan,
>
> "# s2ram -a 1 -m" gives:
> "The acpi_sleep, vbe_save, vbe_post, radeontool and pci_save parameters
> must be used with --force"
>
> So it just won't work, I
On Sat, Jul 28, 2007 at 04:28:21PM +0530, Arun Raghavan wrote:
> On 7/27/07, Stefan Seyfried <[EMAIL PROTECTED]> wrote:
> > On Mon, Jul 23, 2007 at 12:46:04AM +0530, Arun Raghavan wrote:
>
> > Are you using a framebuffer? If yes, try booting with "vga=0" for a
> > plain VGA console. There are mach
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello Stefan,
"# s2ram -a 1 -m" gives:
"The acpi_sleep, vbe_save, vbe_post, radeontool and pci_save parameters
must be used with --force"
So it just won't work, I only get that message.
"s2ram -f -a1 -m" works, but I don't always seem to get the ba
On Mon, Jul 30, 2007 at 12:06:02AM +0200, Alexandr Kara wrote:
> Hello,
> I can succesfully suspend and resume (with loosing only WiFi connection)
> a machine that is not in the database:
>
> s2ram -i produces this:
>
> sys_vendor = "FUJITSU SIEMENS"
> sys_product = "AMILO Pro Edition
On Sun, Jul 29, 2007 at 05:03:55PM -0500, Justin Ferguson wrote:
>
> This machine can be identified by:
> sys_vendor = "Dell Inc."
> sys_product = "MP061 "
> sys_version = ""
> bios_version = "A08"
>
> s2ram -f (no other arguments) works like a charm
On Sun, Jul 29, 2007 at 02:56:12PM +0300, Antti Laine wrote:
> Hi. I have a HP Compaq nc4400 notebook pc which doesn't seem to be on
> suspend's whitelist, but works just fine with --force with the latest
> bios (it did not work with the old bios it had in it when a got the
> computer). Here
On Fri, Jul 27, 2007 at 11:14:09PM +0100, Robert Hart wrote:
>
> My laptop suspends properly from both X and console without any parameters
> passed to s2ram.
>
> # s2ram -i
> This machine can be identified by:
> sys_vendor = "Hewlett-Packard"
> sys_product = "HP Pavilion dv2500 Noteb
On Fri, Jul 27, 2007 at 08:45:41PM +0200, Rafael J. Wysocki wrote:
> On Friday, 27 July 2007 18:33, Stefan Seyfried wrote:
> > On Fri, Jul 27, 2007 at 05:18:45PM +0200, Rafael J. Wysocki wrote:
> >
> > > > (yes, i think i know what it does; writing 1 into the state of the
> > > > framebuffer devic
On Sat, Jul 28, 2007 at 08:24:56PM +0200, Manuel Bernhardt wrote:
> Stefan Seyfried schrieb:
> >> please whitelist following board:
> >>
> >> sys_vendor = "System manufacturer"
> >> sys_product = "System Product Name"
> >> sys_version = "System Version"
> >> bios_version = "ASUS
On Sat, Jul 28, 2007 at 01:30:29AM +0800, Kanru Chen wrote:
> On Fri, Jul 27, 2007 at 06:16:55PM +0200, Stefan Seyfried wrote:
> > I'd guess that you get more luck from the console with
> > s2ram -f -a3
> > or
> > s2ram -f -p -m
> >
> > if this does not help, reading http://en.opensuse.org/S2ram m
On Fri, Jul 27, 2007 at 07:24:31PM +0300, Alon Bar-Lev wrote:
> On 7/27/07, Stefan Seyfried <[EMAIL PROTECTED]> wrote:
> > But i am not the one to decide this, as i am only maintaining a small piece
> > of the code (mainly the whitelist).
>
> Why do you forward people to suse URLs on whitelist?
>
On Fri, Jul 27, 2007 at 07:38:52PM +0200, Pavel Machek wrote:
> If the needed quirks differ between otherwise identical i386 and
> x86-64 installation, I'd like to know. That means there's serious
> problem somewhere.
Well, the '-a' quirks not working on x86_64 - that does not surprise
me at all
On Sun, Jul 29, 2007 at 10:54:01PM +0200, Hendrik-Jan Heins wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hello Pavel, list,
>
> Today I did some extensive testing with both i386 and amd64 in the X61s.
> The results are somewhat surprising (yes, to me too).
> First: I currently use
On Fri, Jul 27, 2007 at 07:41:27PM +0200, Pavel Machek wrote:
> Hmm, yes, I guess I want to now. So you have thinkpad that is broken
> with -a1 -m, in 64-bit mode only? And no other differences? (Like,
> same kernel framebuffer driver, both time from console?)
I have a thinkpad on my desk (T61 wi
On Mon, Jul 30, 2007 at 03:31:43AM +, Joe Nahmias wrote:
> On Tue, Jul 17, 2007 at 05:00:42PM +0200, Stefan Seyfried wrote:
> > But "-a3" works, too? Then i'd take that one, since most thinkpads
> > work well with "-a 3" and i'd like to avoid too many special cases.
>
> Yes, -a3 works as well.
On Sat, Jul 28, 2007 at 12:20:00AM +0200, maestro wrote:
> Hello Stefan!
>
> well that does not sound that good :-(
unfortunately :-(
> one thing that i noticed when resuming on 2.6.18-1 (debian) kernel is
> that i can ping the resumed machine just fine and nmap returns the same
> open ports as
23 matches
Mail list logo
