<blockquote style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;" class="gmail_quote"><font color="black" face="Verdana,Arial,Helvetica" size="2"><font color="black" face="Verdana,Arial,Helvetica" size="2"><font color="#660066">> Just a guess, but is the service started? <br>
> <br>>
"service lirc start" <br></font> <br>The device node /dev/lirc0 is
created when the lirc kernel driver <br>successfully loads, not when
lircd is started. <br> <br><font color="#660066">> I had the same
problem on FC10 so I just added something like this to <br>>
/etc/rc.d/rc.local : <br>> <br>> if [ ! -e /dev/lirc0 ]; then <br>>
mknod /dev/lirc0 c 61 0 <br>> chown root:root /dev/lirc0 <br>>
chmod 660 /dev/lirc0 <br>> fi <br>> <br>> Kinda hackey, but it
worked. <br></font> <br>Um. No. It didn't. Trust me. The only thing it
might possibly have <br>done is make lirc happy because its got a device
node to connect to <br>before the driver is actually registered.
Current lirc will actually <br>happily start up and wait for the device
node to appear. But a driver <br>*must* get loaded and *must* register
an lirc device for something to <br>actually be backing /dev/lircX.
Simply creating the device node does <br>NOT accomplish that. <br> <br><font color="#660066">> This post might help: <br>> <a href="http://www.linuxquestions.org/questions/slackware-14/lirc-linux-remote-control-isnt-setting-up-dev-properly-udev-problem-599664/" rel="nofollow" target="_blank">http://www.linuxquestions.org/questions/slackware-14/lirc-linux-remote-control-isnt-setting-up-dev-properly-udev-problem-599664/</a>
<br></font> <br>No, the real answer is this: the hdpvr ir enable patch
was <br>accidentally dropped from the Fedora kernels when they were
rebased <br>from 2.6.31 to 2.6.32, and I haven't got around to putting
it back in <br>place. In other words, its not going to work until he's
got an hdpvr <br>driver patched to enable the ir part. <br> <br>-- <br>Jarod
Wilson <br>jarod [at] wilsonet </font></font></blockquote><div><br>Sheesh! Did someone pee in your corn flakes this morning?<br><br>I never claimed to be an expert, nor to know the exact problem causing the OPs issue. I was simply stating what worked for *me* and offering *possible* solutions. Nothing was stated as fact and I'm sure people on this list are smart enough to make that distinction. Your sarcastic remarks and down-talking were unnecessary and unwarranted.<br>
<br>I had perceived you as good guy helping out the community by, among other things, creating the Fedora setup guides. I had used your guides several times to set up my own myth machines and can truly say that I appreciate their existence, but I now realize that they were only created in a vain attempt to demonstrate your "linux superiority".<br>
<br>I re-read your reply several times in the voice of The Comic Book Guy from The Simpsons and it made me laugh. So, thanks for that at least.<br></div>