lircd start problem

Bug #1312287 reported by Dan Volkman
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
lirc (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

If no one else is having lircd(8) problems, ignore this bug report and I will make a work around for me. After upgrading from 13.<what-ever-current> to 14.04 my IR remote stopped working, no output from irw(1) or mode2(1). After some digging I found it worked right if I started lircd(8) with no argument. Please note the lines below:

# grep REMOTE_SOCKET /etc/lirc/hardware.conf
REMOTE_SOCKET=""
# service lirc start
# ps -ef | grep lirc
root 4601 2201 0 11:34 ? 00:00:00 /usr/sbin/lircd --output=/run/lirc/lircd --device=/dev/lirc0
# irw (does not work)

(So I set REMOTE_SOCKET to default settings per manual stating what default is)
# grep REMOTE_SOCKET /etc/lirc/hardware.conf
REMOTE_SOCKET="/var/run/lirc/lircd"
# service lirc start
# ps -ef | grep lirc
root 4694 2201 0 11:42 ? 00:00:00 /usr/sbin/lircd --output=/var/run/lirc/lircd --device=/dev/lirc0
(it looks right but)
# irw (does not work)

# ps -ef | grep lirc
root 4694 2201 0 11:42 ? 00:00:00 /usr/sbin/lircd --output=/var/run/lirc/lircd --device=/dev/lirc0
# service lirc stop
(copy command from ps output above and past it as a command)
# /usr/sbin/lircd --output=/var/run/lirc/lircd --device=/dev/lirc0
# irw (it works)

(I know this is usually an environment issue so here is my environment before launching the above /usr/sbin/lircd)
# env
SHELL=/bin/bash
TERM=xterm
OLDPWD=/etc/init.d
USER=root
SUDO_USER=dan
SUDO_UID=1000
USERNAME=root
MAIL=/var/mail/root
PATH=/usr/sbin:/usr/bin:/sbin:/bin
PWD=/
LANG=en_US.UTF-8
SHLVL=1
SUDO_COMMAND=/bin/bash
HOME=/home/dan
LANGUAGE=en_US
LOGNAME=root
LESSOPEN=| /usr/bin/lesspipe %s
SUDO_GID=1000
DISPLAY=:0.0
LESSCLOSE=/usr/bin/lesspipe %s %s
XAUTHORITY=/home/dan/.Xauthority
_=/usr/bin/env

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: ubuntu-release-upgrader-core 1:0.220.2
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: Unity
Date: Thu Apr 24 11:03:22 2014
InstallationDate: Installed on 2013-02-06 (441 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
Symptom: dist-upgrade
UpgradeStatus: Upgraded to trusty on 2014-04-24 (0 days ago)
VarLogDistupgradeTermlog:

Revision history for this message
Dan Volkman (danvolkman) wrote :
affects: ubuntu-release-upgrader (Ubuntu) → lirc (Ubuntu)
Revision history for this message
Dan Volkman (danvolkman) wrote :

So I just had to have my IR remote so I dug deep into the IR processes. Bottom line, when the "rc_core" module is loaded it includes many components, some of which has no meaning to your system. I learn how data flowed from the USB IR through the driver and other modules and how to exclude module components that were not needed. Rebooted, problem solved.

How to exclude unnecessary module components.
To see module components:
# lsmod | grep rc_core

To exclude the Sanyo Decoder component from rc_core module create a file in /etc/modules.d. Use a name that has meaning such as "blacklist-IR.conf. Put the following line in that file. Do the same with other unneeded elements.

install ir_sanyo_decoder /bin/true

F.Y.I. Here is what I put in my Blacklist file.

install ir_sony_decoder /bin/true
install ir_jvc_decoder /bin/true
install ir_rc5_decoder /bin/true
install ir_nec_decoder /bin/true
install cx23885 /bin/true
install rc_hauppauge /bin/true
install ir_sanyo_decoder /bin/true

--------------------

Revision history for this message
Georg (stiggeorg) wrote :

I have the same problem after upgrading to 14.04; the remote just stopped working. Everything seems to load correctly, but there is no output from irw or mode2.

⟫ dmesg | grep ttyS
[ 0.504063] 00:06: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
[ 0.505388] 0000:05:00.0: ttyS4 at I/O 0xd000 (irq = 20, base_baud = 115200) is a 16550A
[ 0.505468] 0000:05:00.0: ttyS5 at I/O 0xd100 (irq = 20, base_baud = 115200) is a 16550A

⟫ dmesg | grep lirc
[ 4.432792] lirc_dev: IR Remote Control driver registered, major 249
[ 4.435963] lirc_serial: module is from the staging directory, the quality is unknown, you have been warned.
[ 5.348020] lirc_serial lirc_serial.0: auto-detected active high receiver
[ 5.348095] lirc_serial lirc_serial.0: lirc_dev: driver lirc_serial registered at minor = 0

⟫ sudo setserial -a /dev/ttyS0
/dev/ttyS0, Line 0, UART: unknown, Port: 0x03f8, IRQ: 4
        Baud_base: 115200, close_delay: 50, divisor: 0
        closing_wait: 3000
        Flags: spd_normal

⟫ cat /etc/modprobe.d/lirc-serial.conf
#COM1 equivalent, /dev/ttyS0
options lirc_serial irq=4 io=0x3f8

⟫ ls /dev/lirc*
/dev/lirc0 /dev/lircd

⟫ cat /etc/lirc/hardware.conf
# /etc/lirc/hardware.conf
#
#Chosen Remote Control
REMOTE="Home-brew (16x50 UART compatible serial port)"
REMOTE_MODULES="lirc_dev lirc_serial"
REMOTE_DRIVER=""
REMOTE_DEVICE="/dev/lirc0"
REMOTE_LIRCD_CONF="/usr/share/lirc/remotes/avermedia/lircd.conf.avermediarmtk"
REMOTE_LIRCD_ARGS=""
<and more...>

I have tried the suggestions from Dan above, but to no avail. Both of the following shows nothing:
⟫ irw

⟫ sudo mode2 -d /dev/lircd

The remote itself works, as I can see another device reacting to the pulses from the the remote. It also worked like a charm in 13.10 before the upgrade.

Revision history for this message
Georg (stiggeorg) wrote :

My problem is solved. It seems the /etc/lirc/lircd.conf was reset and I had not restored it. A bit of a nuisance, though, that the lircd.conf file is over written when updating the system.

Revision history for this message
Alec Leamas (leamas-alec) wrote :

Overwriting an existing lircd.conf is a packaging bug. It's fixed in the new 0.9.4b (zesty - experimental) update.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package lirc - 0.9.4c-1

---------------
lirc (0.9.4c-1) experimental; urgency=medium

  * New upstream release.
  * New tool irtext2udp.
  * Resolves build errors on kernels > 4.8.0A.
  * Most of patches upstreamed.

 -- Alec Leamas <email address hidden> Sat, 22 Oct 2016 14:52:05 +0200

Changed in lirc (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.