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

Good question.

All I know is that on one of my installs with Chameleon 1012, Voodoo-based 9.6.0 kernel, and 10.5.7, things seem to run okay. The only issues I had noticed (I didn't spend too much time in it), was in System reporting. In System Profiler, 'errors in gathering info' for Hardware and Memory. I don't mean wrong specs, just no info.

But, like you, I was curious about the older versions of the bootloaders, like PC-EFI v8 and v9 that's used in Wolf's EFI boot script.

I expected the biggest issue in using the 9.6.0 kernel in 10.5.7, but everything, except reporting, appeared normal.

 

MAJ

 

Thanks for the reply MAJ.

 

What I'll probably do is put my utility HDD back in, and then re-do the EFI partition with your script based on the new kexts and kernel. That way I'm on the same page as everyone else. Then update to 10.5.7.

 

Just out of curiosity. Is there something special about the kexts you used in the wolfie package you used to link to? What i'm trying to say is... is there anything stopping me using the updated kexts/kernel and rerunning Wolfies EFI script and reformatting the EFI partition?

Link to comment
Share on other sites

Thanks for the reply MAJ.

 

What I'll probably do is put my utility HDD back in, and then re-do the EFI partition with your script based on the new kexts and kernel. That way I'm on the same page as everyone else. Then update to 10.5.7.

 

Just out of curiosity. Is there something special about the kexts you used in the wolfie package you used to link to? What i'm trying to say is... is there anything stopping me using the updated kexts/kernel and rerunning Wolfies EFI script and reformatting the EFI partition?

Which kernel do you plan on using?

Since wolf's script uses the older bootloader, the vanilla kernel will cause a system clock speedup issue that will affect timings in just about everything you use. Everything appears to runs about twice the speed. GUI affects, dock bounces, spinning progress indicator, etc. Plus the actual clock that tells time is off. Pretty annoying at best. Ask around. Heh.

So, I'd stay with the Voodoo-based kernel on that bootloader.

 

Your only other option is to update your bootloader on the EFI partition. The Chameleon site has an installer that will do this for you. If you do this, you'd be able to run the new vanilla kernel.

 

regards,

MAJ

Link to comment
Share on other sites

Which kernel do you plan on using?

Since wolf's script uses the older bootloader, the vanilla kernel will cause a system clock speedup issue that will affect timings in just about everything you use. Everything appears to runs about twice the speed. GUI affects, dock bounces, spinning progress indicator, etc. Plus the actual clock that tells time is off. Pretty annoying at best. Ask around. Heh.

So, I'd stay with the Voodoo-based kernel on that bootloader.

 

Your only other option is to update your bootloader on the EFI partition. The Chameleon site has an installer that will do this for you. If you do this, you'd be able to run the new vanilla kernel.

 

regards,

MAJ

 

Hi MAJ.

 

Thanks again for the reply.

 

In that case, I'll change bootloaders and change to the vanilla kernel.

 

Is there anything stopping me running your script on top of my install (already EFI'd with wolf's script).

 

i.e. Take my utility disk, take your script, and associated goodies (kernel/kexts etc), and re EFI my current installation? again, only extra kexts installed into the actual system folder are the ones to get the 4870 working (Natit and the 4x70 pkg).

Link to comment
Share on other sites

hi, i'm using ex58-ud5 with ati 4870

when i install ideneb 1.4 and select only the following:

 

kernel voodoo 9.5

intel ich10

sound alc889a

ethernet r1000

fix patch seatbelt

no video is selected.

 

after the install when i try to boot up i do a -v and it loads for 1-2secs then the system reboots.

 

please advise. should i be selecting vanilla sse3 instead?

 

thanks.

Link to comment
Share on other sites

Hi MAJ.

 

Thanks again for the reply.

 

In that case, I'll change bootloaders and change to the vanilla kernel.

 

Is there anything stopping me running your script on top of my install (already EFI'd with wolf's script).

 

i.e. Take my utility disk, take your script, and associated goodies (kernel/kexts etc), and re EFI my current installation? again, only extra kexts installed into the actual system folder are the ones to get the 4870 working (Natit and the 4x70 pkg).

That would work, but the bootloader that's installed on the EFI partition is going to interfere when you try to boot. Likely because it was made active. You can boot if you select the partition your main install is on from the BIOS.

 

You can erase the EFI partition this way in the Terminal, replacing "X" with your drive number:

diskutil eraseVolume "HFS+" "EFI" diskXs1

 

If you decide to make your boot partition active using my script, double-check the code first (I don't know what version you have):

There is a line in the "fdisk_scrpt" that will have the following:

#./fdisk -e /dev/disk${DISK_ID} < fdisk_makeactive.commands

Make sure there ISN'T a "#" in front of the command, like the above. Remove it, if it does.

 

MAJ

 

hi, i'm using ex58-ud5 with ati 4870

when i install ideneb 1.4 and select only the following:

 

kernel voodoo 9.5

intel ich10

sound alc889a

ethernet r1000

fix patch seatbelt

no video is selected.

 

after the install when i try to boot up i do a -v and it loads for 1-2secs then the system reboots.

 

please advise. should i be selecting vanilla sse3 instead?

 

thanks.

You need to enter "busratio=20" at the boot prompt if you are using the Voodoo kernel on a Core i7 system.

 

MAJ

Link to comment
Share on other sites

reboot cycle when i used the latest DD script.

 

here are my steps, installed using ideneb 1.4 voodoo kernel on HD#1

ran the mobo_installer script and installed everything (used retail dvd 10.5.5) on HD#2

made the HD#2 active, installed chameleon 2.0

rebooted.

chameleon bootloader allows me to select either HD1 or HD2.

i select HD#2 and it just goes and reboot.

tried busratio=20 -v same thing

 

please help!!

Link to comment
Share on other sites

Hi Guys,

 

I am running on the Voodoo Kernel. It all works fine with 10.5.7. I do however have a problem with my lan. It doesn't work. Today was the first day I actually connected my pc to my modem, so I don't know if it ever worked (on 10.5.6) Lan is working in Vista, so the hardware is ok.

 

I know I should keep an install in case I want to run the script. Since I don't have that many harddrives I formatted the disk I installed Kalyway on.

 

Is it possible (till I have money for a new harddisk) to reintall kexts on a live system ? Or should I reinstall Kalyway on a seperate disk (which I don't have at the moment, since I installed Vista on that disk) I doublechecked if appleiofamily.kext (or something like that,I can't acces my MAC drive from Windows) is there, and it is. Could it be I downloaded the script at the time the proper driver for my Realtek LAN was missing ?

 

If I can get my LAN to work I would be happy for the moment. I will do a reinstall as soon as I have a new harddisk. I am broke though at the moment, since I just recieved my HP W2558hc monitor ! Man, what a huge monitor !

 

For the rest, I am using Chameleon V2RC1. Works like a charm. My Hack is recognized as a Macbook Pro though ! I did edit the smbios.plist. Changed it to Mac Pro 3.1 Stil when I login the screen says 'macbook pro'. In system profiler it says it's a Mac Pro 3.1, but the upper part of the textbox says Macbook Pro. How can I change this ? Is there another file besides the smbios.plist I should edit ?

 

Overall things are looking great. And btw, DD, I think I finally know why I had so much trouble getting OSX to boot on my new i7. I have a i7 D0 stepping. There is support for the D0 stepping from BIOS F6. My motherboard had F4 when I recieved it, so the first thing I did (3,5 week) ago when I had my machine up and running is flash the BIOS. At one point my motherboard wouldn't even BOOT into the BIOS anymore, so I used the button on the back of the motherboard to reset the CMOS. At that point I didn't have D0 support anymore, since the BIOS was back to F4. That might have caused bootproblems too ofcourse.

 

F7 (the latest) runs great for me btw. 4 ghz on stock voltage ! I'm not even gonna overvolt the cpu. I am happy the way it runs now.

Link to comment
Share on other sites

The new bootloader installs in the same exact way as the old one, from the script point of view. It's just a different file. So, I'd be confident that the new one would cleanly overwrite the old one. I'm 99% confident. :(

I got some info that may be useful. I went ahead and installed the newer Chameleon over the old. It worked; began booting properly. However, OSX 10.5.7 soon rebooted during boot. Rather than restoring the entire drive image, I reinstalled the old Chameleon over the new, and things were working again - except of course the Hardware information is unavailable and the OS is only seeing and using one core.

 

This firmly establishes the apparent fact that the revision of Chameleon bootloader is a crucial determining factor, when it comes to success using the 4870, the UD5, your script, or a combination of these.

 

And, as you said, it seems that we're going to have to wait for somebody to hack an update to that one file before this particular combination of OSX revision and hardware is properly recognized.

Link to comment
Share on other sites

Hi Guys,

 

I am running on the Voodoo Kernel. It all works fine with 10.5.7. I do however have a problem with my lan. It doesn't work. Today was the first day I actually connected my pc to my modem, so I don't know if it ever worked (on 10.5.6) Lan is working in Vista, so the hardware is ok.

 

I know I should keep an install in case I want to run the script. Since I don't have that many harddrives I formatted the disk I installed Kalyway on.

 

Is it possible (till I have money for a new harddisk) to reintall kexts on a live system ? Or should I reinstall Kalyway on a seperate disk (which I don't have at the moment, since I installed Vista on that disk) I doublechecked if appleiofamily.kext (or something like that,I can't acces my MAC drive from Windows) is there, and it is. Could it be I downloaded the script at the time the proper driver for my Realtek LAN was missing ?

 

If I can get my LAN to work I would be happy for the moment. I will do a reinstall as soon as I have a new harddisk. I am broke though at the moment, since I just recieved my HP W2558hc monitor ! Man, what a huge monitor !

 

For the rest, I am using Chameleon V2RC1. Works like a charm. My Hack is recognized as a Macbook Pro though ! I did edit the smbios.plist. Changed it to Mac Pro 3.1 Stil when I login the screen says 'macbook pro'. In system profiler it says it's a Mac Pro 3.1, but the upper part of the textbox says Macbook Pro. How can I change this ? Is there another file besides the smbios.plist I should edit ?

 

Overall things are looking great. And btw, DD, I think I finally know why I had so much trouble getting OSX to boot on my new i7. I have a i7 D0 stepping. There is support for the D0 stepping from BIOS F6. My motherboard had F4 when I recieved it, so the first thing I did (3,5 week) ago when I had my machine up and running is flash the BIOS. At one point my motherboard wouldn't even BOOT into the BIOS anymore, so I used the button on the back of the motherboard to reset the CMOS. At that point I didn't have D0 support anymore, since the BIOS was back to F4. That might have caused bootproblems too ofcourse.

 

F7 (the latest) runs great for me btw. 4 ghz on stock voltage ! I'm not even gonna overvolt the cpu. I am happy the way it runs now.

 

looks like i have the F6 bios (only one available on gigabyte's website), i've been getting alot of crashes lately too, i'm going to see if i can disable that D0 support, maybe that is my reason i have so many crashes as well!

 

where did you find F7 bios?

Link to comment
Share on other sites

kernel trap, debugger called: panic

kernel loadable modules in backtrace with dependecies

com.superhai.driver.GenericCPUPowermanagement dependency: com.apple.iokit.IOACPIFamily 1.2.0

bsd process name corresponding to current thread kernel_task

mac os version: 9g55

 

constantly getting kernal panic errors like this after running moboinstaller

 

any advice ?

Link to comment
Share on other sites

Found this in a Sound Tutorial Thread

 

HDAenabler needs edit to work on 10.5.7

 

actual HDAenabler info.plist says:

		<key>com.apple.kernel.iokit</key>
	 <string>6.9.9</string>

 

need to say:

		<key>com.apple.kernel.iokit</key>
	 <string>7.9.9</string>

Link to comment
Share on other sites

 

Thank you, now will try to update BIOS from a USB drive using Qflash.

 

 

My KP are definitely related the SPLEEP / SHUTDOWN / REBOOT.

 

Last night, when shutting down, everything was ok, but this morning, when trying to turn that machine on, I saw that in fact my Hacknitosh didn't shut down but went to spleep, and experienced KP waking up...

 

Try now to updtae BIOS and to change modele name...

 

Let you know.

 

nicos

Link to comment
Share on other sites

I have KP after waking up from sleep and then shutdown!

I already changed the MacPro4,1 identifier to MacPro3,1.

I have NO System.kext, NO Applesmbios.kext and NO "LegacyAppleAHCIPort.kext" in /extra.

I am using vanilla 9.7.0 Kernel from 10.5.7 .

And I already have the new F7d Bios.

Link to comment
Share on other sites

I have KP after waking up from sleep and then shutdown!

I already changed the MacPro4,1 identifier to MacPro3,1.

I have NO System.kext, NO Applesmbios.kext and NO "LegacyAppleAHCIPort.kext" in /extra.

I am using vanilla 9.7.0 Kernel from 10.5.7 .

And I already have the new F7d Bios.

 

Same thing...but my BIOS is F5.

 

AHCI mode, C1E disabled, C3,C6... disabled.

 

?

 

ps: Hey MAJ, what is your BIOS version ? Cannont update your Bioles profile from the front page because of dismatching BIOS version. Thanks.

Link to comment
Share on other sites

kernel trap, debugger called: panic

kernel loadable modules in backtrace with dependecies

com.superhai.driver.GenericCPUPowermanagement dependency: com.apple.iokit.IOACPIFamily 1.2.0

bsd process name corresponding to current thread kernel_task

mac os version: 9g55

 

constantly getting kernal panic errors like this after running moboinstaller

 

any advice ?

 

 

I'm hitting the same problem right now. I got kalyway 10.5.2 working and managed to successfully install, combo update, and patch 10.5.6 but I can't boot into it :/

Link to comment
Share on other sites

I'm hitting the same problem right now. I got kalyway 10.5.2 working and managed to successfully install, combo update, and patch 10.5.6 but I can't boot into it :/

If you're using the newer Chameleon bootloader (v2.0 RC1), try installing the older one (v1012). I used the script for this, and it installed over the preexisting bootloader twice without mishap. The reason I make this suggestion is because I confirmed for myself that, at least in my case, v2.0 RC1 would not permit 10.5.7 to boot fully, while v1012 would.

Link to comment
Share on other sites

Hey all. I'm a VERY late adopter... mainly because I can't afford to reformat right now.

 

I'm running Wolfie's script with the 9.6.0 voodoo kernel on a GA-EX58-UD5 and a Sapphire 4870 Dual DVI.

 

My question is whether anyone (if there is such a person out there) is running a system with the Darwin bootloader as per Wolfie's original script and has updated to 10.5.7 successfully?

 

I hIn the EFI partition, I have in the Extensions folder:

 

AppleSMBIOS

ArcMSR (Areca ARC-1222 RAID)

dsmos

HDAEnabler

IONetworkingFamily

LegacyAppleACHIPort

LegacyAppleIntelPIIXATA

LegacyHDAController

LegacyHDAPlatformDriver

LegacyIOACHIBlockStorage

LegacyJMicronJMB36xSATA

System

 

And I have the Natit to suit the 4870 with the 4870 driver pack (7_radeon_hd_48x0_drivers) installed and they're in the HDD's S/L/E.

 

Everything currently works.

 

Just want to make sure.

 

Cheers.

 

 

I'm using Wolfie's script (with the kexts that came with it and 9.6.0) with darwin and am currently running 1.5.7. Just had to re-run the script from my kaly usb drive (probably do to me installing freebsd before booting back into OSX after the update :huh:)

Link to comment
Share on other sites

Thank you, now will try to update BIOS from a USB drive using Qflash.

 

 

My KP are definitely related the SPLEEP / SHUTDOWN / REBOOT.

 

Last night, when shutting down, everything was ok, but this morning, when trying to turn that machine on, I saw that in fact my Hacknitosh didn't shut down but went to spleep, and experienced KP waking up...

 

Try now to updtae BIOS and to change modele name...

 

Let you know.

 

nicos

 

is everyone using S3 or S1 in powermanagement?

 

also i tried going to bios version F4 and still getting kernel panics. doesn't seem to make a difference.

 

anyone with a working bios do you guys have a profile online that we can take a look at?

Link to comment
Share on other sites

Hello guys,

 

Europe is awake, but America is still spleeping i guess...

 

I've tried to change my mac model name, but changing the smbios.plist, only affect my ram (I changed the brand name to see) but does absolutly nothing to the mac model, even if the file is corrected (when I open it, all changed are effective) ? I rebooted of course.

 

Regarding to RAM, altough "About this mac" says 6Go, Istat reconize only 4 GO and "more info" in "About..." says :

ECC : Désactivées

 

Bank0/1/A0 :

 

Taille : 2 Go

Type : DDR3

Vitesse : 1600 MHz

État : OK

Fabricant : GSKILL

Numéro de pièce : 0x48594D503131325336344350362D59352020

Numéro de série : 0x00001020

 

Bank2/3/A1 :

 

Taille : Vide

Type : Vide

Vitesse : Vide

État : Vide

Fabricant : Vide

Numéro de pièce : Vide

Numéro de série : Vide

 

Bank4/5/A2 :

 

Taille : 2 Go

Type : DDR3

Vitesse : 1600 MHz

État : OK

Fabricant : GSKILL

Numéro de pièce : 0x48594D503131325336344350362D59352020

Numéro de série : 0x00003021

 

Bank6/7/A3 :

 

Taille : Vide

Type : Vide

Vitesse : Vide

État : Vide

Fabricant : Vide

Numéro de pièce : Vide

Numéro de série : Vide

 

Bank8/9/A4 :

 

Taille : 2 Go

Type : DDR3

Vitesse : 1600 MHz

État : OK

Fabricant : Apple Inc.

Numéro de pièce : ABCDEFGHIJ

Numéro de série : 1234567890

 

Bank10/11/A5 :

 

Taille : Vide

Type : Vide

Vitesse : Vide

État : Vide

Fabricant : Vide

Numéro de pièce : Vide

Numéro de série : Vide

 

"

 

Is the all 6Go working?

 

Are we gonna have the same kernel panic when RAM in use is gonna be over 4Go, as we experienced with former hacknitoshes (when RAm was over 3Go) ?

 

 

For info :

 

When an eSATA drive is plugged (Using a bracket plugged into Jmicron Onboard Sata Ports, the white ones) the sytem cannot recover from a sleep. I imagine it's because he cannot turn it off...

 

 

 

My first WD Velociraptor drive is now fixed, I guess I'm gonna move back to 10.5.6 and Kernel 9,7 9j56... But continu test on the other drive.

 

Call: Does anyone have OC bios profil for BIOS F5 ? Would appreciate it as I don't know why, I can't OC my system, even with good "how to"...

 

is everyone using S3 or S1 in powermanagement?

 

also i tried going to bios version F4 and still getting kernel panics. doesn't seem to make a difference.

 

anyone with a working bios do you guys have a profile online that we can take a look at?

 

S3 is a must.

 

Who's got a BIOS profile for F5...good question man.

Link to comment
Share on other sites

very strange, when i go to integrated peripherals and have:

onboard Sata/ide device to ENABLED and MODE: AHCI

maybe 2-3secs after typing busratio=20 -v it loads then boom freezes while using voodoo kernel.

 

if i have this disabled in bios it loads the kernel further but i get:

 

AppleDecrypt: page_transform: in_blk = 0x2dd27000, out_blk = 0x2dd28000

AppleDecrypt: page_transform: in_blk = 0x2dd27000, out_blk = 0x2dd28000

AppleDecrypt: page_transform: in_blk = 0x2dd27000, out_blk = 0x2dd28000

AppleDecrypt: page_transform: in_blk = 0x2dd27000, out_blk = 0x2dd28000

AppleDecrypt: page_transform: in_blk = 0x2dd27000, out_blk = 0x2dd28000

AppleDecrypt: page_transform: in_blk = 0x2dd27000, out_blk = 0x2dd28000

AppleDecrypt: page_transform: in_blk = 0x2dd27000, out_blk = 0x2dd28000

AppleDecrypt: page_transform: in_blk = 0x2dd27000, out_blk = 0x2dd28000

AppleDecrypt: page_transform: in_blk = 0x2dd27000, out_blk = 0x2dd28000

AppleDecrypt: page_transform: in_blk = 0x2dd27000, out_blk = 0x2dd28000

AppleDecrypt: page_transform: in_blk = 0x2dd27000, out_blk = 0x2dd28000

AppleDecrypt: page_transform: in_blk = 0x2dd

 

and it hangs.

 

any help is greatly appreciated!

Link to comment
Share on other sites

MAJ

 

DSDT files sent .. Process was via ur post #1 using RC1 and genuine Retail DVD 10.5.6... will send a few more examples once the other machine becomes available.

 

Gotta love those 8-cores .. pushed Geekbench up ... now 14K+ :(

 

thxs

 

If you happen to have a copy of the dsdt file that your system created (that didn't work) and a copy of the one that was supplied to you, would you be able to post it for me? I'd like to compare them and see what can be done about this issue on the ASUS boards.

 

You're saying your version of the dsdt file didn't have the CPU aliases in it?

 

MAJ

Link to comment
Share on other sites

Hello,

 

I followed the Retail DVD install guide, and then did the Apple combo update to 10.5.7. I then followed and selected the default options and everything works, except the onboard ethernet isn't recognized.

 

I tried installing the Pystar Realtek R1000 kext using PCWiz's Universal Installer tool, but still no luck, ethernet is not recognized.

 

What can I do to debug/troubleshoot, or where should I look? Anyone have any ideas?

 

Thanks!

 

-R.

Link to comment
Share on other sites

Reinstall the IONetworkingFamily.kext located in the kext folder of MAJ's Installer Pack - use Kext Helper b7.. this has helped.

 

Hello,

 

I followed the Retail DVD install guide, and then did the Apple combo update to 10.5.7. I then followed and selected the default options and everything works, except the onboard ethernet isn't recognized.

 

I tried installing the Pystar Realtek R1000 kext using PCWiz's Universal Installer tool, but still no luck, ethernet is not recognized.

 

What can I do to debug/troubleshoot, or where should I look? Anyone have any ideas?

 

Thanks!

 

-R.

Link to comment
Share on other sites

 Share

×
×
  • Create New...