Patrick, Thanks for responding. The output in my previous message is from the 'Messages - JACK Audio Connection Kit' window. I start this from the Applications menu. If I run qjackclt from the command line, I get: :~$ qjackctl X Error: BadDevice, invalid or uninitialized input device 166 Major opcode: 144 Minor opcode: 3 Resource id: 0x0 Failed to open device X Error: BadDevice, invalid or uninitialized input device 166 Major opcode: 144 Minor opcode: 3 Resource id: 0x0 Failed to open device Warning: no locale found: /usr/share/locale/qjackctl_en_US.UTF-8.qm Any ideas? Dave Patrick Shirkey wrote:

You didn't answer to the first question, which I think is the major. You have three possibilities: 1) run everything as root, it might work then but not recommended; 2) run everything as regular user with realtime-lsm module loaded and properly setup; 3) run everything as regular user with pam security rlimits properly set; Bye. -- rncbc aka Rui Nuno Capela rncbc(a)rncbc.org

David Froseth wrote: Unbuntustudio.org might have something for you spending some time reading. I found this primordial url: https://help.ubuntu.com/community/UbuntuStudioPreparation Don't know if it will do on your particular case, but I guess you'll be on the right track in adding your regular username to the "audio" group and check whether your /etc/security/limits.conf file has something similar as I have on my opensuse boxes, like the following: @audio - rtprio 90 @audio - nice -10 @audio - memlock 4000000 Bye. -- rncbc aka Rui Nuno Capela rncbc(a)rncbc.org

David Froseth wrote: Is your username part of the "audio" group as I implied? -- rncbc aka Rui Nuno Capela rncbc(a)rncbc.org

Rui, I looked in /etc/group and found this in the list of groups: audio:x:29:dfro Is this what you are talking about? Thanks, Dave David Froseth wrote:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 David Froseth schrieb: I think it would, yet it would of course not get the best out of your processor so build a kernel from source may be th better way to get the thing working.

<delurk for a useless comment> Actually I found that barring it's daunting appearance, building a new kernel is a quite well documented and trivial procedure. Often it's just a question of following a step by step guide for the distribution in question. Granted if it goes wrong you better know what you are doing to get the boat afloat again... </> Robert/

Guys, I am not a total newcomer to the command line. I have been using the CLI for about two years. I have been installing, compiling, and using *nix programs, which have been ported over to OSX's X11. I have had a linux box (which I build into a server case, so I can take it to gigs) for about a month. I have found that linux is very similar to OSX command line, so everything has carried over (and sftp'ed and scp'ed over) easily. I am a newcomer to linux audio, though. The cd player works and I can hear sound in the headphones from the motherboard soundcard. Ardour is compiled and installed, and many of the other sound programs are installed and launch fine, but I am snagged by the jack/qjackctl thing. You can suggest command line stuff. I am sure there are big holes in my understanding, but I don't think I will accidentally erase my hard drive. My current status with jack, qjackctl is as follows. If I run 'jackd' from the command line, I get: $ jackd -d alsa 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. loading driver .. creating alsa driver ... hw:0|hw:0|1024|2|48000|0|0|nomon|swmeter|-|32bit control device hw:0 configuring for 48000Hz, period = 1024 frames, 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 It looks like jack is working. But when I next run 'qjackctl' from the command line, I get: $ qjackctl X Error: BadDevice, invalid or uninitialized input device 166 Major opcode: 144 Minor opcode: 3 Resource id: 0x0 Failed to open device X Error: BadDevice, invalid or uninitialized input device 166 Major opcode: 144 Minor opcode: 3 Resource id: 0x0 Failed to open device Warning: no locale found: /usr/share/locale/qjackctl_en_US.UTF-8.qm Also, the qjackctl GUI window launches and displays this message: 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. `default' server already active 14:01:59.752 JACK was stopped with exit status=1. 14:01:59.945 Could not connect to JACK server as client. Please check the messages window for more info. 14:02:05.182 MIDI connection change. qjackctl cannot connect to jack server as client. (?) Thanks for the help! Dave Paul Davis wrote:

Lee, I am running Ubuntu Edgy. I believe I compiled and installed JACK from source. I have version 'jackd 0.102.20'. Dave Lee Revell wrote:

please tell us what the output of this command is: locate libjack

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 David Froseth schrieb: cut this for now, once you got a usable kernel installed, and have alsa-seq working. you can start jackd Realtime as a normal user and start to find out what the system is all about. Further tuning is usefull and can give better overall performance but the basics must be established before. Plus: to set up the ubuntumusique-repo and having the kernel working is quite easy, before you apply further tuning, read, look, learn how the whole thing ticks. z