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

I believe the 9.6.3 shutdown issue is somewhat related to AppleHDA since after 'CPU Halted' a long list of 'Sound Assertion' errors/commands are listed and then the system simply hangs.

 

However when I disabled the onboard audio in the BIOS the system simply hangs after 'CPU Halted'

 

I'm going back to Voodoo for now.

Link to comment
Share on other sites

HUGE thanks to Digital_Dreamer and Wolfienuke... you guys are amazing.

 

Got 10.5.6 up and running... here are my stats:

EX58-UD5

Intel Core i7 920 2.66 gHz

6 GB DDR3 triple-channel

Nvidia GeForce 9800 GT 512

Machine is running fast and looks beautiful... only two problems:

 

1) Audio not working. I've added the ALCinject.kext and the legacy HDA kext and tried everything else I can think of, but still no audio device recognized at all. Is there something I'm missing?

 

2) I finally got Disk Utility to recognize my hard drive for being larger than 128 GB by changing the IDE mode from legacy to native and changing the disk mode from IDE to AHCI in the bios. However, I cannot resize the 128 GB partition or even create a new one. Disk Utility gives me an error... something about "mediakit says partition map too small". If I try to add a new partition, it says "Filesystem does not allow partition size" or something like that. I'm pretty sure others have encountered the same problem. Any fixes for this?

 

Thanks!

Which install did you use? EFI boot or plain boot-132?

Did nothing show up in the Inputs or Outputs in the System Preferences/Sound?

 

As for the drive issue, I know someone else had the same issue and the only solution is to erase or repartition it.

 

I've got the Digital_Dreamer 9.6.3 install working pretty well now.

 

Main issues revolve around sleep (p1 Pos)

with a fresh install the system will put itself to sleep after 15 minutes by default

i can actually sleep my machine and it powers down the hard drives and monitor (nothing else)

and i can resume it without there "appearing" to be anything wrong.

However, it kills the audio and breaks shutdown.

 

If i dont let it sleep then audio works and so does shutdown.

 

Maybe some of you are walking away from your computer for 15 minutes and it tried to sleep and broke stuff but you didnt notice or put it together. Or maybe this is an isolated thing i'm experiencing.

 

btw running f6

Yeah, sleep ruins a lot of things. You're not alone. Even if you manage to wake, your system is unstable. I can get KP doing any disk related stuff. My eSATA drive is unrecognized and drops off with a 'disk removal warning.'

 

I am using DD's wonderful script, but I don't see any kexts in the Extra Folder. What am I doing wrong? Thanks.

Like others, I haven't had much success using the Extra folder, so the patches are all thrown in S/L/E like usual.

 

Why does the patch flash this?

 

2009-04-25 09:06:31.363 diskutil[99615:10b] _CFGetHostUUIDString: unable to determine UUID for host. Error: 35

I get that error every time I run the Terminal on a kernel-updated system. When using 9.6.3 or 9.7.0 kernel, those errors are all over the place.

 

Joeblough-thanks for the reply, then why is there an Extra Folder created using DD's script and the Chameleon Bootloader?

 

Has anyone gotten Chameleon to point to EFI Boot partition?

 

Anyone experiencing random shutdowns? My computer just restarts after about 20 minutes-no OC and temps are fine.

I'd look at your system log (Console) for any clues first. If it's hardware related (likely), it may not even be in the log - you'll just see a slight gap in time from the last action taken right to the boot process. My first hunch is a RAM or memory related error, but that usually results in a KP.

 

Post a clip of your system.log from when the system was running right up to the reboot messages.

 

<br /><br /><br />

 

i think the /Extra folder is just part of the default chameleon install. i did have chameleon installed on the EFI partition but i never got all the kexts to load right. no random shutdowns but i did have a random lockup last night... sigh.

You'd think that just using the EFI boot kexts in Extra on a fresh vanilla install would be the ticket. Throwing the patched kexts from a boot-132 install appears to create unresolved dependency issues. I'd guess the Extra could just be used for kexts that have no dependency issues, like dsmos, disabler, Natit, or simply those that did not originate from the OS install.

 

