[mythtv-users] PVR 500 defective?

Cory Papenfuss papenfuss at juneau.me.vt.edu
Thu Sep 29 10:47:38 UTC 2005


 	Well, I played with my PVR-500 a bit last night.  I followed the 
thread here:
http://www.gossamer-threads.com/lists/ivtv/devel/24322?search_string=second%20pvr-500;#24322

 	My card had the 0x60 vs. 0x61 tuners just like the other guy's. 
So, I applied the patch that adds the lines:

    TVEEPROM_KERN_INFO("Second (radio) tuner idx %d\n",
                                                    eeprom_data[i + 2]);
 	to tveeprom.c.  It does seem to work now.

 	I don't know if that helps your problem.  In fact, I haven't even 
figured out how that patch really does anything... it appears to only 
printk() a debug message.

-Cory

On Wed, 28 Sep 2005, Cory Papenfuss wrote:

> 	I will try to look closer at my card tonight and see if I can see if 
> my dmesg log matches anyone else's situation.  My trouble is getting the 
> machine in the same place as the cable signal and 'net access.
>
> -Cory
>
> On Wed, 28 Sep 2005, Danesh wrote:
>
>> Cory::
>> 
>> Both tuners seem to initialize.
>> 
>> 
>> Dave::
>> 
>> Under /lib/modules I have
>> 
>> -r--r--r--   1 root root 369K Sep 27 23:07 HcwFalcn.rom
>> -r--r--r--   1 root root  14K Sep 27 23:07 HcwMakoA.ROM
>> lrwxrwxrwx   1 root root   25 Sep 27 23:07 ivtv-fw-enc.bin ->
>> /lib/modules/HcwFa
>> 
>> md5sums
>> 
>> 5f5fa240ada73c3565f5f7de4c7b5138  HcwFalcn.rom
>> 3a4803384f749d644ee1f1ca9dcb12fa  HcwMakoA.ROM
>> 5f5fa240ada73c3565f5f7de4c7b5138  ivtv-fw-enc.bin
>> 
>> I will try downgrading the firmware to an older version. Is the
>> 0x02040011 version the one on the CD?
>> 
>> I can access both tuners fine. Only one gives me nothing but static. I
>> don't know if this is related to a 'vbi: Invalid argument' I get on
>> the terminal when mythfrontend is running.
>> 
>> 
>> Greg::
>> 
>> Thanks for the pointer. I had it setup this way already. The capturing
>> Im trying to do which is giving me static is using ptune and cat
>> /dev/v4l/video0 > ~/vid0.mpg. The tuner0, tuner1, s-video0, etc
>> doesn't come into it.
>> 
>> 
>> 
>> On 9/28/05, Dave Sherohman <esper at sherohman.org> wrote:
>>> On Wed, Sep 28, 2005 at 10:34:40AM -0400, Cory Papenfuss wrote:
>>>>       There was a thread about a similar thing on ivtv-devel a week or
>>>> so ago.  A friend of mine's PVR-500 and the one I recently purchased has
>>>> the same problem:  only tuner1 works... tuner2 is static.  I haven't had
>>>> time to work on mine and figure it out.
>>> 
>>> Looks to me like Danesh has a different problem...  He said he's
>>> getting static from the first tuner (he calls it "video0", you call
>>> it "tuner 1"), while the second works fine.
>>> 
>>> I have a problem with mine where the first tuner works fine and the
>>> second tuner returns nothing, though, and haven't been able to get
>>> anything definitive from ivtv-users...  Guess I'll have to check out
>>> ivtv-devel and see what I can find there.
>>>
>>>>       IIRC, the current theory has to do with i2c not initializing it
>>>> properly and/or the tveeprom module used is the wrong one.  I tried
>>>> manually loading the ivtv-based tveeprom on mine last night (rather than
>>>> the kernel one), but no joy.
>>> 
>>> Oh, looks like you're affected by the problem under discussion on
>>> ivtv-devel?  Do you show a bunch of errors in dmesg that look like
>>> "ivtv warning: i2c client addr: 0x44 not found for command
>>> 0x40046406!"?  If so, that's the same problem I have...  (Danesh,
>>> OTOH, is definitely having a different problem than I am, since he
>>> initializes without any of those errors.)
>>>
>>>>  On Wed, 28 Sep 2005, Danesh wrote:
>>> 
>>>>> cx25840: loading /lib/modules/HcwMakoA.ROM
>>>>> ivtv: i2c attach to card #0 ok [client=cx25840, addr=44]
>>>>> ivtv: i2c attach to card #0 ok [client=wm8775, addr=1b]
>>>>> tda9885/6/7: chip found @ 0x86
>>>>> ivtv: i2c attach to card #0 ok [client=tda9887, addr=43]
>>>>> ivtv: loading /lib/modules/ivtv-fw-enc.bin
>>>>> ivtv: Encoder revision: 0x02050032
>>>>> ivtv warning: Encoder Firmware can be buggy, use version 0x02040011!!!!
>>> 
>>> This is what I would look at first.  Are you sure you have the right
>>> firmware binaries in /lib/modules?  Here's what I've got in mine:
>>> 
>>> -r--r--r--  1 root root  14264 2005-08-27 20:14 HcwMakoA.ROM
>>> -rw-r--r--  1 root root 262144 2005-08-27 20:12 ivtv-fw-dec.bin
>>> -rw-r--r--  1 root root 262144 2005-08-27 20:12 ivtv-fw-enc.bin
>>> 
>>> # md5sum HcwMakoA.ROM ivtv-fw-dec.bin ivtv-fw-enc.bin
>>> 3a4803384f749d644ee1f1ca9dcb12fa  HcwMakoA.ROM
>>> 305dba74bbe5905447add8883f3ecb68  ivtv-fw-dec.bin
>>> ab75947ef1b086e26f9b08e628baa02e  ivtv-fw-enc.bin
>>> 
>>> If yours don't match, you may want to try downloading an older
>>> ivtv-fw-enc.bin/ivtv-fw-dec.bin and see if that helps.  (A check of
>>> my dmesg output shows that I'm using revision 0x02040011, as
>>> recommended by the warning you're getting.)
>>> 
>>> --
>>> The freedoms that we enjoy presently are the most important victories of 
>>> the
>>> White Hats over the past several millennia, and it is vitally important 
>>> that
>>> we don't give them up now, only because we are frightened.
>>>   - Eolake Stobblehouse (http://stobblehouse.com/text/battle.html)
>>> 
>>> 
>>> _______________________________________________
>>> mythtv-users mailing list
>>> mythtv-users at mythtv.org
>>> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
>>> 
>>> 
>>> 
>> _______________________________________________
>> mythtv-users mailing list
>> mythtv-users at mythtv.org
>> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
>> 
>
>

-- 

*************************************************************************
* Cory Papenfuss                                                        *
* Electrical Engineering candidate Ph.D. graduate student               *
* Virginia Polytechnic Institute and State University                   *
*************************************************************************



More information about the mythtv-users mailing list