[GUIDE] Scripted Yosemite/Mavericks Install on Gigabyte Mobos

[digital_dreamer]

<snip>

At first boot into Lion DF4 all kexts loaded as if using -f flag.

<snip>

 

Thanks for your feedback, everdone.

 

The above quoted happens because there is no boot cache, so the bootloader is forced to load all kexts from S/L/E, just like would happen if you forced it to ignore the boot cache.

 

On the RAID front, marliwahoo and Crna Brada were able to boot DP4 on Apple RAID by putting the entire S/L/E boot cache in /Extra. This can be accomplished in the script by using the Combo option, where the /Extra and /System cache is combined and built into /Extra.

 

MAJ

[DocShadow]

Decided to try DP 4. I have it up and running on my EX58-UD5 but need to 'clean' up a few things.

 

Used both my SL 10.6.6 DSDT and a freshly created DSDT from windows using DSDT Auto-Patcher and no difference.

 

First .... no sound. If I try and use VoodooHDA I get a KP. I've also tried ALC889a.kext, AppleHDA.kext, Legacy889HDA.kext. In this case it will load to desktop but no sound.

 

Second ... and more importantly, the computer will sort of sleep and not wake up. I know when it goes into a 'fake' sleep as the screen goes black and the video card fan increases in speed. I have to hard/soft restart it to get control back.

 

I have currently loaded ... EvOreboot, FakeSMC, IOAHCIBlockStorageinjector, IONetworkingFamily, JMicro36xeSATA, NullCPUPowerManagement, AppleRTC

 

I have also boot to desktop without DSDT but find that I can use VoodooHDA for sound but I still have the sleep problem and need NVEnabler to get graphics.

 

All kexts are changed using the script.

 

Contents of com.apple.Boot.plist ....

 

<key>Default Partition</key>

<string>hd(0,2)</string>

<key>EthernetBuiltIn</key>

<string>Yes</string>

<key>GenerateCStates</key>

<string>Yes</string>

<key>GeneratePStates</key>

<string>Yes</string>

<key>GraphicsEnabler</key>

<string>Yes</string>

<key>Instant Menu</key>

<string>Yes</string>

<key>Kernel</key>

<string>mach_kernel</string>

<key>Kernel Flags</key>

<string>-v -usecache</string>

<key>Legacy Logo</key>

<string>Yes</string>

<key>SMBIOS</key>

<string>/Extra/smbios.plist</string>

 

Contents of smbios.plist ...

 

<key>SMbiosversion</key>

<string>MP41.88Z.0081.B07.0910130729</string>

<key>SMmanufacter</key>

<string>Apple Inc.</string>

<key>SMmemmanufacter</key>

<string>Corsair XMS3</string>

<key>SMmempart</key>

<string>TR3X661600C9</string>

<key>SMmemserial_1</key>

<string>000123-01234567-0</string>

<key>SMmemserial_2</key>

<string>EMPTY</string>

<key>SMmemserial_3</key>

<string>000123-01234567-1</string>

<key>SMmemserial_4</key>

<string>EMPTY</string>

<key>SMmemserial_5</key>

<string>000123-01234567-2</string>

<key>SMmemserial_6</key>

<string>EMPTY</string>

<key>SMmemspeed</key>

<string>1333</string>

<key>SMmemtype</key>

<string>24</string>

<key>SMproductname</key>

<string>MacPro4,1</string>

<key>SMboardproduct</key>

<string>Mac-F221BEC8</string>

<key>SMserial</key>

<string>SECRETNUMBER</string>

<key>SMsystemversion</key>

<string>1.0</string>

 

Thanks,

[Crna Brada]

....I've filed a bug report on this elsewhere:

"Installed on a RAID setup (striped) Lion DP4. It appears all is there as far as system files and bootloader support is concerned. However, Chameleon doesn't read the RAID correctly at the screen selection.

My RAID is called "MacRAID" and the helper partitions are the default names, "Boot OS X". But, the Chameleon (r1002) screen shows "MacRAID 1" and MacRAID 2" instead. Of course, the boot process is very, very short and nothing gets loaded."

 

This applies to both the /Extra and EFI installs. Doesn't sound like a difficult fix. Accessing Lion RAID info is slightly different from Snow.

 

kind regards,

MAJ

 

MAJ (or digital_dreamer),

 

Thank you vey much for your detailed response! I learnt a bit more about Hackintosh from it.

Looking forward to a new version of your installation tool with Chameleon fix for Lion RAID.

Please let me know if I can help.

 

Best regards,

Crna Brada

[Jay Bomb]

I may have taking a big leap here but I need some minor help. I decided to attempt to update my Snow 10.6.2 to 10.6.7 First time through I got a kernel panic about the Sleep.kext, once I installed the new kexts via the Hackinstaller file and updated the boot cache it hangs when loading the drive and then my screen just shuts off but the computer stays on. Should I run the DSDT patcher? or change something around? Once I get this updated I will like to try out 10.7

[VirusX]

First time through I got a kernel panic about the Sleep.kext, once I installed the new kexts via the Hackinstaller file and updated the boot cache it hangs when loading the drive and then my screen just shuts off but the computer stays on. Should I run the DSDT patcher? or change something around?

Could you please provide more information? Which kexts do you use? Which bootloader? What graphic card do you have?

 

regards

[Jay Bomb]

Could you please provide more information? Which kexts do you use? Which bootloader? What graphic card do you have?

 

regards

 

I believe just the kexts that are in the Hackinstaller script package on the front page. I'm still on Chameleon RC2 and I believe my GPU is a EVGA 8800+

 

I could be doing something wrong with the kexts. When I booted into my Kaly drive, (after the first time I got the panic) I removed the old sleep kext from my main partition. Then when I ran the installer it took me straight to the kext updater once I identified which drive I was installing to. When I rebooted now I get the hanging loading scroll and no signal from screen.

 

I downloaded the new sleep kext for 10.6.7 this morning but won't be able to test till later. I hope this information helps a bit more.

[Windows04]

I believe just the kexts that are in the Hackinstaller script package on the front page. I'm still on Chameleon RC2 and I believe my GPU is a EVGA 8800+

 

I could be doing something wrong with the kexts. When I booted into my Kaly drive, (after the first time I got the panic) I removed the old sleep kext from my main partition. Then when I ran the installer it took me straight to the kext updater once I identified which drive I was installing to. When I rebooted now I get the hanging loading scroll and no signal from screen.

 

I downloaded the new sleep kext for 10.6.7 this morning but won't be able to test till later. I hope this information helps a bit more.

 

Do you have graphics kexts installed or do you just use Graphicsenabler = Yes in Chameleon? If you use neither of those, it can be that the system loads, but isn't able to display something because the graphic drivers aren't installed (= hanging loading scroll).

 

What's the last thing(s) you see when you boot with kernel flag -v? (just typ -v in Chameleon before you hit enter to boot your drive)

[nabziF99]

Long-time user of the script; it's pretty fabulous!

 

I have three questions currently which I've had difficulty finding straight answers for:

 

1. It is well established that Chameleon has trouble with partitions over 1TB (or at least used to; is the latest RC5 any better about this?). Since I want my primary volume to be larger than 1TB, my solution was to start with 1 small partition, get the OS running, then resize to fill the rest of the drive, and for some reason Chameleon still works. But that little trick falls apart if the drive ever has to be repaired with DiskWarrior, since you have to reinstall the bootloader after a DW repair. Now that the partition is "full size", reinstalling Chameleon once again gives the boot0 error. (Strangely, v5.01 of the script detects the bootloader it just installed, but if I try the same with v5.54 of the script it says no bootloader installed, even immediately after using the script to install Chameleon.) So I guess the only solution that takes potential future DW repairs into account, is to keep the boot partition 1TB or less? Drives (and thus partitions) will only get larger in the future, so I predict this problem will become more and more prevalent unless it is fixed (if it is even fixable).
    
    
   
2. Speaking of Chameleon - the current version of the script says RC5 r691 is "your best choice". Indeed, I've read that it fixes restart without resorting to a kext, and while I don't restart often, when I do it is rather annoying to have to manually hit the reset switch. But I have some trepidation about upgrading from the latest official release (RC4 684) to an unofficial release. That one came out such a long time ago; is the official release no longer being developed? (I suppose the entire osx86 concept is rather unofficial; declaring RC4 "official" and RC5 "unofficial" seems a bit like splitting hairs, so perhaps my hesitation is unfounded?)
    
    
   
3. In the script's section "Modify plists and EFI strings", the default option is "For HackInstaller", with the other options for specific boot partition(s). I assume when you choose "For HackInstaller" and then run the full install, the Plists/EFI strings are copied to whichever partition you're installing to. Which specific installation step copies the Plist info from the script to the partition? Just curious. (I thought it was the kext/kernel installer but that wasn't it.)
   

[digital_dreamer]

I have three questions currently which I've had difficulty finding straight answers for:

All good questions, nabziF99!

 

It is well established that Chameleon has trouble with partitions over 1TB (or at least used to; is the latest RC5 any better about this?). Since I want my primary volume to be larger than 1TB, my solution was to start with 1 small partition, get the OS running, then resize to fill the rest of the drive, and for some reason Chameleon still works. But that little trick falls apart if the drive ever has to be repaired with DiskWarrior, since you have to reinstall the bootloader after a DW repair. Now that the partition is "full size", reinstalling Chameleon once again gives the boot0 error. (Strangely, v5.01 of the script detects the bootloader it just installed, but if I try the same with v5.54 of the script it says no bootloader installed, even immediately after using the script to install Chameleon.) So I guess the only solution that takes potential future DW repairs into account, is to keep the boot partition 1TB or less? Drives (and thus partitions) will only get larger in the future, so I predict this problem will become more and more prevalent unless it is fixed (if it is even fixable).

And, here I thought the volume size limitation was fixed. I see issues with >2TB. I personally have two 1TB drives and no issues to report, but they really fall under 1TB.

 

Bootloader detection is far more complete in v5.5x. All the previous ones would do is look for the main boot file copied to root, but it would ignore the stage-0 (boot0) and stage-1 (boot1h or boot1hfs) installations. All three stages are required to boot, however, so the previous scripts have been misleading. Once I figured out a way to detect the installation of the stage-0 and stage-1 installs, I incorporated it into v5.5.

 

I don't know if there should be a different procedure for bootloader installation on >1TB. I've been looking.

 

Speaking of Chameleon - the current version of the script says RC5 r691 is "your best choice". Indeed, I've read that it fixes restart without resorting to a kext, and while I don't restart often, when I do it is rather annoying to have to manually hit the reset switch. But I have some trepidation about upgrading from the latest official release (RC4 684) to an unofficial release. That one came out such a long time ago; is the official release no longer being developed? (I suppose the entire osx86 concept is rather unofficial; declaring RC4 "official" and RC5 "unofficial" seems a bit like splitting hairs, so perhaps my hesitation is unfounded?)

Good points.

I call it unofficial only because the team hasn't frozen the feature set and development is still a moving target. Although RC5 has not been 'officially' released, the developers have been making the latest releases publicly available on the forums. Revision 1028 is the latest as of today. I'm currently using r1020.

There are issues, but most of the issues are with new features that have been added from other branches, including support for new graphic cards. The issues seldom affect day-to-day general use. One exception I've noticed is not being able to enter flags at the prompt on the non-GUI version. I hope Meklort will fix this shortly.

 

I don't know when the Chameleon Team is going to make RC5 official. They have been merging in the different branches with rapid pace in the few last months. It appears the upcoming Lion release has gotten many moving even faster, prompting me to believe its official release is due shortly. Lion has complicated a few things. Lion on RAID needs a little help, but it's workable.

 

 

In the script's section "Modify plists and EFI strings", the default option is "For HackInstaller", with the other options for specific boot partition(s). I assume when you choose "For HackInstaller" and then run the full install, the Plists/EFI strings are copied to whichever partition you're installing to. Which specific installation step copies the Plist info from the script to the partition? Just curious. (I thought it was the kext/kernel installer but that wasn't it.)

Sorry, this hasn't been really clear. I've thought about this issue myself.

It's only during the initial bootloader installation that the plists get copied over. This is the time the /Extra folder is built and populated. After that, copying over the plists from the HackInstaller is optional, again during a bootloader install. When you are prompted with the following question, you have the option to copy over those plists:

"Some bootloader support files already exist in YOUR_VOLUME.

Preserve this /Extra directory and its contents, instead of

removing them and copying new ones from script's /Plists folder?"

 

best regards,

MAJ

[Windows04]

DD, could you please send me the boot file of rev 1020, I really have no idea how I should make the boot file myself using the trunk files :S...

[Jay Bomb]

Do you have graphics kexts installed or do you just use Graphicsenabler = Yes in Chameleon? If you use neither of those, it can be that the system loads, but isn't able to display something because the graphic drivers aren't installed (= hanging loading scroll).

 

What's the last thing(s) you see when you boot with kernel flag -v? (just typ -v in Chameleon before you hit enter to boot your drive)

 

I tried to get a decent photo. After I typed -v on boot it showed files be loaded (text rolls down screen) then it went to a black screen and more text rolled down, near the end I got about 10+ lines that read:

 

Sound assertion "0 == entry" failed in "/SourceCache/AppleHDR...

Sound assertion "0 == entry" failed in "/SourceCache/AppleHDR...

Sound assertion "0 == entry" failed in "/SourceCache/AppleHDR...

Sound assertion "0 == entry" failed in "/SourceCache/AppleHDR...

etc. and then the screen went off again.

 

I tried switching out the Graphics kext with others in the repository folder but no luck. I do remember before I was using custom strings provided by Aquamac in order to get my GPU to work probably. I suspect this is probably where all is going wrong. Not sure how to approach it yet.

 

Question: Would it be wise to just wait for 10.7 since I do plan to upgrade on release date next week? Or should I go ahead and install DP4 over my Snow Drive? Thanks for all the assistance.

[digital_dreamer]

I do remember before I was using custom strings provided by Aquamac in order to get my GPU to work probably. I suspect this is probably where all is going wrong. Not sure how to approach it yet.

Yep, I believe that string is what you need and why you get a black screen without it.

 

P.S. If you use custom strings or a graphics injector kext, make sure you have the GraphicsEnabler key/string in boot plist deleted or set as "No" so that there is no conflict.

 

Question: Would it be wise to just wait for 10.7 since I do plan to upgrade on release date next week? Or should I go ahead and install DP4 over my Snow Drive? Thanks for all the assistance.

I'd wait, because the golden candidate release may not allow you to update your existing DP4, requiring you to reinstall from scratch anyway.

 

Windows04

The RC5 r1020 is here.

This is my repository that the new script release will be checking in for updates.

 

MAJ

 

First .... no sound. If I try and use VoodooHDA I get a KP.

This happens due to a conflict with the vanilla AppleHDA.kext. The solution is to disable that kext by renaming it and rebuilding the cache. I plan on having the script automatically renaming this kext anytime the VoodooHDA.kext is involved.

 

Second ... and more importantly, the computer will sort of sleep and not wake up. I know when it goes into a 'fake' sleep as the screen goes black and the video card fan increases in speed. I have to hard/soft restart it to get control back.

 

I have currently loaded ... EvOreboot, FakeSMC, IOAHCIBlockStorageinjector, IONetworkingFamily, JMicro36xeSATA, NullCPUPowerManagement, AppleRTC

Getting sleep to work is a moving target and may change with the final release. Wish there was a magic bullet that fixes sleep for all setups.

 

Contents of com.apple.Boot.plist ....

I'd remove the -usecache kernel flag, as that's not recognized or used anymore by the latest RC5 releases. The official flag is now a key: UseKernelCache with the "Yes" string. This setup won't work with the mkext cache that the script produces. It's either install all kexts in /System and use kernelcache, or install kexts in /Extra and use the normal mkext cache from the kexts (like Snow).

 

 

MAJ

[DocShadow]

Thanks for your help.

 

Used another DSDT, deleted AppleHDA.kext and now have sound with VoodooHDA.

 

Too bad about sleep ... kind of useless without it. I'll have to keep plugging along and see if I can 'stumble' across a solution.

 

I noticed I get the error nstat_lookup_entry failed on loading .... any idea what that is?

[DocShadow]

When running the "Run kext/kernel installer" or "Update System boot cache" I get the error ...

 

stat: /Volumes/MacLion/Users/Ted/Library/Preferences/ByHost/com.apple.syncservices.ConflictResolver.5AF50D3A-D707-57AF-B76C-A29AE84A1CB2.lockfile.plist: stat: No such file or directory

 

Any idea why and how I can fix it?

 

It seems that my boot cache is not being refreshed.

 

Thanks.

[pcace]

Hey,

 

i want to re install my Hackintosh because all the time i used it i have had Graphic problems. Now i want to set it up with a raid0 (4HDDs).

 

i Downloaded the Newest Hackinstaller and burned a Preboot CD. Now the Problem is, everytime i boot into the Bootloader and change to the retail DVD, (yes, i reloaded via f5) my Computer simply restarts!

 

Has anyone an idea what the Problem could be?!

 

 

Thanks,

 

Pcace

[rumz]

10.6.8 is out. Presumably it puts in place whatever underpinnings Lion needs to be installed from the App Store. Be interested to see what happens. 10.6.7 is working so nice

 

Best way to back up an install before trying an upgrade? SuperDuper do the job?

[veddernick]

10.6.8 is ready, in apple's update page

[digital_dreamer]

stat: /Volumes/MacLion/Users/Ted/Library/Preferences/ByHost/com.apple.syncservices.ConflictResolver.5AF50D3A-D707-57AF-B76C-A29AE84A1CB2.lockfile.plist: stat: No such file or directory

That 'stat' message is fixed in my latest unreleased version. However, it shouldn't affect any boot cache updates.

If there is nothing new in the kexts directory, the boot cache doesn't actually get updated. This is due to Apple implementation of the 'kextcache' command and nothing you have control over, unless you delete the present boot cache to force an update.

 

If the boot cache is not getting updated when you believe it should be, I'll need the Install log to see what's going on.

 

Sorry for the trouble.

 

i Downloaded the Newest Hackinstaller and burned a Preboot CD. Now the Problem is, everytime i boot into the Bootloader and change to the retail DVD, (yes, i reloaded via f5) my Computer simply restarts!

Are able to see any messages on the screen, like "can't find kernel" or something else?

Have you tried the other ISO, "BootCD"?

What version of Snow is the DVD?

 

best of wishes,

MAJ

 

P.S. I plan on release a new script version shortly. It will allow one to build a boot disk in a multitude of ways:

From DVD to DVD/ISO

From DVD to drive

From ISO (or App Store download) to DVD/ISO

From ISO (or App Store download) to drive

 

This has been very time-consuming to bug test. Ugg.

[epitaphic]

Tried out 10.6.8 on a test hd, looks like they changed quite a lot of stuff. While I can boot into the OS without any problems, ethernet and wifi are not working and the OS is dog slow; beach balls everywhere, 3-6 second delay launching stuff that normally take <0.2s (menu items, spotlight, network prefs, etc)

 

FYI: Using CruiSAr's method with DD's script.

[pcace]

Are able to see any messages on the screen, like "can't find kernel" or something else?

Have you tried the other ISO, "BootCD"?

What version of Snow is the DVD?

 

Hi,

 

i managed it to install OSX. I installed it via my MacbookPro.

But now my next question: How can i use 2 Graphic cards? I have a Nvidia 9800GT and a 260GTX.

 

 

Any Idea what the simplest way would be?

 

 

Thanks,

 

Pcace

[jhrfc]

Tried out 10.6.8 on a test hd, looks like they changed quite a lot of stuff. While I can boot into the OS without any problems, ethernet and wifi are not working and the OS is dog slow; beach balls everywhere, 3-6 second delay launching stuff that normally take <0.2s (menu items, spotlight, network prefs, etc)

 

FYI: Using CruiSAr's method with DD's script.

 

Thanks for the heads up, i was getting quite complacent about updates unde rmy 10.6 setup, so may have applied this without doing a full backup. Please post if you find any more info or solutions.

Cheers

Jon

[pcace]

By the way: what is the best method to backup a raid0?

 

 

Thanks,

 

Pcace

[everdone]

Updated to 10.6.8 (from 10.6.7) on a GA-EX-58 and GA-EX58A board without a major problem. The only thing that 'broke' was audio but that was easily fixed by reloading the audio kexts that had been previously loaded to fix audio in 10.6.7.

[rgb]

Updated to 10.6.8 (from 10.6.7) on a GA-EX-58 and GA-EX58A board without a major problem. The only thing that 'broke' was audio but that was easily fixed by reloading the audio kexts that had been previously loaded to fix audio in 10.6.7.

 

hi.

 

My audio was broke too

Could you share how do you fix it?

Thx

 

Updated to 10.6.8 (from 10.6.7) on a GA-EX-58 and GA-EX58A board without a major problem. The only thing that 'broke' was audio but that was easily fixed by reloading the audio kexts that had been previously loaded to fix audio in 10.6.7.

 

hi.

 

My audio was broke too

Could you share how do you fix it?

Thx

[@ROBASEFR]

Updated to 10.6.8 (from 10.6.7) on a GA-EX-58 and GA-EX58A board without a major problem. The only thing that 'broke' was audio but that was easily fixed by reloading the audio kexts that had been previously loaded to fix audio in 10.6.7.

 

GA -EX58-UD5

 

Updated 10.6.7 to 10.6.8 from rescue disk and the 10.6.8 combo update with Pacifist.

 

Then used 5.54 install script and chameleonRC5 rev 841 bootloader.

 

No major problem for the moment