I believe the 9.6.3 shutdown issue is somewhat related to AppleHDA since after 'CPU Halted' a long list of 'Sound Assertion' errors/commands are listed and then the system simply hangs.

 

However when I disabled the onboard audio in the BIOS the system simply hangs after 'CPU Halted'

 

I'm going back to Voodoo for now.

Let us know if there are still sleep issues after going back to Voodoo kernel. If the problems persist, I'll see about hacking in an option to install the PC-EFI v9 bootloader.

 

regards,

MAJ

Link to comment
Share on other sites

well i guess you could run his script over the iPC installation but that's probably not such a good idea. who knows what non-vanilla kexts iPC has put in /System/Library/Extensions and how they interact with digital_dreamer's? you mentioned you only have one disk, so you have to do it on another machine, i mean, you cant boot from the same disk you're going to erase and reinstall retail osx onto :)

 

Yea, not sure what I was thinking there :) In any event, I have NO idea what I did, but I got it working with all cores. Now the only issue I have is the fast clock. From reading through this thread it doesn't seem like anyone has fully identified what's causing that yet.

 

 

d_d's script will put the dsdt.aml file whereever it needs to be for the boot loader to find it. i think for the latest chameleon, that's in /Extras (or is it /Extra, now i cant remember). or it might be in / (the root folder, which is what you see when you just double click your hard disk). of course if you do the install on another machine, the root folder will be /Volumes/disk_for_ud4p/ and Extras will be in /Volumes/disk_for_ud4p/Extras. you just need to look for the file called dsdt.aml in either of those places after d_d's script has finished and drag it to the trash.

 

but i just use the terminal for all of this stuff... 'sudo rm /Volumes/disk_for_ud4p/dsdt.aml' and then enter your password...

 

Cool, I will keep this in mind when I switch back over to retail.

 

 

Btw, sleep works perfect in vanilla and voodoo using the F8a BIOS on the UD4P. I can come back 3 hours later with either and resume no problem.

Link to comment
Share on other sites

Btw, sleep works perfect in vanilla and voodoo using the F8a BIOS on the UD4P. I can come back 3 hours later with either and resume no problem.

 

yeah, i'm starting to think all of my resume from sleep problems are hardware/overclock related. i've backed off BCLK to 150MHz with a cpu multiplier of 20x and a memory multiplier of 8x. (from BCLK=166Mhz, 20x and 8x) this underclocks the memory a bit... but so far it has not locked up coming out of sleep or had a random hang.

Link to comment
Share on other sites

yeah, i'm starting to think all of my resume from sleep problems are hardware/overclock related. i've backed off BCLK to 150MHz with a cpu multiplier of 20x and a memory multiplier of 8x. (from BCLK=166Mhz, 20x and 8x) this underclocks the memory a bit... but so far it has not locked up coming out of sleep or had a random hang.

 

Yea, definitely update to F8a. I had no sleep issues when using the stock speeds, only once I overclocked (3.6ghz). After updating to F8a, it didn't matter what I had the CPU clocked at, it always worked.

 

Here is where I got the F8a BIOS from:

 

http://www.overclock.net/intel-motherboard...os-updates.html

Link to comment
Share on other sites

and now i just hosed up one of the versions so badly that it won't boot. yikes. this looks like it is going to be a lot of work to get right. i think this is work that wolfienuke has already done for us, but for whatever reason my machine is all funny when running his kexts.

 

so for laffs i built an Extensions.mkext out of wolfienuke's kexts (plus dsmos and disabler) and put it in /Extras. somewhat to my surprise, it almost all works. i had problems with the ethernet for a while - i think the RealtekR1000.kext won't load from /Extras due to dependency problems, and even after i moved it to /S/L/E, it still didnt work. but a full power-down of the board fixed that, so i guess the UD4P has the same ethernet port lockup problem as the UD5? anyway that left audio.

 

at first, audio was not working for me. true to form i keep trying things and not keeping track of what i was doing; bad science. anyway i found some package called HDA_885_889A_BETA_V5.zip somewhere out there. i put those in my mkext and still no joy. but i think what happened was at some point along the line i took the AppleHDA.kext from d_d's kexts and put it in /S/L/E, and this was incompatible with the 3 kexts that are in that zipfile. i pulled the stock AppleHDA.kext out of the 10.5.6 combo updater, put it in /S/L/E and rebuilt the extensions cache, rebooted and the audio is back! but i have the 0 != result assertion every 5 seconds problem. it does seem to work properly, however. i dont have any front panel audio hooked up yet, but the back panel audio works.

 

