[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: wired network connection has stopped working



On Friday 21 August 2015 22:07:27 tom arnall wrote:

> Greetings!

>

> About a year ago my wired modem connection stopped working. I can find

> nothing on google which helps.

>

> In dmesg there is:

>

> eth0: link is not ready

>

> Here is ifconfig output, in case it is useful for people trying to

> help me with the problem:

>

> eth0 Link encap:Ethernet HWaddr 00:24:7e:6a:c3:93

> UP BROADCAST MULTICAST MTU:1500 Metric:1

> RX packets:0 errors:0 dropped:0 overruns:0 frame:0

> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0

> collisions:0 txqueuelen:1000

> RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

> Interrupt:20 Memory:fc600000-fc620000

 

Can you check that the ethernet cable is detected with

 

ethtool eth0

 

It should report something like this:

 

Settings for eth0:

Supported ports: [ TP ]

Supported link modes: 10baseT/Half 10baseT/Full

100baseT/Half 100baseT/Full

1000baseT/Half 1000baseT/Full

Supported pause frame use: No

Supports auto-negotiation: Yes

Advertised link modes: 10baseT/Half 10baseT/Full

100baseT/Half 100baseT/Full

1000baseT/Half 1000baseT/Full

Advertised pause frame use: Symmetric

Advertised auto-negotiation: Yes

Link partner advertised link modes: 10baseT/Half 10baseT/Full

100baseT/Half 100baseT/Full

Link partner advertised pause frame use: Symmetric

Link partner advertised auto-negotiation: Yes

Speed: 100Mb/s

Duplex: Full

Port: Twisted Pair

PHYAD: 1

Transceiver: internal

Auto-negotiation: on

MDI-X: off

Supports Wake-on: g

Wake-on: g

Link detected: yes

 

See that the "Link detected" is "yes". Make sure the speed is at least 100Mb/s full duplex. 10Mb/s or half duplex would mean there is likely a problem with the cable.

 

This week, I recently experienced a problem with a I217-V network card on a HP laptop. It was impossible to stay connected to a ssh server for long. The connection was lost after a few seconds. It turned out it was caused by the power management (Wake on Lan) as configured by the Windows driver. Disabling Wol on Windows solved the problem. The problem suddenly appeared after some update or other on the Windows side or the Linux side somewhere during the last month.

 

Frederic


Reply to: