On Thu, Nov 15, 2012 at 6:56 PM, Ronciak, John <john.ronc...@intel.com>wrote:
> > -----Original Message-----
> > From: Paul Gortmaker [mailto:paul.gortma...@gmail.com]
> > Sent: Wednesday, November 14, 2012 4:23 PM
> > To: e1000-devel@lists.sourceforge.net
> > Subject: [E1000-devel] Successful rescue of older E1000 with corrupted
> EEPROM
>
[...]
>
> >
> > Good luck in your own rescue attempts!
>
> Hi Paul,
>
> Thanks for all the work here. However, please be careful in doing this.
> If you write the wrong EEPROM image to your corrupted EERPOM you could
> brick your NIC/LOM worse than it is already. You could get it into such a
> state that it won't even show up on the PCI bus. I totally understand
> where you are going with this and while it may help some it could also hurt
> others who use an incompatible EEPROM image as the "good" source for the
> EEPROM. In addition, since you are using LOM devices in this example, the
> maker of the platform that has the LOM on it can have specialized
> parameters in the EEPROM which might not be set unless the exact EEPROM
> image is burned to the device. This may enable or disable features the
> manufacturer wants to have enabled or disabled for various reasons. So if
> the exact EEPROM image is not used to correct the corrupted EEPROM, there
> can be problems with doing this.
>
> This is just a word of warning. We cannot be responsible for problems
> incurred from following these instructions.
>
> We do appreciate the work you have done here. It may help some people.
>
Thanks John for the follow-up. You are correct that people should not jam
any
random EEPROM data from one board/card/revision into another, and I hope
that nothing I described in my post gave that impression, since I only fixed
two corrupted bytes in a case where the corruption was clear. Folks should
not write platform specific EEPROM data from one system to another any
more than they would take a MSI BIOS image and write it to an ASUS
motherboard just because they shared a common chipset. At the same time,
I'd hate to see the knowledge exchange muted simply over concerns about
the always present "I will cut and paste this because I found it on the
internet"
crowd, since they will always be present, and will find an infinite number
of
ways to vandalize their hardware, their environment, and anything else they
can manage to touch -- regardless of the number of disclaimers issued.
Paul.
--
>
> Cheers,
> John Ronciak
> Intel Corp.
>
>
>
------------------------------------------------------------------------------
Monitor your physical, virtual and cloud infrastructure from a single
web console. Get in-depth insight into apps, servers, databases, vmware,
SAP, cloud infrastructure, etc. Download 30-day Free Trial.
Pricing starts from $795 for 25 servers or applications!
http://p.sf.net/sfu/zoho_dev2dev_nov
_______________________________________________
E1000-devel mailing list
E1000-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/e1000-devel
To learn more about Intel® Ethernet, visit
http://communities.intel.com/community/wired
