Disconnects when lid closes

I was curious if there is a setting that when you close the lid to your laptop that it doesn't disconnect you from being on-line?? When i re-open the top my AIM and internet is logged off..
Mac Book   Mac OS X (10.4.8)  

When you close your screen, your computer is essentially sleeping. So the harddisks stop. Meaning no data transfer at all..
If you want, get lucky and buy a new macbook that doesnt sleep when you close the lid. haha. mine did that. but i got it fixed.

Similar Messages

  • Urgent: Shut down when lid closes problem

    My Mabook pro / mid 2010 / Yosemite 10.10 shuts down when lid closes. This is new in the last few days, not after any system updates. It wont restart after lid opens again, unless repeatedly holding down power button for long periods. Strangely, the sleep light is on before I open the lid, but once lid is open, it's completely off.
    Does anyone know the cause and/or fix for this? I'm really worried it's the beginning of the end, and I rely on this machine for work and need to travel in a few days! Thanks in advance for any trouble shooting tips.

    Just to clarify; when I say "this is new" I mean the problem, not the laptop.

  • Shutting off when lid closes

    I just bought a 13 inch MBP yesterday. I know macbooks are supposed to sleep when the lid is closed by default. But a few times when I opened the lid, the computer had appeared to turn completely off. The indicator light on the front was steady when the lid was closed, not blinking like I believe it is supposed to be when sleeping.
    Any ideas?

    1. Within 14 days of purchase of an Apple product, you can either return it or exchange it for a new one.
    2. You have 90 days of free tech support from Apple from the date of purchase.
         AppleCare: 1-800-275-2273.
    3. For
        A portable Mac doesn't appear to respond properly when you close or open the lid.
        Reset SMC. http://support.apple.com/kb/HT3964
        Choose the method for:
        "Resetting SMC on portables with a battery you should not remove on your own".

  • Laptop shuts down when lid closes

    My 15" powerbook has been acting up the last few days ever since I downloaded the last group of updates. When I close the lid to put it to sleep the entire computer shuts down. When I open it and start it up it gives me the message that the computer was unexpected shut down. Any ideas?

    Sorry, then I have to give up
    Hopefully an other user can provide more assistance to you.
    I would give Apple a phone call and ask for support, since it seems to be affiliated with the replacement battery (at least I would state so to get support).

  • Restarts when lid closes

    Sometimes when I close the lid in battery mode I here the TA DA! and I open the monitor and here the OS X is booting up like on a restart. It does not happen all the time. Any ideals what could be causing this? I leave my power settings in the Normal mode.

    I have the same problem... But, more often than not, if I close the lid while it's still "thinking" about shutting down, I get frozen in some weird zombie limbo, in which the computer is half-shut-down, but, like, frozen in sleep mode... and i have a **** of a time getting it to respond and restart. when i finally DO restart, i get a message saying it wasn't shut down properly. (tho: it WAS shut down properly. it's just this bizarre restart it does when i shut the lid.) would LOVE advice!

  • Ichat/internet disconnecting when lid is closed

    Hello,
    Whenever i'm online using ichat or I doing anything internet-related, when i shut the cover of the computer everything signs off....i get disconnected from the internet completely and kicked off of ichat/aim. how can i shut this off?
    Thank you!

    Closing the lid puts the computer to sleep, which closes all of its network connections except for the ability to wake it up by sending it a magic packet over the Ethernet interface.
    (28178)

  • [SOLVED]laptop suspend when LID close, even set HandleLidSwitch=ignore

    i've modify
    HandleLidSwitch=ignore
    systemctl restart systemd-logind.service
    But when close LID, it suspend.
    Then i click some key on keybord , it come back.
    /var/log/everything:
    Mar 21 11:20:59 localhost logger: ACPI action undefined: PNP0C0A:00
    Mar 21 11:21:06 localhost dbus-daemon[317]: dbus[317]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.229" (uid=1000 pid=22838 comm="systemctl stop laptop-mode.service ") interface="org.freedesktop.systemd1.Manager" member="StopUnit" error name="(unset)" requested_reply="0" destination="org.freedesktop.systemd1" (uid=0 pid=1 comm="/sbin/init ")
    Mar 21 11:21:13 localhost systemd[1]: Stopped Laptop Mode Tools.
    Mar 21 11:21:15 localhost logger: ACPI action undefined: PNP0C0A:00
    Mar 21 11:21:37 localhost systemd[1]: Reloading.
    Mar 21 11:21:37 localhost systemd[1]: /usr/lib/systemd/system-generators/systemd-fstab-generator exited with exit status 1.
    Mar 21 11:21:37 localhost [358276.901952] systemd-fstab-generator[22955]: Failed to create mount unit file /run/systemd/generator/tmp.mount, as it already exists. Duplicate entry in /etc/fstab?
    Mar 21 11:21:47 localhost logger: ACPI action undefined: PNP0C0A:00
    Mar 21 11:22:02 localhost logger: ACPI action undefined: PNP0C0A:00
    Mar 21 11:22:23 localhost logger: LID opened
    Mar 21 11:22:31 localhost systemd[1]: Starting Sleep.
    Mar 21 11:22:31 localhost systemd[1]: Reached target Sleep.
    Mar 21 11:22:31 localhost systemd[1]: Starting Suspend...
    Mar 21 11:22:31 localhost logger: LID closed
    Mar 21 11:22:31 localhost systemd-sleep[23159]: Suspending system...
    Mar 21 11:22:32 localhost kernel: [358330.844138] PM: Syncing filesystems ... done.
    Mar 21 11:22:32 localhost kernel: [358331.305611] PM: Preparing system for mem sleep
    Mar 21 11:22:47 localhost kernel: [358331.412348] Freezing user space processes ... (elapsed 0.02 seconds) done.
    Mar 21 11:22:47 localhost kernel: [358331.439427] Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done.
    Mar 21 11:22:47 localhost kernel: [358331.452995] PM: Entering mem sleep
    Mar 21 11:22:47 localhost kernel: [358331.453150] Suspending console(s) (use no_console_suspend to debug)
    Mar 21 11:22:47 localhost kernel: [358331.466400] e1000e 0000:00:19.0: irq 48 for MSI/MSI-X
    Mar 21 11:22:47 localhost kernel: [358331.749415] sd 0:0:0:0: [sda] Synchronizing SCSI cache
    Mar 21 11:22:47 localhost kernel: [358331.749546] sd 0:0:0:0: [sda] Stopping disk
    Mar 21 11:22:47 localhost kernel: [358332.106062] i915 0000:00:02.0: power state changed by ACPI to D3hot
    Mar 21 11:22:47 localhost kernel: [358332.242667] PM: suspend of devices complete after 497.619 msecs
    Mar 21 11:22:47 localhost kernel: [358332.243146] PM: late suspend of devices complete after 0.473 msecs
    Mar 21 11:22:47 localhost kernel: [358332.243658] xhci_hcd 0000:03:00.0: wake-up capability enabled by ACPI
    Mar 21 11:22:47 localhost kernel: [358332.269361] ehci_hcd 0000:00:1d.0: wake-up capability enabled by ACPI
    Mar 21 11:22:47 localhost kernel: [358332.282850] ehci_hcd 0000:00:1a.0: wake-up capability enabled by ACPI
    Mar 21 11:22:47 localhost kernel: [358332.309313] PM: noirq suspend of devices complete after 66.169 msecs
    Mar 21 11:22:47 localhost kernel: [358332.309974] ACPI: Preparing to enter system sleep state S3
    Mar 21 11:22:47 localhost kernel: [358332.310597] PM: Saving platform NVS memory
    Mar 21 11:22:47 localhost kernel: [358332.317339] Disabling non-boot CPUs ...
    Mar 21 11:22:47 localhost kernel: [358332.320383] smpboot: CPU 1 is now offline
    Mar 21 11:22:47 localhost kernel: [358332.323050] smpboot: CPU 2 is now offline
    Mar 21 11:22:47 localhost kernel: [358332.325460] smpboot: CPU 3 is now offline
    Mar 21 11:22:47 localhost kernel: [358332.327433] ACPI: Low-level resume complete
    Mar 21 11:22:47 localhost kernel: [358332.327483] PM: Restoring platform NVS memory
    Mar 21 11:22:47 localhost kernel: [358332.328066] Enabling non-boot CPUs ...
    Mar 21 11:22:47 localhost kernel: [358332.331542] smpboot: Booting Node 0 Processor 1 APIC 0x1
    Mar 21 11:22:47 localhost kernel: [358332.355520] CPU1 is up
    Mar 21 11:22:47 localhost kernel: [358332.358971] smpboot: Booting Node 0 Processor 2 APIC 0x2
    Mar 21 11:22:47 localhost kernel: [358332.587540] CPU2 is up
    Mar 21 11:22:47 localhost kernel: [358332.590984] smpboot: Booting Node 0 Processor 3 APIC 0x3
    Mar 21 11:22:47 localhost kernel: [358332.605172] CPU3 is up
    Mar 21 11:22:47 localhost kernel: [358332.610534] ACPI: Waking up from system sleep state S3
    Mar 21 11:22:47 localhost systemd[1]: Time has been changed
    Mar 21 11:22:47 localhost systemd[1]: systemd-tmpfiles-clean.timer: time change, recalculating next elapse.
    Mar 21 11:22:47 localhost acpid: client 328[0:0] has disconnected
    Mar 21 11:22:47 localhost systemd-sleep[23159]: System resumed.
    Mar 21 11:22:47 localhost kernel: [358332.611098] i915 0000:00:02.0: power state changed by ACPI to D0
    Mar 21 11:22:47 localhost kernel: [358332.661492] ehci_hcd 0000:00:1a.0: wake-up capability disabled by ACPI
    Mar 21 11:22:47 localhost kernel: [358332.688143] ehci_hcd 0000:00:1d.0: wake-up capability disabled by ACPI
    Mar 21 11:22:47 localhost kernel: [358332.715055] sdhci-pci 0000:01:00.0: MMC controller base frequency changed to 50Mhz.
    Mar 21 11:22:47 localhost kernel: [358332.741549] xhci_hcd 0000:03:00.0: wake-up capability disabled by ACPI
    Mar 21 11:22:47 localhost kernel: [358332.741712] PM: noirq resume of devices complete after 130.745 msecs
    Mar 21 11:22:47 localhost kernel: [358332.743008] PM: early resume of devices complete after 0.206 msecs
    Mar 21 11:22:47 localhost kernel: [358332.743043] i915 0000:00:02.0: setting latency timer to 64
    Mar 21 11:22:47 localhost kernel: [358332.743146] mei 0000:00:16.0: irq 46 for MSI/MSI-X
    Mar 21 11:22:47 localhost kernel: [358332.743195] ehci_hcd 0000:00:1a.0: setting latency timer to 64
    Mar 21 11:22:47 localhost kernel: [358332.743215] e1000e 0000:00:19.0: irq 48 for MSI/MSI-X
    Mar 21 11:22:47 localhost kernel: [358332.743301] snd_hda_intel 0000:00:1b.0: irq 49 for MSI/MSI-X
    Mar 21 11:22:47 localhost kernel: [358332.743481] ehci_hcd 0000:00:1d.0: setting latency timer to 64
    Mar 21 11:22:47 localhost kernel: [358332.743508] ahci 0000:00:1f.2: setting latency timer to 64
    Mar 21 11:22:47 localhost kernel: [358332.743611] iwlwifi 0000:02:00.0: RF_KILL bit toggled to enable radio.
    Mar 21 11:22:47 localhost kernel: [358332.744213] mei 0000:00:16.0: wd: failed to find the client
    Mar 21 11:22:47 localhost kernel: [358332.811881] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
    Mar 21 11:22:47 localhost kernel: [358332.981624] usb 4-1.2: reset high-speed USB device number 3 using ehci_hcd
    Mar 21 11:22:47 localhost kernel: [358333.061455] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
    Mar 21 11:22:47 localhost kernel: [358333.061936] ACPI Error: [GTF0] Namespace lookup failure, AE_NOT_FOUND (20120913/psargs-359)
    Mar 21 11:22:47 localhost kernel: [358333.061944] ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.PRT0._SDD] (Node ffff880149a55cf8), AE_NOT_FOUND (20120913/psparse-536)
    Mar 21 11:22:47 localhost kernel: [358333.062035] ACPI Error: [GTF0] Namespace lookup failure, AE_NOT_FOUND (20120913/psargs-359)
    Mar 21 11:22:47 localhost kernel: [358333.062041] ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.PRT0._GTF] (Node ffff880149a55d20), AE_NOT_FOUND (20120913/psparse-536)
    Mar 21 11:22:47 localhost kernel: [358333.062591] ACPI Error: [GTF0] Namespace lookup failure, AE_NOT_FOUND (20120913/psargs-359)
    Mar 21 11:22:47 localhost kernel: [358333.062599] ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.PRT0._SDD] (Node ffff880149a55cf8), AE_NOT_FOUND (20120913/psparse-536)
    Mar 21 11:22:47 localhost kernel: [358333.062690] ACPI Error: [GTF0] Namespace lookup failure, AE_NOT_FOUND (20120913/psargs-359)
    Mar 21 11:22:47 localhost kernel: [358333.062696] ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.PRT0._GTF] (Node ffff880149a55d20), AE_NOT_FOUND (20120913/psparse-536)
    Mar 21 11:22:47 localhost kernel: [358333.062739] ata1.00: configured for UDMA/100
    Mar 21 11:22:47 localhost kernel: [358333.074899] sd 0:0:0:0: [sda] Starting disk
    Mar 21 11:22:47 localhost kernel: [358333.246448] iwlwifi 0000:02:00.0: L1 Enabled; Disabling L0S
    Mar 21 11:22:47 localhost kernel: [358333.253820] iwlwifi 0000:02:00.0: Radio type=0x0-0x0-0x3
    Mar 21 11:22:47 localhost kernel: [358333.391539] restoring control 00000000-0000-0000-0000-000000000101/0/2
    Mar 21 11:22:47 localhost kernel: [358333.391541] restoring control 00000000-0000-0000-0000-000000000101/1/3
    Mar 21 11:22:47 localhost kernel: [358333.391543] restoring control 00000000-0000-0000-0000-000000000101/2/6
    Mar 21 11:22:47 localhost kernel: [358333.391544] restoring control 00000000-0000-0000-0000-000000000101/3/7
    Mar 21 11:22:47 localhost kernel: [358333.391545] restoring control 00000000-0000-0000-0000-000000000101/5/9
    Mar 21 11:22:47 localhost kernel: [358333.693001] PM: resume of devices complete after 950.103 msecs
    Mar 21 11:22:47 localhost kernel: [358333.694210] PM: Finishing wakeup.
    Mar 21 11:22:47 localhost kernel: [358333.694214] Restarting tasks ... done.
    Mar 21 11:22:47 localhost kernel: [358333.706265] video LNXVIDEO:01: Restoring backlight state
    Mar 21 11:22:47 localhost logger: ACPI action undefined: PNP0C0A:00
    Mar 21 11:22:47 localhost acpid: client connected from 328[0:0]
    Mar 21 11:22:47 localhost acpid: 1 client rule loaded
    Mar 21 11:22:47 localhost systemd[1]: Started Suspend.
    Mar 21 11:22:47 localhost systemd[1]: Service sleep.target is not needed anymore. Stopping.
    Mar 21 11:22:47 localhost systemd[1]: Stopping Sleep.
    Mar 21 11:22:47 localhost systemd[1]: Stopped target Sleep.
    Mar 21 11:22:47 localhost systemd[1]: Starting Suspend.
    Mar 21 11:22:47 localhost systemd[1]: Reached target Suspend.
    Mar 21 11:22:50 localhost logger: ACPI action undefined: PNP0C0A:00
    Last edited by whille (2013-03-21 05:26:24)

    You are still using acpid.  That is triggering the suspend, not logind.
    Edit: Also use [ code ] [ /code ] tags (without the spaces) for things like your logs.  Hit the "quote" button if you are more of a visual learner.
    This is how you use code tags.
    Last edited by WonderWoofy (2013-03-21 03:38:53)

  • Airport drops when lid closes

    Hey all,
    I'd really appreciate your help on this, I can't figure out if it's a normal defect of the MBA or just my model....I just got my ACD and I couldn't figure out why the network was constantly dropping when my 4 year old powerbook found it just fine. Then I realized when the lid is closed, or almost closed, the network completely drops even though the computer runs just fine (with my display, external keyboard and mouse). I can't figure this out. Something in the hinge is turning off the airport card?
    Thanks in advance.

    Sorry about the sidetracking, was trying to correct the information that the other poster added (in two posts) that you can't use the MBA with it closed so others would not think that was true.
    The closed lid may be interfering with the WiFi antenna or placing the antenna in a position where something is in the way that can block the signal. Other possibility is closing the lid is causing a problem with a short/loose connection due to a defect. To eliminate the first, move the arrangement of your monitor, etc. For the second you'd need to have it serviced.

  • Suspends only every second time when lid closed

    Hello everybody, my problem is as the  subject: to suspend I have to close usually the laptop lid twice.
    I'm using kde, but I have also used years ago fluxbox, tweaking scripts and using laptop-mode (which is not running now). Thanks in advance for every idea where to look.
    /etc/acpi$ cat handler.sh
    #!/bin/sh
    # Default acpi script that takes an entry for all actions
    minspeed=`cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_min_freq`
    maxspeed=`cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq`
    setspeed="/sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed"
    set $*
    case "$1" in
    button/power)
    case "$2" in
    PBTN|PWRF)
    logger "PowerButton pressed: $2"
    poweroff
    logger "ACPI action undefined: $2"
    esac
    button/sleep)
    case "$2" in
    SLPB|SBTN)
    echo -n mem >/sys/power/state
    logger "ACPI action undefined: $2"
    esac
    ac_adapter)
    case "$2" in
    AC|ACAD|ADP0)
    case "$4" in
    00000000)
    echo -n $minspeed >$setspeed
    #/etc/laptop-mode/laptop-mode start
    00000001)
    echo -n $maxspeed >$setspeed
    #/etc/laptop-mode/laptop-mode stop
    esac
    logger "ACPI action undefined: $2"
    esac
    battery)
    case "$2" in
    BAT0)
    case "$4" in
    00000000)
    logger 'Battery online'
    00000001)
    logger 'Battery offline'
    esac
    CPU0)
    *) logger "ACPI action undefined: $2" ;;
    esac
    button/lid)
    case "$3" in
    close)
    logger 'LID closed'
    open)
    logger 'LID opened'
    logger "ACPI action undefined: $3"
    esac
    logger "ACPI group/action undefined: $1 / $2"
    esac
    # vim:set ts=4 sw=4 ft=sh et:

    I actually do not understand who comands at the end - this handler.sh or the settings in Kde-powermanaging, I guess it's the second, I did remove the actions for suspend on lid close time ago. I made a test now, when I change handler.sh and check "do nothing when lid close" in kde powersettings happens exact the same: performs suspend every second time only.
    button/lid)
    case "$3" in
    close)
    logger 'LID closed'
    /usr/sbin/pm-suspend
    open)
    logger 'LID opened'
    logger "ACPI action undefined: $3"
    esac
    Last edited by steff (2012-07-21 17:08:46)

  • I have a MacBook Pro 15" 2.53GHz Mid2009.. updated to Lion which is now 10.7.3 build 11D50b... when I close lid and connect to Cinema Display, display will not activate... disconnect display, open lid laptop display will not activate... used to work fine.

    I have a MacBook Pro 15" 2.53GHz Mid2009.. updated to Lion which is now 10.7.3 build 11D50b... when I close lid and connect to Cinema Display, display will not activate when keyboard/mouse used... disconnect display, open lid and laptop display will not activate... only way out is hold power button.  Worked fine before Lion update.   Any Advice?

    Thanks very much Coander15... I've printed the doc you pointed me towards and I'll run through it.. hoping it helps!
    Before I installed Lion I simply hit any key on the keyboard or clicked the mouse...
    The keyboard is USB (usually connected to monitor which is connected to laptop... have tried direct connect to laptop as well with no luck) and mouse is USB wireless to one of those tiny plug in's... have tried direct connect USb mouse as well with no luck.
    I could plug the closed/sleeping laptop into the monitor and unplug from the monitor without incident all day/night... always worked fine. 
    Had heard something about this happening w/ Lion but went ahead anyway. 
    Oh well...
    Hoping your pointer helps... will let you know how it turns out.  Thanks very much for responding!!!

  • I've connected my macbook pro (os 10.6.8) to an external display, but it will not go into clam shell mode!  When I close the lid the laptop goes to sleep, and I am unable to wake it using the external keyboard or mouse.

    A rundown of what I've tried:
    Adjusting energy settings to try to prevent sleep
    Pluging the USB keyboard and wacom tablet directly into the laptop (as opposed to a usb hub)
    My laptop's power cable is connected
    My display (a Vizio TV) is recognized in the System Preferences panel
    I'd been using this TV for about a year with my older Macbook Pro (OS 10.5.8), though using a different wireless keyboard and mouse
    ***Update:  The issue seems to lie with the keyboard and wacom tablet.  I am trying to use a wireless Case Logic keyboard (with dongal) and wired wacom tablet to wake the Macbook Pro in clamshell mode.  To experiment, I tried using my Logitech wireless keyboard & mouse set (also dongal) that I had been using before and it wakes the computer without any problems!  However, I really need to be able to use my wacom tablet.  If I switch to the tablet after waking the computer using the Logitech keyboard & mouse it works, but once the computer sleeps it won't work anymore.  I could keep switching back and forth I suppose, but it's sort of a pain.  There has to be an easier way!  Any ideas why the wired wacom tablet is unable to wake the computer in clamshell mode?
    Thanks!

    So your keyboard or mouse won't wake the Mac when you close the lid correct? Try resetting the SMC and pram
    Shut down the computer.
    Disconnect the MagSafe power adapter from the computer, if it's connected.
    Remove the battery.
    Press and hold the power button for 5 seconds.
    Release the power button.
    Reconnect the battery and MagSafe power adapter.
    Press the power button to turn on the computer.
    Resetting NVRAM / PRAM
    Shut down your Mac.
    Locate the following keys on the keyboard: Command (⌘), Option, P, and R. You will need to hold these keys down simultaneously in step 4.
    Turn on the computer.
    Press and hold the Command-Option-P-R keys before the gray screen appears.
    Hold the keys down until the computer restarts and you hear the startup sound for the second time.
    Release the keys.

  • Won't go to sleep when I close the lid

    When I close the lid of my Macbook Pro (running Lion) it doesn't realy go to sleep.  When I open the lid the screen goes black.  Does anyone know what the issue is?
    Thanks

    if you're sayingt he light doesn't blink anymore, that's new to lion.
    if you are really having issues that you think are a bug instead of how it should work, try resetting your SMC as this should solve any issues with putting your computer to sleep with the lid.
    http://support.apple.com/kb/ht3964
    Resetting the System Management Controller (SMC)
    Resetting the SMC on Mac portables with a battery you can remove
    Note: Learn about removing the battery on MacBook and MacBook Pro.
    Shut down the computer.
    Disconnect the MagSafe power adapter from the computer, if it's connected.
    Remove the battery.
    Press and hold the power button for 5 seconds.
    Release the power button.
    Reconnect the battery and MagSafe power adapter.
    Press the power button to turn on the computer.
    Resetting the SMC on portables with a battery you should not remove on your ownNote: Portable computers that have a battery you should not remove on your own include MacBook Pro (Early 2009) and later, all models of MacBook Air, and MacBook (Late 2009).
    Shut down the computer.
    Plug in the MagSafe power adapter to a power source, connecting it to the Mac if its not already connected.
    On the built-in keyboard, press the (left side) Shift-Control-Option keys and the power button at the same time.
    Release all the keys and the power button at the same time.
    Press the power button to turn on the computer. 
    Note: The LED on the MagSafe power adapter may change states or temporarily turn off when you reset the SMC.

  • My Macbook Air wouldn't go to sleep when I close the lid. I have tried to reset the SMC, but it didn't solve the problem.

    Normaly it goes to sleep, when I close the Lid, but suddently this function stopped. That means that Mac'en still is running and become warm, during transport.
    (Macbook Air 13 ", medio 2011, 1,7 core i5, 4 MB ram, 256 GB, iMac 22", Timecapsule 1 TB, Airport Express, 2 Iphone 4, 1 iPhone 3s, iPad2)

    Test after each of the following steps that you haven’t already tried:
    Step 1
     ▹ System Preferences ▹ Print & Scan ▹ Open Print Queue...
    Check all printers for unfinished jobs. Deal with any you find.
    Step 2
     ▹ System Preferences ▹ Energy Saver ▹ Power Adapter ▹ Wake for network access: uncheck. You may need to unlock the preference pane by clicking the lock icon in the lower left corner and entering your administrator password.
    Step 3
     ▹ System Preferences ▹ Energy Saver ▹ Schedule… ▹ Start up or wake: uncheck
    Step 4
    Disconnect all wired peripherals except keyboard, mouse or trackball, and monitor, if applicable.
    Step 5
    Launch the Activity Monitor 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.
    ☞ If you’re running Mac OS X 10.7 or later, open LaunchPad. Click Utilities, then Activity Monitor in the page that opens.
    Select All Processes from the menu in the toolbar of the Activity Monitor window, if not already selected. Enter “powerd” (without the quotes) in the "Filter" text field. Select the powerd process and click the Quit Process button in the toobar (stop-sign icon.) In the sheet that opens, click Force Quit. You’ll be prompted for your administrator password. The process will be relaunched immediately.
    Step 6
    Boot in safe mode and log in. The instructions provided by Apple are as follows:
    Be sure your Mac is shut down.
    Press the power button.
    Immediately after you hear the startup tone, hold the Shift key. The Shift key should be held as soon as possible after the startup tone, but not before the tone.
    Release the Shift key when you see the gray Apple icon and the progress indicator (looks like a spinning gear).
    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.
    Note: If FileVault is enabled under Mac OS X 10.7 or later, or if a firmware password is set, you can’t boot in safe mode.
    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 Mac 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 7
    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 8
    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.

  • How do i run an external monitor with my macbook and change settings so that when i close the lid the signal to the monitor is not lost and i can continue using the mac with a mouse and a wireless keyboard?

    How do i run an external monitor with my macbook and change settings so that when i close the lid the signal to the monitor is not lost and i can continue using the mac with a mouse and a wireless keyboard?

    No, nothing will prevent the computer from going to sleep when you close its display except third-party hacks that are designed to do exactly that. I strongly advise against using any of those, as they may interfere with successful entry into clamshell mode (and they carry other downside risks as well). Just wait until the computer is asleep (with its sleep light pulsing), then press any key on the keyboard. It sounds as though your setup is working as it's designed to do.

  • HT3382 I have a Samsung VGA Monitor connected to my MacBook Pro using the Mini Display Port to VGA Adapter.  How do I configure the computer so that it doesn't sleep when I close the lid of the computer.

    I have a Samsung VGA Monitor connected to my MacBook Pro using the Mini Display Port to VGA Adapter.  How do I configure the computer so that it doesn't sleep when I close the lid of the computer.

    Hi alangium,
    Welcome to the Support Communities!
    Resetting your computer's PRAM should restore your Macbook Pro's screen appearance.
    OS X Mavericks: Reset your computer’s PRAM
    http://support.apple.com/kb/ph14222
    This article may provide some information about your Mini DisplayPort to AVI adapter.  Have you tried to connect a different VGA monitor to your Macbook to see if you get the same results?
    Apple Mini DisplayPort adapters: Frequently asked questions (FAQ)
    http://support.apple.com/kb/HT3382
    18. What is the maximum resolution available for use with the Apple Mini DisplayPort to VGA adapter?
    The resolution available with the Apple Mini DisplayPort to VGA Adapter is 1920 x 1200. VGA displays that use higher refresh rates (such as 85 Hz) at resolutions of 1600 x 1200 or greater may not generate video properly until you lower the refresh rate.
    Apple computers: Troubleshooting issues with video on internal or external displays
    http://support.apple.com/kb/HT1573#5
    How can I detect displays?
    If the detect displays option is not available, hold down the Option key while you are in the Display pane.
    How do I select additional resolutions on my display?
    You can use the Display pane of System Preferences to specify how your display works. Not all options appear for all display models. By default the best resolution for your display will already be selected in System Preferences.
    To select a different resolution, use the Scaled option. Some additional resolutions may be available when you hold the Option button.
    I hope this information helps ....
    - Judy

Maybe you are looking for