I will do that on Mojave I use the aerial screensaver from Apple TV 4
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
Let’s continue this elsewhere: Please tell me what you think by emailing softwarenetwork@outlook.com
My GPU is even lower then this, 2004 Nvidia GPU, GeForce 6200. Indeed, the motherboard is from 2008. But the GPU still worked fine with High Sierra and now it works with Mojave, via the Dosdude1 patch.
OK, then I don't know.
I thought someone had said that using the "convert to APFS" in Disk Utility wiped the drive. Is that not true?
Prefect time for advertising
If you’re interested in Retail Technologies for iPhone and iPad, please visit: www.devapple.weebly.com/screensaver
We support businesses such as metroPCS and MED Store IT, with 3,000 peak web views.
I know next to nothing about retail demo software, but coincidentally enough, that site's where I've been getting most of my copies of the beta release notes. So if you're the one putting them up there, thank you!
I’m one of the people who keep the website chugging along- thanks for using our site!
In my experience, converting the HFS+ (journaled) SSD drive to APFS in Disk Utility do not wipe the drive.
I just wonder why I see the verbose output when I reboot after applying successfully the APFS rom patch (and not the post-install one).
Precision : before installing Mojave Beta9, i was with HighSierra on the same SSD, and with APFS file format, patched with the @dosdude1 APFS post-install patch.
Cordialement,
PJN
Last edited:
Thank you. I have attached two screen shots of the details I receive and wrote below.
I ran the QT1.app which came with this mcard2 and enabled the WiFi and Bluetooth under Sierra and High Sierra. When I run it now I receive an error "cp: info.plist: No such file or directory (1)"
If I go into "edit" the application output is this:
path to resource "Info.plist"
--set path "Contentes"Resources:Info.plist"
do shell script "cp Info.plist /System/Library/Extensions/IO80211Family.kext/Contents/PlugIns/AirPortBrcm4360.kext/Contents" with administrator privileges
do shell script "touch /System/Library/Extensions/" with administrator privileges
do shell script "/sbin/shutdown -r now" with administrator privileges
No !
But when I had installed Mojave beta9 in HFS after erasing the SSD (HS with APFS post-install patch) i did not have the verbose output at booting...which comes only after the installation os the APFS rom patch and the conversion HFS/APFS.
Do you thing i have to un-install the APFS post-install patch ? And how to do that ?
Many thanks for your help,
PJN
I don't really know, I'm just guessing. But if you've patched your ROM you don't need the post-install patch. I'm sure someone will be along in a minute to tell you how to do so.
Edit: I found this answer from @dosdude1 earlier in the thread. I assume he was talking about the post-install patch
All you'd need to do is set your Startup Disk to the APFS volume using System Preferences (after patching your BootROM of course). Optionally, you can mount the EFI System Partition of your hard disk and delete "/BOOT/BOOTX64.EFI", startup.nsh, and apfs.efi
Last edited:
Use 'sudo diskutil list' to find the EFI partition on the Mojave drive. Assuming it was disk0s1. mount the EFI partition with
sudo diskutil mount disk0s1
Then you can use the Finder to drag the "/BOOT/BOOTX64.EFI", startup.nsh, and apfs.efi files on the mounted EFI volume to the trash.
[doublepost=1535717629][/doublepost]
Use 'sudo diskutil list' to find the EFI partition on the Mojave drive. Assuming it was disk0s1. mount the EFI partition with
sudo diskutil mount disk0s1
Then you can use the Finder to drag the BOOT folder in the mounted EFI and the apfs.efi
It would be nice if we had more options for Metal compatible cards on the MacPro 3,1. The GTX 680 cards seem like they would generate a ton of heat inside the chassis compared to the HD2600 XT which, at its age, can't be good for the future longevity of these machines.
Thank's
I'll try this evening.
But, if I trash these files, will the APFS rom patcher still work ?
My SSD with Mojave is as (disk3s1) :
Of course. The BootROM patcher (if indeed you've run it) changes the BootROM i.e. re-flashes it, to enable booting APFS volumes. Hence the risk of running the patcher.
As I stated before, if you have an APFS patched ROM, you must DESELECT the "APFS Patch" option in the post-install tool to prevent the extra EFI stuff being installed for systems that don't have APFS support in the BootROM. I have no way of checking this with the post-install tool, so you will need to deselect it manually before applying post-install patches.
yes, indeed, i ran the APFS rom patcher as described here :
https://forums.macrumors.com/thread...ed-macs-thread.2121473/page-212#post-26352834
Olrik - from my experience on mbp 5.3 with HS APFS already installed last year - just as a point of reference:
1. I backed up my data
2. I wiped out all vestiges of old APFS on my boot drive within terminal with diskutil etc. (all the extra EFI stuff...)
3. reformatted to HFS+ clean - just to make sure I started from a know classic state...
4. flashed my rom with v2
5. rebooted with latest patcher stick and reformatted my boot disk to APFS
6. installed Mojave
7. post-installed
8. voila!
There are many variations of this, but it got me up and running clean on a new APFS partition. With no verbose messages (which I had before)
You have already performed Step 4. Step 3 was just a precaution. Make sure you de-select the post-install APFS PATCH option (per dude's warning and if you use the latest patcher - my older patcher 1.1.2 did not have that option)
Sorry if this is redundant assistance, but just wanted to relate my successful approach since we started from the same state.
Bonne chance.
One issue that I have been wondering about with the unsupported Mac support is how does this impact the Intel microcode fixes. One wouldn't necessarily expect Apple to bundle fixes for processors not on the list of supported machines.
Merci,
I'll first try do do that this evening, we'll see...and I'll tell you about the result :
delete "/BOOT/BOOTX64.EFI", startup.nsh, and apfs.efi
Sorry to bang on about this, but I want to get it clear in my mind. If you have an installed system (HS or Majove) on an SSD formatted as APFS, and you're using the apfs post-install patch to allow booting, AND you then patch your ROM, is it sufficient to run the post-installer and deselect the apfs patch (and run the patcher, obvs)? I'm guessing not i.e. I'm guessing your post-installer doesn't check the currently selected patches in the dialog against what patches are already installed, and then uninstalls those that are now deselected. Is this correct? My apologies if it really is that clever. I know you've provided a shell script to uninstall patches in the past, but I don't know if you'd use that to just uninstall the apfs patch.
No, the post-install tool will not uninstall anything. It simply applies the patches that are ticked, and does not apply the ones that aren't. In the case of APFS ROM patching, you do NOT need the "APFS Patch" from the post-install tool if you've applied the APFS ROM Patch on your system.
Excellent. So, in the case where you just want to uninstall the apfs post-install patch (and do nothing else), what you have to do is:
mount the EFI System Partition of your hard disk and delete "/BOOT/BOOTX64.EFI", startup.nsh, and apfs.efi
Correct?
Worked on my MacPro 3,1 yesterday to switch an APFS patched drive to boot normally with the APFS patched ROM.