Quantcast

Re: lirc installation on raspberry pi running Raspbian jessie

classic Classic list List threaded Threaded
22 messages Options
12
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: lirc installation on raspberry pi running Raspbian jessie

mailing.list
 
 
Gesendet: Freitag, 08. Januar 2016 um 13:58 Uhr
Von: "Alec Leamas" <[hidden email]>
 
On 08/01/16 13:04, [hidden email] wrote:
> Hi,
> I'm having trouble installing lirc on a raspberry pi running debian jessie.
> With the packaged (old) version 0.9.0, sending via command line tools
> irsend and receiving from a c program works, but I require sending from
> a c program using lirc_client API, so I would like to upgrade to >= 0.9.2.
> I tried to follow http://www.lirc.org/html/install.html, with and
> without --prefix=/usr, without it appears everything gets installed but
> not in "default" paths, it seems "not properly" installed (pardon my
> missing expertise),

Yep, as noted in the installation docs most of the examples presume
--prefix=/usr. "Not properly" in perhaps not the correct statement, it's
more like that this setup isn't documented. The manpages should be OK,
though.

> with I get multiple errors during install, such as
> Makefile:614: recipe for target 'install-recursive' failed
> make[1]: *** [install-recursive] Error 1

There should certainly be no such failures... something is very broken
in your build.

Here is two routes:

- You could try the preliminary 0.9.4 debian packages available using
dget [1].
- We could try to sort out the build. Please post (a link to) a
complete build log.

Cheers!

-alec

[1] dget -x
http://mentors.debian.net/debian/pool/main/l/lirc/lirc_0.9.4~pre1-1.1.dsc

 
 
Thanks for your response! I started down the "preliminary 0.9.4 package" route. Following the instructions on https://wiki.debian.org/DebianMentorsFaq#How_do_I_install_a_package_from_mentor.debian.net.3F , I was successful until the "debuild -us -uc" step, which exited with a fatal error. I'll post the complete log below. Any advice? Much appreciated!
 
Regards
 
Val
 
 
pi@raspberrypi:~/lirc-0.9.4~pre1 $ debuild -us -uc
 dpkg-buildpackage -rfakeroot -D -us -uc
dpkg-buildpackage: Quellpaket lirc
dpkg-buildpackage: Quellversion 0.9.4~pre1-1.1
dpkg-buildpackage: Quelldistribution experimental
dpkg-buildpackage: Quellen geändert durch Alec Leamas  <[hidden email]>
 dpkg-source --before-build lirc-0.9.4~pre1
dpkg-buildpackage: Host-Architektur armhf
 fakeroot debian/rules clean
dh clean --with autoreconf --with python3 --with-systemd
   dh_testdir -O--with-systemd
   dh_auto_clean -O--with-systemd
   dh_autoreconf_clean -O--with-systemd
   dh_clean -O--with-systemd
 dpkg-source -b lirc-0.9.4~pre1
dpkg-source: Information: Quellformat »3.0 (quilt)« wird verwendet
dpkg-source: Information: lirc wird unter Benutzung des existierenden ./lirc_0.9.4~pre1.orig.tar.gz gebaut
dpkg-source: Information: lirc wird in lirc_0.9.4~pre1-1.1.debian.tar.xz gebaut
dpkg-source: Information: lirc wird in lirc_0.9.4~pre1-1.1.dsc gebaut
 debian/rules build
dh build --with autoreconf --with python3 --with-systemd
   dh_testdir -O--with-systemd
   debian/rules override_dh_autoreconf
make[1]: Entering directory '/home/pi/lirc-0.9.4~pre1'
dh_autoreconf /home/pi/lirc-0.9.4~pre1/autogen.sh
libtoolize: putting auxiliary files in `.'.
libtoolize: copying file `./ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIR, `m4'.
libtoolize: copying file `m4/libtool.m4'
libtoolize: copying file `m4/ltoptions.m4'
libtoolize: copying file `m4/ltsugar.m4'
libtoolize: copying file `m4/ltversion.m4'
libtoolize: copying file `m4/lt~obsolete.m4'
configure.ac:40: installing './config.guess'
configure.ac:40: installing './config.sub'
configure.ac:9: installing './install-sh'
configure.ac:9: installing './missing'
daemons/Makefile.am: installing './depcomp'
make[1]: Leaving directory '/home/pi/lirc-0.9.4~pre1'
   dh_auto_configure -O--with-systemd
configure: WARNING: unrecognized options: --disable-maintainer-mode
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking whether gcc understands -c and -o together... yes
checking for style of include used by make... GNU
checking dependency style of gcc... none
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... none
checking whether make sets $(MAKE)... (cached) yes
checking for sh... /bin/sh
checking for modinfo... modinfo
checking for pkg-config... yes
checking for xsltproc... yes
checking for man2html... yes
checking for doxygen... yes
checking whether ln -s works... yes
checking build system type... arm-unknown-linux-gnueabihf
checking host system type... arm-unknown-linux-gnueabihf
checking how to print strings... printf
checking for a sed that does not truncate output... /bin/sed
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for fgrep... /bin/grep -F
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking the maximum length of command line arguments... 1572864
checking whether the shell understands some XSI constructs... yes
checking whether the shell understands "+="... yes
checking how to convert arm-unknown-linux-gnueabihf file names to arm-unknown-linux-gnueabihf format... func_convert_file_noop
checking how to convert arm-unknown-linux-gnueabihf file names to toolchain format... func_convert_file_noop
checking for /usr/bin/ld option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for dlltool... no
checking how to associate runtime and link libraries... printf %s\n
checking for ar... ar
checking for archiver @FILE support... @
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for sysroot... no
checking for mt... mt
checking if mt is a manifest tool... no
checking how to run the C preprocessor... gcc -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for dlfcn.h... yes
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker (/usr/bin/ld) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... no
checking how to run the C++ preprocessor... g++ -E
checking for ld used by g++... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes
checking for g++ option to produce PIC... -fPIC -DPIC
checking if g++ PIC flag -fPIC -DPIC works... yes
checking if g++ static flag -static works... yes
checking if g++ supports -c -o file.o... yes
checking if g++ supports -c -o file.o... (cached) yes
checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes
checking dynamic linker characteristics... (cached) GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking for a Python interpreter with version >= 3.1... python3
checking for python3... /usr/bin/python3
checking for python3 version... 3.4
checking for python3 platform... linux
checking for python3 script directory... ${prefix}/lib/python3.4/site-packages
checking for python3 extension module directory... ${exec_prefix}/lib/python3.4/site-packages
checking for python3... yes
checking for ANSI C header files... (cached) yes
checking whether time.h and sys/time.h may both be included... yes
checking fcntl.h usability... yes
checking fcntl.h presence... yes
checking for fcntl.h... yes
checking limits.h usability... yes
checking limits.h presence... yes
checking for limits.h... yes
checking sys/ioctl.h usability... yes
checking sys/ioctl.h presence... yes
checking for sys/ioctl.h... yes
checking sys/time.h usability... yes
checking sys/time.h presence... yes
checking for sys/time.h... yes
checking syslog.h usability... yes
checking syslog.h presence... yes
checking for syslog.h... yes
checking for unistd.h... (cached) yes
checking util.h usability... no
checking util.h presence... no
checking for util.h... no
checking libutil.h usability... no
checking libutil.h presence... no
checking for libutil.h... no
checking pty.h usability... yes
checking pty.h presence... yes
checking for pty.h... yes
checking for an ANSI C-conforming const... yes
checking for inline... inline
checking for off_t... yes
checking for pid_t... yes
checking for size_t... yes
checking whether struct tm is in sys/time.h or time.h... time.h
checking return type of signal handlers... void
checking for vprintf... yes
checking for _doprnt... no
checking for gethostname... yes
checking for gettimeofday... yes
checking for mkfifo... yes
checking for select... yes
checking for socket... yes
checking for strdup... yes
checking for strerror... yes
checking for strtoul... yes
checking for snprintf... yes
checking for strsep... yes
checking for vsyslog... yes
checking for daemon... yes
checking python3 module: yaml... yes
checking for forkpty... no
checking for forkpty in -lutil... yes
checking for X... libraries , headers
checking for gethostbyname... yes
checking for connect... yes
checking for remove... yes
checking for shmat... yes
checking for IceConnectionNumber in -lICE... yes
checking for getopt_long... yes
checking for which drivers can be installed on this system...
checking usb.h usability... no
checking usb.h presence... no
checking for usb.h... no
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for FTDI... no
checking for FTDI... no
checking portaudio.h usability... no
checking portaudio.h presence... no
checking for portaudio.h... no
checking alsa/asoundlib.h usability... yes
checking alsa/asoundlib.h presence... yes
checking for alsa/asoundlib.h... yes
checking for snd_pcm_open in -lasound... yes
checking for ALSA SB RC hwdep support... yes
checking linux/input.h usability... yes
checking linux/input.h presence... yes
checking for linux/input.h... yes
checking linux/lirc.h usability... no
checking linux/lirc.h presence... no
checking for linux/lirc.h... no
checking scsi/sg.h usability... yes
checking scsi/sg.h presence... yes
checking for scsi/sg.h... yes
checking for linux/input.h... (cached) yes
checking linux/types.h usability... yes
checking linux/types.h presence... yes
checking for linux/types.h... yes
checking for linux/hiddev.h... yes
checking for HIDDEV_FLAG_UREF support... yes
checking sys/soundcard.h usability... yes
checking sys/soundcard.h presence... yes
checking for sys/soundcard.h... yes
checking linux/i2c-dev.h usability... yes
checking linux/i2c-dev.h presence... yes
checking for linux/i2c-dev.h... yes
checking for SYSTEMD... no
checking systemd system unit directory... /lib/systemd/system
 
