From: Auke Kok <auke-jan.h.kok@intel.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Auke Kok <auke-jan.h.kok@intel.com>,
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 14:24:38 -0700 [thread overview]
Message-ID: <44B6BA16.5040902@intel.com> (raw)
In-Reply-To: <44B6B5FB.6070400@goop.org>
Jeremy Fitzhardinge wrote:
> Auke Kok wrote:
>> 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.
> This appears to be a link to the T60 1.06 update. Do you know if
> they're planning an X60 update too?
x60 bios upgrade 1.06 is here: (found by typing "x60 bios" in the search bar
on the same website)
http://www-307.ibm.com/pc/support/site.wss/license.do?filename=mobiles/7buj04uc.iso
unfortunately the changelog for this BIOS upgrade doesn't tell us much if the
DSPD feature was affected or not. I also have not tried this one either.
Cheers,
Auke
next prev parent reply other threads:[~2006-07-13 21:25 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
2006-07-13 21:07 ` Jeremy Fitzhardinge
2006-07-13 21:24 ` Auke Kok [this message]
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=44B6BA16.5040902@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.