After upgrading my kernel from 3.1.1 to 3.3.5 (both times gentoo-sources), I can no longer wake up this machine by pressing a key on the keyboard or clicking/moving the mouse, which used to work flawless before. Shortly pressing a key lights up the numlock-key, indicating it's under power, but nothing more happens - wake up via powerbutton works.
++++++++++[>+++++++>++++++++++>+++>+<<<<-]>++.>+.+++++++..+++.>++.<<+++++++++++++++.>.+++.------.--------.>+.>.
same here, I upgraded from 3.2.12 to 3.3.8. Just as in avx's case, my kernels are both gentoo-sources.
If anybody has any insights, I'd also be happy to hear about them.
Bumping this, currently at 3.4.2, same problem.
++++++++++[>+++++++>++++++++++>+++>+<<<<-]>++.>+.+++++++..+++.>++.<<+++++++++++++++.>.+++.------.--------.>+.>.
Now on 3.5.0, still doesn't work and I'm getting pissed.
++++++++++[>+++++++>++++++++++>+++>+<<<<-]>++.>+.+++++++..+++.>++.<<+++++++++++++++.>.+++.------.--------.>+.>.
Not that this will help, but I have not been able to wake up via a USB attachment for over a year.
I can no longer hibernate either. Not me, the PC.
I can however suspend. Sure no mouse or keyboard hit or click will awaken, but as soon as I hit the power button, I have a resumed desktop within 5 seconds.
So why not just hit the power button?
Whatever you do, do it properly!
So why not just hit the power button?
Because it's door->desk, reach over it, press key, walk around desk, sit, machine is one vs. walk a few meters more, press button, return - the machine is placed rather far away, which normally doesn't matter.
I googled around a little and so far found no other notices on other distributions where people are newly having this problem, only people who never had it working in the first place.
If I'd were better in kernel stuff or had a clue, where the problem might be located, I'd try to fix it, but I'm not really willing to `git bisect` over dozens of kernel changes.
++++++++++[>+++++++>++++++++++>+++>+<<<<-]>++.>+.+++++++..+++.>++.<<+++++++++++++++.>.+++.------.--------.>+.>.
I just compiled 3.3.8 and discovered this exact problem. Keyboard lights up but nobody's home!
What the ??
Make sure your kernel has ACPI processor support enabled.
11. USB4 S3 *disabled pci:0000:00:1a.1 <-- huh?
Enabled in one place, disabled the next???
So the device is enabled but the bus isn't? How bizarre. I didn't have to do anything before to get it to work.
What the hell? It seems there's a disconnect! udev was one of the updates, maybe a ruleset changed?
Ah-HA! Apparently I did have to do something before! I had a file in /etc/local.d/ called 'enableusbwake.start' with 'echo "USB4" > /proc/acpi/wakeup' in it. Apparently it's been so long I forgot.
It appears udev is now setting this automatically. So I removed the file in /etc/local.d/ and rebooted and alas, it works again. udev was setting it correctly and my script was disabling it!
The keyboard was enabled but the USB hub itself was not (the first line/response.) /proc/acpi/wakeup indicates it IS enabled, but it clearly is not.
And I can put it to sleep and wake it up with the keyboard like I usually can. Tried several times, works a-ok. So basically using /proc/acpi/wakeup is useless now, or it's not in sync or something...
If you are having this problem you'll have to identify your keyboard and then create a file in /etc/local.d/ like I have (your USB IDs will obviously be different.) Sigh...
Wow, long text, I'll read and try this later, thanks (just a reminder post^^).
++++++++++[>+++++++>++++++++++>+++>+<<<<-]>++.>+.+++++++..+++.>++.<<+++++++++++++++.>.+++.------.--------.>+.>.
Yeah, sorry about that. I was going and documenting step-by-step what I was trying. It might help others troubleshoot this annoying problem though. It seems that /proc/acpi/wakeup now is not connected to /sys/devices/*... only when I directly toggled the hub in /sys/devices did the stupid thing start working again. I guess there's not much reason to keep the deprecated /proc/acpi in the kernel anymore.
It still works, I woke my computer with the spacebar this morning.
I am sure there was a similar problem on gentoo-user and it was solved via a kernel config option. You might want to hit the archive.
I identify as a dirty penismensch.
Ehm, the archive on http://archives.gentoo.org/gentoo-user/date.xml ends at April 07 2012?!
Anyway, couldn't find something on gmane or via Google, any clue in what timeframe that thread may have been?
++++++++++[>+++++++>++++++++++>+++>+<<<<-]>++.>+.+++++++..+++.>++.<<+++++++++++++++.>.+++.------.--------.>+.>.
Ehm, the archive on http://archives.gentoo.org/gentoo-user/date.xml ends at April 07 2012?!
Anyway, couldn't find something on gmane or via Google, any clue in what timeframe that thread may have been?
I searched too, I couldn't find anything. I used gossamer-threads.com but only found results for up to Nov 2011, but that wasn't the same problem.
I unplugged my computer today to move it, and plugged in the keyboard to the wrong hub so it stopped working again.
The problem is acpitool says stuff is enabled, but under /sys/devices/ it is NOT enabled, and apparently that's the part that matters.
I actually wrote a quick bash script to check and set these things, I posted it in the Tips & Tricks forum.
I actually wrote a quick bash script to check and set these things, I posted it in the Tips & Tricks forum.
Testing.
What I'm wondering, if this is somehow device/chipset/... specific, cause my Macbook wakes up just fine without any special treatment, my desktop never did until I played with these things sometime last year.
Edit, Works, thanks.
++++++++++[>+++++++>++++++++++>+++>+<<<<-]>++.>+.+++++++..+++.>++.<<+++++++++++++++.>.+++.------.--------.>+.>.
Use of /proc/acpi/* is deprecated, so I doubt it will be fixed...
Doesn't matter, as I said above, I'm running a pretty long time (>1 year) without /proc/acpi and wakeup still worked, up until the point where I did the initial post for this topic.
++++++++++[>+++++++>++++++++++>+++>+<<<<-]>++.>+.+++++++..+++.>++.<<+++++++++++++++.>.+++.------.--------.>+.>.
Interestingly enough, on my computer /proc/acpi/wakeup still exists, even after removing the deprecated /proc/acpi directories and files from my kernel. I guess acpitool -w is still using /proc/acpi/wakeup but it does not reflect what is actually enabled under /sys/devices.
Does /proc/acpi/wakeup still exist on your install too?
Does /proc/acpi/wakeup still exist on your install too?
Yep.
++++++++++[>+++++++>++++++++++>+++>+<<<<-]>++.>+.+++++++..+++.>++.<<+++++++++++++++.>.+++.------.--------.>+.>.
Kernel patch to change USB hub wakeup behavior.
should be enabled for wakeup by default.
enable it explicitly if it is desired.
So it is fully up to userspace tools (or maybe custom udev rules? Haven't tried that) to re-enable devices that no longer work.
Good to know, thanks.
++++++++++[>+++++++>++++++++++>+++>+<<<<-]>++.>+.+++++++..+++.>++.<<+++++++++++++++.>.+++.------.--------.>+.>.
Good to know, thanks.
That's an upstream change. They change stuff all the time without warning people. I still remember my scsi driver failing to build because they changed something in the kernel.
++++++++++[>+++++++>++++++++++>+++>+<<<<-]>++.>+.+++++++..+++.>++.<<+++++++++++++++.>.+++.------.--------.>+.>.
That is strange. Did you check /proc/acpi/wakeup too?
Mine's been working fine.
Aha, for some reason, pretty much everything in /proc/acpi/wakeup was set to disabled. Blindly enabling every device here helped and it's working again. Thanks.
++++++++++[>+++++++>++++++++++>+++>+<<<<-]>++.>+.+++++++..+++.>++.<<+++++++++++++++.>.+++.------.--------.>+.>.
No problem.