(rest of log in 2nd message)
 
 

------------------------------------------------------------------------------
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: lirc installation on raspberry pi running Raspbian jessie

mailing.list
(rest of log)
 
configure: Building all userspace drivers.
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating VERSION
config.status: creating Makefile
config.status: creating lirc.pc
config.status: creating lirc-driver.pc
config.status: WARNING:  'lirc-driver.pc.in' seems to ignore the --datarootdir setting
config.status: creating daemons/Makefile
config.status: creating plugins/Makefile
config.status: creating tools/Makefile
config.status: creating lib/Makefile
config.status: creating doc/Makefile
config.status: creating configs/Makefile
config.status: creating doc/docpage.xsl
config.status: creating systemd/Makefile
config.status: creating config.h
config.status: executing depfiles commands
config.status: executing libtool commands
configure: WARNING: unrecognized options: --disable-maintainer-mode
Summary of selected options:
----------------------------------------
prefix:                         /usr
sysconfdir:                     /etc
x_progs:                        irxevent xmode2
host:                           arm-unknown-linux-gnueabihf
host_os:                        linux-gnueabihf
forkpty:                        -lutil
usb_libs
lockdir:                        /var/lock/lockdev
Conditionals:
BUILD_ALSA_SB_RC:yes
BUILD_DSP:yes
BUILD_FTDI:no
BUILD_HIDDEV:yes
BUILD_I2CUSER:yes
BUILD_LIBALSA:yes
BUILD_IGUANAIR:yes
BUILD_LIBPORTAUDIO:no
BUILD_USB:no
BUILD_XTOOLS:yes
HAVE_DOXYGEN:yes
HAVE_MAN2HTML:yes
HAVE_PYMOD_YAML:yes
INSTALL_ETC:yes
NEED_PYTHON3:no
SYSTEMD_INSTALL:yes
DEVEL:yes

Now enter 'make' and 'make install' to compile and install the package.
   dh_auto_build -O--with-systemd
make[1]: Entering directory '/home/pi/lirc-0.9.4~pre1'
make  all-recursive
make[2]: Entering directory '/home/pi/lirc-0.9.4~pre1'
Making all in lib
make[3]: Entering directory '/home/pi/lirc-0.9.4~pre1/lib'
../tools/lirc-make-devinput -i > input_map.inc
../tools/lirc-make-devinput -i > lirc/input_map.inc
make  all-am
make[4]: Entering directory '/home/pi/lirc-0.9.4~pre1/lib'
/bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. -I..  -I.. -Wall -Wp,-D_FORTIFY_SOURCE=2  -D_FORTIFY_SOURCE=2  -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -c -o config_file.lo config_file.c
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -I.. -Wall -Wp,-D_FORTIFY_SOURCE=2 -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -c config_file.c  -fPIC -DPIC -o .libs/config_file.o
/bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. -I..  -I.. -Wall -Wp,-D_FORTIFY_SOURCE=2  -D_FORTIFY_SOURCE=2  -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -c -o ciniparser.lo ciniparser.c
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -I.. -Wall -Wp,-D_FORTIFY_SOURCE=2 -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -c ciniparser.c  -fPIC -DPIC -o .libs/ciniparser.o
/bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. -I..  -I.. -Wall -Wp,-D_FORTIFY_SOURCE=2  -D_FORTIFY_SOURCE=2  -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -c -o dictionary.lo dictionary.c
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -I.. -Wall -Wp,-D_FORTIFY_SOURCE=2 -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -c dictionary.c  -fPIC -DPIC -o .libs/dictionary.o
/bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. -I..  -I.. -Wall -Wp,-D_FORTIFY_SOURCE=2  -D_FORTIFY_SOURCE=2  -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -c -o driver.lo driver.c
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -I.. -Wall -Wp,-D_FORTIFY_SOURCE=2 -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -c driver.c  -fPIC -DPIC -o .libs/driver.o
/bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. -I..  -I.. -Wall -Wp,-D_FORTIFY_SOURCE=2  -D_FORTIFY_SOURCE=2  -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -c -o drv_admin.lo drv_admin.c
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -I.. -Wall -Wp,-D_FORTIFY_SOURCE=2 -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -c drv_admin.c  -fPIC -DPIC -o .libs/drv_admin.o
/bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. -I..  -I.. -Wall -Wp,-D_FORTIFY_SOURCE=2  -D_FORTIFY_SOURCE=2  -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -c -o dump_config.lo dump_config.c
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -I.. -Wall -Wp,-D_FORTIFY_SOURCE=2 -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -c dump_config.c  -fPIC -DPIC -o .libs/dump_config.o
/bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. -I..  -I.. -Wall -Wp,-D_FORTIFY_SOURCE=2  -D_FORTIFY_SOURCE=2  -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -c -o input_map.lo input_map.c
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -I.. -Wall -Wp,-D_FORTIFY_SOURCE=2 -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -c input_map.c  -fPIC -DPIC -o .libs/input_map.o
/bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. -I..  -I.. -Wall -Wp,-D_FORTIFY_SOURCE=2  -D_FORTIFY_SOURCE=2  -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -c -o ir_remote.lo ir_remote.c
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -I.. -Wall -Wp,-D_FORTIFY_SOURCE=2 -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -c ir_remote.c  -fPIC -DPIC -o .libs/ir_remote.o
/bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. -I..  -I.. -Wall -Wp,-D_FORTIFY_SOURCE=2  -D_FORTIFY_SOURCE=2  -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -c -o lirc_log.lo lirc_log.c
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -I.. -Wall -Wp,-D_FORTIFY_SOURCE=2 -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -c lirc_log.c  -fPIC -DPIC -o .libs/lirc_log.o
/bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. -I..  -I.. -Wall -Wp,-D_FORTIFY_SOURCE=2  -D_FORTIFY_SOURCE=2  -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -c -o lirc_options.lo lirc_options.c
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -I.. -Wall -Wp,-D_FORTIFY_SOURCE=2 -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -c lirc_options.c  -fPIC -DPIC -o .libs/lirc_options.o
lirc_options.c: In function 'parse_O_arg':
lirc_options.c:88:2: error: 'for' loop initial declarations are only allowed in C99 or C11 mode
  for (int i = 0; i < argc; i += 1) {
  ^
lirc_options.c:88:2: note: use option -std=c99, -std=gnu99, -std=c11 or -std=gnu11 to compile your code
Makefile:582: recipe for target 'lirc_options.lo' failed
make[4]: *** [lirc_options.lo] Error 1
make[4]: Leaving directory '/home/pi/lirc-0.9.4~pre1/lib'
Makefile:457: recipe for target 'all' failed
make[3]: *** [all] Error 2
make[3]: Leaving directory '/home/pi/lirc-0.9.4~pre1/lib'
Makefile:630: recipe for target 'all-recursive' failed
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory '/home/pi/lirc-0.9.4~pre1'
Makefile:426: recipe for target 'all' failed
make[1]: *** [all] Error 2
make[1]: Leaving directory '/home/pi/lirc-0.9.4~pre1'
dh_auto_build: make -j1 returned exit code 2
debian/rules:20: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: Fehler: Fehler-Exitstatus von debian/rules build war 2
debuild: fatal error at line 1376:
dpkg-buildpackage -rfakeroot -D -us -uc failed
 

------------------------------------------------------------------------------
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: lirc installation on raspberry pi running Raspbian jessie

Alec Leamas
In reply to this post by mailing.list
On 08/01/16 18:47, [hidden email] wrote:
> *Gesendet:* Freitag, 08. Januar 2016 um 13:58 Uhr
> *Von:* "Alec Leamas" <[hidden email]>

> Thanks for your response! I started down the "preliminary 0.9.4 package"
> route. Following the instructions on
> https://wiki.debian.org/DebianMentorsFaq#How_do_I_install_a_package_from_mentor.debian.net.3F
> , I was successful until the "debuild -us -uc" step, which exited with a
> fatal error. I'll post the complete log below. Any advice? Much appreciated!

My bad... the wrong version was packaged. I have updated the package,
please make a new download and rebuild.

Cheers!

--alec

PS: If you run into problems again, use pastebin.com or some similar
site so you can paste an url to the buildlog instead of splitting it
into several messages. DS


------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: lirc installation on raspberry pi running Raspbian jessie

mailing.list
Gesendet: Freitag, 08. Januar 2016 um 19:50 Uhr
Von: "Alec Leamas" <[hidden email]>

> On 08/01/16 18:47, [hidden email] wrote:
> > *Gesendet:* Freitag, 08. Januar 2016 um 13:58 Uhr
> > *Von:* "Alec Leamas" <[hidden email]>

> > Thanks for your response! I started down the "preliminary 0.9.4 package"
> > route. Following the instructions on
> > https://wiki.debian.org/DebianMentorsFaq#How_do_I_install_a_package_from_mentor.debian.net.3F
> > , I was successful until the "debuild -us -uc" step, which exited with a
> > fatal error. I'll post the complete log below. Any advice? Much appreciated!
>
> My bad... the wrong version was packaged. I have updated the package,
> please make a new download and rebuild.
>
> Cheers!
>
> --alec
>
> PS: If you run into problems again, use pastebin.com or some similar
> site so you can paste an url to the buildlog instead of splitting it
> into several messages. DS
 

Thanks, the updated version of the package fixed that error, now the two command worked:
debuild -us -uc
dpkg -i lirc_0.9.4~pre1.deb

However, trying to follow http://www.lirc.org/html/configuration-guide.html I don't succeed at all, although I had 0.9.0 running fine, so I would appreciate some further advice.

(Since the build error/abort did not occur anymore, I did not record the log. If that's needed, is there a log file generated automatically or alternatively, I could repeat the two commands above and post the log; in that case, should I deinstall before or just install a second time?)

Below, I provide my current status (and what puzzles me) with 0.9.4 and for reference my configuration which worked for 0.9.0, hoping that might help.

Thanks,

Regards,

Val



Status after install of 0.9.4:


There is "/dev/lirc0"

There is no "lirc/lircd" in "/var/run/".
Installation problem or manual configuration steps needed?

There is no subdirectory "lirc" in "/etc/".
Installation problem or manual configuration steps needed?

There is no "lirc" in "/etc/init.d/".

There is no file "~/.config/lircrc"
Do I need to create an empty lircrd file there?



"sudo mode2 --driver default --device /dev/lirc0"
gives error message:
sudo: mode2: Command not found

"lircd --nodaemon --device /dev/lirc0 --driver default"
gives error message:
-bash: lircd: Command not found

"irw"
gives error message:
-bash: irw: Kommando nicht gefunden.

Do I need to do this in a particular directory or is there an installation problem?


The statement in my C program
#include <lirc/lirc_client.h>
gives error during compile
fatal error: lirc/lirc_client.h: file or directory not found



If I understand correctly, I will be using the general approach using LIRC (/var/run/lirc/lircd), because I want so send IR commands.

I have my lircd.conf file which complies with the technical specification of my IR protocol, and worked for receiving IR commands from my C program and for sending IR commands using the command line command "irsend" in 0.9.0.



My 0.9.0 config was as follows:

I added
 
lirc_dev
lirc_rpi gpio_in_pin=23 gpio_out_pin=22

to /etc/modules (still is configured that way).

I had changed /etc/lirc/hardware.conf to

########################################################
# /etc/lirc/hardware.conf
#
# Arguments which will be used when launching lircd
LIRCD_ARGS="--uinput"
 
# 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="default"
# usually /dev/lirc0 is the correct setting for systems using udev
DEVICE="/dev/lirc0"
MODULES="lirc_rpi"
 
# Default configuration files for your hardware if any
LIRCD_CONF=""
LIRCMD_CONF=""
########################################################


I added /boot/config.txt file (still is configured that way):

dtoverlay=lirc-rpi,gpio_in_pin=23,gpio_out_pin=22


In 0.9.0 I had to create an empty lircrd file (touch /etc/lirc/lircrc), although I didn't use that functionality, otherwise LIRC was complaining.


 
 
 
 

------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: lirc installation on raspberry pi running Raspbian jessie

Alec Leamas
On 09/01/16 14:22, [hidden email] wrote:
> Gesendet: Freitag, 08. Januar 2016 um 19:50 Uhr
> Von: "Alec Leamas" <[hidden email]>
>
>> On 08/01/16 18:47, [hidden email] wrote:
>>> *Gesendet:* Freitag, 08. Januar 2016 um 13:58 Uhr
>>> *Von:* "Alec Leamas" <[hidden email]>
>

> dpkg -i lirc_0.9.4~pre1.deb
>
> However, trying to follow http://www.lirc.org/html/configuration-guide.html I don't succeed at all, although I had 0.9.0 running fine, so I would appreciate some further advice.
>
> (Since the build error/abort did not occur anymore, I did not record the log. If that's needed, is there a log file generated automatically or alternatively, I could repeat the two commands above and post the log; in that case, should I deinstall before or just install a second time?)
>
> Below, I provide my current status (and what puzzles me) with 0.9.4 and for reference my configuration which worked for 0.9.0, hoping that might help.

> Status after install of 0.9.4:

First: try 'dpkg -L lirc'. That should list the files of the installed
package. These should  include /etc/lirc, /usr/bin/mode2,
/usr/sbin/lircd and many other files.

You can also list the files in your package: dpkc -c
lirc_0.9.4~pre1.deb. These should be installed.

To make anything work you must also install liblirc0.

>> There is "/dev/lirc0"

OK, this is created by the kernel and reflects some kind of hardware you
have (a USB IR receiver?).

> There is no "lirc/lircd" in "/var/run/".
> Installation problem or manual configuration steps needed?

This is OK, it's created by lircd when started.

> There is no subdirectory "lirc" in "/etc/".
 > Installation problem or manual configuration steps needed?

See above, your installation is not OK.

>
> There is no "lirc" in "/etc/init.d/".

lirc uses systemd, see the configuration guide [1]. So, nothing in
/etc/init.d. Also, note that 0.9.4 does not use hardware.conf.


> There is no file "~/.config/lircrc"
> Do I need to create an empty lircrd file there?

No, it,s a much later issue related to using lirc  wiht e. g., mythtv or
kodi.

> "sudo mode2 --driver default --device /dev/lirc0"
> gives error message:
> sudo: mode2: Command not found

See above, failed installation.

>
> "lircd --nodaemon --device /dev/lirc0 --driver default"
> gives error message:
> -bash: lircd: Command not found

Probably the same, but note that that lircd lives in /usr/sbin which
might not be in your PATH

> "irw"
> gives error message:
> -bash: irw: Kommando nicht gefunden.

Same as mode2


> Do I need to do this in a particular directory or is there an installation problem?


Here is certainly installation problem(s)...


> The statement in my C program
> #include <lirc/lirc_client.h>
> gives error during compile
> fatal error: lirc/lirc_client.h: file or directory not found

You need to install liblirc-dev to get the headers

> If I understand correctly, I will be using the general approach using LIRC (/var/run/lirc/lircd), because I want so send IR commands.
>
> I have my lircd.conf file which complies with the technical specification of my IR protocol, and worked for receiving IR commands from my C program and for sending IR commands using the command line command "irsend" in 0.9.0.

It should work just fine. You could either replace existing
/etc/lirc/lircd.conf or use the preferred solution to just drop it in
/etc/lirc/lirc.conf.d

The installation should also give you a big fat warning about a breaking
upgrade and a hint about a manual upgrade script which yoi seemingly
havn't got (or noticed?). So, agaiun, the installation step seems to
have failed.

Also: have you got the dependencies in place? The lirc packages depends
in liblirc, so it shouldn't really be possible too install just that.
The easiest way might be to just do dpkg -i *.deb, but there can
certainly be unresolved dependencies anyway. But, dpkg should complain
in that case.

Sorry, I'm quite new to Debian packaging and a bit unsure about the
mechanics.

Cheers!

--alec

[1] http://lirc.sourceforge.net/lirc.org/html/configuration-guide.html

------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: lirc installation on raspberry pi running Raspbian jessie

mailing.list
Gesendet: Samstag, 09. Januar 2016 um 16:00 Uhr
Von: "Alec Leamas" <[hidden email]>

> First: try 'dpkg -L lirc'. That should list the files of the installed
> package. These should include /etc/lirc, /usr/bin/mode2,
> /usr/sbin/lircd and many other files.

> You can also list the files in your package: dpkc -c
> lirc_0.9.4~pre1.deb. These should be installed.

> To make anything work you must also install liblirc0.

That was helpful, thanks! Apparently something went wrong first time around, I did the complete install procedure again and now the dependencies are in place, sorry, my bad...


> >> There is "/dev/lirc0"

> OK, this is created by the kernel and reflects some kind of hardware you
> have (a USB IR receiver?).

I'm using a Raspberry Pi. It has GPIO (general purpose input/output) pins (https://www.raspberrypi.org/documentation/hardware/raspberrypi/gpio/README.md), which can be connected to an IR sending diode and an IR receiver. A worked example can be found here (http://www.sunfounder.com/index.php?c=case_incs&a=detail_&id=307&name=Sensor%20Kit%20for%20B+).


Now that the installation succeeded, I followed http://www.lirc.org/html/configuration-guide.html, but I'm experiencing a problem where I can only *once* execute e.g. the IRSEND command (or my C program that transmits an IR signal); from the second time I execute IRSEND, an error occurs. With 0.9.0 I had it working ok.

I believe to have set up everything in 0.9.4 as for the working 0.9.0 configuration ("default" driver, "dev/lirc0" device, "lirc_rpi" kernel module), except for 0.9.0 config option LIRCD_ARGS="--uinput", being depreciated, do I need to do something there? Despite reading the man page, I'm not sure if/how to use lircd-uinput tool. Could that have to do with the problems I'm having?

I'm attaching logs for the problem with first IRSEND (ok) and second IRSEND (error), as well as errors when using lircd as service when starting irw and the configurations im using (0.9.4 and previously working 0.9.0 hardware.conf).

Much appreciate your advice,

Regards,

Val




This is how the lircd looks after first IRSEND command that works:

pi@raspberrypi:~ $ lircd --nodaemon
lircd-0.9.4-devel[3432]: Info: lircd:  Opening log, level: Info
lircd-0.9.4-devel[3432]: Info: Using remote: MP3.
lircd-0.9.4-devel[3432]: Notice: lircd(default) ready, using /var/run/lirc/lircd
lircd-0.9.4-devel[3432]: Notice: accepted new client on /var/run/lirc/lircd
lircd-0.9.4-devel[3432]: Info: Cannot configure the rc device for /dev/lirc0
lircd-0.9.4-devel[3432]: Info: removed client



And this was the corresponding IRSEND command:

pi@raspberrypi:/etc/lirc/lircd.conf.d $ irsend SEND_ONCE MP3 TASTE_ANAUS
pi@raspberrypi:/etc/lirc/lircd.conf.d $



After the second IRSEND command, lircd looks as follows:

lircd-0.9.4-devel[3432]: Notice: accepted new client on /var/run/lirc/lircd
lircd-0.9.4-devel[3432]: Info: Cannot configure the rc device for /dev/lirc0
lircd-0.9.4-devel[3432]: Error: could not open /dev/lirc0
lircd-0.9.4-devel[3432]: default_init(): Device or resource busy
lircd-0.9.4-devel[3432]: Warning: Failed to initialize hardware
lircd-0.9.4-devel[3432]: Error: could not open /dev/lirc0
lircd-0.9.4-devel[3432]: default_init(): Device or resource busy
lircd-0.9.4-devel[3432]: Error: could not set modulation frequency
lircd-0.9.4-devel[3432]: Invalid argument
lircd-0.9.4-devel[3432]: Error: error processing command: SEND_ONCE MP3 TASTE_ANAUS
lircd-0.9.4-devel[3432]: Error: transmission failed
lircd-0.9.4-devel[3432]: Error: could not open /dev/lirc0
lircd-0.9.4-devel[3432]: default_init(): Device or resource busy
lircd-0.9.4-devel[3432]: Info: removed client



And the corresponding IRSEND resulted in this error message:

pi@raspberrypi:/etc/lirc/lircd.conf.d $ irsend SEND_ONCE MP3 TASTE_ANAUS

transmission failed
Error running command: Input/output error
pi@raspberrypi:/etc/lirc/lircd.conf.d $



As suggested by http://www.lirc.org/faq.html, I tried to find out which process might be using /dev/lirc0 and got the following:

pi@raspberrypi:/etc/lirc/lircd.conf.d $ fuser /dev/lirc0
/dev/lirc0:           3432





When I run lircd as a service, I can start, stop, inspect the service ok, but once I start irw, errors occur:

Log for inspecting, running lircd, starting, stoping, starting for test purposes:


pi@raspberrypi:~ $ sudo systemctl status lircd.socket lircd.service
● lircd.socket
   Loaded: loaded (/lib/systemd/system/lircd.socket; disabled)
   Active: inactive (dead)
   Listen: /run/lirc/lircd (Stream)

● lircd.service - LIRC Infrared Signal Decoder
   Loaded: loaded (/lib/systemd/system/lircd.service; disabled)
   Active: inactive (dead)
pi@raspberrypi:~ $ lircd
pi@raspberrypi:~ $ sudo systemctl status lircd.socket lircd.service
● lircd.socket
   Loaded: loaded (/lib/systemd/system/lircd.socket; disabled)
   Active: inactive (dead)
   Listen: /run/lirc/lircd (Stream)

● lircd.service - LIRC Infrared Signal Decoder
   Loaded: loaded (/lib/systemd/system/lircd.service; disabled)
   Active: inactive (dead)
pi@raspberrypi:~ $ sudo systemctl start lircd.socket
pi@raspberrypi:~ $ sudo systemctl status lircd.socket lircd.service
● lircd.socket
   Loaded: loaded (/lib/systemd/system/lircd.socket; disabled)
   Active: active (listening) since Sun 2016-01-10 11:30:55 CET; 2s ago
   Listen: /run/lirc/lircd (Stream)

Jan 10 11:30:55 raspberrypi systemd[1]: Starting lircd.socket.
Jan 10 11:30:55 raspberrypi systemd[1]: Listening on lircd.socket.

● lircd.service - LIRC Infrared Signal Decoder
   Loaded: loaded (/lib/systemd/system/lircd.service; disabled)
   Active: inactive (dead)
pi@raspberrypi:~ $ sudo systemctl stop lircd.socket
pi@raspberrypi:~ $ sudo systemctl status lircd.socket lircd.service
● lircd.socket
   Loaded: loaded (/lib/systemd/system/lircd.socket; disabled)
   Active: inactive (dead)
   Listen: /run/lirc/lircd (Stream)

Jan 10 11:30:55 raspberrypi systemd[1]: Starting lircd.socket.
Jan 10 11:30:55 raspberrypi systemd[1]: Listening on lircd.socket.
Jan 10 11:31:14 raspberrypi systemd[1]: Stopping lircd.socket.
Jan 10 11:31:14 raspberrypi systemd[1]: Closed lircd.socket.

● lircd.service - LIRC Infrared Signal Decoder
   Loaded: loaded (/lib/systemd/system/lircd.service; disabled)
   Active: inactive (dead)
pi@raspberrypi:~ $ sudo systemctl start lircd.socket
pi@raspberrypi:~ $ sudo systemctl status lircd.socket lircd.service
● lircd.socket
   Loaded: loaded (/lib/systemd/system/lircd.socket; disabled)
   Active: active (listening) since Sun 2016-01-10 11:31:31 CET; 2s ago
   Listen: /run/lirc/lircd (Stream)

Jan 10 11:31:31 raspberrypi systemd[1]: Starting lircd.socket.
Jan 10 11:31:31 raspberrypi systemd[1]: Listening on lircd.socket.

● lircd.service - LIRC Infrared Signal Decoder
   Loaded: loaded (/lib/systemd/system/lircd.service; disabled)
   Active: inactive (dead)



Now I run irw, results in an error:


pi@raspberrypi:~ $ irw
read: Connection reset by peer



And inspecting the service again:

pi@raspberrypi:~ $ sudo systemctl status lircd.socket lircd.service -l
● lircd.socket
   Loaded: loaded (/lib/systemd/system/lircd.socket; disabled)
   Active: failed (Result: service-failed-permanent) since Sun 2016-01-10 11:31:45 CET; 57s ago
   Listen: /run/lirc/lircd (Stream)

Jan 10 11:31:31 raspberrypi systemd[1]: Starting lircd.socket.
Jan 10 11:31:31 raspberrypi systemd[1]: Listening on lircd.socket.
Jan 10 11:31:45 raspberrypi systemd[1]: Unit lircd.socket entered failed state.

● lircd.service - LIRC Infrared Signal Decoder
   Loaded: loaded (/lib/systemd/system/lircd.service; disabled)
   Active: failed (Result: start-limit) since Sun 2016-01-10 11:31:45 CET; 57s ago
  Process: 2264 ExecStart=/usr/sbin/lircd --nodaemon (code=exited, status=1/FAILURE)
 Main PID: 2264 (code=exited, status=1/FAILURE)

Jan 10 11:31:45 raspberrypi lircd-0.9.4-devel[2264]: Info: lircd:  Opening log, level: Info
Jan 10 11:31:45 raspberrypi lircd-0.9.4-devel[2264]: Info: Initial device: /dev/lirc0
Jan 10 11:31:45 raspberrypi lircd[2264]: lircd-0.9.4-devel[2264]: Info: lircd:  Opening log, level: Info
Jan 10 11:31:45 raspberrypi lircd[2264]: lircd: there seems to already be a lircd process with pid 2152
Jan 10 11:31:45 raspberrypi lircd[2264]: lircd: otherwise delete stale lockfile /var/run/lirc/lircd.pid
Jan 10 11:31:45 raspberrypi systemd[1]: lircd.service: main process exited, code=exited, status=1/FAILURE
Jan 10 11:31:45 raspberrypi systemd[1]: Unit lircd.service entered failed state.
Jan 10 11:31:45 raspberrypi systemd[1]: Starting LIRC Infrared Signal Decoder...
Jan 10 11:31:45 raspberrypi systemd[1]: lircd.service start request repeated too quickly, refusing to start.
Jan 10 11:31:45 raspberrypi systemd[1]: Failed to start LIRC Infrared Signal Decoder.



This is my config 0.9.4 file:

pi@raspberrypi:/etc/lirc $ cat lirc_options.conf
# These are the default options to lircd, if installed as
# /etc/lirc/lirc_options.conf. See the lircd(8) and lircmd(8)
# manpages for info on the different options.
#
# Some tools including mode2 and irw uses values such as
# driver, device, plugindir and loglevel as fallback values
# in not defined elsewhere.

[lircd]
nodaemon        = False

#driver          = devinput
#raspi-config
driver          = default

#device          = auto
#raspi-config
device          = /dev/lirc0

output          = /var/run/lirc/lircd
pidfile         = /var/run/lirc/lircd.pid
plugindir       = /usr/lib/arm-linux-gnueabihf/lirc/plugins
permission      = 666
allow-simulate  = No
repeat-max      = 600
#effective-user =
#listen         = [address:]port
#connect        = host[:port]
#debug          = 6
#uinput         = ...
#release        = ...
#logfile        = ...

[lircmd]
uinput          = False
nodaemon        = False

[modinit]
# code = modprobe lirc_serial

# raspi-config
code = modprobe lirc_rpi
code = modprobe lirc_dev




For reference, this was my 0.9.0 hardware.conf file:


########################################################
# /etc/lirc/hardware.conf
#
# Arguments which will be used when launching lircd
LIRCD_ARGS="--uinput"
 
# 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="default"
# usually /dev/lirc0 is the correct setting for systems using udev
DEVICE="/dev/lirc0"
MODULES="lirc_rpi"
 
# Default configuration files for your hardware if any
LIRCD_CONF=""
LIRCMD_CONF=""
########################################################


------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: lirc installation on raspberry pi running Raspbian jessie

Alec Leamas
In reply to this post by mailing.list

On 10/01/16 13:52, [hidden email] wrote:
> Gesendet: Samstag, 09. Januar 2016 um 16:00 Uhr
> Von: "Alec Leamas" <[hidden email]>
>

> That was helpful, thanks! Apparently something went wrong first time around, I did the complete install procedure again and now the dependencies are in place, sorry, my bad...
>

> Now that the installation succeeded, I followed http://www.lirc.org/html/configuration-guide.html, but I'm experiencing a problem where I can only *once* execute e.g. the IRSEND command (or my C program that transmits an IR signal); from the second time I execute IRSEND, an error occurs. With 0.9.0 I had it working ok.
>
> I believe to have set up everything in 0.9.4 as for the working 0.9.0 configuration ("default" driver, "dev/lirc0" device, "lirc_rpi" kernel module), except for 0.9.0 config option LIRCD_ARGS="--uinput", being depreciated, do I need to do something there? Despite reading the man page, I'm not sure if/how to use lircd-uinput tool. Could that have to do with the problems I'm having?
>
> I'm attaching logs for the problem with first IRSEND (ok) and second IRSEND (error), as well as errors when using lircd as service when starting irw and the configurations im using (0.9.4 and previously working 0.9.0 hardware.conf).
>
> Much appreciate your advice,
>
> Regards,
>
> Val
>

We need better logs. Set the debug level to 'debug' in lirc_options.conf
(uncomment the line), restart lircd.service and then run irw which
seemingly makes lircd die. Then check the logs using

$ journalctl -b0 /usr/sbin/lircd

which hopefully will give us a better hint. Post (a link to) the log
which hopefully gives us more info.

If you have problems using the new journalctl stuff you can also set the
logfile option in lirc_options.conf. This makes lircd log to the file
instead of using syslog (which now goes to the systemd journal).


Cheers!

--alec





------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: lirc installation on raspberry pi running Raspbian jessie

Alec Leamas
In reply to this post by mailing.list
On 10/01/16 14:48, Alec Leamas wrote:

> We need better logs. Set the debug level to 'debug' in lirc_options.conf
> (uncomment the line), restart lircd.service and then run irw which
> seemingly makes lircd die. Then check the logs using

Also, please check dmesg to see if the kernel module is unhappy. Perhaps
the lirc_rpi module has some logging options? 'modinfo lirc_rpi' should
tell.


Cheers!

--alec


------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Aw: Re: lirc installation on raspberry pi running Raspbian jessie

mailing.list
 
Gesendet: Sonntag, 10. Januar 2016 um 14:54 Uhr
Von: "Alec Leamas" <[hidden email]>
 
On 10/01/16 14:48, Alec Leamas wrote:

> We need better logs. Set the debug level to 'debug' in lirc_options.conf
> (uncomment the line), restart lircd.service and then run irw which
> seemingly makes lircd die. Then check the logs using

Also, please check dmesg to see if the kernel module is unhappy. Perhaps
the lirc_rpi module has some logging options? 'modinfo lirc_rpi' should
tell.


Cheers!

--alec
 
 
The following commands
 
pi@raspberrypi:~ $ lircd
pi@raspberrypi:~ $ sudo systemctl start lircd.socket
pi@raspberrypi:~ $ irw
read: Connection reset by peer
 
resulted in the following lirc log (I used the logfile option): http://pastebin.com/2Z2PEjjM
Not helpful I'm afraid??
 
And here is the dmesg log: http://pastebin.com/TVthwMY4
 
And lirc_rpi modinfo: http://pastebin.com/GHBZN3zu
 
I changed the /etc/modules entry to
 
lirc_dev
lirc_rpi gpio_in_pin = 23 gpio_out_pin = 22 debug = 1
 
to enable debug. Where can the debug output expected to be found?
 
Thanks
 
Val
 
 
 
 
 
 
 

------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Aw: Re: lirc installation on raspberry pi running Raspbian jessie

mailing.list
Maybe this is also/more helpful?
 
With
 
pi@raspberrypi:~ $ lircd --nodaemon
 
in one terminal and
 
pi@raspberrypi:~ $ irsend SEND_ONCE MP3 TASTE_ANAUS
pi@raspberrypi:~ $ irsend SEND_ONCE MP3 TASTE_ANAUS
transmission failed
Error running command: Input/output error
 
in a second terminal (note: first irsend successful, second irsend failed), I got the following lirc debug log:
 
http://pastebin.com/xaNin46w
 
Regards
 
Val
 
 

------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Aw: Re: lirc installation on raspberry pi running Raspbian jessie

Alec Leamas
In reply to this post by mailing.list
On 10/01/16 18:22, [hidden email] wrote:

> *Gesendet:* Sonntag, 10. Januar 2016 um 14:54 Uhr
> *Von:* "Alec Leamas" <[hidden email]>
> On 10/01/16 14:48, Alec Leamas wrote:
>
>  > We need better logs. Set the debug level to 'debug' in lirc_options.conf
>  > (uncomment the line), restart lircd.service and then run irw which
>  > seemingly makes lircd die. Then check the logs using
>
> Also, please check dmesg to see if the kernel module is unhappy. Perhaps
> the lirc_rpi module has some logging options? 'modinfo lirc_rpi' should
> tell.
>
>
> Cheers!
>
> --alec
> The following commands
> pi@raspberrypi:~ $ lircd
> pi@raspberrypi:~ $ sudo systemctl start lircd.socket
> pi@raspberrypi:~ $ irw
> read: Connection reset by peer
> resulted in the following lirc log (I used the logfile option):
> http://pastebin.com/2Z2PEjjM'

Hm... this beats me. It seems like the daemon is more or less
continuously restarting. It certainly shouldn't, and it doesn't on my host.

Is there some left-over from the old installation, so we are starting
two lircd processes? Could you check:

  - ps -ef | grep lircd
  - If there is anything like /etc/init.d/lirc left which might start a
bogus lircd process?
  - If there is a udev rule, either in /lib/udev/rules.d or
/etc/udev/rules.d, which starts lircd when the device is created. Just
grep for lircd...

Cheers!

--alec


------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: lirc installation on raspberry pi running Raspbian jessie

mailing.list
 
 
Gesendet: Sonntag, 10. Januar 2016 um 19:52 Uhr
Von: "Alec Leamas" <[hidden email]>
 
> The following commands
> pi@raspberrypi:~ $ lircd
> pi@raspberrypi:~ $ sudo systemctl start lircd.socket
> pi@raspberrypi:~ $ irw
> read: Connection reset by peer
> resulted in the following lirc log (I used the logfile option):
> http://pastebin.com/2Z2PEjjM'

Hm... this beats me. It seems like the daemon is more or less
continuously restarting. It certainly shouldn't, and it doesn't on my host.

Is there some left-over from the old installation, so we are starting
two lircd processes? Could you check:

- ps -ef | grep lircd
- If there is anything like /etc/init.d/lirc left which might start a
bogus lircd process?
- If there is a udev rule, either in /lib/udev/rules.d or
/etc/udev/rules.d, which starts lircd when the device is created. Just
grep for lircd...

Cheers!

--alec
 
 
Previously, I had 0.9.0 installed (apt-get install) and subsequently deinstalled, and then tried to install 0.9.2 via
./autogen.sh
./configure
make
sudo make install
following http://www.lirc.org/html/install.html, with and without --prefix=/usrboth option. Might there be remaining artefacts I should have removed?
 
Here are the results for the tests you suggested:
 
pi@raspberrypi:~ $ ps -ef | grep lirc
pi        3088  3077  0 20:03 pts/0    00:00:00 grep --color=auto lirc
pi@raspberrypi:~ $
 
pi@raspberrypi:/etc/init.d $ ls -l | grep lirc
pi@raspberrypi:/etc/init.d $
 
pi@raspberrypi:/lib/udev/rules.d $ ls -l | grep lirc
pi@raspberrypi:/lib/udev/rules.d $
 
pi@raspberrypi:/etc/udev/rules.d $ ls -l | grep lirc
pi@raspberrypi:/etc/udev/rules.d $
 
FYI: The file /etc/modules contains:
lirc_dev
lirc_rpi gpio_in_pin = 23 gpio_out_pin = 22
What does lirc_dev do? I have this in there since the 0.9.0 conf per the tutorial; I believe to remember that lirc_rpi needs lirc_dev.
 
Could lirc_rpi debug help? Where would I find the debug log?
 
Could the previously used but now depreciated LIRCD_ARGS="--uinput" (and hence not used anymore) have anything to do with the problem? Need to use lircd-uinput tool?
 
Is your conclusion of a second lirc process coming from the facts that the logfile states on the second (failing attempt to send data)
Jan 10 18:33:54.036916 raspberrypi lircd: Error: could not open /dev/lirc0
Jan 10 18:33:54.037080 raspberrypi lircd: Error: default_init(): Device or resource busy
?
 
Anything else one could take a look at now?
 
Thanks again!
 
Val
 

------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: lirc installation on raspberry pi running Raspbian jessie

Alec Leamas
On 11/01/16 20:34, [hidden email] wrote:

> Previously, I had 0.9.0 installed (apt-get install) and subsequently
> deinstalled, and then tried to install 0.9.2 via
> ./autogen.sh
> ./configure
> make
> sudo make install
> following http://www.lirc.org/html/install.html, with and without
> --prefix=/usrboth option. Might there be remaining artefacts I should
> have removed?
> Here are the results for the tests you suggested:
> pi@raspberrypi:~ $ ps -ef | grep lirc
> pi        3088  3077  0 20:03 pts/0    00:00:00 grep --color=auto lirc
> pi@raspberrypi:~ $
> pi@raspberrypi:/etc/init.d $ ls -l | grep lirc
> pi@raspberrypi:/etc/init.d $
> pi@raspberrypi:/lib/udev/rules.d $ ls -l | grep lirc
> pi@raspberrypi:/lib/udev/rules.d $
> pi@raspberrypi:/etc/udev/rules.d $ ls -l | grep lirc
> pi@raspberrypi:/etc/udev/rules.d $

OK, all looks sane.

> FYI: The file /etc/modules contains:
> lirc_dev
> lirc_rpi gpio_in_pin = 23 gpio_out_pin = 22
> What does lirc_dev do? I have this in there since the 0.9.0 conf per the
> tutorial; I believe to remember that lirc_rpi needs lirc_dev.

Basically, this is about the kernel. Since there is nothing strange in
the kernel dmesg log, and it worked for you using 0.9.0 let's assume
these parts are OK for now.

I have no experience with the lirc_rpi driver but in general most modern
lirc kernel drivers indeed need lirc_dev; it's kind of a framework.

> Could lirc_rpi debug help? Where would I find the debug log?

yes. The log is the dmesg output.

> Could the previously used but now depreciated LIRCD_ARGS="--uinput" (and
> hence not used anymore) have anything to do with the problem? Need to
> use lircd-uinput tool?

This shouldn't have anything to do with your problem. However, the
option is deprecated, not removed, so you can use for now it if you like.

> Is your conclusion of a second lirc process coming from the facts that
> the logfile states on the second (failing attempt to send data)
> Jan 10 18:33:54.036916 raspberrypi lircd: Error: could not open /dev/lirc0
> Jan 10 18:33:54.037080 raspberrypi lircd: Error: default_init(): Device
> or resource busy
> ?

It's definitely not a conclusion, more like a guess. If you use
journalctl instead (no logfile) the messages are marked with the pid (at
least on Fedora) which might be helpful. But yes, as long as the kernel
driver is safe and sound, the message indicates that some other process
is accessing /dev/lirc0. And I don't know any application besides lircd
which does...

> Anything else one could take a look at now?

Yes. If you look into /lib/systemd/system/lircd.service you will find
the exact command line used to run lircd. If stop the lircd.socket
service  and give that command (as root) in a separate window lircd will
run in foreground. Now, if you do your magic with irw and irsend in
another window it would be interesting to see what really happens here...

Another path is to manually reload the kernel drivers. things like
"modprobe -r lirc_rpi; modprobe lirc_rpi" reloads the driver. Does
anything change? It shouldn't, but we have bugs lurking around...


Cheers!

--alec


------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: lirc installation on raspberry pi running Raspbian jessie

Alec Leamas
On 11/01/16 22:22, Alec Leamas wrote:

>> Anything else one could take a look at now?

Above all, use mode2 as described in the Configuration Guide. This will
make it possible to really check the kernel driver. Why didn't I say
that first?

"banging head on keyboard"

--alec

------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: lirc installation on raspberry pi running Raspbian jessie

mailing.list
 
 
Gesendet: Montag, 11. Januar 2016 um 22:38 Uhr
Von: "Alec Leamas" <[hidden email]>
An: [hidden email], [hidden email]
Betreff: Re: lirc installation on raspberry pi running Raspbian jessie
On 11/01/16 22:22, Alec Leamas wrote:

>> Anything else one could take a look at now?

Above all, use mode2 as described in the Configuration Guide. This will
make it possible to really check the kernel driver. Why didn't I say
that first?

"banging head on keyboard"

--alec
 
 
Hopefully this "remote trouble shooting" isn't becoming too much of a burden, much appreciated, I'd really like to get this to work!
 
Here are the results of all the test procedures you suggested, from both of your most recent posts:
 
 
After boot, no lircd startet, just sending some IR codes to the receiver, I can do that as long as I want, no errors, keeps outputing space/pulse info, and I can interrupt and restart "sudo mode2 --driver default --device /dev/lirc0" as often as I want to:
 
pi@raspberrypi:~ $ sudo mode2 --driver default --device /dev/lirc0
Using driver default on device /dev/lirc0
Trying device: /dev/lirc0
Using device: /dev/lirc0
Running as regular user pi
space 3040766
pulse 8960
space 4552
pulse 533
space 595
 
 
 
After boot, no lircd started, looks identical regardless whether "debug = 1" is added to lirc_rpi config in "/etc/modules" or not, for now, I have it set to "debug = 1":
 
pi@raspberrypi:~ $ dmesg | grep lirc
[    3.756514] lirc_dev: IR Remote Control driver registered, major 245
[    4.738558] lirc_rpi: module is from the staging directory, the quality is unknown, you have been warned.
[    5.693201] lirc_rpi: auto-detected active low receiver on GPIO pin 23
[    5.693643] lirc_rpi lirc_rpi: lirc_dev: driver lirc_rpi registered at minor = 0
[    5.693648] lirc_rpi: driver registered!
 
 

Testing to add LIRCD_ARGS="--uinput" to the lirc_options.conf file did not change the problem, irw only workes for the first call (as long as I want to), but once interrupted by control-c and started irw again, no more decoding.
 
 

Next procedure you suggested to test, again directly after boot, with nothing else entered:
pi@raspberrypi:~ $ lircd
pi@raspberrypi:~ $ sudo systemctl stop lircd.socket
pi@raspberrypi:~ $ cat /lib/systemd/system/lircd.service
[Unit]
Description=LIRC Infrared Signal Decoder
Wants=lircd-setup.service
After=network.target lircd-setup.service
[Service]
Type=simple
ExecStart=/usr/sbin/lircd --nodaemon
; User=lirc
; Group=lirc
[Install]
WantedBy=multi-user.target
pi@raspberrypi:~ $ sudo /usr/sbin/lircd --nodaemon
lircd: there seems to already be a lircd process with pid 2172
lircd: otherwise delete stale lockfile /var/run/lirc/lircd.pid
pi@raspberrypi:~ $

Did I do the procedure you suggested incorrectly? Or is that "stale lockfile" indeed the problem?

After that, I tried irw again, and received the following different (!) error messages, now, irw didn't even work the first time, after the service stop/start procedure and the failed attempt to run "sudo /usr/sbin/lircd --nodaemon":
pi@raspberrypi:~ $ sudo systemctl start lircd.socket
pi@raspberrypi:~ $ irw
read: Connection reset by peer
pi@raspberrypi:~ $ irw
Cannot connnect to socket /var/run/lirc/lircd: Connection refused
 
 

And the last of the suggested test procedures, again after boot:
pi@raspberrypi:~ $ sudo modprobe -r lirc_rpi
pi@raspberrypi:~ $ sudo modprobe lirc_rpi
pi@raspberrypi:~ $ lircd
pi@raspberrypi:~ $ irw
0000000000ff18e7 00 TASTE_2 MP3
0000000000ff9867 00 TASTE_WIEDERHOLEN MP3
^C
pi@raspberrypi:~ $ irw
--> here I also sent several IR commands but none was decoded, that's the usual "doesn't work the second time problem",
interestingly, no error message from irw in this case, as above, just "no decoding anything" <--
^C
pi@raspberrypi:~ $ sudo modprobe -r lirc_rpi
modprobe: FATAL: Module lirc_rpi is in use.
pi@raspberrypi:~ $
 
So the restarting of the kernel driver worked right after reboot, but not in the "failed" state.
 
And here the correspondig dmesg for that:
pi@raspberrypi:~ $ dmesg | grep lirc
[    3.800761] lirc_dev: IR Remote Control driver registered, major 245
[    4.785032] lirc_rpi: module is from the staging directory, the quality is unknown, you have been warned.
[    5.753019] lirc_rpi: auto-detected active low receiver on GPIO pin 23
[    5.753584] lirc_rpi lirc_rpi: lirc_dev: driver lirc_rpi registered at minor = 0
[    5.753609] lirc_rpi: driver registered!
[   57.455634] lirc_rpi: cleaned up module
[   57.513747] lirc_dev: module unloaded
[   64.836041] lirc_dev: IR Remote Control driver registered, major 245
[   64.836419] lirc_rpi: module is from the staging directory, the quality is unknown, you have been warned.
[   65.793563] lirc_rpi: auto-detected active low receiver on GPIO pin 23
[   65.794770] lirc_rpi lirc_rpi: lirc_dev: driver lirc_rpi registered at minor = 0
[   65.794791] lirc_rpi: driver registered!
 
 
 
 
 

------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: lirc installation on raspberry pi running Raspbian jessie

Alec Leamas
On 13/01/16 21:17, [hidden email] wrote:

> *Gesendet:* Montag, 11. Januar 2016 um 22:38 Uhr
> *Von:* "Alec Leamas" <[hidden email]>
> *An:* [hidden email], [hidden email]
> *Betreff:* Re: lirc installation on raspberry pi running Raspbian jessie
> On 11/01/16 22:22, Alec Leamas wrote:
>
>  >> Anything else one could take a look at now?
>
> Above all, use mode2 as described in the Configuration Guide. This will
> make it possible to really check the kernel driver. Why didn't I say
> that first?
>
> "banging head on keyboard"

TBH, I just skimmed your message. However, it might be that we have a
kernel bug involved in this. At least on my (virtual) Jessie it seems
that [1] has surfaced again. I'm currently trying to bisect about 15000
commits (!) in the kernel, it takes a *long* time.


Cheers!

--alec

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1260862




------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: lirc installation on raspberry pi running Raspbian jessie

mailing.list
 
Gesendet: Mittwoch, 13. Januar 2016 um 21:37 Uhr
Von: "Alec Leamas" <[hidden email]>

TBH, I just skimmed your message.
 
 
If you find time, the potentially most interesting part might be where the restart "sudo mode2 --driver default --device /dev/lirc0" doesn't work but produces an error. Unless I didn't do it correctly, might that be an indication of the problem's origin...?
 
 
However, it might be that we have a
kernel bug involved in this. At least on my (virtual) Jessie it seems
that [1] has surfaced again. I'm currently trying to bisect about 15000
commits (!) in the kernel, it takes a *long* time.
 
 
I see, that doesn't sound good...
 
Regards
 
Val

------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Aw: Re: lirc installation on raspberry pi running Raspbian jessie

mailing.list
 
 
Gesendet: Mittwoch, 13. Januar 2016 um 22:16 Uhr
Von: "Alec Leamas" <[hidden email]>
 
On 13/01/16 21:53, [hidden email] wrote:
> *Gesendet:* Mittwoch, 13. Januar 2016 um 21:37 Uhr
> *Von:* "Alec Leamas" <[hidden email]>
>
> TBH, I just skimmed your message.
> If you find time, the potentially most interesting part might be where
> the restart "sudo mode2 --driver default --device /dev/lirc0" doesn't
> work but produces an error. Unless I didn't do it correctly, might that
> be an indication of the problem's origin...?

This basically should mean that the driver is in a bad state. If this
theory holds, you should be able to reload the driver (modprobe -r ...;
modprobe ...) and then use mode2 OK again without problems.

 
 
That didn't work in the failed state, it produced the following error:
 
pi@raspberrypi:~ $ sudo modprobe -r lirc_rpi
modprobe: FATAL: Module lirc_rpi is in use.
 
 
 
After stoping the socket and calling it with sudo, that fails with the error message about a stale lockfile:
 
pi@raspberrypi:~ $ lircd
pi@raspberrypi:~ $ sudo systemctl stop lircd.socket
pi@raspberrypi:~ $ sudo /usr/sbin/lircd --nodaemon
lircd: there seems to already be a lircd process with pid 2172
lircd: otherwise delete stale lockfile /var/run/lirc/lircd.pid
 
Is that the problem?
 
 

------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Aw: Re: Re: lirc installation on raspberry pi running Raspbian jessie

mailing.list
 
 
Gesendet: Donnerstag, 14. Januar 2016 um 20:16 Uhr
Von: "Alec Leamas" <[hidden email]>
 
On 14/01/16 20:03, [hidden email] wrote:
> *Gesendet:* Mittwoch, 13. Januar 2016 um 22:16 Uhr
> *Von:* "Alec Leamas" <[hidden email]>

> That didn't work in the failed state, it produced the following error:
> pi@raspberrypi:~ $ sudo modprobe -r lirc_rpi
> modprobe: FATAL: Module lirc_rpi is in use.

I. e., something is holding the /dev/lirc0 device open. See below.

> After stoping the socket and calling it with sudo, that fails with the
> error message about a stale lockfile:
> pi@raspberrypi:~ $ lircd
> pi@raspberrypi:~ $ sudo systemctl stop lircd.socket
> pi@raspberrypi:~ $ sudo /usr/sbin/lircd --nodaemon
> lircd: there seems to already be a lircd process with pid 2172
> lircd: otherwise delete stale lockfile /var/run/lirc/lircd.pid
> Is that the problem?


Sort of. Here is two things: lircd.socket and lircd.service.

lircd.socket is used to fire-up lircd in a specific way which solves
some race conditions. However, when you are testing like you do now it's
probably best to stop and disable lircd.socket; it has some surprises in
it's sleeves. Instead, start and stop lircd.service. The lockfile
probably represents a running lircd.service.

And always, when things are unclear, check for running lircd processes
using e. g., ps -ef.

After stoppping both lircd.socket and lircd.service: can you unload the
lirc-rpi module now?

 
 
 
No, even after stoping both lircd.socket and lircd.service after having entered the "failed" state, unloading results in FATAL: Module lirc_rpi is in use. And ps -ef shows is still a running lircd process. There is no running process before I start it with "lircd".
 
I also tried your other suggestion, running lircd exactly the way /lib/systemd/system/lircd.service shows it, i.e. with sudo /usr/sbin/lircd --nodaemon. This is without running lircd and (trying to) stopping lircd.socket and lircd.service before, since this failed, but rather directly after reboot with sudo /usr/sbin/lircd --nodaemon. Then, in a second window, I run irw, works first time. Once irw is interrupted with Ctrl-C, and restartet, irw does not decode anymore (same problem as before). There are no errors/no text whatsoever in the window where sudo /usr/sbin/lircd --nodaemon is running in the foreground. Interestingly, when I stop sudo /usr/sbin/lircd --nodaemon and restart sudo /usr/sbin/lircd --nodaemon, I have again one time working irw, the second time it's not working again.
 
On the kernel bug assumption, I did numerous (>20) "long" spaces but found not a single case of two spaces with no pulse in between.
 
Regards
 
Val
 
 
 
 

------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Aw: Re: Re: lirc installation on raspberry pi running Raspbian jessie

Alec Leamas
On 15/01/16 15:47, [hidden email] wrote:


> And ps -ef shows is still a running lircd process.

As they say: I cannot parse this... there is no lircd process, right?

> No, even after stoping both lircd.socket and lircd.service after having entered the "failed" state, unloading results in FATAL: Module lirc_rpi is in use. And ps -ef shows is still a running lircd process. There is no running process before I start it with "lircd".


In that case I'd say that this is about the lirc_rpi module. If no
process is accessing  /dev/lirc0 this shouldn't happen.

If there was a clue, it should be in dmesg. But since it's not, perhaps
you should report this against lirc_rpi. In short,the module doesn't
seem to work correctly but I have no clue as to why.

Cheers!

--alec


------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
12
Loading...