- Joined
- Jul 24, 2014
- Messages
- 21
- Motherboard
- Gigabyge GA-Z97-H3D
- CPU
- i5-4570
- Graphics
- HD4 000
- Mac
- Classic Mac
- Mobile Phone
Prior to the actual Mac OS X Mavericks install, I upgraded the motherboard to F5 BIOS and changed BIOS the settings to: optimized defaults, VT-d disabled [1’] (may not be necessary)
Installing Mavericks on an Gigabyte 9-series H97-D3H motherboard [30+ minutes]
9. Rebooted –V => SUCCESS [3’]
10. Used Carbon Copy Cloner and clone this clean install on my “Safe Harbor” partition.
Additional notes
Installing Mavericks on an Gigabyte 9-series H97-D3H motherboard [30+ minutes]
1. Created USB installer (8GB) with UniBeast 4.0.2, under 10.9.4, options: Mavericks / Desktop [20’ depends on how fast your USB key is, can be one hour!]
2. Added tools to USB stick: [5’] a. MultiBeast 6.4.1 b. Kext Utility
c. AppleIntelFramebufferAzul.kext patched for Intel Graphics HD4600 (available here: |
3. Booted on USB Installer with –x –v (safe boot, verbose) options [5’] |
4. Use Utilities > Disk Utility to format hard disk (GUID partition scheme, HFS+ formatted). I created two partitions: a. A 50 GB “Safe Harbor” partition which I will use to store a safe stable install
b. The rest of the disk as my main working partition [2’] |
5. Installed Mavericks on the main partition of the newly formatted hard disk [20’] |
6. Restarted the computer a. pressed F12 to enter BIOS boot menu to boot from the USB installer again => enter the boot loader) [1’] |
b. In the boot loader, select newly installed disk and boot with -V -X options => completed boot in OS X account creation screens. [3’]
c. Created main administrator account (US location / English main language – at least through the whole installation process / French keyboard / no AppleID / Don’t register) [2’]
7. Got in the Finder! Seen as MacPro 3,1 3.4 GHz, Ethernet working, Intel HD Graphics 4600 recognized, Audio: Intel High Definition Audio only recognized but no sound In/Out (except through Airplay) [3’]
8. Post install steps [5’]
|
a. Opened MultiBeast 6.4.1. Based on the “DSDT Free” set, I only selected drivers for Audio: ALC1150 Audio + Intel 9 motherboard support, and for LAN: AppleIntelE1000e v3.1.0. See attached settings
b. Installed and “OKed” to the few system warnings regarding modified kext [5’ be patient].
c. Ran Kext Utility and let it rebuild permissions and system cache, then dragged AppleIntelFramebufferAzul.kext on the Kext Utility window and let it complete the install.
b. Installed and “OKed” to the few system warnings regarding modified kext [5’ be patient].
c. Ran Kext Utility and let it rebuild permissions and system cache, then dragged AppleIntelFramebufferAzul.kext on the Kext Utility window and let it complete the install.
9. Rebooted –V => SUCCESS [3’]
a. Note that this first boot is a bit long, be patient
b. Audio working (headphone port OK HDMI audio needs additional tweaks).
c. Ran benchmark to confirm OpenGL and full CPU acceleration working: OK.
d. AppStore software update, iTunes and iMessage working with no additional changes. I later had to add FileNVRAM.dylib to keep iMessage working.
b. Audio working (headphone port OK HDMI audio needs additional tweaks).
c. Ran benchmark to confirm OpenGL and full CPU acceleration working: OK.
d. AppStore software update, iTunes and iMessage working with no additional changes. I later had to add FileNVRAM.dylib to keep iMessage working.
10. Used Carbon Copy Cloner and clone this clean install on my “Safe Harbor” partition.
Additional notes
- I enabled Airdrop over Ethernet with the following command:
defaults write com.apple.NetworkBrowser BrowseAllInterfaces 1
- I didn’t notice any difference between using the MacPro3,1 and the iMac14,1 system definitions. I used Chameleon Wizard to fine tune the system definition as it is more complete than MultiBeast. Yet, after this iMessage was reporting the common login error and I had to install FileNVRAM.dylib
- While networking was in appearance working fine, I noticed slowness when reading a movie from my AppleTV and Console was recording a continuous flow of “e1000_tx_map: failed to getphysicalsegment” errors. I had to replace MultiBeast’s built-in AppleIntelE1000e v3.1.0 driver with one where the NETIF_F_TSO key is set to false in the driver’s info.plist (it should be the case as these driver does not support TCP Segment Offloading – it would be nice though…). It seems that the developers of the driver know about the issue and it should get fixed.
I am attaching an edited copy to this post.
- While networking was in appearance working fine, I noticed slowness when reading a movie from my AppleTV and Console was recording a continuous flow of “e1000_tx_map: failed to getphysicalsegment” errors. I had to replace MultiBeast’s built-in AppleIntelE1000e v3.1.0 driver with one where the NETIF_F_TSO key is set to false in the driver’s info.plist (it should be the case as these driver does not support TCP Segment Offloading – it would be nice though…). It seems that the developers of the driver know about the issue and it should get fixed.
I am attaching an edited copy to this post.