[alsa-devel] spdif/iec958 outputs at VT1708S not recognized
tiwai at suse.de
Wed May 27 18:51:06 CEST 2009
At Wed, 27 May 2009 12:35:49 -0400,
> Yeah it didn't work.
> I am lost and generally I can find the answers quickly. I cant use the
> "kernel" alsa due to the spdif out and for some reason those undefined
> messages just wont go away. I looked into the kernel source and they both
> do exist in sound core. I can't imagine what could be wrong.
If it's really an ALSA module (not soundcore), it's often because you
didn't unload some old modules before loading a new one.
Also, if the old modules are also update modules located in
/lib/modules/$VERSION/update or so, then the old modules will still
win over the newly installed one in
/lib/modules/$VERSION/kernel/sound/*. IIRC, Ubuntu or some others
install the update modules there. In such a case, you'll need to
specify the installation path explicitly via configure option, too.
If it's the sound core, you need to make sure that this is really
built in, either into the kernel or as a module. And, the kernel tree
really points to the version you are running. There are symbols to be
referred, so it's not only the source you need to build external
At best, you should consult on user forum (or such) for your own
distro, since this topic is really distro-specific.
> -----Original Message-----
> From: Takashi Iwai [mailto:tiwai at suse.de]
> Sent: Wednesday, May 27, 2009 1:35 AM
> To: Sentinel
> Cc: alsa-devel at alsa-project.org
> Subject: Re: [alsa-devel] spdif/iec958 outputs at VT1708S not recognized
> At Tue, 26 May 2009 22:57:31 -0400,
> Sentinel wrote:
> > Okay I figured out my own problem.
> > This is specific to those who run 64bit OS.
> > for anyone who is getting register_sound_special_device error when
> > attempting to compile ALSA, on a 64 bit OS make sure your running your
> > configure properly. Most likely your distro has ALSA libraries located in
> > the /usr/lib64 path not in /usr/lib and most likely the ld.so.conf is set
> > look in /usr/lib64 before it searches /usr/lib which is the default for
> > configure script. As a warning I'd not try to change that order
> > if you have built any 32bit compatibility drivers into /usr/lib
> I guess you are looking at a wrong place.
> The fix must be coincident :)
> Basically alsa-driver (and kernel) compilation doesn't use any
> user-space library, so libpath is irrelevant. The only important
> location is the kernel source tree and its build stub. If these
> aren't set up properly, such an error (version mismatch or so) may
> Note that sound_register_special() and co aren't defined in the ALSA
> driver, but it's defined in sound_core.c in the kernel.
More information about the Alsa-devel