[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: More Ethernet card problems.

If your card is the newer 3C509B, then there may be a driver related problem.
As with the 3C905B(PCI 10/100), the card will detect as being the older card by
older kernels(and modules), but will NOT function properly.  Having given up ISA
based cards a few years ago, I havn't heard if the 509B(ISA card) support has
been added.  I would hope that is has been, but....

							Dave Bristel

On Wed, 2 Jun 1999, Dale Scheetz wrote:

> Date: Wed, 2 Jun 1999 10:23:29 -0400 (EDT)
> From: Dale Scheetz <dwarf@polaris.net>
> To: debian-devel@lists.debian.org
> Subject: More Ethernet card problems.
> Resent-Date: 2 Jun 1999 15:26:20 -0000
> Resent-From: debian-devel@lists.debian.org
> Resent-cc: recipient list not shown: ;
> Yes, I've been bitten again by these 3Com cards, and Yes, I haven't been
> having a good day on any fronts...
> To cut to the chase, I believe that the Ethernet card in my Debian box is
> somehow, subtly broken or misconfigured, and none of the tools I have will
> fix it.
> Major symptom:
> It appears that the driver fails to load at boot time, although I appear
> to be able to successfully load the same driver with insmod after the
> bootup. Including the driver explicitly in /etc/modules causes the machine
> to hang during boot immediately after the line:
> 3c509
> Commenting this line from /etc/modules allows booting (with no message at
> the point of the previous hang) but eth0 is not cofigured, and no driver
> module is loaded (wich explains why the ifconfig fails).
> I suspected that the card had, somehow, gotten back into PnP mode, so I
> ran the 3c5x9setup program again to make sure. All output from this
> program was the same as before, with no errors.
> It troubles me that both 'insmod 3c509' and the setup program report
> everything is fine, and that they perform correctly, when this is not the
> case. The fact that the kernel can detect something wrong when it tries to
> load the driver for the card suggests that all the facts are not being
> reported by these programs.
> Minor Symptom:
> On the possibility that it could be the Windows '95 machine that was at
> fault (the hub reports all cards active once the Debian box appears to be
> configured properly), I booted up the Sparc, which is also on the hub, and
> was able to ping the '95 box, but not the Debian one.
> Even though the card tells the hub it is active, and seems to be
> functional from the point of view of the driver, ifconfig, route, and the
> kernel, I can't ping out with it, and the rest of the net can't ping into
> it.
> Yes, I checked all the cables, even though the fact that the hub
> recognizes every card connected to it seems to imply the cable is good.
> (at least the line that sends the "alive" signal is not broken)
> They are all tightly seated in their connectors.
> I have my son getting me another Ethernet card, so I can swap out and
> verify that the card _is_ bad, but this is not the most desirable
> solution. (specially when he tells me that the card I got in the kit, with
> two cards and a hub for a bit over $100, will cost over $100 all by
> itself!)
> Any ideas welcome,
> Dwarf
> --
> _-_-_-_-_-   Author of "The Debian Linux User's Guide"  _-_-_-_-_-_-
> aka   Dale Scheetz                   Phone:   1 (850) 656-9769
>       Flexible Software              11000 McCrackin Road
>       e-mail:  dwarf@polaris.net     Tallahassee, FL  32308
> _-_-_-_-_-_- See www.linuxpress.com for more details  _-_-_-_-_-_-_-
> -- 
> To UNSUBSCRIBE, email to debian-devel-request@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Reply to: