Hi Pradyumna,
You may also consider applying for privilege access in our Research and Design center, kindly refer to the link below:
http://www.intel.com/content/www/us/en/design/support/account-support.html .
Once approved, This will allow access to Intel confidential content, pre-release information on upcoming products, advanced design tools, and support services to help with your design.
regards,
Vince
↧
Re: Voltage levels are not as per the specs of I210
↧
cannot disable 64-bit BAR on Intel X710 adapter
Hi,
I want (actually, I need) to disable 64-bit BAR on a two-port 10-Gbit Intel X710 adapter (because I'm booting the server via iSCSI, and it's unable to boot because while autoconfiguring the IBA receives 64-bit addresses, and this it's unable to live with it). When I use BootUtil (last version available, 1.6.36.0, launched from FreeDOS since Linux version requires some modules I'm unable to get) for it it says:
[...]
WARNING: BootUtil detected an older version of the device (location 129:0.0) NVM image that expected. Please update the NVM image. WARNING: BootUtil detected an older version of the device (location 129:0.0) NVM image that expected. Please update the NVM image. Disabling 64-bit BAR support on port 3... Error: Unsupported feature.
What am I doing wrong ? I have 4 ports listed by BootUtil, two are from on-board adapter, and two are from discrete XL710 network card, and ports 3 and 4 (device IDs 129:00.0 and 129::0.1) are exactly those. What is even most funny, when I ussue 'BootUtil.exe -ALL -64d', it's capable to disable 64-bit BARs on the on-board ports. In the same time the "Intel Boot Agent Application Notes for BIOS Engineers" clearly states:
c. Configure the Ethernet controller to only request 32-bit memory BAR addresses. All Intel PCIe Ethernet controllers have EEPROM settings that limit the device to advertising only 32-bit memory BAR support.
About the adapter: Linux reports it as (lspci -m)
81:00.0 "Ethernet Controller" "Intel Corporation" "Ethernet Controller X710 for 10GbE SFP+" -r01 "Intel Corporation" "Ethernet Converged Network Adapter X710-2" 81:00.1 "Ethernet Controller" "Intel Corporation" "Ethernet Controller X710 for 10GbE SFP+" -r01 "Intel Corporation" "Ethernet Converged Network Adapter X710"
and this means that it's Intel manufactured one, because the onboard ones say "Super Micro Computer Inc".
Now about this NVM message. I downloaded the latest NVM image and utility, version 5.05, and updated my adapters (the nvmupdate64e utility said there's no updates for the onboard ones, but updated the discrete ones), but the BootUtil still says that it doesn't like the version.
So I will really appreciate if someone will shed some light on this.
Thanks.
↧
↧
Re: XL710 Malicious Driver Detection Event Occured
And I bet this is FreeBSD you are getting these on.
↧
Re: XL710 Malicious Driver Detection Event Occured
After some consideration I realized that this is probably Linux. Long story short: this isn't happening to you - that's what the Intel support told me whan I had a chat with them not long ago about the exactly same issue. Although some people tend to see this.
I guess it's a driver issue. I mean the Intel driver, since yours is too from Intel definitely. Use X710, at least is what I do. If you have an Intel manufactured card - you can try to persuade them this isn't your imagination and you're actually seeing this. Mine was Supermicro "manufactured", so Intel said that's their issue (spoling - Supermicro spent two months just top avoid the reproduction of this issue in their lab, probably because they do know where it leads - to the same support dead end) , in the same time support guy told me that "they have no issue reports with this error on the original Intel boards", so, again, if your board is manufactured by the Itel - you could try.
↧
Re: I217-V problems
Hi Looperx,
Thank you for posting in Wired Ethernet Community.
Ultra low power is a feature on I218.
Based from the attempted fixes, you may consider checking with
Gigabyte support for hardware isolation since error code 10 would normally indicate hardware issue.
regards,
Vince
↧
↧
Re: Empty TCP payload caused by tx-scatter-gather in ixgbevf
Hi PieterLauwers,
Thank you for posting in Wired Ethernet community.
Based on the provided information, you may want to try out
the updated driver - ixgbe 4.4 and ixgbevf 3.2.2 for your HP 560FLB to check if it help in your issue.
Please refer to the HP website link for the drivers. Kindly take note Intel doesn't guarantee
the content of the site below.
http://h20566.www2.hpe.com/hpsc/swd/public/readIndex?sp4ts.oid=5274096&swLangOid=8&swEnvOid=4095
I'd also suggest contacting HP support for further assistance since our 82599 and X540 were integrated to their adapter, there might have customization to better fit into their product.
regards,
Vince
↧
Re: A bus fatal error was detected on a component at bus 0 device 0 function 0 With X710-DA4 FH Card. No error if this is removed.
Hi Dave1555,
Thank you for posting in Wired Ethernet Community.
Looking at the Dell PowerEdge R610 Technical Guide, page 13 under "Optional 1GBe and 10GBe add-in NICs" section, it mentioned Intel X520-DA2, I'd suggest
confirming with Dell Support the details of testing before including X520-DA2 in their list. Details such as server configuration, installed slot, operating system used, NIC configuration and driver used.
kindly refer to Dell PowerEdge R610 Technical Guide link below, please take note Intel does not guarantee the content in that site.
http://www.dell.com/downloads/global/products/pedge/en/server-poweredge-r610-tech-guidebook.pdf
regards,
Vince
↧
Re: x710 SR-IOV problems
Hi Ante, we're still checking your issue. On the other hand, you may also report this issue to Dell for further assistance.
regards,
Vince
↧
Win10 + I219-V + Intel ME + VLANs = BSOD
Yesterday I got an update for the Intel ME component for my MSI Z270 motherboard, and after I restarted the computer, it blue screened on me. I had to end up resetting the Windows install to be able to get access to the computer again, even while I had to download and reinstall all my apps (luckily I have all my files on a different drive).
I started my troubleshooting session. Downloaded all latest drivers for my setup, installed all but the Intel ME drivers, since it was the last thing I did before it broke it all. Ran the Windows update, reconfigured my VLANs, restarted a few times at drivers requests, with no issues. All was fine. Installed the ME drivers, restarted, BSOD. So yeah, I was on the right path.
Reset Windows one more time, installed Intel ME drivers first. Restarted the computer after each driver was getting installed, to find out which one was the ME driver getting upset with. All drivers installed, all was still fine, I felt confused. Ran Windows update, all still fine. Went configure my very first VLAN, BSOD. So I had a big hint.
I downloaded WinDBG and ran it against the memory.dmp files generated during the last BSODs and at all times the error was a memory corruption on the NDIS stack. Not much past that as by default Windows only dumps 200Mb of memory, and I had not changed to collect a full dump and force another crash (full dump sucks when you have 64Gb RAM).
The Intel ME driver 11.6.0.1036 caused this trouble, whereas with driver 11.6.0.1026 VLANs were working just fine. The only reason why I posted this report under Wired networks is because this is the component that is failing, not the ME - but I might either cross-post or have a mod move this thread there.
I am trying to get the previous ME driver 11.6.0.1026 with MSI to roll back and see if the VLAN will still work - I might have them take a look at this topic too. One end user reporting issues might not cause much attention, but a VAR reporting could take a very different route.
So if you happen to use a few advanced features and things got broken on you, hope this can help.
Other related drivers and product version:
Intel PROSet Version 22.0.18.0, with Windows driver version 12.15.23.9
Windows 10 Pro x64, Version 1067 Build 14393.
DUMP_CLASS: 1
DUMP_QUALIFIER: 401
BUILD_VERSION_STRING: 14393.953.amd64fre.rs1_release_inmarket.170303-1614
SYSTEM_MANUFACTURER: MSI
SYSTEM_PRODUCT_NAME: MS-7A69
SYSTEM_SKU: Default string
SYSTEM_VERSION: 1.0
BIOS_VENDOR: American Megatrends Inc.
BIOS_VERSION: 1.10
BIOS_DATE: 02/03/2017
BASEBOARD_MANUFACTURER: MSI
BASEBOARD_PRODUCT: Z270M MORTAR (MS-7A69)
BASEBOARD_VERSION: 1.0
DUMP_TYPE: 1
BUGCHECK_P1: 7
BUGCHECK_P2: d699
BUGCHECK_P3: b96acc4c
BUGCHECK_P4: ffffda87ad768208
POOL_ADDRESS: ffffda87ad768208
FREED_POOL_TAG: Filt
BUGCHECK_STR: 0xc2_7_Filt
CPU_COUNT: 4
CPU_MHZ: bb8
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 9e
CPU_STEPPING: 9
CPU_MICROCODE: 6,9e,9,0 (F,M,S,R) SIG: 48'00000000 (cache) 48'00000000 (init)
DEFAULT_BUCKET_ID: CODE_CORRUPTION
PROCESS_NAME: System
CURRENT_IRQL: 2
ANALYSIS_SESSION_HOST: HQUEST
ANALYSIS_SESSION_TIME: 03-19-2017 17:22:22.0774
ANALYSIS_VERSION: 10.0.14321.1024 amd64fre
LAST_CONTROL_TRANSFER: from fffff803f9060cf3 to fffff803f8f657c0
STACK_TEXT:
ffff8e80`5c558da8 fffff803`f9060cf3 : 00000000`000000c2 00000000`00000007 00000000`0000d699 00000000`b96acc4c : nt!KeBugCheckEx
ffff8e80`5c558db0 fffff80b`f261fbb5 : ffffda87`ad768208 00000000`0000009c ffff8e80`5c558f40 00000000`0000006a : nt!ExFreePool+0x1d3
ffff8e80`5c558e90 fffff80b`f24d8182 : ffff8e80`5c559240 ffff8e80`5c558f49 ffff8e80`5c558fd0 ffffda87`a8421260 : ndis!NdisFreeMemory+0x15
ffff8e80`5c558ec0 fffff80b`f24d2dc2 : ffffda87`99ce1a20 fffff80b`f262766f 00000000`00000000 ffffda87`98fb1c10 : iansw60e+0x8182
ffff8e80`5c558fb0 fffff80b`f262750d : ffffda87`98fb1c10 ffff8e80`5c559130 ffff8e80`5c559240 ffff8e80`5c559410 : iansw60e+0x2dc2
ffff8e80`5c559000 fffff80b`f26270c4 : 00000000`00000002 ffffda87`ad9481a0 ffffda87`ad9481a0 ffffda87`ad9481a0 : ndis!ndisInvokeStatus+0x39
ffff8e80`5c559030 fffff80b`f2626ab8 : ffffda87`ad9481a0 00000000`0000000c ffffda87`ad9481a0 00000000`00000000 : ndis!ndisIndicateStatusInternal+0x464
ffff8e80`5c559210 fffff80b`f26ba175 : ffffda87`ad9481a0 ffffda87`ad9481a0 00000000`00000000 ffffda87`a23fcc00 : ndis!ndisIndicateInitialStateToBinding+0x304
ffff8e80`5c559500 fffff80b`f26b3f29 : ffffb101`5d1c5d70 ffffb101`6816a278 ffffb101`6dd50740 ffffb101`6816a278 : ndis!ndisBindNdis6Protocol+0x541
ffff8e80`5c5597a0 fffff80b`f26b5c2d : ffffda87`ad9481a0 00000000`000013d0 00000000`000013e8 00000000`00000002 : ndis!ndisBindProtocol+0x55
ffff8e80`5c559880 fffff80b`f26b588c : ffff8e80`5c559ad0 ffffda87`ad9495f8 ffffda87`ad949630 ffff8e80`5c559ad0 : ndis!Ndis::BindEngine::Iterate+0x34d
ffff8e80`5c559a80 fffff80b`f26b567a : ffffda87`ad086800 ffffb101`6816a2b8 ffffda87`ad193dc0 00000000`00000000 : ndis!Ndis::BindEngine::UpdateBindings+0x44
ffff8e80`5c559ab0 fffff803`f8e7c6f9 : ffffda87`ad086800 ffffda87`ad949630 ffffda87`00000000 fffff803`00000000 : ndis!Ndis::BindEngine::UpdateBindingsWorkItem+0x3a
ffff8e80`5c559b00 fffff803`f8ecd2d5 : ffff8e80`57017180 00000000`00000080 ffffda87`98477040 ffffda87`ad086800 : nt!ExpWorkerThread+0xe9
ffff8e80`5c559b90 fffff803`f8f6ac86 : ffff8e80`57017180 ffffda87`ad086800 fffff803`f8ecd294 00310100`0d010900 : nt!PspSystemThreadStartup+0x41
ffff8e80`5c559be0 00000000`00000000 : ffff8e80`5c55a000 ffff8e80`5c553000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
↧
↧
Intel Pro 1000 PT Dual - Windows 10 x64 - ANS NIC Teaming
I am running Windows 10 x64 using a Intel Pro 1000 PT Dual Nic. The latest 22.0.1 drivers say they have ANS support for NIC Teaming to finally work on Windows 10 with The Anniversary update.
When I go to configure the adapter I don't get he Nic teaming options in the Adapter Properties dialog menu.
Are the drivers not updating on my PC or are there no driver updates for this card? Or does the 1000 PT dual not work with Teaming even if I had it installed and the teaming options available.
I have another Intel Nice on my computer I217-LM and it has the Teaming properties in the adapter properties dialog menu. If i choose both the PT 1000 ports I get an error when trying to setup the Team.
Error: "Each team must include at least one Intel server device or Intel integrated connection that supports teaming."
Am I missing something here?
Thanks,
Brian
↧
Re: x710 SR-IOV problems
Hi Vince,
Dell is trailing latest driver version by couple of revisions, not sure how much of support is possible to get there. If I downgrade driver, then I have MDD events, and I am back at the beginning, kind of a loop situation.
Let me know if you figure something out.
BR,
Ante
↧
Re: Intel Pro 1000 PT Dual - Windows 10 x64 - ANS NIC Teaming
Hi Brian,
Thank you for posting in Wired Ethernet Community.
The only driver for Intel® PRO/1000 PT Server Adapter in Windows 10 is the one supplied by Microsoft that comes with the Operating System. For list of Intel Server Adapter that supports ANS in Windows 10, please refer to the link below.
http://www.intel.com/content/www/us/en/support/network-and-i-o/ethernet-products/000020905.html
Kindly look for adapter model with "Yes" under "Full Support".
regards,
Vince
↧
Re: cannot disable 64-bit BAR on Intel X710 adapter
Hi drookie,
Thank you for posting in Wired Ethernet Community.
While I'm still checking your query, please share the PXE image "version" loaded and "flash firmware" details of your X710, These information can be found in the right side of the NIC entry after entering "booutil" command under FreeDOS.
regards,
Vince
↧
↧
Re: cannot disable 64-bit BAR on Intel X710 adapter
Hi drookie,
Thank you for posting in Wired Ethernet Community.
While I'm still checking your query, please share the PXE image "version" loaded and "flash firmware" details of your X710, These information can be found in the right side of the NIC entry after entering "bootutil" command under FreeDOS.
regards,
Vince
↧
Re: cannot disable 64-bit BAR on Intel X710 adapter
Hello,
"Firmware" column shows "Not Present" for both ports of the discrete card, thus "version" column is blank. I've already tried to update the flash on this adapter using BootUtil and the supplied bootimage.flb file from the BootUtil tarball, but the BootUtil said after I issued the bootutil.exe -nic=3 -up=iscsi -file=..\bootimage.flb:
Option ROM area in the flash is not supported for this device on port 3.
↧
Re: Where to download NVM update 5.51 for XXV710 ?
Hi Jeanmick,
Please feel free to update me if you still have other inquiries.
rgds,
wb
↧
Re: VLAN adapter not working after reboot - Win10, 22.0.1
Hi Aurelio,
Thank you for the information. will check on this.
rgds,
wb
↧
↧
Re: IEEE 1588 hardware implementation.
Hi Pfrechette,
Please register at embedded design center to access the information.
http://www.intel.com/content/www/us/en/design/support/account-support.html
Rgds,
wb
↧
Re: igb SR-IOV vf driver on FreeBSD strips VLAN tags
Hi ingenium,
Can you provide the exact igb and igbvf driver version used ?
Thanks,
wb
↧
Re: XL710 Malicious Driver Detection Event Occured
HI Hsuivan,
Can you provide more information about what is the exact NVMe firmware version and the exact XL710 NIC model?
Thanks,
wb
↧