Mavericks on Gigabyte GA-B75M
This post describes the steps to install Mavericks on my system, described here.
To install Mavericks, I used UniBeast 4.0.3. To obtain a copy of the required Mavericks installation application from Apple, I used a MacBook Pro; downloaded the app, and performed the steps required to install it on a USB stick, as described in the tonymacx86 site. Note that I didn't upgrade my Mountain Lion system, opting instead for a clean installation.
Mavericks installation was flawless. The only important bits were to ensure that the BIOS settings were correct: in fact, BIOS settings are basically the default ones. In special, VT is enabled, but VT-D must be disabled. Also, XHCI and EHCI handoff must be enabled.
After installation, it is needed to start Multibeast 6.5.0 to fix the correct drivers. My only issue with Multibeast is that it was not clear for me whether it runs progressively or not: if you miss one driver and want to add it, you should still provide all the required drivers, as otherwise something can be missing. On the other side, my failure to select the correct network driver on the first step meant that the incorrect driver was still installed at the end, requiring a (very simple) manual action to remove it.
The correct installation for my system requires:
- Quick Start: select DSDT free
- Audio: add ALC887/888b current
- Disk: add 10.9.4+ TRIM patch ( 3rd party SATA already selected )
- Graphics: nothing
- Misc: no changes (FakeSMC already selected)
- Network: Realtek: add RTL81xx
- System: no changes ( AppleRTC patch already selected )
- Bootloaders: Chimera (already selected)
- Customize: No changes, already selected:
- Basic Boot options
- Generate CPU states
- Hibernate mode -desktop
- Use kernel cache
Checking the logs, I discovered one additional error, which had already appeared on my initial Mountain Lion installation: Sound assertions in AppleHDA*. This error does not seem to affect the normal behaviour of the sound system, but I tried replacing the Realtek ALCxxx audio driver with the VoodooHDA one; unfortunately, this didn't work at all, with the driver reporting no found devices. Back to the ALC887 driver.