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

[bbchucks]

Hey guys. As far as I can tell my sleep/wake is working with 10.5.7. It's S3 for sure because both lights go out on the front of my case. Take a look at my sig and let me know if you need any additional info to troubleshoot.

 

On a side note. I fixed my UUID error #35 by putting UUID.kext in the /Extra folder.

yah my bios has S3 as well, does the other settings in the bios affect this?

strange that me and DD have the same issue though.

[Cosmin Petre]

Wow! Been away for a while and damn, am I behind with the progress?!

 

Any advice appreciated here...

 

I'm still running 10.5.6 on EFI partition with voodoo kernel and the latest kexts from MAJ. I'm planning on setting up a new drive with Chameleon, 10.5.7 etc very soon but for now I sticking with current setup and was wondering if anyone had updated 10.5.6 EFI (Wolf) system?

 

If I was to run the update, am I right in thinking I still need to run the voodoo kernel due to clock speed weirdness? Are there any kexts I need to remove/add (from the last kext package posted by MAJ)?

 

Any feedback from 'old school" EFI-ers appreciated.

 

cheers

[ncsa]

Hi MAJ

 

Sent across another DSDT file .... this one generic and via DSDT GUI

 

Looks like with 10.5.7 the USB plug'n'play is now fully working, so memory sticks/thumb drives are good.

 

Did some editing of smbios to reflect actual HW OC but is there a way for the system to automatically do this so as the OC Changes about MAC is correct?

[mikoffski]

First a BIG thanks to everyone in the thread.... esp. digital_dreamer.

 

I got sleep working on my UD5 rig using

 

 

sudo pmset -a hibernatemode 2

 

 

i'm using the GA-EX58-UD5 - F8b Bios from http://forums.tweaktown.com/f69/gigabyte-latest-bios-28441/

[Asterra]

Hey Maj, or whomever. During the hiatus of the forum, I managed to round up the details pertaining to my current (final?) issue.

 

The issue: After installing vanilla 10.5.6, System Profiler gives the wrong "Model Name" and "Model Identifier". After updating to 10.5.7, this ultimately results in System Profiler failing to provide any info under "hardware".

 

My 10.5.6 installation uses Chameleon v1012, because if I use V2.0 RC1 (what I normally used), the update to 10.5.7 makes OSX unbootable.

 

Now, a fresh 10.5.6 installation using the script and Chameleon v1012 results in the following under System Profiler:

 

Model Name: Mac

Model Identifier: EX58-UD5

 

This is pretty odd, considering that the "Model Identifier" is supposed to be something like "MacPro3,1" or "MacBookPro" or whatever - not the name of the motherboard. Obviously, if the "Model Name" is derived from the "Model Identifier", poor OSX won't have much luck figuring out "EX58-UD5", so I can understand why it defaults to just "Mac" there.

 

I don't recall exactly what these values were with my past Chameleon V2.0 RC1 installs, but I'm pretty sure they were at least valid, like "MacPro4,1" etc.

 

Naturally, the method for specifying "MacPro3,1" with Chameleon v1012 is different from V2.0 RC1. I eventually realized that one has to edit the com.apple.boot.plist and add it to the kernel key string. So I did, and this is what it looked like:

 

<string>busratio=20 macmodel=MacPro3,1 MemSpeed=1600 MemType=DDR3</string>

 

Just like in your very first post, yes. I can confirm that the com.apple.boot.plist edit was a success, because if I choose option 8 in your script ("edit boot plist"), the script shows me what the boot plist already has in it - both in the script itself and on individual volumes. In both the script and on the 10.5.6 install, it properly shows:

 

Kernel key:

busratio=20

macmodel=MacPro3,1

MemSpeed=1600

MemType=DDR3

 

So, here is the problem: Even though the boot plist has MacPro3,1 specified in the right place, System Profiler still shows "Model Name: Mac" and "Model Identifier: EX58-UD5". It's as though specifying this value as MacPro3,1 with Chameleon v1012 does nothing. It gets ignored.

 

