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

[digital_dreamer]

I just now managed to get OSX to boot with the 4870 drivers and Motmot kext, thanks to Digital Dreamer's latest script, Crash4419's custom dissection of said script, and one final item which I found hidden in another thread. The last thing (perhaps the only thing I was missing all along) was the apparent necessity of manually deleting /System/Library/Extensions.mkext. So, maybe I just never saw it clearly outlined and I'm blind. ;p

 

Now... the problem is that even though I definitely have the 7_radeon_hd_48x0_drivers.pkg, the latest ATY_Motmot.kext, and the replacement OpenGL.framework all installed, I don't seem to be able to change resolution, and QE/CI are still off. It's like it never happened. What I think is going on is I simply don't have enough familiarity with OSX to know where to look to enable or change these variables. But it's a fact that my System Preferences only gives me the option of 1024x768xMillions, which seems to be what Digital Dreamer's latest script sets as default (the older script used 1280x1024, and I don't even have that as an option, even though it was obviously working in older installs).

 

Anyone know what's going on now?

I don't know what's going on, either, but it looks like the resolution that is set at boot time is the resolution you're stuck with. You can go into your boot.plist and add the Graphics Mode key and set your resolution to whatever your graphics card supports (i.e. 1280x1024x32 or, maybe, 1280x1024x32@85, but refresh rate is not always supported) To find those resolutions on your system, type "?video" at the boot prompt.

 

I took the Graphics Mode key out of the boot.plist in the latest script just in case it was creating issues for someone. Can't imagine someone having a graphics card that didn't support it, but I wasn't taking chances and decided to keep it at a bare minimum.

 

None of what I provided is the solution to your issue, but at least you may get a higher resolution as a default.

 

MAJ

[Asterra]

I don't know what's going on, either, but it looks like the resolution that is set at boot time is the resolution you're stuck with.

Heh. I have to laugh. You know it's just a doomed effort when your stubbornness pays off and you get it working, only it still doesn't work, and there is no way to divine why not.

 

It didn't like 1600x1200x32@75, and since it reboots the pc before even loading Chameleon, that pretty much means I'll have to reinstall again. Without 75+ Hz and QE/CI, there's no point in using OSX. I think it's time to claim a small victory and hang the hat on this project, until the Winter Solstice, or whenever it is that Apple has decided 10.5.7 will be released. ;p Thanks for all the tips.

[mac kid from jersey]

Heh. I have to laugh. You know it's just a doomed effort when your stubbornness pays off and you get it working, only it still doesn't work, and there is no way to divine why not.

 

It didn't like 1600x1200x32@75, and since it reboots the pc before even loading Chameleon, that pretty much means I'll have to reinstall again. Without 75+ Hz and QE/CI, there's no point in using OSX. I think it's time to claim a small victory and hang the hat on this project, until the Winter Solstice, or whenever it is that Apple has decided 10.5.7 will be released. ;p Thanks for all the tips.

 

Dont reinstall. Just boot from your spare HD by hitting F12 at boot time.

[joeblough]

you know, another thing that came to mind is this:

 

what settings in the BIOS menus change the DSDT as seen by the operating system? i have not experimented with this, but because we are patching the dsdt, if there are any bios settings that affect the dsdt, they would be "frozen" at the moment that you run the dsdt patcher. if you then went into the bios and changed something that gets reflected in the DSDT, your system would never see it because it's loading dsdt.aml.

 

i dont have any proof that the DSDT changes when you tweak the bios settings. i need to experiment with this.

[mattrb]

I was trying DD's new script and I find it is the best method and is a better method then EFI Boot Partition, by far.

 

One problem is that I am in en0 for my network adapter. I am trying to use Parallels and it just wont detect my network adapter. What do I do? Oh and I tried to internet share with the sharing prefpane but that didn't do much.

 

[joeblough]

I was trying DD's new script and I find it is the best method and is a better method then EFI Boot Partition, by far.

 

One problem is that I am in en0 for my network adapter. I am trying to use Parallels and it just wont detect my network adapter. What do I do? Oh and I tried to internet share with the sharing prefpane but that didn't do much.

 

 

are you using any EFI strings for your ethernet? at some point i generated EFI strings for my video card and ethernet using OSX86tools and put them in com.apple.Boot.plist. i have not tried parallels, but vmware fusion does work.

 

what do you mean by "i am in en0 for my network adapter"? i think en0 is what you want the built-in ethernet to be named.

[digital_dreamer]

you know, another thing that came to mind is this:

 

what settings in the BIOS menus change the DSDT as seen by the operating system? i have not experimented with this, but because we are patching the dsdt, if there are any bios settings that affect the dsdt, they would be "frozen" at the moment that you run the dsdt patcher. if you then went into the bios and changed something that gets reflected in the DSDT, your system would never see it because it's loading dsdt.aml.

 

i dont have any proof that the DSDT changes when you tweak the bios settings. i need to experiment with this.

You know, that's a pretty good point. Makes a lot of sense. If you had the DSDT patch created when a particular BIOS feature was turned off, would the OS think it'll never be available, even when you enabled it at a later point? Hmmm.

 

I was trying DD's new script and I find it is the best method and is a better method then EFI Boot Partition, by far.

 

One problem is that I am in en0 for my network adapter. I am trying to use Parallels and it just wont detect my network adapter. What do I do? Oh and I tried to internet share with the sharing prefpane but that didn't do much.

 

I agree. I absolutely love this setup much better than my previous two installs (EFI boot and the popular boot-132). I has the advantages of both installs:

• You can see all your patches at a glance - no mysteries there. So much easier to troubleshoot if problems arise.

• Easy and rapid updates - drag 'n drop, if you wish.

• Vanilla install, so no Apple software update worries, with the possible exception of the kernel, if you're using a different version and the update includes a modified release. (One could have their kernel renamed and that change reflected in the boot.plist to avoid an overwrite from software update, however.)

• The kernel is in it's natural and native location (compared to EFI boot), so VMware Fusion doesn't throw a fit.

• Booting time appears much improved, although I can't confirm that.

• Plus, after two weeks of messing with it, I've never had a mysterious failed boot, as happened with EFI boot on several occasions.

 

But, it was really once we got away from the hardwired, finicky "Extensions" folder in Chameleon 2, things improved.

 

RE: Parallels

Did it detect a network on your previous installs?

 

I just launched VMware Fusion 2 and, sure enough, I don't have network access, either!

I had it before and could browse in Safari. Looked at devices and it said driver improperly installed. So, I tried to reinstall the Ethernet driver, but couldn't because it couldn't find the adapter.

 

I'm going to take a better look at the IONetworkingFamily.kext

 

regards,

MAJ

 

EDIT: I ought to follow joeblough steps and put in a EFI string for Ethernet, then.

[mattrb]

are you using any EFI strings for your ethernet? at some point i generated EFI strings for my video card and ethernet using OSX86tools and put them in com.apple.Boot.plist. i have not tried parallels, but vmware fusion does work.

 

what do you mean by "i am in en0 for my network adapter"? i think en0 is what you want the built-in ethernet to be named.

I looked in System Profiler and that is where I found en0.

Did it detect a network on your previous installs?

Never checked because vanilla is so NEW.

I just launched VMware Fusion 2 and, sure enough, I don't have network access, either!

I had it before and could browse in Safari. Looked at devices and it said driver improperly installed. So, I tried to reinstall the Ethernet driver, but couldn't because it couldn't find the adapter.

Thanks for checking because I thought this was an isolated incident.

I'm going to take a better look at the IONetworkingFamily.kext

Thanks, I don't even know where to start in fixing that kext. Maybe if we just add Realtek driver and not the IONetwork kext that could fix it.

EDIT: I ought to follow joeblough steps and put in a EFI string for Ethernet, then.

Please, could you offer us that string and I could use osx86tools to merge it with my 8800gt string. Thanks DD, your the M-A-N.

[neils]

You had your settings correct. It clear your system is not loading anything from your Mac OS install, just the kexts installed by the script. That's it.

 

Try these things and report back with your findings:

1)

If you did install with my new script, remove all kexts from the Stored_Kext folder with the exception of dsmos.kext, Disabler.kext, and System.kext. Run script and "Update boot cache" and reboot with -v -f flags.

These kexts are the minimum required to boot.

 

report back.

 

If that doesn't work:

2)

Did you say you installed using a 10.5.6 DVD? It might sound silly, but how about downloading the 10.5.6 combo updater (big file) and installing that over your OS install? Like you, I'm running out of options. But, given that this install process works for so many people and that the log only shows the patched kexts being loaded and stalling there, I'm inclined to think something being amiss regarding the OS install.

 

3)

If you're in a position to do a erase and reinstall, do so with the Chameleon 1012 bootloader instead of Chameleon 2.

 

regards,

MAJ

 

Hello,

 

Just to be sure, I reformattd the EFI partition. After that, I erased the harddisk I'm installing on, and downloaded the newest script. I already used the official 10.5.6 combo update, so I already had that.

 

I installed the older chameleon, and for the rest the only thing I changed was the kernel. I installed the 9.6.3 kernel and system kext.

 

