Skip to contentSkip to conversation

b43: Everybody with PHY TX error, please try

DISCUSSION Michael Buesch 6 participants 7 messages Oct 24, 2008 – Nov 6, 2008

lore
Share & tools
lore
#0 lore raw

Everybody with PHY TX error, please try updated firmware from ftp://ftp.linksys.com/opensourcecode/wrt610n/1.00.00.018/wrt610n_v1.00.00.018_us.tgz (Yeah, big tarball. It's 87MB)

Extract the file wrt610n_v1.00.00.018_us/release/src/wl/linux/wl.o out of the archive. Get latest b43-tools:
git clone http://git.bu3sch.de/git/b43-tools.git

Build and install fwcutter from latest b43-tools.git

Extract the firmware from the wl.o file:
b43-fwcutter --unsupported -w /lib/firmware/DESTPATH wl.o

Try to reproduce the PHY TX error with the new firmware.

Thanks.

Signature · 1 line
Greetings Michael.
#1 lore raw

Hi!

I've tried the new firmware. There are still PHY TX errors with my BCM4318.

2008/10/24, Michael Buesch <[email protected]>:

Quoted 25 lines

Everybody with PHY TX error, please try updated firmware from
ftp://ftp.linksys.com/opensourcecode/wrt610n/1.00.00.018/wrt610n_v1.00.00.018_us.tgz (Yeah, big tarball. It's 87MB)

Extract the file wrt610n_v1.00.00.018_us/release/src/wl/linux/wl.o out of the archive. Get latest b43-tools:
git clone http://git.bu3sch.de/git/b43-tools.git

Build and install fwcutter from latest b43-tools.git

Extract the firmware from the wl.o file:
b43-fwcutter --unsupported -w /lib/firmware/DESTPATH wl.o

Try to reproduce the PHY TX error with the new firmware.

Thanks.

--
Greetings Michael.
_______________________________________________
Bcm43xx-dev mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev

#2 lore raw
In reply to Michael Buesch

Hi,

Quoted 3 lines · Michael Buesch

Everybody with PHY TX error, please try updated firmware from ftp://ftp.linksys.com/opensourcecode/wrt610n/1.00.00.018/wrt610n_v1.00.00.018_us.tgz (Yeah, big tarball. It's 87MB)

Sorry, I'm arriving to this late. I'm seeing the following:

[30447.008408] __ratelimit: 2795 callbacks suppressed
[30447.008466] b43-phy0 ERROR: PHY transmission error
[30447.008496] b43-phy0 ERROR: PHY transmission error
[30447.008523] b43-phy0 ERROR: PHY transmission error
[30447.008551] b43-phy0 ERROR: PHY transmission error
[30447.008577] b43-phy0 ERROR: PHY transmission error
[30447.008606] b43-phy0 ERROR: PHY transmission error
[30447.008634] b43-phy0 ERROR: PHY transmission error
[30447.008662] b43-phy0 ERROR: PHY transmission error
[30447.008690] b43-phy0 ERROR: PHY transmission error
[30447.384079] b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10)
[30447.500347] b43-pci-bridge 0000:02:00.0: PCI: Disallowing DAC for device
[30447.500376] b43-phy0: DMA mask fallback from 64-bit to 32-bit
[30447.526191] Registered led device: b43-phy0::tx
[30447.526960] Registered led device: b43-phy0::rx
[30447.527543] Registered led device: b43-phy0::radio
[30454.780114] wlan1: No ProbeResp from current AP 00:1e:2a:e4:de:84 - assume out of range
[30455.681012] wlan1: authenticate with AP 00:1e:2a:e4:de:84
[30455.682225] wlan1: authenticate with AP 00:1e:2a:e4:de:84
[30455.684847] wlan1: authenticated
[30455.684873] wlan1: associate with AP 00:1e:2a:e4:de:84
[30455.688707] wlan1: RX ReassocResp from 00:1e:2a:e4:de:84 (capab=0x411 status=0 aid=1)
[30455.688730] wlan1: associated

This happens repeatedly during file transfers. Everything is quite slow. You can see that the device was reset.

Will the firmware upgrade fix this? Must I be running the latest b43 driver to use the new firmware?

I'm on Ubuntu 8.10 with kernel version 2.6.27-7-generic.

Thanks,
Forest

Signature · 3 lines
Forest Bond
http://www.alittletooquiet.net
http://www.pytagsfs.org
#3 lore raw
In reply to Michael Buesch
Quoted 8 lines · Michael Buesch

Everybody with PHY TX error, please try updated firmware from ftp://ftp.linksys.com/opensourcecode/wrt610n/1.00.00.018/wrt610n_v1.00.00.018_us.tgz (Yeah, big tarball. It's 87MB)

Extract the file wrt610n_v1.00.00.018_us/release/src/wl/linux/wl.o out of the archive. Get latest b43-tools:
git clone http://git.bu3sch.de/git/b43-tools.git

Quoted 6 lines

Build and install fwcutter from latest b43-tools.git

Extract the firmware from the wl.o file:
b43-fwcutter --unsupported -w /lib/firmware/DESTPATH wl.o

Try to reproduce the PHY TX error with the new firmware.

Still getting them, OpenWRT Kamikaze trunk on a Linksys WRT54G

b43-phy0: Broadcom 5352 WLAN found
b43-phy0 debug: Found PHY: Analog 2, Type 2, Revision 7 b43-phy0 debug: Found Radio: Manuf 0x17F, Version 0x2050, Revision 2 b43-phy0 debug: DebugFS (CONFIG_DEBUG_FS) not enabled in kernel config
input: b43-phy0 as /devices/virtual/input/input0
b43-phy0: Loading firmware version 478.104 (2008-07-01 00:50:23) b43-phy0 debug: Chip initialized
b43-phy0 debug: 32-bit DMA initialized
Registered led device: b43-phy0::radio
b43-phy0 debug: Wireless interface started
b43-phy0 debug: Adding Interface type 2
b43-phy0 debug: Removing Interface type 2
b43-phy0 debug: Wireless interface stopped
b43-phy0 debug: DMA-32 rx_ring: Used slots 0/64, Failed frames 0/0 = 0.0%, Average tries 0.00
b43-phy0 debug: DMA-32 tx_ring_AC_BK: Used slots 0/128, Failed frames 0/0 = 0.0%, Average tries 0.00
b43-phy0 debug: DMA-32 tx_ring_AC_BE: Used slots 0/128, Failed frames 0/0 = 0.0%, Average tries 0.00
b43-phy0 debug: DMA-32 tx_ring_AC_VI: Used slots 0/128, Failed frames 0/0 = 0.0%, Average tries 0.00
b43-phy0 debug: DMA-32 tx_ring_AC_VO: Used slots 0/128, Failed frames 0/0 = 0.0%, Average tries 0.00
b43-phy0 debug: DMA-32 tx_ring_mcast: Used slots 0/128, Failed frames 0/0 = 0.0%, Average tries 0.00
input: b43-phy0 as /devices/virtual/input/input1
b43-phy0: Loading firmware version 478.104 (2008-07-01 00:50:23)

Bernhard

#4 lore raw
In reply to Michael Buesch
Quoted 1 line · Michael Buesch

Try to reproduce the PHY TX error with the new firmware.

This helped neither with the PHY TX errors nor with the RX errors where I'm getting invalid frames passed up from the firmware and run into a WARN_ON:

drivers/net/wireless/b43/xmit.c:49
(b43_plcp_get_bitrate_idx_cck)

johannes

#5 lore raw
In reply to Michael Buesch

T24gRnJpLCBPY3QgMjQsIDIwMDggYXQgNjozMiBQTSwgTWljaGFlbCBCdWVzY2ggPG1iQGJ1M3Nj aC5kZT4gd3JvdGU6Cj4gRXZlcnlib2R5IHdpdGggUEhZIFRYIGVycm9yLCBwbGVhc2UgdHJ5IHVw ZGF0ZWQgZmlybXdhcmUgZnJvbQo+IGZ0cDovL2Z0cC5saW5rc3lzLmNvbS9vcGVuc291cmNlY29k ZS93cnQ2MTBuLzEuMDAuMDAuMDE4L3dydDYxMG5fdjEuMDAuMDAuMDE4X3VzLnRnego+IChZZWFo LCBiaWcgdGFyYmFsbC4gSXQncyA4N01CKQo+Cj4gRXh0cmFjdCB0aGUgZmlsZSB3cnQ2MTBuX3Yx LjAwLjAwLjAxOF91cy9yZWxlYXNlL3NyYy93bC9saW51eC93bC5vIG91dCBvZiB0aGUgYXJjaGl2 ZS4KPiBHZXQgbGF0ZXN0IGI0My10b29sczoKPiBnaXQgY2xvbmUgaHR0cDovL2dpdC5idTNzY2gu ZGUvZ2l0L2I0My10b29scy5naXQKPgo+IEJ1aWxkIGFuZCBpbnN0YWxsIGZ3Y3V0dGVyIGZyb20g bGF0ZXN0IGI0My10b29scy5naXQKPgo+IEV4dHJhY3QgdGhlIGZpcm13YXJlIGZyb20gdGhlIHds Lm8gZmlsZToKPiBiNDMtZndjdXR0ZXIgLS11bnN1cHBvcnRlZCAtdyAvbGliL2Zpcm13YXJlL0RF U1RQQVRIICB3bC5vCj4KPiBUcnkgdG8gcmVwcm9kdWNlIHRoZSBQSFkgVFggZXJyb3Igd2l0aCB0 aGUgbmV3IGZpcm13YXJlLgoKSWYgdGhpcyB0YXJiYWxsIGlzIHNvIGxhcmdlIHRoZW4gbWF5YmUg ZG93bmxvYWRpbmcgbGF0ZXN0IHVidW50dQpyZXN0cmljdGVkIG1vZHVsZXMgd2lsbCBiZSBmYXN0 ZXIuCmh0dHA6Ly9wYWNrYWdlcy51YnVudHUuY29tL2ludHJlcGlkL2xpbnV4LXJlc3RyaWN0ZWQt bW9kdWxlcy0yLjYuMjctNy1nZW5lcmljCkFGQUlLIHRoaXMgcGFja2FnZSBjb250YWlucyB0aGUg cHJvcHJpZXRhcnkgQnJvYWRjb20gV0wgZHJpdmVyIHNvIHRoZQpsYXRlc3QgZmlybXdhcmUgbWln aHQgYmUgaW4gaXQgdG9vLgoKLS0gCiMjIFByemVteXPFgmF3IEt1bGN6eWNraSA+Pjw8IEF6cmFl bCBOaWdodHdhbGtlciAjIwojIGphYmJlcjogYXpyYWVsW25hXWphYnN0ZXIucGwgfCB0bGVuOiBh enJhZWwyOWEgIwojIyMgd3d3OiBodHRwOi8vcmVrc2lvLmZ0ai5hZ2guZWR1LnBsL35henJhZWwv ICMjIwo=

#6 lore raw
Quoted 10 lines · Przemek Kulczycki
Quoted 3 lines · Michael Buesch

Everybody with PHY TX error, please try updated firmware from ftp://ftp.linksys.com/opensourcecode/wrt610n/1.00.00.018/wrt610n_v1.00.00.018_us.tgz (Yeah, big tarball. It's 87MB)

If this tarball is so large then maybe downloading latest ubuntu restricted modules will be faster.
http://packages.ubuntu.com/intrepid/linux-restricted-modules-2.6.27-7-generic
AFAIK this package contains the proprietary Broadcom WL driver so the latest firmware might be in it too.

No, not at all.

johannes