Jump to content

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


digital_dreamer
 Share

3,054 posts in this topic

Recommended Posts

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

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. :o

 

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....).

 

I am having the clock problem on vanilla kernel, here's my output

 

kern.clockrate: { hz = 100, tick = 10000, tickadj = 1, profhz = 100, stathz = 100 }
hw.tbfrequency: 1000000000
hw.cpufrequency_max: 2666000000
hw.cpufrequency_min: 2666000000
hw.cpufrequency: 2666000000
hw.busfrequency_max: 532000000
hw.busfrequency_min: 532000000
hw.busfrequency: 532000000
hw.busfrequency = 532000000
hw.cpufrequency = 2666000000
hw.tbfrequency = 1000000000

 

I'm betting there's a kext I either need or don't need, since there seems to be at least some overclockers who aren't having the system clock issue. In a related matter, I believe my lower performance marks are probably caused by this same issue. Did OS X underclock my bus?

Link to comment
Share on other sites

I am having the clock problem on vanilla kernel, here's my output

 

kern.clockrate: { hz = 100, tick = 10000, tickadj = 1, profhz = 100, stathz = 100 }
hw.tbfrequency: 1000000000
hw.cpufrequency_max: 2666000000
hw.cpufrequency_min: 2666000000
hw.cpufrequency: 2666000000
hw.busfrequency_max: 532000000
hw.busfrequency_min: 532000000
hw.busfrequency: 532000000
hw.busfrequency = 532000000
hw.cpufrequency = 2666000000
hw.tbfrequency = 1000000000

 

I'm betting there's a kext I either need or don't need, since there seems to be at least some overclockers who aren't having the system clock issue. In a related matter, I believe my lower performance marks are probably caused by this same issue. Did OS X underclock my bus?

Seems to be related to an incorrect bus frequency reporting from the SMBIOS.

Are you guys with this issue using the Chameleon 2.0 bootloader and included smbios.plist?

I'm using the new 2.0 bootloader, but NOT the included smbios.plist

Just using the old AppleSMBIOS.kext that's part of the usual install (not vanilla).

 

Let me know what bootloader and SMBIOS you are using.

 

regards,

MAJ

Link to comment
Share on other sites

Ok, so I have been waiting for someone to post this....and nobody did, so I took matters into my own hands

 

and with out further ado....

 

mach_kernel 9.6.3 and it does work on the i7 just make sure you have disabler.kext and appledecrypt.kext

 

edit: link was broken sorry.

 

http://rapidshare.com/files/221439525/mach_kernel.zip

 

is it just me or is the kernel AMAZING!!! ... everything works flawlessly with the exception of Activity monitor (It shows all of my ram as inactive).

Link to comment
Share on other sites

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

 

It is indeed a boot from EFI partition on my USB stick.

Link to comment
Share on other sites

Seems to be related to an incorrect bus frequency reporting from the SMBIOS.

Are you guys with this issue using the Chameleon 2.0 bootloader and included smbios.plist?

I'm using the new 2.0 bootloader, but NOT the included smbios.plist

Just using the old AppleSMBIOS.kext that's part of the usual install (not vanilla).

 

Let me know what bootloader and SMBIOS you are using.

 

regards,

MAJ

 

 

I'm not using the new 2.0 bootloader. I'm using the one that comes with Wolf's EFI script. I am, however, using both SMBIOSEnabler.kext and AppleSMBIOS.kext as well as Disabler.kext. Here's all the kexts I have on my EFI partition,

 

AppleSMBIOS.kext
Disabler.kext
dsmos.kext
HDAEnabler.kext
IONetworkingFamily.kext
LegacyAppleAHCIPort.kext
LegacyAppleIntelPIIXATA.kext
LegacyHDAController.kext
LegacyHDAPlatformDriver.kext
LegacyIOAHCIBlockStorage.kext
LegacyJMicronJMB36xSATA.kext
SMBIOSEnabler.kext

 

Anything I need or don't need? Will the newer bootloader fix anything? Can I easily swap it out, what do I need to do?

Link to comment
Share on other sites

So, I'm a little lost as to how get started on this whole process--I want to use the EFI partition method, but everything's still somewhat fuzzy to me. Here's what it sounds like I have to do:

 

1) Use Boot-132 to boot a retail Leopard DVD, and format my disk to HFS+ in a GUID partition.

