macOS Mojave is Now Available on the Mac App Store

[manmo71]

It also broke my Wi-Fi. I was using a $20 Fenvi PCI-e Wi-Fi card I bought off Amazon. It has an Atheros chipset (not sure the exact model). It was working out of the box with no additional kexts or patches since Sierra.

Not sure if Apple have disabled support for it in Mojave. I'm not going to bother attempting to get it fixed, but just go out and buy an BCM94331CD which comes directly from the 2012 iMacs + PCI-e adapter. Hopefully that would give me better and more reliable Wi-Fi + Bluetooth.

Still, let me know if you find any fix for this, as I'd love to be able to use the Atheros until I get the Broadcom.

Try installing the AirPortAtheros40.kext into S/L/E and restart. It fixed it for me.

 

[Justcurious1]

Updated using the latest Clover bootloader, installed Mojave without incident. But I'm a bit confused. For those of you running AMD GPUs have you found that you have had to turn on the iGPU to be able to export H.264? My usual config for years has been boot from PCIe slot with AMD GPU. But as of High Sierra. H.264 export stopped working. I'm running 18,3 SIMBIOS. I have to have both Inject Intel and RadeonDeInit set in config.plist as well as Intelfix and watevergreen in the Other folder.

Interestingly, I just tried a Sierra backup and two things of interest, 1) FCPX will export H.264 with the iGPU turned off but the render is 2X slower, 2) Activity Monitor shows the four cores only maxing out and my CPU fan goes to top speed and Intel Power Gadget shows I'm hitting my 5 GHz overclock and temps running 80 degrees.

Running on Mojave, I need to use the same High Sierra setup with the iGPU on. Curiously, Activity Monitor shows that the cores and threads are now being used, clock does not go over 3.2, the fan is quiet, CPU temp is around 40 degrees yet the export is about 2x faster. I'm not certain QuickSync is enabled.

So, I guess the conclusion is that I should just leave well enough alone and be happy it works. Any insights? Is this bizarre or normal? Can I get even better performance if I can get the CPU to work harder? Thanks.

 

[Jamieson]

Updated through the app store. Everything working perfect...except the obvious Nvidia web driver. Common Nvidia...

 

[ashman70]

Do I have to do anything special when upgrading clover?

 

[labanauskas]

Updated straight from 10.13.6 hfs+. No probs only this string shown up.

 

[VAnative21]

Updated and having issues with my Wi-Fi PCIe not being recognized @ all (Rosewill RNWD-N9003PCE) and my graphics card not recognized as well (AMD Radeon HD 6450)... does Mojave not support either?

 

[LSP]

With proper Clover configuration, apfs.efi is not needed and should not be used. With ApfsDriverLoader-64.efi, PartitionDxe-64.efi, and AptioMemoryFix-64.efi loaded, the live APFS driver can be pulled directly from your OS install and always be the current version each boot.

Does that mean by adding these files I can remove apfs.efi from Drivers64UEFI and it will now use the apfs.efi in the usr/standalone/i386 folder directly

 

[ashman70]

One other question, when doing the upgrade and it reboots, do you choose OSX Mojave pre booter to boot into to continue the upgrade?

 

[Khaibit]

With proper Clover configuration, apfs.efi is not needed and should not be used. With ApfsDriverLoader-64.efi, PartitionDxe-64.efi, and AptioMemoryFix-64.efi loaded, the live APFS driver can be pulled directly from your OS install and always be the current version each boot.

Does that mean by adding these files I can remove apfs.efi from Drivers64UEFI and it will now use the apfs.efi in the usr/standalone/i386 folder directly

Correct! It lets Clover do it the same way real Macs do: by giving just enough support to read that one specific file off the OS disk and then load APFS support directly.

 

[Khaibit]

One other question, when doing the upgrade and it reboots, do you choose OSX Mojave pre booter to boot into to continue the upgrade?

For me at least, the installer correctly set the boot volume. The first reboot, it should be the installer pre-booter; on subsequent ones, it is set to FileVault pre-booter (which is essential if you use FileVault but doesn't hurt anything if you don't). I just let it do its thing and it chose the right boot volume each time for me.