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

[Templeton Peck]

I'm heaving a problem with my system clock going too fast, and I suspect that it is related to the fact that my system profiler displays in memory section 'There was an error while gathering this information.' , and 'about this mac' shows 6GB 400MHz RAM, while in fact it is 1600MHz.

the busratio argument in /Extra/com.apple.boot.plist must match your CPU multiplier setting in the BIOS. For the 920, the default multiplier is 20. If you don't have a 920, then you need to edit com.apple.boot.plist accordingly.

[Templeton Peck]

I have a little problem myself: I keep getting kernel panics 85% of the way through the installation.

 

Here's what I've done:

I have AHCI enabled in both places in the BIOS. I installed Kalyway 10.5.2 to an old PATA drive, and made an image of my retail 10.5.6 dvd, and downloaded the 10.5.7 update. I also downloaded the files from this guide, and ran the patch script. I formatted the target drive in Disk Utility using GUID, and then ran the script. I chose Chameleon RC1 for my boot loader.

 

For the installation itself, I've tried un-checking everyghing but the base system, but even this does not work -- still panics. I'm at my wit's end! Could my retail disc be too new? Could my Kalyway disc be too old? Is it the fact that I'm trying to install from a PATA drive to a SATA drive? What could possibly be causing this!?

 

I'm in the process of downloading a newer kalyway disc (10.5.6) as we speak, so I'll report back then. Also, I admit I skipped the disk verification that occurs during installation (because the mounting verification turned out ok). So I'm going to sit through both verifications this time, and see if it helps.

 

If anyone has any other ideas, be sure to let me know!

Thanks.

[digital_dreamer]

What part of the script takes care of the information displayed in System Profiler?

I'm heaving a problem with my system clock going too fast, and I suspect that it is related to the fact that my system profiler displays in memory section 'There was an error while gathering this information.' , and 'about this mac' shows 6GB 400MHz RAM, while in fact it is 1600MHz.

 

I have declared all the info as kernel flags:

macmodel=MacPro4,1 (3,1)

MemSpeed=1600

MemType=DDR3

boot-uuid=xxxxxx

But it doesn't affect what is seen by the 'system profiler'. Dos this method work only with Voodoo kernel and the new 10.5.7 vanilla kernel requires another method? I'm a little bit confused, since now there is also the smbios.plist to be modified and athe boot.plist. I thought that modification of smbios.plist is for Chamelen_v2_RC1 but I'm probably wrong.

So what should be modified in a case of Vanilla kernel and Chameleon_v1012?

Actually, the vanilla kernel is not compatible with the older Chameleon bootloaders. You have two choices:

1. Stick with Chameleon v1012 and install Voodoo-based kernel, or

2. Install Chameleon 2 RC to use with the already-installed vanilla kernel (9.7.0).

 

<snip>

IM IN!!! MIX MAX of methods and is WORKING!!! im in OSX!

Congrats!

What was the problem? (for the benefit of others who may encounter the same issue.)

 

P.S. Has anyone tried the new Voodoo2 alpha2 kernel (9.7.0)?

 

regards,

MAJ

 

I have a little problem myself: I keep getting kernel panics 85% of the way through the installation.

 

<snip>

If anyone has any other ideas, be sure to let me know!

Thanks.

I'm thinking this is a issue with the JMicron controller, the infamous >4GB KP bug. But, I would think that the Kalyway system would have that fix installed.

 

I don't have experience with dealing with this bug, but we could try several things:

1. Try "maxmem=2048" without the quotes at the bootloader prompt or include it as a kernel flag in your boot.plist

2. You could pull a stick of your RAM.

3. Use a SATA drive.

4. Install the later Kalyway distro, as you are doing.

 

MAJ

[mattrb]

Not sure if anyone is interested, but there is a hacked newer version of bios for this motherboard that upgrades the AHCI and Intel RAID bioses which results in much faster boot times. You can find it here:

 

http://www.xtremesystems.org/forums/showpo...;postcount=2835

 

Make sure you follow this guide so you don't screw anything up:

 

http://forums.tweaktown.com/f69/bios-flash...sh-guide-27576/

 

Keep up the good work DD! I would also love to see a guide for how to use these kexts and Donk's VMWare templates to setup a OSX image on a Windows machine running with this hardware.

 

I used FlashSPI.exe in dos on my floppy disk and it gave the error:

bios id mismatch error

 

Tried qFlash too but we all know that program is garbage

[Templeton Peck]

I'm thinking this is a issue with the JMicron controller, the infamous >4GB KP bug. But, I would think that the Kalyway system would have that fix installed.

 

I don't have experience with dealing with this bug, but we could try several things:

1. Try "maxmem=2048" without the quotes at the bootloader prompt or include it as a kernel flag in your boot.plist

2. You could pull a stick of your RAM.

3. Use a SATA drive.

4. Install the later Kalyway distro, as you are doing.

Cool, thanks! I'll give it a shot. At one point, I actually suspected bad RAM, but your suggestion makes perfect sense.

 

CONFIRMED: I pulled out a stick, and it installed fine. Since I'm only using the PATA drive for rescue/installation to a SATA drive, I'm comfortable with simply adding maxmem to my boot.plist

[desesperate]

Congrats!

What was the problem? (for the benefit of others who may encounter the same issue.)

 

P.S. Has anyone tried the new Voodoo2 alpha2 kernel (9.7.0)?

 

regards,

MAJ

 

Dear Dear,

Thank You .

Im not sure it will benefit anyone but i will try to explain all with pleasure.

 

So what i did:

 

1. Using MacBook laptop : fresh .ISO install 10.5.6 on USB sata connected HD, previously "GUID Partition" formatted.

 

a. installation of mounted osx.iso was done with this script from terminal : cd /Volumes/Mac\ OS\ X\ Install\ DVD/System/Installation/Packages open OSInstall.mpkg

 

2. Download DSDTPatcherGUI_1 (altrouth it was not working for me = execution of DSDT Patcher GUI.app !!! it helped in other way !!! ) : from DSDTPatcherGUI_1 foldre named : Tools , executed Bootloader.pkg . This instaled clean Chameleon on USB driver for me.

 

3. As Extra folder was created this way : than added : Stored_Kexts folder in and dragged all extensions recommended by you [ May ] into: Extra/Stored_Kexts . In Total 10 items.

 

4. Downloaded : SlimbuildGUI-1, opened SlimbuildGUI.app, ad ktext (10 of them and 1 plist ) than created boot.

This procedure created for me missing Extentions.ktext ! After that : draged Extentions.ktext into Extra folder.

 

5. Set + Repared permisions in Extra/Stored_Kexts + cache reset for Extentions.ktext.

 

6. OSX 10.5.7 combo update.

 

Than i mounted HD into PC, and VOILA! Back into OSX WORLD

 

PS. Sorry to all you guys who do not understand my writing, needless to say EN is not my primary LGE.

Hope this make sense.

 

NOW :

 

There is some problems, very slow HD [copy from external FW or USB HD] or DVD sata LG so slow!.

 

Half of hardware is not recognized in ABOUT THIS MAC : MENU, memory 400MHz, but correct amount. No info about system, no Belkin usb WIFI or dual display, and so on.

 

But MYmac IS HERE so now it can be JUST BETTER !!!!

 

THX

[@ROBASEFR]

Hello,

 

Could any body tell me if I'm the only person who has trouble with Spotlight ?

 

Each time I start up my Hackintosh Spotlight starts re-indexing !

 

Thanks for your feed back

[luh3417]

This is what I'd do in your case:

1. Extract kext using Pacifist without Admin privileges (should be 512k in size).

2. Delete original ATY_Init.kext from S/L/E that was installed by Netkas' installer.

3. Copy new kext to script's Kexts/_Graphics folder.

4. Run #5 (Kext installer).

5. Reboot.

Awesome. I'll give it a shot soon and report back.

I'll try to suss out this anomalous size issue too.

Many thanks,

luh

[Cybex]

I got the WWDC Snow Leopard release from my buddy who is an apple dev. I tested it on the UD5 and it works great. So fast compared to Leopard, you guys will impressed when it is released. Snow Leopard was made for i7 as well as SSD, which is what my SL is on.

 

I only put disabler kext, voodoohda kext (b/c I wasnt sure if non-snow leopard sound works but I successfully know voodoohda works), dsmos kext, and DSDT.

I used the guide at http://osx86.fujilives.com/ & files on the irc: #snowleopard room on irc.osx86.hu

 

A few problems though. Main SL drive doesnt show on desktop but does in finder. Drives show up as orange (LegacyIOAHCIBlockStorage.kext didnt work, do I need something else for this?). Sleep is broken (openhaltkext didnt work).

 

Any suggestions. We need Snow Leopard to work before it comes out or else we will be in the dark come day 1.

 

Hey,

 

I tried to install Snow (10A380) also. Worked fine, till about 1 minute and I got this:

http://freepic.nl/img=0fc147884a

 

Did you encounter panics?

[mattrb]

Hey,

 

I tried to install Snow (10A380) also. Worked fine, till about 1 minute and I got this:

http://freepic.nl/img=0fc147884a

 

Did you encounter panics?

 

no but I got the nasty cmos reset. That is a bummer. I think the KP is from doing something wrong like not making your extension.mkext in SL and doing it in the old leopard. I heard there was issues with that. The cmos is fixed by using a non-gigabyte board, I heard that from some.

[proengin]

no but I got the nasty cmos reset. That is a bummer. I think the KP is from doing something wrong like not making your extension.mkext in SL and doing it in the old leopard. I heard there was issues with that. The cmos is fixed by using a non-gigabyte board, I heard that from some.

 

No, I'm afraid the cmos reset is not limited to Gigabyte boards as it happened to my Asus nforce 790sli mb and Macbook unibody.

[Cybex]

Forgot to mention, but I had the CMOS reset right after the KP. Is Apple playing a joke on us?

 

About the Kernel Panic, I heard m0rpheus on IRC say that the KP is related to spotlight and I had to delete a file. Sombody knows what file I need to remove?

[Dividex0]

that's strange, no problem with a UD4P and chameleon 2 here.

 

It could be that I am screwing it up!

This is my first OS X install.

[Cybex]

The solution for my kernel panic was to remove this file:

/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadata.framework/Versions/A/Support/mdworker

 

Does anybody have a fix for the cmos resetting?

[adamk0]

Actually, the vanilla kernel is not compatible with the older Chameleon bootloaders. You have two choices:

1. Stick with Chameleon v1012 and install Voodoo-based kernel, or

2. Install Chameleon 2 RC to use with the already-installed vanilla kernel (9.7.0).

[...]

 

MAJ

Thanks a lot for this info DD! I've installed Chameleon 2RC, run your script again, and everything is working fine, no problem with the clock, correct bus speed, memory info etc. :-)

Thanks, again.

[luh3417]

Could any body tell me if I'm the only person who has trouble with Spotlight ?

My Spotlight seems to be running a lot more than usual also. I used Migration Assistant did you? Its also possible this is to blame.

 

BTW AROBASEFR, have you run http://www.bresink.com/osx/TemperatureMonitor.html even just the trial version to see what kind of temperatures you are getting on your cores, it says in your signature you OC to 3.0 Ghz on the stock cooler.

[@ROBASEFR]

My Spotlight seems to be running a lot more than usual also. I used Migration Assistant did you? Its also possible this is to blame.

 

BTW AROBASEFR, have you run http://www.bresink.com/osx/TemperatureMonitor.html even just the trial version to see what kind of temperatures you are getting on your cores, it says in your signature you OC to 3.0 Ghz on the stock cooler.

 

No i didn't use migration assistant.

 

My temperature is 56°C ±2°C at start up and maximum 64°C ±2°C depending on core after that.

I didn't use intensif core using software.

[joeblough]

No i didn't use migration assistant.

 

My temperature is 56°C ±2°C at start up and maximum 64°C ±2°C depending on core after that.

I didn't use intensif core using software.

 

i find this hard to believe, what is your Vcore set to? at 3.0GHz i was seeing 20C higher temps than you with the stock cooler. now i have 48C idle and 74C loaded with a cooler master 520 and arctic silver paste.

[mangopeach]

i find this hard to believe, what is your Vcore set to? at 3.0GHz i was seeing 20C higher temps than you with the stock cooler. now i have 48C idle and 74C loaded with a cooler master 520 and arctic silver paste.

 

im clocked to 3.72 at stock voltage

temp at idle around 42-45

temp at load 68-78 (if i do a sustained 5 hour burn it gets closer to 80 but for just a few minutes more like 66-68)

[digital_dreamer]

im clocked to 3.72 at stock voltage

temp at idle around 42-45

temp at load 68-78 (if i do a sustained 5 hour burn it gets closer to 80 but for just a few minutes more like 66-68)

I don't believe you're at stock voltage. If the BIOS is set at AUTO, it'll be bumped up.

Check CPU-Z in Windows for the core voltage.

 

MAJ

[mangopeach]

I don't believe you're at stock voltage. If the BIOS is set at AUTO, it'll be bumped up.

Check CPU-Z in Windows for the core voltage.

 

MAJ

 

doesnt it show the voltage right next to auto in bios?

[joeblough]

doesnt it show the voltage right next to auto in bios?

 

yes it does, but as the load changes on the CPU the motherboard is going to slew the voltage. i don't know what the bios is showing next to auto - is that the current voltage, or the peak voltage, or what?

 

according to the people at tweaktown, its almost always a bad idea to leave bios setting at auto while overclocking. however, i still have not figured out a good value for my mild overclock, and i have not been able to really push the system because when i do, it starts locking up coming out of S3.

 

unfortunately for osx users, all of the good overclock tweaking tools (like CPU-Z, which will show the voltages in real time) are only for windows...

[Cybex]

Guys, the CMOS BIOS reset... Is that happening with everybody, or does it happen with just a few motherboards?

[flat top haircut]

There is not one post about how to fix the pop/crack noises that come from a new DD install on my UD5. This motherboard is garbage if there is not a solution.

 

Does anyone know how to fix the pop/crack noises that certainly ruin my Leopard experience? Do I need a BIOS reset?

 

DD, do you know how to fix?

[luh3417]

Guys, the CMOS BIOS reset... Is that happening with everybody, or does it happen with just a few motherboards?

I think they guys in the couple recent pages are talking about Snow Leopard screwing up their CMOS. If I'm correct in that assumption, then its happening with just motherboards running Snow Leopard 10.6.0 developer release.

 

When you say CMOS BIOS reset, it makes me also think that sometimes the Ethernet disappears. People have been fixing this by: shut down, then while power is off, press the reset CMOS button on the back of the motherboard near the ethernet and USB plugs.

 

I googled around and found out this problem also occurs with other operating systems. And that a slightly simpler solution is to simply shut down, THEN ALSO turn off the power supply or unplug it from the wall for a bit. It just worked for me, in fact it worked better than tapping the reset CMOS button. Plus this way you don't have to re-enter all your BIOS settings.