[Ardour-Users] Jack problems in Fiesty PPC

Matthew Polashek matt at tinysongs.com
Wed Aug 1 15:16:02 PDT 2007


I still can't get Jack to start on Ubuntu Feisty for PPC.  any takers? 
Here's the log.




18:14:14.453 Patchbay deactivated.
18:14:14.652 Statistics reset.
18:14:15.169 MIDI connection graph change.
18:14:15.171 MIDI connection change.
18:14:39.994 Startup script...
18:14:39.994 artsshell -q terminate
can't create mcop directory
Creating link /home/matthew/.kde/socket-matthew-laptop.
18:14:40.757 Startup script terminated with exit status=256.
18:14:40.758 JACK is starting...
18:14:40.758 jackd -v -dalsa -r44100 -p1024 -n2 -D -Chw:0,0 -Phw:0,0 -i1 -o1
18:14:40.839 JACK was started with PID=6873 (0x1ad9).
getting driver descriptor from /usr/lib/libjack0.100.0/jack_freebob.so
getting driver descriptor from /usr/lib/libjack0.100.0/jack_dummy.so
getting driver descriptor from /usr/lib/libjack0.100.0/jack_oss.so
getting driver descriptor from /usr/lib/libjack0.100.0/jack_alsa.so
jackd 0.102.20
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.
server `default' registered
loading driver ..
apparent rate = 44100
creating alsa driver ...
hw:0,0|hw:0,0|1024|2|44100|1|1|nomon|swmeter|-|32bit
control device hw:0
configuring for 44100Hz, period = 1024 frames, buffer = 2 periods
Sorry. The audio interface "hw:0,0" doesn't support any of the hardware
sample formats that JACK's alsa-driver can use.
ALSA: cannot configure capture channel
cannot load driver module alsa
registered builtin port type 32 bit float mono audio
registered builtin port type 8 bit raw midi
clock source = system clock via gettimeofday
required capabilities not available
capabilities: = cap_ipc_lock,cap_sys_nice+e
new client: alsa_pcm, id = 1 type 1 @ 0x10026f28 fd = -1
starting server engine shutdown
freeing shared port segments
stopping server thread
last xrun delay: 0.000 usecs
max delay reported by backend: 0.000 usecs
freeing engine shared memory
max usecs: 0.000, engine deleted
no message buffer overruns
cleaning up shared memory
cleaning up files
unregistering server `default'
18:14:41.840 JACK was stopped successfully.
18:14:42.150 Post-shutdown script...
18:14:42.152 killall jackd
jackd: no process killed
18:14:42.414 Post-shutdown script terminated with exit status=256.
18:14:43.194 Could not connect to JACK server as client. Please check
the messages window for more info.



More information about the Ardour-Users mailing list