glenn greenfield wrote:
> Debian Sid 64 bit
> AMD64 X2
> Kernel 2.6.24-smp w/ 4311_2 patch applied from here:
> http://linuxwireless.org/download/b43/patch_2.6.24_for_4311_2
> 
> lspci
> 03:00.0 Network controller: Broadcom Corporation BCM94311MCG wlan
> mini-PCI (rev 02)
> _______________________________________________________
> My kernel configuration:
> 
> # zcat /proc/config.gz |grep B43
> CONFIG_B43=m
> CONFIG_B43_PCI_AUTOSELECT=y
> CONFIG_B43_PCICORE_AUTOSELECT=y
> CONFIG_B43_LEDS=y
> CONFIG_B43_RFKILL=y
> CONFIG_B43_DEBUG=y
> CONFIG_B43_DMA=y
> CONFIG_B43_PIO=y
> CONFIG_B43_DMA_AND_PIO_MODE=y
> # CONFIG_B43_DMA_MODE is not set
> # CONFIG_B43_PIO_MODE is not set
> CONFIG_B43LEGACY=m
> CONFIG_B43LEGACY_PCI_AUTOSELECT=y
> CONFIG_B43LEGACY_PCICORE_AUTOSELECT=y
> CONFIG_B43LEGACY_LEDS=y
> CONFIG_B43LEGACY_RFKILL=y
> CONFIG_B43LEGACY_DEBUG=y
> CONFIG_B43LEGACY_DMA=y
> CONFIG_B43LEGACY_PIO=y
> CONFIG_B43LEGACY_DMA_AND_PIO_MODE=y
> # CONFIG_B43LEGACY_DMA_MODE is not set
> # CONFIG_B43LEGACY_PIO_MODE is not set
> 
> I have completely disabled BCM43xx
> 
> # zcat /proc/config.gz |grep BCM43
> # CONFIG_BCM43XX is not set
> ________________________________________________________
> # lsmod|grep b43
> b43                   161840  0
> rfkill                  9680  3 rfkill_input,b43
> mac80211              143948  1 b43
> led_class               6664  1 b43
> input_polldev           6352  1 b43
> ________________________________________________________
> 
> dmesg|grep b43
> b43-phy0: Broadcom 4311 WLAN found
> b43-phy0 debug: Found PHY: Analog 4, Type 2, Revision 9
> b43-phy0 debug: Found Radio: Manuf 0x17F, Version 0x2050, Revision 2
> input: b43-phy0 as /devices/virtual/input/input9
> b43-phy0 debug: Loading firmware version 351.126 (2006-07-29 05:54:02)
> b43-phy0 debug: Chip initialized
> b43-phy0 debug: 64-bit DMA initialized
> Registered led device: b43-phy0:tx
> Registered led device: b43-phy0:rx
> Registered led device: b43-phy0:radio
> b43-phy0 ERROR: PHY transmission error
> 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-64 0x0200 (RX) max used slots: 1/64
> b43-phy0 debug: DMA-64 0x0340 (TX) max used slots: 0/128
> b43-phy0 debug: DMA-64 0x0300 (TX) max used slots: 0/128
> b43-phy0 debug: DMA-64 0x02C0 (TX) max used slots: 0/128
> b43-phy0 debug: DMA-64 0x0280 (TX) max used slots: 0/128
> b43-phy0 debug: DMA-64 0x0240 (TX) max used slots: 2/128
> b43-phy0 debug: DMA-64 0x0200 (TX) max used slots: 0/128
> input: b43-phy0 as /devices/virtual/input/input10
> b43-phy0 debug: Loading firmware version 351.126 (2006-07-29 05:54:02)
> b43-phy0 debug: Chip initialized
> b43-phy0 debug: 64-bit DMA initialized
> Registered led device: b43-phy0:tx
> Registered led device: b43-phy0:rx
> Registered led device: b43-phy0:radio
> b43-phy0 debug: Wireless interface started
> b43-phy0 debug: Adding Interface type 2
> 
> The device configures and comes up no problem.
> I can even obtain an i.p. via DHCP however the connection only stays
> up for a matter of seconds until I get this error:
> 
> b43-phy0 ERROR: PHY transmission error
> 
> at which point the device is useless and cannot be made to connect
> again until after a reboot.
> Currently I do use WPA however I've even tried disabling encryption
> entirely but the problem persists.
> 
> I'm not sure what to try at this point.  If you'd like further info
> from my system just say so and I'll be glad to post it.

Do you get more than one PHY transmission error? With the BCM4311/2, you will 
get one every time the
interface is brought up. We don't know why, but it is not critical. I use that 
interface with WPA
and have no troubles.

Please send the appropriate section of /var/log/messages starting with the 
firmware version message,
and continuing through to after it has disconnected.

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

Reply via email to