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

Bug#780631: marked as done (e1000e: Intel I217-V non-functional after booting Windows)

Your message dated Sat, 08 May 2021 08:44:51 -0700 (PDT)
with message-id <6096b1f3.1c69fb81.11883.eba5@mx.google.com>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #780631,
regarding e1000e: Intel I217-V non-functional after booting Windows
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
780631: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=780631
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-image-3.16.0-4-amd64
Version: 3.16.7-ckt7-1

After booting Windows, the I217-V Ethernet interface no longer works
properly. DHCP fails. If a static IP address is assigned, ping fails.
It looks as if the interface is transmitting data, but not
successfully receiving anything.

I'm running Debian Testing (Jessie), and Windows 7, on an Asus H87I-PLUS.

Fortunately for me, I'm not the first person to discover this bug.

https://bbs.archlinux.org/viewtopic.php?id=191981

The workaround suggested at the above link solved my problem: in the
Intel driver properties on Windows, go to the "Power Management" tab,
and uncheck all options related to Wake-on-LAN. Note that a minimal
install of the Intel network driver on Windows seems to be
insufficient. I needed the Intel-logo'd property pages to gain access
to all relevant options.

I just tested with linux-image-3.19.0-trunk-amd64 version
3.19.1-1~exp1, and got the same result.

Let me know how I can help. Thanks.

-- graham

--- End Message ---
--- Begin Message --- 
Hi

This bug was filed for a very old kernel or the bug is old itself
without resolution.

If you can reproduce it with

- the current version in unstable/testing
- the latest kernel from backports

please reopen the bug, see https://www.debian.org/Bugs/server-control
for details.

Regards,
Salvatore

--- End Message ---
Reply to: