Kernel 2.6.26.8-rt13

[Free Ekanayaka-3]

Hi all,

according to my own tests and to the report on the list, I think
kernel 2.6.28 is not yet stable enough, rt/latency-wise.

So I've just finished packaging a new 2.6.26, with the latest RT
patch, and a further patch recently posted to the linux-rt mailing
list, which fixes an ALSA midi problem.

Full images and headers are available for both i386 and amd64, just
add:

deb http://apt.64studio.com/backports hardy-backports main

to your sources and run:

apt-get install linux-image-2.6.26-1-multimedia-686
apt-get install linux-headers-2.6.26-1-multimedia-686

for i386 or:

apt-get install linux-image-2.6.26-1-multimedia-amd64
apt-get install linux-headers-2.6.26-1-multimedia-amd64

for amd64, all as sudo.

Ciao!

Free
_______________________________________________
64studio-devel mailing list
64studio-devel@...
http://lists.64studio.com/mailman/listinfo/64studio-devel

[dave-322]

Free Ekanayaka wrote:

> Hi all,
>
> according to my own tests and to the report on the list, I think
> kernel 2.6.28 is not yet stable enough, rt/latency-wise.
>
> So I've just finished packaging a new 2.6.26, with the latest RT
> patch, and a further patch recently posted to the linux-rt mailing
> list, which fixes an ALSA midi problem.
>
> Full images and headers are available for both i386 and amd64, just
> add:
>
> deb http://apt.64studio.com/backports hardy-backports main
>
> to your sources and run:
>
> apt-get install linux-image-2.6.26-1-multimedia-686
> apt-get install linux-headers-2.6.26-1-multimedia-686
>
> for i386 or:
>
> apt-get install linux-image-2.6.26-1-multimedia-amd64
> apt-get install linux-headers-2.6.26-1-multimedia-amd64
>
> for amd64, all as sudo.
>
> Ciao!
>
> Free
>  

Hi, :-)

for i386 on 3.0 alpha install

apt-get install linux-image-2.6.26-1-multimedia-686
apt-get install linux-headers-2.6.26-1-multimedia-686

This gives the best results yet here of the latest test kernels,
qjackctl idles around 2.4%.  With ardour running  = 9.3%
I will run some more tests, but first impressions are very good.

Cheers!
dave.



_______________________________________________
64studio-devel mailing list
64studio-devel@...
http://lists.64studio.com/mailman/listinfo/64studio-devel

[Quentin Harley-2]

> This gives the best results yet here of the latest test kernels,
> qjackctl idles around 2.4%.  With ardour running  = 9.3%
> I will run some more tests, but first impressions are very good.


My sentiment exactly!

My "old" Centrino laptop is running a mastering session with 26 - 30% CPU
usage only.

This is the best kernel so far.  Can't wait to test it on my AMD64x2 at home.

This also bodes well for the 2.6.28 kernel once the RT patches start
becoming available

Cheers,
Quentin

_______________________________________________
64studio-devel mailing list
64studio-devel@...
http://lists.64studio.com/mailman/listinfo/64studio-devel

[Jaromír Mikeš]

<  Hi all,
<  
<  according to my own tests and to the report on the list, I think
<  kernel 2.6.28 is not yet stable enough, rt/latency-wise.
<  
<  So I've just finished packaging a new 2.6.26, with the latest RT
<  patch, and a further patch recently posted to the linux-rt mailing
<  list, which fixes an ALSA midi problem.
<  
<  Full images and headers are available for both i386 and amd64, just
<  add:
<  
<  deb http://apt.64studio.com/backports hardy-backports main
<  
<  to your sources and run:
<  
<  apt-get install linux-image-2.6.26-1-multimedia-686
<  apt-get install linux-headers-2.6.26-1-multimedia-686
<  
<  for i386 or:
<  
<  apt-get install linux-image-2.6.26-1-multimedia-amd64
<  apt-get install linux-headers-2.6.26-1-multimedia-amd64
<  
<  for amd64, all as sudo.
<  
<  Ciao!
<  
<  Free

Hello,

unfortunately I have to report some system freezes with runing jack on my 2.1 etch/lenny system.

freezes with these jack's settings:

/usr/bin/jackd -R -p128 -t5000 -dalsa -r44100 -p16 -n3 -D -Chw:0 -Phw:0 -i2 -o2 -Xseq
/usr/bin/jackd -R -p128 -t5000 -dalsa -r44100 -p32 -n3 -D -Chw:0 -Phw:0 -i2 -o2 -Xseq
/usr/bin/jackd -R -p128 -t5000 -dalsa -r44100 -p64 -n3 -D -Chw:0 -Phw:0 -i2 -o2 -Xseq

seems to be fine with
/usr/bin/jackd -R -p128 -t5000 -dalsa -r44100 -p128 -n3 -D -Chw:0 -Phw:0 -i2 -o2 -Xseq

Not heavily loaded Ardour session used for testing ... no plugins at all.

Cheers

mira

PS: I will test latter 3.0 Alpha
 
_______________________________________________
64studio-devel mailing list
64studio-devel@...
http://lists.64studio.com/mailman/listinfo/64studio-devel

[Gustin Johnson]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

� wrote:

>
> Hello,
>
> unfortunately I have to report some system freezes with runing jack on my 2.1 etch/lenny system.
>
> freezes with these jack's settings:
>
> /usr/bin/jackd -R -p128 -t5000 -dalsa -r44100 -p16 -n3 -D -Chw:0 -Phw:0 -i2 -o2 -Xseq
> /usr/bin/jackd -R -p128 -t5000 -dalsa -r44100 -p32 -n3 -D -Chw:0 -Phw:0 -i2 -o2 -Xseq
> /usr/bin/jackd -R -p128 -t5000 -dalsa -r44100 -p64 -n3 -D -Chw:0 -Phw:0 -i2 -o2 -Xseq
>
> seems to be fine with
> /usr/bin/jackd -R -p128 -t5000 -dalsa -r44100 -p128 -n3 -D -Chw:0 -Phw:0 -i2 -o2 -Xseq
>
> Not heavily loaded Ardour session used for testing ... no plugins at all.

Are we talking about the new 2.6.26 kernel?  What sound card is this?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAklv+pIACgkQwRXgH3rKGfPVpACfZt6vn5k9C7cGWLQyx/bZnQcU
IpMAn2LV0eeiqjy2M08k0DF9CutL0yiA
=nzIP
-----END PGP SIGNATURE-----
_______________________________________________
64studio-devel mailing list
64studio-devel@...
http://lists.64studio.com/mailman/listinfo/64studio-devel

[Gabriel M. Beddingfield]

Free Ekanayaka wrote:
> according to my own tests and to the report on the list, I think
> kernel 2.6.28 is not yet stable enough, rt/latency-wise.
>
> So I've just finished packaging a new 2.6.26, with the latest RT
> patch, and a further patch recently posted to the linux-rt mailing
> list, which fixes an ALSA midi problem.

Tonight... I played with all 3 kernels (2.6.21 64-studio kernel, 2.6.26.8-rt13,
and 2.6.28).  They all worked fine for me, and I couldn't really tell much
difference in performance.

Hardware is PIII 500MHz ~384MB RAM.  I tried a comb. of
ZynAddSubFx+Ardour+Hydrogen play/record... and didn't get any xruns in any of
the 3 kernels.  I was able to set ZynAddSubFx to a patch that caused xruns --
but that was only because the patch was pegging the processor (i.e. not a RT issue).

Thanks for the good work!  I'll switch to 2.6.26 like everyone else and watch
for problems.

-Gabriel


_______________________________________________
64studio-devel mailing list
64studio-devel@...
http://lists.64studio.com/mailman/listinfo/64studio-devel

[Daniel James-2]

Hi Mira,

> unfortunately I have to report some system freezes with runing jack on my 2.1 etch/lenny system.
>
> freezes with these jack's settings:
>
> /usr/bin/jackd -R -p128 -t5000 -dalsa -r44100 -p16 -n3 -D -Chw:0 -Phw:0 -i2 -o2 -Xseq
> /usr/bin/jackd -R -p128 -t5000 -dalsa -r44100 -p32 -n3 -D -Chw:0 -Phw:0 -i2 -o2 -Xseq
> /usr/bin/jackd -R -p128 -t5000 -dalsa -r44100 -p64 -n3 -D -Chw:0 -Phw:0 -i2 -o2 -Xseq

Those settings are quite weird, you are running two different -p
settings per command line, for example.

Also, -p16 is extremely low latency, I would expect that to cause
problems. Try something like:

/usr/bin/jackd -R -dalsa -dhw:0 -r44100 -p256 -n3

