New problem with jackd in dream studio
 

Have spent about 15 hours looking at jackd questions everywhere, but this seems to be a different issue, and hopefully simple- I am not that 'new' to Linux, but my actual time at the terminal is low.....very low, and there is a lot I haven't covered yet.
So- I start the machine, Dream Studio starts jackd at boot. But jackd fails to run. Jackd message looks like this;
17:54:22.109 Logging started --- Tue Jan 3 17:54:22 2012 ---
17:54:22.237 Patchbay activated.
17:54:22.250 Statistics reset.
17:54:22.266 Startup script...
17:54:22.267 pausepulse
17:54:22.271 ALSA connection graph change.
E: main.c: Failed to kill daemon: No such process
17:54:25.107 Startup script terminated with exit status=256.
17:54:25.108 JACK is starting...
17:54:25.108 /usr/bin/jackd -p1024 -t5000 -dalsa -dhw:0 -r44100 -p1024 -n4 -o1 -Xseq
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
17:54:25.151 JACK was started with PID=1643.
17:54:25.332 ALSA active patchbay scan...
17:54:25.333 ALSA connection change.
no message buffer overruns
JACK compiled with System V SHM support.
17:54:25.569 ALSA active patchbay scan...
loading driver ..
apparent rate = 44100
creating alsa driver ... hw:0|hw:0|1024|4|44100|0|1|nomon|swmeter|-|32bit
control device hw:0
configuring for 44100Hz, period = 1024 frames (23.2 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: cannot set channel count to 1 for playback
ALSA: cannot configure playback channel
cannot load driver module alsa
17:54:26.589 JACK was stopped successfully.
17:54:26.590 Post-shutdown script...
17:54:26.590 killall jackd
jackd: no process found
17:54:27.197 Post-shutdown script terminated with exit status=256.
17:54:27.599 Could not connect to JACK server as client. - Overall operation failed. - Unable to connect to server. Please check the messages window for more info.

So it seems there may be a problem with ALSA, or JACKD has a problem with ALSA? It looks like jackd was updated just before the failure, it did originally work to the limited extent I understood it.
If the jackd update doesn't play well with unupdated ALSA, I have no idea how to revert it. I am grateful in advance for any help offered!!

This file may help, if your system has it /etc/sound/README

Also, how did you update ALSA? with apt-get, Synaptic or...?

Solved... "New" Problem with jackd in Dream Studio
 

Still learning... But just last night I tried another cofiguration of jack, latest of literally hundreds of attempts. No luck. I have been making it worse instead of better, and the message window got shorter, ending with "Sorry, can not start jack".... Then I once more reconfigured it as it was when I copied and pasted the original message. Of course it failed with basically the same message.
While (once again) reading through the message window, I noticed "ALSA can not resolve one channel" (paraphr.)So I setup jack once again and specified 2 channels. Problem solved, even though I thought I had done that before...
To answer your question,I believe jack was updated automatically with system updater, though I wasn't paying close attention when it happened, there were a bunch of updates at the time, and one 'security update' seemed to be having problems downloading (I think) because the wireless connection was shutting down whenever the macine would go into power save mode/ screensaver..
(this is a 'laptop' intel 950 chip 64 bit intel integrated HDA sound. But I am running all 32 bit linux software)
I hope this helps someone else, even though the issue was minor, it was impossible to record audio with jack not properly set up. There are still sound issues, for instance the tiny onboard speaker won't work, testing the sound in system tests results in a hang with "waiting for sound to respond", but the headphone output and soundcard midi has worked fine, even when jack was not running. I am still working to resolve an issue with "system timer resolution too low, 240hz" as well. "sudo ......... snd-rtctimer" results in "fatal,module not found" message. Probably the subject of another question/thread....
I'll be happy to provide what little info I have garnered if anyone has a question, and thanks for the response!!!
Jim