Networking problem with Dell Dimension 8100 (3com 3c920)

Hello,

I seem to be having network issues with a Dell Dimension 8100 (Pentium 4)
with built-in 3com 3c920 ethernet. It’s running 6.1.0 .

I am trying to use qnet to edit and develop code on another machine running
6.1.0, this one with a 3com 3c905c ethernet card.

Both of these cards have the exact same vendor and device IDs according to
‘pci’. The 3c920 card appears to the OS as a 3c905c.

Anyway, when accessing the remote machine from the 8100, sometimes accessing
files through /net/ works just fine, but more often than not, it
takes anywhere from 2 seconds to a full minute to even get a directory
listing. I’ve tried both tcpip and ttcpip stacks, qnet using bind=ether and
bind=ip,resolve=dns. Nothing seems to fix it.

So, I decided to look at a lower level. I pinged Windows machines that are
in the same rooms as the two computers described above. The remote machine
(with the 3c905c card) had no packet loss, and a min/avg/max time of
0/0/1ms. The 8100 (with the 3c920 card), out of 651 packets, dropped 11,
had 10+ duplicates, and had times of 0/327/4780ms. This same machine booted
into win2k, pinging the same remote machine, has no packet loss, and times
of 0/0/0 ms.

I think there’s something up with the QNX support for the 3c920. Has anyone
else had this problem?

Thanks,

-davin


Davin Swanson
http://www.imdl.gatech.edu

Hi Davin,

I don’t belive the 3c920 is a supported chipset. If it happens to work
then it is by luck. From my understanding this chipset is currently
in the process of being supported.

E.


Davin Swanson <gt6032c@mail.gatech.edu> wrote:

Hello,

I seem to be having network issues with a Dell Dimension 8100 (Pentium 4)
with built-in 3com 3c920 ethernet. It’s running 6.1.0 .

I am trying to use qnet to edit and develop code on another machine running
6.1.0, this one with a 3com 3c905c ethernet card.

Both of these cards have the exact same vendor and device IDs according to
‘pci’. The 3c920 card appears to the OS as a 3c905c.

Anyway, when accessing the remote machine from the 8100, sometimes accessing
files through /net/ works just fine, but more often than not, it
takes anywhere from 2 seconds to a full minute to even get a directory
listing. I’ve tried both tcpip and ttcpip stacks, qnet using bind=ether and
bind=ip,resolve=dns. Nothing seems to fix it.

So, I decided to look at a lower level. I pinged Windows machines that are
in the same rooms as the two computers described above. The remote machine
(with the 3c905c card) had no packet loss, and a min/avg/max time of
0/0/1ms. The 8100 (with the 3c920 card), out of 651 packets, dropped 11,
had 10+ duplicates, and had times of 0/327/4780ms. This same machine booted
into win2k, pinging the same remote machine, has no packet loss, and times
of 0/0/0 ms.

I think there’s something up with the QNX support for the 3c920. Has anyone
else had this problem?

Thanks,

-davin


Davin Swanson
http://www.imdl.gatech.edu