[tulip] errors using tulip in a compaq Alpha ds10

[Kelly Roestel]

The switch says that this server is in Full-Duplex.  I will try the new 
driver.  Maybe that will help with the problems.

Here is what the mii-diag said.

Kelly


[root@server1 common]# ./mii-diag 
Using the default interface 'eth0'.
Basic registers of MII PHY #32:  1000 786c 0000 0000 0621 41e1 0000 0000.
 Basic mode control register 0x1000: Auto-negotiation enabled.
 You have link beat, and everything is working OK.
 Your link partner advertised 41e1: 100baseTx-FD 100baseTx 10baseT-FD 
10baseT.

>>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<<

On 12/21/00, 12:31:54 PM, Donald Becker <becker@scyld.com> wrote regarding 
Re: [tulip] errors using tulip in a compaq Alpha ds10:


> On Thu, 21 Dec 2000, Kelly Roestel wrote:

> > I am getting a lot of RX error on a HP switch connected to a Compaq Alpha
> > ds10 that is using the onboard ethernet.  Most of the errors are FCS and
> > alignment errors.  I was wondering if someone was having this problem as
> > well.  I have included the tulip-diag report.  Please any help would be
> > great.

> What was the driver detection message?

> Usually FCS/CRC and alignment error indicated corrupted packets due to 
bad
> cables.

> The only outstanding problem report with the DS10 is that sometimes the
> 21143 chips don't switch into full duplex mode, and you get reported
> collisions.  This problem is easy to identify:
>    the chip is set to full duplex mode
>    the Tx collision count is incrementing
> I belive that this is fixed with the current driver, but it's a pretty
> obscure bug so I can't be certain.


> Donald Becker                         becker@scyld.com
> Scyld Computing Corporation           http://www.scyld.com
> 410 Severn Ave. Suite 210             Second Generation Beowulf Clusters
> Annapolis MD 21403                    410-990-9993