Gustin Johnson wrote: > Ralf Mardorf wrote: > <snip> > >> Increasingly reading the FAQ also means doing a basic google search, > >> though this has problems as typified by the so-called killall jackd > >> "problem". > > I can't see any hints how to solve this problem for my hardware. At the > > Because this is *not* a problem. You will see "killall jack" whenever > jack crashes. This particular message is part of the clean up process > to help ensure that there are no jack processes still running after a > crash. You need to look elsewhere to figure out what caused the actual > crash. > > So, ignore the killall jackd message, all it means is that jack crashed. > There are hundreds of ways of crashing jack, you need to figure out > what is wrong in your case.
It's OT for this thread. In my case (and for some others) it appears without rhyme or reason. For some people Linux audio was fine with a 32bit mobo and after only changing the mobo to a 64bit mobo, killall jackd appears at random. Also for me Linux audio worked with my old mobo, excepted that it was to slow with Linux for my needs. Because I'm using Linux for video, internet etc., even if I'm now making music with Windows, I always can test if a new kernel or something else might solve this problem. Searaching for the reason, without any clue isn't fun.
signature.asc
Description: OpenPGP digital signature
_______________________________________________ 64studio-users mailing list [email protected] http://lists.64studio.com/mailman/listinfo/64studio-users
