10.4.6 - waking from sleep - never fully wakes

Recently upgraded to 10.4.6 and been having some weird things happen since the upgrade.
Whenever my PowerBook G4 sleeps and I return back to work - sometimes it never wakes and the screen remains black.
or
It begins to awaken and runs very slow. The computer appears to still be responding, but any apps that I try to run will begin to start up then never finish. The spinning ball is all that I get. The computer is not locked up as I can move the mouse all around, etc...
Any thoughts?
I have read most of the posts on sleep issues, but nothing quite like this one...
Thanks!
Tim

If your Mac happily goes to sleep but won't wake up--Hold down the power switch to force-reboot your machine and get it running again.
Don't worry-your Mac isn't narcoleptic. Its Open Firmware system or NVRAM (nonvolatile RAM) is likely corrupt, and your Mac can't remember how to wake up.
Restart your Mac and immediately hold down the Command-Option-O-F key combo until you see a somewhat intimidating command-line display that ends with the Open Fimware prompt. Type the following line:
reset-all
press Return
Your Mac will reboot. Once it's running, put it back to sleep to test. If the problem recurs your Energy Saver preferences may be the culprit. Delete the com.apple.PowerManagement.plist file (go to Finder/Hard drive/Library/Preferences/SystemConfiguration)--don't worry, your Mac will regenerate a new one--and then restart to see if that rights the wrong.
Still did'nt work? Might be time to call AppleCare or see an Apple Genius or a technician.
Cheers!
DALE

Similar Messages

  • Logic Pro X inaccessible after waking from sleep when using an MCU Control Surface

    I'm having a problem I cannot seem to get around without force quitting Logic every time.  If I have a Control Surface setup as a Mackie Control (v1.0); and if the computer goes to sleep, and then i turn off the controller while the computer is asleep (for any reason), and then wake the computer without turning on the controller first, Logic becomes completely unusable and must be force quit.
    My controller in this example is Solid State Logic's Nucleus controller, however it happens with other Mackie Control compatible controllers (i have another one i tested against), BUT not a real Mackie Controller sold by Mackie (i tested with that as well); more details below.
    For the SSL controller, Logic automatically sets it up like this:
    Now if the computer goes to sleep, and i wake it up, i get the following dialog, which is fine:
    After clicking on "Continue" button or hitting the enter key, Logic is rendered useless, as if there is a modal dialog still open somewhere.  Clicking anywhere on the gui results in white flashes and nothing else.  doing cmd+Q to quit actually makes it try to quit (a save dialog appears), but it never does successfully quit, making me resort to force-quitting.  For an example, here's a pic of the file menu at this point:
    I also have a regular Mackie Control Unit (MCU Pro) and the strange thing is with that unit, everything works fine after sleep, turning off controller, and re-awakening.  However, there is a difference in what kind of dialog is displayed after the sleep, which probably has something to do with this issue.
    Here is the setup screen of the MCU Pro:
    And here is the dialog for the missing ports after waking from sleep:
    This dialog is completely different than the other control surface's missing ports dialog.  When clicking on "Keep unassigned" here, Logic resumes working fine.
    The project is as minimal as possible; nothing is loaded, all that's there is an empty instrument track and a Control Surface configured.
    I'm using a Mac Mini (late 2012)
    Processor  2,6 GHz Intel Core i7
    Memory  16 GB 1600 MHz DDR3
    Graphics  Intel HD Graphics 4000
    Software  OS X 10.9.4 (13E28)
    with Logic Pro X 10.0.7
    Any help would be greatly appreciated!!

    Did you ever figure out a solution to this problem?
    I just pulled out my original Emagic Logic Control (MIDI) and I have having the same problem.

  • My MBP doesn't remember my Time Capsule wireless network when waking from sleep

    My MBP (OS 10.5.8) doesn't remember my Time Capsule wireless network when waking from sleep.  Thus, every time my MBP wakes from sleep, I need to select the Airport icon in the upper menu bar, select "Join other network", enter SSID and password.  This is very cumbersome.  And, I never had this problem when I was using the ISP's provided wireless router/gateway/DSL modem. Adding the Time Capsule and using it to generate the wireless network has introduced this problem. 
    It appears that this problem has to do with the hidden SSID.  I don't need the lecture on how hidden SSID provides no serious security benefit.  That's why I have the WPA2 encryption.  I'm interested in a solution that will allow the Time Capsule to generate the wireless network, maintain a hidden SSID, continue to use WPA2 encryption, but have my MBP recognzie and autoconnect to this network.
    Solutions I've alread tried:
    1. Open Network Preferences
    2. Select Airport from left hand column (and ensure Airport is at top of that list)
    3.  Select Advanced
    4.  Delete all Preferred Networks.
    5.  Apply settings.
    6.  Restart computer
    7.  Return to Network Preferences and from Advanced page, manually add my network with hidden SSID and WPA2 password
    This solution works fine as long as I don't take my computer elsewhere and connect to another network.  As soon as my preferred networks list gets another network, my MBP stops finding my TC network.  Since I take my laptop to a lot of places (it's a laptop, after all...) this is a problem.
    As I say, prior to adding the TC on my network (and using it to generate the wireless network), my MBP had no problem keeping 50+ preferred network names/passwords in the Preferred Network list, but always automatically finding/connecting to my home network without the need to "Join other network."  Thus, I assume the problem lies with the Time Capsule.
    Any ideas?

    LaPastenague, thanks for weighing in.  Didn't know that the hidden SSID capability was not IEEE standardized, and thus different devices will handle hidden SSID differently.  With my admittedly limited knowledge of how SSID/hidden SSID works, I'm still a little confused as to why my MBP would remember the generic router/gateway's hidden network, but struggle with the TC's hidden network.
    To my knowledge, when an SSID is broadcast by a base station (Airport, wireless gateway, etc.), a connecting device (like a laptop, iPad, etc.) detects this broadcast--this would be a passive reception of this SSID signal.
    When an SSID is hidden, the base station does not broadcast its identification.  Rather, a connecting device must transmit the name, and when the base station recognizes the broadcast, the connection is made. That's what you do when you select "Join another network" and manually enter the SSID.
    The idea with OS X's Network Preferences is that these steps, whether for hidden networks or broadcast SSIDs, become automated.
    Where is the potential for a different chipset between the TC and the previously used wireless router/gateway to alter this functionality?  Shouldn't the selection of an SSID by the MBP to broadcast to seek for a base station be a function solely on the MBP?  And once broadcast by the MBP, the TC should detect and reply? 
    Basically, the MBP can connect to the hidden TC manually just fine.  The MBP can connect to the old setup automatically just fine.  The MBP cannot connect to the TC automatically.  Aren't these automatic connection functions solely on the MBP?
    I'll try un-hiding the network and re-verifying that the problem is exclusively with the hidden network.
    Z

  • Leopard forgets color profiles when waking from sleep on MBP Santa Rosa

    I have a 15" MBP Santa Rosa with a 22" Samsung external monitor. I performed a clean (erase and) install on my machine. Upon waking from sleep, the computer seems to have forgotten the color profiles loaded for the displays. To correct this, I open system preferences and then the display option. As soon as the display options are shown on the window, my MBP loads the correct profile. This has happened for both displays, though far more frequently on the external display. The profile for my Samsung was created using color calibration hardware/software but the MBP display is running the stock profile from Leopard.
    Any thoughts? Has anyone else experienced this?

    same issue here. also had it in tiger, but much more frequently in leopard. seems to be whenever my display wakes from sleep.
    MBP 2.4 GHz SR purchased 6/07. also driving samsung 245bw external display (which has never been affected, unless perhaps my calibrated and default profiles aren't different enough for me to notice--the difference is severe on my built-in display).
    console contains this:
    2/26/08 4:56:33 PM [[0x0-0xaf0af]].com.apple.systempreferences[[4593]] objc[[4593]]: Class O3Panel is implemented in both /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/Con trast.monitorPanel/Contents/MacOS/Contrast and /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/Geo metry.monitorPanel/Contents/MacOS/Geometry. Using implementation from /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/Geo metry.monitorPanel/Contents/MacOS/Geometry.
    2/26/08 4:56:33 PM [[0x0-0xaf0af]].com.apple.systempreferences[[4593]] objc[[4593]]: Class O3Panel is implemented in both /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/Geo metry.monitorPanel/Contents/MacOS/Geometry and /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/VPT .monitorPanel/Contents/MacOS/VPT. Using implementation from /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/VPT .monitorPanel/Contents/MacOS/VPT.
    2/26/08 4:56:33 PM [[0x0-0xaf0af]].com.apple.systempreferences[[4593]] objc[[4593]]: Class O3Panel is implemented in both /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/VPT .monitorPanel/Contents/MacOS/VPT and /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/Bez el.monitorPanel/Contents/MacOS/Bezel. Using implementation from /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/Bez el.monitorPanel/Contents/MacOS/Bezel.
    2/26/08 4:56:33 PM [[0x0-0xaf0af]].com.apple.systempreferences[[4593]] objc[[4593]]: Class O3Panel is implemented in both /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/Bez el.monitorPanel/Contents/MacOS/Bezel and /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/Ext endedTouchSwitch.monitorPanel/Contents/MacOS/ExtendedTouchSwitch. Using implementation from /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/Ext endedTouchSwitch.monitorPanel/Contents/MacOS/ExtendedTouchSwitch.
    2/26/08 4:56:33 PM [[0x0-0xaf0af]].com.apple.systempreferences[[4593]] objc[[4593]]: Class O3Panel is implemented in both /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/Ext endedTouchSwitch.monitorPanel/Contents/MacOS/ExtendedTouchSwitch and /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/Pow erMode.monitorPanel/Contents/MacOS/PowerMode. Using implementation from /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/Pow erMode.monitorPanel/Contents/MacOS/PowerMode.
    2/26/08 4:56:33 PM [[0x0-0xaf0af]].com.apple.systempreferences[[4593]] objc[[4593]]: Class O3Panel is implemented in both /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/Pow erMode.monitorPanel/Contents/MacOS/PowerMode and /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/Aut horization.monitorPanel/Contents/MacOS/Authorization. Using implementation from /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/Aut horization.monitorPanel/Contents/MacOS/Authorization.
    2/26/08 4:56:33 PM [[0x0-0xaf0af]].com.apple.systempreferences[[4593]] objc[[4593]]: Class O3Panel is implemented in both /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/Aut horization.monitorPanel/Contents/MacOS/Authorization and /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/TVO ptions.monitorPanel/Contents/MacOS/TVOptions. Using implementation from /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/TVO ptions.monitorPanel/Contents/MacOS/TVOptions.
    Message was edited by: thomas jerde

  • Mac Pro restarts when waking from sleep

    Hi everyone.
    I just got a brand new Mac Pro (2 x 2.66GHz), and had Apple upgrade the RAM to 2GB (4 x 512MB). My first problem is that the computer always restarts when waking from sleep, which is annoying! I have reset the SMC by unplugging the machine for a minite, but the problem persists. I have also tried sleeping the computer with nothing plugged in except the monitor and keyboard/mouse, but I get the same problem. All software/firmware is fully up to date.
    I have also just noticed that the System Profiler states that there is only 1GB RAM in the computer, even though I am sure that it recognised 2GB when I got the machine a fortnight ago (I even have a screen shot of 'about this mac' to prove it!). Can anybody help, or do I need to phone Apple support?
    Thanks,
    Matthew

    I have a similar problem - hard restart when closing the lid to put it to sleep. It looks like there is a bluetooth issue(?), but I'm not sure what to do with it. We don't have any blue tooth devices in our house. From the console log:
    Jan 5 14:57:49 Rigpa kernel[0]: System SafeSleep
    Jan 5 14:57:49 Rigpa mDNSResponder: Adding browse domain local.
    Jan 5 14:57:49 Rigpa kernel[0]: hibernatepage_listsetall start
    Jan 5 14:57:49 Rigpa kernel[0]: hibernatepage_listsetall time: 51 ms
    Jan 5 14:57:49 Rigpa kernel[0]: pages 93229, wire 29477, act 34496, inact 2520, zf 1141, could discard act 9830 inact 15765
    Jan 5 14:57:49 Rigpa kernel[0]: hibernatepage_listsetall found pageCount 93229
    Jan 5 14:57:49 Rigpa kernel[0]: IOHibernatePollerOpen, mlget_interruptsenabled 0
    Jan 5 14:57:49 Rigpa kernel[0]: IOHibernatePollerOpen(0)
    Jan 5 14:57:49 Rigpa kernel[0]: writing 92989 pages
    Jan 5 14:57:49 Rigpa kernel[0]: image1Size 41692160
    Jan 5 14:57:49 Rigpa kernel[0]: all time: 5774 ms, comp time: 437 ms, deco time: 0 ms,
    Jan 5 14:57:49 Rigpa kernel[0]: image 159194624, uncompressed 276045824 (67394), compressed 158654492 (57%), sum1 529d572d, sum2 c6e9eed5
    Jan 5 14:57:49 Rigpa kernel[0]: hibernatewriteimage done(0)
    Jan 5 14:57:49 Rigpa kernel[0]: sleep
    Jan 5 14:57:49 Rigpa kernel[0]: Enabling XMM register save/restore and SSE/SSE2 opcodes
    Jan 5 14:57:49 Rigpa kernel[0]: Started CPU 01
    Jan 5 14:57:49 Rigpa kernel[0]: IOBluetoothHCIController::restartShutdownWL this is a wake from sleep
    Jan 5 14:57:49 Rigpa kernel[0]: System Wake
    Jan 5 14:57:52 Rigpa mDNSResponder: Repeated transitions for interface lo0 (127.0.0.1); delaying packets by 5 seconds
    Jan 5 14:57:53 Rigpa configd35: posting notification com.apple.system.config.network_change
    Jan 5 14:57:53 Rigpa lookupd185: lookupd (version 369.6) starting - Sat Jan 5 14:57:53 2008

  • Mac Mini WiFi (airport) fails after waking from sleep

    I recently bought a Mac Mini (Mid 2010 model)...my first Apple computer since my dearly departed IIe.  I've been having repeated intermittent issues with the WiFi on this machine.
    Owning it for two weeks, then one day it woke from sleep, and decided it no longer knew the password to my wireless network.  With everything else in my house on wireless, I knew that the password had not been changed (I am using WPA2).  Every time I would retype the password, I would get either a 'Connection Timeout' error, or an 'Incorrect Password' error.  Every once in a while it would connect, but it would not get a valid IP.
    Restarted the system, and then it tells me there's 'No Airport Card Installed'
    Reset PMU/SMU/PRAM (etc) and the airport card comes back, but it STILL will not connect.
    I go into keychain, and delete the saved wireless password.
    I create a new 'location'.
    No go.
    So I made a trip with my machine to the Genius bar at my local apple store.  Miracle of miracles, it WORKS PERFECTLY from the moment they turn it on. Get it home, it continues to work perfectly.  This was Saturday.
    This morning, same problem starts again.  I was having similar issues with my iPad not connecting to the WiFi when waking from sleep, but this was fixed when I factory reset the iPad.  I've never experienced this issue with either of my iPod touches (3rd and 4th gen).  I'm not having any wireless problems with my PS3, Wii, Blu-ray player, Android phone, Nook, HP Printer, or Windows laptop. 
    My router is a D-link F5D8235-4 v2000, with firmware 2.01.09 (latest available)

    Hi, this has worked for a few...
    Make a New Location, Using network locations in Mac OS X ...
    http://support.apple.com/kb/HT2712
    10.7 & 10.8…
    System Preferences>Network, top of window>Locations>Edit Locations, little plus icon, give it a name.
    10.5.x/10.6.x/10.7.x instructions...
    System Preferences>Network, click on the little gear at the bottom next to the + & - icons, (unlock lock first if locked), choose Set Service Order.
    The interface that connects to the Internet should be dragged to the top of the list.
    10.4 instructions...
    Is that Interface dragged to the top of Network>Show:>Network Port Configurations.
    If using Wifi/Airport...
    Instead of joining your Network from the list, click the WiFi icon at the top, and click join other network. Fill in everything as needed.
    For 10.5/10.6/10.7/10.8, System Preferences>Network, unlock the lock if need be, highlight the Interface you use to connect to Internet, click on the advanced button, click on the DNS tab, click on the little plus icon, then add these numbers...
    208.67.222.222
    208.67.220.220
    Click OK.

  • Macbook Air 2014 Black Screen w cursor after waking from sleep.

    I just purchased a brand new macbook air this past week. I noticed within the first day of using that if my machine went into sleep mode, and I hit a key to take it out of sleep mode, it would go to a black screen with my cursor for about 30 seconds.
    It does not do it every time but enough that it is annoying. I am coming from a mid 2011 mac air that did not have any issues. (only replaced for all day battery)
    Do you think this a hardware or software issue? If i swap this mac out do you think I will just encounter the same thing?
    I have read numerous posts regarding waking from sleep issues but they all seem to be affecting MacBooks purchased between 2012 and 2013.
    Any help would be much appreciated.
    Nick

    UPDATE:
    I called apple tech support and after talking a bit decided best course of action was to replace the macbook air as I was inside my 14 day buyers remorse.
    I came home and hoped all was well when this one began doing the same thing. I made an appt with the genius bar to dive further in to this and we did a complete wipe on the computer and reinstalled the OS. The "genius" said I'm probably bringing something over from my previous mac air. (even though it never had this issue).
    So after completely reinstalling the OS and setting up my macbook as new I pretty much lost all my settings and what not accumulated after 3 years with my previous mac. They did use Time Machine to at least bring my iPhoto library over and iTunes music.
    It has been exactly one day since this was completed and the computer is doing the exact same thing. ***!!!

  • Noisy CDRW when waking from sleep

    I see there is a firmware update if I have a superdrive to make the drive quiet when waking from sleep.
    http://support.apple.com/kb/HT3744
    Thanks,
    Joe

    Getting this same error since switching from Firewire to USB. I have a Maxtor drive in an Adaptec enclosure. It has it's own power supply and both USB and Firewire 400 connections. Just upgraded to a new Mini from old Powerbook, so no more Firewire 400!
    The big difference between USB and FW:
    With the old PB G4 and Firewire, when I put it to sleep, I could hear the external drive actually spin down. On wake up, It would spin up and mount properly. Now with the Mini and USB, when I sleep the Mini, the external drive NEVER SPINS DOWN. I did some research and found that many drives have built-in power management that basically powers them down after some idle time. So the Mini is going to sleep with mounted drives, at some point later the drive sleeps itself, then when the Mini wakes, the drive's not there.
    Obviously, Firewire is doing a better job of talking to my external than USB. I'm ordering a FW400-to-800 cable and will test this. I also think it has something to do with the chipset/firmware in the external enclosure, as many people are reporting their external USBs behave properly during sleep.

  • Freeze when waking from sleep since 10.4.11

    Ever since updating to 10.4.11, My MBP locks up upon waking from sleep. It's the same problem I've had for months. The screen freezes and I get a spinning beach ball and the hard drive clicks. It usually happens when scrolling web pages in Safari, but it also happens at other times, but not as frequently. It happens a second time and the entire system seizes up. No crash log is generated. Anyone else seeing this?

    I ran AHT and TechTool Deluxe 3.1.1 again and both reported no hard drive problems. I'm fully backed up and I'm calling Apple Care tomorrow. I'm concerned because I have one of the problematic Seagate hard drives; serial number and firmware match the troublemakers. Back over the summer, I called Apple Care about this and they suggested I rename my existing ~/Library/Preferences folder and restart to create all new pref files. This seemed to work for about two-three weeks.

  • When waking from sleep getting "Device Removal" error on Lacie external

    When waking from sleep getting "Device Removal" error on Lacie external drive. This drive is my Time Machine back-up and I don't want to lose it. I don't know if anyone else has seen this error. Let me know.

    Getting this same error since switching from Firewire to USB. I have a Maxtor drive in an Adaptec enclosure. It has it's own power supply and both USB and Firewire 400 connections. Just upgraded to a new Mini from old Powerbook, so no more Firewire 400!
    The big difference between USB and FW:
    With the old PB G4 and Firewire, when I put it to sleep, I could hear the external drive actually spin down. On wake up, It would spin up and mount properly. Now with the Mini and USB, when I sleep the Mini, the external drive NEVER SPINS DOWN. I did some research and found that many drives have built-in power management that basically powers them down after some idle time. So the Mini is going to sleep with mounted drives, at some point later the drive sleeps itself, then when the Mini wakes, the drive's not there.
    Obviously, Firewire is doing a better job of talking to my external than USB. I'm ordering a FW400-to-800 cable and will test this. I also think it has something to do with the chipset/firmware in the external enclosure, as many people are reporting their external USBs behave properly during sleep.

  • Trackpad Jerky or Unresponsive when waking from sleep

    I've been having a problem with my trackpad being extremely jerky and unresponsive when it is waking up from sleep. I am a new mac user and I've only had my macbook pro since christmas and this problem is really getting annoying. Twice, I've had to just push the power button and press enter so my notebook would shut down and I could restart. Any Ideas?

    First, when waking from sleep, MBP requires a little to get up to speed as it wakes if properly put to sleep. The MBP does hibernate and write to the hard disc when sleeping and this takes some time as does reading back. The book will be viewable immediately on waking but can seem laggard while fully getting up to speed from hibernation. Do not try to wake the computer until the little wake/sleep light has begun pulsing. Two, if you have a usb connection going or an expresscard inserted ... ensure that it lets the computer wake/sleep properly. Before sleeping the 'book, power off the connected items so that they do not interfere with the process.
    What connections do you use? and what processes are going when you attempt to sleep the computer?
    Use the Activity Monitor and the Console to check what is happening. Both the Console Log and the System Log in the console can provide you with info regarding your problems. Check the logs and post problematic entries here if you cannot interpret them yourself.
    Message was edited by: Rhyd

  • Losing Displays Color setting when waking from sleep

    Hey y'all!
    I haven't seen this specific problem addressed anywhere in the forums - I have a Pismo 500 running 10.3.9. The problem is that when I wake the Pismo from sleep, nine times out of ten, it defaults to the uncalibrated display space. If I open the Prefs pane, the Displays>Color tab shows the correct calibrated profile selected, but the colors and such are way off. If I just click on the selected profile, it goes back to that profile correctly - but that's too many mouse clicks just to see correctly after waking!
    The confusing thing is that this problem never shows up during starts/restarts - during the boot process, the Pismo correctly applies the selected profile and the change is noticable (my display is natively WAAAAY too blue/cyan for my tastes and line of work). So it works from a standing start, and from a warm reboot, just not waking from sleep.
    The problem didn't manifest until after I moved from 10.2.x to 10.3, but that move solved so many other problems, I'm still happy I did it.
    Any thoughts?

    Hi,
    I do have a work around this problem.
    Go to mac hd, to users, to what looks like a house, to library, to colorsync, to profiles. Open profiles and take that profile and put it on the desktop.
    Next go to mac hd, to library, to colorsync, to profiles, to displays.
    Open displays and place the profile on the desktop in the there.
    That solved my problem.
    emac   Mac OS X (10.3.9)   Combodrive, SN G84162YCQJB

  • After waking from sleep, my iMac (Lion) is unresponsive.  The mouse moves, but when I click things it won't open them.

    After waking from sleep, my iMac (Lion) is unresponsive.  The mouse moves, but when I click things it won't open them.
    This has happened EVERY time the iMac goes to sleep for the last few days.. the only way I have found to resolve the issue is to manually restart the computer each time via the button on the back of the iMac.
    Any and all help is appreciated!
    Thanks

    FWIW, I never sleep my machines or their HDs, just their displays and never have an issue waking up the displays, usually run 24/7. Give that a shot.

  • IMac G5 Dies When Waking From Sleep

    I have a Rev A iMac G5 I bought in 2004. Recently it started doing some weird stuff when waking from sleep. After looking at some of the other posts, I think this is going to be repetitive, but I thought I would see if anyone had any suggestions
    After either putting the computer to sleep or letting it go to sleep, it will frequently die after the mouse has been clicked to wake it up. I have tried resetting both the SMU and PRAM as well as repairing disk permissions and repairing the disk. None of this has seemed to help. Occasionally, I get lucky and am able to wake it from sleep normally, but this doesn't happen often. After it dies following the mouse click, I can unplug it and then plug it back in and it will start up normally. Interestingly, it will start up from shutdown normally as well as restart normally. Additionally, as long as it doesn't go to sleep, I think you can typically use it as long as you want and it won't quit.
    Today, I took the back cover off and messed around with it for awhile. The diagnostic LED behavior seems odd to me. LED #1 comes on when it is plugged into the outlet. When following Apple's instructions for troubleshooting a computer that won't start up, mine does fine because as I said it will start up normally if you unplug it and then plug it back in. Because of this, I set my computer to go to sleep quickly with inactivity. Although it did wake normally at least once, it died numerous times. The irregularity seems to occur with LED #2. One time it "died", I believe LED #2 actually remained lit and something seemed to still be working based on noise. However, the green light for the "caps lock" button wouldn't come on. Other times LED #2 would go out when it died after pushing the mouse with it asleep. During these times, I could push the internal power button and LED #2 would briefly light up, but nothing more than that would happen. On more than one occasion I would then push the SMU reset button and then push the internal power button again at which point LED #2 would fail to come on at all. After pushing the power button (and occasionally pushing the SMU button again) what seemed to be a random number of times, the computer would all the sudden start up normally again.
    My top 3 guesses are a failed power supply, failed logic board, or exhausted PRAM battery (I have never changed it). The first two may be a bit to pricey for me to consider replacing. If they are the problem, I may just settle for setting the computer to never sleep. Does this sound like it could be caused by the PRAM battery going out?
    Any advice would be greatly appreciated!
    Message was edited by: Joshua213

    My bad on not reporting back sooner. Indeed, replacing the PRAM battery did not fix the problem. The situation seems odd to me as I was able to sometimes wake the computer from sleep without it quitting while others times it dies. It does fine as long as it doesn't go to sleep. I can start it up and shut it down with no problems; additionally, it appears to do fine even when left on for long periods of time as long as it doesn't go to sleep. To be correct it doesn't seem to so much be the state of "sleeping", but the act of trying to wake it up from sleep. I don't think ventilation is a problem.
    What I have done is just set it to not sleep. We just shut it down once in awhile. Rather than forking out the money, I think I will just use this work around as long as it continues to work.

  • Connection problems after waking from sleep????

    I'm having a strange issue with my 2012 Macbook Pro running OSx v10.8. I take my computer with me between home and school, and I usually just put it to sleep during the commute. For the last few weeks, when I got to school and woke up my MBP, it wouldn't connect to the internet. It recognized the WiFi connection, but did not assign a valid IP address. It was only when I shut the computer down and rebooted it that I was able to connect. Strangely, when I got home, I had no problem connecting to my home network, even after waking up from sleep.
    After a little while of this, it got worse. Now, even after re-starting, I am unable to connect at school. (WiFi icon shows exclamation point). This is also true for my home network.
    Here's the kicker. When I log out of my default account and log into the guest account, I have no trouble either in school or at home. Waking from sleep is never a problem and I connect everywhere. However, as soon as I log back into my other account, I lose connectivity.
    I have tried renewing my DHCP lease, or manually inputting an address, but neither of these have worked. I have resorted to using the guest account, and I want access to my old files again without having to switch back and forth.
    If anyone has any input on this, it would be greatly appreciated!! Feel free to e-mail me at [email protected]
    Thanks!

    same issue here..
    reset my network settings and reset phone a billion times already, same issue still occur. sometimes the phone will wake up with wifi and sometimes it will go to 3g, one time it went to GPRS, its just really bizarre. If i open safari it will ask if i want to join the network that i originally set up, but when i select the network it just says "unable to connect". If i just leave the phone be for a couple hours and wake it up again, it will rejoin the wifi network.
    I use remote to control my music library, but if my phone goes to sleep, it won't reconnect again so it's basically useless.
    BIZARRRRRE, driving me crazy..

Maybe you are looking for