Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
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.
This is my first plea for help and I hope I am doing it right.
I am running 64-bit Linux Mint 17.2 Rafaela on an HP EliteBook 8570w (A7C38AV) with 16GiB System Memory and have 'lost' eth0. As I have searched the forums and google and found similar problems, but unfortunately, none of the solutions for those problems resolved mine, I am hoping to find an answer to my problem amongst you.
eth0 appeared to work fine yesterday before I shut down the system, but after starting and logging on today, I haven't been able to get it back online. I am fortunately able to use the wireless connection to access the internet and these forums. The very first thing I tried was 'apt-get update && apt-get dist-upgrade -y' followed by init 6, but that did not help.
I will greatly appreciate any help/advice.
The following is a description of my system and the steps I have taken until now:
Relevant System Information -
# uname -a
Linux hobo 3.16.0-38-generic #52~14.04.1-Ubuntu SMP Fri May 8 09:43:57 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
# cat /etc/lsb-release
DISTRIB_ID=LinuxMint
DISTRIB_RELEASE=17.2
DISTRIB_CODENAME=rafaela
DISTRIB_DESCRIPTION="Linux Mint 17.2 Rafaela"
# cat /etc/network/interfaces
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
BIOS Information
Vendor: Hewlett-Packard
Version: 68IAV Ver. F.40
Release Date: 01/31/2013
Address: 0xF0000
Runtime Size: 64 kB
ROM Size: 5120 kB
Characteristics:
PCI is supported
PC Card (PCMCIA) is supported
BIOS is upgradeable
BIOS shadowing is allowed
Boot from CD is supported
Selectable boot is supported
EDD is supported
Print screen service is supported (int 5h)
8042 keyboard services are supported (int 9h)
Serial services are supported (int 14h)
Printer services are supported (int 17h)
ACPI is supported
USB legacy is supported
Smart battery is supported
BIOS boot specification is supported
Function key-initiated network boot is supported
Targeted content distribution is supported
UEFI is supported
BIOS Revision: 15.64
Firmware Revision: 80.26
Steps and results until now -
# modprobe -r e1000e; modprobe e1000e
Afterwhich, the following was reported by dmesg:
[ 2283.177799] e1000e: Intel(R) PRO/1000 Network Driver - 2.3.2-k
[ 2283.177803] e1000e: Copyright(c) 1999 - 2014 Intel Corporation.
[ 2283.178167] e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
[ 2283.178213] e1000e 0000:00:19.0: irq 52 for MSI/MSI-X
[ 2283.954204] e1000e: probe of 0000:00:19.0 failed with error -2
I also installed kernel 4.2.0-30-generic, booted, repeated modprobe -r e1000e; modprobe e1000e, but the results were the same. Because of this I have gone back to booting kernel 3.16.0-38-generic.
Thanks for the recommendation, jefro. Before checking the forums today, I decided to take the battery out of the laptop and let it sit for a few minutes and after putting the battery back in and booting up, the interface was there. I had tried powering off (even overnight), but not removing the battery, so it appears to have been an issue with the BIOS and not the adapter or the kernel module.
Thanks again for all of your help and suggestions. The issue is resolved.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.