Kodi Community Forum - Power-On from MCE Remote not working

i would like to enable power-on from the mce remote to my system.

i stumbled into this issue when troubleshooting another issue following an update to the dharma beta 3

reading through the thread "No resume form standby with vista remote after 2.6.32-23 #37 Kernel version", it seemed that i wasnt running an appropriate kernel level.
infact, i was still running Ubuntu Karmic (9.10). so first step was to upgrade to Ubuntu Lucid. 10.04.1 was available when i attempted this through Distribution Manager. This completed successfully, and required subsequent updates to nVidia drivers, ALSA and Lirc to newer versions running on Lucid.

POwer-off from remote works within XBMC, as it did before any upgrade work.

i followed the following threads for info as to how to set up wake-on-usb:
Ubuntu Suspend / Wake
Enable Wake-On-Device

However, i am unable to power-on the device still, even though my kernel is at an appropriate level.

my config is as follows:

Motherboard: ASUS P5N7A-VM. XBMC connected to HDTV via HDMI. Recieve audio via HDMI too. MCE Remote plugged into rear USB port. Ubuntu Lucid (10.04.1)

lsusb
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 002: ID 0471:0815 Philips eHome Infrared Receiver
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 002: ID 15c2:0038 SoundGraph Inc.
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 002: ID 2040:8400 Hauppauge
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

lspci | grep US
00:04.0 USB Controller: nVidia Corporation MCP79 OHCI USB 1.1 Controller (rev b1)
00:04.1 USB Controller: nVidia Corporation MCP79 EHCI USB 2.0 Controller (rev b1)
00:06.0 USB Controller: nVidia Corporation MCP79 OHCI USB 1.1 Controller (rev b1)
00:06.1 USB Controller: nVidia Corporation MCP79 EHCI USB 2.0 Controller (rev b1)
01:05.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 62)
01:05.2 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 65)

cat /proc/acpi/wakeup
Device S-state Status Sysfs node
UAR1 S4 disabled pnp:00:0b
SMB0 S4 disabled pci:0000:00:03.2
USB0 S4 disabled pci:0000:00:04.0
USB2 S4 disabled pci:0000:00:04.1
US15 S4 enabled pci:0000:00:06.0
US12 S4 disabled pci:0000:00:06.1
NMAC S5 enabled pci:0000:00:0a.0
PBB0 S4 disabled pci:0000:00:09.0
HDAC S4 disabled pci:0000:00:08.0
XVR0 S4 disabled pci:0000:00:0c.0
XVR1 S4 disabled
P0P5 S4 disabled
P0P6 S4 disabled pci:0000:00:15.0
P0P7 S4 disabled pci:0000:00:16.0
P0P8 S4 disabled
P0P9 S4 disabled

i am not sure why the USB devices are reporting as S-state "S4". maybe this is causing the issue?
i have written the "echo USB0 > /proc/acpi/wakeup" into /etc/rc.local and confirm this seems to work as expected. i have tried all 4 listed USB devices to make sure i have the correct port specified.

uname -r -v
2.6.32-25-generic-pae #45-Ubuntu SMP Sat Oct 16 21:01:33 UTC 2010

XBMC
team-xbmc-svn repository running Dharma Beta 3

Lirc
0.8.6-0ubuntu4.1

the "No resume form standby with vista remote after 2.6.32-23 #37 Kernel version" thread mentions to initially downgrade to 2.6.32-22 to restore functionality. later in the thread, people indicate that 2.6.32-25-44 onwards work too. could this be related?

can anyone confirm this motherboard is compatible?

can anyone help?

i hope so...

jingo_man

yeah dude its the kernel, pretty sure anyway

except i think the fix is in a newer kernel so you don't have to downgrade anymore.

upgrade to a new kernel and see how that goes.

mick.

It should work with that kernel,

both of your USB seemed to still be disabled from what you posted here. if you do an echo USB0 from a command line and then issue a sudo pm-suspend does it work to resume. If so there is something not right in your rc.local.

rgds,

Dave

thanks for the replies guys

xbmcn00b - i was under the impression that by upgrading to Ubuntu Lucid and fully updating everything, as of last week, that the kernel i currently have, should have the fix contained... i think rodercot is insinuating this too.

Quote:uname -r -v
2.6.32-25-generic-pae #45-Ubuntu SMP Sat Oct 16 21:01:33 UTC 2010

rodercot - the current config you are seeing from "cat /proc/acpi/wakeup" is US15, however, i have round-robin'd through all the USB devices in the rc.local file and rebooted each time but unable to get it to power on. it was only after the last attempt, that i resorted to posting here in the forums.

