Login at Kodi Home

anthony.selby · 2013-12-09, 01:50

Where did you get

EHC1 and EHC2

* by the way Thanks for the help

But that didn't fix it ... (I also just ran sudo apt-get upgrade and that didn't help either)

Bagger · 2013-12-09, 11:30

Enhanced Host Controller , usb 2 controller.
Just from reading around, people with the address, point something ( 1-1.6 in your case ) seemed to need ehc wakeup in their rc.local. Was just an idea.

With me, from a fresh install of XBMCBuntu, which is Ubuntu 12.10 and XBMC frodo 12.2
I only need 2 lines added to the rc.local and I could sleep and wake from the power button on the remote. A keyspan MCE RC6 compatible remote.

anthony.selby · 2013-12-12, 02:01

Anyone else have any ideas ?

vbat99 · 2013-12-12, 02:59

Only suggestion I have is remove the spaces between
usbcore.autosuspend and = sign, and between = sign and -1. Rebuild Grub and give a try
ie:

Code:
usbcore.autosuspend=-1

anthony.selby · 2013-12-13, 01:02

Thanks ... but that didn't do it

User 172595 · (This post was last modified: 2014-05-01, 17:22 by User 172595.)

Hi,
I also can't wake up from sleep using my remote + FLIRC receiver. Like anthony.selby, I made sure that I have everything set, as mentioned in this thread. Here's a summary (I'll try to emphasize what's different in my case):

in /proc/acpi/wakeup, I have all my USB ports set as *enabled (even though they're not called "USB" but something else) I didn't even need to set this - I have a USB keyboard wakeup option in my BIOS, and enabled that

Code:
root@HTPC:~# cat /proc/acpi/wakeup Device S-state Status Sysfs node PB2 S4 *disabled PB3 S4 *disabled PB4 S4 *disabled PB5 S4 *disabled PB6 S4 *disabled PB7 S4 *disabled SBAZ S4 *disabled pci:0000:00:14.2 UAR1 S4 *disabled pnp:00:0b P0PC S4 *disabled pci:0000:00:14.4 OHC1 S4 *enabled pci:0000:00:12.0 EHC1 S4 *enabled pci:0000:00:12.2 OHC2 S4 *enabled pci:0000:00:13.0 EHC2 S4 *enabled pci:0000:00:13.2 OHC3 S4 *disabled EHC3 S4 *disabled OHC4 S4 *enabled pci:0000:00:14.5 XHC0 S4 *enabled pci:0000:00:10.0 XHC1 S4 *enabled pci:0000:00:10.1 PE20 S4 *disabled pci:0000:00:15.0 PE21 S4 *disabled pci:0000:00:15.1 PE22 S4 *disabled PE23 S4 *disabled
note that my waking with a keypress from a wired USB keyboard works. Just waking using my FLIRC receiver (which is supposed to translate IR signals to key presses) doesn't. Also, note, that there isn't a problem with configuration of the FLIRC receiver - when I am in XBMC (or even in the Grub menu selection), my remote works perfectly
My receiver idVendor is 20a0 and idProduct is 0001 according to lsusb:

Code:
root@HTPC:~# lsusb Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 004: ID 045e:00dd Microsoft Corp. Comfort Curve Keyboard 2000 V1.0 Bus 003 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 003 Device 002: ID 20a0:0001 Clay Logic Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 009 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 008 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 007 Device 002: ID 1058:1042 Western Digital Technologies, Inc. Bus 007 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 006 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Interestingly, though, running:

Code:
grep 20a0 /sys/bus/usb/devices/*/idProduct
returns nothing! (Not sure, if this may have something to do with the cause of the problem. But from lsusb, I know that the receiver is on Bus 003 Device 002, and I was able to locate it manually it's in /3-1/. Just for confirmation:

Code:
root@HTPC:~# cat /sys/bus/usb/devices/3-1/idVendor 20a0 root@HTPC:~# cat /sys/bus/usb/devices/3-1/idProduct 0001
of course, power/wakeup is enabled for this device:

Code:
root@HTPC:~# cat /sys/bus/usb/devices/3-1/power/wakeup enabled
I also found out that there are also other directories similar to /3-1/. They are:

Code:
root@HTPC:~# ls -l /sys/bus/usb/devices/3-1* lrwxrwxrwx 1 root root 0 May 1 15:38 /sys/bus/usb/devices/3-1 -> ../../../devices/pci0000:00/0000:00:12.0/usb3/3-1 lrwxrwxrwx 1 root root 0 May 1 15:38 /sys/bus/usb/devices/3-1:1.0 -> ../../../devices/pci0000:00/0000:00:12.0/usb3/3-1/3-1:1.0 lrwxrwxrwx 1 root root 0 May 1 15:38 /sys/bus/usb/devices/3-1:1.1 -> ../../../devices/pci0000:00/0000:00:12.0/usb3/3-1/3-1:1.1

However, the other two folders (3-1:1.0 and 3-1:1.1) don't have idVendor nor idProduct files inside them. They both have a /power/ folder inside, but it doesn't contain wakeup. For example:

Code:
root@HTPC:/sys/bus/usb/devices/3-1:1.0/power# ls async runtime_active_kids runtime_enabled runtime_status runtime_usage

I have no idea what 3-1:1.0 and 3-1:1.1 are. But I'm assuming (maybe wrongly) that just 3-1 is the one I should be concerned with.
Since the devices in /proc/acpi/wakeup are set to *Enabled properly, and /sys/bus/usb/devices/3-1/power/wakeup is also set to enabled properly, I didn't run anything else to make those changes permanent. (They are permanent, I double-checked by rebooting.)
The only other thing is modified Grub: those 2 lines in my /etc/default/grub are:

Code:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash usbcore.autosuspend=-1" GRUB_CMDLINE_LINUX=""
UPDATE: and I also added this:

Code:
root@HTPC:~# cat /etc/udev/rules.d/90-mcewakeup.rules SUBSYSTEM=="usb", ATTRS{idVendor}=="20a0", ATTRS{idProduct}=="0001" RUN+="/bin/sh -c 'echo enabled > /sys$env{DEVPATH}/../power/wakeup'"

And I'm still helpless :-( Any help greatly appreciated!

UPDATE: And now I just tried another thing - I noticed that in my BIOS (Asrock motherboard) there are several options for wakeup. One is USB keyboard/remote - that's the one I had initially enabled, and there's also USB mouse wake up. That was previously disabled, now I enabled it. Didn't help. Interestingly though:

Waking by pressing a key on my wired keyboard works fine
Waking by pressing a key on my remote (for which the FLIRC receiver is configured) doesn't :-( this is the problem I'm trying to solve
Waking by pressing clicking with my USB wireless mouse also doesn't work - even though I set that option in the BIOS

User 172595 · (This post was last modified: 2014-05-01, 18:13 by User 172595.)

OK, for all FLIRC users, try this: https://flirc.zendesk.com/hc/en-us/artic...r-computer After setting this up, I was able to wake the system from sleep using my remote. Hooray Smile

So apparently, there wasn't anything wrong with the XBMCbuntu configuration that I described above.

Now only to configure some remote macros in such a way that I can use the same button for both wakeup and sleep. But that's a lesser issue.

vbat99 · 2014-05-01, 20:13

Glad you got it sorted as have no experience with the flirc device.