From: Don_Giovanni <the...@gm...> - 2009-10-28 08:19:28
|
I have an issue where devices assigned to /dev/lirc0 will work but devices assigned 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. Using lirc 0.8.6 Ubuntu 9.10 Kernel 2.6.31-14-generic ls /dev/lirc* shows /dev/lirc0 /dev/lirc1 /dev/lircd /dev/lircd1 are all there My current configs are posted below. Any ideas? -DG /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" /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="" |
From: Jeremy Y. <jy...@um...> - 2009-10-28 14:17:32
|
Since this is an Ubuntu thing I'll take it off-list. Jeremy Don_Giovanni wrote the following on 10/28/2009 4:18 AM: > I have an issue where devices assigned to /dev/lirc0 will work but > devices assigned 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. > > Using lirc 0.8.6 > Ubuntu 9.10 > Kernel 2.6.31-14-generic > > ls /dev/lirc* shows /dev/lirc0 /dev/lirc1 /dev/lircd /dev/lircd1 > are all there > > My current configs are posted below. Any ideas? > > -DG > > > /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" > > > /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="" > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry(R) Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9 - 12, 2009. Register now! > http://p.sf.net/sfu/devconference > > > |
From: <li...@ba...> - 2009-10-28 19:21:58
|
Hi! Don_Giovanni "the...@gm..." wrote: > I have an issue where devices assigned to /dev/lirc0 will work but > devices assigned to /dev/lirc1 will not. What do you mean by "will not work"? Do you use "irw /dev/lircd1" and "irsend --device=/dev/lircd1" to access the second device? Christoph |
From: Jeremy Y. <jy...@um...> - 2009-10-28 21:49:51
|
This is part of the Ubuntu package. The /etc/init.d/lircd script is supposed to do all that stuff for you, but it's obviously not working in this case. Nothing wrong with LIRC itself as far as I can tell :) Jeremy Christoph Bartelmus wrote the following on 10/28/2009 3:13 PM: > Hi! > > Don_Giovanni "the...@gm..." wrote: > > >> I have an issue where devices assigned to /dev/lirc0 will work but >> devices assigned to /dev/lirc1 will not. >> > > What do you mean by "will not work"? > Do you use "irw /dev/lircd1" and "irsend --device=/dev/lircd1" to access > the second device? > > Christoph > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry(R) Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9 - 12, 2009. Register now! > http://p.sf.net/sfu/devconference > > > |
From: <li...@ba...> - 2009-10-29 07:23:10
|
Hi! Jeremy Yoder "jy...@um..." wrote: > This is part of the Ubuntu package. The /etc/init.d/lircd script is > supposed to do all that stuff for you, but it's obviously not working in > this case. Nothing wrong with LIRC itself as far as I can tell :) You have not understood my question. I know that Ubuntu is starting two instances of lircd. But in order to take advantage of this setup you have to use the tools like irw and irsend correctly. The init script won't do this for you. Christoph >> Don_Giovanni "the...@gm..." wrote: >> >> >>> I have an issue where devices assigned to /dev/lirc0 will work but >>> devices assigned to /dev/lirc1 will not. >>> >> >> What do you mean by "will not work"? >> Do you use "irw /dev/lircd1" and "irsend --device=/dev/lircd1" to access >> the second device? >> >> Christoph >> >> --------------------------------------------------------------------------- >> --- Come build with us! The BlackBerry(R) Developer Conference in SF, CA >> is the only developer event you need to attend this year. Jumpstart your >> developing skills, take BlackBerry mobile applications to market and stay >> ahead of the curve. Join us from November 9 - 12, 2009. Register now! >> http://p.sf.net/sfu/devconference >> >> >> |
From: Don_Giovanni <the...@gm...> - 2009-10-29 08:10:16
|
Christoph Bartelmus <li...@ba...> wrote: >> I have an issue where devices assigned to /dev/lirc0 will work but >> devices assigned to /dev/lirc1 will not. > >What do you mean by "will not work"? >Do you use "irw /dev/lircd1" and "irsend --device=/dev/lircd1" to access >the second device? Original poster getting back here for the first time (didn't expect so manyreplies so quickly). To answer your question Christoph, yes both devices have been verified individually. I have done the following: 1)Specified in my hardware.conf for remote to use /dev/lirc0 -confirmed working with irw (keys pressed on remote show on screen correctly) specified transmitter in hardware.conf to use /dev/lirc1 -tested irsend...nothing sent (channels do not change and cannot see IR with camera) 2)Switched them around so that hardware.conf specifies transmitter uses /dev/lirc0 -tested with irsend and confirmed working (i can now change channels) specified remote to use /dev/lirc1 -test with irw...no input shows up on the screen. So currently on my machine it appears each device works perfectly, just not when assigned to /dev/lirc1 DG On Thu, Oct 29, 2009 at 2:09 AM, Christoph Bartelmus <li...@ba...> wrote: > Hi! > > Jeremy Yoder "jy...@um..." wrote: >> This is part of the Ubuntu package. The /etc/init.d/lircd script is >> supposed to do all that stuff for you, but it's obviously not working in >> this case. Nothing wrong with LIRC itself as far as I can tell :) > > You have not understood my question. I know that Ubuntu is starting two > instances of lircd. But in order to take advantage of this setup you have > to use the tools like irw and irsend correctly. The init script won't do > this for you. > > Christoph > >>> Don_Giovanni "the...@gm..." wrote: >>> >>> >>>> I have an issue where devices assigned to /dev/lirc0 will work but >>>> devices assigned to /dev/lirc1 will not. >>>> >>> >>> What do you mean by "will not work"? >>> Do you use "irw /dev/lircd1" and "irsend --device=/dev/lircd1" to access >>> the second device? >>> >>> Christoph >>> >>> --------------------------------------------------------------------------- >>> --- Come build with us! The BlackBerry(R) Developer Conference in SF, CA >>> is the only developer event you need to attend this year. Jumpstart your >>> developing skills, take BlackBerry mobile applications to market and stay >>> ahead of the curve. Join us from November 9 - 12, 2009. Register now! >>> http://p.sf.net/sfu/devconference >>> >>> >>> > > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry(R) Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9 - 12, 2009. Register now! > http://p.sf.net/sfu/devconference > |
From: Jeremy Y. <jy...@um...> - 2009-10-30 02:41:54
|
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 Don_Giovanni wrote: > Christoph Bartelmus <li...@ba...> wrote: > >>> I have an issue where devices assigned to /dev/lirc0 will work but >>> devices assigned to /dev/lirc1 will not. >>> >> What do you mean by "will not work"? >> Do you use "irw /dev/lircd1" and "irsend --device=/dev/lircd1" to access >> the second device? >> > > Original poster getting back here for the first time (didn't expect so > manyreplies so quickly). > To answer your question Christoph, yes both devices have been verified > individually. > > I have done the following: > 1)Specified in my hardware.conf for remote to use /dev/lirc0 > -confirmed working with irw (keys pressed on remote show on screen correctly) > specified transmitter in hardware.conf to use /dev/lirc1 > -tested irsend...nothing sent (channels do not change and cannot see > IR with camera) > > 2)Switched them around so that hardware.conf specifies transmitter > uses /dev/lirc0 > -tested with irsend and confirmed working (i can now change channels) > specified remote to use /dev/lirc1 > -test with irw...no input shows up on the screen. > > So currently on my machine it appears each device works perfectly, > just not when assigned to /dev/lirc1 > > DG > > On Thu, Oct 29, 2009 at 2:09 AM, Christoph Bartelmus <li...@ba...> wrote: > >> Hi! >> >> Jeremy Yoder "jy...@um..." wrote: >> >>> This is part of the Ubuntu package. The /etc/init.d/lircd script is >>> supposed to do all that stuff for you, but it's obviously not working in >>> this case. Nothing wrong with LIRC itself as far as I can tell :) >>> >> You have not understood my question. I know that Ubuntu is starting two >> instances of lircd. But in order to take advantage of this setup you have >> to use the tools like irw and irsend correctly. The init script won't do >> this for you. >> >> Christoph >> >> >>>> Don_Giovanni "the...@gm..." wrote: >>>> >>>> >>>> >>>>> I have an issue where devices assigned to /dev/lirc0 will work but >>>>> devices assigned to /dev/lirc1 will not. >>>>> >>>>> >>>> What do you mean by "will not work"? >>>> Do you use "irw /dev/lircd1" and "irsend --device=/dev/lircd1" to access >>>> the second device? >>>> >>>> Christoph >>>> >>>> --------------------------------------------------------------------------- >>>> --- Come build with us! The BlackBerry(R) Developer Conference in SF, CA >>>> is the only developer event you need to attend this year. Jumpstart your >>>> developing skills, take BlackBerry mobile applications to market and stay >>>> ahead of the curve. Join us from November 9 - 12, 2009. Register now! >>>> http://p.sf.net/sfu/devconference >>>> >>>> >>>> >>>> >> ------------------------------------------------------------------------------ >> Come build with us! The BlackBerry(R) Developer Conference in SF, CA >> is the only developer event you need to attend this year. Jumpstart your >> developing skills, take BlackBerry mobile applications to market and stay >> ahead of the curve. Join us from November 9 - 12, 2009. Register now! >> http://p.sf.net/sfu/devconference >> >> > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry(R) Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9 - 12, 2009. Register now! > http://p.sf.net/sfu/devconference > > > |