After I got the error-messages from > ~$ dmesg | tail > [ 45.188273] Cause could be too long delays in usb-hcd interrupt handling. > [ 45.806157] Sequence Error!(hcd_frame=4 ep=8in;wait=1025,frame=1). > [ 45.806160] Most propably some urb of usb-frame 1025 is still missing. > [ 45.806163] Cause could be too long delays in usb-hcd interrupt handling. > [ 48.999817] Sequence Error!(hcd_frame=127 ep=10out;wait=127,frame=124). > [ 48.999820] Most propably some urb of usb-frame 127 is still missing. > [ 48.999823] Cause could be too long delays in usb-hcd interrupt handling. > [ 49.899488] Sequence Error!(hcd_frame=3 ep=8in;wait=1024,frame=0). > [ 49.899492] Most propably some urb of usb-frame 1024 is still missing. > [ 49.899494] Cause could be too long delays in usb-hcd interrupt handling.upt handling. I looked it up and found the following entry on http://alsa.opensrc.org/Tascam_US-122 (Troubleshooting hints > Audio Playback) : "The reason [for this error] is [that] ubuntu-drivers are working with usb 2.0 and the US-122 is with usb1.1. This can be solved by unloading usb2.0 functionality:" sudo rmmod ehci_hcd So I tried it right away: ~$ sudo rmmod ehci_hcd [sudo] password for ...: ERROR: Module ehci_hcd does not exist in /proc/modules Well, I think that is related to my ubuntu version. So I went for sudo modprobe ehci_hcd Alone with that, nothing changed, so I tried the next suggestions: ~$ sudo rmmod snd-usb-usx2 ~$ sudo modprobe snd-usb-usx2y nrpacks=1 Nothing changed, until I set nrpacks to '3': ~$ sudo jackd -dalsa -dhw:2,0 -r48000 -p1024 -n2 jackdmp 1.9.7 Copyright 2001-2005 Paul Davis and others. Copyright 2004-2011 Grame. jackdmp comes with ABSOLUTELY NO WARRANTY This is free software, and you are welcome to redistribute it under certain conditions; see the file COPYING for details no message buffer overruns no message buffer overruns JACK server starting in realtime mode with priority 10 control device hw:2 control device hw:2 audio_reservation_init Acquire audio card Audio2 creating alsa driver ... hw:2,0|hw:2,0|1024|2|48000|0|0|nomon|swmeter|-|32bit control device hw:2 configuring for 48000Hz, period = 1024 frames (21.3 ms), buffer = 2 periods ALSA: final selected sample format for capture: 24bit little-endian ALSA: use 2 periods for capture ALSA: final selected sample format for playback: 24bit little-endian ALSA: use 2 periods for playback ALSA: poll time out, polled for 31999193 usecs JackAudioDriver::ProcessAsync: read error, stopping... It looks like jackd comes closer to getting us-122 running, but still something keeps it from really getting there... sela 2012/2/29 Fabio Sela <fabiosela@xxxxxx>: >>> I downloaded and installed the kernel 3.0.13: >> >>There's no reason not use 3.0.22 ... > > ok, got 3.0.22 ... > > ~$ uname -vr > 3.0.22-030022-generic #201202201735 SMP Mon Feb 20 22:36:19 UTC 2012 > >>There must be some error. >>What is the output of "dmesg | tail" after this? > > here you go: > > ~$ dmesg | tail > [ 45.188273] Cause could be too long delays in usb-hcd interrupt handling. > [ 45.806157] Sequence Error!(hcd_frame=4 ep=8in;wait=1025,frame=1). > [ 45.806160] Most propably some urb of usb-frame 1025 is still missing. > [ 45.806163] Cause could be too long delays in usb-hcd interrupt handling. > [ 48.999817] Sequence Error!(hcd_frame=127 ep=10out;wait=127,frame=124). > [ 48.999820] Most propably some urb of usb-frame 127 is still missing. > [ 48.999823] Cause could be too long delays in usb-hcd interrupt handling. > [ 49.899488] Sequence Error!(hcd_frame=3 ep=8in;wait=1024,frame=0). > [ 49.899492] Most propably some urb of usb-frame 1024 is still missing. > [ 49.899494] Cause could be too long delays in usb-hcd interrupt handling. > > Sounds like there might be a hint in there... some usb-issue? > > cheers > sela > > >>------------------------------ >> >>Message: 2 >>Date: Tue, 28 Feb 2012 16:08:34 +0100 >>From: Clemens Ladisch <cladisch@xxxxxxxxxxxxxx> >>Subject: Re: US-122: permanent problem on ubuntustudio >> 11.10 >>To: alsa-user@xxxxxxxxxxxxxxxxxxxxx >>Message-ID: <4F4CEDF2.2040001@xxxxxxxxxxxxxx> >>Content-Type: text/plain; charset=us-ascii >> >>Fabio Sela wrote: >>> I downloaded and installed the kernel 3.0.13: >> >>There's no reason not use 3.0.22 ... >> >>> Now, trying to start jack still fails: >>> >>> ALSA: cannot set hardware parameters for playback >> >>There must be some error. >>What is the output of "dmesg | tail" after this? >> >> >>Regards, >>Clemens >> >> > 2012/2/28 Fabio Sela <fabiosela@xxxxxx>: >> Hi Clemens, >> >>> grep bandwidth /var/log/* >>>or for recent messages only: >>> dmesg | grep bandwidth >> >> ... don't get any error messages here. >> >> >>>The bug I'm thinking about was fixed in 3.0.13; the current stable >>>kernel version is 3.2.7. A newer kernel might be available through >>>online updates, if Ubuntustudio has them. >> >> I downloaded and installed the kernel 3.0.13: >> >> uname -vrs >> Linux 3.0.13-030013-generic #201112091235 SMP Fri Dec 9 17:35:57 UTC 2011 >> >> Now, trying to start jack still fails: >> >> ~$ sudo jackd -dalsa -dhw:2,0 -r48000 -p1024 -n2 >> jackdmp 1.9.7 >> Copyright 2001-2005 Paul Davis and others. >> Copyright 2004-2011 Grame. >> jackdmp comes with ABSOLUTELY NO WARRANTY >> This is free software, and you are welcome to redistribute it >> under certain conditions; see the file COPYING for details >> no message buffer overruns >> no message buffer overruns >> JACK server starting in realtime mode with priority 10 >> control device hw:2 >> control device hw:2 >> audio_reservation_init >> Acquire audio card Audio2 >> creating alsa driver ... hw:2,0|hw:2,0|1024|2|48000|0|0|nomon|swmeter|-|32bit >> control device hw:2 >> configuring for 48000Hz, period = 1024 frames (21.3 ms), buffer = 2 periods >> ALSA: final selected sample format for capture: 24bit little-endian >> ALSA: use 2 periods for capture >> ALSA: final selected sample format for playback: 24bit little-endian >> ALSA: use 2 periods for playback >> ALSA: cannot set hardware parameters for playback >> ALSA: cannot configure playback channel >> Cannot initialize driver >> JackServer::Open() failed with -1 >> Failed to open server >> >> >> Or trying it with '-dhw:2' instead of '-dhw:2,0' >> >> ~$ sudo jackd -dalsa -dhw:2 -r48000 -p1024 -n2 >> jackdmp 1.9.7 >> Copyright 2001-2005 Paul Davis and others. >> Copyright 2004-2011 Grame. >> jackdmp comes with ABSOLUTELY NO WARRANTY >> This is free software, and you are welcome to redistribute it >> under certain conditions; see the file COPYING for details >> no message buffer overruns >> no message buffer overruns >> JACK server starting in realtime mode with priority 10 >> control device hw:2 >> control device hw:2 >> audio_reservation_init >> Acquire audio card Audio2 >> creating alsa driver ... hw:2|hw:2|1024|2|48000|0|0|nomon|swmeter|-|32bit >> control device hw:2 >> configuring for 48000Hz, period = 1024 frames (21.3 ms), buffer = 2 periods >> ALSA: final selected sample format for capture: 24bit little-endian >> ALSA: use 2 periods for capture >> ALSA: final selected sample format for playback: 24bit little-endian >> ALSA: use 2 periods for playback >> ALSA: prepare error for playback on "hw:2" (Broken pipe) >> Cannot start driver >> JackServer::Start() failed with -1 >> Failed to start server >> control device hw:2 >> Released audio card Audio2 >> audio_reservation_finish >> control device hw:2 >> >> >> sela >> >> ------------------------------ >> >>>Message: 3 >>>Date: Mon, 27 Feb 2012 17:15:57 +0100 >>>From: Clemens Ladisch <cladisch@xxxxxxxxxxxxxx> >>>Subject: Re: US-122: permanent problem on ubuntustudio >>> 11.10 >>>To: alsa-user@xxxxxxxxxxxxxxxxxxxxx >>>Message-ID: <4F4BAC3D.4010609@xxxxxxxxxxxxxx> >>>Content-Type: text/plain; charset=us-ascii >>> >>>Fabio Sela wrote: >>>>> Which kernel version? Try the latest update. >>>> >>>> ~$ uname -vrs >>>> Linux 3.0.0-16-generic #28-Ubuntu SMP Fri Jan 27 17:44:39 UTC 2012 >>>> I downloaded the latest version of Ubuntustudio 11.10 only recently (a >>>> couple of weeks ago) and installed it right-away from DVD. Should I >>>> still go for a newer one (is there)? >>> >>>The bug I'm thinking about was fixed in 3.0.13; the current stable >>>kernel version is 3.2.7. A newer kernel might be available through >>>online updates, if Ubuntustudio has them. >>> >>>>> Check the system log for bandwidth error messages. >>>> >>>> Can you give me a hint how to look for that? >>> >>> grep bandwidth /var/log/* >>>or for recent messages only: >>> dmesg | grep bandwidth >>> >>>The message would be something like "cannot submit datapipe ... not >>>enough bandwidth". >>> >>> >>>Regards, >>>Clemens >> ------------------------------- >>>2012/2/27 Fabio Sela <fabiosela@xxxxxx>: >>> Clemens, >>> >>>> Which kernel version? Try the latest update. >>> >>> ~$ uname -vrs >>> Linux 3.0.0-16-generic #28-Ubuntu SMP Fri Jan 27 17:44:39 UTC 2012 >>> >>> I downloaded the latest version of Ubuntustudio 11.10 only recently (a >>> couple of weeks ago) and installed it right-away from DVD. Should I >>> still go for a newer one (is there)? >>> >>>> Check the system log for bandwidth error messages. >>> >>> Can you give me a hint how to look for that? >>> I never worked on the logfiles, but would it be e.g. like 'cat >>> /var/log/syslog | grep bandwidth' ? Only that does not give me any >>> interesting error-messages: >>> >>> /var/log$ cat syslog | grep bandwidth >>> Feb 21 07:52:09 ubuntu kernel: [ 14.083499] cfg80211: >>> (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) >>> Feb 21 09:44:05 ubuntu kernel: [ 8.150424] cfg80211: >>> (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) >>> Feb 21 10:22:35 ubuntu kernel: [ 11.913162] cfg80211: >>> (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) >>> Feb 23 22:07:08 ubuntu kernel: [ 12.798987] cfg80211: >>> (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) >>> Feb 24 08:08:06 ubuntu kernel: [ 12.102207] cfg80211: >>> (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) >>> Feb 25 22:16:57 ubuntu kernel: [ 11.981356] cfg80211: >>> (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) >>> Feb 25 22:18:32 ubuntu kernel: [ 11.614490] cfg80211: >>> (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) >>> Feb 25 23:48:45 ubuntu kernel: [ 11.756647] cfg80211: >>> (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) >>> Feb 27 07:58:20 ubuntu kernel: [ 12.180472] cfg80211: >>> (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) >>> >>> Stefan >>> >>> 2012/2/27 Clemens Ladisch <cladisch@xxxxxxxxxxxxxx>: >>>> Fabio Sela wrote: >>>>> I have been trying to get my Tascam US-122 USB Audio interface running >>>>> on Ubuntustudio 11.10 >>>> >>>> Which kernel version? Try the latest update. >>>> >>>>> ALSA: cannot set hardware parameters for playback >>>>> ... >>>>> 00:1a.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 05) >>>> >>>> Probably an EHCI driver bug. >>>> Check the system log for bandwidth error messages. >>>> >>>>> When I start alsamixer and select the usx2y sound-device, I get the >>>>> message: " This sound device does not have any controls." >>>> >>>> This is OK for devices that actually do not have any software- >>>> controllable controls. >>>> >>>> >>>> Regards, >>>> Clemens ------------------------------------------------------------------------------ Virtualization & Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ _______________________________________________ Alsa-user mailing list Alsa-user@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/alsa-user
