[PlanetCCRMA] Failing to start jack for some reasons...

[Fernando Lopez-Lezcano]

On Sat, 2007-09-01 at 18:11 +0100, Michael TD Nelson wrote:
> Hi all,
> 
> I did post this to the Linux-Audio-User list, but I forgot to put a
> subject on it, and no-one replied anyway. Sorry for the bandwidth waste,
> but I would like to sort this out, so I can start having some fun.
> 
> I haven't posted here for some time now. I've been busy at work, but
> finally, I have a linux box together that works again... It's a long
> story.
> 
> Still, I have a problem. When I started jack on my first RME soundcard,
> it worked fine. However, I've added a second RME card, and now I'm
> having problems starting jack on either of them.
> 
> The machine is an Athlon64 3200 on an MSI nForce4 board. I'm running an
> up-to-date Planet CCRMA on Fedora Core 6. The first soundcard (that did
> work in this machine) is an RME DIGI9636, and the second is an RME 96/8
> PAD.
> 
> Both cards are second-hand, but I have seen each of them working before
> - the DIGI9636 was used previously with FC3 a year ago, and the 96/8 PAD
> was working in a Windows machine earlier today.
> 
> I'm using qjackctl. Here is an excerpt of the messages as I attempt to
> start jack on the DIGI9636:
> 
> *****
> 
> 04:01:22.393 JACK is starting...
> 04:01:22.393 jackd -R -dalsa -r48000 -p1024 -n2 -D -Chw:0,0 -Phw:0,0 -i2
> -o2

You should not try to tell jack exactly what to do :-), I would just use
the "interface" field in qjackctl to select "hw:0", remove the entries
from the "input device" and "output device" fields, and let jack figure
out the number of channels (ie: set "input channels" and "output
channels" to 0). 

> 04:01:22.395 JACK was started with PID=3488 (0xda0).
> jackd 0.103.0
> Copyright 2001-2005 Paul Davis 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 ..
> Enhanced3DNow! detected
> SSE2 detected
> apparent rate = 48000
> creating alsa driver ... hw:0,0|hw:0,0|1024|2|48000|2|2|nomon|swmeter|-|
> 32bit
> control device hw:0
> configuring for 48000Hz, period = 1024 frames, buffer = 2 periods
> ALSA: final selected sample format for capture: 32bit little-endian
> ALSA: cannot set channel count to 2 for capture
> ALSA: cannot configure capture channel

Apparently the capture channel does not have exactly 2 channels...

Completely reasonable if this is the 9636.

> cannot load driver module alsa
> no message buffer overruns
> 04:01:22.640 JACK was stopped successfully.
> 04:01:22.640 Post-shutdown script...
> 04:01:22.640 killall jackd
> jackd: no process killed
> 04:01:22.874 Post-shutdown script terminated with exit status=256.
> 04:01:24.408 Could not connect to JACK server as client. Please check
> the messages window for more info.
> JACK tmpdir identified as [/dev/shm]
> 04:04:06.538 Startup script...
> 04:04:06.539 artsshell -q terminate
> JACK tmpdir identified as [/dev/shm]
> 04:04:06.782 Startup script terminated with exit status=256.
> 
> *****
> 
> And here is the output for the 96/8 PAD. This one gives a lot of xruns.
> If attempting to start 'real-time', it just stops again straight away,
> as follows:
> 
> *****
> 
> 04:04:06.783 JACK is starting...
> 04:04:06.783 jackd -R -dalsa -r48000 -p1024 -n2 -D -Chw:1 -Phw:1 -i2 -o2
> 04:04:06.797 JACK was started with PID=3610 (0xe1a).
> jackd 0.103.0
> Copyright 2001-2005 Paul Davis 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 ..
> Enhanced3DNow! detected
> SSE2 detected
> apparent rate = 48000
> creating alsa driver ... hw:1|hw:1|1024|2|48000|2|2|nomon|swmeter|-|
> 32bit
> control device hw:1
> configuring for 48000Hz, period = 1024 frames, buffer = 2 periods
> ALSA: final selected sample format for capture: 32bit little-endian
> ALSA: use 8 periods for capture
> ALSA: final selected sample format for playback: 32bit little-endian
> ALSA: use 8 periods for playback

Hmmm, there is some conflict with the number of periods you are
specifying?

> 04:04:08.893 Server configuration saved to "/home/nels/.jackdrc".
> 04:04:08.895 Statistics reset.
> 04:04:09.507 Client activated.
> 04:04:09.509 Audio connection change.
> 04:04:09.521 Audio connection graph change.
> 04:04:09.531 XRUN callback (1).
> JACK tmpdir identified as [/dev/shm]
> Enhanced3DNow! detected
> SSE2 detected
> 04:04:11.518 XRUN callback (45 skipped).
> jackd watchdog: timeout - killing jackd

This is different, apparently jack is not (probably) receiving
interrupts from the card, the watchdog process times out and kills
everything. 

-- Fernando


> zombified - calling shutdown handler
> 04:04:11.926 Shutdown notification.
> 04:04:11.926 Client deactivated.
> 04:04:11.927 JACK was stopped successfully.
> 04:04:11.927 Post-shutdown script...
> 04:04:11.927 killall jackd
> cannot read result for request type 7 from server (Connection reset by
> peer)
> cannot send request type 7 to server
> cannot read result for request type 7 from server (Broken pipe)
> jackd: no process killed
> 04:04:12.146 Post-shutdown script terminated with exit status=256.
> 
> *****
> 
> Where should I start? Am I doing something obviously/stupidly wrong?
> Please let me know what other information might help.