[471] in linux-net channel archive

home help back first fref pref prev next nref lref last post

Re: PLIP still a no go

daemon@ATHENA.MIT.EDU (Martin Kraemer)
Tue Jun 13 08:47:35 1995

To: m-ke0082@SPARKY.CS.NYU.EDU (Ken Estes)
Date: Tue, 13 Jun 1995 12:44:54 +0200 (MDT)
From: "Martin Kraemer" <Martin.Kraemer@mch.sni.de>
In-Reply-To: <9506130357.AA08798@SPARKY.CS.NYU.EDU> from "Ken Estes" at Jun 12, 95 11:57:22 pm

Hello Ken,

> [...] It is an old
> machine) I have the cable plugged into the parallel port that came
> with the machine.  I have done nothing special to the machine

One (stupid)  idea comes  to my  mind... is  it possible  that you  have a
_buffered_ printer card?  That is, one where the parallel interface chip's
output pins do not go directly to the plug but go thru a buffer chip (that
prevents the  parallel  interface  chip from  dying  when  there's  static
electricity on  the plug). These  buffers work  only unidirectional,  thus
making bidirectional use of the port impossible (As far as I remember, the
PLIP protocol works using 4-bit wide "nibbles". But then again, I might be
wrong).

At least, you  could try to  use a "well known"  printer card, since  your
configuration seems to be correct.

One thing that struck me was this:
[nimbus]
> plip0     Link encap:10Mbps Ethernet  HWaddr FC:FC:80:FD:9A:20
>           inet addr:128.253.154.32  P-t-P:128.253.154.33  Mask:255.255.0.0
>           UP POINTOPOINT RUNNING  MTU:1500  Metric:1
>           RX packets:0 errors:0 dropped:0 overruns:0
>           TX packets:522 errors:0 dropped:0 overruns:0
>           Interrupt:5 Base address:0x3bc
> ----------------------------------------------
> from cirrus we have
> plip1     Link encap:10Mbps Ethernet  HWaddr FC:FC:80:FD:9A:21
>           inet addr:128.253.154.33  P-t-P:128.253.154.32  Mask:255.255.0.0
>           UP POINTOPOINT RUNNING  MTU:1500  Metric:1
>           RX packets:643 errors:0 dropped:1 overruns:0
>           TX packets:0 errors:819 dropped:0 overruns:0
                         ^^^^^^^^^^
>           Interrupt:7 Base address:0x378 

Why does only cirrus have Tx errors? It seems to be able to receive,
though! Perhaps it even received all of the 522 sent packets sent by
nimbus.

    Martin
-- 
| S I E M E N S |   Martin.Kraemer@mch.sni.de   |       Siemens Nixdorf
| ------------- |   Voice: +49-89-636-46021     |   Informationssysteme AG
| N I X D O R F |   FAX:   +49-89-636-44994     |    81730 Munich, Germany
~~~~~~~~~~~~~~~~  (My opinions only, of course)


home help back first fref pref prev next nref lref last post