Tyler,

The cause the stopping is really that your disk doesn't write fast
enough. I have used Ardour to record from usb soundcards for a long time
- 8 hours of a session, 4 channels - and if I wanted to use the built
in HDD with NTFS on it it stopped because it can't write fast enough. I
haven't tried to set the memlimit, because I haven't need that, it is
just a warnig. Maybe if you use 32 ch and filled with real-time effects
you probably need that...

In some cases dyne at booting the correct DMA setting not recognised for
IDE HDD-s.
try to add ide=66 or ide=100 at the boot menu to kernel parameters.



Tyler Leavitt wrote:
> Hey. So I get the warning message when I start up Ardour2 (Dynebolic 2.5.2)
> about memory lock and checking "/etc/security/limits.conf" and using
> "ulimits -l" to check what my memlock is. Well... I originally had a memlock
> when I checked limits.conf that was really low (@audio memlock), and my
> ulimits -l output was 32. I tried changing the number to unlimited with no
> change (restarted comp). Then commented out the line all together,
> restarted, no change. And by no changes I mean ulimits -l still shows 32 and
> still get the Ardour warning at startup. After about 30 seconds of recording
> it stops and says isk can't write fast enough. Is there another
> "limits.conf" I'm missing? I toyed around with the 2 Jack settings for
> memory lock and unlimited memory to no results. Any help?
>
> Tyler
> _______________________________________________
> dyne:bolic GNU/Linux http://dynebolic.org
> open wiki http://lab.dyne.org/DynebolicFaq
>
>
>