You are not logged in.
Pages: 1
Hi there,
I have trouble to configure my ethernet link. It worked well a week ago. I think it appears after systemd update (but i am not sure...) :
- libsystemd (234.11-3 -> 234.11-4)
- systemd (234.11-3 -> 234.11-4)
- linux (4.12.3-1 -> 4.12.4-1)
ip link show eno1
2: eno1: <NO-CARRIER,BROADCAST,MULTICAST,PROMISC,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
link/ether brd ff:ff:ff:ff:ff:ff
networkctl
IDX LINK TYPE OPERATIONAL SETUP
1 lo loopback carrier unmanaged
2 eno1 ether no-carrier configuring
3 wwp0s20u8c2i12 wwan off unmanaged
4 wlp2s0 wlan routable configured
4 links listed.
cat /etc/systemd/network/eno1.network
[Match]
Name=eno1
[Network]
DHCP=yes
[DHCP]
RouteMetric=10
dmesg | grep e1000e
[ 10.935543] e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
[ 10.935544] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
[ 10.935757] e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
[ 11.025832] e1000e 0000:00:19.0 0000:00:19.0 (uninitialized): registered PHC clock
[ 11.108408] e1000e 0000:00:19.0 eth0: (PCI Express:2.5GT/s:Width x1) 34:e6:d7:3a:28:83
[ 11.108415] e1000e 0000:00:19.0 eth0: Intel(R) PRO/1000 Network Connection
[ 11.108449] e1000e 0000:00:19.0 eth0: MAC: 11, PHY: 12, PBA No: FFFFFF-0FF
[ 11.284533] e1000e 0000:00:19.0 eno1: renamed from eth0
journalctl -u systemd-networkd
-- Reboot --
Aug 09 16:26:34 systemd[1]: Starting Network Service...
Aug 09 16:26:34 systemd-networkd[269]: Enumeration completed
Aug 09 16:26:34 systemd[1]: Started Network Service.
Aug 09 16:26:34 systemd-networkd[269]: eth0: Renamed to eno1
Aug 09 16:26:34 systemd-networkd[269]: eno1: IPv6 successfully enabled
Aug 09 16:26:35 systemd-networkd[269]: wwan0: Renamed to wwp0s20u8c2i12
Aug 09 16:26:35 systemd-networkd[269]: wlan0: Renamed to wlp2s0
Aug 09 16:26:35 systemd-networkd[269]: wlp2s0: IPv6 successfully enabled
Aug 09 16:26:39 systemd-networkd[269]: wlp2s0: Gained carrier
Aug 09 16:26:39 systemd-networkd[269]: wlp2s0: DHCPv4 address 192.168.1.128/24 via 192.168.1.1
Aug 09 16:26:40 systemd-networkd[269]: wlp2s0: Gained IPv6LL
Aug 09 16:26:52 systemd-networkd[269]: wlp2s0: Configured
I didn't find solution for this... Add an IP address manually did'nt bring the interface up.
Thanks !
Last edited by yelin (2017-09-07 15:11:32)
Offline
Plug the cable in. Seriously.
What are the status of the link LEDs on you NIC? Have you access to the router? What are the status of its Link LEDs for your port?
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
Yes, of course the cable is plug. The leds are off. I tried it with multiple cables, with multiple switch/routeur.
It works fine with others computers.
Offline
You would be astonished how often it is the cable I am bothered that the link lights are off.
What happens if you boot from the install media or a different operating system?
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
I can imagine
I just tried to boot from a live system. I have the same problem.
My laptop is a Dell one, and I have no ethernet when I plug it on the docking station (I repeat that i'm sure about the cable ).
edit : I checked the bios configuration, the NIC interface is enable.
Last edited by yelin (2017-08-09 16:55:31)
Offline
Hi there,
I have trouble to configure my ethernet link. It worked well a week ago. I think it appears after systemd update (but i am not sure...) :
- libsystemd (234.11-3 -> 234.11-4)
- systemd (234.11-3 -> 234.11-4)
- linux (4.12.3-1 -> 4.12.4-1)
Have you tried rolling back those packages to check whether it is definitely a software problem?
Last edited by Slithery (2017-08-09 16:57:59)
Offline
Well, I downgraded systemd and linux kernel but there is no change...
It seems like a hardware issue, but the problem appears with the docking station too. Any idea ?
Offline
The problem persist after a BIOS upgrade.
Next step is to put my SSD in another laptop (if I can find one).
Last edited by yelin (2017-08-10 07:53:55)
Offline
I put another SSD in the laptop. The problem persist. I will send it back to after sale service.
Many thanks to both of you for your ideas.
Offline
when I plug it on the docking station
...
Does the notebook have an integrated RJ45 slot?
Offline
Yes, it have an integrated NIC.
Offline
Bypass the dock?
Offline
The problem exist for both the integrated RJ45 slot and the docking station slot.
Offline
Have you checked your bios/firmware setup for any option about blocking access to the network port? It's a huge coincidence that all ethernet ports stopped working.
R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K
Offline
Yes, I agree it is really strange, but i updated the BIOS. The ethernet interface is enable.
Offline
The dock is probably only a relay for the integrated NIC.
What chip is that actually (lspci -v) and (grep dmesg) does it load some firmware?
Offline
You are right, only one driver (e1000e) is loaded when the laptop is plugged or not.
Offline
what model is your laptop? have you checked that it is not blocked by some combination of keys?
Offline
What happens if you reload the module and what is the power state of its PCI device?
Offline
It was a Dell e7450. Dell just changed my laptop, so my problem is solved, I guess.
Offline
Pages: 1