[mythtv-users] Does anyone have a working dual pvr-250 setup?

[James L. Paul]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sunday 23 November 2003 20:40, Vinton Coffman wrote:
> My mythtv box has been broken for two weeks now and no one seems to be
> attempting to fix it on the ivtv driver side of development.  I'm back
> to running two vcr's.  All I get are the log messages below and 0 MB
> files.  If two shows are recorded at the same time and are the same
> length, both get recorded.  Then everything else is 0 MB.  It would be
> less upsetting if it wasn't for the fact that it worked 99.9% of the
> time until I tried to update mythtv and ivtv about two weeks ago.  Does
> anyone have a tarball for the driver that still works?  I tried
> reverting to an older version of cvs but it complained that some files
> were no longer in the repository and wouldn't compile.

First of all, I recommend an attitude adjustment. Nobody owes you anything for 
this software, it's the other way around. :)

Second of all, if you were using a previous version/configuration that worked, 
simply return to using that. If you want to be on the bleeding edge of alpha 
code, it's unreasonable to expect it to work all the time or even at all.

Third, I have a working dual PVR-250 setup. It's running 0.12 and is very 
stable for me. No, I don't have a magic tarball that will allow you do 
duplicate my success with a single command. I honestly wish I did, but that 
just isn't going to happen yet.

Fourth, the reason I'm happily surfing my MythTV and bevy of modules is due to 
tremendous efforts of the community here and key individuals. It's only at 
their mercy and generosity that anything happens at all, and I fully realize 
I have no cause to complain without also being willing do dig in and lend my 
time to the coding.

> I don't believe its a myth problem, the developer for ivtv is supposed
> to be adding a bunch of new features before Thanksgiving and nothing
> new has been commited to cvs since I updated to this broken version.
> I'd really appreciate a working tarball or a work around if anyone has
> one.

Fall back to a non-broken version. Fall back to a working version of ivtv. 
Don't insist on running the very latest broken version, try running a recent 
working version instead. Try not to feel bad that you are running code less 
than 12 hours old. ;)

> BTW, I tried to current tarball from the ivtv site and cvs as of 9:00
> pm EST with no better luck.

Don't expect instant results on ivtv development from the mythtv users list.

> Thanks,
> Vinton
>
>
> Nov 24 01:00:02 localhost kernel: ivtv: DMA buffer DeQueue failed! got
> 1, want 2
> Nov 24 01:00:02 localhost kernel: ivtv: DEC: free_q: 0 elements
> Nov 24 01:00:02 localhost kernel: ivtv: DEC: dma_q: 0 elements
> Nov 24 01:00:02 localhost kernel: ivtv: DEC: full_q: 99 elements
> Nov 24 01:00:02 localhost kernel: ivtv: DMA buffer DeQueue failed! got
> 1, want 2
> Nov 24 01:00:02 localhost kernel: ivtv: DEC: free_q: 0 elements
> Nov 24 01:00:02 localhost kernel: ivtv: DEC: dma_q: 0 elements
> Nov 24 01:00:02 localhost kernel: ivtv: DEC: full_q: 99 elements
> Nov 24 01:00:02 localhost kernel: ivtv: DMA buffer DeQueue failed! got
> 1, want 2
> Nov 24 01:00:02 localhost kernel: ivtv: DEC: free_q: 0 elements
> Nov 24 01:00:02 localhost kernel: ivtv: DEC: dma_q: 0 elements
> Nov 24 01:00:02 localhost kernel: ivtv: DEC: full_q: 99 elements
> Nov 24 01:00:02 localhost kernel: ivtv: DMA buffer DeQueue failed! got
> 1, want 2
> Nov 24 01:00:06 localhost kernel: ivtv: DEC: free_q: 0 elements
> Nov 24 01:00:06 localhost kernel: ivtv: DEC: dma_q: 0 elements
> Nov 24 01:00:06 localhost kernel: ivtv: DEC: full_q: 99 elements
> Nov 24 01:00:06 localhost kernel: v: DMA buffer DeQueue failed! got 1,
> want 2
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE/wcHiT8BYaKRUpkQRAqpQAJ9wmEouqAl0gv7hgSwYEl2ceVr+KQCeOaZT
CHziNl+rpiQZMyQD5WV7te8=
=/VWW
-----END PGP SIGNATURE-----