Did 10.8.4 break Target Display Mode?

Question

Level 1

0 points

Did 10.8.4 break Target Display Mode?

I've been using Target Display Mode for years now for my PC (ATI graphics card with MDP output) but after 10.8.4 I've been unable to switch to Target Display Mode. Mostly it just flickers - other times it just goes black. I've tested the PC on another monitor and that works fine.

6/6/13 8:50:43.754 PM WindowServer[174]: Received display connect changed for display 0x3f003c

6/6/13 8:50:43.762 PM WindowServer[174]: New display device coming on-line. Switching from virtual display mode

6/6/13 8:50:43.767 PM WindowServer[174]: Created shield window 0x163 for display 0x04273580

6/6/13 8:50:43.767 PM WindowServer[174]: handle_will_sleep_auth_and_shield_windows: no action for lock state 1

6/6/13 8:50:43.768 PM WindowServer[174]: Received display connect changed for display 0x3f003d

6/6/13 8:50:44.058 PM WindowServer[174]: Display 0x003f003d: GL mask 0x2; bounds (2944, 0)[1 x 1], 1 modes available

off-line, enabled, Vendor ffffffff, Model ffffffff, S/N ffffffff, Unit 1, Rotation 0

UUID 0xffffffffffffffffffffffff003f003d

6/6/13 8:50:44.059 PM WindowServer[174]: Display 0x04273580: GL mask 0x1; bounds (0, 0)[1920 x 1200], 36 modes available

Main, Active, on-line, enabled, built-in, boot, OpenGL-accel, Vendor 610, Model 9cd6, S/N 0, Unit 0, Rotation 0

UUID 0x0000061000009cd60000000004273580, ColorProfile { 11, "iMac"}

6/6/13 8:50:44.059 PM WindowServer[174]: GLCompositor: GL renderer id 0x01021b02, GL mask 0x00000003, accelerator 0x00003c93, unit 0, caps QEX|QGL|MIPMAP, vram 1024 MB

texture units 8, texture max 16384, viewport max {16384, 16384}, extensions FPRG|NPOT|GLSL|FLOAT

I'm guessing the highlighted log entry got something to do with it - saying it's offline and some wierd resolution and display modes available.

Anyone else experiencing something similar since 10.8.4? And if it is related to the update - anyway of doing a rollback to 10.8.3?

Regards

Simon

Posted on Jun 6, 2013 12:04 PM

Reply

Answer 1

rkaufmann87

Level 10

140,790 points

Jun 6, 2013 12:07 PM in response to Mordrin

NO but you may need to restart in Recovery Mode, run Disk Utilities - Reset DIsk Permissions and while you're there please Repair Disk.

BTW you don't state which iMac you so it's a little tough to help you out.

Reply

Answer 2

Mordrin Author

Level 1

0 points

Jun 6, 2013 12:14 PM in response to rkaufmann87

Sorry - it's a Mid 2010 iMac 27-inch.

I'll try Reset Disk Permissions and Repair right away.

Reply

Answer 3

Mordrin Author

Level 1

0 points

Jun 6, 2013 12:38 PM in response to rkaufmann87

Unfortunately the Reset Disk Permissions and Repair Disk didn't help. The permission reset did change permissions on a lot of folders - including some related to CoreGraphics - but I'm still unable to activate Target Display Mode.

When screen just flickers, I receive the following errors:

6/6/13 9:32:54.041 PM com.apple.launchd[1]: (com.apple.dpd[456]) Exited with code: 75

6/6/13 9:32:54.065 PM coreaudiod[155]: Disabled automatic stack shots because audio IO is active

6/6/13 9:32:54.066 PM coreaudiod[155]: Enabled automatic stack shots because audio IO is inactive

I believe com.apple.dpd is a Display Port Daemon? Not sure what exit code 75 means though.

When I manage to get it to activate (and see just a black screen) I get these log entries:

6/6/13 9:33:16.537 PM WindowServer[118]: Received display connect changed for display 0x4273580

6/6/13 9:33:16.540 PM WindowServer[118]: No display devices are on-line. Switching to virtual display mode

6/6/13 9:33:16.540 PM WindowServer[118]: Received display connect changed for display 0x3f003d

6/6/13 9:33:16.794 PM WindowServer[118]: Display 0x41dc9d01: GL mask 0x2; bounds (0, 0)[1280 x 1024], 2 modes available

off-line, enabled, built-in, Vendor 756e6b6e, Model 76697274, S/N 0, Unit 1, Rotation 0

UUID 0xffffffffffffffffffffffff003f003d

6/6/13 9:33:16.794 PM WindowServer[118]: Display 0x41dc9d00: GL mask 0x1; bounds (0, 0)[2560 x 1440], 11 modes available

Main, Active, on-line, enabled, built-in, Vendor 756e6b6e, Model 76697274, S/N 0, Unit 0, Rotation 0

UUID 0x0000061000009cd60000000004273580

6/6/13 9:33:21.795 PM WindowServer[118]: post_notification : Time out waiting for reply from "Google Chrome Helper" for notification type 100 (CID 0x14c03, PID 430)

6/6/13 9:33:21.798 PM WindowServer[118]: Created shield window 0x51 for display 0x41dc9d01

6/6/13 9:33:21.804 PM WindowServer[118]: Created shield window 0x52 for display 0x41dc9d00

6/6/13 9:33:21.805 PM WindowServer[118]: Display added

6/6/13 9:33:21.805 PM WindowServer[118]: Display removed

6/6/13 9:33:21.808 PM WindowServer[118]: Display 0x41dc9d00: GL mask 0x1; bounds (0, 0)[2560 x 1440], 11 modes available

Main, Active, on-line, enabled, built-in, Vendor 756e6b6e, Model 76697274, S/N 0, Unit 0, Rotation 0

UUID 0x0000061000009cd60000000004273580

6/6/13 9:33:21.808 PM WindowServer[118]: Display 0x41dc9d01: GL mask 0x2; bounds (3584, 0)[1 x 1], 2 modes available

off-line, enabled, built-in, Vendor 756e6b6e, Model 76697274, S/N 0, Unit 1, Rotation 0

UUID 0xffffffffffffffffffffffff003f003d

6/6/13 9:33:21.811 PM SRFeature[378]: DisplayReconfigured 04273580 00000220

6/6/13 9:33:21.813 PM SRFeature[378]: DisplayReconfigured 41DC9D00 0000011E

Gotta admit this is a bit above my head - can't make much sense of it.

Reply

Answer 4

rkaufmann87

Level 10

140,790 points

Jun 6, 2013 3:17 PM in response to Mordrin

For the most part you dont' need to be concered with the information. Apple publishes an advice letter that addresses this at support.apple.com/kb/TA21090.

That being said I would recommend you run Repairing Disk Permissions at least 2x in a row and also while you are in Disk Utility run Repair Disk too. You have to be Recovery Mode to do this, please remember that.

Reply

Answer 5

Mordrin Author

Level 1

0 points

Jun 7, 2013 12:49 PM in response to rkaufmann87

Ok, I've tried your suggestions - ran Repair Disk Permissions twice while in Recovery Mode and Repair Disk as well. Still same problem.

I also tried attaching my MacBook instead of the PC and was unable to get Target Display Mode to work for that one either - same errors in log.

So my guess is either the update broke it or something broke on my installation. Guess next troubleshooting step is a reinstall 😟

Thanks for your suggestions though - would have been really happy if that would have fixed the problem.

Reply

Answer 6

Jun 7, 2013 5:06 PM in response to Mordrin

Hi, i'm presenting the same problem after updating to 10.8.4.

i've tried to solved doing the recomendations that i saw here, but nothing...

Did you find a solution for the problem of the startup?

thanks for your time, i'll be waiting for an answer.

Reply

Answer 7

Jul 6, 2013 6:22 AM in response to Mordrin

I'm having the same problem with 10.8.4 running on my Late 2009 iMac. I have my iMac hooked up to my PC's Radeon 6870 via DisplayPort. It has always worked perfectly for me, but now the screen either just flickers, or goes to a black screen. If you keep trying, eventually it will switch successfully, but it takes a LOT of tries. I hope someone fixes this soon, or someone finds a workaround. This is a very important feature for me.

Reply

Answer 8

rkaufmann87

Level 10

140,790 points

Jul 6, 2013 6:29 AM in response to wightlight

wightlight wrote:

I'm having the same problem with 10.8.4 running on my Late 2009 iMac. I have my iMac hooked up to my PC's Radeon 6870 via DisplayPort. It has always worked perfectly for me, but now the screen either just flickers, or goes to a black screen. If you keep trying, eventually it will switch successfully, but it takes a LOT of tries. I hope someone fixes this soon, or someone finds a workaround. This is a very important feature for me.

Please create your own thread, rather than a "me too", your issue may be different.

Reply

Answer 9

Mordrin Author

Level 1

0 points

Jul 31, 2013 1:59 AM in response to wightlight

I know it's been a while but I just wanted to let you know that a colleague of mine had a 10.8.3 installer. I used this for a reinstall and have not had any issues with TDM since. It's definitely an issue introduced in 10.8.4 and I wish Apple would acknowledge this as I have intention of installing any more updates until this bug is fixed.

Reply

Answer 10

Mordrin Author

Level 1

0 points

Oct 9, 2013 7:42 AM in response to Mordrin

Another update...

After the release of 10.8.5 and supplemental update, I finally worked up the courage to try again - hoping the issue was fixed...

It is not 😟

Had trouble switching to TDM on my first attempt after applying 10.8.5. I used the 10.8.3 installer and reinstalled again and everything was working fine again but I really don't like having to lag that much behind on security related patches so a fix or at least an acknowledgement that this is actually a problem would be nice.

Reply

Answer 11

Mordrin Author

Level 1

0 points

Oct 24, 2013 12:06 AM in response to Mordrin

Well...just tried Mavericks. TDM still broken but much more difficult to revert to 10.8.3 as I had problem booting on my 10.8.3 installer USB stick. I had to erase the disk before I could boot on the USB and then perform a time machine restore as part of the installation process.

I guess I'm permanently stuck on 10.8.3 since Apple haven't even acknowledged this problem, I don't have much hope this will ever be fixed 😟

Reply

Answer 12

stanno

Level 1

4 points

Nov 6, 2013 1:57 PM in response to Mordrin

Just wondering whether you have had any luck sorting TDM issue? I have excatly the sampe problem... TDM has worked perfectly for a year or so now... until I updated to Mavericks. Cable is fine... how the **** do I fix this???

Help?

Reply

Answer 13

Mordrin Author

Level 1

0 points

Nov 7, 2013 1:38 AM in response to stanno

No solution I'm afraid. Like I wrote earlier, this hasn't worked since 10.8.4 and the only "workaround" that is working for me was a reinstall of 10.8.3 and not applying any updates.

But you should at least report it to Apple - if more people report the issue there might be a small chance they would actually start looking into the problem. You can report it using the Mac OS X Feedback form: http://www.apple.com/feedback/macosx.html

Reply

Answer 14

stanno

Level 1

4 points

Nov 7, 2013 2:36 PM in response to Mordrin

Hey Mordrin - I re-installed 10.8.5 through time machine backup (down from Mavericks) and everything is working as normal. It's a shame that the updates play havock with everything. I will forward feedback to Apple regarding issue.

Reply