[mythtv-users] lirc rebooting woes

[Ed]

I had the same problem, and I think I just fixed it after 4 days of 
playing with it. I'm not really sure how all this works or why this 
worked for me, but maybe it will work for you too. My problem was 
related to something with udev. I tried the fix for it that is in 
located here http://bugzilla.atrpms.net/ (search of udev) that Jarod 
suggested but that did nothing  however when i ran this command:

cp -rp /dev/lirc* /etc/udev/devices/

It seemed to fix the problem. I think this is copying the lirc dev 
syslink so they are created again at next reboot, but I'm not to 
familiar with how udev works so i'm not to sure the details. I hope 
this works for you. Please report back your outcome, and if anyone can 
explain a little more in-depth what is going on here please do. Thanks 
for everyone's input  that got me this far.


On Dec 8, 2004, at 2:59 PM, nate s wrote:

> try modprobing it again.  Even though it's already loaded, if the
> lirc_i2c gets loaded first, it won't work.
>
> -Nate
>
>
> On Wed, 08 Dec 2004 07:04:13 -0600, Richard C. Isaacson
> <ri at beldurnik.com> wrote:
>> Hey I was wondering if anyone had crossed this before. I am having
>> problems with my lirc after reboot. I can not get it to run 
>> correctly. I
>> modprobem ivtv and lirc_i2c. These look like they are coming up ok.
>> Though when I go and try to start up lircd and test through irw it 
>> just
>> exits out. I get the following in my /var/log/messages:
>>
>> Dec  8 06:41:38 myth kernel: lirc_dev: IR Remote Control driver
>> registered, at major 61
>> Dec  8 06:41:38 myth kernel: bttv: driver version 0.9.15 loaded
>> Dec  8 06:41:38 myth kernel: bttv: using 8 buffers with 2080k (520
>> pages) each for capture
>> Dec  8 06:41:38 myth kernel: lirc_i2c: chip found @ 0x18 (Hauppauge 
>> IR)
>> Dec  8 06:41:38 myth kernel: ivtv: i2c attach [client=Hauppauge IR,ok]
>> Dec  8 06:41:38 myth kernel: lirc_dev: 
>> lirc_register_plugin:sample_rate: 10
>> Dec  8 06:42:05 myth lircd 0.7.0[3472]: lircd(any) ready
>> Dec  8 06:42:05 myth lircd: lircd startup succeeded
>> Dec  8 06:42:07 myth lircd 0.7.0[3472]: accepted new client on 
>> /dev/lircd
>> Dec  8 06:42:07 myth lircd 0.7.0[3472]: could not get file information
>> for /dev/lirc
>> Dec  8 06:42:07 myth lircd 0.7.0[3472]: default_init(): No such file 
>> or
>> directory
>> Dec  8 06:42:07 myth lircd 0.7.0[3472]: caught signal
>> Dec  8 06:59:30 myth lircd 0.7.0[3489]: lircd(any) ready
>> Dec  8 06:59:30 myth lircd: lircd startup succeeded
>> Dec  8 06:59:33 myth lircd 0.7.0[3489]: accepted new client on 
>> /dev/lircd
>> Dec  8 06:59:33 myth lircd 0.7.0[3489]: could not get file information
>> for /dev/lirc
>> Dec  8 06:59:33 myth lircd 0.7.0[3489]: default_init(): No such file 
>> or
>> directory
>> Dec  8 06:59:33 myth lircd 0.7.0[3489]: caught signal
>>
>> It worked fine after I had just installed it. Though when I went to
>> reboot it broke. Anyone have an idea?
>>
>> uname -a = Linux myth.beldurnik.com 2.6.9-1.681_FC3 #1 Thu Nov 18
>> 15:13:22 EST 2004 x86_64 x86_64 x86_64 GNU/Linux
>>
>> -rich
>>
>> _______________________________________________
>> mythtv-users mailing list
>> mythtv-users at mythtv.org
>> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
>>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users