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

[Crash4419]

Heh, the kernel symbols are from System.kext. Were you able to install the System.kext into S/L/E?

 

Here are the UD5_boot-132 kexts. Install them in S/L/E and make sure permissions are repaired or fixed. I have included various kernels and their matching System.kext, so make sure that matching System.kext gets installed, as well. It would be best not to install these on a live system, but if you like to live on the edge, you can certainly try.

These are for Crash4419, garhunie, neils and anyone else not having success with the kexts installed in /Extra.

 

Again, these should be installed in S/L/E. Many of them will replace the vanilla version of the same name. Make sure permissions are repaired. This will give you the same setup as before and still retain the use of the new bootloader.

 

best regards,

MAJ

 

Thank you DD, I will try this in an hour or so. However when you say repair permissions does that mean using disk utility or running chown and chmod in terminal?

[digital_dreamer]

Thank you DD, I will try this in an hour or so. However when you say repair permissions does that mean using disk utility or running chown and chmod in terminal?

Either will work, but the Terminal method is the only thing that will work on the non-Apple kexts like dsmos, Disabler, etc.

 

I'll see about that new PC-EFI V9 bootloader modded by Andy.

 

regards,

MAJ

[Crash4419]

Either will work, but the Terminal method is the only thing that will work on the non-Apple kexts like dsmos, Disabler, etc.

 

I'll see about that new PC-EFI V9 bootloader modded by Andy.

 

regards,

MAJ

 

hmm that might be part of my problem...in that case how do you repair permissions on a separate hard drive through terminal if I am working off my utility drive?

 

chmod -R 755 /Volumes/osx86

chown -R root:wheel /Volumes/osx86/

[joeblough]

hmm that might be part of my problem...in that case how do you repair permissions on a separate hard drive through terminal if I am working off my utility drive?

 

chmod -R 755 /Volumes/osx86

chown -R root:wheel /Volumes/osx86/

 

whoa! don't do that!! you will mess up everything.

 

those commands should only be applied to the extensions in /System/Library/Extensions, and perhaps the kernel itself. if you do this to the whole disk you won't be able to log in anymore!

 

when OSX repairs permissions, it actually consults a table of proper default permissions for all the system-related files. you don't want everything to be 755, for instance. the "7" means root has read, write and execute permission. it does not make sense to give execute permission to a file which is not an executable or shell script.

[Crash4419]

Good news!

 

I booted into my utility drive and ran

 

chmod -R 755 /Volumes/OSX86/System/Library/Extensions

chown -R root:wheel /Volumes/OSX86/System/Library/Extensions

 

now if you remember from previous posts I took the kext's from the Extra folder and placed them in the OSX86/System/Library/Extensions and simply repaired permissions through disk utility.

 

Now atleast the system boots however chameleon still does NOT load the MemSpeed=1333 as listed in com.apple.boot.plist located in both /Extra and /Library/Preferences/SystemConfiguration

[bernito]

Is there any chance I could get a somewhat more detailed outline of what steps you took with which files? I'll explain my points of confusion:

 

1) The guide says to grab 7_radeon_hd_48x0_drivers.pkg and run it. Afterwards, it instructs to grab ATY_Motmot.kext and install that with Kext Helper. Is this (Motmot) the latest Netkas Natit kext?

 

2) A natit kext seems to have been installed a-la Digital Dreamer's scripted OSX installation. Does one need to do something with this preexisting natit kext?

 

3) The guide says to replace the OpenGL.framework in the case of the 4870. Skip this? Or, if you don't skip this, is it important to do this step before the first reboot? (The Guide's chronology isn't 100% clear on this point.)

 

4) How is your 4870 connected to your monitor(s)? The Guide's thread has a lot of evidence suggesting that this actually makes a difference, despite how baffling that may sound.

 

I'm just trying to narrow things down. You say you got it working, but unless Motmot is not the same thing as the latest Netkas Natit kext, I've already undertaken those steps five different times with the same failure each time, necessitating a full reinstall.

 

Here were my steps:

1. Install a retail 10.5.6 image on a newly GPT formatted drive

2. Ran Wolfienuke's installer package and replaced the included the Natit kext with Netkas latest Natit kext.

