[PlanetCCRMA] jack problem after recent system upgrade

Fernando Lopez-Lezcano nando@ccrma.Stanford.EDU
Mon Dec 19 10:00:02 2005


On Mon, 2005-12-19 at 08:09 -0500, Peter Lutek wrote:
> greetings!
> 
> i'm on an fc3 planet laptop, which was working flawlessly, until i 
> recently did a bunch of available upgrades. now jack won't start:
> 
>  >/usr/bin/jackd -R -dalsa -r44100 -p128 -n2 -D -Chw:1,0 -Phw:1,0
> jackd 0.99.36
> Copyright 2001-2003 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.
> cannot lock down memory for jackd (Cannot allocate memory)
> loading driver ..
> apparent rate = 44100
> creating alsa driver ... hw:1,0|hw:1,0|128|2|44100|0|0|nomon|swmeter|-|32bit
> control device hw:1
> configuring for 44100Hz, period = 128 frames, buffer = 2 periods
> nperiods = 2 for capture
> nperiods = 2 for playback
> JACK: unable to mlock() port buffers: Cannot allocate memory
> jack_create_thread: error -1 switching current thread to rt for 
> inheritance: Unknown error 4294967295
> cannot start watchdog thread
> cannot load driver module alsa
> Segmentation fault
> 
> is this possibly related to the pam upgrade? any other clues?
> 
> thanks very much.

What version of the kernel are you booting, and what is your current
version of pam?

  uname -r
  rpm -q pam

Does it start fine if you ommit the "-R" flag?
-- Fernando