Sleeping/Waking an Xserve G5?

I've been doing a bunch of testing recently and am having an (interesting) problem trying to get an XServe G5 to wake from sleep. Sleep mode clearly works (as the power light will pulse, as expected), but every mechanism that I use to wake it fails.
Waking with ARD will attempt to start the machine, and fail after 10 or so seconds saying communication failed.
Sending the magic WOL packets through perl scripts, 3rd party tools, and other ways all fail.
Diagnostics:
I have verified that the nodes are (apparently) configured for the Wake-on-LAN access:
root# systemsetup -getwakeonnetworkaccess
Wake On Network Access: On
I have also verified that the magic packets are sent properly using tcpdump to inspect the packets. They are sending the magic sequence properly.
Figuring that the XServe G5 may only listen for WOL packets on en0, I tested only that port. (For what it's worth, en1 also failed the waking process.)
The node can be woken up by pressing the power button quickly. The restore DOES work, just not the WOL portion.
Has anyone had any experience with this problem?
1,750 clustered XServe G5s   Mac OS X (10.4.3)   2xDual 2.0Ghz G5 PowerMac, 2.0Ghz MacBook Pro

Sending the magic WOL packets through perl scripts, 3rd
party tools, and other ways all fail.
You don't say what third-party tools you tried, nor whether
any of the methods you tried work on other non-Xserve Macs.
Just for curiosity, so that we know we are starting from a
good test basis, try the free Wake-on-Lan utility:
http://www.readpixel.com/wakeonlan/index.html
I've never tried it on my Xserve G5, but it does work on the
other Macs on our LAN.
Russ
Xserve G5 2.0 GHz 2 GB RAM   Mac OS X (10.4.8)   Apple Hardware RAID, ATTO UL4D, Exabyte VXA-2 1x10 1u

Similar Messages

  • Problems going to sleep, waking up, restarting, etc

    I just bought a refurbished Macbook...and we are already developing an intense love/hate relationship because of it's eratic sleep behaviors. So this morning I tested it by trying various methods of sleeping/waking/restarting.
    Here are my morning Macbook activities:
    1: Macbook is sleeping, I open it...it appears to be functioning...then 5 minutes later, I get the "you need to restart your computer" box (the one with all the different languages)
    2: Restart--Freezes on blue screen with rotating wheel
    3: Turn off/on using power button
    3: Put to sleep using Option/Command/Eject; wake using power IT WORKS!!!
    4: Put to sleep by closing lid; open to wake and it seems to work! I try to shut down using the Apple menu...and I get the spinning beachball...
    5: Turn off/on using power button
    6: Reset PRAM
    7: Put to sleep using Option/Command/Eject; wake using power
    IT WORKS!!!
    8: Put to sleep by closing lid; open to wake...seems to work but the spinning wheel appears on the desktop and I have no mouse...so I have to restart it AGAIN
    9: Put to sleep using Option/Command/Eject; open to wake;
    IT WORKS!!!
    10: Put to sleep using Option/Command/Eject; wake using power...seems to work but when I open my airport menu, it freezes and the menu becomes unaccessible and will not disappear...restart AGAIN
    11: Put to sleep by closing lid; open to wake...so far, so good...
    This basically covers every issue my Macbook has had in the last week, except for the three or four times it just won't start and sits on a black screen, going through some script indefinitely...yeah...that one didn't repeat today.
    Yes, my software is up-to-date...
    Yes, I reset my PRAM...
    Yes, I reset the SMC...
    Any suggestions would be much appreciated!

    Hi -
    I'd try booting to your Install DVD while holding 'D' ...this will launch the Apple Hardware Test.
    If things are fine here, then start to that DVD again but this time hold down 'C'. When you finally have a 'top menu' bar across the screen, use it and launch Disc Utility and then verify and repair both permissions and the disc itself.
    On restart, reset your SMC once again...
    http://docs.info.apple.com/article.html?artnum=303319

  • Problems sleeping, waking up from sleep

    My MacBook sometimes behaves oddly when sleeping.
    1. Often, the sleep light is solidly lit for at least several minutes before going into the pulsing mode. This can happen when I close the lid or when I choose sleep from the apple menu. Sometimes it never goes into pulse mode, at least not for 15 or more minutes.
    2. If I open the lid while the light is solid, the screen will usually (always?) stay black. Closing the lid will sometimes make the I'm-waking-up optical drive noise. When that happens, sometimes the backlight will go on (while the lid is still closed), sometimes not. If it doesn't go on while closed, the backlight will sometimes come on when the lid is opened, but sometimes it stays dead.
    3. If I cannot persuade the machine to wake up, and waiting doesn't cause it to go into pulse mode, a few times quick presses on the power button has woken it up. Otherwise, I have to power cycle.
    4. Sometimes when the machine does wake up, the screen stays almost entirely black. Pressing the brightness-increase keys (Fn-F2, in my case) has no effect. I can very faintly see things on the screen, so I can (for example) see that apple-tab apple-Q is indeed shutting things down. (The list of barely visible icons gets shorter.) Hitting a save/cancel dialog is almost impossible, as is finding shutdown on the apple menu, so I usually end up power cycling.
    5. Sometimes, not always, when the machine wakes up the screen is several notches down in brightness, so I have to bump it back up (Fn-F2). I run it on the highest brightness.
    I have reset the PRAM, NVRAM, and SMC. Firmware and OS are up to date. (1.1, 10.4.9).
    Macbook Core Duo   Mac OS X (10.4.9)  
    Macbook Core Duo   Mac OS X (10.4.9)  

    Welcome to the Apple discussions.
    If the restart message is one with several languages, that's a kernel panic. It is usually, but not always, caused by hardware, and within hardware, memory is often the issue.
    First thing I would do is to run the Apple hardware test. Try rebooting holding the D key down. If that doesn't bring up the AHT, insert the first OS X disk that came with your system, and reboot holding the D key down (or hold the alt/option key down and choose the AHT). Choose the extended test when prompted. Does that show up any hardware issues?
    You can also run a program like rember to test the memory. Run it overnight: http://www.kelleycomputing.net/rember/
    This kernel panic FAQ is pretty thorough: http://www.thexlab.com/faqs/kernelpanics.html
    You can also try reseating the memory to see if that makes a difference (take it out, put it back in, to ensure a good connection).

  • Mac mini sleeping/waking problems

    Hello everyone,
    I'm experiencing constant issues with my mac mini.
    To awake it from sleep I have to push the power button, the screen goes grey with a progress bar display - not unlike on my macbook pro when resuming from low batteries - and all the drives connect to it appear to have been ejected incorrectly.
    I tried the usual troubleshooting steps, bar resetting smc, so far.
    My system details:
    Mac mini 2012 | 16GBram | 2.7 Ghz Quad Core | Mavericks 10.9.5
    Any suggestion highly appreciated
    val

    rwgleaves wrote:
    I took it to the Apple store Genius bar today - my 5th trip - and they did just what I'd hoped.  They replaced the Mac Mini with a brand new machine. 
    This is why I buy Mac/Apple!
    Excellent new, sorry you had so much trouble on the way. And yes, Apple Stores are awesome!

  • Sleeping, waking problems

    I purchased my macbook fourteen months ago and only began using it regularly when my imac was being repaired.
    After using it in mornings, I close the lid and the sleep light comes on. In afternoons, I raise the lid, the sleep light goes off, but the screen stays black. I can only get the on screen by restarting via power button. this problem occurs on a regular basis.
    The battery is not the problem and I've disconnected external devices.
    Also, when I put it in sleep mode with the lid up, it sometimes awaken by itself.
    Thankfully, I have applecare, but they haven't identified the problem. I would be very appreciative of information I can relay to the repair person.

    wow i used to have the same problem. i sent it into apple and they had to replace like a logic board or system controller?? but since yours is over a year old it has no warranty unless u got applecare i guess u would have to pay... ;(

  • Repeated, seemingly random system freezes which "reset" by sleeping/waking

    My FW800 1ghz (shortly after APP expiring, natch) began unpredictably freezing (pointer moves, but all apps go unresponsive, audio stops, etc). I can't establish a pattern with it; sometimes I am not even in the room - for example I'll happen to hear iTunes stutter, then stop, then sure enough I'm in a freeze.
    During the freeze, I can attempt to move windows around or apple-tab between apps, but nothing. I somehow discovered that the way out of this is to use the power button to put the system to sleep. After pressing the power button to sleep, the system will appear to hang for one, five, sometimes as many as ten more minutes, then in a flash everything I might have tried to do since the freeze (like move windows or open menus) will happen in very quick succession (within a half a second) then the system will sleep. I can then wake the system, and then it behaves completely normally, as if nothing at all had ever been out of the ordinary. Sometimes I go several days without a freeze, sometimes it happens a few times within a day.
    I am inclined to think that this is a hardware issue, since an erase and reinstall from scratch did not resolve the problem. I've "memtested" my RAM within an inch of its life and it's clear. Does anything have any inklings about this? Is this perhaps a cache going bad (this is where my knowledge about the system workings gets very thin)? The fact that all the instructions I'm putting into the system "during" a freeze DO manage to execute, eventually (at the brink of sleep), tells me that something is bottlenecking it all... but.... what?
    G4 FW800 1ghz   Mac OS X (10.4)  

    Have you run the Apple Hardware Test?
    Do you have any Seagate SATA 7200.9 or .10 drives?
    Disk Warrior 4.0?
    Ever since I started using Applejack, I don't use anything else to remove cache files, but I do use it from time to time. And I do a lot of backups and restores of the boot drive (like to change my system configuration a lot I guess).
    Zeroing a drive may, but it may not, remap bad sectors. Unless you use TechTool Pro 4.1.2 or later, or Intech Speedtools to check, in some cases a 7-way write is needed.
    I would assume you have "enough" memory, ie, 1GB or more. And have installed newer drives as well. That the boot drive has ample free space.
    iTunes is great for finding RAM errors. Applejack now has option to install and use Memtest from Single User Mode. And my preference is to use FSCK or an emergency boot drive to repair drives, NOT use the Tiger DVD which has an older version.
    Some systems could have RAM or disk errors even during or right after a reinsall. Shouldn't happen, but there is a lot of file fragmentation installing and upgrading that goes on.
    I would invest in a new 300GB-ish drive and begin using Applejack. Also, run you system without 3rd party stuff like background processes, and see if it happens - and if it happens during Safe Boot.

  • Mac Pro Ports cycling power during sleep - waking up drives

    If I try to sleep my Mac Pro 6,1 under Yosemite, everything powers down as expected, I’ve even successfully used ‘Jettison’ to eject the USB drives on the first sleep power down.  However, the Mac then powers its ports back up, awaking the USB and Thunderbolt drives, and other USB peripherals, and in doing so remounts the disk, which then when it goes back to sleep is incorrectly ejected.
    There seems to be a roughly 2 minutes cycling of power of the ports when it sleeps.  Powers all down in about 30 seconds, all lights out, screens go dark.  Then maybe 30 seconds later the ports power back up, the drive lights (and other USB devices) power back up, maybe for 30 seconds before then powering back down.  The screens do remain dark throughout this per Sleep.  All this happens while under Sleep, and carries on cycling ports power this way, mounting and ejecting drives incorrectly each time as it goes…..  This doesn’t seem right?  It never happened under Mavericks. Have I got a Yosemite bug or a hardware issue cropped up by chance when I powered down my computer over Christmas and then installed Yosemite as a clean install?
    The Thunderbolt Lacie RAID is NOT being incorrectly unmounted. That's fine.
    The two 1TB WD drives in a Hornettek Serial ATA USB 3 connected enclosure are being incorrectly unmounted during sleep as detailed above.
    Both these external drives are directly plugged to the MacPro.

    Whew, I thought I was the only one with this problem. I'm also getting the "double-click" sounds when trying to wake the machine up from the dead zone (after going to sleep- either on its own or after attempting to awaken it a few minutes after manually putting it to sleep).
    I've had my computer serviced by a Mac-authorized repair center three times for this issue. The first visit resulted in an operating system upgrade to Leopard, which seem to fix the issue for a few days. When it reappeared, the second visit resulted in a logic board switch- the technician actually kept it there because the problem reoccurred after testing the new board. He then found a broken wire in the power supply and replaced that. On the third visit, they actually had to send it in to the Apple engineering department- who replaced the video card with an updated version of the same.
    This is driving me insane- the repair center knows their stuff (I'm in IT, myself so I know they're not incompetent)... they've exhausted nearly every possible solution- replaced every component, different OS, etc... the apple engineers couldn't even fix it. I dread going to the Apple Store because I know the people at the Genius Bar are way less knowledgable than the guys I go to... but since I'm still under AppleCare, I may be able to get a machine swap if they can't fix the problem in a few weeks.

  • IChat, sleeping/waking computer

    every time my computer goes to sleep, it disconnects me from ichat, and when i wake my computer, it reconnects. is there a way i can change the settings so it stays connected??

    Hi
    Its because its going to sleep your mac disconnects from all network activity.
    You could go to sys prefs/energy saver/sleep and change "put computer to sleep...." to never and set "put display to sleep...." to what you want.
    Tony

  • Issues with 13" Macbook Pro Retina sleeping/waking and starting up?

    I am having 2 issues which are driving me insane.
         1. It will not wake after the lid is closed for more than an hour or 2 and I have to hold the power button down to turn it off and startup again. - SO ANNOYING!
         2. Occasionally it will not startup. It makes it to the apple logo screen with the spinning thing and just stays on that screen (I have left it overnight and nothing      changed), and I am forced to hold the power button down to turn it off and startup again.
    Not impressed, its been like this since day 1. Its only a month old today.
    Any information would be helpful considering apple care talk to me like im an idiot, e.g. "Have you tried turning it off and on again?". I work in I.T. so i've tried most things, such as SMC reset and clearing the PRAM to no avail.
    Thanks guys

    I'll just assume no one can help then...

  • Trying to figure out these KP when waking from sleep...

    I've been dealing with this for a while now and have come up with 2 new errors. This is happening when the computer is woken from a long state of sleep. I can't seem to reproduce it simply by sleeping & waking the computer.
    Unresolved kernel trap(cpu 1): 0x300 - Data access DAR=0x000000005330A9BC PC=0x000000000033BB94
    Latest crash info for cpu 1:
    Exception state (sv=0x5b3dea00)
    PC=0x0033BB94; MSR=0x00009030; DAR=0x5330A9BC; DSISR=0x40000000; LR=0x0033BB8C; R1=0x63617580; XCP=0x0000000C (0x300 - Data access)
    Backtrace:
    0x00000000 0x0033BBE8 0x0033FF6C 0x00340394 0x5B302088 0x638DD5B4
    0x644FFC10 0x64500F6C 0x64501124 0x644F010C 0x644DD724 0x644E9CB0 0x644E427C 0x644E4100
    0x644E3F5C 0x0035A028 0x644E3D8C 0x644E3E9C 0x6377F374 0x6377F24C 0x6377F0A8 0x0035A028
    0x6377F02C 0x0034C700 0x0034CAC4 0x0003F9BC 0x000B0E54
    Kernel loadable modules in backtrace (with dependencies):
    com.apple.driver.AppleOnboardAudio(2.5.7f2)@0x644db000->0x6451ffff
    dependency: com.apple.driver.AppleDBDMAAudio(2.5.7f2)@0x644ad000
    dependency: com.apple.iokit.IOAudioFamily(1.6.5fc3)@0x63779000
    dependency: com.apple.iokit.IOUSBFamily(3.2.7)@0x6370c000
    com.apple.iokit.IOAudioFamily(1.6.5fc3)@0x63779000->0x63798fff
    dependency: com.apple.kext.OSvKernDSPLib(1.1)@0x636bc000
    com.apple.driver.AppleK2(1.7.2f1)@0x638d9000->0x638dffff
    dependency: com.apple.iokit.IOPCIFamily(2.5)@0x5b2f9000
    dependency: com.apple.iokit.IOKeyLargo(1.7.2f1)@0x638c0000
    dependency: com.apple.driver.IOPlatformFunction(1.8.7d5)@0x5b313000
    com.apple.iokit.IOPCIFamily(2.5)@0x5b2f9000->0x5b30cfff
    Proceeding back via exception chain:
    Exception state (sv=0x5b3dea00)
    previously dumped as "Latest" state. skipping...
    Exception state (sv=0x5b365a00)
    PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)
    BSD process name corresponding to current thread: kernel_task
    Mac OS version:
    9G55
    Kernel version:
    Darwin Kernel Version 9.6.0: Mon Nov 24 17:39:01 PST 2008; root:xnu-1228.9.59~1/RELEASE_PPC
    System model name: PowerMac7,3
    panic(cpu 1 caller 0xFFFF0003): "Uncorrectable machine check: pc = 00000000000CE03C, msr = 1000000000101030, dsisr = 00008000, dar = 0000000084C9AA44\n" " AsyncSrc = 0000000000000000, CoreFIR = 0010000000000000\n" " L2FIR = 0000000000000000, BusFir = 0000000000000000\n"@/SourceCache/xnu/xnu-1228.9.59/osfmk/ppc/tr`

    Hi-
    I'd test the RAM, as errors from the RAM handling data can corrupt system software on the hard drive.
    I'd test the hard drive, for above stated reason, as well as other corruption (non-RAM related errors) can also cause data access problems.
    Beyond this, data access will occur via the VRAM of the graphics card, and via the cache of the processor.
    Since you have been down the graphics card route, cache malfunction could be a possibility.
    Along with Rember, run the system test from the AHT (Apple Hardware Test).
    *A couple of notes on the Ballistix memory:*
    The voltage rating is 2.8v, whereas the G5 uses a 2.5v rated DIMM.
    DDR2 memory is rated at 2.1v, but the dual core G5 is rated at 1.8v.
    Dual core G5's support CAS ratings of 4 and 5, but the Ballistix are CAS 3.
    Crucial memory selector *does not recommend* Ballistix for any Mac model.
    Granted, the RAM may function, but it does not meet spec, and can create phantom problems.
    More notes from MacGuru's forum:
    [Norm LeMieux] ...there's potentially another issue with DDR2 that may not have existed before for Macs: high-speed memories. If you look at Crucial's Quad-compatible modules (1GB), you'll see PC2-4200 modules with 4-4-4-10 timing at the top, followed by PC2-5300 modules (which are CL=5 @ 667MHz, but probably 4-4-4-10 @ 533MHz). This is the performance when the modules are powered by the standard voltage of 1.8V.
    Ê The high-performance Ballistix modules can do 3-3-3-12 @ 533MHz, but they require a higher voltage: 2.1V. This is fine if you have control over your memory rail, but the Mac does not. And since the SPDs are programmed with "JEDEC-standard PC2-4200 values", the OS is just going to program the memory controller to run the same (4-4-4-10). Thus, there's no point [currently, on the Mac] is buying the high-performance modules which are $160 more per 2GB kit.
    Ê Crucial has admitted that, if the system cannot operate at 2.1V, then it will "throttle down" and run at the standard rate. This mirrors what others have been saying elsewhere on the 'Net, but hopefully there's a little more information here.
    I've seen many posts of system troubles that were the result of trying to use memory that was "better" than what is spec'd.
    The facts of the matter are, that Mac's cannot really benefit from so-called "high-performance" memory due to the control of memory speed by the SPD.
    Furthermore, using a product like Ballistix, which is targeted to the PC overclockers crowd, tempts fate with memory that is not of the spec put forth by Apple Developers.
    Power Mac G5 Computers (October 2005) Memory Specs
    G5 RAM Expansion Specs

  • 2009 Quad MP freezes after waking from sleep

    Hey again.
    I've read numerous reports about the sleep/waking problem but mine seems to be different. I even created a new main admin account to see if some of my preferences (I migrated my user accounts from an iMac over to the new MP) and still having the same issues.
    If I let the system go to sleep it will on its own but when I wake it up the keyboard and mouse don't do anything. I even unplugged the mouse/keyboard and plugged them back in and still nothing. I have to hold the power button down to shutdown. Upon restarting everything is fine again.
    Now if I put the system to sleep manually it will sleep and wake perfectly!! I know I can work around this by not letting it go to sleep on it's own but why would be wake from sleep one way but not the other?
    Any help welcome.
    PS. I have a OWC 1TB FW800 hooked up, Wacom tablet/pen, keyboard and that is it. I have the hard drives set to 'sleep', and only have istat menu bar running. I've tried it with that off and no programs running and still have the same results.

    but after I bought this MP it's been headache after headache. (Sleep issues, monitor issues..)
    Are you still under warranty? Can you have the machine replaced? I would try to do that... No reason for bad experiences from a brand new machine. No one deserves that and you may just have gotten a machine by nature that is a bit buggy. Granted the dust is still settling about these Macs and how they play out in the real world. But consistent problems like yours, are worth fixing. Getting the Mac replaced would be ideal.
    JM is probably right about the driver, I forgot that too. One removes everything except the kernel of trouble in the first place. It's a shot anyway. There could be more going on.

  • How to stop my Time Machine external hard drive preventing iMac from sleeping?

    I have a late 2012 iMac, and have discovered that sometimes (I haven't noticed a pattern of when it doesn/doesn't happen) the computer will immediately wake up after I set it to Sleep (Apple Menu>Sleep). Through elimination I have found that it is the the USB 3.0 external hard drive I use as a Time Machine back-up that is the culprit; unplugging it then allows the computer to sleep. If I unplug it, then plug it back in later on, this normally solves the problem for a while, but not forever. This same Hard Drive didn't cause the wake problem on my previous '08 iMac.
    A big issue is that when the machine immediately wakes from sleep, the display stays off (until I move the mouse) - this is good from a power saving point of view, but means I don't know if/when the machine is immediately waking from sleep (I have to listen to the fan when setting it to Sleep mode to hear if it has actually woken back up).
    I've searched the forums, but can't find another poster with the same problem as myself. Can anyone advise a course for me to pursue to prevent this from happening?
    Thanks. Jamie

    Hi Frank. Nope, I'm still having the same symptoms; the plugged in external drive (TIme Machine) will wake the machine up a couple of seconds after it winding down when put to into sleep mode. Ejecting the drive and then sleeping the machine works. After plugging it in again to do a Time machine backup, it will allow the computer to sleep soundly for the first few sessions (eg a few days of sleeping, waking, sleeping, waking, etc), but then it will then suddenly start preventing it from sleeping again after a while.
    It seems I'm fortunate in my case that the display stays dark (or off?) when the machine has been woken from sleep, but this was actually preventing me from knowing the machine wasn't in fact asleep for quite some time; I only eventually cottoned on because there wasn't any delay when 'waking' my machine (which there normally is). I would then have to carefully listen to the spinning fans to know if in fact it had gone to sleep or not.
    So, to summarise, unfortunately no, I haven't solved this yet. If anyone else has a solution, please let us know?
    Also, I've noticed occasionally after waking that there is a relatively quiet 'crackle' sound (kind of electrical sounding) from the bottom-right area of the machine. This goes on every so often for about 30mins. I see this is also an issue with other people's late 2012 iMacs, but I've not seen if anyone has a solution to it?

  • OS X 10.4.6 Update problem-Waking up

    hello everyone.
    I am a new mac user after finally having enough of Bill's Windows Bulls*.
    I did the 10.4.6 update and since then it appears that when my comp goes to sleep it seems normal but when I open the cover of the laptop it doesnt wake up. Just a black screen. Is anyone else having this problem.
    So I sit and wait, move the mouse around click keys and get nothing...causing me to have to turn off the laptop manually with the power button. Then when it loads it may freeze or I get a warning saying to hold down the power button to restart, finally after a few trys is will restart normally.
    Any ideas? I have liked my mac for the past month since I have made the switch from windows but this is getting me frustrated.
    Thanks
    ~Tony

    Welcome to the Apple Discussions!
    Does the same thing happen if you choose "Sleep" from the Apple menu, without closing the lid, and then try to wake it up?
    Then when it loads it may freeze or I get a warning saying to hold down the power button to restart, finally after a few trys is will restart normally.
    I think this is your bigger issue. It sounds like you're seeing a "kernel panic".
    http://docs.info.apple.com/article.html?artnum=106227
    Is this what you're seeing? If so, repairing the trouble that's causing your kernel panic will probably also help cure your trouble with sleep & waking. There are a couple of helpful links you might want to check out:
    http://discussions.apple.com/thread.jspa?messageID=607531
    http://www.thexlab.com/faqs/kernelpanics.html
    -Doug

  • External display and sleep issues

    A 15-inch MacBook Pro worked fine with an external display and keyboard prior to the 10.5.2 update. After the update the external display goes dark when the laptop is closed. Hitting the external keyboard momentarily wakes up the external display but then it almost immediately goes back to sleep. It's as if the MBP thinks it's in battery mode and not plugged into an AC outlet.
    All Energy Saver settings are to keep the display awake. Could this be a corrupt driver or some other issue?
    Thanks.

    Theres been a lot of disscussion about this and it's a BIG problem. Check this out:
    http://discussions.apple.com/thread.jspa?messageID=6597635&#6597635
    http://discussions.apple.com/thread.jspa?messageID=6669894
    A lot of us are having the following problems after the graphic update:
    -not waking from sleep (waking, but display staying dark, restart is only solution)
    -not being able to use in clamshell mode (with external monitor)
    -not being able to run external monitor at full resolution
    I've also had some weird bugs like the settings and calibration of my external somehow coming over to my MBP monitor after disconnecting the them.
    I hope Apple can fix this.
    Tim

  • Apple wired keyboard cause unwanted wakeup from sleep

    Hi,
    when I want to sleep (either by keyboard or power button) Mac mini, the computer enters sleep.
    Unfortunately, after a few seconds, the computer wakes up without interference.
    I've tried all the recommended procedures to fix problems with sleeping/waking without success.
    When I disconnect the keyboard and press power button, the computer falls to sleep and remains in sleep.
    When I connect this keyboard to another Mac Mini, this is also self-awakening.
    Please, can anybody help me with this strange problem?
    Thanks
    === from kernel.log ==========================
    May 25 21:13:13 mini kernel[0]: System Sleep
    May 25 21:13:14 mini kernel[0]: Wake reason = EHC2
    May 25 21:13:14 mini kernel[0]: System Wake
    May 25 21:13:14 mini kernel[0]: Previous Sleep Cause: 5
    May 25 21:13:14 mini kernel[0]: The USB device Keyboard Hub (Port 4 of Hub at 0x26000000) may have caused a wake by issuing a remote wakeup (2)
    May 25 21:13:14 mini kernel[0]: The USB device Apple Keyboard (Port 2 of Hub at 0x26400000) may have caused a wake by issuing a remote wakeup (3)
    ========================================

    As I noted above, computer goes to sleep by every way - power button, sleep timer, shortcut or menu.
    But remains sleeping ONLY with keyboard unconnected.
    Problematic keyboard worked well for many months until recently.
    Same situation is on another Mac mini.
    With another keyboard (from old PC) everything works fine (except hibernating shortcut, of course).

Maybe you are looking for

  • After the 10.9.4 update, ssh no longer worked until I poked a firewall hole for sshd-keygen-wrapper

    I upgraded two of my Macs, a Mac Mini, A, and a MacBook Air, B, to OS X 10.9.4, using Software Update. After that, I could no longer ssh from A to B, but ssh from B to A worked fine. After some poking around for differences, I then noticed that in Ma

  • System Error due to JCO communication failure? during mapping

    in my JDBC-XI-Proxy scenario, there is BPM with a transformation step, in that step, during execution it gives Jco failure error, and particularly when the payload is very large.... my question is: 1.  how JCo communication failure occurs in case of

  • How do I delete 9.4 GB of email from my ipad?

    How do I delete 9.4 GB of email from my ipad so I have enough space for ios 7?

  • Vol_init

    Loaded Solaris 10/08. Upon logging in I'm getting errors stating fatal: vol_init: already a daemon running. Then the volfs just goes into maintenance. I have tried clearing the service through svcadm but immediately on the console I see 10 messages o

  • Photoshop CS5 can't handle lots of text..?

    Recently migrated to CS5. Was running Photoshop CS5 just fine for a week, working mainly on images... but now that I need to work on something that has more text in it (like a graphical CV) the screen isn't reflecting the changes I'm making. I can cl