So, here is where I am now.:
I boot up and go to a terminal window in X and issue lsmod I see 2
modules,
one for the network card and another that is a 4 digit number that starts
with 8 and I can't remember the rest.
Next I switch to /usr/local/nist/emc and enter the command
./run.mystepper
This seems to start out fine and I see starting emc and then installing
motion module. Then I get the following error message:
segmentation fault
rmmod: steppermod: devise or resource busy
rmmod: rtl_sched is in use
And that is where it leaves me.
If I then enter lsmod I see steppermod and rtl_sched in the list with the
previous 2 entries. steppermod is marked as [uninitialized]. If I try
rmmod
manually, I get the error noted above.
Any ideas of what I should try now.
OK, let's reboot to get rid of all the installed modules, etc. and do this
by hand rather that by script. As user root from a terminal window in X do:
cd /usr/local/nist/emc
insmod -v /usr/src/rtl/modules/rtl_sched
insmod -v /usr/local/nist/emc/plat/rtlinux_09J/lib/steppermod.o
SHMEM_BASE_ADDRESS=0x3F00000 PARPORT_IO_ADDRESS=0x378
plat/linux_2_0_36/bin/mmio -ini 64stepper.ini &
plat/linux_2_0_36/bin/mmtask -ini 64stepper.ini &
plat/linux_2_0_36/bin/xemc -ini 64stepper.ini
The long commands may wrap to the next line in the terminal window, that's
OK, just hit ENTER at the end. This should get the EMC started without all
the fancy error checking stuff in that script file. Let me know if you get
any errors from this procedure. You are not the only guy to have trouble
with these script files, although I can't figure out what the problems are
caused by.
Thanks,
Matt
P.S. If you want to call today (Memorial Day), I'm around and not that
busy, so if you need to do that it's OK.
(410) 521-3715
