"On SuSE, you need to do a 'make cloneconfig' before the 'make menuconfig' and all the rest. This is easily forgotten, usually giving you a kernel that doesn't work."
Something I didn't know. However it didn't do the trick quite yet as the resulting kernel was still borked. I'll try a "make distclean" and start again.
That sounds like you're sources are still misconfigured. I had this effect on an AMD system as well, and only with SuSE 9.0. The symptom was some unresolved symbols when trying to load the reiserfs module, resulting in a kernel panic at boot time because the root fs could not be mounted. Try a "make mrproper" in /usr/src/linux and go through the entire configure/build process again. You should be able to get more info by scribbling down the kernel panic message and googling for it. Good luck!
I take the point about capabilities being of no use if you can't run jackd with realtime anyway. I just guessed that capabilities might allow me to run jackd with realtime in the first place
The cap patch lets you run jackd (using the jackstart wrapper program) with realtime priorities without having to run it as root. If jack does run as root (using sudo, setsuid or whatever) you get the same effect without having to patch the kernel.
On my SuSE 9.0 system, this makes a *great* difference. I still have some gripes using SuperCollider with Jack, when the system is under high load, but all in all Jack runs very smooth at low latencies.
Albert
-- Dr. Albert Gr"af Dept. of Music-Informatics, University of Mainz, Germany Email: [EMAIL PROTECTED], [EMAIL PROTECTED] WWW: http://www.musikwissenschaft.uni-mainz.de/~ag
