On Mon, May 10, 2010 at 10:19:15AM -0700, Neil Baylis wrote:
> that didn't seem to change anything. It still reports the same error about
> mode 4. I double checked that the change to the modprobe file was correct,
> and just for superstition I rebooted as well.
In this case the reboot is necessary. The parport_pc driver is loaded
either at boot time or the first time any program tries to access a
parallel port. After the parport_pc driver is loaded, removing it with
rmmod leaves some hardware (particularly "ISAPNP" hardware) in a
different state then at boot time.
If you're still seeing the "mode 4" message, then I suspect that the
parport_pc driver isn't really disabled (it shouldn't be able to happen
without parport_pc loaded).
Can you double check that your edit to /etc/modprobe.d/emc2 was saved?
It should look like this:
# Remove the '#' before 'install' below to prevent regular Linux programs
# from accessing the parallel port. This also means that the linux
# parport number may not be used to identify the port in loadrt hal_parport.
install parport_pc /bin/true
After emc fails to run, check whether the parport_pc module is loaded or
not; that will help me see whether I'm barking up the wrong tree. If
this command prints any lines when run in the terminal, then the module
is loaded. Otherwise, it's not:
lsmod | grep parport_pc
Jeff
------------------------------------------------------------------------------
_______________________________________________
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users
