James,

        Can you post the same info Brendan did? Full ivtv debug info, exact
modules.conf, motherboard model/specs/chipset?

I've tried the modules.conf Brenden posted, and I still get the same
result, static. :( Although I do get these errors in my ivtv debug log
using the new modules.conf settings:

May 10 23:10:51 ipso kernel: i2c_adapter i2c-0: I2C level transfers not
supported
May 10 23:10:51 ipso kernel: wm8775: Failed to update register 0 (R23)
with 2e00.
May 10 23:10:51 ipso kernel: i2c_adapter i2c-0: I2C level transfers not
supported
May 10 23:10:51 ipso kernel: wm8775: Failed to update register 2 (R11)
with 1621.
May 10 23:10:51 ipso kernel: i2c_adapter i2c-0: I2C level transfers not
supported
May 10 23:10:51 ipso kernel: wm8775: Failed to update register 3 (R12)
with 1902.
May 10 23:10:51 ipso kernel: i2c_adapter i2c-0: I2C level transfers not
supported
May 10 23:10:51 ipso kernel: wm8775: Failed to update register 9 (R18)
with 2482.
May 10 23:10:51 ipso kernel: i2c_adapter i2c-0: I2C level transfers not
supported
May 10 23:10:51 ipso kernel: wm8775: Failed to update register 10 (R19)
with 2601.
May 10 23:10:51 ipso kernel: i2c_adapter i2c-0: I2C level transfers not
supported
May 10 23:10:51 ipso kernel: wm8775: Failed to update register 12 (R21)
with 2b0f.
May 10 23:10:51 ipso kernel: ivtv: i2c attach [client=wm8775[50],ok]
May 10 23:10:51 ipso kernel: tda9885/6/7: chip found @ 0x86

I haven't had time to narrow down the exact cause yet, but I will try to
do so in the coming days.

Also Brenden and/or James, can you email me directly your 3 firmware
files (HcwMakoA.ROM,ivtv-fw-dec.bin,ivtv-fw-enc.bin)? My MD5 sums don't
match yours at all, even though I got the firmware from my CD (v2.4).

Thanks.

On Tue, 2005-05-10 at 19:45 -0500, James A. Pattie wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Brendan Hoar wrote:
> > On Tue, 10 May 2005, Mike Benoit wrote:
> > 
> >>Brendan,
> >>
> >>    Can you post your full ivtv debug information, as well as your
> >>motherboard model/chipset/specs for comparison?
> > 
> > 
> > 
> > 0. In the past, I did have to search and destroy older tuner.ko modules
> > that were hanging around causing trouble, but I *think* that chris fixed
> > the make install process in the driver directory's makefile.
> > 
> 
> snip..
> 
> > 
> > 5. Cards (in order recognized): PVR-350, PVR-500, HD-3000 (HD-3000 not
> > configured with mythtv yet).
> > 
> > 6. Contents of /etc/mythtv/modules/ivtv file (the debian way?):
> >     alias char-major-61 lirc_i2c
> >     alias char-major-81 videodev
> >     alias char-major-81-0 ivtv
> >     alias char-major-81-1 ivtv
> >     alias char-major-81-2 ivtv
> >     options ivtv ivtv_std=0,0,0 tuner=47,57,57 tda9887=0,0,0
> >     ivtv_debug=1,1,1
> >     options cx25840 no_black_magic=1 i2c_enable=1,1
> >     options saa7127 i2c_enable=1,-1,-1
> >     options msp3400 once=1 simple=1
> > 
> 
> yeah!!!! It works!!!  I added the ivtv options line, removing the leading 
> value
> since I don't have a 350 installed and now I get tuner input!!!
> 
> I also added the cx25840, saa7127 and msp3400 just to be complete (even though
> the saa7127 and msp3400 aren't being loaded in this scenario).
> 
> I've done the testing and the only options that are required to make it work
> consistently for me are:
> 
> - --------------------------------
> options ivtv tda9887=0,0 ivtv_debug=1,1
> options cx25840 no_black_magic=1
> - --------------------------------
> 
> The ivtv_debug is just to limit debug output. :)
> 
> I did some quick searching in the wiki and the mailing list archives and
> couldn't find anything that explicitly stated that the pvr150/500 needs the
> tda9887 option to ivtv to work!  Shouldn't the driver be detecting that it 
> needs
> that module and loading it automatically?
> 
> - --
> James A. Pattie
> [EMAIL PROTECTED]
> 
> Linux -- SysAdmin / Programmer
> Xperience, Inc.
> http://www.pcxperience.org/
> 
> GPG Key Available at http://www.pcxperience.com/gpgkeys/james.html
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.5 (GNU/Linux)
> Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
> 
> iD8DBQFCgVWqtUXjwPIRLVERAlhkAKDoaDcxxBFPINsqDR/beM13N07SKACgvEwE
> CAs7PJSZrHM8v9+z6y0q1Tw=
> =V9KH
> -----END PGP SIGNATURE-----
> 
-- 
Mike Benoit <[EMAIL PROTECTED]>

Attachment: signature.asc
Description: This is a digitally signed message part

Reply via email to