Daniel James wrote: > Hi Ralf, > >> I often get the message "Cannot allocate memory", e.g. after starting >> Jack: > > Is your user a member of the audio group? Have you set a memlock value > in /etc/security/limits.conf ? (We now comment out the memlock by > default). > > Cheers! > > Daniel
64 Studio: @audio - rtprio 99 [EMAIL PROTECTED] - memlock 250000 [EMAIL PROTECTED] - nice -10 @audio - nice -19 Suse 11.0: @audio - rtprio 99 @audio - memlock unlimited @audio - nice -10 I didn't changed it and for Suse I set it to unlimited, I only changed the nice value for 64 Studio and I will change it for Suse 11.0 too, but that won't take effect to the memory problem. Maybe it's critical because 128 MB of my 2GB are used as frame buffer for the integrated ATI or because of my BIOS. Memtest got troubles with the memory, but no non-rt-audio application ever got trouble with the RAM. Another bizarre thing is, that Suse detects my CPU running at 1000MHz and sometimes up to 18000MHz. 64 Studio detected it always running correct with 21000MHz. Maybe the CPU will be clocked depending to the load and maybe this will take effect to the MIDI timing. I would say the user is in the group audio without checking if it's like this, but maybe something unwanted happend so I checked it and yes, the 64 Studio user is in the following $ groups spinymouse adm disk dialout cdrom floppy audio video plugdev netdev stb-admin powerdev scanner camera I tested Rosegarden with 64 Studio so this might not be the trouble and I'm shure, but I will check it too, that I'm also in the group audio for Suse. *?*
signature.asc
Description: OpenPGP digital signature
_______________________________________________ 64studio-users mailing list [email protected] http://lists.64studio.com/mailman/listinfo/64studio-users
