ThinkWiki - User contributions [en]

Problem with e1000: EEPROM Checksum Is Not Valid

2019-08-15T04:00:25Z

Cheloide: /* Using Preboot tool on linux */

== Problem Description ==
On certain ThinkPads, [[e1000]] driver for [[Intel Gigabit Ethernet (10/100/1000)]] fails to load with the following error message in /var/log/messages:

<pre>
e1000: 0000:02:00.0: e1000_probe: The EEPROM Checksum Is Not Valid
e1000: probe of 0000:02:00.0 failed with error -5
</pre>

The problem is caused by a power savings feature obstructing normal operation, and causes the first bytes read from the EEPROM to be corrupt, resulting in a random or invalid MAC address (but no other data corruption). The EEPROM checksum test traps the problem and the driver refuses to load.

== Solutions ==

Try to reload the e1000 module until the ethernet is pluged in, and the hardware have a chance to detect a link.

=== Use e1000e---Kernel Patch ===
Auke Kok published two patches in October 2007 that help solve both the "corrupted" EEPROM read and bad latency.
One of the patches moves many network cards over to the e1000e (e1000 for PCI-Express) module. The second disables some PCIe power management features that were the cause for the bad EEPROM read and some stability issues.
[http://kerneltrap.org/mailarchive/linux-netdev/2007/10/31/374579 <nowiki>[PATCH 3/4] e1000/e1000e: Move PCI-Express device IDs over to e1000e</nowiki>]
[http://kerneltrap.org/mailarchive/linux-netdev/2007/10/31/374573 <nowiki>[PATCH 2/4] e1000e: Disable L1 ASPM power savings for 82573 mobile variants</nowiki>]
Refer to [http://www.linuxhq.com/patch-howto.html LinuxHQ] on how to apply kernel patches.

=== From Lenovo ===
Lenovo provides a [http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=MIGR-67166 script] that uses 'ethtool' command to update the card's settings. They say it is for SLED 10 but the Linux flavor shouldn't really matter. For some users, neither of the circumventions listed below help, but this script does!

=== Via module parameter ===

In recent kernels (at least with 2.6.22, maybe also in 2.6.21) there is a kernel module option to make the module ignore the error.

Load the module like this
<pre>
modprobe e1000 eeprom_bad_csum_allow=1
</pre>

You might also apply that parameter via modprobe.d or if you are using Debian/Ubuntu as append-line in your bootloader: e1000.eeprom_bad_csum_allow=1

=== From Mat's Blog ===
The fundamental solution is explained at [http://www.matinfo.ch/blog/archive/2007/01/26/intel-nic-pxe-e05-error.html Mat's Blog]
which directs the reader to Intel's site to download PROBOOT.EXE.

'''DO NOT USE THIS TOOL ON THINKPADS.''' The IBAUTIL.EXE tool that it contains is designed only to work with discrete ethernet parts that are on PCI/PCIe cards. It is not at all intended for use with laptop parts, although it is not sufficiently careful to refuse to run on such hardware. Improper use of this tool can leave your LAN firmware corrupted to the point that it will not even enumerate on the PCI bus and you will probably have to have your laptop repaired to restore the LAN functionality.
See http://www.mail-archive.com/e1000-devel@lists.sourceforge.net/msg00398.html for an Intel Linux driver employee's comments on this.
'''
=== Comment: ===
'''
I used PROBOOT.EXE Version 15.2 (file version 4.0.100.1124) on Bios Version 2.26 (79ETE6WW) for T60 Type 2007-53G with success.
The copied instruction is:
 “ Download PROBOOT.EXE from Intel. Get the first one from the list - the
one without Network adapter, it says only "Intel® Boot Agent PROBOOT.exe
version: 11.2", install that - it will create a folder with some files -
put these on a bootable floppy (or two) or a bootable CD. Boot to DOS with
the floppy or CD and run "IBAUtil.exe -DEFCFG" that will reset the
configuration and all should be OK „ 
I used an old bootable W98 to start the computer and a second CD with the files above. It is only working under DOS!

=== Using Preboot tool on linux ===

{{WARN|Try at your own risk!}}
This has been tested on a {{T60}} running 64bit Debian buster displaying the error '''e1000e the nvm checksum is not valid'''

1. Download [https://downloadcenter.intel.com/download/19186 Intel® Ethernet Connections Boot Utility, Preboot Images, and EFI Drivers '''(For Linux)''']
2. On a Terminal Go to the download directory {{cmduser|cd /path/to/Preboot.tar.gz}}
3. Create a folder for the files {{cmduser|mkdir Preboot}}
4. untar the file {{cmduser|tar -xvzf Preboot.tar.gz -C Preboot}}

if you're running a 32Bit installation of linux, follow this instructions (This was not tested)

5. cd to BootUtil folder for your architecture {{cmduser|cd Preboot/APPS/BootUtil/Linux32/}}
6. Give execution permissions to bootutil32e {{cmduser|chmod +x bootutil32}}
7. Run {{cmduser|sudo ./bootutil32 -NIC 1 -defcfg }}

if you're running a 64Bit installation of linux, follow this instructions
5. cd to BootUtil folder for your architecture {{cmduser|cd Preboot/APPS/BootUtil/Linux_x64}}
6. Give execution permissions to bootutil64e {{cmduser|chmod +x bootutil64e}}
7. Run {{cmduser|sudo ./bootutil64e -NIC 1 -defcfg }}

[https://superuser.com/a/1170175/449434 Source (superuser.com)]

== Circumvention ==

* Upgrade your BIOS

Lenovo has published newer BIOS revisions that appear to fix the issue for some users. The BIOS upgrade turns off "Deep smart power down" which has been known to cause issues at initialization time (the driver can re-enable the issue later if you desire, the feature works correctly then).

* Insert a cable

Inserting a linked network cable bypasses the problem.

* Take the checksum twice

This [http://sourceforge.net/tracker/index.php?func=detail&aid=1474679&group_id=42302&atid=447449 bug report] describes a fix -- take the checksum twice. First time will report a bad checksum, second will work (the problem seems to be triggered by some power-saving technology). This requires a tweak to the driver source and a rebuild of your kernel. This is much better than a previous "fix" published here that disabled checksum checking entirely.

I updated the patch above to 2.6.22:
<pre>
diff -urN linux-2.6.22-suspend2-r1.orig/drivers/net/e1000/e1000_main.c linux-2.6.22-suspend2-r1/drivers/net/e1000/e1000_main.c
--- linux-2.6.22-suspend2-r1.orig/drivers/net/e1000/e1000_main.c 2007-08-17 23:32:04.000000000 +0200
+++ linux-2.6.22-suspend2-r1/drivers/net/e1000/e1000_main.c 2007-09-05 16:39:11.000000000 +0200
@@ -999,16 +999,18 @@
goto err_eeprom;
}

- /* before reading the EEPROM, reset the controller to
- * put the device in a known good starting state */
-
- e1000_reset_hw(&adapter->hw);
-
- /* make sure the EEPROM is good */
-
if (e1000_validate_eeprom_checksum(&adapter->hw) < 0) {
- DPRINTK(PROBE, ERR, "The EEPROM Checksum Is Not Valid\n");
- goto err_eeprom;
+ /* before reading the EEPROM, reset the controller to
+ * put the device in a known good starting state */
+
+ e1000_reset_hw(&adapter->hw);
+
+ /* make sure the EEPROM is good */
+
+ if (e1000_validate_eeprom_checksum(&adapter->hw) < 0) {
+ DPRINTK(PROBE, ERR, "The EEPROM Checksum Is Not Valid\n");
+ goto err_eeprom;
+ }
}

/* copy the MAC address out of the EEPROM */
</pre>
[[User:Ra|Ra]] 15:28, 5 September 2007 (UTC)

* Remove/add kernel module

Removing and adding the kernel module is a possible work-around. As root, run

<pre>
# modprobe -r e1000
# modprobe e1000
</pre>

On some occasions, the commands have to be run twice before eth0 becomes useable.
On some X60s this will not work at all.

* Disabling and re-enabling the NIC in the BIOS

For some it fixed the issue finally, for some it helped just temporarily.

* Hacking the kernel to carry on even if the checksum is not valid

Although being a very ugly, hack, this works fine for me. To do that, you have to search drivers/net/e1000/e1000_main.c for the line containing the error message and then comment out the following two lines which set the error state and then jump to the error code. Although this doesn't fry the hardware for me, consider yourself warned...

== See also ==

* [http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=MIGR-67166 Lenovo's solution]
* [http://sourceforge.net/tracker/index.php?func=detail&aid=1474679&group_id=42302&atid=447449 bug report] submitted for e1000 driver.
* Discussion at [http://forums.gentoo.org/viewtopic-t-476305-highlight-e1000.html Gentoo forums]

Problem with e1000: EEPROM Checksum Is Not Valid

2019-08-15T03:56:04Z

Cheloide:

== Problem Description ==
On certain ThinkPads, [[e1000]] driver for [[Intel Gigabit Ethernet (10/100/1000)]] fails to load with the following error message in /var/log/messages:

<pre>
e1000: 0000:02:00.0: e1000_probe: The EEPROM Checksum Is Not Valid
e1000: probe of 0000:02:00.0 failed with error -5
</pre>

The problem is caused by a power savings feature obstructing normal operation, and causes the first bytes read from the EEPROM to be corrupt, resulting in a random or invalid MAC address (but no other data corruption). The EEPROM checksum test traps the problem and the driver refuses to load.

== Solutions ==

Try to reload the e1000 module until the ethernet is pluged in, and the hardware have a chance to detect a link.

=== Use e1000e---Kernel Patch ===
Auke Kok published two patches in October 2007 that help solve both the "corrupted" EEPROM read and bad latency.
One of the patches moves many network cards over to the e1000e (e1000 for PCI-Express) module. The second disables some PCIe power management features that were the cause for the bad EEPROM read and some stability issues.
[http://kerneltrap.org/mailarchive/linux-netdev/2007/10/31/374579 <nowiki>[PATCH 3/4] e1000/e1000e: Move PCI-Express device IDs over to e1000e</nowiki>]
[http://kerneltrap.org/mailarchive/linux-netdev/2007/10/31/374573 <nowiki>[PATCH 2/4] e1000e: Disable L1 ASPM power savings for 82573 mobile variants</nowiki>]
Refer to [http://www.linuxhq.com/patch-howto.html LinuxHQ] on how to apply kernel patches.

=== From Lenovo ===
Lenovo provides a [http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=MIGR-67166 script] that uses 'ethtool' command to update the card's settings. They say it is for SLED 10 but the Linux flavor shouldn't really matter. For some users, neither of the circumventions listed below help, but this script does!

=== Via module parameter ===

In recent kernels (at least with 2.6.22, maybe also in 2.6.21) there is a kernel module option to make the module ignore the error.

Load the module like this
<pre>
modprobe e1000 eeprom_bad_csum_allow=1
</pre>

You might also apply that parameter via modprobe.d or if you are using Debian/Ubuntu as append-line in your bootloader: e1000.eeprom_bad_csum_allow=1

=== From Mat's Blog ===
The fundamental solution is explained at [http://www.matinfo.ch/blog/archive/2007/01/26/intel-nic-pxe-e05-error.html Mat's Blog]
which directs the reader to Intel's site to download PROBOOT.EXE.

'''DO NOT USE THIS TOOL ON THINKPADS.''' The IBAUTIL.EXE tool that it contains is designed only to work with discrete ethernet parts that are on PCI/PCIe cards. It is not at all intended for use with laptop parts, although it is not sufficiently careful to refuse to run on such hardware. Improper use of this tool can leave your LAN firmware corrupted to the point that it will not even enumerate on the PCI bus and you will probably have to have your laptop repaired to restore the LAN functionality.
See http://www.mail-archive.com/e1000-devel@lists.sourceforge.net/msg00398.html for an Intel Linux driver employee's comments on this.
'''
=== Comment: ===
'''
I used PROBOOT.EXE Version 15.2 (file version 4.0.100.1124) on Bios Version 2.26 (79ETE6WW) for T60 Type 2007-53G with success.
The copied instruction is:
 “ Download PROBOOT.EXE from Intel. Get the first one from the list - the
one without Network adapter, it says only "Intel® Boot Agent PROBOOT.exe
version: 11.2", install that - it will create a folder with some files -
put these on a bootable floppy (or two) or a bootable CD. Boot to DOS with
the floppy or CD and run "IBAUtil.exe -DEFCFG" that will reset the
configuration and all should be OK „ 
I used an old bootable W98 to start the computer and a second CD with the files above. It is only working under DOS!

=== Using Preboot tool on linux ===

{{WARN|Try at your own risk!}}
This has been tested on a {{T60}} displaying the error '''e1000e the nvm checksum is not valid'''

1. Download [https://downloadcenter.intel.com/download/19186 Intel® Ethernet Connections Boot Utility, Preboot Images, and EFI Drivers '''(For Linux)''']
2. On a Terminal Go to the download directory {{cmduser|cd /path/to/Preboot.tar.gz}}
3. Create a folder for the files {{cmduser|mkdir Preboot}}
4. untar the file {{cmduser|tar -xvzf Preboot.tar.gz -C Preboot}}

if you're running a 32Bit installation of linux, follow this instructions

5. cd to BootUtil folder for your architecture {{cmduser|cd Preboot/APPS/BootUtil/Linux32/}}
6. Give execution permissions to bootutil32e {{cmduser|chmod +x bootutil32}}
7. Run {{cmduser|sudo ./bootutil32 -NIC=1 -DEFAULTCONFIG }}

if you're running a 64Bit installation of linux, follow this instructions
5. cd to BootUtil folder for your architecture {{cmduser|cd Preboot/APPS/BootUtil/Linux_x64}}
6. Give execution permissions to bootutil64e {{cmduser|chmod +x bootutil64e}}
7. Run {{cmduser|sudo ./bootutil64e -NIC=1 -DEFAULTCONFIG }}

[https://superuser.com/a/1170175/449434 Source (superuser.com)]

== Circumvention ==

* Upgrade your BIOS

Lenovo has published newer BIOS revisions that appear to fix the issue for some users. The BIOS upgrade turns off "Deep smart power down" which has been known to cause issues at initialization time (the driver can re-enable the issue later if you desire, the feature works correctly then).

* Insert a cable

Inserting a linked network cable bypasses the problem.

* Take the checksum twice

This [http://sourceforge.net/tracker/index.php?func=detail&aid=1474679&group_id=42302&atid=447449 bug report] describes a fix -- take the checksum twice. First time will report a bad checksum, second will work (the problem seems to be triggered by some power-saving technology). This requires a tweak to the driver source and a rebuild of your kernel. This is much better than a previous "fix" published here that disabled checksum checking entirely.

I updated the patch above to 2.6.22:
<pre>
diff -urN linux-2.6.22-suspend2-r1.orig/drivers/net/e1000/e1000_main.c linux-2.6.22-suspend2-r1/drivers/net/e1000/e1000_main.c
--- linux-2.6.22-suspend2-r1.orig/drivers/net/e1000/e1000_main.c 2007-08-17 23:32:04.000000000 +0200
+++ linux-2.6.22-suspend2-r1/drivers/net/e1000/e1000_main.c 2007-09-05 16:39:11.000000000 +0200
@@ -999,16 +999,18 @@
goto err_eeprom;
}

- /* before reading the EEPROM, reset the controller to
- * put the device in a known good starting state */
-
- e1000_reset_hw(&adapter->hw);
-
- /* make sure the EEPROM is good */
-
if (e1000_validate_eeprom_checksum(&adapter->hw) < 0) {
- DPRINTK(PROBE, ERR, "The EEPROM Checksum Is Not Valid\n");
- goto err_eeprom;
+ /* before reading the EEPROM, reset the controller to
+ * put the device in a known good starting state */
+
+ e1000_reset_hw(&adapter->hw);
+
+ /* make sure the EEPROM is good */
+
+ if (e1000_validate_eeprom_checksum(&adapter->hw) < 0) {
+ DPRINTK(PROBE, ERR, "The EEPROM Checksum Is Not Valid\n");
+ goto err_eeprom;
+ }
}

/* copy the MAC address out of the EEPROM */
</pre>
[[User:Ra|Ra]] 15:28, 5 September 2007 (UTC)

* Remove/add kernel module

Removing and adding the kernel module is a possible work-around. As root, run

<pre>
# modprobe -r e1000
# modprobe e1000
</pre>

On some occasions, the commands have to be run twice before eth0 becomes useable.
On some X60s this will not work at all.

* Disabling and re-enabling the NIC in the BIOS

For some it fixed the issue finally, for some it helped just temporarily.

* Hacking the kernel to carry on even if the checksum is not valid

Although being a very ugly, hack, this works fine for me. To do that, you have to search drivers/net/e1000/e1000_main.c for the line containing the error message and then comment out the following two lines which set the error state and then jump to the error code. Although this doesn't fry the hardware for me, consider yourself warned...

== See also ==

* [http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=MIGR-67166 Lenovo's solution]
* [http://sourceforge.net/tracker/index.php?func=detail&aid=1474679&group_id=42302&atid=447449 bug report] submitted for e1000 driver.
* Discussion at [http://forums.gentoo.org/viewtopic-t-476305-highlight-e1000.html Gentoo forums]

Problem with e1000: EEPROM Checksum Is Not Valid

2019-08-15T03:51:56Z

Cheloide: /* Solutions */

== Problem Description ==
On certain ThinkPads, [[e1000]] driver for [[Intel Gigabit Ethernet (10/100/1000)]] fails to load with the following error message in /var/log/messages:

<pre>
e1000: 0000:02:00.0: e1000_probe: The EEPROM Checksum Is Not Valid
e1000: probe of 0000:02:00.0 failed with error -5
</pre>

The problem is caused by a power savings feature obstructing normal operation, and causes the first bytes read from the EEPROM to be corrupt, resulting in a random or invalid MAC address (but no other data corruption). The EEPROM checksum test traps the problem and the driver refuses to load.

== Solutions ==

Try to reload the e1000 module until the ethernet is pluged in, and the hardware have a chance to detect a link.

=== Use e1000e---Kernel Patch ===
Auke Kok published two patches in October 2007 that help solve both the "corrupted" EEPROM read and bad latency.
One of the patches moves many network cards over to the e1000e (e1000 for PCI-Express) module. The second disables some PCIe power management features that were the cause for the bad EEPROM read and some stability issues.
[http://kerneltrap.org/mailarchive/linux-netdev/2007/10/31/374579 <nowiki>[PATCH 3/4] e1000/e1000e: Move PCI-Express device IDs over to e1000e</nowiki>]
[http://kerneltrap.org/mailarchive/linux-netdev/2007/10/31/374573 <nowiki>[PATCH 2/4] e1000e: Disable L1 ASPM power savings for 82573 mobile variants</nowiki>]
Refer to [http://www.linuxhq.com/patch-howto.html LinuxHQ] on how to apply kernel patches.

=== From Lenovo ===
Lenovo provides a [http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=MIGR-67166 script] that uses 'ethtool' command to update the card's settings. They say it is for SLED 10 but the Linux flavor shouldn't really matter. For some users, neither of the circumventions listed below help, but this script does!

=== Via module parameter ===

In recent kernels (at least with 2.6.22, maybe also in 2.6.21) there is a kernel module option to make the module ignore the error.

Load the module like this
<pre>
modprobe e1000 eeprom_bad_csum_allow=1
</pre>

You might also apply that parameter via modprobe.d or if you are using Debian/Ubuntu as append-line in your bootloader: e1000.eeprom_bad_csum_allow=1

=== From Mat's Blog ===
The fundamental solution is explained at [http://www.matinfo.ch/blog/archive/2007/01/26/intel-nic-pxe-e05-error.html Mat's Blog]
which directs the reader to Intel's site to download PROBOOT.EXE.

'''DO NOT USE THIS TOOL ON THINKPADS.''' The IBAUTIL.EXE tool that it contains is designed only to work with discrete ethernet parts that are on PCI/PCIe cards. It is not at all intended for use with laptop parts, although it is not sufficiently careful to refuse to run on such hardware. Improper use of this tool can leave your LAN firmware corrupted to the point that it will not even enumerate on the PCI bus and you will probably have to have your laptop repaired to restore the LAN functionality.
See http://www.mail-archive.com/e1000-devel@lists.sourceforge.net/msg00398.html for an Intel Linux driver employee's comments on this.
'''
=== Comment: ===
'''
I used PROBOOT.EXE Version 15.2 (file version 4.0.100.1124) on Bios Version 2.26 (79ETE6WW) for T60 Type 2007-53G with success.
The copied instruction is:
 “ Download PROBOOT.EXE from Intel. Get the first one from the list - the
one without Network adapter, it says only "Intel® Boot Agent PROBOOT.exe
version: 11.2", install that - it will create a folder with some files -
put these on a bootable floppy (or two) or a bootable CD. Boot to DOS with
the floppy or CD and run "IBAUtil.exe -DEFCFG" that will reset the
configuration and all should be OK „ 
I used an old bootable W98 to start the computer and a second CD with the files above. It is only working under DOS!

=== Using Preboot tool on linux ===
{{WARN|Try at your own risk!}}
This has been tested on a T60 displaying the error '''e1000e the nvm checksum is not valid'''

1. Download [https://downloadcenter.intel.com/download/19186 Intel® Ethernet Connections Boot Utility, Preboot Images, and EFI Drivers '''(For Linux)''']
2. On a Terminal Go to the download directory {{cmduser|cd /path/to/Preboot.tar.gz}}
3. Create a folder for the files {{cmduser|mkdir Preboot}}
4. untar the file {{cmduser|tar -xvzf Preboot.tar.gz -C Preboot}}

if you're running a 32Bit installation of linux, follow this instructions

5. cd to BootUtil folder for your architecture {{cmduser|cd Preboot/APPS/BootUtil/Linux32/}}
6. Give execution permissions to bootutil32e {{cmduser|chmod +x bootutil32}}
7. Run {{cmduser|sudo ./bootutil32 -NIC=1 -DEFAULTCONFIG }}

if you're running a 64Bit installation of linux, follow this instructions
5. cd to BootUtil folder for your architecture {{cmduser|cd Preboot/APPS/BootUtil/Linux_x64}}
6. Give execution permissions to bootutil64e {{cmduser|chmod +x bootutil64e}}
7. Run {{cmduser|sudo ./bootutil64e -NIC=1 -DEFAULTCONFIG }}

[https://superuser.com/a/1170175/449434 Source (superuser.com)]

== Circumvention ==

* Upgrade your BIOS

Lenovo has published newer BIOS revisions that appear to fix the issue for some users. The BIOS upgrade turns off "Deep smart power down" which has been known to cause issues at initialization time (the driver can re-enable the issue later if you desire, the feature works correctly then).

* Insert a cable

Inserting a linked network cable bypasses the problem.

* Take the checksum twice

This [http://sourceforge.net/tracker/index.php?func=detail&aid=1474679&group_id=42302&atid=447449 bug report] describes a fix -- take the checksum twice. First time will report a bad checksum, second will work (the problem seems to be triggered by some power-saving technology). This requires a tweak to the driver source and a rebuild of your kernel. This is much better than a previous "fix" published here that disabled checksum checking entirely.

I updated the patch above to 2.6.22:
<pre>
diff -urN linux-2.6.22-suspend2-r1.orig/drivers/net/e1000/e1000_main.c linux-2.6.22-suspend2-r1/drivers/net/e1000/e1000_main.c
--- linux-2.6.22-suspend2-r1.orig/drivers/net/e1000/e1000_main.c 2007-08-17 23:32:04.000000000 +0200
+++ linux-2.6.22-suspend2-r1/drivers/net/e1000/e1000_main.c 2007-09-05 16:39:11.000000000 +0200
@@ -999,16 +999,18 @@
goto err_eeprom;
}

- /* before reading the EEPROM, reset the controller to
- * put the device in a known good starting state */
-
- e1000_reset_hw(&adapter->hw);
-
- /* make sure the EEPROM is good */
-
if (e1000_validate_eeprom_checksum(&adapter->hw) < 0) {
- DPRINTK(PROBE, ERR, "The EEPROM Checksum Is Not Valid\n");
- goto err_eeprom;
+ /* before reading the EEPROM, reset the controller to
+ * put the device in a known good starting state */
+
+ e1000_reset_hw(&adapter->hw);
+
+ /* make sure the EEPROM is good */
+
+ if (e1000_validate_eeprom_checksum(&adapter->hw) < 0) {
+ DPRINTK(PROBE, ERR, "The EEPROM Checksum Is Not Valid\n");
+ goto err_eeprom;
+ }
}

/* copy the MAC address out of the EEPROM */
</pre>
[[User:Ra|Ra]] 15:28, 5 September 2007 (UTC)

* Remove/add kernel module

Removing and adding the kernel module is a possible work-around. As root, run

<pre>
# modprobe -r e1000
# modprobe e1000
</pre>

On some occasions, the commands have to be run twice before eth0 becomes useable.
On some X60s this will not work at all.

* Disabling and re-enabling the NIC in the BIOS

For some it fixed the issue finally, for some it helped just temporarily.

* Hacking the kernel to carry on even if the checksum is not valid

Although being a very ugly, hack, this works fine for me. To do that, you have to search drivers/net/e1000/e1000_main.c for the line containing the error message and then comment out the following two lines which set the error state and then jump to the error code. Although this doesn't fry the hardware for me, consider yourself warned...

== See also ==

* [http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=MIGR-67166 Lenovo's solution]
* [http://sourceforge.net/tracker/index.php?func=detail&aid=1474679&group_id=42302&atid=447449 bug report] submitted for e1000 driver.
* Discussion at [http://forums.gentoo.org/viewtopic-t-476305-highlight-e1000.html Gentoo forums]

Category:X1 Carbon (3rd Gen)

2019-08-15T03:15:14Z

Cheloide: Added System freezes

This page gives an overview of the Lenovo New ThinkPad X1 Carbon Ultrabook™ (3rd Gen) (2015), also referred to as '''X1C3'''. 
Previous generations: [[:Category:X1 Carbon|2012]], [[:Category:X1 Carbon 2nd|2014]]
{{QUOTE|Jonas Hendrickx|ThinkScopes.com|[http://www.thinkscopes.com/blog/2015/01/06/lenovo-thinkpad-x1-carbon-gen-3-review-2/ The new X1 Carbon Gen 3 goes by several name, internally it is referred as Mystique 2, while the gen 2 is Mystique 1, and ThinkPad X1 Carbon Gen 1 is called the Genesis]}}

= Details =
{{Todo|Please note that the specs below are incomplete, help needed!}}
* '''Machine type:''' 20BS*, 20BT*
* '''Processor:''' One of the following ULV fifth generation [[Intel Core]] processors (code name: "Broadwell"):
** Intel® Core™ i5-5200M (2.2-2.7GHz, 3MB L3 cache)
** Intel® Core™ i5-5300M (2.3-2.9GHz, 3MB L3 cache)
** Intel® Core™ i7-5500U (2.4-3.0GHz, 4MB L3 cache)
** Intel® Core™ i7-5600U (2.6-3.2GHz, 4MB L3 cache)
* '''Graphics:''' [[Intel HD Graphics|Intel HD Graphics 5500]]
* '''Display:'''
** 14.0" WQHD (2560x1440), 260nit, IPS with multitouch
** 14.0" WQHD (2560x1440), 300nit
** 14.0" HD+ (1920x1080), 300nit
* '''Memory:''' Soldered directly on the mainboard, with capacities of:
** 4GB DDR3L SDRAM PC3-12800
** 8GB DDR3L SDRAM PC3-12800
* '''Disk:'''
** 128GB SSD
** 256GB SSD
** 512GB PCIe SSD
* '''WLAN:'''
** Intel Dual-Band Wireless-N 7265 (Stone Peak 2 BN) 2x2 AC + Bluetooth 4.2
** Intel Dual-Band Wireless-AC 7265 (Stone Peak 2 AC) 2x2 AC + Bluetooth 4.2

* '''WWAN:'''
** Sierra Wireless EM7345
** Ericsson Business Mobile Networks BV N5321 gw
* '''Bluetooth:''' Bluetooth 4.2 supported by WLAN module
* '''Keyboard:''' 5-row with Trackpoint, backlit Keyboard keys
* '''I/O Ports:'''
** 2 x USB 3.0 (1 with AOU)
** Audio/Mic Combo
** OneLink Dock
** HDMI
** MiniDP
** Ethernet mini jack
** Sim card slot
* '''Battery:''' Up to 10.9 hours
* '''Webcam:''' [[Integrated camera]] 1.3MP - 720P with mute function
* '''Audio:''' Dolby® Home Theater® v4 with Digital Dual Array microphone certified for Microsoft Lync
* '''Fingerprint Reader''': yes
* '''Wired ethernet network''': yes, via a external dongle provided [https://www.flickr.com/photos/hendry/16769857511/ FRU:04X6435; Lenovo P/N:SC10A39882AB]
* Size: 13.03in x 8.94in x 0.73in (331mm x 227mm x 18.5mm)
* Weight: 3.07 lb (1.39 kg)

* [http://support.lenovo.com/us/en/products/laptops-and-netbooks/thinkpad-x-series-laptops/thinkpad-x1-carbon-20bs-20bt Download and support page for ThinkPad X1 Carbon 3rd Gen]
* [http://download.lenovo.com/pccbbs/mobiles_pdf/x1_carbon3_hmm_en_sp40g55065.pdf Hardware Maintenance Manual Thinkpad X1 Carbon 3] (52,995,586 bytes)

= Distro resources =
==Archlinux==
Amazingly the X1C3 works out of the box on Archlinux. Only a couple of niggly issues remain:
* HDMI sound output does not work
* Trackpad is a horrible UX
* [https://wiki.archlinux.org/index.php/Lenovo_ThinkPad_X1_Carbon_(Gen_3) Resources for running with Archlinux]

==Debian==
Debian Jessie worked out of the box via the Ethernet connection and a netinst image on USB. All buttons appear to work. Need some more time to test but amazing. Did install the non-free firmware and repos. Confirmed that HDMI audio does work however I had to configure the HDMI audio source to be higher in the list to be selected for output. ArchLinux above should work with proper settings.

==Ubuntu==
[http://fredrik.wendt.se/2015/02/24/lenovo-thinkpad-x1-carbon-3rd-gen/ Ubuntu 14.10 on ThinkPad X1 Carbon 3rd Gen]

= Troubleshooting =

== Unrecoverable System Freezes ==
Users have reported freezes when their systems are under medium/heavy load or playing html5 videos (Youtube, Netflix) with the only option being a hard power off.

this issue is usually related to c-states, a power saving feature on intel CPUs

===Fixes===
====Disabling c-states from bios (Easy)====
This solution is simpler than the others since does not involve editing system files nor needs superuser access.

1. Enter Bios Setup
2. Config > Power Management > CPU Power Management > Disabled

====Adding a Kernel parameter to GRUB Bootloader (Medium, needs administrator privileges)====
This solutions applies only to GRUB Bootloader, if you're not using GRUB [https://wiki.archlinux.org/index.php/kernel_parameters#Configuration you should search instructions on how to add kernel parameters to the one you're using], the parameter should be the same.

1. Edit file {{path|/etc/default/grub}}
2. Locate the variable {{bootparm|GRUB_CMDLINE_LINUX_DEFAULT|}}.
3. Add {{bootparm|intel_idle.max_cstate|0}} to the variable (0 should disable c-states falling back to acpi, 1 or 2 should work too). The variable should end similar to {{bootparm|GRUB_CMDLINE_LINUX_DEFAULT|intel_idle.max_cstate=0 quiet"}}
4. Run {{cmdroot|update-grub}} as administrator to apply the new configuration.
5. Reboot.

[https://bugzilla.kernel.org/show_bug.cgi?id=193011 Bugzilla Bug report ]

[https://bbs.archlinux.org/viewtopic.php?id=236686&p=2 ArchLinux forums ]

[[Category:X1_Carbon]][[Category:X Series]]