On Sat, 19 Nov 2005 12:35:42 +0100, "Hans Verkuil" <[EMAIL PROTECTED]>
said:
> On Saturday 19 November 2005 11:51, Xenna wrote:
> > On Sat, 19 Nov 2005 11:26:41 +0100, "Hans Verkuil"
> > <[EMAIL PROTECTED]>
> >
> > said:
> > > On Saturday 19 November 2005 11:21, Xenna wrote:
> > > > On Sat, 19 Nov 2005 11:00:38 +0100, "Hans Verkuil"
> > > > <[EMAIL PROTECTED]>
> > > >
> > > > said:
> > > > > On Saturday 19 November 2005 10:47, Xenna wrote:
> > > > > > L.S,
> > > > > >
> > > > > > I have recently set up a MytTV server from scratch . I
> > > > > > started out with a single PVR350 which work fine, both the
> > > > > > tuner and TV-Out. I was very happy with MythTV so a week ago
> > > > > > I went out and bought a PVR500. (both cards are quite new
> > > > > > which may be part of the problem).
> > > > > >
> > > > > > The two cards work perfectly on their own, but whenever I try
> > > > > > to use them together in the system the PVR350 fails
> > > > > > altogether and the PVR500 limps on with only one tuner.
> > > > > >
> > > > > > Log of the PVR350 on its own: http://pastebin.com/435195
> > > > > > Log of the PVR500 on its own: http://pastebin.com/435196
> > > > > > Log and problem description of both cards together:
> > > > > > http://pastebin.com/435194
> > > > > >
> > > > > > /etc/modprobe.conf: http://pastebin.com/435199
> > > > > >
> > > > > > System specs:
> > > > > > MSI K8N Neo2 Platinum-54G,S939,nForce3 Ultra, GLAN
> > > > > > AMD Athlon 64 3200+, 2.0Ghz, 512Kb cache,S-939,Box
> > > > > > Dane-Elec 1Gb Dual-Channel Kit, 2x512Mb, PC3200
> > > > > > Matrox G400 AGP Dual Head 32MB
> > > > > > Fedora Core 4 (i386)
> > > > > > IVTV 0.4.0 (RPM install according to
> > > > > > http://wilsonet.com/mythtv/fcmyth.php)
> > > > > >
> > > > > > I've seen many reports of these cards working well together
> > > > > > (that's why I bought the PVR500) but I've also seen reports
> > > > > > of problems similar (or somewhat different) to mine. I'm
> > > > > > thinking that perhaps newer versions of the Hauppauge cards
> > > > > > have come out that the IVTV drivers are not quite compatible
> > > > > > with.
> > > > > >
> > > > > > Thanks very much in advance for any help.
> > > > > >
> > > > > > If I need to do some more testing let me know!
> > > > >
> > > > > Make sure you use no module options at all (I saw from the log
> > > > > that you use at least a enable_output option for saa7127). Make
> > > > > sure the cards do not get too hot (overheating is one cause for
> > > > > problems). It has nothing to do with newer version since they
> > > > > work fine on their own.
> > > >
> > > > Hi Hans,
> > > >
> > > > Thanks for looking into this.
> > > >
> > > > I commented all the modprobe.conf option lines out as seen below:
> > > >
> > > > # ivtv modules setup
> > > > alias char-major-61 lirc_i2c
> > > > alias char-major-81 ivtv
> > > > alias char-major-81-0 ivtv
> > > > alias char-major-81-1 ivtv
> > > > alias char-major-81-2 ivtv
> > > > alias tveeprom tveeprom-ivtv
> > > > alias msp3400 msp3400-ivtv
> > > > #options ivtv ivtv_debug=1 tuner=5
> > > > #options saa7127 enable_output=1 output_select=0 pal=1
> > > > install ivtv /sbin/modprobe --ignore-install ivtv
> > > > #; /sbin/modprobe ivtv-fb
> > > > #install lirc_i2c /sbin/modprobe ivtv; /sbin/modprobe
> > > > --ignore-install lirc_i2c
> > > >
> > > > Unfortunately the situation remains exactly the same. Overheating
> > > > seems unlikely. The cards are not hot to the touch at all and the
> > > > system is hardly doing any work at all.
> > > >
> > > > Do you have any other suggestions?
> > >
> > > If you switch the cards around, does that make any difference? Can
> > > you make the kernel log available of the ivtv initialization now
> > > that you have removed the module options?
> >
> > Switching the cards around was one of the first things I tried, but
> > it didn't make any difference (surprisingly - to me - the PVR350 is
> > detected as the first card no matter which order I put them in).
> >
> > The log with the module options removed is here:
> > http://pastebin.com/435225
> >
> > > It's a weird one, never seen something like this before.
> >
> > I was afraid of that :(
>
> Interesting problem: it looks as if the I2C bus of the pvr350 isn't
> detected. Run the i2cdetect program (part of the lm-sensors package):
>
> First run: i2cdetect -l
I did that, it gave no output, then I tried "i2cdetect -v -l", which
gave:
Warning: Unsupported flag "-v"!
Syntax: i2cdetect [-y] [-a] [-q|-r] I2CBUS [FIRST LAST]
i2cdetect -l
i2cdetect -V
I2CBUS is an integer
With -a, probe all addresses (NOT RECOMMENDED)
With -q, uses only quick write commands for probing (NOT RECOMMENDED)
With -r, uses only read byte commands for probing (NOT RECOMMENDED)
If provided, FIRST and LAST limit the probing range.
With -l, lists installed busses only
Error: No I2C busses found!
Be sure you have done 'modprobe i2c-dev'
and also modprobed your i2c bus drivers
So I tried 'modprobe i2c-dev' and then i2cdetect worked. It seems the
i2c-dev module isn't loading automatically. (don't know if it should)
This had me hoping that perhaps the cards would now function properly
but the symptoms appear to remain unchanged.
> This shows all I2C busses. For each ivtv bus run:
>
> i2cdetect -a X (where X is the bus number, e.g. 3 for bus i2c-3).
>
> Please report the output of these commands.
http://pastebin.com/435253
Regards,
Xenna
_______________________________________________
ivtv-users mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-users