<br><br><div><span class="gmail_quote">On 7/17/07, <b class="gmail_sendername">Leighton Brough</b> <<a href="mailto:brough@baremetalsoft.com">brough@baremetalsoft.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Craig Huff wrote:<br>> Problem: I can't get my remote to wake up my system. I want to be able to wake from the suspend-to-disk state, which I *think* is S4 (important that I have this right -- see below)<br>><br>
> Earlier in this thread Leighton reported that he was using the Microsoft MCE USB remote to wake his system from the suspend-to-RAM state.<br>><br>> I have an Asus M2NPV-VM motherboard based system which I am still configuring and I have a (newly purchased) Microsoft MCE USB remote attached.
<br>><br>> I have all the mobo jumpers repositioned to supply standby power to the keyboard and the backpanel USB ports, where I have the MCE receiver attached.<br>><br>> I *can* wake my system up with the keyboard I'm using while I set it up, but eventually it has to go ;-).
<br>><br>> I have turned on the BIOS setting for allowing/enabling PCI events to wake the system up.<br>><br>> I have tried doing the following before suspending to disk:<br>> # echo USB0 > /proc/acpi/wakeup
<br>> # echo USB2 > /proc/acpi/wakeup<br>> # echo PS2K > /proc/acpi/wakeup<br>> and then suspending with (IIRC):<br>> # echo disk > /sys/power/state<br>><br>> Since I plan to use Suspend2 (now called TuxOnIce! I think) and already have in installed, I tried that, too, after the three echoes to /proc/acpi/wakeup with:
<br>> hibernate<br>><br>> I've tried various keys on the remote and can see the receiver feedback LED respond, but the system stays off until I use the keyboard or front panel power switch.<br>><br>> After performing the three echoes to /proc/acpi/wakeup, I get the following with this command:
<br>> # cat /proc/acpi/wakeup | grep enabled<br>> PS2M 4 enabled<br>> PS2K 4 enabled<br>> USB0 4 enabled<br>> USB2 4 enabled<br>><br>> I interpret this to mean the USB ports, keyboard and mouse are all enabled to wake the system from the S4 state.
<br>><br>> Have I left any stones unturned or is this mobo doomed to not wake from S4 via this IR receiver?<br>><br>><br>The only other stones I can suggest to turn are:<br><br>The only button on the MCE remote which will wake the system is the
<br>power button. So make sure this is the one you are pressing. For me this<br>is the only button which causes the receiver LED to flash when the<br>system is suspended.<br><br>Some time ago, using an earlier kernel (sometime before
2.6.18 - I<br>forget which) I found I had to manually set the power state of the USB<br>receiver then unload the USB driver module to prevent this from turning<br>it off when suspending. I forget the exact files involved, but I think
<br>it was something like /sys/.../power. I guess it's unlikely this is your<br>problem, but if you're trying to exhaust all possibilities it might be<br>worth having a rummage in /sys too. Or for that matter you could try
<br>another kernel, since it seems the support for ACPI and power management<br>continues to improve over time. Of course your kernel needs to be built<br>with ACPI support too, but I don't think you'd see /proc/acpi if it wasn't.
<br><br>There's a kernel command line parameter called "acpi_os_name" which<br>allows you to specify the name which the OS reports to the ACPI<br>subsystem, which in turn may alter the behaviour of this. Try Googling
<br>for this, it might give you some ideas. Also, there are some ACPI<br>support issues with Linux, due to the Microsoft versus Intel compiler<br>being used to build the ACPI tables. Some folks have found they need to<br>
fix the ACPI tables to get features to work. Again, Googling for Linux<br>and ACPI might give you some things to try.<br><br>When I was first experimenting with this I temporarily installed Windows<br>2000 (or maybe it was XP) just to prove the HW worked OK. You can set
<br>the "allow this device to wake the system" option for the USB receiver,<br>then hibernate and try the remote power button. This was (relatively)<br>quick and easy to get going, and gave me the confidence to persevere
<br>with the required Linux config. That may be something else you can try.<br><br>The only other thing I can think of to suggest is to try both enabling<br>and disabling the BIOS setting for PCI event wakeup (I don't have this
<br>setting in my BIOS). But you've probably already tried that.<br><br>For what it's worth, when I cat /proc/acpi/wakeup I also see state 4 for<br>all devices, even though my system wakes from S3. I'm not sure the "4"
<br>means "S4" or the ACPI device power state the USB device will be put<br>into on suspend (related to but different from the S1 - S5 system power<br>states).<br><br>Leighton</blockquote><div><br>Is it possible to do this with a serial receiver? What if I get a usb serial dongle?
<br><br>-Dave<br></div><br></div><br clear="all"><br>-- <br>David Frascone<br><br>Happiness is a warm modem