IR Remote for Cloudshell/dietpi

[noobs4u]

I have the cloudshell case for my XU4 with dietpi installed. I also have cloudshell and the lirc package installed. I am unable to get the IR remote to work at all even after going through the config screen and selecting it to install the hardkernel remote. Is there further configurations that need to be done for it to work with the LCD on the cloudshell?

[odroid]

http://odroid.com/dokuwiki/doku.php?id= ... _ir_config
Any log file?

[noobs4u]

http://odroid.com/dokuwiki/doku.php?id= ... _ir_config
Any log file?

Already did that. Using Hardkernel IR remote. Followed the prompts and installed the defaults for the Hardkernel remote which should be already configured. And as far as a log file is concerned, I wouldn't even know where to look. Could you provide a general directory that I should start in? I'm running dietpi currently.

[odroid]

Check the output of "lsmod" command.
There should be below two modules.
gpio-ir-recv
gpioplug-ir-recv

And you can find "/dev/lirc0" device node.

[noobs4u]

Check the output of "lsmod" command.
There should be below two modules.
gpio-ir-recv
gpioplug-ir-recv

And you can find "/dev/lirc0" device node.

Code: Select all

root@DietPi:~# lsmod
Module                  Size  Used by
xt_multiport            1607  2
iptable_filter          1475  1
ip_tables              12007  1 iptable_filter
cdc_ether               4507  0
usbnet                 22217  1 cdc_ether
r8152                  53236  0
ina231_sensor           8388  0
i2c_s3c2410             8876  0
fb_ili9340              3597  1
ir_lirc_codec           4034  0
lirc_dev                9711  1 ir_lirc_codec
gpioplug_ir_recv        1176  0
gpio_ir_recv            2874  0
fbtft_device           37972  0
fbtft                  31765  2 fb_ili9340,fbtft_device
syscopyarea             3057  1 fbtft
sysfillrect             3400  1 fbtft
sysimgblt               2147  1 fbtft
fb_sys_fops             1348  1 fbtft
spi_s3c64xx            13713  0
fuse                   75445  1
root@DietPi:~#

Code: Select all

root@DietPi:/dev# ls
lirc0               ptyd7  ptysc  ptyy1     tty45  ttydd  ttySAC3  ttyxf
lircd               ptyd8  ptysd  ptyy2     tty46  ttyde  ttysb    ttyy0
log                 ptyd9  ptyse  ptyy3     tty47  ttydf  ttysc    ttyy1

[odroid]

Looks fine for me.

Same configuration worked well on our Ubuntu image.
You need to report this issue on the DietPi thread.

I think below two lines might not be compatible with DietPi or Debian image if the lirc demon doesn't work correctly.
https://github.com/mdrjr/cloudshell_ir/ ... _ir.sh#L39
https://github.com/mdrjr/cloudshell_ir/ ... _ir.sh#L51

[noobs4u]

Looks fine for me.

Same configuration worked well on our Ubuntu image.
You need to report this issue on the DietPi thread.

I think below two lines might not be compatible with DietPi or Debian image if the lirc demon doesn't work correctly.
https://github.com/mdrjr/cloudshell_ir/ ... _ir.sh#L39
https://github.com/mdrjr/cloudshell_ir/ ... _ir.sh#L51

I posted this over at the dietpi forum: http://fuzon.co.uk/phpbb/viewtopic.php?f=11&t=376. Hopefully Fourdee will be able to take a look.

[Fourdee]

Looks fine for me.

Same configuration worked well on our Ubuntu image.
You need to report this issue on the DietPi thread.

I think below two lines might not be compatible with DietPi or Debian image if the lirc demon doesn't work correctly.
https://github.com/mdrjr/cloudshell_ir/ ... _ir.sh#L39
https://github.com/mdrjr/cloudshell_ir/ ... _ir.sh#L51

Looks like the configuration vars are different compared to whats expected by the install script. None of the items listed below are in the Jessie config after installation (/etc/lirc/hardware.conf). So none of these get applied:
https://github.com/mdrjr/cloudshell_ir/ ... sh#L32-L36

Code: Select all

root@DietPi-XU4:~# cat /etc/lirc/hardware.conf
# /etc/lirc/hardware.conf
#
# Arguments which will be used when launching lircd
LIRCD_ARGS=""

#Don't start lircmd even if there seems to be a good config file
#START_LIRCMD=false

#Don't start irexec, even if a good config file seems to exist.
#START_IREXEC=false

#Try to load appropriate kernel modules
LOAD_MODULES=true

# Run "lircd --driver=help" for a list of supported drivers.
DRIVER="/dev/lirc0"
# usually /dev/lirc0 is the correct setting for systems using udev
DEVICE=""
MODULES=""

# Default configuration files for your hardware if any
LIRCD_CONF=""
LIRCMD_CONF=""

The Odroid remote hw config file does get applied correctly: https://github.com/mdrjr/cloudshell_ir/ ... sh#L51-L82

As far as I can tell the IR receiver is working (press a few buttons then ctrl+c to exit):

Code: Select all

cat /dev/lirc0

I'am pretty sure the lirc daemon isnt running either due to the missing configuration settings, can you paste results noobs4u?

Code: Select all

systemctl status lirc -l

So it looks like an issue with the configuration side of lirc. I'll boot up Ubuntu on my XU4 and compare lirc installation and configuration.

[Fourdee]

I think it may be an issue with the service script (/etc/init.d/lirc). I couldn't get the service to launch, even with bare minimal settings and using a remote template in

