Mailing List Archive: MythTV: Users

Remote control not working in MythWelcome after hibernate

Index | Next | Previous | View Threaded

mpr.list at googlemail

Jan 6, 2008, 1:54 AM

Post #1 of 10 (1079 views)
Permalink

Remote control not working in MythWelcome after hibernate

Hello MythTV-users!

As stated in the topic, the remote control for my Hauppauge Nova-T 500 DVB-T
card is not working in MythWelcome after resume from hibernate.
I am using ACPI wakeup and as my system will not wake up from a complete power
off, I hibernate the system instead. Waking up for scheduled recordings works
fine, as well as going back to S4 sleep state after the desired period of
idleness.

The remote control used to be adressed as /dev/input/eventX where the X would
vary after hibernation, thus causing it to be non functional (except the
arrow keys, which by the way do work in MythWelcome too) in the frontend.
I have solved this problem by creating a udev link called /dev/input/remote
and pointing the /etc/lirc/hardware.conf to the link instead of the eventX.

When I power on the Myth box, MythWelcome will instantly start the countdown
to shut down again and pressing the OK button on the remote to start the
frontend doesn't do a thing. I will have to press space or return on the
keyboard (which I ultimately want to get rid off when the HTPC will move to
the living room). Also the menu button on the remote will not bring up the
menu. If I open it with M on the keyboard, the arrow keys on the remote will
let me select the menu options though... In the frontend, the remote always
works after hibernation.

I think you get the point...

I already changed the focus settings of XFCE, that did not help.
If I launch irw in a ssh session while the MythBox is in MythWelcome, I can
see every keypress.

The facts that the arrow keys always work and ALL keys work after a cold
boot/reboot make me assume that MythWelcome is addressing the remote control
as /dev/input/eventX where the X only matches the remote before the system
got hibernated the first time.
Still, the only config file I found that mentions the remote as a device
is /etc/lirc/hardware.conf.

Now some info on my system:

Asus P4B266-LM mainboard with a P4 1.8 GHz and 664 MB RAM
GeForce 6200 256 MB NVidia Driver 100.14.11
Hauppauge Nova-T 500 (set up as described in and config files for the remote
from the wiki)
MythBuntu 7.10, MythTV 0.20.2

Rock on,
Jan

PS: This is my first post on a mailing list ever, be gentle... ;)

PPS: Seems like KMail does not like Gmail or something. It seemed to me that
the mail never made it to the list, so I resent it. If it now appears twice,
I am truly sorry for that.
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

mpr.list at googlemail

Jan 14, 2008, 9:22 PM

Post #2 of 10 (990 views)
Permalink

Re: Remote control not working in MythWelcome after hibernate [In reply to]

On 1/6/08, MPR List <mpr.list [at] googlemail> wrote:
> Hello MythTV-users!
>
> As stated in the topic, the remote control for my Hauppauge Nova-T 500 DVB-T
> card is not working in MythWelcome after resume from hibernate.
> I am using ACPI wakeup and as my system will not wake up from a complete power
> off, I hibernate the system instead. Waking up for scheduled recordings works
> fine, as well as going back to S4 sleep state after the desired period of
> idleness.
>
> The remote control used to be adressed as /dev/input/eventX where the X would
> vary after hibernation, thus causing it to be non functional (except the
> arrow keys, which by the way do work in MythWelcome too) in the frontend.
> I have solved this problem by creating a udev link called /dev/input/remote
> and pointing the /etc/lirc/hardware.conf to the link instead of the eventX.
>
> When I power on the Myth box, MythWelcome will instantly start the countdown
> to shut down again and pressing the OK button on the remote to start the
> frontend doesn't do a thing. I will have to press space or return on the
> keyboard (which I ultimately want to get rid off when the HTPC will move to
> the living room). Also the menu button on the remote will not bring up the
> menu. If I open it with M on the keyboard, the arrow keys on the remote will
> let me select the menu options though... In the frontend, the remote always
> works after hibernation.
>
> I think you get the point...
>
>
> I already changed the focus settings of XFCE, that did not help.
> If I launch irw in a ssh session while the MythBox is in MythWelcome, I can
> see every keypress.
>
>
> The facts that the arrow keys always work and ALL keys work after a cold
> boot/reboot make me assume that MythWelcome is addressing the remote control
> as /dev/input/eventX where the X only matches the remote before the system
> got hibernated the first time.
> Still, the only config file I found that mentions the remote as a device
> is /etc/lirc/hardware.conf.
>
>
> Now some info on my system:
>
> Asus P4B266-LM mainboard with a P4 1.8 GHz and 664 MB RAM
> GeForce 6200 256 MB NVidia Driver 100.14.11
> Hauppauge Nova-T 500 (set up as described in and config files for the remote
> from the wiki)
> MythBuntu 7.10, MythTV 0.20.2
>
> Rock on,
> Jan
>
> PS: This is my first post on a mailing list ever, be gentle... ;)
>

Pardon me to bump my own message...

But the issue has become even more severe now that I have moved the
HTPC interiors to an Antec Fusion V2 case, which is located in the TV
rack.
After a cold boot the remote works in MythWelcome, but once hibernated
and woken up again, I need to start a VNC session on my laptop just to
press "Start Frontend". In the frontend the remote will work just
fine, like before...

Now that the case comes with a built-in IR receiver, is there any
chance to use that instead of the dongle for the TV card? I don't
think the Hauppauge remote is MCE compatible though...

Rock on,
Jan
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

foppe.benedictus at knkv

Jan 14, 2008, 11:14 PM

Post #3 of 10 (989 views)
Permalink

Re: Remote control not working in MythWelcome after hibernate [In reply to]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

MPR List schreef:
| Pardon me to bump my own message...
|
| But the issue has become even more severe now that I have moved the
| HTPC interiors to an Antec Fusion V2 case, which is located in the TV
| rack.
| Now that the case comes with a built-in IR receiver, is there any
| chance to use that instead of the dongle for the TV card? I don't
| think the Hauppauge remote is MCE compatible though...

I have a kind of the same question, I also have the Antec Fusion V2 but
a MCE remote and can't get it working. With mode2 I get a output but
when using a lircd.conf from the web irw doesn't do anything, the same
with a licrd.conf I made myself with irrecord (not all buttons
configured, but that shouldn't matter, does it?) or when I use the codes
that mode2 gives me, irw doesn't respond.
Yes, I have adjusted hardware.conf (I use Ubuntu with Mythbuntu installed).
Is there anyway I can see the codes are correct and where it goes wrong?

Foppe
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHjF1atK8Zi+dRolURAp6/AJ4/C1jfxKMuokL+DkfheEP3EIM/YgCdHbzc
JMYr2VWh2CQwAwO2UbK5jZ0=
=b973
-----END PGP SIGNATURE-----
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

derliebegott at gmail

Jan 15, 2008, 12:58 AM

Post #4 of 10 (966 views)
Permalink

Re: Remote control not working in MythWelcome after hibernate [In reply to]

2008/1/15, MPR List <mpr.list [at] googlemail>:
> On 1/6/08, MPR List <mpr.list [at] googlemail> wrote:
> > Hello MythTV-users!
> >
> > As stated in the topic, the remote control for my Hauppauge Nova-T 500 DVB-T
> > card is not working in MythWelcome after resume from hibernate.
> > I am using ACPI wakeup and as my system will not wake up from a complete power
> > off, I hibernate the system instead. Waking up for scheduled recordings works
> > fine, as well as going back to S4 sleep state after the desired period of
> > idleness.
> >
> > The remote control used to be adressed as /dev/input/eventX where the X would
> > vary after hibernation, thus causing it to be non functional (except the
> > arrow keys, which by the way do work in MythWelcome too) in the frontend.
> > I have solved this problem by creating a udev link called /dev/input/remote
> > and pointing the /etc/lirc/hardware.conf to the link instead of the eventX.
> >
> > When I power on the Myth box, MythWelcome will instantly start the countdown
> > to shut down again and pressing the OK button on the remote to start the
> > frontend doesn't do a thing. I will have to press space or return on the
> > keyboard (which I ultimately want to get rid off when the HTPC will move to
> > the living room). Also the menu button on the remote will not bring up the
> > menu. If I open it with M on the keyboard, the arrow keys on the remote will
> > let me select the menu options though... In the frontend, the remote always
> > works after hibernation.
> >
> > I think you get the point...
> >
> >
> > I already changed the focus settings of XFCE, that did not help.
> > If I launch irw in a ssh session while the MythBox is in MythWelcome, I can
> > see every keypress.
> >
> >
> > The facts that the arrow keys always work and ALL keys work after a cold
> > boot/reboot make me assume that MythWelcome is addressing the remote control
> > as /dev/input/eventX where the X only matches the remote before the system
> > got hibernated the first time.
> > Still, the only config file I found that mentions the remote as a device
> > is /etc/lirc/hardware.conf.
> >
> >
> > Now some info on my system:
> >
> > Asus P4B266-LM mainboard with a P4 1.8 GHz and 664 MB RAM
> > GeForce 6200 256 MB NVidia Driver 100.14.11
> > Hauppauge Nova-T 500 (set up as described in and config files for the remote
> > from the wiki)
> > MythBuntu 7.10, MythTV 0.20.2
> >
> > Rock on,
> > Jan
> >
> > PS: This is my first post on a mailing list ever, be gentle... ;)
> >
>
> Pardon me to bump my own message...
>
> But the issue has become even more severe now that I have moved the
> HTPC interiors to an Antec Fusion V2 case, which is located in the TV
> rack.
> After a cold boot the remote works in MythWelcome, but once hibernated
> and woken up again, I need to start a VNC session on my laptop just to
> press "Start Frontend". In the frontend the remote will work just
> fine, like before...
>
> Now that the case comes with a built-in IR receiver, is there any
> chance to use that instead of the dongle for the TV card? I don't
> think the Hauppauge remote is MCE compatible though...

