public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: CaT <cat@zip.com.au>
To: Pavel Machek <pavel@suse.cz>
Cc: swsusp@lister.fornax.hu, linux-kernel@vger.kernel.org
Subject: Re: can't get linux to perform a bios suspend (was: Re: [FIX, please test] Re: 2.5.70-bk16 - nfs interferes with s4bios suspend)
Date: Mon, 23 Jun 2003 19:58:37 +1000	[thread overview]
Message-ID: <20030623095837.GE583@zip.com.au> (raw)
In-Reply-To: <20030623095058.GB6158@atrey.karlin.mff.cuni.cz>

On Mon, Jun 23, 2003 at 11:50:58AM +0200, Pavel Machek wrote:
> > 
> > And it activated bios suspend just fine. It didn't resume properly though.
> > The bios resume screen was left behind and the whole setup hung. I've
> > been using the suspend2disk functionality of this laptop under apm and 2.4.x
> > just fine (for months really - I rarely 'rebooted' my laptop) so I don't
> > think it's the bios that's b0rked.
> 
> And did you use S4bios with 2.4.X? apm and acpi are really different.

No. Never really used acpi under 2.4.x cos it all seemed like a bit mess
to me and the couple of times I tried it it just didn't do much of anything.
apm worked so I stuck with it. When I moved to 2.5.x I decided to test-run
as much as possible and so started using acpi.

As a note: at least the screen displayed and the requirements from the 
bios are both thesame when apm and acpi are used.

> Modification you did is wrong; I'd try
> 
> #ifdef CONFIG_SOFTWARE_SUSPEND
>         if ((state == 4) && (state_string[1] != 'b')) {
> 	        software_suspend();
>                 goto Done;
>         }
> #endif  

I had that in my original testing. It hung. I'll try again and tell
you where.

> Does s3 work for you? s3 and s4bios should be really similar.

Haven't tried s3. Will do so asap.

-- 
Martin's distress was in contrast to the bitter satisfaction of some
of his fellow marines as they surveyed the scene. "The Iraqis are sick
people and we are the chemotherapy," said Corporal Ryan Dupre. "I am
starting to hate this country. Wait till I get hold of a friggin' Iraqi.
No, I won't get hold of one. I'll just kill him."
	- http://www.informationclearinghouse.info/article2479.htm

  reply	other threads:[~2003-06-23  9:42 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-13  3:37 2.5.70-bk16 - nfs interferes with s4bios suspend CaT
2003-06-13  6:30 ` Pavel Machek
2003-06-15 18:06 ` Pavel Machek
2003-06-15 23:00   ` CaT
2003-06-15 23:16     ` Pavel Machek
2003-06-15 18:31 ` [FIX, please test] " Pavel Machek
2003-06-16  0:11   ` CaT
2003-06-16  1:41     ` [Swsusp] " Michael Frank
2003-06-16 10:47     ` Pavel Machek
2003-06-18  8:16       ` CaT
2003-06-18 10:17         ` Pavel Machek
2003-06-18 10:26           ` CaT
2003-06-18 10:35             ` Pavel Machek
2003-06-21 14:24               ` can't get linux to perform a bios suspend (was: Re: [FIX, please test] Re: 2.5.70-bk16 - nfs interferes with s4bios suspend) CaT
2003-06-22 15:15                 ` Pavel Machek
2003-06-23  0:58                   ` CaT
2003-06-23  9:50                     ` Pavel Machek
2003-06-23  9:58                       ` CaT [this message]
2003-07-01  8:03                       ` CaT

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030623095837.GE583@zip.com.au \
    --to=cat@zip.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@suse.cz \
    --cc=swsusp@lister.fornax.hu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox