From: Takashi Iwai Subject: Re: Unable to open plughw:0,0 from user program. Date: Thu, 23 Aug 2007 21:38:46 +0200 Message-ID: References: <46CDD5A8.3000006@cox.net> Mime-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mx1.suse.de (mail.suse.de [195.135.220.2]) by alsa0.perex.cz (Postfix) with ESMTP id 163152432F for ; Thu, 23 Aug 2007 21:38:47 +0200 (CEST) In-Reply-To: <46CDD5A8.3000006@cox.net> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: alsa-devel-bounces@alsa-project.org Errors-To: alsa-devel-bounces@alsa-project.org To: stan Cc: ALSA Developers List-Id: alsa-devel@alsa-project.org At Thu, 23 Aug 2007 11:44:56 -0700, stan wrote: > > Hi, > > I am unable to use plughw:0,0 as a device string while calling > err = snd_pcm_open (&alsa_dev, hw_from_default, SND_PCM_STREAM_PLAYBACK, 0); > > The same call works with hw_from_default == 'default', but fails when it > is 'plughw:0,0'. > The error is > cannot open audio device "plughw:0,0" (Device or resource busy) Maybe the devce is really in use? Try "fuser /dev/snd/*" > I am using the latest snapshot of alsa-lib, alsa-lib20070821. I tried > debugging but I cannot trace through the macros. As near as I can tell > there have been no changes to alsa.conf, and this worked just fine > before the latest upgrade alsa package alsa-lib.1.0.14-3 > > Is this a deliberate change in alsa that is known about, and is there a > way to still get the functionality? The old library binary might still remain. Some distros install libasound in /lib (or /lib64), instead of /usr/lib (or /usr/lib64). Takashi