netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Auke Kok <auke-jan.h.kok@intel.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: profilek@users.sourceforge.net, squat@users.sourceforge.net,
	NetDev <netdev@vger.kernel.org>,
	Jesse Brandeburg <jesse.brandeburg@intel.com>,
	"Ronciak, John" <john.ronciak@intel.com>
Subject: Re: e1000 fails to load sometimes: The EEPROM Checksum Is Not Valid
Date: Thu, 13 Jul 2006 13:59:39 -0700	[thread overview]
Message-ID: <44B6B43B.6000005@intel.com> (raw)
In-Reply-To: <44B6B14A.3020001@goop.org>

Jeremy Fitzhardinge wrote:
> Auke Kok wrote:
>> Sorry for the long wait, there's some new information on this that 
>> just this morning arrived.
> Thanks for the update.
> 
>> The latest EEPROM's from Lenovo (obtainable from their websites as 
>> .iso) seem to have this feature turned off, which resolves the issue.
> 
> Do you have a specific link to this update?  I can't see anything 
> obvious on their site relating to this.

See:

http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-63027

links to the latest .iso image.

Note: I haven't tried the 1.07 update myself. I had to *downgrade* our test 
system to actually expose the bug.

Cheers,

Auke

  reply	other threads:[~2006-07-13 21:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-13 18:47 e1000 fails to load sometimes: The EEPROM Checksum Is Not Valid Auke Kok
2006-07-13 20:47 ` Jeremy Fitzhardinge
2006-07-13 20:59   ` Auke Kok [this message]
2006-07-13 21:07     ` Jeremy Fitzhardinge
2006-07-13 21:24       ` Auke Kok
2006-07-13 21:57         ` Jeremy Fitzhardinge
  -- strict thread matches above, loose matches on Subject: below --
2006-06-01 23:47 Jeremy Fitzhardinge

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=44B6B43B.6000005@intel.com \
    --to=auke-jan.h.kok@intel.com \
    --cc=jeremy@goop.org \
    --cc=jesse.brandeburg@intel.com \
    --cc=john.ronciak@intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=profilek@users.sourceforge.net \
    --cc=squat@users.sourceforge.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;
as well as URLs for NNTP newsgroup(s).