Comment 51 for bug 164627

This is an example of what the hardware.conf file should look like.
It can be located at /etc/lirc/hardware.conf

##
# /etc/lirc/hardware.conf
#
#Chosen Remote Control
REMOTE="MSI TV@nywhere Master"
REMOTE_MODULES=""
*REMOTE_DRIVER="devinput"*
*REMOTE_DEVICE="/dev/input/by-path/pci-0000:02:01.0--event-ir"*
*REMOTE_LIRCD_CONF="msi/lircd.conf.tvanywhere"*
REMOTE_LIRCD_ARGS=""

#Chosen IR Transmitter
TRANSMITTER="None"
TRANSMITTER_MODULES=""
TRANSMITTER_DRIVER=""
TRANSMITTER_DEVICE=""
TRANSMITTER_LIRCD_CONF=""
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=""

##

Please pay special attention to the bold parts... These are normally what
you should take special care to setup correctly as this actually defined
which hardware to use...
instead of using */dev/input/eventX* I have specified the value *
/dev/input/by-path/pci-0000:02:01.0--event-ir*
this will allow the inpt device always to be consistent. note that yours
will be different. just check in the path what you have and replace the one
i supplied with yours.

also note that you will also need to setup the actual remote if it's not
available on lirc.

irrecord is the command to do this with.. It's an easy setup with irrecord.

Good luck!!!!

On Mon, Mar 30, 2009 at 2:36 PM, Claudiu Vlad <email address hidden>wrote:

> Kopernik, you could try this:
>
> lshal | grep -n5 IR
>
> and look for the /dev/input/somethinglikeevent6
>
> That is your IR receiver device.
>
>
>
> On Mon, Mar 30, 2009 at 11:09 AM, Panayiotis Savva <email address hidden>
> wrote:
>
> > No it is not after all...
> > This is the reason we needed to stop GDM... :) To find if this is an
> > exclusive access problem on gdm or not... Obviously lirc is just not
> > configured properly.
> >
> > You are basing your ir remote on event6 (which could change simply by
> > re-arranging hardware or even on startup...)
> >
> > What you need to do is reconfigure LIRC.
> > sudo dpkg-reconfigure lirc
> >
> > Make sure you select the correct input device for your video card /
> remote
> > control.
> >
> > You are getting an exclusive access problem probably on the wrong
> hardware
> > (**event 6)
> >
> > Try this:
> >
> > When configuring lirc, ensure that you choose /dev/by-path/pci*****IR****
> > I
> > can't remeber the exact path for this setting, but it will come up in the
> > list when you reconfigure lirc... with ****IR**** I mean to try and
> find
> > the device that has the IR specified in it.
> >
> > Good Luck!
> >
> > On Mon, Mar 30, 2009 at 9:37 AM, k0per.nik <email address hidden>
> > wrote:
> >
> > > Well, this command seems to do nothing but stopping GDM from working!
> > When
> > > I type 'irw' still nothing happens!
> > > Let me demonstrate you changes in daemon log:
> > >
> > > when I type 'sudo /etc/init.d/lirc restart' I get:
> > >
> > > Mar 30 08:27:39 gryphon lircd-0.8.3[8823]: caught signal
> > > Mar 30 08:27:40 gryphon lircd-0.8.3[9102]: lircd(userspace) ready
> > >
> > > then I type 'irexec' and get:
> > >
> > > Mar 30 08:27:47 gryphon lircd-0.8.3[9102]: accepted new client on
> > > /dev/lircd
> > > Mar 30 08:27:47 gryphon lircd-0.8.3[9102]: initializing
> > '/dev/input/event6'
> > >
> > > then I type 'irw' and get:
> > >
> > > Mar 30 08:30:37 gryphon lircd-0.8.3[9102]: accepted new client on
> > > /dev/lircd
> > >
> > > but when I press buttons on my remote, I still get no output!
> > >
> > > Maybe the problem I have is not associated with this bug in any way!
> > >
> > > --
> > > lirc based applications can not get exclusive access to /dev/input
> > > interface
> > > https://bugs.launchpad.net/bugs/164627
> > > You received this bug notification because you are a direct subscriber
> > > of the bug.
> > >
> >
> > --
> > lirc based applications can not get exclusive access to /dev/input
> > interface
> > https://bugs.launchpad.net/bugs/164627
> > You received this bug notification because you are a direct subscriber
> > of the bug.
> >
>
> --
> lirc based applications can not get exclusive access to /dev/input
> interface
> https://bugs.launchpad.net/bugs/164627
> You received this bug notification because you are a direct subscriber
> of the bug.
>