Re: [E1000-devel] support for RHEL/CentOS 7.3?

[email protected]] Sent: Thursday, December 01, 2016 11:51 AM To: Friesen, Chris B (Wind River) ; [email protected] Subject: Re: [E1000-devel] support for RHEL/CentOS 7.3? i40evf will be updated by early Q1 2017. Otherwise, the latest drivers compile on RHEL 7.3. Todd Fujinak

Re: [E1000-devel] support for RHEL/CentOS 7.3?

[email protected]] Sent: Tuesday, November 29, 2016 9:31 AM To: Fujinaka, Todd ; [email protected] Subject: Re: [E1000-devel] support for RHEL/CentOS 7.3? On 11/29/2016 11:09 AM, Fujinaka, Todd wrote: > In general we don't mention version numbers of OSes and I don't expect w

Re: [E1000-devel] support for RHEL/CentOS 7.3?

On 12/01/2016 01:51 PM, Fujinaka, Todd wrote: > i40evf will be updated by early Q1 2017. Otherwise, the latest drivers > compile on RHEL 7.3. For what it's worth, I was not able to compile the latest ixgbe/ixgbevf on 7.3. I took the 7.3-related src/kcompat.h changes from i40e driver and applie

Re: [E1000-devel] support for RHEL/CentOS 7.3?

On 11/29/2016 11:09 AM, Fujinaka, Todd wrote: > In general we don't mention version numbers of OSes and I don't expect we'll > start. > > I can also tell you that we also posted newer versions of the other three > drivers. Could you point me towards these newer versions? The latest "i40evf stab

Re: [E1000-devel] support for RHEL/CentOS 7.3?

(503) 712-4565 -Original Message- From: Chris Friesen [mailto:[email protected]] Sent: Tuesday, November 29, 2016 8:50 AM To: Fujinaka, Todd ; [email protected] Subject: Re: [E1000-devel] support for RHEL/CentOS 7.3? On 11/29/2016 09:33 AM, Fujinaka, Todd w

Re: [E1000-devel] support for RHEL/CentOS 7.3?

Application Engineer Networking Division (ND) Intel Corporation [email protected] (503) 712-4565 -Original Message- From: Chris Friesen [mailto:[email protected]] Sent: Tuesday, November 29, 2016 7:26 AM To: [email protected] Subject: [E1000-devel] support for

Re: [E1000-devel] support for RHEL/CentOS 7.3?

On 11/29/2016 09:33 AM, Fujinaka, Todd wrote: > I would suggest you check e1000.sourceforge.net and see that there's three > newer drivers than the one you're using. The latest should compile on > RHEL7.3. I did check there. The changelogs don't say anything about support for 7.3, and I assumed

[E1000-devel] support for RHEL/CentOS 7.3?

I recently tried compiling i40e version 1.5.19 on CentOS 7.3 and it crapped all over. I've attached the logs to preserve line length. It looks like they've backported some stuff in a way that breaks assumptions in a bunch of the Intel out-of-tree drivers. Are there plans to add support for 7

Re: [E1000-devel] Support for Intel Ethernet Connection I219-V

On Fri, Jul 29, 2016 at 1:59 PM, Alexey Muranov wrote: > On 27 Jul 2016, at 17:45, Alexander Duyck wrote: > >> Other than that I can't think of too many other ways to modify the >> EEPROM without actually going in and modifying it yourself. I believe >> the e1000e driver supports modifying an EE

Re: [E1000-devel] Support for Intel Ethernet Connection I219-V

On 27 Jul 2016, at 17:45, Alexander Duyck wrote: > Other than that I can't think of too many other ways to modify the > EEPROM without actually going in and modifying it yourself. I believe > the e1000e driver supports modifying an EEPROM via ethtool, so one > possible fix would be to disable th

Re: [E1000-devel] Support for Intel Ethernet Connection I219-V

On 27 Jul 2016, at 17:45, Alexander Duyck wrote: > By any chance when you boot the laptop does it display a message about > pressing ctrl + S to enter the NIC setup? If so you may want to try > going into that menu to change options as it appears that doing so may > have an effect on the EEPROM.

Re: [E1000-devel] Support for Intel Ethernet Connection I219-V

By any chance when you boot the laptop does it display a message about pressing ctrl + S to enter the NIC setup? If so you may want to try going into that menu to change options as it appears that doing so may have an effect on the EEPROM. Specifically just changing the amount of time that the me

