Bcm43236 Drivers

Translation(s): English - Français

This page describes how to enable support for WiFi devices based on Broadcom BCM4301, BCM4306, BCM4311, BCM4312, BCM4318, BCM4321 and BCM4322 chips on Debian systems.

Support and Services. Customer Support Portal; Software Documentation; Support Documents and Downloads. Drivers download; drivers license; Bcm43236 Drivers For Mac ⚙⚙⚙ DOWNLOAD. Jul 3, 2014 — BCM43236 802.11abgn Wireless Adapter Bus 001 Device 001: ID Driver: e1000e State: connected Default: yes HW Address. TWFM-B001T is based on Broadcom BCM43236 solution. A “BCM43236 rev 2” is attached to USB. The unit has 3 buttons: 2 Back (Reset, Wireless), 1 Top (WPS “dome”) WLAN support of BCM43236: no full mac driver 16.880000 brcmfmac: brcmfusbfwdownload: unsupported chip 43236 rev 2. Broadcom BCM4324 Wireless LAN Driver for Windows 10 (64-bit), 8.1 (64-bit) - ThinkPad 10.

Contents

  1. Broadcom 43xx wireless devices
    1. Drivers
    2. Supported Devices

Identification

The PCI ID is not sufficient to determine the Broadcom chip within.

The relevant driver has built-in logic to probe the actual chip, for example:

Refer to http://wireless.kernel.org/en/users/Drivers/b43#Supported_devices for more information.

Drivers

There are multiple drivers supporting Broadcom wireless LAN chips.

Linux kernel drivers:

  • b43 (supported devices)

    • Introduced in Linux 2.6.24.
    • Supports BCM4321 and BCM4322 as of Linux 2.6.38.
  • b43legacy (supported devices)

    • For 802.11b-only devices and the BCM4306 revision 2.
    • Introduced in Linux 2.6.24.
  • brcmsmac (supported devices)

    • Introduced in Linux 2.6.37, included in Debian Linux 2.6.32 kernel images.
    • Supports BCM4313, BCM43224 and BCM43225.
  • rndis_wlan (supported devices)

    • Introduced in Linux 2.6.25.
    • Supports BCM4320 USB devices.
  • brcmfmac (supported devices)

    • Supports BCM43602.
  • wl (supported devices)

    • Non-free vendor driver, not in mainline Linux kernels.
  • bcm43xx
    • Introduced in Linux 2.6.17.
    • Disabled in Debian 2.6.24 and later kernels.
    • Removed from Linux at 2.6.26.

More information on b43/b43legacy can be found on the Linux Wireless b43 driver page. The b43, b43legacy, brcmsmac and wl drivers do not support any USB devices.

Using Windows' binary drivers:

  • NDISwrapper plus the relevant Windows NDIS driver. This is a workaround for devices not supported by the Linux kernel, such as USB devices based on Broadcom wireless chips (other than the BCM4320).

b43 and b43legacy

These drivers are included as modules in Debian kernel images. Firmware from userspace is required for device operation.

Firmware is not packaged by the Debian Project. It must be downloaded and extracted, which can be performed by the firmware-b43-installer, firmware-b43legacy-installer or firmware-b43-lpphy-installer packages during their installation. An Internet connection is required.

  1. Add a 'contrib' component to your existing repository line in /etc/apt/sources.list; for example:

  2. (Note: do not add a new line. Just add ' contrib non-free' to the end of your existing line.)
  3. Update the list of available packages:

  4. Install the appropriate firmware installer package:

    For devices with a BCM4306 revision 3, BCM4311, BCM4318, BCM4321 or BCM4322 chip, install firmware-b43-installer:

    For devices with a BCM4312 LP-PHY chip (PCI ID 14E4:4315), install firmware-b43-installer:

    For devices with a BCM4301 chip or the BCM4306 revision 2 chip, install firmware-b43legacy-installer: A PCI ID check will be performed. When satisfied, the relevant Broadcom proprietary driver will be acquired, the firmware within will be extracted and installed.

  5. If not already performed, connect the device to your system. The necessary kernel module is automatically loaded for supported devices.

  6. Configure your wireless interface as appropriate.

Troubleshooting

  • Examine the kernel ring buffer (dmesg(1)) to verify the required firmware files are being loaded by the driver. Lack of firmware is the usual reason for the 'SIOCSIFFLAGS: No such file or directory' error message.

    • Run dpkg-reconfigure firmware-b43-installer, dpkg-reconfigure firmware-b43legacy-installer or dpkg-reconfigure firmware-b43-lpphy-installer (as relevant) to fetch and extract firmware again.

    • If necessary, firmware can be manually acquired and extracted using the b43-fwcutter utility, see http://wireless.kernel.org/en/users/Drivers/b43#Device_firmware_installation. The b43-fwcutter package will need to be installed.

  • Debian 6.0 'Squeeze' users: prior to Linux 3.0, DMA errors may occur on some systems with LP-PHY devices (589867).

    • To workaround:

  • Known issues with the b43 driver are documented on its homepage.

NDISwrapper

This should only be used as a last resort, if the device is not supported by Linux kernel drivers (e.g. Broadcom USB devices, other than the BCM4320).

Blacklist Linux kernel drivers

If loaded, the b43/b43legacy drivers will conflict with NDISwrapper. To unload and blacklist:

Installation

Kernel module and NDIS driver installation is described on the NDISwrapper page.

Supported Devices

b43

The page HowToIdentifyADevice/PCI explains how to identify a PCI device.

  • http://wireless.kernel.org/en/users/Drivers/b43#Supported_devices

b43legacy

The page HowToIdentifyADevice/PCI explains how to identify a PCI device.

  • http://wireless.kernel.org/en/users/Drivers/b43#Supported_devices

See Also

  • brcm80211 - Broadcom BCM4313, BCM43224, BCM43225 devices

  • rndis_wlan - Broadcom BCM4320 devices

  • How to use a WiFi interface

  • NDISwrapper

  • wl (vendor driver)

  • BCMHybridBTFirmware - Firmware installation for hybrid bluetooth adapters

External Links

  • http://wireless.kernel.org/en/users/Drivers/b43 - b43, b43legacy homepage;

    • irc://irc.freenode.net/bcm-users - driver IRC channel

CategoryHardware | CategoryWireless

< User talk:M86

Linux-driver for RTL8723BE

Linux-drivers: https://github.com/lwfinger

--Kristjan

This driver should be in kernel 3.15

--Larry
noted + added. thx. --M86 (talk) 00:39, 22 January 2014 (EST)

Linux-driver for RTL8821AE

A staging driver will appear in kernel 3.14, The 'final' version should be in the normal wireless tree by kernel 3.15.

--Larry

Atheros AR5B22

This module is used in the HP Chromebook 14, model 14-Q030SG (according to the label on the back of the notebook).

