On Tue, Jul 26, 2016 at 3:22 AM, Alexey Muranov
<alexey.mura...@gmail.com> wrote:
>
>>>> I executed bootutil64e from Intel Ethernet Connections Boot Utility (
>>>> https://downloadcenter.intel.com/download/19186 ) under Ubuntu, here is the
>>>> output:
>>>>
>>>>   Intel(R) Ethernet Flash Firmware Utility
>>>>   BootUtil version 1.6.13.0
>>>>   Copyright (C) 2003-2016 Intel Corporation
>>>>
>>>>   Type BootUtil -? for help
>>>>
>>>>   Port Network Address Location Series  WOL Flash Firmware                
>>>> Version
>>>>   ==== =============== ======== ======= === ============================= 
>>>> =======
>>>>     1   D017C2201F59     0:31.6 Gigabit N/A FLASH Not Present
>>>>
>>>>
>>>> This made me think: if BootUtil reports that "FLASH Not Present", could it
>>>> mean that NVM is not used at all and its contents is random?  If this is 
>>>> the
>>>> case, shouldn't e1000e detect this and not test the checksum?
>
>
>
>>> The flash and NVM are two separate items.  The flash enables things
>>> like PXE booting and iSCSI whereas the NVM stores things like the
>>> Network Address.
>
> Nevertheless, it looks like someone in 2011 managed to use BootUtil to fix 
> the NVM:
>
> https://thesorcerer.wordpress.com/2011/07/01/guide-intel-82573l-gigabit-ethernet-with-ubuntu-11-04-and-fix-pxe-e05/
>
> However, taking into account the disclaimer in the end, i do not feel like 
> trying this right away.
>
> - Alexey.

Like I said in my earlier email all that needs to happen is an update
to the NVM to force the checksum to be redone.  In the case of the
BootUtil program what it is doing is adding a flash so as a result it
goes through and sets the  configuration for the flash which happens
to exist in the NVM.

So for example in the case of one of my test systems I can go through
and enable the flash for the LAN port on my motherboard.  That in and
of itself doesn't change anything in the NIC EEPROM, however if I then
go into the configuration bits for the port in my BIOS and alter the
PXE link speed or wake on LAN settings I can see that it ends up
changing the EEPROM on the device.

So one thing you may want to try would be to modify the driver as I
suggested in the previous email, then use the "ethtool -e <dev>"
command to capture a copy of your current EEPROM.  Then try digging
through your BIOS to see if you have options for enabling the flash
image for the device, and if so if it will allow you to modify any
options for the port that might trigger the NVM to be updated.  You
should be able to verify if anything changes by just comparing the
most recent EEPROM dump via "ethtool -e" to what you captured before
you started making any changes.

- Alex

------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports.http://sdm.link/zohodev2dev
_______________________________________________
E1000-devel mailing list
E1000-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/e1000-devel
To learn more about Intel&#174; Ethernet, visit 
http://communities.intel.com/community/wired

Reply via email to