(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
14 matches
Mail list logo
