Don Giovanni
October 25th, 2009, 05:04 PM
*Solved see bottom of post*
I have an issue where devices set to /dev/lirc0 will work but devices set to /dev/lirc1 will not.
remote(ir receiver) on lirc0 and ir transmitter on lirc1 = remote only works
If i switch it around
transmitter to lirc0 and remote to lirc1 = transmitter only works
I've tested both devices and they are both fully functional when assigned to lirc0 but both stop working when assigned to lirc1. So for some reason lirc1 isn't being looked at or isn't loading properly
If I look under /dev/ lirc0, lirc1, lircd and lircd1 are all there.
Here are my current configs.
/etc/lirc/hardware.conf
# /etc/lirc/hardware.conf
#
#Chosen Remote Control
REMOTE="Hauppauge TV card"
REMOTE_MODULES="lirc_dev lirc_i2c"
REMOTE_DRIVER=""
REMOTE_DEVICE="/dev/lirc0"
REMOTE_SOCKET=""
REMOTE_LIRCD_CONF="hauppauge/lircd.conf.hauppauge"
REMOTE_LIRCD_ARGS=""
#Chosen IR Transmitter
TRANSMITTER="SRC-200A_3"
TRANSMITTER_MODULES="lirc_dev lirc_serial"
TRANSMITTER_DRIVER=""
TRANSMITTER_DEVICE="/dev/lirc1"
TRANSMITTER_SOCKET=""
TRANSMITTER_LIRCD_CONF="mts/lircd.conf.mts"
TRANSMITTER_LIRCD_ARGS=""
#Enable lircd
START_LIRCD="true"
#Don't start lircmd even if there seems to be a good config file
#START_LIRCMD="false"
#Try to load appropriate kernel modules
LOAD_MODULES="true"
# Default configuration files for your hardware if any
LIRCMD_CONF=""
#Forcing noninteractive reconfiguration
#If lirc is to be reconfigured by an external application
#that doesn't have a debconf frontend available, the noninteractive
#frontend can be invoked and set to parse REMOTE and TRANSMITTER
#It will then populate all other variables without any user input
#If you would like to configure lirc via standard methods, be sure
#to leave this set to "false"
FORCE_NONINTERACTIVE_RECONFIGURATION="false"
START_LIRCMD=""
/etc/lirc/lircd.conf
#/etc/lirc/lircd.conf
#
#Moved transmitter entry in front of remote entry
#Neither will function if transmitter is entered second
#reason unknown - worked in previous versions
#Configuration for SRC-200A_3 transmitter:
include "/usr/share/lirc/extras/transmitters/mts/lircd.conf.mts"
#Configuration for the Hauppauge TV card remote:
include "/usr/share/lirc/extras/more_remotes/hauppauge/lircd.conf.hauppauge"
A quick ls /dev/lirc* shows
/dev/lirc0 /dev/lirc1 /dev/lircd /dev/lircd1
*Update October 29,2009*
I posted this issue to the lirc email list. Jeremy Yoder confirmed there was an issue in his /etc/init.d/lirc script and with testing on my side he created a patch.
Quoting his post on the lirc email list http://sourceforge.net/mailarchive/forum.php?thread_name=4AEA5262.60006%40umich.edu&forum_name=lirc-list
"Just to update, the bug was mine in the /etc/init.d/lirc script (as I
suspected). It turns out I'm linking both /dev/lircd and /dev/lircd1 to
/var/run/lirc/lircd. Doh.
I should have a patch ready for Ubuntu in a day or two.
Jeremy"
So in case someone else is having trouble with this you should see a fix come down the line soon :D
I have an issue where devices set to /dev/lirc0 will work but devices set to /dev/lirc1 will not.
remote(ir receiver) on lirc0 and ir transmitter on lirc1 = remote only works
If i switch it around
transmitter to lirc0 and remote to lirc1 = transmitter only works
I've tested both devices and they are both fully functional when assigned to lirc0 but both stop working when assigned to lirc1. So for some reason lirc1 isn't being looked at or isn't loading properly
If I look under /dev/ lirc0, lirc1, lircd and lircd1 are all there.
Here are my current configs.
/etc/lirc/hardware.conf
# /etc/lirc/hardware.conf
#
#Chosen Remote Control
REMOTE="Hauppauge TV card"
REMOTE_MODULES="lirc_dev lirc_i2c"
REMOTE_DRIVER=""
REMOTE_DEVICE="/dev/lirc0"
REMOTE_SOCKET=""
REMOTE_LIRCD_CONF="hauppauge/lircd.conf.hauppauge"
REMOTE_LIRCD_ARGS=""
#Chosen IR Transmitter
TRANSMITTER="SRC-200A_3"
TRANSMITTER_MODULES="lirc_dev lirc_serial"
TRANSMITTER_DRIVER=""
TRANSMITTER_DEVICE="/dev/lirc1"
TRANSMITTER_SOCKET=""
TRANSMITTER_LIRCD_CONF="mts/lircd.conf.mts"
TRANSMITTER_LIRCD_ARGS=""
#Enable lircd
START_LIRCD="true"
#Don't start lircmd even if there seems to be a good config file
#START_LIRCMD="false"
#Try to load appropriate kernel modules
LOAD_MODULES="true"
# Default configuration files for your hardware if any
LIRCMD_CONF=""
#Forcing noninteractive reconfiguration
#If lirc is to be reconfigured by an external application
#that doesn't have a debconf frontend available, the noninteractive
#frontend can be invoked and set to parse REMOTE and TRANSMITTER
#It will then populate all other variables without any user input
#If you would like to configure lirc via standard methods, be sure
#to leave this set to "false"
FORCE_NONINTERACTIVE_RECONFIGURATION="false"
START_LIRCMD=""
/etc/lirc/lircd.conf
#/etc/lirc/lircd.conf
#
#Moved transmitter entry in front of remote entry
#Neither will function if transmitter is entered second
#reason unknown - worked in previous versions
#Configuration for SRC-200A_3 transmitter:
include "/usr/share/lirc/extras/transmitters/mts/lircd.conf.mts"
#Configuration for the Hauppauge TV card remote:
include "/usr/share/lirc/extras/more_remotes/hauppauge/lircd.conf.hauppauge"
A quick ls /dev/lirc* shows
/dev/lirc0 /dev/lirc1 /dev/lircd /dev/lircd1
*Update October 29,2009*
I posted this issue to the lirc email list. Jeremy Yoder confirmed there was an issue in his /etc/init.d/lirc script and with testing on my side he created a patch.
Quoting his post on the lirc email list http://sourceforge.net/mailarchive/forum.php?thread_name=4AEA5262.60006%40umich.edu&forum_name=lirc-list
"Just to update, the bug was mine in the /etc/init.d/lirc script (as I
suspected). It turns out I'm linking both /dev/lircd and /dev/lircd1 to
/var/run/lirc/lircd. Doh.
I should have a patch ready for Ubuntu in a day or two.
Jeremy"
So in case someone else is having trouble with this you should see a fix come down the line soon :D