Prior to 3.2 I had to use "echo USB0 > /proc/acpi/wakeup" to allow my
keyboard/mouse to wake up the computer (USB0 was disabled by default).
Now with 3.2 this no longer the case (USB0 is enabled by default).
In my case, I want it disabled since I have my keyboard + mouse attached
with a KVM. With USB0 enabled, the keyboard & mouse will wake up the
system. All it takes is a bump of the mouse and next thing I know the
system is back on.
TLDR; Something changed, in regards to the suspend code, in 3.2
Those commands were working fine before Linux 3.2.
But now, they seem to be ineffective (i.e. the corresponding devices are
marked as '*disabled' in the output of `cat /proc/acpi/wakeup`).
Greetings,
I can't believe I topped posted!!!!! Argh! So so sorry!
May not be much help, but....
Prior to 3.2 I had to use "echo USB0 > /proc/acpi/wakeup" to allow my
keyboard/mouse to wake up the computer (USB0 was disabled by default).
Now with 3.2 this no longer the case (USB0 is enabled by default).
In my case, I want it disabled since I have my keyboard + mouse attached
with a KVM. With USB0 enabled, the keyboard & mouse will wake up the
system. All it takes is a bump of the mouse and next thing I know the
system is back on.
TLDR; Something changed, in regards to the suspend code, in 3.2
~pyther
01-20-2012, 08:49 AM
Bastien Dejean
Authorized Resume Devices and Linux 3.2
Matthew Gyurgyik:
> May not be much help, but....
>
> Prior to 3.2 I had to use "echo USB0 > /proc/acpi/wakeup" to allow
> my keyboard/mouse to wake up the computer (USB0 was disabled by
> default). Now with 3.2 this no longer the case (USB0 is enabled by
> default).
On the contrary, this is extremely helpful: it means my rc.local
commands are indeed effective, they disable EHC1 and EHC2 which are now
enabled by default, so I've just removed those lines.
Authorized Resume Devices and Linux 3.2
