[GUIDE] Scripted Yosemite/Mavericks Install on Gigabyte Mobos

[AutumnJazz]

I notice you have a GeForce 9800 GTX+ 512MB. This particular card has been troublesome in getting QE/CI in SL, unfortunately.

However, are you using a EFI string or some injector for the nVidia card?

 

As for ethernet, sounds like you need to reinstall the kext in /System. I don't know why it wouldn't be working, as it shouldn't get overwritten by any updates, unless you were using a IONetworkingFamily.kext that had the Realtek kext inside the Plugins folder.

I have the RealtekR1000SL.kext installed in /System.

 

 

SCRIPT UPDATE:

(front page is not updated)

I have a updated HackInstaller shell script for use.

It incorporates a new DSDT fix selector: Just use the up and down arrow keys to navigate the list and enable/disable the fixes using the right and left keys.

Plus, it incorporates some handy troubleshooting routines (really needed with all the variables in DSDT codes) where failed fixes are simply aborted and the script continues with the next fix. Additionally, on failed fixes, the script will dump the results in a folder for the user to email to me to analyze.

Those who've had DSDT issues with the recent script are encouraged to try this new version and report back.

 

Plus, the issue with "too many partitions/drives" is partially resolved, as the user is given the choice to continue.

 

Just replace the current shell script in ~extra/Resources with this version.

 

MAJ

Thank you! I'll give it a try when I get home.

 

Edit: I used osx86 tools to get my graphics card working with an EFI string. Should I delete that before I use the DSDT patcher, or is it ok to leave in there?

[CruiSAr]

Thank you! I'll give it a try when I get home.

 

Edit: I used osx86 tools to get my graphics card working with an EFI string. Should I delete that before I use the DSDT patcher, or is it ok to leave in there?

It is ok to leave it there, EFI strings have nothing to do with the DSDT patcher

[pik0n]

Will this work with core i7 4.3 or 3.6GHz?

 

Thanks!

[AutumnJazz]

It failed on the sleep fix. I haven't tried rebooting yet, I suppose I will, though.

 

And to change from PC-EFI to Chameleon, should I run the regular Chameleon installer or should I use the "Install bootloader (pre-patch)" option in the script?

 

http://tinypaste.com/8a2fe

[digital_dreamer]

Will this work with core i7 4.3 or 3.6GHz?

 

Thanks!

Overclocking will have no bearing on this setup. Feel free to OC to infinity and beyond...

 

It failed on the sleep fix. I haven't tried rebooting yet, I suppose I will, though.

 

And to change from PC-EFI to Chameleon, should I run the regular Chameleon installer or should I use the "Install bootloader (pre-patch)" option in the script?

RE: sleep fix. Nothing to worry about. It'll skip a fix that doesn't fit in properly. Besides, it's just a warning, not a "error" that would prevent booting.

If you get an error result, that could prevent booting. Warnings can be ignored. In fact, the sleep fix is designed to remove that last warning that keeps showing up in the DSDT error log: Reserved method must return a value (_WAK)

However, in order for me to determine what the issue is, would you be able to email the Sleep dump folder in /~extra/DSDT_Patcher/Debug?

 

If you want to use the script, using the included bootloader install option is the best way to go, as it sets up the install like the script expects it. The standalone installers won't install the boot.plist or smbios.plist or set up the folders. You're given more flexibility and options with the script.

 

best regards,

MAJ

[AutumnJazz]

Overclocking will have no bearing on this setup. Feel free to OC to infinity and beyond...

 

 

RE: sleep fix. Nothing to worry about. It'll skip a fix that doesn't fit in properly. Besides, it's just a warning, not a "error" that would prevent booting.

If you get an error result, that could prevent booting. Warnings can be ignored. In fact, the sleep fix is designed to remove that last warning that keeps showing up in the DSDT error log: Reserved method must return a value (_WAK)

However, in order for me to determine what the issue is, would you be able to email the Sleep dump folder in /~extra/DSDT_Patcher/Debug?

 

If you want to use the script, using the included bootloader install option is the best way to go, as it sets up the install like the script expects it. The standalone installers won't install the boot.plist or smbios.plist or set up the folders. You're given more flexibility and options with the script.

 

best regards,

MAJ

I tried to send you a PM, but I kernel panicked before I could upload the file.

 

DSDT debug folder: http://www.megaupload.com/?d=VBI4XO3K

 

Also, I was wondering if you could point me in a direction so that I could get my sound working? I tried VoodooHDA, but that caused the aforementioned kernel panic. My board uses the ALC889 (not A)...

 

Thanks again for all of your help, though. Very few people go so out of their way to assist and make tools for others, with no monetary benefit for themselves.

[Denis Davydov]

after update to 10.6.4 today morning (I use CruiSAir's dsdt file),

I have couple of shut-downs. Not sure if it's connected with the update, but

it never happened before, never.

 

How do you find log files and see what's the reason (kernel panic?) and how to fix it?

 

Thank you.

 

Denis.

[macaddict1234]

without using a mac to do it, on windows 7 how do i create a bootable USB flash drive to put the preboot iso onto?

 

I've already wasted several cds trying to get a working preboot to get my snow leopard to install...

 

Do i just drag the contents of an ISO to a FAT32 pen drive and boot from it?

[digital_dreamer]

after update to 10.6.4 today morning (I use CruiSAir's dsdt file),

I have couple of shut-downs. Not sure if it's connected with the update, but

it never happened before, never.

 

How do you find log files and see what's the reason (kernel panic?) and how to fix it?

 

Thank you.

 

Denis.

Try the Console, looking at the kernel.log at /private/var/log. This is the log that gets created at boot, the same one you see when using -v.

You won't find KPs on shutdown there, though.

Were your shutdowns immediate, or following a KP? If immediate and you see no signs in the System.log, you may have a hardware issue, as the system wouldn't be able to update a log in that scenario.

 

without using a mac to do it, on windows 7 how do i create a bootable USB flash drive to put the preboot iso onto?

 

I've already wasted several cds trying to get a working preboot to get my snow leopard to install...

 

Do i just drag the contents of an ISO to a FAT32 pen drive and boot from it?

You've already tried to burn CDs? What were the symptoms? Did it attempt to read, but with EBIOS read errors? Did you get the following?

boot 0: GPT

boot 0: testing

boot 0: testing

boot 0: error

What WIN utility are you using?

 

The ISO is designed as a El Torito-style bootable ISO9660 filesystem, which is specific to optical media. I may play around with this and try the "-hard-disk-boot" argument and see if it'll create a bootable MBR hard drive.

 

MAJ

[Vasto]

without using a mac to do it, on windows 7 how do i create a bootable USB flash drive to put the preboot iso onto?

 

I've already wasted several cds trying to get a working preboot to get my snow leopard to install...

 

Do i just drag the contents of an ISO to a FAT32 pen drive and boot from it?

You need to burn the image file. Simply dragging the contents won't work.

[Denis Davydov]

Try the Console, looking at the kernel.log at /private/var/log. This is the log that gets created at boot, the same one you see when using -v.

You won't find KPs on shutdown there, though.

Were your shutdowns immediate, or following a KP? If immediate and you see no signs in the System.log, you may have a hardware issue, as the system wouldn't be able to update a log in that scenario.

 

That's what I see in system.log:

 

Jul 12 09:31:02 net17 PubSubAgent[1311]: _CFGetHostUUIDString: unable to determine UUID for host. Error: 35
Jul 12 09:31:09 net17 GrowlHelperApp[1258]: *** attempt to pop an unknown autorelease pool (0x101f600)
Jul 12 09:31:39 net17 GrowlHelperApp[1258]: *** attempt to pop an unknown autorelease pool (0x80a200)
Jul 12 09:32:39 net17 GrowlHelperApp[1258]: *** attempt to pop an unknown autorelease pool (0x810600)
Jul 12 09:33:15 net17 GrowlHelperApp[1258]: *** __NSAutoreleaseNoPool(): Object 0x2e1d420 of class NSEvent autoreleased with no pool in place - just leaking
Jul 12 09:33:15 net17 GrowlHelperApp[1258]: *** attempt to pop an unknown autorelease pool (0x809200)
Jul 12 09:37:09 net17 GrowlHelperApp[1258]: *** attempt to pop an unknown autorelease pool (0x80e600)
Jul 12 09:44:09 net17 GrowlHelperApp[1258]: *** attempt to pop an unknown autorelease pool (0x80e600)
Jul 12 10:01:17 localhost com.apple.launchd[1]: *** launchd[1] has started up. ***
Jul 12 10:01:17 localhost com.apple.launchd[1]: *** Verbose boot, will log to /dev/console. ***

 

and here's kernel.log:

 

Jul 12 09:01:13 Dens-Mac-Pro kernel[0]: BootCache: hit rate below threshold (11244 hits on 22489 lookups)
Jul 12 09:07:35 Dens-Mac-Pro kernel[0]: PPPoE domain init
Jul 12 10:01:21 localhost kernel[0]: npvhash=4095
Jul 12 10:01:21 localhost kernel[0]: PAE enabled
Jul 12 10:01:21 localhost kernel[0]: 64 bit mode enabled

 

The restart was at 10 I guess (today it was a restart, not a shutdown though).

 

So it seems to me I have no signs of a software problem.

 

Yet, I'm still sure it's connected with an update. Maybe some problems with cooler on CPU/GPU at 10.6.4? Anybody have such problems?

[digital_dreamer]

That's what I see in system.log:

 

Jul 12 09:31:02 net17 PubSubAgent[1311]: _CFGetHostUUIDString: unable to determine UUID for host. Error: 35

<SNIP>

Jul 12 09:44:09 net17 GrowlHelperApp[1258]: *** attempt to pop an unknown autorelease pool (0x80e600)

Jul 12 10:01:17 localhost com.apple.launchd[1]: *** launchd[1] has started up. ***

 

and here's [b]kernel.log[/b]:

 

[code]Jul 12 09:01:13 Dens-Mac-Pro kernel[0]: BootCache: hit rate below threshold (11244 hits on 22489 lookups)

<snip>

Jul 12 09:07:35 Dens-Mac-Pro kernel[0]: PPPoE domain init

Jul 12 10:01:21 localhost kernel[0]: npvhash=4095

 

The restart was at 10 I guess (today it was a restart, not a shutdown though).

 

So it seems to me I have no signs of a software problem.

 

Yet, I'm still sure it's connected with an update. Maybe some problems with cooler on CPU/GPU at 10.6.4? Anybody have such problems?

Looks to be hardware.

I'm assuming those two snippings you posted are where the system shutdown/restarted.

The absence of a KP and seeing those gaps in time with no correlating evidence that would produce a shutdown/restart appears to point to hardware. The GrowlHelperApp wouldn't cause this and neither would your ethernet settings (PPPoE). However, just to be sure, look for the same log pattern on a successive shutdown/restart.

I'd check your RAM first, by pulling out a bank at a time and booting.

 

 

The UUID error indicates you don't have a platform UUID set up. If you aren't using a UUID injector/kext, then you should use the newer bootloaders that automatically inject the UUID based on a SystemID. You insert a SystemID (actually a UUID) in the boot.plist and it'll create a platform UUID for you (different from the SystemID UUID). I have not gone this route, yet, so exact details are a little sketchy. This is not a serious issue. It just creates annoying log messages and some software will not function properly without a valid UUID.

 

The low boot cache hit rate may indicate that you have booted with some kexts that are not designated for this particular install. You should only have one kext included in the /Extra boot cache (fakesmc.kext). If you have another Mac install and you are booting into the bootloader on that install, but selecting a different system to boot from, the bootloader will still use the kexts (boot cache) from the other install (not the one selected). This would create a kext mismatch scenario where the kexts expected are not found or the right types/versions. This could lead to system instability, but we'd need more details first.

Again, this may be completely normal, depending on certain setups, and may mean nothing at all in your case.

 

MAJ

[macaddict1234]

You've already tried to burn CDs? What were the symptoms? Did it attempt to read, but with EBIOS read errors? Did you get the following?

boot 0: GPT

boot 0: testing

boot 0: testing

boot 0: error

What WIN utility are you using?

 

The ISO is designed as a El Torito-style bootable ISO9660 filesystem, which is specific to optical media. I may play around with this and try the "-hard-disk-boot" argument and see if it'll create a bootable MBR hard drive.

 

MAJ

 

 

Hi yeah i've tried burning some bootloaders to CD using Verdant's guide, i used a utility called "Infra Recorder" and successfuly burnt one image to disk which was successful up to the screen where it prompts you to press F5 to rescan and swap disks to retail snow leopard disk but when i press return to boot from my Retail 10.6 disk it produces a grey screen with lines (this was using ATI 4570 mobility external VGA to a monitor at 1920x1080). Tried again using a lower resolution with just the laptop screen itself 1366x768 i think this just produces a grey screen no lines, i've left it for 10-15 minutes so it definately wasn't still loading from the disk.

 

p.s. this was after the screen with the chameleon and the whirling circle thing.

 

 

You need to burn the image file. Simply dragging the contents won't work.

 

My original question was how i can make a bootable pen drive not cd (as i've wasted a few disks trying to get a working one, had the problems listed above), i have a kingston 16gb i'd like to try it on, so how exactly do you burn an image file to a pen drive?

[Denis Davydov]

Looks to be hardware.

I'm assuming those two snippings you posted are where the system shutdown/restarted.

The absence of a KP and seeing those gaps in time with no correlating evidence that would produce a shutdown/restart appears to point to hardware. The GrowlHelperApp wouldn't cause this and neither would your ethernet settings (PPPoE). However, just to be sure, look for the same log pattern on a successive shutdown/restart.

I'd check your RAM first, by pulling out a bank at a time and booting.

 

 

The UUID error indicates you don't have a platform UUID set up. If you aren't using a UUID injector/kext, then you should use the newer bootloaders that automatically inject the UUID based on a SystemID. You insert a SystemID (actually a UUID) in the boot.plist and it'll create a platform UUID for you (different from the SystemID UUID). I have not gone this route, yet, so exact details are a little sketchy. This is not a serious issue. It just creates annoying log messages and some software will not function properly without a valid UUID.

 

The low boot cache hit rate may indicate that you have booted with some kexts that are not designated for this particular install. You should only have one kext included in the /Extra boot cache (fakesmc.kext). If you have another Mac install and you are booting into the bootloader on that install, but selecting a different system to boot from, the bootloader will still use the kexts (boot cache) from the other install (not the one selected). This would create a kext mismatch scenario where the kexts expected are not found or the right types/versions. This could lead to system instability, but we'd need more details first.

Again, this may be completely normal, depending on certain setups, and may mean nothing at all in your case.

 

MAJ

 

I run into w7 and played some games (to load the system) for several hours and then left PC through the night - no restart what so ever.

I feel it must be connected with the update.

 

Regarding extra kext's, I have another hack (iPC distributive, i guess), but it's installed on different HD and therefore I guess different bootloader is used.

Still, while running this (main) install, i see plenty of "loaded HSF+ file... S/L/E/....kext" with Chameleon green logo on screen background (just after I select what to boot in bootloader).

 

 

What I tried now is I went back to original DSDT file and .kexts (with UUID kext included) and will see if I have restarts or not.

 

 

btw, I think it might be a good idea to write a step-by-step faq for noobs like me on how to update current installation with a new script.

Say, I would like to use newer version to be able to use RAID (or any other feature).

If I understand it correct, from the "USING THE SCRIPT" I do:

1) + 2) + 4) + 7) ?

 

