Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Of course it will be blocked - that's a 980 GPU. 680s and 780s are supported by Apple meaning they don't require Nvidia's web drivers to work out of the box.

The 680 has also been blocked from the USB Installer per many posts here. If the 780 worked for you, great. I was just surprised as I have not seen reports from anyone else using a metal NVIDIA card who has been able to use the USB installer.
 
The 680 has also been blocked from the USB Installer per many posts here. If the 780 worked for you, great. I was just surprised as I have not seen reports from anyone else using a metal NVIDIA card who has been able to use the USB installer.
I don't think a flashed 680 is blocked by Apple on purpose.. It is a bug that they need to fix.
 
I don't think a flashed 680 is blocked by Apple on purpose.. It is a bug that they need to fix.
Of course it's a bug. But it still prevents use of the USB method at the moment, along with all of the web driver NVIDIA cards. Maybe the 780 is the only NVIDIA card that works with the USB installer at the moment. I haven't seen reports of success from anyone else with an NVIDIA card who has been able to successfully install Mojave via USB, hence my surprise that it worked for you.
 
I used createinstallmedia. Since I don't have an EFI GPU (thus no boot picker) I had to pull all bootable drives from the chassis, leaving only the blank installation drive and the USB stick with the installer. Long black screen waiting for it to boot from the USB flash drive. Then I immediately went into Disk Utility and proceeded to erase the drive as APFS (encypted), which worked fine.

Yes, the volume was re-mounted after it was erased with disk utility.

I will try this again today when I get back to my cMP. Obviously, with a non-EFI GPU it's not viable for me to enable FV anyway, but I was curious if Apple had blocked that method also. If it worked for you that's definitely encouraging though. I will report back later today.

Edit: and I think OP was speaking about losing the ability to store your recovery key in iCloud, which is normally offered when enabling FV through the GUI. I think he was asking if there is any way to do that after the fact. I don't believe so, but have never actually looked into it.

Yes, exactly. So I don't have to worry about the password or manually create a key - It would be automatically set up with iCloud. This is what I've done previously, activate FileVault after install.

But if I understand you correctly, you could install Mojave with a non-EFI GPU, but not the GTX 680 because of the bug?
So if I boot Mojave installer on USB + my blank drives, and use my non-Mac GTX 1060 - I can format APFS Encrypted and install Mojave, and thus "Enable" FileVault?

I guess the problem would be the actual install, when the computer reboots I wouldn't be able to see the "Harddrive password" prompt, but just wait and hope for the best...? And then type at a random point?

Afterwards of course I could drop in my GTX 680 and complete setup.

Or maybe I'm stuck between two issues:
1. Not being able to run USB installer because of GTX 680 bug
2. Not being able to use GTX 1060 install to APFS Encrypted because installer detects it's non-EFI.
 
Last edited:
Yes, exactly. So I don't have to worry about the password or manually create a key - It would be automatically set up with iCloud. This is what I've done previously, activate FileVault after install.

But if I understand you correctly, you could install Mojave with a non-EFI GPU, but not the GTX 680 because of the bug?
So if I boot Mojave installer on USB + my blank drives, and use my non-Mac GTX 1060 - I can format APFS Encrypted and install Mojave, and thus "Enable" FileVault?

I guess the problem would be the actual install, when the computer reboots I wouldn't be able to see the "Harddrive password" prompt, but just wait and hope for the best...? And then type at a random point?

Afterwards of course I could drop in my GTX 680 and complete setup.

Or maybe I'm stuck between two issues:
1. Not being able to run USB installer because of GTX 680 bug
2. Not being able to use GTX 1060 install to APFS Encrypted because installer detects it's non-EFI.

I think your GPUs are going to prevent you from using the 10.14.0 USB installer. Your item #1 is correct ("Not being able to run USB installer because of GTX 680 bug"), but you probably can't use your 1060 either because it requires Web Drivers to be recognized as a Metal-capable card, and those won't be installed from within the installer. So the install will not proceed saying that you must install a Metal-capable card to continue.

If you have the time, I really think it would be worth it to try using dosdude1's patcher to make a new USB installer. I tried this last night and was able to install to an encrypted drive, whereas the stock USB installer prevented that. Dosdude1 is a trusted contributed here, and he's been doing this for a long time. So the risk of something going wrong is really quite low.

In fact, you'd also be helping the community here, because I'm not sure if anyone has tested whether or not the mods he made to the installer disable the check for a metal-capable card or not. If using his modified installer allows you to proceed with the install (either with your 680 or your 1060) then it could be a solution to others here with NVIDIA cards who prefer to do a clean install via USB.

