Locked Memory problems
22 Jan 2013 08:24 #28937
by marsheng
Locked Memory problems was created by marsheng
I'm trying to get a Git version of linuxcnc working on Ubuntu 10.04
When I try to run linuxcnc after building it, I get this error message repeated a few times:
If I try to change memlock parameter using ulimit -l, I get the error:
bash: ulimit: max locked memory: cannot modify limit: Operation not permitted
And if I change the two files (attached) as recommended, nothing happens.
Is there any way round this?
When I try to run linuxcnc after building it, I get this error message repeated a few times:
RTAPI: Locked memory limit is 64KiB, recommended at least 20480KiB.
This can cause the error 'failed to map shmem'.
For more information, see
http://wiki.linuxcnc.org/cgi-bin/emcinfo.pl?LockedMemory
HAL: ERROR: could not open shared memory
halcmd: hal_init() failed: -22
NOTE: 'rtapi' kernel module must be loadedIf I try to change memlock parameter using ulimit -l, I get the error:
bash: ulimit: max locked memory: cannot modify limit: Operation not permitted
And if I change the two files (attached) as recommended, nothing happens.
Is there any way round this?
Please Log in or Create an account to join the conversation.
22 Jan 2013 11:24 #28938
by PCW
Replied by PCW on topic Locked Memory problems
What LinuxCNC version is this? There was a bug like this with 2.4 (fixed in 2.4.1)
Please Log in or Create an account to join the conversation.
22 Jan 2013 17:45 #28950
by ArcEye
Replied by ArcEye on topic Locked Memory problems
Hi
What git downloaded version are you running?
I had this several times with the master a few months back, it was actually nothing to do with memory, it didn't like the config I was using and threw up lots of spurious errors like this.
I gave up bothering with the master until it stabilised.
I currently have 2.6.0-pre0-3635-g0949c8a on a RIP and it runs OK (from a zip download not git)
regards
What git downloaded version are you running?
I had this several times with the master a few months back, it was actually nothing to do with memory, it didn't like the config I was using and threw up lots of spurious errors like this.
I gave up bothering with the master until it stabilised.
I currently have 2.6.0-pre0-3635-g0949c8a on a RIP and it runs OK (from a zip download not git)
regards
Please Log in or Create an account to join the conversation.
Time to create page: 0.432 seconds