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

[joeblough]

PS/2 keyboard

I open the terminal and I can write. But if I run the RUN-PATCHER can not write

http://es.geocities.com/dissenys_isa/Picture1.jpg

 

 

 

well when you are entering a password, the system does not echo it back to you so someone can not read your password over your shoulder!

 

just type your password and press return, it will work. this is normal behavior for any unix command line system.

[walterav]

Nice to see this thread is still being updated! Keep up the good work.

 

I didn't know that there was already a vanilla 10.5.6.3 version going around, very nice to see the progress, I just got one question left.

 

Is it already possible getting all the white jmicron ports (4) working? I only got 2 ports working in the non vanilla setup...

[gyasih]

Thanks for the suggestions, I will try later today. I am just looking at all the replies to my post-I installed Vista today and it crashed too. Would a bad GPU cause this kind of shutdown?

 

As we speak, it crashed again 20 ago-within minutes of booting OSX. I booted OSX again and currently I am streaming video to PS3 and downloading stuff and no crash! Weird.

[L3B3R]

PS/2 keyboard

I open the terminal and I can write. But if I run the RUN-PATCHER can not write

http://es.geocities.com/dissenys_isa/Picture1.jpg

I have an idea and it may just be an honest mistake on your part. You need to enter the password from the distro disk (in your case iDeneb), not the one that you are using the script on. Do you have 2 different passwords, one for the distro and one for the retail disks? I use the same password so that I don't have to use my brain . Another possibility is that you don't have a password assigned to the distro disk. If that is the case then you need to create one.

[digital_dreamer]

PS/2 keyboard

I open the terminal and I can write. But if I run the RUN-PATCHER can not write

The password you enter should be your user account password, the same one you enter when installing software. Are you set up as the Administrator of that account? Was one set up when you created your user account? Do you have any odd characters in that password? (I don't think one could be entered anyway)? I only ask that because I remember seeing accents in the hard drive name you posted earlier.

 

Nice to see this thread is still being updated! Keep up the good work.

 

I didn't know that there was already a vanilla 10.5.6.3 version going around, very nice to see the progress, I just got one question left.

 

Is it already possible getting all the white jmicron ports (4) working? I only got 2 ports working in the non vanilla setup...

I didn't know all the jmicron ports weren't working! I never tested them. Is nothing recognized on those ports?

Seems odd they'd be non-operational. Well, our work is never done, is it?

 

Thanks for the suggestions, I will try later today. I am just looking at all the replies to my post-I installed Vista today and it crashed too. Would a bad GPU cause this kind of shutdown?

 

As we speak, it crashed again 20 ago-within minutes of booting OSX. I booted OSX again and currently I am streaming video to PS3 and downloading stuff and no crash! Weird.

When you say "crash" in Vista, are you saying a restart or shutdown, or bluescreen? A crash comes it different flavors and mean different things.

But, your symptoms are certainly characteristic of RAM issues - they're random and dependent on data activity at the problematic memory addresses. You could go all day without a crash, because no data is being read or written in that trouble spot. Then, get them all the time, because that area is being used frequently.

I'm not exactly familiar with 3-channel memory, but I'm sure you can run just one memory module. I'd pull all modules out, but one. (is it a 2GB x 3?) That one module needs to be in the proper bank for operation. Boot your system and do your work. If it crashes, tag that module as bad and check the other two in the same manner. If all three have the same symptoms, it's not likely to be RAM (that would be quite a coincidence), but a motherboard issue. It's likely you'd find one module as bad.

 

All these tests are assuming your RAM timings are correct to begin with.

 

Report back with your findings.

MAJ

[neils]

Hi Digital Dreamer, Wolfie, and all other enthusiasts !

 

First of all, many thanks for the tutorials you both uploaded. It's really appreciated a lot.

 

I have build a new core i7 system, after 7 months of saving money. I really wanted to build a fast hakintosh. Fast, but also compatible with a vanilla install.

 

I have installed OSX 26 times already (I wrote down what I did every single time) but I just can't get OSX to boot. I have tried both DD as well as Wolfies method, but whatever it is, it still doesnt work. I already have a Pentium D hakintosh, running Leo4all based on a guid partitioned drive.

 

I will say precisely what I did, I really hope you guys can help me out !

 

1: I took a brand new harddisk and putted it in my old Pentium D Hakintosh running Leo4all.

 

2: I formatted the new harddisk from this Leo4all install. I created 3 partitions, and choose the GUID partitioned option.

 

3: I created an ISO of my retail 10.5.6 install DVD, and mounted this image.

 

4: I installed OSX on my new harddisk, on a partition I named 'OSX'.

 

5: After install was ready, I downloaded Wolfie's EFI Partition Boot Install, the lastest version (3.1 I tink)

 

6: I didnt add any foreign kext or kernels, I just left Wolfies script as it is.Then I ran the script.

 

7: On my new i7 system, I configured the BIOS exactly as suggested in Digital Dreamers post. AHCI enabled etc.

 

8: I took out the new harddisk, and putted it in my new i7 system

 

9: I powered on te computer.

 

10: Small succes, the darwin bootloader starts !

 

11: Darwin tries to boot my OSX partition, but after 10 seconds it suddenly reboots.

 

12: Same as point 11. Its keep on rebooting. I'm in a loop !

 

13: When I boot in -s mode, I see the Voodoo kernel is loaded, but I also see messages like, 'the ..... disk is read only'

 

I also tried to use digital dreamers method. That one seemed to work, It actually booted up in the new chameleon. I choose to boot OSX, and I also got to see the aplle logo. Unfortunately, it hangs on the apple logo screen. When I boot in -v mode in dd method, I get mesages like '...... has immediate depencies on etc....

 

I have a gigabyte UD4-P motherboard.

 

What could this be ? Should I download other kexts ? I didnt change anything in wolfies method.

 

Could I upload something like my apple.boot.plist, so you guys can see what might be the problem ?

 

Please help me out ! I already read this thread 4 times, but I'm stuck !

 

Many thanks in advance !

[gyasih]

DD-I was talking about a restart, yes my RAM is 2GBX3. I will change my timings 1st on Auto it reads 7-7-7-16 . I believe it should be at 8-8-8-24.

[Crash4419]

So as we look forward to update to 10.5.7 should we go ahead and install the 9.7.0 kernel you posted?

 

also is the included system.kext for 10.5.6? or 10.5.7

 

ALSO my system is now being identified as a MacPro2,1 under 9.6.3 even though I have the boot.plist specified to MacPro3,1

[digital_dreamer]

Hi Digital Dreamer, Wolfie, and all other enthusiasts !

 

First of all, many thanks for the tutorials you both uploaded. It's really appreciated a lot.

 

I have build a new core i7 system, after 7 months of saving money. I really wanted to build a fast hakintosh. Fast, but also compatible with a vanilla install.

 

I have installed OSX 26 times already (I wrote down what I did every single time) but I just can't get OSX to boot. I have tried both DD as well as Wolfies method, but whatever it is, it still doesnt work. I already have a Pentium D hakintosh, running Leo4all based on a guid partitioned drive.

 

I will say precisely what I did, I really hope you guys can help me out !

 

1: I took a brand new harddisk and putted it in my old Pentium D Hakintosh running Leo4all.

 

2: I formatted the new harddisk from this Leo4all install. I created 3 partitions, and choose the GUID partitioned option.

 

3: I created an ISO of my retail 10.5.6 install DVD, and mounted this image.

 

4: I installed OSX on my new harddisk, on a partition I named 'OSX'.

 

5: After install was ready, I downloaded Wolfie's EFI Partition Boot Install, the lastest version (3.1 I tink)

 

6: I didnt add any foreign kext or kernels, I just left Wolfies script as it is.Then I ran the script.

 

7: On my new i7 system, I configured the BIOS exactly as suggested in Digital Dreamers post. AHCI enabled etc.

 

8: I took out the new harddisk, and putted it in my new i7 system

 

9: I powered on te computer.

 

10: Small succes, the darwin bootloader starts !

 

11: Darwin tries to boot my OSX partition, but after 10 seconds it suddenly reboots.

 

12: Same as point 11. Its keep on rebooting. I'm in a loop !

 

13: When I boot in -s mode, I see the Voodoo kernel is loaded, but I also see messages like, 'the ..... disk is read only'

 

I also tried to use digital dreamers method. That one seemed to work, It actually booted up in the new chameleon. I choose to boot OSX, and I also got to see the aplle logo. Unfortunately, it hangs on the apple logo screen. When I boot in -v mode in dd method, I get mesages like '...... has immediate depencies on etc....

 

I have a gigabyte UD4-P motherboard.

 

What could this be ? Should I download other kexts ? I didnt change anything in wolfies method.

 

Could I upload something like my apple.boot.plist, so you guys can see what might be the problem ?

 

Please help me out ! I already read this thread 4 times, but I'm stuck !

 

Many thanks in advance !

Wolfienuke's kexts are specifically designed with the UD5 board in mind. Off hand, I don't know the what the differences are in the two mobos, but I'm sure it wouldn't be enough to prevent the system from booting.

What we need is the photo of the on-screen log. That will help a lot!

 

Best of wishes,

MAJ

 

DD-I was talking about a restart, yes my RAM is 2GBX3. I will change my timings 1st on Auto it reads 7-7-7-16 . I believe it should be at 8-8-8-24.

That should make a difference! Those timings are a bit tight and would certainly be unreliable.

 

So as we look forward to update to 10.5.7 should we go ahead and install the 9.7.0 kernel you posted?

 

also is the included system.kext for 10.5.6? or 10.5.7

 

ALSO my system is now being identified as a MacPro2,1 under 9.6.3 even though I have the boot.plist specified to MacPro3,1

That's entirely up to you.

The System.kexts are the matching pairs for each kernel. One is 9.6.3 and the other 9.7.0

 

As for the model identifier, I'm finding that the kernel is ignoring that flag in our boot.plist. It's still reading "MemSpeed" and "MemType", though.

So, for the fix (we can't change the model identifier), we'll just remap our model name to the "new" identifier.

I've changed the script so that it'll probe the hardware for the identifier and allow you to modify your name based on that identifier. That's probably confusing, let me illustrate:

In the SPMachineTypes.plist is the list of model identifiers and their corresponding name:

	<key>MacPro2,1</key>
<string>MacPro</string>
<key>MacPro3,1</key>
<string>Hackintosh Pro</string>

 

Before, I assumed it would always be MacPro3,1 (because of that kernel flag) so that name stayed fixed. So, any name changes were applied to that string, as you can see above. Now, we'll read MacPro2,1 from the hardware (or any identifier your hardware is set to in the future) and be able to change the string for that key, instead. It'll be more flexible.

 

I'll upload the updated script with support for Extensions in Extra tonight.

 

P.S. I found that I was wrong regarding the new System.kext needing to be in S/L/E. It had failed for me because I had incidentally deleted the vanilla version from that directory. So, you can really have the vanilla System.kext in S/L/E and put the updated one (if you are using an updated/modified kernel) in Extra.

 

MAJ

[Crash4419]

Now why would the kernel force MacPro2,1?

 

Those are the old 8-core Mac Pro's with dual Quad-Core Intel Xeon “Clovertown” 5300 Series processors.

 

Does the identifier affect updates?

[digital_dreamer]

Now why would the kernel force MacPro2,1?

 

Those are the old 8-core Mac Pro's with dual Quad-Core Intel Xeon “Clovertown” 5300 Series processors.

 

Does the identifier affect updates?

Yeah, I know!

 

The MacPro3,1 tag is in three places in our AppleSMBIOS.kext. Not picking up anything there. I'm thinking it's the bootloader and that may be why they supplied us their version of the smbios.plist so we can change such info. I haven't used it, however, but may check it out.

 

MAJ

 

EDIT: As for updates, good call. I believe so. So, it's in our interest to have that changed. I think the new Core i7 ones are MacPro4,1

[dascriter]

Which install did you use? EFI boot or plain boot-132?

Did nothing show up in the Inputs or Outputs in the System Preferences/Sound?

 

As for the drive issue, I know someone else had the same issue and the only solution is to erase or repartition it.

 

 

Yeah, sleep ruins a lot of things. You're not alone. Even if you manage to wake, your system is unstable. I can get KP doing any disk related stuff. My eSATA drive is unrecognized and drops off with a 'disk removal warning.'

 

 

Like others, I haven't had much success using the Extra folder, so the patches are all thrown in S/L/E like usual.

 

 

I get that error every time I run the Terminal on a kernel-updated system. When using 9.6.3 or 9.7.0 kernel, those errors are all over the place.

 

 

I'd look at your system log (Console) for any clues first. If it's hardware related (likely), it may not even be in the log - you'll just see a slight gap in time from the last action taken right to the boot process. My first hunch is a RAM or memory related error, but that usually results in a KP.

 

Post a clip of your system.log from when the system was running right up to the reboot messages.

 

 

You'd think that just using the EFI boot kexts in Extra on a fresh vanilla install would be the ticket. Throwing the patched kexts from a boot-132 install appears to create unresolved dependency issues. I'd guess the Extra could just be used for kexts that have no dependency issues, like dsmos, disabler, Natit, or simply those that did not originate from the OS install.

 

 

Let us know if there are still sleep issues after going back to Voodoo kernel. If the problems persist, I'll see about hacking in an option to install the PC-EFI v9 bootloader.

 

regards,

MAJ

 

 

HUGE thanks to Digital_Dreamer and Wolfienuke... you guys are amazing.

 

Got 10.5.6 up and running... here are my stats:

EX58-UD5

Intel Core i7 920 2.66 gHz

6 GB DDR3 triple-channel

Nvidia GeForce 9800 GT 512

Machine is running fast and looks beautiful... only two problems:

 

1) Audio not working. I've added the ALCinject.kext and the legacy HDA kext and tried everything else I can think of, but still no audio device recognized at all. Is there something I'm missing?

 

2) I finally got Disk Utility to recognize my hard drive for being larger than 128 GB by changing the IDE mode from legacy to native and changing the disk mode from IDE to AHCI in the bios. However, I cannot resize the 128 GB partition or even create a new one. Disk Utility gives me an error... something about "mediakit says partition map too small". If I try to add a new partition, it says "Filesystem does not allow partition size" or something like that. I'm pretty sure others have encountered the same problem. Any fixes for this?

 

