From: "Jim Crilly" <jim@why.dont.jablowme.net>
Date: Mon, 30 May 2005 19:48:20 -0400
To: "Ian E. Morgan" <imorgan@webcon.ca>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>, pavel@suse.cz
Subject: Re: Q: swsusp with S5 instead of S4?
Message-ID: <20050530234820.GR28288@voodoo>
Mail-Followup-To: "Ian E. Morgan" <imorgan@webcon.ca>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	pavel@suse.cz
References: <Pine.LNX.4.62.0505021701090.14807@light.int.webcon.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.62.0505021701090.14807@light.int.webcon.net>
User-Agent: Mutt/1.5.9i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1100
Lines: 27

On 05/02/05 05:13:15PM -0400, Ian E. Morgan wrote:
> I'm using swsusp on my new HP dv1000 notebook. In general most everything
> works just fine, in terms of general computing anyways, after resume.
> 
> However, some of the ancilary functions, such as LCD brightness, RF kill
> switch, and volume mute button do not work after resuming.

I had a similar issue in that the power button wouldn't issue any acpi
events after resuming. This was annoying because I could hit the power key
to suspend only once. The solution was to simply remove the acpi button
module before suspend and reload it after resume, if you can figure out
which modules drive the functions that aren't working for you the same
might be possible.

Note that I was using swsusp2 and not the in-kernel swsusp, but I doubt
that would make a difference.

> 
> Regards,
> Ian Morgan

Jim.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/