|
John Connett wrote:
> John Connett wrote:
> > Any suggestions as to how to narrow it down? I have an Intel
> > EtherExpress PRO 100+ and a 3COM 3c905B which I could try instead of the
> > KNE 100TX to see if that makes a difference.
>
> A tiny light at the end of the tunnel! Just tried an Intel EtherExpress
> PRO 100+ and it works! Unfortunately, the hardware is fixed for the
> application I am working on and has to use a single Kingston KNE 100TX
> NIC ...
Some more information. The LocalNode problem has been observed with
both the old style (21140-AF) and the new style (21143-PD) of Kingston
KNE 100TX NIC. This suggests that there is a good chance that it will
be seen with other "tulip" based NICs. It has been observed with both
the "v0.90 10/20/98" and the "v0.91 4/14/99" versions of tulip.c.
I have upgraded to vs-0.9 and the behaviour remains the same: the
EtherExpress PRO 100+ works; the Kingston KNE 100TX doesn't work.
It is somewhat surprising that the choice of NIC should have this impact
on the LocalNode behaviour but work successfully on connections to slave
servers.
Any suggestions as to how I can identify the feature (or bug) in the
tulip driver would be gratefully received. If it is a bug I will raise
it on the tulip mailing list.
Thanks in anticipation
--
John Connett (jrc@xxxxxxxxxxxxxx)
|
