[GUIDE] Scripted Yosemite/Mavericks Install on Gigabyte Mobos

[KeNgoaiDao]

10.7.2 amazing works with dd's script hackinstaller 6.52 (RAID 0 with no Facetime)

[fruitbat04]

The reason you guys are having problems with logging in with iCloud is because the latest Chameleon doesn't work with it.

 

You need to go back to 1493 as detailed here http://forum.voodooprojects.org/index.php?topic=2215.0

 

I think some kind person recompiled the latest version with the fix in, but I'm not sure where it is.

 

Maybe Maj could put 1493 back into the script as an option until they fix it?

 

Rolling back confirmed to fix by lots of people including me.

[digital_dreamer]

fruitbat04,

Anyone should be able to roll back to r1493 with the latest script. Just show the log for Chameleon (3 L) and use arrow keys to get back to 1493 and download. Binaries are still available. <thumbsup>

 

However, this fix was pulled because it doesn't work with Apple RAID, so beware.

 

Thanks!

 

best regards,

MAJ

[bbchucks]

fruitbat04,

Anyone should be able to roll back to r1493 with the latest script. Just show the log for Chameleon (3 L) and use arrow keys to get back to 1493 and download. Binaries are still available. <thumbsup>

 

However, this fix was pulled because it doesn't work with Apple RAID, so beware.

 

Thanks!

 

best regards,

MAJ

Why not just use Chimera as the bootloader? Chimera doesn't have that issue as i've mentioned before.

[L3B3R]

Why not just use Chimera as the bootloader? Chimera doesn't have that issue as i've mentioned before.

As I stated in my previous post I have tried Chimera but I still cannot log in. Maybe I will try the older Chameleon.

[BlueSky2000]

I'm having issues updating as well however I am not getting a KP. I have tried both new Chameleon and Chimera but have not had success. It seems like I am just not getting video support even though I am using the same EFI string as previous (nvidia 9800 gtx). Attached is the last lines I see in verbose before the screen goes blank. The PC stays on like it is running still so I am assuming it is just a graphics issue, but if someone sees errors in the screenshot please let me know. Also, is there a kext that is working in lion for nvidia cards?

 

 

Hi,

I have a 9800 GTX+ using GFX string. I had a same issue with you and I was finally able to fix it. This is how I fixed.

I changed from

<key>device_type</key>

<string>NVDA,Geforce</string>

 

to

 

<key>device_type</key>

<string>NVDA,Parent</string>

[aikidoka25]

Lucky and Unlucky you! Guess i gotta search the forums if 10.7.2 work with ATY kext and 4870.

 

I am using Sapphire 4870 and it works completely with just GraphicsEnabler = Yes

[tsunoo]

Hi,

I have a 9800 GTX+ using GFX string. I had a same issue with you and I was finally able to fix it. This is how I fixed.

I changed from

<key>device_type</key>

<string>NVDA,Geforce</string>

 

to

 

<key>device_type</key>

<string>NVDA,Parent</string>

 

GREAT. EXCELLENT! I've got now the perfect screen resolution (1600x1200 instead of default 1280x1024)

For information (for the others not for you) the DD Script doesn't know this key and it have to be inserted manually

 

my org.chameleon.boot.plist look like this now:

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">

<plist version="1.0">

<dict>

<key>EthernetBuiltIn</key>

<string>Yes</string>

<key>GUI</key>

<string>No</string>

<key>Graphics Mode</key>

<string>1280x1024x32</string>

<key>GraphicsEnabler</key>

<string>Yes</string>

<key>Kernel</key>

<string>mach_kernel</string>

<key>Kernel Flags</key>

<string>-v arch=i386</string>

<key>Timeout</key>

<string>1</string>

<key>device_type</key>

<string>NVDA,Parent</string>

</dict>

</plist>

[itdoesnotwork]

As requested, here is my complete Install log. It's quite long, but should contain the whole information. I hope you'll find your way through.

 

Concerning your question, it did not overwrite existing plists when choosing preserve option, but obviosly did not install the bootloader correctly either.

 

Further more, another problem occurred: Today I wanted to add sleepenabler and OSXRestart to Extra, but when I choose kext installer, it tells me that it can't proceed without an os installed.. ??? Volume is the correct one. See last few lines of the log..Install.log.zip

[bbchucks]

Sleep is working on 10.7.2 if you use the kext from the google.code URL.

[nabziF99]

