[GUIDE] Retail OS X Install (10.5.8) on Gigabyte GA-EX58-UD5 (Core i7) Mobo

[inspired7]

First off a big thanks for developing this. I have a P6T D V2 mobo and was trying the method described in the P6T D thread but couldn't get leopard to install (it would always fail). I noticed your install pack and used it and now I have everything sorted out and running great (sound, lan, gfx, etc) except, I can't get my system to boot running ALL cores and HT. The DSDT patcher in your install kit puts the DSDT.aml file in my root so I know it has installed but when I enable all cores and ht after reboot I get... "Still waiting for root device". I have tried moving my drives around but no go. As soon as I go back to 1 core and no ht it boots fine.

 

Any ideas? Can I delete the generated dsdt.aml file and run the dsdt patcher separately and manually adjust the file? Do you think this is even the problem? Is there a kext file associated with the SATA controller and detecting drives that I could change to a different version to try? I am not sure how apple detects the drives and why this happens when all the cores are enabled.

 

Thank you for your time.

[ѕӎѳѳ₮ңӌ]

Do you mean dsmos.kext? I have that in the extensions folder for the script.

 

Do you mean that I should I try deleting the dsmos.kext from the extensions folder of the script and replacing it with the apple decrypt kext?

 

basically over christmas my machine just stopped booting, hanging at that screen you just posted. i tried everything, i reinstalled 20 odd times, always using the apple decrypt kext as it had always worked for me and been quicker than dmos. however it must have become corrupted as when i replaced it with dmos.kext my machine booted, for the first time in over a month.

 

so basically what i am saying is, re-download dmos.kext or download appledecrypt.kext and try it. you have nothing to lose. it may or may not work for you, as my googling found many things that can result in hanging at that line, but as you are also on an x58 chipset, you have a good chance of it working!

[digital_dreamer]

Here is what I'm seeing after attempting wolfienuke's method.

I'm using i7 920 and this Mobo

Anyone know what I can do?

I don't see any evidence that the system can see your OS X install. The log doesn't indicate access has been made. The natit.kext, or whatever graphics injector you are using, doesn't support the graphics card you are using. What OS X install method are you using?

 

 

First off a big thanks for developing this. I have a P6T D V2 mobo and was trying the method described in the P6T D thread but couldn't get leopard to install (it would always fail). I noticed your install pack and used it and now I have everything sorted out and running great (sound, lan, gfx, etc) except, I can't get my system to boot running ALL cores and HT. The DSDT patcher in your install kit puts the DSDT.aml file in my root so I know it has installed but when I enable all cores and ht after reboot I get... "Still waiting for root device". I have tried moving my drives around but no go. As soon as I go back to 1 core and no ht it boots fine.

 

Any ideas? Can I delete the generated dsdt.aml file and run the dsdt patcher separately and manually adjust the file? Do you think this is even the problem? Is there a kext file associated with the SATA controller and detecting drives that I could change to a different version to try? I am not sure how apple detects the drives and why this happens when all the cores are enabled.

 

Thank you for your time.

There just might be a problem with the way my script is stripping out those CPU aliases. This isn't the first time I got this type of feedback. As I don't have a ASUS board to test, I'm relying entirely on user feedback, so thanks for this report.

As it is now, the script immediately reruns the DSDT patcher again when it finds those aliases, so your chances of grabbing the .aml file and hand editing it is practically impossible. However, you can go into the script folder run the DSDT Patcher separately from ~extra/DSDT_Patcher. Type "cd " in Terminal without quotes (notice the space), and drag the DSDT_Patcher folder to the Terminal window, hit "Enter". Then, type "./dsdtpatcher.sh" without the quotes.

What I'll do sometime later is set the script up to prompt the user to re-run the patcher, if desired. That will allow the user a time to grab the .aml file and hand-edit it before running it again.

 

Let me know if this hand-edit works for you. If it does, I'll would like a copy of the hand-edited file and the previous unedited file from you, if you can provide it. Thanks!

 

regards,

MAJ

[tsunoo]

Here is what I'm seeing after attempting wolfienuke's method.

I'm using i7 920 and this Mobo

Anyone know what I can do?

 

try this:

- delete the com.apple.boot.plist located in the "EFI Boot Installer v3" directory

- call again install.sh and do a "1) install"

[inspired7]

There just might be a problem with the way my script is stripping out those CPU aliases. This isn't the first time I got this type of feedback. As I don't have a ASUS board to test, I'm relying entirely on user feedback, so thanks for this report.

As it is now, the script immediately reruns the DSDT patcher again when it finds those aliases, so your chances of grabbing the .aml file and hand editing it is practically impossible. However, you can go into the script folder run the DSDT Patcher separately from ~extra/DSDT_Patcher. Type "cd " in Terminal without quotes (notice the space), and drag the DSDT_Patcher folder to the Terminal window, hit "Enter". Then, type "./dsdtpatcher.sh" without the quotes.

What I'll do sometime later is set the script up to prompt the user to re-run the patcher, if desired. That will allow the user a time to grab the .aml file and hand-edit it before running it again.

 

Let me know if this hand-edit works for you. If it does, I'll would like a copy of the hand-edited file and the previous unedited file from you, if you can provide it. Thanks!

 

regards,

MAJ

 

 

Thanks for responding. It is nice to have some help. Anyway I reran the DSDT patcher both with the method you indicated and manually following M J's guide and the problem I am seeing is that the dsdt.dsl file that is generated doesn't contain any "Alias CPU" references to delete. I have attached my file that is generated for you to look at. Do you know how I would modify this? If I remove dsdt.aml from the root directory I cannot boot at all so I know it is somewhat working... maybe just missing references to allow all cores. Hope you have an idea. Thanks again

dsdt.dsl.zip

[digital_dreamer]

Thanks for responding. It is nice to have some help. Anyway I reran the DSDT patcher both with the method you indicated and manually following M J's guide and the problem I am seeing is that the dsdt.dsl file that is generated doesn't contain any "Alias CPU" references to delete. I have attached my file that is generated for you to look at. Do you know how I would modify this? If I remove dsdt.aml from the root directory I cannot boot at all so I know it is somewhat working... maybe just missing references to allow all cores. Hope you have an idea. Thanks again

I posted a reply to the ASUS thread.

 

regards,

MAJ

[Sumrall]

I don't see any evidence that the system can see your OS X install. The log doesn't indicate access has been made. The natit.kext, or whatever graphics injector you are using, doesn't support the graphics card you are using. What OS X install method are you using?

 

I'm trying to install using wolfienuke's EFI Partition script...

 

I tried starting over. I have an external HD and my hackintosh HD plugged into my iMac. I used the external HD to boot and install a retail version of 10.5.4 on to my hackintosh HD. Then I downloaded v3.1 of the script and double-clicked install.command. I didn't do anything extra, since I'm already in new territory. I just let the script run. However, there wasn't any indication that the script did anything upon restarting.

 

Should I be able to see the EFI partition under Disk Utilities (because I don't)?

 

When I booted my second attempt on my new machine I got the same log I posted above.

 

This isn't because of the video card, though, is it? I'm using ATI HD4870 1GB and I've found instances where people got it to work, I just thought that this came latter in the process and not upon booting.

 

I hope that I can eventually diagnose this stuff myself, but until then I'm just stuck until someone helps (which I appreciate more than ya'll know).

 

EDIT: If this helps here my EFI Installer Log

 

and a shot of my install screen.

EFI_Installer_Log.rtf

Install_Screen.tiff

[thx4dat]

@ DD and Wolfienuke

 

Both yourself and wolfienuke have done an amazing amount of work. Thank you.

 

question: DD, If I decide to use the ATI 4870 should I remove the included Nvidia kext from the folder that your script uses? Or will it be OK to leave it as it is. I don't know if the two kext would conflict. It is a question rooted in ignorance cause I don't know anything about extensions, specifically in these case, if they would conflict with each other.

 

Thank you

[digital_dreamer]

I'm trying to install using wolfienuke's EFI Partition script...

 

I tried starting over. I have an external HD and my hackintosh HD plugged into my iMac. I used the external HD to boot and install a retail version of 10.5.4 on to my hackintosh HD. Then I downloaded v3.1 of the script and double-clicked install.command. I didn't do anything extra, since I'm already in new territory. I just let the script run. However, there wasn't any indication that the script did anything upon restarting.

 

Should I be able to see the EFI partition under Disk Utilities (because I don't)?

 

When I booted my second attempt on my new machine I got the same log I posted above.

 

This isn't because of the video card, though, is it? I'm using ATI HD4870 1GB and I've found instances where people got it to work, I just thought that this came latter in the process and not upon booting.

 

I hope that I can eventually diagnose this stuff myself, but until then I'm just stuck until someone helps (which I appreciate more than ya'll know).

 

EDIT: If this helps here my EFI Installer Log

 

and a shot of my install screen.

Sumrall,

The only thing I can see that is amiss is that fdisk (of the make drive active utility) is not able to unmount all partitions on your drive, at least that's in the log as shown. Do you have more than one partition on that drive? However, it still appears the BIOS is able to hand-off control to the bootloader, anyway. But, after loading the kexts from the EFI partition, it's not going to your OS X install.

You should NOT be able to see the EFI partition in disk Utility. All GUID partitions will have that partition and Apple doesn't want users to see it and tamper with it. The install logs shows nothing amiss here - all proper files are located on the EFI partition.

 

I'd pull the Natit.kext (or any other graphics injector) out of your Extensions to install folder and give it a go, again. DON'T do a "Update" on wolfienuke's script. Always do "Install" for best results.

 

@ DD and Wolfienuke

 

Both yourself and wolfienuke have done an amazing amount of work. Thank you.

 

question: DD, If I decide to use the ATI 4870 should I remove the included Nvidia kext from the folder that your script uses? Or will it be OK to leave it as it is. I don't know if the two kext would conflict. It is a question rooted in ignorance cause I don't know anything about extensions, specifically in these case, if they would conflict with each other.

 

Thank you

I don't have a concrete answer for that, but, if you are having issues and the file is suspect, it's always a good idea to remove what's deemed unnecessary in an effort to eliminate that possibility. But, as far as I know, they shouldn't conflict and only work with their designed for video card brands.

 

regards,

MAJ

[HeartQ8]

I thank DD for the script and others for this topic which open my eyes on Mac installation from original DVD. I would like to list here my steps I took to install Mac OS on GA-EX58-extrim MoBo (same as UD5 but with hyper cooler) and how I come over the list issues in this topics and wish DD will update his file if needed.

 

I use same steps as in DD article on first page with those changes:

 

1- My 3 Hard Disk (500GB) installed as all masters on SATA 6 main ports (I used try and error on ports to avoid slaves, I used ports 1,3,5) and install two DVD-ROM DL on SATA on second ports bank (on port1), and the other one on IDE port as slave (you have to set switch on the drive). set the BIOS as DD shows in his article AHCI for SATA RAID/AHCI Mode and Onboard SATA/IDE Ctrl Mode to IDE. by this setting you will not see ROM-DVD option on boot screen to save time (I hate the start up screen it took more thank 20 sec to boot by all settings), beside I found I can not install XxX leopard 10.5.6 version on the second drive to run DD script.

 

2- I inject in DD scripts what I need, for my Graphics my string for my GF 9400 GT 512 string in com.apple.boot.plist and my RAM speed under plists folder and removes ATI kext from _Graphics section. Under Misc_Patches in _to install AppleACPOPS2Nub.kext and ApplePS2Controller.kext to activate my PS2 Mouse and Keyboard (may DD need to put those kext under _repository section as an option to users).

 

3- from here I follow DD way and boot from my main hard disk with MAc OS and you will notice all working the PS/2 issue and sleep option is working, I will come to VMware Fusion.

 

 

I noticed and here need DD feedback:

 

1- when I installed iDeneb 1.4 with kernel 9.5.0, it reports 7 cores CPU but on kernel 9.6.0 it shows 4 cores, which one correct, is that correct 4 cores ?

 

2- the Audio driver will not support 7.1 only front speaker or back speakers (output 1 or output 2), I know it is driver issue and hope to be solved. Hope there is a software to fix the sound.

 

3- after time or updating from Apple or else after PC sleep the kernel report panic and I have to run post script option 5 from DD script and it solve the issue.

 

4- VMware Fusion will not install and report kernel permission issue and after I use OSX86Tools to reinstall mach_kernel.voodoo in your script it will install and now Vista Ultimate 64bit working in full with VMware Fusion v2.0.2.

 

So now from time to time if I have sleep or VMware problems, I run 5)post-script from DD script from recovery drive with XxX leopard and than from my main Mac OS drive I run OSX86Tools to reinstall the kernel.

[Sumrall]

The install logs shows nothing amiss here - all proper files are located on the EFI partition.

 

Do you know why? when I boot it says things like:

 

choosed model Alkor says not supported by R600

Alkor: Required dictionaries not found in plist

extension "com.apple.driver.AppleHDAController" cannot be found

can't find extension com.apple.driver.AppleHDAController

ca't determine dependencies for com.apple.driver.AppleHDAController

Counldn't alloc class "AppleHDAController"

[iktus]

Chameleon RC1 is out...

DD ... I expect that you update the guide and the script

Tnx4all

[digital_dreamer]

Do you know why? when I boot it says things like:

 

choosed model Alkor says not supported by R600

Alkor: Required dictionaries not found in plist

extension "com.apple.driver.AppleHDAController" cannot be found

can't find extension com.apple.driver.AppleHDAController

ca't determine dependencies for com.apple.driver.AppleHDAController

Counldn't alloc class "AppleHDAController"

The Alkor related messages are from the Natit.kext (ATI graphics injector).

If you are using the boot from EFI setup, there are going to be a lot of audio dependency issues. There are three audio related kexts installed with wolfienuke's script on the EFI partition. They depend on some other kexts that are in the normal OS X install location (S/L/E). Therefore, those messages reveal that the main OS X install can't be found/located.

The AppleHDAController is located inside the Plugins folder in the AppleHDA.kext in S/L/E.

 

So, basically, this install can't proceed as it can't find the required main OS install for some reason. It could be that it expects it somewhere other than where it is.

 

Chameleon RC1 is out...

DD ... I expect that you update the guide and the script

Tnx4all

Oooo! Thanks for that.

 

regards,

MAJ

 

MAJ

[chemu]

I mentioned this a month ago and got crickets in this thread. I think this symlink has been tried and does not work with EFI Partition Boot. I am assuming you haven't tried to symlink the kernel because this is your first post. Can anyone corroborate with this hypothesis.

 

I'm just telling you what I did to make Fusion work with the EFI Partition Boot. I don't know why it works, I just know that it did for me.

I installed OS X with the boot from EFI Partition and Fusion did not work until I tried this.

 

I don't know why you assume that I haven't tried to symlink the kernel just because this is my first post.

 

If you want corroboration why don't you try it yourself?

[Jagull]

anyone know how well Maya runs on this board & cpu?

[thx4dat]

I don't have a concrete answer for that, but, if you are having issues and the file is suspect, it's always a good idea to remove what's deemed unnecessary in an effort to eliminate that possibility. But, as far as I know, they shouldn't conflict and only work with their designed for video card brands.

 

regards,

MAJ

 

Thank you for your reply. The reason I asked was that I was using a microsoft usb keyboard with my powerbook. Immediately after I installed the kext and the application I got kernel panics, freazes, and very weird behavior with my firewire drives. I uninstalled all the windows apps and the kext, OSX recognized my keyboard and all was well.

 

Best regs

[hobes270]

Hey! Is there a way to do the EFI method with chameleon? So we can have a boot picture and stuff like that?

 

THnaks!

[tstm]

Thank you very much Digital Dreamer and Wolfienuke!

 

I installed using the Wolfie method, EFI. I didn't have my retail DVD at hand, so I used my restore DVD from my Macbook Pro (10.5.2). I simply plugged my harddisk into my MB Pro using a USB->SATA converter, partitioned the disk, installed OSX onto it and then rand the Wolfie script. The system booted fine (after a few trial-and-error runs). I might have had to fiddle around a bit with the network drivers to make network work with the wolfie script, I don't have the details how to do that anymore.

 

After install, I applied 10.5.6 Combo update, it ran fine without issues.

 

To make the graphics work, I ran the Netkas 48xx modules in and installed the new Natit.kext into the EFI partition. I also had to put two adapters into my HDMI port on the graphics card. An HDMI->DVI and a DVI->VGA adapter did the trick.

 

I updated the wolfie Voodoo 9.5 kernel with 9.6 and renamed it to mach_kernel in both the EFI partition and in the real install partition root. This made VMWare Fusion work. Also the seatbelt kext needed to be updated for the dmgs not to crash.

 

And to all those wondering about VMWare not working with EFI, my thinking is that you need to have the running kernel image in /mach_kernel even if you're not booting from it.

 

The integrated sound still doesen't work.. but that's not an issue for me since I use USB sound anyway.

 

Unfortunately sleep does not work either. I can go to sleep, it does it very fast even.. but can't wake up. Does anyone else have sleep (S3) working on UD5 F5?

 

Also, could someone post hints/instructions on how to install Chameleon? I gotta have it, it looks so good. The instructions at chameleons site are straightforward enough.. but I'd like to have some confirmation that it won't break this very nice setup I've got going here..

 

 

Some info about my hardware:

Gigabyte EX58-UD5 (Bios F5)

Core i7 920 @ 3.4GHz (20x170)

3x2GB G-Skill

Gainward Radeon HD4870 1024MB Golden Sample

HP LP3065 30" 2560x1600 Display

External USB soundcard

[hobes270]

THe new chameleon is out, version 2, that DOES support EFI boot.

 

 

If we are using EFI method, how do we go about installing this?

[tstm]

Well, I can tell you how NOT to do it.

 

The install itself seemed fine using the following instructions (of course <disk> should be replaced with the correct number):

 

1. download Chameleon zip file
2. unzip file
3. open up terminal
4. cd /
5. mkdir /Volumes/EFI; sudo mount_hfs /dev/disk<disk>s1 /Volumes/EFI; cd /Volumes/EFI
6. sudo mkdir Extra; sudo cp -R /Volumes/EFI/Extensions /Volumes/EFI/Extra
7. cd into Chameleon download directory
8. sudo cp -R smbios.plist Themes /Volumes/EFI/Extra
9. sudo fdisk -f boot0 -u -y /dev/rdisk<disk>
10. sudo dd if=boot1h of=/dev/rdisk<disk>s1 bs=512 count=2
11. sudo cp boot /Volumes/EFI

 

The Chameleon bootloader loaded and everything seemed to work fine (Windows booted like a charm) - but ALAS when I tried to boot into OSX, I got lots of SMC errors and IOKitWaitQuiet errors etc, and then the system hung with a light blue screen. With a little googling, I think the reason was that the blacklists needed for Wolfies EFI are not working properly. The IOKitWaitQuiet errors manifest when AppleHWSensor.kext (which is normally blacklisted) loads up (correct me if I'm wrong).

 

So, as of now, I didn't get the EFI solution working with the Chameleon bootloader. Luckily the boot code is easy enough to replace.. and now I'm back to the standard boot process..

[digital_dreamer]

Hey! Is there a way to do the EFI method with chameleon? So we can have a boot picture and stuff like that?

 

THnaks!

 

 

THe new chameleon is out, version 2, that DOES support EFI boot.

If we are using EFI method, how do we go about installing this?

 

 

Well, I can tell you how NOT to do it.

 

The install itself seemed fine using the following instructions (of course <disk> should be replaced with the correct number):

 

1. download Chameleon zip file
2. unzip file
3. open up terminal
4. cd /
5. mkdir /Volumes/EFI; sudo mount_hfs /dev/disk<disk>s1 /Volumes/EFI; cd /Volumes/EFI
6. sudo mkdir Extra; sudo cp -R /Volumes/EFI/Extensions /Volumes/EFI/Extra
7. cd into Chameleon download directory
8. sudo cp -R smbios.plist Themes /Volumes/EFI/Extra
9. sudo fdisk -f boot0 -u -y /dev/rdisk<disk>
10. sudo dd if=boot1h of=/dev/rdisk<disk>s1 bs=512 count=2
11. sudo cp boot /Volumes/EFI

 

The Chameleon bootloader loaded and everything seemed to work fine (Windows booted like a charm) - but ALAS when I tried to boot into OSX, I got lots of SMC errors and IOKitWaitQuiet errors etc, and then the system hung with a light blue screen. With a little googling, I think the reason was that the blacklists needed for Wolfies EFI are not working properly. The IOKitWaitQuiet errors manifest when AppleHWSensor.kext (which is normally blacklisted) loads up (correct me if I'm wrong).

 

So, as of now, I didn't get the EFI solution working with the Chameleon bootloader. Luckily the boot code is easy enough to replace.. and now I'm back to the standard boot process..

It's all very nice. I have it running on my boot-132 setup. The Chameleon crew have a installer you can all use. It's for both the standard boot-132 and boot from EFI setup. Play around with it. You'll like it. There's a Extensions folder to dump your kexts. So far, I haven't run into any real issues - can boot into Vista and both Mac partitions from it.

Can't post a link to it, but you can see it at chameleon.osx86.hu

 

Right now, I'm still working on incorporating it into the script. Incidentally, I had a bunch of boot pictures all set up for the PC-EFI v9 setup, converting them to ".raw" with the clut file (color lookup table). But, just got this Chameleon bootloader today, which uses ".png". Heh. So, all boot pictures have been converted over to png for Chameleon v2. A total of 23 boot pictures to choose from. Works okay, now.

 

I just have to get the boot.plist reworked, as we have a new boot.plist location in /Extra. Makes for a bit of confusion regarding which .plist to edit. Grrr.

 

-------------

The reason why that above posted install code doesn't work is that it's not complete!

The kexts aren't being blacklisted because there's no Voodoo kernel installed on the EFI partition (that I can see). It's running the vanilla kernel in the main install location. Ouch.

The Voodoo kernel still needs to be installed on EFI root, although I haven't seen any mention of it in the threads.

Additionally, the Extensions.mkext needs to be packed/rebuilt (This is what Snow Leopard is going to expect) and installed in /Extra also.

 

regards,

MAJ

[nateB]

I've not been able to get a boot-132 Retail install to work. Inevitably I see hangs on something or other. I'm using the .zip kext package from the first post, the voodoo kernel included (with its kext) and a plist with just the busratio=20 -v flag, yet making no progress.

 

Is there a post or thread with thorough details on creating a boot-132 specifically for the EX58-UD5?

[Cosmin Petre]

It's all very nice. I have it running on my boot-132 setup. The Chameleon crew have a installer you can all use. It's for both the standard boot-132 and boot from EFI setup. Play around with it. You'll like it.

Hey MAJ, Been away for a while and just checked in to see Chameleon released. I wondered if you'd got it working with your EFI Boot system yet?

 

Also, what are the real benefits of this loader - eye candy aside - does it offer any significant advantages to the set up we have (wolfs) currently. Is it worth tinkering?

 

thanks

[@ROBASEFR]

I

 

-------------

The reason why that above posted install code doesn't work is that it's not complete!

The kexts aren't being blacklisted because there's no Voodoo kernel installed on the EFI partition (that I can see). It's running the vanilla kernel in the main install location. Ouch.

The Voodoo kernel still needs to be installed on EFI root, although I haven't seen any mention of it in the threads.

Additionally, the Extensions.mkext needs to be packed/rebuilt (This is what Snow Leopard is going to expect) and installed in /Extra also.

 

regards,

MAJ

Hello,

 

I saw the new updated Chameleon-2.0-r431.pkg (april 1st,2009)

What will it install and where ?

 

Will it install on a EFI partition ?

 

Actually I don't have an /Extra folder in my EFI partition, do i have to create it ? If yes, what do I have to put in ?

 

Thanks for your feed back

[beboy]

I have a question… does SATA Raid works with this mother board and MacOS X ?

 

Thanks