No ethernet link detected on internal ethernet connection

Resolve the "no ethernet link detected" error in Linux by verifying physical connections, checking cable integrity, and inspecting interface status via ip link. If hardware is functional, update network drivers or adjust MAC addresses to resolve software-level detection failures. This guide provides a systematic approach to restoring connectivity.

Verify Physical Layer Connectivity

Before diving into complex software diagnostics, ensure that the physical layer is functioning correctly. The most common cause of this error is a loose cable, a faulty port, or an inactive network interface card (NIC). Start by visually inspecting the Ethernet cable and the ports on both your computer and the router or switch. Look for bent pins inside the RJ45 connector and ensure the cable clicks securely into place. Check the LED indicators on the Ethernet port. Most modern NICs have lights that blink when data is transmitted and stay solid when a link is established. If no lights are active, the issue is likely hardware-related. Try using a different Ethernet cable, as cables can degrade over time or suffer from internal breaks. Additionally, test the port on the other end of the connection by plugging another device into it to rule out router-side issues. If you are using a docking station or USB-to-Ethernet adapter, ensure it is firmly seated and receiving adequate power. Some low-power ports may not provide sufficient voltage to activate the link negotiation process. Disconnecting and reconnecting the adapter while the system is running can sometimes re-trigger the enumeration process.

Check Interface Status with Command Line Tools

Once physical connections are confirmed, use Linux command-line tools to diagnose why the operating system does not detect the link. Open a terminal and run the following command to list all network interfaces and their states:

ip link show

Look for your Ethernet interface, which typically has a name like eth0, enp3s0, or ens33. Check the state field. If it says DOWN, the interface is administratively disabled. You can bring it up using:

sudo ip link set eth0 up

Replace eth0 with your actual interface name. If the state is NO-CARRIER, it means the kernel sees the device but detects no physical link. This often points to driver issues or mismatched speed/duplex settings. If the interface is UP but still shows no IP address, proceed to check your network configuration files. For more detailed troubleshooting on reachability, consider reviewing Troubleshooting Linux Device Not Reachable During Network (Ping).

Inspect Driver and Kernel Messages

Kernel logs often contain crucial information about why an Ethernet controller fails to establish a link. Use the dmesg command to filter messages related to your network interface. Run:

dmesg | grep -i eth

Or, if you know the specific PCI address of your NIC, search for that identifier. Look for errors such as "firmware missing," "probe failed," or "link down." If the driver fails to load properly, you may need to reinstall or update the kernel module. Identify the driver currently in use by running:

ethtool -i eth0

This command displays the driver name, version, and bus information. If the driver is outdated or incompatible with your kernel version, consider updating your system packages. On Ubuntu-based systems, use:

sudo apt update && sudo apt upgrade

On Fedora or RHEL-based distributions, use:

sudo dnf update

After updating, reboot your system to ensure the new kernel modules are loaded. If the problem persists, check if the firmware package for your NIC is installed. Many modern Intel and Realtek cards require separate firmware blobs to function correctly.

Adjust Speed and Duplex Settings

In some cases, auto-negotiation between your NIC and the switch fails due to mismatched settings. You can manually set the speed and duplex mode using ethtool. First, check current settings:

ethtool eth0

Look for the "Speed" and "Duplex" fields. If they show "Unknown" or "Auto," try forcing a specific setting. For example, to force 100 Mbps full duplex:

sudo ethtool -s eth0 speed 100 duplex full autoneg off

Test if the link comes up. If it does, you can make this change persistent by adding the command to a network configuration script or systemd service. However, manual settings should be used cautiously, as they can cause collisions if the other end of the link is configured differently. Always revert to auto-negotiation unless necessary:

sudo ethtool -s eth0 autoneg on

For advanced scenarios involving emulated Ethernet or virtual interfaces, refer to How to Emulate Ethernet between two USB-C ports in Linux to understand how virtual links differ from physical ones.

Reset Network Manager Configuration

Network managers like Netplan, NetworkManager, or systemd-networkd can sometimes hold onto stale configurations. Resetting these services can clear corrupted state. For Netplan users on Ubuntu, regenerate the configuration:

sudo netplan generate
sudo netplan apply

For NetworkManager, restart the service:

sudo systemctl restart NetworkManager

Clear any cached DHCP leases by deleting the lease files in /var/lib/NetworkManager/ or /run/dbus/, depending on your distribution. This forces the system to request a fresh IP address upon reconnection. If you suspect a conflict with MAC addresses, especially after cloning a VM or replacing hardware, generate a new random MAC address temporarily to see if the switch accepts the connection.

Frequently Asked Questions

Why does my Ethernet light stay off even with a good cable?

The light may remain off if the NIC is powered down in BIOS/UEFI settings or if the driver is not loaded. Check your system's hardware configuration to ensure the onboard LAN is enabled. Additionally, verify that the kernel module is active using lsmod.

Can I fix this issue without root access?

No, diagnosing and fixing link detection issues requires administrative privileges. Commands like ip link set and ethtool need root permissions to modify interface states. Without root access, you can only view status but cannot change configurations.

What causes auto-negotiation to fail?

Auto-negotiation can fail due to mismatched cable categories, faulty wiring, or incompatible switch ports. It may also fail if one side is forced to a specific speed while the other remains on auto. Using a Cat5e or higher cable usually resolves basic negotiation issues.

How do I check if my NIC is recognized by the kernel?

Use the lspci | grep -i ethernet command to list all Ethernet controllers detected by the PCI bus. If your NIC appears here but shows no link, the hardware is recognized but may have driver or configuration problems.

Is it safe to disable IPv6 to fix Ethernet issues?

Disabling IPv6 rarely fixes physical link detection problems, as link status operates at Layer 1 and 2 of the OSI model. However, it can help resolve connectivity issues where IPv6 routing conflicts prevent traffic flow. Adjust this setting only after confirming the physical link is established.