Thank you.

 

Denis.

 

UPD: so far so good. Maybe it's because today it's only 17C outside compared to over 30C couple of days before.

I also noticed that in Windows, yesterday, fan (not sure which one, on cpu I have CoolerMaster v8) rotated faster and therefore was more noisy compared to osx. Yet, I think it was that way from the very beginning.

[mrfatcatt]

The new script dated today is not loading in terminal properly

[AutumnJazz]

Hey, I was wondering how I can get my graphics working again? Since I used the DSDT patcher, osx86tools' EFI string thing just doesn't work anymore. I tried using the DSDT patcher, but it just says this:

 DSDT Patch Selector: 

Length larger than Min/Max window fix								Enabled 
Snow Leopard CMOS reset fix										  Enabled 
CPU Alias fix													   Disabled 
Sleep fix (_WAK)													 Enabled 
Power button fix													 Enabled 
Time Machine fix					   (Not implemented.)		   Disabled 
Shutdown fix						   (Not implemented.)		   Disabled 
Orange/External HD icon fix			(Not implemented.)		   Disabled 
USB Device Removal error fix		   (Not implemented.)		   Disabled 
USB native driver hack				 (Not implemented.)		   Disabled 
HDA ALC889a hack					   (Not implemented.)		   Disabled 
ATI graphics hack					  (Not implemented.)		   Disabled 
NVIDIA graphics hack				   (Not implemented.)		   Disabled 
Intel SpeedStep fix					(Not implemented.)		   Disabled 
PS/2 Controller fix					(Not implemented.)		   Disabled 
IRQNoFlags fix						 (Not implemented.)		   Disabled 

Use ↑ and ↓ arrow keys to navigate and → arrow key to toggle fixes.
Press Return/Enter to start patching or press "e" to cancel and exit.

 

Any ideas?

[digital_dreamer]

The new script dated today is not loading in terminal properly

Can you elaborate on that a bit more? I need details.

 

Hey, I was wondering how I can get my graphics working again? Since I used the DSDT patcher, osx86tools' EFI string thing just doesn't work anymore. I tried using the DSDT patcher, but it just says this:

<SNIP>

 

Any ideas?

Are you saying you had a working EFI string and now, after using the DSDT patcher, you don't have QE/CI anymore? Are you sure you still have a EFI string in the boot.plist?

As for the posted DSDT selector list, I don't see anything wrong. Does it not do its job? I need details.

 

EDIT: You are safe with just hitting Enter/Return and letting the DSDT patcher do the job. The default selections apply to just about every board, so there's no harm in applying the fixes. The previous scripts had already applied these fixes, with the exception of the Sleep and Power Button fix.

 

MAJ

[digital_dreamer]

UPD: so far so good. Maybe it's because today it's only 17C outside compared to over 30C couple of days before.

I also noticed that in Windows, yesterday, fan (not sure which one, on cpu I have CoolerMaster v8) rotated faster and therefore was more noisy compared to osx. Yet, I think it was that way from the very beginning.

Isn't the fan controlled by the BIOS at the hardware level? I'm not sure a OS has any role in this. Correct me if I'm wrong, however.

 

EDIT: On a real Mac I know the OS has control, which leads to the infamous jet-taking-off sound when the system hangs.

 

MAJ

[AutumnJazz]

Are you saying you had a working EFI string and now, after using the DSDT patcher, you don't have QE/CI anymore? Are you sure you still have a EFI string in the boot.plist?

As for the posted DSDT selector list, I don't see anything wrong. Does it not do its job? I need details.

 

EDIT: You are safe with just hitting Enter/Return and letting the DSDT patcher do the job. The default selections apply to just about every board, so there's no harm in applying the fixes. The previous scripts had already applied these fixes, with the exception of the Sleep and Power Button fix.

 

MAJ

Yes, I had a working EFI string. I don't know what QE/CI is...

I tried using osx86 tools to re-apply the EFI string, but it was a no go.

 

Re: DSDT: The ones with (Not implemented.) don't allow me to enable/disable them. They just stay disabled. So, for example, I cannot enable the nvidia hack (which I assume would let my graphics work fine without using osx86 tools) or any of those others.

[mrfatcatt]

every now and then i dont see any inro txt when i launch the script

[joker3001]

Hey,

 

the issue is that it simply doesn't sleep. The screens turn black, but fans continue rotating. After forcing shutdown then (because its not waking up...) i looked into the console but there were nothing like kernelpanic etc...

 

Now i use the realtek Kext for ethernet. It works nice!

 

 

Thank you,

 

 

pcace

Dude,

 

Did you manage to sort this issue?

 

Regards

J

[joker3001]

