Intel 82579V has the ID 8086-1503, while i350-T2 has the ID 8086-1521. The support in UBU is the following:
- EFI 0.0.07 supports both, while ROM 0.1.04 supports only 82579V
- EFI 6.9.07 supports only i350-T2, ROM 1.5.72 supports only i350-T2
- EFI 6.6.04 supports both, ROM 1.5.62 supports both
This means that UBU does the right thing, which was already tested by others. As to why he is getting the opposite, I suspect it is either because of his system getting confused by 2 controllers and 3 ports, or he flashed something else. You can see in this post that he already has done other changes to the file, so a clear statement on what he changed/updated and with what UBU version, is a necessary step. Secondly, from where he gets that version of 6.1.16? The original file has 5.5.23, while UBU is offering 0.0.07/6.9.07/6.6.04. Has he ever updated to that version with UBU or MMTool?
My stand on this problem is that it is mainboard or user specific, not something related to UBU. When you have X reports that the new select method works and one report that claims the opposite of what Intel itself wrote in the modules, I would trust the X reports. I’m not saying inuchanbt did something wrong, but his screens support my statement. Apart from the bogus 6.1.16, do I see a “Connected” status on all 3 ports? I would very much doubt he has 3 Lan cables connected to his board, but he can clarify this and the other questions.
I can confirm that since UBU 1.32.1, I can boot off the Intel 82579V correctly but with the 6.8.x versions of the OROM, I couldn’t boot off the Intel 82579V even though I enabled the Network Stack in the BIOS.
@lordkag
I am sure with double check that I had flashed with the option 2 (EFI 6.9.07) by UBU v1.33.
I also checked my I350-T2 board with other system and found that it has EFI v6.1.16.
As you suggesting, my local environment may cause the opposite. The BIOS menu of the i350-T2 2nd port reports it is disconnected but all the three ports are surely connected to Cisco C2960G switch but all the three ports of the switch are configured with IEEE 802.3ad teaming members.
I have no idea why this happens but I just can say that now 82579V and i350-T2 1st port are controlled by EFI 6.9.07 of i350-T2 while i350-t2 2nd port is controlled by EFI v6.1.16 of the mainboard in fact.
It can not be. Version 6.8. does not support the 82579 chip.
If you are not hard, please, do the following:
enable in BIOS full UEFI mode
after reboot, make screenshots tabs network cards.
@inuchanbt
@lordkag
It seems that the version 6.1.16 flashed into the very network cards i350-T2, and make them a priority.
What if the update network cards i350-T2 to the latest version 6.9.07?
Added:
https://downloadcenter.intel.com/downloa…and-EFI-Drivers
I think that if you update the network card I350-T2 to the latest version 6.9.07, then the controller 82579, will have to get version of the BIOS of the motherboard.
Since your UBU 1.3.2.1 which contained the 82579V OROM 1.0.4, it now works perfectly. 
Thanks anyway.
@ rootuser123
We are now EFI interest instead OROM
@inuchanbt
I started with the wrong assumption that i350-T2 is on board, so much that I missed the part “in PCI-E slot” and couldn’t understand why you had 6.1.16 and why you said “conflicts with UEFI driver v6.1.16 on the i350-T2”. Talk about cognitive dissonance! Now that I’m awaken, here is what is happening:
- your UEFI firmware from mainboard loads one version of Intel EFI UNDI driver, the external card loads another.
- in the ideal situation, the BIOS/UEFI would be smart enough to handle the situation and handle each controller with their EFI driver. This is not happening, for some reason.
- with the original and unmodified BIOS you probably see 5.5.23 for onboard and 6.1.16 for each of the 2 ports from external card, or 6.1.16 for all. You can check this, if you want.
- with UBU option 1, even though 0.0.07 should support both, you get an incompatibility between newer branch of 0.0.07 and older branch of 6.1.16. But 0.0.07 is too fresh to be taken into consideration, not to mention it is unsigned.
- with UBU option 2 you get 6.1.16 loaded for onboard (it supports both) and 6.9.07 loaded for external (supports only i350-T2). The loading of 6.1.16 for the first port of external card is confusing beyond words, not sure how the card operates with two drivers at the same time. This is a sign that you shouldn’t use this option either.
- with UBU option 3, even though 6.6.04 supports both, you get an incompatibility between older branch of 6.1.16 and newer branch of 6.6.04.
- You can thank Intel for all the above mess. Why they split the original working driver into 3 parts that overlap and break each other, only their mind knows.
The only way to fix this is to flash the chip of i350-T2 with Intel dedicated tools. If you don’t want to take the risk, I suggest to simply ignore the updating of Intel Lan modules in UBU. But if you want to update, you have two options:
1. Update i350-T2 to 6.9.07 (or any higher version), update onboard to 6.6.04 - last working version. The only question is if these are compatible or Intel broke them long before 6.6.04. You also have the option of 0.0.07 for onboard (still updated), but the incompatibility might be even more pronounced. Or none at all, only a test can tell.
2. Update onboard and external to 6.6.04, the last working version for both. I don’t know if the BIOS will still load a separate driver for each controller, but at least 6.6.04 should be compatible with 6.6.04. Again, 0.0.07 is compatible, but the driver is not mature, you will have to flash each new version, you never know when Intel will remove support for older controllers.
If you decide to flash, take the last published file from here and use BootUtil in DOS. For your own sake, read the commands. For your own safety, dump the current image first and upload it here. It could be that the image is a multi-ROM with PXE+EFI or a single EFI, it might have a modified EFI… Once you upload the dump, I can tell you what image you need and me or Sonix will tell you what to flash. The command will probably be “Bootutil -devid=0x1521 -di=pxe+efi” for getting the small file or “Bootutil -Nic=x -up=pxe+efi -file=bootimg.flb” for direct flashing, but let’s not jump to conclusion.
Edit:
@Sonix, you misunderstood the report from rootuser123. He said the same thing as you, that 6.8.xx/6.9.xx is NOT supported by 82579V. This shows once again that the current options in UBU are good. And yes, we had the same idea and solution for inuchanbt. He needs to flash his external card separately or simply ignore UNDI drivers.
I would add that verdion EFI driver 6.6.04 in Intel® Ethernet Connections Boot Utility, Preboot images, and EFI Drivers 6/16/2015 20.0
6.9.07 -> 20.3
@lordkag
Support for the 82579V/LM is not in the version 6.7.xx . Personally I tested the Asus P8Z77-V.
Edit:
I forgot to add that now flashed EFI UNDI version 0.0.07, works without problems.
Yes, the last version to support 82579V/LM is 6.6.04, but I only written 6.8.xx/6.9.xx as a reference to rootuser123 post. Good call on posting the PREBOOT with 6.6.04. But is that necessary, is BootUtil not able to flash a small ROM image? Is the .FLB image a requirement?
I dont know. I have no external network cards Intel to test.
@lordkag , thanks for your detailed consideration and advice.
I love updating i350-T2! But now I cannot reboot this system so I will try to dump the image on i350-T2 by Bootutil later.
FYI, I upload the boot options of i350-T2 #1 and #2 on Intel Proset 10.3. I cannot find the same of 82579V.
#1 It says that on the Main window (left), Intel boot agent is currently disabled. On the Flash Information window (right), version numbers are not displayed for LAN on Motherboard (LOM) devices.
#2 EFI Version: 6.1.16, PXE Version: 1.5.50
Sorry, it’s Japanese but I have no idea how to change language for this.
@lordkag @SoniX
I tried bootutil and this attempt could let me realized many things.
Anyway, I upload the dumped file now.
I350#1.zip (162 KB)
I350#1.BIN - contains, in order:
1 OROM PXE
2 EFI UNDI as OROM.
How to collect the image of a hand, I do not know. We must look BootUtil commands.
@lordkag , @SoniX
I tried bootutil in DOS booted from USB flash drive.
This is the result of bootutil withaout any options.
Intel(R) Ethernet Flash Firmware Utility
BootUtil version 1.5.69.0
Copyright (C) 2003-2015 Intel Corporation
Type BootUtil -? for help
Port Network Address Location Series WOL Flash Firmware Version
==== =============== ======== ======= === ============================= =======
1 5404A64B7FA3 0:25.0 Gigabit YES FLASH Not Present
2 2C534A011334 10:00.0 Gigabit YES UEFI,PXE Enabled 1.5.50
3 2C534A011335 10:00.1 Gigabit YES FLASH Disabled
Port 1 should be 82579V on board.
Port 2 should be i350-T2 port 1.
Port 3 should be i350-T2 port 2.
So, I dumped by BOOTUTIL -SI -NIC=2 -FILE=I350#1.BIN.
-NIC=3 option dumped exactly the same.
-NIC=1 option occurred an error and nothing dumped.
The firmware of the Port 3 is disabled. This is the reason why only the i350-T2 port 2 is controlled by v6.9.07 of P9X79 Deluxe BIOS, I believe.
I also found these three messages while booting in this order.
PXE-E01: PCI Vendor and Device IDs do not match!_
Initializing Intel(R) Boot Agent GE v1.5.50
PXE 2.1 Build 092 (WfM 2.0)
Press Ctrl+S to enter the Setup Menu…
Initializing Intel(R) Boot Agent GE v1.5.72
PXE 2.1 Build 092 (WfM 2.0)
Press Ctrl+S to enter the Setup Menu…
The 1st (error) message appeared even without i350-T2 board so that it should be for 82579V.
The 2nd message should be for i350-T2 port 1.
The 3rd message should be for i350-T2 port 2.
@lordkag , @SoniX
I tried all the four patterns of enable / disabled status for i350-T2 flash rom.
i350 chip always prefers own UEFI driver v6.1.16 but likes v6.9.07 on P9X79 Deluxe BIOS better than her partner’s.
Of course, v6.9.07 doesn’t know 82579V so that his menu disappears when all the v6.1.16 are disabled.
Additionally, I found an interesting side effect. Any USB flash drives connected to the on-board USB2.0 port of the chipset cannot be detected by BIOS when even one UEFI driver v6.9.07 is active.
I tried most of all the USB2.0 ports including internals and five kinds of USB flash drives, and got the same result for all. But in any conditions, USB BD-RW can always be detected by BIOS.
Every NIC port governed by v6.9.07 is always disconnected in the BIOS menu and this might have some relation with this phenomenon because all the NIC and USB port can be used after Windows driver is loaded but I have completely no idea about the reason.
I have noticed USB2.0 ports cannot detect USB flash drives but I didn’t investigate the causes because the the on-board USB3.0 (ASM1042) ports work well enough.
Test Result NIC menus on BIOS.zip (1.8 MB)
The good news is that the image on i350-T2 is not modified from original and it is composed as Sonix said = PXE 1.5.50 + EFI 6.1.16, which you already know. The image has some Combo Rules before ROMs, so it appears it was flashed with the full BootImg.FLB image. You can obtain a small image with “bootutil -devid=0x1521 -di=pxe+efi” from PREBOOT 19.0 and compare for yourself. Now, for your messages:
- no flash information or devices for onboard because it has no chip, it takes the PXE/EFI from mainboard chip. It can’t be flashed with BootUtil, use UBU for updating.
- the second flash is disabled and can be toggled with -FLASHENABLE or -FE vs -FLASHDISABLE or -FD, if it really has a secondary chip to flash the image. It just might depend on the chip of first port.
- if you get the messages “Initializing Intel(R) Boot Agent GE v1.5.5x” on the same configuration, with nothing flashed in between, it probably means that there is a firmware for the second port, but is locked from upgrading. See above.
- the USB issue is something to investigate on your own, with different configurations.
- your chart is interesting, but it starts with a wrong base, 6.1.16 and 6.9.07 are different branches and incompatible. That’s why you get Disconnected on such combinations. The last pattern has both flash devices disabled, thus the full Disconnected.
I would suggest you try my two suggestions from yesterday. You need to flash i350-T2 with either 6.6.04 or 6.9.07, then use UBU with option 3. The flash command should be “BOOTUTIL -nic=x -up=pxe+efi” and BootImg.flb should be in the same folder. Maybe you can also enable the second flash device and flash it with the same version as port 1. Then you can do your full tests and report back which works.
Edit: The chart is more complicated than I first thought:
- onboard seems to prefer highest version available, which happens to be 6.1.16 from external. If you remove external, I’m sure it will work with UBU option 1 and 3.
- when a flash is enabled, it takes the image from its chip.
- when a flash is disabled, it takes the image from onboard.
- 6.1.16 and 6.9.07 should be incompatible, but why pattern 2 and 3 have different result on 6.1.16?
- pattern 4 suggest that a flash must be enabled for Connected. Or that 6.9.07 is incompatible when loaded from onboard.
- you need to flash i350-T2 and enable both devices if you want some peace of mind. Or have the same version for onboard and external.
Waiting for my new Z170 motherboard: is UBU compatible with it’s bios? Thanks…
X99 and SKL-platform - Aptio 5. Only update EFI files.
In UBU v1.35 added update the GOP Driver SKL.
@lordkag @inuchanbt
I made a comparison. If we remove the file I350#1.BIN all the headlines FLB, the files are identical.
In general, it is necessary to update both network cards i350-T2. Then it is possible that a version conflict disappears.
@lordkag , @SoniX
I tried i350-T2 with v6.9.07 and BIOS with v0.0.07 (option 1 by UBU 1.33 LAN menu).
I updated port #1 of i350-T2 then both #1 and #2 are updated, as you suggested.
Now on-board USB2.0 of my system has become quite unstable.
I should also try v6.6.40 but now P9X79 Deluxe BIOS cannot be updated to any versions even by BIOS Flashback so now I am investigating it.