Archive:HOW-TO:Enable Wake-On-Device for Ubuntu - Revision history

Ned Scott: because some people don't understand what "outdated" means

2015-04-04T07:02:45Z

because some people don't understand what "outdated" means

Ned Scott: Ned Scott moved page HOW-TO:Enable Wake-On-Device for Ubuntu to Archive:HOW-TO:Enable Wake-On-Device for Ubuntu

2014-03-19T09:55:43Z

Ned Scott moved page HOW-TO:Enable Wake-On-Device for Ubuntu to Archive:HOW-TO:Enable Wake-On-Device for Ubuntu

← Older revision	Revision as of 09:55, 19 March 2014
(No difference)

Ned Scott at 09:55, 19 March 2014

2014-03-19T09:55:21Z

← Older revision		Revision as of 09:55, 19 March 2014
Line 1:		Line 1:
			{{outdated}}

	This Article discusses enabling wake-up from your remote device under Ubuntu. In order to perform the following tasks you must be [[root]].		This Article discusses enabling wake-up from your remote device under Ubuntu. In order to perform the following tasks you must be [[root]].

Line 167:		Line 169:

	Your Wake-On-Device setup is now complete.		Your Wake-On-Device setup is now complete.

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

>NedBot: moved How-to-TEMP:Enable Wake-On-Device for Ubuntu to HOW-TO:Enable Wake-On-Device for Ubuntu: Bot: Moved page

2011-10-03T15:05:30Z

moved How-to-TEMP:Enable Wake-On-Device for Ubuntu to HOW-TO:Enable Wake-On-Device for Ubuntu: Bot: Moved page

← Older revision	Revision as of 15:05, 3 October 2011
(No difference)

>NedBot: moved How-to:Enable Wake-On-Device for Ubuntu to How-to-TEMP:Enable Wake-On-Device for Ubuntu: Bot: Moved page

2011-10-03T14:57:48Z

moved How-to:Enable Wake-On-Device for Ubuntu to How-to-TEMP:Enable Wake-On-Device for Ubuntu: Bot: Moved page

← Older revision	Revision as of 14:57, 3 October 2011
(No difference)

Ned Scott: moved Enable Wake-On-Device to How-to:Enable Wake-On-Device for Ubuntu

2011-09-25T21:25:33Z

moved Enable Wake-On-Device to How-to:Enable Wake-On-Device for Ubuntu

← Older revision	Revision as of 21:25, 25 September 2011
(No difference)

Ned Scott at 21:25, 25 September 2011

2011-09-25T21:25:11Z

← Older revision		Revision as of 21:25, 25 September 2011
Line 2:		Line 2:

	Note: This article contains examples of what you should see. Examples, marked with eg. will be different then your computer. Please follow the instructions and do not copy and paste examples or undesired results may occour.		Note: This article contains examples of what you should see. Examples, marked with eg. will be different then your computer. Please follow the instructions and do not copy and paste examples or undesired results may occour.



	== Identification of resume devices ==		== Identification of resume devices ==
Line 64:		Line 62:
	00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller		00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
	00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control		00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control



	== Enabling wakeup status for devices ==		== Enabling wakeup status for devices ==
Line 171:		Line 167:

	Your Wake-On-Device setup is now complete.		Your Wake-On-Device setup is now complete.

			[[Category:How-to]]

>NedBot: Robot: Cosmetic changes

2011-09-07T16:09:18Z

Robot: Cosmetic changes

← Older revision		Revision as of 16:09, 7 September 2011
Line 1:		Line 1:
	This Article discusses enabling wake-up from your remote device under Ubuntu. In order to perform the following tasks you must be [[root]].		This Article discusses enabling wake-up from your remote device under Ubuntu. In order to perform the following tasks you must be [[root]].

	Note: This article contains examples of what you should see. Examples, marked with eg. will be different then your computer. Please follow the instructions and do not copy and paste examples or undesired results may occour.		Note: This article contains examples of what you should see. Examples, marked with eg. will be different then your computer. Please follow the instructions and do not copy and paste examples or undesired results may occour.



	== Identification of resume devices ==		== Identification of resume devices ==
	This section discusses identification of the resume devices. You must be root for all following steps.		This section discusses identification of the resume devices. You must be root for all following steps.

	* Become root		* Become root
Line 40:		Line 40:
	lspci		lspci

	You will see a list of PCI devices. The first coloumn in lspci will match the Sysfs node coloumn in /proc/acpi/wakeup		You will see a list of PCI devices. The first coloumn in lspci will match the Sysfs node coloumn in /proc/acpi/wakeup

	EG.		EG.
Line 98:		Line 98:


	You should now see that your devices are enabled. Test your resume function at this time and verify proper operation.		You should now see that your devices are enabled. Test your resume function at this time and verify proper operation.

	=== Troubleshooting auto-resume ===		=== Troubleshooting auto-resume ===
Line 110:		Line 110:
	If that doesn't fix the auto-resume issue (meaning your setup still auto-resumes almost immediately after going to sleep), there may be an ACPI conflict that we can fix in GRUB.		If that doesn't fix the auto-resume issue (meaning your setup still auto-resumes almost immediately after going to sleep), there may be an ACPI conflict that we can fix in GRUB.

	There is also a conflict on these ion boards between nvidia SMbus and acpi and we want to fix that so we will do that now as well. This is only a workaround for now, though it may be fixed in later kernels. You can find the bug reports on Google and track them to know when you'll want to remove this line. Here is a link to one https://bugs.launchpad.net/ubuntu/+source/linux/+bug/440780 of the active tickets.		There is also a conflict on these ion boards between nvidia SMbus and acpi and we want to fix that so we will do that now as well. This is only a workaround for now, though it may be fixed in later kernels. You can find the bug reports on Google and track them to know when you'll want to remove this line. Here is a link to one https://bugs.launchpad.net/ubuntu/+source/linux/+bug/440780 of the active tickets.

	We need to edit our grub boot line in order to accomplish this fix. Since 9.10 and newer uses GRUB2, things are a little different so first lets get out of root by typing		We need to edit our grub boot line in order to accomplish this fix. Since 9.10 and newer uses GRUB2, things are a little different so first lets get out of root by typing
Line 148:		Line 148:
	More information about this: http://forum.xbmc.org/showthread.php?t=76944		More information about this: http://forum.xbmc.org/showthread.php?t=76944

	== Committing to rc.local ==		== Committing to rc.local ==

	* Edit /etc/rc.local and add the echo commands required to enable authorized devices		* Edit /etc/rc.local and add the echo commands required to enable authorized devices

>Creanium: Adding additional auto-resume fixes.

2010-12-24T06:57:06Z

Adding additional auto-resume fixes.

@@ Line 107: / Line 107: @@
 enabling USB2 as an enabled wakeup device causes the computer to resume immediately..
   root@XBMCLive:~# echo USB2 > /proc/acpi/wakeup
 If 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

>Martijn02: Added information about a bug in the latest ubuntu kernels that prevents USB devices from getting the power they need to auto resume.

2010-08-09T09:15:21Z

Added information about a bug in the latest ubuntu kernels that prevents USB devices from getting the power they need to auto resume.

← Older revision		Revision as of 09:15, 9 August 2010
Line 107:		Line 107:
	enabling USB2 as an enabled wakeup device causes the computer to resume immediately..		enabling USB2 as an enabled wakeup device causes the computer to resume immediately..
	root@XBMCLive:~# echo USB2 > /proc/acpi/wakeup		root@XBMCLive:~# echo USB2 > /proc/acpi/wakeup

			If 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

	== Committing to rc.local ==		== Committing to rc.local ==