-
All replies
-
Helpful answers
-
May 12, 2011 2:20 PM in response to msinanianby tbeseda,msinanian, the monitor was only a few months old. Well within its warranty, and too close to the release for the Thunderbolt interface to not have been tested against.
-
May 12, 2011 2:26 PM in response to tbesedaby msinanian,@tbesda, mine too! (bought it in january 2011, bought the new MBP march 2011). But they refused to do a swap-out (free replacement). just a return.
you did a swap out for free? 24 for 27 at ZERO dollars?
-
May 12, 2011 6:44 PM in response to DanRybby lachness,Went to the Genius bar today with my Macbook Pro 2011 and my 11 month old 24 ACD and demonstrated the flickering/blackout issues for the 2nd time.
Showed the forum posts on this issue. I also discussed the debugging I had done with senior level support staff over the phone and let Martin (the genius) read thru those discussions.
Martin asked me "how would you like Apple to handle this". 10 out of 10 for Martin.
II asked for an Apple Display compatible with the Macbook Pro and was willing to pay the difference. The store manager agreed. I paid the extra $100.00 .
Walked out with a 27" ACD and all is looking good. Transferring the remaining AppleCare onto the 27 ACD.
-
May 13, 2011 2:13 PM in response to DanRybby mamezito,i found the solution for this problem, problem is macbook pro has 2 videocards- the integrated one can't run external display so u need to switch to radeon card in order to use external display, u can try this soft http://codykrieger.com/gfxCardStatus
-
May 13, 2011 2:35 PM in response to mamezitoby njbagger,Unfortunately no. My 24" ACD is still having blackouts and flicker while using gfxCardStatus in "descrete" mode.
Would have been wonderful, if it had done the trick.
-
May 13, 2011 2:39 PM in response to mamezitoby iFrodo,Excuse me, but I doubt you have a MBP 2011 AND a Apple Cinema Display 24", for three reasons:
1st: The MBP switch automatically to discrete graphic card (the radeon) when an external display is connected
2nd: The problem described here is not that the external display doesn't run, but that it flicker regularly, so there is an image but it's unstable.
3nd: The solution (use GfxCardStatus to set "Discrete only" you give doesn't solve the problem with ACD 24" and MBP 2011.
If you had a MBP 2011 AND a ACD 24", you would have seen by yourself that not only your "solution" doesn't work, but also that the problem is not about the external display not working, but instead that the external display works but is unstable with blackout flickers regularly.
-
May 16, 2011 12:36 PM in response to DanRybby iFrodo,I've got a 13" MBP 2011 for work, and guess what? No issue at all!
Also, as you can read on this very forum, iMac 2011 also have issues with 24" LED Cinema Display.
What is in common with iMac and MBP 15" and 17"? They both use AMD GPU for external display, while 13" MBP 2011 use Intel HD Graphics 3000 for external display.
So it really seems to be a problem with AMD GPUs, and what is making this theory even more credible, is that my father have a assembled PC (i.e: custom made) with an AMD graphic card, and it suffers similar symptoms with his HDTV.
It seems that AMD GPUs are not coping very well with some displays. So the real cause of the issue here seems to be GPU related, maybe it's just a GPU driver issue, I don't know, but it clearly has something to do with the GPU. Why would a 13" MBP, that is using the same Thunderbolt chip as 15" and 17", have no issue whatsoever, while Macs and PC having similar issue I've seen, are all using AMD GPUs.
-
May 16, 2011 1:00 PM in response to iFrodoby El Presidente,Interesting. I've always found it puzzling how Apple won't give you the option of driving external displays with the integrated graphics. I understand plugging the laptop to an external means you're likely gonna be doing heavy duty work but still there are times when you don't need the GPU power (regular surfing for example)
I'm still waiting on my exntension cable so i can promptly email customer relations again and tell them what i already predicted...external cable won't solve the problem.
-
May 16, 2011 1:03 PM in response to iFrodoby msinanian,I totally agree with iFrodo: given all the facts, this must be an AMD GPU issue. GPU's tend to be a tender spot for new MBP releases. Some models back, there were huge issues with nVidia GPUs, prompting recalls, etc... So it wouldn't be the first time, but it's just odd that the bug is "lack of compability with certain monitors." Why certain monitors? We'll never know...
-
May 16, 2011 1:17 PM in response to msinanianby yvesfrombuc,I called apple care last week (Apple Europe support). They sent me two data capture programs, i had to run these programs when the pb occurs (flickering and black screen). So i did it and sent them the reports...they made engineers request with that stuff. I have to wait a few days, and if they don't find a solution, genius bar guy said i will be put in relation with the commercial service, as i said i want a new screen. So wait and see....
-
May 16, 2011 3:15 PM in response to iFrodoby Kyle O'Bannon,Again, my early 2011 MacBook Pro 13-inch is very much affected and it is sans AMD GPU. I've exchanged my 13-inch two times now and all three have experienced the same black out and flickering issues. My 24-inch ACD continues to work flawlessly with my 2009 MacBook Pro, however. If your 13-inch works without fault, consider yourself lucky.
-
May 16, 2011 11:02 PM in response to Kyle O'Bannonby iFrodo,Indeed, yesterday my work 13" MacBook Pro with the 24" LED Cinema Display have worked fine for about an hour or two, and then the display started flickering too.
So I sadly have to confirm that it affects any Thunderbolt equipped Mac, being MBP or new iMacs. Then it seems not related at all with AMD GPUs, but really seems to be a very specific incompatibility with the screen itself... The defect being on the Mac or screen size, remains to be determine.
We've read numerous reports that 27" version works just fine, and the 27" have a full Mini DP connector, with audio, while 24" doesn't have the audio pin. It then may be related to that, maybe Thunderbolt doesn't like being connected to a not fully implemented mini DP connector, this could explain why El Presidente was giving a mini DP extension cable to try, I think Apple is trying to verify this kind of cause by doing that.
That would be interesting to see the result of that possible "fix"... El Presidente, don't forget to report to us as soon as you get your extension cable
-
May 16, 2011 11:23 PM in response to DanRybby jacblinde,You are all wrong! remember that the 24" ACD issue is not new and that a sister discussion started in 2009. In my own case I've experienced problems connected to a 15" late 2009, a new MBP 13" i7, and now a new 15" i7. Failure is just worse with the thunderbolt connector. It's a design or manufacturing flaw of the ACD.
I wonder if some series have not been made with defective (cheap ?) components.
-
May 17, 2011 2:03 PM in response to DanRybby Dirki,Impressions from Germany:
For 3 weeks i got my new 15" MBP Thunderbolt. I´ve a 24" Cinema Display which worked well with my 2010 MBP.
With the new MBP i got the flashes and freezes, no chance to work normally with the combination.
My 24" Cinema Display had some grey marks and i´ve AppleCare, so i sent it to a Apple-Dealer to repaired it.
I told him that the new MBP doesn´t work with the 24" and a lot of people have problems with it.
In that time, the new Firmware-Update for the MBP was out, so i install it, but couldnt test it without the Display.
Last Friday, the repaired 24" Display arrived, they changed the panel.
On the repair log they write, that Thunderbolt is incompatibel to the 24" Cinema Display and Apple is working on a solution.
BUT:
Since last Friday the Display works fine with my new MBP, no flash or freeze since 40 hours.
-
May 17, 2011 10:15 PM in response to Dirkiby iFrodo,@Dirki
So if I understand corerctly, they changed only the panel, and not the logic board?
I got mine fixed, and they changed the logic board only, not the panel...
This would mean that it's an incompatibility with the panel. I hope Apple can find a software fix to that, otherwise that would cost them a lot if they have to replace every single panels of people affected...
I'd suggest you to report it to Apple if you confirm it to still working fine in a full week usage. That could help them find a fix.