From: Amin Azez <azez@ufomechanic.net>
To: linux-kernel@vger.kernel.org, jesse.brandeburg@gmail.com,
me@privacy.net, hpa@zytor.com
Subject: Re: Intel 82559 NIC corrupted EEPROM
Date: Tue, 14 Aug 2007 17:35:23 +0100 [thread overview]
Message-ID: <46C1D9CB.9040208@ufomechanic.net> (raw)
Regarding the thread accessible at:
http://groups.google.com/group/linux.kernel/browse_frm/thread/bdc8fd08fb601c26
that ended with "looks like it is specific to your hardware",
Can I check where we are with this?
I've just had a small installation run fail on 3 boxes with the same
problems, on new hardware, which sort of suggests there is no longer a
shortage of test scenarios.
To summarise, in my case it looks as though it really was a bad
checksum, by using the eepro100 driver and the lucky-fortune eeprom tool
at http://www.hockin.org/~thockin/enet_eeprom/enet_eeprom.tgz I was able
to re-write the mac address and thus have the EEPROM checksum re-calculated.
I don't recall the original reporter (John) saying that he had tried this.
I'm still checking with my supplier to see how this could have happened.
Sam
next reply other threads:[~2007-08-14 17:37 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-14 16:35 Amin Azez [this message]
[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 --
2006-11-03 17:28 John
2006-11-04 1:46 ` H. Peter Anvin
2006-11-04 6:22 ` thockin
2006-11-04 6:28 ` thockin
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
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=46C1D9CB.9040208@ufomechanic.net \
--to=azez@ufomechanic.net \
--cc=hpa@zytor.com \
--cc=jesse.brandeburg@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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
Powered by JetHome