Thanks!

Which install did you use? EFI boot or plain boot-132?

Did nothing show up in the Inputs or Outputs in the System Preferences/Sound?

 

As for the drive issue, I know someone else had the same issue and the only solution is to erase or repartition it.

 

I used the EFI boot. And yeah nothing is showing up in inputs or outputs. As for the hard drive already reformatted and dealt with.

 

Thanks

[Crash4419]

If the SPMachineTypes.plist lists all of the currently known Mac identifiers up to 10.5.6 then it is logical to say that by using that kext, the lastest MacPro SHOULD be listed as 3,1 and UNTIL 10.5.7 is released containing the updated kext we will not be seeing 4,1 unless we manually alter the plist.

[joeblough]

DD-I was talking about a restart, yes my RAM is 2GBX3. I will change my timings 1st on Auto it reads 7-7-7-16 . I believe it should be at 8-8-8-24.

 

i'm running corsair XMS3 dimms in my UD4. by default the bios sets up the multipliers for 1066Mhz, and 8-8-8-24. the SPD of these dimms is supposed to say 9-9-9-24 @ 1333Mhz. if you increase the speed to 1333MHz the bios leaves the timings at 8-8-8-24, which is unreliable. i dont know why the bios does not recompute the CAS latencies when you increase the frequency, nor do i know why it decides to use 1066MHz in the first place.

 

i had a lot of instability on resume from sleep and power-on until i fixed the ram timings.

[digital_dreamer]

If the SPMachineTypes.plist lists all of the currently known Mac identifiers up to 10.5.6 then it is logical to say that by using that kext, the lastest MacPro SHOULD be listed as 3,1 and UNTIL 10.5.7 is released containing the updated kext we will not be seeing 4,1 unless we manually alter the plist.

Crash4419,

Sure, but I have no control over the identifier.

EDIT: I just used the included smbios.plist that came with the bootloader (put it in Extra) and it takes care of the identifier. Just open the plist and edit the SMproductname key.

In the meantime, I'm going to see what info our system still uses from the AppleSMBIOS.kext. We may be able to get along without it and just use the smbios.plist in Extra.

 

best regards,

MAJ

 

EDIT: I have updates available on the front page. Everyone should be able to get a really nice setup. Sleep works for me. I can wake and have experienced no instability. VMware Fusion works, too.

[L3B3R]

EDIT: I have updates available on the front page. Everyone should be able to get a really nice setup. Sleep works for me. I can wake and have experienced no instability. VMware Fusion works, too.

There is no way that I can do a fresh install now with all the apps that I have and stuff. I am not exactly sure on how to upgrade so that I can use your new amazing script. Can I do an upgrade from the retail dvd on that drive from inside my disrto and then run the script? Will that get rid of the modified kexts?

