Tascam us122 mkII not recording
1 Attachment(s)
I have a Tascam us122 mkII usb sound card. The card was working fine last year, but after some update something broke. Now I can't hear anything and can't record anything. I'm mostly interested in capturing audio for a video project I'm working on, not playback. The processing/editing will be done on another PC.
I am running Gentoo kernel 3.11.3 I have jack installed and the jack use flag enabled. I don't have a /etc/asound.conf or a ~/.asoundrc since I read it's not needed anymore. I have alsa-firmware installed too. I have /etc/udev/rules.d/55-tascam.rules : Code:
ATTRS{idVendor}=="1604", ATTRS{idProduct}=="8006", RUN+="/bin/sh -c '/sbin/fxload -D %N -s /usr/share/alsa/firmware/usx2yloader/tascam_loader.ihx -I /usr/share/alsa/firmware/usx2yloader/us122fw.ihx'" Code:
$ lsusb Code:
$ aplay -l Code:
$ arecord -l Code:
usx2yloader: no US-X2Y-compatible cards found Code:
# ls -l /proc/bus Any help/ideas? I'll be happy to add any info I forgot to include. |
Hi
Until you get a better reply as I don't have your hardware 1) Can you link to the guide you followed pls b) I believe your guide is wrong with at least 2 errors, let me show another device guide and explain ############ http://www.astro.caltech.edu/~mcs/tascam_us122/ #################### first you need the fxload package either from your repo or from source and you did not mention it Secondly your udev rule is claiming that your vendor has 2 ids....and I allege No According to my link.....fxload will allow vendor 0644 product 8021 to show a new entry in lsusb but your udev rule assumes it stays the same ----its possible based on the link, that the new product id will become 8022 So what I am suggesting is just run lsusb the second time and see what your new product is called. ---this is similar to creating manually udev rules for flip flop usb dongle modems. good luck Leaping ahead, when you know what the next product is called you can manually run Code:
sudo /usr/bin/usx2yloader EDIT I forgot to mention, please check the pathways to each executable in your current udev rule please ie when you have installed fxload /sbin/fxload /usr/share/alsa/firmware/usx2yloader/tascam_loader.ihx /usr/bin/usx2yloader and you may need a sym link for the alsa firmware to /lib/firmware/usx2yloader as per google https://help.ubuntu.com/community/TASCAM_US-122 |
Thanks for the reply. The fxload is installed i just forgot to mention it. The reason for 2 rules is that for some reason the ids have changed since the last time I used the card, so I copied the old rule and modified it. I already tried 8022 but no luck. I will try some more and post back in a couple of days, I'm out pf town currently.
|
no worries but just to be blunter after running the first firmware, I am suggesting run lsusb to find the model change
no rush either as I am infrequent poster so happy others to take over if I am slower to reply |
Ok, looks like the issue is narrowed down a bit. If I manually run fxload:
Code:
# fxload -D /dev/bus/usb/001/002 -s /usr/share/alsa/firmware/usx2yloader/tascam_loader.ihx -I /usr/share/alsa/firmware/usx2yloader/us122fw.ihx Code:
# lsusb |
All times are GMT -5. The time now is 03:14 AM. |