Can't start jackd

Message

earlyjp · Post by **earlyjp** » Sat Mar 26, 2011 5:24 pm

Greetings!
I'm writing to ask for some assistance with getting jackd to load. First, I should mention that this is a fresh Gentoo install, and that I am running the following kernel, alsa, and jackd versions.

Code: Select all

$ uname -a
Linux DAW 2.6.36-gentoo-r5 #1 SMP Tue Mar 22 06:50:14 EDT 2011 x86_64 AMD Athlon(tm) II X4 640 Processor AuthenticAMD GNU/Linux

$ head -80 /tmp/alsa-info.txt.q6NhCFyfJT 
upload=true&script=true&cardinfo=
!!################################
!!ALSA Information Script v 0.4.59
!!################################

!!Script ran on: Sat Mar 26 16:58:46 UTC 2011


!!Linux Distribution
!!------------------

Gentoo Base System release 1.12.14


!!DMI Information
!!---------------

Manufacturer:      System manufacturer
Product Name:      System Product Name


!!Kernel Information
!!------------------

Kernel release:    2.6.36-gentoo-r5
Operating System:  GNU/Linux
Architecture:      x86_64
Processor:         AMD Athlon(tm) II X4 640 Processor
SMP Enabled:       Yes


!!ALSA Version
!!------------

Driver version:     1.0.23
Library version:    1.0.23
Utilities version:  1.0.23


!!Loaded ALSA modules
!!-------------------

snd_ice1712


!!Sound Servers on this system
!!----------------------------

Jack:
      Installed - Yes (/usr/bin/jackd)
      Running - No


!!Soundcards recognised by ALSA
!!-----------------------------

 0 [M44            ]: ICE1712 - M Audio Delta 44
                      M Audio Delta 44 at 0xec00, irq 21


!!PCI Soundcards installed in the system
!!--------------------------------------

03:06.0 Multimedia audio controller: VIA Technologies Inc. ICE1712 [Envy24] PCI Multi-Channel I/O Controller (rev 02)


!!Advanced information - PCI Vendor/Device/Susbsystem ID's
!!--------------------------------------------------------

03:06.0 0401: 1412:1712 (rev 02)
	Subsystem: 1412:d633
<snip>

$ jackd --version
jackd version 0.118.0 tmpdir /dev/shm protocol 24

My problem is that I cannot start jackd. I've tried doing so as a user and root, and using a variety of arguments to jackd. jackd will load, but it will always close after a few seconds (depending on the arguments used). What's more, the reported error messages vary with the arguments. Here is a sampling:

Code: Select all

$ jackd -d alsa  
jackd 0.118.0
Copyright 2001-2009 Paul Davis, Stephane Letz, Jack O'Quinn, Torben Hohn and others.
jackd 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

JACK compiled with System V SHM support.
loading driver ..
creating alsa driver ... hw:0|hw:0|1024|2|48000|0|0|nomon|swmeter|-|32bit
control device hw:0
configuring for 48000Hz, period = 1024 frames (21.3 ms), buffer = 2 periods
ALSA: final selected sample format for capture: 32bit integer little-endian
ALSA: use 2 periods for capture
ALSA: final selected sample format for playback: 32bit integer little-endian
ALSA: use 2 periods for playback
jackd watchdog: timeout - killing jackd
Aborted

$ jackd -d alsa -r 48000 -p 128
jackd 0.118.0
Copyright 2001-2009 Paul Davis, Stephane Letz, Jack O'Quinn, Torben Hohn and others.
jackd 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

JACK compiled with System V SHM support.
loading driver ..
apparent rate = 48000
creating alsa driver ... hw:0|hw:0|128|2|48000|0|0|nomon|swmeter|-|32bit
control device hw:0
configuring for 48000Hz, period = 128 frames (2.7 ms), buffer = 2 periods
ALSA: final selected sample format for capture: 32bit integer little-endian
ALSA: use 2 periods for capture
ALSA: final selected sample format for playback: 32bit integer little-endian
ALSA: use 2 periods for playback
ALSA: poll time out, polled for 4008394 usecs
DRIVER NT: could not run driver cycle
jack main caught signal 12

$ jackd -d alsa -r 48000 -p 128 -C hw:0
jackd 0.118.0
Copyright 2001-2009 Paul Davis, Stephane Letz, Jack O'Quinn, Torben Hohn and others.
jackd 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

JACK compiled with System V SHM support.
loading driver ..
apparent rate = 48000
creating alsa driver ... -|hw:0|128|2|48000|0|0|nomon|swmeter|-|32bit
control device hw:0
configuring for 48000Hz, period = 128 frames (2.7 ms), buffer = 2 periods
ALSA: final selected sample format for capture: 32bit integer little-endian
ALSA: use 2 periods for capture
impossible sample width (1) discovered!

$ jackd -d alsa -r 48000 -p 128 -P hw:0
jackd 0.118.0
Copyright 2001-2009 Paul Davis, Stephane Letz, Jack O'Quinn, Torben Hohn and others.
jackd 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

JACK compiled with System V SHM support.
loading driver ..
apparent rate = 48000
creating alsa driver ... hw:0|-|128|2|48000|0|0|nomon|swmeter|-|32bit
control device hw:0
configuring for 48000Hz, period = 128 frames (2.7 ms), buffer = 2 periods
ALSA: final selected sample format for playback: 32bit integer little-endian
ALSA: use 2 periods for playback
ALSA: poll time out, polled for 4008706 usecs
DRIVER NT: could not run driver cycle
jack main caught signal 12

$jackd -vr -d alsa
jackd 0.118.0
Copyright 2001-2009 Paul Davis, Stephane Letz, Jack O'Quinn, Torben Hohn and others.
jackd 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

getting driver descriptor from /usr/lib64/jack/jack_dummy.so
getting driver descriptor from /usr/lib64/jack/jack_net.so
getting driver descriptor from /usr/lib64/jack/jack_alsa.so
JACK compiled with System V SHM support.
server `default' registered
registered builtin port type 32 bit float mono audio
registered builtin port type 8 bit raw midi
clock source = system clock via clock_gettime
loading driver ..
start poll on 3 fd's
creating alsa driver ... hw:0|hw:0|1024|2|48000|0|0|nomon|swmeter|-|32bit
new client: alsa_pcm, id = 1 type 1 @ 0x608fc0 fd = -1
control device hw:0
configuring for 48000Hz, period = 1024 frames (21.3 ms), buffer = 2 periods
ALSA: final selected sample format for capture: 32bit integer little-endian
ALSA: use 2 periods for capture
ALSA: final selected sample format for playback: 32bit integer little-endian
ALSA: use 2 periods for playback
new buffer size 1024
registered port system:capture_1, offset = 4096
registered port system:capture_2, offset = 8192
registered port system:capture_3, offset = 12288
registered port system:capture_4, offset = 16384
registered port system:capture_5, offset = 20480
registered port system:capture_6, offset = 24576
registered port system:capture_7, offset = 28672
registered port system:capture_8, offset = 32768
registered port system:capture_9, offset = 36864
registered port system:capture_10, offset = 40960
registered port system:capture_11, offset = 45056
registered port system:capture_12, offset = 49152
registered port system:playback_1, offset = 0
registered port system:playback_2, offset = 0
registered port system:playback_4, offset = 0
registered port system:playback_5, offset = 0
registered port system:playback_6, offset = 0
registered port system:playback_7, offset = 0
registered port system:playback_8, offset = 0
registered port system:playback_9, offset = 0
registered port system:playback_10, offset = 0
++ jack_sort_graph
++ jack_rechain_graph():
+++ client is now alsa_pcm active ? 1
client alsa_pcm: internal client, execution_order=0.
-- jack_rechain_graph()
-- jack_sort_graph
15920 waiting for signals
ALSA: poll time out, polled for 32042943 usecs
DRIVER NT: could not run driver cycle
stopping driver
detaching driver
jack main caught signal 12
starting server engine shutdown
freeing shared port segments
stopping server thread
max delay reported by backend: 0.000 usecs
freeing engine shared memory
max usecs: 0.000, engine deleted
WARNING: 3 message buffer overruns!
cleaning up shared memory
cleaning up files
unregistering server `default'

I have carefully followed the instructions for building the low latency kernel, alsa, and most recently jack (found at http://en.gentoo-wiki.com/wiki/JACK). Everything has gone smoothly, except that I cannot start jackd.

I am fairly sure that all is well with alsa. I was able to launch alsamixer, make adjustments to levels, and enable capture on the appropriate channels. There appears to be some problem with jackd's ability to interface with the alsa driver for this card (ICE1712 -- M-Audio Delta 44).

I would very much appreciate some guidance for interpreting these error messages, and any configuration suggestions for getting jackd going.

Thank you,
~Jim

aCOSwt · Post by **aCOSwt** » Sat Mar 26, 2011 5:50 pm

Well :
- I suggest that you first install media-sound/qjackctl and set your parameters / launch jackd via this interface.
- Which DE are you under ?

BTW, there is no big problem running jack with the ICE1712 driver. The only trouble I found is that bug I reported : https://bugs.gentoo.org/show_bug.cgi?id=348902

Ant P. · Post by **Ant P.** » Sat Mar 26, 2011 6:18 pm

I'd guess that it either can't exclusively access the card (something else is using ALSA) or the settings are too extreme. Try it with higher latency + 16-bit to see if it works at all.

earlyjp · Post by **earlyjp** » Sat Mar 26, 2011 7:38 pm

Thank you for your response, aCOSwt. Please see my remarks below...

aCOSwt wrote:Well :
- I suggest that you first install media-sound/qjackctl and set your parameters / launch jackd via this interface.
- Which DE are you under ?

I have refrained from installing qjackctl until I was sure the underlying apps are working. It's the same reason I'm using Gentoo, in general. I'm trying to understand and test x before installing anything that depends on x. So far, it's worked well, and I'm learning a lot.

The only DE I've installed is XFCE4. In this case, I'm choosing what is reported to be a low-resource consuming DE. If KDE is required for qjackctl (as mentioned in its description), I'd again prefer to have jackd working before installation, as to minimize the chances of other interactions contributing to my problem.

BTW, there is no big problem running jack with the ICE1712 driver. The only trouble I found is that bug I reported : https://bugs.gentoo.org/show_bug.cgi?id=348902

Your report is very interesting, indeed. And, it makes me wonder if other functions of this driver are equally sparse.

I don't know what has happened. I used this card without any trouble for years under older versions of Ubuntu Studio, and I bought the card because it was considered to be well supported by the Linux community. However, trying to get this same interface going in my new AMD64 system has been very frustrating. I've spent the last two weeks trying multiple distros and many more combinations of arguments. Nothing I've tried has worked, and the reported errors haven't helped me figure out what may be wrong.

earlyjp · Post by **earlyjp** » Sat Mar 26, 2011 8:20 pm

Thank you for your response, Ant P. Please see my remarks below...

Ant P. wrote:I'd guess that it either can't exclusively access the card (something else is using ALSA) or the settings are too extreme. Try it with higher latency + 16-bit to see if it works at all.

Yes, that makes sense to me. And, again, that is why I have taken the installation step by step. I've knowingly installed nothing that might be trying to access the card, i.e. no other sound apps. Is there something I could examine, perhaps in /proc, that might indicate a contention?

If I'm understanding the arguments correctly, latency is largely controlled by the number of periods (-n) and the number of frames (-p). I've also tried short (-S), i.e. 16 bit operation. As you can see below, different values yield the same result.

Code: Select all

$ jackd -vr -d alsa -p 512 -S
jackd 0.118.0
Copyright 2001-2009 Paul Davis, Stephane Letz, Jack O'Quinn, Torben Hohn and others.
jackd 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

getting driver descriptor from /usr/lib64/jack/jack_dummy.so
getting driver descriptor from /usr/lib64/jack/jack_net.so
getting driver descriptor from /usr/lib64/jack/jack_alsa.so
JACK compiled with System V SHM support.
server `default' registered
registered builtin port type 32 bit float mono audio
registered builtin port type 8 bit raw midi
clock source = system clock via clock_gettime
loading driver ..
start poll on 3 fd's
creating alsa driver ... hw:0|hw:0|512|2|48000|0|0|nomon|swmeter|-|16bit
new client: alsa_pcm, id = 1 type 1 @ 0x609050 fd = -1
control device hw:0
configuring for 48000Hz, period = 512 frames (10.7 ms), buffer = 2 periods
ALSA: final selected sample format for capture: 32bit integer little-endian
ALSA: use 2 periods for capture
ALSA: final selected sample format for playback: 32bit integer little-endian
ALSA: use 2 periods for playback
new buffer size 512
registered port system:capture_1, offset = 2048
registered port system:capture_2, offset = 4096
registered port system:capture_3, offset = 6144
registered port system:capture_4, offset = 8192
registered port system:capture_5, offset = 10240
registered port system:capture_6, offset = 12288
registered port system:capture_7, offset = 14336
registered port system:capture_8, offset = 16384
registered port system:capture_9, offset = 18432
registered port system:capture_10, offset = 20480
registered port system:capture_11, offset = 22528
registered port system:capture_12, offset = 24576
registered port system:playback_1, offset = 0
registered port system:playback_2, offset = 0
registered port system:playback_3, offset = 0
registered port system:playback_5, offset = 0
registered port system:playback_6, offset = 0
registered port system:playback_7, offset = 0
registered port system:playback_8, offset = 0
registered port system:playback_9, offset = 0
registered port system:playback_10, offset = 0
++ jack_sort_graph
++ jack_rechain_graph():
+++ client is now alsa_pcm active ? 1
client alsa_pcm: internal client, execution_order=0.
-- jack_rechain_graph()
-- jack_sort_graph
16023 waiting for signals
ALSA: poll time out, polled for 16024472 usecs
DRIVER NT: could not run driver cycle
stopping driver
detaching driver
jack main caught signal 12
starting server engine shutdown
freeing shared port segments
server thread back from poll
stopping server thread
last xrun delay: 0.000 usecs
max usecs: 0.000, engine deleted
WARNING: 3 message buffer overruns!
cleaning up shared memory
cleaning up files
unregistering server `default'

$ jackd -vr -d alsa -d hw:0 -S
jackd 0.118.0
Copyright 2001-2009 Paul Davis, Stephane Letz, Jack O'Quinn, Torben Hohn and others.
jackd 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

getting driver descriptor from /usr/lib64/jack/jack_dummy.so
getting driver descriptor from /usr/lib64/jack/jack_net.so
getting driver descriptor from /usr/lib64/jack/jack_alsa.so
JACK compiled with System V SHM support.
server `default' registered
registered builtin port type 32 bit float mono audio
registered builtin port type 8 bit raw midi
clock source = system clock via clock_gettime
loading driver ..
start poll on 3 fd's
creating alsa driver ... hw:0|hw:0|1024|2|48000|0|0|nomon|swmeter|-|16bit
new client: alsa_pcm, id = 1 type 1 @ 0x7f2918001740 fd = -1
control device hw:0
configuring for 48000Hz, period = 1024 frames (21.3 ms), buffer = 2 periods
ALSA: final selected sample format for capture: 32bit integer little-endian
ALSA: use 2 periods for capture
ALSA: final selected sample format for playback: 32bit integer little-endian
ALSA: use 2 periods for playback
new buffer size 1024
registered port system:capture_1, offset = 4096
registered port system:capture_2, offset = 8192
registered port system:capture_3, offset = 12288
registered port system:capture_4, offset = 16384
registered port system:capture_5, offset = 20480
registered port system:capture_6, offset = 24576
registered port system:capture_7, offset = 28672
registered port system:capture_8, offset = 32768
registered port system:capture_9, offset = 36864
registered port system:capture_10, offset = 40960
registered port system:capture_11, offset = 45056
registered port system:capture_12, offset = 49152
registered port system:playback_1, offset = 0
registered port system:playback_2, offset = 0
registered port system:playback_4, offset = 0
registered port system:playback_5, offset = 0
registered port system:playback_6, offset = 0
registered port system:playback_7, offset = 0
registered port system:playback_8, offset = 0
registered port system:playback_9, offset = 0
registered port system:playback_10, offset = 0
++ jack_sort_graph
++ jack_rechain_graph():
+++ client is now alsa_pcm active ? 1
client alsa_pcm: internal client, execution_order=0.
-- jack_rechain_graph()
-- jack_sort_graph
16027 waiting for signals
ALSA: poll time out, polled for 32043065 usecs
DRIVER NT: could not run driver cycle
stopping driver
detaching driver
jack main caught signal 12
starting server engine shutdown
freeing shared port segments
server thread back from poll
stopping server thread
last xrun delay: 0.000 usecs
max usecs: 0.000, engine deleted
WARNING: 3 message buffer overruns!
cleaning up shared memory
cleaning up files
unregistering server `default'

$ jackd -d alsa -n 4
jackd 0.118.0
Copyright 2001-2009 Paul Davis, Stephane Letz, Jack O'Quinn, Torben Hohn and others.
jackd 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

JACK compiled with System V SHM support.
loading driver ..
creating alsa driver ... hw:0|hw:0|1024|4|48000|0|0|nomon|swmeter|-|32bit
control device hw:0
configuring for 48000Hz, period = 1024 frames (21.3 ms), buffer = 4 periods
ALSA: final selected sample format for capture: 32bit integer little-endian
ALSA: use 4 periods for capture
ALSA: final selected sample format for playback: 32bit integer little-endian
ALSA: use 4 periods for playback
jackd watchdog: timeout - killing jackd
Aborted

There are several references "poll time out" messages. I don't understand what jackd (or alsa) is waiting for, or why it isn't seeing it.

aCOSwt · Post by **aCOSwt** » Sat Mar 26, 2011 8:21 pm

earlyjp wrote:I have refrained from installing qjackctl until I was sure the underlying apps are working. It's the same reason I'm using Gentoo, in general. I'm trying to understand and test x before installing anything that depends on x. So far, it's worked well, and I'm learning a lot.

I understand this well.
However :
qjackctl brings a lot of advantages amongst which the fact that you can see and manage jack's connections to its clients.

In the traces you provide, it does seem that you get Xruns.

This makes Ant_P worrying about your latency, which could be a possibility.

I however do not think identically as your 21.3 ms latency reported is not that low. But I think that as soon as you launch jackd, jackd is overflown by requests from audio apps ? / drivers ? requests.
Of course, jackd's clients should be launched after jack.

So please do install qjackctl. From what you will report to us from what you can see on qjackctl's windows, it will be far easier for us to help you.

EDIT : BTW, if you get a non-empty one, can you post /etc/asound.conf and or your $HOME/.asoundrc

And do not worry about your ICE1712, it will work with jack !

earlyjp · Post by **earlyjp** » Sat Mar 26, 2011 8:39 pm

aCOSwt wrote: So please do install qjackctl. From what you will report to us from what you can see on qjackctl's windows, it will be far easier for us to help you.

Alright, I will do that and report the results. Thanks again for your assistance.

earlyjp · Post by **earlyjp** » Sat Mar 26, 2011 9:40 pm

Alright, qjackctl is now installed. I can report the following test results:

1) If I just open qjackctl and use only the default values (Realtime, rate=48000, frames=1024, periods=2, etc.), jackd reports errors as before, and the qjackctl interface becomes unresponsive, requiring a force close. The same is true if I select frames=512.

2) With frames=256, jackd still closes after a few seconds as before, but at least qjackctl continues to work. I can attempt to restart with different values, but as with the command line, there seem to be no combinations of arguments that satisfies jackd. Here are two examples -- one with frames=256, and the other with frames=128 and verbose mode:

Code: Select all

17:28:50.471 Patchbay deactivated.
17:28:50.472 Statistics reset.
17:28:50.478 ALSA connection graph change.
17:29:07.796 JACK is starting...
17:29:07.796 /usr/bin/jackd -dalsa -dhw:0 -r48000 -p256 -n2
jackd 0.118.0
Copyright 2001-2009 Paul Davis, Stephane Letz, Jack O'Quinn, Torben Hohn and others.
jackd 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
JACK compiled with System V SHM support.
17:29:07.800 JACK was started with PID=10545.
loading driver ..
apparent rate = 48000
creating alsa driver ... hw:0|hw:0|256|2|48000|0|0|nomon|swmeter|-|32bit
control device hw:0
configuring for 48000Hz, period = 256 frames (5.3 ms), buffer = 2 periods
ALSA: final selected sample format for capture: 32bit integer little-endian
ALSA: use 2 periods for capture
ALSA: final selected sample format for playback: 32bit integer little-endian
ALSA: use 2 periods for playback
17:29:10.107 JACK connection change.
17:29:10.107 Server configuration saved to "/home/earlyjp/.jackdrc".
17:29:10.108 Statistics reset.
17:29:10.118 Client activated.
17:29:10.120 JACK connection graph change.
ALSA: poll time out, polled for 8003367 usecs
DRIVER NT: could not run driver cycle
17:29:15.813 JACK connection graph change.
jack main caught signal 12
cannot continue execution of the processing graph (Broken pipe)
cannot continue execution of the processing graph (Broken pipe)
cannot continue execution of the processing graph (Broken pipe)
cannot continue execution of the processing graph (Broken pipe)
cannot continue execution of the processing graph (Broken pipe)
cannot continue execution of the processing graph (Broken pipe)
cannot continue execution of the processing graph (Broken pipe)
cannot continue execution of the processing graph (Broken pipe)
cannot continue execution of the processing graph (Broken pipe)
cannot continue execution of the processing graph (Broken pipe)
cannot continue execution of the processing graph (Broken pipe)
cannot continue execution of the processing graph (Broken pipe)
cannot continue execution of the processing graph (Broken pipe)
cannot continue execution of the processing graph (Broken pipe)
cannot continue execution of the processing graph (Broken pipe)
17:29:15.822 Client deactivated.
cannot continue execution of the processing graph (Broken pipe)
17:29:15.823 JACK was stopped successfully.
cannot continue execution of the processing graph (Broken pipe)
(line repeated many times)

17:33:19.831 Patchbay deactivated.
17:33:19.832 Statistics reset.
17:33:19.839 ALSA connection graph change.
17:33:47.443 JACK is starting...
17:33:47.443 /usr/bin/jackd -v -dalsa -dhw:0 -r48000 -p128 -n2
jackd 0.118.0
Copyright 2001-2009 Paul Davis, Stephane Letz, Jack O'Quinn, Torben Hohn and others.
jackd 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
getting driver descriptor from /usr/lib64/jack/jack_dummy.so
getting driver descriptor from /usr/lib64/jack/jack_net.so
getting driver descriptor from /usr/lib64/jack/jack_alsa.so
JACK compiled with System V SHM support.
server `default' registered
17:33:47.449 JACK was started with PID=10561.
registered builtin port type 32 bit float mono audio
registered builtin port type 8 bit raw midi
clock source = system clock via clock_gettime
loading driver ..
start poll on 3 fd's
apparent rate = 48000
creating alsa driver ... hw:0|hw:0|128|2|48000|0|0|nomon|swmeter|-|32bit
new client: alsa_pcm, id = 1 type 1 @ 0x609110 fd = -1
control device hw:0
configuring for 48000Hz, period = 128 frames (2.7 ms), buffer = 2 periods
ALSA: final selected sample format for capture: 32bit integer little-endian
ALSA: use 2 periods for capture
ALSA: final selected sample format for playback: 32bit integer little-endian
ALSA: use 2 periods for playback
new buffer size 128
registered port system:capture_1, offset = 512
registered port system:capture_2, offset = 1024
registered port system:capture_3, offset = 1536
registered port system:capture_4, offset = 2048
registered port system:capture_5, offset = 2560
registered port system:capture_6, offset = 3072
registered port system:capture_7, offset = 3584
registered port system:capture_8, offset = 4096
registered port system:capture_9, offset = 4608
registered port system:capture_10, offset = 5120
registered port system:capture_11, offset = 5632
registered port system:capture_12, offset = 6144
registered port system:playback_1, offset = 0
registered port system:playback_2, offset = 0
registered port system:playback_3, offset = 0
registered port system:playback_4, offset = 0
registered port system:playback_5, offset = 0
registered port system:playback_6, offset = 0
registered port system:playback_7, offset = 0
registered port system:playback_8, offset = 0
registered port system:playback_9, offset = 0
registered port system:playback_10, offset = 0
++ jack_sort_graph
++ jack_rechain_graph():
+++ client is now alsa_pcm active ? 1
client alsa_pcm: internal client, execution_order=0.
-- jack_rechain_graph()
-- jack_sort_graph
10561 waiting for signals
17:33:49.642 JACK connection change.
17:33:49.643 Server configuration saved to "/home/earlyjp/.jackdrc".
17:33:49.643 Statistics reset.
17:33:49.654 Client activated.
17:33:49.656 JACK connection graph change.
server thread back from poll
new client: qjackctl, id = 2 type 2 @ 0x7faacc526000 fd = 14
start poll on 4 fd's
server thread back from poll
new client qjackctl using 15 for events
start poll on 4 fd's
server thread back from poll
start poll on 4 fd's
server thread back from poll
start poll on 4 fd's
server thread back from poll
start poll on 4 fd's
server thread back from poll
start poll on 4 fd's
server thread back from poll
start poll on 4 fd's
server thread back from poll
start poll on 4 fd's
server thread back from poll
start poll on 4 fd's
server thread back from poll
start poll on 4 fd's
server thread back from poll
start poll on 4 fd's
server thread back from poll
start poll on 4 fd's
server thread back from poll
start poll on 4 fd's
server thread back from poll
start poll on 4 fd's
server thread back from poll
++ jack_sort_graph
++ jack_rechain_graph():
+++ client is now alsa_pcm active ? 1
client alsa_pcm: internal client, execution_order=0.
+++ client is now qjackctl active ? 1
client qjackctl: start_fd=7, execution_order=0.
client event poll on 15 for qjackctl starts at 3192971667
back from client event poll after 91 usecs
client qjackctl: wait_fd=11, execution_order=1 (last client).
-- jack_rechain_graph()
-- jack_sort_graph
start poll on 4 fd's
server thread back from poll
start poll on 4 fd's
server thread back from poll
start poll on 4 fd's
server thread back from poll
start poll on 4 fd's
server thread back from poll
start poll on 4 fd's
server thread back from poll
start poll on 4 fd's
server thread back from poll
start poll on 4 fd's
server thread back from poll
start poll on 4 fd's
server thread back from poll
start poll on 4 fd's
server thread back from poll
start poll on 4 fd's
server thread back from poll
start poll on 4 fd's
server thread back from poll
start poll on 4 fd's
server thread back from poll
start poll on 4 fd's
server thread back from poll
start poll on 4 fd's
start poll on 4 fd's
server thread back from poll
start poll on 4 fd's
server thread back from poll
start poll on 4 fd's
server thread back from poll
start poll on 4 fd's
server thread back from poll
start poll on 4 fd's
server thread back from poll
start poll on 4 fd's
server thread back from poll
start poll on 4 fd's
server thread back from poll
start poll on 4 fd's
server thread back from poll
start poll on 4 fd's
server thread back from poll
start poll on 4 fd's
server thread back from poll
start poll on 4 fd's
ALSA: poll time out, polled for 4011528 usecs
DRIVER NT: could not run driver cycle
stopping driver
detaching driver
17:33:51.469 JACK connection graph change.
client event poll on 15 for qjackctl starts at 3194786257
back from client event poll after 42 usecs
client event poll on 15 for qjackctl starts at 3194786312
back from client event poll after 8 usecs
client event poll on 15 for qjackctl starts at 3194786327
client event poll on 15 for qjackctl starts at 3194786346
back from client event poll after 11 usecs
client event poll on 15 for qjackctl starts at 3194786363
back from client event poll after 6 usecs
client event poll on 15 for qjackctl starts at 3194786376
back from client event poll after 6 usecs
client event poll on 15 for qjackctl starts at 3194786389
back from client event poll after 5 usecs
client event poll on 15 for qjackctl starts at 3194786400
back from client event poll after 6 usecs
client event poll on 15 for qjackctl starts at 3194786412
back from client event poll after 5 usecs
client event poll on 15 for qjackctl starts at 3194786422
back from client event poll after 6 usecs
client event poll on 15 for qjackctl starts at 3194786433
back from client event poll after 5 usecs
client event poll on 15 for qjackctl starts at 3194786444
back from client event poll after 5 usecs
client event poll on 15 for qjackctl starts at 3194786455
back from client event poll after 6 usecs
client event poll on 15 for qjackctl starts at 3194786466
back from client event poll after 6 usecs
client event poll on 15 for qjackctl starts at 3194786478
back from client event poll after 8 usecs
client event poll on 15 for qjackctl starts at 3194786492
back from client event poll after 5 usecs
client event poll on 15 for qjackctl starts at 3194786502
back from client event poll after 5 usecs
client event poll on 15 for qjackctl starts at 3194786513
back from client event poll after 5 usecs
client event poll on 15 for qjackctl starts at 3194786524
back from client event poll after 5 usecs
client event poll on 15 for qjackctl starts at 3194786535
back from client event poll after 19 usecs
client event poll on 15 for qjackctl starts at 3194786560
client event poll on 15 for qjackctl starts at 3194786574
back from client event poll after 9 usecs
jack main caught signal 12
starting server engine shutdown
freeing shared port segments
server thread back from poll
stopping server thread
stopping watchdog thread
last xrun delay: 0.000 usecs
max delay reported by backend: 0.000 usecs
freeing engine shared memory
max usecs: 0.000, engine deleted
WARNING: 3 message buffer overruns!
cleaning up shared memory
cleaning up files
unregistering server `default'
cannot continue execution of the processing graph (Broken pipe)
(again, repeated many times)

I hope this is instructive. Honestly, I'm at a loss as to what to try next. Perhaps there is some magic combination of arguments that will satisfy jackd, but given how many arguments there are, finding it would be a long shot.

Thanks to all who are reading this.
~Jim

aCOSwt · Post by **aCOSwt** » Sat Mar 26, 2011 9:50 pm

- (As far as you can know) Which jack clients are active before you launch jack ?
- Which jack clients are you launching ?
- Before launching jack from qjackctl, open the connection window, then start jack
Can you see links established then broken between what and what ?

EDIT : Please do post your /etc/asound.conf and / or $HOME/.asoundrc if they exist

EDIT2 : As far as I can see, you do not run jackd in realtime mode.
You definitely shlould.

earlyjp · Post by **earlyjp** » Sat Mar 26, 2011 9:53 pm

Hello again,
Just saw your edit...

aCOSwt wrote: EDIT : BTW, if you get a non-empty one, can you post /etc/asound.conf and or your $HOME/.asoundrc

And do not worry about your ICE1712, it will work with jack !

I do not have an /etc/asound.conf. Should I? I do have an /etc/asound.state, and that seems to have volume settings for the various channels in the Delta 44.

I do not have an ~/.asoundrc, either. Again, I'd be curious if it's needed, and why I don't have one. I do have a ~/.jackdrc that contains:

Code: Select all

/usr/bin/jackd -v -dalsa -dhw:0 -r48000 -p128 -n2

This would seem to be the last invocation of jackd via qjackctl.

I'm encouraged by your optimism!

earlyjp · Post by **earlyjp** » Sat Mar 26, 2011 11:55 pm

aCOSwt wrote:- (As far as you can know) Which jack clients are active before you launch jack ?
- Which jack clients are you launching ?
- Before launching jack from qjackctl, open the connection window, then start jack
Can you see links established then broken between what and what ?

EDIT : Please do post your /etc/asound.conf and / or $HOME/.asoundrc if they exist

EDIT2 : As far as I can see, you do not run jackd in realtime mode.
You definitely shlould.

Regarding the clients, there are no active clients, as far as I know. qjackctl is the only one I've installed. I did open the connection window, but never saw anything appear. I tried that several times.

I have tried this with and without realtime mode (both command line and qjackctl in my examples), but the response is the same -- can't keep jackd active. I'm not seeing anything in the jackd output that reports the state of realtime (unlike the other arguments). Do you?

Ant P. · Post by **Ant P.** » Sun Mar 27, 2011 2:30 am

Seems like this might be a driver problem with M-Audio chipsets. I don't have one myself, but I've had a few cards where jackd would only run with really specific settings. You might just need to try combinations until it works.

Also, try running jackd from a single-user-mode boot (you might need to start the alsasound initscript manually), that'll rule out the sound card being blocked by any other processes if nothing else.

aCOSwt · Post by **aCOSwt** » Sun Mar 27, 2011 8:38 am

1/ Try with these settings : On qjackctl settings tab : From top to bottom
-First row : +Real time +Soft Mode
-middle row : 89 / 256 / 48000 / 3 / 16 / dont care / dont care / 256 / 500 / 2
-Right row : hw:2 / Sinusoïd / playback only / default / default / default /default / default

2/ By the way, do adapt the interface message box to your hardware. But, if you did the things correctly in terms of kernel configuration + default alsa configuration and as I presume that you are likely to get some embedded hdaudio-like system, then your additional sound card is likely to be named hw:2
If I am wrong, do correct.
Note that I ask you to try with playback only first as you definitely seem to get things throwing data to jackd when it is not ready for. => Avoiding capture as a beginning will half our troubles.

3/ OF COURSE : DO ENSURE THAT NO OTHER SOUND SERVER (pulseaudio / esd....) IS RUNNING

4/ Of course, do ensure that your card's Multitrack Internal Clock is set appropriately for 48.000 Hz. There could be some mismatch here as if you set for jack a sampling rate different from the internal clock then jack will not be in sync with audio capture.

BTW : For the time being (until we ensure that basic settings and environment are OK) my opinion is that you can ignore the bug reported in the preceding post as I do not believe you get a ten years old hardware driven by a ten years old software...

earlyjp · Post by **earlyjp** » Sun Mar 27, 2011 4:53 pm

Ant P. wrote:Seems like this might be a driver problem with M-Audio chipsets. I don't have one myself, but I've had a few cards where jackd would only run with really specific settings. You might just need to try combinations until it works.

Also, try running jackd from a single-user-mode boot (you might need to start the alsasound initscript manually), that'll rule out the sound card being blocked by any other processes if nothing else.

There have been a number of issues related to these cards over the past 2-3 years, and you can find many posts from angry ICE1712 users on various forums. These cards were among the most highly recommended and supported when I bought mine -- what happened?

I like your idea about single user. I will try that and report back later.

earlyjp · Post by **earlyjp** » Sun Mar 27, 2011 5:14 pm

aCOSwt wrote:1/ Try with these settings : On qjackctl settings tab : From top to bottom
-First row : +Real time +Soft Mode
-middle row : 89 / 256 / 48000 / 3 / 16 / dont care / dont care / 256 / 500 / 2
-Right row : hw:2 / Sinusoïd / playback only / default / default / default /default / default

2/ By the way, do adapt the interface message box to your hardware. But, if you did the things correctly in terms of kernel configuration + default alsa configuration and as I presume that you are likely to get some embedded hdaudio-like system, then your additional sound card is likely to be named hw:2
If I am wrong, do correct.
Note that I ask you to try with playback only first as you definitely seem to get things throwing data to jackd when it is not ready for. => Avoiding capture as a beginning will half our troubles.

3/ OF COURSE : DO ENSURE THAT NO OTHER SOUND SERVER (pulseaudio / esd....) IS RUNNING

4/ Of course, do ensure that your card's Multitrack Internal Clock is set appropriately for 48.000 Hz. There could be some mismatch here as if you set for jack a sampling rate different from the internal clock then jack will not be in sync with audio capture.

BTW : For the time being (until we ensure that basic settings and environment are OK) my opinion is that you can ignore the bug reported in the preceding post as I do not believe you get a ten years old hardware driven by a ten years old software...

I thought I would report that I did try suggestion 1 -- still failing. And, again, it is the "poll time out" message. I should mention that I could not select the '16' option in middle row (greyed out), or the 'Sinusoid' option in right row (not in the pull down list). I'm not sure if that would make a difference.

Regarding suggestion 2, I did disable all on-board audio devices in the BIOS, specifically to help isolate this problem. So, the ICE1712 is hw:0 and the only audio device listed by lspci and aplay -l.

For suggestion 3, again I have not knowingly installed anything that could be trying to access the card. However, there was a suggestion to try this from single user mode, and I will try that.

Suggestion 4 is confirmed. Clock=48000.

aCOSwt · Post by **aCOSwt** » Sun Mar 27, 2011 5:23 pm

Why don't you first try to see if jack works with your on board audio ? This would definitely tell that you problem is ICE1712 specific ?

earlyjp · Post by **earlyjp** » Sun Mar 27, 2011 5:24 pm

Testing in single user mode failed with the same results. I am going to investigate what these "poll time out" messages mean.

earlyjp · Post by **earlyjp** » Mon Mar 28, 2011 11:31 pm

aCOSwt wrote:Why don't you first try to see if jack works with your on board audio ? This would definitely tell that you problem is ICE1712 specific ?

Good idea. I activated the HD Audio in the BIOS:

Code: Select all

$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: SB [HDA ATI SB], device 0: VT1708S Analog [VT1708S Analog]
  Subdevices: 2/2
  Subdevice #0: subdevice #0
  Subdevice #1: subdevice #1
card 0: SB [HDA ATI SB], device 1: VT1708S Digital [VT1708S Digital]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: M44 [M Audio Delta 44], device 0: ICE1712 multi [ICE1712 multi]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

Experimenting with various qjackctl combinations, I found the following:

1) I could start jackd using

Code: Select all

/usr/bin/jackd -dalsa -dhw:0,0 -r48000 -p512 -n2 -P

This is only playback on the analog channels, but at least jackd starts and continues to run.

2) Any other combination involving capture or duplex on either card fails with the same problem, as before. Some combinations would cause qjackctl to freeze.

On another note, I tried the LiveCD for AV Linux 4.2 (32 bit), and I could not start jackd in this distro, either -- same problem. Although, I only had the Delta 44 active at the time.

So, that's 3 distros (5 versions total) -- all exhibiting the same problem. It it worth trying to take this to the ALSA folks?

aCOSwt · Post by **aCOSwt** » Tue Mar 29, 2011 1:08 pm

can you confirm what I understand :

- Embedded sound system : Works only in playback-only mode
- ICE1712 : Never works, even in playback-only mode.

- Can you find and list the IRQs associated to your system.
- Can you put your AUDIO DELTA on another PCI slot

earlyjp · Post by **earlyjp** » Tue Mar 29, 2011 4:28 pm

aCOSwt wrote:can you confirm what I understand :

- Embedded sound system : Works only in playback-only mode
- ICE1712 : Never works, even in playback-only mode.

- Can you find and list the IRQs associated to your system.
- Can you put your AUDIO DELTA on another PCI slot

You are correct.

I will re-check the IRQs when I get home. I've checked them before, and I do not recall any contention. I haven't checked since activating the on-board sound, though.

I can try a new PCI slot. There are only two on the motherboard.

Here's a thought. Have you ever used the test number in Skype? You make a connection, record a short message, and then that message is played back to you. We could use a tool like that for ALSA and JACK -- a script that allows you to record and then playback on each channel. That would surely help me now.

Thanks for your continued interest!

aCOSwt · Post by **aCOSwt** » Tue Mar 29, 2011 5:33 pm

- About your suggestion : I do not think it would be helpful now. We are still yet stuck by a lower level problem.

- While you are at it, can you repost newer jackd's logs. (With your ICE1712 + playback only)

- You wrote that the resolution field was greyed. => What is the value fixed : 16 or something else ?

- A priori out of topic but... just in case... from your first posts I deduce that you did not enable anything regarding MIDI in your kernel. (wrong / correct ?)

- And... By the way... confirm that without jackd, playback and capture are correctly handled by your hardware.