then if that works OK try -p128 and see if you get xruns.

I personally use -r44100 with -p128 -n2 for tracking (and -p256 -n2 for
mastering) with a Delta 1010, but -n3 for any USB or onboard sound
chipset which only opens at -r48000.

> PS: I will test latter 3.0 Alpha

Please do, and try Free's new 2.6.26 RT kernel with it. We need lots of
testing on that combination, as it's likely to be the basis of the 3.0
beta release.

Cheers!

Daniel
_______________________________________________
64studio-devel mailing list
64studio-devel@...
http://lists.64studio.com/mailman/listinfo/64studio-devel

[Jaromír Mikeš]

Hi,

<  > unfortunately I have to report some system freezes with runing jack on my 2.1
<  etch/lenny system.
<  >
<  > freezes with these jack's settings:
<  >
<  > /usr/bin/jackd -R -p128 -t5000 -dalsa -r44100 -p16 -n3 -D -Chw:0 -Phw:0 -i2
<  -o2 -Xseq
<  > /usr/bin/jackd -R -p128 -t5000 -dalsa -r44100 -p32 -n3 -D -Chw:0 -Phw:0 -i2
<  -o2 -Xseq
<  > /usr/bin/jackd -R -p128 -t5000 -dalsa -r44100 -p64 -n3 -D -Chw:0 -Phw:0 -i2
<  -o2 -Xseq
<  
<  Those settings are quite weird, you are running two different -p
<  settings per command line, for example.

These settings are copy/paste from my .jackdrc file

<  
<  Also, -p16 is extremely low latency, I would expect that to cause
<  problems.

Yes I now ... I tried it just for testing, usually my jack running fine from -p64 and higher with 2.6.21-rt and my own build kernel 2.6.24.7-rt20.

< Try something like:
<  
<  /usr/bin/jackd -R -dalsa -dhw:0 -r44100 -p256 -n3
<  
<  then if that works OK try -p128 and see if you get xruns.
<  
<  I personally use -r44100 with -p128 -n2 for tracking (and -p256 -n2 for
<  mastering) with a Delta 1010, but -n3 for any USB or onboard sound
<  chipset which only opens at -r48000.

I made a test on onboard card ...so -n3 should be ok for me

latter on I got freeze also with -p128

I did all tests with Nvidia proprietary driver 180.22 on.

Now I switched to free driver and I was able to run jack with -p16 ... some xruns, but not freezes even I tried to provoke them.
And lower system load then my older kernels.

Maybe someone else should confirm or dis-confirm my experience with nvidia 180.22 and 2.6.26.8-rt13 on 686.

mira
   
BTW: any link for xruns definition? I would like to understand more..
What does it mean the red numbers in brackets?


<  
<  > PS: I will test latter 3.0 Alpha
<  
<  Please do, and try Free's new 2.6.26 RT kernel with it. We need lots of
<  testing on that combination, as it's likely to be the basis of the 3.0
<  beta release.
<  
<  Cheers!
<  
<  Daniel
<  
<  
<  
_______________________________________________
64studio-devel mailing list
64studio-devel@...
http://lists.64studio.com/mailman/listinfo/64studio-devel

[Lincoln Spiteri]

The first -p before the driver definition is the number of jack ports IIRC.

On Fri, Jan 16, 2009 at 11:43 AM, Daniel James <daniel@...> wrote:

Hi Mira,

unfortunately I have to report some system freezes with runing jack on my 2.1 etch/lenny system.

freezes with these jack's settings:

/usr/bin/jackd -R -p128 -t5000 -dalsa -r44100 -p16 -n3 -D -Chw:0 -Phw:0 -i2 -o2 -Xseq
/usr/bin/jackd -R -p128 -t5000 -dalsa -r44100 -p32 -n3 -D -Chw:0 -Phw:0 -i2 -o2 -Xseq
/usr/bin/jackd -R -p128 -t5000 -dalsa -r44100 -p64 -n3 -D -Chw:0 -Phw:0 -i2 -o2 -Xseq

Those settings are quite weird, you are running two different -p settings per command line, for example.

Also, -p16 is extremely low latency, I would expect that to cause problems. Try something like:

/usr/bin/jackd -R -dalsa -dhw:0 -r44100 -p256 -n3

then if that works OK try -p128 and see if you get xruns.

I personally use -r44100 with -p128 -n2 for tracking (and -p256 -n2 for mastering) with a Delta 1010, but -n3 for any USB or onboard sound chipset which only opens at -r48000.

PS: I will test latter 3.0 Alpha

Please do, and try Free's new 2.6.26 RT kernel with it. We need lots of testing on that combination, as it's likely to be the basis of the 3.0 beta release.

Cheers!

Daniel

_______________________________________________
64studio-devel mailing list
64studio-devel@...
http://lists.64studio.com/mailman/listinfo/64studio-devel

_______________________________________________
64studio-devel mailing list
64studio-devel@...
http://lists.64studio.com/mailman/listinfo/64studio-devel

[dave-322]

Jaromír Mikeš wrote:

> Hi,
>
> I did all tests with Nvidia proprietary driver 180.22 on.
>
> Now I switched to free driver and I was able to run jack with -p16 ...
> some xruns, but not freezes even I tried to provoke them.
> And lower system load then my older kernels.
> Maybe someone else should confirm or dis-confirm my experience with
> nvidia 180.22 and 2.6.26.8-rt13 on 686.
>
> mira

Hi Mira,

When I first installed 3.0 alpha I stayed with the "nv" driver for quite
some time and it worked fine.
I am running the 2.6.26.8-rt13 now and using NVIDIA-Linux-x86-173.14.12.
This kernel and graphics driver are working well together for me.
I can use a newer nVidia driver but the one above gives me the best
gui/audio balance.
I haven't tried the nvidia 180.22 but the ones previous to this I've tested
and newer is not always better for my computer needs here.

Cheers!
dave.


_______________________________________________
64studio-devel mailing list
64studio-devel@...
http://lists.64studio.com/mailman/listinfo/64studio-devel

[Daniel James-2]

Hi Lincoln,

> The first -p before the driver definition is the number of jack ports IIRC.

You're quite right, I checked the man page and it's for the maximum
number of ports - how weird to use the same switch for two completely
different things!

I normally leave this setting on the default of 256 in qjackctl, so it
doesn't show up in my jackd command line.

Cheers!

Daniel
_______________________________________________
64studio-devel mailing list
64studio-devel@...
http://lists.64studio.com/mailman/listinfo/64studio-devel

[Daniel James-2]

Hi Mira,

> I did all tests with Nvidia proprietary driver 180.22 on.
>
> Now I switched to free driver and I was able to run jack with -p16 ...
> some xruns, but not freezes even I tried to provoke them.
> And lower system load then my older kernels.

Ah ha...

> Maybe someone else should confirm or dis-confirm my experience with
> nvidia 180.22 and 2.6.26.8-rt13 on 686.

That would be helpful.

>   BTW: any link for xruns definition? I would like to understand more..
> What does it mean the red numbers in brackets?

According to:
http://www.linuxmao.org/tikiwiki/tiki-pagehistory.php?page=Jack&preview=52

"The bracketed one is the xrun callback count as reported by libjack,
taking qjackctl as a client. The other one (outside the brackets) are
the xrun count as detected by the brute-force method of lurking/parsing
the literal jackd stdout/stderr captured output."

Cheers!

Daniel
_______________________________________________
64studio-devel mailing list
64studio-devel@...
http://lists.64studio.com/mailman/listinfo/64studio-devel

[Jaromír Mikeš]

<  > unfortunately I have to report some system freezes with runing jack on my 2.1
<  etch/lenny system.
<  >
<  > freezes with these jack's settings:
<  >
<  > /usr/bin/jackd -R -p128 -t5000 -dalsa -r44100 -p16 -n3 -D -Chw:0 -Phw:0 -i2
<  -o2 -Xseq
<  > /usr/bin/jackd -R -p128 -t5000 -dalsa -r44100 -p32 -n3 -D -Chw:0 -Phw:0 -i2
<  -o2 -Xseq
<  > /usr/bin/jackd -R -p128 -t5000 -dalsa -r44100 -p64 -n3 -D -Chw:0 -Phw:0 -i2
<  -o2 -Xseq
<  >
<  > seems to be fine with
<  > /usr/bin/jackd -R -p128 -t5000 -dalsa -r44100 -p128 -n3 -D -Chw:0 -Phw:0 -i2
<  -o2 -Xseq
<  >
<  > Not heavily loaded Ardour session used for testing ... no plugins at all.
<  
<  Are we talking about the new 2.6.26 kernel?  What sound card is this?

