Kodi Community Forum

I had similar problems and manage to fix it (eventually...). I will explain how i did this and hope it will help you fix your problem.

To be sure you are using the correct path in rc.local run then command 'lsusb' and write down the 2nd ID number of your device.

For example, if the output of lsusb is:

Bus 001 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 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 002: ID 413c:2003 Dell Computer Corp. Keyboard
Bus 004 Device 002: ID 1784:0008 TopSeed Technology Corp. eHome Infrared Transceiver
Bus 004 Device 003: ID 046d:c518 Logitech, Inc. MX610 Laser Cordless Mouse

You write down the 2nd ID number in the line of your transceiver. 0008 in this case (I made the number bold).

Now use that number in the next command:


The result looks something like this:


Of course your path can be different from the above example. Write this path down and use the cat command to see if wakeup is indeed enabled.

Don't forget to add this path to your rc.local file. In my example the result is "4-2", so just to be sure i added USB4 too. If your result is "3-2" then add USB3 etc. Also add USB1. I read somewhere that this helps "waking up the USB bus" or something. Don't know exactly how or why

So using the above examples, i would add the following lines to rc.local:


Also make sure rc.local is executable.


Now reboot and try it out. Good luck!

As far as the echo USB1 > /proc/acpi/wakeup I've found that it is more or less a guess and check. In my case the one that needs to be enabled is US31. No idea how to figure it out without trying them so I normally turn them all on and go through and turn them off one at a time until it breaks.

Devaron,

Thanks, that did it. Looks like I finally have XBMC on this machine working perfectly. Now to transition my other 2 HTPCs to XBMC Ubuntu instead of Windows Vista!

(2012-04-19, 20:10)Devaron Wrote: [ -> ]I had similar problems and manage to fix it (eventually...). I will explain how i did this and hope it will help you fix your problem.

To be sure you are using the correct path in rc.local run then command 'lsusb' and write down the 2nd ID number of your device.

For example, if the output of lsusb is:

Bus 001 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 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 002: ID 413c:2003 Dell Computer Corp. Keyboard
Bus 004 Device 002: ID 1784:0008 TopSeed Technology Corp. eHome Infrared Transceiver
Bus 004 Device 003: ID 046d:c518 Logitech, Inc. MX610 Laser Cordless Mouse

You write down the 2nd ID number in the line of your transceiver. 0008 in this case (I made the number bold).

Now use that number in the next command:

Code:

grep 0008 /sys/bus/usb/devices/*/idProduct

The result looks something like this:

Code:

/sys/bus/usb/devices/4-2/idProduct:0008

Of course your path can be different from the above example. Write this path down and use the cat command to see if wakeup is indeed enabled.

Don't forget to add this path to your rc.local file. In my example the result is "4-2", so just to be sure i added USB4 too. If your result is "3-2" then add USB3 etc. Also add USB1. I read somewhere that this helps "waking up the USB bus" or something. Don't know exactly how or why

So using the above examples, i would add the following lines to rc.local:

Code:

echo USB1 > /proc/acpi/wakeup
echo USB4 > /proc/acpi/wakeup
echo enabled > /sys/bus/usb/devices/4-2/power/wakeup

Also make sure rc.local is executable.

Code:

sudo chmod +x /etc/rc.local

Now reboot and try it out. Good luck!

I tried your suggestion and unfortunately it still isn't waking up for me, so I am not sure what other step I am missing. I actually ordered two flirc IR receivers earlier this week from the story on the xbmc home page and the mutliple reviews littered on the xbmc forum post saying how wonderful the device is. They are about the same price as a MCE remote and hopefully half the hassle, plus money goes to a cancer charity with the purchase.

Looks like I spoke to soon. Although the fix did allow me to wake from suspend with the remote if I manually forced the computer into sleep, XBMC does not fall to sleep automatically. Instead, it just starts to go sleep then immediately wakes itself.

The other issue is that placing "echo enabled > /sys/bus/usb/devices/4-2/power/wakeup" into rc.local does not update the file. I think the rc.local file is run before the /sys/bus/usb/devices/4-2/power/wakeup is created by the system. Not sure how I delay the rc.local file from executing until after all the system startup processes are completed.

Looks like adding a delay into rc.local fixed the sleep problem. Now everything seems to be running fine.

If anyone else runs into this issue, just add the line:


into rc.local where the "20" stands for 20 seconds.

Hello,

I have a similar problem; I can wakeup from my IR, but if the system goes to suspend again, the second wakeup fails. I reboot, suspend, wakeup from IR works fine again, but only one time.

Any idea?

Thanks in advance.

(2012-04-20, 20:24)KiZD Wrote: [ -> ]Hello,

I have a similar problem; I can wakeup from my IR, but if the system goes to suspend again, the second wakeup fails. I reboot, suspend, wakeup from IR works fine again, but only one time.

Any idea?

Thanks in advance.

I have the exact same issue as KiZD I'm running a Zotac HD-id11. Any ideas?

Hi all,

I know this thread is a little old but I'm running in to the same problem, I'm using xbmcbuntu (with a MSI motherboard (P67A-G45), ACPI resume events are handled by the OS according to the BIOS) when I run lsusb I get this


so my controller is on 1-3, but if I run this ..

I get this out put


so I put both of these in my rc.local


made sure wake on USB event is enabled in my bios but it still doesnt wake up (it will suspend) from the remote

if I look at

cat /proc/acpi/wakeup I don't see any USB there ??


any help would be great ... once I get this working I was hoping I could send a serial string out of one of my comm ports to turn the tv on and off but I wanted to get this working first and deal with that after wards ...

anyone have any ideas ??

Thanks again

* a little side note ... if I do suspend from the remote and push the power button the weather widget is wrong ... (says something like 166 degrees out, if I refresh it works again but I would like to get that working as well)

*EDIT: I have been messing around ... not exactly sure what I'm doing but google helps a little, I have updated the bios, and enabled wakeup on the EUSB and USBE and it worked ... now on to the weather and serial stuff

Take a look at this thread in the ubuntuforums and see if any of the tips help: http://ubuntuforums.org/showthread.php?t=1968487

Here's a fix for the weather add-on bug (where the reported temperature spikes after resuming from suspend): http://forum.xbmc.org/showthread.php?tid=132942

@artafael Thanks

I got the TV to power on and off with the S3 events by plugging a RS232 cable in to the TV and the PC then on my tv (a runco) sending a [SAB0000 turns it off and a [SAB0001 turns it back on so I editted

/etc/pm/sleep.d/99lirc-resume

added a echo [SAB0000 > /dev/ttyUSB0 and it turns off