so i'm going to put back wolfienuke's LegacyHDAController/PlatformDriver and HDAEnabler and see what happens. if that doesnt work, there should be something in this thread:

 

http://www.insanelymac.com/forum/index.php?showtopic=140941

 

that will work for this board. for all i know that's the source of wolfienuke's kexts anyway.

 

almost done. though i've *still* had a couple of lockups (once while just logging out). i might have to back my overclocks all the way out to understand if that's the cause.

 

Yea, definitely update to F8a. I had no sleep issues when using the stock speeds, only once I overclocked (3.6ghz). After updating to F8a, it didn't matter what I had the CPU clocked at, it always worked.

 

Here is where I got the F8a BIOS from:

 

http://www.overclock.net/intel-motherboard...os-updates.html

 

thanks, yeah i am running f8a since last night. i found it there with some furious googling. before i suspected my memory timing as the culprit (and it was definitely wrong), but now i'm running at 1200MHz on 1333MHz memories so it really should be stable. still have had 2 hangs, but no lockup on resume from sleep.

Link to comment
Share on other sites

Here is my error log before it shut down. It had been on all day w/o me doing much-I left the house for 5 hours. Geekbench messed up when I tried to close it. Then about 10 minutes or less BOOM-shutdown.

 

this looks to me like a hardware problem. have you run memtest86+ on this system to make sure your memory is good? a bus error like that can be caused by memory corruption. is it stable when running XP or Vista? i cant remember if you said you are overclocking or not.

 

the UUID messages are a mystery. i don't have these. can you try setting a static IP address for this machine and rebooting?

Link to comment
Share on other sites

Well, here's the pseudo-boot-132 from EFI setup :D :

It's not a standard boot-132 setup with the kexts in S/L/E and it's not a boot from EFI setup. All the "Boot from EFI" kexts are in Chameleon's Extra folder with a virgin Extensions directory in S/L/E. So, like boot from EFI, we can have a vanilla install and do software updates without any issues. Additionally, just like the boot from EFI approach, you can use fake plists that contain just the modified info needed, while using the always-updated binaries stored in S/L/E.

 

However, I like this setup better, because, unlike the mysterious EFI partition, I get to see all the patches at a glance, which simplifies management. (Well, if you're like me, I like to fiddle with things and tweak.) To see the hidden EFI partition, you have to use the Terminal and 'make EFI directory' and mount it. When you're through with it, you need to unmount it, and 'delete the directory.' (The unmount is mandatory - if it isn't done, you got problems!) It's a little work and annoying. But, if you want a Mac install that "looks" like a Mac install as far as the boot drive files are concerned, then the boot from EFI setup is it. That doesn't mean much to me as visibility and manageability, and Chameleon's Extra folder provides you that.

What's cool is that at first all I had in the Extra/Extensions folder is dsmos.kext, Disabler.kext, and Natit.kext, with a .mkext file of them in Extra. Booted like a charm, but, of course, I didn't have audio, networking, "internal" drive icons, etc.

 

Now, I was going to add a "Boot from EFI" option to my script, but I think I'll scratch that. This would be much, much easier to support. All I would need to do is remove the post patch routine that removes the incompatible kexts and just have the patched kexts transfered to Extra/Extensions, with a .mkext file created from them. (In fact, the script already will create the .mkext file from any kexts in Extra/Extensions.)

 

Oh, as a side note, this setup is on the 9.7.0 kernel and I just discovered a big benefit: No beachballs from blocked I/O!

I put the system to sleep and, after wakening, my eSATA drives go unrecognized, as usual. However, when I double-clicked on the drive icons, instead of the disappearing icons, warning and beachball, I get the drive window without any contents and the spinning progress indicator on the bottom of the window. But, no beachball! I can continue to do anything else in the Finder while it does this (indefinitely, I suppose). This is good news! :)

 

EDIT: Oh, and VMware Fusion 2 works just fine on this setup.

 

Booted with "Boot from EFI" kexts in Chameleon's Extra folder.

Kexts normally deleted from S/L/E are highlighted in Extensions directory (Vanilla OS install).

pseudo-Boot.gif

 

Here is my error log before it shut down. It had been on all day w/o me doing much-I left the house for 5 hours. Geekbench messed up when I tried to close it. Then about 10 minutes or less BOOM-shutdown.

 

It's pretty clear from the log where it rebooted, but it leaves no trace or clue as to why. Therefore, it's hardware issue the OS isn't informed about. Is this system overclocked? Are your RAM settings correct for the specs? Can you run prime95 without a KP?

 

From your description, are you saying you had it on for 5 hours and it didn't have a problem until 10 minutes after you ran Geekbench? So activity triggers it. Or, RAM activity. Hmmmm.

What I would do is see if I can run Windows on it (I know :) ) and see if the problem persists. If so, I'd either change out the RAM or RMA the board.

 