Code: Select all

/usr/share/lirc/remotes/

Noobs4u, please try the following after you run https://raw.githubusercontent.com/mdrjr ... tall_ir.sh , then test your device:

Code: Select all

/usr/sbin/lircd --driver=default --device=/dev/lirc0 --uinput

[studioai]

I think it may be an issue with the service script (/etc/init.d/lirc). I couldn't get the service to launch, even with bare minimal settings and using a remote template in

Code: Select all

/usr/share/lirc/remotes/

Noobs4u, please try the following after you run https://raw.githubusercontent.com/mdrjr ... tall_ir.sh , then test your device:

Code: Select all

/usr/sbin/lircd --driver=default --device=/dev/lirc0 --uinput

I have same problem, In my case

after run lircd by

Code: Select all

/usr/sbin/lircd --driver=default --device=/dev/lirc0 --uinput

irw works normally

but

after starting lirc service by

Code: Select all

systemctl start lirc

irw doesn't work

should I create custom lircd.service for systemd?

[noobs4u]

I think it may be an issue with the service script (/etc/init.d/lirc). I couldn't get the service to launch, even with bare minimal settings and using a remote template in

Code: Select all

/usr/share/lirc/remotes/

Noobs4u, please try the following after you run https://raw.githubusercontent.com/mdrjr ... tall_ir.sh , then test your device:

Code: Select all

/usr/sbin/lircd --driver=default --device=/dev/lirc0 --uinput

Well, it definitely had results. It messed the LCD screen up really good. Nothing a restart couldn't fix though. It seemed to want to navigate through dietpi-config but the cloudshell was also displaying over the top of it at the same time. After rebooting, the remote was rendered useless and the cloudshell LCD was back to normal. The results you requested earlier:

Code: Select all

root@PlexMedia:~# systemctl status lirc -l
● lirc.service - LSB: Starts LIRC daemon.
   Loaded: loaded (/etc/init.d/lirc)
   Active: active (exited) since Sun 2016-04-24 02:37:38 BST; 10min ago
  Process: 640 ExecStart=/etc/init.d/lirc start (code=exited, status=0/SUCCESS)

Apr 24 02:37:38 PlexMedia lirc[640]: srm7500libusb
Apr 24 02:37:38 PlexMedia lirc[640]: tira
Apr 24 02:37:38 PlexMedia lirc[640]: tira_raw
Apr 24 02:37:38 PlexMedia lirc[640]: udp
Apr 24 02:37:38 PlexMedia lirc[640]: uirt2
Apr 24 02:37:38 PlexMedia lirc[640]: uirt2_raw
Apr 24 02:37:38 PlexMedia lirc[640]: usb_uirt_raw
Apr 24 02:37:38 PlexMedia lirc[640]: usbx
Apr 24 02:37:38 PlexMedia systemd[1]: Started LSB: Starts LIRC daemon..
Apr 24 02:37:38 PlexMedia lirc[640]: .
root@PlexMedia:~#

[Fourdee]

I have same problem, In my case

after run lircd by

Code: Select all

/usr/sbin/lircd --driver=default --device=/dev/lirc0 --uinput

irw works normally

but

after starting lirc service by

Code: Select all

systemctl start lirc

irw doesn't work

should I create custom lircd.service for systemd?

Interesting, so it appears there is a bug in the service script installed by Lirc on Jessie. Basically rendering the service unusable.
If you do make a systemd service script, post it here and I will test it on my XU4 also.

[Fourdee]

Code: Select all

root@PlexMedia:~# systemctl status lirc -l
● lirc.service - LSB: Starts LIRC daemon.
   Loaded: loaded (/etc/init.d/lirc)
   Active: active (exited) since Sun 2016-04-24 02:37:38 BST; 10min ago
  Process: 640 ExecStart=/etc/init.d/lirc start (code=exited, status=0/SUCCESS)

Apr 24 02:37:38 PlexMedia lirc[640]: srm7500libusb
Apr 24 02:37:38 PlexMedia lirc[640]: tira
Apr 24 02:37:38 PlexMedia lirc[640]: tira_raw
Apr 24 02:37:38 PlexMedia lirc[640]: udp
Apr 24 02:37:38 PlexMedia lirc[640]: uirt2
Apr 24 02:37:38 PlexMedia lirc[640]: uirt2_raw
Apr 24 02:37:38 PlexMedia lirc[640]: usb_uirt_raw
Apr 24 02:37:38 PlexMedia lirc[640]: usbx
Apr 24 02:37:38 PlexMedia systemd[1]: Started LSB: Starts LIRC daemon..
Apr 24 02:37:38 PlexMedia lirc[640]: .
root@PlexMedia:~#

Thanks. Yep, I thought as much, the service says active but the daemon is not running (exited).

Well, it definitely had results. It messed the LCD screen up really good. Nothing a restart couldn't fix though. It seemed to want to navigate through dietpi-config but the cloudshell was also displaying over the top of it at the same time. After rebooting, the remote was rendered useless and the cloudshell LCD was back to normal.

Interesting. You can stop/start dietpi-cloudshell at any time by simply running dietpi-cloudshell over SSH.
It might be worth testing the remote in a different environment (eg: kodi), just so we can get an idea if the remote is functional.

[studioai]

Interesting, so it appears there is a bug in the service script installed by Lirc on Jessie. Basically rendering the service unusable.

Sorry I solved this problem by installing ir-keytable. So, there's no systemd script. Sorry !