[LAU] jack no longer starting with Audiophile 2496 on desktop PC

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: linux-audio-user <linux-audio-user@...>
Date: Sunday, March 23, 2014 - 10:22 am

It was working. Now it's not. JACK starts up fine with the built-in
audio @ 96K and ~2.33msec latency. Doesn't work with 2496 @ 96K (or 48K)
at much higher latencies.

Using kernel 3.2.0-4 AMD64 Debian Sid via Aptosid, with and without RT;
also tried kernel 3.13 (non-RT).

I am a member of the audio group.

alsa-base shows v1.0.25+3, things like alsa-tools-gui report 1.0.27-2,
alsa-utils 1.027.2-1.

Starting from command line gives me this:

david@sempronbox:~$ /usr/bin/jackd -dalsa -dhw:M2496 -r96000 -p512 -n2
-Xseq
jackdmp 1.9.10
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2013 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
no message buffer overruns
JACK server starting in realtime mode with priority 10
audio_reservation_init
Acquire audio card Audio3
creating alsa driver ...
hw:M2496|hw:M2496|512|2|96000|0|0|nomon|swmeter|-|32bit
configuring for 96000Hz, period = 512 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
port created: Midi-Through:midi/playback_1
port created: Midi-Through:midi/capture_1
port created: E-MU-XMidi1X1:midi/playback_1
port created: E-MU-XMidi1X1:midi/capture_1
port created: M-Audio-Audiophile-24/96:midi/playback_1
port created: M-Audio-Audiophile-24/96:midi/capture_1
ALSA: poll time out, polled for 15999020 usecs
JackAudioDriver::ProcessAsync: read error, stopping...

^CJack main caught signal 2
port deleted: E-MU-XMidi1X1:midi/playback_1
port deleted: M-Audio-Audiophile-24/96:midi/playback_1
port deleted: Midi-Through:midi/playback_1
port deleted: E-MU-XMidi1X1:midi/capture_1
port deleted: M-Audio-Audiophile-24/96:midi/capture_1
port deleted: Midi-Through:midi/capture_1
Released audio card Audio3
audio_reservation_finish

Was doing it in previous 3.2 non RT kernel, updated to 3.13 kernel and
still doing it.

QJackCtl reports this:

21:24:33.243 Patchbay deactivated.
21:24:33.254 Statistics reset.
21:24:33.255 ALSA connection change.
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
21:24:39.134 Startup script...
21:24:39.135 artsshell -q terminate
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
sh: 1: artsshell: not found
21:24:39.537 Startup script terminated with exit status=32512.
21:24:39.537 JACK is starting...
21:24:39.537 /usr/bin/jackd -dalsa -dhw:M2496 -r96000 -p512 -n2 -Xseq
21:24:39.539 JACK was started with PID=4684.
no message buffer overruns
no message buffer overruns
no message buffer overruns
jackdmp 1.9.10
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2013 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
JACK server starting in realtime mode with priority 10
audio_reservation_init
Acquire audio card Audio3
creating alsa driver ...
hw:M2496|hw:M2496|512|2|96000|0|0|nomon|swmeter|-|32bit
configuring for 96000Hz, period = 512 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
port created: Midi-Through:midi/playback_1
port created: Midi-Through:midi/capture_1
port created: E-MU-XMidi1X1:midi/playback_1
port created: E-MU-XMidi1X1:midi/capture_1
port created: M-Audio-Audiophile-24/96:midi/playback_1
21:24:39.733 ALSA connection graph change.
port created: M-Audio-Audiophile-24/96:midi/capture_1
21:24:46.671 Could not connect to JACK server as client. - Overall
operation failed. - Server communication error. Please check the
messages window for more info.
JackPosixProcessSync::LockedTimedWait error usec = 5000000 err =
Connection timed out
Driver is not running
Cannot create new client
Cannot read socket fd = 16 err = Success
CheckRes error
JackSocketClientChannel read fail
Cannot open qjackctl client
21:24:48.496 JACK is stopping...
Jack main caught signal 15
ALSA: poll time out, polled for 15999021 usecs
JackAudioDriver::ProcessAsync: read error, stopping...
port deleted: E-MU-XMidi1X1:midi/playback_1
port deleted: M-Audio-Audiophile-24/96:midi/playback_1
port deleted: Midi-Through:midi/playback_1
port deleted: E-MU-XMidi1X1:midi/capture_1
port deleted: M-Audio-Audiophile-24/96:midi/capture_1
port deleted: Midi-Through:midi/capture_1
21:24:55.791 ALSA connection graph change.
Released audio card Audio3
audio_reservation_finish
21:24:55.923 JACK was stopped successfully.
21:24:55.928 Post-shutdown script...
21:24:55.929 killall jackd
jackd: no process found
21:24:56.335 Post-shutdown script terminated with exit status=256.

aplay -l shows this:

**** List of PLAYBACK Hardware Devices ****
card 0: SB [HDA ATI SB], device 0: VT1828S Analog [VT1828S Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: SB [HDA ATI SB], device 1: VT1828S Digital [VT1828S Digital]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: SB [HDA ATI SB], device 2: VT1828S Alt Analog [VT1828S Alt Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: HDMI [HDA ATI HDMI], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 3: M2496 [M Audio Audiophile 24/96], device 0: ICE1712 multi
[ICE1712 multi]
Subdevices: 1/1
Subdevice #0: subdevice #0

Figuring that maybe it was a piece of dead hardware, I booted a stock
Ubuntu 13.04 AMD64 live DVD, added JACK and some other pertinent stuff,
set it up with the same settings I use in the installed Aptosid setup -
and the damn thing worked.

Linux audio is very fragile, apparently.

Ideas?

--
David W. Jones
gnome@hawaii.rr.com
authenticity, honesty, community
http://dancingtreefrog.com
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user@lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-user

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

This is the only confirmed message in this thread.