Mailing List Archive: MythTV: Users

ACPI Wakeup stopped working

Index | Next | Previous | View Threaded

memoryguy at gmail

Jun 7, 2012, 6:36 PM

Post #1 of 6 (559 views)
Permalink

ACPI Wakeup stopped working

Hi,

I assume it's something I did wrong, but I can't think of what I might
have done, other than installing OS (Mythbuntu 11.10) updates

I noticed that suddenly ACPI Wakeup isn't working anymore. I've set it
up according to the wiki page, http://www.mythtv.org/wiki/ACPI_Wakeup
, and it has been working perfectly since I built the current machine
last August. I didn't make any configuration changes recently.

I followed the manual tests and it seemed to indicate that it was working:

$ sudo sh -c "echo 0 > /sys/class/rtc/rtc0/wakealarm"
$ sudo sh -c "echo `date '+%s' -d '+ 15 minutes'` >
/sys/class/rtc/rtc0/wakealarm"
$ cat /proc/driver/rtc
rtc_time : 01:16:30
rtc_date : 2012-06-08
alrm_time : 01:31:23
alrm_date : 2012-06-08
alarm_IRQ : yes
alrm_pending : no
update IRQ enabled : no
periodic IRQ enabled : no
periodic IRQ frequency : 1024
max user IRQ frequency : 64
24hr : yes
periodic_IRQ : no
update_IRQ : no
HPET_emulated : yes
BCD : yes
DST_enable : no
periodic_freq : 1024
batt_status : okay

but then when I shut down and wait, the machine doesn't turn back on.
Since the manual steps are not working, I guess it's probably not
directly a MythTV problem.

I'm running Mythbuntu 11.10, with latest updates (as far as I know),
and Myth version:

$ mythbackend --version
Please attach all output as a file in bug reports.
MythTV Version : v0.25.1-1-g016db04
MythTV Branch : fixes/0.25
Network Protocol : 72
Library API : 0.25.20120506-1
QT Version : 4.7.4
Options compiled in:
linux profile use_hidesyms using_alsa using_oss using_pulse
using_pulseoutput using_backend using_bindings_perl
using_bindings_python using_bindings_php using_crystalhd using_dvb
using_firewire using_frontend using_hdhomerun using_ceton using_hdpvr
using_iptv using_ivtv using_joystick_menu using_libcec using_libcrypto
using_libdns_sd using_libxml2 using_lirc using_mheg using_opengl_video
using_qtwebkit using_qtscript using_qtdbus using_v4l2 using_x11
using_xrandr using_xv using_bindings_perl using_bindings_python
using_bindings_php using_mythtranscode using_opengl using_vaapi
using_vdpau using_ffmpeg_threads using_live using_mheg using_libass
using_libxml2

Anyone have a similar problem, or can suggest anything that I can investigate?

I did have a problem a few days ago where, somehow, the OS/database
filesystem filled up, and it took a bit to make MySQL happy again, but
I'm nearly positive that wakeup was still working after that.

Thanks,
aaron
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users

keemllib at gmail

Jun 7, 2012, 6:54 PM

Post #2 of 6 (543 views)
Permalink

Re: ACPI Wakeup stopped working [In reply to]

On 06/07/2012 08:36 PM, aaron wrote:
> I assume it's something I did wrong, but I can't think of what I might
> have done, other than installing OS (Mythbuntu 11.10) updates
...

Hi;

Did a line like this in /etc/default/grub get removed?

GRUB_CMDLINE_LINUX_DEFAULT="hpet=disabled"

--
Bill
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users

memoryguy at gmail

Jun 7, 2012, 7:05 PM

Post #3 of 6 (544 views)
Permalink

Re: ACPI Wakeup stopped working [In reply to]

On Thu, Jun 7, 2012 at 9:54 PM, Bill Meek <keemllib [at] gmail> wrote:
>
> Hi;
>
> Did a line like this in /etc/default/grub get removed?
>
> GRUB_CMDLINE_LINUX_DEFAULT="hpet=disabled"

Ah, interesting ... it looks like there isn't such a line:

aperl [at] monste:/etc/default$ grep CMDLINE grub
GRUB_CMDLINE_LINUX_DEFAULT=""
GRUB_CMDLINE_LINUX=""

but how can I tell whether there was something in the past?

Oh wait, actually as I look at the file I remember I had been trying
to address an intermittent boot hang by fiddling some grub options
(which proved to be ineffective) and I had (long ago) landed on the
above non-value. So I guess such a line wasn't removed.... should I
try adding it? :)

(it's busy recording at the moment, but I could try it later/tomorrow
when it's not busy)

Thanks,
aaron
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users

dmoo1790 at ihug

Jun 7, 2012, 9:18 PM

Post #4 of 6 (538 views)
Permalink

Re: ACPI Wakeup stopped working [In reply to]

On 08/06/12 14:05, aaron wrote:
> On Thu, Jun 7, 2012 at 9:54 PM, Bill Meek<keemllib [at] gmail> wrote:
>>
>> Hi;
>>
>> Did a line like this in /etc/default/grub get removed?
>>
>> GRUB_CMDLINE_LINUX_DEFAULT="hpet=disabled"
>
> Ah, interesting ... it looks like there isn't such a line:
>
> aperl [at] monste:/etc/default$ grep CMDLINE grub
> GRUB_CMDLINE_LINUX_DEFAULT=""
> GRUB_CMDLINE_LINUX=""
>
> but how can I tell whether there was something in the past?
>
> Oh wait, actually as I look at the file I remember I had been trying
> to address an intermittent boot hang by fiddling some grub options
> (which proved to be ineffective) and I had (long ago) landed on the
> above non-value. So I guess such a line wasn't removed.... should I
> try adding it? :)
>
> (it's busy recording at the moment, but I could try it later/tomorrow
> when it's not busy)
>
> Thanks,
> aaron

I've been using the ACPI wakeup for ages with no probs. With myth 0.23
and now 0.25. I don't have the
GRUB_CMDLINE_LINUX_DEFAULT="hpet=disabled" option in /etc/default/grub
either. And I don't recall fiddling with that file. I'm running Ubuntu
10.04.

Sorry but I can't see any obvious clue in your emails. Just a thought:
Your BIOS settings haven't changed?
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users

memoryguy at gmail

Jun 8, 2012, 3:04 AM

Post #5 of 6 (532 views)
Permalink

Re: ACPI Wakeup stopped working [In reply to]

On Fri, Jun 8, 2012 at 12:18 AM, David Moore <dmoo1790 [at] ihug> wrote:
>
>
> I've been using the ACPI wakeup for ages with no probs. With myth 0.23 and
> now 0.25. I don't have the GRUB_CMDLINE_LINUX_DEFAULT="hpet=disabled" option
> in /etc/default/grub either. And I don't recall fiddling with that file. I'm
> running Ubuntu 10.04.

Thanks, I don't recall seeing that line in mine before, either. And it
always did work for me.

>
> Sorry but I can't see any obvious clue in your emails. Just a thought: Your
> BIOS settings haven't changed?

I was taking a look in the BIOS/UEFI, and it looks like everything is
okay. My building did have a power outage last Thursday (May 31), but
I'm pretty sure the wakeup continued working after that. Anyway, it
looked like the "Wake on RTC" setting was still Enabled. After I try
to set a wakeup time, if I reboot into the BIOS the Wake on RTC time
is still set to something like:
Days: 15
Hour: 0
Min: 0
Sec: 0

(the machine is off at the moment, if it's important I can turn it on
when I come home from work and get the exact numbers it shows. But I
think it's just indicating that the alarm isn't actually getting set)

Thanks,
aaron
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users

memoryguy at gmail

Oct 7, 2012, 7:08 AM

Post #6 of 6 (361 views)
Permalink

Re: ACPI Wakeup stopped working [In reply to]

On Fri, Jun 8, 2012 at 6:04 AM, aaron <memoryguy [at] gmail> wrote:
>
> I was taking a look in the BIOS/UEFI, and it looks like everything is
> okay. My building did have a power outage last Thursday (May 31), but
> I'm pretty sure the wakeup continued working after that. Anyway, it
> looked like the "Wake on RTC" setting was still Enabled. After I try
> to set a wakeup time, if I reboot into the BIOS the Wake on RTC time
> is still set to something like:
> Days: 15
> Hour: 0
> Min: 0
> Sec: 0
>
> (the machine is off at the moment, if it's important I can turn it on
> when I come home from work and get the exact numbers it shows. But I
> think it's just indicating that the alarm isn't actually getting set)

So I've been "working around" the issue for quite a while, by making
sure the machine is turned on in the morning before I leave for work,
and shutting it down/rebooting it occasionally to "avoid" crashes and
hangs. I tried updating the BIOS a few times, and other random
ideas... Finally I think I figured out the problem.

It seems that having "Wake on RTC" *enabled* in the BIOS is the
problem. I came to an idea that maybe it was because I had tried to
enable all the other "Wake on blah" options (none of which are working
for me :( ), and I thought maybe there's a conflict. So I turned them
all off, except RTC, and still no dice. So finally I decided to turn
off Wake on RTC, a kablammo, wakeup now works.

I still have a different issue with the machine hanging irregularly
during bootup (the screen stays blank, so I have no idea whether it's
a LILO (no wait, Mythbuntu uses GRUB, doesn't it... whether it's a
GRUB) or kernel/startup problem.... after I hit the Reset button when
it hangs, I'm brought to a GRUB prompt and have to hit Enter to keep
booting (at some point I fixed that so I don't have to intervene, but
the change got lost during some recent package update). Usually this
second boot works, but occasionally it hangs as well, but this time I
can see the kernel messages. But that's another issue for another
e-mail. :)

Just wanted to let everyone know that I managed to solve my wakeup
issue, finally. Since I know you were all waiting with baited breath
to hear the outcome ;-)

In case it helps anyone else solve such a mystery in the future...

aaron
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads