Thanks Fernando,<br><br>That did it. JACK is working now.<br><br>I have a couple more questions to as you:<br><br>1. Now that I've got the planetccrma kernel, JACK and the apps packages installed and apparently working, I'm thinking that I should probably remove the planetccrma testing repository from my Yum configuration (I only needed it to install the testing kernel).<br>
Do I remove it with:<br>rpm -e planetccrma-testing<br>or...<br>yum remove planetccrma-testing<br>or something like that?<br><br>2. I'm getting an update notice for a Fedora kernel upgrade of the <a href="http://2.6.24.6">2.6.24.6</a> kernel, which is the planetccrma kernel that I installed from the planetccrma testing repo. Should I apply this upgrade or will it cause problems for me?<br>
<br>Paul<br><br><div class="gmail_quote">On Fri, May 16, 2008 at 4:21 AM, Fernando Lopez-Lezcano <<a href="mailto:nando@ccrma.stanford.edu">nando@ccrma.stanford.edu</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><div></div><div class="Wj3C7c">On Thu, 2008-05-15 at 22:39 -0700, Paul Vallee wrote:<br>
> hmm, as I was saying...<br>
><br>
> When I try to startup jack with the JACK Audio Connection Kit I get<br>
> the following output in the messages window:<br>
><br>
> With realtime option selected in Setup:<br>
> 21:05:23.603 Patchbay deactivated.<br>
> 21:05:23.680 Statistics reset.<br>
> 21:05:23.796 ALSA connection graph change.<br>
> 21:05:23.924 ALSA connection change.<br>
> 21:07:48.630 Startup script...<br>
> 21:07:48.631 artsshell -q terminate<br>
> 21:07:49.078 Startup script terminated with exit status=256.<br>
> 21:07:49.082 JACK is starting...<br>
> 21:07:49.084 /usr/bin/jackd -R -P70 -dalsa -dhw:0 -r48000 -p64 -n2 -m<br>
> jackd 0.109.12<br>
> Copyright 2001-2005 Paul Davis and others.<br>
> jackd comes with ABSOLUTELY NO WARRANTY<br>
> This is free software, and you are welcome to redistribute it<br>
> under certain conditions; see the file COPYING for details<br>
> JACK compiled with System V SHM support.<br>
> 21:07:49.124 JACK was started with PID=6336.<br>
> loading driver ..<br>
> Enhanced3DNow! detected<br>
> SSE2 detected<br>
> apparent rate = 48000<br>
> creating alsa driver ... hw:0|hw:0|64|2|48000|0|0|nomon|swmeter|-|<br>
> 32bit<br>
> control device hw:0<br>
> configuring for 48000Hz, period = 64 frames (1.3 ms), buffer = 2<br>
> periods<br>
> ALSA: final selected sample format for capture: 32bit little-endian<br>
> ALSA: use 2 periods for capture<br>
> ALSA: final selected sample format for playback: 32bit little-endian<br>
> ALSA: use 2 periods for playback<br>
> **** alsa_pcm: xrun of at least 0.055 msecs<br>
> **** alsa_pcm: xrun of at least 0.072 msecs<br>
> ... many more xruns ...<br>
<br>
</div></div>What hardware do you have? You should not have that many xruns. If it is<br>
an hda intel based card you have to have at least 3 buffers instead of 2<br>
as you have now.<br>
<div class="Ih2E3d"><br>
> 21:07:51.150 Could not connect to JACK server as client. - Overall<br>
> operation failed. - Unable to connect to server. Please check the<br>
> messages window for more info.<br>
<br>
</div>Hmmm, probably a library problem. You are running the "testing" version<br>
of jack and I imagine that has a problem in x86_64 (although other users<br>
have installed before). I would suggest you revert to the "stable"<br>
version.<br>
<br>
To do that you could:<br>
- disable the repo files installed by planetccrma-repo-testing<br>
- "rpm -e --nodeps jack-audio-connection-kit.i386"<br>
- "rpm -e --nodeps jack-audio-connection-kit.x86_64"<br>
(you have two packages because you have the i386 and x86_64 version<br>
installed).<br>
- yum install jack-audio-connection-kit<br>
<font color="#888888"><br>
-- Fernando<br>
</font><div><div></div><div class="Wj3C7c"><br>
<br>
<br>
<br>
> ... many more xruns ...<br>
> ... and so I stop it ...<br>
> 21:07:55.842 JACK is stopping...<br>
> **** alsa_pcm: xrun of at least 0.042 msecs<br>
> jack main caught signal 15<br>
> no message buffer overruns<br>
> 21:07:55.893 JACK was stopped successfully.<br>
> 21:07:55.895 Post-shutdown script...<br>
> 21:07:55.897 killall jackd<br>
> jackd: no process killed<br>
> 21:07:56.365 Post-shutdown script terminated with exit status=256.<br>
><br>
> With realtime option unselected in Setup:<br>
> 21:21:59.084 Patchbay deactivated.<br>
> 21:21:59.262 Statistics reset.<br>
> 21:21:59.395 ALSA connection graph change.<br>
> 21:21:59.480 ALSA connection change.<br>
> 21:22:10.464 Startup script...<br>
> 21:22:10.465 artsshell -q terminate<br>
> 21:22:10.911 Startup script terminated with exit status=256.<br>
> 21:22:10.913 JACK is starting...<br>
> 21:22:10.913 /usr/bin/jackd -dalsa -dhw:0 -r48000 -p64 -n2 -m<br>
> 21:22:10.937 JACK was started with PID=6398.<br>
> jackd 0.109.12<br>
> Copyright 2001-2005 Paul Davis and others.<br>
> jackd comes with ABSOLUTELY NO WARRANTY<br>
> This is free software, and you are welcome to redistribute it<br>
> under certain conditions; see the file COPYING for details<br>
> JACK compiled with System V SHM support.<br>
> loading driver ..<br>
> Enhanced3DNow! detected<br>
> SSE2 detected<br>
> apparent rate = 48000<br>
> creating alsa driver ... hw:0|hw:0|64|2|48000|0|0|nomon|swmeter|-|<br>
> 32bit<br>
> control device hw:0<br>
> configuring for 48000Hz, period = 64 frames (1.3 ms), buffer = 2<br>
> periods<br>
> ALSA: final selected sample format for capture: 32bit little-endian<br>
> ALSA: use 2 periods for capture<br>
> ALSA: final selected sample format for playback: 32bit little-endian<br>
> ALSA: use 2 periods for playback<br>
> **** alsa_pcm: xrun of at least 0.491 msecs<br>
> **** alsa_pcm: xrun of at least 0.075 msecs<br>
> ... many more xruns ...<br>
> 21:22:13.000 Could not connect to JACK server as client. - Overall<br>
> operation failed. - Unable to connect to server. Please check the<br>
> messages window for more info.<br>
> ... many more xruns ...<br>
> ... so I stop it ...<br>
> 21:22:16.732 JACK is stopping...<br>
> **** alsa_pcm: xrun of at least 0.058 msecs<br>
> jack main caught signal 15<br>
> no message buffer overruns<br>
> 21:22:16.779 JACK was stopped successfully.<br>
> 21:22:16.784 Post-shutdown script...<br>
> 21:22:16.785 killall jackd<br>
> jackd: no process killed<br>
> 21:22:17.230 Post-shutdown script terminated with exit status=256.<br>
><br>
> The only difference I can see is that JACK was reported to have<br>
> actually started with the realtime option turned off but not when it<br>
> was turned on. In either case though, the client could not connect to<br>
> the server.<br>
><br>
> Here's my setup:<br>
><br>
> JACK Audio Connection Kit version:<br>
> rpm -q jack-audio-connection-kit<br>
> jack-audio-connection-kit-0.109.12-0.svn1135_942.1.fc8.ccrma<br>
> jack-audio-connection-kit-0.109.12-0.svn1135_942.1.fc8.ccrma<br>
> - there seems to be 2 of them! Maybe because I have 2 versions of the<br>
> planetccma kernel installed. Could this cause problems?<br>
><br>
> planetccrma kernel version:<br>
> 2.6.24.6-1.rt3.4.fc8.ccrmart.x86_64<br>
><br>
> I have the following lines at the bottom of<br>
> the /etc/security/limits.conf<br>
> ## Automatically appended by the Planet CCRMA<br>
> jack-audio-connection-kit<br>
> * - rtprio 99<br>
> * - memlock 4194304<br>
> * - nice -10<br>
><br>
> Snippets from /var/log/messages that might be relevant:<br>
> May 15 14:12:06 localhost kernel: Linux version<br>
> 2.6.24.6-1.rt3.4.fc8.ccrmart (<a href="mailto:mockbuild@cm-matlab.stanford.edu">mockbuild@cm-matlab.stanford.edu</a>) (gcc<br>
> version 4.1.2 20070925 (Red Hat 4.1.2-33)) #1 SMP PREEMPT RT Tue May 6<br>
> 16:44:13 EDT 2008<br>
> ...<br>
> May 15 14:12:06 localhost kernel: Real-Time Preemption Support (C)<br>
> 2004-2007 Ingo Molnar<br>
> ...<br>
> May 15 14:12:06 localhost kernel: Clockevents: could not switch to<br>
> one-shot mode:<6>Clockevents: could not switch to one-shot mode: lapic<br>
> is not functional.<br>
> May 15 14:12:06 localhost kernel: Could not switch to high resolution<br>
> mode on CPU 0<br>
> May 15 14:12:06 localhost kernel: lapic is not functional.<br>
> May 15 14:12:06 localhost kernel: Could not switch to high resolution<br>
> mode on CPU 1<br>
> ...<br>
> May 15 14:12:06 localhost kernel: Clockevents: could not switch to<br>
> one-shot mode:<6>Clockevents: could not switch to one-shot mode: lapic<br>
> is not functional.<br>
> May 15 14:12:06 localhost kernel: Could not switch to high resolution<br>
> mode on CPU 1<br>
> May 15 14:12:06 localhost kernel: lapic is not functional.<br>
> May 15 14:12:06 localhost kernel: Could not switch to high resolution<br>
> mode on CPU 0<br>
> ...<br>
> May 15 14:12:06 localhost kernel: ALSA sound/pci/hda/hda_intel.c:732:<br>
> codec_mask = 0x1<br>
> ...<br>
> May 15 14:12:06 localhost kernel: Clocksource tsc unstable (delta =<br>
> -62578070 ns)<br>
> ...<br>
> May 15 14:12:55 localhost pulseaudio[3053]: main.c: This program is<br>
> not intended to be run as root (unless --system is specified).<br>
> May 15 14:12:56 localhost pulseaudio[3053]: alsa-util.c: Device (null)<br>
> doesn't support 44100 Hz, changed to 48000 Hz.<br>
> May 15 14:12:56 localhost pulseaudio[3053]: alsa-util.c: Device (null)<br>
> doesn't support 44100 Hz, changed to 48000 Hz.<br>
> May 15 14:12:56 localhost pulseaudio[3053]: alsa-util.c: Cannot find<br>
> fallback mixer control "Mic".<br>
> ...<br>
> May 15 14:16:53 localhost pulseaudio[3354]: polkit.c: Failed to show<br>
> grant dialog: Unable to lookup exe for caller<br>
> May 15 14:16:53 localhost pulseaudio[3354]: polkit.c: PolicyKit<br>
> responded with 'auth_admin_keep_always'<br>
> May 15 14:16:53 localhost pulseaudio[3354]: main.c:<br>
> setrlimit(RLIMIT_NICE, (31, 31)) failed: Operation not permitted<br>
> May 15 14:16:53 localhost pulseaudio[3354]: alsa-util.c: Device (null)<br>
> doesn't support 44100 Hz, changed to 48000 Hz.<br>
> May 15 14:16:53 localhost pulseaudio[3354]: alsa-util.c: Device (null)<br>
> doesn't support 44100 Hz, changed to 48000 Hz.<br>
> May 15 14:16:53 localhost pulseaudio[3354]: alsa-util.c: Cannot find<br>
> fallback mixer control "Mic".<br>
> ...<br>
><br>
> I hope this is is enough information to spark some ideas about how to<br>
> get JACK working on my machine.<br>
><br>
> --<br>
<br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Kind Regards,<br><br>Paul Vallee<br><a href="mailto:pv.vallee@gmail.com">pv.vallee@gmail.com</a><br><br>.