3. Booted into this new clean Wolfie install.

4. Ran the radeon_hd_48x0_drivers.pkg, repaired permissions and rebooted.

5. Attached a DVI cable to the port closest to the motherboard on my ATI Diamond HD4870 card and it worked the first time.

 

I didn't use/do anything with ATY_Motmot.kext or OpenGL.framework. Hope this is helpful and good luck.

[joeblough]

Good news!

 

I booted into my utility drive and ran

 

chmod -R 755 /Volumes/OSX86/System/Library/Extensions

chown -R root:wheel /Volumes/OSX86/System/Library/Extensions

 

now if you remember from previous posts I took the kext's from the Extra folder and placed them in the OSX86/System/Library/Extensions and simply repaired permissions through disk utility.

 

Now atleast the system boots however chameleon still does NOT load the MemSpeed=1333 as listed in com.apple.boot.plist located in both /Extra and /Library/Preferences/SystemConfiguration

 

that's good news. usually OSX throws up a warning that a kext was improperly installed if it does not have the right ownership/permissions. but it probably only does this if you put a bad kext in your boot volume's /System/Library/Extensions. if you put it on a secondary disk i dont think it runs mkextcache, which is what detects the problem.

 

i'm still at work, so i cant check, but i know that chameleon might ignore everything in boot.plist and instead wants to take all SMBIOS related strings from smbios.plist.

 

do you have /Extra/smbios.plist installed?

[neils]

Heh, the kernel symbols are from System.kext. Were you able to install the System.kext into S/L/E?

 

Here are the UD5_boot-132 kexts. Install them in S/L/E and make sure permissions are repaired or fixed. I have included various kernels and their matching System.kext, so make sure that matching System.kext gets installed, as well. It would be best not to install these on a live system, but if you like to live on the edge, you can certainly try.

These are for Crash4419, garhunie, neils and anyone else not having success with the kexts installed in /Extra.

 

Again, these should be installed in S/L/E. Many of them will replace the vanilla version of the same name. Make sure permissions are repaired. This will give you the same setup as before and still retain the use of the new bootloader.

 

best regards,

MAJ

 

Thanks for you efforts DD. How should I use the 123 kexts ? Can I just install 10.5.6 on my new disk, using your script ? Should I cope all this kexts to system/library/extensions, and not to the extra folder ? What about the dsdt.aml file ? Should I delete this one in the extra folder ?

 

I have installed OSX 13 times today. I switched to using wolfies method again. I downloaded the efi mounter program you mentioned earlier on in this thread. This is what I did today:

 

1: I formatted the disk I'm installing on again using the guid partition option Succes !

2: In installed the retail copy of OSX (still using my older Pentium D hackintosh) Succes !

3: I dowloaded wolfies script, version 3.1

4: From the first post of this thread I also downloaded the latest kexts for wolfies script, with the 9.6.3 vanilla kernel.

5: I removed all kexts and kernels that came with wolfies script and replaced them with the ones you supplied as the latest kexts in the first post of this thread using the 9.6.3 vanilla kernel (that is the one I would prefer to use)

6: I ran wolfies script

7: After wolfies script was done, I mounted the efi partition, to check if all files were copied. They are all there, so I should be able to boot now. There is also a dsdt.aml file though, but I left it there

8: I umounted the efi partition, and took out the harddisk (probably for the 60th time) to see if my i7 will boot now

9: No boot, this is the screen I get.

 

 

I am (ofcourse) willing to try to install with the latest kexts for the 123 you mentioned DD, but please give me a hand about how to install

 

Btw, I also removed the dsdt.aml file, but then it also didn't boot.

 

I am installing OSX again right now using your script DD. I will report later what the results are.

[Asterra]

Simply use the Natit.kext located in DD's install package and then install the following package: http%3A//www.mediafire.com/%3Fmz1leyhyolh However be sure to customize the install and de-select Natit.kext. In addition you want to always boot with -f

Well, now I've done that. The thing about not installing the Natit.kext was new, so I had hopes that maybe that was the missing ingredient. It was not to be.

 

