On Sunday 27 November 2005 19:48, Xenna wrote:
> On Sun, 27 Nov 2005 15:47:43 +0100, "Xenna"
>
> <[EMAIL PROTECTED]> said:
> > On Sun, 27 Nov 2005 15:11:51 +0100, "Hans Verkuil"
> > <[EMAIL PROTECTED]>
> >
> > said:
> > > On Sunday 20 November 2005 12:43, Xenna wrote:
> > > > OK, I tried the following things:
> > > > - I removed the power leads from 2 of the 3 harddisks. (this
> > > > left just the Matrox video the 2 Hauppauge cards and the 250 GB
> > > > SATA disk): No difference.
> > > > - I replaced the Matrox AGP videocard with the ASUS AGP
> > > > videocard from my GF's PC: No difference.
> > > > - I swapped the Hauppauge cards around: No difference.
> > > >
> > > > So on with the i2c debugging. The ic2-algo-bit module had a
> > > > debug option so I tried that:
> > > >
> > > > $ modprobe i2c-algo-bit i2c_debug=2
> > > > $ modprobe i2c-dev
> > > > $ modprobe videodev
> > > > $ modprobe i2c-via
> > > >
> > > > $ insmod /tmp/ivtv.ko ivtv_debug=33
> > > >
> > > > http://pastebin.ru/1000
> > > >
> > > > I'm busy downloading KnoppMyth R5A22. I'll try and see if I get
> > > > the same symptoms when I boot from the KnoppMyth CD. If so, I
> > > > intend to put the 2 PVR cards in my GF's PC and boot with
> > > > KnoppMyth also. See if I get the same problem. If so, the
> > > > problem must be either with the cards or the ivtv/i2c drivers
> > > > (I think).
> > >
> > > Any news on this?
> >
> > I'm glad you haven't forgotten me :)
> >
> > The KnoppMyth CD wanted to reformat my GF's PC to run a backend so
> > I abandoned that.
> >
> > I've done the following things:
> >
> > - I found someone offering a one year old PVR350 in my city and
> > tried that in combination with my PVR500. Exactly the same
> > problems. - I upgraded my Fedora kernel to 2.6.14 and compiled the
> > latest 0.4 version of IVTV. I must have broken something in the
> > process because then everything started failing. My '500 only gave
> > a signal on the second tuner and nothnig but static on the first
> > one. My '350 stopped working altogether.
> >
> > I veryfied that I hadn't fried my cards in the process by putting
> > them in a windows PC and running them under WinTV. Both work well
> > (although WinTV doesn't seem to use the second '500 tuner).
> > Conclusion: my FC4 install must be hosed.
> >
> > This sunday I'm busy installing FC4 (that yum upgrade sure takes
> > long) on my desktop (an older Dell gx260, 2.4 P4 CPU). If I get the
> > cards to coexist properly on that system, I'll let you know and
> > just start using that as a Myth server instead (and make a backup).
> > If they don't work together, I'll reinstall my current server as
> > well and go back to life with two tuners.
> >
> > It seems you live close to my place of work (if you're still in C
> > a/d IJ). If at some point you'd be interested in looking at the
> > cards or system I could arrange that easily. ( all in the interest
> > of ivtv perfection of course ;)
>
> It works!
>
> After completing the ivtv install and setting up the right firmware
> version for the PVR500 I now have TV image and sound on all three
> tuners. I haven't looked at the TV-Out and the IR input but I'm
> hopeful that that will also be OK.
>
> So now it seems to me that the most likely 'culprit' must be my "MSI
> K8N Neo2 Platinum-54G,S939,nForce3 Ultra, GLAN" motherboard or maybe
> even the AMD 64 CPU (not likely I hope). Something in the 2.6.13/14
> kernels or the ivtv driver must have problems in using this
> motherboard in combination with both a PVR350 and a PVR500 while both
> cards work fine when alone in the system. What do you think, Hans?
>
> I'm still thinking whether to get a different 75 EURO Socket 939
> motherboard to get my especially-bought-for-MythTV server up and
> running or break down and just use the Dell as a server.

I'd rather fix the bug! But in order to do that I need you to compile 
the linux kernel yourself. Either the FC4 kernel or just download the 
kernel source from ftp.kernel.org and compile that one. Once you have 
that and can reproduce the same problem, then I can tell you where to 
put some debug messages so that I can see what is happening. Debug 
module options are not enough in this case.

        Hans

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

Reply via email to