- Sep 1, 2014
- GT 740
- Mobile Phone
Mine are wired.
It seems unlikely it me that it's the processor difference. Normally it means the SMBIOS is wrong, so it may be a problem with your config.plist on the EFI partition of your install flash drive.
I haven't used Bluetooth myself. As you can see in the post above, it could cause problems waking your monitor. If you want to try, I would get your machine working with wired devices and a working flash drive you can boot from. Then try backing up and changing the USB AML on your system drive. If it doesn't work, the worst case would be that you disable Bluetooth and all your USB ports and then no keyboard or mouse works. If that happens, you'd boot from the flash drive (which has it's own working copy of the USB AML) with your wired keyboard and mouse and then restore your working USB AML on the system drive, at which point if you rebooted to the system drive you'd be back to where you started. (Then you could try again, of course.)
I wanted to keep my old High Sierra install just in case, so I put in a new drive and did a fresh install and then restored my user data with the Migration Assistant.
- ASRock Fatal1ty Z370 Gaming-ITX/ac
- i7-8700 (not K; I have a small case with a small CPU cooler and prefer the 65W chip)
Sapphire Pulse RX 580 8192 MB (with two fans, about all that can fit in the case)I ended up taking this card out, and got the machine working with integrated graphics
- Samsung 970 Evo m.2 NVMe
- Some working Broadcom Wireless mini card -- frankly I don't remember the model, but it might have been one of these. It was frightfully difficult to replace the Intel card that the board shipped with due to the odd enclosure and very fragile connectors on those cards. I busted one of the antenna mounts off the Intel card, and couldn't get the mount out of the cable end without breaking that too and had to replace it with one I had lying around. While the wireless now works is macOS, I don't recommend this unless you have a pretty delicate touch and some spare parts just in case.
- An Acer 43" 4K monitor (ET430K). To avoid the black-screen-with-HDMI problem, I'm using a DisplayPort connection, though there are troubleshooting directions here if you prefer HDMI.
I could not get the 10.14.2 install to work with a default UniBeast install drive -- I had to customize config.plist, kexts, and etc. to avoid reboots and hangs during installation and the first boot. So I've ended up with a boot drive that looks a lot like the installed system. But it works.
- Back up old data (with Time Machine, SuperDuper, whatever)
- Since I was doing a clean install and copying data over, I deauthorized iTunes and signed out of iCloud and iMessage from my old High Sierra install
- Create a USB drive with UniBeast 9 as described here. NOTE: if reusing an old USB install drive, make sure to clear off the EFI partition. If erasing in Disk Utility, make sure you erase the whole USB drive not just the existing partition. If using Disk Utility in Mojave on another machine, use View / Show All Devices in order to be able to do that.
- After the UniBeast drive is done, run RehabMan's Clover package (I used v4701), making sure to select the USB drive as the destination. Customize to install for UEFI booting only, and under UEFI drivers add EmuVariableUefi-64
- After upgrading Clover, your EFI partition should still be mounted; check whether HFSPlus.efi is in EFI/CLOVER/drivers64UEFI -- if not, get it and put it there.
- You can remove all the kexts from EFI/CLOVER/kexts/Other. Then put in these kexts (this will get current versions):
- FakeSMC (none of the underscore sensor plugins needed, app not needed, just the one kext)
- Get Clover Configuratorand the attached config.plist (should work with 8xxx or 9xxx CPUs). Open the config.plist with Clover Configurator.
- Go to the SMBIOS screen, and hit Generate New under the Serial Number and under the SMUUID.
- Hit the Check Coverage button to the right. Enter the CAPTCHA on the Web page that comes up and ensure that it says the serial number is invalid (NOTE: you WANT it to be invalid -- as in, not used by a real Mac! If it shows machine data go back to Clover Configurator and hit the Generate New buttons again and then Check Coverage again).
- If you know what your system drive will be named, go to the Boot screen and enter the name over Default Boot Volume
- Save the file
- Copy the config.plist customized above to EFI/CLOVER/config.plist on the USB drive
- If installing from a USB3 drive, copy aaron-usb-config.aml (download and unzip the attachment below) to EFI/CLOVER/ACPI/patched/ which will enable all the USB3 ports on the board EXCEPT the one to the right of the HDMI port. If installing from a USB2 drive it should work anywhere.
- Boot to the install drive.
- It's easy if it's the only bootable device. If not, I don't have luck with the F11 boot list; I instead go into the BIOS and rearrange the boot list to put the USB on top and then save and exit.
- Once booted, it takes a while to get to the initial install screen.
- If needed, run Disk Utility from there to clear off the target partition (or initialize the drive, if it's new).
- Proceed with the Mojave installer
- It rebooted at least twice for me.
- It ran an initial progress bar until it said "2 minutes remaining" and then suddenly rebooted
- On reboot, select to boot to the system drive from the Clover menu
- It took a long time to come up to a GUI here, then showed a progress bar with no progress completed and "13 minutes remaining", then rebooted
- Select to boot to the system drive again. This time after the long wait it came up to the progress bar ad immediately completed a small fraction ("12 minutes remaining") and then did the rest of the install.
- It got to a 10-second countdown to reboot with a "reboot now" button, but there was no mouse pointer or anything so I just waited it out.
- At this point I could get into Mojave with working Ethernet by booting off the UniBeast drive. I did the user migration here, though you can do it later (if you plan to do it later, I recommend not creating a first user account with the same name during the installation)
- Using the same Clover installer you used for the flash drive, install Clover to the system drive. Select the same options as before, but this time also check Install RC scripts on target volume.
- It again leaves the EFI partition (on the system drive) mounted.
- Also mount the EFI partition from the flash drive. I identify the EFI partition from Terminal with "diskutil list" and mount it with "sudo diskutil mount /dev/diskNs1" where diskN is the identifier for the USB drive, as shown by "diskutil list". After that a second "EFI" shows up in the Finder sidebar. The one with the eject symbol and the same icon as "Install macOS Mojave" is the flash drive, the other is the system drive.
- Replace the config.plist that Clover generated on the system drive with the one from the flash drive.
- Copy the kexts IntelMausiEthernet, FakeSMC, Lilu, WhateverGreen, and USBInjectAll from the flash drive EFI/CLOVER/kexts/Other to the system drive EFI/CLOVER/kexts/Other
- Add the AppleALC kext to that directory on the system drive for audio support
- If you did the wireless swap, also add the AirportBrcmFixup kext to that directory on the system drive
- Eject the USB flash drive and Reboot
- You should boot into Mojave successfully, with Audio working (and Wireless as well, if you did that)
After that, things seem to be working in Mojave. Yay!
- This should be pretty much working already. I set the name of my machine under System Preferences / Sharing before activating anything.
- If you have any questions, follow the iMessage guide. It never hurts to run the iMessageDebugv2 provided in that guide, save the result, reboot, run it again, and compare to make sure all the values are the same.
- After confirming that the iMessageDebugv2 output does not change across reboots, sign into iCloud and iMessage.
Addeddum: USB Support
I did not get the port-limit patch working in 10.14.2.
This board has a total of 8 USB3 ports (which also count as 8 USB2 ports) plus 2 USB2-only case ports and a USB2-only port for the internal Bluetooth... for a total of 19.
To keep this under the 15-port limit, I chose to disable the case USB2 ports (since I'm using the USB3 ones anyway) and the back USB port to the right of the HDMI port (I just taped over it to remind myself). The attached aaron-usb-config.aml uses this configuration. If you want a different USB configuration, you'll need to generate your own AML for it using RehabMan's procedure.