remote stops working on resume - XBMCFreak XBMCBuntu
#16
erhnam Wrote:Don't need to bookmark. I've just added this fix: https://github.com/xbmc/XBMCbuntu/commit...3448263d0e

I did this fix manually and it worked.
Reply
#17
TugboatBill Wrote:I did this fix manually and it worked.

yup, same here!
Reply
#18
Flomaster Wrote:im running this version and have the 99-lirc script.... when I have xbmc set to "suspend" I can not wake it, but if I change it to hibernate I am able to wake it. when in suspend I can see its getting power because its flashing red when I press the remote power button.

I have my rc.local setup as follows

Code:
echo USB0 > /proc/acpi/wakeup
echo USB2 > /proc/acpi/wakeup
echo US12 > /proc/acpi/wakeup
echo US15 > /proc/acpi/wakeup
echo enabled > /sys/bus/usb/devices/4-1/power/wakeup


exit 0

wonder what the deal is..

and should I have a /etc/pm/sleep.d/90_lirc as well as /etc/pm/sleep.d/99-lirc

-=Jason=-

edit: ahh fuck .. cat /proc/acpi/wakeup has USB0 disabled. I must have done that.. time to change it and report back.

EDIT: USB0 keeps getting changed to disabled. grrrr


Shouldn't it read echo "USB0" > /proc/acpi/wakeup, etc (note the quotes)?

Also you had US12 and US15 rather than USB12 and USB15?

IIRC it is preferable to only enable the USB ports that are necessary, rather than a blanket enablement.
Anti-Fascist◾Artist◾Atheist◾Barefoot◾Cis-male◾Cyclist◾Gay◾Geeky◾Introverted◾Likes weird stuff◾Living with depression & anxiety◾Naturist◾Pierced◾Socialist◾He/him
Reply
#19
dnairb Wrote:Shouldn't it read echo "USB0" > /proc/acpi/wakeup, etc (note the quotes)?

Also you had US12 and US15 rather than USB12 and USB15?

IIRC it is preferable to only enable the USB ports that are necessary, rather than a blanket enablement.

ok, I just made the change to my rc.local file... I'll try it out when my son isn't watching a show.. or else he will start crying.

-=Jason=-
Reply
#20
I have had this issue and tried the suggestions in this and other threads, without success. I have changed my rc.local file with and without quotes with no luck. (AS Rock ION 330 with MCE Remote, worked fine under Dharma)

I run cat /proc/acpi/wakeup (using Putty as user XBMC) and USB0 and USB2 both show S4 Disabled

I then run echo USB0 > /proc/acpi/wakeup AND echo USB2 > /proc/acpi/wakeup but get an error saying Permission denied (as I am not root) I then run "sudo su root" and when prompted "[sudo] password for xbmc:" I can run the command again.

Then I run cat /proc/acpi/wakeup and both USB0 and USB2 both say S4 Enabled.

I add the below to etc/rc.local

echo USB0 > /proc/acpi/wakeup
echo USB2 > /proc/acpi/wakeup


and make it executable using the command sudo chmod +x /etc/rc.local

However rebooting it reverts to disabled for USB0 and USB2.

So my question is can/do I have to enable these commands in some way for the XBMC user not the root user? What do I need to do?

I am not confident with Linux/Ubuntu/XBMCbuntu, but I can copy / paste!

Reply
#21
Agento, you are not the only one... Have exactly the same issue on my ASRock 330. And as you said, worked fine under Dharma. When logged in as root, I can run the echo command for both USB ports and set them to "enabled" (confirmed with the cat command). But adding this to rc.local does not work. Also when added with sudo sh -c in front of the echo commands... (yes, with single quotes)

Very annoying...
Reply
#22
Hi all, quick update. Managed to get it working. I copied my old rc.local file from dharma and added the line to enable the device after enabling the usb port. Only thing I noticed there were no quotes round the usb0 as stated earlier in the thread and there are no spacer/blank lines. Made no other changes, rebooted and it now works exactly as before. I'll post my exactly file when I can so you can compare.
Reply
#23
Good news! Would appreciate that Agento!
Reply
#24
(2012-03-28, 23:44)agento Wrote: Hi all, quick update. Managed to get it working. I copied my old rc.local file from dharma and added the line to enable the device after enabling the usb port. Only thing I noticed there were no quotes round the usb0 as stated earlier in the thread and there are no spacer/blank lines. Made no other changes, rebooted and it now works exactly as before. I'll post my exactly file when I can so you can compare.

Hi All,

Here is my rc.local file Between the *****'s,

*************************************
#!/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.
echo USB0 > /proc/acpi/wakeup
echo enabled > /sys/bus/usb/devices/2-3/power/wakeup
exit 0
*****************************************************

I did some additional testing. I re-added extra spacing and also seems to work now. Very wierd. Cant understand it.

All I WOULD say is ensure you use putty as ROOT, not the default XBMC user. This also applies to FTP if you use it to transfer the rc.local file rather than edit live.

As ever, your USB port may be different, and your devices/X-X/ may also differ. Don't just copy and paste!

Oh and make sure XBMC power settings are set to suspend, NOT hibernate/switch off. That caught me out on one occasion!
Reply
#25
Hi guys

this is my first post to this forum. i have the following 2 problems, as with lots of other users:

1. i can not resume with the remote.
2. remote stops working after the resume (i resume by pressing the power button on my pc casing)

i have tried almost everything mentioned in this and other forums but of no use. following is the info that i have :

1. PC with Intel DG45ID motherboard.
2. XBMCbuntu version 11.10
3. HP MCE remote.
4. lirc version 0.9.0 (so i can not do the MythTV procedure mentioned in this post some where)
5. XBMCbuntu setup to suspend in the power management.
6. lsusb output 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 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 002: ID 045e:006d Microsoft Corp. eHome Remote Control Keyboard keys <--- this is my remote
Bus 007 Device 002: ID 1997:0409

7. cat proc/acpi/wakeup is :

Device S-state Status Sysfs node
P0P1 S3 *disabled
UAR1 S3 *disabled pnp:00:03
P0P2 S3 *disabled pci:0000:00:1e.0
USB0 S3 *disabled pci:0000:00:1d.0
USB1 S3 *disabled pci:0000:00:1d.1
USB2 S3 *disabled pci:0000:00:1d.2
EUSB S3 *disabled pci:0000:00:1d.7
USB3 S3 *enabled pci:0000:00:1a.0
USB4 S3 *disabled pci:0000:00:1a.1
USBE S3 *disabled pci:0000:00:1a.7
PEX0 S4 *disabled
PEX1 S4 *disabled
PEX2 S4 *disabled
PEX3 S4 *disabled
PEX4 S4 *disabled
GBE S4 *enabled pci:0000:00:19.0
USB5 S3 *disabled pci:0000:00:1a.2
PWRB S5 *enabled


8. when i tried to restart the /etc/init.d/lirc, it gives me the following error:

root@raz-xbmc:/etc/lirc# /etc/init.d/lirc start
* Loading LIRC modules
* Unable to load LIRC kernel modules. Verify your
* selected kernel modules in /etc/lirc/hardware.conf


9. above error is because /etc/lirc/hardware.conf file has REMOTE_MODULES="lirc_dev lirc_mceusb2" but "lirc_mceusb2" does not exists in my system. when i remove this module, it does not give any error but remote still does not work after resume.

10. output of "lsmod | grep irc"

ir_lirc_codec 12770 0
lirc_dev 18700 1 ir_lirc_codec
rc_core 25797 9 ir_lirc_codec,ir_sony_decoder,ir_jvc_decoder,ir_rc6_decoder,rc_rc6_mce,ir_rc5_decoder,ir_nec_decoder,mceusb

10. output of "lsmod | grep mce"

rc_rc6_mce 12454 0
mceusb 17602 0
rc_core 25797 9 ir_lirc_codec,ir_sony_decoder,ir_jvc_decoder,ir_rc6_decoder,rc_rc6_mce,ir_rc5_decoder,ir_nec_decoder,mceusb

let me know if anyone can help or need more info to solve this issue.

thanks


Reply
#26
Hi again,

following code solved the problem of waking up the pc from suspend:

#set wake via remote
echo enabled > /sys/bus/usb/devices/3-5/power/wakeup
for i in 0 1 2 3 4 5
do
enabled=`cat /proc/acpi/wakeup | grep "USB$i" | awk {'print $3}'`
echo "$enabled"
if [ "$enabled" = "disabled" ] || [ "$enabled" = "*disabled" ]
then
echo "USB$i" > /proc/acpi/wakeup
fi
done



but after the resume, remote still does not work. no output in the irw command too. I tried /etc/init.d/lirc stop/start but no luck Sad

need urgent help please.

thanks
Reply
#27
(2012-04-25, 21:02)raufiq Wrote: Hi again,

following code solved the problem of waking up the pc from suspend:

#set wake via remote
echo enabled > /sys/bus/usb/devices/3-5/power/wakeup
for i in 0 1 2 3 4 5
do
enabled=`cat /proc/acpi/wakeup | grep "USB$i" | awk {'print $3}'`
echo "$enabled"
if [ "$enabled" = "disabled" ] || [ "$enabled" = "*disabled" ]
then
echo "USB$i" > /proc/acpi/wakeup
fi
done



but after the resume, remote still does not work. no output in the irw command too. I tried /etc/init.d/lirc stop/start but no luck Sad

need urgent help please.

thanks

UPDATE: I have wireless remote (Rii new model with USB receiver) and when i enable all my USB ports, I can wake up the system by pressing a key on my wireless remote. it means that BIOS is supporting wake from USBHuh

waiting for a solution ...... Sleepy
Reply
#28
Regarding the Rii usb receiver there seem to be an existing problem. I have problems in WIN7 and have the same problem with wake up.
There is also a thread at avsforum that is 2 years old describing this problem. http://www.avsforum.com/t/1232708/rii-mi...s-keyboard

This is what I discovered.
I put my ASRock htpc with Windows 7 home premium into hibernation and try to wake my HTPC with the keyboard.
My keyboard has two states indicated by LED indicators. A steady green light- awake, a flashing yellow - hibernate.

If I press any key on the keyboard I can see on the LED indicators that the keyboard is awakening from both states and transmits the keystroke.
This will wake my HTPC. But now the HTPC will ignore the keyboard completely.
If keep on pressing keys on the keyboard while it still is awake it looks like it is transmitting the keystrokes.
But if I leave the keyboard until it hibernates and then press a key I can see on the LED's that it tries to connect with the USB radio but fails.

One other test I made was to wake the HTPC with an other device. I used the IR remote that came with the PC and also a Logitech wireless mouse.
If I wake the HTPC from hibernation with any other device, the keyboard will work perfectly.

It is definitely something wrong with the USB radio that is used in these keyboards and perhaps in combination with hardware/bios.
If I check for hardware changes in the device manager, windows still believes there is a HID keyboard attached.
The only way to reset the USB radio seems to power cycle it.

I have opened my USB radio and found a Cypress CYRF69213. It seems that the cpu part is still working but the radio part has stopped working.
Reply

Logout Mark Read Team Forum Stats Members Help
remote stops working on resume - XBMCFreak XBMCBuntu0