![mid 2010 macbook pro gpu reflow mid 2010 macbook pro gpu reflow](https://www.ursecta.com/wp-content/uploads/2019/03/IMG_3589.png)
Mid 2010 macbook pro gpu reflow update#
My apologies for the super long wall of text, and if this is in the wrong area, just trying to recycle and reuse all that I've got! Many thanks for any suggestions!ĮTA: I did make sure to update EVERYTHING post-Install. I do have the Vostro, but the keyboard is HORRIBLE to type on, and the screen resolution on the 2010 MBP is far more crisp (the Manjaro desktop background looked fantastic on it), so that's why I'd rather not use the Dell if I don't have to. Given the fact that I was at the end of the macOS road for the machine ended with High Sierra, my plan was to move that machine to Linux to get a few more years out of it. My main reason for doing is that I'm just trying to hold off on buying a new laptop for a while longer (maybe after nearly 11 years, it's time) as my 2011 was doing just fine for everything I used it for up until the GPU failure. The Dell also only has the integrated Intel HD Graphics 3000, with no discreet GPU to speak of.Īgain, I tried the original 4GB of 1066MHz RAM thinking the memory controller just didn't know how deal with unsupported module speeds, but that wasn't the case.
![mid 2010 macbook pro gpu reflow mid 2010 macbook pro gpu reflow](https://www.jeffgeerling.com/sites/default/files/images/samsung-850-ssd-in-macbook-pro-2011-sata.jpg)
However, the Dell, with a similar 1600MHz, 4GB module and an SSD, is far snappier, and I have no slowdowns or hiccups of any kind. Now, this was the mobile iteration of Sandy Bridge (which many of us stuck with our SB desktop chips for YEARS, I know I ran my 2600K until just last year) so I know IPC improvements were massive, and that 2.10GHz on SB is not the same as 2.10GHz the previous gen chip.
Mid 2010 macbook pro gpu reflow driver#
I'm wondering if the issue is an underlying Apple hardware driver issue I have a Dell Vostro 3550, with an i3-2310M, which although is a year newer than the i5-520M, and has double the BUS speed, and slightly higher memory bandwidth, it's severely limited in top clock speed, at a mere 2.10GHz. I always read while researching that many users only experienced slow browsers on the first start, after which the browser would be have normally for the duration of the session that the machine was on. I read previous posts about removing TimeShift, and that made no difference. Everything else seems fairly snappy, but it just hangs up on the browser. Switched to Mint (Uma) and repeated the same process. Running top didn't show anything interesting, even during the lock-up phases. I've always been a Mint fan, but decided to try Manjaro first (which is equally nice, IMO), and noticed the same issue of the computer grinding to a complete halt when attempting to open the browser. I will note that I tried with the original 2x2GB modules as well, and the results were the same. I did put in the original 4GB, 1600MHz module from the 2011, and while Ark says the 520M was rated up to 1066MHz, the issue I'm experiencing doesn't seem to related to the increase memory frequency. I remembered I had my 2010 MBP, with the i5-520M, and a GeForce GT 330M all it needed was an SSD, and the old RAM module from the 2011 (I'd happily give it the 16GB I put in the 2011, but the 520M can only recognize up to 8GB). Sourcing a 2012 board as a drop in replacement was another option, but ultimately not cost-effective in the grand scheme. Those who had their dGPUs replaced under Apple's extended repair program ultimately encountered the same issue some time later. I used to do board repair, and could easily get a replacement chip and take on a BGA chip replacement, but I don't feel that's worth it either given the fact that any NOS/used chip is likely doomed to fail the same way. With the recent demise of my 2011 MacBook Pro (the AMD gpu issue finally got me after over a decade of faithful service), I decided that attempting to flash the MUX (using DOSDUDE1's method), or attempting to disable the dGPU within the Recovery OS and relying on the iGPU for a sluggish experience wasn't going to be the way forward.