Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
  • Like
Reactions: TimothyR734
I have an MBP6,2 with GPU/capacitor issues that's similar to mani girafe's random reboot...

And here's a thread about it...

https://forums.macrumors.com/threads/gpu-kernel-panic-in-mid-2010-whats-the-best-fix.1890097/
Sorry but those are two different things. GPU capacitor problem is solvable by replacing the capacitor, GPU is fine . I think @dosdude1 has a video in youtube addressing just that.

Nevertheless you may be right attending to the symptoms ( kernel panic)
 
  • Like
Reactions: TimothyR734
I've gotten Mojave up and running on my MacPro 3,1 with a GTX 660ti, and everything seems good. Thanks to @dosdude1 for your work for the community. It's greatly appreciated!
if that GTX 660 Ti is based on the GK106, it will artifact randomly and make the display unusable. It's been an issue with GTX 650ti to 660ti since high sierra and later
[doublepost=1564582033][/doublepost]
Hi all

I have Macbook pro 6,2 , used the Dosdude patcher mojave 10.14.5 , apply all process , works fine but sometimes the mac reboot randomly

I would like upgrade 10.14.6 by apple update , but when the first time i apply 10.14.6 update , i restart on my usb installer dosdude mojave , apply post install etc , reboot again but the screen display me the picture


impossible to boot ??

i reinstall with the 10.14.5 dosdude installer ? no probleme except some random reboot

thanks for help ?

hey can you please do me a favor? Can you install gfxcardstatus, force the intel HD active, open safari and see if there's any cursor lag as you hover over links? My 6,2 has been bugged since .5 release even in a clean install. It works fine on the GT 330M though
 
  • Like
Reactions: TimothyR734
Not true. MacBook Pro 6,2 is the mid 2010 15" model, the one with GPU problems is the 2011 (8,2 ?) one. I'd check thermal problems first. Maybe it's time to put some new thermal grease in that processor?

No he is 100% correct, the 2010 15" models suffer badly from random reboots because of a GPU issue. The 2011's suffer badly from white screen issues preventing booting into the OS. Completely different issues for completely different problems.

The 2010's are mitigated with the Mid2010 GPU patch : https://github.com/julian-poidevin/MBPMid2010_GPUFix/blob/master/FAQ.md

The 2011's are mitigated by disabling the Discrete GPU and only using the built in Intel 3000 : https://forums.macrumors.com/thread...ntel-integrated-gpu-efi-variable-fix.2037591/
 
  • Like
Reactions: TimothyR734
No he is 100% correct, the 2010 15" models suffer badly from random reboots because of a GPU issue. The 2011's suffer badly from white screen issues preventing booting into the OS. Completely different issues for completely different problems.

The 2010's are mitigated with the Mid2010 GPU patch : https://github.com/julian-poidevin/MBPMid2010_GPUFix/blob/master/FAQ.md

The 2011's are mitigated by disabling the Discrete GPU and only using the built in Intel 3000 : https://forums.macrumors.com/thread...ntel-integrated-gpu-efi-variable-fix.2037591/
Nope, that is not correct. GT330M NEVER fails in the 2010 15" and 17" machines, it's just a bad capacitor on the GPU frambuffer power rail that causes random kernel panics. I have a video here explaining the whole issue and performing the repair. That software solution should not be used under any circumstances, the system should be repaired properly. Now, you ARE correct about the 2011 machines, they have a defective AMD Radeon HD 6xxx series GPU, which AMD irresponsibly never actually fixed. Therefore, those systems CAN'T be properly repaired. However, the best solution for them is to permanently disable the dedicated GPU, using my custom gMux IC firmware. The "EFI variable fix" you've linked is nothing more than the reliance of an NVRAM variable to keep the dGPU disabled, which can get reset VERY easily, making that solution MUCH worse than a permanent dGPU disable either via hardware or custom gMux IC firmware.
 
Hi,

I have a last question concerning APFS. I'm still runing High Sierra on HFS+ and planning to install Mojave on my xp941, which is coming soon.

Should I apply the APFS Rom Patcher before or after the installation of Mojave?

Thanks,

frenchieisverige
 
  • Like
Reactions: TimothyR734
Nope, that is not correct. GT330M NEVER fails in the 2010 15" and 17" machines, it's just a bad capacitor on the GPU frambuffer power rail that causes random kernel panics. I have a video here explaining the whole issue and performing the repair. That software solution should not be used under any circumstances, the system should be repaired properly. Now, you ARE correct about the 2011 machines, they have a defective AMD Radeon HD 6xxx series GPU, which AMD irresponsibly never actually fixed. Therefore, those systems CAN'T be properly repaired. However, the best solution for them is to permanently disable the dedicated GPU, using my custom gMux IC firmware. The "EFI variable fix" you've linked is nothing more than the reliance of an NVRAM variable to keep the dGPU disabled, which can get reset VERY easily, making that solution MUCH worse than a permanent dGPU disable either via hardware or custom gMux IC firmware.

Not trying to start a fight, but your post is a bit pedantic. From the users perspective, there definitely IS a problem with the video card. When you do anything even slightly GPU intensive it causes a KP and reboots. I never said the software was a fix, I said it's a mitigation. Of course a hardware fix is always preferable, but that does NOT mean a software fix should never be used, nor does it mean it cannot be a valid use case. We have hundreds of these machines that were worthless before the fix and rock solid afterwards. Not sure where your hatred of the software solution comes from, but in mine (and hundreds / thousands of others), it's misplaced.

Likewise the 2011's are rock solid once the AMD video card is disabled in the EFI. While I agree it's fairly easy to clear the variable, it's also trivially easy to put it back, a script makes it even more so. Since these machines have powerful i7 processors and can take up to 16GB of ram, there are thousands of users willing to take the chance on a possibility of an issue that is easily remedied at any point with 30 seconds of typing at a shell. Again, I agree that a hardware fix is preferred but it's just not always feasible, fiscally or otherwise.
 
Nope, that is not correct. GT330M NEVER fails in the 2010 15" and 17" machines, it's just a bad capacitor on the GPU frambuffer power rail that causes random kernel panics. I have a video here explaining the whole issue and performing the repair. That software solution should not be used under any circumstances, the system should be repaired properly. Now, you ARE correct about the 2011 machines, they have a defective AMD Radeon HD 6xxx series GPU, which AMD irresponsibly never actually fixed. Therefore, those systems CAN'T be properly repaired. However, the best solution for them is to permanently disable the dedicated GPU, using my custom gMux IC firmware. The "EFI variable fix" you've linked is nothing more than the reliance of an NVRAM variable to keep the dGPU disabled, which can get reset VERY easily, making that solution MUCH worse than a permanent dGPU disable either via hardware or custom gMux IC firmware.

I think that's something wrong.
i also suffer of mouse lag (only when using safari) and random KP (with latests dosdude1 patcher I didn't notice yet), but I found those bugs only when running Mojave.
All fine on High Sierra, so I think that's nothing wrong with the GPU.
 
  • Like
Reactions: TimothyR734
I think that's something wrong.
i also suffer of mouse lag (only when using safari) and random KP (with latests dosdude1 patcher I didn't notice yet), but I found those bugs only when running Mojave.
All fine on High Sierra, so I think that's nothing wrong with the GPU.

The mouse lag is fine on 10.14.3(the first january release) and earlier. It doesn't happen on the 330M under any versions though - just the intel HD arrandale. When i get a bit more free time, ill mess around with it some more as no one here is willing to lend a hand despite countless requests. It's not my config since it happens even on a clean install with nothing installed.

As for the capacitor issue, i rather use a software solution that keeps things stable and usable vs a kernel panicking mess/paper weight. The hardware fix is of course better but not everyone is knowledgeable in performing that fix (or have the tools for it) Since the machine is almost 10 years old, it's not even worth paying someone to do it. As the other guy said, not sure why the hate for the software fix. Besides, isn't this entire thread a software fix (patching OS to run unsupported OS) vs a hardware fix (buying a new one)

Anyways I've been using gfxcardstatus + that patch (along with a whole bunch of other patches to enable handoff/continuity) and my machine has been stable since
 
How do we install supplemental update to non-APFS system?
The same question have I too.
My MBP is not shutting down since 14.6 correctly:
dosdude help us! ;)
[doublepost=1564691026][/doublepost]
Hmm...
That is not what is written on dosdude's website. I have a cMP 3,1 from 2008 which does not support APFS natively. Thus, I'll need to use his boot patch. The downside of this patch is that it removes the possibility to boot on recovery partition.
Am I missing something?
This is not my experience, the patcher always updated the recovery partition.
Just try it.
 
Just updated my HackPro5,1 from Mojave 10.14.5 to 10.14.6. Process was simple thanks to DosDude's patcher! Completed the upgrade from the AppStore and before booting into Mojave 10.14.6 for the first time, I booted Mojave Installer USB patched with DosDude 1.33 and applied just the Legacy Video Patch (that's all I needed - no model selection and no other patches since I'm using CLOVER to manage SIP, I specify -no_compat_check CLOVER boot option and I'm using USBInjectAll.kext / custom SSDT-UIAC).

My system specs are:
  • Motherboard: Biostar TH55HD
  • CPU: Xeon X3450 (Overclocked)
  • Memory: 16GB DDR3
  • MacOS: Mojave 10.14.6 APFS
  • CLOVER R5018
 

On non-APFS system we are getting this;

Screen Shot 2019-08-02 at 00.31.38.png
 
That is normal for HFS systems I am trying to getting to my desktop after installing the supplemental update but no luck

Even on APFS volumes, the supplemental update is problematic. On my MacPro 3,1 with 10.14.6, when applying the supplemental update from the software update preference panel, the update hangs at the 16 minutes remaining mark after the reboot. This is despite reapplying the patches at the reboot.

I just noticed that downloading the 10.14.6 full installer from a supported machine gets 14.6.03 rather than the previous 14.6.02 so hopefully this one has the supplemental update folded in. Apple has been known to do that for supplemental updates but not for security updates.
 
  • Like
Reactions: TimothyR734
Is the recovery partition supposed to work for native APFS systems? I can't see any mention of it, only that it's not working for non-APFS models. I did an otherwise successfull clean install on a MacBookPro8,1 (early 2011) and just gets the No-sign when holding cmd-R. Tried the "fix" here from @jackluke but it didn't help.
 
  • Like
Reactions: TimothyR734
Which system type are you using?
APFS after 30 mins it finally went to the login screen then another 5 min wait after I entered my password then the screen went white so now back to reinstalling 10.14.6 final I wouldn't recommend installing this update
[doublepost=1564697367][/doublepost]
Is the recovery partition supposed to work for native APFS systems? I can't see any mention of it, only that it's not working for non-APFS models. I did an otherwise successfull clean install on a MacBookPro8,1 (early 2011) and just gets the No-sign when holding cmd-R. Tried the "fix" here from @jackluke but it didn't help.
If you are APFS try running the script in the terminal
 

Attachments

  • apfsrecoveryfix.command.zip
    1.2 KB · Views: 137
I think that update bricked my MacBook 5,2 I can't reinstall 10.14.6 final with the patcher get an error, hold my option button can see my hdd for selection but disk utility won't load to check for errors I'm stumped
and pissed :(
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.