Broadcom bcm43xx broken with 2.6.20.8 kernel
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
bcm43xx-fwcutter (Ubuntu) |
Invalid
|
Medium
|
Unassigned | ||
linux (Ubuntu) |
Incomplete
|
Undecided
|
Unassigned | ||
linux-source-2.6.20 (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: bcm43xx-fwcutter
Switched from Edgy to Feisty at Herd 3. All went well. Apply a slew of updates every few days, mostly with no trouble.
The last kernel update from 2.6.20.6 -> 2.6.20.8 breaks my wireless card though. Booting on 2.6.20.6 fixes the problem.
Just from watching the boot progress, it's clear that there's a problem with bcm43xx-fwcutter. During boot, it complains that the firmware in my wireless card is too old and must be upgraded. This seems a bit fishy since this problem is brought on by switching kernels, not from an upgrade in bcm43xx-fwcutter.
If this problem doesn't get fixed automatically in the next few days/weeks of patches, I'll see if I can gather some more specifics to attach to this issue. At this point, hoping it's just something trivial, and that I don't actually have to upgrade my firmware.
ProblemType: Bug
Date: Wed Feb 14 14:34:54 2007
DistroRelease: Ubuntu 7.04
Uname: Linux zd7000 2.6.20-6-386 #2 Wed Jan 31 20:48:57 UTC 2007 i686 GNU/Linux
Changed in bcm43xx-fwcutter: | |
importance: | Undecided → Medium |
Changed in linux-source-2.6.20: | |
status: | Unconfirmed → Confirmed |
Changed in bcm43xx-fwcutter: | |
status: | Rejected → Confirmed |
yup this happens to me as well, i did actually attempt to cut some firmware out that was >4.x but bcm43xx-fwcutter rejected the .sys files i tried. Why does the kernel update demand that seeing as there are no easily available 4.x series firmware files out there to play with. since we cant get the new firmware to extract and the old firmware doesnt work until this is fixed i wager to say most bcm43xx driver users will be SOL unless like me thay have a wired connection.