Wakes from sleep then sleeps again

Hi there, I've posted a message previously on these boards asking a question about a sleep problem, wherein my iBook wouldn't wake from sleep and had to be forced shutdown to restart. This was resolved with the help of these boards in the form of a key command combination which reset some part of the hardware.
This issue isn't anywhere near as serious, but I'm wondering if it might hint at an overall problem. Sometimes, when I wake my iBook from sleep - all is well, but then the iBook goes pretty much straight back to sleep, although sometimes there is a 30 (or so) second pause before it does so. Any ideas? The iBook can always be woken again and always stays awake the second time around.
Thanks

Try resetting the Power Management Unit (PMU). It may think your battery is low. I can't remember how to reset the PMU on the iBook off hand.. but it should be in the Applecare database.

Similar Messages

Mac Book pro slow to wake from sleep

Hi , Sometimes when I leave my mac book pro and it goes to sleep (screen goes black when lid open) it takes a while to wake from sleep again - sometimes up to 30-40 seconds? This seems very odd for an expensive machine that is around 6 months old and something that never used to happen with my old powerbook G4. It doesn't happen all the time but regularly. Should I be worried? Any help greatly appreciated!

I'm curious if you ever found a solution for this issue. I recently purchased the SanDisk Extreme II 480GB, replacing my OWC Extreme Pro 240GB. The OWC never experienced the "slow to wake" issue whereas the SanDisk drive does, consistently. To make sure I'm having the same symptoms, this is what happens to me: Put the mac to sleep (either manually or letting it do it on its own, waiting for the led to pulse showing that it is asleep), then wake it up (press a key on the keyboard), the logon screen shows almost immediately but as soon as I try to type the pinwheel/beach ball shows up, I wait between 20 and 30 seconds and then I'm able to type and all is well.
I contataced SanDisk and their support was horrible. They simply told me "contact MAC for this issue" (no joke, not "contact Apple" but "contact MAC", in all caps). I explained that it works fine with the OWC drive just not the SanDisk. They replied with another article showing that all macs have trouble waking from sleep (not true). I replied again indicating that I've never had this issue with any of my 3rd party drives, only this SanDisk. Then the replied simply stating that all mac's have issues with 3rd party hard drives when waking from sleep. At this point I threw a fit and yelled at my screen, even though it wasn't my screens fault.
In any case, their support has not been willing to do any actual troubleshooting. I'd love to return it and I might have to - but as you stated, it's annoying to have this issue but the performance is fine the rest of the time.
Thanks for any input you have.
Bryan

New macbook pro wont wake from sleep

Hi everyone, I got the new macbook pro 15 inch with retina display about a month ago, the problem is it will not wake from when the screen goes to sleep, not all the time but enuff for me to want to throw it out the window, when it is in sleep mode i go to touch the touch pad then the keybord lights up like its about to work then dies and i end up tuning the computer off from the off button.
I have been on the phone with apple for many hours and its doing my head in and losing my mind and they have done a re set, a re install and also after that didnt work we wiped the computer and downloaded the software directley from apple and started fresh again " AND STILL DOES NOT WAKE FROM SLEEP " i have taken it back to jb hifi where i got it from in Liverpool westfields and they said sorry we cant help you and apple are saying you have to take the computer to apple and leave it with them for a few weeks, very hard for me as i use the computer everyday to run my business and i feel ripped off big time they should replace it straight away.
Has anyone had this problem before ? any ideas ? thank you very much for you time. Dave

Apple has replaced systems for others after several tries at repairs have failed. Find an Apple Authorized Service Provider and take it in for service, as Apple support directed. Apple would have replaced the system outright in the first 14 days of ownership. After that, you need to give them the opportunity to repair it under warranty.
Since you use it for business, have you asked if the Apple Authorized Service Provider can provide a loaner? Or considered renting one for the short period it would be repaired? Or talked to the Apple Authorized Service Provider about expediting repair?

Mountain lion - wake from sleep - destroys hdd

I upgraded my macbook pro mid 2009 model to mountain lion.
First crash - left my computer for 3 hrs playing music using iTunes. Hdd went to sleep, screen is sleeping as well. I moved my mouse and everything froze. Music stopped. Waited for a minute. Nothing happened. I forced shutdown by holding power button for 5 seconds. Reboot failed because hdd can no longer be detected. (Gray folder with question mark) Not even by the install disk.
I brought it to the service center and they replaced my hdd after i approved it. It works ok then. Reinstalled mountain lion and all my stuff.
Second crash - i left my computer for an hour playing music through Grooveshark. Screen and hdd went to sleep while music still played ok. I moved the mouse to wake from sleep but the screen remained black. I can see the cursor not moving but the music was still playing. I put down the lid and waited for a few seconds before turning it on. Screen was still black except for mouse. Music stopped when i closed the lid. I forced shutdown by holding the power button for 5 seconds. Reboot failed because the hdd cannot be detected. (Gray folderneith question mark) Not even by the install disk.
I'm going to the repair center tomorrow and have it checked again. It's only been a week since i got back from the repair center...
So i was reading about the issues with mountain lion waking from sleep where the hdd has slept as well. But it seems that their hdds were intact and they were able to reboot. Mine however, has left my hdd as a heavy paper weight.
2 things, how do I repair the hdds and use them again? Is the issue caused by waking from sleep with the hdd sleeping as well?
Note that in both occurrences, my mbp was plugged in.
Or is it possible that the 2009 model just can't handle mountain lion?
I'm thinking of using ubuntu to force mount my 2 broken hdds and hopefully recover some of my data though all my important files and documents are in sugarsync and dropbox. (Thank God for online storage!) though this is quite detrimental to teaching...

