Page 1 of 1
Wireless issues with sleep mode
Posted: Mon May 08, 2006 10:40 pm
by wirels
I really hate shutting down, and with the extended life battery, there's no real reason to do it. Nice fast resume and shutdown just by closing and lifting the screen.
But there's a catch. Inevitably when I resume, I have problems reconnecting to a wireless network. I do have the verizon card built in and if I had a previous session, even though I properly disconnected before entering standby, it still gives me issues. The client locks up, it won't start the card up, etc. Sometimes I have to terminate the process, sometimes I have to go into the device manager, disable then enable. Othertimes it's only fixed by a reboot. sigh.
Similar things happen with the regular 802.11 rig. The card won't start back up or it can't find base stations without a refresh or reboot. It's just annoying.
Has anyone out there experienced anything similar? Have you called IBM/Lenovo? I'll probably call them a little later this week when I have more time than right now. Just curious to see if I'm the only one.
Thanks,
Bill
___
1740-69U
Re: Wireless issues with sleep mode
Posted: Tue May 09, 2006 9:05 am
by archer6
wirels wrote:
Has anyone out there experienced anything similar? Have you called IBM/Lenovo?
_
1740-69U
Yes I have experienced the same thing.
What has worked for me is to simply wait a few seconds and the connection will restore itself. Once the lcd cover is lifted, the computer "searches" for a new connection. This is normal. The wait time varies according to conditions such as signal strength from the AP, other applications that are running and using resources etc.
I find that if I'm on the web only, it's quite fast at reconnecting. However if I have many apps open it takes a bit longer.
Let me know if this works for you.
Archer6
Posted: Wed May 10, 2006 1:00 am
by wirels
Nope, that sure doesn't work for me.
I can let it sit forever, I won't find anything...for the verizon card, the app just locks. I can kill it, restart the app and nothing works.
Now, this bit is going to sound ridiculous. Yesterday I was doing my disable / enable routine. I accidently left the Sierra / Verizon card on disable, launched the app and connected fine. The darn thing still shows disabled in the device manager and I assure you I'm on it this very moment posting on the forum. Crazyness.
So, I won't say that the solution is to leave it disabled, but it is working much better now. This could also be due to a slightly new technique. Before entering sleep mode, I disconnect from verizon, then close the app (connection manager). I guess the clean start helps things out. It's been much better since I've done that.
As for the WiFi stuff, I guess I'll try disocnnecting in similar fashion next time (most the time I'm on the Verizon service).
Thanks for the notes Archer.
Best,
Bill
Posted: Wed May 10, 2006 11:19 am
by archer6
wirels wrote:
Now, this bit is going to sound ridiculous. Yesterday I was doing my disable / enable routine. I accidently left the Sierra / Verizon card on disable, launched the app and connected fine. The darn thing still shows disabled in the device manager and I assure you I'm on it this very moment posting on the forum. Crazyness.
I agree the wireless can be Crazyness.
Based on this additional info you have provided, I remembered a similar problem on my friends ThinkPad. He brought it over to me, and I uninstalled and reinstalled the driver. You may want to do this on yours, as it should be stable after that.
Keep me posted.
Archer6
Posted: Wed May 10, 2006 11:51 am
by wirels
Archer,
I'm not touching it now. I mean, sure, the configuration is weird, but who am I to mess with the gods, nature, moon phases, et al.
If it breaks again, I'll absolutely re-install the drivers. If that happens, I'll post how it goes.
Thanks for the suggestion.
Bill
Posted: Wed May 10, 2006 1:24 pm
by archer6
wirels wrote:Archer,
I'm not touching it now. I mean, sure, the configuration is weird, but who am I to mess with the gods, nature, moon phases, et al.
If it breaks again, I'll absolutely re-install the drivers. If that happens, I'll post how it goes.
Thanks for the suggestion.
Bill
Sounds Good, as sometimes the best upgrade is NO upgrade
Archer6
Posted: Fri May 12, 2006 7:10 pm
by wirels
Okay, I've got 2 things that I've managed to get to work with the Verizon / Sierra Wireless card. One of them might also help withe the WiFi card for those of you who don't have the Sierra option.
First thing:
I disconnect from everything wireless. Next, throw the master wireless power switch on the front of the machine to the off position. Allow the os time to disconnect all the devices, then enter standby. When resuming, power back up the wireless devices via the switch and things seem to come back much more nicely.
And the second:
Simply tell the verizon connection magager to disconnect from the service, however do not close the manager out. Enter standby then resume. Simply tell the manager to reconnect. Has worked about 4 times for me so far.
I think my problem might have been trying to resume the verizon connection manager. Either way, it seems to be much more consistent than before. There doesn't seem to be a lot of interest in this thread, however I wanted to be through and offer the bit of resolve I've discovered incase someone needs this in the future.
Good luck all.
Bill
Posted: Fri May 12, 2006 11:07 pm
by Riddil
The Verizon card is really glitchy. Supposedly there's a new firmware update coming out for the card in the next couple weeks that's supposed to fix a lot of the suspend / resume oddities seen on the card.
*shrug*
We'll see.
Posted: Sat May 13, 2006 6:11 pm
by wirels
Riddil,
I gotta say, ever since I've gotten really methodical about figuring out how to get it working properly, things have been great.
Today I discovered that if I leave the connection active and enter stand-by, I can reconnect when I resume. I've done it about 4 times today without a problem. It just comes back to life with the connection manager up but disconnected. I'll still need to try after a reboot just to make sure it's not some one boot weirdness.
I'll still be very interested in the update though. =]
Bill
Posted: Mon Sep 10, 2007 6:59 pm
by spaznrq
My wireless card started to fail with a problem similar to this recently, but I've just updated my BIOS (to 2.13), along with other driver updates, and it seems to be working after one standby. *knocks on wood*
If you are interested in reading about the problem:
I have a X60 1709-7HU, Intel 3945ABG wireless card, using Window's wireless connection manager. I've been using this setup for over a year, placing it in standby mode and tossing it into my backpack in between classes. I would bring it back from standby and wireless would connect within 5 seconds and I would be happily surfing the web where ever I ended up.
Recently, I started to lose connection to my router at home after a few hours. Then I started to notice it lost wireless connection every time I resume it from standby. It was very annoying, as I had to perform a shutdown or restart for me to connect online again.
I would remove my stored connection, reconnect back to the same network and made sure my password was correct, and see the "acquiring network" message for over a minute. Then I would be left with "limited connection".
I tried to reinstall the drivers to my wireless card multiple times (using the ones provided by Lenovo) but the problem would persist. My next step would be to try any newer drivers from Intel, but I decided to perform a System Update to see what would happen.
I just finished updating my BIOS and video card drivers, along with a few other listed items (such as Intel Matrix Driver, etc. I don't remember the others) and now it seems to be working fine. Hopefully it stays this way.
I hope this serves to help others with a similar problem, although I didn't list anything more specific than to update the BIOS to 2.13.
Posted: Wed Sep 12, 2007 9:15 am
by ronny
I had this problem too. Cant say what did it, but i updated bios and reinstalled vista WITHOUT lenovo connection manager. Maybe the bios was at fault, maybe there was a conflict between windows and connection manager, maybe something else. Fact is, tho, i havent had this problem even once since i reinstalled.