Hi,

I have Antec Fusion Black with probably same built-in IR reciever. it
is using lirc_imon and I am using it with Hauppauge MCE remote which I
got together with PVR500.

After suspend, IR receiver does not work at all for me. The only way
to get it work was to restart/reload lirc and lirc modules. The
problem ist that I also have to restart mythfrontend/mythwelcome,
because mythfrontend does not react on lirc after it was restarted.
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

bryan.bennetts at gmail

Jan 15, 2008, 2:03 AM

Post #5 of 10 (975 views)
Permalink

Re: Remote control not working in MythWelcome after hibernate [In reply to]

On Sunday 06 January 2008 09:54, Jan wrote:
> Hello MythTV-users!
>
> As stated in the topic, the remote control for my Hauppauge Nova-T 500
> DVB-T card is not working in MythWelcome after resume from hibernate.
> I am using ACPI wakeup and as my system will not wake up from a complete
> power off, I hibernate the system instead. Waking up for scheduled
> recordings works fine, as well as going back to S4 sleep state after the
> desired period of idleness.
>
> The remote control used to be adressed as /dev/input/eventX where the X
> would vary after hibernation, thus causing it to be non functional (except
> the arrow keys, which by the way do work in MythWelcome too) in the
> frontend. I have solved this problem by creating a udev link called
> /dev/input/remote and pointing the /etc/lirc/hardware.conf to the link
> instead of the eventX.
>
> When I power on the Myth box, MythWelcome will instantly start the
> countdown to shut down again and pressing the OK button on the remote to
> start the frontend doesn't do a thing. I will have to press space or return
> on the keyboard (which I ultimately want to get rid off when the HTPC will
> move to the living room). Also the menu button on the remote will not bring
> up the menu. If I open it with M on the keyboard, the arrow keys on the
> remote will let me select the menu options though... In the frontend, the
> remote always works after hibernation.
>

FWIW, the countdown shouldn't be starting at all. If the machine is
successfully waking up to start recordings it means that mythWelcome is
correctly setting the wakeup time? If that's the case when you manually
power up mythWelcome performs a check between the current time and the next
scheduled wakeup time, if the difference is greater than a given threshold it
*should* just start the FE automagically. Of course, there is the chance you
are manually powering up within the threshold period, at which point all bets
are off and you'd get the case you are seeing.

> I think you get the point...
>
>
> I already changed the focus settings of XFCE, that did not help.
> If I launch irw in a ssh session while the MythBox is in MythWelcome, I can
> see every keypress.
>
>
> The facts that the arrow keys always work and ALL keys work after a cold
> boot/reboot make me assume that MythWelcome is addressing the remote
> control as /dev/input/eventX where the X only matches the remote before the
> system got hibernated the first time.
> Still, the only config file I found that mentions the remote as a device
> is /etc/lirc/hardware.conf.
>
>
> Now some info on my system:
>
> Asus P4B266-LM mainboard with a P4 1.8 GHz and 664 MB RAM
> GeForce 6200 256 MB NVidia Driver 100.14.11
> Hauppauge Nova-T 500 (set up as described in and config files for the
> remote from the wiki)
> MythBuntu 7.10, MythTV 0.20.2
>
> Rock on,
> Jan

IIRC you can tell hibernate to stop services before going to sleep and restart
them afterwards, you *may* get some mileage stopping lirc/mythbackend and
restarting them or possibly removing the event handling module and
re-inserting it? I guess experimentation would be the key.

>
> PS: This is my first post on a mailing list ever, be gentle... ;)
>
> PPS: Seems like KMail does not like Gmail or something. It seemed to me
> that the mail never made it to the list, so I resent it. If it now appears
> twice, I am truly sorry for that.

Hmm, I use KMail and GMail not had this problem...bad luck I guess :)

Bryan.
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

mpr.list at googlemail

Jan 15, 2008, 2:17 AM

Post #6 of 10 (975 views)
Permalink

Re: Remote control not working in MythWelcome after hibernate [In reply to]

On 1/15/08, Bryan Bennetts <bryan.bennetts [at] gmail> wrote:

> FWIW, the countdown shouldn't be starting at all. If the machine is
> successfully waking up to start recordings it means that mythWelcome is
> correctly setting the wakeup time? If that's the case when you manually
> power up mythWelcome performs a check between the current time and the next
> scheduled wakeup time, if the difference is greater than a given threshold it
> *should* just start the FE automagically. Of course, there is the chance you
> are manually powering up within the threshold period, at which point all bets
> are off and you'd get the case you are seeing.
>
I have unchecked the option to start the FE automatically if the
machine is powered on manually because this makes MythWelcome crash
when I exit the frontend again. That may or may not be related.
Waking up for recordings works so far, only there is no way to start
the Frontend from Mythwelcome if I start the MythBox manually.

> IIRC you can tell hibernate to stop services before going to sleep and restart
> them afterwards, you *may* get some mileage stopping lirc/mythbackend and
> restarting them or possibly removing the event handling module and
> re-inserting it? I guess experimentation would be the key.
>

Well, I am stopping lirc and mythbackend and unloading all the DVB
modules before hibernate, other wise it would not work at all. I can
not confirm what Ma wrote that mytfrontend would not react to lirc
being restarted, might be different with the lirc_imon module, which I
do not use for the remote (yet).

> Hmm, I use KMail and GMail not had this problem...bad luck I guess :)

Well that was some confusion about @gmail.com and @googlemail.com
(which we have to use in Germany due to legal issues), it works now...

Thanks for the help so far, if there is any further info which I need
to dig out, I will happily do so when I get home tonight!

Rock on,
Jan
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

derliebegott at gmail

Jan 15, 2008, 2:38 AM

Post #7 of 10 (971 views)
Permalink

Re: Remote control not working in MythWelcome after hibernate [In reply to]

2008/1/15, MPR List <mpr.list [at] googlemail>:
> On 1/15/08, Bryan Bennetts <bryan.bennetts [at] gmail> wrote:
>
>
> > FWIW, the countdown shouldn't be starting at all. If the machine is
> > successfully waking up to start recordings it means that mythWelcome is
> > correctly setting the wakeup time? If that's the case when you manually
> > power up mythWelcome performs a check between the current time and the next
> > scheduled wakeup time, if the difference is greater than a given threshold it
> > *should* just start the FE automagically. Of course, there is the chance you
> > are manually powering up within the threshold period, at which point all bets
> > are off and you'd get the case you are seeing.
> >
> I have unchecked the option to start the FE automatically if the
> machine is powered on manually because this makes MythWelcome crash
> when I exit the frontend again. That may or may not be related.
> Waking up for recordings works so far, only there is no way to start
> the Frontend from Mythwelcome if I start the MythBox manually.
>
> > IIRC you can tell hibernate to stop services before going to sleep and restart
> > them afterwards, you *may* get some mileage stopping lirc/mythbackend and
> > restarting them or possibly removing the event handling module and
> > re-inserting it? I guess experimentation would be the key.
> >
>

