Subject: 3Com 3C595 ethernet PCI/10/100
To: None <port-i386@NetBSD.ORG>
From: None <mika@cs.caltech.edu>
List: port-i386
Date: 02/18/1996 05:04:42
Hello,
  I was wondering if anyone had solved this problem yet. I'm trying to
set up NetBSD on a lab of 25 pentiums, and I've run into this nasty problem
that the machines refuse to do anything nice with the ethernet cards.
The ethernet cards are 3Com's new, snazzy 3C595 10/100 Mbps PCI cards.

The kernel I am running is "NetBSD-current" (1.1A) as of a few days ago
and the config file says it supports "3C590". Since 3C590's are generally
referred to as "3C59X" I decided to try making the 595 appear as a 590 
by adding the appropriate vendor codes, etc. Things didn't work so well
(more about that later), so I tried porting if_vx.c from FreeBSD.. 
I could probably do that given a big chunk of time that I don't have, but
if someone has already been working on it, I'd rather avoid it.

Anyhow, I'm not really sure the problem is that the device driver isn't 
working. This is what happens: I boot the system (and with the minor 
modifications to the kernel I mentioned above), it recognizes the card
as device ep1 (or so), at pci0 etc. I can ifconfig it and then I can
get a very few packets in or out.. usually I have to run both tcpdump
and telnet at the same time to get any response from either. My untrained
eye suggests that the problem is that interrupts are not being 
delivered to the proper place. Either the "3C590" driver the I modified
can't deal with the situation or else I have a hardware setup problem..
(I tried switching cards and turning off support for everything I know
I don't have, etc etc etc) either way the symptoms are about the same
as when there's an IRQ conflict on the NE2000 I used to ftp stuff.

Does anyone out there know a Whole Lot about these things? :)

   Regards,
    Mika Nystrom <mika@vlsi.cs.caltech.edu>
    Department of Computer Science
    California Institute of Technology
    Pasadena, Calif., U.S.A.

P.S. I am not subscribed to this list, so please CC: me in your responses
(if any).