On Thu, 24 Mar 2005 22:20:16 -0500, Scot L. Harris <[EMAIL PROTECTED]> wrote: > On Thu, 2005-03-24 at 22:01, Nick wrote: > > On Thu, 24 Mar 2005 21:43:10 -0500, Scot L. Harris <[EMAIL PROTECTED]> > > wrote: > > > On Thu, 2005-03-24 at 20:10, Scot L. Harris wrote: > > > > For the past couple of weeks I have been having great success running a > > > > mythtv system with a single PVR-350 card. > > > > > > > > Today I tried to add a second capture card, a PVR-250MCE, and have run > > > > into some problems. > > > > > > > > > Scot, > > > > I would also assume that if the frontend is configured to use the > > 350's decoder, both sound and video would be produced from the 350. > > Are you sure it's not that the 350 audio is hooked back into your > > on-board sound? > > > > > Does the order of the cards in the system make a difference? The new > > > PVR-250 seems to be video0 now and the PVR-350 is video1. > > > > Per my other message, yes the order did make a difference. Re-ordering > the cards would probably have worked as well as the solution I used > which was to modify the entry in the mythfrontend setup screens to point > to video17 instead of video16 for the decoder output. > > This piece is working now. > > > > > > I would hazard a guess that when you installed the 250 card you > > installed it inbetween your AGP slot and the 350 card. It has been > > given a lower BusID which (I think) means it is detected first (this > > is also likely why it grabs video0) > > > > Correct. Actually I am using a PCI video card but it is only used > during setup and debug as I am using the PVR-350's output. > > > > > *possibles* It looks like that 250 card has not been properly > > identified in the bus scan (or perhaps it just never is. Make sure you > > are using a version of ivtv that supports the 250MCE and also that > > there are no udev issues stopping the correct devices being created > > when the ivtv drivers are loaded. > > > > Which version of ivtv supports the 250MCE? I currently have these > loaded: > > ivtv-firmware-enc-2.04.024-4.at > ivtv-kmdl-2.6.10-1.760_FC3smp-0.3.2d-67.rhfc3.at > ivtv-firmware-1.8a-4.at > ivtvdev-0.8-1.rhfc3.at > ivtv-firmware-dec-2.02.023-4.at > perl-Video-ivtv-0.13-6.rhfc3.at > ivtv-0.3.2d-67.rhfc3.at > > > > (On a personal note, I gave up on FC3 and downgraded to FC2 and since > > then my system has been a lot more stable. I''ll need to get FC3 > > installed at some point but there were additional frustrations like > > the udev issues that FC2 didn't give me) > > This does not seem to be a udev issue, at least I don't think it is. I > did need to copy the nvidia* files to the udev/devices directory to get > that part working but have not had to do anything with the video stuff > yet. > > I was able to run the dd test with both cards and created files I was > able to play through mplayer. > > It maybe that I need to reorder the cards to get the 350 as video0 again > and the 250 as video1. I suspect though that there is an entry buried > in the database that I could modify just like the encoder entry to get > this working correctly.
You shouldn't have a problem with the ivtv version, but might want to try the latest 0.2.x if you have any stability issues, and as you can access the cards from the command line they are seemingly installed properly. I would therefore suggest going back into mythtv-setup and remvoing the card definitions to clear the database, and then redefining them with the correct device names and inputs as you had (i.e. both tuners sharing the same cable lineup) and then retesting from inside myth. > BTW: thanks for the reply. It helps to know someone is listening. :) > No worries. When I started before Christmas I had absolutely zero mythtv or ivtv knowledge so it's nice to be able to help out others if I can at all. Cheers, Nick _______________________________________________ mythtv-users mailing list [email protected] http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
