IRW killing LIRC Daemon ... Troubleshooting advice?

[jert]

Greetings, all.

First of all, I just want to say thankyou to the Linux byopvr community ... the posts here have saved me a major headache on more than one occasion.  But I don't seem to be able to find a solution to my current issue ...

I'm building a MythTV build on Fedora Core 3, using an ATI XT800Pro for TV-output and a Hauppauge WinTV PVR-150 for video capture. 

Yes, I know ... ATI = run for the hills!  Don't worry, I was able to solve those problems on my own.  My current issue, however, is with LIRC.

If I start up lircd -n (no daemon mode) and watch the output, starting up irw kills the daemon.  If I try to run irw a second time, I get a connection refused error ... and sure enough, the ps shows that lircd is no longer running. 

I'm using the LIRC 0.7.1 build, which is supposed to support the PVR 150 card, and I've got the newer black and grey Hauppauge remote ... from dmesg, it appears that all of the ivtv and lirc drivers are loading correctly.  Of course, the next question is always 'How about your lircd log?' ... but for some reason, it doesn't exist.

Can someone provide me with some guidance as to how to approach the troubleshooting of this problem?  I'm away from the box for a few hours now (needed a sanity break), so I won't be able to post logs for a bit ... but any help or advice people could provide in the meantime would be much appreciated.

Many thanks!
-Jeremy

[bouchecl]

Greetings, all.

First of all, I just want to say thankyou to the Linux byopvr community ... the posts here have saved me a major headache on more than one occasion.  But I don't seem to be able to find a solution to my current issue ...

I'm building a MythTV build on Fedora Core 3, using an ATI XT800Pro for TV-output and a Hauppauge WinTV PVR-150 for video capture. 

[...]

Can someone provide me with some guidance as to how to approach the troubleshooting of this problem?  I'm away from the box for a few hours now (needed a sanity break), so I won't be able to post logs for a bit ... but any help or advice people could provide in the meantime would be much appreciated.

Thanks. We try.

lirc gave me some headaches early on. But that's part of the fun!

I would check a couple of things:

Have you done EVERYTHING Jarod suggests in his howto, including the paragraph called "UPDATE"? It is important for instance to load both drivers very early in the boot process...

What version of the ivtv driver are you running? PVR-150 support is recent in ivtv and the developers are still tweaking with it. FWIW, I run lirc 0.7.1 with ivtv 0.36w (both from ATrpms) on a FC3 installation, although, my IR receiver is connected to a PVR-250.

[jert]

Thanks for your reply.

I hadn't got as far as the UPDATE section, as I wanted to get it working manually before I started worrying about the 'at boot time' configuration.  As it is, I've managed to hack things together ... although I don't know whether there are any downsides to the way I fixed things.

I'm also running lirc 0.71 with ivtv 0.3.6w from ATrpms.  From the Lircd output before it would shut itself down, combined with a few hours of searching forums, I realized that the issue was with udev adding the 0 to my lirc device ...

ls /dev/lirc* was giving me '/dev/lircd' and '/dev/lirc0', but no /dev/lirc.

In the end, I started up the daemon (to create the /dev/lirc0 device) and used "ln -s /dev/lirc0 /dev/lirc" to create a symbolic link that would redirect the daemon to the actual device.  From that point I was able to get irw to stay up long enough to verify the IR receiver was working, and the rest of the setup went smooth as cake.

I don't know how valid a fix like this really is ... but as long as it has me up and running, I'm happy. 

[JayRCz]

That is one way to fix the problem. Another way is to start lircd using   lircd -d /dev/lirc0    I had the same problem and that's how I fixed it.