Problems with 3c905b

[Bret McGuire]

	I have seen problems similar to this, although I've never seen the
IP-Config error.  I would imagine that's due to the fact that, at least
temporarily, I have to configure my routing information manually.
	The machine I'm working with is an AMD-K6 running Red Hat 4.0 with
the most recent copy of 3c59x.c (v0.99?).  I am trying to configure
Ethernet traffic within my own subnet; there are only two entries in my
routing table, one for the loopback and one for the subnet this machine is
on.  Even with this minimal configuration, I get the following error when
trying to send packets to machines on the same network...

eth0: transmit timed out, tx_status 00 status xxxx

	Where xxxx varies over time.  I also have to shut the machine down
or else I see the message repeated multiple times.
	This marks at least the third mention of this bug; one on
linux-kernel, one on this list, and my problem.  Is this a known bug?


								- Bret -

On Mon, 26 Oct 1998, Patrick Robert Aland wrote:

> I have a 3c905b running on a RedHat 5.1 with Kernel 2.1.125
> I am noticing a few errors that I have not been able to fix.
> The first is that my network connectivity will suddenly stop and if I look
> in the messages file i see LOTS (like hundreds) of lines that say:
> 
> kernel: eth0: transmit timed out, tx_status 00 status e000.
> and then it says
> kernel: eth0: Tx Ring full, refusing to send buffer.
> 
> Sometimes doing a /etc/rc.d/init.d/network stop and then start will fix
> this but most of the time I have to reboot.
> 
> During boot the netcard initialization is as follows:
> 
> kernel: eth0: 3Com 3c905B Cyclone 100baseTx at 0x6100, 00:10:4b:9c:ca:93,
> IRQ 11
> kernel:   8K byte-wide RAM 5:3 Rx:Tx split, 10baseT interface.
> kernel:   Enabling bus-master transmits and whole-frame receives.
> kernel: 3c59x.c:v0.99E 5/12/98 Donald Becker
> http://cesdis.gsfc.nasa.gov/linux/drivers/
> kernel: IP-Config: Incomplete network configuration information.
> 
> I cannot seem to determine what is causing the IP-Config error because I
> never got one with my old net-card.(An ne2000 PCI)
> 
> Has anyone seen this problem in the past and if so were they able to
> resolve it? Thanks.
> 
> 
> --Patrick Aland
> --Stetson University
>