> > > > But it was there once. So far only a reboot has fixed this. I'm not sure > > why. > > > Sometimes you can end up with kernel modules that claim to be dependent > on > each other, and the kernel won't let either fo them go. > (at this point it is rather out of LinuxCNC's hands) > > You can diagnose this situation with lsmod. > You may find that hal_parport is still there, and in theory modprobe > should be able to unload it, but sometimes it seems to refuse to try. > > What does it actually say in the middle section of the error dump? (That is > typically where the useful information is, and in the last few lines of the > dmesg output) > > -- > atp
I finally got the Charge Pump working by removing the dependence on estop. Then the board enable on pin 1 is fooled with net xenable => parport.0.pin-01-out I now have motion. A few more details to work out and I can try and get the second parallel port working. John _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
