Ethernet does not work at all
I haven't used my NIC for some time, and now it doesn't work anymore, at all. I can assign IP addresses to it manually (sudo ip addr add 192.168.2.155/24 broadcast 192.168.2.255 dev eth0
, for example), but I cannot even ping hosts in the same network.
Very suspicious in my eyes is that ethtool (ethtool -S eth0
) displays some transmitted packets, but always exactly zero received bytes & packets. Something is clearly wrong.
Here is a list of the things I tried
- rebooting
- tried other cable
- tried other port (this laptop has one port on it's docking station and one on the laptop itself ; they're internally connected to the same NIC)
- tried other switch (switch A: 8 port GbE, switch B: 5 port 100 MbE)
- Downgraded kernel and linux-firmware to older versions (3.13 and mid-2013 respectively)
- booted latest arch linux live medium ; didn't work, same symptoms
booted Ubuntu 14.04.1 live medium ; didn't work, same symptoms
In every setup mentioned above I tried accessing the network by manually assigning an IP address, by using wicd. In the start I also tried NetworkManager, same results
At this point I suspect the NIC may be broken, if so, how could I validate this or rule it out?
This is the NIC in question (Thinkpad X200):
00:19.0 Ethernet controller: Intel Corporation 82567LM Gigabit Network Connection (rev 03)
Subsystem: Lenovo Device 20ee
Flags: bus master, fast devsel, latency 0, IRQ 44
Memory at f2600000 (32-bit, non-prefetchable) [size=128K]
Memory at f2625000 (32-bit, non-prefetchable) [size=4K]
I/O ports at 1840 [size=32]
Capabilities: [c8] Power Management version 2
Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [e0] PCI Advanced Features
Kernel driver in use: e1000e
Kernel modules: e1000e
ethtool -S eth0:
NIC statistics:
rx_packets: 0
tx_packets: 90
rx_bytes: 0
tx_bytes: 8113
rx_broadcast: 0
tx_broadcast: 70
rx_multicast: 0
tx_multicast: 20
rx_errors: 0
tx_errors: 0
tx_dropped: 0
multicast: 0
collisions: 0
rx_length_errors: 0
rx_over_errors: 0
rx_crc_errors: 0
rx_frame_errors: 0
rx_no_buffer_count: 0
rx_missed_errors: 0
tx_aborted_errors: 0
tx_carrier_errors: 0
tx_fifo_errors: 0
tx_heartbeat_errors: 0
tx_window_errors: 0
tx_abort_late_coll: 0
tx_deferred_ok: 0
tx_single_coll_ok: 0
tx_multi_coll_ok: 0
tx_timeout_count: 0
tx_restart_queue: 0
rx_long_length_errors: 0
rx_short_length_errors: 0
rx_align_errors: 0
tx_tcp_seg_good: 0
tx_tcp_seg_failed: 0
rx_flow_control_xon: 0
rx_flow_control_xoff: 0
tx_flow_control_xon: 0
tx_flow_control_xoff: 0
rx_csum_offload_good: 0
rx_csum_offload_errors: 0
rx_header_split: 0
alloc_rx_buff_failed: 0
tx_smbus: 0
rx_smbus: 0
dropped_smbus: 0
rx_dma_failed: 0
tx_dma_failed: 0
rx_hwtstamp_cleared: 0
uncorr_ecc_errors: 0
corr_ecc_errors: 0
Using tcpdump -i eth0 I don't see any traffic at all.
networking arch-linux
bumped to the homepage by Community♦ 49 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
I haven't used my NIC for some time, and now it doesn't work anymore, at all. I can assign IP addresses to it manually (sudo ip addr add 192.168.2.155/24 broadcast 192.168.2.255 dev eth0
, for example), but I cannot even ping hosts in the same network.
Very suspicious in my eyes is that ethtool (ethtool -S eth0
) displays some transmitted packets, but always exactly zero received bytes & packets. Something is clearly wrong.
Here is a list of the things I tried
- rebooting
- tried other cable
- tried other port (this laptop has one port on it's docking station and one on the laptop itself ; they're internally connected to the same NIC)
- tried other switch (switch A: 8 port GbE, switch B: 5 port 100 MbE)
- Downgraded kernel and linux-firmware to older versions (3.13 and mid-2013 respectively)
- booted latest arch linux live medium ; didn't work, same symptoms
booted Ubuntu 14.04.1 live medium ; didn't work, same symptoms
In every setup mentioned above I tried accessing the network by manually assigning an IP address, by using wicd. In the start I also tried NetworkManager, same results
At this point I suspect the NIC may be broken, if so, how could I validate this or rule it out?
This is the NIC in question (Thinkpad X200):
00:19.0 Ethernet controller: Intel Corporation 82567LM Gigabit Network Connection (rev 03)
Subsystem: Lenovo Device 20ee
Flags: bus master, fast devsel, latency 0, IRQ 44
Memory at f2600000 (32-bit, non-prefetchable) [size=128K]
Memory at f2625000 (32-bit, non-prefetchable) [size=4K]
I/O ports at 1840 [size=32]
Capabilities: [c8] Power Management version 2
Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [e0] PCI Advanced Features
Kernel driver in use: e1000e
Kernel modules: e1000e
ethtool -S eth0:
NIC statistics:
rx_packets: 0
tx_packets: 90
rx_bytes: 0
tx_bytes: 8113
rx_broadcast: 0
tx_broadcast: 70
rx_multicast: 0
tx_multicast: 20
rx_errors: 0
tx_errors: 0
tx_dropped: 0
multicast: 0
collisions: 0
rx_length_errors: 0
rx_over_errors: 0
rx_crc_errors: 0
rx_frame_errors: 0
rx_no_buffer_count: 0
rx_missed_errors: 0
tx_aborted_errors: 0
tx_carrier_errors: 0
tx_fifo_errors: 0
tx_heartbeat_errors: 0
tx_window_errors: 0
tx_abort_late_coll: 0
tx_deferred_ok: 0
tx_single_coll_ok: 0
tx_multi_coll_ok: 0
tx_timeout_count: 0
tx_restart_queue: 0
rx_long_length_errors: 0
rx_short_length_errors: 0
rx_align_errors: 0
tx_tcp_seg_good: 0
tx_tcp_seg_failed: 0
rx_flow_control_xon: 0
rx_flow_control_xoff: 0
tx_flow_control_xon: 0
tx_flow_control_xoff: 0
rx_csum_offload_good: 0
rx_csum_offload_errors: 0
rx_header_split: 0
alloc_rx_buff_failed: 0
tx_smbus: 0
rx_smbus: 0
dropped_smbus: 0
rx_dma_failed: 0
tx_dma_failed: 0
rx_hwtstamp_cleared: 0
uncorr_ecc_errors: 0
corr_ecc_errors: 0
Using tcpdump -i eth0 I don't see any traffic at all.
networking arch-linux
bumped to the homepage by Community♦ 49 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
I haven't used my NIC for some time, and now it doesn't work anymore, at all. I can assign IP addresses to it manually (sudo ip addr add 192.168.2.155/24 broadcast 192.168.2.255 dev eth0
, for example), but I cannot even ping hosts in the same network.
Very suspicious in my eyes is that ethtool (ethtool -S eth0
) displays some transmitted packets, but always exactly zero received bytes & packets. Something is clearly wrong.
Here is a list of the things I tried
- rebooting
- tried other cable
- tried other port (this laptop has one port on it's docking station and one on the laptop itself ; they're internally connected to the same NIC)
- tried other switch (switch A: 8 port GbE, switch B: 5 port 100 MbE)
- Downgraded kernel and linux-firmware to older versions (3.13 and mid-2013 respectively)
- booted latest arch linux live medium ; didn't work, same symptoms
booted Ubuntu 14.04.1 live medium ; didn't work, same symptoms
In every setup mentioned above I tried accessing the network by manually assigning an IP address, by using wicd. In the start I also tried NetworkManager, same results
At this point I suspect the NIC may be broken, if so, how could I validate this or rule it out?
This is the NIC in question (Thinkpad X200):
00:19.0 Ethernet controller: Intel Corporation 82567LM Gigabit Network Connection (rev 03)
Subsystem: Lenovo Device 20ee
Flags: bus master, fast devsel, latency 0, IRQ 44
Memory at f2600000 (32-bit, non-prefetchable) [size=128K]
Memory at f2625000 (32-bit, non-prefetchable) [size=4K]
I/O ports at 1840 [size=32]
Capabilities: [c8] Power Management version 2
Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [e0] PCI Advanced Features
Kernel driver in use: e1000e
Kernel modules: e1000e
ethtool -S eth0:
NIC statistics:
rx_packets: 0
tx_packets: 90
rx_bytes: 0
tx_bytes: 8113
rx_broadcast: 0
tx_broadcast: 70
rx_multicast: 0
tx_multicast: 20
rx_errors: 0
tx_errors: 0
tx_dropped: 0
multicast: 0
collisions: 0
rx_length_errors: 0
rx_over_errors: 0
rx_crc_errors: 0
rx_frame_errors: 0
rx_no_buffer_count: 0
rx_missed_errors: 0
tx_aborted_errors: 0
tx_carrier_errors: 0
tx_fifo_errors: 0
tx_heartbeat_errors: 0
tx_window_errors: 0
tx_abort_late_coll: 0
tx_deferred_ok: 0
tx_single_coll_ok: 0
tx_multi_coll_ok: 0
tx_timeout_count: 0
tx_restart_queue: 0
rx_long_length_errors: 0
rx_short_length_errors: 0
rx_align_errors: 0
tx_tcp_seg_good: 0
tx_tcp_seg_failed: 0
rx_flow_control_xon: 0
rx_flow_control_xoff: 0
tx_flow_control_xon: 0
tx_flow_control_xoff: 0
rx_csum_offload_good: 0
rx_csum_offload_errors: 0
rx_header_split: 0
alloc_rx_buff_failed: 0
tx_smbus: 0
rx_smbus: 0
dropped_smbus: 0
rx_dma_failed: 0
tx_dma_failed: 0
rx_hwtstamp_cleared: 0
uncorr_ecc_errors: 0
corr_ecc_errors: 0
Using tcpdump -i eth0 I don't see any traffic at all.
networking arch-linux
I haven't used my NIC for some time, and now it doesn't work anymore, at all. I can assign IP addresses to it manually (sudo ip addr add 192.168.2.155/24 broadcast 192.168.2.255 dev eth0
, for example), but I cannot even ping hosts in the same network.
Very suspicious in my eyes is that ethtool (ethtool -S eth0
) displays some transmitted packets, but always exactly zero received bytes & packets. Something is clearly wrong.
Here is a list of the things I tried
- rebooting
- tried other cable
- tried other port (this laptop has one port on it's docking station and one on the laptop itself ; they're internally connected to the same NIC)
- tried other switch (switch A: 8 port GbE, switch B: 5 port 100 MbE)
- Downgraded kernel and linux-firmware to older versions (3.13 and mid-2013 respectively)
- booted latest arch linux live medium ; didn't work, same symptoms
booted Ubuntu 14.04.1 live medium ; didn't work, same symptoms
In every setup mentioned above I tried accessing the network by manually assigning an IP address, by using wicd. In the start I also tried NetworkManager, same results
At this point I suspect the NIC may be broken, if so, how could I validate this or rule it out?
This is the NIC in question (Thinkpad X200):
00:19.0 Ethernet controller: Intel Corporation 82567LM Gigabit Network Connection (rev 03)
Subsystem: Lenovo Device 20ee
Flags: bus master, fast devsel, latency 0, IRQ 44
Memory at f2600000 (32-bit, non-prefetchable) [size=128K]
Memory at f2625000 (32-bit, non-prefetchable) [size=4K]
I/O ports at 1840 [size=32]
Capabilities: [c8] Power Management version 2
Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [e0] PCI Advanced Features
Kernel driver in use: e1000e
Kernel modules: e1000e
ethtool -S eth0:
NIC statistics:
rx_packets: 0
tx_packets: 90
rx_bytes: 0
tx_bytes: 8113
rx_broadcast: 0
tx_broadcast: 70
rx_multicast: 0
tx_multicast: 20
rx_errors: 0
tx_errors: 0
tx_dropped: 0
multicast: 0
collisions: 0
rx_length_errors: 0
rx_over_errors: 0
rx_crc_errors: 0
rx_frame_errors: 0
rx_no_buffer_count: 0
rx_missed_errors: 0
tx_aborted_errors: 0
tx_carrier_errors: 0
tx_fifo_errors: 0
tx_heartbeat_errors: 0
tx_window_errors: 0
tx_abort_late_coll: 0
tx_deferred_ok: 0
tx_single_coll_ok: 0
tx_multi_coll_ok: 0
tx_timeout_count: 0
tx_restart_queue: 0
rx_long_length_errors: 0
rx_short_length_errors: 0
rx_align_errors: 0
tx_tcp_seg_good: 0
tx_tcp_seg_failed: 0
rx_flow_control_xon: 0
rx_flow_control_xoff: 0
tx_flow_control_xon: 0
tx_flow_control_xoff: 0
rx_csum_offload_good: 0
rx_csum_offload_errors: 0
rx_header_split: 0
alloc_rx_buff_failed: 0
tx_smbus: 0
rx_smbus: 0
dropped_smbus: 0
rx_dma_failed: 0
tx_dma_failed: 0
rx_hwtstamp_cleared: 0
uncorr_ecc_errors: 0
corr_ecc_errors: 0
Using tcpdump -i eth0 I don't see any traffic at all.
networking arch-linux
networking arch-linux
edited Aug 23 '14 at 15:40
dom0
asked Aug 23 '14 at 15:12
dom0dom0
193110
193110
bumped to the homepage by Community♦ 49 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 49 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Connect to a network wired or wireless. dhcpcd
is automatically loaded on boot.
dhcpcd.service
is started by default for all interfaces. Stop it if manually configuring wired network.
systemctl stop dhcpcd.service
for connecting to a wireless network
wifi-menu wlo1
with wlo1
being the wireless interface.ip link
to see interfaces, or to bind dhcpcd
to ethernet use
systemctl start dhcpcd@eth0.service
If dhcpd fails on startup, start dhcpcd manually.
dhcpcd eth0
Archlinux wiki network configuration
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f151778%2fethernet-does-not-work-at-all%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Connect to a network wired or wireless. dhcpcd
is automatically loaded on boot.
dhcpcd.service
is started by default for all interfaces. Stop it if manually configuring wired network.
systemctl stop dhcpcd.service
for connecting to a wireless network
wifi-menu wlo1
with wlo1
being the wireless interface.ip link
to see interfaces, or to bind dhcpcd
to ethernet use
systemctl start dhcpcd@eth0.service
If dhcpd fails on startup, start dhcpcd manually.
dhcpcd eth0
Archlinux wiki network configuration
add a comment |
Connect to a network wired or wireless. dhcpcd
is automatically loaded on boot.
dhcpcd.service
is started by default for all interfaces. Stop it if manually configuring wired network.
systemctl stop dhcpcd.service
for connecting to a wireless network
wifi-menu wlo1
with wlo1
being the wireless interface.ip link
to see interfaces, or to bind dhcpcd
to ethernet use
systemctl start dhcpcd@eth0.service
If dhcpd fails on startup, start dhcpcd manually.
dhcpcd eth0
Archlinux wiki network configuration
add a comment |
Connect to a network wired or wireless. dhcpcd
is automatically loaded on boot.
dhcpcd.service
is started by default for all interfaces. Stop it if manually configuring wired network.
systemctl stop dhcpcd.service
for connecting to a wireless network
wifi-menu wlo1
with wlo1
being the wireless interface.ip link
to see interfaces, or to bind dhcpcd
to ethernet use
systemctl start dhcpcd@eth0.service
If dhcpd fails on startup, start dhcpcd manually.
dhcpcd eth0
Archlinux wiki network configuration
Connect to a network wired or wireless. dhcpcd
is automatically loaded on boot.
dhcpcd.service
is started by default for all interfaces. Stop it if manually configuring wired network.
systemctl stop dhcpcd.service
for connecting to a wireless network
wifi-menu wlo1
with wlo1
being the wireless interface.ip link
to see interfaces, or to bind dhcpcd
to ethernet use
systemctl start dhcpcd@eth0.service
If dhcpd fails on startup, start dhcpcd manually.
dhcpcd eth0
Archlinux wiki network configuration
answered Aug 23 '14 at 17:28
portport
5113
5113
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f151778%2fethernet-does-not-work-at-all%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown