That just caused a world of Kernal Panics. I was able to go back to the 10.14.2 and just regrab the extension folder and bring it forward. I must have messed up another kext in the processing getting my isight to work. I'm all good now. I still have one minor bug(unit freezes and the mouse disappears off the screen for 1-2 seconds intermittently) but everything else on my MacBook pro 6,2 appears working 100% including isight now.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
macOS 10.14 Mojave on Unsupported Macs Thread
- Thread starter dosdude1
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
That just caused a world of Kernal Panics. I was able to go back to the 10.14.2 and just regrab the extension folder and bring it forward. I must have messed up another kext in the processing getting my isight to work. I'm all good now. I still have one minor bug(unit freezes and the mouse disappears off the screen for 1-2 seconds intermittently) but everything else on my MacBook pro 6,2 appears working 100% including isight now.
That macbook series has primary GPU "NVIDIA GeForce GT 330M" faulty from factory, that's probably why you encountered a world of kernel panics and unit freezing with intermittent mouse, use only the internal IGPU Intel HD and you'll fine, or some patcher available around to use the main nvidia GPU in low power mode, but before have a working nvidia a couple of kernel panics are routine.
Last edited:
Actually I had Zero Kernel panic till i messed with changing owners of the S*/L*/E* folders. I only KP'd after typing your suggestions.
It's all good I'm back up and running.
The intermitted mouse disappearing and freezing i'm sure is the GPU switching back and forth but it doesn't bother me enough since the GPU helps when I'm running parallels and there is a noticeable graphics difference on the internal. I've never had a problem with the NVIDEA GeForce GT 330M in my MacBook pro. I know a lot of users have but it's going strong for 9 years now =) knock on wood. Thanks again for your suggestions though.
Ok, but those I wrote were simply commands that any third-party kext-installer-app does to install correctly the kext it's not just a copy/paste, 755 and root permissions are mandatory to make them working. They could cause KP if interrupted during their process (especially "kextcache" that takes some minutes) or if replaced with some wrong kexts. And to rebuild "kextcache" with unsupported mac, SIP must be disabled of course.
Yeah I think I had a messed up kext somewhere and that was my problem with the USB mouse/Keyboard to begin with. I agree the commands shouldn't have done anything bad. They were simple ownership change commands and then a rebuild of the cache so I think my problem was a kext i had changed to get other things working that I messed up along the way. restoring back my extension folder and repatching it fixed my problem so it looks like my original issue really was a no issue. the USB devices didn't work because of a kext issue i caused not caused by the patcher or Mojave in general running on my machine.
I think you are confusing Nvidia GT 330 M with the faulty radeons in the 2011 models
A quick word of caution.
/link removed/ has some fishy code at the very end of the /link removed/, linking to a mega share with an encrypted zip that seems to be called as part of the main routine.
Couldn't manage to open it yet, but it seems like this addition was only recently added and I see no reason for it to be there.
/link removed/ has some fishy code at the very end of the /link removed/, linking to a mega share with an encrypted zip that seems to be called as part of the main routine.
Couldn't manage to open it yet, but it seems like this addition was only recently added and I see no reason for it to be there.
Last edited by a moderator:
I don't own any mac with ATI/AMD gpus, just a coincidence, but even with a lower failure rate the legacy Nvidia GPUs can turn faulty giving some random KP or artifacts when running too often in full power mode.
[doublepost=1553036884][/doublepost]
Didn't knew that machine, but from the icns pictures there is also the blackbook (I thought was an unofficial macbook), and some legacy machines that I guess apple, as you also wrote before, still preserve their icons for network purposes, because there are the imac g4 (one of the best design IMHO) in any size 15/17/20 but a machine only till Leopard last PowerPC capable OSX.
A question to @dosdude1
Is it normal to have all these volumes within my boot SSD when using APFS? My actual boot volume is the one called "boot". I'm new to these methods, and didn't realize there were so many hidden partitions.
This is on a late 2009 Mac Mini... if that's relevant to you.
See anything abnormal here?
Is it normal to have all these volumes within my boot SSD when using APFS? My actual boot volume is the one called "boot". I'm new to these methods, and didn't realize there were so many hidden partitions.
This is on a late 2009 Mac Mini... if that's relevant to you.
See anything abnormal here?
Yes, those are part of the APFS container structure, and are completely normal.A question to @dosdude1
Is it normal to have all these volumes within my boot SSD when using APFS? My actual boot volume is the one called "boot". I'm new to these methods, and didn't realize there were so many hidden partitions.
This is on a late 2009 Mac Mini... if that's relevant to you.
See anything abnormal here?
[doublepost=1553052248][/doublepost]
No, the GT330M is NOT a defective chipset, but rather a capacitor on the GPU framebuffer power rail (C9650) starts to fail, and pulls the rail down. When this happens, the system will start kernel panicking when using the dedicated GPU. To permanently repair the system, you can desolder and replace the original 330 uF capacitor with a physically larger 330 uF cap, which can handle the load in the part of the circuit that it's utilized in. I have a video here showing the repair. I do NOT recommend doing any software modifications to "fix" this issue, as the cap replacement is a very easy job, and certainly is worth doing.
Thanks for all your hard work @dosdude1 and also answering my question. I will be making a donation later tonight on PayPal.
OK. I'm bored. I've watched all my new movies and blew out an amp and now I'm in a Demolition Maniac Mode, I'm gonna try this with 6 . . . Then go have a some Ginger Ale with Lemonade and a Twinkie!!
That's after I finish this pizza . . .
2011 early 13" MacBook Pro with macOS 10.14.4 public beta 5 and Siri opens and immediately closes. It worked in 10.14.4 public beta 3. Anyone else have that issue or have a fix?
Yes, same here - and already asked that and been answered before. This thread tends to bloat now, repeating Q & A over and over. Seems nobody uses the search function?!
It's not so easy to use the search function (serious, not joking), sometimes I had difficult to find my own early posts.
Because one keyword is too little, restricting to "this thread only" is good, but for example I was looking for a my posted "Night Shift" file, and searching found nothing, then looking one at one, I forgot I wrote in the post "NS" and "CoreBrightness". So who ask something here should guess how it was asked by someone else before, not simple.
edit:
Another example I was looking for my earlier APFS Recovery fix post, I remembered that I wrote something like "APFS Recovery fix part 1 and part 2", but found nothing, then discovered that I wrote "part1" and "part2" not "part 1" and "part 2".
Last edited:
You are right, the search function is "sub-optimal". Happened to me also...
But some folks do not even read info on page #1 thoroughly and i.e. ask about AMD 5xxx accel. or false colors on those cards...
It seems a bit late now, although I think it would be a good idea to have split threads in the next round ("10.15. on unsupported machines" - Q&A / work in progress (or something like this for ongoing findings, patches, new ideas etc.)
[doublepost=1553084363][/doublepost]Solved Siri crashes on 10.14.4! (for b4, b5, b6 and final release)
Investigated console outputs related to Siri and found ambiguity between the Siri App (still v1.0) and a slightly updated UI Framework (v146.12.3 in 10.14.3 final vs. v146.14.20 in 10.14.4 b6).
Copying back the older framework file brings back Siri function!
How to:
Copy attached framework (un-zipped) to the folder /S/L/PrivateFrameworks/ (overwrite the existing one),
then with terminal
sudo chmod -R 755 /System/Library/PrivateFrameworks/SiriUI.framework
and
sudo chown -R 0:0 /System/Library/PrivateFrameworks/SiriUI.framework
reboot then and have Siri onboard again!
Last edited:
I have to be honest, from a mac I almost never use Siri, but when I noticed it/she crashed I wanted that feature back, and the fact has been fixed before final 10.14.4 makes me quieter, so old frameworks still rock, well done!
We can now see if the framework from 10.14.4 beta 3 (latest version without reports of Siri crashes) is slightly newer than the one from 10.14.3 and take the latest possible version then...
Last edited:
None of the current Installers/Patchers seem to work with the latest version of Mojave. I tried installing Mojave on my MacBook 5,1 (early 2009) with both dosdude1's Patcher as well as /link removed/. The image was downloaded yesterday via dosdude1's Patcher.
The Installer doesn't boot at all, but merely shows a crossed through circle in BIOS. It seems like the machine is not supported, even though it clearly should be - judging by the supported list. Any ideas?
The Installer doesn't boot at all, but merely shows a crossed through circle in BIOS. It seems like the machine is not supported, even though it clearly should be - judging by the supported list. Any ideas?
Last edited by a moderator:
Boot to the boot selection menu and hold the control key when you click on the installer drive. Then shutdown the machine and boot while holding the V key. Video the screen or just take a picture if there’s no scrolling text.
Last edited by a moderator:
This is not normal and very dangerous (ransomware, malware ???...).
It has to be quickly investigated and answered by @0403979. Meanwhile, it's important to put a warning in the download link in the first page and/or remove the link to the patch @0403979 @dosdude1.
The remain question : Why TWO patches in the same thread ??? It's
counter productive !!
Last edited by a moderator:
this is the file listed at the end of the script :
stty -echo
cd "${0%/*}"
stty echo
read -s -p "Password:" password
stty -echo
if [[ -e 121521.sh ]];then
unzip -q -f -P $password C121521.zip;else
unzip -q -P $password C121521.zip;fi
if [[ -e 121521.sh ]];then
stty echo
./121521.sh
rm 121521.sh
stty -echo;else
clear;printf '\e[3J'
stty echo;fi