Well this is strange. I downloaded the newest version of the script and happened to target my old 10.6.6 volume, at which time the script immediately and without warning began "updating boot caches for Snow Leopard". Oh {censored} I thought, I haven't even done anything yet and it already thinks something needs updating, this cannot be good.

After rebooting to a few kernel panics (and my own panics), I realized what the script had done: it had renamed com.apple.Boot.plist to org.chameleon.Boot.plist, which my existing bootloader (Chameleon v2.0-RC4) doesn't recognize.

Did I do something wrong, or is it the script's mission to wipe com.apple.boot.plist off of Hackintoshes everywhere, without first bothering to check for the existence of an older bootloader? I managed to rename the plist back to what it was and things seem to be back to normal...but I'm left with questions:

1. Was the filename the only change, or does the script go monkeying with the contents too when it converts old com.apple.Boot.plist?
   
2. Is there a way to avoid this with the current script, or must I choose between using an older script or update the bootloader (whether I want to or not)? Or maybe a way to get the older bootloader to use org.chameleon.Boot.plist?
   

Thank you for any suggestions!

[tsunoo]

Well this is strange. I downloaded the newest version of the script and happened to target my old 10.6.6 volume, at which time the script immediately and without warning began "updating boot caches for Snow Leopard". Oh {censored} I thought, I haven't even done anything yet and it already thinks something needs updating, this cannot be good.

After rebooting to a few kernel panics (and my own panics), I realized what the script had done: it had renamed com.apple.Boot.plist to org.chameleon.Boot.plist, which my existing bootloader (Chameleon v2.0-RC4) doesn't recognize.

Did I do something wrong, or is it the script's mission to wipe com.apple.boot.plist off of Hackintoshes everywhere, without first bothering to check for the existence of an older bootloader? I managed to rename the plist back to what it was and things seem to be back to normal...but I'm left with questions:

1. Was the filename the only change, or does the script go monkeying with the contents too when it converts old com.apple.Boot.plist?
   
2. Is there a way to avoid this with the current script, or must I choose between using an older script or update the bootloader (whether I want to or not)? Or maybe a way to get the older bootloader to use org.chameleon.Boot.plist?
   

Thank you for any suggestions!

 

well if you read about the history script in this group you had to learn that the script is only compliant with the new bootloader.

So upgrade the boot loader or use the old script.

[digital_dreamer]

nabziF99,

Ouch. Sorry for the trouble. I had not considered that someone would be using a earlier version of Chameleon, especially RC4, on my latest script. My intention is to provide the latest updates and compatibility with the latest releases. The script came installed with the latest Chameleon release at the time and was designed to work with those releases.

 

At present, each time the target volume is selected in the script, it will rename the boot plist for compatibility with the latest bootloaders.

The boot plist is the only file that is renamed. Nothing else is changed.

 

I'm assuming there is a valid reason RC4 is being used in your case. Would you explain why? Don't take me the wrong way, but I'm just curious. You got a right to use whatever you want. If I can get a valid reason for this, I'll code in a portion to check the revision number and skip the renaming, if it doesn't apply. This shouldn't be too difficult, as the check routines are mostly in place.

But, from my POV, it would be much easier to simply update the bootloader, than write some extra code for backward compatibility in some rare cases.

 

itdoesnotwork,

I'll look at the log. Thanks!

 

tsunoo,

That's cool that the device_type key can be added right in the boot plist as apposed to the EFI string!

Note that in a dual graphics card setup, you will have to change the EFI string. The GPU driving the main monitor should have NVDA,Parent and the secondary GPU should have NVDA,Child. It's also recommended that the following be removed from any GPU plist:

<key>name</key>
<string>NVDA,Parent</string>

 

best of wishes,

MAJ

[fruitbat04]

Why not just use Chimera as the bootloader? Chimera doesn't have that issue as i've mentioned before.

 

The latest Chimera KP's my system. Not an option in my case.

 

@DD yeah the binaries are available and it fixes the issue fine. Just thought you might want to include it as an option in the script

[everdone]

In playing around with different bootloaders and not really knowing which plist each one needs, I have both a org.chameleon and com.Apple Plist in the Extra folder. They are identical except for the name. The bootloader chooses the one it wants and ignores the other.

 

Once finished 'playing' one can discard the unused file.

 

I haven't found any solution to the iCloud login problem yet. Earlier chameleon bootloaders, Chimera and changing Smbios - nothing works. It's not a real problem as I don't plan on using iCloud, but I would like to make it work.

 

Upgrade to 10.7.2 went smoothly on all my machines. It was only necessary to reinstall the audio kext to get audio working after the update.

 

The ATI 5770 video card works (as well as NVidia 9500 cards) nicely using GraphicsEnabler=Yes with most all the newer bootloaders. I have tried other 5xxx and 4xxx cards with less success. The VGA port normally works but the DVI port doesn't, ie, no video at the desktop. One can set an AtiConfig to get the DVI port working but then the Apple DVD player will not work.

[fruitbat04]

In playing around with different bootloaders and not really knowing which plist each one needs, I have both a org.chameleon and com.Apple Plist in the Extra folder. They are identical except for the name. The bootloader chooses the one it wants and ignores the other.

 

Once finished 'playing' one can discard the unused file.

 

I haven't found any solution to the iCloud login problem yet. Earlier chameleon bootloaders, Chimera and changing Smbios - nothing works. It's not a real problem as I don't plan on using iCloud, but I would like to make it work.

 

Have you got a serial number in your smbios? As long as you've got that and use the earlier Chameleon or Chimera, it should work.

[digital_dreamer]

The latest Chimera KP's my system. Not an option in my case.

 

@DD yeah the binaries are available and it fixes the issue fine. Just thought you might want to include it as an option in the script

The Chimera bootloader is not currently an option in the script?? Should be.

 

In playing around with different bootloaders and not really knowing which plist each one needs, I have both a org.chameleon and com.Apple Plist in the Extra folder. They are identical except for the name. The bootloader chooses the one it wants and ignores the other.

 

Once finished 'playing' one can discard the unused file.

 

I haven't found any solution to the iCloud login problem yet. Earlier chameleon bootloaders, Chimera and changing Smbios - nothing works. It's not a real problem as I don't plan on using iCloud, but I would like to make it work.

 

Upgrade to 10.7.2 went smoothly on all my machines. It was only necessary to reinstall the audio kext to get audio working after the update.

 

The ATI 5770 video card works (as well as NVidia 9500 cards) nicely using GraphicsEnabler=Yes with most all the newer bootloaders. I have tried other 5xxx and 4xxx cards with less success. The VGA port normally works but the DVI port doesn't, ie, no video at the desktop. One can set an AtiConfig to get the DVI port working but then the Apple DVD player will not work.

The boot plist name change was in r1105 and the com.apple.Boot.plist is no longer used. Since it is only read by the bootloader, one can safely delete/remove/rename the com.apple.Boot.plist.

Oddly, although the Chameleon change log says it was "now depreciated and will not exist forever," implying it was still in use, I found no evidence that was the case - it wouldn't even attempt to read a com.apple.Boot.plist from that point onward. It didn't appear to look for a com.apple.Boot.plist, if the org.chameleon.Boot.plist was not present. So, I made sure the script changed the name from the old to the new, so that it would be read by the bootloader.

Unfortunately, this wasn't a "use the new if present or the old if not" situation. It was a "use the new or else it won't work" situation.

_____________

 

As a side note, I hadn't been able to get my MobileMe mail from Mail 5.1 for a few days since upgrading to 10.7.2, although it was accessible via web interface. The account would always go offline and the Incoming Mail Server field was always grayed out, even if I filled it in during setup. After setup, it would still be grayed out with the "mail.example.com" text and one could not replace it. A warning would always pop up saying, "The Incoming Mail Server field cannot be left blank."

 

I just installed Chimera 1.5.4, logged in to iCloud, transferred from MobileMe to iCloud and all is fine, now. It would have been nice if Apple would have just informed us MobileMe users that we had to take steps to transfer to iCloud for this to work. Originally, I wasn't convinced that moving to iCloud was the fix for my situation, but it was.

 

regards,

MAJ

[Lyle M]

Lyle M,

re: r1625

Got to be on that bleeding edge, eh?!

 

MAJ

I can't help myself. Worse, your script makes it even easier.

 

Cheers,

Lyle

[L3B3R]

EDIT:

 

