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

[digital_dreamer]

I have a near flawless DIGITAL_DREAMER'S STANDARD RETAIL DVD INSTALL on one hard drive, but have been surprisingly unsuccessful getting WOLFIENUKE'S BOOT FROM EFI PARTITION RETAIL DVD INSTALL to work on my other drive. I have tried every conceivable kext combo to no avail, so any thoughts are appreciated. I have attached the boot log below and I suspect the culprit is my HD4870, but plenty of folks seem to have a similar setup (and its working fine on the DD Standard Retail drive?

Error: Couldn't read XML property list for multikext archive entry 1.
XML parse error: OSUnserializeXML: syntax error near line 1

bernito,

From you log I quoted above, it looks like you might have used the "increase version numbers" feature in the wolfienuke script and that converts the plists' XML format to binary, leaving a unreadable file at startup. Known bug in the script.

 

I'd suggest re-downloading a fresh copy of the script and run it again without using the "increase version numbers" feature and that will, hopefully, be the ticket.

Or, you could download my updated version of those kexts for boot from EFI setup located on the front page.

 

regards,

MAJ

[feng'a]

Which brings me to a question how to you guys get your system profiler to display the i7 I haven't really tried because it's not that important but just thought I would ask.

 

Mine said Unknown when I first installed... but I used OSx86 Tools to change the description to whatever (Core i7 920)

[Boeing 737]

Hi All,

 

Thank's for this great tutorial, work perfect on my GA X58 UD5.

 

I use the Boot from EFI partition on one disk.

 

By the way i wanted to try to use an USB stick to boot on it and one hard disk with leopard on it.

 

I install the EFI partition on the USB stick and modify the com.apple.boot.plist with the hard disk identifier.

 

It start to boot on the stick as i wanted but not continue to boot on the hard drive where leopard was installed.

 

does i need to add more info on the EFI partition ?

 

Thank you very much

 

Regards.

 

B737

[nateB]

Hi All,

 

I install the EFI partition on the USB stick and modify the com.apple.boot.plist with the hard disk identifier.

 

From what I've read, this method doesn't work so well with the current tools available.

There's some info in this thread. You may also want to look into the new RC of Chameleon.

[Tek]

From what I've read, this method doesn't work so well with the current tools available.

There's some info in this thread. You may also want to look into the new RC of Chameleon.

 

FYI, I have used an 8GB SanDisk Cruzer USB stick to install using the EFI boot partition method and it worked fine. There isn't enough space on it to store my image of Mac OS X 10.5.6 Retail to use to install on a hard drive but I can confirm it does work. I used the same methods to install on a hard drive as I did to install to a USB stick. I eventually used a 120GB 2.5" drive connected via USB instead to perform the same task which is considerably faster than booting from a USB stick.

[zccef]

Thanks Boogusboy! exactly what i was looking for. i recived a waiting for root device error, if i remember correctly that is a storage error. Now i can begain my wolfie EFI boot. I am headed to the beganing of the thread to search as i assume others have run in to the same problem.

 

 

http://i687.photobucket.com/albums/vv234/z...pg?t=1239895597

[bernito]

It works if I use Wolfie's script and kext's unchanged.

 

My question is if I want to use the new Chameleon, should I use the installer and if so, should I only install it to the EFI partition and not load anything else (it comes with a few kexts) or should I download the binaries and use OSX tools to install to EFI partition (again, what to load - only the bootloader or the associated kexts, etc.)?

 

Now on to trying to get vmware fusion to read my vista ultimate hard drive...

 

 

Error: Couldn't read XML property list for multikext archive entry 1.
XML parse error: OSUnserializeXML: syntax error near line 1

bernito,

From you log I quoted above, it looks like you might have used the "increase version numbers" feature in the wolfienuke script and that converts the plists' XML format to binary, leaving a unreadable file at startup. Known bug in the script.

 

I'd suggest re-downloading a fresh copy of the script and run it again without using the "increase version numbers" feature and that will, hopefully, be the ticket.

Or, you could download my updated version of those kexts for boot from EFI setup located on the front page.

 

regards,

MAJ

[chadisawesome]

I did a complete start over and I'm still getting the networking problems so I am almost positive it's hardware related now, but that's not what this post is about.

 

When I did the startover I reformatted the drive from scratch and I "thought" I copied all the kexts correctly, but now my computer is reporting itself as a MacBook Pro instead of MacPro 3,1 which is what it was doing before the re-do. I've done a lot of searching and everyone seems to point to http://my.macdotnub.info/ for the solution, but unfortunately his site is down, so I'm unable to get the files they are pointing to there, so if anyone could let me know what files I need to replace to get the computer to report itself as a MacPro instead of macbook I would appreciate it. I know it probably has very little to do with the system in the grand scheme of things, but I'm a bit of a perfectionist.

 

Thanks again for everyone

[boogusboy]

I did a complete start over and I'm still getting the networking problems so I am almost positive it's hardware related now, but that's not what this post is about.

 

When I did the startover I reformatted the drive from scratch and I "thought" I copied all the kexts correctly, but now my computer is reporting itself as a MacBook Pro instead of MacPro 3,1 which is what it was doing before the re-do. I've done a lot of searching and everyone seems to point to http://my.macdotnub.info/ for the solution, but unfortunately his site is down, so I'm unable to get the files they are pointing to there, so if anyone could let me know what files I need to replace to get the computer to report itself as a MacPro instead of macbook I would appreciate it. I know it probably has very little to do with the system in the grand scheme of things, but I'm a bit of a perfectionist.

 

Thanks again for everyone

 

Digital_Dreamer supplies a boot.plist in the very first post of this thread with machine identification in it. Consult his post, but you can specify in the boot flags.

[mangopeach]

GOOD NEWS

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

I have iPC 10.5.6 running with everything except deep sleep.

 

My 920 is clocking to 3.6ghz at stock voltages.

evga 9800gtx+ fully working.

sound is working.

6gb Gskill ddr3 1600 - running and reporting properly.

 

geekbench is 12819

 

 

BAD NEWS

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

I have been having a heck of a time getting EFI Boot Installer method working.

 

- Replaced the kexts with the one's DD has on the front page for EFI boot method.

- Removed the video kexts since i have a graphics string that works.

- updatedDD's com.apple.boot.plist bootflags, and my video card string in the com.apple.boot.plist

 

 

Here's what i want to do...

I want to use the wolfie EFI Boot Installer with the new 9.6.3 i7 kernel.

I tried to follow the last few pages of banter about this but got lost.

 

Can someone spell it out for me... like here's how you populate files in the EFI Boot Installer to use the new 9.6.3 kernel?

 

DD, maybe you could make a bonus zip file on the first page with the kexts needed for the new 9.6.3 i7 kernel. Which kexts do i need to take out or add to GA-EX58-UD5_EFI_boot_kexts.zip file?

 

I tried making EFI Boot Installer work with the voodoo kernel and it booted but was all wonky.

 

Maybe I just need to keep blundering along until i find it out on my own.

 

Anyway thanks to everybody for your help with this. I need to get my non distro efi + retail method working so im not tempted to use iPC

[woot4fun]

The motherboard is buggy. Both the UD5 and the extreme. The ethernet dies on repeat reboots. I used to get it a lot when setting up my hackintosh. Not so much now as I rarely reboot/switch my mac off.

 

The temporary fix is this: switch your power supply off, wait for all the lights to switch off, then turn it back on.

 

From what I've seen, this is OS and driver independent, a BIOS update could possibly fix this but it remains to be seen.

http://forums.tweaktown.com/f69/ex58-ud5-problem-28739/

http://forums.tweaktown.com/f69/ga-ex58-ex...trollers-30596/

 

On a separate note, I'm pretty sure wake from sleep only works depending on the settings in the BIOS. The same goes for sound. I'm still debugging it, but at the moment I have a setup for 2.66Ghz, get wake from sleep but the sound is crackling. On another, 3.0Ghz, wake from sleep doesn't work (monitor stays off) and sound works fine (there are more differences in settings than the base clock though).

 

Anyone come across this?

 

I returned the first mobo I had over this problem. The new one, 30+ days into use also had a port lock up. The power all the way off cleared the problem up. Thanks for the info.

[Boeing 737]

FYI, I have used an 8GB SanDisk Cruzer USB stick to install using the EFI boot partition method and it worked fine. There isn't enough space on it to store my image of Mac OS X 10.5.6 Retail to use to install on a hard drive but I can confirm it does work. I used the same methods to install on a hard drive as I did to install to a USB stick. I eventually used a 120GB 2.5" drive connected via USB instead to perform the same task which is considerably faster than booting from a USB stick.

 

Hi Tek,

 

Thank's for your answer, yes i can boot on a USB stick with leopard install on it. But do you confirm that you boot on your USB stick with EFI boot partition only on it and with leopard install on a hard disk ?

 

Thank you.

 

Rgr

 

B737

[feng'a]

I'll do a few tests tonight, but I did copy about 300GB of photos from my windows SMB share to my mac with no issues... it seemed to copy at an alright rate... but I'll test for you tonight if you like.

 

ok I did a network copying kinda test copying MP3s from my server (running Vista x64 on a Gigabyte GA-X38-DQ6 via a Netgear Desktop Gigabit switch) to my i7 based hackintosh.

 

Attached is a screenshot of my network monitor

 

 

was getting a fairly consistent transfer with higher peaks after the screenshot was taken... looking to be fairly consistent around 38-40MB/sec

[mattrb]

Can someone spell it out for me... like here's how you populate files in the EFI Boot Installer to use the new 9.6.3 kernel?

If you want vmware fusion, you need to put the 9.6.3 kernel on your Installation drive. EFI Boot Installer will not do that. If you dont care about VMware then you could replace it with the mach_kernel.voodoo inthe kernel folder and supposedly system.kext is not needed because the vanilla kernel uses vanilla system.kext. Unfortunately, the wolfienuke script is dated and has issues for me with swapping kexts that DD supplied.

Also when the version updater is used in the script, it kills the installation for me. Where's wolfie when when you need him.

 

 

DD, maybe you could test this out for us to confirm that your can get your new kexts working so we dont have to give up hope so easy.

[Tek]

Hi Tek,

 

Thank's for your answer, yes i can boot on a USB stick with leopard install on it. But do you confirm that you boot on your USB stick with EFI boot partition only on it and with leopard install on a hard disk ?

 

Thank you.

 

Rgr

 

B737

 

Don't quite remember but I think it is set for EFI boot partition. I'll verify and post the results.

[digital_dreamer]

If you want vmware fusion, you need to put the 9.6.3 kernel on your Installation drive. EFI Boot Installer will not do that. If you dont care about VMware then you could replace it with the mach_kernel.voodoo inthe kernel folder and supposedly system.kext is not needed because the vanilla kernel uses vanilla system.kext. Unfortunately, the wolfienuke script is dated and has issues for me with swapping kexts that DD supplied.

Also when the version updater is used in the script, it kills the installation for me. Where's wolfie when when you need him.

DD, maybe you could test this out for us to confirm that your can get your new kexts working so we dont have to give up hope so easy.

I hope to have something ready for you guys this weekend. Chameleon 2.0 RC1 and vanilla kernel. It's been a busy week.

 

regards,

MAJ

[Cosmin Petre]

I hope to have something ready for you guys this weekend. Chameleon 2.0 RC1 and vanilla kernel. It's been a busy week.

 

regards,

MAJ

MAJ, Are you running Vanilla kernel? If so, have you had any issues with the system clock?

[zccef]

thanks for posting mattrb i was working wolfies script with D_D's updated kexts and i couldnt figure out why it was failing. are you haveing problems with the IONetworkingFamily.kext specificaly RealtekR1000.kext? and then searching for root device? or is that just something i am missing or misinstalling? sorry i cant be more specific as i dont have an immage of the error will get one up when i get home.

 

D_D thanks so much for looking in to the problem.

[digital_dreamer]

MAJ, Are you running Vanilla kernel? If so, have you had any issues with the system clock?

No. I'm not that far along, yet.

Been tied up with other matters.

 

Hope to try this evening. Is the system clock only a issue with OCed boards or is it apparent on stock settings (or a setting close to a Apple spec clock)? If this issue isn't settled, we may have to continue using the Voodoo kernel.

 

I'd guess that since there's no "FSB", Apple probably is using a different variable hidden somewhere. Or, maybe they have the "FSB" variable fixed with a constant we need to use.

 

I don't know much about situation, but I wonder what the Terminal output of the following would produce on both a i7 Hackintosh and i7 Apple system:

sysctl kern.clockrate

and

sysctl hw | grep frequency

regards,

MAJ

 

EDIT: Would someone be able to measure what the clock delta would be after, say, an hour, or some unit of time, preferably a long period? Make sure you have the internet clock sync turned off (not Automatically set Date & Time....).

[Cosmin Petre]

Hope to try this evening. Is the system clock only a issue with OCed boards or is it apparent on stock settings (or a setting close to a Apple spec clock)? If this issue isn't settled, we may have to continue using the Voodoo kernel.

I was experiencing this with stock settings. I have switched back to voodoo for the moment but can help test the vanilla kernel over the weekend if needed.

[mangopeach]

I hope to have something ready for you guys this weekend. Chameleon 2.0 RC1 and vanilla kernel. It's been a busy week.

 

regards,

MAJ

 

thanks amigo - you are a die hard and your efforts are very much appreciated.

[miketress]

Running overclocked i7 920 @ 3.8 Ghz with vanilla kernel ( Kernel not on EFI volume, VMWare working)

 

 
[b]sysctl kern.clockrate[/b]
kern.clockrate: { hz = 100, tick = 10000, tickadj = 1, profhz = 100, stathz = 100 }

[b]sysctl hw | grep frequency[/b]
hw.tbfrequency: 1000000000
hw.cpufrequency_max: 3800000000
hw.cpufrequency_min: 3800000000
hw.cpufrequency: 3800000000
hw.busfrequency_max: 800000000
hw.busfrequency_min: 800000000
hw.busfrequency: 800000000
hw.busfrequency = 800000000
hw.cpufrequency = 3800000000
hw.tbfrequency = 1000000000

 

Time appears to run normally, I'm seeing no difference between my Mac clock and the one on my phone. ( With automatic Date and Time turned off)

 

Mike

 

Edit: After more than an hour, I can confirm the internal clock is running fine.

[Hakintos]

 

Hakintos,

I see two problems with the screenshot:

First, you don't have a GUID partition. It looks like it was formated in Windows (fdisk) or, perhaps, all that got installed in the boot sector is the bootloader. You need to run Disk Utility and reinitailize it as a GUID partition using the "Options" button.

 

The other issue I see would explain why my script has trouble recognizing the drives. There appears to be special characters in the drive name that's causing the columns not to line up in the list. What language and keyboard input are you using?

 

I have a updated script that I hope to have out in a couple days (gotta get my taxes done!!) that will allow you to just select from a list, instead of forcing you to type out the names.

 

Try the disk reformatting first and see how it all goes.

Sounds like a good CMOS clear is in order.

Try reformatting the drive as GUID first before installing anything.

 

 

regards,

MAJ

 

Thanks for everything. GUID and installed with iPC 10.5.6 Also I have installed iDeneb 10.5.6

 

How can I enter my password? I hit the keyboard and I can not write.

[th3joker]

Running overclocked i7 920 @ 3.8 Ghz with vanilla kernel ( Kernel not on EFI volume, VMWare working)

 

 
[b]sysctl kern.clockrate[/b]
kern.clockrate: { hz = 100, tick = 10000, tickadj = 1, profhz = 100, stathz = 100 }

[b]sysctl hw | grep frequency[/b]
hw.tbfrequency: 1000000000
hw.cpufrequency_max: 3800000000
hw.cpufrequency_min: 3800000000
hw.cpufrequency: 3800000000
hw.busfrequency_max: 800000000
hw.busfrequency_min: 800000000
hw.busfrequency: 800000000
hw.busfrequency = 800000000
hw.cpufrequency = 3800000000
hw.tbfrequency = 1000000000

 

Time appears to run normally, I'm seeing no difference between my Mac clock and the one on my phone. ( With automatic Date and Time turned off)

 

Mike

 

Edit: After more than an hour, I can confirm the internal clock is running fine.

 

Hi Mike,

 

I'm running the same as you - 920 i7 OC'd to 3.8GHz and I've tried the new kernel with no success. How where you able to make the switch from the Voodoo kernel successfully.

 

Any pointers will be gratefully received.

[digital_dreamer]

Running overclocked i7 920 @ 3.8 Ghz with vanilla kernel ( Kernel not on EFI volume, VMWare working)

 

 
[b]sysctl kern.clockrate[/b]
kern.clockrate: { hz = 100, tick = 10000, tickadj = 1, profhz = 100, stathz = 100 }

[b]sysctl hw | grep frequency[/b]
hw.tbfrequency: 1000000000
hw.cpufrequency_max: 3800000000
hw.cpufrequency_min: 3800000000
hw.cpufrequency: 3800000000
hw.busfrequency_max: 800000000
hw.busfrequency_min: 800000000
hw.busfrequency: 800000000
hw.busfrequency = 800000000
hw.cpufrequency = 3800000000
hw.tbfrequency = 1000000000

 

Time appears to run normally, I'm seeing no difference between my Mac clock and the one on my phone. ( With automatic Date and Time turned off)

 

Mike

 

Edit: After more than an hour, I can confirm the internal clock is running fine.

I installed the 9.6.3 vanilla kernel on my boot-132 install (not EFI) and left it running all night (12 hours) with no automatic time updates.

I see no evidence of the clock being out of time, either. Running F7A.

 

regards,

MAJ

 

EDIT: The only thing I noticed on that install was mysterious UUID related errors in the Terminal when I do diskutil checks.