Verify the permissions on the lirc devices are 666

I am pretty sure once I had to pass --permission=666 --device=/dev/lirc/lirc0 because the devices were created with 600 permissions and lircd was looking for /dev/lirc which was actually a directory....


Ant Daniel wrote:



On 10/17/05, *Jon Kunze* <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote:

    I tried the symlink, and it seemed to work... until i rebooted.

    So now I've got bigger problems. Like before, I uninstalled lirc
    via yum and then tried to reinstall yum, which fixed the problem
    before, but only until I rebooted.

    I did the following

    # yum remove lirc-kmdl-$KVER
    # yum remove lirc

    then I did

    # yum install lirc-kmdl-$KVER
          This line fails as it says there is no match for my kernel
    # yum install lirc
          This one goes fine

    Then I do the

    # /sbin/depmod -a
    # /sbin/modprobe lirc_i2c
          No moduble lirc_i2c found
    # /sbin/chkconfig lircd on
    # /sbin/service lircd start      [OK]

    Then when I run either irw or mythfrontend, I get "lircd dead, but
    subsys locked" again.


    Any ideas on this? Unfortunately I'm at work right now, so I can't
    put the exact error messages in this email, but I will be able to
    later tonight if anyone has any ideas. Thanks.



    On 9/30/05, *Nick* <[EMAIL PROTECTED]
    <mailto:[EMAIL PROTECTED]>> wrote:

        On 30/09/05, Jon Kunze <[EMAIL PROTECTED]
        <mailto:[EMAIL PROTECTED]>> wrote:


---------- Forwarded message ----------
From: Jon Kunze < [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>>
Date: Sep 29, 2005 7:08 PM
 Subject: Re: [mythtv-users] Re: lircd starts fine, but
        crashes as soon as
something tries to use it
To: Nate Thompson < [EMAIL PROTECTED]
        <mailto:[EMAIL PROTECTED]>>

Ok, when I try the symlink, it says /dev/lirc already exists.
        Any ideas?
Removing the /dev/lirc and the doing the symlink goes
        through, but still
when I start the frontend lirc locks.

        Does the LIRC log give any useful info when it fails now?

        You can also start lircd using the parameter --device=/dev/lirc0 -
        does this work at all?

        Nick



    _______________________________________________
    mythtv-users mailing list
    [email protected] <mailto:[email protected]>
    http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


After a recent update I was also having this problem (using FC3) when the symlink is set there was no problems, but the link was lost on reboot.

I solved it on my setup by editing /etc/sysconfig/lircd:
# Options to lircd
LIRCD_OPTIONS="-d /dev/lirc0"

This then gets lircd to look at the already existing /dev/lirc0 rather than the missing /dev/lirc

------------------------------------------------------------------------

_______________________________________________
mythtv-users mailing list
[email protected]
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


--
Allan McIntosh

Software Designer


Atreus Systems, Inc.

613-233-1741 ext: 217 (Office)
613-233-8204 (Fax)

[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> www.atreus-systems.com <http://www.atreus-systems.com/>

_______________________________________________
mythtv-users mailing list
[email protected]
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

Reply via email to