Linux

NAVIGATION
CATEGORIES
REFERRENCE
LINKS
  • Up for Grabs: Pinnacle PCTV Pro card

    9 answers - 952 bytes - related search similar search Add To My Delicious Add To My Stumble Upon Add To My Google Mark Add To My Facebook Add To My Digg Add To My Reddit

    Hello all,
    I have a Pinnacle PCTV Pro card (EMPTYV), NTSC version. Card has
    51013170-1.4A on it, with Fusion 878A, an HCF4052i and a TDS988STS chip
    on it. I would add the dmesg output, but I don't seem to have accesst o
    my box at home. I have a remote and serial receiver also. I do not
    have any software, and apparently this Card requires an internal Audio
    card patch cable, which I do not have. I think it might be a CD-RM
    type patch cable, but not 100% sure. I bought this used, w/o the
    missing pieces, and I don't have the time to do anything with it.
    The card seems to capture Video ok, but when I used it bare, it didn't
    capture any sound. I'm not sure if it's a driver issue, if I need the
    internal audio cable, or what.
    So, If anyone knows anything about this card, or needs one to do
    further driver development/expirements, contact me.
    LMK.
    Mark Paulus.
  • No.1 | | 1057 bytes | |

    WW!!!

    This card is so bad that I can't even give it away?!?!?!?

    Mark Paulus wrote:
    Hello all,

    I have a Pinnacle PCTV Pro card (EMPTYV), NTSC version. Card has
    51013170-1.4A on it, with Fusion 878A, an HCF4052i and a TDS988STS chip
    on it. I would add the dmesg output, but I don't seem to have accesst o
    my box at home. I have a remote and serial receiver also. I do not
    have any software, and apparently this Card requires an internal Audio
    card patch cable, which I do not have. I think it might be a CD-RM
    type patch cable, but not 100% sure. I bought this used, w/o the
    missing pieces, and I don't have the time to do anything with it.

    The card seems to capture Video ok, but when I used it bare, it didn't
    capture any sound. I'm not sure if it's a driver issue, if I need the
    internal audio cable, or what.

    So, If anyone knows anything about this card, or needs one to do
    further driver development/expirements, contact me.

    LMK.

    Mark Paulus.
  • No.2 | | 2153 bytes | |

    Hi, Mark,

    Em Qua, 2006-09-06 21:17 -0600, Mark Paulus escreveu:
    WW!!!

    This card is so bad that I can't even give it away?!?!?!?
    No, it is not really a bad card. Probably, for it to output audio, an
    audio cable (the same used on old CD-RMs) is required. This is a very
    cheap and easy to find cable. Most bt8xx devices don't provide digital
    audio.

    I'm not sure about this specific model, but a few Pinnacle boards also
    support digital audio, using an ALSA (snd-bt87x) or SS module
    (btaudio).

    If you don't have interest on this board, for sure you can send it to
    us. We always need newer board types to test improvements and changes at
    main drivers.

    For example, right now, I'm working on redesigning bttv driver, removing
    all V4L1 stuff from it. This means several changes at audio processor
    drivers. Having other boards with different chipsets would help testing.

    You may also help the project by testing our code on your board. The
    experimental new bttv driver, without V4L1 code, is available at:
    http://linuxtv.org/hg/~mchehab/bttv

    Cheers,
    Mauro.

    Mark Paulus wrote:
    Hello all,

    I have a Pinnacle PCTV Pro card (EMPTYV), NTSC version. Card has
    51013170-1.4A on it, with Fusion 878A, an HCF4052i and a TDS988STS chip
    on it.

    I would add the dmesg output, but I don't seem to have accesst o
    my box at home. I have a remote and serial receiver also. I do not
    have any software, and apparently this Card requires an internal Audio
    card patch cable, which I do not have. I think it might be a CD-RM
    type patch cable, but not 100% sure. I bought this used, w/o the
    missing pieces, and I don't have the time to do anything with it.

    The card seems to capture Video ok, but when I used it bare, it didn't
    capture any sound. I'm not sure if it's a driver issue, if I need the
    internal audio cable, or what.

    So, If anyone knows anything about this card, or needs one to do
    further driver development/expirements, contact me.

    LMK.

    Mark Paulus.
  • No.3 | | 7819 bytes | |

    Mauro Carvalho Chehab wrote:
    Hi, Mark,

    Em Qua, 2006-09-06 21:17 -0600, Mark Paulus escreveu:
    >WW!!!
    >>

    >This card is so bad that I can't even give it away?!?!?!?

    No, it is not really a bad card. Probably, for it to output audio, an
    audio cable (the same used on old CD-RMs) is required. This is a very
    cheap and easy to find cable. Most bt8xx devices don't provide digital
    audio.

    I'm not sure about this specific model, but a few Pinnacle boards also
    support digital audio, using an ALSA (snd-bt87x) or SS module
    (btaudio).

    If you don't have interest on this board, for sure you can send it to
    us. We always need newer board types to test improvements and changes at
    main drivers.

    For example, right now, I'm working on redesigning bttv driver, removing
    all V4L1 stuff from it. This means several changes at audio processor
    drivers. Having other boards with different chipsets would help testing.

    You may also help the project by testing our code on your board. The
    experimental new bttv driver, without V4L1 code, is available at:
    http://linuxtv.org/hg/~mchehab/bttv

    Cheers,
    Mauro.

    >Mark Paulus wrote:

    Hello all,

    I have a Pinnacle PCTV Pro card (EMPTYV), NTSC version. Card has
    51013170-1.4A on it, with Fusion 878A, an HCF4052i and a TDS988STS chip
    on it.

    >I would add the dmesg output, but I don't seem to have accesst o

    my box at home. I have a remote and serial receiver also. I do not
    have any software, and apparently this Card requires an internal Audio
    card patch cable, which I do not have. I think it might be a CD-RM
    type patch cable, but not 100% sure. I bought this used, w/o the
    missing pieces, and I don't have the time to do anything with it.

    The card seems to capture Video ok, but when I used it bare, it didn't
    capture any sound. I'm not sure if it's a driver issue, if I need the
    internal audio cable, or what.

    So, If anyone knows anything about this card, or needs one to do
    further driver development/expirements, contact me.

    Mauro,

    I finally have a bit of time, and I have put this card into a "spare"
    machine I can work with. So

    Machine is running Debian Sarge w/ a 2.6.16 kernel from sarge-backports.
    Box has a PVR-150; an Air2PC ATSC card, and this Pinnacle Pro TV card

    I grabbed your experimental new bttv driver, put it into a directory:
    /usr/src/bttv/bttv. ran 'make' & 'make install', and all seemed to go
    good. (attaching build results).

    When booting, or trying to 'modprobe bttv' however, I get a bunch of

    Sep 27 11:14:30 mythtv2 kernel: bttv: disagrees about version of symbol
    videobuf_streamoff
    Sep 27 11:14:30 mythtv2 kernel: bttv: Unknown symbol videobuf_streamoff
    Sep 27 11:14:30 mythtv2 kernel: bttv: disagrees about version of symbol
    videobuf_poll_stream
    Sep 27 11:14:30 mythtv2 kernel: bttv: Unknown symbol videobuf_poll_stream
    Sep 27 11:14:30 mythtv2 kernel: bttv: Unknown symbol ir_codes_avermedia
    Sep 27 11:14:30 mythtv2 kernel: bttv: disagrees about version of symbol
    videobuf_read_stop
    Sep 27 11:14:30 mythtv2 kernel: bttv: Unknown symbol videobuf_read_stop
    Sep 27 11:14:30 mythtv2 kernel: bttv: Unknown symbol ir_codes_apac_viewcomp
    Sep 27 11:14:30 mythtv2 kernel: bttv: Unknown symbol ir_codes_avermedia_dvbt
    Sep 27 11:14:30 mythtv2 kernel: bttv: disagrees about version of symbol
    videobuf_reqbufs
    Sep 27 11:14:30 mythtv2 kernel: bttv: Unknown symbol videobuf_reqbufs
    Sep 27 11:14:30 mythtv2 kernel: bttv: disagrees about version of symbol
    videobuf_waiton
    Sep 27 11:14:30 mythtv2 kernel: bttv: Unknown symbol videobuf_waiton
    Sep 27 11:14:30 mythtv2 kernel: bttv: disagrees about version of symbol
    videobuf_queue_is_busy
    Sep 27 11:14:30 mythtv2 kernel: bttv: Unknown symbol videobuf_queue_is_busy
    Sep 27 11:14:30 mythtv2 kernel: bttv: disagrees about version of symbol
    videobuf_dqbuf
    Sep 27 11:14:30 mythtv2 kernel: bttv: Unknown symbol videobuf_dqbuf
    Sep 27 11:14:30 mythtv2 kernel: bttv: disagrees about version of symbol
    videobuf_queue_init
    Sep 27 11:14:30 mythtv2 kernel: bttv: Unknown symbol videobuf_queue_init
    Sep 27 11:14:30 mythtv2 kernel: bttv: Unknown symbol videobuf_dqbuf
    Sep 27 11:14:30 mythtv2 kernel: bttv: disagrees about version of symbol
    videobuf_queue_init
    Sep 27 11:14:30 mythtv2 kernel: bttv: Unknown symbol videobuf_queue_init
    Sep 27 11:14:30 mythtv2 kernel: bttv: disagrees about version of symbol
    btcx_riscmem_alloc
    Sep 27 11:14:30 mythtv2 kernel: bttv: Unknown symbol btcx_riscmem_alloc
    Sep 27 11:14:30 mythtv2 kernel: bttv: disagrees about version of symbol
    btcx_riscmem_free
    Sep 27 11:14:30 mythtv2 kernel: bttv: Unknown symbol btcx_riscmem_free
    Sep 27 11:14:30 mythtv2 kernel: bttv: Unknown symbol videobuf_dma_unmap
    Sep 27 11:14:30 mythtv2 kernel: bttv: disagrees about version of symbol
    videobuf_read_stream
    Sep 27 11:14:30 mythtv2 kernel: bttv: Unknown symbol videobuf_read_stream
    Sep 27 11:14:30 mythtv2 kernel: bttv: disagrees about version of symbol
    videobuf_querybuf
    Sep 27 11:14:30 mythtv2 kernel: bttv: Unknown symbol videobuf_querybuf
    Sep 27 11:14:30 mythtv2 kernel: bttv: disagrees about version of symbol
    video_unregister_device
    Sep 27 11:14:30 mythtv2 kernel: bttv: Unknown symbol video_unregister_device
    Sep 27 11:14:30 mythtv2 kernel: bttv: disagrees about version of symbol
    videobuf_qbuf
    Sep 27 11:14:30 mythtv2 kernel: bttv: Unknown symbol videobuf_qbuf
    Sep 27 11:14:30 mythtv2 kernel: bttv: disagrees about version of symbol
    video_device_alloc
    Sep 27 11:14:30 mythtv2 kernel: bttv: Unknown symbol video_device_alloc
    Sep 27 11:14:30 mythtv2 kernel: bttv: disagrees about version of symbol
    videobuf_read_one
    Sep 27 11:14:30 mythtv2 kernel: bttv: Unknown symbol videobuf_read_one
    Sep 27 11:14:30 mythtv2 kernel: bttv: disagrees about version of symbol
    video_register_device
    Sep 27 11:14:30 mythtv2 kernel: bttv: Unknown symbol video_register_device
    Sep 27 11:14:30 mythtv2 kernel: bttv: disagrees about version of symbol
    videobuf_iolock
    Sep 27 11:14:30 mythtv2 kernel: bttv: Unknown symbol videobuf_iolock
    Sep 27 11:14:30 mythtv2 kernel: bttv: disagrees about version of symbol
    videobuf_streamon
    Sep 27 11:14:30 mythtv2 kernel: bttv: Unknown symbol videobuf_streamon
    Sep 27 11:14:30 mythtv2 kernel: bttv: disagrees about version of symbol
    videobuf_mmap_setup
    Sep 27 11:14:30 mythtv2 kernel: bttv: Unknown symbol videobuf_mmap_setup
    Sep 27 11:14:30 mythtv2 kernel: bttv: disagrees about version of symbol
    videobuf_next_field
    Sep 27 11:14:30 mythtv2 kernel: bttv: Unknown symbol videobuf_next_field
    Sep 27 11:14:30 mythtv2 kernel: bttv: Unknown symbol ir_codes_nebula
    Sep 27 11:14:30 mythtv2 kernel: bttv: disagrees about version of symbol
    video_device_release
    Sep 27 11:14:30 mythtv2 kernel: bttv: Unknown symbol video_device_release
    Sep 27 11:14:30 mythtv2 kernel: bttv: disagrees about version of symbol
    videobuf_mmap_mapper
    Sep 27 11:14:30 mythtv2 kernel: bttv: Unknown symbol videobuf_mmap_mapper
    Sep 27 11:14:30 mythtv2 kernel: bttv: disagrees about version of symbol
    videobuf_mmap_free
    Sep 27 11:14:30 mythtv2 kernel: bttv: Unknown symbol videobuf_mmap_free

    I'm going to guess that I've done something stupid, but I have no clue
    as to how to determine what the stupid thing was. Any pointers would be
    appreciated.

    Thanks.
  • No.4 | | 812 bytes | |

    Em Qua, 2006-09-27 11:18 -0600, Mark Paulus escreveu:

    When booting, or trying to 'modprobe bttv' however, I get a bunch of

    Sep 27 11:14:30 mythtv2 kernel: bttv: disagrees about version of symbol
    videobuf_streamoff

    I'm going to guess that I've done something stupid, but I have no clue
    as to how to determine what the stupid thing was. Any pointers would be
    appreciated.

    Quite simple: you have a previous version of videodev loaded when you
    tried to insert bttv. You may solve this by:

    make rmmod (it will do rmmod for all newly created modules)

    if you want to make sure you don't have any obsoleted modules on your
    kernel installation, you may also do:

    make rminstall
    make install

    Thanks.

    Cheers,
    Mauro.
  • No.5 | | 2000 bytes | |

    Mauro Carvalho Chehab wrote:
    Em Qua, 2006-09-27 11:18 -0600, Mark Paulus escreveu:

    >When booting, or trying to 'modprobe bttv' however, I get a bunch of
    >>

    >Sep 27 11:14:30 mythtv2 kernel: bttv: disagrees about version of symbol
    >videobuf_streamoff


    >I'm going to guess that I've done something stupid, but I have no clue
    >as to how to determine what the stupid thing was. Any pointers would be
    >appreciated.


    Quite simple: you have a previous version of videodev loaded when you
    tried to insert bttv. You may solve this by:

    make rmmod (it will do rmmod for all newly created modules)

    if you want to make sure you don't have any obsoleted modules on your
    kernel installation, you may also do:

    make rminstall
    make install

    >Thanks.
    >>

    Cheers,
    Mauro.

    Well, that fixed a couple of things, but some things are still broke
    (namely, now I get the disagrees/unknown symbol problems with ivtv 0.6.3
    driver for my PVR-150. I've attached dmesg output.

    I will play around with some tools with this new driver, and then I will
    probably have a question on what do I need to define in Mythtv-0.19 in
    order to get the card recognized with new driver module.

    Another couple of questions. Are there any kind of testing/diagnostic
    tools available for these v4l2 devices? I have ivtvctl for my ivtv
    devices, and I have scan/dvbsnoop/azap for my air2pc ATSC card. What do
    I have that is analogous in v4l2 land? v4lctl complains about no
    /dev/dvi devices.

    Is there supposed to be sound with your new driver? I just ran v4l-info
    and saw this:
    audio
    ioctl VIDICGAUDI: Invalid argument
    and I don't see any /dev/dsp* devices.

    That should be yet again enough for one night.
  • No.6 | | 1594 bytes | |

    Em Qui, 2006-09-28 12:13 -0600, Mark Paulus escreveu:

    Mauro Carvalho Chehab wrote:
    Em Qua, 2006-09-27 11:18 -0600, Mark Paulus escreveu:

    Well, that fixed a couple of things, but some things are still broke
    (namely, now I get the disagrees/unknown symbol problems with ivtv 0.6.3
    driver for my PVR-150. I've attached dmesg output.
    You need to recompile ivtv. The easiest way for doing:

    make ivtv
    make
    make install

    I will play around with some tools with this new driver, and then I will
    probably have a question on what do I need to define in Mythtv-0.19 in
    order to get the card recognized with new driver module.
    Mythtv does support analog boards (although I've no luck making it
    working here). I use instead tvtime or xawtv.

    Another couple of questions. Are there any kind of testing/diagnostic
    tools available for these v4l2 devices? I have ivtvctl for my ivtv
    devices, and I have scan/dvbsnoop/azap for my air2pc ATSC card. What do
    I have that is analogous in v4l2 land? v4lctl complains about no
    /dev/dvi devices.
    There are some nice tools at v4l2-apps/ dir (a variant of itvtctl,
    called v4l2-ctl). v4l-ctl should work fine also.

    Is there supposed to be sound with your new driver? I just ran v4l-info
    and saw this:
    audio
    ioctl VIDICGAUDI: Invalid argument
    and I don't see any /dev/dsp* devices.

    That should be yet again enough for one night.
    Can you post your dmesg after you modprobe bttv? It will depend on your
    exact device model.

    Cheers,
    Mauro.
  • No.7 | | 8810 bytes | |

    Mauro Carvalho Chehab wrote:
    Em Qui, 2006-09-28 12:13 -0600, Mark Paulus escreveu:
    >Mauro Carvalho Chehab wrote:

    Em Qua, 2006-09-27 11:18 -0600, Mark Paulus escreveu:

    >Well, that fixed a couple of things, but some things are still broke
    >(namely, now I get the disagrees/unknown symbol problems with ivtv 0.6.3
    >driver for my PVR-150. I've attached dmesg output.

    You need to recompile ivtv. The easiest way for doing:

    make ivtv

    Explain this please? I understand the two following statements, but
    this one is cryptic to me.

    make
    make install

    I just tried these 2 in my ivtv0.6.3 source tree, and I am still getting
    Unknown/disagree errors. So, something isn't happy somewhere


    >I will play around with some tools with this new driver, and then I will
    >probably have a question on what do I need to define in Mythtv-0.19 in
    >order to get the card recognized with new driver module.

    Mythtv does support analog boards (although I've no luck making it
    working here). I use instead tvtime or xawtv.

    Mythtv was recognizing the card, and was doing video. The problem is
    (the thing that started this whole mess) getting "integrated" audio out
    and then telling Mythtv where to go look for it. having a different
    driver type for Mythtv that doesn't prompt for an Audio Device
    (something similar to a Hauppauge PVR-150/250/350/500 perhaps).

    >Another couple of questions. Are there any kind of testing/diagnostic
    >tools available for these v4l2 devices? I have ivtvctl for my ivtv
    >devices, and I have scan/dvbsnoop/azap for my air2pc ATSC card. What do
    >I have that is analogous in v4l2 land? v4lctl complains about no
    >/dev/dvi devices.

    There are some nice tools at v4l2-apps/ dir (a variant of itvtctl,
    called v4l2-ctl). v4l-ctl should work fine also.
    >Is there supposed to be sound with your new driver? I just ran v4l-info
    >and saw this:
    >audio
    >ioctl VIDICGAUDI: Invalid argument
    >and I don't see any /dev/dsp* devices.
    >>

    >That should be yet again enough for one night.

    Can you post your dmesg after you modprobe bttv? It will depend on your
    exact device model.
    ivtv: disagrees about version of symbol video_unregister_device
    ivtv: Unknown symbol video_unregister_device
    ivtv: disagrees about version of symbol video_device_alloc
    ivtv: Unknown symbol video_device_alloc
    ivtv: disagrees about version of symbol video_register_device
    ivtv: Unknown symbol video_register_device
    ivtv: disagrees about version of symbol video_device_release
    ivtv: Unknown symbol video_device_release
    bttv: disagrees about version of symbol videobuf_streamoff
    bttv: Unknown symbol videobuf_streamoff
    bttv: disagrees about version of symbol videobuf_poll_stream
    bttv: Unknown symbol videobuf_poll_stream
    bttv: disagrees about version of symbol videobuf_read_stop
    bttv: Unknown symbol videobuf_read_stop
    bttv: Unknown symbol videobuf_dma_pci_unmap
    bttv: disagrees about version of symbol videobuf_reqbufs
    bttv: Unknown symbol videobuf_reqbufs
    bttv: disagrees about version of symbol videobuf_waiton
    bttv: Unknown symbol videobuf_waiton
    bttv: disagrees about version of symbol videobuf_queue_is_busy
    bttv: Unknown symbol videobuf_queue_is_busy
    bttv: disagrees about version of symbol videobuf_dqbuf
    bttv: Unknown symbol videobuf_dqbuf
    bttv: disagrees about version of symbol videobuf_queue_init
    bttv: Unknown symbol videobuf_queue_init
    bttv: disagrees about version of symbol btcx_riscmem_alloc
    bttv: Unknown symbol btcx_riscmem_alloc
    bttv: disagrees about version of symbol btcx_riscmem_free
    bttv: Unknown symbol btcx_riscmem_free
    bttv: disagrees about version of symbol videobuf_read_stream
    bttv: Unknown symbol videobuf_read_stream
    bttv: disagrees about version of symbol videobuf_querybuf
    bttv: Unknown symbol videobuf_querybuf
    bttv: Unknown symbol videobuf_dma_pci_sync
    bttv: disagrees about version of symbol video_unregister_device
    bttv: Unknown symbol video_unregister_device
    bttv: disagrees about version of symbol videobuf_qbuf
    bttv: Unknown symbol videobuf_qbuf
    bttv: disagrees about version of symbol video_device_alloc
    bttv: Unknown symbol video_device_alloc
    bttv: disagrees about version of symbol videobuf_read_one
    bttv: Unknown symbol videobuf_read_one
    bttv: disagrees about version of symbol video_register_device
    bttv: Unknown symbol video_register_device
    bttv: disagrees about version of symbol videobuf_iolock
    bttv: Unknown symbol videobuf_iolock
    bttv: disagrees about version of symbol videobuf_streamon
    bttv: Unknown symbol videobuf_streamon
    bttv: disagrees about version of symbol videobuf_mmap_setup
    bttv: Unknown symbol videobuf_mmap_setup
    bttv: disagrees about version of symbol videobuf_next_field
    bttv: Unknown symbol videobuf_next_field
    bttv: disagrees about version of symbol video_device_release
    bttv: Unknown symbol video_device_release
    bttv: disagrees about version of symbol videobuf_mmap_mapper
    bttv: Unknown symbol videobuf_mmap_mapper
    bttv: disagrees about version of symbol videobuf_mmap_free
    bttv: Unknown symbol videobuf_mmap_free
    bttv: driver version 0.9.16 loaded
    bttv: using 8 buffers with 2080k (520 pages) each for capture
    bt878: Unknown symbol bttv_read_gpio
    bt878: Unknown symbol bttv_write_gpio
    bt878: Unknown symbol bttv_gpio_enable
    Intel 810 + AC97 Audio, version 1.01, 02:37:25 Jul 16 2006
    b2c2-flexcop: i2c master_xfer failed
    b2c2-flexcop: i2c master_xfer failed
    nxt200x: nxt200x_readbytes: i2c read error (addr 0x0a, err == -121)
    Unknown/Unsupported NXT chip: 00 00 00 00 00
    b2c2-flexcop: i2c master_xfer failed
    lgdt330x: i2c_read_demod_bytes: addr 0x59 select 0x02 error (ret == -121)
    bcm3510: Revision: 0x1, Layer: 0xb.
    b2c2-flexcop: found the bcm3510 at i2c address: 0x0f
    DVB: registering frontend 0 (Broadcom BCM3510 VSB/QAM frontend)
    b2c2-flexcop: initialization of 'Air2PC/AirStar 2 ATSC 1st generation'
    at the 'PCI' bus controlled by a 'FlexCopIIb' complete
    bttv: Bt8xx card found (0).
    ACPI: PCI Interrupt Link [APC2] enabled at IRQ 17
    ACPI: PCI Interrupt 0000:01:09.0[A] -Link [APC2] -GSI 17 (level,
    high) -IRQ 209
    bttv0: Bt878 (rev 17) at 0000:01:09.0, irq: 209, latency: 32, mmio:
    0xe4000000
    bttv0: detected: Pinnacle PCTV [card=39], PCI subsystem ID is 11bd:0012
    bttv0: using: Pinnacle PCTV Studio/Rave [card=39,autodetected]
    bttv0: gpio: en=00000000, out=00000000 in=00ffefff [init]
    bttv0: i2c: checking for MSP34xx @ 0x80 not found
    bttv0: pinnacle/mt: id=5 info="NTSC / mono" radio=no
    bttv0: using tuner=33
    bttv0: i2c: checking for MSP34xx @ 0x80 not found
    bttv0: i2c: checking for TDA9875 @ 0xb0 not found
    bttv0: i2c: checking for TDA7432 @ 0x8a not found
    tuner 3-0043: chip found @ 0x86 (bt878 #0 [sw])
    tda9887 3-0043: tda988[5/6/7] found @ 0x43 (tuner)
    tuner 3-0060: Chip ID is not zero. It is not a TEA5767
    tuner 3-0060: chip found @ 0xc0 (bt878 #0 [sw])
    tuner 3-0060: microtune: companycode=4d54 part=04 rev=04
    tuner 3-0060: microtune MT2032 found, K
    bttv0: registered device video0
    bttv0: registered device vbi0
    bttv0: PLL: 28636363 =35468950 ok

    # ./v4l2-ctl
    Driver info:
    Driver name : bttv
    Card type : BT878 video (Pinnacle PCTV Stud
    Bus info : PCI:0000:01:09.0
    Driver version: 2320
    Capabilities : 0x05010015
    Video Capture
    Video
    VBI Capture
    Tuner
    Read/Write
    Streaming
    Format:
    Type : Video Capture
    Width/Height : 320/240
    Pixel Format : BGR3
    Field : Interlaced
    Bytes per Line: 960
    Size Image : 230400
    Colorspace : Unknown (00000000)
    Format:
    Type : Video
    Left/Top : 0/0
    Width/Height: 320/240
    Field : Any
    Chroma Key : 00000000
    Clip Count : 0
    Format:
    Type : VBI Capture
    Sampling Rate : 28636363 Hz
    : 244 samples (8.52064e-06 secs after leading edge)
    Samples per Line: 2048
    Sample Format : GREY
    Start 1st Field : 10
    Count 1st Field : 16
    Start 2nd Field : 273
    Count 2nd Field : 16
    Video input : 0 (Television)
    Frequency: 0 (0.000000 MHz)
    Video standard = 0x00009000
    NTSC-M/M-KR
    Tuner:
    Capabilities : 62.5 kHz multi-standard
    Frequency range : 44.0 MHz - 958.0 MHz
    Signal strength : 0%
    Current audio mode : mono
    Available subchannels: mono

    Cheers,
    Mauro.
  • No.8 | | 3059 bytes | |

    Em Ter, 2006-10-03 14:28 -0600, Mark Paulus escreveu:

    Mauro Carvalho Chehab wrote:
    Em Qui, 2006-09-28 12:13 -0600, Mark Paulus escreveu:
    >Mauro Carvalho Chehab wrote:

    Em Qua, 2006-09-27 11:18 -0600, Mark Paulus escreveu:

    >Well, that fixed a couple of things, but some things are still broke
    >(namely, now I get the disagrees/unknown symbol problems with ivtv 0.6.3
    >driver for my PVR-150. I've attached dmesg output.

    You need to recompile ivtv. The easiest way for doing:

    make ivtv

    Explain this please?
    make help will explain it ;)

    ivtv - enable merged ivtv build, using the latest ivtv sources
    from ivtvdriver.org (requires subversion)

    It will basically use svn to download ivtv and proper link it into hg
    tree.

    >I will play around with some tools with this new driver, and then I will
    >probably have a question on what do I need to define in Mythtv-0.19 in
    >order to get the card recognized with new driver module.

    Mythtv does support analog boards (although I've no luck making it
    working here). I use instead tvtime or xawtv.

    Mythtv was recognizing the card, and was doing video. The problem is
    (the thing that started this whole mess) getting "integrated" audio out
    and then telling Mythtv where to go look for it. having a different
    driver type for Mythtv that doesn't prompt for an Audio Device
    (something similar to a Hauppauge PVR-150/250/350/500 perhaps).
    Mythtv never worked for me. I had to confess that I'm a bit lazy with
    userspace apps - anything that took me more than 5 min to install, it is
    poorly documented and have some weird dependencies is something I'm not
    like to use ;)

    So I can't help on this issue.

    >Another couple of questions. Are there any kind of testing/diagnostic
    >tools available for these v4l2 devices? I have ivtvctl for my ivtv
    >devices, and I have scan/dvbsnoop/azap for my air2pc ATSC card. What do
    >I have that is analogous in v4l2 land? v4lctl complains about no
    >/dev/dvi devices.

    There are some nice tools at v4l2-apps/ dir (a variant of itvtctl,
    called v4l2-ctl). v4l-ctl should work fine also.
    >Is there supposed to be sound with your new driver? I just ran v4l-info
    >and saw this:
    >audio
    >ioctl VIDICGAUDI: Invalid argument
    >and I don't see any /dev/dsp* devices.
    >>

    >That should be yet again enough for one night.

    Can you post your dmesg after you modprobe bttv? It will depend on your
    exact device model.
    ivtv: disagrees about version of symbol video_unregister_device
    ivtv: Unknown symbol video_unregister_device
    Those messages just shows that you've compiled ivtv with older v4l core
    stuff. It will work only after you do "make ivtv".

    Cheers,
    Mauro.
  • No.9 | | 1761 bytes | |

    Mauro Carvalho Chehab wrote:
    make help will explain it ;)

    ivtv - enable merged ivtv build, using the latest ivtv sources
    from ivtvdriver.org (requires subversion)

    It will basically use svn to download ivtv and proper link it into hg
    tree.

    Cheers,
    Mauro.

    , did that, and guess what?

    Still having problems

    First off, I am using a 2.6.16-2-k7 Debianized kernel, provided by
    www.backports.org. That all has been working fine.

    When I do
    make ivtv
    make

    I get a failure: Can't determine how to make prerequisite ivtv-reset.s
    required by ivtv-reset.o.

    , go in and fix Makefile.ivtv and remove ivtv-reset.o, since it no
    longer seems to be in the trunk for ivtv.
    Now when I build, I get:
    / In function `ivtv_v4l2_ioctls':
    / error: structure has no member
    named `type'
    / error: structure has no member
    named `type'
    make[3]: [/] Error 1

    I also thought maybe I was having some troubles, since I'm using a
    2.6.16 kernel, which means that I should be using a 0.6 ivtv driver.
    So, I update v4l/Makefile to pull from
    svn co ivtv;
    However, that seems to have other conflicts with your driver stuff:
    / In function
    `ivtv_set_audio_for_msp34xx':
    / error: storage size of `mspm'
    isn't known
    / error: `MSP_SET_MATRIX'
    undeclared (first use in this function)
    / error: (Each undeclared
    identifier is reported only once
    / error: for each function it
    appears in.)

    / warning: unused variable `mspm'
    / In function `ivtv_audio_set_matrix':
    / error: `MSP_SET_MATRIX'
    undeclared (first use in this function)
    make[2]: [/] Error 1

    Any other advice?

Re: Up for Grabs: Pinnacle PCTV Pro card


max 4000 letters.
Your nickname that display:
In order to stop the spam: 8 + 7 =
QUESTION ON "Linux"

EMSDN.COM