Hello,

I have been using MythTV with the latest ivtv drivers for some time.
Then a few months ago, about 2/3rds of my channels went out.  I don't
believe I was making any changes to the software at the time.  The
channels I lost now all appear to be partially tuned to the wrong
channel.  For instance, I think channel 56 or thereabouts appears on
most of the dead channels along with a healthy helping of fuzz over the
top.  The 1/3rd of channels that remain functional work fine.

When this first occurred, I suspected it was an issue with my cable
provider.  Normal analog TVs worked fine on the line, but I thought
perhaps the analog/digital conversion was more picky if there was a
noisy input, so I didn't put a lot of effort into debugging since I was
already in the process of moving.

Now that I've finally moved in and had time to work on the mythbox, I
observe the same symptoms.  I'm on a completely different cable provider
now, but still 2/3rds of my channels are duplicated fuzz from another
channel.  I have tested using ivtv-tune to verify that it's not just
MythTV whacking out.  Sure enough I still get fuzz on those dead
channels when reading from /dev/video0.

It is certainly possible that my card is dying, but I did run across a
mailing list thread a few months back where other users had experienced
the same bizarre behavior in the 350 and it was due to a driver bug.  I
have looked again for that thread but have failed to find it.

So, my question is: has anyone else recently observed this issue?  If
so, was it a hardware problem or could the drivers be blamed at all?  

Here's a few details about my system configuration.  I can certainly
provide more in the future if necessary:

Distro: Debian testing
Kernel: custom 2.4.22 built from Debian sources
ivtv: the drivers that come with the kernel + 1.0.3
No 350 output framebuffer set up.
Other 3rd-party modules: nvidia proprietary, lirc 0.8.2

Thanks in advance for any help.  Please let me know what commands you'd
like me to run if you need more technical detail on my configuration.

tim

_______________________________________________
ivtv-users mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-users

Reply via email to