Re: 3com 905c

[Alexander List <alexlist@sbox.tu-graz.ac.at>]

On Fri, 28 Sep 2001, Christofer Algotsson wrote:

> p166mhz w/ 128Mb RAM, five SCSI-disks, 3c905b, some PCI videocard.

I'm not sure if this applies to your particular problem, but from my
experience with 3com cards on old mainboards...

Have you had a look at the PCI bus? Is the mainboard's bus compatible with
the requirements of this card, e.g. does it say "no bursts" somewhere"?

You could easily figure that out with 'cat /proc/pci', it should tell you
enough about the system. An example of such a card in an Asus P2B-DS,
working quite stable:

PCI devices found:
  Bus  0, device   0, function  0:
    Host bridge: Intel Corporation 440BX/ZX - 82443BX/ZX Host bridge (rev 3).
      Master Capable.  Latency=64.
      Prefetchable 32 bit memory at 0xe4000000 [0xe7ffffff].
  Bus  0, device   1, function  0:
    PCI bridge: Intel Corporation 440BX/ZX - 82443BX/ZX AGP bridge (rev 3).
      Master Capable.  Latency=64.  Min Gnt=136.
[...]
  Bus  0, device   9, function  0:
    Ethernet controller: 3Com Corporation 3c905B 100BaseTX [Cyclone] (rev 48).
      IRQ 10.
      Master Capable.  Latency=32.  Min Gnt=10.Max Lat=10.
      I/O at 0xa800 [0xa87f].
      Non-prefetchable 32 bit memory at 0xe1000000 [0xe100007f].
[...]

> Driver for the 905 card is 3c59x.c ;


I once succeeded just dropping the latest version of this driver into the
kernel source tree and recompiling, maybe this helps. It should work if no
interfaces have changed.

You might want to check out http://www.scyld.com/network/vortex.html

regards

Alex

-- 
People often think of research as a form of development -- that it's
about doing exactly what you planned, doing it on time, and doing it
with resources that you said you'd use.  But if you're going to do
that, you have to know what you are doing, and if you know what you
are doing, it isn't really research."
             --Dave Liddle, The New Yorker, Feb. 23/Mar.2, 1998, p84