Screen blinks/flashes upon wake from sleep. is this normal?

I just got my Macbook a few days ago and started to notice that my screen flashes or blinks when it wakes from sleep. I have searched on Google and haven't seen any one post about it so I'm guessing this is normal. This is not the flicker of brightness that other people are talking about.
What happens is: I press a key or open the lid to wake it from sleep, and then very briefly for a second I will see the screen flash on (sometimes you can see a small image of the desktop), then it is black for a second, then the screen comes on normally. The delay of the screen coming back on after the blink seems to be getting longer so I was starting to worry this might be a problem. (granted the delay of the screen coming on is maybe like 2 seconds, but its noticeable) I had a Thinkpad previously and never noticed the screen acting like this.
If anyone can tell me if I need to bring this in to the nearest store or if it is normal I would appreciate it. I don't want to overreact as this is my first Mac and I don't have any problems so far. But I want to be safe if this is an indicator of future screen problems. Thanks!!
Macbook   Mac OS X (10.4.8)  

Take it to your local Apple store and they will send it off for repair. Or call Apple and they will send you a box to mail it in for repair.
I took my MacBook to the Apple store for the infamous screen flicker problem and they had the logic board and the LCD replaced. Problem is gone and the screen is better than before!
J

Similar Messages

  • Black screen upon wake from sleep when I change power state while in sleep

    Hi,
    I'm having this problem where my MacbookPro won't always wake from sleep.
    OSX is 10.6.3 and fully updated.
    I've done a lot of troubleshooting, and I can now replicate the issue 100%:
    1 - Put the MacbookPro to sleep by closing lid
    2 - Change power source (from plugged-in to battery or vice versa)
    3 - open lid - MacbookPro will wake, but stays at black screen and is unresponsive.
    Only if I change power state while sleeping will this issue show. Anyone else experincing this issue, and anygot got a clue on what to do?
    regards,
    Lasse

    I've seen the same issue after upgrading to 10.6.3. I have a one year old MacBook Pro. I would have the screen be black after coming back from sleep or hibernate (tried both).
    The workaround I found is to close the lid -almost- all the way and then immediately open it back up again, like I am catching the Mac going back to sleep and then changing my mind. For whatever reason, this has been reliably solving my issue for the last couple weeks reliably.
    Only other oddity I noticed is that immediately after upgrading OS X told me that my one year old battery needed to go in for servicing...
    Anyway, now all looks right with the world assuming you don't mind a quick close/open cycle.. Lovely...
    Tim

  • White flash when wake from sleep

    Just upgraded my 2007 iMac to ML. Notice that when I wake from sleep there's a white flash, or perhaps a bit longer, on screen before the desktop appears. It's similar to the white screen when booting, just before the worm gear appears.
    Anyone else notice it? Normal behavior?

    Yes, on a mid-2011 MacBook Air. Tried resetting SMC, no luck. I've installed all the prior firmware updates. It only happens when running on battery power. I'm going to experiment with disabling Power Nap when running on battery to see if that makes a difference.

  • Launch application upon wake from sleep

    Is there an automator that will launch an application when the computer wakes from sleep? I do video chats w/ my elderly mother via iChat. I can wake her computer from my home using WakeOnLan. However, she sometimes quits iChat so it is not always running. I would like to have some sort of automator set to launch iChat everytime the computer wakes from sleep. I assume if iChat is already running, it would not matter.
    If anyone knows how to do this or if it is even possible, please let me know.
    Thanks,
    Randy

    Gary,
    Thanks for pointing me in the right direction. I ended up using DisplayWatcher as it also has the ability to run an automator application upon waking from sleep. There were some other apps that were too complicated for me -- had to enter Unix commands/code and I did not understand how to do this.
    Thanks again,
    Randy

  • VNC - Screen Resolution Problem on Wake from Sleep

    My question: When it either wakes from sleep or cold boots (NOT on restart for some reason), Mac OS X seems to be confused on the previous resolution of my screen. On wake or cold boot, my main screen SOMETIMES gets set for 800x600 at 56 Hz, according to the display preference pane. I normally run at 1152x870 at 75 Hz. In the past, I have just used the "Detect Displays" command from the display preference pane. This always fixes the screen resolution and restores it to the correct setting.
    This would not be a problem if I didn't have to run VNC. These screen res changes are crashing my VNC server. Here's what I do. I run a VNC server (OSXvnc is the name). I go away. Machine goes to sleep. From machine 'x' I send a wake-on-wan packet (a pain in the butt to figure out for me, BTW). My VNC Machine wakes up. I know it's awake, because I can login to it from remote, using SSH. But the screen res problem happened, and OSXvnc shuts down and won't reinitialize automatically. It says "Screen Resolution Changed - Server Reinitialized", and the "Start Server" button is waiting to be pressed. Of course, this cripples my ability to use VNC.
    For what it's worth, this problem has happened with two different video cards. Granted, the first card was an ATI Radeon 9000 with 64 MB or VRAM and the second card is the same model with 128 MB VRAM. It's virtually the same card, but still, that's two different cards.
    I have 2 CRT displays connected thru adapters (DVI-VGA and ADC-VGA) to the ATI. I'm running all the latest updates for Panther, according to Software Update. This problem has been with me since 10.2.3. I lived with it until it started really getting in the way (VNC crippling & such).
    Any thoughts? -- iJW
    G4 Dual 1 GHz MDD (no FW 800)   Mac OS X (10.3.9)  

    One other item I just discovered. It seems that whether or not my monitors are powered on has something to do with it. When my monitors are on, the problem doesn't happen.
    I like turning them off to save electricity. If I'm using the computer remotely, I already have a monitor. I don't need one powering up at my home that no one's looking at anyway. So the question still stands...
    Anyone?
    G4 Dual 1 GHz MDD (no FW 800)   Mac OS X (10.3.9)  

  • Screen flickers when computer wakes from sleep

    O.k., so I also had this problem when I updated to 10.6.8, but it's still here in Lion.........
    When the computer wakes from sleep, I get a single flicker along the bottom 1/3rd of the screen, then everything's o.k.
    It's just annoying, that's all. I've backed out to 10.6.7 on 3 occasions, and the flicker disappears.
    Anyone else having this issue?
    I'm running a 2010 Quad-core Mac Pro with SSD and 27" Display.
    Bob.

    Update:
    I've now been to the local Apple store, and tried their display Mac Pro/27" Cinema Display combo, and guess what.......the screen flickers on wake-up.
    I asked the guy in the store about it, and he says "oh yes, I see that. No-one has noticed that before, I wonder if mine does it at home".
    I tried the Mac Mini with 27" Cinema display, and the 27" iMacs, and they were o.k. (no flicker).
    So, this only affects Mac Pro's running 2560 x 1440 resolution.
    I've booked another call with Apple Support. No doubt they'll still tell me to take my computer in for testing, even though I've shown they all do it (the guy in the Apple shop suggested that, even though I demonstrated the flicker to him on the one in the shop).
    I wonder how long this will take to get a software fix? Problem is, the Pro is not mass-market (like Macbooks and iMacs), so it may take an awful long time.
    In the meantime, I'm sticking with 10.6.7.
    Bob.

  • Time Machine "preparing backup" eternally upon wake from sleep

    at a bit of a loss here...
    iMac 24" (version which offered 7300GT as BTO option)
    10.5.5 with all updates applied
    LaCie 500 gig USB 2.0 drive directly attached.
    Up until about two months ago, Time machine functioned fined. Then for some reason, the following started to happen. (no known reason, no software update related etc, that I know of)
    scenario... Time Machine functions correctly EXCEPT when waking from sleep. If iMac wakes from sleep and attempts a backup immediately (e.g. more than one hour has passed), it gets stuck "preparing backup" forever. I've let it run overnight (actually as long as about 30 hours), it never stops. Finder and other programs become extremely non-responsive, machine is almost unusable. Literally, the only way out is to manually shut down external drive, with attendant warnings/errors.
    What I've done:
    1) deleted the time machine .plist file
    2) erased, repartioned (as a single partition) external drive
    3) started brand new time machine backup (takes about three hours)
    At this point, time machine will backup up fine... I can force a successful backup, if I leave the machine running, at one hour it does a successful backup.
    BUT, as soon as it goes to sleep, time machine is hosed.
    The only workable method for using time machine is to turn the external drive and time machine off when not using it, and turn the whole shootin' match on to do what essentially becomes manual backups. These backup are fairly lengthy, as time machine also does lengthy "preparing backup", but they complete in about 30 minutes to one hour.
    Given that time machine doesn't give mountable/cloneable backup, I'm probably going to go back to Carbon Copy Cloner. Still, I like the ease/regularity of Time Machine, and would use it if it works.
    Any ideas?
    thanks

    It could be a number of things. There are lots of things that Time Machine does in order to "manage" backups -- apart from just copying data to the backup drive.
    It has to manage the transition of hourly backups into daily backups and must also transition daily backups into weekly backups. Each time it does this it has to move a lot of data around. It also has to maintain indexes of everything so you can quickly find backups should you want to perform a restore.
    I've also noticed that there are circumstances that can cause TM to question whether it can trust it's existing backup database... I've caught Time Machine saying that it needs to do a "deep traversal" of the backup (basically it wants to check and see what it really has) and this can take a very long time.
    Still... 30 hours is an extremely long amount of time. I'm almost wondering if there's a problem with either your USB bus or your drive when they wake up such that you may be getting a huge number of retries on something that should have happened quickly.
    I'd suggest you start the "Console" utility, select "All Messages" at the left, and then watch the messages being written to your log file. Not only does Time Machine log all of it's progress messages to the system.log (in more detail than you'd see in the Time Machine UI), but so do lots of other system processes. If you're getting USB bus problems the error messages would likely show up in the same log. I'm especially suspicious about non-TM related causes since you said you've already blown away your TM backups & preferences and started from scratch and you're still getting the problem.
    Try re-creating your problem with the Console log messages being displayed and see if you can't see something in the log that would let you get a little closer to the root cause.
    Regards,
    Tim

  • Alert beep upon wake from sleep

    Hello,
    I seem to have a strange alert beep that occurs when waking from sleep.
    It only just appeared after I applied the 10.4.8 software update.
    I wouldn't be concerned but today when I booted-up my machine immediately kernal paniced and told me to restart.
    It seems independent of what software is open.
    I can't seem to find any start-up items that could be to blame.
    Any thoughts on trouble shooting this?
    Thanks in advance,
    Andrew

    I just repeated the beep on wake from sleep.
    Here is the console system log from before and after the sleep session.
    Oct 15 11:44:05 r-r-andrew-nelsons-computer kernel[0]: hibernate image path: /var/vm/sleepimage
    Oct 15 11:44:05 r-r-andrew-nelsons-computer kernel[0]: sizeof(IOHibernateImageHeader) == 512
    Oct 15 11:44:05 r-r-andrew-nelsons-computer kernel[0]: Opened file /var/vm/sleepimage, size 1073741824, partition base 0xc805000, maxio 400000
    Oct 15 11:44:05 r-r-andrew-nelsons-computer kernel[0]: hibernate image major 14, minor 2, blocksize 512, pollers 3
    Oct 15 11:44:05 r-r-andrew-nelsons-computer kernel[0]: hibernateallocpages flags 00000000, gobbling 0 pages
    Oct 15 11:44:08 r-r-andrew-nelsons-computer launchd: Server 0 in bootstrap 1103 uid 0: "/usr/sbin/lookupd"[75]: exited abnormally: Hangup
    Oct 15 11:44:08 r-r-andrew-nelsons-computer configd[34]: posting notification com.apple.system.config.network_change
    Oct 15 12:15:13 r-r-andrew-nelsons-computer kernel[0]: System SafeSleep
    Oct 15 12:15:13 r-r-andrew-nelsons-computer kernel[0]: hibernatepage_listsetall start
    Oct 15 12:15:13 r-r-andrew-nelsons-computer kernel[0]: hibernatepage_listsetall time: 68 ms
    Oct 15 12:15:13 r-r-andrew-nelsons-computer kernel[0]: pages 105739, wire 23101, act 14824, inact 19629, zf 9273, could discard act 19923 inact 18989
    Oct 15 12:15:13 r-r-andrew-nelsons-computer kernel[0]: hibernatepage_listsetall found pageCount 105739
    Oct 15 12:15:13 r-r-andrew-nelsons-computer kernel[0]: IOHibernatePollerOpen, mlget_interruptsenabled 0
    Oct 15 12:15:13 r-r-andrew-nelsons-computer kernel[0]: IOHibernatePollerOpen(0)
    Oct 15 12:15:13 r-r-andrew-nelsons-computer kernel[0]: writing 105519 pages
    Oct 15 12:15:13 r-r-andrew-nelsons-computer kernel[0]: image1Size 37189120
    Oct 15 12:15:13 r-r-andrew-nelsons-computer kernel[0]: all time: 3605 ms, comp time: 675 ms, deco time: 0 ms,
    Oct 15 12:15:13 r-r-andrew-nelsons-computer kernel[0]: image 114174464, uncompressed 272822272 (66607), compressed 113735084 (41%), sum1 4c777e1e, sum2 e53985f3
    Oct 15 12:15:13 r-r-andrew-nelsons-computer kernel[0]: hibernatewriteimage done(0)
    Oct 15 12:15:13 r-r-andrew-nelsons-computer kernel[0]: sleep
    Oct 15 12:15:13 r-r-andrew-nelsons-computer kernel[0]: Enabling XMM register save/restore and SSE/SSE2 opcodes
    Oct 15 12:15:13 r-r-andrew-nelsons-computer kernel[0]: Started CPU 01
    Oct 15 12:15:13 r-r-andrew-nelsons-computer kernel[0]: IOBluetoothHCIController::restartShutdownWL this is a wake from sleep
    Oct 15 12:15:13 r-r-andrew-nelsons-computer kernel[0]: System Wake
    Oct 15 12:15:15 r-r-andrew-nelsons-computer lookupd[242]: lookupd (version 369.6) starting - Sun Oct 15 12:15:15 2006
    Oct 15 12:15:18 r-r-andrew-nelsons-computer launchd: Server 0 in bootstrap 1103 uid 0: "/usr/sbin/lookupd"[242]: exited abnormally: Hangup
    Oct 15 12:15:18 r-r-andrew-nelsons-computer configd[34]: posting notification com.apple.system.config.network_change
    Oct 15 12:15:18 r-r-andrew-nelsons-computer lookupd[249]: lookupd (version 369.6) starting - Sun Oct 15 12:15:18 2006
    Any insight would be appreciated.
    Cheers
    MacBook Pro 15" 1.83GHz, 1G RAM, 80G HD (W8611), XP Home under Parallels   Mac OS X (10.4.8)   Dell Inspiron 4100 XP Home

  • Creaking sound upon wake from Sleep

    I have only had my MBP (very first mac) last 1/25 and for a few days would wake from sleep totally silent.  In the last couple of days occasionally it wil make a creaking sound for a couple of seconds after I raise the lid sounds kinda like gears. Not very loud tho.  But since this is a refurbished (june 2012) unit I was just wondering if this is normal.  My old toshiba would always make creaky gear sounding noises at wake from sleep for much longer.  But since it is silent it is silent most times I was wondering if this was normal or a known problem?

    Originally Posted by Lawrence-NYP
    I suppose you have tried playing around with the sound settings in the control panel?
    If that's the case, however no one else replies to your thread, you might consider re-format your computer.
    In fact I have. And this is on a freshly formatted drive unfortunately.

  • Airport issue upon wake from sleep

    When my mac pro wakes from sleep it connects to my preffered wireless network but it has some serious issues and doesn't work. When it restarts the airport icon shows connected, but mysteriously shows a weak signal and when I try to do anything that needs to talk to the network it fails. The only way to fix the issue is turn airport off then on again and hey presto I'm back on a full signal and can surf n stuff.
    I'm using a 1st gen Airport Express N basestation, which works fine as I have 5 other macs in the house (non a mac pro) that don't have the issue.
    Looking in my logs i see a few interesting things, it looks like when the system is woken up it sets the country code to X3 and then fails to get a proper link. When I restart airport it sees the network uses GB as the country.
    I can't be the only person with this problem.
    Feb 18 07:25:44 Big-Mac kernel[0]: en2: 802.11d country code set to 'X3'.
    Feb 18 07:25:44 Big-Mac kernel[0]: en2: Supported channels 1 2 3 4 5 6 7 8 9 10 11 12 13 36 40 44 48 52 56 60 64
    Feb 18 07:25:44 Big-Mac kernel[0]: Intel8254x -- Link Down -- 00:1d:4f:48:99:d5 -- called by disable() --
    Feb 18 07:25:43 Big-Mac configd[14]: rtmsg: error writing to routing socket
    Feb 18 07:25:44 Big-Mac kernel[0]: -- Auto-Negotiation Advertisement Register (04d) = 0xde1
    Feb 18 07:25:44 Big-Mac kernel[0]: -- Auto-Negotiation Link Partner Ability Register (05d) = 0x0
    Feb 18 07:25:44 Big-Mac kernel[0]: -- Auto-Negotiation Gigabit Advertisement Register (09d) = 0xe00
    Feb 18 07:25:44 Big-Mac kernel[0]: -- Auto-Negotiation Gigabit Link Partner Ability Register (10d) = 0x0
    Feb 18 07:25:44 Big-Mac kernel[0]: -- PHY Specific Status Register (17d) = 0x8000
    Feb 18 07:25:44 Big-Mac kernel[0]: Intel8254x -- Link Down -- 00:1d:4f:48:99:d4 -- called by disable() --
    Feb 18 07:25:44 Big-Mac kernel[0]: -- Auto-Negotiation Advertisement Register (04d) = 0xde1
    Feb 18 07:25:44 Big-Mac kernel[0]: -- Auto-Negotiation Link Partner Ability Register (05d) = 0x0
    Feb 18 07:25:44 Big-Mac kernel[0]: -- Auto-Negotiation Gigabit Advertisement Register (09d) = 0xe00
    Feb 18 07:25:44 Big-Mac kernel[0]: -- Auto-Negotiation Gigabit Link Partner Ability Register (10d) = 0x0
    Feb 18 07:25:44 Big-Mac kernel[0]: -- PHY Specific Status Register (17d) = 0x8040
    Feb 17 23:42:12 Big-Mac kernel[0]: System Sleep
    Feb 18 07:25:44 Big-Mac kernel[0]: System Wake
    Feb 18 07:25:44 Big-Mac kernel[0]: Previous Sleep Cause: 5
    Feb 18 07:25:44 Big-Mac kernel[0]: USB caused wake event (EHCI)
    Feb 18 07:25:44 Big-Mac kernel[0]: Intel8254x -- Link Down -- 00:1d:4f:48:99:d5 -- called by enableHardware() --
    Feb 18 07:25:44 Big-Mac kernel[0]: -- Auto-Negotiation Advertisement Register (04d) = 0xde1
    Feb 18 07:25:44 Big-Mac kernel[0]: -- Auto-Negotiation Link Partner Ability Register (05d) = 0x0
    Feb 18 07:25:44 Big-Mac kernel[0]: -- Auto-Negotiation Gigabit Advertisement Register (09d) = 0xe00
    Feb 18 07:25:44 Big-Mac kernel[0]: -- Auto-Negotiation Gigabit Link Partner Ability Register (10d) = 0x4000
    Feb 18 07:25:44 Big-Mac kernel[0]: -- PHY Specific Status Register (17d) = 0x8000
    Feb 18 07:25:44 Big-Mac kernel[0]: Intel8254x -- Link Down -- 00:1d:4f:48:99:d4 -- called by enableHardware() --
    Feb 18 07:25:44 Big-Mac kernel[0]: -- Auto-Negotiation Advertisement Register (04d) = 0xde1
    Feb 18 07:25:44 Big-Mac kernel[0]: -- Auto-Negotiation Link Partner Ability Register (05d) = 0x0
    Feb 18 07:25:44 Big-Mac kernel[0]: -- Auto-Negotiation Gigabit Advertisement Register (09d) = 0xe00
    Feb 18 07:25:44 Big-Mac kernel[0]: -- Auto-Negotiation Gigabit Link Partner Ability Register (10d) = 0x4000
    Feb 18 07:25:44 Big-Mac kernel[0]: -- PHY Specific Status Register (17d) = 0x8000
    Feb 18 07:25:44 Big-Mac kernel[0]: WLCE_COUNTRY_CODECHANGED
    Feb 18 07:25:44 Big-Mac /System/Library/CoreServices/backupd[25846]: Backup requested due to disk attach
    Feb 18 07:25:44 Big-Mac kernel[0]: en2: 802.11d country code set to 'GB'.
    Feb 18 07:25:44 Big-Mac kernel[0]: en2: Supported channels 1 2 3 4 5 6 7 8 9 10 11 12 13 5 6 7 8 9 10 11 12 13 1 2 3 4 5 6 7 8 9 36 40 44 48 52 56 60 64 100 104 108 112 116 120 124 128 132 136 140 40 48 56 64 104 112 120 128 136 36 44 52 60 100
    Feb 18 07:25:44 Big-Mac kernel[0]: jnl: disk8s3: journal start/end pointers reset! (jnl 0xaddec18; s 0x1be000 e 0x1be000)
    Feb 18 07:25:47 Big-Mac TextMate[17557]: Error checking for new version: no Internet connection
    Feb 18 07:25:47 Big-Mac TextMate[17557]: Will try again in one hour
    Feb 18 07:25:49 Big-Mac kernel[0]: AirPort: Link Up on en2

    I had the same issues at 10.5.2, however, they went away when I upgraded the OS to 10.5.3. You can now get the 10.5.4 combo upgrade.
    Joe

  • Blank Screens After Startup and Wake From Sleep

    About half the time I startup my Mac Pro or wake it up from sleep, the screen will go blank, usually about 20-30 seconds after video appears on the screen. The system seems to be running, you just can't see anything.
    I have had the screen go completely white, black or blue and occasionally, there will be a solid color with vertical lines throughout the screen. The only thing that will get display back is a forced restart of the entire computer.
    I've zapped PRAM and run run hardware test with no issues reported but the problem keeps coming back.
    I'm driving a Dell 2407 on my ATI 1900XT. Dell supplied a single-link DVI cable, could that cause issues with a dual-link port on the video card?
    Mac Pro   Mac OS X (10.4.9)   ATI 1900XT, 2GB RAM

    Intel Macs, especially MacBook Pros seem to be notorious for sleep issues...either not sleeping when supposed to, or not waking up from sleep properly.
    My MacBook Pro has come out of the brief case hot as heck with a dead battery often enough, even with all the updates appled. If you listen to the MacBreak Weekly podcast, that's a common complaint of Merlin Mann, who can't figure it out with his machine, and he's no dummy when it comes to Macs. Not very encouraging, is it?
    Still, what I would try is reinstalling the OS X 10.4.9 update. I've often read/heard on podcasts that it's better to manually install the larger Combo version of the updates. That seems to have fixed problems for me in the past.
    Get the Intel 10.4.9 Combo Update here: http://www.apple.com/support/downloads/macosx1049comboupdateintel.html
    Good luck.

  • Mac Mini reboots restarts upon wake from sleep

    Since 'upgrading' from Lion to Mountain Lion, my Mac Mini reboots (Restarts) whenever I wake it from sleep. I've applied every update hoping it will be fixed. Apple has been unable to resolve the issue short of their standard suggestion to reformat and reinstall from scratch. I've had to resort to disabling the energy saver.
    A Google search turns up many similar complaints. Anyone have a fix or suggestion?
    Thanks

    Did you get anywhere with this? I have the same problem i fear as per my separate post
    https://discussions.apple.com/thread/4779128

  • MacBook Air freezing upon wake from sleep

    Hello there! Ever since installing Mavericks, my MacBook Air freezes nearly every time I wake it from sleep. Whever I open the lid, it allows me to enter my password, and then it freezes. Other times, it will let me log in, and then whenever I try to use Safari or another application it freezes. It doesn't completely freeze, I get the beachball and everything. What is going on?

    Hello there AustinJGibson,
    It sounds like you are having performance issues with Mavericks.
    It sounds like you are seeing some performance issues after having installed Mac OS X 10.9.
    I want to recommend the troubleshooting information from this article named:
    OS X Mavericks: If your Mac runs slowly
    http://support.apple.com/kb/PH13895
    If you find your Mac is running slowly, there are a number of potential causes that you can check.
    An app you’re using may require more memory than your computer has. To see how much memory your computer has, choose Apple menu > About This Mac. See the documentation that came with the app to find out what it requires. To find out how to increase your computer’s memory, see the documentation that came with it.Find the manual for your Mac
    Quit any application that isn’t compatible with your computer. For example, an application may require a different processor or graphics card. See the documentation that came with the application to find out what it requires.
    To see what processor your computer has, choose Apple menu > About This Mac.
    To see what graphics card your computer has, choose Apple menu > About This Mac, click More Info, and then click Displays.
    Your computer’s startup disk may not have enough free disk space. To make disk space available, you can move files to another disk and then delete files you no longer need on the startup disk.Increase disk space
    Quit any apps you’re not using.
    If none of these suggestions work, you may need to repair your computer’s disk in Disk Utility.Repair a disk
    Next I would perform a Safe Boot:
    Mac OS X: What is Safe Boot, Safe Mode?
    http://support.apple.com/kb/ht1564
    Thank you for using Apple Support Communities.
    Regards,
    Sterling

  • Wireless connection lost upon wake from sleep

    I recently joined the 21st century and purchased broadband internet for my home. I am connecting via wireless ethernet using an original Airport card and flying-saucer type base station. All I did was connect the base station to the cable modem with an ethernet cable, plug it in, and restart my eMac. The network showed up right away and I was connected. Unfortunately, after my Mac went to sleep and I woke it up, not only was there not a connection, but there was no sign of the network.
    Airport status showed it was still on, but in the spot where the networks show there was nothing. Restarting corrected the problem, but I assume only until it sleeps again. I can change the settings to make it monitor-only sleep, but I would like a more permanent solution.
    What might help to fix the problem, and was there something I needed to do besides just turn my machine off and on to set up this network?
    Thanks.

    If you pose this problem over in the Airport or Tiger networking forums, you'll find you've stumbled into a morass of conflicting reports. There have been a disturbing number of reports of Airport connections lost in Tiger after wake from system sleep, usually not reconnected until after a restart. Some people have some success checking the box to put the Airport icon in the menubar ans using that to turn Airport off, wait a few minutes, and turn it back on, yet others have reported that only works part of the time and others report it doesn't work at all. Some have reported improvement after downloading and running the full OS X Update Combo 10.4.10 (PPC) on top of an OS updated via Software Update. And the large majority of Airport users never report any problems at all using Tiger. It really sounds like there's no one cause and no one fix.
    There is a workaround: don't let the Mac go into system sleep. Use the Energy Saver system preference to set system sleep to Never, uncheck the 'put hard drives to sleep when possible' box, and set the display-only sleep to say 20 minutes. If the eMac is in a bedroom and the sleepers are sensitive to fan noise or power LED lights, that will be a problem, but likely less aggravating than losing your broadband connection.

  • Battery percentage indicator takes a little while to update when resuming from sleep - is this normal?

    Hi folks,
    I recently bought a new MacBook Pro with Retina (13") and have noticed a pecularity with the battery indicator that I'd appreciate an opinion on please.
    I've charged my MBPr battery to full (100% on the menu bar and green light on the MagSafe connector). I disconnect the power and close the lid which puts that MacBook to sleep. After leaving it overnight, I open the lid and and the unlock screen shows the percentage battery having gone down by a couple of percent (which I take to be normal) - e.g. 98%. However, when I unlock and get back to the desktop, it's still showing as 100%. Clicking on the battery icon, it shows as calculating the amount of time left. After about a minute or so, it tells me how much estimated time I've got left, and the percentage indicator updates to give me the correct percentage. When using it normally, the percentage indicator drops on the desktop as I would expect it to.
    Is this normal for it to give the correct percentage on the unlock screen, but then to give the original (pre-sleep) percentage when unlocked, until it has updated and worked out how much time it's got left on battery?
    I've read elsewhere that many folks have been having issues with the battery indicator since Mavericks rolled out, and there are some resets that can be done by pressing various key combinations whilst powering on. I've had the MacBook only a few days, and haven't installed anything on it - it hasn't even been connected to the internet yet - so I assumed that it should be working correctly from the off - unless there's something buggy with Mavericks causing this?
    I would normally shut down a computer overnight, but I like how the MBP instantly resumes when I open the lid. Am also wondering whether it'll take a few charge cycles before the battery reaches full capacity and is properly calibrated. The system report shows that it shipped to me having undergone only 3 charge cycles to date.
    Any opinions would be much appreciated.
    Cheers,
    Gopha

    After some more testing:
    Disabling the battery percentage indicator and then re-enabling it causes the percentage value to update to the 'correct' value. Rebooting the MacBook also causes it to update to the correct value.
    Seems like I'm not the only one with this particular issue: https://discussions.apple.com/message/24402123#24402123
    https://discussions.apple.com/message/24406197#24406197
    as a newbie to Macs and Mavericks, am I right in saying that there is currently an issue with Mavericks?
    Thanks,
    Gopha

Maybe you are looking for