Lmyllari, you may want to forward your inquiry to Linux* distribution support community for further assistance since this is an operating system that we do not support.
However, we are going to test this feature on a Windows environment. I will let you know if it worked.
Make sure you have the latest BIOS version installed (0021)
thank you for looking into this. I assume the CIR works on Windows too. The problem seems to be the values BIOS reports.
I was originally at BIOS version 0018 and updated to 0021 - there seem to be no change related to this.
To clarify, the DSDT snippet I posted is not related to the operating system, and doesn't seem correct when compared to the ACPI specification (rev 5.0, section 6.3.7).
We tested CIR using a TSGH-IR02 remote control on a D54250WYK NUC and CIR worked just fine on a Windows environment.
We have not validated any CIR device under Linux, unfortunately
Sylvia - I think that you're misunderstanding.
While it's true that it works in Windows, Imyllari is saying that the status reported by the BIOS is incorrect due to ACPI standards that everyone abides by. Even though it works in Windows, this would still be a bug. Can you verify and let us know if this will be fixed in the next BIOS update release?
Sylvia, any update on this? Could somebody look into the BIOS (specifically _STA for CIRP) and make sure it complies with the ACPI specification?
1 of 1 people found this helpful
For those of you who want to use your internal infrared reciever with Linux and OpenELEC do the following in SSH as a workaround until this is fixed by Intel.
-- do these commands
-- enter the following
modprobe -r nuvoton-cir
echo "auto" > "/sys/bus/acpi/devices/NTN0530:00/physical_node/resources"
-- press ctrl+x and then Y
-- do these commands
chmod 755 autostart.sh
This should load the driver correctly. To check if it works write "irw" in the command prompt and start pressing your remote to see if it recieves any signals.
Tested on Intel Nuc D54250WYK with OpenELEC 3.2.4.
All credit goes to Imyllari who actually solved the issue.
I contacted the NUC team about this. After reading through the thread they gave me the following advice:
"They also need to install a package called LIRC that should be in the repository for the Linux Distribution they are using. Not familiar with this version of Linux. We have been able to get IR devices to work with Ubuntu and Linux Mint."
I will try this on my Haswell NUC running Linux Mint at home and let you know the results.
This issue is deeper than that. The issue isn't getting the buttons mapped, but getting the OS to recognise the IR-component. Please have someone who works on the BIOS (i.e. a developer, not a general support person) look over the information that Imyllari provided in the first post. This issue potentially affects everyone using an OS that complies with the ACPI standards.
Any update on this? It would be real swell if someone could find out if Intel intends to fix this.
Come on, Intel people. Please verify the issue.
I tried this fix for my d34010wyb and it didn't seem to have any effect.
You can disregard. Funny how these commands don't work at all when there's a typo.
Next time I'll double check my typing first.
Thanks for the fix!