can you please be more precise about what commands you are suggesting please? in addition, what would the difference be between issuing a "sudo pm-suspend" command to what XBMC does when i shut down from within the application, using my remote?or is it just a manual instruction to verify what is going on in my system?

i will try when i return home...

cheers again Big Grin

I am not sure what xbmc uses anymore I have always used pm-suspend as a test and that is where my suspend and wake up scripts are found /etc/pm/sleep.d - but that is another topic. Make sure before you do any of this you are at root.

sudo su

Just issue the echo USB0 > /proc/acpi/wakeup from the command line.

then check it is not disabled any more by cat /proc/acpi/wakeup

you know here is a link to a how-to I did a while back. check that out and follow it, skip the autoresume part at this point. It tells you how to do it and test pm-suspend as well if none of that work re-locate your rcvr to another usb port on the machine. I always find that I end up using one of the ports under the lan port.

http://wiki.xbmc.org/?title=HOW-TO_Insta...ermissions

regards,

Dave

ok, sorry for dragging up an old thread... but i am back to trying to figure out how to power on from my microsoft usb remote!

so now, i am on an even more up-to-date version of the kernel:

Quote:$ uname -r -v
2.6.32-30-generic-pae #59-Ubuntu SMP Tue Mar 1 23:01:33 UTC 2011

i once again followed rodercot's guide (which is all i have been doing in the past too)

still nothing! grrr... i have also applied various echo xxxx > /proc/acpi/wakeup commands in the /etc/rc.local file so its enabled at bootup. i have juggled around the usb reciever into different usb ports.

info about my usb devices:

Quote:$ lsusb
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 002: ID 045e:0745 Microsoft Corp.
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 003: ID 15c2:0038 SoundGraph Inc.
Bus 004 Device 002: ID 0471:0815 Philips eHome Infrared Receiver
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 002: ID 2040:8400 Hauppauge
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

the current content of the /proc/acpi/wakeup file is as follows:

Quote:$ cat /proc/acpi/wakeup
Device S-state Status Sysfs node
UAR1 S4 disabled pnp:00:0b
SMB0 S4 disabled pci:0000:00:03.2
USB0 S4 disabled pci:0000:00:04.0
USB2 S4 enabled pci:0000:00:04.1
US15 S4 disabled pci:0000:00:06.0
US12 S4 disabled pci:0000:00:06.1
NMAC S5 enabled pci:0000:00:0a.0
PBB0 S4 disabled pci:0000:00:09.0
HDAC S4 disabled pci:0000:00:08.0
XVR0 S4 disabled pci:0000:00:0c.0
XVR1 S4 disabled
P0P5 S4 disabled
P0P6 S4 disabled pci:0000:00:15.0
P0P7 S4 disabled pci:0000:00:16.0
P0P8 S4 disabled
P0P9 S4 disabled

from this output, which USB device should i use?
is the list of devices in the /proc/acpi/wakeup the full list of ALL available usb devices? or only the wakeup-compatible devices?
are there some models of this microsoft usb remote that arent capable?
why are all devices only listed as "S4" in the wakeup file? isnt that "suspend to disk/hibernate" - arent we setting this to suspend (S3)..? if so, can i edit these values?

here's hoping someone still watches this thread and gives a damn! haha

cheers, jingo_man

For me the solution was;

Quote:In Ubuntu 10.10 Maverick, Kernel 2.6.35-* You Should enable sysfs based wakeup on Remote Control device,

on my system it is done by

Code:
echo enabled > /sys/bus/usb/devices/2-4/power/wakeup

You can find which is Your device by grepping dmesg, for me it is mceusb

Code:
dmesg |grep mceusb

http://wiki.xbmc.org/index.php?title=Ubu...end_/_Wake

I added the echo line to my rc.local file...

i got bored, so decided to enable each device listed in turn, run pm-hibernate & -suspends, and then attempt power-on via the remote. lets call it last resort...

however, by luck not design, the top item, was actually the device i was looking for:

Quote:Device S-state Status Sysfs node
UAR1 S4 disabled pnp:00:0b

it turned out the usb ports i was enabling are the front-ports on my antec case, which has the bluetooth keyboard & mouse plugged in, so enabled these aswell, so now able to wake up from few devices as well as WoL.

i had googled other places about the /proc/acpi/wakeup file and found others using various "/sys/..." paths instead. i wouldnt know where this particular device would be in this structure either, but as i stumbled across the correct device(s) i think i will stick with what i have. but thanks for the pointers.