Archive:Suspend and wake in Ubuntu - Revision history

Karellen at 01:01, 20 August 2020

2020-08-20T01:01:49Z

← Older revision		Revision as of 01:01, 20 August 2020
Line 119:		Line 119:

	<source lang="bash">chmod 755 /etc/pm/sleep.d/90_lirc</source>		<source lang="bash">chmod 755 /etc/pm/sleep.d/90_lirc</source>

	~~[[Category:Linux]]~~
	~~[[Category:How-to]]~~

Karellen: Karellen moved page HOW-TO:Suspend and wake in Ubuntu to Archive:Suspend and wake in Ubuntu without leaving a redirect: Outdated

2020-08-20T01:01:24Z

Karellen moved page HOW-TO:Suspend and wake in Ubuntu to Archive:Suspend and wake in Ubuntu without leaving a redirect: Outdated

← Older revision	Revision as of 01:01, 20 August 2020
(No difference)

Ned Scott at 06:47, 1 June 2016

2016-06-01T06:47:14Z

← Older revision		Revision as of 06:47, 1 June 2016
Line 1:		Line 1:
			{{cleanup}}

	=Enabling Suspend / Wake / Shutdown / Power off on Ubuntu Linux=		=Enabling Suspend / Wake / Shutdown / Power off on Ubuntu Linux=
	First, test XBMC to see if it already suspends. You may not need any extra setup. If it does not suspend properly, one or more of the following techniques may be necessary. Go through them in order and stop once you have a working suspend and wake. Be certain to test it more than once, there is a bug that will express itself as not suspending after the first wake is successful.		First, test XBMC to see if it already suspends. You may not need any extra setup. If it does not suspend properly, one or more of the following techniques may be necessary. Go through them in order and stop once you have a working suspend and wake. Be certain to test it more than once, there is a bug that will express itself as not suspending after the first wake is successful.

Ned Scott: /* Enable Wake on Other Devices */

2015-05-13T01:26:45Z

Enable Wake on Other Devices

← Older revision		Revision as of 01:26, 13 May 2015
Line 82:		Line 82:
	== Ubuntu Kernel bug ==		== Ubuntu Kernel bug ==
	If you are running a recent Ubuntu lucid install, and your device refuses to resume from standby even while the correct wakeup devices are set in /proc/acpi/wakeup. It could be caused because of a bug in the current Ubuntu kernel. Kernel versions starting from 2.6.32-23 are affected by this bug. A possible solution is to downgrade your kernel to 2.6.32-22. More information about this: http://forum.kodi.tv/showthread.php?t=76944		If you are running a recent Ubuntu lucid install, and your device refuses to resume from standby even while the correct wakeup devices are set in /proc/acpi/wakeup. It could be caused because of a bug in the current Ubuntu kernel. Kernel versions starting from 2.6.32-23 are affected by this bug. A possible solution is to downgrade your kernel to 2.6.32-22. More information about this: http://forum.kodi.tv/showthread.php?t=76944

	~~== Enable Wake on Other Devices ==~~
	~~[[Enable Wake-On-Device\|More information on this page.]]~~

	== Use an Xbox Remote Start-up Kit ==		== Use an Xbox Remote Start-up Kit ==

NedBot: web link corrections for xbmc.org -> kodi.tv; cosmetic changes

2015-05-13T01:16:00Z

web link corrections for xbmc.org -> kodi.tv; cosmetic changes

Wiz561: /* Add Custom Actions to PolicyKit */

2014-08-31T13:45:28Z

Add Custom Actions to PolicyKit

← Older revision		Revision as of 13:45, 31 August 2014
Line 9:		Line 9:
	Make sure the following packages are installed.		Make sure the following packages are installed.

	<source lang="bash">sudo apt-get install policykit-1 upower acpi-support</source>		<source lang="bash">sudo apt-get install policykit-1 upower acpi-support consolekit</source>

	Now run "pkaction" and verify that the following are present.		Now run "pkaction" and verify that the following are present.

>Sja1440 at 13:14, 1 May 2012

2012-05-01T13:14:12Z

← Older revision		Revision as of 13:14, 1 May 2012
Line 1:		Line 1:
	=Enabling Suspend / Wake on Ubuntu Linux=		=Enabling Suspend / Wake / Shutdown / Power off on Ubuntu Linux=
	First, test XBMC to see if it already suspends. You may not need any extra setup. If it does not suspend properly, one or more of the following techniques may be necessary. Go through them in order and stop once you have a working suspend and wake. Be certain to test it more than once, there is a bug that will express itself as not suspending after the first wake is successful.		First, test XBMC to see if it already suspends. You may not need any extra setup. If it does not suspend properly, one or more of the following techniques may be necessary. Go through them in order and stop once you have a working suspend and wake. Be certain to test it more than once, there is a bug that will express itself as not suspending after the first wake is successful.

>Sja1440 at 13:10, 1 May 2012

2012-05-01T13:10:53Z

← Older revision		Revision as of 13:10, 1 May 2012
Line 26:		Line 26:
	</pre>		</pre>

	~~NOTE~~: You may have to comment out the existing 20-xbmclive.pkla as well until this issue is resovled:		NOTES:

			(1) You may have to comment out the existing 20-xbmclive.pkla as well until this issue is resovled:
	[http://trac.xbmc.org/ticket/11581]		[http://trac.xbmc.org/ticket/11581]

			(2) With xbmc Eden on Ubuntu 12.04 it was necessary to change in the above "ResultInactive=no" to "ResultInactive=yes".

	[http://forum.xbmc.org/showpost.php?p=448088&postcount=54 Credit to '''kroete''']		[http://forum.xbmc.org/showpost.php?p=448088&postcount=54 Credit to '''kroete''']

Ned Scott at 11:06, 14 February 2012

2012-02-14T11:06:09Z

← Older revision		Revision as of 11:06, 14 February 2012
Line 117:		Line 117:
	<source lang="bash">chmod 755 /etc/pm/sleep.d/90_lirc</source>		<source lang="bash">chmod 755 /etc/pm/sleep.d/90_lirc</source>

	[[~~category~~:Linux]]		[[Category:Linux]]
			[[Category:How-to]]

Ned Scott: moved Ubuntu Suspend / Wake to HOW-TO:Suspend and wake in Ubuntu

2012-02-14T11:05:48Z

moved Ubuntu Suspend / Wake to HOW-TO:Suspend and wake in Ubuntu

← Older revision	Revision as of 11:05, 14 February 2012
(No difference)

← Older revision		Revision as of 01:16, 13 May 2015
Line 1:		Line 1:
	=Enabling Suspend / Wake / Shutdown / Power off on Ubuntu Linux=		=Enabling Suspend / Wake / Shutdown / Power off on Ubuntu Linux=
	First, test XBMC to see if it already suspends. You may not need any extra setup. If it does not suspend properly, one or more of the following techniques may be necessary. Go through them in order and stop once you have a working suspend and wake. Be certain to test it more than once, there is a bug that will express itself as not suspending after the first wake is successful.		First, test XBMC to see if it already suspends. You may not need any extra setup. If it does not suspend properly, one or more of the following techniques may be necessary. Go through them in order and stop once you have a working suspend and wake. Be certain to test it more than once, there is a bug that will express itself as not suspending after the first wake is successful.

	==Enable ACPI S1/S3 Suspend in your BIOS==		== Enable ACPI S1/S3 Suspend in your BIOS ==

	Make sure your ACPI S1/S3 is enabled in your BIOS. There are as many ways to do this as there are different BIOSes out there. Refer to your motherboard documentation for details.		Make sure your ACPI S1/S3 is enabled in your BIOS. There are as many ways to do this as there are different BIOSes out there. Refer to your motherboard documentation for details.

	==Add Custom Actions to PolicyKit==		== Add Custom Actions to PolicyKit ==
	Make sure the following packages are installed.		Make sure the following packages are installed.

Line 29:		Line 29:

	(1) You may have to comment out the existing 20-xbmclive.pkla as well until this issue is resovled:		(1) You may have to comment out the existing 20-xbmclive.pkla as well until this issue is resovled:
	[http://trac.~~xbmc~~.~~org~~/ticket/11581]		[http://trac.kodi.tv/ticket/11581]

	(2) With xbmc Eden on Ubuntu 12.04 it was necessary to change in the above "ResultInactive=no" to "ResultInactive=yes".		(2) With xbmc Eden on Ubuntu 12.04 it was necessary to change in the above "ResultInactive=no" to "ResultInactive=yes".

	[http://forum.~~xbmc~~.~~org~~/showpost.php?p=448088&postcount=54 Credit to '''kroete''']		[http://forum.kodi.tv/showpost.php?p=448088&postcount=54 Credit to '''kroete''']

	==Disable Usbcore Autosuspend==		== Disable Usbcore Autosuspend ==

	Add a boot option to grub to disable the usbcore autosuspend. This bug exhibits itself as immediately waking after suspension.		Add a boot option to grub to disable the usbcore autosuspend. This bug exhibits itself as immediately waking after suspension.

	Edit '''/etc/default/grub''' and add '''usbcore.autosuspend=-1''' to '''GRUB_CMDLINE_LINUX_DEFAULT'''. Example:		Edit '''/etc/default/grub''' and add '''usbcore.autosuspend=-1''' to '''GRUB_CMDLINE_LINUX_DEFAULT'''. Example:

	<pre>GRUB_CMDLINE_LINUX_DEFAULT="quiet splash xbmc=autostart,noredir usbcore.autosuspend=-1"</pre>		<pre>GRUB_CMDLINE_LINUX_DEFAULT="quiet splash xbmc=autostart,noredir usbcore.autosuspend=-1"</pre>
Line 47:		Line 47:
	<source lang="bash">sudo update-grub</source>		<source lang="bash">sudo update-grub</source>

	=Remote Suspend / Wake=		= Remote Suspend / Wake =
	Using an IR remote to suspend and wake your XBMC HTPC is much easier than getting off the couch.		Using an IR remote to suspend and wake your XBMC HTPC is much easier than getting off the couch.

	* [http://www.loggn.de/linux-xbmc-aus-bereitschaftsmodus-per-mce-fernbedienung-aufwecken/ HowTo for Ubuntu 12.04 (Kernel 3.2) - XBMC - Wakeup with MCE remote control]		* [http://www.loggn.de/linux-xbmc-aus-bereitschaftsmodus-per-mce-fernbedienung-aufwecken/ HowTo for Ubuntu 12.04 (Kernel 3.2) - XBMC - Wakeup with MCE remote control]
	* [http://www.loggn.de/linux-probleme-nach-dem-bereitschaftsmodus-fernbedienung-netzwerk-und-sound-funktionieren-nicht/ HowTo for Ubuntu 12.04 (Kernel 3.2) - XBMC - Problems after resume from sleep]		* [http://www.loggn.de/linux-probleme-nach-dem-bereitschaftsmodus-fernbedienung-netzwerk-und-sound-funktionieren-nicht/ HowTo for Ubuntu 12.04 (Kernel 3.2) - XBMC - Problems after resume from sleep]

	==Enable Wake on USB Activity==		== Enable Wake on USB Activity ==
	If your IR receiver is plugged into a USB port. You can have Linux recognize IR traffic on the USB bus as a signal to wake XBMC. This method can have the drawback of waking XBMC unnecessarily because you're using the remote for other devices.		If your IR receiver is plugged into a USB port. You can have Linux recognize IR traffic on the USB bus as a signal to wake XBMC. This method can have the drawback of waking XBMC unnecessarily because you're using the remote for other devices.

	First find which USB bus your IR receiver is connected to. The command '''lsusb''' can be somewhat useful for determining this, or you can just start at 0 and work your way up until you find it. The command to wake upon USB traffic is:		First find which USB bus your IR receiver is connected to. The command '''lsusb''' can be somewhat useful for determining this, or you can just start at 0 and work your way up until you find it. The command to wake upon USB traffic is:

	<source lang="bash">sudo sh -c 'echo "USB0" > /proc/acpi/wakeup'</source>		<source lang="bash">sudo sh -c 'echo "USB0" > /proc/acpi/wakeup'</source>

	Replace USB0 with USB1 and so on until you find it. Once you do, add it to your startup by editing '''/etc/rc.local''' and putting the following line before '''exit 0'''.		Replace USB0 with USB1 and so on until you find it. Once you do, add it to your startup by editing '''/etc/rc.local''' and putting the following line before '''exit 0'''.

	<source lang="bash">echo "USB0" > /proc/acpi/wakeup</source>		<source lang="bash">echo "USB0" > /proc/acpi/wakeup</source>
Line 80:		Line 80:
	<source lang="bash">dmesg \|grep mceusb</source>		<source lang="bash">dmesg \|grep mceusb</source>

	==Ubuntu Kernel bug==		== Ubuntu Kernel bug ==
	If you are running a recent Ubuntu lucid install, and your device refuses to resume from standby even while the correct wakeup devices are set in /proc/acpi/wakeup. It could be caused because of a bug in the current Ubuntu kernel. Kernel versions starting from 2.6.32-23 are affected by this bug. A possible solution is to downgrade your kernel to 2.6.32-22. More information about this: http://forum.~~xbmc~~.~~org~~/showthread.php?t=76944		If you are running a recent Ubuntu lucid install, and your device refuses to resume from standby even while the correct wakeup devices are set in /proc/acpi/wakeup. It could be caused because of a bug in the current Ubuntu kernel. Kernel versions starting from 2.6.32-23 are affected by this bug. A possible solution is to downgrade your kernel to 2.6.32-22. More information about this: http://forum.kodi.tv/showthread.php?t=76944

	==Enable Wake on Other Devices==		== Enable Wake on Other Devices ==
	[[~~Enable_Wake~~-On-Device\|More information on this page.]]		[[Enable Wake-On-Device\|More information on this page.]]

	==Use an Xbox Remote Start-up Kit==		== Use an Xbox Remote Start-up Kit ==
	There are a few kits out there that can be soldered into a classic Xbox to enable power-on by pressing a set remote button on the Xbox DVD kit. These can be adapted to a PC, and carries the advantage of working regardless of the state of the system in the same way a power button does.		There are a few kits out there that can be soldered into a classic Xbox to enable power-on by pressing a set remote button on the Xbox DVD kit. These can be adapted to a PC, and carries the advantage of working regardless of the state of the system in the same way a power button does.

	[http://forum.~~xbmc~~.~~org~~/showthread.php?t=64328 One example of how to install a XERC 2 XE is located here.]		[http://forum.kodi.tv/showthread.php?t=64328 One example of how to install a XERC 2 XE is located here.]

	==Fix the Lirc Device Increment Bug==		== Fix the Lirc Device Increment Bug ==
	NOTE: You have to enable control of XBMC via HTTP for this to work.		NOTE: You have to enable control of XBMC via HTTP for this to work.
	If your IR remote does not work after waking from sleep, you most likely have this bug. The IR software for Linux, Lirc, will create a new device '''/dev/lirc1''' because it presumes the old device '''/dev/lirc0''' is in use by another process. This confuses XBMC and you end up with a non-working remote. The solution is to shutdown Lirc before suspension and then start it back up after wake. This is done by creating a script at '''/etc/pm/sleep.d/90_lirc''' :		If your IR remote does not work after waking from sleep, you most likely have this bug. The IR software for Linux, Lirc, will create a new device '''/dev/lirc1''' because it presumes the old device '''/dev/lirc0''' is in use by another process. This confuses XBMC and you end up with a non-working remote. The solution is to shutdown Lirc before suspension and then start it back up after wake. This is done by creating a script at '''/etc/pm/sleep.d/90_lirc''' :

	<source lang="bash"># Script to disable lirc before suspend and restart after wake.		<source lang="bash"># Script to disable lirc before suspend and restart after wake.