[mythtv-users] Re: My Lirc problems - I'm dying here..

[Shay - MythTV]

At 12:38 AM 9/18/2003, you wrote:
>On Wednesday, Sep 17, 2003, at 13:49 US/Pacific, Axel Thimm wrote:
>
>>On Wed, Sep 17, 2003 at 10:24:47AM -0500, Shay - MythTV wrote:
>>>I posted these to the Lirc list, but its a pretty quite list and I haven't
>>>gotten a response, so I thought I'd ask some of the great people here on
>>>the MythTV list...
>>>
>>>I have a PVR-250 with the grey remote. [...]
>>>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
>>
>>Shouldn't you be using the ivtv driver for a PVR-250 instead of the
>>bttv one?
>
>Something is definitely still out of whack... However, I see bttv stuff 
>load up on my fully functional system also (and no bttv card in it):
>
>Sep 10 20:47:44 buddah kernel: i2c-core.o: i2c core module version 2.8.0 
>(20030714)
>Sep 10 20:47:44 buddah kernel: ivtv: Found an iTVC16 based chip
>Sep 10 20:47:44 buddah kernel: PCI: Found IRQ 10 for device 00:07.0
>Sep 10 20:47:44 buddah kernel: PCI: Sharing IRQ 10 with 00:06.2
>Sep 10 20:47:44 buddah kernel: PCI: Sharing IRQ 10 with 00:10.2
>Sep 10 20:47:44 buddah kernel: tuner: probing ivtv i2c driver #0 i2c 
>adapter [id=0x10005]
>Sep 10 20:47:44 buddah kernel: tuner: chip found @ 0xc2
>Sep 10 20:47:44 buddah kernel: tuner(bttv): type forced to 2 (Philips NTSC 
>(FI1236,FM1236 and compatibles)) [insmod]
>Sep 10 20:47:44 buddah kernel: saa7114.c: starting probe for adapter ivtv 
>i2c driver #0 (0x10005)
>Sep 10 20:47:44 buddah kernel: saa7114.c: detecting saa7114 client on 
>address 0x42
>Sep 10 20:47:44 buddah kernel: saa7115.c: writing init values
>Sep 10 20:47:44 buddah kernel: status: (1E) 0x89, (1F) 0xb1
>Sep 10 20:47:44 buddah kernel: msp34xx: init: chip=MSP3435G-B6, has NICAM 
>support
>Sep 10 20:47:44 buddah kernel: msp3410: daemon started
>Sep 10 20:47:44 buddah kernel: ivtv: Encoder revision: 0x02040008
>Sep 10 20:47:44 buddah kernel: ivtv: Registered v4l2 device, minor 0
>Sep 10 20:47:44 buddah kernel: ivtv: Registered v4l2 device, minor 32
>Sep 10 20:47:44 buddah kernel: ivtv: Registered v4l2 device, minor 224
>Sep 10 20:47:44 buddah kernel: lirc_dev: IR Remote Control driver 
>registered, at major 61
>Sep 10 20:47:44 buddah kernel: bttv: driver version 0.7.104 loaded
>Sep 10 20:47:44 buddah kernel: bttv: using 4 buffers with 2080k (8320k 
>total) for capture
>Sep 10 20:47:44 buddah kernel: bttv: Host bridge is PCI device 1106:3116 
>(VIA Technologies, Inc.)
>Sep 10 20:47:44 buddah kernel: lirc_i2c: chip found @ 0x18 (Hauppauge IR)
>Sep 10 20:47:44 buddah kernel: lirc_dev: lirc_register_plugin:sample_rate: 10
>Sep 10 20:47:44 buddah kernel: ivtv: ivtv-api.c: unknown ioctl 0x803c7601
>
>
>I seem to recall that lirc_dev has some hooks into bttv, as does the tuner 
>module. However, note that only one bttv loaded up on my box (0.7.104, 
>since I never put 0.9.11 on it).
>
>Shay, try uninstalling the ATrpms bttv 0.9.11 kernel modules, and see what 
>happens... If I get bored (not likely), I'll try adding them to my setup 
>to see if it breaks things. It shouldn't, since the 0.9.11 bttv should 
>just supplant 0.7.104, per the directives at the top of your modules.conf 
>file, but I'm not seeing what is causing both of them to load on your system.
>

I ended up just doing a format/reinstall..  And guess what, It's still not 
working.. if I do a depmod -a and then modprobe ivtv I get:

Sep 18 10:54:47 localhost kernel: bttv: Host bridge is VIA Technologies, 
Inc. VT8363/8365 [KT133/KM133]
Sep 18 10:54:47 localhost kernel: bttv: Host bridge is VIA Technologies, 
Inc. VT82C686 [Apollo Super ACPI]
Sep 18 10:54:47 localhost insmod: 
/lib/modules/2.4.20-20_29.rh9.at/kernel/drivers/media/video/bttv.o: 
init_module: No such device
Sep 18 10:54:47 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 18 10:54:47 localhost insmod: 
/lib/modules/2.4.20-20_29.rh9.at/kernel/drivers/media/video/bttv.o: insmod 
bttv failed
Sep 18 10:54:47 localhost modprobe: modprobe: Can't locate module rivatv
Sep 18 10:54:47 localhost kernel: lirc_i2c: chip found @ 0x18 (Hauppauge IR)
Sep 18 10:54:47 localhost kernel: lirc_dev: 
lirc_register_plugin:sample_rate: 10


It's like it's trying to do more than it should.. I notice that your log 
doesn't have any of the mod stuff..  unless it's normally hidden..

ackkkk..

-Shay