Re: [E1000-devel] Support for Intel Ethernet Connection I219-V

I have found Intel's documentation for the NVM of I219 : http://www.intel.com/content/dam/www/public/us/en/documents/datasheets/ethernet-connection-i219-datasheet.pdf (Section 10). I am afraid it is too technical for me though. - Alexey. On 27 Jul 2016, at 12:33, Alexey Muranov wrote: > A

Re: [E1000-devel] Support for Intel Ethernet Connection I219-V

Alexander, thanks for the explanations and for looking into this. I have installed the latest e1000e module (3.3.4) with "patched out" NVM checksum validation. This made Ethernet connection work. Here is my dmesg output, just in case: $ dmesg | grep e1000e [9.650532] e1000e: modu

Re: [E1000-devel] Support for Intel Ethernet Connection I219-V

On Tue, Jul 26, 2016 at 3:22 AM, Alexey Muranov 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 ver

Re: [E1000-devel] Support for Intel Ethernet Connection I219-V

>>> 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

Re: [E1000-devel] Support for Intel Ethernet Connection I219-V

Alexander, thanks for all these details. Yes, i am mostly interested in fixing it in a permanent fashion. Ideally i would like to figure out the root cause and to find a simple procedure to make ASUS B8430UA work with Linux, to put it somewhere on a wiki or StackExchange. (I also do not feel

Re: [E1000-devel] Support for Intel Ethernet Connection I219-V

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. One workaround that you might be able to use would be to just modify your driver to skip over the loop that actually invokes the NVM check. If you

Re: [E1000-devel] Support for Intel Ethernet Connection I219-V

I think i might have new information about my problem with I219-V under Linux, where e1000e reports "The NVM Checksum Is Not Valid". I executed bootutil64e from Intel Ethernet Connections Boot Utility ( https://downloadcenter.intel.com/download/19186 ) under Ubuntu, here is the output: Intel(

Re: [E1000-devel] Support for Intel Ethernet Connection I219-V

On 23 Jul 2016, at 13:15, Alexey Muranov wrote: > Could this be a sign of incompatibility of e1000e with Intel Ethernet > Connection I219-V? Well, this was probably a silly question, if you say that the checksum is incorrect. > Could you, please, give me some details about this checksum verif

Re: [E1000-devel] Support for Intel Ethernet Connection I219-V

I have exchanged my laptop for a new one.  The online store accepted to exchange it because besides Ethernet under Linux, i also had problems with keyboard backlight under Windows. The new one has no problems with keyboard backlight, but the issue with Ethernet is the same: under Linux i get

Re: [E1000-devel] Support for Intel Ethernet Connection I219-V

In two separate letters, ASUS customer service acknowledged that, according to my description, the NVM problem might be technical and not related to Linux, and they replied that they do not have tools for checking or restoring the contents of the NVM, but if i find any, they will be glad if i le

Re: [E1000-devel] Support for Intel Ethernet Connection I219-V

Alexey Muranov wrote: I wrote to Asus (my laptop maker), and they responded that they can only help with setting up the original hardware and software, and they cannot help if i have installed Linux, because the laptop was sold with Windows. I wrote to them again explaining that it looks

Re: [E1000-devel] Support for Intel Ethernet Connection I219-V

On 15 Jul 2016, at 20:07, Rustad, Mark D wrote: > Don Buchholz wrote: > >> Finally, given dmesg output that you posted earlier, if the >> NVM checksum is bad, it really won't matter if your driver >> supports the hardware or not. The driver will not load if >> the hardware has been corrupted.

Re: [E1000-devel] Support for Intel Ethernet Connection I219-V

Don Buchholz wrote: We can not (reliably) map the name "I219V" to a PCIe device. Use lspci(8) to ascertain the device id#, and then use modinfo(8) to see if that device ID is listed on one of the "alias" lines. The fact that the driver loaded at all is a sign that the device is supported by

Re: [E1000-devel] Support for Intel Ethernet Connection I219-V

;>> >>>> - Alex >>>> >>>> On Sun, Jul 10, 2016 at 8:49 AM, Neftin, Sasha >>>> wrote: >>>>> I have no idea. From your email I can see that you talk about ASUS >>>>> laptop. I suggest you contact ASUS support too. >

Re: [E1000-devel] Support for Intel Ethernet Connection I219-V

00:00:00:00:00 >>>> inet 127.0.0.1/8 scope host lo >>>> valid_lft forever preferred_lft forever >>>> inet6 ::1/128 scope host >>>> valid_lft forever preferred_lft forever >>>> 2: wlp1s0: mtu 1500 qdisc m

Re: [E1000-devel] Support for Intel Ethernet Connection I219-V

settings: Onboard Devices >>> Configuration - Onboard PCIE LAN - is this option enabled? >>> >>> Skype Meג„¢! >>> >>> -Original Message- >>> From: Alexey Muranov [mailto:[email protected]] >>> Sent: Sunday, July 10, 2016

Re: [E1000-devel] Support for Intel Ethernet Connection I219-V

@gmail.com] >> Sent: Sunday, July 10, 2016 3:42 PM >> To: Neftin, Sasha >> Cc: [email protected] >> Subject: Re: [E1000-devel] Support for Intel Ethernet Connection I219-V >> >> Thank you for the confirmation. >> >> Would you know by any chance then w

Re: [E1000-devel] Support for Intel Ethernet Connection I219-V

nboard Devices > Configuration - Onboard PCIE LAN - is this option enabled? > > Skype Meג„¢! > > -Original Message- > From: Alexey Muranov [mailto:[email protected]] > Sent: Sunday, July 10, 2016 3:42 PM > To: Neftin, Sasha > Cc: [email protected]

Re: [E1000-devel] Support for Intel Ethernet Connection I219-V

Muranov [mailto:[email protected]] Sent: Sunday, July 10, 2016 3:42 PM To: Neftin, Sasha Cc: [email protected] Subject: Re: [E1000-devel] Support for Intel Ethernet Connection I219-V Thank you for the confirmation. Would you know by any chance then why the Ethernet is not

Re: [E1000-devel] Support for Intel Ethernet Connection I219-V

essage- > From: Alexey Muranov [mailto:[email protected]] > Sent: Sunday, July 10, 2016 12:45 AM > To: [email protected] > Subject: [E1000-devel] Support for Intel Ethernet Connection I219-V > > Hello, > > I have a laptop with Intel Ethernet Connect

Re: [E1000-devel] Support for Intel Ethernet Connection I219-V

Hello, 3.3.4 should work with I219-V. Thanks, Sasha -Original Message- From: Alexey Muranov [mailto:[email protected]] Sent: Sunday, July 10, 2016 12:45 AM To: [email protected] Subject: [E1000-devel] Support for Intel Ethernet Connection I219-V Hello, I have a

[E1000-devel] Support for Intel Ethernet Connection I219-V

Hello, I have a laptop with Intel Ethernet Connection I219-V. I want to install Linux on it, but cannot yet get Ethernet to work under Linux. I believe it is because the driver is missing. The version 3.3.4 of e1000e is not documented to support Intel Ethernet Connection I219-V (it only goe

Re: [E1000-devel] Support for Symmetric RSS Hashing?

hear it worked for you. :) -Don Skidmore From: Derek Ditch [mailto:[email protected]] Sent: Wednesday, June 22, 2016 12:23 PM To: Fujinaka, Todd Cc: Skidmore, Donald C ; [email protected] Subject: Re: [E1000-devel] Support for Symmetric RSS Hashing? It seems the ixgbe 4.4.6

Re: [E1000-devel] Support for Symmetric RSS Hashing?

) > Intel Corporation > [email protected] > (503) 712-4565 > > -Original Message- > From: Derek Ditch [mailto:[email protected]] > Sent: Tuesday, June 21, 2016 10:57 AM > To: Skidmore, Donald C > Cc: [email protected] > Subject: Re: [E1000

Re: [E1000-devel] Support for Symmetric RSS Hashing?

ation >> [email protected] <mailto:[email protected]> >> (503) 712-4565 >> >> -Original Message- >> From: Derek Ditch [mailto:[email protected]] >> Sent: Tuesday, June 21, 2016 10:57 AM >> To: Skidmore, Donald C >> C

Re: [E1000-devel] Support for Symmetric RSS Hashing?

: Skidmore, Donald C Cc: [email protected] Subject: Re: [E1000-devel] Support for Symmetric RSS Hashing? Don, Thanks for the suggestion. I hadn’t noticed the “hkey” argument to ethtool -X before. However, it appears my hardware doesn’t support it (though I could be doing it wrong

Re: [E1000-devel] Support for Symmetric RSS Hashing?

, 2016 10:57 AM To: Skidmore, Donald C Cc: [email protected] Subject: Re: [E1000-devel] Support for Symmetric RSS Hashing? Don, Thanks for the suggestion. I hadn’t noticed the “hkey” argument to ethtool -X before. However, it appears my hardware doesn’t support it (though I could be

Re: [E1000-devel] Support for Symmetric RSS Hashing?

e 19, 2016 9:20 PM >> To: [email protected] >> Subject: [E1000-devel] Support for Symmetric RSS Hashing? >> >> I’ve been using and recommending Intel NICs for years for network sensor >> platforms. I’m a huge user of Bro (http://bro.org <http://br

Re: [E1000-devel] Support for Symmetric RSS Hashing?

rge.net > Subject: [E1000-devel] Support for Symmetric RSS Hashing? > > I’ve been using and recommending Intel NICs for years for network sensor > platforms. I’m a huge user of Bro (http://bro.org <http://bro.org/>) and also > leveraged Suricata for signature-based detections.

[E1000-devel] Support for Symmetric RSS Hashing?

I’ve been using and recommending Intel NICs for years for network sensor platforms. I’m a huge user of Bro (http://bro.org ) and also leveraged Suricata for signature-based detections. Lately, I’ve started working with trying to get away from PF_RING as my hardware interface lay

[E1000-devel] Support

Zenfone bootloader/root/custom rom. -- Go from Idea to Many App Stores Faster with Intel(R) XDK Give your users amazing mobile app experiences with Intel(R) XDK. Use one codebase in this all-in-one HTML5 development environ

[E1000-devel] Support for E1000 PCI-E driver

Hi Sir We are porting Linux on Netlogics Board . For checking PCI initialisation , we are using E1000 driver as loadable module . While PCI initialisation is working fine with Core zero ( as I am able to load E1000 driver and ping works fine) but for another core I am facing "e1000_clean_tx_irq:

[E1000-devel] Support for --set-rxfh-indir in igb

Hi! ethtool has a new option --set-rxfh-indir that should allow one to modify the RSS indirection table. This would allow to tune the number of queues to match the number of processors. For example, actually, it is not possible to load-balance 8 IRQ on 3 CPU. With the possibility to mo

Re: [E1000-devel] Support e1000 M88 PHY registers in -d

On Mon, 2011-04-04 at 10:41 +0100, Ben Hutchings wrote: > On Mon, 2011-04-04 at 01:36 -0700, Jeff Kirsher wrote: > > On Sat, Apr 2, 2011 at 09:24, Ben Hutchings > > wrote: > > > Anthony, > > > > > > I'm now upstream maintainer for ethtool so I've picked up your patch > > > again. > > > > > > On F

Re: [E1000-devel] Support e1000 M88 PHY registers in -d

On Mon, 2011-04-04 at 01:36 -0700, Jeff Kirsher wrote: > On Sat, Apr 2, 2011 at 09:24, Ben Hutchings wrote: > > Anthony, > > > > I'm now upstream maintainer for ethtool so I've picked up your patch > > again. > > > > On Fri, 2010-03-19 at 00:32 -0400, Anthony DeRobertis wrote: > >> Package: ethtoo

Re: [E1000-devel] Support e1000 M88 PHY registers in -d

On Sat, Apr 2, 2011 at 09:24, Ben Hutchings wrote: > Anthony, > > I'm now upstream maintainer for ethtool so I've picked up your patch > again. > > On Fri, 2010-03-19 at 00:32 -0400, Anthony DeRobertis wrote: >> Package: ethtool >> Version: 1:2.6.33-1 >> Severity: wishlist >> >> The M88 PHY regist

Re: [E1000-devel] Support e1000 M88 PHY registers in -d

Anthony, I'm now upstream maintainer for ethtool so I've picked up your patch again. On Fri, 2010-03-19 at 00:32 -0400, Anthony DeRobertis wrote: > Package: ethtool > Version: 1:2.6.33-1 > Severity: wishlist > > The M88 PHY registers contain useful information like the cable length > estimate an