a modified chameleon boot file for chameleon 2 RC4.

 

I am using AsereBLN_v1.1.9 Bootloader which can be installed using DD's latest script.

 

 

ALTERNATIVE (Boot loader)

The modded PCEfi 10.6 bootloader from Prasys' blog also works but I am not using that in this guide, if you want to use that one you can google it.

 

 

Hi CruiSAr,

 

Awesome guide, going to try it tonite.

Just wondering about the booloader. Can I use the stock "AsereBLN_v1.1.9 Bootloader" from DD's script?

 

Awww .. should have looked at DD's script closer .. option is there ..

 

Cheers

J

[digital_dreamer]

Yes, I had a working EFI string. I don't know what QE/CI is...

I tried using osx86 tools to re-apply the EFI string, but it was a no go.

 

Re: DSDT: The ones with (Not implemented.) don't allow me to enable/disable them. They just stay disabled. So, for example, I cannot enable the nvidia hack (which I assume would let my graphics work fine without using osx86 tools) or any of those others.

If you believe the DSDT patch is interfering with your graphics, you can delete the DSDT.aml file in the Extra folder and reboot.

Once you have working graphics, you can then go into the DSDT patcher and apply one fix at a time and reboot in a effort to determine what fix is interfering. You'd need to start with the first one on the list and work down, as the beginning ones are crucial and basic, and progressively get more complex down the list.

However. I don't believe any of the DSDT routines have any bearing on your graphics at all. Something else is amiss. What are you using as an indicator that your graphics are not working? No resolutions in Displays? No transparent menu bar? No operational video?

 

The "Not implemented" fixes are simply not implemented yet.

I kept that list there to provide a preview of what's to come and as a visible to-do list.

 

every now and then i dont see any inro txt when i launch the script

"Intro text?" Are you referring to the "previously saved volume selection" portion where you are prompted to okay that selection?

If you're drives are asleep, the script is going to have to wait until the drives are all spinning and awake before gathering the needed information.

[joker3001]

Hi,

 

I've been re-installing today and just have one issue left.

 

I followed CruiSAr guide. I am using the Voodoo audio kext, only way sound works on my box.

 

I did my initial install (10.6) and everything was working, including sleep.

 

Ran the combo Update to 10.6.4, restarted and clicked sleep, the box sleeps. Bringing it back from sleep results in no signal to screen but the box seems to fire up!

 

I have edited the dsdt from CruiSAr to removed the sound section.

I have the following kexts (all in /S/L/E)

fakemc

Realtek

OpenHaltRestart (box would not restart without this)

VoodooHDA (I got an error on startup and no sound using the DSDT method, had to remove section from DSDT to get sound)

 

Everything works fine except coming back from sleep .. would the OpenHaltRestart be the cause of this?

Any clues?

 

Oh .. I also don't know what my bios version .. what should it be .. I'll check that too.

 

Thanks

J

[CruiSAr]

Hi,

 

I've been re-installing today and just have one issue left.

 

I followed CruiSAr guide. I am using the Voodoo audio kext, only way sound works on my box.

 

I did my initial install (10.6) and everything was working, including sleep.

 

Ran the combo Update to 10.6.4, restarted and clicked sleep, the box sleeps. Bringing it back from sleep results in no signal to screen but the box seems to fire up!

 

I have edited the dsdt from CruiSAr to removed the sound section.

I have the following kexts (all in /S/L/E)

fakemc

Realtek

OpenHaltRestart (box would not restart without this)

VoodooHDA (I got an error on startup and no sound using the DSDT method, had to remove section from DSDT to get sound)

 

Everything works fine except coming back from sleep .. would the OpenHaltRestart be the cause of this?

Any clues?

 

Oh .. I also don't know what my bios version .. what should it be .. I'll check that too.

 

Thanks

J

If you are using the specific board we are using and you followed my guide correctly then everything should work for you as it has for others. Based on my guide the only kext in S/L/E should be for networking.

 

THe DSDT should work for bios F9 to F12. The sound hack in DSDT uses the black port for output (will fix this when I get time). Sometimes certain GPU's cant wake up from sleep, what GPU are you using?