A knowledge base article about Surface Pro Devices and eduroam provided by the UC Berkeley IT Service Hub - Knowledge Portal
If you are having issues connecting to eduroam using a Surface Pro device it may be necessary to roll back the wifi driver. Follow the instructions below to check the driver version and roll back the driver if necessary.
Note: airbears2 will be decommissioned, all new connections should be to eduroam.
- This solution has been tested on Surface Pro 3 running Windows 10.
Before you begin
Task to be performed
- Check to see which driver the wireless adapter is using:
1. Go to Control Panel>Hardware and Sound, select Device Manager.

2. Expand the Network adapters section.

3. Right-click Marvell Wireless adapter and select Properties.
4. Click the Driver tab to see which driver version is installed.
Good driver:
Driver date: 10/29/2014
Driver Version: 15.68.3066.135
- If you see the "Good driver" and still cannot connect or stay connected to eduroam please contact CSS IT at 510-664-9000 for further assistance.
Bad driver:
Driver date: 6/4/2015
Driver Version: 15.68.3091.193
- If you see the "Bad driver" follow these steps to roll it back. Please note- you must log in as Admin to make changes to the device driver.
- Download the good driver version and unzip.
- Right-click mrvlpcie8897.inf and install.
- Open Device Manager, right click on Marvell Wireless adapter and select Update Driver Software.
- Select Browse my computer for driver software and then Let me pick from a list of device drivers on my computer.
- Navigate to your download location and select version 15.68.3066.135 [10/29/2014] click Next.
- Reboot when prompted and reconnect to eduroam.
- Be aware that Windows Update will attempt to update the rolled-back driver the next time it runs. To disable automatic updates go to Control Panel> System and Security> Windows Update> Change Settings and change the default from Install automatic updates.
If you have issues connecting to eduroam or Berkeley-IoT, try rebooting your device and go through these steps again. If this does not resolve connectivity please contact us for help: