In the last 24 hours we have replaced lircd with a different version and overhauled the whole remote subsystem, so what you describe above is no longer necessary and is probably not valid now. There is still a bit more work to be done but in short:
- Make sure you check for and install updates so the latest lirc and eventlircd packages are installed.
- Save your lircd.conf at /home/osmc/lircd.conf
- If you have a Pi 1 enable GPIO IR remote support in hardware in the OSMC Settings addon, then reboot.
Your remote should now work, but be aware that your lircd.conf key names should adhere to linux-input-layer naming conventions - such as KEY_OK, KEY_UP and so on. (For an example look at /etc/lirc/osmc-remote-lircd.conf)
Currently loading the GPIO module from the hardware support option in the Settings addon is not working on the Pi 2 - but should be working for Alpha 5.
For a quick and dirty hack to load the lirc_rpi module on boot for a Pi 2 you can add the following to /etc/rc.local just before the exit 0 line:
modprobe lirc_rpi