[LAU] tracking down xruns

[david]

Dan S wrote:
> 2009/12/22 Josh Lawrence <hardbop200 at gmail.com>:
>> hey list,
>>
>> I've been struggling for the past couple of weeks trying to get my
>> netbook to perform well as a lightweight music workstation (mostly
>> synth work, light daw stuff).  I'm getting many, many xruns, clients
>> getting kicked, etc.  something is clearly not right.  how do I begin
>> tracking down the source of xruns?  I have an -rt kernel, a usb sound
>> card using -p256 -n3, running fluxbox with only wicd running to manage
>> my network.  point is, I've tried the hunt-and-peck method and
>> (surprise) it hasn't done any good.  how can I go about finding out
>> what exactly is tripping jack up, and what I can do to stop it?
> 
> Is your user a member of the audio group with rt permissions?
> 
> Have you tried pushing jackd's priority up? e.g. -P 70, on some
> systems I've seemed to need that.
> 
>> (PS - I've said it before:  maybe I'm expecting too much of a netbook.
>>  could that be it?)
> 
> No, lots of people have done good things on netbooks. You don't say
> which model you're on though.

I believe we have a list member regularly using his EEEPC quite well in 
performance, maybe he has some tips? I also seem to recall he had a link 
  where he put up his customized RT kernel packages optimized for EEEPC?

-- 
David
gnome at hawaii.rr.com
authenticity, honesty, community