Broadcom Virtual Wireless Adapter

[Irmgard Rossie]

Hithere,I've reserved Win 10 upgrade. GetWin10 App says my Broadcom Virtual Wireless Adapter (Dell Wireless WLAN 1501 Half Mini-Card Driver) isn't fully compatible with Win 10 and I'll experience connectivity problems on my machine after upgrading. I can't get any drivers from Dell/Broadcom site that are compatible with Win 10 on my machine. Does it mean after upgrading to Win 10 I'll lose wireless connection on my laptop or Win10 will support my device out of the box? How to fix that issue?

Today, upgraded Dell Inspiron 15R N5010, Windows 10, with Broadcom Virtual Wireless Adapter and IDT High Definition Audio. Upgrade, restart and Windows Update and restart all worked perfectly. No issues with the Broadcom Wireless Adapter or the IDT HD Audio. All worked immediately after upgrade with no new drivers. And all of my other apps worked, a few with updated needed. System appears to be of a high quality, fast and eliminating IE was a good step.

Initially, I reserved WIN10 but could not upgrade due to Broadcom Compatibility issue. Instead used The MS Media Creation Tool, with the, 'Update This PC Now' option. Then following all the prompts. Took about 2 1/2 hours to upgrade, in place, with no impact on my files, etc.

Dell doesn't even support 8.1 on this system - so it won't have any 10 support. If Broadcom doesn't have support for the chip (they likely will though) you'd need to replace the wireless adapter to use Windows 10.

I highly suspect the drivers will work. Even if Dell doesn't support the drivers, they typically will work with new installations of Windows. However I would back up my computer long before trying to install Windows 10. I am prepared for the same issue with my Dell Latitude E6410 (circa 2011).

There are other problems with the N5010 and windows 10 that have been reported at the Dell Forums. Don't be too quick to upgrade until you can determine if your model is even compatible. You might just keep what you have until you buy a new computer. See the Dell Community Forum at Dell Support for more info.

I had the same problem, however some time ago i replaced the wifi card by the intel dualband wireless AC7260. The Broadcom Virtual Wifi Adapter was still in my configuration, but indicates not installed. I just removed it and get rid of the remark for the upgrade.

I just installed Windows 10 on my old Inspiron 15R N5010 and it's working great. I had the same alert as everybody, but Windows 10 work great except when turning on the laptop where I have a black screen for 1 minute. lol

I wilk have bought new laptop by the end of 2020 when Win7 support comes to the end. Upgrading N5010 is to risky and random. If something goes wrong, you'll lose your recovery partition. And Win 7 runs smoothly

Hi everyone! I'm glad and not so glad to be here at the same time... I'm glad because I finally decided to try out Arch Linux, and I'm not happy because if you see this post it means that something went wrong during the installation

those are the things i've tried so far... i've read that archlinux sometimes has a little trouble detecting these broadcom wifi cards, but I haven't found a concrete solution yet... Any help is greatly appreciated

Then follow the wiki here to identify the actual chipset on your card. You will also find links to information from that wiki page to identify the driver options for your card. There are - at least - two different chipsets in cards labeled BCM4352. Unfortunately, it seems the options for these are limited to bad and worse - but knowing which one you have will be important for knowing the next steps.

EDIT: oops, I missed that the wl module was already loaded. So that (mostly) rules out the "bad" option, and you may be left with "worse" of ndiswrapper, or just finding another wireless card to use. But still it would be good to get the actual chip information to be sure (as perhaps wl would work if you blacklist / unload any competing modules).

Yes, sorry, I had my terminology backwards. That's the chipset name, but I was looking for the PCI-ID which is 14e4:43b1. According to the docs, this card is not even expected to be supported by the 'wl' module (there is another BCM4352 which is). So you may be left just with ndiswrapper (which I've never had to use and it seems to even have been removed from the broadcom wiki page).

If you installed the wl driver and did not reboot afterwards, reboot (you can also try to remove the modules first)

If you did reboot after installing broadcom-wl, try to fully power down the system (remove the battery, if you can) and boot cold.

yes i also have windows on my pc, although i don't think it should interfere since arch linux isn't actually installed yet as i am still on archiso (and i installed a new SSD where i will have arch linux separate from windows)

Which is irrelevant to the matter at hand.

Typically the USB boot would prevent that, but also typically the wifi chip dropping out is the primary symptom.

=> 3rd link below. Mandatory.

Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.

What you need to do to get it working within the installation iso is first to follow seth's post, then either edit the kernel command line to blacklist all other broadcom modules while booting the iso, or `rmmod` those other modules once booted and (re)load the wl module. These are the steps I listed in post #4.

Note that in many ways getting this working in the iso may be harder than in a newly installed system (aside from broadcom-wl being preinstalled) as lots of *other* drivers are also installed and a bit tricker to blacklist which may be part of the problem. So following the advice below to install via ethernet or tether may be wise, then this should be easier to troubleshoot on an actual system.

shortly after that, pacstrap tried to install the packages. then i got hit with a whole wall of error messages where it basically says, that it failed to retrieve the file 'core.db' from a mirror. it looks like it tried dozens of mirrors.

(For anyone reading this with the same issue, just follow the tethering link that Seth sent and follow the usb instruction part. create the file and plug your phone in via cable and make sure that your iphone trusts the pc)

yesterday i used archinstall to install everything after setting up internet connection via tethering and got the same result from the journalctl command, so i thought i might need to do everything manually, which doesn't seem to be the case...

No. You should solve the problem. To do so, start a new thread and actually describe that problem including what it means that the bios "doesn't recognizes" your arch install while also including information about what boot loader you installed, how you installed it, and how you configured it.

I had a similar issue with internal machines not picking up my card so I created a new virtual network in virt-manager with NAT set to forward to my wireless card. I then use virtio and just select that network in the VM settings.

When you have Hyper-V running on Microsoft Windows Server 2012 or Windows Server 2012 R2 together with Broadcom NetXtreme 1-gigabit network adapters (but not NetXtreme II network adapters), you may notice one or more of the following symptoms:

Virtual machines may randomly lose network connectivity. The network adapter seems to be working in the virtual machine. However, you can't ping or access network resources from the virtual machine. Restarting the virtual machine doesn't resolve the issue.

You can't ping or connect to a virtual machine from a remote computer. These symptoms may occur on some or all virtual machines on the server that's running Hyper-V. Restarting the server immediately resolves network connectivity to all the virtual machines.

It's a known issue with Broadcom NetXtreme 1-gigabit network adapters that use the b57nd60a.sys driver. This issue will occur when virtual machine queue (VMQ) is enabled on the network adapter. (By default, VMQ is enabled by the Broadcom network driver.)

These network adapters are also sold under different model numbers by some server OEMs. HP sells these drivers under model numbers NC1xx, NC3xx, and NC7xx. You may be using driver version 16.2, 16.4, or 16.6, depending on which OEM version you're using or whether you're using the Broadcom driver version.

This issue is resolved in Broadcom driver b57nd60a.sys version 16.8 and newer. In March 2015, Broadcom published driver version 17.0 for download. In April 2015, HP published version 16.8 of the driver for their affected network adapters. Contact your server OEM if you need a driver that's specific to your server.

If you can't update your network adapter driver to resolve the issue, you can work around the issue by disabling VMQ on each affected Broadcom network adapter by using the Set-NetAdapterVmq PowerShell command.

By default, VMQ is disabled on the Hyper-V virtual switch for virtual machines that are using 1-gigabit network adapters. VMQ is enabled on a Hyper-V virtual switch only when the system is using 10-gigabit or faster network adapters. This means that by disabling VMQ on the Broadcom network adapter, you aren't losing network performance or any other benefits because this is the default. However, you need to do this to work around the driver issue.

Associated Privilege Management Capability:An instance of CIM_RoleBasedManagementCapabilities describing the capabilities of the mentioned instance of CIM_Privilege as described in subclause 6.3.4. Role Based Authorization Profile

CIM_EthernetPortAllocationSettingData (EPASD) CIM_EthernetPortAllocationSettingData that represents settings specifically related to allocation of an Ethernet port resource. Profile to Enable Automated Deployment of OVF Packages

Cloud Auditing Data Federation (CADF):An open standard that addresses the need for cloud security policies by enabling cross-vendor information sharing via its data format and interface definitions. Cloud Auditing Data Federation (CADF) - Data Format and Interface Definitions Specification

3a8082e126