On 09/15/2012 08:04 AM, peter@xxxxxxxxxxxxxx wrote:
i've just switched over to jack1... it fails as well, with a different
error message (don't know if this sheds any more light on the situation!):
plutek@palnote:~$ jackd 0.122.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 = 44100
creating alsa driver ...
hw:0,0|hw:0,0|256|2|44100|0|0|nomon|swmeter|-|32bit
control device hw:0
configuring for 44100Hz, period = 256 frames (5.8 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: prepare error for playback on "hw:0,0" (Input/output error)
DRIVER NT: could not run driver cycle
**** alsa_pcm: xrun of at least 0.013 msecs
thanks again for any help on this!
ooops... getting rid of the extra -p flag, and going with -p1024, i get this:
plutek@palnote:~$ jackd -dalsa -r44100 -p1024 -n2 -D -Chw:0,0 -Phw:0,0&
[1] 3580
plutek@palnote:~$ jackd 0.122.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 = 44100
creating alsa driver ... hw:0,0|hw:0,0|1024|2|44100|0|0|nomon|swmeter|-|32bit
control device hw:0
configuring for 44100Hz, period = 1024 frames (23.2 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
All errors seem to point to a problem with interrupts. Somehow the
kernel is not handling interrupts from the soundcard, or the soundcard
is not generating them. Jack's driver waits for them and they never
arrive and as a result eventually the watchdog kills the whole thing in
the case of jack1.
Anything in /var/log/messages?
On 09/13/2012 11:24 AM, Peter Lutek wrote:
i suppose it's possible there's some weird interaction between the more
recent kernels and my ThinkPad T520.
That would seem to be the case, something must have changed in the newer
kernel versions. I'm successfully running a pci express card and
multiface II under 3.2.18-1.rt29.1.fc14.ccrma.i686.rtPAE in a Lenovo
T510 (older than yours).
-- Fernando
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user@xxxxxxxxxxxxxxxxxxxx
http://lists.linuxaudio.org/listinfo/linux-audio-user
