You are not logged in.

#1 2013-03-10 19:39:55

janoliver
Member
Registered: 2011-06-01
Posts: 48

[solved] e1000e: Ethernet Port not seeing any carriers

Hi, I really don't know what to do anymore.

My ethernet port, who is named enp0s25 by systemd, doesn't work. After boot it is down, after setting it up by either ifconfig or "ip link", it shows the following:

 ~ ifconfig                
enp0s25: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether 64:31:50:94:20:0a  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 20  memory 0xd4800000-d4820000
~ ip addr
...
4: enp0s25: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN qlen 1000
    link/ether 64:31:50:94:20:0a brd ff:ff:ff:ff:ff:ff

Sometimes, the device is apparently sleeping, because

~ ethtool enp0s25    
Settings for enp0s25:
Cannot get device settings: No such device
Cannot get wake-on-lan settings: No such device
Cannot get message level: No such device
Cannot get link status: No such device

But with "modprobe -r e1000e && modprobe e1000e" I can wake it up:

~ sudo ethtool enp0s25                           
Settings for enp0s25:
	Supported ports: [ TP ]
	Supported link modes:   10baseT/Half 10baseT/Full 
	                        100baseT/Half 100baseT/Full 
	                        1000baseT/Full 
	Supported pause frame use: No
	Supports auto-negotiation: Yes
	Advertised link modes:  10baseT/Half 10baseT/Full 
	                        100baseT/Half 100baseT/Full 
	                        1000baseT/Full 
	Advertised pause frame use: No
	Advertised auto-negotiation: Yes
	Speed: Unknown!
	Duplex: Unknown! (255)
	Port: Twisted Pair
	PHYAD: 1
	Transceiver: internal
	Auto-negotiation: on
	MDI-X: Unknown (auto)
	Supports Wake-on: pumbg
	Wake-on: g
	Current message level: 0x00000007 (7)
			       drv probe link
	Link detected: no

This is what dmesg says during boot and trying to use the port:

~ dmesg | grep e1000e
[    4.369636] e1000e: Intel(R) PRO/1000 Network Driver - 2.1.4-k
[    4.369640] e1000e: Copyright(c) 1999 - 2012 Intel Corporation.
[    4.378023] e1000e 0000:00:19.0: setting latency timer to 64
[    4.378104] e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
[    4.378139] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[    4.755103] e1000e 0000:00:19.0 eth0: (PCI Express:2.5GT/s:Width x1) 64:31:50:94:20:0a
[    4.755107] e1000e 0000:00:19.0 eth0: Intel(R) PRO/1000 Network Connection
[    4.755158] e1000e 0000:00:19.0 eth0: MAC: 10, PHY: 11, PBA No: FFFFFF-0FF
[  142.346831] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[  142.449982] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[  379.944965] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X

The device works perfectly with a recent arch live cd and also in windows. I nowhere can find any errors or warnings concerning this. What can I do?

Oli

PS: I tried several boot parameters I found on the internet related to pci stuff, nothing helped. The device did work a couple of days ago but I can't recall if some kernel update or anything else broke it.

Last edited by janoliver (2013-03-10 22:16:55)

Offline

#2 2013-03-10 22:03:28

mich41
Member
Registered: 2012-06-22
Posts: 592

Re: [solved] e1000e: Ethernet Port not seeing any carriers

Looks like a kernel bug. You should have old kernel packages laying in /var/cache/pacman/pkg/ so you can try reverting to some older version.

Once you have a version which works and one which doesn't, you can download git repo and git-bisect the exact commit which screwed things up. Or hope that somebody else does it and eventually it'll get fixed upstream; actually if the bug isn't somehow specific to your hardware it's likely that it will be discovered independently by others and fixed.

Last edited by mich41 (2013-03-10 22:07:21)

Offline

#3 2013-03-10 22:16:30

janoliver
Member
Registered: 2011-06-01
Posts: 48

Re: [solved] e1000e: Ethernet Port not seeing any carriers

Hi, thank you for the answer and yes, you are right. I found the discussion for that and somebody apparently already submitted a patch.

What helps me for now is executing

echo on > /sys/bus/pci/devices/0000\:00\:19.0/power/control 

to bring the interface up.

Offline

#4 2013-03-19 21:06:29

Mantichore
Member
Registered: 2012-11-04
Posts: 19

Re: [solved] e1000e: Ethernet Port not seeing any carriers

Same problem here. Wrote an udev rule which sets this automatically:

SUBSYSTEM=="pci", ATTR{vendor}=="0x8086", ATTR{subsystem_device}=="0x21f3", ATTR{device}=="0x1502" ATTR{power/control}="on"

Offline

#5 2013-04-05 13:58:01

dmoebius
Member
Registered: 2013-04-05
Posts: 6

Re: [solved] e1000e: Ethernet Port not seeing any carriers

Thanks a thousand times!!
I got exactly the same problem with kernel 3.8.4-1 or 3.8.5-1 and Dell Latitude E6430.

The udev rule solved the problem for me, but I had to change the subsystem_device id to 0x0534 (got this from 'lspci -vn').

Offline

#6 2013-05-08 12:24:27

shuaiming
Member
From: HangZhou
Registered: 2013-03-27
Posts: 1

Re: [solved] e1000e: Ethernet Port not seeing any carriers

Thanks a billion, I've got exactly this problem too. I had to reboot laptop every time when pluging and unpluging  cable.

[ice@ice-thinker bin]$ ls /sys/class/net/ -l
total 0
lrwxrwxrwx 1 root root 0 May  8 20:10 enp0s25 -> ../../devices/pci0000:00/0000:00:19.0/net/enp0s25
lrwxrwxrwx 1 root root 0 May  8 19:55 lo -> ../../devices/virtual/net/lo
lrwxrwxrwx 1 root root 0 May  8 19:55 wlp2s0 -> ../../devices/pci0000:00/0000:00:1c.4/0000:02:00.0/net/wlp2s0


echo on > /sys/bus/pci/devices/0000\:00\:19.0/power/control

this way can bring me network back.

reloading e1000e kernel module dose not work for me.

Last edited by shuaiming (2013-05-08 12:34:04)

Offline

Board footer

Powered by FluxBB