Re: Linux vs. DOS

Matt,

Thanks again for your kindness in helping.

Here is where I am at now. The problem was that I removed the !/bin/csh -f
line as I was originally getting a message about invalid parameter and the
csh parameter list would appear. So, I figured the line was commented out so
that removing it shouldn't hurt and that error went away. Silly me!!. I
tried to put the line back in and the original error returned even when I
copy and pasted it out of the run.stepper file (which produces plenty of
errors, just not the csh error). I ended up opening the run.stepper file for
edit and deleting all except the first line and saving it as run.mystepper
in the /usr/local/nist/emc directory and then running "chmod o+x
run.mystepper" command that Jon gave me. Now I could execute run.mystepper
with out any errors so I opened it for edit and copy and pasted all of the
run.64step378 file into it except for the first line that I had from the
run.stepper file.

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.

Thanks again,


Tim
[Denver, CO]

> -----Original Message-----
> From: Matt Shaver [mailto:mshaver@...]
> Sent: Sunday, May 30, 1999 9:49 PM
> To: CAD_CAM_EDM_DRO@onelist.com
> Subject: Re: [CAD_CAM_EDM_DRO] Linux vs. DOS
>
>
> From: "Matt Shaver" <mshaver@...>
>
> > Well, I played around a little more and applied the Microsoft
> trick (shut
> > down and reboot) and booted back to the original kernel (I left it as an
> > option in Lilo along with an option to boot to Windows 95). I tried
> running
> > insmod and it worked as it should. I then booted to the rtlinux kernel
> and
> > now it seems that I can issue insmod from the command line and it works.
> > Unfortunately, when I try ./run.64step378 I still get a number of
> "command
> > not found" errors. Is there a way to put in an echo or something in the
> > run.64step378 file so I can get an idea what the commands are that can't
> be
> > found.
>
> Hey, quit gettin' ahead of me here! ;)
>
> 1. Just put in lines like:
>
> echo "your_message_goes_here"
>
> This is done a lot in the run.64step378 file already.
>
> 2. Make sure that the line:
>
> #!/bin/csh -f
>
> is the very FIRST line in the file (no blank lines above)!
>
> 3. Check the plat/linux_2_0_36/bin/ directory to see that mmio,
> mmtask, and
> xemc are there.
>
> 4. Check that the path to the EMC code is /usr/local/nist/emc. Note that
> 'cd /usr/local/nist/emc' is on of the first lines in run.64step378.
>
> I'm here till late, so you can even call if you want.
>
> Matt
> (410) 521-3715
>
>
> ------------------------------------------------------------------------
> It's finally here! What's your opinion?
> http://www.onelist.com
> Create a Star Wars discussion group at ONElist.
> ------------------------------------------------------------------------
> welcome to CAD_CAM_EDM_DRO@..., an unmodulated list for
> the discussion of shop built systems in the above catagories.
>