ethernet 82573L on-chip is not working on my Thinkpad
Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
ethernet 82573L on-chip is not working on my Thinkpad
ethernet 82573L on-chip is not working on my Thinkpad. It is working alright with Windoes 7 on the same Thinkpad computer -- so it apparently is not a hardware problem. My system ist Linux Mint 19.1
The e1000e driver is activated for a device at PCI bus address 0000:02:00.0. Vendor and model number of that device is 8086:109a, and PCI lookup confirms that it's your card, indeed.
There are two messages that don't look good, though I can't say what they really mean:
Code:
[ 3.170785] e1000e 0000:02:00.0: The NVM Checksum Is Not Valid
...
[ 3.192214] e1000e: probe of 0000:02:00.0 failed with error -5
After the "probe failed" message, nothing. I guess the driver thinks that something is wrong with the interface. Or perhaps something is indeed wrong, the Windows driver doesn't care, and the Linux driver does.
Googling for these messages yields several results. This one looks promising: https://superuser.com/questions/1104...el-ethernet-co, though it seems that the solution involves patching the driver source code. It's over two years old, too; if this is a driver bug, it should be fixed. Perhaps it's sufficient to update the driver?
At this point I am afraid I am not much smarter than you and definitely not smarter than Google .
Last edited by berndbausch; 01-07-2019 at 04:59 AM.
<snip>
[By the way, how do you insert those nice "code:" windows?]
You can use the quote and/or code tags in the reply window or edit window by highlighting the text and selecting the # for code and quote balloon(left of the #) for quoting which is on the window menu above the edit window.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.