Pages

Sunday, February 2, 2014

Lenovo U530 Touch WiFi Problem Continued

This may not be a Lenovo and/or Intel driver issue. It might be Windows 8/8.1. I’m trying a couple of different fixes to see what sticks.

Disable Energy Management

Maybe the OS isn’t telling the adapter the right thing regarding when to shut down?
  1. Network and Sharing Center > Change adapter settings
  2. Edit your wifi adapter > Properties > Configure
  3. Choose Power Management tab and uncheck everything.
image

Disable MSI Support

I don’t know what MSI Support is, but there’s some evidence that Win8 doesn’t communicate with WiFi adapters in the same way regarding it. See Mark Hanna’s answer in this thread. https://communities.intel.com/thread/32169
[Here’s his answer copy/pasted]
Some Intel engineers did investigate this issue and this is what they found. When the system is in battery mode to save power, Windows 8 is doing something different compared to Windows 7 and earlier versions of Windows. For some reason the driver is not getting called by the OS in battery mode resulting in transmit hangs.
I do not anticipate any driver update for this issue, but you should be able to make a registry change to the interrupt type from MSI to legacy to work around the issue. After disabling MSI on a test machine here, the hang was no longer happening.
MSI can be disabled from registry. You can use Windows Device Manager to find the hardware device ID information that will be part of the path to the registry setting shown in brackets and highlightedbelow. Hardware IDs can be found in the device's "Details" tab.
Here is an example for my network connection. The numbers are different because I have a different network connection, but this does show where to find the hardware IDs.
HardwareIDs.jpg
The above information is what you will need from your network connection in order to locate the right place in the Windows registry.
Caution: Make sure you back up your registry before proceeding. Changing or deleting registry keys can have unintended consequences.
Registry Setting Path:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\PCI\[VEN_8086&DEV_XXXX&...]\3&33fd14ca&0&C8\Device Parameters\InterruptManagement\MessageSignaledInterruptProperties
Change "MSISupported" value to '0'. The value is '1' by default. You can always go back and change to '1' again if you run into any new issues.
Here is a screen shot of my registry setting that I navigated to using the hardware IDs I found in Windows device manager:
MSI.jpg

 

Update 2014-02-02

Neither of the above solved my problem. However, I finally found a forum from Intel discussing the issue, and discovered I’m not running the latest Intel drivers (I am running the latest driver on Lenovo’s site). There were several steps to deal with, but I’m install both the Bluetooth and WiFi drivers soon. I’ll check that the other changes I made aren’t in place—running default settings—and report back.
http://www.intel.com/p/en_US/support/detect

Update 2014-02-03

I don’t know yet if the latest drivers prevent the adapter from dropping down to 11mbps, but I do know the adapter got turned off while in sleep mode, and came on shortly after coming out of sleep. The power profile definitely isn’t set to do that, so I’m turning off the adapter’s Properties > Power Management > Allow the computer to turn off this device to save power.


Update 2014-02-05

The laptop hasn’t dropped to 11mbps since installing the latest drivers. I’m also letting Intel PROSet manage wireless. I just realized that of course the wireless goes to sleep while the laptop’s in sleep mode. That’s what it’s supposed to do.The import thing to me is that it properly wakes up, which it appears to be now. I have a daily backup using Windows Home Server, and the laptop is configured to wake from sleep or hibernate to perform that. Haven’t tried it in hibernate, yet!

Here’s another nugget: running System File Checker, e.g. sfc /scannow, found corrupt files it couldn’t repair. “Cannot repair member file”. I found this link that suggested running, as administrator,

dism /online /cleanup-image /restorehealth.

This indeed repaired the image, and running sfc again found no errors.

Cannot repair member file [l:36{18}]"Amd64\CNBJ2530.DPB"

sfc /scannow – Cannot repair member file

Update 2014-02-17

I tried letting Windows manage my WiFi, and began having troubles again (suddenly slower speed, dropping connection). So, for some reason, letting PROSet manage the wireless makes a big difference.

Sadly, I was unable to connect to a Days Inn wireless recently. But I had no problem connecting with my smart phone. Windows 8 issue? Maybe the next W8 update will make an improvement.