[mythtv] No luck with LIRC...
Chris
cisip at sprintmail.com
Fri Jan 31 22:00:18 EST 2003
I have a Creative Infra Receiver remote control working fine with mythtv
using lirc 0.6.6.
When I initially installed it, I had the problem with the lircd daemon
quitting when I try to use the remote. When I inspected another pc with
lirc I found /dev/lirc was created which pointed to /dev/ttySx
(corresponding to the com port where the remote is connected) so I
created this device file pointing it to /dev/ttySx and everything is
fine.
On Fri, 2003-01-31 at 09:27, Jeff_Mitchell at accessbusinessgroup.com
wrote:
>
> John-
>
> Amazingly, my Creative IR Reciever just came via UPS last night. I'm
> running Mandrake 9.0, and opted to install from source. I was getting the
> exact same behavior as the original post (the daemon crapping out because
> it couldn't open /dev/lirc), and I went through all sorts of machinations
> last night to get to the state I'm at now (I *think* I'm closer, but still
> not working.)
>
> I compiled and loaded the lirc_serial module (The setup script says it's
> not necessary, but I read about someone else needing it in one of the hits
> that Google turned up), and went through a few cycles of installing from
> source, uninstalling from source, installing the Mandrake-supplied package,
> and inunstalling said rpm.
>
> Currently, here's my behavior:
>
> [root at localhost root]# cd /dev/
> [root at localhost dev]# ls -Al l*
> crw-rw-rw- 1 root root 61, 0 Jan 31 00:09 lirc
> srw-rw-rw- 1 root root 0 Jan 31 00:33 lircd=
> prw-r--r-- 1 root root 0 Jan 31 00:10 lircm|
> srw-rw-rw- 1 root root 0 Jan 31 00:09 log=
> [root at localhost dev]# lircd -n
> lircd 0.6.6: lircd(creative) ready
> lircd 0.6.6: accepted new client on /dev/lircd
> lircd 0.6.6: could not reset tty
> lircd 0.6.6: caught signal
> Terminated
> [root at localhost dev]#
>
> It should be noted that after the line "lircd 0.6.6: lircd(creative)
> ready", there's a wait until I run irw from another terminal. Also, the
> command lircd -n is the same as lircd -n -d /dev/lirc. I've tried it,
> feeding /dev/lirc/0, /dev/lircd, and /dev/lircd/0, and all of those die,
> yelling about those devices not existing.
>
> I plan on posting this to the LIRC list later this morning, and if I get an
> a solution, I'll make sure to spread the wealth. Of course, if anyone here
> has any ideas, I'd be happy to take them from this list, too.
>
> -Jeff
>
>
>
>
> John
> <johnmythtv at crombe.c To: Development of mythtv <mythtv-dev at snowman.net>
> om> cc:
> Sent by: Subject: Re: [mythtv] No luck with LIRC...
> mythtv-dev-bounces at s
> nowman.net
>
>
> 01/31/2003 08:32 AM
> Please respond to
> Development of
> mythtv
>
>
>
>
>
>
> Hi Pete,
>
> I don't seem to have a /dev/lirc/0 (wouldn't it show up below if I did?).
>
> Tried to insmod lirc_dev and it didn't find it. I searched and found the
> .c
> in the drivers/lirc_dev directory. Went there and did a make there (make
> install too but even after that I had to do an insmod lirc_dev.o for it to
> find that module). Anyway, I can now load EITHER insmod lirc_serial OR
> lirc_dev but not both. Depending on the order, I either get "Device or
> resource busy" (lirc_serial first) or "init_module: Input/output error"
> (lirc_dev first). Do you have both modules installed together? If so, in
> what order? Maybe each module needs to be associated with a unique device
> (like "lircd" and "lird" or "lirc/0")?
>
> Any more tips would help!
> Thanks,
> JC
>
> ----- Original Message -----
> From: "Pierre-Olivier Bouchard" <petecool at vl.videotron.ca>
> To: "Development of mythtv" <mythtv-dev at snowman.net>
> Sent: Friday, January 31, 2003 7:28 AM
> Subject: Re: [mythtv] No luck with LIRC...
>
>
> >
> > > Here's how a ll of my lirc* devices look:
> > >
> > > crw-rw-rw- 1 root root 61, 0 Jan 15 05:08 /dev/lirc
> > > srw-rw-rw- 1 root root 0 Jan 31 01:16 /dev/lircd=
> > > prw-r--r-- 1 root root 0 Jan 30 04:48 /dev/lircm|
> > >
> >
> > Try to use /dev/lirc/0 if you have one (modprobe'ing in the lirc_dev and
> > lirc_serial might help if they weren't automatically loaded).
> >
> > I had to do that to make it work.
> >
> >
> > Pete
> > _______________________________________________
> > mythtv-dev mailing list
> > mythtv-dev at snowman.net
> > http://www.snowman.net/mailman/listinfo/mythtv-dev
> >
> >
>
>
> _______________________________________________
> mythtv-dev mailing list
> mythtv-dev at snowman.net
> http://www.snowman.net/mailman/listinfo/mythtv-dev
>
>
>
>
> _______________________________________________
> mythtv-dev mailing list
> mythtv-dev at snowman.net
> http://www.snowman.net/mailman/listinfo/mythtv-dev
More information about the mythtv-dev
mailing list