Thanks @ian57 for the clarification.

Kodi and Samba 1.0 could be the issue. I can't find out what smb-version my NAS (a LaCie 5big network 2) has on board. Though I don't have any issues connecting Win10, Mac Catalina or Ubuntu Focal to it, which seems strange is smb 1.0 is such a big problem.

exFat is actually good news, concerning bigger files. But even on exfat it is not possible to have multiple files with the same name but different uppercase/lowercase letters - they would still be treated as the same file! (unlike on linux filesystems for example).
So giving errors for not finding files according to different case sentitivity is simply a dumb design decision.

Perhaps I will go through all the pain again and try to set up recalbox 7.1 on my pi. Lockdown gives me plenty of time anyway. Just looking for the good (no, I don't say "positive" ) things.

Danke @Strykjar für die Lösung! Hatte das selbe Problem und habs jetzt nach deiner Anleitung geändert und jetzt funktioniert wieder alles!

Thanks @ian57 for the clarification.

Kodi and Samba 1.0 could be the issue. I can't find out what smb-version my NAS (a LaCie 5big network 2) has on board. Though I don't have any issues connecting Win10, Mac Catalina or Ubuntu Focal to it, which seems strange is smb 1.0 is such a big problem.

exFat is actually good news, concerning bigger files. But even on exfat it is not possible to have multiple files with the same name but different uppercase/lowercase letters - they would still be treated as the same file! (unlike on linux filesystems for example).
So giving errors for not finding files according to different case sentitivity is simply a dumb design decision.

Perhaps I will go through all the pain again and try to set up recalbox 7.1 on my pi. Lockdown gives me plenty of time anyway. Just looking for the good (no, I don't say "positive" ) things.

No upgrade path from 6.x is very sad
Tried a new install of 7.1 anyway.

• a lot of my bios files which did fine on 6.1 are now invalid - because 7.1 looks for CASE SENSITIVE FILENAMES! Why would you do that on a FAT file system, which has no real case sensitivity? After renaming them, most work. Some are still invalid (PCEngine for example)
• Kodi 18.9 does not connect to my samba share. I don't know why, it works fine with Kodi 17 on RecalBox 6.1...
• My IR remote does not work in Kodi any more (again). Going through the whole IR setup process is too much work for me now ...

so, in the end, too much work for no apparent gain. I'll pass this release. Thanks anyway for the effort.

File found. Edited. Everything fine! Thanks again for the help!

Ah, so it was relocated! Perfect, will test this as soon as possible!

I am missing the file .\share\system.emulationstation\es_systems.cfg

this file defined which emulator or file types get used for the different platforms. It was able to edit this file to, for example, exclude certain file types from the automatic detection (important for PSX-games with individual audio track files, so they are not scraped multiple times) or for defining specific emulator cores for certain platforms (I did that for MAME, so i could combine my arcade and neogeo collections)

Has es_systems.cfg just been relocated or was it removed from the new release on purpose?

@paradadf said in Kodi 17 IR Remote:

@fonzman would you mind creating a Merge Request (MR) on gitlab to add those missing parameters by default?

https://gitlab.com/recalbox/recalbox/blob/master/board/recalbox/fsoverlay/recalbox/scripts/kodilauncher.sh#L49

done

Thank you paradadf, I know this faq.
I followed it some time ago when I configured lirc for Kodi 15 (back with recalbox 3.x or 4.0?), and made updates to Kodi 16.2 (with recalbox 4.1).
As I said, buildroot OS is recognizing my IR inputs also in Recalbox 6.0.
See this from my current setup:
irw
0000000077e1d0e4 00 KEY_UP Appleremote
0000000077e1d0e4 01 KEY_UP Appleremote
0000000077e1b0e4 00 KEY_DOWN Appleremote
0000000077e1b0e4 01 KEY_DOWN Appleremote
0000000077e1e0e4 00 KEY_RIGHT Appleremote
0000000077e1e0e4 01 KEY_RIGHT Appleremote
0000000077e110e4 00 KEY_LEFT Appleremote
0000000077e110e4 01 KEY_LEFT Appleremote
0000000077e110e4 02 KEY_LEFT Appleremote
0000000077e120e4 00 KEY_PLAY Appleremote
0000000077e120e4 01 KEY_PLAY Appleremote
0000000077e140e4 00 KEY_MENU Appleremote
0000000077e140e4 01 KEY_MENU Appleremote

only in Kodi no button presses are registered. And as I wrote in my last post, Kodi 16.2 (on Recalbox 4.1) has these 2 lines in the kodi.log:
14:03:48 T:1836053472 INFO: LIRC Process: using: /var/run/lirc/lircd
14:03:48 T:1836053472 INFO: LIRC Connect: successfully started

But they are missing from the kodi.log in Kodi 17.6 under Recalbox 6.0!

For me it seems Kodi starts without LIRC support. Can I somehow enable it? What does Recalbox exactly do when I press "Start Kodi" in the emulationstation-menu?

SOLVED!!

On Recalbox 6.0 Kodi 17.6 does ACTUALLY start without IR support! To rectify this, follow these steps:

• ssh to your recalbox
• make your system writeable with mount -o remount,rw /
• edit line 49 in /recalbox/scripts/kodilauncher.sh to look like this (changes are bold):
  LD_LIBRARY_PATH="/usr/lib/mysql" /usr/lib/kodi/kodi.bin --standalone -fs --lircdev /var/run/lirc/lircd
• restart

Just analyzed my kodi.log from 16.1 vs. 17.6 and found this:

in Kodi 16.1 this is present:
14:03:48 T:1836053472 INFO: LIRC Process: using: /var/run/lirc/lircd
14:03:48 T:1836053472 INFO: LIRC Connect: successfully started

...but missing from Kodi 17.6
Seems 17.6 is actually missing/not looking for the LIRC/IR driver!

I also have a problem with my IR remote.

I made all the preparations (which work fine in Recalbox 4.1 with Kodi 16.1):
dtoverlay=lirc-rpi in /boot/config.txt is active
/recalbox/share/system/.config/lirc/lircd.conf exists
irw recognizes my IR inputs
/recalbox/share/system/.kodi/userdata/keymaps/remote.xml is the default from Kodi 17.6
/recalbox/share/system/.kodi/userdata/Lircmap.xml did not change since upgrade (and thus should work)

Still, Kodi ignores my IR remote. Is it possible that the Kodi-Version on 6.0 DragonBlaze was compiled without IR support?

Danke @Strykjar für die Lösung! Hatte das selbe Problem und habs jetzt nach deiner Anleitung geändert und jetzt funktioniert wieder alles!