Bug 249526 - LostIntel PRO/Wireless 3945 wireless adaptor after recent yum update
Summary: LostIntel PRO/Wireless 3945 wireless adaptor after recent yum update
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: iwlwifi-firmware   
(Show other bugs)
Version: 7
Hardware: i686
OS: Linux
low
urgent
Target Milestone: ---
Assignee: Matthias Saou
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-07-25 12:26 UTC by Edmond Hui
Modified: 2007-11-30 22:12 UTC (History)
1 user (show)

Fixed In Version: upgraded kernel 2.6.22
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2007-07-29 13:03:44 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description Edmond Hui 2007-07-25 12:26:16 UTC
Description of problem:
After a yum update a day ago, the Intel Pro wireless 3945 wireless card
disappeared from network manager, rendering no wireless function at all. Smolt
still reporting it but that's all. 

The hardware is a Thinkpad T60 see
http://smolt.fedoraproject.org/show?UUID=eac88a4e-757b-4343-b375-4220dfac422e

Also found that in system-config-network that the wireless connection is unable
to change (OK button disabled) and wlan device renamed to wlan0.bak

Noticed recently iwlwifi and network manager were updated.

Version-Release number of selected component (if applicable):
NetworkManager-gnome-0.6.5-7.fc7
iwlwifi-firmware-2.14.4-1
kernel-2.6.21-1.3228.fc7

How reproducible:
unknown... currently struck with all latest

Steps to Reproduce:
1. yum update to latest
2.
3.
  
Actual results:
wireless service lost

Expected results:
no impact to network manager and wireless service

Additional info:

Comment 1 Edmond Hui 2007-07-28 15:36:45 UTC
The problem is corrected after upgraded to kernel-2.6.22.1-33


Note You need to log in before you can comment on or make changes to this bug.