All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Frank Barknecht <fbar@footils.org>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Quattro woes or: What does "SNDRV_PCM_IOCTL_START failed" mean?
Date: Tue, 11 Mar 2003 13:55:15 +0100	[thread overview]
Message-ID: <s5hllzm2hcc.wl@alsa2.suse.de> (raw)
In-Reply-To: <20030311103209.GA4139@fliwatut.scifi>

At Tue, 11 Mar 2003 11:32:09 +0100,
Frank Barknecht wrote:
> 
> Hallo,
> Takashi Iwai hat gesagt: // Takashi Iwai wrote:
> 
> > At Mon, 10 Mar 2003 23:33:22 +0100,
> > Frank Barknecht wrote:
> > > ALSA lib pcm_hw:454(snd_pcm_hw_start) SNDRV_PCM_IOCTL_START failed:
> > > Broken pipe
> > 
> > do you see any kernel message?
> > if the start fails in the pcm trigger callback, usb-audio driver
> > should show some error message there.
> 
> No, there only are the usual (de-)registering messages regarding
> snd-usb-audio. The only difference between my notebook and the laptop
> has been the kernel-version. Just 5 minutes ago I downgraded the
> notebook's kernel to 2.4.18 and now the error message went away! I'm
> currently still getting a lot of clicks, that probrably are caused by
> some wrong period settings in my application, but in general it is
> fine. For example "jackd -d alsa -d hw:0 -n 2" clicks, but "-n 3" is
> smooth.

make sure that you starting the jack with 48kHz and the period size
aligned to 48, such as 48, 96, 192...


Takashi


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

  reply	other threads:[~2003-03-11 12:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-10 22:33 Quattro woes or: What does "SNDRV_PCM_IOCTL_START failed" mean? Frank Barknecht
2003-03-11 10:02 ` Takashi Iwai
2003-03-11 10:32   ` Frank Barknecht
2003-03-11 12:55     ` Takashi Iwai [this message]
2003-03-11 18:02       ` Frank Barknecht
2003-03-11 18:44         ` Paul Davis
     [not found]         ` <20030311184050.5D539C6F38@mailproxy1.netcologne.de>
2003-03-11 18:57           ` Frank Barknecht

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=s5hllzm2hcc.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=fbar@footils.org \
    /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.