Hi there,
I'd like to use s2ram (current Debian unstable packages:
0.6~cvs20070513-1) on the following machine:
sys_vendor = "IBM"
sys_product = "252545G"
sys_version = "ThinkPad X41"
bios_version = "74ET47WW (1.17 )"
I can invoke s2ram without any additional parameters witho
On Sun, May 20, 2007 at 09:19:30PM +0200, Jörn Dreyer wrote:
> Am Mittwoch, den 16.05.2007, 20:20 +0200 schrieb Stefan Seyfried:
> > > [...]
> > >
> > > ~$ sudo s2ram -i
> > > This machine can be identified by:
> > > sys_vendor = "FUJITSU SIEMENS"
> > > sys_product = "CELSIUS H240"
> >
On Wed, May 23, 2007 at 07:30:55AM +0200, [EMAIL PROTECTED] wrote:
> On Wed, May 16, 2007 at 07:48:53PM +0200, Stefan Seyfried wrote:
> > 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 ide
On Wed, May 16, 2007 at 11:06:15PM +0200, Benoit Thiell wrote:
> It works fine in both cases. I just use the -f option.
Ok, thanks for confirming, i added it to the list.
>
> ++
>
> Stefan Seyfried wrote:
> > On Wed, May 09, 2007 at 11:45:07AM +0200, Benoit Thiell wrote:
> >> Hi,
> >>
> >> thank
On Sun, May 20, 2007 at 09:08:05AM +, [EMAIL PROTECTED] wrote:
> Hi,
>
> my test with s2ram with M2NPV-VM shows the following:
> (1) s2ram -f works under X with NVIDIA driver 1.0-9755 both TV and RGB output.
>
> (2) s2ram -f does not work under console (runlevel 1) both TV and RGB output.
>
On Wed, May 16, 2007 at 09:12:47PM +, Jasper Mackenzie wrote:
> 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_
On Sat, May 19, 2007 at 01:10:52PM +0200, Petric Frank wrote:
> Hello,
>
> i got a Z61m with ATi X1400 and 1680x1050 display. Due to this i have ti use
> the closed source fglrx driver to get X with the native display resolution.
>
> This is what "s2ram -i" (Version 0.5) emits:
> ---
On Sat, May 19, 2007 at 10:54:43PM +0200, [EMAIL PROTECTED] wrote:
> Hello,
> here are the s2ram parameters for my laptop
>
> valid s2ram call:
> s2ram -f -s
>
> s2ram -i
> This machine can be identified by:
> sys_vendor = "FUJITSU SIEMENS"
> sys_product = "LIFEBOOK E4010"
> sys_v
On Sun, May 20, 2007 at 07:28:40PM +1000, Simon Cullen wrote:
> Eeek ... Sorry: I forgot to mention that I am running s2ram -f -p -m. None
> of the other options appear to work at all. (They just go to a blank screen
> and don't actually suspend the machine.)
Does it suspend if you just do "echo
[sorry for jumping late at this thread, i have been pretty busy :-(]
On Sun, May 20, 2007 at 09:02:23PM +0200, Rafael J. Wysocki wrote:
> On Sunday, 20 May 2007 20:31, Tim Dijkstra wrote:
> > On Sun, 20 May 2007 15:27:18 +0200
> > Stefan Richter <[EMAIL PROTECTED]> wrote:
> >
> > > Rafael wrote:
On Sun, May 20, 2007 at 11:00:17PM +0200, Rafael J. Wysocki wrote:
> On Sunday, 20 May 2007 22:45, Tim Dijkstra wrote:
> > "Rafael J. Wysocki" <[EMAIL PROTECTED]> wrote:
> >
> > > But HOWTO is for the suspend to disk. It has "suspend to disk" in the
> > > title,
> > > so I wouldn't expect s2ram-
On Sun, May 20, 2007 at 11:15:20AM -0500, Omar Buhidma wrote:
> s2ram -f works fine:
>
>
> outreach:~ # s2ram -i
> This machine can be identified by:
> sys_vendor = "Dell Inc."
> sys_product = "MP061 "
> sys_version = ""
> bios_version = "A06"
> See h
On Sun, May 20, 2007 at 10:47:34PM +0200, Tim Dijkstra wrote:
> Hi Luca,
>
> I just got this report from a swap-offset user:
>
> I've just stumbled upon this message in my syslog after today's upgrade of
> uswsusp:
>
> program swap-offset is using a deprecated SCSI ioctl, please convert it
On Sun, May 20, 2007 at 11:03:52PM +0200, Josef Zenisek wrote:
> Hi,
>
> just wanted to let you know that my machine is unsupported by s2ram, see
> output below. Force to suspend works.
>
> Machine is unknown.
> This machine can be identified by:
> sys_vendor = "Gigabyte Technology Co., Lt
On Tue, May 22, 2007 at 04:00:59PM +0100, Manuel Padilha wrote:
> Hi everyone,
>
> This email is per instructions on http://en.opensuse.org/S2ram
> I've successfully configure suspend to ram on a Lenovo T60 laptop.
> s2ram -f -a 3 worked perfectly (-a 1 didn't, and i never got to try -a 2).
>
> H
On Wed, May 23, 2007 at 08:49:09PM +0200, Till Dörges wrote:
> Hello folks,
>
> I just experimented a bit with s2ram and it seems that it works okay on my
> machine. I
> tested it both from X11 and the console. A couple of test runs worked
> satisfactorily.
> The only that's wrong is that the de
On Sun, May 27, 2007 at 02:44:34AM +0200, Steffen wrote:
> Hi!
>
> Thanks for your tool!
>
> This machine can be identified by:
> sys_vendor = "FUJITSU SIEMENS"
> sys_product = "AMILO PRO V8010 "
> sys_version = "F0 "
> bios_version = "
On Sun, May 27, 2007 at 10:44:28AM +0200, Marco Nenciarini wrote:
>
> As requested in http://en.opensuse.org/S2ram this is a sucess report.
> My Sony Vaio PCG-GRT916Z(IT) works perfectly with s2ram -f (ithout any
> additional argument)
>
> sys_vendor = "Sony Corporation"
> sys_product
On Mon, May 28, 2007 at 06:52:49PM +0200, jetxee wrote:
> Hello,
>
> I tried s2ram on my Acer TravelMate 2420 laptop. s2ram reports that this
> machine is unknown:
>
> ~~
> Machine is unknown.
> This machine can be identified by:
> sys_vendor = "Acer"
> sys_product = "TravelMate 24
On Wed, May 30, 2007 at 05:06:38PM +0100, Amit Walambe wrote:
> Hi there!
> I have a P4 dual processor machine, with Intel 915 chipset. I am running
> 2.6.22-rc3 (config attached) on Debian
> Sid. swsusp version is 0.6-cvs200.
> Can anyone have pointers to what I might be doing wrong? More inform
On Wed, May 30, 2007 at 08:35:05PM +0200, Benedikt Nimmervoll wrote:
> Hi!
> Thanks for your marvellous suspend scripts, they work amazingly well :)
> I thought, I should add an computer to your hardware list:
>
> sys_vendor = "Hewlett-Packard"
> sys_product = "HP Compaq nx6325 (EY350EA
On Thu, May 31, 2007 at 11:07:11AM +0200, Florian Ragwitz wrote:
> Hi there,
>
> I'd like to use s2ram (current Debian unstable packages:
> 0.6~cvs20070513-1) on the following machine:
>
> sys_vendor = "IBM"
> sys_product = "252545G"
> sys_version = "ThinkPad X41"
> bios_versi
Hi!
Stefan Seyfried wrote:
> On Wed, May 30, 2007 at 05:06:38PM +0100, Amit Walambe wrote:
>> I followed instructions on http://en.opensuse.org/S2ram, and here is output
>> for following commands (obtained by
>> 's2ram [options] > filename 2>&1') :
>>
>> * s2ram -f -a 1
>> * s2ram -f -a 2
>> * s2
On Thu, May 31, 2007 at 04:40:37PM +0200, Stefan Seyfried wrote:
> On Sun, May 27, 2007 at 10:44:28AM +0200, Marco Nenciarini wrote:
> >
> > As requested in http://en.opensuse.org/S2ram this is a sucess report.
> > My Sony Vaio PCG-GRT916Z(IT) works perfectly with s2ram -f (ithout any
> > addition
On Thu, May 31, 2007 at 05:44:32PM +0200, Marco Nenciarini wrote:
> On Thu, May 31, 2007 at 04:40:37PM +0200, Stefan Seyfried wrote:
> > On Sun, May 27, 2007 at 10:44:28AM +0200, Marco Nenciarini wrote:
> > >
> > > As requested in http://en.opensuse.org/S2ram this is a sucess report.
> > > My Sony
On Wed, May 30, 2007 at 05:48:35PM +0100, Chris Hammond wrote:
> Thanks for the work on suspend. I have a Fujitsu Siemens Amilo A 1630 which
> includes a radeon mobility 9700 GPU. I was totally unable to get
> suspend/resume to work on Ubuntu Feisty with the xorg radeon dri driver
> whereas it work
On Thu, May 31, 2007 at 05:00:24PM +0200, Till Dörges wrote:
> On 31.05.2007 16:33, Stefan Seyfried wrote:
>
> >> I just experimented a bit with s2ram and it seems that it works okay on my
> >> machine. I
> >> tested it both from X11 and the console. A couple of test runs worked
> >> satisfactor
desktop with integrated graphics
works both from X and from the console
Stefan Seyfried schrieb:
On Sun, May 20, 2007 at 11:03:52PM +0200, Josef Zenisek wrote:
Hi,
just wanted to let you know that my machine is unsupported by s2ram, see
output below. Force to suspend works.
Machine is u
On Thu, May 31, 2007 at 06:03:59PM +0200, Josef Zenisek wrote:
> desktop with integrated graphics
> works both from X and from the console
Ok, thanks for confirming, i have added it to the list.
> >>just wanted to let you know that my machine is unsupported by s2ram, see
> >>output below. Force
On Thu, May 31, 2007 at 04:19:19PM +0100, Amit Walambe wrote:
> Hi!
> Stefan Seyfried wrote:
> > On Wed, May 30, 2007 at 05:06:38PM +0100, Amit Walambe wrote:
> >> I followed instructions on http://en.opensuse.org/S2ram, and here is
> >> output for following commands (obtained by
> >> 's2ram [opt
Hi,
the first hunk fixes s2ram -n, without it does not print what hacks would
actually be applied.
The other hunks let s2ram complain louder about machines that are still
UNSURE. The fedora guys made pretty bad experiences with entries marked
UNSURE and we actually seldom get reports to confirm t
(i cc'ed the suspend-devel list, which is the correct adress for reports)
On Fri, Mar 02, 2007 at 09:04:26PM -0500, Mark Peters wrote:
>
> The default works great!
>
> *thepeters:~ #* s2ram -f
> Switching from vt7 to vt1
>
> switching back to vt7
> *thepeters:~ #* s2ram
> Machine is unknown.
>
(i added suspend-devel to cc:)
On Tue, Mar 13, 2007 at 07:20:16PM +0200, Antonis Tsolomitis wrote:
>
> Hello. The latest s2ram works fine for this laptop. The only configuration
> needed
> is to load linux with vga=0 (this can be permanently added to, say,
> lilo.conf).
>
> The command that wo
Yep that's right, this is with the r300 dri driver (mesa 6.5.2). I wasn't
able to suspend any other way than with that combination (although I stopped
going down the list after it worked on that one). 's2ram -f -a 1' and 's2ram
-f -a 3' made the computer completely crash on resume, all the others
On Thu, 31 May 2007 18:24:43 +0200
Stefan Seyfried <[EMAIL PROTECTED]> wrote:
> Hi,
>
> the first hunk fixes s2ram -n, without it does not print what hacks would
> actually be applied.
>
> The other hunks let s2ram complain louder about machines that are still
> UNSURE. The fedora guys made pret
On Thursday, 31 May 2007 15:27, Stefan Seyfried wrote:
> On Sun, May 20, 2007 at 11:00:17PM +0200, Rafael J. Wysocki wrote:
> > On Sunday, 20 May 2007 22:45, Tim Dijkstra wrote:
> > > "Rafael J. Wysocki" <[EMAIL PROTECTED]> wrote:
> > >
> > > > But HOWTO is for the suspend to disk. It has "suspen
Hi Stefan,
Thanks for your reply. Yes, it did suspend. (A decided improvement since I
last tried that method.) When I tried to resume the screen did not come
back, and the caps light wouldn't respond, though there was intermittent
hard disk activity. So that's the same behaviour I was finding
I've just had another shot at s2ram: running s2ram -f -p -m from VT2 will
suspend the machine---and it is resumable. Still, after resume if I try to
switch back to X (VT7) it blanks and freezes, and then a hard power off is
required.
Thank you---again
On 01/06/07, Simon Cullen <[EMAIL PROTE
On Thu, May 31, 2007 at 02:08:17PM +0200, Stefan Seyfried wrote:
> I have seen similar things on different machines, but usually it was "reboot"
> not rebooting but hanging instead.
> I strongly believe that this is not related to the s2ram program, so please
> report this on the acpi-devel and/or
39 matches
Mail list logo
