From: thockin@hockin.org
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: John <me@privacy.net>,
linux-kernel@vger.kernel.org, linux.nics@intel.com
Subject: Re: Intel 82559 NIC corrupted EEPROM
Date: Fri, 3 Nov 2006 22:28:08 -0800 [thread overview]
Message-ID: <20061104062808.GA15871@hockin.org> (raw)
In-Reply-To: <20061104062251.GA15100@hockin.org>
On Fri, Nov 03, 2006 at 10:22:51PM -0800, thockin@hockin.org wrote:
> On Fri, Nov 03, 2006 at 05:46:25PM -0800, H. Peter Anvin wrote:
> > Basically, Auke wants you to throw away your NIC and/or motherboard.
> > Since you're effectively dead, the only damage you can do by disabling
> > the check has already been done. This unfortunately seems to be fairly
> > common with e100, especially for the on-motherboard version, and you
> > basically have two options: either disable the check or write an offline
> > tool to reprogram the EEPROM.
>
> I have a tool to write the eepro100 EEPROM. Let me see if I can find it.
> It even had all the default data coded, ready to restore a NIC to default.
>
> However - back in the eepro100.c days, it was considered a warning only if
> the EEPROM had a bad checksum. There were two "supported" formats for the
> EEPROM, one of which was just the MAC address. And it worked!
One from the vaults: http://www.hockin.org/~thockin/enet_eeprom/
It's pretty simple, but easily hacked. ifdown your interface first! :)
Tim
next prev parent reply other threads:[~2006-11-04 6:28 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-03 17:28 Intel 82559 NIC corrupted EEPROM John
2006-11-04 1:46 ` H. Peter Anvin
2006-11-04 6:22 ` thockin
2006-11-04 6:28 ` thockin [this message]
2006-11-07 11:23 ` John
2006-11-07 17:17 ` H. Peter Anvin
2006-11-07 17:43 ` Auke Kok
2006-11-07 18:27 ` H. Peter Anvin
2006-11-07 18:34 ` Auke Kok
2006-11-07 18:38 ` H. Peter Anvin
2006-11-08 10:55 ` John
2006-11-08 16:17 ` Auke Kok
2006-11-09 12:17 ` John
2006-11-09 17:03 ` Auke Kok
2006-11-08 17:26 ` Jesse Brandeburg
2006-11-09 14:15 ` John
2006-11-10 0:19 ` Jesse Brandeburg
2006-11-10 12:03 ` John
2006-11-15 8:34 ` John
2006-11-27 14:17 ` John
2006-11-27 20:34 ` Jesse Brandeburg
2006-11-29 11:26 ` John
2006-11-29 18:55 ` Jesse Brandeburg
[not found] ` <45704001.9040108@privacy.net>
2006-12-04 23:26 ` Jesse Brandeburg
[not found] <fa.FcMVUlqOXU3cAnxsPEN6d8T0wxU@ifi.uio.no>
[not found] ` <fa.0FC8eT8GQaLxmNQTrsqyNFjRK4E@ifi.uio.no>
[not found] ` <fa.nds0CFkNbotWh4VNM05EixY68wE@ifi.uio.no>
[not found] ` <fa.K3Gpuu7oYQv+4q85Ziy3ljV6u+E@ifi.uio.no>
[not found] ` <fa./RNOPU0DwWMrnKJSqlMaY+Y16JM@ifi.uio.no>
[not found] ` <fa.yV32AYzot0OkvPVCY7VTCvd6rJw@ifi.uio.no>
2007-02-07 11:06 ` John
2007-02-13 19:45 ` Brandeburg, Jesse
-- strict thread matches above, loose matches on Subject: below --
2007-08-14 16:35 Amin Azez
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20061104062808.GA15871@hockin.org \
--to=thockin@hockin.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux.nics@intel.com \
--cc=me@privacy.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox