[mythtv-users] lircd quit working

[Lord Darkhelmet]

Thanks for the help, its working now.   I still had the previous kernel 
installed along with the old lirc kernel modules, once they were removed 
and rebooted everything worked.  Still no idea why it quit to begin 
with,  I didn't start messing with anything until after it freaked.  
This go around I had to create a link from /dev/lirc to /dev/lirc0 which 
is odd becuase when it was initially set-up the link was not needed.

Dean.


Nick Morrott wrote:
> On 12/11/06, Lord Darkhelmet <lord_darkhelmet at accesscomm.ca> wrote:
>   
>> I had lircd working just fine under fedora 5 using a PVR-150 card and
>> remote.  Not sure what happened but the remote quit working.  After
>> restarting the lircd I tried irw to see if it was receiving.  I just
>> dropped me to a command prompt.  checking the /var/log/messages file I
>> find this:
>>
>> Nov 12 13:29:41 mythbox lircd-0.8.1-CVS[8408]: caught signal
>> Nov 12 13:29:47 mythbox lircd-0.8.1-CVS[25102]: lircd(userspace) ready
>> Nov 12 13:29:50 mythbox lircd-0.8.1-CVS[25102]: accepted new client on
>> /dev/lircd
>> Nov 12 13:29:50 mythbox lircd-0.8.1-CVS[25102]: accepted new client on
>> /dev/lircd
>> Nov 12 13:30:15 mythbox lircd-0.8.1-CVS[25102]: removed client
>> Nov 12 13:34:25 mythbox lircd-0.8.1-CVS[25102]: accepted new client on
>> /dev/lircd
>> Nov 12 13:34:47 mythbox lircd-0.8.1-CVS[25102]: removed client
>> Nov 12 13:34:58 mythbox lircd-0.8.1-CVS[25102]: accepted new client on
>> /dev/lircd
>> Nov 12 13:35:13 mythbox lircd-0.8.1-CVS[25102]: removed client
>> Nov 12 13:41:37 mythbox lircd-0.8.1-CVS[25102]: caught signal
>> Nov 12 13:41:41 mythbox lircd-0.8.1-CVS[25213]: lircd(userspace) ready
>> Nov 12 13:41:43 mythbox lircd-0.8.1-CVS[25213]: accepted new client on
>> /dev/lircd
>> Nov 12 13:41:43 mythbox lircd-0.8.1-CVS[25213]: could not get file
>> information for /dev/lirc
>> Nov 12 13:41:43 mythbox lircd-0.8.1-CVS[25213]: default_init(): No such
>> file or directory
>> Nov 12 13:41:43 mythbox lircd-0.8.1-CVS[25213]: caught signal
>>
>>
>> In my /dev I have a device called lircd not lirc.   I tried creating a
>> symlink from lirc to lircd.  This allowed irw to run with out crashing
>>     
>
> You don't want to do this.
>
>   
>> lircd but it still didn't echo any codes received from the remote.   I
>> re-installed ivtv and lirc through yum,  same results.   Then tried
>> updating the kernel, ivtv and lirc kernel modules,  same results.   Any
>> idea what happened and how to fix?   Using a digital camera I can see
>>     
>
> A missing /dev/lirc or /dev/lirc0 normally means your LIRC kernel
> modules are not loaded, or failed to load. The /dev/lircd device is
> created when lircd is running.
>
> It seems Fedora users often (always?) have to create a symlink between
> /dev/lirc and /dev/lirc0 to cater for programs that expect one or the
> other. This can be done manually, or in the udev rule that creates the
> LIRC devices. Is /dev/lircd the only LIRC device you have?
>
> $ ls -l /dev/lirc*
>
> Also, if you are running lircd as a service, check to make sure it is
> using the appropriate driver (seems to be if the Tx is working) and
> device.
>
>   
>> the remote transmitting but I have no idea how to test the IR receiver.
>>     
>
> In this case check your LIRC log output when the PVR-150 (lirc_i2c)
> modules are loaded to make sure it is picking up both receiver and
> transmitter.
>
> Nick
>