2013-12-03, 16:32
(2013-12-03, 01:44)BLKMGK Wrote:(2013-12-02, 07:53)musicman_234 Wrote: Newcomer here. Been reading this thread with great interest, as i have an i5 NUC. For the life of me, I can't get the CIR working. I've read, and re-read, the threads on how to fix it (the workaround). I'm not a Linux expert, but my trouble seems to be that I can't actually modify the resources file for the NTN0530. I do the 'echo "auto"...' Command, and then cat the file, and its no different. I've played with permissions (chmod) to no avail. The resources file always starts with "status = disabled". I've verified CIR is enabled in BIOS.
I'm running Linux mint 15. Fully upgraded it.
Help?
I had several issues getting Mint to work and switched to Openelec, much much easier!
To get the CIR working on Openelec follow these instructions to create the http://wiki.openelec.tv/index.php?title=Autostart.shautostart. I believe this will NOT work for standard Mint. Once the file is created and you're logged in via ssh run nano to edit the file. You can copy paste in the commands to active the CIR from other posts in this thread. Save the file! You can then either reboot OR run the file by typing ./autostart.sh - it won't return anything.
This assumes of course that you're on the latest bios, 21 I think it is? It's a bios bug that forces us to do this workaround so I suspect that bios version matters. Once this is done I think you'll find Openelec pretty polished!
P.S. I've just remembered, once the autostart.sh file has been created you can also just edit it via the smb share from a Windows machine - it's in the configurations folder. IF you do this you MUST not use Notepad to edit, download and use Notepad+ as it won't put end of line crap in the file like Notepad does. This hidden eol stuff trips up Linux!
Not a BIOS issue. I just upgraded to bios 21. No change in behavior. CIR still not working at all. If OpenElec can work, there's no reason Mint can't work. Really hoping someone seeing this will have a suggestion or two for debugging this...I've no idea how to tell if the driver is actually connecting to the hardware or not.
