Currently Being ModeratedJan 4, 2013 4:39 AM (in response to MetamorphX)
I have the same problem as well. Only just realised that all my problems i have been having for the last few months have been cause by this.
100% CPU usage, No audio over displayport, massive heat output from imac
I thought it was my PC and have bought a new power supply and 7970.
Currently Being ModeratedJan 16, 2013 9:52 PM (in response to zead29)
In 10.8.2 it is working? In this thread, a guy said that it wasn't.
Currently Being ModeratedMar 29, 2013 11:05 AM (in response to geoffreyfrommatthews)
Giving this thread a bump. I went through a long period where the problem could be fixed whenever it cropped up by restarting in Safe Boot mode, then restarting again. Had a good long run of success with that, but it ended today when I allowed Software Update to do it's thing -- security update, Java update, HP Printer update, iTunes update. BIG mistake!
No amount of reboot/unplug/replug displayport cable appears to do the trick. I saw the referenced thread that suggests Mt. Lion does NOT solve the problem, but with a single recent data point and at least one older that said Mt. Lion DID solve it, I'm left wondering. Anyone else see this problem resolved with Mt. Lion?
Anyone know how to revert the OS to 10.6.7 without a Time Machine backup?
Currently Being ModeratedMar 29, 2013 2:45 PM (in response to geoffreyfrommatthews)
FOr mr mt lion is a work around at best.
I Can now use target display mode with out the iMac running at 100% amd over heating. I can also change the brightness but it resets every time I switch between computers.
MY solution is sell the iMac and buy a 27" standalone monitor with multiple inputs and a mac mini.
BUt the way apple is going I may just drop the mac altogether. The better experience of osx is being ruined by arrogance on apples part.
Currently Being ModeratedMar 29, 2013 3:44 PM (in response to BT Productions)
Brightness controls don't work. It never fails to enter Target Displaly mode when connected (via my Monoprice displayport-to-diplayport cable) to my MBPr's Thunderbolt port. It does NOT enter Target Display mode if connected (via the same cable) to my Thunderbolt Cinema Display's TB port, but I assume that's expected.
Oddly, Brightness controls are working after yet another Shut Down / Safe Boot / Restart cycle. The only difference between the latest cycle and the previous couple attempts: I accidentally left the displayport cable connected between iMac and MBPr-attached TB Cinema Display, and tried to put it into Target Display mode in while in Safe Boot, then again after restart. When the latter failed, I realized the cable was still plugged into the Cinema Display. Plugged it directly into the second TB port on the MacBook, put it in Target Display, and found the brightness controls are working again.
I've been running this setup long enough to know that the brightness controls won't work if, when I switch to Target Display mode, the iMac's screen doesn't automatically (and immediately) adjust itself to something dimmer than "blindingly bright."
Currently Being ModeratedMar 29, 2013 3:34 PM (in response to merve0o0)
@merve0o0: Are you saying that your displayport iMac 27" running Mountain Lion always responds to the brightness control keys when you switch it to Target Display mode? And if so, which rev (10.8.__) are you on?
Currently Being ModeratedMar 29, 2013 3:39 PM (in response to geoffreyfrommatthews)
Yeah, I've been waiting to update to ML because I was worried about Final Cut Pro 7 not working. Now I've gotten into a good flow with Premiere. And I actually need to update for some software. I've bought it and have it running on my MBP. So this was the one thing still holding me back from updating to ML on the iMac. So it sounds like it's working ok then, after your update? I don't think I've done a system update on this iMac since I got it in 2010. I know that's not safe since I need the security patches, but I use this feature a lot.
Currently Being ModeratedMar 29, 2013 3:51 PM (in response to BT Productions)
My iMac is still on OS 10.6.8, but did run the Software Update this morning. No idea why the Brightness controls stopped working after the Update earlier in the day, nor why cycling through several iterations of the Shut Down / Safe Boot / Restart / Target Display steps failed to get them working, nor why they've started working again after one more cycle this afternoon.
Hope you'll post your experiences here if you do migrate your iMac to ML.
Currently Being ModeratedMar 29, 2013 4:06 PM (in response to geoffreyfrommatthews)
Ah, ok. I was thinking you were on ML. Yeah, I'm on 10.6.7 and it works perfectly. 10.6.8 is when the feature broke (the brightness controls stopped working).
I had it confirmed by someone that the feature was working correctly in the most up to date (that was January) version of Mountain Lion.
Here's the thread. Start with my post at #15.
So I would say go ahead and update to ML and you'll probably be set. Now that I'm thinking about it again, I'll probably do mine next week. If so, I'll post back. If you update first, let me know how it goes.
Currently Being ModeratedMar 29, 2013 4:11 PM (in response to BT Productions)
Oh, and btw, I recommend disconnecting any monitor (whether it's an input or output) when doing system/ OS updates. I had a terrible experience with my MBP a few years back when I did a software update and I think the cause was that I had it hooked up to a monitor at the time. It took a few months until the next update to fix it. I don't remember specifics, but it had to do with the display not turning off or turning on or something.
This is all why I thoroughly research any OS updates, and probably led to me not updating other software or mobile apps before I can confirm that it works properly.
Currently Being ModeratedMar 29, 2013 4:23 PM (in response to geoffreyfrommatthews)
AFAIK, they stopped making install disks. So either an install from the App Store, or a download from the App Store that is put onto a bootable USB drive (not sure exactly how/ if that works) are the only ways. I would really, really hope that they didn't screw it up again that fast. But I guess it is worth checking to be sure. lol.