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