Posts by jonbags

Hi all, anyone else running a NUC with the AVX build, utilizing the in-built ir receiver?

It has stopped working for me post devel-20180211

I posted this output earlier, however again for reference:-

output from devel-20180211 (currently working)

dmesg | grep cir
[    4.493374] nuvoton-cir 00:01: found NCT6776F or compatible: chip id: 0xc3 0x33
[    4.565473] lirc lirc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) registered at minor = 0
[    4.565493] nuvoton-cir 00:01: driver has been successfully loaded

output from devel-20180219 (not working)

dmesg | grep cir
[    4.545143] nuvoton-cir 00:01: found NCT6776F or compatible: chip id: 0xc3 0x33
[    4.693619] rc rc0: lirc_dev: driver nuvoton-cir registered at minor = 0
[    4.694318] nuvoton-cir 00:01: driver has been successfully loaded

I see that it is referring to the device as rc0 and not lirc0 in the newer kernel, however not too sure if a config change is required somewhere to reflect this..

grabbing an output from ir-keymap, i can see it has the same table / protocols loaded as the working build

Found /sys/class/rc/rc0/ (/dev/input/event10) with:
    Driver nuvoton-cir, table rc-rc6-mce
    Supported protocols: lirc rc-5 rc-5-sz jvc sony nec sanyo mce_kbd rc-6 sharp xmp 
    Enabled protocols: lirc nec rc-6 
    Name: Nuvoton w836x7hg Infrared Remote
    bus: 25, vendor/product: 1050:00c3, version: 0x0033
    Repeat delay = 500 ms, repeat period = 125 ms

Whilst the driver seems to load ok, I get no test signals received performing tests:-

ir-keytable -t

or

mode2

I have also tried putting a keymap file for my xbox_one remote in the rc_keymaps folder. ir-keytable reads this ok when instructed to:-

ir-keytable -c -w /storage/.config/rc_keymaps/xbox_one

However, does not make a difference unfortunately.

I have also tried toggling between ir modes in the NUC bios (RC6 & MCE remote)

Switching the lirc service on in libreelec also has no effect.

Would appreciate any other suggestions if anyone has some.

Cheers

I'll try stuffing with the config when I am home next week, cheers

output from devel-20180211 (currently working)

BroStation:~ # dmesg | grep cir
[    4.493374] nuvoton-cir 00:01: found NCT6776F or compatible: chip id: 0xc3 0x33
[    4.565473] lirc lirc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) registered at minor = 0
[    4.565493] nuvoton-cir 00:01: driver has been successfully loaded

Output from devel-20180214

BroStation:~ # dmesg | grep cir
[    4.592880] nuvoton-cir 00:01: found NCT6776F or compatible: chip id: 0xc3 0x33
[    4.697293] rc rc0: lirc_dev: driver nuvoton-cir registered at minor = 0
[    4.697367] nuvoton-cir 00:01: driver has been successfully loaded

Hi mate, same model as you I believe. Not sure of the kernel config, not my area of expertise sorry.

I'll make do with LibreELEC-Generic.x86_64-8.2-devel-20180211.tar

Cheers for all your work

Hi mate, still no go with the CIR on build LibreELEC-Generic.x86_64-8.2-devel-20180214.tar unfortunately

Hey mate, I have updated to your AVX2 build LibreELEC-Generic.x86_64-8.2-devel-20180213.tar and i have found that the built-in CIR is no longer working with my Xbox One remote.

I'm running a NUC5i7RYH

Dropping back to LibreELEC-Generic.x86_64-8.2-devel-20180211.tar seems to work fine again.

Logs attached if you are able to check it out, **this board is not letting me upload zip attachments at present, so the full log zip if needed is at:-

here

Cheers

escalade Hey mate, apologies if this is something obvious that I have missed, but do you have a changelog location? For example on the avx builds, is there somewhere I can see what has changed between LibreELEC-Generic.x86_64-8.2-devel-20170925.tar and LibreELEC-Generic.x86_64-8.2-devel-20170927.tar?

I searched this thread and could not find a changelog discussion.

Cheers

Cheers mate!

escalade Hey mate. Got some time to provide logs for my NFS issue on 20170904 avx build I mentioned above

I am running a nuc5i7ryh

Kodi Log

system log

hardware log

I can see this myself if thats a clue.

18:40:02.463 T:140050200839936   DEBUG: SECTION:LoadDLL(libnfs.so.8)
18:40:02.463 T:140050200839936   DEBUG: Loading: libnfs.so.8
18:40:02.463 T:140050200839936   ERROR: Unable to load libnfs.so.8, reason: libnfs.so.8: cannot open shared object file: No such file or directory
18:40:02.463 T:140050200839936   DEBUG: Dll libnfs.so.8 was not found in path
18:40:02.463 T:140050200839936   ERROR: NFS: Error loading libnfs (HandleDyLoad).

Cheers for all your work legend

Hi mate, diggin the build. Just an FYI, been using the AVX build on my NUC and with the latest one (20170904) I am unable to browse any NFS shares.

Reverted to 20170829 and all was good again.

I did not grab any logs at the time but will do tonight.

Cheers for your work!