Just wanted to follow up on this thread to let everyone know what became of this issue.
First, I gave up on the 500 and returned it in exchange for another 250. So now, I have dual 250s.
I installed one of the 250s and went through the motions of trying to
validate the feed on /dev/video0
That step was specific to using a PVR-350 with TV Out ( under the
heading Running X on the PVR-350's TV-Out ).
-Tim
On 10/10/05, Larry K [EMAIL PROTECTED] wrote:
Tim,
I don't see that anywhere in Jarod's guide. Appreciate further info.
On 10/10/05, Timothy McFadden [EMAIL PROTECTED]
Tim,
I don't see that anywhere in Jarod's guide. Appreciate further info.On 10/10/05, Timothy McFadden [EMAIL PROTECTED]
wrote:Also check to see if you used Jarod's mkinit-rd patch to include the
ivtv drivers.You need to re-make the initial ramdisk with the newdrivers
I now have the right version of the ivtv driver loading. To do
this I had to upgrade to kernel 2.6-12-1.1378 in order to get atrpms to
install the driver properly. I was using 2.6-10.x and there
appears to be no prepackaged ivtv 0.3.x driver for this kernel.
Now, having gotten the ivtv driver
One additional thing I fergot to mention. If I take out the 3 alias commands from modprobe.conf:
alias tveeprom tveeprom-ivtv
alias tuner tuner-ivtv
alias msp3400 msp3400-ivtv
The unknown module messages go away in the dmesg output. Then, the modprobe info looks the same as above.
Any
On Monday 10 October 2005 22:13, Larry K wrote:
I now have the right version of the ivtv driver loading. To do this I had
to upgrade to kernel 2.6-12-1.1378 in order to get atrpms to install the
driver properly. I was using 2.6-10.x and there appears to be no
prepackaged ivtv 0.3.x driver for
On Oct 10, 2005, at 3:13 PM, Larry K wrote:
I now have the right version of the ivtv driver loading. To do
this I had to upgrade to kernel 2.6-12-1.1378 in order to get
atrpms to install the driver properly. I was using 2.6-10.x and
there appears to be no prepackaged ivtv 0.3.x driver
On 10/10/05, Keith C [EMAIL PROTECTED] wrote:
On Oct 10, 2005, at 3:13 PM, Larry K wrote: I now have the right version of the ivtv driver loading.To do this I had to upgrade to kernel 2.6-12-1.1378 in order to get atrpms to install the driver properly.I was using
2.6-10.x and there appears to be
I don't have the tveeprom.c anywhere on my system ( I searched for it like so: find / -name tveeprom.c).
I suspect I am using the kernel version of tveeprom now. However,
I still have the original issue that is the source of my angst: I
get good audio and video on /video1, but nothing but static
Keith C wrote:
On Oct 10, 2005, at 3:13 PM, Larry K wrote:
I now have the right version of the ivtv driver loading. To do this I
had to upgrade to kernel 2.6-12-1.1378 in order to get atrpms to
install the driver properly. I was using 2.6-10.x and there appears
to be no prepackaged ivtv
I can certainly install the card on my win2k machine as a test.
What I'm doing now to test the card is to cat from /dev/video0 and /dev/video1, like so:
# /usr/bin/ivtvctl -u 0x3000 -d /dev/video0
# /usr/bin/ivtvctl -p 6 -d /dev/video0
# /usr/bin/ivtvctl -f width=720,height=480 -d /dev/video0
This problem has come up on the list several times before. lirc_i2c
sometimes pulls in the cx88xx module for some reason (doesn't happen
to me any more, but did until fairly recently) and that conflicts with
the ivtv version of tveeprom. For me, editing tveeprom.c did NOT fix
the problem, I still
Why is cx88xx loading? You have another capture card in there
somewhere? And if you do, this is a conflict where the kernel cx88xx
module will not use the ivtv tveeprom. So you'll have to use the
kernel version of tveeprom.
I don't have anything installed except the PVR-500MCE. I have no
I don't have anything installed except the PVR-500MCE. I have no
idea why cx88xx is loading. The machine has the pvr-500 and an
nvidia video card. That's it.
Then you should probably look into why bttv/cx88xx is loading. Thats
not a good thing. Look through dmesg for more bttv and
On 10/10/05, Larry K [EMAIL PROTECTED] wrote:
Actually, I'm using 0.3.8. Not 0.4.x.
Ok. Well, I looked back at the thread and there were so many messages
that I'm a bit confused.
Do locate tveeprom.ko, then move any it finds to tveeprom.ko.HIDE.
Repeat for tuner and tda9887. Then reboot. Since
I am trying to troubleshoot a new PVR-500 that only works at video1,
while video0 produces black and white static (no audio).
After pursuing numerous leads, I noticed somethin in my log that caught
my eye. I thought I was running version 0.3.8 of the ivtv driver
based on what I had installed
On Sun, 9 Oct 2005, Larry K wrote:
Is something wrong here? Does 0.2.0 in this context mean that I'm not
loading the 0.3.8 driver?
Yes; see the very recent archives for the Cannot install new 0.4.0 ivtv
drivers thread.
Cheers,
Phil
___
ivtv-devel
17 matches
Mail list logo
