jaunty: b43 not able to link an access point with BCM4306
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
on fresh jaunty upgrade (from hardy): linux-image-
firmware have been correrctly installed:
$ ls /lib/firmware/b43
a0g0bsinitvals4.fw a0g1initvals5.fw lp0bsinitvals13.fw pcm5.fw
a0g0bsinitvals5.fw a0g1initvals9.fw lp0bsinitvals14.fw ucode11.fw
a0g0bsinitvals9.fw b0g0bsinitvals13.fw lp0bsinitvals15.fw ucode13.fw
a0g0initvals4.fw b0g0bsinitvals4.fw lp0initvals13.fw ucode14.fw
a0g0initvals5.fw b0g0bsinitvals5.fw lp0initvals14.fw ucode15.fw
a0g0initvals9.fw b0g0bsinitvals9.fw lp0initvals15.fw ucode4.fw
a0g1bsinitvals13.fw b0g0initvals13.fw n0absinitvals11.fw ucode5.fw
a0g1bsinitvals5.fw b0g0initvals4.fw n0bsinitvals11.fw ucode9.fw
a0g1bsinitvals9.fw b0g0initvals5.fw n0initvals11.fw
a0g1initvals13.fw b0g0initvals9.fw pcm4.fw
dmesg tells:
$ dmesg|grep b43
[ 4.035264] b43-pci-bridge 0000:02:02.0: PCI INT A -> Link[LNK3] -> GSI 17 (level, low) -> IRQ 17
[ 20.026166] b43-phy0: Broadcom 4306 WLAN found
[ 30.406696] input: b43-phy0 as /devices/
[ 30.436053] b43 ssb0:0: firmware: requesting b43/ucode5.fw
[ 30.509742] b43 ssb0:0: firmware: requesting b43/pcm5.fw
[ 30.515922] b43 ssb0:0: firmware: requesting b43/b0g0initval
[ 30.534225] b43 ssb0:0: firmware: requesting b43/b0g0bsinitv
[ 30.656054] b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10)
[ 30.717720] Registered led device: b43-phy0::tx
[ 30.717740] Registered led device: b43-phy0::rx
[ 30.717759] Registered led device: b43-phy0::radio
[ 30.732050] b43-phy0: Radio turned on by software
All seem OK as for hardy heron, but iwconfig cannot access my AP:
$ iwconfig wlan0
wlan0 IEEE 802.11bg ESSID:"sxxxxxo"
Retry min limit:7 RTS thr:off Fragment thr=2352 B
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
This used to work at rate 1MB with b43 on Hardy, but now i can see b43 cannot acces the only access point of my ESSID (distant of 2 meters).
b43legacy seems to not recognize my chip at all.
affects: | ubuntu → linux (Ubuntu) |
Hi ben,
This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http:// cdimage. ubuntu. com/releases/ .
If it remains an issue, could you run the following command from a Terminal (Applications- >Accessories- >Terminal) . It will automatically gather and attach updated debug information to this report.
apport-collect -p linux 391020
Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https:/ /wiki.ubuntu. com/KernelMainl ineBuilds . Once you've tested the upstream kernel, please remove the 'needs- upstream- testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs- upstream- testing' text. Please let us know your results.
Thanks in advance.
[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]