[GUIDE] Scripted Yosemite/Mavericks Install on Gigabyte Mobos

[joker3001]

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?

 

Hi, Thanks for the reply ..

 

The board is a GA-EX58-UD5 (rev 1).

 

I've got a 512MB EVGA 9800GTX+ for gpu.

 

I'm going to flash the bios because I think I am on an older version.

 

I'm installing from Leopard, does that make a difference and the script always fails updating boot caches (probably because of os differences)?

 

The only thing I added to the com.apple.boot plist is the gfx string.

 

Is there a way to install the 10.6.4 combo update directly after the main os install and before booting?

 

Cheers

J

[CruiSAr]

Hi, Thanks for the reply ..

 

The board is a GA-EX58-UD5 (rev 1).

 

I've got a 512MB EVGA 9800GTX+ for gpu.

 

I'm going to flash the bios because I think I am on an older version.

 

I'm installing from Leopard, does that make a difference and the script always fails updating boot caches (probably because of os differences)?

 

The only thing I added to the com.apple.boot plist is the gfx string.

 

Is there a way to install the 10.6.4 combo update directly after the main os install and before booting?

 

Cheers

J

Your GPU should work ok but that is up to you to research on. In my opinion, most Nvidia card should work OOB using the Asere BLN BootLoader which can be installed using DD's script.

 

It doesnt matter how you install the 10.6.4 update. It shoudlnt really make any big difference. The script canot update bootCaches as Leopard is only 32 bit and thus a 64 bit bootCache cannot be created thats why you need to boot in single user mode and build the cache.

 

Probably DD fixed this but I am not sure. If you used the modded bootLoader like I explained then you wouldnt need the efi string but this may be different for your GPU. A couple of Nvidia GPU's give tons of headaches.

[digital_dreamer]

I'm installing from Leopard, does that make a difference and the script always fails updating boot caches (probably because of os differences)?

Building boot caches for SL from Leopard should only be a problem if you are attempting to work with x86_64 kexts in /Extra. The script should automatically direct any x86_64 kexts to be installed into /System (or S/L/E). A boot cache from x86_64 kexts in /Extra is just not possible in Leopard.

So, you have two options:

1. Install them into /System as the script will try to do by default. Once in SL, you can move some of the kexts back into /Extra and rebuild the cache properly. Reboot.

2. Or, install them in /Extra while ignoring the warnings. Then, boot in Single-User mode (-s), type buildcache at the prompt and have the script build it for you there. Reboot.

 

 

Just a heads up on the ATY_Init.kext I included in the last upload (v4.54) that was updated by netkas for the 58XX cards. I've had a lot of trouble with it when using it for my ATI 4870 X2.

1. Slow boots

2. Many applications refusing to launch - a infinite bounce or single bounce with no GUI.

 

Couldn't even launch Console. But, the Apple bug reporter would show up after force quitting, so, I could see what was happening. Something wrong with the ATI graphics info.

Anyhow, I replaced it with the older version and all is well. The 4870 X2 info is there in the new ATY_Init.kext plist. I'll be comparing it with the older one.

 

MAJ

[joker3001]

Thanks Guys.

 

I think main problem was bios was version F7. Updated that and sleep started working.

Followed the guides to a T and happy now.

 

Thanks again guys, appreciate the hard work.

 

Regards

J

[AutumnJazz]

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.

It was osx86 tools' fault. For whatever reason, it wasn't patching the boot.plist file. So, I just added the hexadecimal key manually and now all is well.

 

But if the ATI graphics hack isn't implemented, what's the point of "Added updated ATY_Init.kext with support for the ATI 58XX graphics cards."? (I mainly ask because I actually want a 5850, but I'm not sure how I would get it to work considering osx86 tools doesn't list it.)

[digital_dreamer]

But if the ATI graphics hack isn't implemented, what's the point of "Added updated ATY_Init.kext with support for the ATI 58XX graphics cards."? (I mainly ask because I actually want a 5850, but I'm not sure how I would get it to work considering osx86 tools doesn't list it.)

The ATY_Init.kext is an entirely separate and independent method of adding ATI graphics support. It doesn't rely on info from DSDT.

Once the DSDT routine is added with support for various GPUs, the ATY_Init.kext for ATI graphics and EFI_strings for nVidia cards won't be needed, in theory.

 

So, there are basically three different ways to inject your graphic card info into the system:

1. via injector kext like ATY_Init.kext, NVEnabler.kext, NVinject.kext, etc.

2. via EFI strings, which doesn't work for ATI cards in general.

3. via DSDT modifications

 

MAJ

[AutumnJazz]

The ATY_Init.kext is an entirely separate and independent method of adding ATI graphics support. It doesn't rely on info from DSDT.

Once the DSDT routine is added with support for various GPUs, the ATY_Init.kext for ATI graphics and EFI_strings for nVidia cards won't be needed, in theory.

 

So, there are basically three different ways to inject your graphic card info into the system:

1. via injector kext like ATY_Init.kext, NVEnabler.kext, NVinject.kext, etc.

2. via EFI strings, which doesn't work for ATI cards in general.

3. via DSDT modifications

 

MAJ

Ah, alright then. I saw you were having some trouble with the latest ATY_init.kext, how goes that?

[digital_dreamer]

Ah, alright then. I saw you were having some trouble with the latest ATY_init.kext, how goes that?

There's still trouble there for my 4870 X2. However, it's likely just affecting the 4870 X2 cards. Perhaps a typo in the plist? (All the CR were stripped from the entire plist, so it wouldn't be surprising if there were some missing or added characters in that part.)

I'm just using the older one for now and waiting for a response from netkas.

 

MAJ

[lemarqq]

Can i get some help,please ?

I wanna download Snow Leopard,but i don't know which version,for my mobo ( cpu Intel 7 920 )

Please,if you know,give me a pm.Thanks

[nateB]

I have a totally oddball question. Can a color profile on a monitor be affected by anything in the kext or bootloader processes here? I've been bothered by a too-bright display and blown-out colors or a while and have used all the hardware recalibration stuff I have to try to resolve it with no progress.

 

But what I've just discovered is that my monitor looks better if I unplug the DVI cable, wait a second, and then plug it back in. Things now look like they should. Whites are milder, the reds not so absurd. They remain OK after going to sleep and coming back, but a reboot will whack everything out again. This is a 2 display setup on a 9800gtx, on 10.6.4, with corrections made for the nvidia driver problems in 10.6.4. I'm using the latest Chameleon in the DD script with graphicsenabled=yes and NV Enabler 64.kext. Both monitors improve their images after being unplugged and plugged in again, and look fine through my MBP output.

 

Are there any instances of problems like this elsewhere? Does it sound like video card hardware or something with the drivers in use?

[digital_dreamer]

nateB,

Can you get full graphics with just the graphicsenabled=yes flag and no NVEnabler 64.kext?

Or, how about just using a EFI string, instead of the kext?

I'm not sure any of that would make a difference, but I'm thinking a EFI string may load earlier. It doesn't appear it's getting your monitor info correctly. Does the monitor name and port name appear correctly in System Profiler or System Preferences/Displays (after boot, but before unplugging/plugging cable)?

 

I've found color management to be a mixed bag. My 4870 X2 and 22" NEC CRT isn't able to manage the contrast correctly. Have little control over it when trying to edit the profile.

 

MAJ

[nateB]

Thanks for the reply.

 

Can you get full graphics with just the graphicsenabled=yes flag and no NVEnabler 64.kext?

Or, how about just using a EFI string, instead of the kext?

I'm not sure any of that would make a difference, but I'm thinking a EFI string may load earlier. It doesn't appear it's getting your monitor info correctly. Does the monitor name and port name appear correctly in System Profiler or System Preferences/Displays (after boot, but before unplugging/plugging cable)?

 

I've found color management to be a mixed bag. My 4870 X2 and 22" NEC CRT isn't able to manage the contrast correctly. Have little control over it when trying to edit the profile.

 

-Using only graphicsenabled=yes with no supporting kext gets me a display but no resolution control. Everything is terribly lo-res.

 

-With only the EFI string things display at proper resolution but the color issues persist.

 

-The info for the display is unchanged from boot, even after unplugging and reconnecting, in the Profiler. The Profiler does think that the video card is a GTX+ though when using graphicsenabled=yes and the NVE 64 kext . I can't figure out what's changed by removing the cable.

[jhrfc]

nateB,

Can you get full graphics with just the graphicsenabled=yes flag and no NVEnabler 64.kext?

Or, how about just using a EFI string, instead of the kext?

I'm not sure any of that would make a difference, but I'm thinking a EFI string may load earlier. It doesn't appear it's getting your monitor info correctly. Does the monitor name and port name appear correctly in System Profiler or System Preferences/Displays (after boot, but before unplugging/plugging cable)?

 

I've found color management to be a mixed bag. My 4870 X2 and 22" NEC CRT isn't able to manage the contrast correctly. Have little control over it when trying to edit the profile.

 

MAJ

 

This is one of the reasons why I bit the bullet and paid more for an nvidia GPU, I was able to load the specific HW calibrated profile for my setup and get great colour performance.(Although Apple crippling Nvidia 3d performance with 10.6.4 was not good!!)

Cheers

Jon

[AutumnJazz]

This is one of the reasons why I bit the bullet and paid more for an nvidia GPU, I was able to load the specific HW calibrated profile for my setup and get great colour performance.(Although Apple crippling Nvidia 3d performance with 10.6.4 was not good!!)

Cheers

Jon

1. Do you mean you bought an Apple-bound GPU? (Eg. the EVGA 285 GTX made specifically for Mac Pros.)

2. What did Apple do to nvidia performance in 10.6.4?

[jhrfc]

1. Do you mean you bought an Apple-bound GPU? (Eg. the EVGA 285 GTX made specifically for Mac Pros.)

No I've got a PC card Zotac 1gb GTX285. Works great with the injection in asere bootloader, and native drivers (or did, see below).

 

2. What did Apple do to nvidia performance in 10.6.4?

Something in 10.6.4 update severely affected graphics performance in some nvidia GPUs see:

http://www.tuaw.com/2010/06/21/steam-doesn...ll-with-10-6-4/

My framerates where 30% of what they where.

 

Luckily for us with hackintoshes, there is a workaround involving setting your modelid in smbios .plist to MacPro3,1 which restores performance.

If I had shelled out for a geniune macpro and mac gtx285, i'd be hopping mad with Apple.

Cheers

Jon

[antovasa]

UPDATE: Solution at post: 2697

Hi Digital_Dreamer:

 

I have a Hackintosh working correctly since 10 months thanks to your fantastic script. Somedays back i came here to see for updates and i saw that you added support for RAID on your latest script version, so i formatted my hd's to have fun.

 

First, maybe there is any special instruction on how to setup a system using the Apple RAID, i created the RAID Array, then installed OS X, booted using your prebuild boot cd and run the the hackintosh script. Let me know any special instruction for a RAID setup.

 

But the DSDT patcher of your latest script does not corrects the CMOS Error because the CPU looses BIOS config on each restart. Maybe the bootloader (tried booth PC-EFI 10.6 and Chameleon 2 RC4) is not able to see the DSDT file.

 

Also, i was using an EFI string to make my graphic card to work perfectly, but with this new version of your script it does not work (i mean, i just see on basic resolution without QE anc CI). I thing all this is related to the RAID setup.

 

I have a GA-EX58-UD5 Bios F12

 

I really would love to use the RAID mode, let me know if there is something that i can do. Thanks in advance and congratulation for your fantastic work

 

 

Here is part of the DSDT Log so you can see:

 

http://tinypaste.com/e7dbd

[Sumrall]

Ok, I am installing using the pre-boot cd method. After I switch to the installation cd (Mac OS X 10.6.3), everything seems to be going as planned, but then I get a kernal panic.

 

This is what I see...

 

Any ideas on what I can do? Forgive me if I've missed something. I have been searching. It looks like something with the graphics card? I didn't think that would cause me to hang up. I'm using the ATI 4870 (which is working on the Leopard build that I'm on now).

 

Any help would be great.

Thanks.

[digital_dreamer]

antovasa,

Sorry you are having issues with the RAID setup.

The DSDT log looks fine, but I need the Install.log to see what's happening and if the DSDT file is getting copied to the correct location.

 

All the issues you mention appear to point to a common area: Are you sure you have the RAID selected as your target in the script when installing the DSDT patch, EFI string, etc?

There aren't any special instructions for the RAID, as it's treated like a regular hard drive.

 

Let me see the Install.log and I'll analyze what's up.

 

Best of wishes,

MAJ

 

Ok, I am installing using the pre-boot cd method. After I switch to the installation cd (Mac OS X 10.6.3), everything seems to be going as planned, but then I get a kernal panic.

<snip>

That is odd.

I'm going to release a different preboot CD/ISO without any ATI injector kexts. I'll let you know when I post it.

EDIT: Have you tried the other Boot CD?

EDIT: The sequel: Here's an updated PrebootCD/ISO.

 

MAJ

[Sumrall]

Great, I'll try that now. Just tried the other Boot CD with the same result.

 

Update:

 

Well, I used the new pre-boot cd and didn't get the kernal panic. However, now I'm getting hung up after it goes to the apple logo loading screen. The cd stops after a few seconds and then a small crossed-out circle appears. Nothing happens after that.

 

Actually, the first time it went to a screen that asked me to manually restart the computer (in 5 languages).

 

Also, I've noticed that the BIOS setting for AHCI keeps getting turned off. Could that be causing the hang-up?

[digital_dreamer]

Sumrall,

Hmmm. Have you tried the other boot CD download.

Try booting with the -v flag, so the boot log will be visible and a picture can be taken of the KP.

What board are you using?

 

As for the BIOS setting, that would appear normal, as Snow Leopard will reset the BIOS settings. Until we get a patched DSDT (CMOS reset fix) in there, you'll have to keeping loading your settings at each boot.

 

 

antovasa,

Does nothing show up in the Sound preferences? Make sure you have "Internal Speakers" selected in Outputs and that you are using the Green output jack.

 

MAJ

[antovasa]

antovasa,

Does nothing show up in the Sound preferences? Make sure you have "Internal Speakers" selected in Outputs and that you are using the Green output jack.

 

MAJ

 

Let me tell you that AZALIA was disabled on the BIOS, i think that those multiples CMOS resets modified the original settings, and when i corrected them i forgot to activate that. Sorry.

 

Here is an install.log of a problematic installation http://tinypaste.com/34597

 

UPDATE: Found the Problem

 

I'm able to do a Full working RAID. I did various tests and this is what i found:

 

I think that the problem was caused by an external HD (HFS+ Formatted) that i used to copy the script to the computer. I think that Maybe the scripts gets confused because it sees another HFS+ volume connected when installing the bootloaded and installing the kexts. I'm pretty sure that everytime i selected to install on the RAID volume.

 

Maybe you should check your script, because if for some reason we have another HFS+ volume at the time of executing the script for the first time it gets confused or do not operates correctly.

 

So here are the Steps to do a RAID installation without problems with current script version (GA-EX58-UD5):

 

Follow the Preboot CD Method described by Digital_Dreamer

 

1. Boot Using your Preboot CD

2. Insert SL Disc , press F5 to refresh then press Enter

3. Before starting the setup, Go to Utilities, Disk Utility and create a RAID Volume OS Extended + Journaled

4. Start SL Setup (do not install printers and unneeded languages) Then Wait

5. When Setup Finishes it will restart, extract SL Install Disk

Note: Step 5 is because you cannot Eject SL Installs Disc before the boot

6. Insert preboot CD, boot with F12 to boot from the CD, and later select first HD of the RAID on chameleon then ENTER

 

At this point i finish SL Setup (User, Password, Name, i see the introvideo) then i'n at Desktorp with basic resolution

 

7. Copy Hackinstaller Script to the computer.

 

8. Before starting the script, eject unneeded drives (external and internal if you have, you leave the RAID and its related HD's.

 

9. Run the script, select your RAID volume then go trough steps 2,5,7 , 9 for the EFI String of your Video Card, then step 6.

 

Reboot and voilá, it works perfect.

[digital_dreamer]

antovasa,

Glad you got the RAID setup going.

 

I parsed through the log you posted and didn't find any show stoppers. I found a few little bitty things that I'm going to clean up, like the script attempting to copy the READ_ME clippings from the Themes folder.

 

The only thing that's a mystery to me is the drive that shows up when you're in the Plist Selector/Editor. It's blank and doesn't have a ID. I thought it would be from your unnamed NTFS volume, but I have the same setup and the script ignores NTFS partitions. I also thought it would be the Preboot_CD, but I mount those ISOs all the time and the script is set up to ignore those read-only volumes. I don't know where that line comes from.

 

I have 6 drives, including AppleRAID, on my system and multiple HFS partitions have never been a issue. I test with various setups, even renaming partitions with odd characters and duplicate names, just to try to cover all scenarios.

 

Did this other drive you copied the script from have the same name as the other?

Also, when the script didn't work out for you the first time, what was the behavior? What indicated something was wrong?

 

best of wishes,

MAJ

 

Sumrall,

You can pull the ElliottForceLegacyRTC.kext out of the Misc. Patches repository folder and have that installed. It will take care of the CMOS reset issue, until we get a DSDT patch.

 

MAJ

[antovasa]

antovasa,

Glad you got the RAID setup going.

 

I parsed through the log you posted and didn't find any show stoppers. I found a few little bitty things that I'm going to clean up, like the script attempting to copy the READ_ME clippings from the Themes folder.

 

The only thing that's a mystery to me is the drive that shows up when you're in the Plist Selector/Editor. It's blank and doesn't have a ID. I thought it would be from your unnamed NTFS volume, but I have the same setup and the script ignores NTFS partitions. I also thought it would be the Preboot_CD, but I mount those ISOs all the time and the script is set up to ignore those read-only volumes. I don't know where that line comes from.

 

I have 6 drives, including AppleRAID, on my system and multiple HFS partitions have never been a issue. I test with various setups, even renaming partitions with odd characters and duplicate names, just to try to cover all scenarios.

 

Did this other drive you copied the script from have the same name as the other?

Also, when the script didn't work out for you the first time, what was the behavior? What indicated something was wrong?

 

best of wishes,

MAJ

 

The External HD is a Hitachi 2TB inside a Macally Enclosure, i connected it to the computer using the firewire 400 port of the front of the PC. It's Volume name is Data Drive.

 

I did about 7 install from scratch tests, and every test with this drive connected caused the Script to have that weird behavior with that unnamed volume.

 

The behavior of the script was the next:

 

2. Installed Bootloader successfully

5. Installed Kexts successfully

7. Created the DSDT sucessfully

9. Went to create the EFI for my Video Card and the RAID volume was not available, just the /script one

 

Went back to Install Kexts and it finishes without processing information (i think it is not able to view the RAID helper partitions)

 

Went back to Install Bootloader, and it says that there is no BootLoader installed. So i install it back

 

Do the kext install again and it works.

 

Go to Plist, and i see that unnamed volume.

 

That what happens. Its strange i know.

 

P.S. Would it be possible to make the prebootcd routine to generate a PrebootCD with the DSDT.aml information that your script gets from the computer. That would be great, its very annoying to have to re-setup BIOS every time that i boot the computer using that CD.

 

Is there any limitation to do that?

[schwamm]

Speaking of raid, does anyone know of a good value hardware-based RAID? I've had the apple raid working before, but the performance gain was not what I expected. If anyone has an easily supported raid card let me know.

 

Also, thank you so much for this script! I'm a professional web developer, and I've been using the same SL installation on my UD4P board since SL came out. Works perfectly, never had a kernel panic.

 

I have a friend who does video editing and owns a dual-processor 2.26ghz nehalem mac pro. My hackintosh (at 3.75ghz) rendered HD video faster than the real mac, which cost 3 times as much. And when his mac broke down, guess who they called at the last minute to save them? Me with my hackintosh. It's an amazing machine, thanks for all your work making it possible!

[digital_dreamer]

<SNIP>

P.S. Would it be possible to make the prebootcd routine to generate a PrebootCD with the DSDT.aml information that your script gets from the computer. That would be great, its very annoying to have to re-setup BIOS every time that i boot the computer using that CD.

 

Is there any limitation to do that?

Thanks for that info. It's helpful.

Here's my only suggestion: Anytime a drive is plugged in (external), make sure you restart the script or reselect your target volume (#17). I'm thinking that, perhaps, a volume was introduced after the script was started and that may have created some issues. I can't think of what else.

 

If you ever plan to repeat those install steps with the external drive connected and you find it behaving oddly, let me see the install.log. Unfortunately, the log that was posted doesn't show that external drive connected (or if it was actually connected after the script start, that may explain some things, but can't be for sure).

 

But, I want to thank you for working through this, as it'll help me get this worked out to be as painless as possible for everyone. That's the goal.

 

MAJ