Paralell port problems SOLVED!

To be pedantic, it isn't "crashing" it is exiting with an error.

The difference is that there will be some useful debug data available that will describe the error.

You might want to try referencing the parallel ports by index number (0, 1, 2) istead of base address.[/quote]

I was under the understanding that step config required the address, I will give it a try with only port numbers.

I attempted just using the port numbers vice the actual address and LinuxCNC had issues with that.
Error says port 1 not found. I am still not getting an option to assign parport 2 address in step config must still be something else grabbing that port before LinuxCNC gets it. Will try removing that card and see if that will release it so I can assign it to something useful.

gizmo6023 wrote: I attempted just using the port numbers vice the actual address and LinuxCNC had issues with that.
Error says port 1 not found.

Does is find port 0?

There does seem to be a problem with lp (printer thing) grabbing the parports in newer distributions. I can't help much, I stopped using the parport several years ago.

Looks like it is having issues:

dave@debian:~$ dmesg | grep par
[ 0.004092] AppArmor: AppArmor disabled by boot time parameter
[ 1.231270] hpet0: 3 comparators, 64-bit 14.318180 MHz counter
[ 2.441740] ahci 0000:00:1f.2: flags: 64bit ncq pm led clo pio slum part ccc ems
[ 7.952108] PM: Hibernation image partition 8:5 present
[ 8.704534] parport0: PC-style at 0xdca0, irq 18 [PCSPP,TRISTATE,EPP]
[ 8.800225] parport0: PC-style at 0xdcc8, irq 19 [PCSPP,TRISTATE,EPP]
[ 12.866304] ppdev: user-space parallel port driver
[ 731.603303] PARPORT: ERROR: linux parport 0 not found
[ 806.720709] PARPORT: ERROR: linux parport 1 not found
dave@debian:~$

I have the system running with the first port address listed, still have one input available but would like to have the other port working so I can install limit switches and probe/touch plate

cat /proc/ioports

Might (I stress, _might_) give you more info about the available parports.

andypugh wrote: cat /proc/ioports

Might (I stress, _might_) give you more info about the available parports.

At this point a might option is worth a shot if it helps resolve this issue.
Last night I removed the second parport from the machine, rebooted, shutdown, and reinstalled the parport, ran the following in terminal sudo modprobe parport_pc
sudo rmmod ppdev
sudo rmmod lp
sudo rmmod parport_pcand
then attempted to assign it only to generate error on start parport 1 not found.