I even tried manually adding "macmodel=MacPro3,1" at Chameleon's startup, not that I really expected anything from that. And it didn't help. "Model Name: Mac". "Model Identifier: EX58-UD5". Where is it getting this wrong information? How can I fix it?

 

It needs to be stressed that Chameleon V2.0 RC1 doesn't work for me after the 10.5.7 update. It instantly reboots the moment Chameleon lets it start booting. Only v1012 works.

 

Anyone? ;p

[antareus]

I hate to be that guy, but there might be someone like me reading this.

 

There are three installation methods documented here (supposedly). Which one is best? Which one results in the most pure install? I saw a much simpler install that requires a second Mac posted, but I can't tell if that's method #3 or #4.

 

Any advice on which method to go with would be great. Thanks!

[iamnicos]

I hate to be that guy, but there might be someone like me reading this.

 

There are three installation methods documented here (supposedly). Which one is best? Which one results in the most pure install? I saw a much simpler install that requires a second Mac posted, but I can't tell if that's method #3 or #4.

 

Any advice on which method to go with would be great. Thanks!

 

Hey...you're not a bad guy...don't punish yourself like this man !

 

On this thread there is two methods documented here : Pure EFI (Wolfenuke's one) and DD script method using chamaleon V2 (but DD as updated his script and we are now to V3.5)

 

EFI method is suposed to be closer to a real mac install, as the system remains 100% "vanilla" what so ever. All files you need to boot is stocked in a EFi invisible partition on wich the system is booting from. But you will have to use voodoo kernel (wich is not a bad thing). And ask for support (where is wolfenuke by tha way? Hope is fine) if your update f*cked up your system (like the 10.5.7 wich appears to be more tricky for everyone than a regular update)

 

DD script is a mix between boot 132 (install a retail OSX and modified it in order to make it work, like install kext you need in S/L/E and delet ones you can't have to boot) and EFI (using other elements than the regular system ones, but placed in a different place). It's like having an EFi partition but it's visible and can be tweaked with no big efforts. The man is putting a lot of his time on this thread to help people. Running scrip and updating to 10.5.6 is not an issue (just place system.kext from the script in S/L/E). 10.5.7 update is taking everyone attention right now.

 

"Wich one is better" is depending on the Kernel, the bootloader you want to use, the updates you wanna make...and this is a very big subject.

Because using a certain kernel version or a certain boot loader won't allow you to share info with others and request a related support. From the same install, you can have many parameters that makes you're infos hard to sumarise.

 

Basicaly, if you want support from this thread, the better is to use DD script (latest version) with the kernel provided (9.7 9J56), not to make the 10.5.7 until someone have clear infos and fixes, and to read and ask for infos.

 

Have a good day.

 

ps: the install of DD script has not to be made from a different pc but from a different drive with a distro (like IPC 10.5.6 or kalyway) on it.

[digital_dreamer]

Wow! Been away for a while and damn, am I behind with the progress?!

 

Any advice appreciated here...

 

I'm still running 10.5.6 on EFI partition with voodoo kernel and the latest kexts from MAJ. I'm planning on setting up a new drive with Chameleon, 10.5.7 etc very soon but for now I sticking with current setup and was wondering if anyone had updated 10.5.6 EFI (Wolf) system?

 

If I was to run the update, am I right in thinking I still need to run the voodoo kernel due to clock speed weirdness? Are there any kexts I need to remove/add (from the last kext package posted by MAJ)?

 

Any feedback from 'old school" EFI-ers appreciated.

 

cheers

I don't have the absolute latest kexts in the kext download package now (it may not have the LegacyJMicronATASATAIDE kext for ATA drives on the JMicron controller), but they should work fine for your EFI boot setup. And, as you have already noted, the vanilla kernels and older bootloaders don't mix well, so stick with the Voodoo-based 9.6.0 kernel.

You still have the option to install the latest v2.0 RC1 bootloader onto the EFI partition if you really want to run the vanilla kernels, but you'll have to install it yourself. I've focused much of my time on fine-tuning the /Extra boot process, so really don't have any support included for the EFI partition boot setups in the script.

 

 

Hi MAJ

 

Sent across another DSDT file .... this one generic and via DSDT GUI

 

Looks like with 10.5.7 the USB plug'n'play is now fully working, so memory sticks/thumb drives are good.

 

Did some editing of smbios to reflect actual HW OC but is there a way for the system to automatically do this so as the OC Changes about MAC is correct?

Thanks, again, for providing all these files!

If you can, try my new script v 3.6 and see and if produces a working DSDT file for you. Made a lot of changes to it. You may observe the DSDT log for a status of what happened. Let me know.

 

Regarding the smbios on-the-fly editing: not presently. This feature was originally provided by the modified AppleSMBIOS.kext, which included software code to do this trick. I don't know how to get around this issue and it requires support from the bootloader, so we'll have to wait for someone to provide a solution.

 

<snip>

Now, a fresh 10.5.6 installation using the script and Chameleon v1012 results in the following under System Profiler:

 

Model Name: Mac

Model Identifier: EX58-UD5

<snip>

Anyone? ;p

I think this is happening on your system because we have removed the modified AppleSMBIOS.kext, which originally provided this info. This kext is longer useful for Cham2 RC1 users. That kext is still located in the Misc_Patches/_repository folder. Go ahead and install it and it should retrieve the kernel flags and provide it for System Profiler.

 

I hate to be that guy, but there might be someone like me reading this.

 

There are three installation methods documented here (supposedly). Which one is best? Which one results in the most pure install? I saw a much simpler install that requires a second Mac posted, but I can't tell if that's method #3 or #4.

 

Any advice on which method to go with would be great. Thanks!

iamnicos provided a good explanation.

But, I might add or provide an attempt at simplifying the choice.

The technical advantages between the two have become increasingly slim.

1.

The primary advantage of the EFI boot setup now is in its invisibility - there is no visible evidence of having a patched system. This, however, comes at a manageability cost. It's a little more difficult to see/observe/manage the patches, and you need the Terminal or a script to handle that. Wolf's script handles this, but has a few limitations and some bugs.

Additionally, due to the fact that it's using the older bootloader, no vanilla kernel can be used, only the Voodoo-based kernels.

2.

The primary advantage of the /Extra boot setup is in its manageability, due in part to the visible folders and contents, plus a script that provides much useful information to the user and many features. Unlike wolfienuke's script, this script is continually updated, perhaps too often, much to the chagrin of its users.

An additional plus is that this setup allows the kernel to reside in its natural location in the root directory of the boot drive. This allows some programs, like VMware Fusion, to function without modifications.

 

 

Some news I've found regarding the MacPro4,1 identifier:

Using this identifier is only a problem for those who do NOT have a Core i7 system. Because Apple Software Update may download software specifically compiled for the Core i7 on a MacPro4,1 system, users of older CPUs will clearly experience instability or KPs. So, all of us here shouldn't need to worry about this issue. Continue using this identifier.

 

UPDATE: 5/16/2009

• • Script version 3.6 is released.
  
• • Script includes option to install individual kexts into S/L/E, instead of /Extra/Stored_Kexts. Script keeps track of what's installed into S/L/E and, with a simple selection, they can be restored back to /Extra.
  
• • You have the option to include a "_For_System" folder inside /Extra/Stored_Kexts. This folder offers the following features:
  
  • Any kexts dragged into this folder will get installed into
  S/L/E
  via "
  Update boot caches
  " script routine. Script will also use this folder if it's present for the "
  Kext/kernel installer
  " routine.
  
  
  • Kexts removed from this folder or transfered to
  /Extra
  will be deleted from
  S/L/E
  after the "
  Update boot caches
  " script routine.
  
  
  • For the curious and concerned, original kexts with equivalent names in S/L/E are not replaced, but renamed with ".original" tacked on the filename. Other installed kexts get a duplicate file with ".duplicate" added to filename for script to keep track of.

  
  

• • The "_to_install" folders have been removed from the Kexts directory to help clean it up. Kexts simply need to be outside their "_repository" folders.
  
• • Natit.kext updated
  
• • VoodooHDA v0.2.2 audio kext and prefPane are included for those who wish to use it. This is an Open Source audio driver for our boards.
  
• • Reworked the DSDT routine. Hopefully, the patch will enable all cores without any additional modifications on ASUS and similar boards.
  

Many have been needing to install kexts into S/L/E, so I thought this would be handy. This was a major undertaking and required me to create a specific set of rules and checks. But, in the end, I think some will find it so easy to use - just drag and drop into /Extra/Stored_Kexts or /Extra/Stored_Kexts/_For_System, then "update" and reboot.

 

Note that the "_For_System" folder is not created by the script (it works fine without it) - you must create it. However, if you create this folder inside Stored_Kexts, then the script will use it and you can drag and drop there for S/L/E installs. Without this folder, you can still install into S/L/E from within the script.

 

Just to clarify:

When you use the "Kext/Kernel installer", you are installing from the script's folders. Use this for your initial install or if you need to do a "clean" reinstall.

After that initial install, you can make whatever changes you'd like to the Stored_Kexts (and /_For_System, if included) folder, whether from within the script or outside via drag and drop. To make those changes reflected in the boot, run "Update boot caches". Unlike the "Kext/Kernel installer," these kexts are "installed" via "Update boot caches" from the /Stored_Kexts folders. Once you play with this setup, you'll see how it works.

 

EDIT: This is not different from the process you've already been using. The only difference is the ability to install into S/L/E (inside or outside the script), addition of the "_For_System" folder, and drag and drop capability.

 

If you have any questions, let me know.

 

regards,

MAJ

[Cosmin Petre]

You still have the option to install the latest v2.0 RC1 bootloader onto the EFI partition if you really want to run the vanilla kernels, but you'll have to install it yourself

Thanks MAJ

 

What would be the correct method here?

 

Is installing the new bootloader on EFI best done via terminal?

 

Would I have to copy a version of the vanilla kernel to the EFI partition or do I remove the voodoo kernel and let the system use the vanilla kernel at root? - if so that would that need an edit to the boot.plist (that points at voodoo)?

[Jory Cameron]

Please help me, I am also a total newbie. I have install retail OSX 10.5.5 onto a SATA 1TB HDD through my usb to sata on a hackintoshed mini 9.

I do the following.

 

1. Install OSX 10.5.5 using step 4 in the script.

2. Install the OSX 10.5.7 combo update on to the drive.

3. run the script steps 2,3,5,7 with out the voodoo kernel or the natit.kext in the script.

4. Disconnect my drive and connect it to my GA-EX58-UD5 and boot from it using -V

5. Everything boots properly I go to the script to have it change my processor info.

6. Then I go to the smbois in the extra folder and change my ram value to 24.

7. Lastly I go to check my system profiler and it only shows I have 2 core, and so does the activity monitor!

 

What can I do to fix this?? I need all my cores!

 

Also what do I need to do to get the nvidia geforce 9800GT working properly?

 

 

My sytem is as follows:

 

GA-EX58-UD5

12 GB ram

nvidia 9800 GT

 

 

Please please please help!

[RickyTan]

Wow! Been away for a while and damn, am I behind with the progress?!

 

Any advice appreciated here...

 

I'm still running 10.5.6 on EFI partition with voodoo kernel and the latest kexts from MAJ. I'm planning on setting up a new drive with Chameleon, 10.5.7 etc very soon but for now I sticking with current setup and was wondering if anyone had updated 10.5.6 EFI (Wolf) system?

 

If I was to run the update, am I right in thinking I still need to run the voodoo kernel due to clock speed weirdness? Are there any kexts I need to remove/add (from the last kext package posted by MAJ)?

 

Any feedback from 'old school" EFI-ers appreciated.

 

cheers

 

 

I had a Wolfie install and wanted to stay pure EFI. I would recommend first installing Chameleon 2.0 RC1 before upgrading to 10.5.7. I had issues and KP's all over the place because I tried upgrading to 10.5.7 using Wolfie's method (munky bootloader). However, I was using the Voodoo 9.5.0 kernel. The 9.6.0 Voodoo kernel did not work for me either, but I had so many problems it may have been something else.

 

The short answer is, upgrade to Chameleon 2.0 RC1 first and then upgrade to 10.5.7 so you can use the vanilla 10.5.7 kernel. It's all working for me now, audio included, and I'm pure EFI/vanilla.

Check back a few pages for my post on all the details of how to do the Wolfie --> Chameleon migration.

[Cosmin Petre]

Check back a few pages for my post on all the details of how to do the Wolfie --> Chameleon migration.[/b]

Nice one, cheers. I'll dig out your old post.

 

So, you have no issues at all on 10.5.7?

[Asterra]

Model Name: Mac

Model Identifier: EX58-UD5

 

I think this is happening on your system because we have removed the modified AppleSMBIOS.kext, which originally provided this info. This kext is longer useful for Cham2 RC1 users. That kext is still located in the Misc_Patches/_repository folder. Go ahead and install it and it should retrieve the kernel flags and provide it for System Profiler.

I'm so close, I can taste it. I did remove AppleSMBIOS.kext before (upon recommendation) and had forgotten.

 

Well, just now, I did fresh 10.5.6 install #50, this time with an unmodified version of your 3.5 script, except that the com.apple.boot.plist had things added to the kernel to specify MacPro3,1, 1600Mhz, DDR3, of course. AppleSMBIOS.kext was already included in the _to_install directory by default, so I was good to go.

 

Unfortunately, now that I'm using the fresh 10.5.6 install, I am still seeing the following: Mac Model: Mac. Mac Identifier: EX58-UD5. AppleSMBIOS.kext was installed, alright, because it's right there in Stored_Kexts. I took a look at its info.plist and it has "MacPro3,1" all over the place. So where the heck OSX is getting "EX58-UD5", I haven't a freaking clue.

 

Did I edit the wrong com.apple.boot.plist? (I edited the one in "Plists".)

 

Edit: Based on what you determined about MacPro4,1, I will favor that identifier instead of MacPro3,1. But first I must figure out why OSX (or whatever) is ignoring what I am specifying, and using "EX58-UD5" from wherever it's getting that.

[AdamNJ77]

I used the 3.5 script and have everything working fine as far as I can tell. It is showing all 8 cores for the i7 920. Are there any advantages, or things I should update that the 3.6 script will provide me? My only problem is still waking from sleep. The video and then the tower go to sleep, and the tower wakes back up but I never receive video back. I am using a Sapphire Toxic 4870 1GB Radeon card. Everything else for the card worked natively with the 10.5.7 update. Dual displays work, resolution change, QE/CI, etc... So will the 3.6 help my wake issue, or add any improvements over what I have installed?.

Also, I used DD's script, and I know this a completely stupid newbie question but I don't know whether I installed Vanilla or Voodoo. How can I tell now that the system is up and running? Thanks for any help

[digital_dreamer]

<snip>

Edit: Based on what you determined about MacPro4,1, I will favor that identifier instead of MacPro3,1. But first I must figure out why OSX (or whatever) is ignoring what I am specifying, and using "EX58-UD5" from wherever it's getting that.

So, you're using the Chameleon 1012 bootloader and "macmodel=MacPro4,1" without the quotes as a kernel flag, with that AppleSMBIOS.kext? Just trying to confirm.

 

This is the combination that should work in 10.5.6. In 10.5.7, it's a whole different ball game.

 

MAJ

 

I used the 3.5 script and have everything working fine as far as I can tell. It is showing all 8 cores for the i7 920. Are there any advantages, or things I should update that the 3.6 script will provide me?

<snip>

The new script won't offer any advantages for you. It's using the same kexts. It only offers a bit more flexibility in managing the kexts, that's all.

 

The sleep problems are common in 10.5.7 now and we'll have to wait until the dust settles and all devices get proper sleep support via updates. My issues are just like yours - goes to sleep, but video doesn't wake. Actually, I don't think the system is recovering at all, as there's no USB activity to the devices and the logs don't show anything added until reboot.

 

If you want to know what kernel you're running, the easily way is launching System Profiler and viewing Software system overview.

 

Speaking of the vanilla kernels, I must mention that those of you running 10.5.7 on Chameleon 2, make sure you do not install any of the kernels (or System.kexts) in the script folder, as they are not needed. The included 9.7.0 version in the script folder is actually a slightly older build than the one in the 10.5.7 update, so there were probably some bug fixes or issues resolved. The only kernel I keep in the script folder now is the Voodoo-based 9.6.0 kernel for the Chameleon 1012 bootloader.

 

regards,

MAJ

[animani]

Hi guys I first want to thanks everyone is making this possible.

 

I have been reading through loads of tutorials specially this for the motherboard I want to buy.

 

I have seen someone saying you could do it in an easy way using a Macintosh and a free hard drive for making the hackintosh install.

 

Has anyone done that and actually tell me if that way simplify the process and it solves possible incompatibilities?

 

I am going to use this hardware:

 

Gigabyte X58-UD5

 

Intel Core i7 920 2.66Ghz Box 1366

 

OCZ DDR3 PC3-12800 Platinum XTC Triple Channel 6GB

 

NVIDIA GeForce 6600 LE with 128MB of GDDR SDRAM (from my actual late 2005 Mac)

16x SuperDrive with double-layer support (from my actual late 2005 Mac)

 

[Asterra]

So, you're using the Chameleon 1012 bootloader and "macmodel=MacPro4,1" without the quotes as a kernel flag, with that AppleSMBIOS.kext? Just trying to confirm.

Was using "macmodel=MacPro3,1", actually, but same difference. AppleSMBIOS.kext is included, does install (I see it in Stored_Kexts now). I don't make any modifications to it. I only modify the com.apple.boot.plist located in Plists.

 

This is the combination that should work in 10.5.6. In 10.5.7, it's a whole different ball game.

Understood. When I update to 10.5.7, it does work (and QE/CI starts working), but System Profiler fails even harder. I don't even get "Mac" / "EX58-UD5". I get something like "can't retrieve info". I think the problem can come closer to being resolved if we can just figure out where System Profiler is getting "EX58-UD5" from. I will happily eliminate that text and force it to accept MacPro4,1.

[FUT1L1TY]

Hey,

 

Mine was "kind of" working sometimes. KP only occur few minutes (1 or 2) after, but not correctly.

 

You say you'e on 10.5.7, but wich Kernel version ? Have you run the script after updating ? If so, did you remove the kernel from the folder "to install" to "repository" ? Any other Kext ?

 

regards

 

I did a clean install of 10.5.7 using the following:

 

1) A working machine

2) An extra hard drive that has been freshly formatted

