Agree with fatski. i had a long night trying to figure this out, and now its solved. thank you!!
Agree with fatski. i had a long night trying to figure this out, and now its solved. thank you!!
Thank you! This worked great for me! If people are interested in troubleshooting a little more, I've put more details in this post, including manually toggling the enabled state without udev.
Your solution works great for my USB keyboard and mouse, but I'm still having trouble getting my laptop's internal keyboard or trackpad to wake the computer. I'm not sure that it's considered a USB device, but I did some troubleshooting. Firstly, I triedThen (ignoring the "/sys/devices/platform/serial8250/tty/*" entries) I manually toggled all of the 18 disabled wakup files to enabled. None of them fixed the problem for me... Would anyone know if there's another wakeup file to find, or something else?Code:$ find /sys/devices/ -name wakeup
I am confused. Why do the "#echo USB2 >> /proc/acpi/wakeup" lines in rc.local not only no longer work, but if not commented out cause the /proc/acpi/wakeup devices to be disabled (assuming the 90.mcewakeuprules file is in place)?
Has anyone else found that a recent upgrade has broken this workaround? I presume it's the kernel upgrade to 3.2.0-25.
Since this upgrade, I cannot get my computer to suspend at all. I have a udev rule as described in this thread to allow my mouse to wake up the computer. If I attempt to suspend, the computer immediately wakes back up. I removed the udev rule (or rebooted the computer without the mouse plugged in) and I can suspend fine.
Oddly enough, if I manually alter the wakeup file instead (as per my post here), e.g. withI can suspend fine, but the moues no longer wakes the computer up anyway.Code:$ sudo su # echo enabled > /sys/bus/usb/devices/3-1.3/power/wakeup
No, not really. But lately I've had to do this (and fool around with the other stuff in this thread) in order to get suspend/resume to work. Maybe its a bug or maybe it is a feature? So far this has been a question of trial and error for me. I thought of writing up some experiences because I know I'm not alone...I'm just a regular MythTV user.
Ah okay. Thanks for sharing your advice. Something to keep in mind I guess.
Cheers.
Thanks!!
Bookmarks