On Monday 21 November 2005 01:21, Rod wrote:
> No response so I am reposting.
Sorry, was busy with other things.
> On Tue, Nov 15, 2005 at 08:13:43AM +0100, Hans Verkuil wrote:
> > On Tuesday 15 November 2005 06:41, Rod wrote:
> > > On Sun, Nov 13, 2005 at 10:10:16AM +0100, Hans Verkuil wrote:
> > > > On Sunday 13 November 2005 05:09, Rod wrote:
> > > > > Greetings,
> > > > >
> > > > > I didn't get any response from ivtv-users so I'm hoping that
> > > > > there may be an answer here. I am at the end of my rope
> > > > > having gone over all the documentation, FAQ's and lists.
> > > > >
> > > > > I am having trouble configuring sound with a dual input
> > > > > setup.
> > > > >
> > > > > I have installed a PVR-250 and PVR-350 individually and they
> > > > > both work fine by themselves. When I put both cards in at
> > > > > the same time, I lose sound on the PVR-250.
> > > > >
> > > > > I am using ivtvdriver 0.4.0 and have been following Jarrod's
> > > > > instructions. I am using Fedora Core 4
> > > > >
> > > > > Here is my lspci -v output for the cards and sound
> > > >
> > > > <snip>
> > > >
> > > > > Any direction on where I go from here would be greatly
> > > > > appreciated.
> > > >
> > > > I'd recommend trying ivtv-0.5.0 first: it replaces the msp3400
> > > > driver with a newer version from v4l. You should remove these
> > > > lines:
> > > >
> > > > alias tveeprom tveeprom-ivtv
> > > > alias tuner tuner-ivtv
> > > > alias tda9887 tda9887-ivtv
> > > > alias msp3400 msp3400-ivtv
> > > >
> > > > and also make sure all ivtv versions of these modules are
> > > > removed (or it will pick up the wrong one).
> > >
> > > Here is the debug info with 0.5.0. PVR350 gives sound, PVR-250
> > > still does not.
> > >
> > > Nov 14 23:31:48 mythbox kernel:
> > > ivtv: ==================== START INIT IVTV ====================
> > > Nov 14 23:31:48 mythbox kernel: ivtv: version 0.4.0 (tagged
> > > release)
> >
> > loading
> >
> > Still 0.4.0, not 0.5.0.
>
> Sorry, missed that. OK, you are going to have to forgive my
> ignorance here. I am trying to follow the instructions in ivtv-0.5.0
> and don't know what to expect. If I read
>
> README.1ST
>
> Snip>>>
>
> "The next step is to build ivtv as usual."
>
> I am assuming this just means doing a "make && make install" in the
> top level directory of the ivtv-0.5.0 source.
Correct.
> Is there something else I am missing here?
>
> "IMPORTANT: the firmware names have been changed to more standardized
> names:"
>
> Is there something implicit in this statement that I need to be aware
> of?
You probably have to copy (and rename) the files from /lib/modules to
the hotplug firmware directory. The location can be found in the
file /etc/hotplug/firmware.agent (from memory, it may be located
somewhere else in /etc).
>
> "modinfo ivtv" now indicates 0.5.0
>
> "/sbin/modprobe ivtv" returns
>
> FATAL: Error inserting ivtv
> (/lib/modules/2.6.13-1.1532_FC4/ivtv/ivtv.ko): Unknown symbol in
> module, or unknown parameter (see dmesg)
>
> dmesg
>
> Snipp>>>
>
> ivtv: disagrees about version of symbol tveeprom_hauppauge_analog
> ivtv: Unknown symbol tveeprom_hauppauge_analog
> ivtv: disagrees about version of symbol tveeprom_hauppauge_analog
> ivtv: Unknown symbol tveeprom_hauppauge_analog
>
> What to do here?
Are you very sure you no longer have an old tveeprom floating around
in /lib/modules? Almost certainly this is the case and the old tveeprom
(without the tveeprom_hauppauge_analog symbol) is picked up.
>
> > > Nov 14 23:31:48 mythbox kernel: msp34xx: ivtv version
> >
> > Still the msp3400 from ivtv, you shouldn't see this specific
> > message anymore.
> >
> > > ### modprobe.conf file
> > >
> > > options ivtv debug=16
> >
> > ^^^^^^^^^^^^^^
> >
> > Should be options msp3400 debug=16
>
> OK but I need to get 0.5.0 going first.
>
> I appreciate your patience.
That's OK. Don't hesitate to repost (as you did) if you didn't see a
reply after a few days. Sometimes I loose track if there are many posts
or I am busy with other things.
Hans
_______________________________________________
ivtv-devel mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-devel
