Installation of OS X 10.5.6 on a PC
The following is my geeky chronicle of installing OS X 10.5.6 on my PC Hardware from start to finish.
Recently an old HP laptop of mine decided that it was time to die, leaving me with no means of being a web surfing couch potato. Instead of bothering with figuring out which component went to hardware heaven, I decided it was time to purchase a new laptop that didn’t run so frustratingly slow when trying to play a game. Since I was under the spell of Steve Jobs’s reality distortion field, I decided to finally buy an Apple computer, and optted for one of those aluminum unibody Macbooks. I’ve been pleased with it since I bought it, and after a few hours of delta training myself from how OS X works vs Windows, I’ve been able to adjust pretty easily.
I’m not going to list the various deserved praises that OS X has over Windows, or vice-versa, but briefly, there were a few reasons for me deciding to try to put OS X on my PC hardware. I fit their strategy of the “walled garden“. I owned enough existing components (iPhone & AppleTV) of Apple’s offerings where this seemed to be the next logical progression. I was able to get rid of Picassa, and migrate to iPhoto, tie to to my Contacts, etc, etc. This left me wanting to get my PC on board with all the new toys goodness, and ultimately get some space back on my Macbook by migrating the disk-heavy media (Photos, Movies, Music) onto my PC.
I did some research on the Internet, and what first became apparent is that the methods to get OS X on your PC have changed so radically over the last 2 or 3 years, that unless you are reading under a current context, you will go down the wrong rabbit hole of tutorials. I learned a few things to ignore, mostly posts about OS X Tiger (10.4.x) and the whole SSE2/SSE3 kernel hacks, since I had modern hardware. There are also tutorials that will mention EFI emulation so that you can run a “Vanilla” kernel (basically an unhacked “holy grail” installation that is patch/hack free). This requires actually successfully installing OS X onto your PC at least once to even get to that point, at least in my experience. The Insanely Mac forums has been a great resource to put it all together. After reading and figuring out what to ignore (anything before mid 2008, mostly), I decided to try using a pre-configured “release” install. There are several out there (Kalyway, iPC, iDeneb, etc), and your mileage may vary. There is also a method called Boot-132 which seems promising in that it theoretically will allow you to configure an initial boot CD that you boot from and then use a Retail OS X DVD install disc to do your installation, thus giving you a clean installation.
It is very important that you know your hardware configuration before even trying to do this, so let me preface my progress with my hardware configuration. I am running an Intel DG965WH motherboard, and an NVidia 8800GT card. It’s as basic as they come. I was able to derive my SATA and Audio chipset from the motherboard model, so make sure you know these basic things beforehand.
My first attempt to get the installation to try the Boot-132 method. There is a Boot-132 maker out there that will attempt to ease the creation of the boot CD. There are also pre-made Boot-132 .ISOs (the version I ran across required a Mac) out there that are supposed to offer “noob” support. I opted for the pre-configured disc.
I put the CD in and fired up the PC. I got to a Darwin bootloader prompted, and following the tutorial, swapped the CD with a retail copy of OS X 10.5.6, and hit Enter. I got excited when I got the grey Apple loading screen, followed by an OS X installation background, complete with the beachball. After the installer finished initializing, it then informed me that I was not allow to install OS X on this computer. Doh! I then downloaded some other Boot-132 preconfigured CD, with the same results. (In hindsight, I believe either image may have worked after changing a piece of hardware, read on for what that was)
Frustrated, I decided to try a “release” version of the installation. I randomly decided on the Kalyway 10.5.3 release. I booted straight off of the DVD, and it let me on to the Installation wizard. Score! The installation was rather painless, and completed in about 20 minutes. I pop the DVD out, let the PC reboot, and get a grey Apple loading screen, yay! I wait a minute or two, and end up getting the ghostbusters circle with slash through it. At this point, I don’t know what that means I do more Googling.
I find out that by booting from one of my Boot-132 CDs that brings you to a Darwin bootloader prompt, that I could boot the OS in verbose mode (-v) so I could see what was going on. Turned out I got the very common “waiting for boot device…” error. More Googling ensued and it turned out that OS X does not like IDE DVD drives. (This may not be true with all releases, but I decided to see if it mattered.) I made a trip to Best Buy and picked up a SATA DVD drive and put that in my computer. It booted into an OSX post-installation wizard. Yay! (I currently believe this may have allowed my first attempt using Boot-132 to work in hindsight).
The first step of the wizard had me identifying my keyboard by hitting buttons on my keyboard next to my shift buttons, and worked fine. I then was asked if I wanted to import my MobileMe settings, which I said no, because I figured that it would try to get online and blow up since I was pretty sure my network adapter was not working yet. Even though I had selected the no option, when clicking next, the wizard hung and would go no further. More Googling told me to try to disable Firewire on my BIOS. I did so, and booted back in, and was able to get to the next stop of the wizard. Cool. Weird, but cool.
My first test was to see if I could even get my network, audio, and graphics working properly. This introduced me to .kexts. A .kext is a kernel extension, the closest analogue to that of a driver in the Windows world. To spare me from bouncing between my laptop for internet and my PC, I optted to get network working first. This went pretty painlessly by Googling for it and found an Intel networking kext that enabled my Internet. I then tried getting my NVidia card to work by using an injector called NVInstaller. NVInstaller appeared to work, as I was able to get the resolution to change. Audio proved to be much more frustrating, more on that later. Things seemed to be going well, so I tried to install World of Warcraft on it to test out the graphics acceleration. This was a fail. The disk i/o would get progressively slower and slower during the install and ultimately stopped. The DVD drive was unresponsive. I chalked this up to something wrong with the Kalyway release and tried to install the Kalway 10.5.4 addon patch, hoping this would help. I installed the patch, and rebooted, only to get the circle with slash ghostbusters symbol again, totally screwing my install. I called it a night and opted to continue the next day.
The following day, with the confidence of knowing my hardware could technically boot OS X, I looked for a different release that was more current. I picked iPC 10.5.6 Universal (AMD and Intel) which was the most recent version at the time. Since this, 10.5.7 is now the most recent, but this was still closer than Kalyway 10.5.3. iPC’s installer offered more options during install, such as pre-choosing which kexts to install, as well as power-saving fixes, etc. This release did not need me to disable firewire, as Kalyway’s did. The install took only 10 minutes and I was at the desktop. This install also pre-loaded my network kexts with no problem.
I then used NVInstaller to get my video going, and installed World of Warcraft and patched it current. I tried to get into the game to test the 3D acceleration, only to be told my card did not support 3D acceleration. Dang. More Googling pointed me to a different injector called NVKush. I tried NVKush and WOW started up without issue. Heck yeah. But no sound.
Sound proved to be very painful. My audio chipset was a Sigmatel 9271D. I was unable to track this kext down initially, but tried the 9271, but it was not compatible. I finally was able to track one down on the Insanely Mac forums, but I was not able to download any attachments from there. Found out I had to donate to the forums to download files. Fair enough, $10 later I was able to download the kext and get it working. For those with other Sigmatel chipsets, there is a painful tutorial on how to patch your HD Audio kext by booting to a Linux ISO and extracting the codec info to a .txt file.
Long story short, I now had the kexts and injectors to install OSX using iPC 10.5.6 after much Googling and headache. I have had no problems getting updates from Apple (except 10.5.7, I’ve heard it can mess stuff up, but I’ll try it one day). I’ve also tried the iDeneb 10.5.6 release and I’ll say that its installation options are more comprehensive and offer better explanations of all the options over iPC. With all these releases, this still gets back to the matter of getting a “Vanilla” install without relying on releases, aka the holy grail of installs.
This gets back to the EFI bootloader. iPC installed Chameleon 1.x (can’t remember which version). Basically a an EFI bootloader emulates the EFI of a real Mac. EFI is basically the natural progression/replacement of the traditional BIOS. This bootloader will also allow you to place your kexts in /Extras/Extensions instead of /System/Library/Extensions. This is unique in that updating your OS will not screw up your hacked kext files. This also theoretically means that you can wipe your OS and install off a retail DVD. It’s just getting the kexts into /Extras/Extensions that requires you to have OS X installed or access to a mac that can place them in there.
What I’m not clear on is if /Extras/Extensions is mapped to the 200MB EFI partition that was made and it’s just transparent to me, or if it’s part of the same Volume as my OS. I’m nervous to try to wipe my install and see for myself. I’ll see what happens after making a backup.
After it’s all said and done, my installation works just like a real Mac with no problem. It was definitely cheaper than buying a real Mac, but I just can’t justify the price of the hardware premium that Apple puts on them.
Hopefully this long chronicle will help anyone that is Googling for help on getting a running Hackintosh. Good luck if you are, and drop me a comment and maybe I can help.