Got it!!! With a little help from a friend.
He figured out 0x378 is for a on-board parallel port. Mine is a add on.
I do lspci -vvv and search for 9900 device. Then I use the first I/O port.
>From below the I/O is e010 so my port is 0e010. Worked great!!
bill@CNC:~/Desktop$ lspci -vvv
01:00.0
On 11 October 2015 at 01:40, Willy Snow wrote:
> Linux ports 0 and 1 did not work. 0x378 seemed to load (it did not give
> error message). I still cannot make the motor turn if I set Parport Base
> Address to 0x378 in Stepconf Wizard.
Caveat: I haven't even tried to use a parport for about 5 year
Hi Andy,
I fixed the typos.
Linux ports 0 and 1 did not work. 0x378 seemed to load (it did not give
error message). I still cannot make the motor turn if I set Parport Base
Address to 0x378 in Stepconf Wizard.
halcmd: loadrt hal_parport cfg="0"
Error: could not insert module
/usr/realtime-3.4-9
On 10 October 2015 at 16:59, Willy Snow wrote:
> bill@CNC:~/Desktop$ halrun
> halcmd: loadrt hal_parport cfg-"0"
> [ 141.692879] hal_parport: Unknown parameter `cfg-"0"
That could just be a typo. you have cfg- not cfg=
--
atp
If you can't fix it, you don't own it.
http://www.ifixit.com/Manife
Hi Andy,
Here is the hal load for port 0 and 1. They both don't load. I would assume
I am connected to linux "0" since they have different errors.
FYI: Last night I swapped card ports to see if this was this issue.
bill@CNC:~/Desktop$ halrun
halcmd: loadrt hal_parport cfg-"0"
Error: could not in
On 10 October 2015 at 01:55, Willy Snow wrote:
> d000-dfff : PCI Bus :04
> d000-d007 : :04:00.0
> d010-d017 : :04:00.0
This could be it, but I was hoping for something a little more unambiguous
>>Does the linuxCNC parport driver load?
> bill@CNC:~$ loadrt hal_parport cfg="