Two things I should mention, though. First, I have never been able to successfully boot into an OSX with -f. It always gets stuck on some process near the end. Not a loop; not something that would cause the no smoking symbol to appear. Just stuck, forever.

 

Second, this is a little bizarre. I've discovered that it is impossible for me to install OSX (from Kalyway) if my monitor is hooked up to DVI port 1. It panics at around 65%. Three times it did that, and then I switched it back to port 2, and no more issues. I mention this mainly because it may have some bearing on my continued issues with the 4870.

[mangopeach]

mangopeach, I've seen this problem with my recent DD install also. And I've seen it with 9.6.3, 9.6.0 also. Haven't tried the voodoo kernels yet. Here's what I did to fix it.

 

Funny, I'm eating a mango now, champagne, its really good.

 

1. Create the RAID array just like you have and let it error out.

 

2. Reboot.

 

3. Delete the RAID array. Recreate the RAID array. Done.

 

I haven't been successful with booting the my Striped RAID array yet. I like the simple and clear process outlined in using the /Extra folder Chameleon and DD's script. Copying the /Extra folders to the "Boot" drives is just as complicated as using the EFI partition. I digress.

 

Not to mention my attention span is

 

Oh look! A Chicken...

 

 

BINGO. worked like a charm.. thx amigo

[neils]

Hi DD,

 

I reformatted my harddisk again, to try the new 123 kexts you provided.

 

Here is what I did.

 

I formatted the disk and installed osx retail 10.5.6 using my old Pentium D hackintosh. The install was succesful. After that I ran your script, I didn't change a thing, I only changed the kernel to 9.6.3 (instead of the defauly 9.7.0)

 

After I ran the scipt, I took the 123 kexts you provided, and copied them to S/L/E. Then I ran disk utility, and repaired permission on the partition I installed the retail 10.5.6 on. Just to be sure, I deleted the dsdt.anl file in the extra folder.

 

I tried to boot on my i7 (I reset the bios before I installed the harddisk, and set everything just like the picture of your bios in the first post)

 

Chameleon (as always I would almost say) boots up nicely. OSX however doesn't boot. I did get to see the grey apple logo though. The PC restarts within 3 seconds after I try to boot in OSX however. The same when I boot in -V mode or F-mode. Reboot, the old famous loop again !

 

Man. I really, and I mean really, have no clue what else I could try. Can I upload something so you can look what might be my problem ? Something like a boot.plist or a log or whatever ?

 

It's 6.29 am in Holland. I've been working on this from 15.00. It has to work. Other people with an UD4-P have working setups as well. Do I need other kexts ? Can I install just the bare minimum to see what happens then ?

 

In the post above I mentioned the results I had when I used wolfies script. As you can see from the bootscreen, OSX does recognize the UD4-P.

 

Am I overlooking something here ? I have tried like every kernel and every kext package I could find in this thread. I am a smart guy, but I'm in direstraits now.

[digital_dreamer]

Good news!

 

I booted into my utility drive and ran

 

chmod -R 755 /Volumes/OSX86/System/Library/Extensions

chown -R root:wheel /Volumes/OSX86/System/Library/Extensions

 

now if you remember from previous posts I took the kext's from the Extra folder and placed them in the OSX86/System/Library/Extensions and simply repaired permissions through disk utility.

 

Now atleast the system boots however chameleon still does NOT load the MemSpeed=1333 as listed in com.apple.boot.plist located in both /Extra and /Library/Preferences/SystemConfiguration

Great!

So, we're running the 'legacy' kexts in S/L/E, now? That's a interesting scenario. Does everything work? I'm concerned that those 'fake' kexts with equivalent names in S/L/E and that only contain plists would replace the real ones that contain the binaries, plugins, etc. The boot-132 kexts are are the full-featured kexts that are designed for placement in S/L/E.

The smbios.plist in /Extra may be overriding the kernel flags in boot.plist.

 

Thanks for you efforts DD. How should I use the 123 kexts ? Can I just install 10.5.6 on my new disk, using your script ? Should I cope all this kexts to system/library/extensions, and not to the extra folder ? What about the dsdt.aml file ? Should I delete this one in the extra folder ?

 

