On Mon, 19 Jul 2004, DeJiang Jin wrote:
> My computers in the system have a build-in NIC and I add one more
> NIC (3com). The former uses the tg3 driver that install with Redhat
> Fedora OS. The later use the 3com driver that com with these NIC.
> Both work fine for general use.
What do you call a "3com NIC" ? Is it a 3c905 series or something
else ? What is the name of the driver "that comes with these NIC" ?
3Com makes some cards that can be driven by tg3 as well (3c996), so
the paragraph above is quite confusing...
What do you call "work fine" ? Have you tried bidirectional TCP
traffic on a link between 2 computers using the "3Com cards" ? If UDP
works fine or unidirectional TCP works fine, but bidirectional TCP
doesn't, I'd expect a problem with the media autonegotiation. This
rings a bell: if you are using Fedora Core 1 and the "3Com cards" are
in fact 3c905B (Cyclone), then there are known problems with the
interaction between kudzu and these cards which makes media operations
(including autonegotiation) fail. Turn off kudzu ('chkconfig kudzu
off') and then reboot to see if this restores the expected
functionality.
> When I installed LAM7.06, NICs of 3com are configured to use. LAM
> can be booted but fail to run mpi programs as described above.
Is booting slow ? This would confirm the autonegotiation problem.
> It is more interested that if only one node in the system keeps the
> use of 3com NIC LAM also works.
This is strange, but again if autonegotiation fails, strange things
happen...
--
Bogdan Costescu
IWR - Interdisziplinaeres Zentrum fuer Wissenschaftliches Rechnen
Universitaet Heidelberg, INF 368, D-69120 Heidelberg, GERMANY
Telephone: +49 6221 54 8869, Telefax: +49 6221 54 8868
E-mail: Bogdan.Costescu_at_[hidden]
|
