[mythtv-users] Re: Lirc irw problems...

[Shay - MythTV]

At 03:35 PM 9/16/2003, you wrote:
>On Tuesday, Sep 16, 2003, at 08:18 US/Pacific, Shay - MythTV wrote:
>
>>At 08:10 AM 9/16/2003, Axel wrote:
>>>On Tue, Sep 16, 2003 at 07:47:17AM -0500, Shay - MythTV wrote:
>>> >
>>> > Jarod,
>>> >
>>> > Thanks for looking.  Here is my modules.conf.
>>> >
>>> > # For ivtv
>>> > path[toplevel]=/lib/modules/`uname -r'/drivers/media/video
>>> > # For bttv and saa7134
>>> > path[toplevel]=/lib/modules/`uname -r`/v412
>>> > # default path
>>> > path[toplevel]=/lib/modules/`uname -r`
>>>
>>>Look at the first `uname -r`: The second backtick is mistyped.
>>>
>>>Fix that and run depmod. Then have a look at
>>>/lib/modules/`uname -r`/modules.dep
>>>It should mention the desired modules before the legacy ones, and
>>>dependencies should be drawing the new modules.
>>>
>>>If all ist right, unload all associated modules and restart your apps,
>>>the modules should load correctly.
>>>--
>>
>>Thanks for the help Axel!  I'll have to wait to try it till I get 
>>home.  I also have no sound with my video,  I'm hoping this fixes that 
>>too, it would be too sweet though I'm sure.. ;)
>
>I'd say there's actually a good chance that'll fix your sound issue also. 
>Without the proper line, as Axel pointed out, it is very likely the wrong 
>msp3400 is getting loaded, and thus the audio problems.
>

So it fixed my audio problem, but not my original problem which was with 
Lirc.  Here is what I do, and subsequently get in the log:

/sbin/depmod -a
/sbin/modprobe lirc_dev

sep 17 08:34:33 localhost kernel: lirc_dev: ir remote control driver 
registered, at major 61

/sbin/modproe lirc_i2c

sep 17 08:34:39 localhost kernel: i2c-core.o: i2c core module version 2.8.0 
(20030714)
sep 17 08:34:39 localhost kernel: linux video capture interface: v1.00
sep 17 08:34:39 localhost kernel: bttv: driver version 0.7.104 loaded
sep 17 08:34:39 localhost kernel: bttv: using 4 buffers with 2080k (8320k 
total) for capture
sep 17 08:34:39 localhost kernel: bttv: host bridge is via technologies, 
inc. vt8363/8365 [kt133/km133]
sep 17 08:34:39 localhost kernel: bttv: host bridge is via technologies, 
inc. vt82c686 [apollo super acpi]
sep 17 08:34:39 localhost kernel: linux video capture interface: v1.00
sep 17 08:34:39 localhost kernel: bttv: driver version 0.9.11 loaded
sep 17 08:34:39 localhost kernel: bttv: using 8 buffers with 2080k (520 
pages) each for capture
sep 17 08:34:39 localhost kernel: bttv: host bridge is via technologies, 
inc. vt8363/8365 [kt133/km133]
sep 17 08:34:39 localhost kernel: bttv: host bridge is via technologies, 
inc. vt82c686 [apollo super acpi]
sep 17 08:34:39 localhost insmod: 
/lib/modules/2.4.20-20_29.rh9.at/kernel/drivers/media/video/bttv.o: 
init_module: no such device
sep 17 08:34:39 localhost insmod: hint: insmod errors can be caused by 
incorrect module parameters, including invalid io or irq 
parameters.       you may find more information in syslog or the output 
from dmesg
sep 17 08:34:39 localhost insmod: 
/lib/modules/2.4.20-20_29.rh9.at/v4l2/bttv.o:init_module: no such device
sep 17 08:34:39 localhost insmod: hint: insmod errors can be caused by 
incorrect module parameters, including invalid io or irq 
parameters.       you may find more information in syslog or the output 
from dmesg
sep 17 08:34:39 localhost insmod: 
/lib/modules/2.4.20-20_29.rh9.at/v4l2/bttv.o:insmod bttv failed
sep 17 08:34:39 localhost modprobe: modprobe: can't locate module rivatv

/usr/bin/irw

sep 17 08:39:14 localhost lircd 0.7.0pre2[2825]: accepted new client on 
/dev/lircd
sep 17 08:39:14 localhost lircd 0.7.0pre2[2825]: could not open /dev/lirc
sep 17 08:39:14 localhost lircd 0.7.0pre2[2825]: default_init(): no such device
sep 17 08:39:14 localhost lircd 0.7.0pre2[2825]: caught signal


-Shay