From: Gene H. <gen...@ve...> - 2006-07-29 03:14:06
|
On Friday 28 July 2006 08:09, Jeff Epler wrote: >On Thu, Jul 27, 2006 at 02:34:56PM -0400, Gene Heskett wrote: >> I finally found the new src cvs repo, and downloaded it, following the >> usual instructs in the README to build it. > >Where did you look when you were trying to find out where the new CVS >server is? Did you find outdated information about the sourceforge CVS >server? Please help us improve our website/wiki. I first went to srcfrg and couldn't seem to access the cvs server with anything but a ping. So I finally went to the srcfrg web page and read the fine print which said I needed to change my access command line so it would read em...@cv.... Or something along those lines. Anyway I finally grabbed that with a new checkout, configured it and typed make, only to be greeted by a message advising me this was old code and that I should goto linuxcnc.org for the real stuff. That wasted 2 days. >> Unforch, scripts/emc runs into a perms problem very quickly: >> >> insmod: error inserting '/home/gene/emc2/rtlib/motmod.ko': -1 Operation >> not permitted >> HAL:7: ERROR: insmod failed, returned 1 > >Here's the deceptive error: some emc2 code uses -1 as a generic error, >but insmod always displays this as 'Operation not permitted'. If you >get that error, always dig deeper.* I did, it was axis related, old version, fixed that, which in turn meant I had to redo the setuid part of the make. >> [12036.999796] HAL: creating thread servo-thread, 0 nsec >> [12036.999801] HAL: ERROR: create_thread called with period of zero >> [12036.999805] MOTION: failed to create 0 nsec servo thread > >Here's the true error, from the kernel log. I don't get that with the >'stepper_inch.ini' configuration in CVS. Did you change anything in >your .ini or .hal files, or copy it from an older version of emc2? Older version. I figured out you all had changed the periods from fractional seconds in float, to integers in nanoseconds, fixed up all the other damages the cvs checkout did to my .ini file, and then it squawked about the parport module being loaded, so I became root and unloaded lp, parport_pc and parport. It then would run. Sorta. Enabling the machine and turning on the psu for the motors, I find that axis says its running at a default speed of about .100" per minute, and that no step-dir sigs are getting to the drivers. The motors are locked in position. >Jeff >* In the olden days, an error similar to this would be displayed if you > forgot to 'sudo make setuid'. Now you get a much more useful message > in that case: > module_helper is not setuid root I saw that after the install of the newer axis 1.4b and redid it. Now the 2 questions are: Why aren't my motors running?, and if they were, why so glacially slow? Or are they just imitating the list server? Now thats glacial... -- Cheers, Gene People having trouble with vz bouncing email to me should add the word 'online' between the 'verizon', and the dot which bypasses vz's stupid bounce rules. I do use spamassassin too. :-) Yahoo.com and AOL/TW attorneys please note, additions to the above message by Gene Heskett are: Copyright 2006 by Maurice Eugene Heskett, all rights reserved. |