Bug 16196

Summary:	Intel I217-LM Ethernet adapter unusable because of Windows power saving options
Product:	Mageia	Reporter:	Davy Defaud <davy.defaud>
Component:	RPM Packages	Assignee:	Kernel and Drivers maintainers <kernel>
Status:	RESOLVED OLD	QA Contact:
Severity:	critical
Priority:	Normal	CC:	marja11, tmb
Version:	5
Target Milestone:	---
Hardware:	All
OS:	Linux
URL:	https://bbs.archlinux.org/viewtopic.php?id=191981
Whiteboard:
Source RPM:	kernel-3.19.8-3.mga5.src.rpm	CVE:
Status comment:

Description Davy Defaud 2015-06-24 12:40:34 CEST

Description of problem:
Intel I217-LM Ethernet adapter becomes unusable after booting Windows, because of the power saving options that Windows is setting. Problem and solution are described in this ArchLinux thead:
 https://bbs.archlinux.org/viewtopic.php?id=191981

The only solution seems to be booting Windows to disable all the power saving options of the network adapter.

The Linux network driver is e1000e. I've not seen any fix at that time.

Steps to Reproduce:

This bug happened on a brand new Dell Precision T1700 first booted on Windows.
A collegue of mine, with the same box has not been hit by the bug because he has installed Mageia without booting Windows.


Reproducible: 

Steps to Reproduce:

Davy Defaud 2015-06-24 15:46:05 CEST

Assignee: bugsquad => tmb

Thierry Vignaud 2015-07-31 09:57:48 CEST

CC: (none) => tmb

Comment 1 Marja Van Waes 2016-08-26 11:43:14 CEST

Mass-reassigning all bugs with "kernel" in the Source RPM field that are assigned to tmb, to the kernel packagers group, because tmb is currently MIA.

Assignee: tmb => kernel

Comment 2 Marja Van Waes 2018-04-28 21:55:16 CEST

Hi Davy,

Thank you for having taken the needed time to report this issue!

Did this bug get fixed? If so, please change its status to RESOLVED - FIXED

If it didn't, then we regret that we weren't able to fix it in Mageia 5. Mageia 5 has officially reached its End of Life on December 31st, 2017 https://blog.mageia.org/en/2017/11/07/mageia-5-eol-postponed/
It only continued to get important security updates since then, because we are waiting for a big Plasma5 update in Mageia 6, that'll fix many of the Mageia 5 => 6 upgrade issues.

If you haven't seen that this bug got fixed, then please check whether this bug still exists in Mageia 6. If it does, then please change the Version (near the top, at the left) to "6". If you know it exists in Cauldron, then change Version to Cauldron. If you see it in both Cauldron and Mageia 6, then please set Version to Cauldron and add MGA6TOO on the Whiteboard.

Thanks,
Marja

CC: (none) => marja11

Comment 3 Davy Defaud 2018-05-25 15:13:32 CEST

Hi Marja,

Unfortunately, I can’t verify. :-/

In summer 2015, I configured VirtualBox to be able to run the installed Windows 7 as a virtual machine from within Mageia. So I was able to boot the Windows system on the hardward as well as run it as a VirtualBox VM in Mageia. That was nice.

I even upgraded the system to Windows 10. But honestly, I rarely use it.

When I saw your post asking me to check if the bug still exists, I rebooted my computer to boot the Windows, something I haven’t done for more than 1 year. And I got a Windows 10 style BSOD. So, I’m not able to change the Windows WOL options to check if the bug still exists. I’m sorry!

Regards,

Davy

P.-S. : I asked a colleague of mine with the same configuration to boot on Windows, and the result was the same BSOD.

Comment 4 Marja Van Waes 2018-10-07 16:46:23 CEST

(In reply to Davy Defaud from comment #3)
> Hi Marja,
> 
> Unfortunately, I can’t verify. :-/
> 
 <snip>

Thanks for answering!

It is no problem. I'll just close this bug report as OLD, then, because Mageia 5 is no longer maintained.

Resolution: (none) => OLD
Status: NEW => RESOLVED