On Thursday 30 November 2006 19:45, Trev Jackson wrote:
> Hi,
>
> I don't have a new enough kernel to run 0.8.1. however I downloaded
> it and the cs53l32a module which is required by the avc2410 doesn't
> appear to be there. cs53l32a was transfered to the v4l project, so I
> don't know if it is included somewhere in later distros, ivtv should
> automatically load the module and the module sets the audio sample
> rate to the correct speed.
>
> Part of the dmesg output should include the CS53L32A module giving
> something similar to the following:
>
> cs53l32a: Ignoring new-style parameters in presence of obsolete ones
> cs53l32a 0-0011: ivtv driver
> cs53l32a 0-0011: chip found @ 0x22 (ivtv i2c driver #0)
>
> Perhaps you need to install v4l to get the cs53l32a module
cs53132a is part of the kernel since 2.6.16. But the module may not be
enabled in the kernel. See also note 3 in the ivtv README.
Hans
>
> Best Regards
>
> Trev
>
> On Thursday 30 November 2006 17:34, Kipp Cannon wrote:
> > Hi Trev,
> >
> > Thanks for the quick reply! OK, here goes, output of dmesg
> > following "modprobe ivtv"
> >
> > ivtv: ==================== START INIT IVTV ====================
> > ivtv: version 0.8.1 (tagged release) loading
> > ivtv: Linux version: 2.6.18.3 preempt mod_unload gcc-4.1
> > ivtv: In case of problems please include the debug info between
> > ivtv: the START INIT IVTV and END INIT IVTV lines, along with
> > ivtv: any module options, when mailing the ivtv-users mailinglist.
> > ivtv0: Autodetected Adaptec VideOh! AVC-2410 card (cx23416 based)
> > PCI: Enabling device 0000:00:0e.0 (0110 -> 0112)
> > ACPI: PCI Interrupt 0000:00:0e.0[A] -> GSI 19 (level, low) -> IRQ
> > 201 ivtv0: loaded v4l-cx2341x-enc.fw firmware (262144 bytes)
> > tuner 0-0043: chip found @ 0x86 (ivtv i2c driver #0)
> > tda9887 0-0043: tda988[5/6/7] found @ 0x43 (tuner)
> > tuner 0-0060: All bytes are equal. It is not a TEA5767
> > tuner 0-0060: chip found @ 0xc0 (ivtv i2c driver #0)
> > tuner 0-006b: chip found @ 0xd6 (ivtv i2c driver #0)
> > saa7115 0-0021: saa7115 found @ 0x42 (ivtv i2c driver #0)
> > msp3400 0-0040: MSP3425G-B8 found @ 0x80 (ivtv i2c driver #0)
> > msp3400 0-0040: MSP3425G-B8 supports radio, mode is autodetect and
> > autoselect ivtv0: Encoder revision: 0x02050032
> > ivtv0: Registered device video0 for encoder MPEG
> > ivtv0: Registered device video32 for encoder YUV
> > ivtv0: Registered device vbi0 for encoder VBI
> > ivtv0: Registered device video24 for encoder PCM audio
> > tuner 0-0060: type set to 43 (Philips NTSC MK3 (FM1236MK3 or
> > FM1236/F)) ivtv0: i2c hardware 0x00000040 (cs53l32a) not found for
> > command 0x4008646d! ivtv0: Initialized Adaptec VideOh! AVC-2410,
> > card #0
> > ivtv: ==================== END INIT IVTV ====================
> >
> >
> > My first attempt at all of this was using firmware files from the
> > latest driver available from Adaptec's website, and I got the same
> > "slow motion recording" behaviour. Those firmware files, though,
> > caused the ivtv driver to emit a warning about the firmware version
> > being not equal to known-good versions, so I tried with the
> > firmware available from the ivtv wiki pages, and the change had no
> > effect. The demo recording was made with firmware downloaded from
> > the ivtv wiki pages. I don't set any options for any of the
> > modules.
> >
> > -Kipp
> >
> > On Thu, 30 Nov 2006, Trev Jackson wrote:
> > > Hi Kipp
> > >
> > > It looks like you either have the ivtv driver set up for the
> > > wrong card type, or you are using an early version of ivtv.
> > >
> > > The avc-2410 is slightly different from the hauppauge cards in
> > > that it needs the speed that audio is captured at setting up and
> > > this should work in the current version of ivtv.
> > >
> > > If you email to the list a copy of the dmesg output after you
> > > have loaded the ivtv driver I should be able to help you more.
> > >
> > > Best Regards
> > >
> > > Trev Jackson
> > >
> > > On Thursday 30 November 2006 16:43, Kipp Cannon wrote:
> > >> Hi,
> > >>
> > >> I have an AVC-2410, and I can't get it to produce a sensible
> > >> recording. An example can be found at
> > >>
> > >> http://www.lsc-group.phys.uwm.edu/~kipp/test.mpg
> > >>
> > >> The file is ~10 MB, 10 seconds, and was obtained by
> > >>
> > >> $ cat /dev/video0 >test.mpg
> > >>
> > >> The recording is too slow, as though the data (video frames and
> > >> audio) were captured with a sample clock that was running too
> > >> fast. Is this a problem people have seen before? Anybody know
> > >> how to fix it?
> > >>
> > >> I have another question: has anybody had success getting
> > >> transcode to read directly from an IVTV /dev/video0 device?
> > >> Nothing I've tried will make it work, I get error messages about
> > >> invalid ioctl()s and so on. Any working example at all would be
> > >> helpful. I have had no problem with a BT878-based card.
> > >>
> > >> -Kipp
> > >>
> > >> _______________________________________________
> > >> ivtv-users mailing list
> > >> [email protected]
> > >> http://ivtvdriver.org/mailman/listinfo/ivtv-users
> > >
> > > _______________________________________________
> > > ivtv-users mailing list
> > > [email protected]
> > > http://ivtvdriver.org/mailman/listinfo/ivtv-users
> >
> > _______________________________________________
> > ivtv-users mailing list
> > [email protected]
> > http://ivtvdriver.org/mailman/listinfo/ivtv-users
>
> _______________________________________________
> ivtv-users mailing list
> [email protected]
> http://ivtvdriver.org/mailman/listinfo/ivtv-users
_______________________________________________
ivtv-users mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-users
