> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Matt > Sent: Sunday, 10 April 2005 3:29 p.m. > To: ivtv-devel@lists.sourceforge.net > Subject: Re: [ivtv-devel] pvr500 > > On Apr 9, 2005 8:22 PM, Rick Stewart > <[EMAIL PROTECTED]> wrote: > > As far as I can tell, you comma separate settings for each tuner in > > their device order. So if /dev/video0 is your first PVR-250, > > /dev/video1 is your second PVR-250, /dev/video3 is input 0 > from your > > PVR-500 and /dev/video4 is input 1 from your PVR-500 your > modprobe.conf might look like: > > > > options saa7127 i2c_enable=-1,-1,-1,-1 options cx25840 > > i2c_enable=1,1,1,1 no_black_magic=1 options tda9887=0 options ivtv > > ivtv_debug=1 tuner=47,47,58,58 > > > > As long as your tuners are auto-detecting OK, you should be able to > > get the actual numbers for the last line from the output of dmesg. > > Some others out there might have better advice but that's > my take on > > it ;-) > > > > Cheers, > > > > Rick > > > > > -----Original Message----- > > > From: [EMAIL PROTECTED] > > > [mailto:[EMAIL PROTECTED] On Behalf Of Matt > > > Sent: Sunday, 10 April 2005 1:08 p.m. > > > To: ivtv-devel@lists.sourceforge.net > > > Subject: Re: [ivtv-devel] pvr500 > > > > > > On Apr 9, 2005 7:10 PM, Rick Stewart > <[EMAIL PROTECTED]> > > > wrote: > > > > I was getting this exact same problem with a PVR150 and it > > > all burst > > > > into life after adding the following options to modprobe.conf > > > > > > > > options saa7127 i2c_enable=-1 > > > > options cx25840 i2c_enable=1 no_black_magic=1 options tda9887=0 > > > > options ivtv ivtv_debug=1 tuner=58 > > > > > > > > I don't know why setting the tuner type makes any > > > difference because > > > > it autodetects as a type 58 - NB: you'll want to put your > > > own tuner type in! > > > > > > > > > > > > > > So if I had 2 PVR-250s and 1 PVR-500, what should it look like? > > > > > > Matt > > > > > > > > Thanks, I tried it, but it still didn't work. dmesg says my > tuner for the 250s is 8 (like I remember it being before) and > for the 500 is 57. > Either way, putting them in explicitly didn't work. I still > have NO clue why it work the 1 time out of 100 tries. The > only change was that Alsa wasn't installed in the new kernel > when I tried it. >
Have you tried removing ivtv and reloading it again rather than just Firing up myth after a reboot? i.e. #rmmod ivtv #modprobe ivtv Then starting mythbackend and mythfrontend. It sometimes seems to work better/more reliably for some reason ... > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide Read honest & > candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > _______________________________________________ > ivtv-devel mailing list > ivtv-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/ivtv-devel > ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ ivtv-devel mailing list ivtv-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ivtv-devel
