On 5/14/05, Brian Jackson <[EMAIL PROTECTED]> wrote:
> Nick Rosier wrote:
> > I just added another PVR150MCE (PAL) to my system but I have trouble
> > getting this setup to work; the detection order of the cards is: 350,
> > new 150, old 150. Initialisation of the 350 and new 150 works fine but
> > the old 150 won't initialize properly anymore:
> >
> > ivtv: i2c client addr: 0x50 not found!
> > ivtv: Error -19 reading Hauppauge eeprom.
> > ivtv: Possible causes: the tveeprom module was not loaded, or
> > ivtv: the eeprom kernel module was loaded before the tveeprom module.
> >
> > tveeprom module is loaded (it's used for the 2 other cards) and kernel
> > eeprom is not loaded so can't be that...
> > Seeing as it's my old card which worked fine before, I doubt it's a HW
> > problem.
> > Anyone got any ideas?
>
> Did you try just moving the cards around? Sometimes motherboards only have a
> certain number of pci slots that can be busmaster. Maybe you've got too many
> cards in that board now.
I've got the 350 in PCI slot 1, my new 150 in PCI slot 2 and my old
150 in PCI slot 3.
So it worked with cards in slot 1 and 3. Put the new card in slot 2;
now I've got working cards in slots 1 and 2, the card in slot 3
stopped working. I swapped both 150's (slots 2 and 3) and I'm still
stuck with the cards in slots 1 and 2 working, slot 3 still doesn't
work
I think it's got something to do with the i2c busses:
# i2cdetect -l
i2c-4 unknown SMBus nForce2 adapter at 4c40
Algorithm unavailable
i2c-3 unknown SMBus nForce2 adapter at 4c00
Algorithm unavailable
i2c-2 unknown ivtv i2c driver #2
Algorithm unavailable
i2c-1 unknown ivtv i2c driver #1
Algorithm unavailable
i2c-0 unknown ivtv i2c driver #0
Algorithm unavailable
0 -> 350
1 -> working 150
2 -> not working 150
# i2cdetect -y -a 0
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
10: XX XX XX XX XX XX XX XX UU XX XX XX XX XX XX XX
20: XX UU XX XX XX XX XX XX XX XX XX XX XX XX XX XX
30: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
40: UU XX XX UU UU XX XX XX XX XX XX XX XX XX XX XX
50: UU XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
60: XX UU XX XX XX XX XX XX XX XX XX XX XX XX XX XX
70: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
# i2cdetect -y -a 1
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
10: XX XX XX XX XX XX XX XX XX XX XX UU XX XX XX XX
20: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
30: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
40: XX XX XX UU UU XX XX XX XX XX XX XX XX XX XX XX
50: UU XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
60: XX UU XX XX XX XX XX XX XX XX XX XX XX XX XX XX
70: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
# i2cdetect -y -a 2
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
10: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
20: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
30: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
40: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
50: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
60: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
70: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
So i2c-busses 0 and 1 return values for some addresses, bus 2 doesn't
seem to be working.
N.
-------------------------------------------------------
This SF.Net email is sponsored by Oracle Space Sweepstakes
Want to be the first software developer in space?
Enter now for the Oracle Space Sweepstakes!
http://ads.osdn.com/?ad_ids93&alloc_id281&op=click
_______________________________________________
ivtv-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ivtv-devel
