[mythtv-users] LIRCD problems with FC4

Thom Paine painethom at gmail.com
Mon Nov 21 22:49:09 EST 2005


I tried all the info in this post.

I do have /dev/lirc
[root at mythmbe dev]# ll lirc*
lrwxrwxrwx 1 root root 5 Nov 21 17:18 lirc -> lirc0
crw-rw---- 1 root root 61, 0 Nov 21 17:18 lirc0
srw-rw-rw- 1 root root 0 Nov 21 22:39 lircd
[root at mythmbe dev]#

I tried irrecord -d /dev/lirc thom.txt and I just get a gap error.

I re-downloaded the lircd.conf file from Jarod's site, and reinstalled it to
be sure I had the right one in the first place.

I know the hardware is good, as I had this working several times before. I'm
still trying to get settled with a good master back end. This was supposed
to be the last install on this rig.

Thanks for all the help so far. Very appreciated.

On 11/21/05, R. Geoffrey Newbury <newbury at mandamus.org> wrote:
>
> On Mon, 21 Nov 2005 19:23:34 +0000, Nick wrote:
>
> >On 05/09/05, Myth <myth at tacgun.com> wrote:
> >>
> >> Hauppauge PVR-350 (Brand new - series 991)
> >> Running absolute latest version of Fedora Core
> >> Following step-by-step instructions from http://wilsonet.com/mythtv/
> >> When I get to the part that tells me to start LIRCD - nothing happens.
> >> I check /var/log/messages and find the following:
>
> <Big snip>
> >> Sep 4 16:16:00 myth modprobe: FATAL: Error inserting bttv
> >> (/lib/modules/2.6.12-1.1447_FC4/kernel/drivers/media/video/bttv.ko):
> >> Unknown symbol in module, or unknown parameter (see dmesg)
> >> Sep 4 16:16:00 myth kernel: bttv: Unknown symbol tveeprom_read
> >> Sep 4 16:16:00 myth kernel: bttv: Unknown symbol
> tveeprom_hauppauge_analog
> >> Sep 4 16:16:01 myth modprobe: WARNING: Error inserting cx88xx
> >> (/lib/modules/2.6.12-
> 1.1447_FC4/kernel/drivers/media/video/cx88/cx88xx.ko):
> >> Unknown symbol in module, or unknown parameter (see dmesg)
> >> Sep 4 16:16:01 myth modprobe: FATAL: Error inserting cx8800
> >> (/lib/modules/2.6.12-
> 1.1447_FC4/kernel/drivers/media/video/cx88/cx8800.ko):
> >> Unknown symbol in module, or unknown parameter (see dmesg)
> >> Sep 4 16:16:01 myth kernel: cx88xx: Unknown symbol tveeprom_read
> >> Sep 4 16:16:01 myth kernel: cx88xx: Unknown symbol
> >> tveeprom_hauppauge_analog
> >> Sep 4 16:16:01 myth kernel: cx8800: Unknown symbol cx88_reset
> >> Sep 4 16:16:01 myth kernel: cx8800: Unknown symbol
> cx88_call_i2c_clients
>
> This bit implies that you are trying to load the cx8800 module but you do
> not have a bttv card in the machine..
>
>
> >> Sep 4 16:16:01 myth kernel: lirc_i2c: chip found @ 0x18 (Hauppauge IR)
> >> Sep 4 16:16:01 myth kernel: ivtv: i2c attach [client=Hauppauge IR,ok]
> >> Sep 4 16:16:01 myth kernel: lirc_dev: lirc_register_plugin:
> sample_rate: 10
>
> This bit implies that you have:
> modprobe lirc_i2c
> modprobe lirc_dev
> modprobe lirc_yourdriver
>
> in modprobe,conf... so far so good if true.
>
> >At this point, what does (as root):
> >
> >'service lircd status'
> >
> >give? If it says it's running, you should be good to go as long as you
> >have a suitable lircd.conf file in /etc and have your receiver plugged
> >into the correct plug on the back of the card. If it says 'lircd dead,
> >but subsystem locked' it may likely be a udev issue related to device
> >creation (lircd may be trying to use a device that doesn't exist)
>
> OR, it failed without cleaning up after itself.
> look in /var/log/subsys for a 'lircd' file.
>
> OR udev created a file socket /dev/lirc/0 for example but lircd is
> looking for /dev/lirc
> you need udev to create a symlink to /dev/lirc from /dev/lirc/0 if that is
> the case. (Check the archives at gossamer-threads... I wrote something
> about this this morning).
>
> FINALLY, make sure that when lircd is started as a daemon that you call
> the correct file socket... that is, call it with -d /dev/lirc or whatever,
> to make sure where it is looking.
>
> Note that if you do not have the correct permissions (including in init.d)
> the init.d script will fail at "rm'ing" the file. The script does that if
> it is run properly.
>
> >To run irw, you need lircd running. To run irrecord (to see if
> >anything is being received) you do not want lircd running.
>
> Conversely and this can be a real gotcha, you cannot have lircd running to
> test with mode2...The idea is to test with mode2 to see if the 'frontend'
> hardware works, then start lircd and try the daemon backend.
>
> Test both mode2 and irw with their -d /dev/lirc options. If those do but
> something else does not, then you can guess what is not going on.
>
> >Finally, check to see whether you have a /var/log/lircd.log file as
> >this may give some useful info (I'm not sure if the atrmp binaries
> >include the separate logging support built in).
>
> If the rpm does not, consider compiling from source and exercise that
> option..
>
> Geoff
>
> R. Geoffrey Newbury newbury at mandamus.org
> Barrister and Solicitor Telephone: 905-271-9600
> Mississauga,Ontario, Canada Facsimile: 905-271-1638
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
>



--
-=/>Thom
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mythtv.org/pipermail/mythtv-users/attachments/20051121/57e24c1e/attachment.htm


More information about the mythtv-users mailing list