From: jordan johnston <triplesquarednine@gmail.com>
To: alsa-devel@alsa-project.org
Subject: Status of the Tascam US-122mkII???
Date: Sat, 19 Jun 2010 13:35:32 -0400 [thread overview]
Message-ID: <AANLkTimaehZwC-e1pmbQl-pLNb7gVp2Rt5Ujz4BfduR_@mail.gmail.com> (raw)
hello,
Recently, i have gotten my hands on a Tascam US-122mkII. i have done
a lot of reading/googling and i can see that the device has been added
to the snd-usb-us122l and even-cross referenced my own device to make
sure the Id and such were there.
Currently, i am unable to get sound out of the Unit. it does
however, power up on boot.
I have tried many things to get it working, and i have even gotten
Jack to give me the option of picking this Device, however it shows
errors
and does not work :(
**** I am curious about the status of these drivers??
**** does anyone have this unit working at all?
**** and the steps they used to get it working. ( as much of the info
i have read doesn't seem quite uptodate )
is there possibly firmware for this unit or do i use the -US122L
firmware instead?
for Just a bit of background, I am using Fedora 12 with Planet CCRMA.
however, i do not using the CCRMA kernel, as it doesn't cut it for me.
A: it doesn't support a lot of newer hardware, B: it doesn't use MSI-X
on my machine(shared USB/soundcard) C: It's bloated... D: no BFS
scheduler.
Instead i am using Zen-kernel which tends to be a lot more up to
date, and i have gotten much better performance from Zen than any
other
kernel on any distro i have ever used.
now, I am more than willing to provide any information that might
help.... this is what i know so far.
dmesg:
ALSA sound/usb/usx2y/usb_stream.c:603: status=-2
ALSA sound/usb/usx2y/usb_stream.c:603: status=-2
ALSA sound/usb/usx2y/us122l.c:365: us122l_start error -14
snd-usb-us122l: probe of 1-5:1.1 failed with error -22
i have tried googling these messages to no avail. i poked around
through the driver, i've tried some of the trouble-shooting tips
provided by the guy who originally
got the older models to work, removing echi-hcd, or unbinding it,
unplugging it, etc. but nothing seems to be making a difference.
Then my thought was that i need a proper asound.conf or .asoundrc.
because the soundcard seems to be available, when i unbind it and
unplug/plug the unit back in.
i even tried removing them to see if on reboot, that they might be
reconfigured, but no luck.
if anyone can provide help, that would be greatly appreciated. I
have a 30-day return, so if i can't figure it out, i will be returning
it
for a FFADO approved/fully-supported device. however that being said,
wouldn't it be nice to still take the opportunity to have this
device better supported or help debug some issues??
while i am not a really good programmer, i think i could be useful, as
i have this device in front of me
and can provide useful information to developers, just let me know
what you need!
Jordan
next reply other threads:[~2010-06-19 17:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-19 17:35 jordan johnston [this message]
2010-06-19 17:42 ` Status of the Tascam US-122mkII??? Daniel Mack
[not found] ` <AANLkTilfDBFqGH41TGF0H855CfCm8fOjGMW7lwH1tXi_@mail.gmail.com>
2010-06-19 18:09 ` Daniel Mack
[not found] ` <AANLkTikfeTzrOttiyI9BqqD3zHI7NXY8ScyXoY8Ruq8N@mail.gmail.com>
2010-06-19 18:57 ` Daniel Mack
2010-06-19 19:03 ` Tobias Hansen
[not found] ` <AANLkTimJ17dGo6K3Gy8_tlhIezFFY0XDRyj53i8tj1pi@mail.gmail.com>
2010-06-19 20:19 ` Tobias Hansen
2010-06-19 20:45 ` jordan johnston
2010-06-19 20:47 ` jordan johnston
2010-06-19 20:58 ` Tobias Hansen
2010-06-19 22:42 ` jordan johnston
2010-06-19 22:41 ` Daniel Mack
[not found] ` <AANLkTikUAdL-tQ4CslnBRUP5dFFvKofvFRZn5gOiWRrD@mail.gmail.com>
[not found] ` <20100619230147.GP17833@buzzloop.caiaq.de>
[not found] ` <AANLkTimMpFrOzMctNCYcohyT-btYpUornvYGk2Tz1WFu@mail.gmail.com>
[not found] ` <20100619232244.GR17833@buzzloop.caiaq.de>
2010-06-19 23:53 ` jordan johnston
-- strict thread matches above, loose matches on Subject: below --
2010-06-19 23:05 Daniel Mack
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=AANLkTimaehZwC-e1pmbQl-pLNb7gVp2Rt5Ujz4BfduR_@mail.gmail.com \
--to=triplesquarednine@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).