Okay, guys.. I'm going to maybe sound a bit daft here.. but have any of you fiddled with your Energy Saver control panel settings and changed the timer that sets sleep more than once between booting up? For some reason, you can only set the sleep timer ONCE between boot ups. More than once, and it starts to act up and DOES cause problems - it gave me fits with my beige G3 running under Panther until I fingered it out.
Also, do you have your systems set to sleep the disk drives whenever possible?
The thought occurs - and this happened a lot to me on my beige, that if I had the unit sleep (either by setting it manually, or letting the timer do it) when the hard drive was already sleeping, it would crash on the wake. THAT was a never fail thing. Now that I had/have the beige running an XPostFacto install of Panther - and what with it being unsupported and all, I put it down to that.
But reading here, I'm thinking that in some instances, there may be a similar thing going on with your new machines - look at what the complaints are tied to.. hard drives and displays and sleep and all THREE are controlled by the Energy Saver control panel in one way or another. It does access the hardware in a different mode than the manual sleep and may be conflicting.
The fact that I can see it reported by a few that sleep running under Windows works is a BIG 'heads up' for me. My bet is a software/firmware clash.
Then again, I may just be blowing smoke in the air here.. but I'm feeling a bit chuffed that I managed to get the problem nailed for another gent who had the same sleep issue with his MacPro that I have - and the solution that I suggested works for my beige!
I have NO idea if this will help any of you, but check in your Energy Saver settings - un-check the hard drive sleep, set the display sleep timer and CPU sleep timer to never sleep, then reboot.
Use ONLY the manual sleep that you set from the menu bar and see if your system sleeps then wakes w/o problems.
If you need to have the machine sleep after a few minutes or hours of inactivity - set the timer only ONCE (between reboots) and see if that holds.
Could someone try this and see what happens? I'd be interested to know what results, if any, people have. It may work, stupid as it sounds.
Deb.