On Sun, 2010-05-16 at 15:59 -0400, Rick Green wrote:
What sort of sound card do you have? This is starting to look like a
sound card problem, jack should not get zombified. What soundcard do you
have? What parameters did you use to start jack?
("cat /proc/asound/cards" to see which cards you have installed).
> I again launch qjackctl, and press the start button.
That is wrong. If jack is running you should not see anything from
> I leave it at the defaults, and press 'start audio engine'. It
Yup. Maybe as root? You should never use anything as root, there is no
need. Just start everything from the normal user (not root) that you
login as normally.
> So I think "Hey, they've improved Ardour, so I no longer need to use
Usually you don't need to reboot. I don't know why jack is having
> Now I launch Ardour, and let it start jack for me. I open a little test
Unlikely (there is some basic problem with jack).
> So I stop ardour, and then
I also would be sick of rebooting if I were in your shoes!
You should try the simplest possible way to start jack first, from the
command line of a terminal:
jackd -R -d alsa -d hw:0
That should start it with 1024 frames per period, 2 periods at 44100 Hz
sampling rate. See what happens when you do that. The problems you are
having suggests some issue with the soundcard, specially the hung jack
processes. Always run jackd as a normal user (not root).
You could also look at /var/log/messages or the output of dmesg to see
if there any kernel error messages like "Oops" or "BUG" statements.
Linux-audio-user mailing list