<br><br><div><span class="gmail_quote">On 3/2/07, <b class="gmail_sendername">Nick Morrott</b> <<a href="mailto:knowledgejunkie@gmail.com">knowledgejunkie@gmail.com</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 02/03/07, <a href="mailto:nightshade@podiluk.com">nightshade@podiluk.com</a> <<a href="mailto:nightshade@podiluk.com">nightshade@podiluk.com</a>> wrote:<br>> Hello,<br>><br>> I'm trying to get MythTv installed on FC6. I've followed the excellent
<br>> guide by Jarod. I did the part setting up lirc and when I used irw I did<br>> get output when I pressed the buttons. I continued on with the install and<br>> everything went fine and I can watch TV and recored shows. I went to go
<br>> use my remote and nothing... I tried using irw to test and it just returns<br>> back to the prompt without doing anything. I have a MCE USB RC6 remote.<br>><br>> Here are logs and config files of everything I can think of:
<br>><br></blockquote></div>I recently ran into a similar problem as yours on my FC6 box, except I have a ATI USB remote. I have been running this system as a Myth frontend for about a year without any issues with lirc. Then I did the most recent kernel upgrade and it broke lirc for some reason. What I found is that there were three modules loaded for my remote: lirc_atiusb, lirc_dev, and ati_remote. I haven't really had time to fully investigate, but it seems that the ati_remote module wasn't playing well with the other two. Now, these coexisted fine on previous kernels, but for some reason won't work with the latest one. I searched around on Google and came up with a hit for someone who had a similar problem under FC5. He simply renamed the ati_remote module and that fixed the problem. I did the same and everything seems to be working now. I think I could have accomplished the same thing by blacklisting the ati_remote module.
<br><br>Not 100% the same problem as yours due to the different remotes. But I was getting the exact same symptoms; modules loading, lircd starting, and then crashing with the "no /dev/lirc" message as soon as I fired up Myth front-end. Perhaps you have another module loading that is interfering with lirc.
<br><br>