It really doesn't take long to make the installer drive (especially if you already have "Install macOS Mojave.app" downloaded. Just download the patcher here and follow the directions. You will get a message that the patcher isn't intended for your model (since it's designed to be used with Macs that Apple dropped from the compatibility list) but it will happily proceed past that to make the USB installer.

If you decide to try it, please report back your results!
 
I think your GPUs are going to prevent you from using the 10.14.0 USB installer. Your item #1 is correct ("Not being able to run USB installer because of GTX 680 bug"), but you probably can't use your 1060 either because it requires Web Drivers to be recognized as a Metal-capable card, and those won't be installed from within the installer. So the install will not proceed saying that you must install a Metal-capable card to continue.

If you have the time, I really think it would be worth it to try using dosdude1's patcher to make a new USB installer. I tried this last night and was able to install to an encrypted drive, whereas the stock USB installer prevented that. Dosdude1 is a trusted contributed here, and he's been doing this for a long time. So the risk of something going wrong is really quite low.

In fact, you'd also be helping the community here, because I'm not sure if anyone has tested whether or not the mods he made to the installer disable the check for a metal-capable card or not. If using his modified installer allows you to proceed with the install (either with your 680 or your 1060) then it could be a solution to others here with NVIDIA cards who prefer to do a clean install via USB.

It really doesn't take long to make the installer drive (especially if you already have "Install macOS Mojave.app" downloaded. Just download the patcher here and follow the directions. You will get a message that the patcher isn't intended for your model (since it's designed to be used with Macs that Apple dropped from the compatibility list) but it will happily proceed past that to make the USB installer.

If you decide to try it, please report back your results!
I’m happy to test and report back. I initially didn’t want to use the patcher, as my system should be supported officially. But would it be possible to patch the installer, and then NOT run the post-install band have a clean, vanilla install? Or does the patcher change some of the system files?
I’m through with Hackintosh and patches for now. I want a clean system, and my 4.1->5.1 was the solution.

But if I have to modify the installer to get encryption and fix 680 bug, that’s not a problem.
 
I’m happy to test and report back. I initially didn’t want to use the patcher, as my system should be supported officially. But would it be possible to patch the installer, and then NOT run the post-install band have a clean, vanilla install? Or does the patcher change some of the system files?
I’m through with Hackintosh and patches for now. I want a clean system, and my 4.1->5.1 was the solution.

But if I have to modify the installer to get encryption and fix 680 bug, that’s not a problem.

I do not know for certain, but my hunch is that the only modifications made to the installer are to disable all the checks for incompatible Macs.
 
So to sum up the things I've done so far, and my specs:

- Mac Pro 2009
- Flashed to 2010
- 6 Core X5690 installed - works
- eVGA GTX680 2GB flashed to Mac EFI

First successful Mojave install:
1. Install High Sierra to secondary drive (probably 10.13.6, firmware was upgraded during install)
2. Download and run Mojave installer from High Sierra, firmware is updated to 138.0.0.0.0
3. Install Mojave to primary drive from High Sierra - Works, but not FileVault.

Failed attempts:
1. Booting Install Mojave from USB (created with Diskmaker X)
2. Try to install to clean, unencrypted APFS drive - Fail because of GPU "not supporting" Metal or FileVault enabled
3. Try to install to encrypted APFS, same problem.
4. Try to upgrade from High Sierra to Mojave - not possible to choose encrypted drive.

Second successful Mojave install:
1. Already had High Sierra installed (from 4. last failed attempt)
2. Used office MacBook (High Sierra) to create a dosdude1 Mojave patched USB
3. Booted off USB, used "gpt destroy /dev/diskX" to remove "4 volumes" on some of the drives (tried installing OS)
4. Had to partition to HFS+ then APFS Encrypted on the earlier High Sierra drive to get only one volume
5. Formatted 3 out of 4 drives to APFS Encrypted (last one has some data)

Bear in mind that the Mojave installer now already had skipped language selection etc. The typical menu with Disk Utility, Install macOS etc was not there. I am not sure if this was because of an existing High Sierra install being detected, but I don't think so. This is probably the patch's work. After all drives were set up (except one) I could easily click "continue" and choose a drive to install to, I chose my largest 512GB SSD which was APFS Encrypted - Installation started straight away. When finished, and automatically rebooting, I pulled out the USB, and it booted to "Disk Password".

This looked very different from High Sierra. There are some slight shadows around it, and the text field said "Enter Password" but was very hard to read. Could be because I'm using a TV without game mode at the moment though. It could also be different for me because this is Mojave - the user login symbols are larger.

I need verification from Dosdude1 if something has been changed here. If not, it's vanilla Mojave which after accepting my password booted straight to "Welcome" where I can configure my Mac.

This is where I'm right now, everything seems to be fine, I'm just gonna setup my Mac.


So the only thing that didn't "look vanilla" for me, was that Disk password prompt, which could be a result of Mojave being different from High Sierra, and my TV adding the shadows because it wasn't in game mode.

TL;DR:
- Dosdude1 Mojave Patch tool can be used to circumvent GTX 680 bug AND APFS encrypted drives, thus enabling FileVault.
 
  • Like
Reactions: bookemdano
So to sum up the things I've done so far, and my specs:

- Mac Pro 2009
- Flashed to 2010
- 6 Core X5690 installed - works
- eVGA GTX680 2GB flashed to Mac EFI

First successful Mojave install:
1. Install High Sierra to secondary drive (probably 10.13.6, firmware was upgraded during install)
2. Download and run Mojave installer from High Sierra, firmware is updated to 138.0.0.0.0
3. Install Mojave to primary drive from High Sierra - Works, but not FileVault.

Failed attempts:
1. Booting Install Mojave from USB (created with Diskmaker X)
2. Try to install to clean, unencrypted APFS drive - Fail because of GPU "not supporting" Metal or FileVault enabled
3. Try to install to encrypted APFS, same problem.
4. Try to upgrade from High Sierra to Mojave - not possible to choose encrypted drive.

Second successful Mojave install:
1. Already had High Sierra installed (from 4. last failed attempt)
2. Used office MacBook (High Sierra) to create a dosdude1 Mojave patched USB
3. Booted off USB, used "gpt destroy /dev/diskX" to remove "4 volumes" on some of the drives (tried installing OS)
4. Had to partition to HFS+ then APFS Encrypted on the earlier High Sierra drive to get only one volume
5. Formatted 3 out of 4 drives to APFS Encrypted (last one has some data)

Bear in mind that the Mojave installer now already had skipped language selection etc. The typical menu with Disk Utility, Install macOS etc was not there. I am not sure if this was because of an existing High Sierra install being detected, but I don't think so. This is probably the patch's work. After all drives were set up (except one) I could easily click "continue" and choose a drive to install to, I chose my largest 512GB SSD which was APFS Encrypted - Installation started straight away. When finished, and automatically rebooting, I pulled out the USB, and it booted to "Disk Password".

This looked very different from High Sierra. There are some slight shadows around it, and the text field said "Enter Password" but was very hard to read. Could be because I'm using a TV without game mode at the moment though. It could also be different for me because this is Mojave - the user login symbols are larger.

I need verification from Dosdude1 if something has been changed here. If not, it's vanilla Mojave which after accepting my password booted straight to "Welcome" where I can configure my Mac.

This is where I'm right now, everything seems to be fine, I'm just gonna setup my Mac.


So the only thing that didn't "look vanilla" for me, was that Disk password prompt, which could be a result of Mojave being different from High Sierra, and my TV adding the shadows because it wasn't in game mode.

TL;DR:
- Dosdude1 Mojave Patch tool can be used to circumvent GTX 680 bug AND APFS encrypted drives, thus enabling FileVault.

Great! Yes, the USB installer created via dosdude1's patch does bypass the normal menu you see when you boot from a vanilla USB installer (he added his own menu visible during the entire installation process with links to those utilities plus more.).

As for the changes to the FV password entry screen, it may have looked different because FileVault was enabled before any user was created. Normally you enable FV after the OS is set up, so the password entry screen first has you select a user name, then enter that user's password. But when you create the encrypted volume the way you did, you are using the password you set up when encrypting it. Not sure if that changes after you go through the macOS setup process or not. Have you rebooted again since doing that?

Anyway, glad you were able to get it working, and thanks for sharing your experience. Hopefully this thread will help others in the future who wish to follow down the same path.
 
Great! Yes, the USB installer created via dosdude1's patch does bypass the normal menu you see when you boot from a vanilla USB installer (he added his own menu visible during the entire installation process with links to those utilities plus more.).

As for the changes to the FV password entry screen, it may have looked different because FileVault was enabled before any user was created. Normally you enable FV after the OS is set up, so the password entry screen first has you select a user name, then enter that user's password. But when you create the encrypted volume the way you did, you are using the password you set up when encrypting it. Not sure if that changes after you go through the macOS setup process or not. Have you rebooted again since doing that?

Anyway, glad you were able to get it working, and thanks for sharing your experience. Hopefully this thread will help others in the future who wish to follow down the same path.
Yes, the login was there before there was a user. But doing the same in High Sierra resulted in a different looking screen. So there are differences, but it could be Mojave, not the patch.

Other; My login screen is ugly. No background, and shadow on “enter password”. So there is something that is different after the patch...?

I tried re-running “Install Mojave” from Mojave, but won’t let me because of the encrypted drive.
[doublepost=1538678410][/doublepost]
Yes, the login was there before there was a user. But doing the same in High Sierra resulted in a different looking screen. So there are differences, but it could be Mojave, not the patch.

Other; My login screen is ugly. No background, and shadow on “enter password”. So there is something that is different after the patch...?

I tried re-running “Install Mojave” from Mojave, but won’t let me because of the encrypted drive.

My login screen is also just grey now.
Seemingly because of FileVault (drive is encrypted, no access to my photos?)
Also the screen blinks after logging in, as if it switches GPU drivers. The fan is typically also spinning faster, then slows down after logging in. Not sure if this is because of the patch?
 
Yes, the login was there before there was a user. But doing the same in High Sierra resulted in a different looking screen. So there are differences, but it could be Mojave, not the patch.

Other; My login screen is ugly. No background, and shadow on “enter password”. So there is something that is different after the patch...?

I tried re-running “Install Mojave” from Mojave, but won’t let me because of the encrypted drive.
[doublepost=1538678410][/doublepost]

My login screen is also just grey now.
Seemingly because of FileVault (drive is encrypted, no access to my photos?)
Also the screen blinks after logging in, as if it switches GPU drivers. The fan is typically also spinning faster, then slows down after logging in. Not sure if this is because of the patch?

In my experience (perhaps others can confirm), the FileVault login screen on the cMP has always been gray. It used to be this way for every Mac prior to, I want to say Yosemite or El Cap. For the more modern Macs, that update replaced the gray background with whatever your current wallpaper image was, presumably so it would appear more like a normal macOS login. But even with High Sierra (which is the last OS I used with FV on my cMP) the FileVault login has always been gray. It was disappointing, but all in all a minor quibble since we don't spend much time at that screen anyway (and further logouts and logins once the computer is booted do have the pretty wallpaper).

My experiences using FV were with a MVC-flashed GeForce 750 Ti and using a 4K monitor. So maybe with other configurations the cMP does use the user's wallpaper on the FV password entry screen. But gray was always what I saw.
 
In my experience (perhaps others can confirm), the FileVault login screen on the cMP has always been gray. It used to be this way for every Mac prior to, I want to say Yosemite or El Cap. For the more modern Macs, that update replaced the gray background with whatever your current wallpaper image was, presumably so it would appear more like a normal macOS login. But even with High Sierra (which is the last OS I used with FV on my cMP) the FileVault login has always been gray. It was disappointing, but all in all a minor quibble since we don't spend much time at that screen anyway (and further logouts and logins once the computer is booted do have the pretty wallpaper).

My experiences using FV were with a MVC-flashed GeForce 750 Ti and using a 4K monitor. So maybe with other configurations the cMP does use the user's wallpaper on the FV password entry screen. But gray was always what I saw.
Hmm... I see.
I’ve read the way to fix it is to disable, reboot, then enable FileVault. I’m gonna try, but it then probably won’t let me enable again.

On my GFs MBA 2012 we enabled FileVault after installing Mojave, and she still got the same nice login screen.
But how about those shadows around password though? It looks weird, and the blink halfway through logging in.
[doublepost=1538680300][/doublepost]I’m also nervous of what will happen with future updates. Maybe 10.14.1 will require me to disable FileVault again, or at least 10.15 next year.

So I’m considering (as Mojave can be clean installed vanilla from a second High Sierra drive) just skipping FileVault on this computer. How much would it matter?
Of course there will family photos etc that I’d like to keep private, but really someone would have to steal the computer, or restore data from my drives if I sell them to get the data right?

Does FileVault offer any other safety besides that?

Because I would probably put family photos/videos on a second drive anyways, which I could easily format with APFS Encrypted (because Mojave isn’t going to be installed there).

I’m just considering the pros cons, and in all the necessity of encryption. Laptops make sense because they are outside the house, but a desktop computer? Is it just a problem if I sell it to someone else?
 
Hmm... I see.
I’ve read the way to fix it is to disable, reboot, then enable FileVault. I’m gonna try, but it then probably won’t let me enable again.

On my GFs MBA 2012 we enabled FileVault after installing Mojave, and she still got the same nice login screen.
But how about those shadows around password though? It looks weird, and the blink halfway through logging in.
[doublepost=1538680300][/doublepost]I’m also nervous of what will happen with future updates. Maybe 10.14.1 will require me to disable FileVault again, or at least 10.15 next year.

So I’m considering (as Mojave can be clean installed vanilla from a second High Sierra drive) just skipping FileVault on this computer. How much would it matter?
Of course there will family photos etc that I’d like to keep private, but really someone would have to steal the computer, or restore data from my drives if I sell them to get the data right?

Does FileVault offer any other safety besides that?

Because I would probably put family photos/videos on a second drive anyways, which I could easily format with APFS Encrypted (because Mojave isn’t going to be installed there).

I’m just considering the pros cons, and in all the necessity of encryption. Laptops make sense because they are outside the house, but a desktop computer? Is it just a problem if I sell it to someone else?

I recall that my 2010 Mac Mini also has always had the gray FV login screen. But my 2014 Mini uses the current wallpaper. So I think Apple only enabled that for Macs 2012 and newer (or maybe 2011 and newer).

Not sure about the other graphical glitches you saw. Maybe take a video and post it so we can see what you're seeing. But I really don't think that has anything to do with dosdude1's patcher. It could relate to Mojave or the 138.0.0.0.0 firmware. Remember Apple expects that no one using Mojave on a cMP is seeing that screen, so they may not have tested it during Mojave development. As you said before, it may also be caused by the particular monitor & connection method you are using.

As for how updates will be handled, it is of course possible that they will not install properly if FV is enabled, but I think it's equally likely that they will install fine. We just won't know until 10.14.1 is released (or someone tries the beta). As such, I would be hesitant to recommend enabling FV in this way on a daily driver machine or with priceless personal data.

W1SS mentioned an alternative method that involves locating your entire home folder on a different disk or partition that you would then encrypt. That involves needing to create a dummy user that you use to boot the computer, login, and then unlock the encrypted drive. You could then log in to your actual user account and proceed as normal. If you're interested in that he offered to detail the steps involved.

I don't think FV offers any benefits other than protecting sensitive data from being physically retrieved from your disk (like if someone gained access to your cMP or if it was stolen). It's just for peace of mind, and most folks here don't seem to miss it. As someone who uses it on all my Macs though, I have to admit I am bummed that Apple didn't use a tiny fraction of its vast resources to keep it working on the cMP--especially given their newfound emphasis on privacy and keeping its users' data protected from thieves and law enforcement alike.

Oh well, as others have said, we should feel lucky that Apple is supporting our old cheese graters on Mojave at all.

P.S. There is one additional benefit to FV---especially on SSDs. It makes it much safer to sell or donate them in the future. Unlike HDDs, securely erasing an SSD is more complex and harder for the average person to do. By using FV, you can be assured that simply formatting the drive destroys the encryption key and thus any data that was on the drive is gone. To be sure, there are other ways to accomplish this, but FV was the easiest way.
 
Disabled FileVault, then tried enabling - nope, cannot do it, same as before.

The blinking now happened BEFORE login, so I guess that’s before/after unlocking the drive. So that explains that, you’re basically skipping the normal login screen.

Anyways

Conclusion - Screw it. I’m skipping FileVault for all my drives. If it will be officially supported - I will enable it through preferences.

The only benefit I can find is as you mentioned - if selling the SSD’s. Whenever I start using SSD’s I encrypt, mostly for MacBooks etc where the drive is “non-replaceable”.

I’m going back to High Sierra on a second drive, and clean installing Mojave that way. This only because of the GTX 680 bug, which really doesn’t matter, once it’s installed it’s the same thing.

I’ll have a clean installed (although not from USB) Mojave Mac, ready to be set up. No patching or other Hackintosh-similar annoyance.

Thanks for all the help! I hope my findings and conclusion might help others as well.
 
  • Like
Reactions: bookemdano
I see nothing has changed in last 5 month - Mojave usb installer still not recognise nVidia GTX680 as a card with Metal support.
Today succesfully updated to Mojave from High Sierra, bootrom changed to 140.0.0.0.0
Then i decided to do a clean install from USB drive and got error message, that there no graphic card with metal support (or FileVault must be disabled - but it has been disabled and even formatted).
Then i found this thread...
Now i'm installing Sierra for later update to Mojave from macOS.
Spent many-many hours and i'm too much hungry!
P.S. I wonder if Apple knows about this problem? And if yes, why not fix it, especially if the card is officially supported? I will contact their support.
 
I have to assume that at least one GTX 680 owner has filed a bug report--probably even during the beta period. But it certainly can't hurt for you to file one yourself. You can do so at bugreport.apple.com
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.