Tyler Trafford wrote:
Yeah, it should work. Make sure you use the parameter cardtype=1 for
the cx25840 module. Post logs for more specific help.
That's interesting. I finally got a channel to tune in by setting
cardtype=2
Does this mean I have an older driver installed?
--
Drew Lane wrote:
> I've been trying to get MythTV going on with my Diamond
> XtremeTV PVR-550 PCI card, but no luck yet.
>
> Is this card supported?
Yeah, it should work. Make sure you use the parameter cardtype=1 for
the cx25840 module. Post logs for more specific help.
--
Tyler Trafford
-
I've been trying to get MythTV going on with my Diamond
XtremeTV PVR-550 PCI card, but no luck yet.
Is this card supported?
The chipset on the PCI card shows:
Conexant MPEG II A/V
CX23416-12
0428Y1CV
0429 TAIWAN
Thanks!
---
SF.Net email is
I run Gentoo as well, and I think I was getting those FBxxx errors as
well when I was using the version of ivtv in portage, however it never
prevented my system from working.
You might want to look elsewhere for the problem at hand. Are you sure
you're sending the signal out the correct port?
> IANAE and I also use FC3 not gentoo, but it looks to me that you have
> kernel 2.4 modprobe settings for a 2.6 kernel.
>
> My modprobe is as follows (It's the 2nd to last line that leads me to
> my observation)
> alias char-major-81 videodev
> alias char-major-81-0 ivtv
> alias tveeprom tveeprom
On 7/5/05, Matt Salerno <[EMAIL PROTECTED]> wrote:
> Gentoo 2005.1
> Xorg 6.8.2-r1
> ivtv: version 0.2.0 (rc3j)
>
> I have read just about every howto I could find, but I cannot get X
> out though the pvr-350. I have used the supplied X driver from the
> source, I have compiled my own X driver, w
Gentoo 2005.1
Xorg 6.8.2-r1
ivtv: version 0.2.0 (rc3j)
I have read just about every howto I could find, but I cannot get X
out though the pvr-350. I have used the supplied X driver from the
source, I have compiled my own X driver, with video=vc:64-64 appended
to my kernel parameters and without,
Sorry I've been so MIA, I've had a lot of work to do recently.
Tyler Trafford wrote:
No, it does- but that magic is just a manual write to the tda9887, and
Bryan intended that patch to be a test to see if that really was the
source of your problem.
The black magic patch sets up the tda98
I had a similar issue with my PVR 250 after issuing an errant ivtvctl command.
The PVR 350
installed in the same computer worked fine and nothing else had changed. I
believe I tried
switching to a non-existant input on the PVR 250 using ivtvctl and that may
have caused my
problem. Afterwar
Hi,
Tyler Trafford wrote:
Morten Rønseth wrote:
Tyler Trafford wrote:
Erm, doesn't loading tda9887 with "port1=0 port2=0" do the same thing
as the "black magic"?
I wouldn't know. I was under the impression that Bryan's patch
re-introduced the black magic that was removed in s
yeah i've read the past posts and the wiki, mainly just trying to avoid
any limitations or stability issues that might still be there. i had a
350 in the past but got rid of it before this functionality in the
driver was available.
oh well, it's only money ;). i'll be ordering up a new 350 t
I haven't got sound on the 500 tuners with ivtv-0.3.6x - I have also
tried loading tda9887 with '/sbin/modprobe tda9887 port1=0 port2=0'
The latest good one is ivtv-0.3.6u
Anybody noticing anything obvious from the log?
Regards
Sigurd
Jul 5 20:12:18 localhost kernel: ivtv: ===
Morten Rønseth wrote:
> Tyler Trafford wrote:
>
>> Erm, doesn't loading tda9887 with "port1=0 port2=0" do the same thing
>> as the "black magic"?
>
> I wouldn't know. I was under the impression that Bryan's patch
> re-introduced the black magic that was removed in some 0.3.5 version. But
> ma
Hi,
Tyler Trafford wrote:
Morten Rønseth wrote:
Jasper van der Neut - Stulen wrote:
/sbin/modprobe tda9887 port1=0 port2=0
/sbin/modprobe ivtv tda9887=0
I will try it when I get home, the patch you're using is the
't
On Tue, Jul 05, 2005 at 01:20:40PM -0400, Tyler Trafford wrote:
> Morten R?nseth wrote:
> > Jasper van der Neut - Stulen wrote:
>
> >>> /sbin/modprobe tda9887 port1=0 port2=0
> >>> /sbin/modprobe ivtv tda9887=0
>
> >> I will try it when I get home, the patch you're using is the
> >> 'tda9887-me
Morten Rønseth wrote:
> Jasper van der Neut - Stulen wrote:
>>> /sbin/modprobe tda9887 port1=0 port2=0
>>> /sbin/modprobe ivtv tda9887=0
>> I will try it when I get home, the patch you're using is the
>> 'tda9887-merge-modparms3.diff' ?
>
> No - it's the one re-introducing black magic...:-) S
Hi,
Jasper van der Neut - Stulen wrote:
On Tue, Jul 05, 2005 at 03:04:07PM +0200, Morten R?nseth wrote:
Hi
I had the same issue - it turned out that preinstalled Mandrake 10.1
modules were getting in the way (tda9887 specifically), along with some
quirks in the cx25840 modul
I have been having a problem with jumpy video and audio ever since I
wiped my box a while back. I am using a PVR-250 I have had for a
couple years now. I had
FC3 running fine with Mythtv and had to wipe the box for other
reasons. After the wipe, the video was jumpy. It didn't matter if I
tried
Chera Bekker <[EMAIL PROTECTED]> wrote:
> Hi list,
>
> I have a wintv pvr150 working perfectly with the ivtv 0.3.6(p) drivers.
> When I replace the pvr150 with a pvr150mce I only get static with mythtv
> (or mplayer). What exactly are the differences. Should I use a different
> firmware? Are there
On 7/5/05, Jasper van der Neut - Stulen <[EMAIL PROTECTED]> wrote:
> On Tue, Jul 05, 2005 at 03:04:07PM +0200, Morten R?nseth wrote:
> > Hi
> >
> > >
> > I had the same issue - it turned out that preinstalled Mandrake 10.1
> > modules were getting in the way (tda9887 specifically), along with some
On Tue, Jul 05, 2005 at 03:04:07PM +0200, Morten R?nseth wrote:
> Hi
>
> >
> I had the same issue - it turned out that preinstalled Mandrake 10.1
> modules were getting in the way (tda9887 specifically), along with some
> quirks in the cx25840 module (fixed thanks to Bryan Mayland). I now
> pat
Hi
Jasper van der Neut - Stulen wrote:
On Tue, Jul 05, 2005 at 01:05:54PM +0200, Chera Bekker wrote:
Hi list,
I have a wintv pvr150 working perfectly with the ivtv 0.3.6(p) drivers.
When I replace the pvr150 with a pvr150mce I only get static with mythtv
(or mplayer). What exactly are the
On Tue, Jul 05, 2005 at 01:05:54PM +0200, Chera Bekker wrote:
> Hi list,
>
> I have a wintv pvr150 working perfectly with the ivtv 0.3.6(p) drivers.
> When I replace the pvr150 with a pvr150mce I only get static with mythtv
> (or mplayer). What exactly are the differences. Should I use a differe
Brian Keener wrote:
Morten Rønseth wrote:
Hi,
Brian Keener wrote:
Morten Rønseth wrote:
Hi,
Milos Prudek wrote:
I ve had this problem at the start and that 's what solve it...
don't remember where i get the info, it was on janury that i have
the problem... i ve removed 4STACKS too..
Morten Rønseth wrote:
Hi,
Brian Keener wrote:
Morten Rønseth wrote:
Hi,
Milos Prudek wrote:
I ve had this problem at the start and that 's what solve it...
don't remember where i get the info, it was on janury that i have
the problem... i ve removed 4STACKS too...
you ll have just to tr
Hi list,
I have a wintv pvr150 working perfectly with the ivtv 0.3.6(p) drivers.
When I replace the pvr150 with a pvr150mce I only get static with mythtv
(or mplayer). What exactly are the differences. Should I use a different
firmware? Are there any specific module parameters I should try?
Hi,
This is from the ivtvctl help printout:
[snip]
-K, --passthrough=
set passthrough mode: 1 = on, 0 = off
[IVTV_IOC_PASSTHROUGH]
[/snip]
I have not tried this myself as I do not watch live TV on the MythTV
box, but it may work. It is in the MythTV wiki too..
/Fredrik
On
27 matches
Mail list logo