Wi-Fi is supported by ath9k, Bluetooth will be supported by ath3k (see https://bugzilla.kernel.org/show_bug.cgi?id=68791).

lspci:

lsusb:

OK. I tossed an entry up @ Foxconn U98Z106.00, which should be the specific card in question --M86 (talk) 09:50, 22 January 2014 (EST)

D-Link DSL-2750U

Down here in India, there appears to be a new revision of the D-Link DSL-2750U in the wild, viz., rev. U1.

The last revision of this model was C1, and had a Broadcom SoC. This one, however, appears to be powered by a Realtek SoC.

The firmware revision on my unit is IN_1.08; D-Link has both country-specific and revision-specific firmware for this model.

Some images of the unit:

cat /proc/cpuinfo:

cat /proc/meminfo:

cat /proc/diskstats:

Noted. I'll toss a stub up for it at D-Link DSL-2750U rev U1. More details (board shot[s] esp. would be helpful though.. --M86 (talk) 09:50, 22 January 2014 (EST)
Here's some more info on the router:

Panasonic DY-WL10

I went to the wikidevi page below to install the driver for Windows 7 for the (edit: for the Panasonic DY-WL10)

It started the update driver process and seemed like it was going to install the driver!
Then I got a message that 'a hash could not be found' and that the file was either corrupted or had been tampered with'
Can someone help? Thanks.....
The .inf file should be the only modified part of the driver - everything else was identical to the vendor's driver set
You may want to try the older one, otherwise I'll look into it when able
--M86 (talk) 20:47, 22 December 2013 (EST)

Netgear DG834GB v5

I started a thread over at OpenWrt, and I want to 'donate' the images I made to anyone that may find it useful. As Wikidevi does not yet have that model, feel free to use the images from that thread. I was not allowed to upload them here as I am unregistered.Thread with Images

Noted.. but you may wish to submit them to Wikimedia Commons in the future. They will then be available to any MediaWiki instance w/ Commons support enabled.. and have an infobox clearly stating their license, authorship, date taken, etc..
--M86 (talk) 18:46, 5 December 2013 (EST)
OK, I will do so. I hope, I don't forget it :-)

New Question

Are driver for this device also for Windows 8 avaliable?

there may be one available - take a look at the TL-WN822N v2's driver sets
--M86 (talk) 04:37, 3 December 2013 (EST)

Asus N-66

Trying to coerce it now. Tried with bundled drivers from Asus, the driver loads, the card works somehow, but doesn't see anything. There's newer driver at http://www.mediatek.com/_en/07_downloads/01-1_windowsDetail.php?sn=5034, but still doesn't work.

The driver from 3.12.1 kernel works ok.

indeed, it would probably be best to stick with rt2800usb now that support is there (unless there is a compelling reason to use Ralink's driver)
--M86 (talk) 04:39, 3 December 2013 (EST)

SMCWUSB-N2

Drivers on the site for SMCWUSB-N2 are not recognized by Windows 7. Any alternatives?

You will need to modify the inf file to include the USB ID for this dongle - it is not in there now.
Open the Win7 inf file you need (x indicates a 64-bit target), and add it in (should look similar / identical to the below line)
%ATHR.DeviceDesc.9170% = ATHR_DEV_9170.ndi, USBVID_0CF3&PID_1002
Failing that, just use the vendor's driver.
--M86 (talk) 23:13, 1 October 2013 (EDT)

TP-Link WDR4300 v1.6

Version number of this unit is at 1.6 (PCB ver. 1.3). It has green LEDs now (early units had searchlight-like blue ones) Some parts have changed (Atheros chips are the same, not counting subversions and manufacturing countries), RAM module changed. Power supply also changed. Should you be interested adding it to the site, I can provide all necessary data.

Hmm.. well, I suppose knowing the text found on this board revision would be handy. If there are any additional notable component differences (either in part or revision) or notable board layout changes, that may also be useful to add..
--M86 (talk) 15:26, 21 September 2013 (EDT)
A bunch of photos of v1.0 and 1.6: netload.in/dateiMNhjbE3JBj/w_d&r4300.7z.htm
--murrayd (talk) 22:55, 21 September 2013 (CET)

Winstars WS-WN688N5

I bought a Tecknet adapter from amazon de:http://www.amazon.de/TeckNet%C2%AE-300Mbps-Dualband-Wireless-WPA2-Verschl%C3%BCsselung/dp/B00E38ALDGThis one looks like 2 drops of water to the mentioned WS-WN688N5 adapter (it does not have the uspeed label on the front). It even has the type indiction:WS-WN688N5 REV.D on the back. It does not use the realtek driver mentioned. In fact it is a RAlink RT5572 (from lsusb:148f:5572 Ralink Technology, Corp.). It works with the following driver:http://www.mediatek.com/_en/07_downloads/01-1_windowsDetail.php?sn=5032

Is this a new version/revision (so soon) or is it a mistake?

It is probably a new one. Whomever is manufacturing these things will likely switch things around whenever it is convenient to do so.
I'll toss a new entry up for this particular one. Thx, btw.
--M86 (talk) 12:27, 1 September 2013 (EDT)

TP-LINK TL-WN727N v4

product link: http://www.tp-link.com.cn/product_230.html (only available in Chinese)
--—The preceding unsigned comment was added by person (talk • contribs) . Please sign your posts with ~~~~!
Noted. It has been added. (Thx.)
--M86 (talk) 15:23, 13 August 2013 (EDT)

awus036nha

The driver listed does not work well with AWUS036NHA. The best driver I found to work with it is the one from ALFA's website. The TP-Link driver pulls very few connects and just drops them after connecting. The ALFA driver has been the most reliable despite being an older base driver.

--—The preceding unsigned comment was added by RyokoZekem (talk • contribs) . Please sign your posts with ~~~~!

I believe the original driver CD is also mirrored here - it's linked to on the page (but not the infobox). .. it's not extremely surprising that the TP-LINK driver does not work well with the thing..

--M86 (talk) 19:25, 28 June 2013 (EDT)

Wi-fi adaptor for Panasonic Viera TX-L32E5E

Hello!My name is Cosmin and i want to ask you,what kind of adapter is compatible

with Panasonic TY-WL20 TY-WL20U TY-WL20E Wireless Lan WiFi USB Adaptor Dongle.
Can you tell me,please 1 or 2 brands witch are compatible with those one?
Thank you verry much!

Edimax EW-7822UAC ac adapter provide Linux driver

I found a link in edmaxhttp://www.edimax.com/images/Image/Driver_Utility/Wireless/NIC/EW-7822UAC/EW-7822UAC_linux_v4.2.2_7502.20130517.tar.gz

It seems that they provide Linux driver for this USB 3.0 802.11 ac adapter. I ordered one online. I will let you know if it works. This is the only AC adapter for Linux that I can find so far.

2013-07-26 UpdateI can confirm that edimax EW-7822UAC provide Linux driver. I successfully compiled its driver and connected it in Fedora 19. The download speed can reach average 15MB/s and peak 20MB/s by using perf.

Here is iwconfig: enp6s0u2 IEEE 802.11AC ESSID:'Orz-5Ghz' Nickname:' Mode:Managed Frequency:5.2 GHz Access Point: 74:D0:2B:41:EC:FCBit Rate:867 Mb/s Sensitivity:0/0Retry:off RTS thr:off Fragment thr:off Power Management:off Link Quality=100/100 Signal level=94/100 Noise level=0/100 Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0

lsusb:

Noted. I also just tested the driver with my Belkin F9L1109 (w/ Edimax BR-6478AC AP) and it works quite snappily (~25.7MBps peak and ~16.5MBps average [w/ iperf]). .. I would have tested it earlier... but, to say the least, I am not feeling well atm{
I'll add the driver so it will show up automatically in the infobox shortly.. Thanks for letting me (and everyone else) know!
--M86 (talk) 01:57, 27 July 2013 (EDT)

2013-12-14 Update

I found an updated version of this driver for 3.10+, and can confirm it works with my EW-7822UAC: https://github.com/abperiasamy/rtl8812AU_8821AU_linux
--—The preceding unsigned comment was added by some guy (talk • contribs) . Please sign your posts with ~~~~!

BCM4323 USB WIFI - Catalogue PC Drivers, New Drivers, Drivers ...

noted, I'll look into it when able --M86 (talk) 20:47, 22 December 2013 (EST)

and it has finally been added --M86 (talk) 22:07, 1 February 2014 (EST)

AP mode

Could you please check if it does work in AccessPoint (AP) infrastructure (master) mode under GNU/Linux with hostapd?

Bcm43236
--Thump (talk) 08:06, 1 February 2014 (EST)
From my limited testing, no - the 8812au driver does not currently work w/ hostapd (nl80211) or an older Realtek modified hostapd. A newer Realtek hostapd build may get it to work, however. The one I used was targeted for use with 81xxCU devices (and may have been outdated even for those..).
--M86 (talk) 21:54, 1 February 2014 (EST)

Buffalo WZR-D1100H

Any plans to add Buffalo WZR-D1100H? my page is at Buffalo AirStation WZR-D1100HDarkShadow (talk) 16:50, 25 July 2013 (EDT)

Uh, well, I guess I (or anyone else that feels like it) can - it will not take too much effort.

I assume it is identical hardware to the D1800H - just limited in software w/ Japan specific regulatory crap

--M86 (talk) 00:45, 26 July 2013 (EDT)

TP-LINK TL-WN723N v3

This page[1] said to let you know when a linux driver was available for this chipset? Well, there seems to be one floating about.

[2]
[3].
I used it on my raspberry pi and it works for me. I hope this was a useful contribution.

Thanks for the awesome info on this wiki.

--Brad
It is indeed useful. I found the same source also at https://github.com/liwei/rpi-rtl8188eu without the full kernel tree included (not that it really matters). I'll toss it into the driver template in a sec so it will show up for all rtl8188eu(s) devices...
Thanks.
--M86 (talk) 01:48, 3 May 2013 (EDT)

Linksys AE1200 Windows driver

At least for me (using Ubuntu 12.04).

I've tried lots of things but it only seems to work for WEP and open networks.
I don't know whether it's driver's fault
--200.73.235.156 00:30, 29 March 2013 (EDT)
the driver probably won't work properly with ndiswrapper (from my testing w/ x64 systems, it crashed instantly anyway) - it doesn't even work properly in Windows (at least in XP). a native driver (or maybe vista/7 driver support in ndiswrapper) will likely be required for proper functioning
--M86 (talk) 03:37, 15 April 2013 (EDT)

Arcadyan WN8522D 7-JU Broadcom BCM43236 driver

Arcadyan WN8522D 7-JU Broadcom BCM43236 driver doesn't work on XP

Hi, Thanks for you windows driver.It works fine on Win 7 but i can't install it on XP. Thanks

indeed, it doesn't seem to be working correctly with bcm4323 devices. you may have better luck with the driver for the wnda3100v2.
--M86 (talk) 02:53, 21 February 2013 (EST)
BCM4323

Hi, thanks for the link, i tried this driver but it doesn't work better :(

yeah, I misread what you typed earlier - that driver would never work. anyway, I don't currently have a non-AE2500 BCM43236 dongle to test. you may want to try the NetComm NP920 XP driver (5.100.68.46 [appears to be the same version as the one included with the AE2500], includes the default BCM43236 USB ID) or the AirTies Air 2410 driver (version 5.100.68.27, also includes the default BCM43236 USB ID).. and do let me know if any of those work..
--M86 (talk) 01:07, 3 March 2013 (EST)

Hi, i tried both these two drivers but it doesn't work :( .Xp tell me it doesn't find any driver for this device at this location when i specify manually the folder where i extracted driver files.Thanks

hmm? the standard bcm4323 / bcm43236 USB IDs should be in there. what is the USB ID for your device? see here if you don't know how to find it in the device manager...
you may also want to try disabling the 5GHz band in the device properties (if you do not require it, of course). that seemed to help during my limited testing of a few devices.
--M86 (talk) 23:12, 12 March 2013 (EDT)

Hi, This is the USB ID:

Hi, Up.Did you rode my last comment ? Thanks :)

yes, but please wait, will look into at some point soon
--M86 (talk) 09:22, 11 April 2013 (EDT)

k, well none of the newer BCM driver sets seem be fully working with my test system (X20 w/ USB 1.1) and test dongles (AE2500 and a BCM4319 one), but they do work with 5GHz disabled

give 5.100.68.46 a shot. check the inf file if it fails to install. I have not done exhaustive testing, btw, there are potentially other issues
--M86 (talk) 03:32, 15 April 2013 (EDT)

Hi :) Sorry for my late reply.So it works on xp with 6.30.145.26 version.

Thanks for all :)

Sony UWB-BR100

Hi, I was trying to install the uwb-br100 to my pc. I downloaded the driver you provided, but I have two problems. there is no install file, only the sys file, which I dont know how to install if not going to the device itself and ask for update the driver. Well, my second problem is that I cant do that, because windows 7 dont see my sony dongle. So how can I proceed please, this is top priority for me at the moment.

Please help me,thanks,

Windows driver for TP-LINK TL-WN821Nv3

Whenever I try to install it. My device becomes inactive.

This driver may not have all the necessary stuff in the inf file to initialize it properly. I would suggest trying the one available on TP-LINK's website, if you haven't already.
--M86 23:15, 28 November 2012 (EST)

TL-WN821N V3 @ Windows Server 2012

Can you install it on windows server 2012 been trying for days with V3 drivers, disabling signed signatures and manual work-arounds in the device manager.

Valet Plus M20

I noticed on the article for this router you wrote that TomatoUSB works with it as of 10/13/2011. Do you know where builds this recent can be found, and which type of build should be used?

-- 72.160.105.179 20:30, 22 November 2012 (EST)
Bcm43236 Drivers
10/13/2011 was just the date I had downloaded and flashed the firmware.
tomato-K26-1.28.9054MIPSR2-beta-Std.trx (MD5: fd129513969cca0cca35a674e98aff44), the latest (11/30/2010) non-Toastman MIPSR2 NoUSB-Std was the build I used. I believe I initially flashed the device to DD-WRT before flashing to TomatoUSB.
--M86 20:58, 22 November 2012 (EST)
Okay thanks! Already have DD-WRT on mine and will give that build a shot tonight!
-- 72.160.105.179 21:57, 22 November 2012 (EST)

Junxion Box

Dear M86 my junxion box don't boot anymore, can you make an image of the CF card on your unit and share it please?

I greatly appreciate your help! Thank you.
The Junxion Box I had is long since gone. Sorry.
--M86 10:17, 23 September 2012 (EDT)

Alternative for Sony UWA-BR100

Hey, do you know any working alternative for this Stick? The TP-LINK TL-WN821N uses similar Chips, but you mentioned something about 'Sony locked their devices to the 0411:017f USB ID'.If there is no alternative, how can I modify the TP-LINK Stick to also use the 0411:017f USB ID? (If this is even possible?)Thanks in advance and also thanks for the information already given by you.

--—The preceding unsigned comment was added by 80.153.143.237 (talk • contribs) . Please sign your posts with ~~~~!

Cached

There is no known alternative adapter for the device. There is no known way to modify the EEPROM of AR7010 devices to change the USB ID.
If there was a known way to get third-party dongles working on the device it probably would have been added to the UWA-BR100 page.
--M86 16:49, 19 July 2012 (EDT)

Help on identifying DWA-160 Rev B2 chipset

I have a D-Link DWA-160 rev B2. I confirmed pid and vid. I can't tell what chipset it is though. lsusb -v doesn't say. When I opened the device up there's no identifying chipset information. I might need a magnifying glass. On Windows the Ralink 'USB(RT2870/RT2770/RT307X/RT2070/RT357X/RT3370/RT8070/RT537X)' driver works. On Linux the RT5572 USB driver works. Any ideas on how I can confirm the actual chipset?

--98.218.56.231 01:00, 12 April 2012 (EDT)
DWA-160 rev B2 chip image from the FCC
You can check out the internal images at the FCC site by plugging the FCC ID (KA2WA160B2) in into the FCC website ( http://www.fcc.gov/oet/ea/fccid/ ). It is clearly identifiable as a RT5572 through there. If you don't feel like doing that, take a look at the image to the right.
In Linux, you can confirm the chipset by enabling CONFIG_RT2X00_DEBUG and recompiling rt2800usb (best to use compat-wireless). Then when the device is plugged in and recognized by rt2800usb, a line ('Chipset detected - rt: xxxx, rf: yyyy, rev: zzzz.') will be output by the module and logged into dmesg. I modified the line into a printk so it would output all time without debug set.
--M86 01:16, 12 April 2012 (EDT)
Thanks for the info. I didn't take the metal part off that was covering the actual chip when I took it apart. Weird that that RT3572 driver works for it on Windows but it must be similar enough. The Ralink RT5572 driver works fine on Linux as long as you change it to be GPL. Otherwise it won't get loaded.
--98.218.56.231 01:48, 12 April 2012 (EDT)

Sony_UWA-BR100 Wireless Drivers

on your page http://www.wikidevi.com/wiki/Sony_UWA-BR100 you said to let you know if I can't get the drivers to work.I can download the zip file, but what do I with it then?

--—The preceding unsigned comment was added by 175.39.11.199 (talk • contribs) . Please sign your posts with ~~~~!
i've done everything, and i am at the top of my despair. I've installed the wn821n v3 drivers, but it keeps disconnecting and i keep recieving the BSOD!!!athurx.sys is fault.
i run windows 7 64 bits. tp link version crashes, another version crashes, your version crashes, a 4th version device doesnt start.
Please help!
--—The preceding unsigned comment was added by 78.43.163.173 (talk • contribs) . Please sign your posts with ~~~~!
can't help --M86 16:11, 28 March 2012 (EDT)

Yeah. Works to a point. Installs fine, but cannot find any networks and therefore cannot connect to them. Using Win7 x64 driver on Server 2008 R2 Standard

--—The preceding unsigned comment was added by 72.23.66.169 (talk • contribs) . Please sign your posts with ~~~~!

See Full List On Broadcom.com

It works fine for me with the same dongle (Sony UWA-BR100) and Win7 x64.
--M86 16:58, 11 July 2012 (EDT)

bcmwl_4323x drivers

Download Broadcom BCM943XX/BCM43XX WLAN Driver 5.10.79.7 For ...

Dear admin

i used Ae 2500 by this driver(bcmwl_4323x.zip) ,but it not work in 5g model in China ,can u give me a driver for China
Thanks.
--—The preceding unsigned comment was added by Lishengjing (talk • contribs) . Please sign your posts with ~~~~!
The US driver for the AE2500 is the only driver I have available. FWIW, it works with 5GHz channels here.
--M86 18:21, 2 March 2012 (EST)

Broadcom Inc. | Connecting Everything

older talk

Retrieved from 'https://wikidevi.wi-cat.ru/index.php?title=User_talk:M86/Archive_2&oldid=332622'