08-01-2011 12:21 PM - edited 08-01-2011 12:49 PM
Mine BIOS is latest 1.38.
I have try
(osfh02ww.exe) and put "USBPMon.reg".
Shut down lap and restart from cold boot-and this worked for me!
This is Windows 7 also fix (AFAIK).
And of course have hiberfil.sys enabled "powercfg -h on".
All looks that sleep on W510 is not really working but hibernation way of sleep does. I'd like to be this confirmed from Lenovo.
Hope this helps!
08-02-2011 10:08 AM - edited 08-02-2011 11:26 AM
Just to say that I have installed (nuked as you say) formated HDD with Win 2008 R2 x64 Sp1 included.
And the problem persisits from the first moment.
When I say problems I mean sleep is not clear sleep but run through hybernate and this is not sleep as I used to have on mine previous laptop
08-24-2011 12:56 AM
Just to add that I have this same problem, but dont think its a Windows issue as Im running Ubuntu 11.04
Hibernate seems to work well, but cannot wake up from suspend.
08-24-2011 02:35 AM
08-25-2011 04:12 AM
With all due respect, James, this is old business. And it's ridiculous to suggest the cause is DIMMS or SIMMS not being properly seated when this was a brand new machine shipped from Lenovo. There's an old saying in the USA "when you hear hoof-beats in Texas, don't look for zebras" and that certainly applies here. My problem has been all but solved by totally nuking the hard drive and eliminating all the crap and bloatware that Lenovo installs. I did a *clean* installation of Windows 7 Enterprise and let Windows install as many of the drivers as possible. I only used Lenovo stuff when there was no other choice. I will occasionally get the blinking light issue, but only every 4-5 months. The problem is obivously related (at least the majority of it) to the junk that Lenovo installs.
08-25-2011 06:43 AM
No, I'm not looking for Zebras, but there are plenty of antelope and swine in Texas and they have hooves also so what say we keep an open mind here?
Reseating ram is a viable suggestion, in all your years of owning Thinkpads, you never had a bad ram chip? Or a bit of dust on a ram contact? These machines bounce around on a truck getting to the customer, you don't think that maybe a ram chip could've moved a bit? Hibernation is directly related to the ram.
Not once in this thread has anybody said anything about whether they had hybrid sleep enabled or not. Hybrid sleep makes sleep act like hibernate. It writes to ram.
The problem with windows is that there are power settings everywhere, especially in windows 7. Changing one and not changing the rest won't work. You have to change them all, the problem is finding them all.
If you can't get the settings in Lenovo's power manager working in concert with windows power manager, by all means, get rid of it. But what works for you doesn't neccesarily mean that it will work for anybody else. Some people like Lenovo's so called bloatware.
JameZ is here helping out trying to solve problems and we all try the obvious things first. We're all volunteers here and without the staff and employees coming in here helping, you all would be on your own.
All I'm saying is don't be so quick to dismiss advice that's given, we have to start somewhere and reseating ram is always going to be the first thing to try concerning hibernation. If that doesn't work, then we go to the power settings. A solution comes about from procedure, one step at a time, you of all people, with your experience should know that.
And yeh, there are zebras in Texas
09-01-2011 10:30 AM
@ JameZ - I removed the 2x2GB sticks of third party RAM (though it was IBM supplied), leaving only the single 4GB stick installed, in Slot 0. Reseated to be sure. The problem persists.
@topmahof - I'm seeing this on Ubunti 11.04, so I can safely rule out Windows power settings.
09-01-2011 11:02 AM
I rest my case! The volatile memory SIMMS/DIMMS not being seated is not a problem. That's easy enough to check without popping the hood. How irritated would you be if you were a newby and static-zapped a memory module in the process of following JameZ suggestion. If you know what you are supposed to have installed and it's not displayed in sysinfo, then it *could* be an issue. However, on my laptop, the sysinfo agreed with what was supposed to be there. No reason to mess with pulling stuff apart.
I'm curious about the Linux (Ubuntu) problem as I'm not all that familiar with Linux. Are you running a VM or did you nuke the HD and do a clean install? If running a VM, you could still be at the mercy of whatever Lenovo sticks on the machine prior to shipment. I still think the problem is related to Lenovo bloatware. Since nuking the HD and doing a clean, plain Jane installation of Win7 Enterprise, I've seen only rare (knock on wood) instances of blinking light. I will freely admit Windoze sleep/hibernation has always been a bit dodgy, but I think much of the current problem is related to Lenovo OEM config. They should not be ignoring this although it seems there is an out-of-sight, out-of-mind mentality involved. I do tech support and training for a SoCal software company, so I am well aware of the "scripted approach" which the VIPs/support folks must follow. It's almost always frustrating to deal with them since you don't know if they have MS certifications or have OJT training.
09-02-2011 05:04 AM
I rarely see the problem any longer, but when I do, it seems it's related to trying to bring back from sleep after plugging in a USB device. Haven't been able to replicate, however. I still maintain stripping all the OEM additions and letting Windows install the drivers when necessary seems to all but solve the problem. The loose RAM thing just doesn't wash. I carried my W510 on a 4200+ mile Harley trip in August. Certain enough "jarring" to loose RAM if it was going to happen. No problems.