Hello Stefan!
well that does not sound that good :-(
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 before suspend - but i'm not able to connect to the
running sshd on the resumed machine
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 Notebook PC"
sys_version = "F.05"
bios_version = "F.05"
I am not
On Friday 27 July 2007, Rafael J. Wysocki wrote:
> Well, in fact we're missing someone to take care of the project's web page,
> too.
Hmmm... I cannot help you with web stuff... :(
But I can help you with autoconf/automake...
Alon
-
On Friday 27 July 2007, Rafael J. Wysocki wrote:
> Apart from this you should also clear the PLATFORM_SUSPEND flag in the image
> header. Otherwise, resume will be confused if shutdown_method is originally
> set to "platform".
OK.
What do you think about this one?
I passed the header to save_imag
Hello Pavel,
I'll test this later.
Meanwhile, I found out on the backlight front, that this might be
another quirk. Sometimes the backlight flashes on and off, and the stays
off.
It seems that it does that with both the -a3 and -a1 parameter. I
thought it was only with -a1 but it seems to be just
On Monday, 23 July 2007 11:16, Pavel Machek wrote:
> Hi!
>
> > > AFAICS, recent versions of pciutils depend on it.
> >
> > Oh...
> > You don't have to compile it with zlib...
> >
> > """The configure script will automatically enable support for a compressed
> > pci.ids if you have zlib installed
On Thursday, 19 July 2007 05:20, Alon Bar-Lev wrote:
> On Wednesday 18 July 2007, Rafael J. Wysocki wrote:
> > On Wednesday, 18 July 2007 20:01, Alon Bar-Lev wrote:
> > > Hello,
> > >
> > > I wounder why resume default location is at /usr/local/lib/suspend
> > > and not at /usr/local/sbin...
> > >
Hi,
On Friday, 20 July 2007 19:56, Alon Bar-Lev wrote:
>
> Hello Rafael,
>
> Yet another patch in the suspend2 feature-set series.
> It sets cpufreq to maximum during the cycle.
> It is important to finish the process as quickly as possible (human engineer
> issue :) )
> When running on batteri
Hi,
On Friday, 20 July 2007 17:54, Alon Bar-Lev wrote:
>
> Hello,
>
> This patch enables the user to press "r" during snapshot writing,
> in order to reboot and not shutdown.
>
> One more step toward suspend2 functionality... :)
>
> Best Regards,
> Alon Bar-Lev.
>
> diff -urNp suspend.org/spl
On Friday, 27 July 2007 19:34, Pavel Machek wrote:
> Hi!
>
> > > 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?
>
> Because it was easier that way :-).
>
>
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 device just disables any drawing - and thus any access
> > > of possibly not reall
On Fri, Jul 27, 2007 at 06:16:55PM +0200, Stefan Seyfried wrote:
> On Fri, Jul 27, 2007 at 11:57:49PM +0800, Kanru Chen wrote:
> >
> > Yes, I can do it from console. But after resume, I have to switch to X
> > first then switch back to console to get my screen back.
>
> Ok, so it does _not_ work
> On Mon, Jul 23, 2007 at 07:44:10PM +0200, Hendrik-Jan Heins wrote:
> >
> > I just tested the following:
> >
> > Sidux 2007-2 (tartaros), amd64 on live cd.
> > I loaded it to ram and installed uswsusp.
> > next I did: "s2ram -f -m -a3", three times.
> > Every time the machine suspended correctly
> (i re-added suspend-devel to cc: to keep the conversation on-list, please
> keep it that way)
>
> On Thu, Jul 19, 2007 at 10:40:47PM +0200, Hendrik-Jan Heins wrote:
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA1
> >
> > ah yes, I'm sorry, forgot to answer that one.
> > I'm running i386
Hi!
> > 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?
Because it was easier that way :-).
> I would have expected all be forwarded to suspend.sf.net...
> http://en.open
On Fri, Jul 27, 2007 at 11:57:49PM +0800, Kanru Chen wrote:
> On Fri, Jul 27, 2007 at 04:51:19PM +0200, Stefan Seyfried wrote:
> > On Thu, Jul 26, 2007 at 01:53:49AM +0800, Kanru Chen wrote:
> > > Hi!
> > >
> > > I tried s2ram today, and it works like a charm!
> > >
> > > My computer is identifie
On 7/27/07, Stefan Seyfried <[EMAIL PROTECTED]> wrote:
> i'd guess s2ram.c will be pretty small then:
>
> int main()
> {
> return 0;
> }
>
>
> ;-))
> But this is not the goal of s2ram, as i hopefully already explained
> sufficiently in an earlier mail.
I guess so... Your project.
But I rea
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 device just disables any drawing - and thus any access
> > of possibly not really initialized hardware before running vbe_post
> > etc...)
> > A
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?
I would have expected all be forwarded to suspend.sf.net...
http://en.open
On Fri, Jul 27, 2007 at 04:48:10PM +0200, Simon Lowen wrote:
> Dear all,
>
> I tried to get s2ram to work but found that my laptop is unsupported.
> Any workarounds?
Just follow the URL that is mentioned in the output of s2ram below :-)
> It is the same as a US model of the Vaio SZ. The SZ90
On Fri, Jul 27, 2007 at 06:21:56PM +0300, Alon Bar-Lev wrote:
> On 7/27/07, Rafael J. Wysocki <[EMAIL PROTECTED]> wrote:
> > > (yes, i think i know what it does; writing 1 into the state of the
> > > framebuffer device just disables any drawing - and thus any access
> > > of possibly not really ini
On Fri, Jul 27, 2007 at 06:17:30PM +0300, Alon Bar-Lev wrote:
>
> I suggested to provide the autoconf/automake support, but I don't wish
> to work for nothing.
I for myself don't like the autofoo stuff very much and i think it is a
major PITA for small projects.
But i am not the one to decide thi
On Fri, Jul 27, 2007 at 05:48:52PM +0300, Alon Bar-Lev wrote:
> On 7/27/07, Stefan Seyfried <[EMAIL PROTECTED]> wrote:
> > On Sun, Jul 22, 2007 at 10:09:50PM +0300, Alon Bar-Lev wrote:
> > > > These s2ram_* funcs in the end call code from vbetool/vbetool.c which
> > > > is indeed linked in. But par
On Fri, Jul 27, 2007 at 05:52:15PM +0300, Alon Bar-Lev wrote:
> On 7/27/07, Stefan Seyfried <[EMAIL PROTECTED]> wrote:
> > On Mon, Jul 23, 2007 at 11:25:10AM +0200, Pavel Machek wrote:
> >
> > > Well, so user explicitely configured his machine to run on 80% max,
> > > for some reason. Now you want
On Fri, Jul 27, 2007 at 04:51:19PM +0200, Stefan Seyfried wrote:
> On Thu, Jul 26, 2007 at 01:53:49AM +0800, Kanru Chen wrote:
> > Hi!
> >
> > I tried s2ram today, and it works like a charm!
> >
> > My computer is identified as follows:
> >
> > sys_vendor = "ASUSTeK Computer INC."
> > sys_prod
On Fri, Jul 27, 2007 at 05:24:09PM +0200, Sławomir Skrzyniarz wrote:
> > On Thu, Jul 19, 2007 at 08:33:12PM +0200, Sławomir Skrzyniarz wrote:
> > > > Yes, but does it also work on the text console? (i doubt it, and i'd
> > > > guess that you need to add "-f -p -m" to the s2ram options. Look at
> >
On 7/27/07, Rafael J. Wysocki <[EMAIL PROTECTED]> wrote:
> > (yes, i think i know what it does; writing 1 into the state of the
> > framebuffer device just disables any drawing - and thus any access
> > of possibly not really initialized hardware before running vbe_post
> > etc...)
> > At least it
On 7/27/07, Stefan Seyfried <[EMAIL PROTECTED]> wrote:
> On Wed, Jul 25, 2007 at 05:33:15PM +0300, Alon Bar-Lev wrote:
> > On 7/25/07, Rafael J. Wysocki <[EMAIL PROTECTED]> wrote:
> > > IIRC, we discussed that in the past and decided not to do it.
> >
> > Well... Maybe now when the project advanced
Hi,
On Friday, 27 July 2007 15:27, Stefan Seyfried wrote:
> Hi,
>
> while working on https://bugzilla.novell.com/show_bug.cgi?id=293662 and
> https://bugzilla.novell.com/show_bug.cgi?id=281798 it occured to me that
> including Ubuntu's hack in s2ram might be a good idea.
> It should do no harm -
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 = "F.11"
> bios_version = "6
On Fri, Jul 27, 2007 at 02:13:55PM +0200, [EMAIL PROTECTED] wrote:
>
> Hello,
>
> please whitelist following board:
>
> sys_vendor = "System manufacturer"
> sys_product = "System Product Name"
> sys_version = "System Version"
> bios_version = "ASUS M2N32-SLI DELUXE ACPI BIOS
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 newer Thinkpads work fine
with "-a
On Thu, Jul 26, 2007 at 01:53:49AM +0800, Kanru Chen wrote:
> Hi!
>
> I tried s2ram today, and it works like a charm!
>
> My computer is identified as follows:
>
> sys_vendor = "ASUSTeK Computer INC."
> sys_product = "W3A"
> sys_version = "1.0"
> bios_version = "0801"
>
> It's not in th
On Wed, Jul 25, 2007 at 11:45:20AM -0400, Sergei Serdyuk wrote:
> Hi,
>
> You may want to add this to the whitelist. s2ram works perfectly for my
> on Ubuntu 7.04 if I force it with the -f option.
>
> [EMAIL PROTECTED]:~$ sudo s2ram -i
> This machine can be identified by:
>sys_vendor = "Ace
On Wed, Jul 25, 2007 at 05:33:15PM +0300, Alon Bar-Lev wrote:
> On 7/25/07, Rafael J. Wysocki <[EMAIL PROTECTED]> wrote:
> > IIRC, we discussed that in the past and decided not to do it.
>
> Well... Maybe now when the project advanced you have new arguments?
> It will be much much easier for users
On Tue, Jul 24, 2007 at 05:30:32PM +0300, Alexander Toncovidov wrote:
> Dear All,
>
> I'm glad to let you know that s2ram works fine on my machine running
> openSUSE 10.2
>
> Here are my outputs:
> # uname -r
> 2.6.18.8-0.5-default
>
> # s2ram -i
> This machine can be identified by:
> sys_ve
On Thu, Jul 19, 2007 at 11:04:48PM +0200, Daniel Lombraña González wrote:
> Hi,
>
> I'm on Ubuntu Feisty trying your software. There is one official package for
> us and it's which I'm using. After trying everything on your web page
> (s2ram) because my laptop is not recognize I can say that my nv
On 7/27/07, Stefan Seyfried <[EMAIL PROTECTED]> wrote:
> On Mon, Jul 23, 2007 at 11:25:10AM +0200, Pavel Machek wrote:
>
> > Well, so user explicitely configured his machine to run on 80% max,
> > for some reason. Now you want suspend to explicitely override his
> > setting. That strikes me as a ba
On Sat, Jul 21, 2007 at 06:28:24PM +0300, Alon Bar-Lev wrote:
> On 7/21/07, Holger Macht <[EMAIL PROTECTED]> wrote:
> > This is already done in pm-utils. Upstream uses 'userspace' as governor,
> > which I personally think is wrong. openSUSE uses the 'performance'
> > governor and this only because
On 7/27/07, Stefan Seyfried <[EMAIL PROTECTED]> wrote:
> On Sun, Jul 22, 2007 at 10:09:50PM +0300, Alon Bar-Lev wrote:
> > > These s2ram_* funcs in the end call code from vbetool/vbetool.c which
> > > is indeed linked in. But partly I remembered it wrongly. The hacks
> > > _before_ suspend are call
Dear all,
I tried to get s2ram to work but found that my laptop is unsupported.
Any workarounds?
It is the same as a US model of the Vaio SZ. The SZ90 (91 92 etc) are
the Japanese models.
If you report a problem, please include the complete output above.
[EMAIL PROTECTED]:~# s2ram -i
This mach
On Mon, Jul 23, 2007 at 12:46:04AM +0530, Arun Raghavan wrote:
> Hello all,
> For a long while now I've not been able to get suspend-to-ram to work
> on my HP Pavilion dv5200tx. Has anybody had any luck with this laptop
> model?
>
> Symptom: Suspend happens fine. On resume, there is very little
>
On Fri, Jul 20, 2007 at 10:32:48PM -0400, Vinay wrote:
> My machine identifies itself as follows:
>
>sys_vendor = "Hewlett-Packard"
>sys_product = "HP Pavilion tx1000 Notebook PC"
>sys_version = "Rev 1"
>bios_version = "F.13"
>
> this was not auto detected in ubuntu 7.
On Mon, Jul 23, 2007 at 11:25:10AM +0200, Pavel Machek wrote:
> Well, so user explicitely configured his machine to run on 80% max,
> for some reason. Now you want suspend to explicitely override his
> setting. That strikes me as a bad idea. Plus it does not belong to
> suspend.
100% ACK
--
Stef
On Sun, Jul 22, 2007 at 10:09:50PM +0300, Alon Bar-Lev wrote:
> > These s2ram_* funcs in the end call code from vbetool/vbetool.c which
> > is indeed linked in. But partly I remembered it wrongly. The hacks
> > _before_ suspend are called with an unfrozen userspace, those after on
> > a frozen user
On Sat, Jul 21, 2007 at 11:08:30PM +0300, Alon Bar-Lev wrote:
> On 7/21/07, Alon Bar-Lev <[EMAIL PROTECTED]> wrote:
> > On 7/21/07, Holger Macht <[EMAIL PROTECTED]> wrote:
> > > Right. So if we start putting things like cpufreq in the suspend package,
> > > we would have an argumentation to put eve
On Sat, Jul 21, 2007 at 09:01:03AM +0300, Alon Bar-Lev wrote:
> On 7/21/07, Tim Dijkstra <[EMAIL PROTECTED]> wrote:
> > On Fri, 20 Jul 2007 22:20:51 +0200
> > "Rafael J. Wysocki" <[EMAIL PROTECTED]> wrote:
> >
> > > > Yet another patch in the suspend2 feature-set series.
> > > > It sets cpufreq to
Sorry for coming late to the party...
On Fri, Jul 20, 2007 at 08:56:15PM +0300, Alon Bar-Lev wrote:
>
> Hello Rafael,
>
> Yet another patch in the suspend2 feature-set series.
> It sets cpufreq to maximum during the cycle.
> It is important to finish the process as quickly as possible (human eng
On Thu, Jul 19, 2007 at 03:36:09PM -0400, a v wrote:
> $ sudo s2ram -i
> This machine can be identified by:
> sys_vendor = "TOSHIBA"
> sys_product = "TECRA8100"
> sys_version = "PT810C-11C52"
> bios_version = "Version 2.50"
>
> it only works properly with -a 2 or adding acpi_sl
On Thu, Jul 19, 2007 at 08:33:12PM +0200, Sławomir Skrzyniarz wrote:
> > Yes, but does it also work on the text console? (i doubt it, and i'd guess
> > that you need to add "-f -p -m" to the s2ram options. Look at
> > http://en.opensuse.org/S2ram to find out how to get the best options for
> > your
On Sun, Jul 22, 2007 at 07:48:17PM +0200, maestro wrote:
> Hello, sorry that i did not get back to you earlier
>
> > > i installed debian etch on my notebook [0] because sarge did not support
> > > any suspend capabilities on that model.
> >
> > What kernel version? Can you try a recent vanilla o
On Mon, Jul 23, 2007 at 07:44:10PM +0200, Hendrik-Jan Heins wrote:
>
> I just tested the following:
>
> Sidux 2007-2 (tartaros), amd64 on live cd.
> I loaded it to ram and installed uswsusp.
> next I did: "s2ram -f -m -a3", three times.
> Every time the machine suspended correctly and woke up aga
Hi,
while working on https://bugzilla.novell.com/show_bug.cgi?id=293662 and
https://bugzilla.novell.com/show_bug.cgi?id=281798 it occured to me that
including Ubuntu's hack in s2ram might be a good idea.
It should do no harm - they are apparently doing it unconditionally on all
machines.
This coul
Hello,
please whitelist following board:
sys_vendor = "System manufacturer"
sys_product = "System Product Name"
sys_version = "System Version"
bios_version = "ASUS M2N32-SLI DELUXE ACPI BIOS Revision 1201"
and
sys_vendor = "System manufacturer"
sys_product = "Sys
<>-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> htt
On Friday, 27 July 2007 10:15, Felix Homann wrote:
> Hi,
>
> with recent kernels I'm having several problems suspending with
> s2disk/s2ram. The last kernel it has been working flawlessly was 2.6.18.1:
>
> First, here's what the working kernel says:
>
> 2.6.18.1:
>
> s2disk:
>
Hi,
with recent kernels I'm having several problems suspending with
s2disk/s2ram. The last kernel it has been working flawlessly was 2.6.18.1:
First, here's what the working kernel says:
2.6.18.1:
s2disk:
Except for the message "pm_ops ->prepare failed, using 'shutdown
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. Even after -p -m the X video mode is
messed up but switching manually to a virtual console and back to X fixes
everything.
P.S. I'm available for further
58 matches
Mail list logo
