I am trying to reproduce the problem you report, but for me everything's
working OK. Please clarify how what you're doing differs, so that we
can work on resolving your problems.
I do not know what "boot.iso wheezy image" you are referring to. I
tested with Chris Radek's "binary.hybrid.iso" downloaded according to
the instructions at
http://mid.gmane.org/20140722133743.GD33123%40timeguy.com
I downloaded a new version of the file this morning. The sha1sum of the
image is:
5fbb75f2c1cfabf1780f8e7f0bf07d75c07be0bd binary.hybrid.iso
(this image has been regenerated with linuxcnc 2.6.1, but to the best of
my knowledge nothing about locked memory has changed since Chris first
publicized the binary.hybrid.iso image on July 22)
I tested by running the image in qemu in my other Linux system:
$ qemu-system-i386 -enable-kvm -hda binary.hybrid.iso -m 768
Once it booted to the desktop, I opened a terminal and ran linuxcnc:
$ linuxcnc
selected the sample sim configuration axis.ini. LinuxCNC started and
ran without locked memory errors. (of course, I get realtime delay
errors but that is expected in a virtual machine)
I also could see that the max locked memory was set to 20480:
$ ulimit -l
20480
and that the expected settings were in /etc/security/limits.conf:
$ tail -1 /etc/security/limits.conf
* - memlock 20480 #EMC2
(sic)
I also installed from binary.hybrid.iso, still within qemu. Once booted
into the installed system, linuxcnc still started and all the locked
memory checks gave the same results.
Jeff
------------------------------------------------------------------------------
Infragistics Professional
Build stunning WinForms apps today!
Reboot your WinForms applications with our WinForms controls.
Build a bridge from your legacy apps to the future.
http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk
_______________________________________________
Emc-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-developers
