Monkey boy needs help! Transmit timed out:...
Sat Oct 23 17:53:16 1999
Thanks for your response and thanks for clarifying the distinction
between the storm problem and my lack of as much as a breeze.
I think you must have overlooked the driver version info in my post.
Indeed it was included in the piece you cited, i.e.
eepro100.c:v1.09l 8/7/99 (latest?)
eepro100.c:v1.06 10/16/98 (standard with 2.2.13)
eepro100.c:v1.05 10/16/98 (used below)
Is this not the information you are referring to?
>>>>> On Sat, 23 Oct 1999 17:29:52 -0400, you said:
DS> Gisli Ottarsson wrote:
>> Please help me solve my eepro100 problem which I outline below.
>> Doorstop 486 PCI, Intel Saturn motherboard, 16Mb RAM :-(
>> Intel 82557 EtherExpressPro100B
>> Linux 2.2.13 stripped to the bare essentials. No module support.
>> Compiled with gcc version 2.95.1
>> Driver versions tested:
>> eepro100.c:v1.09l 8/7/99 (latest?)
>> eepro100.c:v1.06 10/16/98 (standard with 2.2.13)
>> eepro100.c:v1.05 10/16/98 (used below)
>> The frequently repeated suggestion to set the value of
>> multicast_filter_limit to 0 or 3 was tried (by editing eepro100.c)
>> but this did not affect my problem.
DS> That parameter doesn't affect the transmit timeout. It affects ethernet
DS> storms which eminate from the card when the card is used for multicast
DS> in certain situations.
DS> [other stuff deleted]
DS> What you don't say anywhere is what version of the eepro100 driver
DS> you're using. Since you've built this kernel, go to the source of the
DS> driver and give that info. There've been reports of a recent driver
DS> version having an effect on the transmit timeout problem, I think. (I
DS> haven't had the transmit timeout problem, only the multicast storm
DS> problem myself. Post the info to the list, and perhaps someone who's
DS> been tracking the transmit timeout problem will be able to help).
DS> Daniel Senie firstname.lastname@example.org
DS> Amaranth Networks Inc. http://www.amaranthnetworks.com