Active2 years, 8 months ago
I have the problem that the ethernet device on the Intel NUC is not found.
ifconfig -a
only shows lo and wlan0 but not eth0.sudo lshw -C net
gives the following output:Elixir Cross Referencer. If, when you install the driver disk, you elect to verify the driver disk when prompted, you should check that the checksum presented by the installer is the same as that in the metadata MD5 checksum file included in this download. I downloaded the Intel e1000 LAN card drivers and followed their instructions. However, when I run make, it says I only have the 2.4.33 source. Hi, I am trying to find the intel e1000 NIC driver that workstation 7 uses. I need it for SCCM OSD PXE boot. I have tried downloading it from itels website but it is a install exe that does not extract.
After running
sudo lshw -C net
and dmesg | grep -e eth -e e1000
, I get this output:Product information (
lspci -nnk
) is the following:Kernel version is 3.19.0-22. I am booting in UEFI mode. The BIOS version is the latest version.
As suggested, I updated the BIOS to the newest version, Left the device without power for a while and changed the hardware configuration. So far without luck!
Intel E1000 Network Card
![E1000 E1000](/uploads/1/2/6/0/126010904/797221209.jpg)
![Intel Intel](/uploads/1/2/6/0/126010904/819612046.png)
I just installed Windows, and the device also isn't working there. This probably means that it's either a BIOS problem, as suggested, or the hardware is actually damaged.
Any further thoughts on this?
For others with similar problems:
In the beginning I thought this was a driver issue. I wanted to install the newest version of the e1000e driver. This requires version 8.x.x of the e1000 driver. When I tried to install this driver, I got the following error message (even though I run kernel version 3.19):
However, it turns out that the old driver on the system was working fine. The real problem has to lay somewhere else.
Daniel Eckert
Daniel EckertDaniel Eckert
2 Answers
From the logs it seems to me you have managed to update the driver from version
2.3.2-k
to 3.2.4.2-NAPI
.I fixed my Intel NUC non working ethernet by:
- download the driver from https://downloadcenter.intel.com/download/15817, currently 3.2.4.2 (as shown in lshw -C above)
make install
in the src folderrmmod e1000e
modprobe e1000e
- and to make the new driver survive a reboot
update-initramfs -u
This I have to repeat at every kernel update, since kernel updates still (
TellMeWhy3.13.0-63
) contain the old driver version 2.3.2-k
, which does not work with my Intel NUC.8,4692424 gold badges7373 silver badges123123 bronze badges
lnappalnappa
Written by Eugene Mihailescu: The NVM checksum is not valid
The root of the problem is in the hardware and this page goes through fixing it.
In my case it was as simple as downloading the Linux version of bootutil from Intel and then chmodding and running the 64 bit version with the parameters
Zanna-NIC=1 -DEFAULTCONFIG
. I simply did this from within Ubuntu for minimal effort.53.1k1414 gold badges149149 silver badges250250 bronze badges
Intel E1000 Driver
DogcatfeeDogcatfee
Not the answer you're looking for? Browse other questions tagged driversintelethernet or ask your own question.
Intel E1000 Drivers
- Time to update the driver. Can't compile under new kernel branch 4.10. UPDATE. Finally!
- This driver is cancer on Debian/Ubuntu/Mint/Whatever. They are hard coding kernel versions that they happen to use, rather than compile depending on whatever kernel build source it's being built on(the point of building from src in the first place). So this driver compile shts itself if every planet isn't aligned with one guy using redhat in a dungeon at intel. This is not the way to sell hardware, kids. Just in case you missed the point of vendor supplied drivers. For example: #define UBUNTU_VERSION_CODE (((LINUX_VERSION_CODE & ~0xFF) << 8) + (UTS_UBUNTU_RELEASE_ABI)) #if UTS_UBUNTU_RELEASE_ABI > 255 #error UTS_UBUNTU_RELEASE_ABI is too large... #endif /* UTS_UBUNTU_RELEASE_ABI > 255 */ #if ( LINUX_VERSION_CODE <= KERNEL_VERSION(3,0,0) ) /* Our version code scheme does not make sense for non 3.x or newer kernels, * and we have no support in kcompat for this scenario. Thus, treat this as a * non-Ubuntu kernel. Possibly might be better to error here. */ #define UTS_UBUNTU_RELEASE_ABI 0 #define UBUNTU_VERSION_CODE 0 #endif
- Works just as well as you hoped it would. If, at your own risk, you want to support both 1Gb and 10Gb with SFP+ modules that have not been tested with both--and are not advertised to work with both--just make multispeed_fiber always true: --------------------- ixgbe/ixgbe-4.0.3/src/ixgbe_phy.c ---------------------- index 102dd53..a3e5f74 100644 @@ -1451,7 +1451,7 @@ s32 ixgbe_identify_sfp_module_generic(struct ixgbe_hw *hw) hw->phy.sfp_setup_needed = true; /* Determine if the SFP+ PHY is dual speed or not. */ - hw->phy.multispeed_fiber = false; + hw->phy.multispeed_fiber = true; if (((comp_codes_1g & IXGBE_SFF_1GBASESX_CAPABLE) && (comp_codes_10g & IXGBE_SFF_10GBASESR_CAPABLE)) || ((comp_codes_1g & IXGBE_SFF_1GBASELX_CAPABLE) && @@ -1771,7 +1771,7 @@ s32 ixgbe_identify_qsfp_module_generic(struct ixgbe_hw *hw) hw->phy.sfp_setup_needed = true; /* Determine if the QSFP+ PHY is dual speed or not. */ - hw->phy.multispeed_fiber = false; + hw->phy.multispeed_fiber = true; if (((comp_codes_1g & IXGBE_SFF_1GBASESX_CAPABLE) && (comp_codes_10g & IXGBE_SFF_10GBASESR_CAPABLE)) || ((comp_codes_1g & IXGBE_SFF_1GBASELX_CAPABLE) &&
- I cannot comment on the driver as I could not get it work on Ubuntu. I thought i'd give it a go, even though I knew it wasn't apart of the supported list. Ubuntu 14.04, 3.13.0-24-generic kernel, Intel Corporation Ethernet Connection I217-V (rev 05). **UPDATE** Booting without the cable plugged in helped!
- For older non-current CentOS boot kernel (such as 1 or 2 sub-revisions behind), you're forced to install the full-source CentOS linux kernel into /usr/src/linux. Cannot rely on 'kernel-devel' package then. Certainly, not Intel's fault. but it works very well.