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.
For those staying with Mojave (macOS 10.14) and want to dismiss software update notification, this can be hidden using software update tool in terminal.

Open terminal and type:
Code:
sudo softwareupdate --ignore "macOS Catalina"

EDIT: Noticed it does not clear notification badge. This seems to be persistent.
 
Last edited:
  • Like
Reactions: TimothyR734
So I ran the APFS ROM patcher on my late 2009 mini 3,1 2.53 Ghz, MX25L3205D chip and it was successful, it took 3 minutes to dump the existing ROM and 10 minutes to write the patched one.

Once done I rebooted and the Mac wouldn't reboot, it stayed idle with its LED on, I waited about 5 minutes then I turned it off using the power button. I turned it on again and it booted fine.

I can't test if it boots APFS yet but soon I'll install Catalina. Thanks to all who helped, this is a fantastic forum that I've been following for many years, I had an account around 2005 but I don't remember the name nor the email address I used.

I've been using almost only Linux for several years now and this mini is my last Mac that isn't obsolete or broken. Macs were my first love though so I still like to see how it is going with them!
 
  • Like
Reactions: Yiorlis59
Open terminal and type:
Code:
sudo softwareupdate --ignore "macOS Catalina"

EDIT: Noticed it does not clear notification badge. This seems to be persistent.
Just finish with:
Code:
sudo softwareupdate --list
It will do a re-scan. For me it now proposes to install Safari 13.0.2 even in System Settings > Software-update
 
hello there... (meme potential ;))

I saw that there is another supplemental update available, so my question is:
I have MacBook pro 13' late 2011, is it safe to update and what to expect?

also with Catalina available now, is it any good or better to stick with Mojave?

thanks:)
 
Hi all,

Same issue here
Does not work for me either in MBP5.3 on Mojave (18G103)

Code:
macbook-pro:~ UserName$ sudo softwareupdate --ignore "macOS Catalina"
Ignored updates:
(
    "macOS Catalina"
)
macbook-pro:~ UserName$ sudo softwareupdate --list
Software Update Tool

Finding available software
No new software available.
macbook-pro:~ UserName$

Cannot get rid of the red 1 from the sys. pref icon in Dock.
Yet Software Update tells me that the sytem is up to date.
 
@dosdude1,

would that be possible at some point to run Mojave on MBP Late 2011 (MacBookPro8,2) with amd graphics enabled? my chip isn't dead yet because i haven't used that machine so much and it would be nice to have that feature.
 
Hi all,

Same issue here
Does not work for me either in MBP5.3 on Mojave (18G103)

Code:
macbook-pro:~ UserName$ sudo softwareupdate --ignore "macOS Catalina"
Ignored updates:
(
    "macOS Catalina"
)
macbook-pro:~ UserName$ sudo softwareupdate --list
Software Update Tool

Finding available software
No new software available.
macbook-pro:~ UserName$

Cannot get rid of the red 1 from the sys. pref icon in Dock.
Yet Software Update tells me that the sytem is up to date.


FIXED MY ISSUE TEMPORARILY!

I managed to get rid of the red 1 from the system preferences in the Dock, from the Software Update in system preferences and also the notification in the Apple menu.
With these 2 following lignes of code in Terminal:
Code:
sudo defaults delete /Library/Preferences/com.apple.SoftwareUpdate.plist LastRecommendedMajorOSBundleIdentifier

defaults write com.apple.systempreferences AttentionPrefBundleIDs 0

And I needed to relaunch the Dock with:
Code:
killall Dock

It works as long as I do not run an update search with Software Update of System Preferences even though I have run (sudo softwareupdate - ignore "macOS Catalina" and sudo softwareupdate --list) before.
 
Last edited:
would that be possible at some point to run Mojave on MBP Late 2011 (MacBookPro8,2) with amd graphics enabled? my chip isn't dead yet because i haven't used that machine so much and it would be nice to have that feature.
The first post and the patcher tool page both indicate that this is unlikely. They recommend disabling the AMD GPU so that only the Intel GPU is used for acceleration (but this causes problems with sleep mode and brightness control). There's a software only solution:
1) http://dosdude1.com/gpudisable/

and a couple hardware solutions (oldest to newest):
2) https://forums.macrumors.com/thread...ook-pro-dedicated-gpu-gmux-ic-bypass.2134019/
3) fix brightness: https://computeco.de/DyingLight.html
4) https://computeco.de/MuxHat.html

and a firmware solution (requires flashing with flashing hardware):
5) https://computeco.de/2019-04-03_1.html
6) https://computeco.de/Demux.html

The above solutions seem to have required a lot of effort to create. If creating an AMD acceleration solution was easier then that would have been done instead. Actually, that conclusion does not follow because those mux bypass solutions were created to solve a different problem : where the AMD GPU has physically failed and it won't work with any OS. The conclusion is probably still true though : the problem to be solved with Mojave is just a driver problem but creating a working driver could take months - probably more effort than creating the mux bypass solutions.
 
  • Like
Reactions: AlexyFoxy
@dosdude1,

would that be possible at some point to run Mojave on MBP Late 2011 (MacBookPro8,2) with amd graphics enabled? my chip isn't dead yet because i haven't used that machine so much and it would be nice to have that feature.

From your perspective it should be completely irrelevant as your AMD chip is inherently faulty. Just use it and let it die on High Sierra. It should not take very long.
 
From your perspective it should be completely irrelevant as your AMD chip is inherently faulty. Just use it and let it die on High Sierra. It should not take very long.
I've got a MacBook Pro early 2011 i7 2.2 (AMD) and still works without any problem and I have given it an extensive use
 
Just wanted to share this fix for some sound and screen brightness problems. I successfully used dosdude's macos Mojave Patcher a few months ago to install 10.14.5 on a 2nd-hand 13" MB Pro 2009. All was going well until I decided to upgrade it to 10.14.6 the other day. Post-install I rebooted from the Mojave Patcher volume and re-applied the patches, then rebooted normally. It worked but I quickly noticed that sound was no longer working (volume keys did nothing and the built-in Internal Speakers were no longer displayed in System Preferences: Sound - Output). Screen brightness also couldn't be changed (either using the screen brightness keys or in System Preferences: Displays - Brightness slider). Even so, I applied some Software Updates (Safari, Xcode, iWork apps) and they installed fine (eventually!). Later I noticed that the system was generally sluggish (it's got 8GB RAM and an SSD so is usually pretty responsive) and after a while was running hot and the fan came on. I decided to reboot to see if any of the problems were cured but things got worse! Reboot took longer than normal and when complete, the system complained that there was no keyboard connected (the trackpad didn't work either)! I was able to shutdown by plugging in a USB mouse and clicking on the login window Shutdown button. I left it for a while to cool right down...
Now for the solution! I rebooted off the Mojave Patcher volume and re-applied all the Patches for the model. AND I also checked the box to Rebuild Caches: once done and rebooted everything is now working normally again: keyboard+trackpad, sound and screen brightness; and the system is snappy and not running hot. This may not solve everyone's problems with hardware not working, but it's worth a try.
Thanks to Dosdude and other contributors for enabling us to keep older Macs running with the latest software. In this case it means my 13-year-old son is able to learn with the latest Xcode/Swift environment.
 
  • Like
Reactions: roronl
solved it:

deleted / renamed NVDAStartup.kext in s/l/e in Patcher Disk.

I just waited a while and the screen got black. So I knew the system was not stuck. It was alive but got no picture. I even was able to shut down the mac with ctrl-alt-cmd-eject.

So I fiddled a while with the nvidia kexts - if NVDAStartup.kext got disabled the patcher continued to boot and displayed the GUI.

Problem sorted.

I might have the same issue, see here:

I'm also having issues with the gpu drivers, after a lot of testing and creating quite some usb's i presume something has changed between the 1.2.3 and 1.3.0 patcher (10.13 patchers work fine as well). I have a 2008 MP3,1 with a efi flashed gtx680 (working boot screens), and only patcher 1.2.3 using up to 10.14.3 create a bootable usb installer. When booting a 1.3.* patched usb stick, the boot progress bar shows fine, until finished, it then kills all video output instead of showing the installer. Same for verbose/safe mode (so no errors), in single user mode video output works fine, since it doesn't seem to initiate the gpu drivers.

Using 1.3.3 with 10.14.5 and removing the nvda*.kext's from /s/l/e on the usb at least allows it to boot the installer with vga output (so i can create a working usb with some modification).

The post installation tools seems to work fine with both the 1.2.3 stick, and 1.3.3 (after removing kexts) to patch a 10.14.5 installation.

I haven't looked into what changed exactly, but My 2010 MBP doesn't have this issue (all usb's work fine without modification). So it seems to be related to something happening with the (patched/older?) nvidia drivers and the gtx680.

And here:

I also used the system preferences software update to update to 10.14.5, except afterwards my MP didn't want to boot any 1.3.* patched usb's (which work fine on my MBP). my old 1.2.3 usb booted fine. I have no other gpu's and tried all outputs. Creating a stock 10.14.5 usb with createinstallmedia, and setting no_compat_check in nvram also works fine, so it must be something the 1.3.* patcher is doing that is breaking things for the gtx680.

I am not talking about the post installation tool (which works fine as stated), I'm talking about actually booting the installer that the patcher created. (before even opening the post install tool). I have no option to "create a usb without legacy video patches" in the patcher. Since a vanilla usb is working, i presume it must be some framework/driver change the patcher is doing to the usb installer.

Presumably this also seems to occurs after installing Catalina, and booting for the first time (to a black screen). I haven't had time to look into it yet, but i probably will have to sooner or later.
 
Last edited:
FIXED MY ISSUE TEMPORARILY!

I managed to get rid of the red 1 from the system preferences in the Dock, from the Software Update in system preferences and also the notification in the Apple menu.
With these 2 following lignes of code in Terminal:
Code:
sudo defaults delete /Library/Preferences/com.apple.SoftwareUpdate.plist LastRecommendedMajorOSBundleIdentifier

defaults write com.apple.systempreferences AttentionPrefBundleIDs 0

And I needed to relaunch the Dock with:
Code:
killall Dock

It works as long as I do not run an update search with Software Update of System Preferences even though I have run (sudo softwareupdate - ignore "macOS Catalina" and sudo softwareupdate --list) before.

Hi all,
I think it works well, because it's been 3 days and I still have not had any notification in the Apple Menu or any red round on System Preferences of the Dock about Catalina's update...
 
Last edited:
I have a MacBook Pro 17 8,3.
The only reason that I have this MacBook is so that I can test software that my customers are using on their Macs. Until Mojave it was fine because I could run the same version as my customers.
Yesterday I successfully upgraded to Mojave using the Mojave Patcher, but I notice that the post installation process has a number of patched including SIP disabler.
Indeed if I now check my SIP status it come up as disabled.
The thing is that my customers mostly have SIP enabled, and so I cannot replicate what my customers have.
Now that Mojave is installed and running on the 8,3 is it necessary to retain the SIP disabled?
Is there way to have it enabled and for the 8,3 to still function?
thanks
 
Hi all,
I think it works well, because it's been 3 days and I still have not had any notification in the Apple Menu or any red round on System Preferences of the Dock about Catalina's update...

Just go and press check for updates. This will bring your red badge back in no time.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.