Intel WiMAX/WiFi Link 6050 series wireless does not work
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux-backports-modules-2.6.32 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Lucid |
Fix Released
|
Wishlist
|
Chase Douglas | ||
Maverick |
Invalid
|
Undecided
|
Unassigned | ||
linux-firmware (Ubuntu) |
Fix Released
|
High
|
Chase Douglas | ||
Lucid |
Won't Fix
|
Undecided
|
Unassigned | ||
Maverick |
Fix Released
|
High
|
Chase Douglas |
Bug Description
SRU Justification for Lucid for linux-backports
The change merely adds the 6050 iwlwifi firmware to the package. The drivers already in the package should be sufficient to utilize the firmware correctly. There is no regression potential because the file did not exist before.
=====
Wireless Controller: Intel WiMAX/WiFi Link 6050 series (Kernel module iwlagn.ko)
Intel wireless controller can be detected, driver is loaded, but clicking network manager shows no access point. Our office has at least 2 APs as I can see them using other systems. Installing linux-backports
Steps to Reproduce:
1. Boot the system
2. Click network manager
3. Look for available AP for wireless connection
Expected result:
Available APs are listed, select the best one to make connection.
Actual result:
No AP can be seen.
Credit:
I cribbed most of this bug description from bug #496496.
Related branches
tags: | added: kernel-series-unknown |
Changed in linux-firmware (Ubuntu): | |
importance: | Undecided → High |
status: | New → Triaged |
assignee: | nobody → Chase Douglas (chasedouglas) |
Changed in linux-backports-modules-2.6.32 (Ubuntu Maverick): | |
status: | New → Invalid |
Changed in linux-backports-modules-2.6.32 (Ubuntu Lucid): | |
importance: | Undecided → Wishlist |
status: | New → Triaged |
assignee: | nobody → Chase Douglas (chasedouglas) |
Changed in linux-backports-modules-2.6.32 (Ubuntu Lucid): | |
status: | Triaged → In Progress |
description: | updated |
tags: |
added: verification-done removed: verification-needed |
I can't seem to link this bug to Karmic, but that's the Ubuntu release I'm running.