envoy510

The chocolate ration is being increased to 25 grammes per week.

Monthly Archives: March 2014

Build complete: the new Hackintosh is a success.

OK, so I wrote about wanting a Mac Pro but not being able to afford one. Well, the deed is done. I purchased the parts, built the computer and installed Mac OS 10.9 on it. My Hackintosh (running Mac OS on non-Apple hardware) is done and it was a great success! Here’s the tale of that journey.

The parts I chose:

CPU: Intel Core i7-4770K 3.5GHz Quad-Core Processor
CPU Cooler: Noctua NH-U14S 55.0 CFM CPU Cooler
Motherboard: Gigabyte GA-Z87X-UD5H ATX LGA1150 Motherboard
Memory: Corsair Vengeance LP 32GB (4 x 8GB) DDR3-1866 Memory
Storage: 2x Samsung 840 Pro Series 128GB 2.5″ Solid State Disk
Storage: 5x Western Digital Red 3TB 3.5″ 5400RPM Internal Hard Drive
Video Card: EVGA GeForce GTX 760 2GB Video Card
Case: Fractal Design Define R4 (Black Pearl) ATX Mid Tower Case
Power Supply: Corsair 760W 80+ Platinum Certified Fully-Modular ATX Power Supply
Other: HighPoint RocketRAID 3620
Other: HDE 2-Port USB Rear Panel Bracket Host Adapter
Other: StarTech.com 2 Port USB 3.0 A Female Slot Plate Adapter

This set of parts were chosen after more than a month of painstaking research, a lot of it on the forums at tonymacx86.com.  This is a great resource for anyone wanting to build a Hackintosh.

I’m a big believer in RAID, so it’s no surprise I chose RAID 1 for Mac OS and RAID 6 for my other stuff.  I was a little nervous about the HighPoint RocketRAID card, since I couldn’t find anyone that had used it in a Hackintosh, but I did find that Mac OS 10.8 and later supported the card I wanted.

The most important components for a Hackintosh are the CPU, motherboard and video card.  The choices I made were for maximal compatibility with Mac OS.

Once I assembled the components into an actual machine, I tested the memory for 3 days (with memtst86) and each individual hard disk with the Western Digital diag program.  Then, it was off to the races…

First up: flash an up-to-date BIOS for the UD5H (F7, but F8 was released shortly after I got it built).  The BIOS settings I used:

  • System Information > Working Environment > Classic Mode
  • Load optimized defaults
  • Performace > Memory > X.M.P. > Profile 1
  • BIOS Features > Intel Virtualization Tech > DISABLED
  • BIOS Features > Boot Option Priorities: set appropriately
  • BIOS Features > Full Screen LOGO Show > DISABLE
  • Peripherals > Device Config > Initial Display Output > PCIe 1 slot
  • Peripherals > Device Config > xHCI Mode > AUTO
  • Peripherals > Device Config > Intel Processor Graphics > DISABLED
  • Peripherals > Device Config > xHCI Hand-OFF > ENABLED (the default, but good to check)
  • Peripherals > Device Config > EHCI Hand-OFF > ENABLED
  • Peripherals > Super I/O Config > Serial Port A > DISABLED
  • Power Management > Wake on Lan > DISABLED
  • Save and Exit Bios

I also updated the firmware on the HighPoint card.

As I said I did software RAID 1 for the Mac OS drive.  I tried doing a test install with hardware RAID 1 (with the SSDs attached to the 3620), but it didn’t work.  I wasn’t sure why, so I moved on to software RAID 1.  I was able to install, but upon rebooting after the install it wasn’t able to boot properly.  After a lot of searching, I figured out the installation had put the boot loader (the thing that loads the operating system) in the wrong place.

When you make a RAID 1 array in the Mac OS Disk Utility, the actual boot partition is a composite of the real underlying disks.  Here is the output of diskutil list:

/dev/disk0
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *128.0 GB   disk0
   1:                        EFI                         209.7 MB   disk0s1
   2:                 Apple_RAID                         127.7 GB   disk0s2
   3:                 Apple_Boot Boot OS X               134.2 MB   disk0s3
/dev/disk1
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *128.0 GB   disk1
   1:                        EFI                         209.7 MB   disk1s1
   2:                 Apple_RAID                         127.7 GB   disk1s2
   3:                 Apple_Boot Boot OS X               134.2 MB   disk1s3
/dev/disk2
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                  Apple_HFS mack-root              *127.7 GB   disk2

The actual boot disk is disk2 and it is made up of two parts, disk0 and disk1.  I think what happened is the installer put the boot loader on /dev/disk2 and not at the beginning of /dev/disk0 and /dev/disk1.  So, I needed to do that.  Here’s how I did it:

newfs_hfs -v EFI /dev/disk0s1
newfs_hfs -v EFI /dev/disk1s1
mkdir /Volumes/EFI
mkdir /Volumes/EFI2
mount_hfs /dev/disk0s1 /Volumes/EFI
mount_hfs /dev/disk1s1 /Volumes/EFI2
cd /Volumes/USB/usr/standalone/i386
fdisk -f boot0 -u -y /dev/rdisk0
fdisk -f boot0 -u -y /dev/rdisk1
dd if=boot1h of=/dev/rdisk0s1
dd if=boot1h of=/dev/rdisk1s1
cp boot /Volumes/EFI/
cp boot /Volumes/EFI2/
umount /Volumes/EFI/
umount /Volumes/EFI2/
fdisk -e /dev/rdisk0 <<EOF
p
f 1
w
y
quit
EOF
fdisk -e /dev/rdisk1 <<EOF
p
f 1
w
y
quit
EOF

I ran this script booted from the UniBeast USB drive I used to install Mac OS.  When you boot from the USB drive, it goes into the Mac OS installer, which allows you to get a Terminal window and execute the above script.  Once I did that, I was able to reboot normally into my newly installed Mac OS 10.9.1.

We’re not done, though.  While Mac OS is running, it’s not fully configured for our Hackintosh hardware.  The next phase is to run MultiBeast and install appropriate drivers for the hardware I have.  For me, these were the settings I used:

Quick Start > DSDT Free
Drivers > Audio > Without DSDT > ALC898 (automatically checks HDAEnabler)
Drivers > Disk > TRIM Enabler > 10.9.x TRIM Patch
Drivers > Misc > FakeSMC v5.3.820 Plugins
Drivers > Misc > FakeSMC v5.3.820 KWMonitor Application
Drivers > Misc > PS/2 Keyboard/Mice and Trackpads
Drivers > Misc > USB 3.0 - Universal
Drivers > Network > Intel hnak's AppleIntelE1000e v2.4.14
Customize > Boot Options > IGPEnabler=No
Customize > Boot Options > Verbose Boot
Customize > Boot Options > 1080p Display Mode
Customize > System Definitions > iMac > iMac 14,2
Build -> Select Install Drive: Mavericks -> Install

Here’s a picture of the MultiBeast window:

Screen Shot 2014-02-28 at 3.00.40 PMWhen I clicked “Install” in the lower right corner I got a popup that said

Kernel extension is not from an identified developer

The kernel extension at “/System/Library/Extensions/GenericUSBXHCI.kext” is not from an identified developer but will still be loaded.

I clicked “OK” to that, then rebooted without the USB drive attached.

The video card I have is a good  performer but it’s also pretty quiet.  It’s got 1152 CUDA cores.  However, to get the most out of it, I needed to install the nVidia CUDA drivers. After doing so, CUDA-Z shows this info:

Screen Shot 2014-02-28 at 3.32.20 PMScreen Shot 2014-02-28 at 3.33.04 PMScreen Shot 2014-02-28 at 3.33.13 PMI haven’t figured out what I can do with this fancy pants video card, but so far the performance good.  The Geekbench 3 score for the new machine is:

Screen Shot 2014-02-28 at 3.41.39 PMThat’s just the 32-bit score.  The 64-bit score requires paying for the app.  By comparison, the Mac Pro score is 3215 (single) / 18296 (multi).  It makes sense the multi-processor score is higher since the 2013 Mac Pro has a Xeon processor, which is much better when multiple cores are active.

What about the stats on various monitored quantities?  Installed with Mac OS (by UniBeast or MultiBeast) is a hardware monitoring program.  Here’s a screen cap of it:

Screen Shot 2014-02-28 at 4.05.42 PMNote the CPU frequency was at 800MHz during the cap, instead of 3.50GHz, which is the normal, non-turbo frequency.  This shows the speed-step (or whatever it’s called in Mac OS) is working with the CPU/motherboard I have.

Finally, some pictures of the build:

20140222-0852-30-6035-5D3 20140222-0901-33-6043-5D3 20140222-0901-41-6044-5D3 20140222-0902-53-6052-5D3 20140222-0907-16-6054-5D3

UPDATE: 2015-02-07

Using RAID mirror for the operating system drive is just too much of a pain in the ass. I did a full backup, removed the RAID partition and the partitions on the two SSDs. Then, I booted into the 10.9.5 installer and restored into one of the drives.

Then, I setup a daily schedule for Super Duper! to make a copy of my root drive onto the second SSD. In the event I have a crash, I can use the second SSD immediately.

Advertisements