Intel NIC (e1000e) problem after booting Windows

feelus · 2014-11-09 12:59:44

I have the Asus Maximus Hero VI Motherboard with Intel I217-V Chipset and i'm experiencing problems with network. I found a similar problem here https://bbs.archlinux.org/viewtopic.php?id=189138 but it was solved by buying new NIC.

When I do cold boot straight into Arch, my network works just fine. I'm using static configuration (i'm sure noone else is using my IP).
Problem occurs when I reboot from Windows into Arch then I'm unable to access any network devices. When I ping my router i get Destination Host Unreachable. If I keep ping running and suspend my computer and then resume, I get 1 response from ping and then again unreachable so it might have something to do with power saving features. Network from windows works fine.

I have installed either latest WHQL or Intel network driver in Windows, I'm currently not sure which one but I can check later.
I have tried rmmod e1000e and modprobe e1000e but no luck. I have also downloaded and compiled latest version of e1000e driver from Intel.

Summary

after cold boot network works (completly unplugged from power, not just turn off computer from OS)
after using windows then rebooting network doesnt work
got Intel Intel I217-V chipset NIC, using latest e1000e driver from Intel
i get 1 ping response from network after resuming computer from sleep
tried using DHCP and static configuration

If anyone could point me into direction where the problem might be i would be thankful.

dmesg

[root@martin-pc-arch martin]# dmesg | grep e1000e
[ 2.028878] e1000e: Intel(R) PRO/1000 Network Driver - 3.1.0.2-NAPI
[ 2.028879] e1000e: Copyright(c) 1999 - 2014 Intel Corporation.
[ 2.030553] e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
[ 2.030566] e1000e 0000:00:19.0: irq 29 for MSI/MSI-X
[ 2.207491] e1000e 0000:00:19.0 eth0: registered PHC clock
[ 2.207493] e1000e 0000:00:19.0 eth0: (PCI Express:2.5GT/s:Width x1) 74:d0:2b:7e:17:9f
[ 2.207495] e1000e 0000:00:19.0 eth0: Intel(R) PRO/1000 Network Connection
[ 2.207520] e1000e 0000:00:19.0 eth0: MAC: 11, PHY: 12, PBA No: FFFFFF-0FF
[ 2.210035] e1000e 0000:00:19.0 eno1: renamed from eth0
[ 2.372364] e1000e 0000:00:19.0: irq 29 for MSI/MSI-X
[ 2.474280] e1000e 0000:00:19.0: irq 29 for MSI/MSI-X
[ 5.303710] e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx

ip a

[root@martin-pc-arch martin]# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
3: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 74:d0:2b:7e:17:9f brd ff:ff:ff:ff:ff:ff
inet 192.168.5.7/24 brd 192.168.5.255 scope link eno1
valid_lft forever preferred_lft forever
inet6 fe80::76d0:2bff:fe7e:179f/64 scope link
valid_lft forever preferred_lft forever

lspci -vvv

[root@martin-pc-arch martin]# lspci -vvv
...
00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I217-V (rev 04)
Subsystem: ASUSTeK Computer Inc. Device 859f
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 29
Region 0: Memory at f6200000 (32-bit, non-prefetchable) [size=128K]
Region 1: Memory at f6239000 (32-bit, non-prefetchable) [size=4K]
Region 2: I/O ports at f040 [size=32]
Capabilities: [c8] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=1 PME-
Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Address: 00000000fee0f00c Data: 41c2
Capabilities: [e0] PCI Advanced Features
AFCap: TP+ FLR+
AFCtrl: FLR-
AFStatus: TP-
Kernel driver in use: e1000e
Kernel modules: e1000e
...

modinfo e1000e

[root@martin-pc-arch martin]# modinfo e1000e | grep version
version: 3.1.0.2-NAPI
srcversion: 58C4B047D24A6394B168B0F
vermagic: 3.17.2-1-ARCH SMP preempt mod_unload modversions

lsmod | grep e1000e

[root@martin-pc-arch martin]# lsmod | grep e1000e
e1000e 244559 0
ptp 17692 1 e1000e

cat /proc/interrupts

[root@martin-pc-arch martin]# cat /proc/interrupts
...
29: 698 14 17 15 PCI-MSI-edge eno1
...

Last edited by feelus (2014-11-09 13:26:39)

Untribium · 2015-01-07 19:51:05

Hi feelus,

I was having the same issue and had no idea it might be related to Windows :)
In my case, unpowering the PC for a few seconds before booting Linux works, but this isn't really a solution...I have "documented my findings" here in case you're interested

feelus · 2015-01-07 20:05:06

Untribium wrote:

Hi feelus,
I was having the same issue and had no idea it might be related to Windows
In my case, unpowering the PC for a few seconds before booting Linux works, but this isn't really a solution...I have "documented my findings" here in case you're interested

Thanks for the reply and link. Yeah, unfortunately i haven't found a solution to this yet either. I think it might be something like a power saving feature, but I'm not really sure. Currently using same method as you, so in case i need to boot Linux after Windows, i just unplug my computer for a while, but hoping for a better and less annoying solution

Slithery · 2015-01-07 20:30:56

Are you sure this has anything to do with Windows and isn't just caused by rebooting?

What happens when you reboot from Arch?

Untribium · 2015-01-07 21:44:13

Rebooting from Arch works just fine, so I'm pretty much 100% sure it's related to Windows and how the Ethernet chip (and/or the mainboard) handles the different operating systems

Arch Linux

#1 2014-11-09 12:59:44

Intel NIC (e1000e) problem after booting Windows

#2 2015-01-07 19:51:05

Re: Intel NIC (e1000e) problem after booting Windows

#3 2015-01-07 20:05:06

Re: Intel NIC (e1000e) problem after booting Windows

#4 2015-01-07 20:30:56

Re: Intel NIC (e1000e) problem after booting Windows

#5 2015-01-07 21:44:13

Re: Intel NIC (e1000e) problem after booting Windows

Board footer