[mythtv-users] Lirc dead but subsys locked fc3

Nick knowledgejunkie at gmail.com
Fri Jun 24 14:24:17 UTC 2005


On 6/24/05, eric.partington at rbc.com <eric.partington at rbc.com> wrote:
>  
> 
> [root at mythbox mythtv]# /sbin/service lircd status 
> I had lirc working fine for a while and since the last reboot it has not
> been functioning at all.  I have looked at the mailing list and there seem
> to be a number of issues that people are trying to sort out.  I just wanted
> to see if there was any more direct solutions floating around. 
> 
> I have an FC3 box with lirc 0.7.1 running the latest stable mythtv rpm
> release. 
> As you can see below when I start lirc it looks fine but after using the
> remote it locks up 
> lircd (pid 5572) is running... 
> [root at mythbox mythtv]# /sbin/service lircd status 
> lircd (pid 5572) is running... 
> [root at mythbox mythtv]# /sbin/service lircd status 
> 
> lircd dead but subsys locked 
> 
> There was no character device in /dev/ before so I created one, not sure if
> that made it any worse.  Judging from the error message that I get in
> /var/log/messages it looks like lirc is looking for /dev/lirc but cant find
> it. 
> 
> [root at mythbox mythtv]# ls -la /dev/li* 
> crw-r--r--  1 root root 61, 0 Jun 24 09:07 /dev/lirc 
> srw-rw-rw-  1 root root     0 Jun 23 22:40 /dev/lircd 
> 
> Jun 23 22:40:01 localhost kernel: lirc_dev: IR Remote Control driver 
> registered, at major 61 
> Jun 23 22:40:16 localhost lircd-0.7.1[3901]: lircd(any) ready 
> Jun 23 22:40:16 localhost lircd: lircd startup succeeded 
> Jun 23 22:40:31 localhost lircd-0.7.1[3901]: accepted new client on 
> /dev/lircd 
> Jun 23 22:40:31 localhost lircd-0.7.1[3901]: could not get file 
> information for /dev/lirc 
> Jun 23 22:40:31 localhost lircd-0.7.1[3901]: default_init(): No such 
> file or directory 
> Jun 23 22:40:31 localhost lircd-0.7.1[3901]: caught signal 
> 
> Any ideas as to how to solve this.  I found a patch on the atrpms bugzilla
> site but don't know how to apply a diff patch.  I tried patch XXX.diff and
> it just sat there doing nothing. 
> 
> Any help is greatly appreciated. 

Eric,

As you're running FC3, you may need an appropriate udev rule to make
sure the LIRC devices are recreated at each boot. There are a couple
of examples in the list archive
http://www.gossamer-threads.com/lists/mythtv/users/ (their search
seems down at the moment).

One other LIRC-related issue is whether myth is trying to use the
correct device (one time I had to symlink lirc to lirc0 I think).

These are the devices on my FC2 (non-udev) machine for your info:

crwxrwxrwx  1 root   root   61, 0 May 20 20:16 /dev/lirc
srwxrwxrwx  1 mythtv mythtv     0 Jun 22 21:14 /dev/lircd

Nick


More information about the mythtv-users mailing list