[Solved] Screen bug after display sleep

Hi,
I have a Asus N55SF (Intel HD and Nvidia GT555M with Optimus).
When my screen wakes up after DPMS off (I mean only the screen suspend, not the system one), it's totally white, and I see leds becoming grey then black (like a cloud). Then it stays like this, the only way I found to make it working again is to put the computer in sleep mode and wake it up.
I can reproduce it, just waiting for the screen to turn off, or manually typing:
$ xset -display :0 dpms force off
I found a similar issue here: http://www.linuxquestions.org/questions … ost4501106
Any idea?
Here's some computer specs:
[grubshka@octave trunk]$ lspci -v
00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family DRAM Controller (rev 09)
Subsystem: ASUSTeK Computer Inc. Device 1347
Flags: bus master, fast devsel, latency 0
Capabilities: <access denied>
Kernel driver in use: agpgart-intel
Kernel modules: intel-agp
00:01.0 PCI bridge: Intel Corporation 2nd Generation Core Processor Family PCI Express Root Port (rev 09) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
I/O behind bridge: 0000d000-0000dfff
Memory behind bridge: da000000-dc0fffff
Prefetchable memory behind bridge: 00000000c0000000-00000000d3ffffff
Capabilities: <access denied>
Kernel driver in use: pcieport
Kernel modules: shpchp
00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. Device 2050
Flags: bus master, fast devsel, latency 0, IRQ 56
Memory at dc400000 (64-bit, non-prefetchable) [size=4M]
Memory at b0000000 (64-bit, prefetchable) [size=256M]
I/O ports at e000 [size=64]
Expansion ROM at <unassigned> [disabled]
Capabilities: <access denied>
Kernel driver in use: i915
Kernel modules: i915
00:16.0 Communication controller: Intel Corporation 6 Series Chipset Family MEI Controller #1 (rev 04)
Subsystem: ASUSTeK Computer Inc. Device 1347
Flags: bus master, fast devsel, latency 0, IRQ 16
Memory at df00b000 (64-bit, non-prefetchable) [size=16]
Capabilities: <access denied>
Kernel driver in use: mei
Kernel modules: mei
00:1a.0 USB Controller: Intel Corporation 6 Series Chipset Family USB Enhanced Host Controller #2 (rev 05) (prog-if 20 [EHCI])
Subsystem: ASUSTeK Computer Inc. Device 1347
Flags: bus master, medium devsel, latency 0, IRQ 16
Memory at df008000 (32-bit, non-prefetchable) [size=1K]
Capabilities: <access denied>
Kernel driver in use: ehci_hcd
Kernel modules: ehci-hcd
00:1b.0 Audio device: Intel Corporation 6 Series Chipset Family High Definition Audio Controller (rev 05)
Subsystem: ASUSTeK Computer Inc. Device 1b73
Flags: bus master, fast devsel, latency 0, IRQ 55
Memory at df000000 (64-bit, non-prefetchable) [size=16K]
Capabilities: <access denied>
Kernel driver in use: HDA Intel
Kernel modules: snd-hda-intel
00:1c.0 PCI bridge: Intel Corporation 6 Series Chipset Family PCI Express Root Port 1 (rev b5) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
I/O behind bridge: 0000c000-0000cfff
Memory behind bridge: de600000-deffffff
Prefetchable memory behind bridge: 00000000d6200000-00000000d6bfffff
Capabilities: <access denied>
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1c.1 PCI bridge: Intel Corporation 6 Series Chipset Family PCI Express Root Port 2 (rev b5) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=03, subordinate=03, sec-latency=0
I/O behind bridge: 0000b000-0000bfff
Memory behind bridge: ddc00000-de5fffff
Prefetchable memory behind bridge: 00000000d5700000-00000000d60fffff
Capabilities: <access denied>
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1c.3 PCI bridge: Intel Corporation 6 Series Chipset Family PCI Express Root Port 4 (rev b5) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=04, subordinate=04, sec-latency=0
I/O behind bridge: 0000a000-0000afff
Memory behind bridge: dd200000-ddbfffff
Prefetchable memory behind bridge: 00000000d4c00000-00000000d55fffff
Capabilities: <access denied>
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1c.5 PCI bridge: Intel Corporation 6 Series Chipset Family PCI Express Root Port 6 (rev b5) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=05, subordinate=05, sec-latency=0
I/O behind bridge: 00009000-00009fff
Memory behind bridge: dc800000-dd1fffff
Prefetchable memory behind bridge: 00000000d4100000-00000000d4afffff
Capabilities: <access denied>
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1d.0 USB Controller: Intel Corporation 6 Series Chipset Family USB Enhanced Host Controller #1 (rev 05) (prog-if 20 [EHCI])
Subsystem: ASUSTeK Computer Inc. Device 1347
Flags: bus master, medium devsel, latency 0, IRQ 23
Memory at df007000 (32-bit, non-prefetchable) [size=1K]
Capabilities: <access denied>
Kernel driver in use: ehci_hcd
Kernel modules: ehci-hcd
00:1f.0 ISA bridge: Intel Corporation HM65 Express Chipset Family LPC Controller (rev 05)
Subsystem: ASUSTeK Computer Inc. Device 1347
Flags: bus master, medium devsel, latency 0
Capabilities: <access denied>
Kernel modules: iTCO_wdt
00:1f.2 SATA controller: Intel Corporation 6 Series Chipset Family 6 port SATA AHCI Controller (rev 05) (prog-if 01 [AHCI 1.0])
Subsystem: ASUSTeK Computer Inc. Device 1347
Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 53
I/O ports at e0b0 [size=8]
I/O ports at e0a0 [size=4]
I/O ports at e090 [size=8]
I/O ports at e080 [size=4]
I/O ports at e060 [size=32]
Memory at df006000 (32-bit, non-prefetchable) [size=2K]
Capabilities: <access denied>
Kernel driver in use: ahci
Kernel modules: ahci
00:1f.3 SMBus: Intel Corporation 6 Series Chipset Family SMBus Controller (rev 05)
Subsystem: ASUSTeK Computer Inc. Device 1347
Flags: medium devsel, IRQ 18
Memory at df005000 (64-bit, non-prefetchable) [size=256]
I/O ports at e040 [size=32]
Kernel driver in use: i801_smbus
Kernel modules: i2c-i801
01:00.0 VGA compatible controller: nVidia Corporation Device 1247 (rev a1) (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. Device 2050
Flags: fast devsel, IRQ 16
Memory at da000000 (32-bit, non-prefetchable) [size=32M]
Memory at c0000000 (64-bit, prefetchable) [size=256M]
Memory at d0000000 (64-bit, prefetchable) [size=64M]
I/O ports at d000 [size=128]
Expansion ROM at dc000000 [disabled] [size=512K]
Capabilities: <access denied>
Kernel modules: nvidiafb, nvidia, nouveau
03:00.0 Network controller: Intel Corporation Centrino Wireless-N 1030 (rev 34)
Subsystem: Intel Corporation Centrino Wireless-N 1030 BGN
Flags: bus master, fast devsel, latency 0, IRQ 54
Memory at ddc00000 (64-bit, non-prefetchable) [size=8K]
Capabilities: <access denied>
Kernel driver in use: iwlagn
Kernel modules: iwlagn
04:00.0 USB Controller: Device 1b21:1042 (prog-if 30 [XHCI])
Subsystem: ASUSTeK Computer Inc. Device 1059
Flags: bus master, fast devsel, latency 0, IRQ 19
Memory at dd200000 (64-bit, non-prefetchable) [size=32K]
Capabilities: <access denied>
Kernel driver in use: xhci_hcd
Kernel modules: xhci-hcd
05:00.0 Ethernet controller: Atheros Communications Device 1083 (rev c0)
Subsystem: ASUSTeK Computer Inc. Device 1851
Flags: bus master, fast devsel, latency 0, IRQ 57
Memory at dc800000 (64-bit, non-prefetchable) [size=256K]
I/O ports at 9000 [size=128]
Capabilities: <access denied>
Kernel driver in use: atl1c
Kernel modules: atl1c
Last edited by grubshka (2011-11-10 21:05:40)

This seems to be fixed now. In the last update, kernel and drivers (and a lot of things) were updated, so I don't know which one fixed the bug...

Similar Messages

Screen Saver and Display Sleep No Longer Work

My set up:
Mac Pro (stock) w/ 3GB RAM running 10.4.8.
Two ADC displays connected via ADC to DVI adapters
Issue:
Recently I've noticed neither my screen saver nor display sleep work. I can get the machine to sleep manually, but not automatically. My energy settings have the display sleeping after 10 min w/ the computer and HDs never sleeping. Screen Saver is set to go on after 5 min.
My MP used to go into screen saver -> display sleep mode fine. I don't know exactly when the issues started, but probably around 10.4.8. I have not installed any major software recently other than normal Apple updates.
What I've tried:
I've tried resetting the Energy Setting and Screen Saver Prefs and then doing a restart.
If anyone has an idea what is preventing my MP from going into screen saver -> display sleep mode please post. This is driving me nuts.
MacBook Pro 1.83 (7200 HD)/ MacPro 2.66/ mini 1.5Ghz / PBG4 1.25Ghz Mac OS X (10.4.8)

Turned out a bad USB device was preventing sleep. Once I removed it the display went to sleep like a baby.

No HDMI signal after display sleep

When my display goes to sleep, after the time defined in the energy saver control panel, my receiver doesn't get the signal from HDMI and sounds stops, which is very anoying when for example I am listening to music. Is there a way to prevent this issue?

Well I guess time was enough to heal my ATV because it is working now.
BTW love the new home screen!

What happened to my login page after display sleep?

I'm not sure what happened but whenever my display goes to sleep and I click the trackpad to turn it back on, a dialog box shows up asking for my password. Prior to two days ago, when I woke the display the login screen would pop up with my user icon (just like the initial login screen, but without Guest), but now it's just the dialog box with a black screen. Anyone have any idea how this happened, or how to get it back to the way it was? I'm running OSX 10.8.4.

Okay. I am still convinced a firmware password. Safe mode wouldn't be a surefire test of this, I was wrong...this would be a test for open firmware password (applicable to machine up to 2010), not EFI password (2011 +). Try Booting into Recovery Mode (command + R) or hold down option at start and select the recovery partition. Are you prompted for a password? If so, there is a fimrware password set and only Apple would be able to unlock your machine. If not, I am out of suggestions. Please test and reply. Thanks.
Firmware Password Protection on Your Mac | Macinstruct
EFI firmware protection locks down newer Macs | MacFixIt - CNET ...

[Solved] Screen locker freezes display

I have been using xautolock (2.2-2) with a locker (recently switched to i3lock) for a couple of years now, with no complaints. Over the last week or so, probably related to Xorg updates (currently on 1.11.2-2), whenever slock was activated by xautolock, the entire display would freeze.
Entering my password had no effect, I couldn't switch to console - the only way to recover the machine was SSH in and reboot.
Frustratingly, there was nothing in Xorg logs, syslogs or dmesg.
I switched back to slock (0.9.6) and the same thing happened. Swapping xautolock out for sinac fixed the issue.
While I am happy enough with sinac, has anyone else experienced this? If it's a bug, I'd like corroboration so I can report it.
# edited title to reflect update below...
Last edited by jasonwryan (2011-12-12 21:42:51)

It seems I was too qucik to blame xautolock. Same issue with sinac -- which leads me to believe it is graphics card/driver related.
Card is an Intel 945GME and the driver is the standard xf86-video-intel. Downgrading to 2.16.0-1 seems to have staved it off for the time being...
Possibly related to this thread Display Locks Up on Screen Lock.

[SOLVED] Inkscape bug after last system update

After the last system update I started to have problems in Inkscape when I tried to adjust the color and alpha sliders to maximum values. They would only go up to 245. This means that a lot of basic colors are not achievable anymore, and the opacity cannot be set to maximum, which basically makes Inkscape unusable. After googling it for a while, I understood that there was a similar problem some time ago with Inkscape version 0.46-7 and GTK+ (here is a far better description of the bug, https://bugzilla.redhat.com/show_bug.cgi?id=467431), but this problem was assumably fixed in a later version (for the Red Hat package anyway). I am using at the moment Inkscape 0.46-10 and GTK2. Anyone with similar problems? Please help and thank you very much!
Last edited by anca (2009-04-02 11:20:53)

anca wrote:
I tried setting the values manually... I even tried, believe it or not, to edit the XML file! Maybe I'm doing something wrong. Could you please describe in more detail what exactly you did to fix it? I have a lot of images to finish and he deadline is getting scaringly close . Anyway, thank you so much for your feed-back!
Anca
under the fill and stroke dialogue (ctrl-f), there is a small input box called RGBA which is just that, 1 byte for each channel. edit it at will. you will notice the sliders dont go past 245, but the value used by inkscape is the hex number there

Screen jitter after long sleep

Hi Folks -
I have macbook air (about 2 years old) running Mac OS X 10.8.3. Lately I'm veen noticing that the LCD screens jitters and jumps when awaking from a long sleep. If I sleep the computer again, and then wake it up immediately, the problem goes away.
Anybody seen anything like that?
Paul

Consider a possible third party software issue.
Consider a visit to the optometrist.

Screen Pixalation when using Sleep and Auto Logout problems. OS bug?

Original Thread here: http://forums.macrumors.com/showthread.php?t=1295058
Thread Tools
Search this Thread
Display Modes
Dec 21, 2011, 01:01 PM
#1
gswilder
macrumors regular
Join Date: Oct 2007
iMac Sleep Problem Waking - Screen Black & Pixelization
Have a new BTO 27" iMac I received a couple of weeks ago. Of course it is running Lion 10.7....
I am having a screen problem "waking" my iMac. (I also have this problem randomly on my MB Air - mid 2011 model)
After the iMac is in true sleep mode
(I have it set to enter a password after sleep mode)
Screen is blank/off
I "wiggle" my mouse or trackpad
Screen is still blank (sometimes it may display my screen saver, but the screensaver is frozen)
If I start moving the mouse or trackpad, it starts "un painting" the black screen. You can see whatever is supposed to be on the screen, such as the logon "button".
It is really wierd. Like a black "overlay" is painted on the resume from sleep screen. As I move my mouse or trackpad, it is basically erasing the black, to show what is underneath. Each movement of the mouse, erases a small black square.
I usually move my mouse around the middle of the screen to uncover the logon button. Press the logon button. The screen magically reappears as normal. I enter my password and system logs back on normally.
It only seems to be when the iMac is in really deep sleep mode. If the screen is just blank for an hour or so. I move the mouse/trackpad, and the logon screen is immediately displayed normally.
Any thoughts or recommendations?
Thanks to all in advance.
Greg
0
Dec 23, 2011, 12:17 AM
#2
gswilder
Thread Starter
macrumors regular
Join Date: Oct 2007
UPdate
Still experimenting.
If certain programs are running (ie Firefox), then I don't have a problem coming out of deep sleep. It gives me a message when I reenter my password, that Firefox prevented the system from logging off.
Does that additional information help? It is a really annoying problem. And since I have it on my MBA, I am concerned it is more widespread. Does anyone else have this issue?
0
Dec 24, 2011, 09:18 PM
#3
UNCHeelYeah
macrumors newbie
Join Date: Dec 2011
Black Screen and "Erasure" with Mouse.
I am having this same problem. I am using the Mac OS X Lion 10.7.2, not using a screen saver, and it happens sporadically upon trying to wake my iMac from sleep mode. The screen is black, and as you move the mouse over the screen, it "erases" the black, like the opposite of a blackboard, to reveal the login name and picture underneath. After that everything works fine. There is no pattern to this that I can discern (e.g. - happens every fifth time, only happens when a program isn't running etc.). It appears random, but is uber annoying, and behaves like a virus. I have Norton Antivirus, and it updates daily, and upon scanning states no virus is found. I also do system scan with MacKeeper, and it scans, says system is excellent. Something is definitely going on, I just wish I knew what it was. If anyone has any knowledge of this, any solution or insight would be greatly appreciated! Thanks!
0
Dec 25, 2011, 12:29 PM
#4
GGJstudios
macrumors G4
Join Date: May 2008
Quote:
Originally Posted by UNCHeelYeah
It appears random, but is uber annoying, and behaves like a virus. I have Norton Antivirus, and it updates daily, and upon scanning states no virus is found.
That's because there are no Mac OS X viruses. You should uninstall Norton. You don't need 3rd party antivirus apps to protect your Mac from malware. Macs are not immune to malware, but no true viruses exist in the wild that can run on Mac OS X, and there never have been any since it was released 10 years ago. The only malware in the wild that can affect Mac OS X is a handful of trojans, which can be easily avoided with some basic education, common sense and care in what software you install. Also, Mac OS X Snow Leopard and Lion have anti-malware protection built in, further reducing the need for 3rd party antivirus apps.
Mac Virus/Malware Info
Quote:
Originally Posted by UNCHeelYeah
I also do system scan with MacKeeper, and it scans, says system is excellent.
You don't need MacKeeper, either. You really don't need "cleaner" or "maintenance" apps to keep your Mac running well, and some of these apps can do more harm than good. Most only remove files/folders or unused languages or architectures, which does nothing more than free up some drive space. It will not make your Mac run faster or more efficiently, since having stuff stored on a drive does not impact performance, unless you're running out of drive space.
Mac OS X does a good job of taking care of itself, without the need for 3rd party software.
Your problem, and the OP's is a graphics problem, likely having to do with the screensaver, not a malware problem.
1
Dec 26, 2011, 08:13 AM
#5
UNCHeelYeah
macrumors newbie
Join Date: Dec 2011
Norton Antivirus, and what does it mean?
I suppose one reason I developed a concern that there was more here than meets the proverbial eye, so to speak was a message that I have received through Norton on multiple occasions. The last message of similar stated messages reads as follows (Norton Antivirus 2.2.1 (5) ): "Vulnerability blocked, December 13th, 2011, 8:57 P.M. When I click on "View Recent Activities", a window is opened that is titled "Activity Log." There, four columns are listed, titled from left to right "Date", "Event Type", "Result", and "Details." Under the December 13th episode, It lists "Portscan" under Event type, "Result" gives an IP Address (192.168.x.xxx), and "Incoming" under details.
I am admittedly a neophyte in the Mac world, having switched over from Windows 7 to Mac recently, but am intent on educating myself to the not-so-subtle differences. The above information that Norton displayed would lead one to believe that their antivirus software is protecting my iMac, and that its subsequent removal would have perhaps disastrous results ( i.e. - my iMac would be susceptible to said "Vulnerability", whatever it is, and that "Incoming would NOT be blocked). I had a conversation with Norton because previously, every time the stated "Vulnerability" attempted access, I was interrupted by a pop-up screen informing me of this. The Norton representative was able to turn off the pop-up screen notification, but stated that it would continue to log episodes of the "Vulnerability" when it attempted to portscan and access. So am I to understand that uninstalling Norton would leave my computer no less vulnerable to this vulnerability? It is confusing to me.
Furthermore, I suppose I did wonder if this vulnerability threat had anything to do with the issue of the black screen erasure with the mouse. I will attempt to post a picture of the screen as it was being erased with the mouse, and perhaps a short movie as well. As previously stated, I do not have a screen saver enabled. Thank you for your input, any information is helpful to me! _
~Marc
http://forums.macrumors.com/attachment.php?attachmentid=317412&d=1324905189
0
Dec 26, 2011, 11:19 AM
#6
gswilder
Thread Starter
macrumors regular
Join Date: Oct 2007
Ditto & FYI Workaround
UncHeel...
Thanks for posting the picture. It is same as my iMac problem. On my iMac, it happens 100% of the time. On my MBA, it happens randomly like yours.
I began to notice if certain programs were running, when it went into screen saver and sleep mode, this didn't happen. And when I woke it up, I got a message that said "could not be logged off due to Firefox or Sketchbook Pro, etc. So that got me to thinking. So....
Over the weekend, I disabled "logoff after xx minutes of activity" in system preferences. That seems to fix the issue. I still have it set to require a password after the screen saver/sleep mode kicks it. But I disabled the logoff toggle.
Still not sure what this is an issue, but seems to be a work around. I just want to make sure my iMac is still going into sleep with these new settings. Including the monitor sleep.
Any thoughts based on this new information?
Thanks again
Greg
0
Dec 26, 2011, 11:52 AM
#7
GGJstudios
macrumors G4
Join Date: May 2008
Quote:
Originally Posted by UNCHeelYeah
The above information that Norton displayed would lead one to believe that their antivirus software is protecting my iMac, and that its subsequent removal would have perhaps disastrous results
You have to remember that many antivirus apps consider cookies to be a "vulnerability" or "threat", when they're not. The only malware in the wild that can affect Mac OS X requires the user to actively install it. As long as a user is reasonably careful about where they get software, there is no need for 3rd party antivirus apps to protect Mac OS X from malware. Just make sure your firewall is enabled (System Preferences > Security > Firewall), and disable Java in your browser (Safari > Preferences > Security > Enable Java (uncheck))
Quote:
Originally Posted by gswilder
I just want to make sure my iMac is still going into sleep with these new settings. Including the monitor sleep.
You can let it sleep without logging off. That way, your apps/documents are still open when you wake it up, rather than having to relaunch apps and reopen documents. Recovery from sleep is much faster than from logging off.
0
Dec 27, 2011, 03:02 PM
#8
rda2w
macrumors newbie
Join Date: Oct 2011
Quote:
Originally Posted by gswilder
UncHeel...
Thanks for posting the picture. It is same as my iMac problem. On my iMac, it happens 100% of the time. On my MBA, it happens randomly like yours.
I began to notice if certain programs were running, when it went into screen saver and sleep mode, this didn't happen. And when I woke it up, I got a message that said "could not be logged off due to Firefox or Sketchbook Pro, etc. So that got me to thinking. So....
Over the weekend, I disabled "logoff after xx minutes of activity" in system preferences. That seems to fix the issue. I still have it set to require a password after the screen saver/sleep mode kicks it. But I disabled the logoff toggle.
Still not sure what this is an issue, but seems to be a work around. I just want to make sure my iMac is still going into sleep with these new settings. Including the monitor sleep.
Any thoughts based on this new information?
Thanks again
Greg
I have had the same problem on my mid-2010 iMac since upgrading to Lion and it's been driving me nuts. The relation to automatic Logoff makes sense to me now that I look at my settings. The logoff was occurring after sleep and it's the only thing I haven't tried yet. I had previously thought it was related to Sleep but it never occurs if I force it to sleep. It only occurs after the system was left unattended and went through it's normal steps of screensaver then sleep. I'll try disabling the automatic Logoff and see if it fixes the problem for me too.
-BA
0
Dec 29, 2011, 10:58 AM
#9
rda2w
macrumors newbie
Join Date: Oct 2011
Quote:
Originally Posted by rda2w
I have had the same problem on my mid-2010 iMac since upgrading to Lion and it's been driving me nuts. The relation to automatic Logoff makes sense to me now that I look at my settings. The logoff was occurring after sleep and it's the only thing I haven't tried yet. I had previously thought it was related to Sleep but it never occurs if I force it to sleep. It only occurs after the system was left unattended and went through it's normal steps of screensaver then sleep. I'll try disabling the automatic Logoff and see if it fixes the problem for me too.
-BA
I can only declare partial success with unpicking "logoff after xx". It solved the pixelated screen issue but now the computer is not sleeping. I guess I'll have to uncheck file sharing now.
-BA
0
Feb 6, 2012, 06:26 PM
#10
ougrad1764
macrumors newbie
Join Date: Apr 2010
Any updates?
Just wanted to see if there had been any changes since the last posting in this thread. I'm experiencing the same issue as OP on my 2011 13" MacBook Air w/ OS X 10.7.3, as well as on my parents' mid-2010 iMac (running OS X 10.7.2).
I can't seem to pin down the cause and have tried the steps suggested previously. Thanks!
0
Feb 21, 2012, 10:03 PM
#11
wchp
macrumors newbie
Join Date: Feb 2012
Still having the same issue here as well.
Have any of you tried a clean install of OSX?
Before I try a full reinstall I did an install on a external drive with no aps, just the bare install and I could not replicate the issue.
I continue to question if this is a graphics card firmware issue or and OS issue.
A reinstall (overlay) of the OS did not resolve the issue.
I have screen shots as follows:
1) Paint pixels on screen
http://i129.photobucket.com/albums/p227/wchp/iMac27%20Graphics%20Problem/photo1. jpg
2) Click Icon
http://i129.photobucket.com/albums/p227/wchp/iMac27%20Graphics%20Problem/photo2. jpg
3) Type in PWD
http://i129.photobucket.com/albums/p227/wchp/iMac27%20Graphics%20Problem/photo3. jpg
4) Logged in:
http://i129.photobucket.com/albums/p227/wchp/iMac27%20Graphics%20Problem/photo4. jpg
Last edited by grapes911; Feb 21, 2012 at 10:12 PM. Reason: replaced img with timg
0
Yesterday, 12:21 AM
#12
jrobin
macrumors newbie
Join Date: Feb 2012
Having the same issue
I have four MacBooks and a MacBook Air. I am seeing this issue on two MacBooks both running Lion 10.7.3. One is a newer i5 MacBook the other is an early 2010. The only common denominator I can think of is they are both set up with Parental Controls and they are set to logoff after X amount of time. The other MacBooks don't have this "pixel painting to revel the login screen issue" I also don't see it on our iMacs or the MacMini. Only the two with the issue are set to auto logoff. So the above poster is most likely on to something. I will give it a try by turning off the auto logoff on the two MacBooks in question. If that solves the problem then I will assume its a bug that needs to be addressed.
0
Yesterday, 12:30 AM
#13
ougrad1764
macrumors newbie
Join Date: Apr 2010
reinstall (overlay) of the OS did not resolve the issue
wchp - Thank you for following up and posting the screenshots. They match exactly what I was experiencing (and what UNCHeelYeah reported previously). I can confirm that I experienced the issue even following a clean reinstall of Snow Leopard on my MacBook Air (13-inch, Mid 2011).
jrobin - "I will give it a try by turning off the auto logoff on the two MacBooks in question. If that solves the problem then I will assume its a bug that needs to be addressed."
Good thinking! Thanks for taking the time to test with your machines. This will help provide further validation of what gswilder (OP) tried as well in reply #6. Interesting about Parental Controls, too.
Side note:
Since I recently joined the Apple Developers program, I did a clean install of SL on my MBA then upgraded via the App Store to Mountain Lion to "kick-the-tires" if you will. Interestingly, I've not yet experienced any issue related to waking from sleep with a black screen and pixilation, even while running all the same apps I had previously. I'll report here (and file a bug report with Apple) if I do see this issue pop-up in ML. I'll be reinstalling SL in a few weeks and will report back if/when the black screen and pixelation issue reappears. I'll be sure to note the applications left running at the time the computer went to sleep.
Last edited by ougrad1764; Yesterday at 12:44 AM. Reason: Follow-up to jrobin (reply came in while I was typing mine)
0
Yesterday, 09:04 AM
#14
evillanueva
macrumors newbie
Join Date: Feb 2012
I have experienced the same issue with my brand new MBA Late 2011.
I recently found out that this only happens when DISPLAY is set to go to sleep minutes before the "Log out after X minutes of inactivity". I had "Display sleep" option set to 5 minutes and "Log out after 10 minutes of inactivity" and this causes the display to go to sleep first (screen goes black) and then, 5 minutes later, it logs out.
If "Display sleep" is off and "Log out after X minutes of inactivity" is on, the issue does not replicate. So Im thinking it has something to do with the screen being black at the moment it logs out. Can you try and replicate that?
Thanks
0
Yesterday, 01:39 PM
#15
wchp
macrumors newbie
Join Date: Feb 2012
Quote:
Originally Posted by evillanueva
I have experienced the same issue with my brand new MBA Late 2011.
I recently found out that this only happens when DISPLAY is set to go to sleep minutes before the "Log out after X minutes of inactivity". I had "Display sleep" option set to 5 minutes and "Log out after 10 minutes of inactivity" and this causes the display to go to sleep first (screen goes black) and then, 5 minutes later, it logs out.
If "Display sleep" is off and "Log out after X minutes of inactivity" is on, the issue does not replicate. So Im thinking it has something to do with the screen being black at the moment it logs out. Can you try and replicate that?
Thanks
Just tested this premise and yes, you are correct.
IF: Screen saver ON after 5m AND require password immediately AND Sleep (Display) after 30m AND Logout after 60m I am able to reproduce the problem.
IF: Screen Saver ON after 5m AND require password immediately AND Sleep (Display) after 30m AND Logut after xx NOT enabled, problem goes away
IF: Screen Saver ON after 5m AND require password immediately AND Sleep (Display) OFF AND Logut after 60M enabled, problem goes away
So on my machine (iMac 27, 3.4/i7, 16GB/1333, Radeon 6970m/2048MB, OSX 10.7.3
It would appear that if I am running Monitor Sleep and it kicks in prior to LogOff then I am able to reproduce this artifact. Only Display sleep with immediate login OR Loguot should be used but not both.
The only other thing to test is is I leave display sleep on, and screen saver on but with NO immediate password and enable logoff if the problem goes away.
Testing for another day.
I have linked this entire thread to a Apple support ticket and will report back on Apples response

Thank you so much wchp, this is brilliant. I have had this annoying problem for a long time. I eventually rang Mac support, they did not know how to fix the problem as you have suggested so they instigated many hardware replacements which eventually left my iMac severely crippled. They eventually replaced it with the latest model. But I spent two months working with a disabled computer which really interfere with my work.
Your solution appears to have solved my problem, at least so far, but I am hopeful that it is a permanent fix. I hope that your suggestions are taken up by Apple support. This may solve many users problems and avoid Apple making expensive fixes that don't actually work.
I thought that the new iMac would not have the 'Wake up from sleep by painting in the login window' problem but it did, this really annoyed me. Anyway now the problem appears to be solved, it's not I will repost and keep working on it. Thanks again.

External display resolution changes after returning from display sleep

I often use an external display as a second screen with my Macbook Pro (OS X 10.8.2) However, when I return to the computer after the display has gone to sleep, the external display resolution changes when the display reappears. Then I have to go into System Preferences > Display and "Detect Displays" in order to return the external display to the proper resolution.
Does anybody know of a way for me to avoid having to do this every time my display sleeps?
Thank you,
Adam

I have the exact same problem.
I found the key combination ⌘ alt F2 also restores the proper resolution on both displays, however it's still a bit annoying

Help! 2010 imac 27" - Display doesn't work after long sleep

I just recently started having this problem. I've had this iMac since 2010 with zero issues, but it seems like ever since I downloaded Yosemite, the screen won't work after the computer has been sleeping for a while. I have to hold the power button and do a hard restart to get it to work again. If the computer has only been sleeping for a while, it wakes just fine. It's only after it's been sleeping all night and I go to use it agsin. I've checked power connections and all is good. Any ideas??

Hi Punisher8522,
Welcome to the Support Communities! The resource below offers some troubleshooting steps to try when your computer won't wake from sleep.
OS X: When your Mac doesn't sleep or wake - Apple Support
http://support.apple.com/en-us/TS5357
Your computer cannot wake from sleep
Make sure your computer isn't powered off by pressing the power key for one second.
If you're using an external display, make sure your display is not powered off or unplugged.
If you are using a Mac desktop:
Make sure the AC power cord is connected securely to the computer and outlet.
Make sure the AC power outlet it is connected to is working properly.
If your computer is plugged into a power strip, make sure the power strip is not turned off. Check to make sure other items connected to the power strip are receiving power.
Your computer is slow to wake from sleep
If you see a progress bar when you wake your computer from sleep, this is normal. The computer is waking from safe sleep.
OS X Recovery and sleep
The system software your computer uses when started from OS X Recovery allows display sleep. Your computer does not go to sleep on idle while started from Recovery unless you are using a Mac notebook that is not connected to AC power.
Additional troubleshooting
If the steps above do not resolve your sleep-related issue, try these additional recommendations.
Reset SMC
The System Management Controller (SMC) is involved in managing power on your computer. Reset the SMC on your Mac if you are having difficulty sleeping or waking your computer.
Reset NVRAM/PRAM
Nonvolatile RAM (NVRAM)/Parameter RAM (PRAM) stores some power-related settings.Try resetting NVRAM/PRAM if you are having difficulty sleeping or waking your computer.
Test with external devices disconnected
Some external devices can prevent your computer from sleeping. Try disconnecting items other than your Apple keyboard or mouse from the built-in USB, Thunderbolt and Firewire ports on your Mac. If this resolves the issue, try reconnecting your external devices one at a time until you find the device preventing sleep or wake. Check the documentation that came with the device, or contact the device manufacturer for more information.
Try Safe Mode
Check to see if the issue still occurs when the computer is started in Safe Mode. If this resolves the issue, it could be related to a third party software item such as:
a login item
a startup item
a third party kernel extension
Try another user account
Try creating another user account, or log in as guest. See if your computer sleeps and wakes properly from the additional user account. If it does, your issue may be related to one of the following:
a login item
an app open in the original user account
You can disable login items from the Accounts pane of System Preferences. Try opening only one app at a time in the original user account to determine which app is preventing sleep. If you isolate the issue to a particular app or login item, check its documentation, or contact the developer of that software for more information.
Last Modified: Sep 19, 2014
I hope this information helps ....
- Judy

Display sleeps after 1-2 minutes running Windows 8.1

Both my MacBook Pro Retina 15-inch (Early 2013) and my wife/son's MacBook Pro 13-inch (Late 2011) are dual booted with Windows 8.1. Both have the same display issue; the display goes to sleep after approximately 1 to 2 minutes (1:20 to be precise). The issue didn't appear until the 2nd day after the install on my MacBook Pro Retina and it has been an ongoing issue for my wife on her 13-inch. Is it related to the 5.1.5621 or 5.1.5640 Boot Camp drivers? Can I remove those drivers and try to go back to the previously released set of drivers? That is when I notice the issue show on my MacBook but honestly there were so many updates through the process that this is just a guess. It's more of a nuisance than anything. After finding and installing Lubbos for the heating issue and TrackPad++ for the trackpad options I was hoping I could solve this as well. Has anyone heard of a fix for this? The only display/sleep issues I've been able to find are not similar to my issue, from what I've read anyways. Any assistance would be greatly appreciated.

I'm having the same problem and have been working with my company for a week trying to resolve this. We've tried the following:
- Altering MTU settings (700 - 1400)
- Turning on/off wireless and connecting via Ethernet
- Turning on/off encryption
- Tried DigiTunnel VPN client
None of this seems to work.
I am able to connect fine via Windows installed on the same MacBook. It's just the MacOS side that disconnects.

Mac Mini wont' Display Sleep after Yosemite Update

My Mac Mini is no longer going into Display Sleep. Instead I now see the Screen Saver. I have checked System Preferences | Energy Saver and it is definitely set to Display Sleep after 10 minutes (The default). What is interesting is that if I try to change the Display Sleep time (e.g. to 1 hour), when I go back into Energy Saver, it is back to 10 minutes - this doesn't look right! In fact none of the options (e.g. Wake on LAN) seem to stay changed.
This seemed to start after the update to Yosemite 10.10.1 a few days ago - but that might be coincidental. Until then Display Sleep had worked fine.
Any suggestions?
Thanks
Nick

This procedure is a diagnostic test. It makes no changes to your data.
Please triple-click anywhere in the line below on this page to select it:
defaults read /Library/Preferences/SystemConfiguration/com.apple.PowerManagement | pbcopy
Copy the selected text to the Clipboard by pressing the key combination command-C.
Launch the built-in Terminal application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Terminal in the icon grid.
Paste into the Terminal window by pressing the key combination command-V. I've tested these instructions only with the Safari web browser. If you use another browser, you may have to press the return key after pasting.
Wait for a new line ending in a dollar sign ($) to appear below what you entered.
The output of the command will be automatically copied to the Clipboard. If the command produced no output, the Clipboard will be empty. Paste into a reply to this message.
The Terminal window doesn't show the output. Please don't copy anything from there.

T60 Type 2623 Blue Screen on Resume from Sleep Mode problem solved - XP Pro

I hope that this post ends some frustrations for some people.
I hope that IBM deals with this issue by getting ATI to fix the video driver issue.
After three months of tracking down blue screens when resuming from Sleep Mode and some lockups while working, I have identified the problem on my T60 Type 2623 running Windows XP-Pro and all service packs and updates. The Sleep Mode resume issues were intermittant and it would be fine for a day or two and then reboot on Resume or reboot every time I used Resume for a while. For months the Blue Screen would reboot and attempt to send the message to Microsoft using the logs, but the logs were always corrupted. I disabled every driver that I could and the problem continued for months.
The problem solution came about when I decided to try my Rhapsody Music account after many months of not using it. I kept getting a message about DRM (Digital Right Management) being disabled and Rhapsody software could not self-fix this. So I finally called Rhapsody and they spent over an hour with me trying to get Rhapsody to work. The support person asked me about my computer and I noted that it was an IBM T60. He then asked about my Video Card and I responded that it was an ATI Mobility Radeon X1300. After a few minutes on hold he asked about my driver version which was 8.442.3-080103a1-057754C the set from January 31, 2008. He noted that there is a known problem wit the 8.4 driver and it interferes with DRM. He had me go to control panel Settings and Hardware and then roll-back the driver to the prior version.
After a reboot, the DRM issue was solved and I soon discovered that my resume from Sleep mode no longer crashed. In fact it has been fine and crash free for over a month now. I have noted that the older driver can sometimes resize my screen to something like 600 X 800 if I close the lid under certain circumstances, but that is just a function key reset to get my normal desktop resolution back. At least it is not a blue screen reboot with a corrupted log file.
Message Edited by retro74 on 07-05-2008 08:50 AM
Solved!
Go to Solution.

Unfortunately I could not fix the problem so I wiped my system and loaded all new drivers before I found this posting.
Is there a way to get the old ATI driver that works? The only one available on the ATI and Lenovo website is the latest one with the problem. I agree with you David, Lenovo should have fixed this problem already with ATI.
John

"Disable Screen Saver" hot corner no longer prevents Display Sleep

I am not sure whether it started only after I upgraded to 10.5.7, but I certainly have this very annoying issue right now.
I have "Disable Screen Saver" assigned to the top right "hot corner". Some time ago I could place my mouse pointer there in order to prevent activating of "Display Sleep" (as well as gradually dimming before jumping into bed).
It no longer works. I have my pointer in the right corner, and nevertheless the display first dims, then goes to sleep.
Is this only my problem? Any ideas how to fix it? Thanks!

Anybody?

Screen saver + Energy Saver (Computer Sleep + Display Sleep) won't work since Mavericks

Howdy,
Sorry to bother you.
My computer: iMac (21.5-inch Mid 2011), Mac OS X (10.7.3)
It took me some time to upgrade to Mavericks, but I did it eventually.
After having some problems with Spotlight (which was infinite looping indexing... and I just had to turn if off from Terminal), I realized I was encountering another big problem to me since the installation of Mavericks.
In System Preferences:
- 'Desktop and Screen Saver > Screen Saver' : it is set to 1 minute;
- 'Energy Saver > Computer Sleep' : it is set to 10 minutes;
- 'Energy Saver > Display Sleep' : it is set to 5 minutes;
- 'Energy Saver > Put hard disks to sleep when possible' : it is checked.
- 'Energy Saver > Wake for network access' : it was checked. I unchecked it. Nothing changes.
- 'Energy Saver > Start up automatically after a power failure' : it is unchecked.
- 'Energy Saver > Allow power button to put computer to sleep' : this option is absent from my System Preferences > Energy Saver, but I would like it.
So, before Mavericks, everything was working great.
Now, after 1 minute, or after 5 minutes, or after 10 minutes: it's all the same. Nothing is sleepy. Nothing is energy saving.
I did not change anything in my computer since I've updated to Mavericks. However, I changed Wi-Fi. Since it was the only new change, I've "played" with 'Energy Saver > Wake for network access'. When I opened my System Preferences, it was checked. I unchecked it. It did not change anything. I'm not sure what it's used for.
I would appreciate any advice to make it work as it used to.
Thanks for your time reading and typing your answer,
Have a good day,
Regards,

- 'Energy Saver > Allow power button to put computer to sleep' : this option is absent from my System Preferences > Energy Saver, but I would like it.
Built into the Software now.
Do a backup.
Quit the application.
Go to Finder and select your user/home folder. With that Finder window as the front window, either select Finder/View/Show View options or go command - J. When the View options opens, check ’Show Library Folder’. That should make your user library folder visible in your user/home folder. Select Preferences/com.apple.systempreferences.plist. Move the .plist to your desktop.
Restart, open the application and test. If it works okay, delete the plist from the desktop.
If the application is the same, return the .plist to where you got it from, overwriting the newer one.
Thanks to leonie for some information contained in this.
You might try Spotlight again. That is how the App Store knows what is installed.

[Solved] Screen bug after display sleep

Similar Messages

Maybe you are looking for