> Well, I am stopping lirc and mythbackend and unloading all the DVB
> modules before hibernate, other wise it would not work at all. I can
> not confirm what Ma wrote that mytfrontend would not react to lirc
> being restarted, might be different with the lirc_imon module, which I
> do not use for the remote (yet).

You want to say that when you kill lircd process and start it again,
you do not have to restart mythfrontend?

I am also removing lirc modules ... maybe I should try without removing them
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

mpr.list at googlemail

Jan 15, 2008, 4:08 AM

Post #8 of 10 (979 views)
Permalink

Re: Remote control not working in MythWelcome after hibernate [In reply to]

On 1/15/08, Ma Begaj <derliebegott [at] gmail> wrote:

> > Well, I am stopping lirc and mythbackend and unloading all the DVB
> > modules before hibernate, other wise it would not work at all. I can
> > not confirm what Ma wrote that mytfrontend would not react to lirc
> > being restarted, might be different with the lirc_imon module, which I
> > do not use for the remote (yet).
>
> You want to say that when you kill lircd process and start it again,
> you do not have to restart mythfrontend?
>
> I am also removing lirc modules ... maybe I should try without removing them

Not exactly, I am hibernating from MythWelcome, so technically the FE
is not even running. And I don't know about the modules, since the IR
receiver of the Nova-T 500 uses /dev/input and the kernel driver for
it, no seperate modules (AFAIK),

On 1/15/08, Bryan Bennetts <bryan.bennetts [at] pulsic> wrote:
>
> Speaking of the DVB drivers you may be interested in this, although I'm not
> sure if it holds for S4 as well as S3 and S5. Of course it depends on what
> version of the DVB drivers you are using as well!
>
> http://bugzilla.kernel.org/show_bug.cgi?id=8689
>
> Bry.

I am unsure how much of that is applicable for the Nova-T 500. It uses
dvb_usb. Besides that, after S3 the tuners won't even work, can't
remember if the remote did. I gave up on S3 pretty quickly after I
found S4 working...
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

eduardhc at gmail

Jan 15, 2008, 4:16 AM

Post #9 of 10 (967 views)
Permalink

Re: Remote control not working in MythWelcome after hibernate [In reply to]

>
> Hello MythTV-users!
>
> As stated in the topic, the remote control for my Hauppauge Nova-T 500
> DVB-T
> card is not working in MythWelcome after resume from hibernate.
> I am using ACPI wakeup and as my system will not wake up from a complete
> power
> off, I hibernate the system instead. Waking up for scheduled recordings
> works
> fine, as well as going back to S4 sleep state after the desired period of
> idleness.
>
> The remote control used to be adressed as /dev/input/eventX where the X
> would
> vary after hibernation, thus causing it to be non functional (except the
> arrow keys, which by the way do work in MythWelcome too) in the frontend.
> I have solved this problem by creating a udev link called
> /dev/input/remote
> and pointing the /etc/lirc/hardware.conf to the link instead of the
> eventX.
>
> When I power on the Myth box, MythWelcome will instantly start the
> countdown
> to shut down again and pressing the OK button on the remote to start the
> frontend doesn't do a thing. I will have to press space or return on the
> keyboard (which I ultimately want to get rid off when the HTPC will move
> to
> the living room). Also the menu button on the remote will not bring up the
>
> menu. If I open it with M on the keyboard, the arrow keys on the remote
> will
> let me select the menu options though... In the frontend, the remote
> always
> works after hibernation.
>
> I think you get the point...
>
>
> I already changed the focus settings of XFCE, that did not help.
> If I launch irw in a ssh session while the MythBox is in MythWelcome, I
> can
> see every keypress.
>
>
> The facts that the arrow keys always work and ALL keys work after a cold
> boot/reboot make me assume that MythWelcome is addressing the remote
> control
> as /dev/input/eventX where the X only matches the remote before the system
>
> got hibernated the first time.
> Still, the only config file I found that mentions the remote as a device
> is /etc/lirc/hardware.conf.
>
>
> Now some info on my system:
>
> Asus P4B266-LM mainboard with a P4 1.8 GHz and 664 MB RAM
> GeForce 6200 256 MB NVidia Driver 100.14.11
> Hauppauge Nova-T 500 (set up as described in and config files for the
> remote
> from the wiki)
> MythBuntu 7.10, MythTV 0.20.2
>
> Rock on,
> Jan
>
> PS: This is my first post on a mailing list ever, be gentle... ;)
>
> PPS: Seems like KMail does not like Gmail or something. It seemed to me
> that
> the mail never made it to the list, so I resent it. If it now appears
> twice,
> I am truly sorry for that.
>

