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

[Dan]

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 :)

-----Original Message-----
From: "IvanK." <chepati at yahoo.com>
Sent: Nov 14, 2003 8:24 PM
To: Dan <dshopkins at earthlink.net>, mythtv-users at mythtv.org
Subject: Re: [mythtv-users] pvr350 TV-out howto problems..

Dan,

I'm addressing your questions below.

On Friday 14 November 2003 09:25 pm, Dan wrote:
> I've been following the instructions from the thread: My first attempt at
> PVR-350 TV-out "howto"
>
> History:
>
> the symbolic link: ln -s video0 /dev/video failed
> (video existed as a directory here)..so anyways I continue...
>

I've seen this and I think it might be the way v4l2 organizes its /dev 
entries.  What they do is have a /dev/video directory with the video0, 
video16, video32, and video224 character device entries inside /dev/video.  
You can work around this peculiarity by either creating links from /dev/
video/video* to /dev or by moving /dev/video/video* to /dev.  The advantage 
of the first approach (linking) is that if v4l2 applications expect to find 
their device files in /dev/video you will not break them.  The disadvantage, 
of course, is that you won't be able to have a /dev/video link to your ivtv 
device.  I would, therefore, recommend that you move /dev/video/* to /dev, 
delete the /dev/video directory and create a link video to video0 or whatever 
happens to be your ivtv device.  If you decide to preserve the /dev/video/
video* structure, then remember to set mythtv to use /dev/video/video16 for 
TV output.  And don't forget to set the correct permissions to /dev/video/
video*





> I was able to get to part:
>  modprobe ivtv-fb
>
> so far so good...At this point the
> fb1: iTVC15 TV out frame buffer device
>
> never showed up in the /var/log/messages


It very much depends on how your sysklogd is configured.  In my case all 
important messages from the kernel, all daemons, etc are written to /var/log/
messages.  What distro are you using?  Perhaps another user of that distro 
can give you a hint where to look for the ivtv output.  I'd suggest running 
this:

grep -li "TV out frame buffer" /var/log/*

It might turn out that the output is in kern.log.  I'm not sure.


hmm, I think you misunderstood, I believe the output is going to the correct the file, when I did the modprobe I got a tone of output, but..
just never did see that key line show up...


>
> so anyways I this point I went on to test..
>
> >rmmod saa7127
> >insmod saa7127 enable_output=1 output_select=0 test_image=1
>
> and got colored bands to output to the tv...
>
> so I continued following the instructions to dd if=/dev/video
> of=/dev/video16 bs=64k
>
> no video at video outout here..
>

No surprise here.  You need to first get your video devices setup correctly.

>
> next day:
> I figured I should attempt to try the Halloween version of ivtv.
>
> after making that, I now get this error when executing the modprobe ivtv-fb
>
> # modprobe ivtv-fb
> /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
>

It appears you're using PAL.  I saw somewhere in ivtv-fb.c (or .h, forgot 
which one) a mention of the need to actually hack the source to get PAL 
working.   Please go to ivtv.sf.net and search through their mailing list 
archives for setting up PAL.  Sorry I can't be of further help here :-(



>
> any suggestions as to how I can back on track??
>
> (mythtv is still tuning in correctly, just cant get the tvout)

Look at it from the bright side -- you're halfway there :-)

IvanK.