On 16/01/06, Luke <[EMAIL PROTECTED]> wrote: > I have finally installed lirc for my MythTV box. I can start the lircd > daemon [OK]. If I check the status soon after, I see that the daemon is > running. However, if I run /usr/bin/irw I get no output and the lircd daemon > dies. My log files show the following entries: > > Jan 16 21:26:55 media lircd-0.8.0-CVS[3464]: lircd(userspace) ready > Jan 16 21:27:10 media lircd-0.8.0-CVS[3464]: accepted new client on > /dev/lircd > Jan 16 21:27:10 media lircd-0.8.0-CVS[3464]: could not get file information > for /dev/lirc > Jan 16 21:27:10 media lircd-0.8.0-CVS[3464]: default_init(): No such file or > directory > Jan 16 21:27:10 media lircd-0.8.0-CVS[3464]: caught signal > > Jan 16 21:27:28 media lircd-0.8.0-CVS[3497]: lircd(userspace) ready > Jan 16 21:27:47 media lircd-0.8.0-CVS[3497]: accepted new client on > /dev/lircd > Jan 16 21:27:47 media lircd-0.8.0-CVS[3497]: could not get file information > for /dev/lirc > Jan 16 21:27:47 media lircd-0.8.0-CVS[3497]: default_init(): No such file or > directory > Jan 16 21:27:47 media lircd-0.8.0-CVS[3497]: caught signal > > What could be the problem here? My remote input is onboard the Prolink > PixelView PlayTV Pro card (a bttv bt878 card).
Simple question - the log states that /dev/lirc does not exist - is this true? It is entirely possible that /dev/lirc0 _does_ exist but the lircd startup script is defaulting to use /dev/lirc. Creating symlink from /dev/lirc0 to /dev/lirc (if this is the case) should fix it. Make sure the symlink has appropriate access permissions for mythtv users. You can also edit the startup script to explicitly set the device, but the symlink is easier. I use a udev rule to make sure the symlink is created at boot as some applications may look for /dev/lirc and others /dev/lirc0. Nick _______________________________________________ mythtv-users mailing list [email protected] http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