2) Install Leopard onto said partition.

3) Boot Leopard using Boot-132, then run wolfienuke's script.

4) Add in any other kexts that I need.

 

Now, it seems like Chameleon, with the RC1 release a couple of weeks ago, became the ideal bootloader of choice. So I'm assuming that if I want to use it, all I have to do is run the installer .pkg available on the Chameleon site--or do I need to do something extra to first remove the bootloader present in wolfienuke's method?

 

Also, from the sounds of it, I'm going to have to reinstall all of my kexts to the EFI partition again after installing Chameleon, because it looks like its installer formats the EFI partition for you. Am I right about that?

 

If anyone could answer any of these questions and verify that I've got the process laid out in my head correctly, I'd be grateful.

 

 

EDIT: I did a little more poking around in this thread and figured out what I had wrong. Now I get it that you essentially need TWO copies of OS X to do this--one working in some way, in order to set up the GUID partition for the other and install from the Leopard DVD. I was confused and thought that you had to run wolfienuke's script from within the copy of OS X that you want to boot from the EFI partition.

Link to comment
Share on other sites

So, I'm a little lost as to how get started on this whole process--I want to use the EFI partition method, but everything's still somewhat fuzzy to me. Here's what it sounds like I have to do:

 

first just get any version of leopard "working" on a separate disk. Use kalyway, iDeneb, iPC, another mac o... You just need it to prep your "real" hard drive. Once you have a distro working on a separate disk then you can use either method "1" or "2" from the beginning of this thread.

 

You dont have to use boot 132 to make the EFI + retail method work. I had good luck with iPC 10.5.6 in part using advice from DDreamer in post 1 of this thread. I lobjobbed iPC 10.5.6 into pretty good shape. It still took a few days of farting around to get my iPC disk working.

 

Don't get discouraged you'll get through phase 1.

Of course, i'm stuck at the next phase so i'm trying to be patient myself.

 

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

 

So fellas, i've been struggling on this, here's what i have been doing..

 

EFI + retail (wolfienuke) method:

  • boot to the iPC 10.5.6 disk (36gb raptor) and create a partition/format for the retail install via diskutility: GUID/journaled on the 300gb velociraptor.
  • i install Mac OS X retail.dmg from the system>installation>OSInstall.mpkg (full install - don't know how to not install language packs...ideas?)
  • unzip "EFI Boot Installer v3"
  • DELETE all kexts from "EFI Boot Installer v3/Extensions"
  • REPLACE kexts with DD's "GA-EX58-UD5_EFI_boot_kexts" except i leave out Natit.kext (i have 9800gtx+)
  • DELETE default mach.kernel.voodoo REPLACE with DD's mach.kernel "EFI Boot Installer v3/Kernels" (not 9.6.3.. yet)
  • I then copy my "com.apple.boot.plist" into the root of the EFI boot installer folder


    <key>Kernel</key>

    <string>mach_kernel</string>

    <key>Kernel Flags</key>

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

    <key>Timeout</key>

    <string>5</string>

    <key>device-properties</key>

    <string>cd0300000100000001000000c10... etc>


  • Run "install.command" (wolfie's script)
  • select appropriate install drive, select yes to modify com.apple.boot.plist so it will add the UUID, etc
  • reboot (change primary drive in bios to other disk)

Results:

starts booting and then KP's

 

How do I get get the log off the EFI drive so I can show you guys where it KP's?

I'd love to get some ideas about what to do with my kexts.

Ultimately getting the new 9.6.3 kernel working would be fine too..

 

I really want to get the EFI + retail method working.

Link to comment
Share on other sites

stuff

 

I'm still very new at this myself, but Munky's EFI boot guide said that you have to make sure to unmount your EFI partition when you're done making modifications to it. Maybe that would fix the problem? (Munky mentions the error you'll get, but I don't know whether it shows up as a KP or not...)

 

umount /Volumes/EFI

 

Worth a shot, I guess.

Link to comment
Share on other sites

I'm still very new at this myself, but Munky's EFI boot guide said that you have to make sure to unmount your EFI partition when you're done making modifications to it. Maybe that would fix the problem? (Munky mentions the error you'll get, but I don't know whether it shows up as a KP or not...)

 

umount /Volumes/EFI

 

Worth a shot, I guess.

 

I think wolfie's script handles that stuff.

Link to comment
Share on other sites

I think wolfie's script handles that stuff.

 

It does, but I thought maybe you had mounted the EFI partition again and were forgetting to unmount it. You probably aren't doing that, but I'd rather make a silly suggestion and have it not be the solution than not make it and find out that that was the problem all along. :P

Link to comment
Share on other sites

I really want to get the EFI + retail method working.

 

Let wolfienuke's script make the boot.plist and enter:

 

macmodel=MacPro3,1 MemSpeed=1600

 

when it asks for kernel Flags.

 

it might need to enter the boot-uuid, I dont know if that is needed in Chameleon 2 though?

Link to comment
Share on other sites

thanks guys.. phat and matt - appreciate ya' chiming in.

 

I will just keep fiddling. On a side note my machine is running at completely stock voltages and overclocked to 3.6ghz with turbo and all the cpu stuff enabled. I did a 3 hour prime test and none of my core got above 81celsius and my geekbench is 12828. That was literally my first "quick" overclock i first set when i built the system two weeks ago. But now i'm wondering if i should just leave well enough alone. 81 degrees full load is "safe" right?

 

---

 

update : now running 3.75ghz at stock voltage. geekbench 13500 cinebench 20k

havent stress tested it yet.

Link to comment
Share on other sites

I just swaped out the voodoo kernel with 9.6.3 and my sys identifier now says its a MacPro2,1 ?

 

I only noticed after I used geekbench, and the "hackintosh" identifier was gone.

 

I know this is something I can change, but what I'm wondering is, was this from the kernel itself or is my system seeing an older kext now that I'm not using the voodoo kernel?

Link to comment
Share on other sites

@digital_dreamer

 

thanks for the script, it worked well for me on a UD4P motherboard.

 

i dont know if you are planning any more development on this script, but it would be nice if the dsdt patching stage could be broken out separately, or if you can have the dsdt patching stage take a dsdt from disk rather than dumping it from the bios. this would let you run the script from a totally different machine. in my case i ran the script on my badaxe2 and of course the dsdt that ended up on the target disk was completely wrong. i had to delete it, then boot the UD4P on the new disk, and dump/patch the dsdt. luckily it would boot without the patched dsdt.

 

also is deep sleep working on the UD5? its not working on the UD4P (goes to sleep, but then does not wake up properly (don't see any kernel panic logs either.) i'd like to get it working - are there particular kexts that are usually the source of sleep problems?

 

thanks again for your efforts, this is great.

Link to comment
Share on other sites

Seems to be related to an incorrect bus frequency reporting from the SMBIOS.

Are you guys with this issue using the Chameleon 2.0 bootloader and included smbios.plist?

I'm using the new 2.0 bootloader, but NOT the included smbios.plist

Just using the old AppleSMBIOS.kext that's part of the usual install (not vanilla).

 

Let me know what bootloader and SMBIOS you are using.

 

regards,

MAJ

 

I have the same results as boogusboy. Wacky clock. 9.6.3 kernel on the EFI, and also installed via OSX86 tools on the main partition.

 

I'm on the f6 bios, with the wolfinuke installer, using the SMBIOS (created 12/26/2008, v1.1.1) from the updated kext pack listed in the first post of this thread.

Link to comment
Share on other sites

My EFI partition setup has been working great, but...

 

I'm still haven't found out why my computer turns on by itself immediately after shut-down. Anyone had this issue? Which kext might be related? usb?

 

Also, I've been reading about overclocking. The i7 920 seems to have a sweetspot of 3.33-3.66. I read that @ 3.33 you can leave the voltages stock and leave on the turbo mode. I like this option, but when I changed bclk to 166 it didn't like it. I could use a little direction here as well.

 

Thanks again.

Link to comment
Share on other sites

My EFI partition setup has been working great, but...

 

I'm still haven't found out why my computer turns on by itself immediately after shut-down. Anyone had this issue? Which kext might be related? usb?

 

Also, I've been reading about overclocking. The i7 920 seems to have a sweetspot of 3.33-3.66. I read that @ 3.33 you can leave the voltages stock and leave on the turbo mode. I like this option, but when I changed bclk to 166 it didn't like it. I could use a little direction here as well.

 

Thanks again.

 

 

I am running 3.6ghz with turbo on at stock voltage. Using a noctua cooler temps are around 80celsius when the machine ispegged. I have gskill ddr3 1600 ram. I also have a coolermaster UCP700W which is supposed to make really clean power... I think the power supply is helping me achieve a decent overclock at stock voltage. I read that the quality of the power is as or more important than the wattage of your PSU.

 

If you like i can go into bios later and share my settings... really i only fiddled around for a few minutes and havent touched it since. Its possible I could go higher but i'm starting to think that would be greedy.

Link to comment
Share on other sites

Also, I've been reading about overclocking. The i7 920 seems to have a sweetspot of 3.33-3.66. I read that @ 3.33 you can leave the voltages stock and leave on the turbo mode. I like this option, but when I changed bclk to 166 it didn't like it. I could use a little direction here as well.

 

Thanks again.

 

Yah i noticed that on my board.. I have the EX58-UD3R and athe first time i OC'd it, was to 3.33... then i was tinkering around with other settings and pushing it higher... but i noticed I couldnt go back to 166 bclk and be as stable as it was a couple of days prior... as a result of other things, I ended up reseting my BIOS back to stock "optimized" values and starting over, and I was able to dial in 166 again, no prob, with stock voltages and "turbo" mode still on.

 

So reload you default BIOS table, set everything up again from scratch and try 166... 3.33ghz is pretty sweet wothout too much heat. You can push it more, but for me... its plenty fast enough.

Link to comment
Share on other sites

Yah i noticed that on my board.. I have the EX58-UD3R and athe first time i OC'd it, was to 3.33... then i was tinkering around with other settings and pushing it higher... but i noticed I couldnt go back to 166 bclk and be as stable as it was a couple of days prior... as a result of other things, I ended up reseting my BIOS back to stock "optimized" values and starting over, and I was able to dial in 166 again, no prob, with stock voltages and "turbo" mode still on.

 

So reload you default BIOS table, set everything up again from scratch and try 166... 3.33ghz is pretty sweet wothout too much heat. You can push it more, but for me... its plenty fast enough.

 

 

fuma what was your exact process to get the 9.6.3 kernel to work? In terms of steps, kexts, efi vs boot 132, etc?

Link to comment
Share on other sites

I am running 3.6ghz with turbo on at stock voltage. Using a noctua cooler temps are around 80celsius when the machine ispegged. I have gskill ddr3 1600 ram. I also have a coolermaster UCP700W which is supposed to make really clean power... I think the power supply is helping me achieve a decent overclock at stock voltage. I read that the quality of the power is as or more important than the wattage of your PSU.

 

If you like i can go into bios later and share my settings... really i only fiddled around for a few minutes and havent touched it since. Its possible I could go higher but i'm starting to think that would be greedy.

 

Yeah, I didn't figure into my budget a good UPS and I wish I had. I only have stock cooling at the moment as well, which is why I just wanted to try 3.33. I also have ddr3 1600 tripple channel set with the extreme memory profile on. Am I leaving the ram speed at auto? It seems to change it from 1600 to 2000. And what about load line calibration? on/off? Id love to see the bios settings of someone with similar setup.

 

And WHYYY can't I power off...so frustrating.

Link to comment
Share on other sites

Installed EFI + Retail (wolfienuke)

with 9.6.3 and additional kexts

used my graphics string

f6 bios

 

booted up - but having issue with time going fast

  • first thing i noticed the opening apple space animation with all the welcome words was playing in double time
  • next i checked system clock and the minute hand is going really fast - trippy to watch.
  • networking is not working.. self assigning ip (sees cable but doesnt go anywhere with DHCP)
  • everything about the gui "feels" fast, the dock, animations
  • geekbench and cinebench both really low - like 50% slower than my iPC drive
  • shutdown/restart/sleep all not working properly

wonder what the culprit is.

 

Dreamer, have you tried EFI method yet with 9.6.3? I know last you mentioned you only tested it with boot 132.

 

--edit--

p.s. i just realized networking broke after i did apple updates.

I dont have the answers just trying to give the clues.

Link to comment
Share on other sites

fuma what was your exact process to get the 9.6.3 kernel to work? In terms of steps, kexts, efi vs boot 132, etc?

 

Hmmm.. "exact" huh? well, I'm at work right now - so this is off the top of my head - if i misspell anything, but basically the rundown is this:

 

installed kayway 10.5.2 on 80gb internal drive, boot into that "recovery drive"... installed retail 10.5.6 dvd (image) that was "restored" onto a new partition via disk utility on a removeable USB drive...

 

Used digital_dreamers boot 132 script to install DSDT override, voodoo kernel, and most of the standard kexts (omitted the ati injector - I have a nvidia, so I used nvinject). Used his included "repository" audio kexts for my board, but not sure if they are working 100% (headphones don't sound like they have too much bass).

 

Boot into new 10.5.6 drive. (the rest of the steps werent in this order for a specific reason, just my sequence of events as I was testing things out over the course of a few days).

 

Used EFI studio 1.1 to generate EFI strings for display & audio.

 

Removed NVINJECT kext

 

Installed Chameleon 2.0RC1.

 

Removed DSDT.aml in root of drive

 

Found 9.6.3 Kernel, opened .zip with pacifist, and copied to drive.

 

Changed entry in com.apple.Boot.plist to mach_kernel

 

Used Kext helper to install disabler.kext and appledecrypt.kext (voodoo kernel took care of this before)

 

rebooted

 

removed voodoo kernel.

 

--

 

I think that's it.

 

I ultimately want to get this thing purely vanilla... and use EFI partition... I'm still messing with a few things here and there like the audio.... and waiting for 10.5.7 to drop!!!!

 

But like I mentioned, now my system is showing it's a MacPro2,1 not 3,1 and I am still having issues with the samba/afp share name - with both kernels its showing as \\MAC(a bunch of letters and numbers) on my network, and not the "user" name.

 

Sleep works fine, shutdown/restart work, but it feels like its shutting down too fast and not doing it's thing properly.

 

"log out" gives a KP!

 

 

Yeah, I didn't figure into my budget a good UPS and I wish I had. I only have stock cooling at the moment as well, which is why I just wanted to try 3.33. I also have ddr3 1600 tripple channel set with the extreme memory profile on. Am I leaving the ram speed at auto? It seems to change it from 1600 to 2000. And what about load line calibration? on/off? Id love to see the bios settings of someone with similar setup.

 

And WHYYY can't I power off...so frustrating.

 

I wouldnt leave the memory profile on and set to auto - 2000 mhz is too high... unfortunately, you can't seem to "lock" in the memory speed when you adjust the base clock - with this new architecture, the "bclk" controls the speed of everything, so if you up that to overclock your system, you also up the memory speed.

 

You can, however, set a specific multiplier for the memory, to say 8x and your memory should run at a decent 1333 mhz if you are keeping the blck at 166. - you can try setting it to 10x at 166blck (1667-ish speed) if you'd like but I didnt notice much of a difference so far in performance, but I did in heat generation! (My build is specific to an audio enviroment where low fan noise is a must).

 

Also, your line calibration, leave it to "off" (default, I believe) to follow intel specs.

 

As for shutdown, are you using the psystar shutdown kext?

 

hope that helps!

Link to comment
Share on other sites

Installed EFI + Retail (wolfienuke)

with 9.6.3 and additional kexts

used my graphics string

f6 bios

 

booted up - but having issue with time going fast

  • first thing i noticed the opening apple space animation with all the welcome words was playing in double time
  • next i checked system clock and the minute hand is going really fast - trippy to watch.
  • networking is not working.. self assigning ip (sees cable but doesnt go anywhere with DHCP)
  • everything about the gui "feels" fast, the dock, animations
  • geekbench and cinebench both really low - like 50% slower than my iPC drive
  • shutdown/restart/sleep all not working properly

wonder what the culprit is.

 

Dreamer, have you tried EFI method yet with 9.6.3? I know last you mentioned you only tested it with boot 132.

 

--edit--

p.s. i just realized networking broke after i did apple updates.

I dont have the answers just trying to give the clues.

I haven't tried the vanilla kernel on the EFI boot setup. But, from your description of the issues, it sounds rather trippy!

Trying to think what would be different between the EFI partition boot and main partition boot as far as the kernel is concerned. :D (Assuming that the EFI boot contributes to the problem.)

 

regards,

MAJ

Link to comment
Share on other sites

 Share

×
×
  • Create New...