[eepro100] Working Now
Infinity2
infinity2@lock-net.com
Tue, 9 Jan 2001 14:21:48 -0500
This did the trick. I recompiled my 2.2.16 to remove the eepro100 from the
kernel, then changed the driver to the one below and it works like a charm.
Thanks a bunch Brian.
Rob Spurlock
Lock-Net
----------------------------------------------------------------------------
--------
Brian Said:
Rob,
FYI: I had very similiar problems back in september with Celeron + D815EAL
motherboard. I've seen many people with complaints on this lists for
months now. My solution was to use the intel supplied linux driver instead
of the one you are trying to use.
Haven't had any problems with it since september, and all 5 of the
servers are under heavy production load.
I used version 1.3.14 -- a newer version is released:
ftp://download.intel.com/support/network/adapter/pro100/e100-1.3.20.tgz
--brian
On Mon, Jan 08, 2001 at 10:17:53PM -0500, Infinity2 wrote:
> Ok, I just build another server, also using an Intel D815EAL. Same exact
> setup as the other one. Celeron 600cpu w/ 128mb ram (PC133 btw). both
> systems lockup doing ftp transfers. I didn't know for sure about the
first
> one, so I just opened up an ncftp session and downloaded something large
> from the internet. Netscape 6 was what I found (not planning on
installing
> it btw), didn't get very far then locked up tight. twice in a row. no
> errors, nothing, nothing to report either.
>
> So, I built another. i have parts for 2 of them (almost ready for the
> garbage) so i put together the second. i can hardly download anything.
> can't even get down new rpm or source code for the new kernels. i'm on my
> last nerve here and about to throw the motherboards out the window. I
don't
> understand how you guys make these motherboards work. what am i missing?
> i'm so fed up. 3 weeks lost and no servers to show for it. my boss is so
> pissed.
>
> do you guys have any input? where else can i go to find out about these
> boards?
>
> Thanks,
> Rob
>
> ----- Original Message -----
> From: "Infinity2" <infinity2@lock-net.com>
> To: <eepro100@scyld.com>
> Sent: Monday, January 08, 2001 7:41 PM
> Subject: Re: [eepro100] Next Problem with eepro100
>
>
> > I too did an eepro100-diag and the results are below. This is done
while
> > the NIC is "working". I'll try to get one when it stops. I have done
all
> > the security and bug updates I can find on RH's website. I'll see when
it
> > craps out again. Thanks!
> >
> > Rob Spurlock
> >
> > [root@NS1 /root]# ./eepro100-diag -Dvvfmaaee
> > eepro100-diag.c:v2.02 7/19/2000 Donald Becker (becker@scyld.com)
> > http://www.scyld.com/diag/index.html
> > Index #1: Found a Intel i82562 EEPro100 adapter at 0xdf00.
> > i82557 chip registers at 0xdf00:
> > 0c000050 07eae800 00000000 00080002 18250021 00000600
> > No interrupt sources are pending.
> > The transmit unit state is 'Suspended'.
> > The receive unit state is 'Ready'.
> > This status is normal for an activated but idle interface.
> > The Command register has an unprocessed command 0c00(?!).
> > EEPROM size probe returned 0xff80c03, 6 bit address.
> > EEPROM contents, size 64x16:
> > 00: 0300 1947 a4c0 1a03 0000 0201 4701 0000
> > 0x08: 0000 0000 49b2 3013 8086 007f ffff ffff
> > 0x10: ffff ffff ffff ffff ffff ffff ffff ffff
> > 0x18: ffff ffff ffff ffff ffff ffff ffff ffff
> > 0x20: ffff ffff ffff ffff ffff ffff ffff ffff
> > 0x28: ffff ffff ffff ffff ffff ffff ffff ffff
> > 0x30: 0000 ffff ffff ffff ffff ffff ffff ffff
> > 0x38: ffff ffff ffff 0000 ffff ffff ffff 9c13
> > The EEPROM checksum is correct.
> > Intel EtherExpress Pro 10/100 EEPROM contents:
> > Station address 00:03:47:19:C0:A4.
> > Board assembly 000000-000, Physical connectors present: RJ45
> > Primary interface chip i82555 PHY #1.
> > MII PHY #1 transceiver registers:
> > 3100 782d 02a8 0330 05e1 0021 0000 0000
> > 0000 0000 0000 0000 0000 0000 0000 0000
> > 2404 0000 0000 0000 0000 0000 0000 0000
> > 0000 0000 0000 0000 0010 0000 0000 0000.
> >
> >
> > ----- Original Message -----
> > From: "Eric Fikus" <eric@fikus.staticky.com>
> > To: <eepro100@scyld.com>
> > Sent: Monday, January 08, 2001 5:38 AM
> > Subject: Re: [eepro100] Next Problem with eepro100
> >
> >
> > > This is the ouput of 'eepro100-diag -Dvvfmaaee' after a
> wait_for_cmd_done
> > timeout message:
> > >
> > > eepro100-diag.c:v2.02 7/19/2000 Donald Becker (becker@scyld.com)
> > > http://www.scyld.com/diag/index.html
> > > Index #1: Found a Intel i82562 EEPro100 adapter at 0xdf00.
> > > i82557 chip registers at 0xdf00:
> > > 0cf00050 00fe0000 00000000 00080002 18250000 00000600
> > > No interrupt sources are pending.
> > > The transmit unit state is 'Suspended'.
> > > The receive unit state is 'Ready'.
> > > This status is normal for an activated but idle interface.
> > > The Command register has an unprocessed command 0cf0(?!).
> > > EEPROM size probe returned 0xff80c03, 6 bit address.
> > > EEPROM contents, size 64x16:
> > > 00: 0300 3e47 518c 1a03 0000 0201 4701 0000
> > > 0x08: 0000 0000 49b2 3013 8086 007f ffff ffff
> > > 0x10: ffff ffff ffff ffff ffff ffff ffff ffff
> > > 0x18: ffff ffff ffff ffff ffff ffff ffff ffff
> > > 0x20: ffff ffff ffff ffff ffff ffff ffff ffff
> > > 0x28: ffff ffff ffff ffff ffff ffff ffff ffff
> > > 0x30: 0000 ffff ffff ffff ffff ffff ffff ffff
> > > 0x38: ffff ffff ffff 0000 ffff ffff ffff ca47
> > > The EEPROM checksum is correct.
> > > Intel EtherExpress Pro 10/100 EEPROM contents:
> > > Station address 00:03:47:3E:8C:51.
> > > Board assembly 000000-000, Physical connectors present: RJ45
> > > Primary interface chip i82555 PHY #1.
> > >
> > > Thanks,
> > > Eric Fikus
> > >
> > > On Sun, Jan 07, 2001 at 03:19:35AM -0700, Eric Fikus wrote:
> > > > I am having a similar problem with kernels 2.2.18 and 2.4.0 with red
> hat
> > 7. I periodically get messages like:
> > > >
> > > > eepro100: wait_for_cmd_done timeout!
> > > > last message repeated 25 times
> > > > kernel: NETDEV WATCHDOG: eth0: transmit timed out
> > > > kernel: eth0: Transmit timed out: status 0050 0cf0 at 3244/3272
> command
> > 000c0000.
> > > >
> > > > After about a minute everything starts working again. Doing
> ifdown/ifup
> > eth0 also fixes the problem.
> > > >
> > > > I'm currently using the driver include with 2.4.0:
> > > > eepro100.c:v1.09j-t 9/29/99 Donald Becker
> > http://cesdis.gsfc.nasa.gov/linux/drivers/eepro100.html
> > > > eepro100.c: $Revision: 1.35 $ 2000/11/17 Modified by Andrey V.
> Savochkin
> > <saw@saw.sw.com.sg> and others
> > > >
> > > > Thanks in advance for any help.
> > > >
> > > > Eric Fikus
> > > >
> > > > _______________________________________________
> > > > eepro100 mailing list
> > > > eepro100@scyld.com
> > > > http://www.scyld.com/mailman/listinfo/eepro100
> > >
> > > _______________________________________________
> > > eepro100 mailing list
> > > eepro100@scyld.com
> > > http://www.scyld.com/mailman/listinfo/eepro100
> >
> >
> > _______________________________________________
> > eepro100 mailing list
> > eepro100@scyld.com
> > http://www.scyld.com/mailman/listinfo/eepro100
>
>
> _______________________________________________
> eepro100 mailing list
> eepro100@scyld.com
> http://www.scyld.com/mailman/listinfo/eepro100
--
The world's most ambitious and comprehensive PC game database project.
http://www.mobygames.com