Bug 248997
Summary: | iwl3945 does not work with testing kernel-2.6.22.1-27.fc7 | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Reindl Harald <spam2> |
Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 7 | CC: | chemobejk, frank.duignan, guido.ledermann, kjh, matthias, walters |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | 2.6.22.1-27.fc7 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2007-07-20 13:57:41 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Reindl Harald
2007-07-20 08:31:10 UTC
Problem seems to be "iwlwifi-firmware.noarch 2.14.3-2" With iwlwifi-firmware.noarch 2.14.4-1 from testing it works with 2.6.22, but this firmware kills iwl3945 unter 2.6.21 iwl3945 is generally strange, if it connects while booting - all works perfect, if you lost your connection a rmmod/modprobe and restart auf wpa_supplicant in many cases will not bring back connection :-( Yes, the firmware update is required for the later version of the driver. It will be pushed at the same time as the updated kernel. There are many open issues regarding iwl3945. Perhaps the 'lost connection' problem you report matches one of those? If not, feel free to open a new bug to cover that. *** Bug 249131 has been marked as a duplicate of this bug. *** *** Bug 249123 has been marked as a duplicate of this bug. *** I see that kernel-2.6.22.1-27.fc7 has been pushed to stable, but the firmware hadn't been :-( I've just asked to have that done through bodhi now. Mhh and it makes me angry Does the last time no one think before publishing kernels the last 2.6.21 with dependecies on new mkinitrd was published while mkinitrd was hanging in "updates-testing" This should not happen often because normal users have big troubles with such actions! *** Bug 249170 has been marked as a duplicate of this bug. *** *** Bug 249331 has been marked as a duplicate of this bug. *** *** Bug 249386 has been marked as a duplicate of this bug. *** |