On Mon, May 10, 2010 at 09:16:42PM -0500, Jon Elson wrote:
I think somebody turned down the priority of
error messages such that my hal_ppmc.c driver doesn't report anything
even when it decides to bomb completely.
In this case, I think the issue is just that the failure is very early
in the
On Mon, May 10, 2010 at 7:18 PM, Jon Elson el...@pico-systems.com wrote:
Neil Baylis wrote:
I rebooted again (this is the third time since I did the upgrade to 2.4)
and
checked lsmod. Still the same: no parport_pc, but parport is loaded with
dependencies lp and ppdev. I tried emc again,
Jeff Epler wrote:
On Mon, May 10, 2010 at 09:16:42PM -0500, Jon Elson wrote:
I think somebody turned down the priority of
error messages such that my hal_ppmc.c driver doesn't report anything
even when it decides to bomb completely.
In this case, I think the issue is just that
Neil Baylis wrote:
I commented out the line in /etc/modprobe.d/emc2, rebooted, and it failed as
before.
Then I uncommented the line, rebooted, and it worked first time again.
I have to assume I somehow got confused when I edited this file the first
time, and thought I had rebooted when I
On Tue, May 11, 2010 at 10:18 AM, Jon Elson el...@pico-systems.com wrote:
Well, this is just RT-linux arcana, and either we will find a good fix
for it, or have to put it prominently in the Wiki.
Since you are apparently the first person to hit this, there won't be a
release note about it
There used to be a capability to run part of a G-code program that
exceeds the machine limits.
I tried doing this today, and got the first big dialog box that says
program exceeds machine minimum on axis Y and hit the run anyway
button. I intended to stop the program before it ran into the
