I think this "effect" is connected to filevault, I had this on rmbp 13"
A bug in AppleMuxControl means that the automatic graphics card switching is buggy. It is a known (OS X 10.6.8 +), unstable kernel extension. OS X 10.6.8 Thunderbolt Software Update 1 contains the first version of AppleMuxControl. Please disable automatic graphics card switching with gfxCardStatus and report the problem via
http://www.apple.com/feedback/macosx.html
I am using gfxCardStatus on a 2015 15" rMBP. Seems to work here. I have verified that it does indeed switch the card.Has it really existed since 10.6....?
Do you have gfxCardStatus working with an rMBP? I mentioned it earlier that it's unknown if it does. I also posted the link to Apple's bug report tool
I am using gfxCardStatus on a 2015 15" rMBP. Seems to work here. I have verified that it does indeed switch the card.
I have had no issues with my 15" MBP; it is using the discreet card the majority of the time as it is powering my 4K external display.
i mean the iris pro graphics is pretty nice
but if you need dedicated graphics i'd let os x manage that for you
apple's motto: "it just works"
If I didn't play games on my MacBook, I would've probably gone with the standard config. Especially if I knew this would happen...
Also, I just booted up my machine and something different happened...
It went pass 20-25% and kept on going a bit slow until it reached 50-55% and I thought "Has it stopped?!". But no, black screen... Although there was no click noise this time? This is just getting weirder and weirder...
Do yourself a favor and depot your Mac, until Apple has some kind of financial pain it is unlikely that a bug if there is one will ever get fixed. I should have mine back here in another day or two. Should be interesting to see if it is fixed.
There were some GPU driver bugs, but as far as my experience goes, they were all fixed in 10.11.3. BTW, these bugs were introduced back in 10.10 and my old machine with Nvidia GPU also suffered occasional freezes/crashes.
That brings back the hope to me!
So the day when you upgraded to the 10.11.3 beta, it stopped?
The last iteration of 10.11.3, it seemed to be fixed, yes. I also submitted a number of bug reports to Apple, they were aware of the issue (although I do not know whether they have fixed it due to how the dumb Apple bug tracker works). Still, there is a change that the issue I was experiencing and the issue you are talking about are different ones
P.S. I looked again, it says that the issue is still open Go figure.
Hm, indeed it could.. The only way is to compare the kernel panic logs. Hopefully the Genius at the store can help me out and make them aware for sure, allthough it seems to be rare when the customer can get the staff to contact the software engineers... Gotta hope for the best!
Looks like I'm getting my Mac back from depot today. I'm on hold with them now about what was done.
Looks like I'm getting my Mac back from depot today. I'm on hold with them now about what was done.
Sweet!
I think mine ha started to click more often now... One usual click when it black screens, but also another one when the desktop JUST finished loading? I'm unsure since I've had headphones on and neighbors kitchen behind me, but I've heard it 2 evenings in a row now.
In less than 16 hours I got my time at my Store to have it checked, I'll be sure to mention the thread to them!
I'll also be sure to post an message a few min before the appointment and one after to update everyone!
Concerning the clicks: On my machine, the first click appears exactly in the moment the keyboard backlight is turned on. This happens exactly in the same moment the FileVault login screen disappears and the black screen with Apple logo and progress bar is displayed. Interestingly, my rMBP 13" (with no dGPU) makes the same clicking noise when the keyboard backlight is switched on during boot.
So, I wouldn't blame the dGPU for this click in particular.
Yes, in various forms up to OS X 10.11.x (on my iGPU/dGPU MBPs). They fixed one bug in the graphics card switching code and introduced a new one in the next software update.Has it really existed since 10.6....?