From: alexander <axeldenstore@gmail.com>
To: alsa-devel@alsa-project.org
Subject: cannot submit syncpipe, usb2 audio
Date: Wed, 04 Jan 2012 23:50:28 +0200 [thread overview]
Message-ID: <4F04C9A4.9020601@gmail.com> (raw)
|I asked in alsa-users about the state of usb2 audio class compliance some time ago but I never got a definitive answer.. I've done some digging on my own and found someone had a similar issue with the same error about a year ago.
This is what dmesg says when I connect the device in usb2 mode, the last row is the error when I try to use it.
[ 2384.749399] usb 1-2: USB disconnect, device number 2
[ 2390.729825] usb 1-2: new high speed USB device number 3 using ehci_hcd
[ 2390.863654] generic-usb 0003:0926:0202.0003: hiddev0,hidraw0: USB HID v1.01 Device [Sound Devices USBPre2] on usb-0000:00:02.1-2/input3
[ 2418.388135] cannot submit syncpipe for urb 0, error -90: internal error
Here are the lsusb -v as usb1.1 http://pastebin.com/Jj6mXHxJ and here as usb2 http://pastebin.com/8uCBAkNb
I've looked at them and the only thing that differs is the|bInterval, wich is 1 in usb1.1 and 4 in usb2
next reply other threads:[~2012-01-04 21:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-04 21:50 alexander [this message]
2012-01-08 16:33 ` cannot submit syncpipe, usb2 audio alexander
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=4F04C9A4.9020601@gmail.com \
--to=axeldenstore@gmail.com \
--cc=alsa-devel@alsa-project.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;
as well as URLs for NNTP newsgroup(s).