Repair the Hard Drive and Permissions - Lion/Mountain Lion
Boot to the Recovery HD:
Restart the computer and after the chime press and hold down the COMMAND and R keys until the menu screen appears. Alternatively, restart the computer and after the chime press and hold down the OPTION key until the boot manager screen appears. Select the Recovery HD and click on the downward pointing arrow button.
Repair
When the recovery menu appears select Disk Utility. After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported then click on the Repair Permissions button. When the process is completed, then quit DU and return to the main menu. Select Restart from the Apple menu.

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.

Power Mac G4 Quicksilver Won't Wake From Sleep

I have a Power Mac G4 Quicksilver 933MHz that will not wake up after it goes to sleep. It is currently running OS X 10.3, has had its hard drive replaced, system reinstalled, and been DiskWarrior'd. Haven't tried replacing the PRAM battery yet but get no indication its dead (clock keeps time wen off). It always connected to an Apple 17" Cinema Display--could that be the source of the problem?

Hi, Toolshed4!
Third Party USB devices and USB PCI cards are notorious potential culprits for no wake from sleep issues so please follow japamac's lead and look at them as potential culprits. Disconnect the external peripherals and test sleep/wake. Swap a third party keyboard and/or mouse with your Apple one(s) and test. Remove any PCI cards, and test. (It's perhaps good practice to reset the PMU after you add or remove an internal component.)
A Cinema Display, especially one with a built-in USB port or hub problem, could create an issue, though it would more likely to be one of not sleeping, rather than not waking. You might quickly check your system log for possible indicators of USB issues with the Display, if you have reason to suspect that its ports may not be functioning properly.
Resetting NVRAM in Open Firmware sometimes resolves the issue. Resetting your PMU as japamac suggested will take care of the NVRAM reset for you.
If the above didn't resolve things, please continue on...
Corrupt Energy Saver preferences are sometimes the cause. Quit System Preferences if it's opened and navigate to /Library/Preferences/System Configuration (folder) and delete the following preference files:
com.apple.PowerManagement.plist
com.apple.AutoWake.plist
(The AutoWake plist file may or may not be present, depending on whether or not you have/had scheduled sleep settings.)
Then navigate to ~/Library/Preferences and delete the com.apple.systemuiserver.plist preference file. Restart and test sleep again.
If your battery is old, it's a good idea to just get a new one. The worst that can happen is that you'll have a spare when you need it. They're about $5 online. If you go to Radio Shack with the one you have, they'll test it for you. Alternately, put a voltmeter on it and insure that you're reading at least 3.3 volts DC. New ones read 3.6 - 3.9 volts.
Gary
Message was edited by: Majordadusma

How to wake from sleep only with power button

Hi,
I still use this old PowerMac G4 (hopefully Apple builds a new MacPro soon!) and when not using it, it is in sleep mode.
Unfortunately my cats like to touch the keyboard, thus waking up my Mac.
Is it possible to wake the mac only by pressing the power button?
If so, how?
regards
kpgkpg

The USB bus is unique from other buses in that it always has power present to it.
Because of this, it can be used to sense activity at a keyboard or other input device to facilitate wake from sleep.
The power button also always has power present, with the main purpose of on and off being extended to options for sleep and wake. This is possible due to the use of a momentary contact switch, with fuction that can be interpreted (time held) for various purposes via software.
why the action on the USB bus has to be a keyboard inpput, but not a mouse click. strange.
Mouse click should also wake the machine if the mouse is USB. If Bluetooth, an option must be selected in the software, and then not all mice are equal.
If wireless, then, again, not all are equal. Some will wake a machine, others won't.

Mac Pro Failed to wake from sleep

Hello All,
I've had my Mac Pro since Aug. 2007. Never had any problems of any kind until this morning.
To wake from sleep (as I always do): depressed arrow key (10:43 AM). There was a delay - then the spinning beach ball for about 2 min. I did a hard shutdown, waited a bit, then restarted at 10:52 AM. Boot up was (as always) quick.
I logged into my (usual) non-admin account and observed:
When all start up items were loaded: Finder windows appeared approximately as follows:
1. A window showing the (not sure of proper term) "internal folders" of main boot up volume.
2. A window showing the internal folders stored on my mirrored RAID back up disk(s)
3. A window showing the internal folders of my bootable back up.
4. A window showing all 3 disk icons[ Main boot, Bootable backup and the RAID].
I closed all of these windows. [Didn't think too much about it but it's not normal to have these widows appear] SO -
Next:
Then I logged out and logged into my admin account to check the system log with console.
It showed an event from last night which I could not interpret but it did not appear to reveal serious problems (something about not being able to make network connection).
But - the second item on the System Log showed the "wake from sleep" sequence (at 10:43 AM).
I'm going to post the entire wake from sleep log below but first I'll state what was obvious to me:
Startup of CPU #1, #2 and #3 appear first - there is NO #4 CPU!
The log for the manual startup at 10:52 showed some apparent problems as I note below.
Next: Once logged in as admin - I launched Activity Monitor just to assure myself that all four CPUs were at least registering - and they were / are.
Hoping someone here can more thoroughly analyze this log report and give me an idea of the cause of the failure to waken.
Naturally, I won't want to put the Mac Pro to sleep again until I'm sure this isn't a "permanent" problem requiring further action (including service, of course).
Also noticed a statement about some app not having correct permissions (apparently at the System level) and something about removing several orphaned files. There's a warning about CarbonCopyCloner scheduled tasks as well. But there my understanding ends.
Thanks in advance:
System Log Report
Jan 30 10:43:04 Macintosh kernel[0]: System Sleep
Jan 30 10:43:04 Macintosh kernel[0]: Enabling XMM register save/restore and SSE/SSE2 opcodes
Jan 30 10:43:04 Macintosh kernel[0]: Started CPU 01
Jan 30 10:43:04 Macintosh kernel[0]: Enabling XMM register save/restore and SSE/SSE2 opcodes
Jan 30 10:43:04 Macintosh kernel[0]: Started CPU 02
Jan 30 10:43:04 Macintosh kernel[0]: Enabling XMM register save/restore and SSE/SSE2 opcodes
Jan 30 10:43:04 Macintosh kernel[0]: Started CPU 03
Jan 30 10:43:04 Macintosh kernel[0]: System Wake
Jan 30 10:43:04 Macintosh kernel[0]: USB caused wake event (EHCI)
Jan 30 10:43:06 Macintosh kernel[0]: Intel8254x -- Link Up -- 00:17:f2:07:af:71 -- called by interruptOccurred() --
Jan 30 10:43:06 Macintosh configd[43]: posting notification com.apple.system.config.network_change
Jan 30 10:43:10 Macintosh kernel[0]: -- Auto-Negotiation Advertisement Register (04d) = 0xde1
Jan 30 10:43:10 Macintosh kernel[0]: -- Auto-Negotiation Link Partner Ability Register (05d) = 0xcde1
Jan 30 10:43:10 Macintosh kernel[0]: -- Auto-Negotiation Gigabit Advertisement Register (09d) = 0xe00
Jan 30 10:43:10 Macintosh kernel[0]: -- Auto-Negotiation Gigabit Link Partner Ability Register (10d) = 0x7c00
Jan 30 10:43:10 Macintosh kernel[0]: -- PHY Specific Status Register (17d) = 0xaf08
Jan 30 10:43:10 Macintosh kernel[0]: Intel8254X -- Negotiated Speed: 1 Gb/s, Duplex: Full, Flow Control: Receive Pause Enabled, Transmit Pause Enabled
Jan 30 10:43:11 Macintosh lookupd[3328]: lookupd (version 369.8) starting - Fri Jan 30 10:43:11 2009
Jan 30 10:43:12 Macintosh xgridagentd: Warning: error opening connection (Jacks Computer): Unable to connect: BEEPError 600 (could not bind socket)
Jan 30 10:43:12 Macintosh crashdump[3329]: WindowServer crashed
Jan 30 10:43:13 Macintosh crashdump[3329]: crash report written to: /Library/Logs/CrashReporter/WindowServer.crash.log
Jan 30 10:43:13 Macintosh configd[43]: posting notification com.apple.system.config.network_change
Jan 30 10:43:13 Macintosh lookupd[3330]: lookupd (version 369.8) starting - Fri Jan 30 10:43:13 2009
Jan 30 10:43:14 Macintosh kernel[0]: AFPSleepWakeHandler: waking up
Jan 30 10:43:16 Macintosh xgridagentd: Warning: error opening connection (Jacks Computer): Unable to open: BEEPError 200 (Success)
Jan 30 10:43:16 Macintosh xgridagentd: Warning: error opening connection (Jacks Computer): Authentication failed
Jan 30 10:48:16 Macintosh xgridagentd: Warning: error opening connection (Jacks Computer): Unable to open: BEEPError 200 (Success)
Jan 30 10:48:16 Macintosh xgridagentd: Warning: error opening connection (Jacks Computer): Authentication failed
<== this is the manual restart at 10:52 ==>
Jan 30 10:52:01 localhost kernel[0]: hi mem tramps at 0xffe00000
Jan 30 10:52:01 localhost kernel[0]: PAE enabled
Jan 30 10:52:01 localhost kernel[0]: 64 bit mode enabled
Jan 30 10:52:01 localhost kernel[0]: standard timeslicing quantum is 10000 us
Jan 30 10:52:01 localhost kernel[0]: vmpagebootstrap: 1230515 free pages
Jan 30 10:52:01 localhost kernel[0]: migtable_maxdispl = 71
Jan 30 10:52:01 localhost kernel[0]: Enabling XMM register save/restore and SSE/SSE2 opcodes
Jan 30 10:52:01 localhost kernel[0]: 79 prelinked modules
Jan 30 10:52:01 localhost kernel[0]: ACPI CA 20060421
Jan 30 10:52:01 localhost kernel[0]: AppleIntelCPUPowerManagement: ready
Jan 30 10:52:01 localhost kernel[0]: AppleACPICPU: ProcessorApicId=0 LocalApicId=0 Enabled
Jan 30 10:52:01 localhost kernel[0]: AppleACPICPU: ProcessorApicId=1 LocalApicId=1 Enabled
Jan 30 10:52:01 localhost kernel[0]: AppleACPICPU: ProcessorApicId=2 LocalApicId=7 Enabled
Jan 30 10:52:01 localhost kernel[0]: AppleACPICPU: ProcessorApicId=3 LocalApicId=6 Enabled
Jan 30 10:52:01 localhost kernel[0]: AppleACPICPU: ProcessorApicId=4 LocalApicId=0 Disabled
Jan 30 10:52:01 localhost kernel[0]: AppleACPICPU: ProcessorApicId=5 LocalApicId=0 Disabled
Jan 30 10:52:01 localhost kernel[0]: AppleACPICPU: ProcessorApicId=6 LocalApicId=0 Disabled
Jan 30 10:52:01 localhost kernel[0]: AppleACPICPU: ProcessorApicId=7 LocalApicId=0 Disabled
Jan 30 10:52:01 localhost kernel[0]: Copyright (c) 1982, 1986, 1989, 1991, 1993
Jan 30 10:52:01 localhost kernel[0]: The Regents of the University of California. All rights reserved.
Jan 30 10:52:01 localhost kernel[0]: using 16384 buffer headers and 4096 cluster IO buffer headers
Jan 30 10:52:01 localhost kernel[0]: Enabling XMM register save/restore and SSE/SSE2 opcodes
Jan 30 10:52:01 localhost kernel[0]: Started CPU 01
Jan 30 10:52:01 localhost kernel[0]: Enabling XMM register save/restore and SSE/SSE2 opcodes
Jan 30 10:52:01 localhost kernel[0]: Started CPU 02
Jan 30 10:52:01 localhost kernel[0]: Enabling XMM register save/restore and SSE/SSE2 opcodes
Jan 30 10:52:01 localhost kernel[0]: IOAPIC: Version 0x20 Vectors 64:87
Jan 30 10:52:01 localhost kernel[0]: Started CPU 03
Jan 30 10:52:01 localhost kernel[0]: ACPI: System State [S0 S3 S4 S5] (S3)
Jan 30 10:52:01 localhost kernel[0]: Security auditing service present
Jan 30 10:52:01 localhost kernel[0]: BSM auditing present
Jan 30 10:52:01 localhost kernel[0]: disabled
Jan 30 10:52:01 localhost kernel[0]: rooting via boot-uuid from /chosen: B4C50221-5F1E-4039-A399-B8A077BADEC1
Jan 30 10:52:01 localhost kernel[0]: Waiting on <dict ID="0"><key>IOProviderClass</key><string ID="1">IOResources</string><key>IOResourceMatch</key><string ID="2">boot-uuid-media</string></dict>
Jan 30 10:52:01 localhost kernel[0]: USB caused wake event (EHCI)
Jan 30 10:52:01 localhost kernel[0]: Got boot device = IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/SATA@1F,2/AppleAHCI/PRT0 @0/IOAHCIDevice@0/AppleAHCIDiskDriver/IOAHCIBlockStorageDevice/IOBlockStorageDri ver/Hitachi HDP725050GLA360 Media/IOGUIDPartitionScheme/AppleHFS_Untitled1@2
Jan 30 10:52:01 localhost kernel[0]: BSD root: disk0s2, major 14, minor 2
Jan 30 10:52:01 localhost kernel[0]: jnl: replay_journal: from: 26849280 to: 10866176 (joffset 0xe8e000)
Jan 30 10:52:01 localhost kernel[0]: FireWire (OHCI) TI ID 8025 built-in now active, GUID 0016cbfffe7992ba; max speed s800.
Jan 30 10:52:01 localhost kernel[0]: hfs mount: enabling extended security on Phyllis_VII
Jan 30 10:52:01 localhost kernel[0]: HFS: Removed 7 orphaned unlinked files
Jan 30 10:52:01 localhost kernel[0]: Jettisoning kernel linker.
Jan 30 10:52:01 localhost kernel[0]: Resetting IOCatalogue.
Jan 30 10:52:01 localhost kernel[0]: PXS1: family specific matching fails
Jan 30 10:52:01 localhost kernel[0]: Matching service count = 1
Jan 30 10:52:01 localhost kernel[0]: Matching service count = 2
Jan 30 10:52:01 localhost kernel[0]: Matching service count = 2
Jan 30 10:52:01 localhost kernel[0]: Matching service count = 2
Jan 30 10:52:01 localhost kernel[0]: Matching service count = 2
Jan 30 10:52:01 localhost kernel[0]: Matching service count = 2
Jan 30 10:52:01 localhost kernel[0]: Previous Shutdown Cause: 3
Jan 30 10:52:01 localhost kernel[0]: NVDANV40HAL loaded and registered.
Jan 30 10:52:01 localhost kernel[0]: PXS1: family specific matching fails
Jan 30 10:52:01 localhost kernel[0]: IPv6 packet filtering initialized, default to accept, logging disabled
Jan 30 10:52:01 localhost memberd[46]: memberd starting up
Jan 30 10:52:01 localhost xgridcontrollerd: Warning: the file /etc/xgrid/controller/client-password has incorrect permissions or ownership (must be 0600, and root/wheel). Password not read.
Jan 30 10:52:01 localhost mDNSResponder-108.6 (Jul 19 2007 11: 41:28)[37]: starting
Jan 30 10:52:01 localhost xgridcontrollerd: Warning: the file /etc/xgrid/controller/agent-password has incorrect permissions or ownership (must be 0600, and root/wheel). Password not read.
Jan 30 10:52:01 localhost lookupd[47]: lookupd (version 369.8) starting - Fri Jan 30 10:52:01 2009
Jan 30 10:52:01 localhost DirectoryService[52]: Launched version 2.1 (v353.6)
Jan 30 10:52:02 localhost xgridcontrollerd: Warning: database file was not closed cleanly.
Jan 30 10:52:02 localhost diskarbitrationd[45]: disk4s3 hfs 3391641B-2431-3F99-A77D-397F417615F1 Boot OSX [not mounted]
Jan 30 10:52:02 localhost diskarbitrationd[45]: disk0s2 hfs C1617214-1C69-33DC-BC3F-1F7559B84120 Phyllis_VII /
Jan 30 10:52:02 localhost diskarbitrationd[45]: disk2s3 hfs 3391641B-2431-3F99-A77D-397F417615F1 Boot OSX [not mounted]
Jan 30 10:52:03 localhost kernel[0]: jnl: replay_journal: from: 1948672 to: 8487424 (joffset 0xba5000)
Jan 30 10:52:03 localhost kernel[0]: AppleIntel8254XEthernet: Ethernet address 00:17:f2:07:af:70
Jan 30 10:52:03 localhost kernel[0]: AppleIntel8254XEthernet: Ethernet address 00:17:f2:07:af:71
Jan 30 10:52:03 localhost configd[43]: No AirPort Driver found.
Jan 30 10:52:03 localhost lookupd[84]: lookupd (version 369.8) starting - Fri Jan 30 10:52:03 2009
Jan 30 10:52:03 localhost xgridcontrollerd: started.
Jan 30 10:52:03 localhost kernel[0]: jnl: replay_journal: from: 37588480 to: 30012416 (joffset 0xe8e000)
Jan 30 10:52:04 localhost xgridcontrollerd: Database load completed.
Jan 30 10:52:04 localhost diskarbitrationd[45]: disk1s2 hfs C7580D0F-35C6-3678-BC27-FFEBE31CCBAC 372 GB Bootable /Volumes/372 GB Bootable
Jan 30 10:52:05 localhost xgridagentd: Notice: agent maximum task count is 4
Jan 30 10:52:05 localhost xgridagentd: Notice: Jacks Computer started.
Jan 30 10:52:05 localhost xgridagentd: Notice: agent will bind to first available controller
Jan 30 10:52:05 localhost /usr/bin/open: kCGErrorRangeCheck : Window Server communications from outside of session allowed for root and console user only
Jan 30 10:52:05 localhost /System/Library/CoreServices/loginwindow.app/Contents/MacOS/loginwindow: Login Window Application Started
Jan 30 10:52:05 localhost loginwindow[95]: Login Window Started Security Agent
Jan 30 10:52:06 localhost mDNSResponder: Adding browse domain local.
Jan 30 10:52:06 Macintosh kernel[0]: Intel8254x -- Link Up -- 00:17:f2:07:af:71 -- called by interruptOccurred() --
Jan 30 10:52:06 Macintosh kernel[0]: -- Auto-Negotiation Advertisement Register (04d) = 0xde1
Jan 30 10:52:06 Macintosh configd[43]: setting hostname to "Macintosh.local"
Jan 30 10:52:06 Macintosh kernel[0]: -- Auto-Negotiation Link Partner Ability Register (05d) = 0xcde1
Jan 30 10:52:06 Macintosh kernel[0]: -- Auto-Negotiation Gigabit Advertisement Register (09d) = 0xe00
Jan 30 10:52:06 Macintosh kernel[0]: -- Auto-Negotiation Gigabit Link Partner Ability Register (10d) = 0x7c00
Jan 30 10:52:06 Macintosh kernel[0]: -- PHY Specific Status Register (17d) = 0xaf08
Jan 30 10:52:06 Macintosh kernel[0]: Intel8254X -- Negotiated Speed: 1 Gb/s, Duplex: Full, Flow Control: Receive Pause Enabled, Transmit Pause Enabled
Jan 30 10:52:09 Macintosh configd[43]: executing /System/Library/SystemConfiguration/Kicker.bundle/Contents/Resources/enable-net work
Jan 30 10:52:09 Macintosh configd[43]: posting notification com.apple.system.config.network_change
Jan 30 10:52:09 Macintosh lookupd[104]: lookupd (version 369.8) starting - Fri Jan 30 10:52:09 2009
Jan 30 10:52:06 Macintosh kernel[0]: HFS: Removed 3 orphaned unlinked files
Jan 30 10:52:06 Macintosh kernel[0]: hfs mount: enabling extended security on 465.8-1 to -2RAID Set 1
Jan 30 10:52:06 Macintosh diskarbitrationd[45]: disk3 hfs EEEA9F73-B66F-3711-8AA4-A9008B69A26A 465.8-1 to -2RAID Set 1 /Volumes/465.8-1 to -2RAID Set 1
Jan 30 10:52:08 Macintosh configd[43]: target=enable-network: disabled
Jan 30 10:52:08 Macintosh xgridagentd: Warning: error opening connection (Jacks Computer): Unable to open: BEEPError 200 (Success)
Jan 30 10:52:08 Macintosh xgridagentd: Warning: error opening connection (Jacks Computer): Authentication failed
Jan 30 10:52:23 Macintosh xgridagentd: Warning: error opening connection (Jacks Computer): Unable to open: BEEPError 200 (Success)
Jan 30 10:52:23 Macintosh xgridagentd: Warning: error opening connection (Jacks Computer): Authentication failed
Jan 30 10:52:38 Macintosh xgridagentd: Warning: error opening connection (Jacks Computer): Unable to open: BEEPError 200 (Success)
Jan 30 10:52:38 Macintosh xgridagentd: Warning: error opening connection (Jacks Computer): Authentication failed
Jan 30 10:53:23 Macintosh xgridagentd: Warning: error opening connection (Jacks Computer): Unable to open: BEEPError 200 (Success)
Jan 30 10:53:23 Macintosh xgridagentd: Warning: error opening connection (Jacks Computer): Authentication failed
Jan 30 10:54:23 Macintosh xgridagentd: Warning: error opening connection (Jacks Computer): Unable to open: BEEPError 200 (Success)
Jan 30 10:54:23 Macintosh xgridagentd: Warning: error opening connection (Jacks Computer): Authentication failed
Jan 30 10:56:38 Macintosh xgridagentd: Warning: error opening connection (Jacks Computer): Unable to open: BEEPError 200 (Success)
Jan 30 10:56:38 Macintosh xgridagentd: Warning: error opening connection (Jacks Computer): Authentication failed
Jan 30 10:57:29 Macintosh /Applications/Carbon Copy Cloner.app/Contents/Resources/ccchelper.app/Contents/MacOS/ccchelper: kCGErrorInvalidConnection : CGSGetNextEventRecord: Invalid connection
Jan 30 10:57:29 Macintosh /System/Library/CoreServices/loginwindow.app/Contents/MacOS/loginwindow: Login Window Application Started
Jan 30 10:57:30 Macintosh launchd: com.bombich.ccc.scheduledtask.9E385C48-1FFF-4A13-8F98-DF4033634CAE: exited abnormally: Abort trap
Jan 30 10:57:30 Macintosh launchd: com.bombich.ccc.scheduledtask.9E385C48-1FFF-4A13-8F98-DF4033634CAE: 9 more failures without living at least 60 seconds will cause job removal
Jan 30 10:57:30 Macintosh loginwindow[241]: Login Window Started Security Agent
Jan 30 10:57:38 Macintosh xgridagentd: Warning: error opening connection (Jacks Computer): Unable to open: BEEPError 200 (Success)
Jan 30 10:57:38 Macintosh xgridagentd: Warning: error opening connection (Jacks Computer): Authentication failed
Jan 30 10:58:23 Macintosh xgridagentd: Warning: error opening connection (Jacks Computer): Unable to open: BEEPError 200 (Success)
Jan 30 10:58:23 Macintosh xgridagentd: Warning: error opening connection (Jacks Computer): Authentication failed
Jan 30 10:59:23 Macintosh xgridagentd: Warning: error opening connection (Jacks Computer): Unable to open: BEEPError 200 (Success)
Jan 30 10:59:23 Macintosh xgridagentd: Warning: error opening connection (Jacks Computer): Authentication failed
Jan 30 11:01:38 Macintosh xgridagentd: Warning: error opening connection (Jacks Computer): Unable to open: BEEPError 200 (Success)
Jan 30 11:01:38 Macintosh xgridagentd: Warning: error opening connection (Jacks Computer): Authentication failed
Jan 30 11:02:38 Macintosh xgridagentd: Warning: error opening connection (Jacks Computer): Unable to open: BEEPError 200 (Success)
Jan 30 11:02:38 Macintosh xgridagentd: Warning: error opening connection (Jacks Computer): Authentication failed
Jan 30 11:03:23 Macintosh xgridagentd: Warning: error opening connection (Jacks Computer): Unable to open: BEEPError 200 (Success)
Jan 30 11:03:23 Macintosh xgridagentd: Warning: error opening connection (Jacks Computer): Authentication failed
==== end====

Hello Alexandre,
First - thank you very much for taking time to offer thorough and informed advice.
However - as indicated in my last post, I have performed the first (and very basic) "test" - I checked to see if Xgrid was included in my network prefs and found that it was. I unchecked it because I don't have the setup to make use of processor resources on the other Mac I have in my home network. (And that other Mac is an old G4 eMac - not much help anyway!)
More specifically: it's apparent that I was using Xgrid "inappropriately" so I think the System Log really indicates that no connection can be found -because there isn't one!
I too still wonder about the "missing CPU 4" but, overall, I see no other indications that there's a problem. Activity Monitor shows all four CPU cores and they're all showing activity. I have not seen (or noticed) this in prior System Log reports so, if I see this again - I'll renew efforts to find it's significance and take appropriate action.
I then put my Mac Pro to sleep, waited a bit, then depressed an arrow key: the machine woke from sleep normally. This "solves" the immediate problem of abnormal wakening - at least I'm satisfied that it does and will continue monitoring for any similar "misbehaviors."
Power Management: I have purposely avoided doing anything with Power Management once I had it set to my liking. That is, I set the screen to sleep in 1 hour, I set the hard drive to "never" (sleep) and only use the Sleep menu command to put the Mac Pro to sleep. My dictum is to "not fix what isn't proved to be broken." Again - if I continue to have problems or new problems crop up, I will then go ahead and start making changes such as those you mention. (Like deleting com.apple.PowerManagemetn.plist)
Next: I did already run permissions repair and may do so again anytime I see problems which could be connected to permissions. Since I have "taken Xgrid" out of the picture, I don't think this particular permissions issue is going to be a problem under my current set up.
CarbonCopyCloner: Here we have a bit of a conundrum. I need! to keep CCC "available" to run scheduled back up tasks. I was given (a very expensive) 1TB wireless backup drive for Xmas and - through long trial and error - found that CCC is the most appropriate back up application for that drive.
For now: I consider that the problem is a bug in CCC and will contact Mr. Bombich about this.
Again: I do appreciate your pointing out this and the other things. You have helped me think through what could have been a very complex process in trouble shooting.
I think that my issue turned out to be simple: I may have accidentally touched the wrong key or key combination when I moved to wake the Mac Pro from sleep. I think that Xgrid was a problem but that now seems to be eliminated. The Mac Pro is now waking normally - which was my original objective.
Oh, and just to be clear: I forgot to mention above that I did re-examine the System Log and there are now no signs of the items in the log I posted originally here.

I'm booting from a new LaCie Thunderbolt SSD and it won't wake from sleep.

As my boot drive I have a new 1TB LaCie Thunderbolt SSD Disk. It's connected to a 27" 2.7 GHz Intel i5 iMac (mid 2011). I'm running OS X 10.8.2. Nothing else is connected on Thunderbolt.
Everything runs fine and very fast, with the one exception of not waking from sleep.
When I try to wake it up, the screen illuminates and the desktop is not completely frozen: I can drag windows around, but I can't open applications or do anything with the Finder. I get a spinning beachball if I move the cursor over the menu bar at the top. The only option is to restart.
I've contacted LaCie and they say their devices are "storage devices" and not "system drives". Yet I've been running my system from a 1TB LaCie D2 for at least a couple of years. I pointed out to LaCie support that nowhere on the box does it say their devices are for storage only.
Any suggestions?

@Kappy - not the most useful of replies mate to be honest.After all, there is a strong possibility that this has everything to do with the way OS X and the thunderbolt interface handle wake from sleep states.
@kbrine:
I am having exactly the same problem but with slightly different hardware:
iMac 27 (mid-2011) with Mountain Lion 10.8.2
Booting from a Crucial M4 SSD in an OWC SATA enclosure connected to a Lacie eSata thunderbolt hub (which is connected to the iMac).
In normal use the drive is super fast and works really well.
But my problem is exactly as you describe, put the machine into sleep, and on wake everything appears to come back ok however you can't open apps from the dock and the spinning beachball appears. You can't do anything else and you have to reboot.
Now the interesting thing is that if I put the machine to sleep and then wake it up again within 1 minute everything works perfectly. After a longer period of time - and I'm presuming when the energy saving profile moves to a deeper sleep state (I don't know for sure so speculation from me here) - I get the problem we are having and I have to reboot.
Here's what I've tried so far:
Updated my SSD to the latest firmware.
No firmware updates available for the OWC enclosure nor the Lacie eSata hub (at least, not that I could find)
Turned off bluetooth (others on this forum had a problem with BT interfering with Thunderbolt displays coming back on after sleep)
Turned off 'Automatic Brightness Adjust' (again, based on Thunderbolt Display problems that others have reported)
I've tried out AutoEJECT and Jettison apps that unmount all external drives and re-mount them when waking from sleep. They've made absolutely no difference. Save yourself a few $$ and don't bother buying them from the App Store.
I've tried unplugging and re-inserting the Thunderbolt cable connecting my eSata hub to the iMac. No effect.
And that's as far as I've got. There are only two things left for me to try:: disable 'Power Nap' which - apparently - can also cause problems with Thunderbolt devices during sleep. But I'm not confident with that being the solution. Turn the power off to the Crucial M4 when the problem occurs and then re-power it in the hope that it causes some sort of refresh of the connection to happen. Again, not sure that's a good solution either as I don't want to be powering down my SSD every time I bring the iMac out of sleep!!!
So I too am open to ideas and opinions on what might be causing these wake-from-sleep problems arising when Mac OS is booted from an external thunderbolt drive.

Is it normal to black out for 3 seconds on wake from sleep?

When my MBP wakes from sleep (usually from opening the lid), the wake from sleep sequences is pretty mystifying. At first I see my desktop screen, but then it goes black for 2 or 3 seconds, and then I can see my desktop screen again and start using the computer. Is this normal? If so, why is this?

I went into the Apple Store when this first started happening to my computer. They had just received a bulletin about it, calling it "safe sleep". It's supposed to keep the things you had on your desktop "safe" in case your battery gets low or something else happens to your computer. So it is "normal". I do find it annoying, however. It actually was happening less after I updated to 10.4.8, but I just did a firmware update (to Boot ROM MB11.0061.B03--check your system profiler) and now it occurs every time I put my computer to sleep for more than 1 minute. I do find it quite annoying, since I would rather have my computer "wake up" immediately when I open the lid (one of the usual bonuses of having a Mac). I noticed that someone said it could be turned off. I'll probably call Support and ask them, since I have AppleCare. I'll get back to you if I have any luck.
Also, remember to download all updates--it really does tend to fix problems that arise. Good Luck!

Wake From Sleep Reboots New Mac Pro 2.8 GHz 8-core 10.5.2

Add me to list of users with this problem.
I bought NEW computer yesterday.
Mac Pro 2.8 GHz 8-core 10.5.2
ATI Radeon HD 2600 XT
Yesterday, I ZeroWrote the OEM Apple hard drive and Installed 10.5.1 from OEM Install disks -- ran all updaters, repaired permissions numerous times during build.
Only 2gb OEM Apple RAM installed
Added on (from original installers): CS3, Office 2008, Toast 8.03, Stuffit 12.01, Silverfast AI 6.5x (Epson 4990). It appeared to be waking properly during the build.
Last night, last Software Update updater ran was ATI RADEON HD 2600 XT Firmware UPC 1.0.
This morning, wake from sleep rebooted machine.
Apple had me disconnect all cables, including power cable for a minute and then plug back in.
This worked for a couple few minute sleeps, but after lunch it rebooted again waking it from sleep.

I got my 8-core StartUp Disk deselected and have had only one auto reboot when waking from sleep.
HOWEVER, now I have heavy vertical bands twice now when it wakes up my 30" Cinema Display:
http://discussions.apple.com/message.jspa?messageID=6919620#6919620
It had wide vertical banding, white edges in corners and edges, and white fog over entire screen that seemed burned into the screen -- it eventually corrected itself back to normal after being on over a couple hours.
Second time, I had wide vertical banding, 6" and 3" wide with rows of white, green, blue pixels.
I connected the 30" to the old Mac Pro -- 10.4.11 -- AND THE BANDING GRAINY SCREEN APPEARED CONNECTED TO THE OTHER MAC like it was burned in the LCD.
So it appears the banding is in the monitor the monitor.
The burn-in cleared itself after being on about 120 minutes.
*It seems the new Mac Pros have some devilish issues with sleep on their Apple Cinema Displays to the point it is destroying the monitors -- or it is coincidence...*

MacBook Pro kernel panic on wake from sleep

I need some advice. Over the past few days, my MacBook Pro has been experiencing kernel panics when I open the screen and it wakes from sleep. The panic is immediate; there is no lag or time between opening the computer and the initiation of the event. It appears to be intermittent however and I wanted to get some input on this before I start troubleshooting it. Perhaps I may need to have Apple take a look at the unit but I would like to solve the issue (if possible) myself.
One thing I did notice is that the kernel panics started only after I recently updated Mac OS X with the most recent Security Update 2006-003, Quicktime 7.1 and Front Row 1.2.2. Not sure if this is related however, it is interesting that the panics started almost immediately following the software update.
Here is the panic log:
panic(cpu 0 caller 0x0019CAEF): Unresolved kernel trap (CPU 0, Type 14=page fault), registers:
CR0: 0x8001003b, CR2: 0x1e9b65c5, CR3: 0x00d65000, CR4: 0x000006e0
EAX: 0x00000000, EBX: 0x1e9b65c5, ECX: 0x00159000, EDX: 0x0040c9c0
ESP: 0x1e9b65c5, EBP: 0x13c33cc8, ESI: 0x001015c5, EDI: 0x039a1fc0
EFL: 0x00010297, EIP: 0x003b13c1, CS: 0x00000008, DS: 0x13c30010
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x13c33b58 : 0x128b5e (0x3bbeb8 0x13c33b7c 0x131bbc 0x0)
0x13c33b98 : 0x19caef (0x3c1340 0x0 0xe 0x3c10f8)
0x13c33c48 : 0x197b53 (0x13c33c5c 0x13c33cc8 0x3b13c1 0x2b100048)
0x13c33c54 : 0x3b13c1 (0x2b100048 0x39a0010 0x150010 0x13c30010)
0x13c33cc8 : 0x3b24f8 (0x39bb700 0x39a1fc0 0x3df3f0 0x162fcb)
0x13c33d08 : 0x379a4c (0x399c480 0x39a1fc0 0x13c33d48 0x3b1d64)
0x13c33d28 : 0x37d2a5 (0x23c4300 0x39a1fc0 0x23c4304 0x23c4300)
0x13c33d48 : 0x3a286a (0x23c4300 0x39a1fc0 0x13c33d78 0x3aecb5)
0x13c33d98 : 0x1885f0 (0x23c4300 0x2f180b4 0x2f180c8 0x11c970)
0x13c33dd8 : 0x12b389 (0x2f37eb4 0x2f18098 0x0 0x0)
0x13c33e18 : 0x124902 (0x2f37e00 0x0 0x18 0x13c33efc)
0x13c33f28 : 0x192efc (0x13c33f54 0x0 0x0 0x0)
0x13c33fd8 : 0x197fa6 (0x38d2318 0x38d2318 0x1e9b65c5 0x1e9b65c5) No mapping exists for frame pointer
Backtrace terminated-invalid frame pointer 0xbffff358
Kernel version:
Darwin Kernel Version 8.6.1: Tue Mar 7 16:55:45 PST 2006; root:xnu-792.9.22.obj~1/RELEASE_I386
Model: MacBookPro1,1, BootROM MBP11.0055.B03, 2 processors, Intel Core Duo, 2 GHz, 1 GB
Graphics: ATI Radeon X1600, ATY,RadeonX1600, PCIe, 256 MB
Memory Module: DIMM1/BANK 1, 1 GB, DDR2 SDRAM, 667 MHz
AirPort: spairportwireless_card_type_airportextreme (0x168C, 0x86), 0.1.17
Bluetooth: Version 1.7.3f4, 2 service, 0 devices, 1 incoming serial ports
Network Service: AirPort, AirPort, en1
Serial ATA Device: ST910021AS, 93.16 GB
Parallel ATA Device: MATSHITADVD-R UJ-857
USB Device: Built-in iSight, Micron, Up to 480 Mb/sec, 500 mA
USB Device: Apple Internal Keyboard / Trackpad, Apple Computer, Up to 12 Mb/sec, 500 mA
USB Device: IR Receiver, Apple Computer, Inc., Up to 12 Mb/sec, 500 mA
USB Device: Bluetooth HCI, Up to 12 Mb/sec, 500 mA
Thanks!
MacBook Pro 2 GHz 1 GB Ram Mac OS X (10.4.6)

One other thing I noticed that could or could not be the problem but is sure curious is the option in the Energy Saver control pane for automaticly dimming the screen before sleep. I first noticed when I got my MacBook Pro that this option was enabled without it be marked as on. I checkmarked it then unchecked it again and the screen did not appear to dim before sleep anymore. However, since the last kernel panic on Monday, I have reenabled the option thinking it could possibly be this. It's kind of far fetched I know, but my system has been stable for past 2 days so perhaps this software flaw in the Energy Saver is the blame. Sort of makes sense since this timmer for dimming is activated before sleep of the display which might corrispond with some part of the sleep/wake system of the computer and/or Mac OS X. Later, I am going to try turning the dimmer off and cycling the computer from sleep to wake and see if I get a panic. I'll keep everyone posted as to my results.

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.

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

Display Changes Resolution When Computer Wakes From Sleep

I have a MacBook Pro bought in May of 2006. In the last year, this problem has been getting progressively more annoying to me. When the computer wakes from sleep (not every time, but most of the time) the screen will flash blue, then reset the resolution to 640 x 480, I think. To fix it, all I have to do is go to System Preferences and change the resolution, but when I do that, it pops up two windows, like it thinks I have a dual display set up. To fix this, I always click 'detect displays,' and it fixes it, but the next time I wake the computer from sleep, it does it again. This isn't really an urgent problem, but I would expect my computer to behave a bit better for me.
Thank you in advance for any aid you might give me.
Lisel

Hi Lisel. I have a similar age MacBookPro that does the same thing. I don't really know how to fix it I'm sorry, I wish I did cause it's annoying. I just thought I'd let you know you're not the only one with this issue.
Basically, for some reason it thinks it has two displays connected, even when there isn't. To stop it being a total pain, make sure when it does come up with the two Display Pref windows to set them both to 1440x900, at least then when it does go dual display it won't be 640x480 and you can still read stuff.
I've also left the Display Pref icon on the top tool bar (next to the AirPort and Bluetooth and stuff), so I can just click that and Detect Displays. When it does that it figures out for itself it doesn't actually have two displays connected and so goes back to normal.
I know that's a workaround and not a fix, sorry. I'd be keen to know if anyone else has any better solutions:)
Thanks,
Mark.

Wakes from sleep then sleeps again

Similar Messages

Maybe you are looking for