2006 Mac Pro - wakes from sleep after 3-5 seconds

Folks, I have a 2006 Mac Pro (2.66 x 2-core) that refuses to stay asleep. The system.log shows this:
Dec 17 12:40:40 Mac-Pro-Wired-1 kernel[0]: System Sleep
Dec 17 12:40:44 Mac-Pro-Wired-1 kernel[0]: Wake reason = UHC2
Dec 17 12:40:44 Mac-Pro-Wired-1 kernel[0]: System Wake
Dec 17 12:40:44 Mac-Pro-Wired-1 kernel[0]: USB (UHCI):Port 2 on bus 0x3d has remote wakeup from some device
OK, so it's a USB device that's keeping the computer from sleeping. According to System Profiler, here is what is on bus 0x3d - Apple wired keyboard (the white one) and a Logitech MX518 gaming mouse is plugged into the USB port on the keyboard.
USB Bus:
Host Controller Location: Built In USB
Host Controller Driver: AppleUSBUHCI
PCI Device ID: 0x2689
PCI Revision ID: 0x0009
PCI Vendor ID: 0x8086
Bus Number: 0x3d
Hub in Apple Pro Keyboard:
Product ID: 0x1003
Vendor ID: 0x05ac (Apple Inc.)
Version: 4.10
Speed: Up to 12 Mb/sec
Manufacturer: Mitsumi Electric
Location ID: 0x3d200000
Current Available (mA): 500
Current Required (mA): 50
USB-PS/2 Optical Mouse:
Product ID: 0xc01e
Vendor ID: 0x046d (Logitech Inc.)
Version: 22.00
Speed: Up to 1.5 Mb/sec
Manufacturer: Logitech
Location ID: 0x3d210000
Current Available (mA): 100
Current Required (mA): 98
Apple Pro Keyboard:
Product ID: 0x020b
Vendor ID: 0x05ac (Apple Inc.)
Version: 4.10
Speed: Up to 12 Mb/sec
Manufacturer: Mitsumi Electric
Location ID: 0x3d230000
Current Available (mA): 250
Current Required (mA): 50
Is the keyboard on port 2, or is it the mouse?
If I unplug the mouse and use the keyboard to place the computer into sleep mode (Option + Command + Eject), the same thing happens. It appears the wake is coming from the keyboard or the keyboard's built-in hub.
I have:
- installed update 10.5.6 using the downloaded combo update.
- reset the SMC (a few times)
- reset PRAM
- repair permissions
and no dice!
I could sure use some help figuring this out.
Thanks...

The sleep feature hardly works on Macs if at all. I had that same issue while on Tiger. Same thing. Mine was a PCI card that would awake it after a period of time. I have had issues with it NOT going to sleep also due to a PCI card and USB hub. I even disconnected everything and had gone back to stock and that still did not resolve it without having to reset the power management controller in Terminal. That was how I got it to work again on my old PPC machine.
One test to try is to disconnect all the USB gear including the hub and let the machine go into sleep on it's own. If it wakes up- it's not related to USB but probably an internal timer that is out of whack or a PCI based issue.
I had so many issues way back in 2004 that I finally gave up and just set it to never sleep. I have never had any issues after that! LOL
So, getting back to the timer deal. There are times when the internal timer in the power management portion of OS X and it can actually flip to a wake command. Best thing to do in your case is to go in and trash the plist file for power management and restart. That should help in that case. If it doesn't make a bit of difference and the issues persist, then there's something other than that going on.

Similar Messages

  • Time Machine turns itself on after my Mac Pro wakes from sleep (every time)

    Hi,
    I have a 2009 Mac Pro and it currently has Lion on it (10.7.4), but the problem I am about to explain started when the machine was running Snow Leopard, so it doesn't appear to be an OS-specific issue.
    I do not currently use Time Machine, I use Carbon Copy Cloner and some online backup solutions to handle backups. I did use Time Machine for a short time on this machine just after it was introduced, but I didn't end up using it for long and the external drive I used for the backups is no longer in service.
    The problem is this:
    I have Time Machine off and I have all of my drives (I have 4 drives in my Mac and an external drive) set not to be backed up for good measure. Time Machine will stay off like it should except in one instance. If I put my machine to sleep, when my Mac wakes, Time Machine is instantly turned on and I get a warning telling me no backup drive has been selected and that I should pick one. I go into the Time Machine preferences and turn it off. It will remain off (I've checked the preferences to be sure) until the next time the machine is put to sleep. Time Machine will remain off, even through reboots. It is only waking from sleep that causes this.
    I've tried zapping the PRAM, getting rid of the Time Machine preferences and even logging into a new, unused user account and testing it from there and the problem continues. This is really starting to annoy me. I wouldn't mind having TM on, but having to click through the warning every time my Mac wakes from sleep is frustrating.
    I don't want to have to buy a new external hard drive and let TM backup to the drive because, as I said, I've got my backup solutions handled already and I'm not willing to put yet more money to use a feature I don't need right now.
    I've done searches online and asked around and no one has been able to help me yet. So I thought I'd try here.
    Anyone have any ideas?

    Do you see a wake reason in Applications>Utilities>Console?

  • Late 2013 Mac Pro wake from sleep crashes - which logs to look at?

    I started encountering wake-from-sleep crashes with my late 2013 Mac Pro a couple of weeks ago.  Prior to that the system had been pretty solid.  Other than app and OS updates installed from the App Store, I can't think of any software changes that might be responsible.
    What logs should I be looking for that could be helpful in diagnosing the problem?  Looking at other posts where people have been trying to diagnose similar issues I see people posting portions of panic logs that show which modules were loaded and might help point to a culprit, but I can't seem to find a log with a panic message in it.
    I had thought I'd determined my Anker USB3 powered-hub was related to the crashes, as when I disconnected it from my system I went several days without a crash.  Today I reconnected the hub with just a few devices on it and got a crash. I disconnected the devices but left the hub attached but got another crash.  I then disconnected the hub again, assuming I'd proved it was the culprit, but the machine has now crashed twice without the hub attached.
    I'm running OS 10.9.4.  Looking at other reports people reported some specific programs that added kernel extensions that were suspected to be the problem, but I don't have any of those programs installed on my Mac. The problem doesn't happen every time I wake the machine, but has happened at least four times today alone (after about three days of no crashes.)

    These instructions must be carried out as an administrator. If you have only one user account, you are the administrator.
    Launch the Console application in any of the following ways:
    ☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
    ☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
    ☞ Open LaunchPad. Click Utilities, then Console in the icon grid.
    If you don't see any reports listed, but you know there was a panic, you may have chosen Diagnostic and Usage Messages from the log list. Choose DIAGNOSTIC AND USAGE INFORMATION instead.
    In the Console window, select
              DIAGNOSTIC AND USAGE INFORMATION ▹ System Diagnostic Reports
    (not Diagnostic and Usage Messages) from the log list on the left. If you don't see that list, select
              View ▹ Show Log List
    from the menu bar.
    There is a disclosure triangle to the left of the list item. If the triangle is pointing to the right, click it so that it points down. You'll see a list of reports. A panic report has a name that begins with "Kernel" and ends in ".panic". Select the most recent one. The contents of the report will appear on the right. Use copy and paste to post the entire contents—the text, not a screenshot.
    In the interest of privacy, I suggest that, before posting, you edit out the “Anonymous UUID,” a long string of letters, numbers, and dashes in the header of the report, if it’s present (it may not be.)
    Please don’t post other kinds of diagnostic report.
    I know the report is long, maybe several hundred lines. Please post all of it anyway.

  • MBA 10.8.4 wakes from sleep after a few seconds

    I have a MacBook Air 4,2 with Mountain Lion 10.8.4 and a lot of trouble with the sleep function. Everytime I want it to sleep, it awakes after same seconds. If I close the lid, the MBA sleeps like a baby until I open it again.
    What I tried:
    - Reset PRAM and SMC
    - Hardware Diagnostics
    - Combo update
    Here is the console diagnostic:
    03.08.13 12:10:35,000 kernel[0]: The USB device Apple Internal Keyboard / Trackpad (Port 2 of Hub at 0xfa100000) may have caused a wake by issuing a remote wakeup (3)
    03.08.13 12:10:35,000 kernel[0]: HID tickle 179 ms
    03.08.13 12:10:35,000 kernel[0]: TBT W (1): 0 [x]
    03.08.13 12:10:35,328 hidd[70]: MultitouchHID: device bootloaded
    03.08.13 12:10:35,000 kernel[0]: AppleUSBMultitouchDriver::checkStatus - received Status Packet, Payload 2: device was reinitialized
    03.08.13 12:10:35,561 configd[18]: network changed: v4(en0-:192.168.1.5) DNS- Proxy- SMB
    03.08.13 12:10:36,000 kernel[0]: MacAuthEvent en0   Auth result for: 00:23:08:d4:ea:3b Auth request tx failed
    03.08.13 12:10:37,061 WindowServer[85]: handle_will_sleep_auth_and_shield_windows: no action for lock state 1
    03.08.13 12:10:37,142 WindowServer[85]: Created shield window 0x4c for display 0x003f003d
    03.08.13 12:10:37,193 WindowServer[85]: handle_will_sleep_auth_and_shield_windows: no action for lock state 1
    03.08.13 12:10:37,214 WindowServer[85]: Created shield window 0x4d for display 0x003f003e
    03.08.13 12:10:37,215 WindowServer[85]: handle_will_sleep_auth_and_shield_windows: no action for lock state 1
    03.08.13 12:10:38,115 awacsd[78]: Exiting
    03.08.13 12:10:38,000 kernel[0]: en0: 802.11d country code set to 'DE'.
    03.08.13 12:10:38,000 kernel[0]: en0: Supported channels 1 2 3 4 5 6 7 8 9 10 11 12 13 36 40 44 48 52 56 60 64 100 104 108 112 116 120 124 128 132 136 140
    03.08.13 12:10:38,000 kernel[0]: MacAuthEvent en0   Auth result for: 00:23:08:d4:ea:3b  MAC AUTH succeeded
    03.08.13 12:10:38,000 kernel[0]: wlEvent: en0 en0 Link UP virtIf = 0
    03.08.13 12:10:38,000 kernel[0]: AirPort: Link Up on en0
    03.08.13 12:10:38,000 kernel[0]: en0: BSSID changed to 00:23:08:d4:ea:3b
    03.08.13 12:10:38,000 kernel[0]: en0::IO80211Interface::postMessage bssid changed
    03.08.13 12:10:38,000 kernel[0]: AirPort: RSN handshake complete on en0
    03.08.13 12:10:38,750 configd[18]: network changed: v4(en0+:192.168.1.5) DNS+ Proxy+ SMB
    03.08.13 12:10:38,760 mDNSResponder[63]: mDNS_RegisterInterface: Frequent transitions for interface en0 (FE80:0000:0000:0000:060C:CEFF:FED5:ABF4)
    03.08.13 12:10:38,761 mDNSResponder[63]: mDNS_RegisterInterface: Frequent transitions for interface en0 (192.168.1.5)
    03.08.13 12:10:38,766 UserEventAgent[11]: Captive: en0: Not probing 'HWR' (protected network)
    03.08.13 12:10:38,770 configd[18]: network changed: v4(en0!:192.168.1.5) DNS Proxy SMB
    03.08.13 12:10:38,997 airportd[27]: _doAutoJoin: Already associated to “HWR”. Bailing on auto-join.
    03.08.13 12:10:39,013 airportd[27]: _doAutoJoin: Already associated to “HWR”. Bailing on auto-join.
    03.08.13 12:10:39,030 airportd[27]: _doAutoJoin: Already associated to “HWR”. Bailing on auto-join.
    03.08.13 12:10:40,000 kernel[0]: fsevents: watcher dbfseventsd (pid: 189) - Using /dev/fsevents directly is unsupported.  Migrate to FSEventsFramework
    03.08.13 12:10:42,528 com.apple.SecurityServer[15]: Session 100003 created
    03.08.13 12:10:42,548 com.apple.SecurityServer[15]: Session 100002 created
    03.08.13 12:10:46,262 com.apple.launchd[1]: (com.apple.coreservices.appleid.authentication[102]) Exit timeout elapsed (20 seconds). Killing
    03.08.13 12:10:46,666 usbmuxd[51]: _send_message (thread 0x100781000): Could not securely send message size 447: SSL_ERROR_SYSCALL errno (Broken pipe).
    03.08.13 12:10:46,667 usbmuxd[51]: AMDeviceValidatePairing (thread 0x100781000): Could not validate pairing with device 1: kAMDDeviceDisconnectedError
    03.08.13 12:11:09,940 com.apple.usbmuxd[51]: _heartbeat_failed heartbeat detected detach for device 0x2-192.168.1.11:0!
    ter
    Any idea? It drives me crazy! I would really like to manipulate the system not to wake up any more if I am not pushing the power button. That would be fine!

    Test after each of the following steps that you haven’t already tried:
    Step 1
    Take all the steps suggested in this support article. That's the starting point for any further effort to solve the problem. Skipping any of those steps may mean that the problem won't be solved.
    Step 2
    From the menu bar, select
    System Preferences ▹ Accessibility ▹ Speakable Items: Off
    Step 3
    Reset the SMC.
    Step 4
    Boot in safe mode and log in to the account with the problem. Note: If FileVault is enabled, or if a firmware password is set, or if the boot volume is a software RAID, you can’t do this. Post for further instructions.
    The login screen appears even if you usually log in automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
    Safe mode is much slower to boot and run than normal. Don’t launch any applications at first. If sleep still doesn’t work properly, back up all data and reinstall the OS. After that, if you still have the issue, make a “Genius” appointment at an Apple Store to have the machine tested.
    If sleep now works as expected, go on to the next step.
    Step 5
    Still in safe mode, launch the usual set of applications that are running when you have the problem, including your login items, one at a time, testing after each one. Some applications may not work; skip them. You might be able to identify the cause of the problem this way.
    Step 6
    If sleep is still working after you’ve launched all the usual applications, reboot as usual (not in safe mode) and test again. If sleep still works, you’re done, at least for the moment.
    If you still have the sleep issue after booting out of safe mode, post again.

  • TS4080 apple thunderbolt display image on display intermittently goes dark, does not wake from sleep after clicking mouse or keyboard, but there is "bonk" sound after clicking mouse or pressing keys. Rebooting by pressing the power button resolves issue.

    My apple thunderbolt display (which I purchased 1.5 years ago; OS 10.7.5 Mac Mini) intermittently goes dark, does not wake from sleep after clicking mouse or keyboard, but there is "bonk" sound after clicking mouse or pressing keys, so am thinking it is a hardware problem with the display. Rebooting by pressing the power button turns the screen back on, but the same phenomenon has occurred several times. Could this be a software issue, or do I need to have my display repaired? Your feedback would be appreciated.

    Hi ED, tough to tell, but it does sound like it's waking with the bonk, just not displaying.
    Long shot but...
    I wonder if it's a variation of this, of which I've seen many different symptoms...
    Resolution
    Move the mouse or trackpad cursor over the center area of the login window so you can see the user icons. Click on the icon of the user that you would like to login as, type in the user's password, and press Return.
    If the login window is configured to show only the name and password fields, type in the user's name and password into the fields, and press Return (even if you cannot see the rest of the login window).
    Additional Information
    This issue will not occur if the display is not sleeping when the account is logged out. Use the steps below to confirm that the account is not configured to log out automatically while the display is sleeping:
        1.    Open System Preferences > Security & Privacy > General.  Click the padlock to unlock the preference pane and enter your admin password. Click the Advanced button at the bottom, then see if the option "Log out after N minutes of inactivity" (where N is the number of minutes) is enabled.
        2.    Open System Preferences > Energy Saver and configure Display Sleep to occur after the account is logged out, by dragging the slider to a number of minutes that is greater than N was set to in the previous step.
    Important: If automatic log out is not needed, disable "Log out after Nminutes of inactivity" in System Preferences > Security & Privacy > General. This will also prevent the issue.
    http://support.apple.com/kb/TS4135?viewlocale=en_US

  • When my macbook pro wakes from sleep the curser is not there, no keys work and the screen is frozen so i have to reboot it

    Sometimes when my macbook pro wakes from sleep the curser has disappeared, the screen is frozen and no keys work. I have to reboot.

    Please read this whole message before doing anything.
    This procedure is a diagnostic test. It’s unlikely to solve your problem. Don’t be disappointed when you find that nothing has changed after you complete it.
    The purpose of the test is to determine whether the problem is caused by third-party software that loads automatically at startup or login, by a peripheral device, or by corruption of certain system caches. 
    Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards. Boot in safe mode and log in to the account with the problem. Note: If FileVault is enabled on some models, or if a firmware password is set, or if the boot volume is a software RAID, you can’t do this. Ask for further instructions.
    Safe mode is much slower to boot and run than normal, and some things won’t work at all, including sound output and  Wi-Fi on certain models. The next normal boot may also be somewhat slow.
    The login screen appears even if you usually log in automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin. Test while in safe mode. Same problem? After testing, reboot as usual (i.e., not in safe mode) and verify that you still have the problem. Post the results of the test.

  • Mac Pro will not sleep after reboot from Win 7 into OS X

    I have the same problem as mentioned in this short thread; http://discussions.apple.com/message.jspa?messageID=11410973
    Does anyone have any more information on this?
    The problems started (I think) after I replaced my Nvidia GT120 with a ATI Radeon HD 5770.

    I've got a Mac Pro and this is what I see when my Mac sleeps... BUT... I don't see anything when it tries to sleep and doesn't... or rather, when it is supposed to sleep...
    Dec 28 10:52:29 Justins-Cool-Mac-Pro kernel[0]: AFPSleepWakeHandler: going to sleep
    Dec 28 10:52:29 Justins-Cool-Mac-Pro /etc/rc.sleep: executing .sleep of user justin
    Dec 28 10:52:31 Justins-Cool-Mac-Pro kernel[0]: hibernate image path: /var/vm/sleepimage
    Dec 28 10:52:31 Justins-Cool-Mac-Pro kernel[0]: sizeof(IOHibernateImageHeader) == 512
    Dec 28 10:52:31 Justins-Cool-Mac-Pro kernel[0]: Opened file /var/vm/sleepimage, size 2147483648, partition base 0xc805000, maxio 400000
    Dec 28 10:52:31 Justins-Cool-Mac-Pro kernel[0]: hibernate image major 14, minor 2, blocksize 512, pollers 3
    Dec 28 10:52:31 Justins-Cool-Mac-Pro kernel[0]: hibernateallocpages flags 00000000, gobbling 0 pages
    Dec 28 10:52:32 Justins-Cool-Mac-Pro kernel[0]: Intel8254x -- Link down -- 00:17:f2:01:83:ec -- called by disable() -- Auto-Neg Advertise Reg (04d) = 0xde1, Link Partner Ability Reg (05d) = 0x45e1
    Dec 28 10:52:32 Justins-Cool-Mac-Pro kernel[0]: Intel8254x -- Link down -- 00:17:f2:01:83:ed -- called by disable() -- Auto-Neg Advertise Reg (04d) = 0xde1, Link Partner Ability Reg (05d) = 0x0

  • Display no longer wakes from sleep after latest updates

    G4 Quicksilver 933, nVidia Ti, 1.5GB, 20in Cinema Display
    I applied the latest updates that were pushed out recently (10.5.2 and the "Leopard Graphics Update") and now my Apple display will not properly come up when I wake the box from suspend.
    That is, it starts and runs fine, but if it goes into sleep, upon waking it will (sometimes) flash the contents of the desktop, and then go black. The litte green light is on. Happens from a logged in session, or from the main login screen.
    I have to hit the reset or power button (or login via SSH and issue a shutdown) to get it to work again.
    I only have a single monitor.
    I tried:
    o Powering the monitor off and on, both from the switch and by pulling the power cable
    o Pulling the DVI cable and reinserting it
    o Resetting NVRAM
    o Re-applying both the 10.5.2 combo installer and the Leopard Graphics Update 1.0 in order
    o Waving a magic wand... I mean, fixing permissions
    o Changing the display resolution a few times
    o Running fsck a few times (only because all these unclean shutdowns are making me nervous)
    o Hitting the "Detect Displays" button in the Displays Prefs panel...
    Aha! Hitting that button causes the display to flash and then go dark. I have to power cycle the unit to get the monitor to come up again.
    I do have the special build option of the faster video adapter which was available all those years ago. It's quaint now, sure, but it was a fast card back then.
    I'm stumped. It's surprising how something like this can turn a perfectly reasonable desktop into a boat anchor.
    Message was edited by: John Verne

    mjelacic wrote:
    This Discussion is marked as Answered, but with my apologies to the other respondents, it is NOT. There is a problem. The software/hardware do NOT work as they are supposed to. Apple needs to address this problem immediately. Mac Book Pro will not wake from sleep when connected to a Cinema Display 23". The problem lies in the most recent operating system updates. Before the update the products worked as advertised, since then they do not. Period.
    With all due respect, I am the one who posted this, and I marked it "answered." Yes, there very well may be a problem with the Leopard Graphics Update 1.0 (what a mouthful! I dub it "LGU v1.0" from this point on.), but this is so far only a hypothesis.
    I found an immediate workaround which suits my purpose. If this does not suit the purposes of completely foreign (to this discussion) symptoms related to Intel-based Apple laptops and external displays, then so be it. I recommend splitting off your own symptoms to a new thread.
    Certainly, my reading of the symptoms described after I posted mine mostly do not sound like what I ran into at all. For example, I never once said that my computer had problems waking from sleep. I said the /display/ had problems waking/starting up after sleep, and this is probably related to the "detect displays" mechanism that the OS uses to find attached displays when it comes out of suspend. Even if this is my misunderstanding it does not matter, since this is how it comes across to a reader. This may indicate that someone may want to clearly and carefully describe /exactly/ what they are seeing, and the steps they took in order to come to any conclusions they might have.
    This will help Apple, and it will certainly help others that search these threads with their own similar but different issues they need solved.
    If there is a common reproducible issue related to displays and the most recent update(s), then Apple already knows about it, or soon will. As far as my immediate needs are concerned, this is answered.

  • Crashes after wake from Sleep after 10.8.1 update

    2.5 Ghz Mac Mini (mid 2011), 8 Gigs of RAM
    Since the day I upgraded to 10.8.1 I have had persistent crashes, 1 every 24 hours or so. It's always shortly after a wake from sleep. In all cases, it is impossible to switch to a random open application. But once I hit that application, no other application will respond to anything, including a Force Quit, or if it will force quit, it won't relaunch. A shut down will hang because an app refuses to quit. I can quit the Finder, but it won't relaunch. Have reinstalled Mountain Lion twice, zapped the PRAM, reset the SMC, checked and extensively tested the HD and RAM. Replaced RAM with original Apple RAM. Didn't help, so I swapped back to the RAM from Crucial. I can't think of anything else to try. Machine does not crash unless it has been asleep. Runs flawlessly when sleep is disabled. After a reboot (usually via a shut down via the power switch, start from scratch, check of the HD integrity, and then a clean restart) the machine will run fine, sleep and wake normally for about 24 hours. As near as I can tell from the logs, the hangs usually begin right after the Time Machine Backup after a wake from sleep finishes. If I don't allow the machine to sleep, there are no problems of any kind. Making me crazy. Did not occur under Lion or the .0 version of Mountain Lion. Is making me crazier than I normally am which is sorta serious.

    Any solutions to this problem?  I too have this kernel panic, however it only happens about once a week.  Always upon wake from sleep as you've indicated. 
    FYI I don't have intego software, or an APC installed.  Nor am I using filevault.
    This is on an up to date, MacBook Pro Retina.
    Robert

  • IMac will not wake from sleep after 10.4.8 Update

    Recently after a couple of software updates my IMac goes to sleep and the Bluetooth keyboard and mouse will not wake it. The option for wake with Bluetooth is checked. I zapped the PRAM and also checked the HD, Nothing has changed. NOTE: No new software or hardware installs were done except for 10.4.8 update and the other mac software updates. This did not happen in prior versions of the OS on my iMac. Is this a new bug?
    iMac G5 1.8 (pre iSight)   Mac OS X (10.4.8)   Bluetooth, Wake from Sleep

    I've been dealing with this same issue, have tried everything, but to no avail. After MANY sessions on the phone with Apple tech support, as well as an Apple product specialist, I was advised to erase my computer and do a fresh install. I did an archive an install, which didn't help, but am not thrilled about the prospect of erasing everything and starting over. This problem started after the August 2006 round of updates. I feel it's bluetooth related, because I used a usb keyboard and mouse for a week as a test, with no problem. The funny thing is, I unchecked "allow bluetooth device to wake computer" thinking it might help, but the bluetooth devices continue to wake the computer anyway (except when it refuses to wake, of course!)
    Jerry

  • Power Mac G4 Wake from Sleep Crash

    I have been having wake from sleep issues since I installed Mac OS 10.5 on my Power Mac G4 three months ago. Technically, this machine is supported by Leopard: it's an 867 MHz G4 with 512 MB of RAM. And indeed, the Leopard installer allowed me to install fine, and while it runs slower than I'd like, it seems to run all the applications just fine. The major problem is that it does not properly wake from sleep. Nearly every time the machine wakes up from sleep, it crashes and needs to be rebooted. It may be a display issue -- the screen frequently looks corrupted when it has crashed -- but the console logs have not given me any clues. It does seem to be related to the amount of time that the machine has spent sleeping, but I have had it crash after a sleep of as little as a few minutes. I have a USB 2.0 PCI card installed, but removing that for a week didn't have any noticeable effect on the problem. I'm stumped, and preparing to downgrade to 10.4, as the machine takes too long to boot for me to live with the option of shutting down and starting up every time I use it.
    I've been very happy with this machine for years and years and frankly I've never had this much of an issue with the Mac OS on an allegedly "supported" machine. As a last resort, I thought I'd ask here whether anyone has another idea that I can try.

    I'm having a similar problem, though with my Powerbook G4, since installing Leopard. It's a 1.5 Mhz model. Everything seems to work properly, but it takes 10 to 12 seconds to wake from sleep. When it is woken, it shows the old screen image and remains frozen for over 10 seconds, before displaying the updated screen and coming back to life. It seems to me that this pause is progressively getting longer. It was only a few seconds to start with, but is now over 10 seconds.
    Any clues?

  • IMac (Early 2009) always wakes from sleep after Security Update 2010-001

    I posted this already in the Snow Leopard section, but wasn't able to get a resolution to the problem:
    http://discussions.apple.com/thread.jspa?threadID=2309613&tstart=0
    I tried all the suggested things, but my iMac still always wakes from sleep and this never happened before the 2010-001 security update. I was asked to paste the console log entry from when this happens, so here it is:
    28/01/2010 08:57:47 kernel Wake reason = OHC2
    28/01/2010 08:57:47 kernel System Wake
    28/01/2010 08:57:47 kernel Previous Sleep Cause: 5
    28/01/2010 08:57:47 kernel USB (OHCI):Port 1 on bus 0x6 has remote wakeup from some device
    I'm wondering if others have seen this and if so know of a solution. At the moment I'm stuck with having to shutdown my iMac every time I leave it. Thanks.

    Here is a solution that should work:
    1. Turn off all Bluetooth devices connected to your computer.
    2. Make sure Bluetooth icon in the Menu Bar is black (BT is On) and BT is not connected to anything
    3. Plug in a USB mouse
    4. Go to System Preferences>Bluetooth>Advanced
    5. The option to "Allow Bluetooth devices to wake this computer" should now be uncheckable>Uncheck it and click OK
    6. Turn on your Bluetooth devices and let them connect to your Mac
    7. Try and put your Mac to sleep and then wake with the power button
    8. Check if the "Allow Bluetooth devices to wake this computer" option is still unchecked (it should be)
    9. Try and restart your Mac and check again if the "Allow Bluetooth devices to wake this computer" option is still unchecked (I had mixed results with this test, depending on the type of the Mac being tested)
    Anyhow, this way you should be able to uncheck the option that causes the issue and it should not get checked again by itself unless you restart your computer and maybe even after that. If it does get checked again after reboot, just get used to putting your Mac only to sleep until a fix from Apple is available or repeat the above process after every reboot if necessary.
    Hope this helps.
    Marian

  • Why won't my macbook pro wake from sleep?

    My MacBook Pro 13" is awesome.  What is not awesome is that I can't wake it from sleep sometimes.  I have tried pressing keys, trackpad and power button with no success.  When I restart, I get the login screen and it will immediatly go to sleep or it will let me type in the password and then go to sleep.  What is going on here.  I thought that Lion would fix this, but it did not.  Anyone have any suggestions?

    Everything seems okay with my computer.  It did not want to wake up 1 time since my last post.  I closed the laptop, let it sit for a few minutes and when I opened it back up it woke up and was fine.  The only thing I can figure is there is something that happens after the laptop has been charging for awhile.  It seems that everytime the computer didn't want to wake from sleep, it had been charging the battery or had just finished charging.  Weird thing to happen.  If you have this problem happen to you, try the steps mentioned earlier in this post (the answer from tjk) will probably fix it.

  • My elderly iMac (about six years old) won't wake from sleep after an electrical failure today, and starts up with a black screen.

    This Intel iMac is about six years old, has had the motherboard replaced by Apple.  Today we had an electrical failure, and it was asleep at the time.  It refused to wake from sleep, and it seems to start up, but the screen stays black.  I tried zapping the PRAM, shutting it down and turning off the surge protector, etc. . .  and still, nothing.  Any thoughts?

    If http://support.apple.com/kb/HT3964 Intel-based Macs: Resetting the System Management Controller (SMC) does not work and you are comfortable working in the Terminal, try the following:
    Enter into the Terminal the following: sudo pmset autopoweroff 0 and sudo pmset standby 0
    If you like the hibernation, you can switch it back on by re-entering the commands with 1's instead of 0's. You can even change the amount of time by adjusting "autopoweroffdelay" and "standbydelay".

  • MacBook won't automatically wake from sleep after flipping computer open.

    The only way my computer both goes to sleep and wakes from sleep is by clicking on the Apple icon and putting it to sleep before closing the lid and by pressing the power button after opening the lid. If I just close the lid without first clicking on "Sleep" under the Apple icon, the computer will continue to run and the Apple on the lid will continue to be lit while the sleep indicator light does not go on. If I just open the lid and do not press the power button, the screen will continue to be black and the sleep indicator light continues to glow. I'm not sure if I reset a system preference or something by mistake, but is there a way to fix this? Or is this an indication of a bigger problem?
    Additionally, when my computer is asleep and I unplug my charging iPod, it wakes from sleep (the sleep indicator light goes black while the Apple on the back of the screen lights up). Is this an indication of a bigger problem?
    My computer is only about 7 months old, so I am a bit worried if it is starting to show wear and tear already. Thank you for your help!

    You're welcome to the Forums.
    Go to System Preferences>Energy Saver, and set a time for your System to sleep.
    Set both sliders to 10 or 15mins to nod off, when Inactive.
    It's never a good idea to plug in or out, while the Computer is sleeping. If someone pokes at your ear while you're sleeping, you'll wake up too.

Maybe you are looking for

  • 648 Max - Identifying but not using both RAM modules

    Hi! I'm totally new here, just stumbled across this forum while googling for a solution to my problem, so please excuse my lack of proper terminology if that should occur. I have the following system (data obtained from Everest 2.20 and own brain): P

  • B2B Message Error - Decrypting S/MIME message failed

    Hi, Am getting following error when i receive the inbound message from trading partner I have set up the certificates on both sides. [2010-04-15T19:53:18.981-04:00] [soa_server1] [ERROR] [] [oracle.soa.b2b.engine] [tid: weblogic.work.j2ee.J2EEWorkMan

  • WPA2 and Netgear WPN824

    Has anybody had any problems with WPA2 security on the MacBook Pro? I switched my wireless network over to WPA2 from WEP tonight, and my G4 Mac Mini and Wii connected with no problems. However, the MBP will join the network with no outbound connectiv

  • ITunes won't let me select show duplicate items on my iPhone 4s.

    I can see the option but it is in faded font color and I cannot select it. Pressing shift, or alt, or control does nothing to remedy the problem. I'm using an iPhone 4S, under the most current iOS (7.1) Thanks in advance for any help.

  • Unable to list firewire devices.thank you now for your future help.

    all right so my firewire decided it cant recognize my sony handycam...so i decided hey it is probably the firewire...so i buy a new firewire and it still doesnt work...so then i was like all right look it up online...i reset my smu nvram pram deleted