Nvidia discussed today the delay in approval of their web drivers to support the newer non-Kepler video cards under Mojave.
https://www.macrumors.com/2018/11/01/nvidia-comment-on-macos-mojave-drivers/
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
Nvidia discussed today the delay in approval of their web drivers to support the newer non-Kepler video cards under Mojave.
https://www.macrumors.com/2018/11/01/nvidia-comment-on-macos-mojave-drivers/
@Macarny
Hello,
Could you please tell me which BT4 dongle do you use ? I want to buy one and install CAT for my macbook7,1 mid 2010.
Thank you
I have a Mac Pro 4,1 flashed to 5,1 with Dual X5690's and 96GB of DDR3 1333 and 1.5TB of SSD's and then a 5TB spindle with a Vega Frontier edition. All was well in Mojave until 10.14.1 suddenly video performance drops 14%. I made sure nothing else was running and rested and rebooted and retested a few more times. Same every time 14% performance drop in all Computer functions. I don't know what they did to the Vega driver but my God it's bad.
Does anyone know if the Hybrid patch already works on 10.14.1? I was in 10.14 but I had to back to High Sierra and now I'm waiting for Hybrid-Flat patchs for update to 10.14.1
I successfully updated a MacBook Pro 7,1 using OTA update and patching and cache rebuilding. Only one unsuccessful boot then booted into patcher and rebuilt the cache.
Just to let you know that I tested an Allegro USB-C PCIe card from Sonnet in my Mac Pro 3.1 with Mojave 14.1 and it worked. I inserted the card in the slot number 2. Here is a test result with a Samsung T5 500GB.
Are you kidding me? Dark/Light mode enhancement is probably priority 9 out of 10, while the useless default Recovery means to most a priority of 0 to 1. If people would care so much for Recovery, they would just stay with the previous OS version. There you can have endless Recovery for what we care. On the other hand Mojave brings a refresh of Light and a total redesign of Dark mode. There is pretty much nothing else visibility-wise to compel a person the switch to otherwise technically less capable Mojave. Since those changes have been denied to our unsupported macs by the greedy Apple, fixing Light/Dark mode on unsupported machines is almost the highest priority. However you seem to be unfamiliar with the huge effort by @pkouame in creating a robust fix, easy to implement with almost no alterations to the original system.
Again don't be driven solely by your own egoistic interests, but instead try to have compassion with the interests of the others, for the difficult such a statement might look like at first.
And while we are still on the subject. Now that you have fixed your default Recovery, I dare you to do the main task this Recovery was designed for, try to do a complete Mojave reinstall within Recovery of your unsupported mac. When you finish please let me know how do you feel about it.
Last edited:
Patch Night Shift needs to be revised to 10.14.1 (it is working, however it does show some inconsistency, since because of it, the boot is slower, reverting back to the original CoreBrightness.framework, boot time back to normal).
Great work @dosdude1, @parrotgeek1 and all the contributors, this is a major effort!
I have installed Mojave on a MacBook Pro 13" (Early 2011) MacBookPro8,1 and I'm having some trouble getting it going... I was able to install and run the post-install patches okay, but it seems it can't boot and doesn't see the boot volume (or Recovery) in the Option-key multi-boot selector.
Here's the process I took;
From what I understand, the MacBookPro8,1 model will natively support APFS booting.
What should I try next? Do I ditch APFS and try a fresh HFS+ install instead? Or should I try using the APFS booting patch on this Mac, even though it should be supported?
My apologies if this has already been covered in one of the 398 earlier pages
-AphoticD
I have installed Mojave on a MacBook Pro 13" (Early 2011) MacBookPro8,1 and I'm having some trouble getting it going... I was able to install and run the post-install patches okay, but it seems it can't boot and doesn't see the boot volume (or Recovery) in the Option-key multi-boot selector.
Here's the process I took;
- Created Mojave installation USB (16GB) using macOS Mojave Patcher v1.2.3, downloading macOS 10.14.1 directly from within the app.
- Booted from the USB drive.
- Used Disk Utility to format a new 128GB mSATA SSD as APFS (GUID partition map).
- Clicked to install Mojave.
- After a minute or so, received a "No packages were eligible for install" error.
- Read the FAQ on dosdude1's server and used the 'date' command to set to today's date.
- Rebooted from USB and successfully installed Mojave.
- Ran the macOS Post Install tool and set the default MacBookPro8,1 patches.
- Ticked the "Rebuild caches" checkbox and clicked Restart.
- On reboot, the SSD was not recognised and the USB installer started up again.
- Removed the USB and rebooted, same result.
- Rebooted back into the Mojave installer via the USB drive.
- Checked the output of 'diskutil list' to confirm the APFS partition map is setup correctly. I don't know much about APFS, but it looks reasonably okay to me ....
- I then did some further reading about manually blessing a volume in case this step was somehow skipped.
- I executed the following commands;
Code:diskutil apfs updatePreboot disk1s2 bless --folder /Volumes/Macintosh\ HD/System/Library/CoreServices --bootefi update_dyld_shared_cache -root /Volumes/Macintosh\ HD -force - Choosing Quit from the Installer and choosing Startup Disk, I was able to see "Macintosh HD" 10.14.1 as bootable. It is selected, so I clicked Restart.
- The MacBook Pro still can't see the APFS volume as bootable at boot time.
From what I understand, the MacBookPro8,1 model will natively support APFS booting.
What should I try next? Do I ditch APFS and try a fresh HFS+ install instead? Or should I try using the APFS booting patch on this Mac, even though it should be supported?
My apologies if this has already been covered in one of the 398 earlier pages
-AphoticD
Last edited:
Working awesome
[doublepost=1541129635][/doublepost]
They will be available soon
A few minutes ago I updated my Mac Mini 3,1 using the OTA and again loop on boot, but as mentioned before on the next restart loaded patcher and force rebuild of cache and all is well.
A little note first boot after system up and running took a long time to get to desktop after logon. Also, from log out to log on again also took a looooong time. Subsequent loads were fast as prior builds.
A little note first boot after system up and running took a long time to get to desktop after logon. Also, from log out to log on again also took a looooong time. Subsequent loads were fast as prior builds.
Last edited:
You need to have installed High Sierra on the system previously, so it's firmware is updated to support booting from APFS volumes. Otherwise, it won't detect the volume.Great work @dosdude1, @parrotgeek1 and all the contributors, this is a major effort!
I have installed Mojave on a MacBook Pro 13" (Early 2011) MacBookPro8,1 and I'm having some trouble getting it going... I was able to install and run the post-install patches okay, but it seems it can't boot and doesn't see the boot volume (or Recovery) in the Option-key multi-boot selector.
Here's the process I took;
- Created Mojave installation USB (16GB) using macOS Mojave Patcher v1.2.3, downloading macOS 10.14.1 directly from within the app.
- Booted from the USB drive.
- Used Disk Utility to format a new 128GB mSATA SSD as APFS (GUID partition map).
- Clicked to install Mojave.
- After a minute or so, received a "No packages were eligible for install" error.
- Read the FAQ on dosdude1's server and used the 'date' command to set to today's date.
- Rebooted from USB and successfully installed Mojave.
- Ran the macOS Post Install tool and set the default MacBookPro8,1 patches.
- Ticked the "Rebuild caches" checkbox and clicked Restart.
- On reboot, the SSD was not recognised and the USB installer started up again.
- Removed the USB and rebooted, same result.
- Rebooted back into the Mojave installer via the USB drive.
- Checked the output of 'diskutil list' to confirm the APFS partition map is setup correctly. I don't know much about APFS, but it looks reasonably okay to me ....
View attachment 800448
- I then did some further reading about manually blessing a volume in case this step was somehow skipped.
- I executed the following commands;
Code:diskutil apfs updatePreboot disk1s2 bless --folder /Volumes/Macintosh\ HD/System/Library/CoreServices --bootefi update_dyld_shared_cache -root /Volumes/Macintosh\ HD -force- Choosing Quit from the Installer and choosing Startup Disk, I was able to see "Macintosh HD" 10.14.1 as bootable. It is selected, so I clicked Restart.
- The MacBook Pro still can't see the APFS volume as bootable at boot time.
From what I understand, the MacBookPro8,1 model will natively support APFS booting.
What should I try next? Do I ditch APFS and try a fresh HFS+ install instead? Or should I try using the APFS booting patch on this Mac, even though it should be supported?
My apologies if this has already been covered in one of the 398 earlier pages
-AphoticD
Add this to the patcher @dosdude1? In case you missed it.
[doublepost=1541132908][/doublepost]
I agree. I don't see the necessity to patch Mojave's recovery partition. You can simply make a backup of the HS one and then restore it. The last thing you want is a glitchy recovery partition. Just stick with a supported one!
You can even just restore a BaseSystem.dmg (from a HS installer) to a small partition and it will function as a recovery system.
Then again, this thread is for Mojave on unsupported hardware. Patching the recovery partition is relevant to this topic. We should not try to stifle discussion about anything unless it's off-topic. We might not use @jackluke's work directly, but I believe he should still be able to document it here! It may prove useful in some way or another.
Any tidbit of information may pave the way to a better understanding of the inner workings of the OS
Last edited:
I had that distributed via Patch Updater, but it caused Bluetooth to stop working completely on some systems (that had working Bluetooth with Mojave to begin with). So I'm not sure what to do. It's not limited to specific machines either, in fact it seems to be completely random. For example, when I had initially pushed that patch, some MacBookPro8,1 users reported that it fixed their issue, while others reported that it made Bluetooth stop working completely. This is the same with all the machines (iMacs, MacBook Airs, Mac Minis, etc); some users said it worked on their system, others said it broke Bluetooth on the exact same system. I have no idea how to reliably distribute this patch.Add this to the patcher @dosdude1? In case you missed it.
[doublepost=1541132908][/doublepost]
I agree. I don't see the necessity to patch Mojave's recovery partition. You can simply make a backup of the HS one and then restore it. The last thing you want is a glitchy recovery partition. Just stick with a supported one!
You can even just restore a BaseSystem.dmg (from a HS installer) to a small partition and it will function as a recovery system.
Then again, this thread is for Mojave on unsupported hardware. Patching the recovery partition is relevant to this topic. We should not try to stifle discussion about anything unless it's off-topic. We might not use @jackluke's work directly, but I believe he should still be able to document it here! It may prove useful in some way or another.
Any tidbit of information may pave the way to a better understanding of the inner workings of the OS
Edit: my macbook has a Ssd and he already was on APFS on HighSierra.
Great work @dosdude1, @parrotgeek1 and all the contributors, this is a major effort!
I have installed Mojave on a MacBook Pro 13" (Early 2011) MacBookPro8,1 and I'm having some trouble getting it going... I was able to install and run the post-install patches okay, but it seems it can't boot and doesn't see the boot volume (or Recovery) in the Option-key multi-boot selector.
Here's the process I took;
- Created Mojave installation USB (16GB) using macOS Mojave Patcher v1.2.3, downloading macOS 10.14.1 directly from within the app.
- Booted from the USB drive.
- Used Disk Utility to format a new 128GB mSATA SSD as APFS (GUID partition map).
- Clicked to install Mojave.
- After a minute or so, received a "No packages were eligible for install" error.
- Read the FAQ on dosdude1's server and used the 'date' command to set to today's date.
- Rebooted from USB and successfully installed Mojave.
- Ran the macOS Post Install tool and set the default MacBookPro8,1 patches.
- Ticked the "Rebuild caches" checkbox and clicked Restart.
- On reboot, the SSD was not recognised and the USB installer started up again.
- Removed the USB and rebooted, same result.
- Rebooted back into the Mojave installer via the USB drive.
- Checked the output of 'diskutil list' to confirm the APFS partition map is setup correctly. I don't know much about APFS, but it looks reasonably okay to me ....
View attachment 800448
- I then did some further reading about manually blessing a volume in case this step was somehow skipped.
- I executed the following commands;
Code:diskutil apfs updatePreboot disk1s2 bless --folder /Volumes/Macintosh\ HD/System/Library/CoreServices --bootefi update_dyld_shared_cache -root /Volumes/Macintosh\ HD -force- Choosing Quit from the Installer and choosing Startup Disk, I was able to see "Macintosh HD" 10.14.1 as bootable. It is selected, so I clicked Restart.
- The MacBook Pro still can't see the APFS volume as bootable at boot time.
From what I understand, the MacBookPro8,1 model will natively support APFS booting.
What should I try next? Do I ditch APFS and try a fresh HFS+ install instead? Or should I try using the APFS booting patch on this Mac, even though it should be supported?
My apologies if this has already been covered in one of the 398 earlier pages
-AphoticD
I'm a little bit confused, what do you mean "128GB mSATA"? I have also a MacBook Pro early 2011, with a normal Samsung evo ssd and a conventional harddrive in a caddy. both versions of Mojave installed flawlessly. I had only to fix the bluetooth.
and I set the graphics to 1554mb.
it works like a charm!
Anybody see or notice the silent update apple did on the macbook pro.
If u scroll down coming in november...
Radeon vega pro...
60% faster
If u scroll down coming in november...
Radeon vega pro...
60% faster
Take screenshot from verbose output. Boot with pressed cmd+v.
I have mbp8,2 with dead gpu, install update 10.14.1 over 10.14 from usb with patcher 1.2.3.
p.s. my english is not perfect
Take screenshot from verbose output. Boot with pressed cmd+v.
I have mbp8,2 with dead gpu, install update 10.14.1 over 10.14 from usb with patcher 1.2.3.
p.s. my english is not perfect
@TimonCello, hmm, dont know, maybe you have smb share and it stuck when try connect it.
However, make new usb installer using mojave patcher 1.2.3 and install over your existing installation.
However, make new usb installer using mojave patcher 1.2.3 and install over your existing installation.
Anyone tried the 10.14.1 to 10.14.2 beta OTA update?
Just for reference, here are my I/O for an NVMe Samsung 960 Evo
drive on a Highpoint card with the dosdude NVME patch applied to a MacPro 3,1 boot rom
Just for reference, here are my I/O for an NVMe Samsung 960 Evo
I tried, but nothing happend when I push C on the jeyboard when I reboot. Always come back on the first screenshot I posted
I took the plunge this morning upgrading my MacPro 3,1 with stock ROM on HFS+ and a Nvidia 680 GPU from a patched 10.14 to 10.14.1 with Dosdude's patcher and a Force rebuild the cache on reboot after the post-install patch and everything went OK in about an hour time. Only the last 12 minutes of installation were half an hour at he end.........
Big thanks to Dosdude1 for his amazing work !!!!!!!
Big thanks to Dosdude1 for his amazing work !!!!!!!
Attachments
Press option button (alt), then select usb key to boot.I tried, but nothing happend when I push C on the jeyboard when I reboot. Always come back on the first screenshot I posted