All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: cltien@cmedia.com.tw
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: CMI8768 patch
Date: Wed, 23 Feb 2005 11:42:06 +0100	[thread overview]
Message-ID: <s5hu0o3sgld.wl@alsa2.suse.de> (raw)
In-Reply-To: <92C0412E07F63549B2A2F2345D3DB515F7D658@cm-msg-02.cmedia.com.tw>

At Wed, 23 Feb 2005 11:42:53 +0800,
Tien, C.L. wrote:
> 
> The message was created with alsa-lib-1.0.8 on RedHat 7.3 (kernel 2.4.26)
> Now I switch to CVS on FC3. I found the result is opposite:
> 
> alsa-lib-1.0.8+RH 7.3, front, rear can be used as -D option, while default shows the above message.
> 
> alsa-lib CVS+FC3 it is ok to "aplay" directly or "aplay -D default", but either front or rear I got
> ALSA lib pcm.c:1939:(snd_pcm_open_conf) Cannot open shared library /usr/lib/alsa-lib/libasound_module_pcm_softvol.so
> aplay: main:508: audio open error: No such file or directory

It's weird.
Please make sure that your cvs tree is all updated properly.

> The libasound.so.2.0.0 is installed successfully and there is no /usr/lib/alsa-lib path
> in my system (should I create?) Please help!

/usr/lib/alsa-lib is the extra path for plugin shared objects.  The
plugins alsa-plugins repository are installed there.  However, the
standard plugins are included in libasound.so.  So, you don't need to
create this directory at all.

Just to be sure: your system is i386, not AMD64, right?


Takashi


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

  reply	other threads:[~2005-02-23 10:42 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-23  3:42 CMI8768 patch "Tien,  C.L. - 田承禮"
2005-02-23 10:42 ` Takashi Iwai [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-02-23 22:50 "Tien,  C.L. - 田承禮"
2005-02-24  4:20 ` Sergio Monteiro Basto
2005-02-24 10:30   ` Takashi Iwai
2005-02-24 18:42     ` Sergio Monteiro Basto
2005-02-24 18:52       ` Takashi Iwai
2005-02-24 23:23         ` Sergio Monteiro Basto
2005-02-24  9:52 ` Takashi Iwai
2005-02-23 20:50 "Tien,  C.L. - 田承禮"
2005-02-22 22:00 "Tien,  C.L. - 田承禮"
2005-02-22 19:07 "Tien,  C.L. - 田承禮"
2005-02-22 19:51 ` Takashi Iwai
2005-02-20 23:20 "Tien,  C.L. - 田承禮"
2005-02-22 11:30 ` Takashi Iwai
2005-02-17 22:11 "Tien,  C.L. - 田承禮"
2005-02-18 10:27 ` Takashi Iwai
2005-02-18 10:58 ` Takashi Iwai

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=s5hu0o3sgld.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=cltien@cmedia.com.tw \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.