As a side note, those UUID errors are ridiculous! There's something about the combination of kexts, bootloader and kernel that setting that off. Fortunately, the above-mentioned setup appears to get rid of it.

Link to comment
Share on other sites

Hi Everyone. Thanks for all your hard work here. I now have my system running off the EFI partition.

 

My main problem is I can't get netflix streaming to work... Anyone have Netflix?

I get ErrorCode: 8102 151 when trying to start a movie. Form what I've read its DRM related. May have something to do with the UUID.

 

I have looked here with no luck.

http://www.insanelymac.com/forum/index.php?showtopic=134517

They don't seem to have a solid solution so I thought I'd get everyone here's take on this issue.

 

Thanks for you help!

-Mike

Link to comment
Share on other sites

Hi Everyone. Thanks for all your hard work here. I now have my system running off the EFI partition.

 

My main problem is I can't get netflix streaming to work... Anyone have Netflix?

I get ErrorCode: 8102 151 when trying to start a movie. Form what I've read its DRM related. May have something to do with the UUID.

 

I have looked here with no luck.

http://www.insanelymac.com/forum/index.php?showtopic=134517

They don't seem to have a solid solution so I thought I'd get everyone here's take on this issue.

 

Thanks for you help!

-Mike

 

that was my thread :)

 

netflix is working for me on my hybrid wolfie/chameleon /Extra install. most likely this is equivalent to digital_dreamer's setup in the previous post.

 

almost certainly the problem is with your SMBIOS. with the EFI install you have to be very careful to make sure that the stuff in the EFI partition is actually being loaded. my guess is that you still have the apple SMBIOS in /S/L/E being loaded instead of the special one on the EFI partition that picks up everything from smbios.plist.

Link to comment
Share on other sites

Digital_Dreamer

 

I just ran into a small hiccup in your script --

 

if you choose not to install Chameleon Bootloader, then the "Extra" directory is never created, so at the point in the post patch where your script installs the DSDT, the you get an error:

 

Create and Install Patched DSDT

mv: rename /X58_Mobo_Installer/~extra/DSDT_Patcher/dsdt.aml to /Volumes/sMacint0sh HD/Extra/DSDT.aml: Not a directory

 

also, I'm not sure if this happens before or after that error... but because there is no "Extra" directory, the command to copy the com.apple.Boot.plist to the "extra" directory actually renames the file to "Extra" in the root of your drive.

Link to comment
Share on other sites

almost certainly the problem is with your SMBIOS. with the EFI install you have to be very careful to make sure that the stuff in the EFI partition is actually being loaded. my guess is that you still have the apple SMBIOS in /S/L/E being loaded instead of the special one on the EFI partition that picks up everything from smbios.plist.

 

Glad to here it is working with our install files. I tried to just remove the AppleSMBIOS.kext form my vanilla install to make sure the EFI one was loading and that did not make a difference. I have been working on using DD's new install on my recovery drive. I'll have to mess around with that and see if I can get netflix working on that install. You have given me new hope! :)

Thanks

 

Edit: Booted to my recovery install and it works here :) Going to try and get this working like DD's last post with all kext in Extra. Now I have lots of things to distract me from studying for my two Exams on monday :D

