2014-08-14, 20:09
(2014-08-14, 20:06)ratzofftoya Wrote:(2014-08-14, 17:10)voip-ninja Wrote:(2014-08-14, 15:50)JasonHoffman Wrote: A couple of weeks ago I installed Openelec fresh and didn't have to modify any scripts for the remote to work. The only change I made was enabling the "remote sends keyboard presses" option, but I don't know that it had anything to do with the remote working or not.
Believe me if I'd had to get into a script I'd remember.
This is what I've got in my autostart.sh
Code:OpenELEC:~ # more /storage/.config/autostart.sh
#!/bin/sh
modprobe -r nuvoton-cir && echo "auto" | tee /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources && modprobe nuvoton-cir
xrandr --output HDMI1 --set "Broadcast RGB" "Full"
The first line was required when I initially loaded Gotham based OE 4.x to get IR to work after initial boot (the 2nd line sets RGB output to "full" on HDMI port 1 to fix some white/black crush issues with my particular TV/AVR combo).
However, you are correct. I just commented it out a second time and the IR is still working. I'm pretty sure though that if I took this line out and tried to use my older Windows Media Center remote profile it would still fail. I specifically did that during troubleshooting and discovered that the remote stopped working when I took that line out.
This all makes me feel like I should just do a fresh install of OE, but have little energy for it at the moment.
Are you using an MCE profile on a Logitech remote or something? I had an Xbox remote and couldn't get the power on to work for the life of me.
Yes, I am using an MCE profile on a Logitech Harmony One. Interestingly several of these device profiles no longer work with the NUC but the "Media Center Extender" profile does.
My understanding is that the new firmware WY0027.BIO fixes some NUC power on issues (although it actually caused mine to stop working till I started using a different device profile) ... and it's possible the xbox remote now works.
It's also worth noting that back when my older profile was working, it would power the NUC up, but it would not then have IR control or power it off... that's why I had the above line in the autostart.sh, apparently OE was not setup to poll for and load the Nuvoton IR driver... I guess they've now fixed that.
