Hack/fix omitted from Ethernet-HOWTO and eexpress.c

Thread View: comp.os.linux.networking

2 messages

[T] Back to Threads [V] Tree View [G] Group Articles

2 total messages Started by Rohan Oberoi Sat, 17 Apr 1999 00:00

#645

Author: Rohan Oberoi
Date: Sat, 17 Apr 1999 00:00

21 lines
1698 bytes

After installing RedHat 5.2 (2.0.36) on a 486DX-66/16 with two Intel
EtherExpress NICs, I noticed the machine would completely hang (dead
screen, no network response -- hard reboot required) practically once
a day.  Recompiling with as many options taken out as possible had no
effect.  

An old copy from DejaNews of the Ethernet-HOWTO mentioned this
hack/fix: replace all instances of "outw(" with "outw_p(" in
drivers/net/eexpress.c.  After recompiling with this change, the
machine has now been up six days without a problem (it does still have
occasional "eth0: CU wedged, status 0140 0000, resetting..." messages
in /var/log/messages, but they no longer freeze the machine).

Does anyone know why this hack/fix was omitted from the HOWTO?  Or
whether there are reasons not to incorporate it into the eexpress.c
distribution?  

Regards,
Rohan.

(PS -- Please remove the obvious from return address if emailing.)

Re: Hack/fix omitted from Ethernet-HOWTO and eexpress.c

#644

Author: Timothy Legge
Date: Tue, 20 Apr 1999 00:00

47 lines
2476 bytes

I

I have been battling a problem that I believe is in the eexpress driver.  I
thought first, that it was the ftp client, however, your message may help.
This is the situation:

1) It worked fine,
2) I did a combination of things, including:
 1) Installed the kernel 2.2.X (original 2.0.x)
 2) Installed a Evergreen Processor upgrade
3) Reformatted and tried to install RedHat via ftp

I received the following error (looped over the screen like a bad basic
program, completely locked the machine):

eth0: Rx frame at 2d20 corrupted status 8cf7, cmd atff, next 6aee pbuf a380,
len 3031

I verified the following:

1) Removing the Evergreen Processor and setting the motherboard back to its
original state (except left it at 33(66) MHz instead of 25(50) MHz) allowed
the system to ftp correctly
2) Removing the linux drive and replacing it with a Windows 3.11 drive (Talk
about your backward steps) allowed me to set up networking and ftp.  (This
was with the Evergreen Processor in place)

This led me to believe, that it was not the card/processor/hardware, but the
Ethernet driver or the ftp client.

I then ftped to the linux box from windows, and tried to retrieve a file
from the linux box, this resulted in the same error on the linux box.

From this I deduced that the problem was probably not the ftp client, since
the ftp server had also been affected.  (This could be a major leap)

My linux system is the following:

Compaq 486 (Prolinea 4/25s)
16 MG of Ram
Intel EtherExpress 16
Processor upgraded with 486 Upgrade AMD 133 from Evergreen

I will attempt your hack/fix, do I need to recompile the entire kernel, or
just that module?

Tim Legge

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads