Is it possible that the firmware file your card needs is not in your Linux distribution? Upgrading kernel does not give you firmware file. Usually, if this is the case, you may see some error log in "dmesg" Just through a possibility, I don't have broadcom radios. But this scenario happened to me for my Intel "Ultimate N 6300" -----Original Message----- From: linux-wireless-owner@xxxxxxxxxxxxxxx [mailto:linux-wireless-owner@xxxxxxxxxxxxxxx] On Behalf Of Chen, Xianwen Sent: Thursday, March 10, 2011 6:04 PM To: linux-wireless@xxxxxxxxxxxxxxx Subject: Re: Status of Broadcom 4353? Thanks a lot guys! I tried both latest stable kernel (linux-2.6.37) and latest mainline kernel (linux-2.6.38-rc8) with CONFIG_BRCM80211=y CONFIG_BRCM80211_PCI=y . No wlan0 turns up yet. Any more hint please? Xianwen On Thu, Mar 10, 2011 at 8:14 PM, Brett Rudley <brudley@xxxxxxxxxxxx> wrote: > Its not intuitive, but 0x4353 is the PCI device ID of the 43224 dual band card which does run under brcm80211. > > Regards > Brett On Thu, Mar 10, 2011 at 7:54 PM, Larry Finger <Larry.Finger@xxxxxxxxxxxx> wrote: > There are two ways that Broadcom chips are connected to a PCIe interface - > one uses the SSB interconnect, and the other does not. In b43, only chips > with SSB are supported. As the 4353 device does not use SSB, b43 does not > work with it. Whether it ever will is being discussed. > > You should use either the brcm80211 driver from compat-wireless or kernels > 2.6.37, or later. You may also use the wl driver from Broadcom if you are > willing to run closed-source software. That driver does not use mac80211. > > Larry -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