Hello Gustin,

yes we are talking about new  2.6.26.8-rt13 .... and card is just simple on-board Intel card  .


Cheers

mira
_______________________________________________
64studio-devel mailing list
64studio-devel@...
http://lists.64studio.com/mailman/listinfo/64studio-devel

[Jaromír Mikeš]

<  >   BTW: any link for xruns definition? I would like to understand more..
<  > What does it mean the red numbers in brackets?
<  
<  According to:
<  http://www.linuxmao.org/tikiwiki/tiki-pagehistory.php?page=Jack&preview=52

french sites? ;-) english pls.

mira

_______________________________________________
64studio-devel mailing list
64studio-devel@...
http://lists.64studio.com/mailman/listinfo/64studio-devel

[Jaromír Mikeš]

<  > Hi,
<  >
<  > I did all tests with Nvidia proprietary driver 180.22 on.
<  >
<  > Now I switched to free driver and I was able to run jack with -p16 ...
<  > some xruns, but not freezes even I tried to provoke them.
<  > And lower system load then my older kernels.
<  > Maybe someone else should confirm or dis-confirm my experience with
<  > nvidia 180.22 and 2.6.26.8-rt13 on 686.
<  >
<  > mira
<  
<  
<  Hi Mira,
<  
<  When I first installed 3.0 alpha I stayed with the "nv" driver for quite
<  some time and it worked fine.
<  I am running the 2.6.26.8-rt13 now and using NVIDIA-Linux-x86-173.14.12.
<  This kernel and graphics driver are working well together for me.
<  I can use a newer nVidia driver but the one above gives me the best
<  gui/audio balance.
<  I haven't tried the nvidia 180.22 but the ones previous to this I've tested
<  and newer is not always better for my computer needs here.
<  
<  Cheers!
<  dave.
<  

Thank you for report Dave ... :-)
_______________________________________________
64studio-devel mailing list
64studio-devel@...
http://lists.64studio.com/mailman/listinfo/64studio-devel

[Jaromír Mikeš]

Hello,

3.0 Alpha and kernel 2.6.26.8-rt13 test

jack setting - (.jackdrc file) /usr/bin/jackd -R -dalsa -r44100 -p2048 -n3 -D -Chw:0 -Phw:0

graphic - free driver "ati"

Having xruns with ardour session with just one plugin (TAP reverbator)


I can't compare with other kernel because ...as I reported before :

>my notebook sometimes stop booting on the line
>drivers/usb/input/hid-core.c: v2.6:USB HID core driver

it is getting worse now ... it happens every time with 2.6.21-multimedia kernel :-(
when I am booting my builded kernel 2.6.24.7-21rt process ending with line:

waiting for root file system ...

I was running similar sessions like above on 2.6.21-multimedia kernel with -p64 or -p128 without problems.

Don't know if it is important:
my installation is upgrade from fresh 2.1studio not latest 3.0 Alpha iso

Cheers

mira



_______________________________________________
64studio-devel mailing list
64studio-devel@...
http://lists.64studio.com/mailman/listinfo/64studio-devel

[Daniel James-2]

Hi Mira,

> 3.0 Alpha and kernel 2.6.26.8-rt13 test
>
> jack setting - (.jackdrc file) /usr/bin/jackd -R -dalsa -r44100 -p2048
> -n3 -D -Chw:0 -Phw:0
>
> graphic - free driver "ati"
>
> Having xruns with ardour session with just one plugin (TAP reverbator)

Do you get the same problem with:

/usr/bin/jackd -R -dalsa -dhw:0 -r44100 -p2048 -n3

?

How about -p256 -n3 or -p256 -n2 ?

Cheers!

Daniel
_______________________________________________
64studio-devel mailing list
64studio-devel@...
http://lists.64studio.com/mailman/listinfo/64studio-devel

[Jaromír Mikeš]

<  > 3.0 Alpha and kernel 2.6.26.8-rt13 test
<  >
<  > jack setting - (.jackdrc file) /usr/bin/jackd -R -dalsa -r44100 -p2048
<  > -n3 -D -Chw:0 -Phw:0
<  >
<  > graphic - free driver "ati"
<  >
<  > Having xruns with ardour session with just one plugin (TAP reverbator)
<  
<  Do you get the same problem with:
<  
<  /usr/bin/jackd -R -dalsa -dhw:0 -r44100 -p2048 -n3
<  
<  ?

Hi Daniel,

yes ...

mira@64studio:~$ /usr/bin/jackd -R -dalsa -dhw:0 -r44100 -p2048 -n3
jackdmp 0.71
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2008 Grame.
jackdmp 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
ALSA: final selected sample format for capture: 32bit little-endian
ALSA: use 3 periods for capture
ALSA: final selected sample format for playback: 32bit little-endian
ALSA: use 3 periods for playback
JackEngine::XRun: client = ardour was not run: state = 2
JackAudioDriver::ProcessAsync Process error
JackEngine::XRun: client = ardour was not run: state = 2
JackAudioDriver::ProcessAsync Process error
JackEngine::XRun: client = ardour was not run: state = 1
JackAudioDriver::ProcessAsync Process error
JackEngine::XRun: client = ardour was not run: state = 1

<  
<  How about -p256 -n3 or -p256 -n2 ?
<  

-p256 going worse
-n2 going worst

Cheers

mira
_______________________________________________
64studio-devel mailing list
64studio-devel@...
http://lists.64studio.com/mailman/listinfo/64studio-devel

[Jaromír Mikeš]

<  > Hi,
<  >
<  > I did all tests with Nvidia proprietary driver 180.22 on.
<  >
<  > Now I switched to free driver and I was able to run jack with -p16 ...
<  > some xruns, but not freezes even I tried to provoke them.
<  > And lower system load then my older kernels.
<  > Maybe someone else should confirm or dis-confirm my experience with
<  > nvidia 180.22 and 2.6.26.8-rt13 on 686.
<  >
<  > mira
<  
<  
<  Hi Mira,
<  
<  When I first installed 3.0 alpha I stayed with the "nv" driver for quite
<  some time and it worked fine.
<  I am running the 2.6.26.8-rt13 now and using NVIDIA-Linux-x86-173.14.12.
<  This kernel and graphics driver are working well together for me.
<  I can use a newer nVidia driver but the one above gives me the best
<  gui/audio balance.
<  I haven't tried the nvidia 180.22 but the ones previous to this I've tested
<  and newer is not always better for my computer needs here.
<  
<  Cheers!
<  dave.
<  

Hi all,

my machine1 2.1 studio etch/lenny

2.6.26.8-rt13 and NVIDIA-Linux-x86-177.82 running nicely now here.

Testing sesion in Ardour ...4 plugins .. drum sequence running in loop ... 2 tracks

maximiser
limiter
2x plate reverb

jack settings (copy/paste jackdrc file) :

/usr/bin/jackd -R -p128 -t5000 -dalsa -r44100 -p128 -n3 -D -Chw:0 -Phw:0 -i2 -o2 -Xseq
 
1) kernel 2.6.21
DSP load 13-15% sometimes spike 20%

2) kernel 2.6.26
DSP load 11-13% no spikes

In both cases on second desktop rotating globe in google earth ..... ;-)

########################################################

I got one other freeze when I was playing with 2.6.26...
I've got work webcam with this kernel ... very first time ...
When I unplug USB of webcam my system got frozen

cheers

mira
_______________________________________________
64studio-devel mailing list
64studio-devel@...
http://lists.64studio.com/mailman/listinfo/64studio-devel

[Gustin Johnson]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jaromír Mikeš wrote:

> Hello Gustin,
>
> yes we are talking about new  2.6.26.8-rt13 .... and card is just
> simple on-board Intel card  .
>
My first suggestion would be to use more conservative jack settings.
Integrated Intels get sketchy at low latency.  On my laptop I have found
that qjackctl's estimated latency should go no lower than 21 msec.  In
the 40 msec range it is pretty stable.

On my Desktop I have an RME 9652 that is stable down in the 5 msec
range, so lower latency is possible, just possibly not with your
hardware.  This may improve with newer kernels (and thus updated
drivers), but I would not expect too much out of the integrated crowd.

You can change the latency by manipulating the Frames/Period and
Periods/Buffer options in qjackctl.

Hth,
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFJcRL/wRXgH3rKGfMRAgFIAJwIeUHG9PJepCTdFsmsCSKKoJY+oQCgm11p
QVufUh19CeXBBaKt3dh+iPY=
=7aHp
-----END PGP SIGNATURE-----
_______________________________________________
64studio-devel mailing list
64studio-devel@...
http://lists.64studio.com/mailman/listinfo/64studio-devel