10 replies to this topic

[JJFLASH]

Hello,

I am beaten and in need of some help.

Problem:

I can't wake my HTPC system from a suspended state using the IR remote. The computer will resume nicely if I press the power button on the computer, ie suspend is working. Note that the IR LED flashes on remote key-presses when suspended and I enter the suspend state using XBMC.

Background:
System MythTV frontend and XBMC Linux HTPC
System has been working well for years with IR remote suspending and resuming perfectly. I can't recall what version of Mythbuntu I was on maybe 9 but most likely 10 MythTV was only V0.23xx and XBMC Dhrama.

Recently XBMC started to freeze randomly during playback, I started to tinker .... and then it was time for a clean install. What a perfect time as Christmas was upon us.

Mythbuntu 11.10 and XBMC 11.0 Beta1 installed with next to no issues which was refreshing. The remote actually worked without any tinkering which was a big relief.

So Far:
I have put a bit of time into it but without any break through so I'll regurgitate my current relevant config in the hope that I can get some suggestions on how to lick this issue.

3.0.0-14-generic #23-Ubuntu

I've turned everything I can to "enabled" in the acpi list below, it doesn't directly state USB4 and I can't seem to turn PEX2,3,4,5 to enabled ( I'm surprised my computer doesn't start by me just sneezing in the room)

~$ cat /proc/acpi/wakeup
Device	S-state	  Status   Sysfs node
PCI0	  S5	*enabled   no-bus:pci0000:00
PEX0	  S5	*enabled   pci:0000:00:1c.0
PEX1	  S5	*enabled   pci:0000:00:1c.1
PEX2	  S5	*disabled  
PEX3	  S5	*disabled  
PEX4	  S5	*disabled  
PEX5	  S5	*disabled  
HUB0	  S5	*enabled   pci:0000:00:1e.0
UAR1	  S3	*enabled   pnp:00:07
USB0	  S3	*enabled   pci:0000:00:1d.0
USB1	  S3	*enabled   pci:0000:00:1d.1
USB2	  S3	*enabled   pci:0000:00:1d.2
USB3	  S3	*enabled   pci:0000:00:1d.3
USBE	  S3	*enabled   pci:0000:00:1d.7
AZAL	  S5	*enabled   pci:0000:00:1b.0

USB listing:

~$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 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 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 002: ID 0609:0322 SMK Manufacturing, Inc. eHome Infrared Receiver
Bus 005 Device 002: ID 045e:0083 Microsoft Corp. Basic Optical Mouse

~$ grep 0322 /sys/bus/usb/devices/*/idProduct
/sys/bus/usb/devices/4-2/idProduct:0322

rc.local:

#!/bin/sh -e
#
# rc.local
#
# This script is executed at the end of each multiuser runlevel.
# Make sure that the script will "exit 0" on success or any other
# value on error.
#
# In order to enable or disable this script just change the execution
# bits.
#
# By default this script does nothing.
sudo sh -c 'echo "USB0" > /proc/acpi/wakeup'
sudo sh -c 'echo "USB1" > /proc/acpi/wakeup'
sudo sh -c 'echo "USB2" > /proc/acpi/wakeup'
sudo sh -c 'echo "USB3" > /proc/acpi/wakeup'
sudo sh -c 'echo "PCI0" > /proc/acpi/wakeup'
sudo sh -c 'echo "PEX0" > /proc/acpi/wakeup'
sudo sh -c 'echo "PEX1" > /proc/acpi/wakeup'
sudo sh -c 'echo "PEX2" > /proc/acpi/wakeup'
sudo sh -c 'echo "PEX3" > /proc/acpi/wakeup'
sudo sh -c 'echo "PEX4" > /proc/acpi/wakeup'
sudo sh -c 'echo "PEX5" > /proc/acpi/wakeup'
sudo sh -c 'echo "HUB0" > /proc/acpi/wakeup'
sudo sh -c 'echo "UAR1" > /proc/acpi/wakeup'
sudo sh -c 'echo "USBE" > /proc/acpi/wakeup'
sudo sh -c 'echo enabled > /sys/bus/usb/devices/4-2/power/wakeup'
sudo sh -c 'echo "AZAL" > /proc/acpi/wakeup'
exit 0

I can confirm that /sys/bus/usb/devices/4-2/power/wakeup is "enabled"

Yes, I do wish I had a back-up.

Thank you for you help in advance and please let me know if you require any logs or additional info.

BTW I know nothing about Linux but I can copy and paste well.

Cheers
Dan

[Lester_Burnham]

Hi,

I would try moving the remote receiver to different USB ports until you end up on a USB3-* and try again.
eg. /sys/bus/usb/devices/3-2/power/wakeup

The most success I've had has been with USB3-*. Sometimes you just can't explain why...

Lester

[JJFLASH]

Hi Lester

I tried the different USB ports on the back plate but they are only USB4 (4-1,4-2) and USB5 (5-1, 5-2) and had no success. The other USB headers are not connected and I have no easy way of connecting to them.

While swapping USB devices around I did try to see if I could get the mouse to wake the system from suspend ie "enable" wakeup on the USB port the mouse is plugged into and the mouse was able to wake the system from suspend.

So I believe this means we can eliminate issues with enabling the USB and device for wakeup.

So the issue might be more specific to the IR USB -SMK Manufacturing, Inc. eHome Infrared Receiver device (software/driver/Lirc?) issue so I'll do some googling on it.

But note this IR USB device was waking up my system on earlier versions of Mythbuntu.

Regards
Dan

[arkay]

It could simply be a kernel bug. I had my system working perfectly for ages, updated and it stopped. Tore more hair our for ages until it was identified as a kernel regression, the next update fixed it.

Sometimes it isn't your fault. I'd suggest googling for other reports of any such bug and maybe getting some live cd's with different kernel versions and trying with those. (You'd have to manually test the config). Suspend issues are notoriously hard to diagnose. If mythbuntu isn't working and can't be made to work you could try dual booting (side by side install), of another myth distro. Or even install the previous one that was working if you don't NEED the latest. That is providing you can prove the issue in the first place.

Finding other using the same remote and mythbuntu version could also help, so hopefully others will pipe up if they're using the same version.

I don't keep up much with ubuntu anything as I'm not a big fan, but there might be an easy way to switch out and try a different kernel too.

Cheers,

Arkay.

[dave1234]

I'm still running a VERY old kernel26 package with the USB patch because the last time I updated I had the same issue! Completely understand the frustration.

[JJFLASH]

I did another clean install with Mythbuntu 11.04 with 2.6.38-13-generic kernal with no luck either.

The kernal; I'll keep at it and report back if I have any luck.

Cheers
Dan

[rileyp]

Dan
I'm doing a clean install of mythbuntu oneric? on a spare a partition at present so Ill keep you posted how I fare with mine. I'm thinking because of in kernel support of the mceusb you need to edit a few things and then it should be all good. Note though that a mceusb receiver will only wake from the power button on its remote and it might just be that when its setup as usb keyboard which it will be by default it may not play the game. I know I disabled the feature in natty after having a hell of time sorting out what was going on with double key presses and some buttons working some not and. My blaster not working at all as well which really confused me which turned out to be a faulty device in the end.
cheers rileyp

Edited by rileyp, 07 January 2012 - 06:18 AM.

[JJFLASH]

rileyp

Keen to know how you get on.

Dan

[rileyp]

rileyp

Keen to know how you get on.

Dan

I havent touched that clean install since I started it how ever many days ago

[Maxx Power]

Not sure if I can help, but on Windows I found that my MS remote couldn't wake my box if it was Hibernating but it works fine if I use Sleep...

I never really looked into why, but worth a shot.

[rileyp]

Ok I finally got around to getting resume from suspend working on the oneric frontend.
It was straight forward
I used Lesters method here
http://www.pcmediace...post__p__309890
my lines in rc.local look like this

# grep 006d /sys/bus/usb/devices/*/idProduct
echo enabled > /sys/bus/usb/devices/2-4/power/wakeup
echo "USB0" > /proc/acpi/wakeup

and that has it working for me.
I put the #grep in so I know how to identify the port from a terminal if I'm silly enough to change ports at some stage


heres a copy of my trials.... as normal user and root all in all it was about 6 or 7 resumes to nail it
http://pastebin.com/K13cjaqc
I found it was on usb0 and not usb 2 and i needed usb0 enabled as well as the sys/bus/usb /device above
cheers rileyp

Edited by rileyp, 21 February 2012 - 06:57 AM.