Hi there. How to remove "iSCSI remote boot" screen on system startup?
↧
Intel I210-T1: remove "iSCSI Remote Boot"
↧
Script to create Intel teaming
Hi ...
Does anyone know how to use Netcmdlets in powershell script to create intel teaming,
and setting up the Speed
Thanks for your Quick Prompts.
↧
↧
Intel boot agent
Acer Altos T11o F3 Server plus Intel server Adapter I340 F4
I have installed a Smoothwall Linux System but I am unable to boot from the harddisk due to PXE trying three times to boot from the internet then only option is to cycle back. The BIOS is version P11 and although previous BIOS versions provided a setting on the first page to turn off PXE, I can't find same on P11.
I believe BootUtil.exe -ALL -FD will disable all adapters, but I have no experience and have no idea how to run the app in my present circumstances.
Your advice would be much appreciated.
Regards,
Kevin.
↧
Intel ethernet drivers v.20.7.1 NDIS62 - crashing SCCM 2012
Had an issue with the latest v.20.7.1 intel ethernet driver download, for which I attempted to load the NDIS62 driver into SCCM 2012 (v.5.0.8239.1000) driver database, which crashed the system. Tried this in both a test environment and live environment and had the same effect in both.
Just a warning to Intel development team and any other users trying to do the same thing!
↧
CVE-2015-2291 Intel Network Adapter Diagnostic Driver IOCTL DoS
A vulnerability in iqvw32.sys and iqvw64e.sys drivers has been discovered in the Intel Network Adapter Driver. Intel Network Adapter Diagnostic Driver is prone to multiple local buffer-overflow vulnerabilities.
An attacker can exploit these issues to crash the affected application; denying service to legitimate users. Due to the nature of this issue, code-execution may be possible but this has not been confirmed.
Note: This issue was previously titled 'Intel Network Adapter Diagnostic Driver CVE-2015-2291 Multiple Remote Code Execution Vulnerabilities'. The title and technical details have been changed to better reflect the underlying component affected.
When will a vendor-supplied patch be available?
Joel
↧
↧
poor network performance when using X520-DA2
I´ve got a problem with a server connection using the following combination:
IBM Server SystemX 3450 Typ:7379-K4G (PCIE x8 slot, 25w), running Windows Server2008R2
Intel Network Adapter X520-DA2
Intel TwinAxial Cable 3m (XDACBL3M)
D-Link switch DGS-1510-52
Problem:
10Gbit Link is up, but the performance is like 10Mbit. Gigabit connection with the internal adapter is much faster!
Even when i try to open the management gui of the adapter it takes several seconds to open and everything seems to be very slow.
As i don´t use them i tried to disable the IPv6 but this didn´t have any effect.
Any ideas?
Thank you in advance! :-)
best regards
Stefan Rindler
↧
X710: DCB (PFC - priority flow control) problem
Hi All,
We have 16 X710 NICs on our different servers. We require to enable PFC (priority flow control) on a specific VLAN priority (like priority #5) on all of the NICs. However, the X710 handles lldp and dcb at the HW level and will not be managed by SW tools like dcbtool as its document says. We noticed that the willing bit is set to 1 for the NICs which means that they can accept configuration from other nodes over DCBX.
So we configured our switches (DELL N4000 series) to advertise PFC configurations to the Intel NICs. But when we set switch to advertise the configuration it wont recognize the NICs as PFC enabled NICs, and when we configure switches to accept configuration from NICs, it gets a configuration which dictates no PFC (all priorities can be dropped).
When we test the switch with other Intel NICs like i520 it is ok, and it works (after configuring the NICs with dcbtool) as expected.
So please help us,
we should configure them ASAP.
Is there any trick to disable HW DCBX and make NIC to pass the DCB/LLDP messages to the OS and later use dcbtool.
If not how should we configure it then?
Regards,
↧
Intel XL710-QDA2 can no longer be changed to 2x40 or 1x40 mode with latest firmware 5.02
The 40Gb modes can no longer be selected using the qcu64e utility since the firmware upgrade from 4.42 to 5.02. Only 4x10 and 2x2x10 options are offered but the XL710-QDA2 card is QSFP+ capable.
# qcu64e /NIC=1 /INFO
Intel(R) QSFP+ Configuration Utility
QCU version: v2.26.17.06
Copyright(C) 2015 by Intel Corporation.
Software released under Intel Proprietary License.
Adapter supports QSFP+ Configuration modification.
Current Configuration: 4x10
Supported Configurations:
4x10
2x2x10A (Top 2 lanes on Module0; Bottom 2 lanes on Module 1)
2x2x10B
Cards that already are in 40Gb mode continue to function in 40Gb mode, but they report invalid configuration with qcu64e:
# qcu64e -nic=1 -info
Intel(R) QSFP+ Configuration Utility
QCU version: v2.26.17.06
Copyright(C) 2015 by Intel Corporation.
Software released under Intel Proprietary License.
Adapter supports QSFP+ Configuration modification.
Current Configuration: Invalid
Supported Configurations:
4x10
2x2x10A (Top 2 lanes on Module0; Bottom 2 lanes on Module 1)
2x2x10B
We are using the i40e driver 1.4.25 on Redhat 6: 2.6.32-573.18.1.el6.x86_64 kernel
# ethtool -i eth4
driver: i40e
version: 1.4.25
firmware-version: 5.02 0x80002285 0.0.0
bus-info: 0000:06:00.0
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
supports-priv-flags: yes
It looks like there is currently no way to downgrade the firmware, which make the cards that are now stuck in 4x10 unusable for us.
↧
SR-IOV failed on Intel Xeon-D 1541's X552 10gbe NIC
Hi all,
I cannot figure out why I cannot enable SR-IOV on Intel Xeon-D 1541's X552 10gbe NIC, it must be the intel's latest ixgbe driver issue because on the same SoC board, the Intel i350 1gbe NIC's sr-iov can be enabled.
Following is the pci device info and also its ixgbe info
root@pve1:/sys/bus/pci/devices/0000:03:00.1# lspci -vnnk -s 03:00.0
03:00.0 Ethernet controller [0200]: Intel Corporation Ethernet Connection X552/X557-AT 10GBASE-T [8086:15ad]
Subsystem: Super Micro Computer Inc Device [15d9:15ad]
Physical Slot: 0-1
Flags: bus master, fast devsel, latency 0, IRQ 25
Memory at fbc00000 (64-bit, prefetchable) [size=2M]
Memory at fbe04000 (64-bit, prefetchable) [size=16K]
Expansion ROM at 90100000 [disabled] [size=512K]
Capabilities: [40] Power Management version 3
Capabilities: [50] MSI: Enable- Count=1/1 Maskable+ 64bit+
Capabilities: [70] MSI-X: Enable+ Count=64 Masked-
Capabilities: [a0] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [140] Device Serial Number 00-00-c9-ff-ff-00-00-00
Capabilities: [150] Alternative Routing-ID Interpretation (ARI)
Capabilities: [160] Single Root I/O Virtualization (SR-IOV)
Capabilities: [1b0] Access Control Services
Capabilities: [1c0] Latency Tolerance Reporting
Kernel driver in use: ixgbe
root@pve1:/sys/bus/pci/devices/0000:03:00.1# modinfo ixgbe
filename: /lib/modules/4.2.8-1-pve/kernel/drivers/net/ethernet/intel/ixgbe/ixgbe.ko
version: 4.1.5
license: GPL
description: Intel(R) 10 Gigabit PCI Express Network Driver
author: Intel Corporation, <linux.nics@intel.com>
srcversion: 9781CEF8A3110F93FF9DBA8
alias: pci:v00008086d000015ADsv*sd*bc*sc*i*
alias: pci:v00008086d00001560sv*sd*bc*sc*i*
alias: pci:v00008086d00001558sv*sd*bc*sc*i*
alias: pci:v00008086d0000154Asv*sd*bc*sc*i*
alias: pci:v00008086d00001557sv*sd*bc*sc*i*
alias: pci:v00008086d0000154Fsv*sd*bc*sc*i*
alias: pci:v00008086d0000154Dsv*sd*bc*sc*i*
alias: pci:v00008086d00001528sv*sd*bc*sc*i*
alias: pci:v00008086d000010F8sv*sd*bc*sc*i*
alias: pci:v00008086d0000151Csv*sd*bc*sc*i*
alias: pci:v00008086d00001529sv*sd*bc*sc*i*
alias: pci:v00008086d0000152Asv*sd*bc*sc*i*
alias: pci:v00008086d000010F9sv*sd*bc*sc*i*
alias: pci:v00008086d00001514sv*sd*bc*sc*i*
alias: pci:v00008086d00001507sv*sd*bc*sc*i*
alias: pci:v00008086d000010FBsv*sd*bc*sc*i*
alias: pci:v00008086d00001517sv*sd*bc*sc*i*
alias: pci:v00008086d000010FCsv*sd*bc*sc*i*
alias: pci:v00008086d000010F7sv*sd*bc*sc*i*
alias: pci:v00008086d00001508sv*sd*bc*sc*i*
alias: pci:v00008086d000010DBsv*sd*bc*sc*i*
alias: pci:v00008086d000010F4sv*sd*bc*sc*i*
alias: pci:v00008086d000010E1sv*sd*bc*sc*i*
alias: pci:v00008086d000010F1sv*sd*bc*sc*i*
alias: pci:v00008086d000010ECsv*sd*bc*sc*i*
alias: pci:v00008086d000010DDsv*sd*bc*sc*i*
alias: pci:v00008086d0000150Bsv*sd*bc*sc*i*
alias: pci:v00008086d000010C8sv*sd*bc*sc*i*
alias: pci:v00008086d000010C7sv*sd*bc*sc*i*
alias: pci:v00008086d000010C6sv*sd*bc*sc*i*
alias: pci:v00008086d000010B6sv*sd*bc*sc*i*
depends: ptp,dca,vxlan
vermagic: 4.2.8-1-pve SMP mod_unload modversions
parm: InterruptType:Change Interrupt Mode (0=Legacy, 1=MSI, 2=MSI-X), default IntMode (deprecated) (array of int)
parm: IntMode:Change Interrupt Mode (0=Legacy, 1=MSI, 2=MSI-X), default 2 (array of int)
parm: MQ:Disable or enable Multiple Queues, default 1 (array of int)
parm: DCA:Disable or enable Direct Cache Access, 0=disabled, 1=descriptor only, 2=descriptor and data (array of int)
parm: RSS:Number of Receive-Side Scaling Descriptor Queues, default 0=number of cpus (array of int)
parm: VMDQ:Number of Virtual Machine Device Queues: 0/1 = disable, 2-16 enable (default=8) (array of int)
parm: max_vfs:Number of Virtual Functions: 0 = disable (default), 1-63 = enable this many VFs (array of int)
parm: VEPA:VEPA Bridge Mode: 0 = VEB (default), 1 = VEPA (array of int)
parm: InterruptThrottleRate:Maximum interrupts per second, per vector, (0,1,956-488281), default 1 (array of int)
parm: LLIPort:Low Latency Interrupt TCP Port (0-65535) (array of int)
parm: LLIPush:Low Latency Interrupt on TCP Push flag (0,1) (array of int)
parm: LLISize:Low Latency Interrupt on Packet Size (0-1500) (array of int)
parm: LLIEType:Low Latency Interrupt Ethernet Protocol Type (array of int)
parm: LLIVLANP:Low Latency Interrupt on VLAN priority threshold (array of int)
parm: FdirPballoc:Flow Director packet buffer allocation level:
1 = 8k hash filters or 2k perfect filters
2 = 16k hash filters or 4k perfect filters
3 = 32k hash filters or 8k perfect filters (array of int)
parm: AtrSampleRate:Software ATR Tx packet sample rate (array of int)
parm: FCoE:Disable or enable FCoE Offload, default 1 (array of int)
parm: LRO:Large Receive Offload (0,1), default 1 = on (array of int)
parm: allow_unsupported_sfp:Allow unsupported and untested SFP+ modules on 82599 based adapters, default 0 = Disable (array of int)
parm: dmac_watchdog:DMA coalescing watchdog in microseconds (0,41-10000), default 0 = off (array of int)
parm: vxlan_rx:VXLAN receive checksum offload (0,1), default 1 = Enable (array of int)
↧
↧
intel nic drivers 19.3 huge 6000+ dpc latency spike once a few secs
hi, i would like to report that the new intel nic drivers version 19.3 that just released recently has huge 6000+ dpc latency spike once in a few secs.
my specs
Intel(R) 82579LM Gigabit Network Connection
windows 7 SP1 32bit + lastest windows update
i downgrade to intel nic drivers previous version 19.1 and the problem is just gone.
↧
x710 disconnections
On my servers on Windows 2012 R2, I have a x710 with random disconnection with two scenarios.
1- During the windows startup, I see many error in the event viewer related to disconnections .
2- Going to the properties of the drivers, cause the nic to disconnect.
I have all lastest drivers and firmware. On the same server we have Mellanox Connectx 4 without any of these issues.
↧
I210 AVB Timers
Hello All,
I am not sure if this is the correct forum to post my question and I would be thankful if someone can point me to the correct one if the question is not relevant.
The question I want to ask is related to the Intel i210-AT chip which I am using for my Industrial solution. I am writing a new Linux driver for the External NIC, which has the i210 chip, for handling packets in a time critical network.
I am using the Time SYNC (section 7.8 in the Intel® Ethernet Controller I210 Datasheet) registers i.e. SYSTIM, TRGTTIML/H0 and TRGTTIML/H1 to create timers using the method explained in "7.8.3.3.1 SYSTIM Synchronized Level Change Generation on SDP Pins"
The timers created are used by the Linux drivers to synchronize the packet transmission in the SR mode (i.e. using launchTime).
I have completed the implementation and the setup works fine if the timers are created in a non-periodic sequence. The problem arises if I try to reset the values or increment the timeout for the timers periodically where the period is lesser than the timeout values.
I am not sure if I have presented my problem correctly here. I would be happy to share other details to clarify the implementation details.
Regards,
Gaurav
↧
i210 FLUPD bit set by write to EEWR? / datasheet description for EELOADCTL and EELOADERR
Hello,
I've got an i210 connected to an SoC and for production I'd like to write the external eeprom via PCIe:
- I map the config space and access the IO area via the config space registers 0x98/0x9C
- The semaphore and sync between FW/SW seems to work
- I write the config (0x80 16bit words) to the SRAM and can read it back, checksum is 0xbaba
Triggering the flash write via FLUPD fails: FLUPD is already set to one by the first write to the SRAM?
After the first SRAM write via EEWR, EEC reads: 0x482a00, is this correct?
When will FLUPD be reset? By whom?
Also I'd like some more documentation on two registers:
Chapter 8.4.2 describes EELOADCTL:
This register provides software EEPROM-mode load status.
All bits are RW to FW, RO to host - excepted to bit 12.
Then it gives a short table for bit0 all ohters are reseved, a second, completely different table describes bits 0:32.
In chapter 8.4.5 EELOADCTL is described a second time with a single sentence.
EELOADERR is in chapter 8.4.4 but there's no description of the bits (table missing?)
Can you please provide me the missing/correct tables for these registers?
Best regards,
Lo
↧
↧
Intel I210-T1: remove "iSCSI Remote Boot"
Hi there. How to remove "iSCSI remote boot" screen on system startup?
↧
Driver Winpe 5 x86 for HP 840 G3 (Intel I219-V) for landesk
Hello,
I need driver Winpe 5 x86 for hp elitebook 840 g3.
I have test with E1D6332.inf it's don't work.
Where can i find the good driver?
Thanks,
↧
PCI\VEN_8086&DEV_1502&SUBSYS_00021179&REV_04 PCI\VEN_8086&DEV_1502&SUBSYS_00021179 PCI\VEN_8086&DEV_1502&CC_020000 PCI\VEN_8086&DEV_1502&CC_0200
Hello all,
I have a Toshiba Z930, which requires the following Intel LAN driver, The scenario is this, if i download these drivers and install them directly onto the laptop they work fine. However when i try to deploy Windows 7 Ent using MDT the image gets deployed however the drivers for the "LAN,card reader, intel management components USB3.0 and wireless" do not install and device manager is displaying exclamations.
Im surprised that the error message says that the connection cannot be made to the deployment share because the following networking device did not have a driver installed
PCI\VEN_8086&DEV_1502&SUBSYS_00021179&REV_04.
So the connection did connect to the deployment share because it loaded windows 7, and the lite touch was executed i have monitoring enabled which show the installation. I have been searching high and wide for an answer and it appears that I need the WINPE drivers ( driver pack)
I have checked the inf files and that have been added to the out of box driver folder on MDT and the Inf files do not have the same hardware ID.
using ms trace the error reports that no networking adapters found. The network drivers for you device are not present.
any help would be appreciated.
Here are the Hardware ID when i manually install the drivers
PCI\VEN_8086&DEV_1502&SUBSYS_00021179&REV_04
PCI\VEN_8086&DEV_1502&SUBSYS_00021179
PCI\VEN_8086&DEV_1502&CC_020000
PCI\VEN_8086&DEV_1502&CC_0200
↧
I211/I217-V Windows 10 LACP teaming fails
Hello,
after the update to Windows 10 (x64, Build 10240) the creation of a teaming group (static or IEEE802.3ad) with a I211+I217-V NIC fails.
Drivers have been upgraded to the latest version available and multiple reinstallations with reboots din't help either. Whenever the group creation wizzard is used and a groupname (several tried), the adapters and LACP have been selected, a Windows pop-up appears to tell me group creation has failed.
However the Windows Device Manager shows a newly created "Intel Advanced Network Services Virtual Adapter", so some kind of configuration seems to get done.
Using Windows 7 SP1 x64 the exact same setup worked flawlessly for months, so Win10/the driver are the likely culprit.
Is anyone experiencing similar problems and/or is this a known bug? Feedback on this issue is greatly appreciated.
Thanks in advance!
Kind regards,
Famaku
↧
↧
Driver update Intel 82567v-2, it is saying I have the latest version, I don't think so?
Hi, I have just upgraded to Windows 10 and it is coming up with error, I have read up online and the resolution for this is to update your drivers. Now my driver is Intel 82567v-2, it is saying I have the latest version, however the latest was 2012? I am unsure as to what to do next, as surely the driver needs an update from 2012?
↧
Thunderbolt networking in Windows OS
Intel releases the whitepaper on how to network two PCs or two MACs using Thunderbolt.
It even states the driver: Thunderbolt Software 2.5 one should be using.
I have scoured the internet, even venturing into these historical image websites and found NOTHING.
INTEL, where can I find Thunderbolt Software 2.5?
Thanx.
-Chet
↧
Intel Ethernet Connection I217-LM (WinPE drivers)
Hi everyone,
We purchased a few DELL Optiplex 9020s that came with an Intel Ethernet Connection I217-LM ethernet controller, and I've been unable to find the correct WinPE x64 drivers for this adapter.
From the Download Center I found what I thought were the correct drivers. In the EXE, I found some WinPE drivers, but apparently these aren't it as I'm not able to connect to my network when I boot up using WinPE.
Can anyone point me in the right direction to get the correct drivers please?
Thanks!
↧