From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Dino Klein" Subject: Re: ACPI wake up event (alarm) Date: Thu, 15 Apr 2004 16:11:37 +0000 Sender: acpi-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Return-path: Errors-To: acpi-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: Jarek Zuk , acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Id: linux-acpi@vger.kernel.org According to the specs the RTC must be able to wakeup a system from S1, S= 2, or S3, S4 is optional, and S5 is not even considered a sleep state, so= the RTC is not required to support S5. (check ACPI 2.0c, section 4.7.2.4= , and table 5-9) Even still, the chipset might support it, as my Via 686B which treats S4 = & S5 the same way. This is just a guess, but perhaps the handling of the wakeup bits in the = linux ACPI is inconsistent, so when you transition to S1, it does allow f= or a wakeup from the RTC, and then doesn't clear it before entering S5 (a= s specified in the footnote). However, when you go directly to S5, the RT= C is not set as wakup source, and that's why it doesn't work. If S3 or S4 work for you, then perhaps you should use them, thus avoiding= this whole issue. One sidenote - are you unmounting the filesystems before putting the mach= ine to S5? after all, that's the equivalent of pressing the power button.= > -----Original Message----- > From: Jarek Zuk [mailto:j.zuk-QYlicCNJNu5TzFIbWlesCw@public.gmane.org] > Sent: Thursday, April 15, 2004 12:48 PM > To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org > Subject: [ACPI] ACPI wake up event (alarm) > > > I have a question about ACPI alarm (/proc/acpi/alarm). > > I have a cron job that runs early in the morning, so I need my machine= to be up at that time. > I dont want to have it up all night, so I want to use the alarm feature= . > > I use kernel 2.4.25 with your corresponding patch. I read everything on= acpi page about > /proc/acpi/sleep and /proc/acpi/alarm . > What I want to do is : > echo 2004-04-15 14:40:00 > /proc/acpi/alarm > echo 5 > /proc/acpi/sleep > > and get the computer up when the specified time comes. > > My problem is that it works sometimes, well what I noticed is that it = works providing that > before I put the system into sleep mode (5) I do : > echo 1 > /proc/acpi/sleep > (the power button starts blinking) > press the button ( system is awake ) > > When I dont do this "echo 1 > /proc/acpi/sleep" thing , the computer = doesn't turn on > whet time comes. :( > > Looks like putting system into a sleep mode 1 changes something that al= lows later to > do proper wakeup. > > Does the system have to be in sleep mode to be woken up by alarm event = ? or it should work > also after shutdown ? > > I want to have this procedure in a script and presing the power button = is kinda difficult from a > script. > > Any pointers are welcome. > Jarek Zuk > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: IBM Linux Tutorials > Free Linux tutorial presented by Daniel Robbins, President and CEO of > GenToo technologies. Learn everything from fundamentals to system > administration.http://ads.osdn.com/?ad_id=3D1470&alloc_id=3D3638&op=3Dc= lick > _______________________________________________ > Acpi-devel mailing list > Acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org > https://lists.sourceforge.net/lists/listinfo/acpi-devel > ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click