I'll try that.
Loaded up my non-pythonic config for kicks, and I get a similar error to
the canned configs:
machinekit@beaglebone:~/Arcus-3D-M2$ ./run.py
loading cramps_cape.bbio... done
installing reset.comp... Compiling realtime reset.c
Linking reset.so
cp reset.so /home/machinekit/machinekit/rtlib/rt-preempt/
done
starting configserver... done
starting linuxcnc... MACHINEKIT - 0.1
Machine configuration directory is '/home/machinekit/Arcus-3D-M2'
Machine configuration file is 'Arcus-3D-M2.ini'
Starting Machinekit...
done
io started
halcmd loadusr io started
Arcus-3D-M2.hal:31: insmod failed, returned -1:
rtapi_app_main(hal_pru_generic): -1 Operation not permitted
See /var/log/linuxcnc.log for more information.
Shutting down and cleaning up Machinekit...
Cleanup done
Machinekit terminated with an error. You can find more information in the
log:
/home/machinekit/linuxcnc_debug.txt
and
/home/machinekit/linuxcnc_print.txt
as well as in the output of the shell command 'dmesg' and in the terminal
stopping configserver... done
machinekit@beaglebone:~/Arcus-3D-M2$
machinekit@beaglebone:~/Arcus-3D-M2$ cat /home/machinekit/linuxcnc_debug.txt
Can not find -sec DISPLAY -var INTRO_GRAPHIC -num 1
3716
PID TTY STAT TIME COMMAND
Stopping realtime threads
Unloading hal components
machinekit@beaglebone:~/Arcus-3D-M2$ cat /home/machinekit/linuxcnc_print.txt
RUN_IN_PLACE=yes
LINUXCNC_DIR=
LINUXCNC_BIN_DIR=/home/machinekit/machinekit/bin
LINUXCNC_TCL_DIR=/home/machinekit/machinekit/tcl
LINUXCNC_SCRIPT_DIR=
LINUXCNC_RTLIB_DIR=/home/machinekit/machinekit/rtlib
LINUXCNC_CONFIG_DIR=
LINUXCNC_LANG_DIR=/home/machinekit/machinekit/src/objects
INIVAR=/home/machinekit/machinekit/libexec/inivar
HALCMD=halcmd
LINUXCNC_EMCSH=/usr/bin/wish8.6
INIFILE=/home/machinekit/Arcus-3D-M2/Arcus-3D-M2.ini
PARAMETER_FILE=../pru-stepper.var
TASK=milltask
HALUI=
DISPLAY=mkwrapper
Starting Machinekit server program: linuxcncsvr
Loading Real Time OS, RTAPI, and HAL_LIB modules
Starting Machinekit IO program: io
Killing task linuxcncsvr, PID=3716
Removing HAL_LIB, RTAPI, and Real Time OS modules
Removing NML shared memory segments
machinekit@beaglebone:~/Arcus-3D-M2$ cat /var/log/linuxcnc.log
Jul 28 18:15:37 beaglebone msgd:0: startup pid=3745 flavor=rt-preempt
rtlevel=1 usrlevel=1 halsize=524288 shm=Posix cc=gcc 4.9.2 version=unknown
Jul 28 18:15:37 beaglebone msgd:0: ØMQ=4.0.5 czmq=3.0.2 protobuf=2.6.1
atomics=gcc intrinsics libwebsockets=<no version symbol>
Jul 28 18:15:37 beaglebone msgd:0: configured: sha=86bb58c
Jul 28 18:15:37 beaglebone msgd:0: built: Jul 28 2017 01:01:30
sha=86bb58c
Jul 28 18:15:37 beaglebone msgd:0: register_stuff: actual hostname as
announced by avahi='beaglebone.local'
Jul 28 18:15:37 beaglebone msgd:0: zeroconf: registering: 'Log service on
beaglebone.local pid 3745'
Jul 28 18:15:38 beaglebone msgd:0: zeroconf: registered 'Log service on
beaglebone.local pid 3745' _machinekit._tcp 49152 TXT
"uuid=a42c8c6b-4025-4f83-ba28-dad21114744a"
"instance=c15230da-73c0-11e7-8ecb-985dad518a99" "service=log"
"dsn=tcp://beaglebone.local:49152"
Jul 28 18:15:38 beaglebone rtapi:0: rtapi_app_main(hal_pru_generic): -1
Operation not permitted
Jul 28 18:15:43 beaglebone rtapi:0: unload: 'tp' not loaded
Jul 28 18:15:43 beaglebone rtapi:0: unload: 'lineardeltakins' not loaded
Jul 28 18:15:43 beaglebone rtapi:0: unload: 'motmod' not loaded
Jul 28 18:15:43 beaglebone rtapi:0: unload: 'hal_bb_gpio' not loaded
Jul 28 18:15:43 beaglebone msgd:0: rtapi_app exit detected - scheduled
shutdown
Jul 28 18:15:45 beaglebone msgd:0: msgd shutting down
Jul 28 18:15:45 beaglebone msgd:0: zeroconf: unregistering 'Log service on
beaglebone.local pid 3745'
Jul 28 18:15:45 beaglebone msgd:0: log buffer hwm: 0% (0 msgs, 0 bytes out
of 524288)
Jul 28 18:15:45 beaglebone msgd:0: normal shutdown - global segment detached
machinekit@beaglebone:~/Arcus-3D-M2$ date
Fri Jul 28 18:19:11 UTC 2017
On Friday, July 28, 2017 at 2:09:08 PM UTC-4, Charles Steinkuehler wrote:
>
> On 7/28/2017 12:59 PM, Daren Schwenke wrote:
> > After the dd, it now takes a seriously long time to boot.
> > Before it was ~45 seconds till it was back on the network. Now it takes
> around
> > 5 minutes.
>
> I'd suggest reinstalling U-Boot on the eMMC. You can do this by hand,
> but the easiest way is probably just to run one of the recent
> "flasher" images (assuming you don't care about what's currently on
> the eMMC).
>
> --
> Charles Steinkuehler
> [email protected] <javascript:>
>
--
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 [email protected].
Visit this group at https://groups.google.com/group/machinekit.
For more options, visit https://groups.google.com/d/optout.
