[PlanetCCRMA] Need help getting JACK working on FC8

Fri May 16 15:52:15 PDT 2008

Thanks Fernando,

That did it. JACK is working now.

I have a couple more questions to as you:

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).
Do I remove it with:
rpm -e planetccrma-testing
or...
yum remove planetccrma-testing
or something like that?

2. I'm getting an update notice for a Fedora kernel upgrade of the
2.6.24.6kernel, 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?

Paul

On Fri, May 16, 2008 at 4:21 AM, Fernando Lopez-Lezcano <
nando at ccrma.stanford.edu> wrote:

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

-- 
Kind Regards,

Paul Vallee
pv.vallee at gmail.com

.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://ccrma-mail.stanford.edu/pipermail/planetccrma/attachments/20080516/7eedfbae/attachment.html 