3) 10.5.6 Retail DVD.iso

4) 10.5.7 Combo Update.DMG (724 megs)

5) DD 3.5 script

6) UUID.kext (attached below)

 

Here are the steps I took:

 

1a) Moved mach_kernel and System.kext from the DD 3.5 script into a non-install folder. (We won't be needing these)

 

1b) Placed the UUID.kext in /Misc_Patches/to_install/ of the 3.5 script

 

2) Mount the 10.5.6 Retail and 10.5.7 combo update.

 

3) Launch DD 3.5 Script, enter password, and select the empty hard drive as the install destination.

 

4) Run steps 2, 3, & 4 manually (that is one at a time)

 

5) Launch the 10.5.7 combo updater. Be sure to select the new drive or you will be applying the update to your current startup disk. Run the update.

 

6) Return to the DD 3.5 script. Run steps 5, 6, 7, 9, & 10 manually.

 

7) Restart and enter BIOS. Make sure your new drive is the boot drive.

 

8) Create temp user. Do not migrate at this point. This failed for me.

 

9) Once you reach the finder. Reboot just to be sure.

 

10) This time you can run the migration assistant from the utilities folder. Be sure the "Files and Folders" are not selected (this will overwrite your /Extra Folder).

 

I just thought I share that in case you were having problems with sleep or what not. I'm using the F6 bios still. Safari 4 seems to be working just fine. I've had no KPs.

 

Good luck!

 

EDIT 1: The Combo update is 729mb and can be found here

 

EDIT 2: I forgot to mention to remove LegacyAppleAHCIPort.kext from the installer script. Let's call that step "1c)". You can do that afterwards manually but remember to rebuild the boot cache using the script.

UUID.kext.zip

[digital_dreamer]

Was using "macmodel=MacPro3,1", actually, but same difference. AppleSMBIOS.kext is included, does install (I see it in Stored_Kexts now). I don't make any modifications to it. I only modify the com.apple.boot.plist located in Plists.

 

 

Understood. When I update to 10.5.7, it does work (and QE/CI starts working), but System Profiler fails even harder. I don't even get "Mac" / "EX58-UD5". I get something like "can't retrieve info". I think the problem can come closer to being resolved if we can just figure out where System Profiler is getting "EX58-UD5" from. I will happily eliminate that text and force it to accept MacPro4,1.

Yeah, I get the same response with Cham 1012 and 10.5.7, unfortunately. If you remove the DSDT file from your boot drive, does that EX58-UD remain after reboot? (Can't tell if you're running 10.5.6 or 10.5.7 now. Did you go back to 10.5.6?)

 

MAJ

[Jory Cameron]

Please help me, I am also a total newbie. I have install retail OSX 10.5.5 onto a SATA 1TB HDD through my usb to sata on a hackintoshed mini 9.

I do the following.

 

1. Install OSX 10.5.5 using step 4 in the script.

2. Install the OSX 10.5.7 combo update on to the drive.

3. run the script steps 2,3,5,7 with out the voodoo kernel or the natit.kext in the script.

4. Disconnect my drive and connect it to my GA-EX58-UD5 and boot from it using -V

5. Everything boots properly I go to the script to have it change my processor info.

6. Then I go to the smbois in the extra folder and change my ram value to 24.

7. Lastly I go to check my system profiler and it only shows I have 2 core, and so does the activity monitor!

 

What can I do to fix this?? I need all my cores!

 

Also what do I need to do to get the nvidia geforce 9800GT working properly?

 

 

My sytem is as follows:

 

GA-EX58-UD5

12 GB ram

nvidia 9800 GT

 

 

Please please please help!

 

Ok I did a fresh install and now everything is up and running.

The only problem I have is I need to know how to get my graphics card going.

It's a Nvidia Geforce 9800 GT 512Mb.

What do I need to do?

[Asterra]

4) 10.5.7 Combo Update.DMG (724 megs)

I'm going to give it a shot, because it's starting to look like Chameleon v1012 (the only version that ultimately gives me QE/CI) just won't play nice with 10.5.7 (the only version that gives me QE/CI). I assume you're using Chameleon V2.0 RC1 in this rundown.

 

One question: Where are you getting a 724MB 10.5.7 combo update? The one I grabbed was about 453MB, and I don't see any other. I'm going to go with it anyway, but.. once it fails, it'll be nice to have a different file to try.

 

Oh, another question. What is the migration assistant, and how is it important to the installation process you outlined? I never used or even heard of such a thing. Although, at the same time, I never used the combo update (I always updated via software update).

 

Yeah, I get the same response with Cham 1012 and 10.5.7, unfortunately. If you remove the DSDT file from your boot drive, does that EX58-UD remain after reboot? (Can't tell if you're running 10.5.6 or 10.5.7 now. Did you go back to 10.5.6?)

I always just resinstall 10.5.6 from scratch, whenever it's time to try something new. The DSDT thing is a big mystery to me. I thought it was essential, but it sounds like it's not. If there's an option in the script to simply remove it, I'll try that before I move on with the installation process outlined by FUT1L1TY.

[AdamNJ77]

Is there anywhere I can DL the 3.5 script still? I accidentally erased my copy and want to try Jory Cameron's instructions exactly since he has sleep working. I know 3.6 is an improvement and if I knew what I was doing more I am sure I would be fine with 3.6. I just want to follow his instructions to the letter so if anyone can point me in the direction of 3.5 I would appreciate it. Thanks