Link to comment
Share on other sites

Glad to here it is working with our install files. I tried to just remove the AppleSMBIOS.kext form my vanilla install to make sure the EFI one was loading and that did not make a difference. I have been working on using DD's new install on my recovery drive. I'll have to mess around with that and see if I can get netflix working on that install. You have given me new hope! :)

Thanks

 

its possible that its just not loading at all. i had a heck of a time with the EFI partition install and finally gave up. i know there was a period of time there where the hacked SMBIOS was not loading right, i just can't remember if it was while i was experimenting with the EFI partition install. i think D_Ds new /Extras install is going to be the right one to use.

Link to comment
Share on other sites

Digital_Dreamer

 

I just ran into a small hiccup in your script --

 

if you choose not to install Chameleon Bootloader, then the "Extra" directory is never created, so at the point in the post patch where your script installs the DSDT, the you get an error:

 

Create and Install Patched DSDT

mv: rename /X58_Mobo_Installer/~extra/DSDT_Patcher/dsdt.aml to /Volumes/sMacint0sh HD/Extra/DSDT.aml: Not a directory

 

also, I'm not sure if this happens before or after that error... but because there is no "Extra" directory, the command to copy the com.apple.Boot.plist to the "extra" directory actually renames the file to "Extra" in the root of your drive.

Ouch!

Thanks for the heads-up on that. I'll fix it right away.

Now, if someone doesn't want to use that bootloader, I suppose they would want that DSDT.aml file installed in the root directory. So, I could just check for the presence of the Extra folder before deciding on where that file goes.

 

regards,

MAJ

Link to comment
Share on other sites

Glad to here it is working with our install files. I tried to just remove the AppleSMBIOS.kext form my vanilla install to make sure the EFI one was loading and that did not make a difference. I have been working on using DD's new install on my recovery drive. I'll have to mess around with that and see if I can get netflix working on that install. You have given me new hope! :)

Thanks

 

Edit: Booted to my recovery install and it works here :) Going to try and get this working like DD's last post with all kext in Extra. Now I have lots of things to distract me from studying for my two Exams on monday :D

 

thats good news. note that i think you have to use the kexts from wolfienuke's EFI package to make this work right. and you need to put in Disabler.kext from D_D's package if you are going to use the vanilla kernel. for these /Extra or EFI type systems you need to modify the versions of the kexts that live in /Extra to make sure they get loaded instead of the vanilla files. wolfienuke's kexts already have these version increases. don't forget to move the dsdt.aml to the /Extra directory and also put the com.apple.Boot.plist there. speaking fo which, i'm using EFI strings for graphics and ethernet which i generated with OSX86Tools.app.

Link to comment
Share on other sites

Glad to here it is working with our install files. I tried to just remove the AppleSMBIOS.kext form my vanilla install to make sure the EFI one was loading and that did not make a difference. I have been working on using DD's new install on my recovery drive. I'll have to mess around with that and see if I can get netflix working on that install. You have given me new hope! :)

Thanks

 

Edit: Booted to my recovery install and it works here :) Going to try and get this working like DD's last post with all kext in Extra. Now I have lots of things to distract me from studying for my two Exams on monday :D

My only issue so far was not being able to use the System.kext in Extra. Now, when we get 10.5.7, we won't have to worry about that. But, for the time being, if you want a matched kernel and System.kext, that kext has got to replace the one in S/L/E. One reason for that is because you can't, or shouldn't, up the version number on that kext to get loading priority over S/L/E. The version needs to be the same as the kernel it works with.

 

Now, I could have run into a fluke and made that decision based on my experience. Someone else could try and make it work with the System.kext in Extra. Would be nice, but of limited value.

 

best of wishes,

MAJ

Link to comment
Share on other sites

I know this is the wrong thread for this technically, but I am using the kexts from D_D's script for my UD3R board.

 

I've been trying find a correct patcher that maps the audio correctly in the sound output. The included kexts in D_D's "repository" for the UD3R, I assume just use the stock AppleHDA.kext, with the new HDAEnabler.kext, LegacyHDAController.kext and LegacyHDAPlatformDriver.kext

 