Hi,
I have the same card as you (Nova T-500) and I usually have the same
issue. I suspect it's something related to the IR driver for this card,
which is not properly restoring after a suspend / resume cycle. My solution
was to add also 'lircd' and 'xdm' to the lists of services being stopped /
started on suspending, so both the LIRC daemon and whole X (and thus
MythFrontend) are restarted. In my case, restarting X was also a must, as
sometimes resuming didn't work fine always othewise.

Anyway, a final thought: your computer should wake up properly with ACPI
either from suspending or from powering off, or simply not work on either
case. I mean, both things are exactly the same from a pure hardware point of
view (suspending IS a full power off, it's just the kernel who saves /
restores the OS state).

So if ACPI wakeup is working from resume but not from power-off then it's
probably because your Linux is saving your "system" time into the BIOS when
powering off (most Linux do that by default), and your BIOS doesn't like
that (at least, mine doesn't like neither...).

You'll probably have to edit the /etc/init.d/clockd script (or whatever is
called in your distro) to save / restore the ACPI programmed time. Basically
you must something like this:

� search for the stop() function in /etc/init.d/clock script
� add this line in the beginning of the function:

ACPI=`cat /proc/acpi/alarm`

� and this one at the end of the function:

echo $ACPI > /proc/acpi/alarm

This should solve your issue.

Best regards,
Eduard

mpr.list at googlemail

Jan 15, 2008, 9:28 PM

Post #10 of 10 (952 views)
Permalink

Re: Remote control not working in MythWelcome after hibernate [In reply to]

On 1/15/08, Eduard Huguet <eduardhc [at] gmail> wrote:

> Hi,
> I have the same card as you (Nova T-500) and I usually have the same
> issue. I suspect it's something related to the IR driver for this card,
> which is not properly restoring after a suspend / resume cycle. My solution
> was to add also 'lircd' and 'xdm' to the lists of services being stopped /
> started on suspending, so both the LIRC daemon and whole X (and thus
> MythFrontend) are restarted. In my case, restarting X was also a must, as
> sometimes resuming didn't work fine always othewise.
>
Well, restarting X works to get the remote back to live in
MythWelcome. This is only a dirty hack IMHO though, since the remote
would work in MythFrontend after hibernate anyway, only I could not
start the FE with the remote...

> Anyway, a final thought: your computer should wake up properly with ACPI
> either from suspending or from powering off, or simply not work on either
> case. I mean, both things are exactly the same from a pure hardware point of
> view (suspending IS a full power off, it's just the kernel who saves /
> restores the OS state).
>
> So if ACPI wakeup is working from resume but not from power-off then it's
> probably because your Linux is saving your "system" time into the BIOS when
> powering off (most Linux do that by default), and your BIOS doesn't like
> that (at least, mine doesn't like neither...).
>
> You'll probably have to edit the /etc/init.d/clockd script (or whatever is
> called in your distro) to save / restore the ACPI programmed time. Basically
> you must something like this:
>
> � search for the stop() function in /etc/init.d/clock script
> � add this line in the beginning of the function:
>
> ACPI=`cat /proc/acpi/alarm`
>
> � and this one at the end of the function:
>
> echo $ACPI > /proc/acpi/alarm
>
> This should solve your issue.
>
> Best regards,
> Eduard
>

I have set up ACPI wake up according to the Ubuntu Wiki
https://help.ubuntu.com/community/MythTV/Install/WhatNext/ACPIWake
and I have done the changes to the hwclock.sh as mentioned there and
like you say. My hwclock.sh was a little different to the example on
the Ubuntu wiki though, so I am not sure if I have added the command
to set the acpi time properly.

Taking restarting X into consideration, a fresh boot will not be much
slower than resuming from hibernate anymore. If the system would wake
up from complete power off, I could as well use that and be safe that
everything will work...

Rock on,
Jan
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads