When I shutdown EMC, and then start it up again, the process of releasing and re-acquiring the parallel port seems to generate a signal that get interpreted as a step. Is there a way to keep Linux from messing with the parallel port when EMC releases it? -- Matt
Hi Matt On Monday 13 February 2006 01:32, Matt Timmermans wrote:
When I shutdown EMC, and then start it up again, the process of releasing and re-acquiring the parallel port seems to generate a signal that get interpreted as a step.
Is there a way to keep Linux from messing with the parallel port when EMC releases it?
The quick way is to unload the lp, parport_pc, and parport kernel modules. In an ideal world, the EMC driver should be registering it's use of the parallel port before the printer driver can claim it. However, to get over the fact that EMC is hardly ever loaded at boot time, the original authors skipped the registration process. Regards, Paul. -- From the Klingon book of C: Klingon function calls do not have 'parameters' - they have 'arguments' - and they ALWAYS WIN THEM.
OK, that sounds good. Hmmm... So (I'm sure I'd know this if I wasn't newish to Linux) if I go into the modules directory and DELETE the lp, parport_pc, and parport kernel modules, will it fix the problem forever, or will it break my boot sequence? -- Matt ----- Original Message ----- From: "Paul" <[email protected]> [...] The quick way is to unload the lp, parport_pc, and parport kernel modules. In an ideal world, the EMC driver should be registering it's use of the parallel port before the printer driver can claim it. However, to get over the fact that EMC is hardly ever loaded at boot time, the original authors skipped the registration process.
Hi Matt On Monday 13 February 2006 01:53, Matt Timmermans wrote:
OK, that sounds good. Hmmm... So (I'm sure I'd know this if I wasn't newish to Linux) if I go into the modules directory and DELETE the lp, parport_pc, and parport kernel modules, will it fix the problem forever, or will it break my boot sequence?
Don't go deleting the modules from the system - It would break a couple of the init scripts run at boot time. Check /etc/modules and comment out lp & co if they are listed, and run "update-rc.d -f cupsys remove" - This last command removes the cupsys init script from the list of services started at boot time. Without booting up a BDI-4 box, I'm not sure if there is anything else that might load the parport modules. I'll check on that tomorrow for you. Regards, Paul. -- From the Klingon book of C: Klingon function calls do not have 'parameters' - they have 'arguments' - and they ALWAYS WIN THEM.
On Sunday 12 February 2006 21:37, Paul wrote:
Hi Matt
On Monday 13 February 2006 01:53, Matt Timmermans wrote:
OK, that sounds good. Hmmm... So (I'm sure I'd know this if I wasn't newish to Linux) if I go into the modules directory and DELETE the lp, parport_pc, and parport kernel modules, will it fix the problem forever, or will it break my boot sequence?
Don't go deleting the modules from the system - It would break a couple of the init scripts run at boot time. Check /etc/modules and comment out lp & co if they are listed, and run "update-rc.d -f cupsys remove" - This last command removes the cupsys init script from the list of services started at boot time. Without booting up a BDI-4 box, I'm not sure if there is anything else that might load the parport modules. I'll check on that tomorrow for you.
Humm, thats not a problem I've hit Paul. And cups is installed and running just fine on that box. I printed one of the docs on that machine, to a printer on this machine with no problem at all, cups found the IPP share when I brought up the "print this" requester just fine. The only thing on the parport out there on the bdi machine is the xylotex card. And one step from a motor when emc2 is first run is like .0002", but this occurs only on the first run of emc2 after the bootup. The only other time I've heard a motor move was if I'd turned off the power and moved them by hand, and then reapplied the power. It'll goto where ever the xylotex card thinks is home because motor power and xylotex power is from the same supply. Could be a max of 3 steps I think.
Regards, Paul.
-- 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.
participants (3)
-
Gene Heskett -
Matt Timmermans -
Paul