But after I generate an EFI string, it only works on "Internal Speakers" instead on "Line Out"... which i remember from my 889a headaches I had with my P45 board, the internal speakers setting uses a DSP highpass filter to rolloff the lower bass so the real "internal speakers" wouldn't pop out of their little cones.

 

I tried loading the kexts in the other repository for the DS4, which include a modified AppleHDA.kext and HDAEnabler.kext only.. no legacy kexts (they're both the 888 chip?)

 

That one works the same way.. no difference I can tell....

 

So does anyone maybe have a solution for this 888 chip to properly map out "line out" to the real "line out"?

Link to comment
Share on other sites

I was able to solve my shutdown issue when running 9.6.3 by installing the provide openhaltrestart.kext located in the misc patches repository.

BIG QUESTION!

 

Since I see we are working out all the kinks of running this new 9.6.3/9.7.0 vanilla kernel prior to the official release of 10.5.7 would it be logical to say that when 10.5.7 is released we can simply update since we already would be running the latest kernel?

 

and what if one was still running Voodoo 9.6.0?

Link to comment
Share on other sites

I know this is the wrong thread for this technically, but I am using the kexts from D_D's script for my UD3R board.

 

I've been trying find a correct patcher that maps the audio correctly in the sound output. The included kexts in D_D's "repository" for the UD3R, I assume just use the stock AppleHDA.kext, with the new HDAEnabler.kext, LegacyHDAController.kext and LegacyHDAPlatformDriver.kext

 

But after I generate an EFI string, it only works on "Internal Speakers" instead on "Line Out"... which i remember from my 889a headaches I had with my P45 board, the internal speakers setting uses a DSP highpass filter to rolloff the lower bass so the real "internal speakers" wouldn't pop out of their little cones.

 

I tried loading the kexts in the other repository for the DS4, which include a modified AppleHDA.kext and HDAEnabler.kext only.. no legacy kexts (they're both the 888 chip?)

 

That one works the same way.. no difference I can tell....

 

So does anyone maybe have a solution for this 888 chip to properly map out "line out" to the real "line out"?

You want to use "Line Out" because "Internal Speakers" has the bass filtered out?

I seem to remember that someone demonstrated how he went through that long plist in (Legacy)HDAPlatformDriver.kext and removed the DSP filter commands for "internal speakers". Tricky part is in knowing just what to remove and keep.

The remapping is much more difficult. Hmmmm, don't really have anymore info than that.

 

I was able to solve my shutdown issue when running 9.6.3 by installing the provide openhaltrestart.kext located in the misc patches repository.

BIG QUESTION!

 

Since I see we are working out all the kinks of running this new 9.6.3/9.7.0 vanilla kernel prior to the official release of 10.5.7 would it be logical to say that when 10.5.7 is released we can simply update since we already would be running the latest kernel?

 

and what if one was still running Voodoo 9.6.0?

Thanks for that helpful info!

 

As for the updates, pretty much so. No need to mess with the kernel and System.kext anymore. We'll have a vanilla install with vanilla kernel.

 

However, I think that because Apple is always going to be releasing OS updates, various aspects of our system may continue to break. Thus, our work on finding solutions to working sleep, restart, shutdown, TM, Bluetooth, wireless, etc. will continue.

Additionally, because of software updates on our side, like, ummm, bootloaders, such work will continue.

 

regards,

MAJ

Link to comment
Share on other sites

You want to use "Line Out" because "Internal Speakers" has the bass filtered out?

I seem to remember that someone demonstrated how he went through that long plist in (Legacy)HDAPlatformDriver.kext and removed the DSP filter commands for "internal speakers". Tricky part is in knowing just what to remove and keep.

The remapping is much more difficult. Hmmmm, don't really have anymore info than that.

 

Hah.. ok.. you're are correct, thanks for the info... I also didnt realize that the "line out" setting routes through the "rear speakers" 5.1 physical output of the board... so I ran both outputs through different channels on my mixer, and A/B'd them by switching internally from "internal speakers" to "line out" and there was no difference in bass at all! It's a minor thing, but I am going to see if I can at least figure out how to change the jack assignments so it reports correctly.

 

Thanks again.

Link to comment
Share on other sites

 Share

×
×
  • Create New...