Again I didn't run the DSDT patcher at all, because I know it doesn't help me, since I'm installing from my older Pentium D hackintosh.

 

I updated the boot caches etc, and took out the disk.

 

On my new i7 system I reset the bios, and set up everything exactly as suggested in the first post of this thread.

 

Chameleon boots up nicely, booted with -v -f. I can see a lot of kexts are being loaded from s/l/e, but when that's done the system reboots.

 

So I took the disk out again, removed all kexts with the exception of dsmos.kext, Disabler.kext, and System.kext, updated cached and crossed my fingers.

 

Unfortunately, same story. Boot loop. Booting in F- -V mode didn't help either.

 

It's weird. Really weird.

[joeblough]

Please, could you offer us that string and I could use osx86tools to merge it with my 8800gt string. Thanks DD, your the M-A-N.

 

just create the ethernet string with osx86tools. its one of the options in the efi strings screen.

[digital_dreamer]

Hello,

 

Just to be sure, I reformattd the EFI partition. After that, I erased the harddisk I'm installing on, and downloaded the newest script. I already used the official 10.5.6 combo update, so I already had that.

 

I installed the older chameleon, and for the rest the only thing I changed was the kernel. I installed the 9.6.3 kernel and system kext.

 

Again I didn't run the DSDT patcher at all, because I know it doesn't help me, since I'm installing from my older Pentium D hackintosh.

 

I updated the boot caches etc, and took out the disk.

 

On my new i7 system I reset the bios, and set up everything exactly as suggested in the first post of this thread.

 

Chameleon boots up nicely, booted with -v -f. I can see a lot of kexts are being loaded from s/l/e, but when that's done the system reboots.

 

So I took the disk out again, removed all kexts with the exception of dsmos.kext, Disabler.kext, and System.kext, updated cached and crossed my fingers.

 

Unfortunately, same story. Boot loop. Booting in F- -V mode didn't help either.

 

It's weird. Really weird.

You're right, neils, it is weird.

 

Well, in that screenshot we can see it loading kexts from both side - that's good.

dsmos.kext loaded

And, various kexts from S/L/E are loading.

However, I see that the wrong LAN driver is loading. If the RealtekR1000.kext LAN driver for your board doesn't load, Apple's version in S/L/E called RTL8169 tries to load and fails, which is to be expected. So, why isn't the RealtekR1000.kext from the IONetworkingFamily.kext loading? Not that it really matters in the whole scheme of things, but little things like this indicate something's wrong.

 

1. Have you used this OS Install disk on any other systems? If you were to attempt to install on an authentic Mac, does it verify all the way through before the install?

2. What kind of system are you using to install the OS on the drive? What version of the OS?

 

Can you see if there are any system.logs in this directory?

cd /volumes/YOUR_BOOT_DRIVE/private/var/log

ls

 

or

open system.log (in that directory)

 

Keep the faith, man.

 

regards,

MAJ

[neils]

Well, I bought my retail copy of OSX second hand. Tomorrow I'm gonna buy a new retail version, just to be sure I don't have a machine specific version.

 

The reason the realtek isn't loading is because I took that screenshot after I removed all kexts except the dsmos.kext, Disabler.kext, and System.kext.

 

I'm also gonna contact Corsair, to verify if my memory settings are indeed correct. I've heard about people who couldn't boot because of memory problems. But first I'm gonna buy a new retail version to be really sure I have indeed the one I need.

 

Thanks again DD. I know it's gonna work in the end, I have faith.

 

 

And I don't have a log. I don't even have a private directory at all on my install disk. Is that normal ?

[joeblough]

Well, I bought my retail copy of OSX second hand. Tomorrow I'm gonna buy a new retail version, just to be sure I don't have a machine specific version.

 

what does the OSX disk look like? if it is black with a big X over a purple galaxy, then it should be a retail copy. the machine specific discs are usually light grey in color, and i dont think they have a big X on them.

[digital_dreamer]

Well, I bought my retail copy of OSX second hand. Tomorrow I'm gonna buy a new retail version, just to be sure I don't have a machine specific version.

 

The reason the realtek isn't loading is because I took that screenshot after I removed all kexts except the dsmos.kext, Disabler.kext, and System.kext.

 

I'm also gonna contact Corsair, to verify if my memory settings are indeed correct. I've heard about people who couldn't boot because of memory problems. But first I'm gonna buy a new retail version to be really sure I have indeed the one I need.

 

Thanks again DD. I know it's gonna work in the end, I have faith.

And I don't have a log. I don't even have a private directory at all on my install disk. Is that normal ?

Ah, regarding the LAN driver.

Okay. I didn't know which boot that screenshot was for.

 

The private directory is typically invisible. But, can you see it in the Terminal?

 

The symptoms you have are very much like what would happen from a machine specific version.

 

regards,

MAJ

[mattrb]

just create the ethernet string with osx86tools. its one of the options in the efi strings screen.

 

I used to use some proggie called efistudio and that failed to get ethernet string but that went nowhere. I attempted to use OSx86tools and got the ethernet plist(without the outer xml tags):

<dict>
 <key>PciRoot(0x1)/Pci(0x1c,0x4)/Pci(0x0,0x0)</key>
 <dict>
	 <key>built-in</key>
	 <string>0x01</string>
 </dict>

 

I merged the plist with my graphics plist for my 8800gt and it did not work. I attempted to add en1 & en2 ethernet from the networking prefpane but that did not work in getting internet. Here is my system profiler with the en1 and en2 that I added. Parallels additions are obviously shown.

 

Has anyone successfully got the ethernet efi strings to work and if they have, is the plist different from mine. Tips on getting success?

 

[MasterLen]

Hi,

 

fist I want to thank DD and all the others for your help...

 

 

I have an issue with sleep....

 

Manual sleep is working great but for me it is not possible to go

on automatic sleep!?

 

AM I the only one who has this issue?

 

Does anyone has a solution for this?

[mac kid from jersey]

Guys, i was having so many problems with my install last night after using the new script.

 

The problem was that I still had an EFI partition. Make sure you delete it guys.

[joeblough]

I used to use some proggie called efistudio and that failed to get ethernet string but that went nowhere. I attempted to use OSx86tools and got the ethernet plist(without the outer xml tags):

<dict>
  <key>PciRoot(0x1)/Pci(0x1c,0x4)/Pci(0x0,0x0)</key>
  <dict>
	  <key>built-in</key>
	  <string>0x01</string>
  </dict>

 

I merged the plist with my graphics plist for my 8800gt and it did not work. I attempted to add en1 & en2 ethernet from the networking prefpane but that did not work in getting internet. Here is my system profiler with the en1 and en2 that I added. Parallels additions are obviously shown.

 

Has anyone successfully got the ethernet efi strings to work and if they have, is the plist different from mine. Tips on getting success?

 

 

that's the same plist that osx86 tools computed for me. however i'm running a UD4P and it only has one ethernet interface. are you on a UD5? what happens if you switch to the other ethernet interface? does it even work under OSX?

[mac kid from jersey]

that's the same plist that osx86 tools computed for me. however i'm running a UD4P and it only has one ethernet interface. are you on a UD5? what happens if you switch to the other ethernet interface? does it even work under OSX?

 

Are you guys actually using the EFI strings for Ethernet as well? Mine seems to work well enough without it. The only problem is that if i actually switch the ports it gives the IP to the same interface .. still works though.

 

Can anyone else confirm that Ethernet behavior for a non EFI Ethernet setup?

 

What about the audio? When I try to detect the audio strings in OSX tools I get an error.

 

Is anyone else using the f7 bios version with the UD5? For some reason it detects my QPI speed as 6.4 instead of 4.8. When I try to set it at 4.8 chameleon doesn't load. It does the same when I try change the memory speed from 1066 to 1333 as well. I tried to see if maybe my geekbench scores were better with the QPI speed @ 6.4 but it seems the same (9.5 k).

[joeblough]

Are you guys actually using the EFI strings for Ethernet as well? Mine seems to work well enough without it. The only problem is that if i actually switch the ports it gives the IP to the same interface .. still works though.

 

Can anyone else confirm that Ethernet behavior for a non EFI Ethernet setup?

 

What about the audio? When I try to detect the audio strings in OSX tools I get an error.

 

Is anyone else using the f7 bios version with the UD5? For some reason it detects my QPI speed as 6.4 instead of 4.8. When I try to set it at 4.8 chameleon doesn't load. It does the same when I try change the memory speed from 1066 to 1333 as well. I tried to see if maybe my geekbench scores were better with the QPI speed @ 6.4 but it seems the same (9.5 k).

 

its a little bit 'cargo cult science' for me - i had to use the ethernet EFI string on my badaxe2 to make time machine work right (and get the internal interface to be named en0), so i just did the same thing for the UD4P assuming it was a good practice.

 

same problem with audio. i'll bet there is a DSDT hack that you could do that would make the audio work with an EFI string. buildsmart did a lot of work on this for the badaxe2 but he didnt reveal much about how he did it.

[mac kid from jersey]

its a little bit 'cargo cult science' for me - i had to use the ethernet EFI string on my badaxe2 to make time machine work right (and get the internal interface to be named en0), so i just did the same thing for the UD4P assuming it was a good practice.

 

same problem with audio. i'll bet there is a DSDT hack that you could do that would make the audio work with an EFI string. buildsmart did a lot of work on this for the badaxe2 but he didnt reveal much about how he did it.

 

Well, it's not that i dont have audio working, I just use the kexts D_D has included with his scripts. I think i would prefer any solution that was more vanilla.

[mangopeach]

neils,

 

you know a BIG variable in your whole thing is trying to do this from another machine... Is there some way you can get a maintenance drive working on the i7? I had good luck with iPC 10.5.6 on mine. Ironically the iPC drive scores 13,300 geekbench vs. 13,100 for the DD vanilla one... Anyway - the simpler and more by the book you can make things, the less likely to run into exotic inexplicable roadblocks, you dig? PM me for an idea on how to get leopard up to snuff...

[fallbrooks13]

ahhhh, Too bad i just left the office or else i would have been testing this.

 

I'm gonna revert bios back to default and then do the changes I have logged in my notebook from initial boot up.

 

Aalways up this late, I need more than 24hrs a day.

 

Should I get off the voodoo 9.6.0 kernel? is the vanilla 9.7.0 or 9.6.3 more stable?

 

Thanks Digital_Dreamer, you the man!

 

UPDATE.

 

restored bios

and now on the 9.7.0 vanilla kernel

 

Things are Running good over here. Machine has been running for over 3 days now and is a work horse. FCP has not crashed or lagged once. Qmaster tasks are running 24/7 too.

 

We're doing post on a multi-screen feature film that on average has over 6 layers of 1280x1080 DVCPOHD video on screen

 

this project LAGGED on our 8-core 2.8ghz.

 

Not on this system though. 85min project file that has 80 video tracks launches in 56sec and and i can instantly scrub through the whole movie.

 

its wonderful. Thanks again everyone!

 

Heres a screen shot of my current system.

[mattrb]

that's the same plist that osx86 tools computed for me. however i'm running a UD4P and it only has one ethernet interface. are you on a UD5? what happens if you switch to the other ethernet interface? does it even work under OSX?

 

UD5 for me, I switched to other ethernet interface w/o restart. Is that necessary to restart?

 

its a little bit 'cargo cult science' for me - i had to use the ethernet EFI string on my badaxe2 to make time machine work right (and get the internal interface to be named en0), so i just did the same thing for the UD4P assuming it was a good practice.

 

same problem with audio. i'll bet there is a DSDT hack that you could do that would make the audio work with an EFI string. buildsmart did a lot of work on this for the badaxe2 but he didnt reveal much about how he did it.

 

Question, Do you know that Ethernet EFI string that involves that "cargo cult science"? I used to have a bad axe2 but I ebayed it to get my i7 setup. I attempted koala's dsdt patcher for windoze to get the sound, ethernet, video working. That was a failure. I think it is because koala's patcher does not work with chameleon 2, atleast that is what I hear is the case.

 

 

Also sometimes my sound cuts in and out. Do you guys know why that happens? Does anyone else have this problem. It happens for me in wolfienukes setup as well as DD's. Tried VoodooHDA as well, and still does the sound issues but voodooHDA works though.

[neils]

neils,

 

you know a BIG variable in your whole thing is trying to do this from another machine... Is there some way you can get a maintenance drive working on the i7? I had good luck with iPC 10.5.6 on mine. Ironically the iPC drive scores 13,300 geekbench vs. 13,100 for the DD vanilla one... :censored2: Anyway - the simpler and more by the book you can make things, the less likely to run into exotic inexplicable roadblocks, you dig? PM me for an idea on how to get leopard up to snuff...

 

Thanks for your help Mango. I already downloaded iPC 10.5.6. It's an ISO though, I downloaded it on my laptop running vista. I do however have an external harddisk. What should I do to boot from the iPC iso on this external disk ? I don't have a dual layer DVD writer in my laptop. The only dual layer writer I have is the one in my new i7 system. It should be possible to boot from this external disk I assume.

 

Could you tell what I should install to at least get to the desktop ? I know I have to use the bootflags cpus=1 busratio=20. Should I install the voodoo kernel ? Should I install any kexts ? I'm only going to use this iPC install to install my retail DVD, so all I really need is a booting iPC version.

 

Many thanks in advance. I decided not to pm you, because other people might face simular problems. It could well be it's gonna work this way. I hope so.

 

Regards, Neils