For those with iCloud not working (don't know about Raid) make sure this is in your org.chameleon.Boot.plist:

 

<key>EthernetBuiltIn</key>

<string>Yes</string>

<key>PCIRootUID</key>

<string>1</string>

[rx7boy]

So is there a fix coming along for us Raid 0 users and iCloud? Maybe even built into the script?

 

Thanks

rx7boy

[jhrfc]

I have finally got 10.7.2 going, with proper graphics, iCloud, FaceTime etc all working.

Here's what I found.

 

10.7.2 did not like my efi strings for my graphics and ethernet interface, so I had to install the version of chameleon that fixed FaceTime login problems, then remove the efi strings from boot plist, and made sure all was working under 10.7.1.

I then installed the 10.7.2 combo update, and updated the caches using DDs script BEFORE rebooting.

I needed to re-apply the patches to enable TRIM support, and edit the AppleGraphicsPowerManagement kext to get back full GPU performance.

I also had terrible problems with Safari 5.1.1 crashing all the time, i deleted it from the unix shell and then downloaded a separate 5.1.1 installer from apple and re-installed, all now well.

 

Have now moved to iCloud from mobile me and all well between my hack, iPhone, and macbookpro.

 

Cheers

Jon

[digital_dreamer]

So is there a fix coming along for us Raid 0 users and iCloud? Maybe even built into the script?

 

Thanks

rx7boy

Unfortunately, this is still an unresolved issue. Either we have Apple RAID 0 working or iCloud working, not both. Chimera v.1.5.4 is supposed to incorporate a special flag (SkipFTFix=Yes) that permits RAID 0 boot at the expense of the FaceTime fix, which, I assume, is related to the iCloud issue. However, I haven't been able to get Chimera to work with RAID, period, as it has trouble locating the kernel. Haven't really spent much time on it, though.

 

regards,

MAJ

[rx7boy]

Unfortunately, this is still an unresolved issue. Either we have Apple RAID 0 working or iCloud working, not both. Chimera v.1.5.4 is supposed to incorporate a special flag (SkipFTFix=Yes) that permits RAID 0 boot at the expense of the FaceTime fix, which, I assume, is related to the iCloud issue. However, I haven't been able to get Chimera to work with RAID, period, as it has trouble locating the kernel. Haven't really spent much time on it, though.

 

regards,

MAJ

 

Hi MAJ

 

Yeah I guess we will just have to wait it out then, I have tried also to get Chimera to work and no luck so oh well, will just sit on this one for awhile. Thanks for letting me know that you have not been able to get it to work either.

 

rx7boy

[jc84]

Unfortunately, this is still an unresolved issue. Either we have Apple RAID 0 working or iCloud working, not both. Chimera v.1.5.4 is supposed to incorporate a special flag (SkipFTFix=Yes) that permits RAID 0 boot at the expense of the FaceTime fix, which, I assume, is related to the iCloud issue. However, I haven't been able to get Chimera to work with RAID, period, as it has trouble locating the kernel. Haven't really spent much time on it, though.

 

regards,

MAJ

 

 

Are we talking about booting from a RAID 0 drive?

As I am successfully running 10.7.2 with full iCloud support and a RAID 0; However it is NOT a Raid 0 Boot. I boot off a SSD drive. I use the RAID 0 for video editing..

[digital_dreamer]

Are we talking about booting from a RAID 0 drive?

As I am successfully running 10.7.2 with full iCloud support and a RAID 0; However it is NOT a Raid 0 Boot. I boot off a SSD drive. I use the RAID 0 for video editing..

I just meant for booting.

I have RAID 0 running, as well, and can boot into it w/Chameleon RC5. But, there isn't any iCloud support when booting into it. With Chimera v1.5.4, I'm not able to boot into it at all. It appears to keep looking into the OS "/Boot OS X/com.apple.boot.X" directory for the kernel. Now, I know the kernelcache is located there, but it shouldn't be looking there with the UseKernelCache=No flag. Plus, there's no sign it is attempting to boot with a kernelcache, as the boot process doesn't progress any further - no kexts are loaded from the cache.

 

Just so that everyone knows:

To boot into RAID via Chameleon RC5 with the kexts or boot cache in /Extra, you must explicitly tell the bootloader not to use the kernel cache via UseKernelCache=No flag. This is because, by default, Chameleon RC5 will try to boot from the kernelcache on a RAID volume and ignore your /Extra kexts or boot cache. The telltale symptom is a stalled boot, with no evidence any kexts in /Extra have loaded when looking at the boot log.

Now, if you put all your kexts in S/L/E and make sure the kernel cache is built, then you can boot with the UseKernelCache=Yes flag or omit the flag entirely.

 

kind regards,

MAJ