[ale] var/messages question

[Armsby John-G16665]

I am trying to make some sense of the vortex.txt file.   I may have a nic problem as my box is several years old.  I thought I would "force" some sort of fix....  The vortex.txt file says:


  For example:

    insmod 3c59x options=0x204

  will force full-duplex 100base-TX, rather than allowing the usual
  autonegotiation.


-bash-2.05b$ /sbin/insmod 3c59x options=0x204
Using /lib/modules/2.4.18-14/kernel/drivers/net/3c59x.o
insmod: a module named 3c59x already exists
-bash-2.05b$ 


This command complains..... any suggestions??

John




-----Original Message-----
From: Chris Fowler [mailto:cfowler at outpostsentinel.com]
To: ale at ale.org
Sent: Monday, March 31, 2003 10:23 PM
To: ale at ale.org
Subject: Re: [ale] var/messages question


On Mon, 2003-03-31 at 20:17, Armsby John-G16665 wrote:
> another question.....
> 
> My web server (Redhat 8.0, 256meg, apache) runs a C++ script 

Huh,  What is a C++ script?

> which ran perfectly up until recently.  When I do a query which will return a LOT of results (Google like search of an intralinet), the output from the server seems to lock up.... I looked a the /var/messages and see this:
> 
> 
> Mar 31 17:31:04 xena kernel: eth0: Transmit error, Tx status register 82.
> Mar 31 17:31:04 xena kernel: Probably a duplex mismatch.  See Documentation/networking/vortex.txt
> Mar 31 17:31:04 xena kernel:   Flags; bus-master 1, dirty 1254(6) current 1254(6)
> Mar 31 17:31:04 xena kernel:   Transmit list 00000000 vs. cf0cb380.
> Mar 31 17:31:04 xena kernel:   0: @cf0cb200  length 800005ea status 000105ea
> Mar 31 17:31:04 xena kernel:   1: @cf0cb240  length 800005ea status 000105ea
> Mar 31 17:31:04 xena kernel:   2: @cf0cb280  length 800005ea status 000105ea
> Mar 31 17:31:04 xena kernel:   3: @cf0cb2c0  length 800005ea status 000105ea
> Mar 31 17:31:04 xena kernel:   4: @cf0cb300  length 800005ea status 000105ea
> Mar 31 17:31:04 xena kernel:   5: @cf0cb340  length 800005ea status 800105ea
> Mar 31 17:31:04 xena kernel:   6: @cf0cb380  length 800005ea status 000105ea
> Mar 31 17:31:04 xena kernel:   7: @cf0cb3c0  length 800005ea status 000105ea
> Mar 31 17:31:04 xena kernel:   8: @cf0cb400  length 800005ea status 000105ea
> Mar 31 17:31:04 xena kernel:   9: @cf0cb440  length 800005ea status 000105ea
> Mar 31 17:31:04 xena kernel:   10: @cf0cb480  length 800005ea status 000105ea
> Mar 31 17:31:04 xena kernel:   11: @cf0cb4c0  length 800005ea status 000105ea
> Mar 31 17:31:04 xena kernel:   12: @cf0cb500  length 800005ea status 000105ea
> Mar 31 17:31:04 xena kernel:   13: @cf0cb540  length 800005ea status 000105ea
> Mar 31 17:31:04 xena kernel:   14: @cf0cb580  length 800005ea status 000105ea
> Mar 31 17:31:04 xena kernel:   15: @cf0cb5c0  length 800005ea status 000105ea
> Mar 31 17:31:10 xena kernel: eth0: Transmit error, Tx status register 82.
> Mar 31 17:31:10 xena kernel: Probably a duplex mismatch.  See Documentation/networking/vortex.txt
> Mar 31 17:31:10 xena kernel:   Flags; bus-master 1, dirty 1260(12) current 1260(12)
> Mar 31 17:31:10 xena kernel:   Transmit list 00000000 vs. cf0cb500.
> --More--(66%)

> 
> What is this stuff?  

>From the messages, it seems like you may have a duplex mismatch for the

network and the card.  Check the setting on the switch and check the
setting on the card.  Make sure the duplex is the same,

Does the Vortex card auto-sense?  Depends on rev level.  The Vortex has
been out since what? 1995?

If you still have problems, Go to Ginstar and pick up $8 PCI card.  It
should work very well.  Usually, they are RTL8139 chipsets.
> 
> 
> Thanks,
> 
> John
> 
> _______________________________________________
> Ale mailing list
> Ale at ale.org
> http://www.ale.org/mailman/listinfo/ale


_______________________________________________
Ale mailing list
Ale at ale.org
http://www.ale.org/mailman/listinfo/ale
_______________________________________________
Ale mailing list
Ale at ale.org
http://www.ale.org/mailman/listinfo/ale