Intel wireless driver responsible for long resume problem

[krma-thkpds]

Some ThinkPad users have been reporting about resume problem where computer which has been put into stand by or hibernate after a few hours takes increasing amount of time to resume. The longer stand by/hibernation the longer resume time.

I was one of those with the problem described. Since then I was investigating my system to find the cause of the problem. Firstly I resotored my system to factory state and then installed programs one by one while monitoring the resume behaviour. The same I did with drivers; installing them one by one and for each installation left my computer in stand by/hibernated for one night to be sure if the most recently installed proogram is really the cause of the problem.

However, yesterday I installed the newest version of Intel wireless driver and left my computer hibernated during the night. In the morning the resume took me whole 4 minutes compared to less then 1 minute before installation of driver mentioned.

I conclude with the fact that this driver is causing the long resume problem and advice other users not to install it, or if you wish to install it first make sure you back up your system before.

[dvorak]

First of all, you can always uninstall it, with drivers there are few files modified, and those just replaced when you 'update' to an older release.

And second of all, only applies to those with Intel wifi-cards :) I lack both the Intel Pro manager software and Intel wifi-cards, but still ocassionally spend a minute watching a black screen when resuming stand by :)

Oh yeah, was your adapter enabled or disabled when you hibernated? And please do try the other option too, perhaps it's just a problem with it being enabled, then trying to connect to a network before resuming activity, or vice-versa.

[krma-thkpds]

The apater was diabled, because I have wired LAN at home. In the proccess of new driver installation the previous version is unninstalled, then new hardware is automatially detected (Intel Wi-Fi) and when the new driver is applued the adapter switches on. I don't see anything here what could be changed by the user. Except that one would have adapter switched on while starting updating, but anyway the old driver is removed and from there on everything is the same in either case.

[dvorak]

The apater was diabled, because I have wired LAN at home. In the proccess of new driver installation the previous version is unninstalled, then new hardware is automatially detected (Intel Wi-Fi) and when the new driver is applued the adapter switches on. I don't see anything here what could be changed by the user. Except that one would have adapter switched on while starting updating, but anyway the old driver is removed and from there on everything is the same in either case.

Not quite understanding your text :)

You need not to uninstall the driver first, simply going opening the device's properties -> driver -> update driver is sufficient for replacing it with what-ever version one wishes.

Okay, resuming stand by with the new driver on and device disabled was longer, how about device enabled? And I suppose when you "updated" to an older version, resuming stand by was as fast as before?

[krma-thkpds]

I did not uninstall it manually. The SI did it. I am saying that it doesn't matter you have the adapter enabled or not, because the SI uninstalls it first. I can try doing this manually but doubt there will be any effect. I think I will just stick to the previous release of the driver.

[dvorak]

I don't know why we're discussing uninstallation actually :)

My whole point regarding disabling/enabling the adapter was that it may make a difference when going to stand by -- and coming out of it, so I asked you to do your experiment the other way too (enable it before stand by or vice-versa).

Just as a side note, you probably can change the driver without restarting too, Software Installer probably requires a restart, but doing it manually shouldn't.