Owners of early 2011 15-inch and 17-inch MacBook Pros are reporting issues with the AMD GPUs in their computers. In some cases, the component completely fails, requiring an expensive replacement of the logic board.
The problem, as highlighted by multiple threads on Apple’s Support Communities forum, first
as a graphical glitch — or, in more serious cases, complete system lockup — when an affected MacBook Pro switches from the integrated Intel graphics chip to the discrete AMD graphics processing unit, or GPU. Reports of the issue first cropped up in February, but have become more frequent over the past month.
Apple introduced an automatic graphics switching system back in 2010, which automatically decides which graphics chip to use, the integrated chip, or the discrete chip, depending on the graphics task the user is working on.
Affected machines display discoloration, banding, and image distortion as the most common symptoms, however, users also report that their computers suddenly freeze without any graphical warning signs. Rebooting is reportedly not a remedy, and some users are attempting to remedy the problem by forcing the MacBook Pro to use only the integrated chips. These attempts have been met with only modest success.
Apple Support Communities forum user “saramwrap” has compiled data showing that the majority of affected machines are early-2011 MacBook pros equipped with the AMD Radeon 6750M GPU. However, users whose computers are equipped with Radeon 6490M, 6750M, and 6970M GPUs are also experiencing the problem.
Apple has not yet addressed the issue, and many users report the only repair option given to users without AppleCare coverage is a pricey $500 logic board replacement.
I have a early-2011 MacBook Pro equipped with a Radeon 6490M, and have so far not experienced any of the issues mentioned above. How about you? Have you experienced any GPU issues with your early-2011 MacBook Pro? Please let us know in the comments section below.
Share this:
Featured Stories4s几近淘汰，未收录
高度值其实就只有两种类型，一个是Default一个是Number
①以下几种键盘类型几乎一样，键盘高度也是一样的
UIKeyboardTypeAlphabet
UIKeyboardTypeASCIICapable
UIKeyboardTypeDefault
UIKeyboardTypeEmailAddress
UIKeyboardTypeNamePhonePad
UIKeyboardTypeNumbersAndPunctuation（数字和标点符号）
UIKeyboardTypeTwitter
UIKeyboardTypeURL
UIKeyboardTypeWebSearch
②以下几种键盘为数字类型的键盘，键盘高度也是一样的
UIKeyboardTypeDecimalPad（带小数点的数字键盘）
UIKeyboardTypeNumberPad（纯数字键盘）
UIKeyboardTypePhonePad（带*+#,;的数字键盘）
本文已收录于以下专栏：
相关文章推荐
转自.cn/s/blog_17ffk.html
- (void)viewDidLoad
    [sup...
最近做的项目中，有一个类似微博中的评论转发功能，屏幕底端有一个输入框用textView来做，当textView成为第一响应者的时候它的Y值随着键盘高度的改变而改变，保证textView紧贴着键盘，但又...
ios8允许第三方键盘使用后，键盘的高度经常不准确，怎么破，不废话，上代码。#import &ViewController.h&@interface ViewController ()@propert...
IOS8.0之后可以安装第三方键盘，如搜狗输入法之类的。
但是使用以前的方法获得的高度都为0.
可以在UIKeyboardDidChangeFrameNotification的通知中实现,这里需要...
1、在viewDidLoad方法中加入监测键盘的通知。
- (void)viewDidLoad {
    [super
viewDidLoad];
    // Do any a...
//在遇到有输入的情况下。由于现在键盘的高度是动态变化的。中文输入与英文输入时高度不同。所以输入框的位置也要做出相应的变化
#pragma mark - keyboardHight
-(void)vi...
iOS怎么获取并移除沙盒中Documents文件夹下的所有文件
最近在项目中，使用TextInput组件的时候，发现键盘弹出的时候，遮盖了表单。咨询了下做iOS的同学，他们的处理是计算键盘的高度和当前输入域的位置，将界面向上移动一段距离。那在ReactNative...
（网上摘抄并进行总结）
首先说明下键盘显示消息和隐藏消息分别为：UIKeyboardWillShowNotification、UIKeyboardWillHideNotification；这个两...
在iOS 5中，键盘的高度是会变化的，比如切换到中文输入法时会在键盘上方多出一层候选字区域，如下图：
而在英文输入法下是没有文字候选区域的。
因此在用户输入场景下，布局的美观和可用性可能受...
他的最新文章
讲师：姜飞俊
您举报文章：
举报原因：
原文地址：
原因补充：
(最多只允许输入30个字)April 3, 2008
Hey! This article is pretty old.
which includes much better information.
The introduction of the brand-new
the last few days has been great! It was worried it would take a while for it to catch on, but the last few days there have been about 150 posts in lots of great topics.
One of those great topics was John Steven's background challenge:
I'm standing before a challenge and because to celebrate this new forum, I like to ask you to inspire me on this issue. We need a background 100% wide but what goes into a different pattern on 50% of the screen. The idea of making background image that is for example 2500px wide and repeat-y is not what I'm looking for.
My first thought was to create 2 divs, a leftHalf, and a rightHalf:
#leftHalf {
background: url(images/bg-1.jpg);
width: 50%;
height: 100%;
#rightHalf {
background: url(images/bg-2.jpg);
width: 50%;
height: 100%;
This works, but it has one "small" (literally) problem. When the browser window is at a width of an odd number of pixels, there is no even 50% split of that number and you get a tiny stripe of white down the middle in between the two divs.
John himself suggested the perfect tweak to this solution, which solves that. Instead of a leftHalf, just apply that background image to the entire body element. This solves the white stripe problem and uses less markup as well!
(yes, the left half's pattern doesn't line up quite right, but it's the theory here that counts!)
Share this:
icon-anchoricon-closeicon-emailicon-linkicon-logo-staricon-menuicon-star