I have installed OSX 13 times today. I switched to using wolfies method again. I downloaded the efi mounter program you mentioned earlier on in this thread. This is what I did today:

 

1: I formatted the disk I'm installing on again using the guid partition option Succes !

2: In installed the retail copy of OSX (still using my older Pentium D hackintosh) Succes !

3: I dowloaded wolfies script, version 3.1

4: From the first post of this thread I also downloaded the latest kexts for wolfies script, with the 9.6.3 vanilla kernel.

5: I removed all kexts and kernels that came with wolfies script and replaced them with the ones you supplied as the latest kexts in the first post of this thread using the 9.6.3 vanilla kernel (that is the one I would prefer to use)

6: I ran wolfies script

7: After wolfies script was done, I mounted the efi partition, to check if all files were copied. They are all there, so I should be able to boot now. There is also a dsdt.aml file though, but I left it there

8: I umounted the efi partition, and took out the harddisk (probably for the 60th time) to see if my i7 will boot now

9: No boot, this is the screen I get.

I am (ofcourse) willing to try to install with the latest kexts for the 123 you mentioned DD, but please give me a hand about how to install

 

Btw, I also removed the dsdt.aml file, but then it also didn't boot.

 

I am installing OSX again right now using your script DD. I will report later what the results are.

neils,

I appreciate your patience. Just hang in there.

The fact that there is a boot failure allows us to peer into the issues and find a workaround that others may benefit from.

 

That screenshot is pretty interesting. The system sees both System.kexts (on EFI partition and S/L/E) and compares versions. But, it appears to stall on the AppleIntelCPUPowerManagement.kext as if the Disabler.kext is not installed. Note that the Disabler.kext should effectively blacklist the AppleIntelCPUPowerManagement.kext. The Disabler kext was installed in EFI, right?

With those messages, I'd bet the Voodoo kernel would work just fine there and your system would boot. Most of the errors are related to kernel/System.kext mismatch and kexts that should be blacklisted, which the Voodoo kernel does automatically.

 

Still, I can't see how you're having these issues, as now you've run the EFI boot setup and have experienced the same problems. So, the Chameleon 2/Extra issue is not the problem. I'd suggest going back to the kernel we all had good success with and that's the Voodoo kernel.

If you still have the EFI boot setup from wolfienuke's script, use the Voodoo-based 9.6.0 kernel and its matching System.kext. Put that kernel in Kernels folder and System.kext in Extensions and "Install", NOT "update" from wolfienuke's script.

 

Let me know how things are going.

 

EDIT: Okay, don't worry about going back to EFI boot, now that you are on the boot-132 setup...

 

Since you have the kexts copied to S/L/E, open Terminal and perform these two commands and reboot, just as Crash4419 did, substituting your boot drive name in the path:

chmod -R 755 /Volumes/YOUR_BOOT_DRIVE/System/Library/Extensions/
chown -R root:wheel /Volumes/YOUR_BOOT_DRIVE/System/Library/Extensions/

MAJ

[neils]

Hi DD,

 

Thanks again for the quick reply. I really have to go to bed now (it's 7.14 am over here and I have to work at 3 pm. Heck, it's even my birthday today, I'm 28 officially yeah ! lol)

 

I get the error message ' operation not permitted' when I try to repair the permissions. I mounted the drive in my older Pentium D hackintosh. Interesting ! It seems it just doesn't repair any permissions, that would explain a lot ! Now only if I knew how to repair them :-)

[digital_dreamer]

Hi DD,

 

Thanks again for the quick reply. I really have to go to bed now (it's 7.14 am over here and I have to work at 3 pm. Heck, it's even my birthday today, I'm 28 officially yeah ! lol)

 

I get the error message ' operation not permitted' when I try to repair the permissions. I mounted the drive in my older Pentium D hackintosh. Interesting ! It seems it just doesn't repair any permissions, that would explain a lot ! Now only if I knew how to repair them :-)

Oh, those were sudo operations that require you log in as super user.

Type sudo -s, then your password. Then, you'll be able to run those commands.

 

Get your rest and have a great day!

 

kind regards,

MAJ

 

P.S. I just had my birthday on the 28th. I'm 45! groan...

[neils]

I couldn't help myself. I used the sudo -s command and typed my password.

 

Then I typed chown -R root:wheel /Volumes/OSX/System/Library/Extensions/

 

I instantly get a blinking cursor again. Should I fill in my uuid instead of the partition name I installed OSX ? The partition name is OSX.

 

Thanks for your wishes :-) I'm gonna make it a great day. I should go to bed earlier though, but I so much want OSX to run I don't really mind.

[sdstever]

Still trying to get Quartz Extreme working for GeForce 9800 GT 512mb DDR3...

 

I've tried following Aquamac's GFX install instructions... I installed the 9 series drivers from Nvidia... I've tried taking NVinject in and out of the extensions folder and updating the EFI partition. It's weird because no matter what I do, nothing seems to change. It's like the adjustments I'm making aren't being applied or something.

 

I wouldn't mind it as is except for the fact that Final Cut Studio 2 needs QE to install. So... I gotta get this figured out.

 

Am I forgetting something? Any help would be greatly appreciated!

[digital_dreamer]

I couldn't help myself. I used the sudo -s command and typed my password.

 

Then I typed chown -R root:wheel /Volumes/OSX/System/Library/Extensions/

 

I instantly get a blinking cursor again. Should I fill in my uuid instead of the partition name I installed OSX ? The partition name is OSX.

 

Thanks for your wishes :-) I'm gonna make it a great day. I should go to bed earlier though, but I so much want OSX to run I don't really mind.

A "blinking cursor" in the Terminal? That's okay. Should only take a second to do that command.

Did you do the chmod command, too? That should only take a second.

 

Anyhow, get your rest!!

 

regards,

MAJ

[fallbrooks13]

My First build and install success!!!

 

Success for me with this motherboard and at the 920 cpu with 9800gtx. everything works great.

 

Big ups to Digital Dreamer for responding to my PM so quickly and helping me understand that I couldn't run the dsdt patcher while working on the drive at another machine. (I was installing on friends computer then migrating the drive to my machine)

 

Using DD's script with voodoo 9.6.0 kernel and no video kext at all.

modified plist for the busration=20

then installing NVinstaller v.52 after boot up

the rest is completely DD's default install

 

sleep

shutdown

restart

sound in and out

video is supported with Quartz Extreem

 

my computer icon is represented as a macbookpro though

because...

about this mac>moreinfo>Hardware>Model Identifier: MacBookPro5,1

 

read this post by lonerdj http://www.insanelymac.com/forum/index.php?showtopic=17564

 

when i searched for ADP2 i found nothing, i also searched MacBookPro5,1 and nothing.

 

Digital Dreamer, How can i fix this?

 

 

Thanks for all the info here.

[Asterra]

Here were my steps:

1. Install a retail 10.5.6 image on a newly GPT formatted drive

2. Ran Wolfienuke's installer package and replaced the included the Natit kext with Netkas latest Natit kext.

Thanks for the rundown. I'm stuck on this step. Perhaps because I am electing to stick with Digital Dreamer's script, the method one might use to successfully replace the Natit kext is eluding me.

 

What I've been doing is going to /Extras/Extensions on the secondary drive (where Natit.kext is to be found after Digital Dreamer's script has finished) and removing Natit.kext via Terminal. Then, to install the replacement Natit.kext (found in one of the ATI threads and current as of April 22), I've been loading up Kext Helper, importing the kext, and modifying its script so that all of the /System/Library/Extensions paths are changed to /Volumes/MAC/System/Library/Extensions, as this would appear to be the only way to install a kext on a secondary drive. I will admit, however, that I have never actually been able to boot any drive I've thus altered.

 

Upon shutdown, OSX first performs some sort of maintenance whose nature is unknown to me.

 

Since this process is a little involved, I am thinking that there must be some straightforward means of replacing a kext (on a secondary drive) that I simply don't know about.

[worthingtoni]

Good news!

 

I booted into my utility drive and ran

 

chmod -R 755 /Volumes/OSX86/System/Library/Extensions

chown -R root:wheel /Volumes/OSX86/System/Library/Extensions

 

now if you remember from previous posts I took the kext's from the Extra folder and placed them in the OSX86/System/Library/Extensions and simply repaired permissions through disk utility.

 

Now atleast the system boots however chameleon still does NOT load the MemSpeed=1333 as listed in com.apple.boot.plist located in both /Extra and /Library/Preferences/SystemConfiguration

 

Sorry if this have been answered and I might as well be totally wrong about this, but anyway.

 

Do you mean that the MemSpeed shows 1600 MHz in About this Mac? At the moment I'm running my memory at 1600 MHz but before the only way to get it to list 1333 MHz in About this Mac was to edit the Info.plist in the AppleSMBIOS.kext. The strange thing about it is that the MacModel name is MacPro4,1 in About this Mac even though it says MacPro3,1 in AppleSMBIOS.kext's Info.plist. So it seems like macmodel get it's info from /Extra/smbios.plist while MemSpeed get it's info from the Info.plist in AppleSMBIOS.kext.

 

Is there anyway to confirm that my hackintosh identifies the macmodel as MacPro4,1 so it's not just a "cosmetic thing" in About this Mac?

 

And I'm also asking my previous question again. Is there anyone else who got the problem with quicktime in web browsers? When playing mp3's in quicktime it makes my browser stop responding and eventually it forces me to do a hard reset.

 

Jon

[rockyIII]

Thanks very much for the useful guides … my ga-ex58-ud5 is working now with 10.5.6.. ;-)

 

 

 

I had some problems with my PS2 keyboard and mouse… the attached files solved it… maybe you wan to includes those kexts in your script…

ApplePS2kexts_10.5.6.ready.zip

[garhunie]

.....

Big ups to Digital Dreamer for responding to my PM so quickly and helping me understand that I couldn't run the dsdt patcher while working on the drive at another machine. (I was installing on friends computer then migrating the drive to my machine).....

 

 

 

Sorry does DSDT have to be run off the same machine as your installing for? I've been using DD script on my MacBook Pro with a external HDD.

[digital_dreamer]

Sorry does DSDT have to be run off the same machine as your installing for? I've been using DD script on my MacBook Pro with a external HDD.

Yes, it should be. The whole point of DSDT is to gather hardware information of the target Mac to make available to the OS.

However, it has been shown that 10.5.6 ignores some DSDT features. In fact, on some boards, like Gigabyte's, this DSDT info is not really needed.

 

But, this situation will not always be the case. Expect your system to become more dependent on DSDT gathered information in coming updates and, therefore, such information needs to accurately reflect the hardware features of your target Mac.

 

regards,

MAJ

[another_ladiesman217]

hi ive successfully installed my 10.5.6 and everything seems to be working the sound and everything, but im not sure if my RAM is performing as it should be here's a screenshot

 

my ram is a Corsair XMS3 1333mhz

 

[digital_dreamer]

Your RAM should be okay, it's just the reporting info that is incorrect.

 

The boot.plist in YOUR_BOOT_DRIVE/Extra should have a kernel flag, "MemSpeed=1333" without the quotes that should take care of this issue. You can use my script to edit it or edit it manually in a text editor:

<key>Kernel Flags</key>

<string>MemSpeed=1333</string>

You may have other flags within that string, separated by a space.

 

_______________________________________________________

 

I went and added an option to install the Chameleon v1012 bootloader in the script. (It's not uploaded.)

Installing it over the existing v2 RC1 didn't go very well at all. Heh. Created some odd booting characteristics and eventually caused the boot drive to no longer mount. It couldn't be fixed by Disk Utility.

So, after an erase and reinstall of OS X and the v1012 bootloader, it booted fine, but now it exhibited the system clock speedup issue. That's immediately noticeable in the OS X welcome movie and various progress indicators. USB hotplugging was a issue, so it appears I'm just going to have to have the script install the System.kext into S/L/E for any install. Other than that it appears functional.

I'm sure the clock issue doesn't manifest itself with the Voodoo-based kernels, so anyone wishing to use the older bootloaders, like v8 and v9 that's used in EFI boot scripts, and v1012, should just use the Voodoo-based kernels with the usual busratio=20 flag until we find a work-around for the clock issue.

 

regards,

MAJ