Greg,
I just tried starting up this config with loadrt prob_parport commented out but
it still errors out.
Peter,
> last week I had just the same problem. It turned out that some other device
> claimed the same addresses as my Netmos 2 port card. This particular one
> may be hard to find. First, use lspic -vv or even lspci -vvv to get more
> information than with lspci -v.
lspci -vv outputs this:
00:0b.0 Serial controller: Titan Electronics Inc VScom 010L 1 port parallel
adaptor (prog-if 02 [16550])
Subsystem: Titan Electronics Inc VScom 010L 1 port parallel adaptor
Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort-
<MAbort- >SERR- <PERR-
Interrupt: pin A routed to IRQ 9
Region 0: I/O ports at c400 [size=8]
Region 1: I/O ports at c800 [size=8]
Region 2: I/O ports at cc00 [size=8]
Region 3: I/O ports at d000 [size=8]
Region 4: Memory at ed001000 (32-bit, non-prefetchable) [size=64]
lspci -vvv outputs this:
00:0b.0 Serial controller: Titan Electronics Inc VScom 010L 1 port parallel
adaptor (prog-if 02 [16550])
Subsystem: Titan Electronics Inc VScom 010L 1 port parallel adaptor
Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort-
<MAbort- >SERR- <PERR-
Interrupt: pin A routed to IRQ 9
Region 0: I/O ports at c400 [size=8]
Region 1: I/O ports at c800 [size=8]
Region 2: I/O ports at cc00 [size=8]
Region 3: I/O ports at d000 [size=8]
Region 4: Memory at ed001000 (32-bit, non-prefetchable) [size=64]
> Look at /proc/ioports: You will find addresses like a400, b000 up to d000.
> My card supplies 6 such possibilities to chose. Behind the valid address
> EMC had put in a line stating "hal parport" as a comment. That's the one.
> If you are not sure, try them all with stepconf: insert the address to be
> tested, doubleclick on Continue to get to the X-Axis page and "test axis".
> If the re is no motion, return with doubleclick and try the next address.
> Within a minute I had tested all 6 addresses given.
> Don't save the stepconf five when leaving in case you have made unintended
> changes.
I think I have done something similar to this by changing the .hal file to the
four different addresses that were shown via lspci -v. 0xc400 caused errors
and the other three would allow axis to start up but there would be no output.
So with the above data shown from lspci, is there anything in there besides the
addresses that could be used to figure out what is happening?
Thanks for the help so far!
Will Baden
_________________________________________________________________
Windows Live™: Keep your life in sync.
http://windowslive.com/explore?ocid=TXT_TAGLM_WL_allup_1a_explore_042009
------------------------------------------------------------------------------
This SF.net email is sponsored by:
High Quality Requirements in a Collaborative Environment.
Download a free trial of Rational Requirements Composer Now!
http://p.sf.net/sfu/www-ibm-com
_______________________________________________
Emc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-users
