<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Nick wrote:
<blockquote
cite="mid5387cd30607061346q4b0f2a2t4f427a4888fdb3b8@mail.gmail.com"
type="cite">
<pre wrap="">What does
# lsmod |grep "lirc"
give?
</pre>
</blockquote>
[root@sandstorm recordings]# /sbin/lsmod | grep lirc<br>
lirc_i2c 8068 0<br>
lirc_dev 12448 1 lirc_i2c<br>
i2c_core 21697 15
cx88xx,bttv,i2c_algo_bit,lirc_i2c,it87,eeprom,i2c_isa,msp3400,saa7115,wm8775,cx25840,tda9887,tuner,ivtv,tveeprom<br>
<br>
<blockquote
cite="mid5387cd30607061346q4b0f2a2t4f427a4888fdb3b8@mail.gmail.com"
type="cite">
<blockquote type="cite">
<pre wrap="">I've read this post
<a class="moz-txt-link-freetext" href="http://www.mythtv.org/pipermail/mythtv-users/2004-April/040219.html">http://www.mythtv.org/pipermail/mythtv-users/2004-April/040219.html</a>
and it looks like I have the same or similar problem: the installed LIRC
was not compiled for my Hauppauge card.
Note that lirc_i2c is not in the list below.
# /usr/sbin/lircd --driver=help
</pre>
</blockquote>
<pre wrap=""><!---->
LIRC kernel modules use the 'default' driver, and so are not listed. I
get the same output on my system (using lirc_serial) and this is also
</pre>
</blockquote>
<br>
Thanks, you saved me wasting my time with that.<br>
<br>
<blockquote
cite="mid5387cd30607061346q4b0f2a2t4f427a4888fdb3b8@mail.gmail.com"
type="cite">
<pre wrap="">For interest, I'm using 2.6.16-1.2111_FC4 with the following RPMs installed:
lirc-kmdl-2.6.16-1.2111_FC4-0.8.1-cvs20060325_58.rhfc4.at
lirc-lib-devel-0.8.1-cvs20060325_58.rhfc4.at
lirc-lib-0.8.1-cvs20060325_58.rhfc4.at
lirc-0.8.1-cvs20060325_58.rhfc4.at
lirc-devices-0.7.0-1.rhfc4.at
</pre>
</blockquote>
Mine aren't exactly the same but I don't see anything wrong with them.
You have the development version of lirc-lib. That could be
significant.<br>
<pre>[root@sandstorm etc]# yum list installed "*lirc*"
Installed Packages
lirc.i386 0.8.1-cvs20060325_58.r installed
lirc-devices.noarch 0.7.0-1.rhfc4.at installed
lirc-kmdl-2.6.16-1.2111_FC4.i686 0.8.1-cvs20060325_58.r installed
lirc-lib.i386 0.8.1-cvs20060325_58.r installed
[root@sandstorm etc]#
</pre>
<blockquote
cite="mid5387cd30607061346q4b0f2a2t4f427a4888fdb3b8@mail.gmail.com"
type="cite">
<pre wrap="">You can check whether you have kernel modules installed for the
current running kernel with:
# find /lib/modules/`uname -r`/ -name lirc*.ko
(You may need to run a depmod after they are freshly installed to
update module dependencies)
</pre>
</blockquote>
[root@sandstorm recordings]# find /lib/modules/`uname -r`/ -name
lirc*.ko<br>
/lib/modules/2.6.16-1.2111_FC4/updates/drivers/lirc/lirc_sasem.ko<br>
/lib/modules/2.6.16-1.2111_FC4/updates/drivers/lirc/lirc_mceusb2.ko<br>
/lib/modules/2.6.16-1.2111_FC4/updates/drivers/lirc/lirc_i2c.ko<br>
/lib/modules/2.6.16-1.2111_FC4/updates/drivers/lirc/lirc_cmdir.ko<br>
/lib/modules/2.6.16-1.2111_FC4/updates/drivers/lirc/lirc_mceusb.ko<br>
/lib/modules/2.6.16-1.2111_FC4/updates/drivers/lirc/lirc_it87.ko<br>
/lib/modules/2.6.16-1.2111_FC4/updates/drivers/lirc/lirc_igorplugusb.ko<br>
/lib/modules/2.6.16-1.2111_FC4/updates/drivers/lirc/lirc_dev.ko<br>
/lib/modules/2.6.16-1.2111_FC4/updates/drivers/lirc/lirc_bt829.ko<br>
/lib/modules/2.6.16-1.2111_FC4/updates/drivers/lirc/lirc_serial.ko<br>
/lib/modules/2.6.16-1.2111_FC4/updates/drivers/lirc/lirc_parallel.ko<br>
/lib/modules/2.6.16-1.2111_FC4/updates/drivers/lirc/lirc_atiusb.ko<br>
/lib/modules/2.6.16-1.2111_FC4/updates/drivers/lirc/lirc_imon.ko<br>
/lib/modules/2.6.16-1.2111_FC4/updates/drivers/lirc/lirc_sir.ko<br>
/lib/modules/2.6.16-1.2111_FC4/updates/drivers/lirc/lirc_gpio.ko<br>
/lib/modules/2.6.16-1.2111_FC4/updates/drivers/lirc/lirc_streamzap.ko<br>
[root@sandstorm recordings]# <br>
<br>
<blockquote
cite="mid5387cd30607061346q4b0f2a2t4f427a4888fdb3b8@mail.gmail.com"
type="cite">
<pre wrap=""><a class="moz-txt-link-freetext" href="http://lirc.cvs.sourceforge.net/lirc/lirc/remotes/hauppauge/lircd.conf.hauppauge?view=markup">http://lirc.cvs.sourceforge.net/lirc/lirc/remotes/hauppauge/lircd.conf.hauppauge?view=markup</a>
This now becomes your /etc/lircd.conf file.
</pre>
</blockquote>
I downloaded that file and removed all the configs except the one that
was for "Hauppague A415-HPG" because that is the model number inside
the battery door of my remote.<br>
<br>
<blockquote
cite="mid5387cd30607061346q4b0f2a2t4f427a4888fdb3b8@mail.gmail.com"
type="cite">
<pre wrap="">You also need to ensure that lircd is starting with the correct
device. On FC4 you normally put any run-time options for lircd in
/etc/sysconfig/lircd (i.e. which device to use, however when using
only 1 kernel module I don't believe you need to pass that.).
</pre>
</blockquote>
So I edited /etc/sysconfig/lircd to have...<br>
<br>
# Options to lircd<br>
LIRCD_OPTIONS="--permission=777 --driver=default --device/dev/lirc1"<br>
<br>
And I restarted lircd<br>
(I varied the device again between lirc0 and lirc1)<br>
<br>
<blockquote
cite="mid5387cd30607061346q4b0f2a2t4f427a4888fdb3b8@mail.gmail.com"
type="cite">
<pre wrap="">With lircd using the correct device, irw should now just work, using
the key names from the newly installed lircd.conf.
</pre>
</blockquote>
No change. irrecord gives the gap error and irw shows nothing.<br>
I really wish it would just work. <sigh><br>
<br>
Scott<br>
<br>
</body>
</html>