[mrmacintosh31]

Now why would the kernel force MacPro2,1? Those are the old 8-core Mac Pro's with dual Quad-Core Intel Xeon "Clovertown" 5300 Series processors. Does the identifier affect updates?

As for updates, good call. I believe so. So, it's in our interest to have that changed. I think the new Core i7 ones are MacPro4,1

 

Here is a screenshot of a Apple Dual i7 system I found somewhere on the net, it seems to confirm that identifier should be 4,1.

 

[digital_dreamer]

There is no way that I can do a fresh install now with all the apps that I have and stuff. I am not exactly sure on how to upgrade so that I can use your new amazing script. Can I do an upgrade from the retail dvd on that drive from inside my disrto and then run the script? Will that get rid of the modified kexts?

No need for a erase and install.

Easy, but longer: reinstall OS X Leopard Retail up to 10.5.6

Less easy, but super quick: Just replace the patched kexts with the vanilla ones I have in the script download. I have all 12 kexts that are deleted/replaced in the download. This is the way I went (pulled it from Retail DVD with Pacifist). Delete all patched kexts - including those that have no vanilla equivalent (dsmos.kext, Disabler.kext, etc. Basically, those with the color label). Also, make sure you Repair Permissions afterward.

(NOTE: I found that I wasn't able to delete all the kexts from the Finder and had to use the Terminal and "rm" them.)

 

I'm not sure about the distro, as I really don't know what gets installed and doesn't.

 

Enjoy!

MAJ

[Fmstrat]

11: Darwin tries to boot my OSX partition, but after 10 seconds it suddenly reboots.

 

12: Same as point 11. Its keep on rebooting. I'm in a loop !

 

Be sure at the Darwin prompt you're hitting F8 and typing busmode=20 in the kernel parameters or this will happen. You can then add this to com.apple.boot.plist as defined in the instructions.

 

 

13: When I boot in -s mode, I see the Voodoo kernel is loaded, but I also see messages like, 'the ..... disk is read only'

 

This generally happens if you're having to use the DVD to boot. If the DVD is still in, be sure to add rd=disk1s1 or whatever your disk is to the kernel paramaters on boot, or you'll actually be trying to mount the DVD in rw mode instead of the installed drive when you get to the terminal.

 

I also tried to use digital dreamers method. That one seemed to work, It actually booted up in the new chameleon. I choose to boot OSX, and I also got to see the aplle logo. Unfortunately, it hangs on the apple logo screen. When I boot in -v mode in dd method, I get mesages like '...... has immediate depencies on etc....

 

I have a gigabyte UD4-P motherboard.

 

Try booting with -f to force the kexts to rebuild. If that doesn't work, use the DVD to boot into terminal mode. Just hit F8, and boot with: busratio=20 rd=disk1s1 -v -s

 

Of course, use your OSX partition instead of disk1s1. After booting, copy over ALL of the kexts from DD's zip file in the first post that are for your hardware. If you skip one, you may get that message. For instance, if you skip JMicron, the ACPI one will throw that error. I beleive they were all color coded red, other than things like Natit that were specific for his video card. After that, be sure your permissions are set properly, and reboot without the DVD, using: busratio=20 -v -f

 

Also, be sure you're using the System.kext that goes with your kernel. That could cause this as well.

[Asterra]

Thanks to Digital Dreamer's script, I am now about 50% done with the whole "install OSX" thing. Rather amazing for only 24 hours of fudging. Anyway, since I don't think anyone else has mentioned this particular panic in this thread, here's where mine craps out. (This is while booting a drive that has vanilla OSX 10.5.6 transparently patched by Digital Dreamer's script, using option 1 and selecting "Yes" at all prompts.)

 

panic(cpu 0 caller 0x004384FF): "Unable to find driver for this platform: \"ACPI\".\n"@/SourceCache/xnu/xnu-1228.12.24/iokit/Kernel/IOPlatformExpert.cpp:1407

 

I can type the rest if it's somehow elucidating. No real idea what I can do to troubleshoot this so there it is. My hardware: Gigabyte UD5, i7 920, SB Audigy2ZS, Sapphire HD4870, WD Caviar 640GB SATA, Pioneer 216 dvd-rom. Settings: 1 core, no hyperthreading, most things disabled.

 

Suggestions? Anyone familiar with this kernel panic? ;p

[iTestTube]

Well, here's the pseudo-boot-132 from EFI setup :

 

My first post. MAJ, your script works brilliantly. My GA-EX58-UD5 setup is 100% after using your script. Updates pass through without issue.

 

Been a lurker for a few days and read through the entire set of threads referenced, including this one. Amazing history!

 

Thank you.

[MasterLen]

@DD

 

your script is great everything except my Video card is running great...

 

I like to add a gfx string for my video card....but I don't no where to put this string...

 

Do I have to put it in the boot.plist in the extra folder?

 

Thanks for your help.

LEN

[Fmstrat]

@DD

 

your script is great everything except my Video card is running great...

 

I like to add a gfx string for my video card....but I don't no where to put this string...

 

Do I have to put it in the boot.plist in the extra folder?

 

Thanks for your help.

LEN

 

This post will walk you through it:

 

http://aquamac.proboards.com/index.cgi?boa...=509&page=1

[Crash4419]

I am am about to do a fresh install w/ 9.7.0

 

Has anyone figured out how to load the Mac4,1 identifier?

 

Or will we have to simply wait until Leopard is updated to know that such a system exists?

[digital_dreamer]

I am am about to do a fresh install w/ 9.7.0

 

Has anyone figured out how to load the Mac4,1 identifier?

 

Or will we have to simply wait until Leopard is updated to know that such a system exists?

In the script folder/~extra/Bootloaders/Chameleon RC1/Extra is a smbios.plist. Edit that plist's SMproductname string and copy it to your boot drive's Extra folder. Chameleon will use this plist for the hardware info. This is the only way I know of for now. The Cham2 bootloader appears to ignore everything else.

 

regards,

MAJ