From: "David Härdeman" <david@hardeman.nu>
To: linux-kernel@vger.kernel.org
Cc: alsa-devel@lists.sourceforge.net
Subject: snd-usb-audio problems with 2.6.18
Date: Sat, 23 Sep 2006 14:54:56 +0200 [thread overview]
Message-ID: <20060923125456.GA7757@hardeman.nu> (raw)
A recent 2.6.18 kernel upgrade on one of my machines broke usb audio.
I'm using a TerraTec Aureon 5.1 USB MKII to feed ac3 audio to a
receiver, but after the upgrade, trying to play any audio (tried aplay,
mplayer, xine, etc...using both oss and alsa audio) results in the
kernel log being filled with the message:
"cannot submit datapipe for urb 5, error -28: not enough bandwidth"
Unfortunately the upgrade was from 2.6.14 (yes, it's old but the machine
has no network connection usually) so there is quite a lot of
differences to the snd-usb-audio driver in the meantime.
Unless someone has suggestions as to a simple fix, I guess I'll
start testing kernels in the 2.6.14 <-> 2.6.18 range soon to try to pin
down a certain changeset...
--
David Härdeman
next reply other threads:[~2006-09-23 12:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-23 12:54 David Härdeman [this message]
2006-09-23 13:23 ` [Alsa-devel] snd-usb-audio problems with 2.6.18 Markus Rechberger
2006-09-24 0:02 ` David Härdeman
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=20060923125456.GA7757@hardeman.nu \
--to=david@hardeman.nu \
--cc=alsa-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox