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.

Rob1n

macrumors member
Jun 8, 2020
70
58
Netherlands
Try to restart your computer into the DosDude USB, reapply the patches and don't select the apfs patch option.
If that doesn't work, reinstall the Mac OS over the disk from the DosDude USB and don't select the apfs patch option. This will not affect your files.
I sent a message to dosdude and he said that you just need to select your startup disk and everything will boot fine.

With all this talk of BootROMs and EFIs, I got to wondering. I installed the APFS Update successfully on my 3,1. Did get verbose start up for the first couple of startups then they went away. And now I am back to a normal boot screen.

I have been doing a lot of everything and have to reboot a lot. And in doing so I usually have boot through Startup Manager. There I see all the bootable volumes. But in with them are 3 EFI volumes that implies that they can be booted from. They are just marked "EFI".

I have never tried not knowing what they could do. But in all the pics posted I haven't seen them in other Startup Managers. I trust that there's one per OS that might need them for whatever reason.

Is there anything I should know about or can do with or to them?

if you do the boot rom patch it wil give you 2 efi drives per os. This is a glitch.
watch this video for more information:

 

avz

macrumors 68000
Oct 7, 2018
1,830
1,896
Stalingrad, Russia
Since, as I said, High Sierra (supported) runs quite well on the Mini, but not Mojave via the Patcher - and you suggest that it should run equally well - where would you look, or what action would you take to remedy this?
YMMV, so don't be afraid to experiment, APFS gives you the ability to almost instantly return to "where you once belonged". Reduce the amount of third party apps and extensions.
Everybody has a different definition of "run equally well". I have no issues running Mojave on a 7200rpm HDD(APFS) with FileVault enabled. Other users will say that APFS and HDD don't play well together. Go figure.
 

trifero

macrumors 68030
May 21, 2009
2,965
2,808
With all this talk of BootROMs and EFIs, I got to wondering. I installed the APFS Update successfully on my 3,1. Did get verbose start up for the first couple of startups then they went away. And now I am back to a normal boot screen.

I have been doing a lot of everything and have to reboot a lot. And in doing so I usually have boot through Startup Manager. There I see all the bootable volumes. But in with them are 3 EFI volumes that implies that they can be booted from. They are just marked "EFI".

I have never tried not knowing what they could do. But in all the pics posted I haven't seen them in other Startup Managers. I trust that there's one per OS that might need them for whatever reason.

Is there anything I should know about or can do with or to them?
It´s normal. Just select the Startup Disk in Preferences and will boot nativelly.
 

joevt

macrumors 604
Jun 21, 2012
6,977
4,265
I sent a message to dosdude and he said that you just need to select your startup disk and everything will boot fine.



if you do the boot rom patch it wil give you 2 efi drives per os. This is a glitch.
watch this video for more information:
Each item shown by Startup Manager points to a different thing. I guess the Startup Manager of old Macs isn't smart enough to understand that it doesn't need to show both items for an APFS partition.

I use the Driver####, DriverOrder method (instead of the rom patch) to load the apfs.efi driver before the Startup Manager on my MacPro3,1.

My Startup Manager has 3 items per APFS macOS (Mojave4, Mojave5, Mojave6, Catalina): System "EFI Boot" (\System\Library\CoreServices\boot.efi), Preboot 🄿 (\_system_uuid_\System\Library\CoreServices\boot.efi), and Recovery 🅁 (\_system_uuid_\boot.efi). Preboot is the one that gets the default .disk_label (I override all the .disk_labels manually with my own .disk_label). Recovery appears only if you bless it manually. The fourth is my custom booter 🄱 using a copy of the dosdude APFS patch (EFI Shell, apfs.efi driver, and startup.nsh script) copied to a separate HFS+ partition. I can boot Catalina with the System, Preboot, or Booter items.

The picture shows three more "EFI Boot" options. One is from Ubuntu boot loader in an EFI partition (\EFI\BOOT\BOOTX64.EFI). The other two are from my Windows 7 and Windows 10 partitions (\EFI\Boot\bootx64.efi). They appear because I also loaded the ntfs.efi driver for this picture (I would not actually try to boot Windows with the EFI loader because it won't work or it would cause problems - so normally I do not load the ntfs.efi driver). You can add a volume icon to any of these but adding a .disk_label does not remove the "EFI Boot". I think "EFI Boot" can only be replaced on volumes that can be blessed (HFS+ and some APFS volumes). Newer Macs may use .disk_label on partitions that cannot be blessed (such as FAT partitions on my Mac mini 2018).

The Recovery (one Recovery per macOS), Shell, and rEFIt items are blessed HFS+ partitions.

A Windows item appears for any disk that has boot code in the MBR. I have two such disks with multiple Windows partitions per disk. Booting one of these items causes the CSM to be loaded (BIOS booting instead of EFI booting), then the MBR boot code is executed which executes the PBR boot code of the partition that is marked as active in the MBR.

MacPro3,1 Startup Manager 2.jpg
 

abcd-abcd

macrumors member
Dec 23, 2011
33
2
I have a Mac Pro 5,1 (was originally a 2009 4,1) with a flashed NVIDIA GeForce GTX 680 2 GB graphics card running Mojave 10.14.6. It was previously running fine (with some help from DosDude1 - I've brought the SSDs over from my old Mac Pro 3,1) but I had to erase & re-install Mojave on my SSD since moving to the Mac Pro 5,1 - but now my graphics card doesn't work properly! Help! It had been working in this 5,1 but now it won't. It isn't shown as Metal-capable any more and the Mac won't play any video at all...

I've tried doing DosDude1's Mac OS post install and selecting SIP Disabler & Legacy Video Card patches, but they don't work... does anyone have any ideas? It would be great if you could help - I've run out of ideas! Thanks!
 
  • Like
Reactions: TimothyR734

Ausdauersportler

macrumors 603
Nov 25, 2019
5,007
5,826
I have a Mac Pro 5,1 (was originally a 2009 4,1) with a flashed NVIDIA GeForce GTX 680 2 GB graphics card running Mojave 10.14.6. It was previously running fine (with some help from DosDude1 - I've brought the SSDs over from my old Mac Pro 3,1) but I had to erase & re-install Mojave on my SSD since moving to the Mac Pro 5,1 - but now my graphics card doesn't work properly! Help! It had been working in this 5,1 but now it won't. It isn't shown as Metal-capable any more and the Mac won't play any video at all...

I've tried doing DosDude1's Mac OS post install and selecting SIP Disabler & Legacy Video Card patches, but they don't work... does anyone have any ideas? It would be great if you could help - I've run out of ideas! Thanks!
Q: You selected the Legacy Video Card patch within the post install tool with a metal capable GPU?
 
  • Like
Reactions: TimothyR734

abcd-abcd

macrumors member
Dec 23, 2011
33
2
Hi Ausdquersportier - thanks for your reply. I only ran the patch because after my Mojave re-installation, the GTX680 was not Metal capable. I believe that only a "Mac Edition" GTX 680 is natively Metal-capable.
 
  • Like
Reactions: TimothyR734

Ausdauersportler

macrumors 603
Nov 25, 2019
5,007
5,826
Hi Ausdquersportier - thanks for your reply. I only ran the patch because after my Mojave re-installation, the GTX680 was not Metal capable. I believe that only a "Mac Edition" GTX 680 is natively Metal-capable.
I am not an MacPro user or expert, but with my iMac I use flashed Nvidia cards, too. The Legacy Video Card patches are meant for "non Metal GPU" equipped systems and to my knowledge these patches bring back some acceleration, but never metal to a non metal card.

To get rid of such a patch just reinstall Mojave again and chose the patches according to your hardware.
 

FlorisVN

macrumors 6502a
Nov 8, 2013
979
380
Hi Ausdquersportier - thanks for your reply. I only ran the patch because after my Mojave re-installation, the GTX680 was not Metal capable. I believe that only a "Mac Edition" GTX 680 is natively Metal-capable.

not true.
all compatible kepler cards work just fine, and are metal compatible.
a mac edition 680 just has the correct apple EFI rom firmware onboard, which gives you the bootscreen as an extra.
you can also easiliy flash a compatible GTX680 your self for your MacPro.

I did mine a while back, and works just fine now as a full Mac edition GTX680 ;)
 

honeycombz

macrumors 6502a
Jul 6, 2013
588
154
Hey, I have a Mac Pro 3,1 running DosDude High Sierra on HFS+ great but it’s time to bump to Mojave for various reasons. Does the patcher install of Mojave deal with the APFS conversion for me?
 
  • Like
Reactions: TimothyR734

jowaju

macrumors 6502
Mar 7, 2019
251
333
Hey, I have a Mac Pro 3,1 running DosDude High Sierra on HFS+ great but it’s time to bump to Mojave for various reasons. Does the patcher install of Mojave deal with the APFS conversion for me?
It will NOT automatically convert to APFS for you during the install. You can convert using Disk Utility before starting the install, or leave it on HFS+, Mojave works with either one.
 
  • Like
Reactions: TimothyR734

honeycombz

macrumors 6502a
Jul 6, 2013
588
154
Convert it, you will need it in the future anyway to go to big sur or later.
Better to convert in High Sierra or update to Mojave, than convert? or can it be done while upgrading to Mojave or should it be done after upgrade. Disk Utility for all non destructive conversions or other methods.
 
Last edited:
  • Like
Reactions: TimothyR734

Fox_McCloud45

macrumors newbie
Nov 6, 2020
4
3
Hello.

I have an Apple Mac Pro 3,1 equipped with an unflashed NVIDIA GeForce GTX 770 2GB, which is consequently not compatible with the EFI display.

While I can properly create an installation medium with dosdude1's macOS Mojave Patcher, I find myself unable to boot from it. Since the Boot Selection menu does run but doesn't display, I use the Startup Disk setting from the System Preferences to set the USB drive as startup disk.

Despite waiting for a rather long time, nothing ever shows up on-screen. As the USB device has a LED showing its activity, I know that it is done booting and I'm pretty sure it's in that state where it has booted but cannot display anything. The CAPS LOCK key works and toggles the keyboard's LED (non-Apple keyboard).

From what I've read, Apple dropped most NVIDIA cards when introducing Metal, but I've also read on MacVidCards that the NVIDIA GeForce GTX 770 was similar enough to the officially-supported NVIDIA GeForce GTX 680 (Mac edition?) to use the native Apple drivers.

At first, I thought this happened because the card is not flashed, since MacVidCards sells Mac-flashed cards. However, I've read on NVIDIA forums that someone successfully got macOS Mojave running with an NVIDIA GeForce GTX 670 card without EFI support. So I'm a bit confused, although I'm pretty sure it's an incompatibility issue.

I have a Mac Pro 1,1 with an EFI-capable AMD Radeon HD 5770 but I'm not that experienced with swapping cards in and out, and I'm not sure that using the AMD card to install the OS then putting the NVIDIA card back in would help; it would feel like an external driver (which does not exist for Mojave) is required.

Someone had a similar issue back in March 2019 and asked for help here but was never answered, or I didn't find his answer.

Thanks in advance.

Edit: I initially found this thread, which is where I found the redirection to this still-active thread. Despite the lack of an EFI-capable card, he was still able to run the installer after waiting some time; but that does not seem to be my case.
 
Last edited:
  • Like
Reactions: TimothyR734

Ausdauersportler

macrumors 603
Nov 25, 2019
5,007
5,826
The 770 is perfectly metal compatible. Apple did not drop NVIDIA cards, they will be still supported in the upcoming Big Sur.

Take a look at this thread covering Open Core on Mac Pro system using a technology to emulate the boot screen.
 
  • Like
Reactions: TimothyR734

Fox_McCloud45

macrumors newbie
Nov 6, 2020
4
3
The 770 is perfectly metal compatible. Apple did not drop NVIDIA cards, they will be still supported in the upcoming Big Sur.

Take a look at this thread covering Open Core on Mac Pro system using a technology to emulate the boot screen.

What I meant is that Apple reduced the number of supported NVIDIA cards drastically, with full hardware acceleration that is.

I took a look at the thread you linked, but it seems to target Mac Pro 4,1 and later models. I've read here that it can run on Mac Pro 3,1 just fine, but you have to disable Lilu and Whatevergreen.kexts to FALSE, which... disables hardware acceleration? I'm not sure, but in that case it would make upgrading pointless.

Also, I made a macOS High Sierra installation medium from dosdude1's High Sierra patcher, and it works fine, although APFS won't work even with post-install patching.
 
  • Like
Reactions: TimothyR734

jowaju

macrumors 6502
Mar 7, 2019
251
333
What I meant is that Apple reduced the number of supported NVIDIA cards drastically, with full hardware acceleration that is.

I took a look at the thread you linked, but it seems to target Mac Pro 4,1 and later models. I've read here that it can run on Mac Pro 3,1 just fine, but you have to disable Lilu and Whatevergreen.kexts to FALSE, which... disables hardware acceleration? I'm not sure, but in that case it would make upgrading pointless.

Also, I made a macOS High Sierra installation medium from dosdude1's High Sierra patcher, and it works fine, although APFS won't work even with post-install patching.
Which video output port are you using on your 770?
 
  • Like
Reactions: TimothyR734

alphascorp

macrumors 6502
Jul 16, 2018
343
635
Brest, France
Hi all,

Successfully installed SecUpd2020-006Mojave (18G6042) on MBP5,3.

Here is the download link on Apple servers:

This time, no need to modify the distribution file (it is not present in the .pkg)
In addition, installing this update does not break appleGVA, softwareupdate.framework, HIToolbox and the Siri waveform continues to work (for those who had modified Siri.app and SiriUI.framework)
The only requirement after installing this update is to reboot on USB Key and re-patch with Dosdude1 Patcher with cache rebuild.

Capture d’écran 2020-11-13 à 00.41.42.png
 

LordeOurMother

macrumors 6502
Jul 10, 2014
397
122
Hi all,

Successfully installed SecUpd2020-006Mojave (18G6042) on MBP5,3.

Here is the download link on Apple servers:

This time, no need to modify the distribution file (it is not present in the .pkg)
In addition, installing this update does not break appleGVA, softwareupdate.framework, HIToolbox and the Siri waveform continues to work (for those who had modified Siri.app and SiriUI.framework)
The only requirement after installing this update is to reboot on USB Key and re-patch with Dosdude1 Patcher with cache rebuild.

View attachment 1662691
How is the performance on Mojave? My MBP mid 2009 does not handle Catalina very well. It handled El Capitan much better.
 

K two

macrumors 68020
Dec 6, 2018
2,314
3,187
North America
How is the performance on Mojave? My MBP mid 2009 does not handle Catalina very well. It handled El Capitan much better.
Catalina is slightly more nimble than Mojave on this Mini3,1. YMMV
32bit, HFS+ and Firewire booting remain intact in Mojave, however. Some trade-offs to consider? If updating beyond Mojave, APFS is the only option.
latest mojave.png
 
  • Like
Reactions: TimothyR734
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.