[FUT1L1TY]

One question: Where are you getting a 724MB 10.5.7 combo update? The one I grabbed was about 453MB, and I don't see any other. I'm going to go with it anyway, but.. once it fails, it'll be nice to have a different file to try.

 

Try this: support.apple.com/downloads/Mac_OS_X_10_5_7_Combo_Update

 

or just do a google search.

[iamnicos]

Is there anywhere I can DL the 3.5 script still? I accidentally erased my copy and want to try Jory Cameron's instructions exactly since he has sleep working. I know 3.6 is an improvement and if I knew what I was doing more I am sure I would be fine with 3.6. I just want to follow his instructions to the letter so if anyone can point me in the direction of 3.5 I would appreciate it. Thanks

 

Here

 

You meant FUT1L1TY's instructions right ?

 

Be sure to remove kernel and system.kext in repository and to add UUID.kext in msc/patches...

 

Let us know of course...

[Jory Cameron]

Hi guys I first want to thanks everyone is making this possible.

 

I have been reading through loads of tutorials specially this for the motherboard I want to buy.

 

I have seen someone saying you could do it in an easy way using a Macintosh and a free hard drive for making the hackintosh install.

 

Has anyone done that and actually tell me if that way simplify the process and it solves possible incompatibilities?

 

I am going to use this hardware:

 

Gigabyte X58-UD5

 

Intel Core i7 920 2.66Ghz Box 1366

 

OCZ DDR3 PC3-12800 Platinum XTC Triple Channel 6GB

 

NVIDIA GeForce 6600 LE with 128MB of GDDR SDRAM (from my actual late 2005 Mac)

16x SuperDrive with double-layer support (from my actual late 2005 Mac)

 

 

I just did this:

 

1. I took my mini 9 hackintosh, connected my HDD for the x58-ud5 and opened DD's script version 3.6 and ran step 2,3,and 4.

2.updated to 10.5.7 using the combo update and selected my x58 drive for the install(because my retail disc is 10.5.5.

3.Opened the script again and ran step 5( I deleted the kernel and the natit.kext because I wanted a vanilla install and have no need for the natit.kext).

4. I disconnected my HDD and connected it to my GA-EX58-UD5 and booted from it.

5. Once it booted I downloaded the script and ran the processor info changer and then deleted the script.

6. I ran software update and of course checked my system profiler to make sure everything was working.

I show all 4 cores and in activity monitor all 8.

 

My system is as follows:

GA-EX58-UD5

1 TB SATA HDD

OS X 10.5.7 Retail and VMware 2 Win 7 RC 2

LG dual layer burner

Nvidia Geforce 9800GT 512Mb

ocZ 12GB DDR3 Ram

 

If you have issue's booting make sure you have you bios profile the same as DD's.