Tascam us-122l on Ubuntu 9.04 (I believe really an IRQ issue) please read.
Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Tascam us-122l on Ubuntu 9.04 (I believe really an IRQ issue) please read.
My issue is with a Tascam US-122l.
Not the US-122. I had one of those and wish I still did. It was easy.
I need some help. Even though I have been a member here for a long time this is the first time I have had to ask. I have always been able to glean the answers I need from someone else's question.
The "symptom" is there is no sound. Currently none at all (except through a mike). If I remove the .asoundrc file I have sound but it comes from the on board sound card.
First I think I would like to get this away from being a sound card issue.
I believe right now that the question is "how can I assign an IRQ to this card?".
To be thorough, a list of hardware:
Gigabyte MB GA-81865GME-775RH
Celeron 2.6 ghz processor
Award BIOS (not updated)
ATI 9800 pro video
1 IDE drive, 1 SATA drive, 1 DVD-RW
1 USB printer
Keyboard and mouse are PS/2.
Tascam US-122L (the item in question)
Let me state categorically that the system recognizes the unit. The modules and drivers are loaded. It shows up in /proc/asound/cards (but not with an IRQ) and if you plug a mike into it sound comes out the speakers. The issue (I believe)is that ALSA only recognizes cards that have an IRQ. Thusly even though my .asoundrc sets it up properly and all the modules (drivers, etc.) get loaded and even hwdinfo lists and all it's functionality correctly but it is not available for use by any of the sound server/applications save jack and it only lists the midi ports.
Still aplay -l will list only the on board sound device and not the Tascam even though it immediately shows up in proc. Asoundconf does list it.
Per ALSA.org website "only real sound cards have IRQ's". So I am assuming that this is the reason it is not available in ALSA/aplay.
I have tried all the HOWTO'S I can find, upgraded from source ALSA and all the rest of the related software.
I looked at compiling the kernel but could find nothing to change that seemed like it would make a difference.
I have moved the plugs and removed and replaced everything possible.
I have tried adding acpi=off irqpoll as kernel options in menu.lst.
I have tried adding noapic pci=irqroute pci=noacpi acpi=off irqpoll as kernel options in menu.lst.
Note that even though I cannot find documentation on these I believe they have been deprecated. At least irqpoll gives an error message as an unknown command.
I have analyzed ad nauseum the results of all of the commands such as lspci, lsmod|grep '^snd',modinfo snd_usb_us122l, modinfo snd_usb_lib, modinfo snd_hwdep, cat /var/log/syslog | grep snd, cat /etc/modprobe.d/alsa-base.conf, hwinfo and more. All give the results expected from a working situation.
Following is information that I think points to issue.
Error exert from dmesg during boot. Finally the boot continues and but does not register the hardware.
[ 18.208021] usb 1-5: device descriptor read/64, error -110
[ 33.424020] usb 1-5: device descriptor read/64, error -110
[ 33.640018] usb 1-5: new high speed USB device using ehci_hcd and address 4
[ 48.752021] usb 1-5: device descriptor read/64, error -110
[ 63.968022] usb 1-5: device descriptor read/64, error -110
[ 64.184018] usb 1-5: new high speed USB device using ehci_hcd and address 5
[ 74.592014] usb 1-5: device not accepting address 5, error -110
[ 74.704023] usb 1-5: new high speed USB device using ehci_hcd and address 6
[ 85.112015] usb 1-5: device not accepting address 6, error -110
[ 85.112094] hub 1-0:1.0: unable to enumerate USB device on port 5
[ 85.376016] usb 4-1: new full speed USB device using uhci_hcd and address 2
[ 100.488018] usb 4-1: device descriptor read/64, error -110
[ 115.704024] usb 4-1: device descriptor read/64, error -110
[ 115.920016] usb 4-1: new full speed USB device using uhci_hcd and address 3
[ 131.032019] usb 4-1: device descriptor read/64, error -110
[ 146.248017] usb 4-1: device descriptor read/64, error -110
[ 146.464017] usb 4-1: new full speed USB device using uhci_hcd and address 4
[ 156.872023] usb 4-1: device not accepting address 4, error -110
[ 156.984020] usb 4-1: new full speed USB device using uhci_hcd and address 5
[ 167.392017] usb 4-1: device not accepting address 5, error -110
[ 167.392090] hub 4-0:1.0: unable to enumerate USB device on port 1
When I plug it in after boot dmesg says:
[ 490.680041] usb 1-5: new high speed USB device using ehci_hcd and address 7
[ 490.812507] usb 1-5: config 1 interface 1 altsetting 1 bulk endpoint 0x83 has invalid maxpacket 9
[ 490.849106] usb 1-5: configuration #1 chosen from 1 choice
[ 492.384591] usbcore: registered new interface driver snd-usb-us122l
Following are the results from procinfo. This may offer a picture worth examination.
Memory: Total Used Free Buffers
RAM: 1026552 750436 276116 35800
Swap: 1646620 0 1646620
First I'd like to tell you that my english isn't really good so I'm sorry for this.
I have a similar issue, and I am kind of a beginner to ubuntu (but I'm better every day =] ).
I have ubuntu 9.04, 2.6.28-13-generic, alsa 1.0.20. So everything has been updated, but still, my TASCAM US122L isn't detected !
No sound at all. (but my motherboard's soundcard works fine).
'cat /proc/asound/modules' gives me '0 snd_hda_intel', nothing else...
'cat /var/log/syslog | grep snd' gives me
Jun 25 13:10:26 tom-desktop kernel: [ 14.188489] usbcore: registered new interface driver snd-usb-us122l
Jun 25 13:48:16 tom-desktop kernel: [ 2292.320032] snd-usb-us122l: probe of 1-4:1.1 failed with error -5 ( <---- every time I plug the US122L in, a new msg like that appears )
I read that the US122L should be detected automatically with 9.04, but seems it doesnt !
I don't know what to do. Help me please... And please remember that I'm not really good using ubuntu commands...
Last edited by stratocastom; 06-25-2009 at 07:18 AM.
Did anyone find a solution to this? I'm running Ubuntu 10.04 and I'm in the exact same situation as you, gorean. Thanks for the detailed info by the way, it helped me get up to speed with the problem...
jackd is the only way anyone seems to use this card
I've gotten this card working under gentoo with a 2.6.32 kernel amd64, and under archlinux with i386. I am currently trying to get it working with arch and amd64 2.6.35. No one seems to use this card as a general purpose sound card. They all use it with jack audio connection kit for pro-audio with ardour or something else which works with jack. The driver creates devices under /dev/snd but you are quite right, aplay -L does not seem to see them. If one could send the right format of data to them, sound should come out, but I have yet to find any instructions for setting the card up to talk to pulseaudio or anything other than jack.
That tells a long, long, story. You should find every device and it's module. You should find a hda Intel device, and a codec chip. What your other card uses I dunno. See what one has the module. Disable the m/b soundcard in the bios, and see what it finds then. Don't post a mile of lshal please. If you feel the world has to see it, pastebin it.