I also found the following information in the print and debug files *machinekit@beaglebone:~$ cat /tmp/linuxcnc.debug* Can not find -sec DISPLAY -var INTRO_GRAPHIC -num 1 2511 PID TTY STAT TIME COMMAND Stopping realtime threads Unloading hal components
*machinekit@beaglebone:~$ cat /tmp/linuxcnc.print* RUN_IN_PLACE=yes LINUXCNC_DIR= LINUXCNC_BIN_DIR=/media/machinekit/rootfs/home/debian/machinekit/bin LINUXCNC_TCL_DIR=/media/machinekit/rootfs/home/debian/machinekit/tcl LINUXCNC_SCRIPT_DIR= LINUXCNC_RTLIB_DIR=/media/machinekit/rootfs/home/debian/machinekit/rtlib LINUXCNC_CONFIG_DIR= LINUXCNC_LANG_DIR=/media/machinekit/rootfs/home/debian/machinekit/src/objects INIVAR=/media/machinekit/rootfs/home/debian/machinekit/libexec/inivar HALCMD=halcmd LINUXCNC_EMCSH=/usr/bin/wish8.6 INIFILE=/opt/nectar-apps/machinekit-config/nectar-dd-02.ini PARAMETER_FILE=./pru-stepper.var TASK=milltask HALUI= DISPLAY=tkemc Starting Machinekit server program: linuxcncsvr Loading Real Time OS, RTAPI, and HAL_LIB modules Starting Machinekit IO program: io Killing task linuxcncsvr, PID=2511 Op woensdag 24 mei 2017 09:48:15 UTC+2 schreef michelvand...@gmail.com: > > Hello All, > I compiled a vanilla machinekit from git using the steps outlined in : > http://www.machinekit.io/docs/developing/machinekit-developing/ > > It had a problem with protobuf not understanding "syntax" in > lib/python/machinetalk/protobuf/nanopb_pb2.py, which I read is related to > which version protobuf is being used. I have protobuf 3.3.0 on the image i > downloaded. > I commented these two syntax lines out, because it automaticly chooses > version2 the lines said. > > Compilation went without any problem afterwards. > > I did the "sudo make setuid" > > when I go to the scripts folder I run ". ./rip-environment", that goes ok. > > But when I try to start machinekit with ./machinekit my.ini it dies with > the following messages : > > May 24 06:45:50 beaglebone rtapi:0: rtapi_app:0: ERROR: cannot attach > global segment key=0x154711 No such file or directory > May 24 06:45:50 beaglebone rtapi:0: rtapi:0: FATAL - failed to attach to > global segment > May 24 06:47:10 beaglebone msgd:0: startup pid=2421 flavor=xenomai > rtlevel=1 usrlevel=1 halsize=524288 shm=Posix cc=gcc 4.9.2 > version=v0.1~-detached~b1ad179 > May 24 06:47:10 beaglebone msgd:0: ØMQ=4.0.5 czmq=2.2.0 protobuf=2.6.1 > atomics=gcc intrinsics libwebsockets=<no version symbol> > May 24 06:47:10 beaglebone msgd:0: configured: sha=b1ad179 > May 24 06:47:10 beaglebone msgd:0: built: May 18 2017 17:11:51 > sha=b1ad179 > May 24 06:47:10 beaglebone msgd:0: register_stuff: actual hostname as > announced by avahi='beaglebone.local' > May 24 06:47:10 beaglebone msgd:0: zeroconf: registering: 'Log service on > beaglebone.local pid 2421' > May 24 06:47:11 beaglebone msgd:0: zeroconf: registered 'Log service on > beaglebone.local pid 2421' _machinekit._tcp 0 TXT > "uuid=a42c8c6b-4025-4f83-ba28-dad21114744a" > "instance=cf9f6c86-404c-11e7-a09a-04a316b5de53" "service=log" > "dsn=ipc:///tmp/0.log.a42c8c6b-4025-4f83-ba28-dad21114744a" > May 24 06:47:13 beaglebone msgd:0: rtapi_app exit detected - scheduled > shutdown > May 24 06:47:15 beaglebone msgd:0: msgd shutting down > > > Anybody an idea why this happens? > > With regards, > Michel > -- website: http://www.machinekit.io blog: http://blog.machinekit.io github: https://github.com/machinekit --- You received this message because you are subscribed to the Google Groups "Machinekit" group. To unsubscribe from this group and stop receiving emails from it, send an email to machinekit+unsubscr...@googlegroups.com. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
