Re: [Alsa-user] FC3 alsa problems

[Gianluca C. <gia...@gm...>]

I created the updated rpm files starting from src.rpm of 1.0.6 and
1.0.10tgz files, and so I get
the alsa-lib-1.0.10 alsa-utils-1.0.10 and alsa-lib-devel-1.0.10 rpm files.
Apparently I didn't change anything important.
But afte "rpm -U" of the new files I get the
ALSA lib setup.c:548:(add_elem) Cannot obtain info for CTL elem
error when trying to play through spdif....
it seems the only difference is that in rpm build, the alsaconf script is
skipped
and sound card configuration delegated to rh tool.
But also creating it and aplying,m didn;t solve my problem...
Boh, I will still try to investigate
it would help to know/debug the origin of the error.
I always was convinced about easiness of debugging problems in Linux vs
Windows,
but with alsa it seems less true...

Gianluca


2005/12/5, Brian L Scipioni <br...@ga...>:
>
> Yes.  All my problems were cured by removing the three 1.0.6 rpms that
> come with FC3.  The only rpm changes i made were:
> rpm -e --nodeps alsa-lib-1.0.6-8.FC3
> rpm -e --nodeps alsa-utils-1.0.6-3
> rpm -e --nodeps alsa-lib-devel-1.0.6-8.FC3
> Then I installed alsa 1.0.10 (with "make install") after building from
> source.
>
> brian
>
> On Sun, 2005-12-04 at 20:53 +0100, Gianluca Cecchi wrote:
> > Did you solve also the
> > > > ALSA lib setup.c:548:(add_elem) Cannot obtain info for CTL elem
> > > > (MIXER,'IEC958 Playback Default',0,0,0): No such file or directory
> > > > aplay: main:544: audio open error: No such file or directory
> >
> > message?
> > With other installs did you use "rpm -U" command over 1.0.6 or what?
> > I think you could not have multiple versions of alsa-lib and alsa-
> > utils on the system...
> > Gianluca
> >
> >
>
>