[mythtv-users] Problems with ACPI shutdown and restart

Yann Lehmann aristide at vtxmail.ch
Tue Feb 25 20:00:59 UTC 2014


On 24. 02. 14 20:57, Craig Huff wrote:
>
> To see what the "most" shutdown state supported for each device/resource
> capable of waking the system up via ACPI, you can run the following
> command as any user:
>
>          # cat /proc/acpi/wakeup
>
> You'll get a list like this:
> Device  S-state   Status   Sysfs node
> HUB0      S5     disabled  pci:0000:00:09.0
> XVR0      S5     disabled  pci:0000:00:0e.0
> XVR1      S5     disabled  pci:0000:00:0d.0
> XVR2      S5     disabled  pci:0000:00:0c.0
> XVR3      S5     disabled  pci:0000:00:0b.0
> USB0      S3     disabled  pci:0000:00:02.0
> USB2      S3     disabled  pci:0000:00:02.1
> MMAC      S5     enabled   pci:0000:00:0a.0
> MMCI      S5     disabled
> UAR1      S5     disabled  pnp:00:08
>
>

Thank you very much Craig for your suggestion.

Unfortunately, the command doesn't seem to mention anything related to 
wakeup on alarm:

yann at myth-backend:~$ cat /proc/acpi/wakeup
Device  S-state   Status   Sysfs node
PCI0      S5    *enabled   no-bus:pci0000:00
USB0      S3    *enabled   pci:0000:00:13.0
USB1      S3    *enabled   pci:0000:00:13.1
USB2      S3    *enabled   pci:0000:00:13.2
USB3      S3    *enabled   pci:0000:00:13.3
USB4      S3    *enabled   pci:0000:00:13.4
USB5      S3    *enabled   pci:0000:00:13.5
SBAZ      S4    *disabled  pci:0000:00:14.2
P2P       S5    *disabled  pci:0000:00:14.4
PCE2      S4    *disabled  pci:0000:00:02.0
PCE3      S4    *disabled
PCE4      S4    *disabled  pci:0000:00:04.0
PCE5      S4    *disabled
PCE6      S4    *disabled
PCE7      S4    *disabled
PCE8      S4    *disabled
PS2K      S5    *enabled   pnp:00:08

As a workaround, I have begun to setup WOL from another computer, as 
explained on the wiki.

But I must be very unlucky these days: the spare system has a problem 
with the onboard NIC. After 2 or 3 reboots, the network link is down, 
and I have to unplug an plug the cable in order to have it coming back. 
May be a problem with shielded cables, who knows.

Thank you anyway for your help and regards


More information about the mythtv-users mailing list