Looking for a driver.

Associate
Joined
24 Nov 2002
Posts
1,647
Location
Abertawe, Cymru.
I have a cherrytrail based mini pc, it came with windows 10 x64, since the last major update the wlan fails to work, I've looked everywhere I can think to find a working 64bit driver.

Broadcom802.11abgn Wireless SDIO Adapter

Anyone have a working driver please?

Cheers.

SJ.
 
I would find the hardware ID for the adapter in the device manager and google that, typically many manufacturers use the same wlan chipset and each provide better or worse
documented driver releases.
.... but how do you know something like the chipset driver is not responsible
 
http://snappy-driver-installer.org/

Try that, I use it all the time at work :)

Stoner81.

Not the OP, but thanks for that! I've been looking for something like this for a while; my motherboard's a few years old now so Asus stopped updating anything. I'd found a few I needed on TechSpot, but this tool found 7 out of date drivers and updated them all seamlessly. Great little app. :)
 
I'm not a fan of these things as they are often loaded with adware or other malware but apparently Driver Booster has a lot of and/or can find the obscure Cherry Trail drivers - most of them are also on Softpedia if you manage to narrow it down.
 
I've tried driverbooster, slimdrivers and googling the hardware id, just cant find a working version. I'll try snappy drivers cheers.
 
Open Device manager, right click on the device and open properties, click on the details tab and then choose Hardware ID from the drop down menu. You will need the VEN id and the DEV id. It should look something like this PCI\VEN_8086&DEV_153A. VEN is the vendor e.g. Broadcom and DEV is specific to the device.

Go to pcidatabase.com and then search via the device ID. A table should appear with broadcoms name. You can then copy the chip description and you should be able to find it from there. In the VEN DEV example I gave above my search comes back with Intel I217-LM Ethernet Connection.

For broadcom the chip name should start with BCM
 
maybe this was unique to laptops - but my DELL bios does have a device ID blacklist, so the the agn 1/2pci card I bought from China never worked,
and was not even acknowledged in device manager, I contemplated a bios edit but chickened out.
 
Open Device manager, right click on the device and open properties, click on the details tab and then choose Hardware ID from the drop down menu. You will need the VEN id and the DEV id. It should look something like this PCI\VEN_8086&DEV_153A. VEN is the vendor e.g. Broadcom and DEV is specific to the device.

Go to pcidatabase.com and then search via the device ID. A table should appear with broadcoms name. You can then copy the chip description and you should be able to find it from there. In the VEN DEV example I gave above my search comes back with Intel I217-LM Ethernet Connection.

For broadcom the chip name should start with BCM

I'm not sure I'm doing this right. I'm getting the hardware ID ok but can't seems to find any results when searching by either the vendor or device ID.
 
I wonder if this is related to what I posted in April: https://forums.overclockers.co.uk/posts/30714306/
I've found out why Windows 10 Creators wasn't installing. Me and many others with a Broadcom 440x ethernet controller are experiencing exactly the issue with the installer hanging. People are getting round this by disabling the controller in their BIOS - my BIOS happens to be one that you can't disable it in. :mad:

Windows 10 Creators Update broke my LAN port - Microsoft Community
Problems with Creators update - Microsoft Community
Hello. I am an Engineer in the Windows Networking team. I can confirm that there is a bug in the Creators Update that affects the compatibility with the Broadcom 440x driver. We are working on resolving this until it is resolved.

Thank you for reporting this! I will post any updates on this issue on thread:

https://answers.microsoft.com/en-us...4590-b2f3-a64b92445385?rtAction=1492183836572

Meanwhile following the steps mentioned in this thread will work around the issue (if you can call disabling Ethernet a valid workaround) until we have a real fix available.
 
Back
Top Bottom