[mythtv-users] Lirc is kickin my butt
Jon Waite
jon at jonwaite.com
Sat Feb 7 21:25:31 EST 2004
D'Oh!, should be 'mode2' or 'xmode2', dunno why I keep thinking those
programs are called dump.
And you shouldn't have a symbolic link from /dev/lirc to /dev/ttyS1,
/dev/lirc needs to be it's own character device with major 61 and minor 0
which should be created from your modules.conf line reading: alias
char-major-61 lirc_serial
Regards, Jon.
> -----Original Message-----
> From: mythtv-users-bounces at mythtv.org
> [mailto:mythtv-users-bounces at mythtv.org] On Behalf Of Philip
> J. Morrison, Jr.
> Sent: Sunday, 8 February 2004 11:44 a.m.
> To: 'Discussion about mythtv'
> Subject: RE: [mythtv-users] Lirc is kickin my butt
>
> I added irq=3 io=0x02f8 in the /etc/modules.conf file and did
> s setserial
> /dev/ttyS1 but I don't seem to have dump2...
>
> I have a config file for the tivo remote taken from multiple
> sources. The only issue is I still don't know if the problem
> is the hardware or if it is just not loaded properly in linux.
>
> Am I supposed to create a symbolic link from /dev/lirc to
> /dev/ttyS1? I have tried both with and without.
> ---
> Phil
>
>
> -----Original Message-----
> From: Jon Waite [mailto:jon at jonwaite.com]
> Sent: Saturday, February 07, 2004 4:37 PM
> To: 'Discussion about mythtv'
> Subject: RE: [mythtv-users] Lirc is kickin my butt
>
> Having just been through this hopefully I can help...
>
> First thing, check that you are loading the lirc_dev and
> lirc_serial modules. Lirc_serial needs the correct parameters
> for your COM port if autodetect fails (IRQ 3 and port 2F8 are
> defaults for COM2 I think, IRQ 4 and port 3F8 for COM1).
>
> Next, you *may* need: setserial /dev/ttyS1 uart none (for
> COM2, COM1 would be /dev/ttyS0) to prevent the kernel serial
> module from grabbing control of
> COM2 and preventing lircd from accessing it. I say *may*
> because this step wasn't necessary for me (and I'm still not
> sure why).
>
> Now try running the 'dump2' or 'xdump2' programs from lirc -
> these will display the raw codes being received from your
> remote (hopefully).
>
> If that works ok, then all you need to do is update
> /etc/lircd.conf with a suitable config file from the lirc for
> your remote before irw is going to show you the actual
> buttons. (http://www.lirc.org/remotes/) if you can't find
> anything suitable there, then use irrecord to create a new
> config file.
>
> If you need to use multiple remotes then you'll need to merge
> together the config files for each remote into /etc/lircd.conf.
>
> Hope that helps, Jon.
>
> > -----Original Message-----
> > From: mythtv-users-bounces at mythtv.org
> > [mailto:mythtv-users-bounces at mythtv.org] On Behalf Of Philip J.
> > Morrison, Jr.
> > Sent: Sunday, 8 February 2004 9:42 a.m.
> > To: 'Discussion about mythtv'
> > Subject: [mythtv-users] Lirc is kickin my butt
> >
> > To have gotten this far and have the stupid remote kick my butt us
> > just frustrating.
> >
> > I have a serial cable plugged into COM2 which ends in an ir
> receiver.
> > It worked in windows but I can't seem to get anything out of it in
> > linux.
> >
> > I have tried to follow both the guide for Fedora Atrpm and the main
> > MythTV site. I have also gone to lirc.org to see if I
> could get any
> > answers.
> >
> > When I run irw (or lircd --nodaemon) I get no feedback that
> it sees me
> > pushing any buttons. Irw just runs and goes away...
> >
> > Can someone point me in the right direction?
> >
> > ---
> > Philip J. Morrison, Jr.
> > pjmorr at intrasection.com
> > This e-mail and any attached files are confidential and may
> be legally
> > privileged. They are meant for private use by the intended
> > recipient(s) only. It is strictly prohibited for anyone to copy,
> > forward, or distribute the enclosed content.
> > If this message has been received in error, please delete it along
> > with any attached files immediately and notify the sender by phone.
> >
> >
> >
> >
> >
>
>
>
More information about the mythtv-users
mailing list