| Summary: | Intel wifi does not connect on boot after update to 4.4.16 kernel | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Thomas Andrews <andrewsfarm> |
| Component: | RPM Packages | Assignee: | Kernel and Drivers maintainers <kernel> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | major | ||
| Priority: | release_blocker | CC: | tmb |
| Version: | 5 | ||
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | CVE: | ||
| Status comment: | |||
| Attachments: |
ifconfig and dmsg for 3.x kernel boot
ifconfig and dmesg for 4.4 kernel boot |
||
|
Description
Thomas Andrews
2016-09-17 04:11:38 CEST
Created attachment 8419 [details]
ifconfig and dmsg for 3.x kernel boot
Created attachment 8420 [details]
ifconfig and dmesg for 4.4 kernel boot
I really don't know what I'm looking at here, but it appears that it is just taking too long before finally loading the correct firmware. A possible workaround might be to remove the Mageia iwlwifi package, which appears to contain several sets of firmware, and install the proper firmware for my chip manually. Of course, that doesn't help to get the Mageia package working as it should. Removing Mageia's iwlwifi package and replacing it with iwlwifi-6000-4 that it is supposed to be using (that I realize is contained in Mageia's iwlwifi) made no difference. Labeling this a release blocker, as I believe it should be fixed before the release of Mageia 5.1. While I have not yet tried the 5.1 isos on this computer, I have been informed that there would be no difference between those and a fully-updated Mageia 5 installation. Priority:
Normal =>
release_blocker Assigning to kernel maintainers. This is a potential blocker for Mageia 5.1 so please consider it a very high priority bug. CC:
(none) =>
drivers My bad... fix coming in 4.4.21-2 CC:
(none) =>
tmb (In reply to Thomas Backlund from comment #6) > My bad... fix coming in 4.4.21-2 Eagerly anticipating... The current situation is quite annoying. Updating to 4.4.21-2 and associated firmware packages does appear to fix the problem. As far as I'm concerned, this bug is resolved and fixed. I don't know if confirmation from another source is needed before marking it as such.
Samuel Verschelde
2016-09-21 10:19:16 CEST
CC:
drivers =>
(none) 4.4.22-1 pushed. same fix went into cauldron kernel-4.7.5-1.mga6 Status:
NEW =>
RESOLVED |