b43 problem.

[Waleed Harbi]

Omri,

If you cannot access to the access point or cannot see it, try update the
kernel "yum update kernel*" , then install these two packages broadcom-wl
kmod-wl.

This is useful link:
http://www.fedoraguide.info/index.php?title=Fedora10#Broadcom_b43_.28Official_driver.21.21.21.29

I hope that help you.

Best Regards,
Waleed Harbi
Success is the sum of small efforts, repeated day in and day out.



On Sun, Jul 26, 2009 at 11:23 PM, Omri Schwarz <ocschwar at mit.edu> wrote:

> Hi, all. I'm running FC 10 on a Lenovo 3000 C100 laptop
> with a Broadcomm 4318 wireless driver. A problem developed today
> that shows as follows in dmesg:
>
> fuse init (API version 7.9)
> wlan0: authenticate with AP 00:1f:33:c7:2d:c6
> wlan0: authenticated
> wlan0: associate with AP 00:1f:33:c7:2d:c6
> wlan0: RX AssocResp from 00:1f:33:c7:2d:c6 (capab=0x421 status=0 aid=3)
> wlan0: associated
> ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
> b43-phy0 debug: Removing Interface type 2
> b43-phy0 debug: Wireless interface stopped
> b43-phy0 debug: DMA-32 rx_ring: Used slots 1/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 2/128, Failed frames 0/5 =
> 0.0%, Average tries 1.20
> 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 2/128, Failed frames 0/2 =
> 0.0%, Average tries 1.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/input11
> b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10)
> b43-phy0 debug: Chip initialized
> b43-phy0 debug: 32-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
> ADDRCONF(NETDEV_UP): wlan0: link is not ready
>
> This happens when I try to bring the interface up first time after booting.
>
> That is, it finds the local network, associates with the
> access point, and tries DHCP, and then instantly drops out.
>
> I'm wondering if it's the chip dying, since Google doesn't show any other
> cases like this.
>
> So, anyhow, here are the kernel details:
>
> Linux localhost.localdomain 2.6.27.25-170.2.72.fc10.i686 #1 SMP Sun Jun 21
> 19:03:24 EDT 2009 i686 i686 i386 GNU/Linux
>
> Anyone seen anything like this? Thanks for your attention.
>
>
> Omri Schwarz --- ocschwar at mit.edu
> Timeless wisdom of biomedical engineering: "Noise is principally
> due to the presence of the patient." -- R.F. Farr
>
> --
> fedora-list mailing list
> fedora-list at redhat.com
> To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
> Guidelines:
> http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/fedora-list/attachments/20090727/c37481f1/attachment-0001.htm>