[mythtv-users] pvr350 TV-out howto problems..

[IvanK.]

Dan,

it's strange, but either you haven't copied and pasted all the ivtv-fb log 
messages from /var/log/messages, or ivtv-fb isn't even trying to be loaded.  
What does your /etc/modules.conf look like?

And we should really dig deeper to find out why that pal stuff keeps popping 
in.  Maybe you'll end up having to recompile ivtv-fb again, who knows...

IvanK.


On Friday 14 November 2003 11:47 pm, Dan wrote:
> thanx for the quick reply..
>
> I will try and meddle with /dev dir as you suggested, with respect to the
> var/log/messages.. I suspect you misunderstood what I was say..Im getting
> output here..losts of other stuff when doing modprobe..
>
> such as:
> >modprobe ivtv-fb
>
> ---------------------------- (just no indictor of framebuffer activity)
> ------- Nov 14 20:41:44 localhost kernel: ivtv: SGarray_size = 200,
> DSGarray_size = 16 Nov 14 20:41:44 localhost kernel: ivtv: Found an iTVC15
> based chip Nov 14 20:41:44 localhost kernel: tuner: probing ivtv i2c driver
> #0 i2c adapter [id=0x10005]
> Nov 14 20:41:44 localhost kernel: tuner: chip found @ 0xc2
> Nov 14 20:41:44 localhost kernel: tuner(bttv): type forced to 2 (Philips
> NTSC (F I1236,FM1236 and compatibles)) [insmod]
> Nov 14 20:41:46 localhost kernel: saa7127: Configuring
> encoder...<6>saa7114.c: s tarting probe for adapter ivtv i2c driver #0
> (0x10005)
> Nov 14 20:41:46 localhost kernel: saa7114.c: detecting saa7114 client on
> address 0x42
> Nov 14 20:41:46 localhost kernel: saa7115.c: writing init values
> Nov 14 20:41:48 localhost kernel: status: (1E) 0x48, (1F) 0xe0
> Nov 14 20:41:49 localhost kernel: msp34xx: init: chip=MSP3448W-A2, has
> NICAM sup port
> Nov 14 20:41:49 localhost kernel: msp3410: daemon started
> Nov 14 20:41:49 localhost kernel: lirc_i2c: chip found @ 0x18 (Hauppauge
> IR) Nov 14 20:41:49 localhost kernel: lirc_dev:
> lirc_register_plugin:sample_rate: 10 Nov 14 20:41:51 localhost kernel:
> ivtv: Encoder revision: 0x02040011 Nov 14 20:41:51 localhost kernel: ivtv:
> Decoder revision: 0x02020023 Nov 14 20:41:51 localhost kernel: ivtv:
> Registered v4l2 device, minor 0 Nov 14 20:41:51 localhost kernel: ivtv:
> Registered v4l2 device, minor 32 Nov 14 20:41:51 localhost kernel: ivtv:
> Registered v4l2 device, minor 224 Nov 14 20:41:51 localhost kernel: ivtv:
> Registered v4l2 device, minor 16 Nov 14 20:41:51 localhost kernel: ivtv:
> You've not seen the last of willy!
>
> Now I still get the actual console output from the modprobe as shown
> below.. -----
> # rmmod ivtv
> # modprobe ivtv-fb
> ioctl: VIDIOC_S_STD
> Standard set to 00003000
> /lib/modules/2.4.20-20_29.rh9.at/kernel/drivers/media/video/ivtv-fb.o:
> unresolved symbol ivtv_debug
> /lib/modules/2.4.20-20_29.rh9.at/kernel/drivers/media/video/ivtv-fb.o:
> unresolved symbol ivtv_pal
> /lib/modules/2.4.20-20_29.rh9.at/kernel/drivers/media/video/ivtv-fb.o:
> insmod
> /lib/modules/2.4.20-20_29.rh9.at/kernel/drivers/media/video/ivtv-fb.o
> failed
> /lib/modules/2.4.20-20_29.rh9.at/kernel/drivers/media/video/ivtv-fb.o:
> insmod ivtv-fb failed
>
> hmm, this is strange..Im using NTSC, not sure why its trying to PAL
> stuff...my system is ntsc...
>
> and yes, I am much happier then I was a week ago..could not even capture
> video..so I figure your right..im about half way there :)