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.

Alex-Microsmeta

macrumors 6502
Jul 14, 2018
376
630
Rome
COMPLETELY BEWILDERED! REALLY NEED SOME HELP WITH THIS, AT WITS END :

Wrote about this a few days ago. Installed to 2010 Mini which ran perfectly fine with build 18G103 on the internal HDD, until I ran the 2020-001 update. Produces endless beachballing, hangs, crashes, etc., BUT ONLY ON THE INTERNAL.

Runs perfectly well updated either on APFS (from Software Update) or HFS+ (by way of standalone/manual) on external drives. But as soon as I copy (with CCC) to the internal it becomes almost unusable. Have already done several reinstalls, but problem persists unabated. Have tried everything I can think of.

Basically do not understand why, when updated from build 18G103 to 18G3020, it won't run properly on the internal. (Never had this problem with Late '09 iMac).

All drives are HDD.

Any help, even wild guesses greatly appreciated.

I have Macmini 2010, but I have updated it to Catalina 10.15.3 and works fine with macOS Catalina Patcher on external HDD APFS. I use internal HDD only for backup, it is 10 years old and I fear it could be broken anytime after all the heavy work it has suffered.
 

RK78

macrumors 6502
Oct 24, 2019
270
92
...I don't have any experience with the CCC, maybe some errors are introduced in the way you clone it. Have you tried cloning using Disk Utility?
Great suggestion. Erased the internal, then used DU Restore from the good, working external HFS+ Appears to be behaving normally now. Not sure why CCC, which I've been using for years, gave me such a hard time for this task. And a BTW, 10.14 from Patcher on HDD appears to run just as well on HSierra, and Sierra before that, both on iMac and Mini -- but maybe a little bit slower on the Mini, which has a less powerful CPU.

Anyway, thanks.
 
  • Like
Reactions: avz

Ausdauersportler

macrumors 603
Nov 25, 2019
5,007
5,826
So If I have a 2011 iMac with a Radeon HD 6xxx I am out of luck on graphic acceleration? Might as well stay with High Sierra?
Ever read this?
 

caravella

macrumors newbie
Feb 14, 2020
24
11
Hi there,

I have a MacBook 7.1 mid 2010 with 8GB RAM and original HDD with 250GB, formatted with APFS.
Thanks to Dosdude's Mojave Patcher, the MacBook with 10.14.6 works very well.

Now I want to install Windows 10 with the Bootcamp Assistant and for this I have created a Bootcamp copy and I deleted in this copy with the text editor in content-info.plist

<key> PreUSBBootSupportedModels </key>

the pre to get the bootoption with a USB stick.
Unfortunately, I always get the following window:

fr_1014_size640.jpg


Does anyone have any idea what it could be?

Caravella
 

wolfie

macrumors regular
Apr 11, 2008
166
43
Hey guys, I made a mistake. I couldn’t get audio Aux sound from my 2012 Catalina Mac mini Dosdude install... so I went and installed the legacy sound patch which has screwed all audio up.

Where is this latch stored so I can remove it?

Secondly, any reason why AUX doesn’t work?
 

Ausdauersportler

macrumors 603
Nov 25, 2019
5,007
5,826
Hey guys, I made a mistake. I couldn’t get audio Aux sound from my 2012 Catalina Mac mini Dosdude install... so I went and installed the legacy sound patch which has screwed all audio up.

Where is this latch stored so I can remove it?

Secondly, any reason why AUX doesn’t work?
Once in a while I have such issues, too. From my experience it is more easy to do another install instead of deleting several kext and rebuilding the prelinked kernel.
Just out of curiosity: Your 2012 Mac mini is a supported machine, I guess you are talking about a Hackintosh clone of it? Just put your hardware description in your personal signature. Makes live more easy for the people here :)
 
Last edited:

wolfie

macrumors regular
Apr 11, 2008
166
43
Once in a while I have such issues, too. From my experience it is more easy to do another install instead of deleting several kext and rebuilding the prelinked kernel.
Just out of curiosity: Your 2012 Mac mini is a supported machine, I guess you are talking about a Hackintosh clone of it? Just put your hardware description in your personal signature. Make live more easy for the people here :)
[automerge]1581863139[/automerge]
I must admit I didn’t realise 2012 was still supported ?
I assumed it wasn’t and went straight for Dosdude. Any harm in doing it Dosdude way? I assume it’s vanilla and Dosdudes software just skipped what it needs to otherwise do.
 

Ausdauersportler

macrumors 603
Nov 25, 2019
5,007
5,826
[automerge]1581863139[/automerge]
I must admit I didn’t realise 2012 was still supported ?
I assumed it wasn’t and went straight for Dosdude. Any harm in doing it Dosdude way? I assume it’s vanilla and Dosdudes software just skipped what it needs to otherwise do.
I would go the apple way as long as the machine is supported. It allows to update in small steps instead of the complete reinstallation of the MacOS from the installer and you do not have any intermediate steps like downloading a patcher, download the installer, patching the installer, avoiding wrongly post installed patches. Just go back to start and do a fresh install. Probably your first place audio problems were just introduced through the patched installer?
 

Alex-Microsmeta

macrumors 6502
Jul 14, 2018
376
630
Rome
Hi
How is the display connected? Probably Single Link DVI to HDMI? If so, you could try using a DisplayPort to HDMI adapter. There's two kinds - passive and active. Passive requires that the DisplayPort output supports DisplayPort dual mode (does the Quadro have that?). Active might be better in your case sense the GPU will send a DisplayPort signal instead of HDMI. You can get a DisplayPort 1.2 to HDMI 2.0 adapter (but your TV only needs HDMI 1.x) which are always active.

https://www.club-3d.com/en/detail/2366/ CAC-1070 DP 1.2 to hdmi 2.0 uhd active adapter
https://www.club-3d.com/en/detail/2438/ CAC-2070 DP 1.2 to hdmi 2.0 uhd active adapter
https://www.club-3d.com/en/detail/2365/ CAC-1073 DP 1.2 cable to hdmi 2.0 uhd 4k60hz active 3m
https://www.club-3d.com/en/detail/2442/ CAC-1080 DP 1.4 to hdmi 2.0b hdr active adapter
https://www.club-3d.com/en/detail/2465/ CAC-1082 DP 1.4 cable to hdmi 2.0b active adapter 2m

The Quadro 2000 is a Kepler generation GPU so it should work in latest macOS?

Hi!

Since you have been so kind, I inform you that I have solved my macOS issue on unsupported hardware ...tricking. I have installed Sierra on ...Vmware for Windows 10. Works fine full screen @1920x1080, fast and stable. Also audio was not working on Mojave patched, now it is perfect :) It is almost fast as my real iMac 2013 and 2 times faster than my Mac mini 2010 with @dosdude1 Catalina Patcher. New macOS versions are heavy and don't add much more, excluding dark theme and useless (for me) Arcade and Apple TV services.

bench.png
 
Last edited:

wire_

macrumors member
Nov 26, 2019
33
26
COMPLETELY BEWILDERED! REALLY NEED SOME HELP WITH THIS, AT WITS END :

Wrote about this a few days ago. Installed to 2010 Mini which ran perfectly fine with build 18G103 on the internal HDD, until I ran the 2020-001 update. Produces endless beachballing, hangs, crashes, etc., BUT ONLY ON THE INTERNAL.

Runs perfectly well updated either on APFS (from Software Update) or HFS+ (by way of standalone/manual) on external drives. But as soon as I copy (with CCC) to the internal it becomes almost unusable. Have already done several reinstalls, but problem persists unabated. Have tried everything I can think of.

Basically do not understand why, when updated from build 18G103 to 18G3020, it won't run properly on the internal. (Never had this problem with Late '09 iMac).

All drives are HDD.

Any help, even wild guesses greatly appreciated.

The observation about Mojave hating HDD is a lame explanation, but prolly not totally wrong. Drive IO demands have gone up in last many releases of MacOS and SSD was desirable / needed years ago, now its essential.

But I think the deeper issue is—and this is why Apple no longer supports older Macs—is not just because they hate legacy users and want to sell more kit, but because there are architecture limits requiring new microcode and instructions only found in later chipsets. Recall there were severe security vulnerabilities in Intel microarchitecture re caches and special remediations requires costly work-arounds at level of instruction set. The innards of an x86 cache-core complex are constantly evolving, like every other part of the system, so Apple likely hit a threshold on acceptable performance and "unsupported" Macs are by definition on the wrong side of this. So it could be an IO bottleneck that's partly mitigated by a faster drive, but becomes pathological for some configurations.

I apologize for this reply sounding like juju, but for example, while I can install and run Mojave on a 2008 Macbook Pro unibody, with SSD it is just barely useable and takes forever on IO. This was not a problem for El Cap, which we should note has long since stopped getting security updates.

So probably latest SW has chipset security workarounds that are not viable on older designs, spoil caches, etc. Perf sucks

You may say "but what about Windows" and keep in mind Msft has never had any problem with your system being eaten by malware—it's actually a point of pride to be destroyed on Windows and everyone was taught to blame themselves decades ago.
 

mrploppy

macrumors regular
Oct 27, 2017
242
128
The observation about Mojave hating HDD is a lame explanation, but prolly not totally wrong. Drive IO demands have gone up in last many releases of MacOS and SSD was desirable / needed years ago, now its essential.

But I think the deeper issue is—and this is why Apple no longer supports older Macs—is not just because they hate legacy users and want to sell more kit, but because there are architecture limits requiring new microcode and instructions only found in later chipsets. Recall there were severe security vulnerabilities in Intel microarchitecture re caches and special remediations requires costly work-arounds at level of instruction set. The innards of an x86 cache-core complex are constantly evolving, like every other part of the system, so Apple likely hit a threshold on acceptable performance and "unsupported" Macs are by definition on the wrong side of this. So it could be an IO bottleneck that's partly mitigated by a faster drive, but becomes pathological for some configurations.

I apologize for this reply sounding like juju, but for example, while I can install and run Mojave on a 2008 Macbook Pro unibody, with SSD it is just barely useable and takes forever on IO. This was not a problem for El Cap, which we should note has long since stopped getting security updates.

So probably latest SW has chipset security workarounds that are not viable on older designs, spoil caches, etc. Perf sucks

You may say "but what about Windows" and keep in mind Msft has never had any problem with your system being eaten by malware—it's actually a point of pride to be destroyed on Windows and everyone was taught to blame themselves decades ago.
FYI, apart from the reluctance to sleep, Mojave on my late 2008 MacBook Pro runs absolutely fine.
 

wire_

macrumors member
Nov 26, 2019
33
26
FYI, apart from the reluctance to sleep, Mojave on my late 2008 MacBook Pro runs absolutely fine.

When you say runs fine, do you mean boots at a speedy clip, desktop comes up rapidly, apps launch snappily, Finder transitions happen as soon as you click?

Or do you mean waiting for things to get going is not too bad and sure UI could be quicker and beachballing sometimes but it runs my programs and it's alot better than nothing?
[automerge]1582146224[/automerge]
When you say runs fine, do you mean boots at a speedy clip, desktop comes up rapidly, apps launch snappily, Finder transitions happen as soon as you click?

Or do you mean waiting for things to get going is not too bad and sure UI could be quicker and beachballing sometimes but it runs my programs and it's alot better than nothing?
The reason I'm harping on this is I have three legacy Macs, 2008 Pro 3,1, late 2008 MPB, 2009 mini on Mojave with SSDs and max RAM all in good working order and none of them feels anywhere close to as speedy as
an old supported 2012 macbook pro.
 

avz

macrumors 68000
Oct 7, 2018
1,830
1,897
Stalingrad, Russia
When you say runs fine, do you mean boots at a speedy clip, desktop comes up rapidly, apps launch snappily, Finder transitions happen as soon as you click?

Or do you mean waiting for things to get going is not too bad and sure UI could be quicker and beachballing sometimes but it runs my programs and it's alot better than nothing?

LOL. You are clearly don't have graphic acceleration.

On my MacBook5,1 Mojave is superior to El Capitan in every single way and actually returns a slightly higher numbers in Geekbench 4, so it is not just subjective.
 

wire_

macrumors member
Nov 26, 2019
33
26
Lol!! GTX680 can't decode h265 and 8 core can transcode h265 to h264 as fast as play it on screen.

So what are you talking about?This is not a just a Metal issue...

I mean thanks to great work by dosdude my system goes from 0 to running, which is a speedup of infinity!

And not only this these old things still useful.

But there are likely good technical reasons that performance tanks in some cases, just like missing support for various of little things

All I am saying to readers is keep light expectations and take anyone who boasts about how quick their old Mac is with some doubt.
 

mrploppy

macrumors regular
Oct 27, 2017
242
128
When you say runs fine, do you mean boots at a speedy clip, desktop comes up rapidly, apps launch snappily, Finder transitions happen as soon as you click?

Or do you mean waiting for things to get going is not too bad and sure UI could be quicker and beachballing sometimes but it runs my programs and it's alot better than nothing?
[automerge]1582146224[/automerge]

The reason I'm harping on this is I have three legacy Macs, 2008 Pro 3,1, late 2008 MPB, 2009 mini on Mojave with SSDs and max RAM all in good working order and none of them feels anywhere close to as speedy as
an old supported 2012 macbook pro.
I mean it "runs fine, boots at a speedy clip, desktop comes up rapidly, apps launch snappily, Finder transitions happen as soon as I click". Yup. If yours doesn't, I suggest something's wrong with your system.

FYI, my internal drive is a 500GB SSD, formatted APFS - about half full.
 

avz

macrumors 68000
Oct 7, 2018
1,830
1,897
Stalingrad, Russia
Lol!! GTX680 can't decode h265 and 8 core can transcode h265 to h264 as fast as play it on screen.

So what are you talking about?This is not a just a Metal issue...

I mean thanks to great work by dosdude my system goes from 0 to running, which is a speedup of infinity!

And not only this these old things still useful.

But there are likely good technical reasons that performance tanks in some cases, just like missing support for various of little things

All I am saying to readers is keep light expectations and take anyone who boasts about how quick their old Mac is with some doubt.

??? You brought GTX680 to a MacBook5,1 discussion??? Are you sure you wired correctly???

All I said is that Mojave is superior to El Capitan on my MacBook5,1, benchmarks confirm that.
 

MacMusic01

macrumors newbie
Feb 21, 2020
26
18
Hi,

I recently installed macOS Mojave on my mid 2010 Macbook using the patcher from dosdue1 which was worked perfectly until i found out when trying to enter recovery mode, the screen came up with the blocked symbol not letting me enter recovery mode which is a big risk for the future if anything should happen.

I have looked all over YouTube and forums as well as Known Issues on dosdude1 website which hasn't come up.

Please help as i cant find anyway to fix this and would hate having to erase my hard drive as the only way it seems to access recovery mode is by using a bootable drive which dosent allow me to do anything on my main hard drive.

Thanks in advance for your help.
 

avz

macrumors 68000
Oct 7, 2018
1,830
1,897
Stalingrad, Russia
Hi,

I recently installed macOS Mojave on my mid 2010 Macbook using the patcher from dosdue1 which was worked perfectly until i found out when trying to enter recovery mode, the screen came up with the blocked symbol not letting me enter recovery mode which is a big risk for the future if anything should happen.

I have looked all over YouTube and forums as well as Known Issues on dosdude1 website which hasn't come up.

Please help as i cant find anyway to fix this and would hate having to erase my hard drive as the only way it seems to access recovery mode is by using a bootable drive which dosent allow me to do anything on my main hard drive.

Thanks in advance for your help.

I used the guide on page 415 of this thread.
 

mrploppy

macrumors regular
Oct 27, 2017
242
128
Hi,

I recently installed macOS Mojave on my mid 2010 Macbook using the patcher from dosdue1 which was worked perfectly until i found out when trying to enter recovery mode, the screen came up with the blocked symbol not letting me enter recovery mode which is a big risk for the future if anything should happen.

I have looked all over YouTube and forums as well as Known Issues on dosdude1 website which hasn't come up.

Please help as i cant find anyway to fix this and would hate having to erase my hard drive as the only way it seems to access recovery mode is by using a bootable drive which dosent allow me to do anything on my main hard drive.

Thanks in advance for your help.
Why do you say booting from another drive doesn't allow you to do anything on your main drive? Maybe I'm missing something.
 

MacMusic01

macrumors newbie
Feb 21, 2020
26
18
Why do you say booting from another drive doesn't allow you to do anything on your main drive? Maybe I'm missing something.
I am referring to the usb flash drive i used to install the macos on, as seen in turtoirals on how to use the patcher. Then in recovery mode (before mojave was installed) i installed mojave from the installer that was on the usb drive.
Then once instillation was complete It came up with the same sign that is stopping me getting into recovery mode but after a reboot it was fine.
but now i have the problem of not being able to get accses to recovery mode
[automerge]1582292834[/automerge]
Before attempt this unplug any external USB hard disks, USB drive and unmount any DMG (also eventually DMG app you were installing) mounted on your desktop.

Boot Mojave normally, then launch Terminal and type (or copy/paste one at once):

diskutil mount disk2s4

cd /Volumes/Recovery/F5A3594D-C5CF-3AAB-A32C-9EBFF51C6FF5/

sudo mv immutablekernel immutablekernelbackup

sudo mv PlatformSupport.plist PlatformSupportbackup


sudo cp -a /System/Library/Prelinkedkernels/prelinkedkernel /Volumes/Recovery/F5A3594D-C5CF-3AAB-A32C-9EBFF51C6FF5/immutablekernel


then type: open /Volumes/Recovery/F5A3594D-C5CF-3AAB-A32C-9EBFF51C6FF5/

landing on Finder using TextEdit or any other plain-text editor launch com.apple.boot.plist

Inside it first check the green part if matches with your file, in this place add the orange part (in one line) close and save:

<string>root-dmg=file:///F5A3594D-C5CF-3AAB-A32C-9EBFF51C6FF5/BaseSystem.dmg -no_compat_check -v</string>

Now, reboot and hold CMD+R after power-on chime, if you still can't reach APFS Recovery, post here a picture of your verbose screen.
dosent work for me, cant find direcoty
 

MacMusic01

macrumors newbie
Feb 21, 2020
26
18
??? You brought GTX680 to a MacBook5,1 discussion??? Are you sure you wired correctly???

All I said is that Mojave is superior to El Capitan on my MacBook5,1, benchmarks confirm that.
Sorry it brought up the wrong post was meant to be another one
 

mrploppy

macrumors regular
Oct 27, 2017
242
128
I am referring to the usb flash drive i used to install the macos on, as seen in turtoirals on how to use the patcher. Then in recovery mode (before mojave was installed) i installed mojave from the installer that was on the usb drive.
Then once instillation was complete It came up with the same sign that is stopping me getting into recovery mode but after a reboot it was fine.
but now i have the problem of not being able to get accses to recovery mode
[automerge]1582292834[/automerge]

dosent work for me, cant find direcoty
Didn't really understand your reply. Are you saying you have Mojave installed on the USB flash drive? What do you mean "in recovery mode (...) I installed Mojave from the ..." ? I'm lost.

Anyhow, forgetting the fact I'm lost, what do you need to do from within Recovery Mode that you can't do when booting from the patched installer?
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.