![]() ![]() The MCE remote protocol is a standard of sorts, so there are actually a whole bunch of 'devices' in Logitech's database which are listed as being for various HTPCs or remote controls which are really just sending the standard MCE commands, and you can pick any of them if what you're actually talking to is an MCE transceiver. Obviously I couldn't sleep with things this way, so I decided to try just one other thing: I changed the profile I was using for the transceiver in the Harmony configuration. Everything seemed to be pointing to Go, yet my remote obstinately would not wake up the system. I had XBMC configured appropriately: wake from actual power-off is rarely going to work, so you want to configure XBMC to suspend when it's told to shut off that setting is in System / Settings / System / Power saving / Shutdown function, set it to Suspend. I had all the even-possibly-relevant firmware settings I could find set to 'yes please let me wake up thank you very much'. I could wake up just fine with a USB keyboard plugged into the same port. All the entries in /proc/acpi/wakeup and /sys that could possibly be the port which my transceiver was plugged into were definitely set to enabled. I suspect the tosuspend reference is ancient now, but I couldn't say for sure. It does seem like poking /proc/acpi/wakeup and/or /sys/blahblahblah/power/wakeup is sometimes necessary for some folks, to enable wake-from-USB at the kernel level for the relevant USB host interface. I don't think there's a lot of woo-woo there, but input from kernel folks who know what the stuff that's being cargo culted there actually does would be welcome. Now this is one of those topics where if you DuckDuckGo it, you'll find some possibly relevant information, and an awful lot of woo-woo. I could suspend the system from the remote, but not wake it up. Then I tried it, and was a sad bunny when it didn't. I set it up with the Philips profile for the Harmony remote, and everything worked fine (as long as I stick the transceiver on a shelf and point it at the wall.yeah, IR is weird), then I thought "hey, maybe on/off from the remote will finally work now!" I say 'genuine' because I bought it off eBay, so who knows, but hey. So I chucked it and replaced it with a 'genuine' MCE remote transceiver, a Philips OVU4120 (much like this newer model). So that receiver started packing up recently it'd frequently get stuck repeating keys, or just not register when it was plugged in, throwing USB errors in the kernel logs. I just had to control the power manually, which really isn't that big of a deal but ate away at me inside, leaving me a hollow, hollow man. I can't recall whether it was on or off that didn't work with the old one, but one didn't. It worked fine for a long time, but one thing that never quite worked was that I couldn't manage to suspend and resume the system from the remote. XBMC and OpenElec are great projects.Įver since I set it up, I've used a janky USB infrared receiver I got off eBay to control it. ![]() The HTPC box has been one of my more succesful hardware purchases: I've had it running ever since that blog post, and it's just great, really. So that Harmony remote I talked about recently is hooked up to (among other things) my HTPC box. One of the feelings that almost makes up for all the hassle that comes with building your own infrastructure is the one you get when that last little bit of a jigsaw puzzle finally fits into place. ![]() ![]() Tl dr: if you've read all the references and still can't get your Harmony or other universal remote to wake up a computer, make sure you use the Media Center Extender or Media Center Keyboard device profile in the Harmony software. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |