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.
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.04, but s2ram -f seemed to work
flawlessly
Vinay
On Thu, Jul 19, 2007 at 05:58:25PM +0200, Ingo wrote:
> Stefan Seyfried schrieb:
> > (i re-added suspend-devel to cc: to keep the conversation on-list)
> >
> > On Wed, Jul 04, 2007 at 09:39:24PM +0200, Ingo wrote:
> >> Stefan Seyfried schrieb:
> >>> On Mon, Jun 18, 2007 at 10:09:11PM +0200, Ingo S
Stefan Seyfried schrieb:
> (i re-added suspend-devel to cc: to keep the conversation on-list)
>
> On Wed, Jul 04, 2007 at 09:39:24PM +0200, Ingo wrote:
>> Stefan Seyfried schrieb:
>>> On Mon, Jun 18, 2007 at 10:09:11PM +0200, Ingo Steiner wrote:
this is just to report a success for s2ram on a
(i added suspend-devel to cc:, this will get this info into a public archive)
On Thu, Jul 05, 2007 at 09:20:45PM -0600, Ed Hoo wrote:
> Here is the information for s2ram on the HP NX5000. s2ram works, but one
> curious thing is that when suspending from the console it works like a
> charm, when i
(i re-added suspend-devel to cc: to keep the conversation on-list)
On Wed, Jul 04, 2007 at 09:39:24PM +0200, Ingo wrote:
> Stefan Seyfried schrieb:
> > On Mon, Jun 18, 2007 at 10:09:11PM +0200, Ingo Steiner wrote:
> >> this is just to report a success for s2ram on a desktop-PC:
> >>
> >> MB: ASUS
(added suspend-devel to cc:, please keep the conversation on-list so that
more people can add their wisdom :-)
On Tue, Jul 17, 2007 at 09:53:13AM -0600, David Baird wrote:
> On 7/17/07, Stefan Seyfried <[EMAIL PROTECTED]> wrote:
> >On Sun, Jul 08, 2007 at 10:14:34PM -0600, David Baird wrote:
> >>
On Thu, Jul 12, 2007 at 12:39:58AM -0300, Jorge Visca wrote:
> Ok, after some testing i found it was the sonypi module. Now the lid
> close is not detected, but anyway i had no use for that when i couldnt
> suspend...
> There is a replacement for this module being developped.
> So,
>
> s2ram -f -a
On Sun, Jul 08, 2007 at 10:14:34PM -0600, David Baird wrote:
> Hi,
>
> I can get s2ram to work from init=/bin/bash, but when I boot the full
> OS and log in (on a text virtual terminal), the system will not
> suspend:
>
> s2ram -f -a 1
Does it "not suspend" (stays on) or does it "not resume"
Pavel Machek wrote:
> That probably means someone (you?) should add printk("suspend not supported by
> sonypi"); return -EINVAL; at begging of its _suspend routine, so that
> we break suspend in reliable and easy-to-debug manner?
>
Pavel Machek wrote:
> That probably means someone (you?) should add printk("suspend not supported by
> sonypi"); return -EINVAL; at begging of its _suspend routine, so that
> we break suspend in reliable and easy-to-debug manner?
>
On Thu 2007-07-12 22:47:56, Jorge Visca wrote:
> Pavel Machek wrote:
> >> Ok, after some testing i found it was the sonypi module. Now the lid
> >> close is not detected, but anyway i had no use for that when i couldnt
> >> suspend...
> >>
> >
> > Be sure to report this to sonypi authors. I'd
Pavel Machek wrote:
>> Ok, after some testing i found it was the sonypi module. Now the lid
>> close is not detected, but anyway i had no use for that when i couldnt
>> suspend...
>>
>
> Be sure to report this to sonypi authors. I'd prefer not to have to
> debug it over and over and over again
> Ok, after some testing i found it was the sonypi module. Now the lid
> close is not detected, but anyway i had no use for that when i couldnt
> suspend...
Be sure to report this to sonypi authors. I'd prefer not to have to
debug it over and over and over again.
> There is a replacement for this
Ok, after some testing i found it was the sonypi module. Now the lid
close is not detected, but anyway i had no use for that when i couldnt
suspend...
There is a replacement for this module being developped.
So,
s2ram -f -a 1
s2ram -f -a 3
and
s2ram -f -p -m
works on a
sys_vendor = "Sony
Hi!
> >> I can get s2ram to work from init=/bin/bash, but when I boot the full
> >> OS and log in (on a text virtual terminal), the system will not
> >> suspend:
> >>
> >> s2ram -f -a 1
> >>
> > Is there any difference in modules between working and broken case?
> > Any interesting messag
On 7/10/07, Pavel Machek <[EMAIL PROTECTED]> wrote:
> Hi!
>
> > I can get s2ram to work from init=/bin/bash, but when I boot the full
> > OS and log in (on a text virtual terminal), the system will not
> > suspend:
> >
> > s2ram -f -a 1
>
> Is there any difference in modules between working and
Pavel Machek wrote:
> Hi!
>
>> I can get s2ram to work from init=/bin/bash, but when I boot the full
>> OS and log in (on a text virtual terminal), the system will not
>> suspend:
>>
>> s2ram -f -a 1
>>
> Is there any difference in modules between working and broken case?
> Any interest
Hi!
> I can get s2ram to work from init=/bin/bash, but when I boot the full
> OS and log in (on a text virtual terminal), the system will not
> suspend:
>
> s2ram -f -a 1
Is there any difference in modules between working and broken case?
Any interesting messages in dmesg?
Hi,
I can get s2ram to work from init=/bin/bash, but when I boot the full
OS and log in (on a text virtual terminal), the system will not
suspend:
s2ram -f -a 1
I tried many of the possibilities listed on
http://en.opensuse.org/S2ram but none seemed to work (except perhaps
with init=/bin/bas
On Mon, Jun 18, 2007 at 10:09:11PM +0200, Ingo Steiner wrote:
> this is just to report a success for s2ram on a desktop-PC:
>
> MB: ASUS M2N-E, Athlon64 X2 4200+ EE
> Graphic Card: MSI nVidia 7100GS
> TV-Card: WinTV PVR 150
> Operating sytem Ubuntu feisty amd64,
> Kernel 2.6.20.16-default
>
> Out
Hi!
I've tried it now and it works fine. My computer is:
ubuntu feisty
Linux 2.6.20-16-generic #2 SMP Thu Jun 7 19:00:28 UTC 2007 x86_64 GNU/Linux
This machine can be identified by:
sys_vendor = "ASUSTeK Computer INC."
sys_product = "A6M"
sys_version = "1.0"
bios_version = "
this is just to report a success for s2ram on a desktop-PC:
MB: ASUS M2N-E, Athlon64 X2 4200+ EE
Graphic Card: MSI nVidia 7100GS
TV-Card: WinTV PVR 150
Operating sytem Ubuntu feisty amd64,
Kernel 2.6.20.16-default
Output of s2ram -i:
*This machine can be identified by:
sys_vendor = "System
On Thu, Jun 07, 2007 at 03:31:18PM -0700, Elliott Martin wrote:
> I wanted to report that s2ram works fine on my computer with the following
> options:
>
> s2ram -f -p -m
>
> # s2ram -i
> This machine can be identified by:
> sys_vendor = "AVERATEC"
> sys_product = "E1200"
> sys_ve
I wanted to report that s2ram works fine on my computer with the following
options:
s2ram -f -p -m
# s2ram -i
This machine can be identified by:
sys_vendor = "AVERATEC"
sys_product = "E1200"
sys_version = "To Be Filled By O.E.M."
bios_version = "080010 "
See http://en.opensus
(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
On Thursday, 17 May 2007 12:50, Tim Dijkstra wrote:
> On Thu, 17 May 2007 11:59:37 +0200
> "Rafael J. Wysocki" <[EMAIL PROTECTED]> wrote:
>
> > On Thursday, 17 May 2007 00:14, Tim Dijkstra wrote:
> > > Hi,
> > >
> > > I've got an report of a laptop that works with
> > > s2ram --vbe_save --vbe_
On Thu, 17 May 2007 11:59:37 +0200
"Rafael J. Wysocki" <[EMAIL PROTECTED]> wrote:
> On Thursday, 17 May 2007 00:14, Tim Dijkstra wrote:
> > Hi,
> >
> > I've got an report of a laptop that works with
> > s2ram --vbe_save --vbe_post
> >
> > But doesn't for s2both with the same options.
> >
>
On Thursday, 17 May 2007 00:14, Tim Dijkstra wrote:
> Hi,
>
> I've got an report of a laptop that works with
> s2ram --vbe_save --vbe_post
>
> But doesn't for s2both with the same options.
>
> What does work however is
> s2both -a 1
>
> Somehow the difference in code path in s2both
Hi,
I've got an report of a laptop that works with
s2ram --vbe_save --vbe_post
But doesn't for s2both with the same options.
What does work however is
s2both -a 1
Somehow the difference in code path in s2both is significant from that of
s2ram (which basically does echo mem > /s
On Mon, May 14, 2007 at 10:39:06PM +0200, Ralph Thormann wrote:
> hello,
>
> i'm using s2ram from the ubuntu package:
>
> uswsusp 0.3~cvs20060928-6ubuntu3
>
> s2ram -i tells me:
>
> s2ram -i
> This machine can be identified by:
> sys_vendor = "IBM"
> sys_product = " "
>
On Tue, Apr 24, 2007 at 11:33:43PM -0300, Cristian S. Rocha wrote:
> Hello,
>
> I test "s2ram -f" in my Notebook and it works fine. Could you append it
> into the whitelist? The "s2ram -i" output is:
>
> gator:~# s2ram -i
> This machine can be identified by:
> sys_vendor = "Hewlett-Packard"
On Sun, Apr 22, 2007 at 10:35:35AM +0200, Tom wrote:
> Hello
>
> I just tried s2ram on my machine (using s2ram -f only), and it just worked
> without problems (I tried from within X (KDE in Kubuntu)).
> According to the Debian "README.s2ram-whitelist" I'm writing to this list to
> report my mach
hello,
i'm using s2ram from the ubuntu package:
uswsusp 0.3~cvs20060928-6ubuntu3
s2ram -i tells me:
s2ram -i
This machine can be identified by:
sys_vendor = "IBM"
sys_product = " "
sys_version = "ThinkPad X40"
bios_version = "1UETD2WW (2.07 )"
s2ram runs perfect,
Hello,
I test "s2ram -f" in my Notebook and it works fine. Could you append it
into the whitelist? The "s2ram -i" output is:
gator:~# s2ram -i
This machine can be identified by:
sys_vendor = "Hewlett-Packard"
sys_product = "Presario V3000 (EZ674UA#ABA)"
sys_version = "
Hello
I just tried s2ram on my machine (using s2ram -f only), and it just worked
without problems (I tried from within X (KDE in Kubuntu)).
According to the Debian "README.s2ram-whitelist" I'm writing to this list to
report my machine to get it into the whitelist.
s2ram -i:
This machine can be
Hi,
(i re-added suspend-devel to cc)
On Mon, Mar 26, 2007 at 01:00:21PM +0200, Christoph Wiesmeyr wrote:
> Unfortunately it only works from the console. If I use the KDE menu for
good.
> suspend the only thing that happens is that the current user is locked. Same
> with the hotkey on the keyb
On Fri, Mar 23, 2007 at 06:50:06PM +0100, Christoph Wiesmeyr wrote:
> Dear Developers!
>
>
> I have tried to use s2ram on my laptop though it was not on the list with the
> supported models. it tourned out that the suspend works rightaway
> with "s2ram -f"
Thanks for reporting. Does it work fr
Dear Developers!
I have tried to use s2ram on my laptop though it was not on the list with the
supported models. it tourned out that the suspend works rightaway
with "s2ram -f"
The output of "s2ram -i" is:
This machine can be identified by:
sys_vendor = "GERICOM"
sys_product = "2
Hi!
> I succeeded to suspend-to-ram my system (home-mounted NForce 4 + Athlon 64 +
> Geforce TC), with the default settings (no need to use s3_bios, vbe, etc...)
>
> But a few seconds after the resume (I can type commands like ls during these
> few seconds), my system hangs with this error :
>
Sorry, I forgot these informations :
I'm running Mandriva 2007, with kernel 2.6.17-11mdv, and
suspend-s2ram-0.5-8mdv2007.0
This is the output of my lspci :
00:00.0 Memory controller: nVidia Corporation CK804 Memory Controller (rev a3)
00:01.0 ISA bridge: nVidia Corporation CK804 ISA Bridge (rev
Hi,
I succeeded to suspend-to-ram my system (home-mounted NForce 4 + Athlon 64 +
Geforce TC), with the default settings (no need to use s3_bios, vbe, etc...)
But a few seconds after the resume (I can type commands like ls during these
few seconds), my system hangs with this error :
CPU 0: Mach
> Do you need any options for s2ram BTW? Can you report them according to
> http://en.opensuse.org/S2ram ?
Im using -f -a3 (as recommended for Intel VidCards, fixing the issue
about the horizontal lines).
> It somehow depends on what your distribution uses to suspend. If it uses
> pm-utils, then
On Wed, Feb 28, 2007 at 06:06:50PM +0100, Sascha Heid wrote:
> Am Mittwoch, den 28.02.2007, 08:56 +0100 schrieb Stefan Seyfried:
> > On Wed, Feb 28, 2007 at 02:35:27AM +0100, Sascha Heid wrote:
> > > Hi List :-)
> > >
> > > I have a Lenovo X60T Tablet.
> > > S2ram works fine but i loose the wacom
Am Mittwoch, den 28.02.2007, 08:56 +0100 schrieb Stefan Seyfried:
> On Wed, Feb 28, 2007 at 02:35:27AM +0100, Sascha Heid wrote:
> > Hi List :-)
> >
> > I have a Lenovo X60T Tablet.
> > S2ram works fine but i loose the wacom stylus.
> > Usually i have to run " setserial /dev/ttyS0 port 0x0200 irq
On Wed, Feb 28, 2007 at 02:35:27AM +0100, Sascha Heid wrote:
> Hi List :-)
>
> I have a Lenovo X60T Tablet.
> S2ram works fine but i loose the wacom stylus.
> Usually i have to run " setserial /dev/ttyS0 port 0x0200 irq 5
> autoconfig" before i start X to make the stylus work, but it does not
> wo
Hi List :-)
I have a Lenovo X60T Tablet.
S2ram works fine but i loose the wacom stylus.
Usually i have to run " setserial /dev/ttyS0 port 0x0200 irq 5
autoconfig" before i start X to make the stylus work, but it does not
work when X is already up.
Is there a way to tell s2ram to run this early en
On 2007-02-17 01:44, Stefan Seyfried wrote:
> > s2ram -f -p -mYES
>
> Good. This one looks "best". Could you try this one from Text mode
> also? It will probably blank the screen (but the light should return
> and anything new typed should be visible), so this is no problem.
I test
On Sat, Feb 17, 2007 at 01:32:33AM +0100, Ricardo Garcia wrote:
> On 2007-02-16 23:52, you wrote:
>
> > So vbetool _was_ used.
>
> Sorry. I think I was confused about this issue. I thought vbetool was an
> independent program that was called by s2ram when available and when
> you specified its c
On 2007-02-16 23:52, you wrote:
> Yes, because the machine is in the "unconfirmed" section of the
> database.
>
> > Thanks again, good luck and keep up the good work.
> >
> > Machine matched entry 122:
> > sys_vendor = 'Acer, inc.'
> > sys_product = 'Aspire 3000*'
> > sys_version =
On Fri, Feb 16, 2007 at 10:46:58PM +0100, Ricardo Garcia wrote:
> Hello,
>
> This is a laptop computer reported to be an Acer Aspire 3000 model (in
> fact, there's a label in the laptop which reads "Aspire 3000"), but the
> specific model is Acer Aspire 3003WLMi. I figured I'd have to report
>
Hello,
This is a laptop computer reported to be an Acer Aspire 3000 model (in
fact, there's a label in the laptop which reads "Aspire 3000"), but the
specific model is Acer Aspire 3003WLMi. I figured I'd have to report
the success and take the opportunity to say thank you and congratulate
you
Hallo Stefan,
* Stefan Seyfried <[EMAIL PROTECTED]> [31-08-06 10:43]:
> On Thu, Aug 31, 2006 at 09:30:26AM +0200, Tim Niemeyer wrote:
> > Hello,
> >
> > s2ram works for me on
> > This machine can be identified by:
> > sys_vendor = "Dell Inc."
> > sys_product = "Latitude D820
On Thu, Aug 31, 2006 at 09:30:26AM +0200, Tim Niemeyer wrote:
> Hello,
>
> s2ram works for me on
> This machine can be identified by:
> sys_vendor = "Dell Inc."
> sys_product = "Latitude D820 "
> sys_version = ""
> bios_version = "A01"
> See http://en.opensuse
Hi,
I don't use framebuffer. It has caused trouble in the past so I decided
I wouldn't need it.
s2ram also works from the console.
Regards,
Martin Sack
Stefan Seyfried wrote:
> On Tue, Aug 01, 2006 at 01:54:50PM +0200, Martin Sack wrote:
>> Hello
>>
>> I'm using s2ram integrated within powersav
On Tue, Aug 01, 2006 at 01:54:50PM +0200, Martin Sack wrote:
> Hello
>
> I'm using s2ram integrated within powersaved on an Acer TravelMate
> 801LCi which has been recognized as a TravelMate 800. Its graphics
> adapter is a Radeon M9 which suffers from the usual radeon chip
> problems. To get s2ra
Hello
I'm using s2ram integrated within powersaved on an Acer TravelMate
801LCi which has been recognized as a TravelMate 800. Its graphics
adapter is a Radeon M9 which suffers from the usual radeon chip
problems. To get s2ram working on this box I had to use vbepost in
s2ram -f -p
which I enabl
On Sun, Jul 16, 2006 at 02:36:47PM +0200, Chirag Rajyaguru wrote:
> Hi,
>
> Ya, as subject says my Dell Inspiron 5150 which is already in the white list
> works with s2ram. I though I should share my information with you guys.
> Untill SUSE 10, I was able to suspend and resume without any hack b
Hi,
sorry for the late reply...
On Thu, Jul 13, 2006 at 03:58:02PM +0100, Hugo Costelha wrote:
> On 7/13/06, Stefan Seyfried <[EMAIL PROTECTED]> wrote:
> >On Thu, Jul 13, 2006 at 03:27:42PM +0100, Hugo Costelha wrote:
> >> Hi,
> >>
> >> It seems that I spoke too soon. Although everything seems to
On Thu, Jul 13, 2006 at 03:27:42PM +0100, Hugo Costelha wrote:
> Hi,
>
> It seems that I spoke too soon. Although everything seems to work
> fine, there is one small glitch. After suspending to ram with the
> option acpi_sleep=s3_mode (also if both modes alre selected), if I
> select restart in th
On Thu, Jul 13, 2006 at 02:59:40PM +0100, Hugo Costelha wrote:
> Hi,
>
> On 7/13/06, Stefan Seyfried <[EMAIL PROTECTED]> wrote:
> >> I have a NEC Versa S900 laptop with SUSE 10.1 with an ATI Radeon M9
> >> and ATI propietary drivers. My computer is not in the whitelist but it
> >> worked just by
Hi,
On Thu, Jul 13, 2006 at 12:54:20PM +0200, Pavel Machek wrote:
> Hi!
>
> New whitelist candidate?
> Pavel
>
> - Forwarded message from Hugo Costelha <[EMAIL PROTECTED]> -
>
> X-Original-To: [EMAIL PROTECTED]
> To: [EMAIL P
Hi!
New whitelist candidate?
Pavel
- Forwarded message from Hugo Costelha <[EMAIL PROTECTED]> -
X-Original-To: [EMAIL PROTECTED]
X-Sieve: CMU Sieve 2.2
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
s=beta; d=gmail
On Fri, Jul 07, 2006 at 01:52:05PM +0200, Pavel Machek wrote:
> I guess this gets best solved on the mailinglist. Usually Stefan adds
> s2ram whitelist entries.
Yes, after some additional questions... :-)
> - Forwarded message from Geoff Kuenning <[EMAIL PROTECTED]> -
>
> To: [EMAIL PRO
I guess this gets best solved on the mailinglist. Usually Stefan adds
s2ram whitelist entries.
Pavel
- Forwarded message from Geoff Kuenning <[EMAIL PROTECTED]> -
X-Original-To: [EMAIL PROTECTED]
X-Sieve: CMU Sieve 2.2
To: [EMAIL PR
65 matches
Mail list logo
