Mailing List Archive

On 10/15/07, E. Ann Black-Ziegelbein <annblackz@gmail.com> wrote:
> I am hoping someone can help. I am setting up MythTV on FC6 -
> 2.6.22.9-61.fc6. I have been following the instructions on
> http://wilsonet.com/mythtv/fcmyth.php?SID&expandables=closed&ivtv=open&pvr350out=open#capture.
> All has been going well - have mythtv settup and X working. I can capture
> video ... and play it back with mplayer. However I can not play it from
> MythTV - just get an error stating "Unable to initialize video". When I
> tail the myth tv logs I see the following:

How are you using the pvr-350's tv-out, via the special option in the
mythtv-setup or plain over X? If you have enable the special tv-out
support try disabling it.

> Additionally - I can not find the ivtvfbctl utiliity ... I am wondering if
> this may be related?

Nope, you should find them in the ivtv-1.0.3-<version>.rpm in the ATrpms repo.

> When I search through the /var/logs/messages and grep
> for ivtv, it looks like I am running ivtv version 1.0.0:

Don't use grep but:
dmesg | tac |
sed -n '/=\ \ END INIT IVTV\ \ =/,/= START INIT IVTV =/p;
/= START INIT IVTV =/q' |
tac

Also have a look at the troubleshooting page [1] and if there are any
error messages in you Xorg.log or kernel log.

Greets
Sander

[1] http://www.ivtvdriver.org/index.php/Troubleshooting

> Oct 14 21:37:46 delldvr kernel: ivtv: ==================== START INIT IVTV
> ====================
> Oct 14 21:37:46 delldvr kernel: ivtv: version 1.0.0 (2.6.22.9-61.fc6 SMP
> mod_unload 686 4KSTACKS ) loading
> Oct 14 21:37:46 delldvr kernel: ivtv0: Autodetected Hauppauge card (cx23415
> based)
> Oct 14 21:37:46 delldvr kernel: ivtv0: loaded v4l-cx2341x-enc.fw firmware
> (3751188808 bytes)
> Oct 14 21:37:46 delldvr kernel: ivtv0: loaded v4l-cx2341x-dec.fw firmware
> (3751188816 bytes)
> Oct 14 21:37:46 delldvr kernel: ivtv0: Encoder revision: 0x02060039
> Oct 14 21:37:46 delldvr kernel: ivtv0: Decoder revision: 0x02020023
> Oct 14 21:37:46 delldvr kernel: ivtv0: Autodetected Hauppauge WinTV PVR-350
> Oct 14 21:37:46 delldvr kernel: tuner 3-0061: chip found @ 0xc2 (ivtv i2c
> driver #0)
> Oct 14 21:37:46 delldvr kernel: saa7115 3-0021: saa7115 found
> (1f7115d0e100000) @ 0x42 (ivtv i2c driver #0)
> Oct 14 21:37:46 delldvr kernel: saa7127 3-0044: saa7127 found @ 0x88 (ivtv
> i2c driver #0)
> Oct 14 21:37:46 delldvr kernel: msp3400 3-0040: MSP4448G-A2 found @ 0x80
> (ivtv i2c driver #0)
> Oct 14 21:37:46 delldvr kernel: ivtv0: Registered device video0 for encoder
> MPEG (4 MB)
> Oct 14 21:37:46 delldvr kernel: ivtv0: Registered device video32 for encoder
> YUV (2 MB)
> Oct 14 21:37:46 delldvr kernel: ivtv0: Registered device vbi0 for encoder
> VBI (1 MB)
> Oct 14 21:37:46 delldvr kernel: ivtv0: Registered device video24 for encoder
> PCM audio (1 MB)
> Oct 14 21:37:46 delldvr kernel: ivtv0: Registered device radio0 for encoder
> radio
> Oct 14 21:37:46 delldvr kernel: ivtv0: Registered device video16 for decoder
> MPEG (1 MB)
> Oct 14 21:37:46 delldvr kernel: ivtv0: Registered device vbi8 for decoder
> VBI (1 MB)
> Oct 14 21:37:46 delldvr kernel: ivtv0: Registered device vbi16 for decoder
> VOUT
> Oct 14 21:37:46 delldvr kernel: ivtv0: Registered device video48 for decoder
> YUV (1 MB)
> Oct 14 21:37:46 delldvr kernel: ivtv0: loaded v4l-cx2341x-init.mpg firmware
> (3751190360 bytes)
> Oct 14 21:37:46 delldvr kernel: ivtv0: Initialized Hauppauge WinTV PVR-350,
> card #0
> Oct 14 21:37:46 delldvr kernel: ivtv: ==================== END INIT IVTV
> ====================
>
> I did try to recompile the saa7127 kernel module and replace, however this
> had no effect. I can't help but think I am missing something basic.
>
> Thanks,
>
> Ann
>
> _______________________________________________
> ivtv-users mailing list
> ivtv-users@ivtvdriver.org
> http://ivtvdriver.org/mailman/listinfo/ivtv-users
>

_______________________________________________
ivtv-users mailing list
ivtv-users@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-users

Thanks Sander!

I disabled mythTV's tv-out support, and now I do have video .... but NO
audio. Interesting, one step closer, however I would really like to
understand what the issue is with MythTV tv-out option then.

Any thoughts on how to get audio?

I did set mythtv back to enabling tv-out and tailed the logs
(/var/log/messages and /var/log/Xorg.0.log) ... but no error/warning
messages.

I did take a look at the troubleshooting page ... nothing there really
aligns with the problems I am seeing - I do already have the compat option
set.

Thanks again,

Ann

On 10/15/07, Sander Sweers <sander.sweers@gmail.com> wrote:
>
> On 10/15/07, E. Ann Black-Ziegelbein <annblackz@gmail.com> wrote:
> > I am hoping someone can help. I am setting up MythTV on FC6 -
> > 2.6.22.9-61.fc6. I have been following the instructions on
> > http://wilsonet.com/mythtv/fcmyth.php?SID&expandables=closed&ivtv=open&pvr350out=open#capture
> .
> > All has been going well - have mythtv settup and X working. I can
> capture
> > video ... and play it back with mplayer. However I can not play it from
> > MythTV - just get an error stating "Unable to initialize video". When I
>
> > tail the myth tv logs I see the following:
>
> How are you using the pvr-350's tv-out, via the special option in the
> mythtv-setup or plain over X? If you have enable the special tv-out
> support try disabling it.
>
> > Additionally - I can not find the ivtvfbctl utiliity ... I am wondering
> if
> > this may be related?
>
> Nope, you should find them in the ivtv-1.0.3-<version>.rpm in the ATrpms
> repo.
>
> > When I search through the /var/logs/messages and grep
> > for ivtv, it looks like I am running ivtv version 1.0.0:
>
> Don't use grep but:
> dmesg | tac |
> sed -n '/=\ \ END INIT IVTV\ \ =/,/= START INIT IVTV =/p;
> /= START INIT IVTV =/q' |
> tac
>
> Also have a look at the troubleshooting page [1] and if there are any
> error messages in you Xorg.log or kernel log.
>
> Greets
> Sander
>
> [1] http://www.ivtvdriver.org/index.php/Troubleshooting
>
> > Oct 14 21:37:46 delldvr kernel: ivtv: ==================== START INIT
> IVTV
> > ====================
> > Oct 14 21:37:46 delldvr kernel: ivtv: version 1.0.0 (2.6.22.9-61.fc6SMP
> > mod_unload 686 4KSTACKS ) loading
> > Oct 14 21:37:46 delldvr kernel: ivtv0: Autodetected Hauppauge card
> (cx23415
> > based)
> > Oct 14 21:37:46 delldvr kernel: ivtv0: loaded v4l-cx2341x-enc.fwfirmware
> > (3751188808 bytes)
> > Oct 14 21:37:46 delldvr kernel: ivtv0: loaded v4l-cx2341x-dec.fwfirmware
> > (3751188816 bytes)
> > Oct 14 21:37:46 delldvr kernel: ivtv0: Encoder revision: 0x02060039
> > Oct 14 21:37:46 delldvr kernel: ivtv0: Decoder revision: 0x02020023
> > Oct 14 21:37:46 delldvr kernel: ivtv0: Autodetected Hauppauge WinTV
> PVR-350
> > Oct 14 21:37:46 delldvr kernel: tuner 3-0061: chip found @ 0xc2 (ivtv
> i2c
> > driver #0)
> > Oct 14 21:37:46 delldvr kernel: saa7115 3-0021: saa7115 found
> > (1f7115d0e100000) @ 0x42 (ivtv i2c driver #0)
> > Oct 14 21:37:46 delldvr kernel: saa7127 3-0044: saa7127 found @ 0x88
> (ivtv
> > i2c driver #0)
> > Oct 14 21:37:46 delldvr kernel: msp3400 3-0040: MSP4448G-A2 found @ 0x80
> > (ivtv i2c driver #0)
> > Oct 14 21:37:46 delldvr kernel: ivtv0: Registered device video0 for
> encoder
> > MPEG (4 MB)
> > Oct 14 21:37:46 delldvr kernel: ivtv0: Registered device video32 for
> encoder
> > YUV (2 MB)
> > Oct 14 21:37:46 delldvr kernel: ivtv0: Registered device vbi0 for
> encoder
> > VBI (1 MB)
> > Oct 14 21:37:46 delldvr kernel: ivtv0: Registered device video24 for
> encoder
> > PCM audio (1 MB)
> > Oct 14 21:37:46 delldvr kernel: ivtv0: Registered device radio0 for
> encoder
> > radio
> > Oct 14 21:37:46 delldvr kernel: ivtv0: Registered device video16 for
> decoder
> > MPEG (1 MB)
> > Oct 14 21:37:46 delldvr kernel: ivtv0: Registered device vbi8 for
> decoder
> > VBI (1 MB)
> > Oct 14 21:37:46 delldvr kernel: ivtv0: Registered device vbi16 for
> decoder
> > VOUT
> > Oct 14 21:37:46 delldvr kernel: ivtv0: Registered device video48 for
> decoder
> > YUV (1 MB)
> > Oct 14 21:37:46 delldvr kernel: ivtv0: loaded v4l-cx2341x-init.mpgfirmware
> > (3751190360 bytes)
> > Oct 14 21:37:46 delldvr kernel: ivtv0: Initialized Hauppauge WinTV
> PVR-350,
> > card #0
> > Oct 14 21:37:46 delldvr kernel: ivtv: ==================== END INIT
> IVTV
> > ====================
> >
> > I did try to recompile the saa7127 kernel module and replace, however
> this
> > had no effect. I can't help but think I am missing something basic.
> >
> > Thanks,
> >
> > Ann
> >
> > _______________________________________________
> > ivtv-users mailing list
> > ivtv-users@ivtvdriver.org
> > http://ivtvdriver.org/mailman/listinfo/ivtv-users
> >
>
> _______________________________________________
> ivtv-users mailing list
> ivtv-users@ivtvdriver.org
> http://ivtvdriver.org/mailman/listinfo/ivtv-users
>

On Tuesday 16 Oct 2007, E. Ann Black-Ziegelbein wrote:

> I disabled mythTV's tv-out support, and now I do have video .... but NO
> audio. Interesting, one step closer, however I would really like to
> understand what the issue is with MythTV tv-out option then.

Since you're using ivtv 1.0, you'll have to use a recent build of MythTV
trunk. If you want something more stable & are prepared to compile it
yourself, you could use MythTV release-0-20-fixes with the following patch.

http://www.iarmst.demon.co.uk/test/mythfix-ivtv-v3.patch

This is the most recent backport of the update needed for ivtv 1.0 support.

Be advised, there is a bug with the ivtv driver currently supplied with kernel
2.6.22, which can cause the mpeg decoder to become disabled. This is fixed in
2.6.23.

--
Ian

_______________________________________________
ivtv-users mailing list
ivtv-users@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-users

I just had this, I had to move my audio from the
PVR-350 audio out to my soundcard. I just bought a
cable last night to do this and it is working fine.

Robb
--- "E. Ann Black-Ziegelbein" <annblackz@gmail.com>
wrote:

> Thanks Sander!
>
> I disabled mythTV's tv-out support, and now I do
> have video .... but NO
> audio. Interesting, one step closer, however I
> would really like to
> understand what the issue is with MythTV tv-out
> option then.
>
> Any thoughts on how to get audio?
>
> I did set mythtv back to enabling tv-out and tailed
> the logs
> (/var/log/messages and /var/log/Xorg.0.log) ... but
> no error/warning
> messages.
>
> I did take a look at the troubleshooting page ...
> nothing there really
> aligns with the problems I am seeing - I do already
> have the compat option
> set.
>
> Thanks again,
>
> Ann
>
> On 10/15/07, Sander Sweers <sander.sweers@gmail.com>
> wrote:
> >
> > On 10/15/07, E. Ann Black-Ziegelbein
> <annblackz@gmail.com> wrote:
> > > I am hoping someone can help. I am setting up
> MythTV on FC6 -
> > > 2.6.22.9-61.fc6. I have been following the
> instructions on
> > >
>
http://wilsonet.com/mythtv/fcmyth.php?SID&expandables=closed&ivtv=open&pvr350out=open#capture
> > .
> > > All has been going well - have mythtv settup
> and X working. I can
> > capture
> > > video ... and play it back with mplayer.
> However I can not play it from
> > > MythTV - just get an error stating "Unable to
> initialize video". When I
> >
> > > tail the myth tv logs I see the following:
> >
> > How are you using the pvr-350's tv-out, via the
> special option in the
> > mythtv-setup or plain over X? If you have enable
> the special tv-out
> > support try disabling it.
> >
> > > Additionally - I can not find the ivtvfbctl
> utiliity ... I am wondering
> > if
> > > this may be related?
> >
> > Nope, you should find them in the
> ivtv-1.0.3-<version>.rpm in the ATrpms
> > repo.
> >
> > > When I search through the /var/logs/messages
> and grep
> > > for ivtv, it looks like I am running ivtv
> version 1.0.0:
> >
> > Don't use grep but:
> > dmesg | tac |
> > sed -n '/=\ \ END INIT IVTV\ \ =/,/= START INIT
> IVTV =/p;
> > /= START INIT IVTV =/q' |
> > tac
> >
> > Also have a look at the troubleshooting page [1]
> and if there are any
> > error messages in you Xorg.log or kernel log.
> >
> > Greets
> > Sander
> >
> > [1]
> http://www.ivtvdriver.org/index.php/Troubleshooting
> >
> > > Oct 14 21:37:46 delldvr kernel: ivtv:
> ==================== START INIT
> > IVTV
> > > ====================
> > > Oct 14 21:37:46 delldvr kernel: ivtv: version
> 1.0.0 (2.6.22.9-61.fc6SMP
> > > mod_unload 686 4KSTACKS ) loading
> > > Oct 14 21:37:46 delldvr kernel: ivtv0:
> Autodetected Hauppauge card
> > (cx23415
> > > based)
> > > Oct 14 21:37:46 delldvr kernel: ivtv0: loaded
> v4l-cx2341x-enc.fwfirmware
> > > (3751188808 bytes)
> > > Oct 14 21:37:46 delldvr kernel: ivtv0: loaded
> v4l-cx2341x-dec.fwfirmware
> > > (3751188816 bytes)
> > > Oct 14 21:37:46 delldvr kernel: ivtv0: Encoder
> revision: 0x02060039
> > > Oct 14 21:37:46 delldvr kernel: ivtv0: Decoder
> revision: 0x02020023
> > > Oct 14 21:37:46 delldvr kernel: ivtv0:
> Autodetected Hauppauge WinTV
> > PVR-350
> > > Oct 14 21:37:46 delldvr kernel: tuner 3-0061:
> chip found @ 0xc2 (ivtv
> > i2c
> > > driver #0)
> > > Oct 14 21:37:46 delldvr kernel: saa7115 3-0021:
> saa7115 found
> > > (1f7115d0e100000) @ 0x42 (ivtv i2c driver #0)
> > > Oct 14 21:37:46 delldvr kernel: saa7127 3-0044:
> saa7127 found @ 0x88
> > (ivtv
> > > i2c driver #0)
> > > Oct 14 21:37:46 delldvr kernel: msp3400 3-0040:
> MSP4448G-A2 found @ 0x80
> > > (ivtv i2c driver #0)
> > > Oct 14 21:37:46 delldvr kernel: ivtv0:
> Registered device video0 for
> > encoder
> > > MPEG (4 MB)
> > > Oct 14 21:37:46 delldvr kernel: ivtv0:
> Registered device video32 for
> > encoder
> > > YUV (2 MB)
> > > Oct 14 21:37:46 delldvr kernel: ivtv0:
> Registered device vbi0 for
> > encoder
> > > VBI (1 MB)
> > > Oct 14 21:37:46 delldvr kernel: ivtv0:
> Registered device video24 for
> > encoder
> > > PCM audio (1 MB)
> > > Oct 14 21:37:46 delldvr kernel: ivtv0:
> Registered device radio0 for
> > encoder
> > > radio
> > > Oct 14 21:37:46 delldvr kernel: ivtv0:
> Registered device video16 for
> > decoder
> > > MPEG (1 MB)
> > > Oct 14 21:37:46 delldvr kernel: ivtv0:
> Registered device vbi8 for
> > decoder
> > > VBI (1 MB)
> > > Oct 14 21:37:46 delldvr kernel: ivtv0:
> Registered device vbi16 for
> > decoder
> > > VOUT
> > > Oct 14 21:37:46 delldvr kernel: ivtv0:
> Registered device video48 for
> > decoder
> > > YUV (1 MB)
> > > Oct 14 21:37:46 delldvr kernel: ivtv0: loaded
> v4l-cx2341x-init.mpgfirmware
> > > (3751190360 bytes)
> > > Oct 14 21:37:46 delldvr kernel: ivtv0:
> Initialized Hauppauge WinTV
> > PVR-350,
> > > card #0
> > > Oct 14 21:37:46 delldvr kernel: ivtv:
> ==================== END INIT
> > IVTV
> > > ====================
> > >
> > > I did try to recompile the saa7127 kernel module
> and replace, however
> > this
> > > had no effect. I can't help but think I am
> missing something basic.
> > >
> > > Thanks,
> > >
> > > Ann
> > >
> > > _______________________________________________
> > > ivtv-users mailing list
> > > ivtv-users@ivtvdriver.org
> > >
> http://ivtvdriver.org/mailman/listinfo/ivtv-users
> > >
> >
> > _______________________________________________
> > ivtv-users mailing list
> > ivtv-users@ivtvdriver.org
> > http://ivtvdriver.org/mailman/listinfo/ivtv-users
> >
> > _______________________________________________
> ivtv-users mailing list
> ivtv-users@ivtvdriver.org
> http://ivtvdriver.org/mailman/listinfo/ivtv-users



____________________________________________________________________________________
Shape Yahoo! in your own image. Join our Network Research Panel today! http://surveylink.yahoo.com/gmrs/yahoo_panel_invite.asp?a=7



_______________________________________________
ivtv-users mailing list
ivtv-users@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-users

Thanks Ian!

I was able to grab your patch file and apply it against the
release-0-20-fixes branch of code checkedout from SVN, and compile it.

Now, I have a question I was hoping you or someone could help with. I was
hoping to apply the new compiled code over my original mythtv installation
(installed via rpm). I did "make install" - but noticed that it seems to
be placing things in a different location than the rpm installer. I am not
a linux or mythtv wiz ... so I was hoping for some pointers on what files to
move where in order for the new compiled binaries to be picked up.

Thanks again,

Ann

PS - I was wanting to keep my original install as I installed myth suite and
I have only downloaded and compiled mythtv

On 10/16/07, Ian Armstrong <mail01@iarmst.co.uk> wrote:
>
> On Tuesday 16 Oct 2007, E. Ann Black-Ziegelbein wrote:
>
> > I disabled mythTV's tv-out support, and now I do have video .... but NO
> > audio. Interesting, one step closer, however I would really like to
> > understand what the issue is with MythTV tv-out option then.
>
> Since you're using ivtv 1.0, you'll have to use a recent build of MythTV
> trunk. If you want something more stable & are prepared to compile it
> yourself, you could use MythTV rxes with the following patch.
> elease-0-20-fi
> http://www.iarmst.demon.co.uk/test/mythfix-ivtv-v3.patch
>
> This is the most recent backport of the update needed for ivtv 1.0support.
>
> Be advised, there is a bug with the ivtv driver currently supplied with
> kernel
> 2.6.22, which can cause the mpeg decoder to become disabled. This is fixed
> in
> 2.6.23.
>
> --
> Ian
>
> _______________________________________________
> ivtv-users mailing list
> ivtv-users@ivtvdriver.org
> http://ivtvdriver.org/mailman/listinfo/ivtv-users
>

Actually, I was able to manually start up what I think is the new version
installed ... and the problem is still there - can not get any tv-out. Ian,
is there some way for me to verify I am running with your patches?

Thanks,

Ann

On 10/17/07, E. Ann Black-Ziegelbein <annblackz@gmail.com> wrote:
>
> Thanks Ian!
>
> I was able to grab your patch file and apply it against the
> release-0-20-fixes branch of code checkedout from SVN, and compile it.
>
> Now, I have a question I was hoping you or someone could help with. I was
> hoping to apply the new compiled code over my original mythtv installation
> (installed via rpm). I did "make install" - but noticed that it seems to
> be placing things in a different location than the rpm installer. I am not
> a linux or mythtv wiz ... so I was hoping for some pointers on what files to
> move where in order for the new compiled binaries to be picked up.
>
> Thanks again,
>
> Ann
>
> PS - I was wanting to keep my original install as I installed myth suite
> and I have only downloaded and compiled mythtv
>
> On 10/16/07, Ian Armstrong <mail01@iarmst.co.uk> wrote:
> >
> > On Tuesday 16 Oct 2007, E. Ann Black-Ziegelbein wrote:
> >
> > > I disabled mythTV's tv-out support, and now I do have video .... but
> > NO
> > > audio. Interesting, one step closer, however I would really like to
> > > understand what the issue is with MythTV tv-out option then.
> >
> > Since you're using ivtv 1.0, you'll have to use a recent build of MythTV
> > trunk. If you want something more stable & are prepared to compile it
> > yourself, you could use MythTV rxes with the following patch.
> > elease-0-20-fi
> > http://www.iarmst.demon.co.uk/test/mythfix-ivtv-v3.patch
> >
> > This is the most recent backport of the update needed for ivtv 1.0support.
> >
> > Be advised, there is a bug with the ivtv driver currently supplied with
> > kernel
> > 2.6.22, which can cause the mpeg decoder to become disabled. This is
> > fixed in
> > 2.6.23.
> >
> > --
> > Ian
> >
> > _______________________________________________
> > ivtv-users mailing list
> > ivtv-users@ivtvdriver.org
> > http://ivtvdriver.org/mailman/listinfo/ivtv-users
> >
>
>

On Thursday 18 Oct 2007, E. Ann Black-Ziegelbein wrote:
> Thanks Ian!
>
> I was able to grab your patch file and apply it against the
> release-0-20-fixes branch of code checkedout from SVN, and compile it.
>
> Now, I have a question I was hoping you or someone could help with. I was
> hoping to apply the new compiled code over my original mythtv installation
> (installed via rpm). I did "make install" - but noticed that it seems to
> be placing things in a different location than the rpm installer. I am not
> a linux or mythtv wiz ... so I was hoping for some pointers on what files
> to move where in order for the new compiled binaries to be picked up.

I assume by 'different location' you mean a different directory. I think
you'll have to do a 'make uninstall' for MythTV to remove the new install.
Then rerun ./configure with the --prefix option to specify where it should
go. I think it defaults to /usr/local, so to place it under /usr you would
run './configure --prefix=/usr'


--
Ian

_______________________________________________
ivtv-users mailing list
ivtv-users@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-users

E. Ann Black-Ziegelbein wrote:
> All has been going well - have mythtv settup and X working. I can capture
> video ... and play it back with mplayer. However I can not play it from
> MythTV - just get an error stating "Unable to initialize video". When I
> tail the myth tv logs I see the following:

I'm pretty much in the same situation as the original poster. I have X
working on my PVR-350's TV out, but not MythTV playback or Live TV. I
get the same error message when I try to playback, "Unable to initialize
video", but my logs show different errors:

2007-10-29 21:50:49.046 TV: Attempting to change from None to
WatchingPreRecorded
2007-10-29 21:50:49.052 DPMS Deactivated
2007-10-29 21:50:49.124 Opening ALSA audio device 'default'.
2007-10-29 21:50:49.148 Mixer unable to find control Master
2007-10-29 21:50:49.148 Mixer unable to find control Master
2007-10-29 21:50:49.148 NVP: Enabling Audio
2007-10-29 21:50:49.148 IVD Error: Framebuffer number query failed.
eno: Invalid argument (22)
Did you load the ivtv-fb Linux kernel module?
2007-10-29 21:51:05.902 TV Error: StartPlayer(): NVP is not playing
after 20000 msec
2007-10-29 21:51:05.903 TV: Changing from None to WatchingPreRecorded
2007-10-29 21:51:05.904 TV: Attempting to change from
WatchingPreRecorded to None
2007-10-29 21:51:05.920 IVD Error: Failed to stop decoder
eno: Invalid argument (22)
2007-10-29 21:51:05.924 TV: Changing from WatchingPreRecorded to None
2007-10-29 21:51:05.925 TV: Attempting to change from None to None
2007-10-29 21:51:06.184 DPMS Reactivated.
0: start_time: 0.036 duration: 323.507
1: start_time: 0.026 duration: 323.482
stream: start_time: 0.289 duration: 3594.635 bitrate=5189 kb/s
2007-10-29 21:51:06.723 AFD: Opened codec 0x82a6980, id(MPEG2VIDEO)
type(Video)
2007-10-29 21:51:06.723 AFD: Opened codec 0x8208cd0, id(MP2) type(Audio)
0: start_time: 0.036 duration: 323.507
1: start_time: 0.026 duration: 323.482
stream: start_time: 0.289 duration: 3594.635 bitrate=5189 kb/s
2007-10-29 21:51:07.923 AFD: Opened codec 0x82a6980, id(MPEG2VIDEO)
type(Video)
2007-10-29 21:51:07.923 AFD: Opened codec 0x8208cd0, id(MP2) type(Audio)

I'm using Ubuntu with kernel 2.6.22-14. I actually had everything
working on feisty, but the playback broke when I upgraded to gutsy.

I believe I have ivtv-fb loaded. It's listed in /etc/modules and I have
"options ivtv-fb osd_compat=1" in /etc/modprobe.d/aliases. And ivtv_fb
shows up when I do lsmod.

Here's my IVTV dmesg output:

[ 13.988000] ivtv: ==================== START INIT IVTV
====================
[ 13.988000] ivtv: version 1.0.0 (2.6.22-14-generic SMP mod_unload
586 ) loading
[ 14.052000] ivtv0: Autodetected Hauppauge card (cx23415 based)
[ 14.712000] ivtv0: loaded v4l-cx2341x-enc.fw firmware (4155196880 bytes)
[ 14.740000] ivtv0: loaded v4l-cx2341x-dec.fw firmware (4155196888 bytes)
[ 14.964000] ivtv0: Encoder revision: 0x02060039
[ 14.972000] ivtv0: Decoder revision: 0x02020023
[ 15.032000] tveeprom 2-0050: Hauppauge model 48132, rev K268, serial#
9945181
[ 15.032000] tveeprom 2-0050: tuner model is LG TAPE H001F MK3 (idx
68, type 47)
[ 15.032000] tveeprom 2-0050: TV standards NTSC(M) (eeprom 0x08)
[ 15.032000] tveeprom 2-0050: audio processor is MSP4448 (idx 27)
[ 15.032000] tveeprom 2-0050: decoder processor is SAA7115 (idx 19)
[ 15.032000] tveeprom 2-0050: has radio, has IR receiver, has no IR
transmitter
[ 15.032000] ivtv0: Autodetected Hauppauge WinTV PVR-350
[ 15.060000] tuner 2-0043: chip found @ 0x86 (ivtv i2c driver #0)
[ 15.060000] tda9887 2-0043: tda988[5/6/7] found @ 0x43 (tuner)
[ 15.064000] tuner 2-0061: chip found @ 0xc2 (ivtv i2c driver #0)
[ 15.112000] saa7115 2-0021: saa7115 found (1f7115d0e100000) @ 0x42
(ivtv i2c driver #0)
[ 15.292000] saa7127 2-0044: saa7129 found @ 0x88 (ivtv i2c driver #0)
[ 15.316000] msp3400 2-0040: MSP4448G-A2 found @ 0x80 (ivtv i2c driver #0)
[ 15.316000] msp3400 2-0040: MSP4448G-A2 supports radio, mode is
autodetect and autoselect
[ 15.316000] tuner 2-0061: type set to 47 (LG NTSC (TAPE series))
[ 15.568000] ivtv0: Registered device video0 for encoder MPEG (4 MB)
[ 15.568000] ivtv0: Registered device video32 for encoder YUV (2 MB)
[ 15.568000] ivtv0: Registered device vbi0 for encoder VBI (1 MB)
[ 15.568000] ivtv0: Registered device video24 for encoder PCM audio (1 MB)
[ 15.568000] ivtv0: Registered device radio0 for encoder radio
[ 15.568000] ivtv0: Registered device video16 for decoder MPEG (1 MB)
[ 15.568000] ivtv0: Registered device vbi8 for decoder VBI (1 MB)
[ 15.568000] ivtv0: Registered device vbi16 for decoder VOUT
[ 15.568000] ivtv0: Registered device video48 for decoder YUV (1 MB)
[ 15.636000] ivtv0: loaded v4l-cx2341x-init.mpg firmware (4155197272
bytes)
[ 15.828000] ivtv0: Initialized Hauppauge WinTV PVR-350, card #0
[ 15.828000] ivtv: ==================== END INIT IVTV
====================

Here's dmesg output related to ivtv-fb. I don't know why the same
messages appear twice. Is that a problem?

[ 16.532000] ivtv0-fb: Framebuffer at 0xed510000, mapped to
0xfa790000, size 1665k
[ 16.608000] ivtv0-fb: === Validated display mode ===
[ 16.608000] ivtv0-fb: Display size 720x480 (720x480 Virtual) @ 32bpp
[ 16.608000] ivtv0-fb: Display position 1,1
[ 16.608000] ivtv0-fb: Display filter : on
[ 16.608000] ivtv0-fb: Color space : RGB
[ 16.640000] ivtv0-fb: === Display mode change ===
[ 16.640000] ivtv0-fb: Display size 720x480 (720x480 Virtual) @ 32bpp
[ 16.640000] ivtv0-fb: Display position 1,1
[ 16.640000] ivtv0-fb: Display filter : on
[ 16.640000] ivtv0-fb: Color space : RGB
[ 16.648000] ivtv0-fb: Running in compatibility mode. Display resize &
mode change disabled
[ 16.648000] ivtv0-fb: Framebuffer registered on ivtv card id 0
...
[ 22.916000] ivtv0-fb: === Validated display mode ===
[ 22.916000] ivtv0-fb: Display size 720x480 (720x480 Virtual) @ 32bpp
[ 22.916000] ivtv0-fb: Display position 1,1
[ 22.916000] ivtv0-fb: Display filter : on
[ 22.916000] ivtv0-fb: Color space : RGB
[ 22.916000] ivtv0-fb: === Validated display mode ===
[ 22.916000] ivtv0-fb: Display size 720x480 (720x480 Virtual) @ 32bpp
[ 22.916000] ivtv0-fb: Display position 1,1
[ 22.916000] ivtv0-fb: Display filter : on
[ 22.916000] ivtv0-fb: Color space : RGB
[ 22.940000] ivtv0-fb: === Display mode change ===
[ 22.940000] ivtv0-fb: Display size 720x480 (720x480 Virtual) @ 32bpp
[ 22.940000] ivtv0-fb: Display position 1,1
[ 22.940000] ivtv0-fb: Display filter : on
[ 22.940000] ivtv0-fb: Color space : RGB

And some relevant X log outputs:

(II) LoadModule: "ivtv"
(II) Loading /usr/lib/xorg/modules/drivers//ivtv_drv.so
(II) Module ivtv: vendor="X.Org Foundation"
compiled for 1.3.0, module version = 1.0.0
ABI class: X.Org Video Driver, version 1.2
[snip]
(II) IVTV: driver for ivtv framebuffer: PVR-350
(II) Primary Device is: PCI 00:0d:0
(--) Chipset PVR-350 found
(II) IVTV(0): using /dev/fb0
(II) resource ranges after probing:
[0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[4] -1 0 0xfd9f0000 - 0xfd9fffff (0x10000) MX[B]
[5] -1 0 0xfe02c000 - 0xfe02cfff (0x1000) MX[B]
[6] -1 0 0xfe02d000 - 0xfe02dfff (0x1000) MX[B]
[7] -1 0 0xfe028000 - 0xfe02bfff (0x4000) MX[B]
[8] -1 0 0xfe02e000 - 0xfe02e0ff (0x100) MX[B]
[9] -1 0 0xfe02f000 - 0xfe02ffff (0x1000) MX[B]
[10] -1 0 0xec000000 - 0xefffffff (0x4000000) MX[B](B)
[11] -1 0 0xfc000000 - 0xfcffffff (0x1000000) MX[B](B)
[12] -1 0 0xd0000000 - 0xdfffffff (0x10000000) MX[B](B)
[13] -1 0 0xfb000000 - 0xfbffffff (0x1000000) MX[B](B)
[14] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[15] -1 0 0x00000000 - 0x000000ff (0x100) IX[B]
[16] -1 0 0x0000d800 - 0x0000d80f (0x10) IX[B]
[17] -1 0 0x00000b70 - 0x00000b73 (0x4) IX[B]
[18] -1 0 0x00000970 - 0x00000977 (0x8) IX[B]
[19] -1 0 0x00000bf0 - 0x00000bf3 (0x4) IX[B]
[20] -1 0 0x000009f0 - 0x000009f7 (0x8) IX[B]
[21] -1 0 0x0000ec00 - 0x0000ec07 (0x8) IX[B]
[22] -1 0 0x0000f000 - 0x0000f00f (0x10) IX[B]
[23] -1 0 0x0000f400 - 0x0000f43f (0x40) IX[B]
[24] -1 0 0x00001c00 - 0x00001c3f (0x40) IX[B]
[25] -1 0 0x0000fc00 - 0x0000fc3f (0x40) IX[B]
(--) IVTV(0): Framebuffer id from dev /dev/fb0 is 0
(II) IVTV(0): IVTV driver version 1.0.0
(II) IVTV(0): Using new API
(II) IVTV(0): Linked framebuffer 'dev/fb0' to yuv device '/dev/video48'
(**) IVTV(0): Depth 24, (**) framebuffer bpp 32
(==) IVTV(0): RGB weight 888
(==) IVTV(0): Default visual is TrueColor
(==) IVTV(0): Using gamma correction (1.0, 1.0, 1.0)
(II) IVTV(0): Hardware: cx23415 TV out (vidmem: 1665k)
(II) IVTV(0): Checking Modes against framebuffer device...
(II) IVTV(0): mode "720x480" ok
(II) IVTV(0): Checking Modes against monitor...
(--) IVTV(0): Virtual size is 720x480 (pitch 720)
(**) IVTV(0): Mode "720x480": 34.6 MHz (scaled from 0.0 MHz), 37.2 kHz,
73.9 Hz
(II) IVTV(0): Modeline "720x480" 34.56 720 752 840 928 480 484 488
504 -hsync -vsync
(**) IVTV(0): Display dimensions: (183, 122) mm
(**) IVTV(0): DPI set to (99, 99)
(II) Loading sub module "fb"
(II) LoadModule: "fb"
(II) Loading /usr/lib/xorg/modules//libfb.so
(II) Module fb: vendor="X.Org Foundation"
compiled for 1.3.0, module version = 1.0.0
ABI class: X.Org ANSI C Emulation, version 0.3
(**) IVTV(0): Using "Shadow Framebuffer"
(II) Loading sub module "shadow"
(II) LoadModule: "shadow"
(II) Loading /usr/lib/xorg/modules//libshadow.so
(II) Module shadow: vendor="X.Org Foundation"
compiled for 1.3.0, module version = 1.1.0
ABI class: X.Org ANSI C Emulation, version 0.3
[snip]
(II) IVTV(0): bitsPerPixel=32, depth=24, defaultVisual=TrueColor
mask: ff0000,ff00,ff, offset: 16,8,0
(II) IVTV(0): Screen init width 720 height 480 virtual 720 480
(==) IVTV(0): Backing store disabled
(II) IVTV(0): Init Video
(II) IVTV(0): Enabling Xv support for PVR350
(EE) Failed to initialize GLX extension (Compatible NVIDIA X driver not
found)
(EE) IVTV(0): FBIOPAN_DISPLAY: Invalid argument

I'm not sure how to fix those 2 X errors. Do I need to load "glx" in my
xorg.conf?

And to superm1_ from #ubuntu-mythtv on IRC, I did install ivtv-utils and
that didn't help.

Thanks for any help.

Eric





_______________________________________________
ivtv-users mailing list
ivtv-users@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-users

On Tuesday 30 Oct 2007, Eric wrote:
> E. Ann Black-Ziegelbein wrote:
> > All has been going well - have mythtv settup and X working. I can
> > capture video ... and play it back with mplayer. However I can not play
> > it from MythTV - just get an error stating "Unable to initialize video".
> > When I tail the myth tv logs I see the following:
>
> I'm pretty much in the same situation as the original poster. I have X
> working on my PVR-350's TV out, but not MythTV playback or Live TV. I
> get the same error message when I try to playback, "Unable to initialize
> video", but my logs show different errors:

> 2007-10-29 21:50:49.148 IVD Error: Framebuffer number query failed.
> eno: Invalid argument (22)
> Did you load the ivtv-fb Linux kernel module?

> I'm using Ubuntu with kernel 2.6.22-14. I actually had everything
> working on feisty, but the playback broke when I upgraded to gutsy.

> I believe I have ivtv-fb loaded. It's listed in /etc/modules and I have
> "options ivtv-fb osd_compat=1" in /etc/modprobe.d/aliases. And ivtv_fb
> shows up when I do lsmod.

It looks like you're running too old a version of MythTV. Once you move up to
ivtv 1.0.0 you need a recent version of MythTV to use the mpeg decoder.
You'll either have to move to a recent trunk version, or compile 0-20-fixes
after applying the following patch.

http://www.iarmst.demon.co.uk/test/mythfix-ivtv-v3.patch

Once MythTV is updated, you can remove 'options ivtv-fb osd_compat=1' since
it's not required.

> (II) IVTV(0): Init Video
> (II) IVTV(0): Enabling Xv support for PVR350
> (EE) Failed to initialize GLX extension (Compatible NVIDIA X driver not
> found)
> (EE) IVTV(0): FBIOPAN_DISPLAY: Invalid argument
>
> I'm not sure how to fix those 2 X errors. Do I need to load "glx" in my
> xorg.conf?

The FBIOPAN_DISPLAY error is harmless and can be ignored.

--
Ian

_______________________________________________
ivtv-users mailing list
ivtv-users@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-users

Thanks for your help. I was still unable to get it successfully working.
When I backed out mythtv with a make uninstall - it removed more than what
it should have. Anyway, I decided to go back to getting mythdora running,
and I have had some success with that. I am making a separate posting to
share my steps in getting it running.

Thanks,

Ann

On 10/18/07, Ian Armstrong <mail01@iarmst.co.uk> wrote:
>
> On Thursday 18 Oct 2007, E. Ann Black-Ziegelbein wrote:
> > Thanks Ian!
> >
> > I was able to grab your patch file and apply it against the
> > release-0-20-fixes branch of code checkedout from SVN, and compile it.
> >
> > Now, I have a question I was hoping you or someone could help with. I
> was
> > hoping to apply the new compiled code over my original mythtv
> installation
> > (installed via rpm). I did "make install" - but noticed that it seems
> to
> > be placing things in a different location than the rpm installer. I am
> not
> > a linux or mythtv wiz ... so I was hoping for some pointers on what
> files
> > to move where in order for the new compiled binaries to be picked up.
>
> I assume by 'different location' you mean a different directory. I think
> you'll have to do a 'make uninstall' for MythTV to remove the new install.
> Then rerun ./configure with the --prefix option to specify where it should
> go. I think it defaults to /usr/local, so to place it under /usr you would
> run './configure --prefix=/usr'
>
>
> --
> Ian
>
> _______________________________________________
> ivtv-users mailing list
> ivtv-users@ivtvdriver.org
> http://ivtvdriver.org/mailman/listinfo/ivtv-users
>

Ian Armstrong wrote:
> On Tuesday 30 Oct 2007, Eric wrote:
>> E. Ann Black-Ziegelbein wrote:
>>> All has been going well - have mythtv settup and X working. I can
>>> capture video ... and play it back with mplayer. However I can not play
>>> it from MythTV - just get an error stating "Unable to initialize video".
>>> When I tail the myth tv logs I see the following:
>>
>> I'm pretty much in the same situation as the original poster. I have X
>> working on my PVR-350's TV out, but not MythTV playback or Live TV. I
>> get the same error message when I try to playback, "Unable to initialize
>> video", but my logs show different errors:
>>
>> 2007-10-29 21:50:49.148 IVD Error: Framebuffer number query failed.
>> eno: Invalid argument (22)
>> Did you load the ivtv-fb Linux kernel module?
>>
>> I'm using Ubuntu with kernel 2.6.22-14. I actually had everything
>> working on feisty, but the playback broke when I upgraded to gutsy.
>>
>> I believe I have ivtv-fb loaded. It's listed in /etc/modules and I have
>> "options ivtv-fb osd_compat=1" in /etc/modprobe.d/aliases. And ivtv_fb
>> shows up when I do lsmod.
>
> It looks like you're running too old a version of MythTV. Once you move up to
> ivtv 1.0.0 you need a recent version of MythTV to use the mpeg decoder.
> You'll either have to move to a recent trunk version, or compile 0-20-fixes
> after applying the following patch.

I upgraded to MythTV 0.20.2 (the latest version in the Ubuntu
repositories) so that I can use Schedules Direct. Would this still be
considered too old?

Thanks,
Eric



_______________________________________________
ivtv-users mailing list
ivtv-users@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-users

On Thursday 01 Nov 2007, Eric wrote:
> Ian Armstrong wrote:
>
> > It looks like you're running too old a version of MythTV. Once you move
> > up to ivtv 1.0.0 you need a recent version of MythTV to use the mpeg
> > decoder. You'll either have to move to a recent trunk version, or compile
> > 0-20-fixes after applying the following patch.
>
> I upgraded to MythTV 0.20.2 (the latest version in the Ubuntu
> repositories) so that I can use Schedules Direct. Would this still be
> considered too old?

If it's a pre-built package then it still won't work. You'll have to download
the source & compile it yourself using the patch I mentioned previously.

If you don't want to build it yourself, you'll probably have to move to
mythtv-trunk.

--
Ian

_______________________________________________
ivtv-users mailing list
ivtv-users@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-users