[GUIDE] Scripted Yosemite/Mavericks Install on Gigabyte Mobos

[LocusOfControl]

I installed a SATAIII card and OCZ SATAIII AgilityHD in my computer the other day which worked without any trouble

 

Then coincidently apple upgrade to 10.6.8 came along and I took the upgrade without thinking

 

Anyway on rebooting I kept getting the "still waiting for boot disk" error , tried usual things without success

 

On closer inspection the error was

 

PCI Configuration changed (bridge = 9 device = 11 cardbus = 0)

 

 

After a bit of nosing around it seems to be IOPCIFamily.kext changed

 

 

Anyway, the answer is 10.6.8 didn't like my DSDT.aml which is quite cut down and had been working for ages

 

Fix was to use the appropriate DSDT.aml from Dood's thread as a temp fix, but gone back to orange icons. - (I have a spare small OS X 10.6 HD for emergencies so could do this)

 

anyway back working now on 10.6.8, appstore and sound working OK, if you get a weird "still waiting for boot disk" error then check your dsdt.aml

[VirusX]

thank god I checked this thread first before updating to 10.6.8. I need a working install at the moment for the last pages of my bachelor-thesis

 

Since I am using Cruisar's DSDT install, I'll wait for him to respond here about his update. So, Cruisar....?

 

thanks

[Crna Brada]

The v6.0b installer will work with DP4, with the exception of copying over the kernel. This will have to be done manually.

However, the version I'm working on works fine. If you can wait a few days, I will release it soon. I'm currently trying to get it to create boot a DVD/ISO from the Lion installer. A lot of it is experimental. Plan to have it work with the DPX versions, for now. I'll put in a mod to work with the upcoming golden candidate release of Lion that comes off the App Store sometime later.

 

As far as RAID, yes, v6.0 will install Lion on RAID. I just did last night.

However, the Chameleon bootloader doesn't recognize the drives properly and you're not able to boot from it.

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

 

Just wondering if there are any news regarding booting Lion from RAID issue - you mentioned an easy fix in Chameleon would solve it.

 

Thanks for your help!

 

[digital_dreamer]

Just wondering if there are any news regarding booting Lion from RAID issue - you mentioned an easy fix in Chameleon would solve it.

 

Thanks for your help!

 

 

No news, yet. The Chameleon team is quite swamped for the moment.

However, just using the Combo boot cache update option works for me. Give it a go.

 

MAJ

[Crna Brada]

No news, yet. The Chameleon team is quite swamped for the moment.

However, just using the Combo boot cache update option works for me. Give it a go.

 

MAJ

 

Thanks MAJ!

 

I am using another trick that leaves RAID installation untouched. I installed Lion on a USB memory stick but "boot-uuid" in com.apple.Boot.plist on USB points to RAID!

It takes time to install Lion on USB and Chameleon startup from USB is slower for a couple of seconds but reward is that you do normal updates - no need for any special treatment and creation of Extension.mkext.

 

Talking about the boot time, I tried to put in com.apple.Boot.plist:

 

<key>UseKernelCache</key>

<string>Yes</string>

 

in a number of RAID or non-RAID working Lion configurations (DP2 - DP4). Consistently, as soon as I include this, I end-up with endless "wheel of death" with Apple's apple on top.

As soon as I remove it, everything gets back to normal and system boots properly!?

 

Any idea what I've been doing wrong so consistently for some two months and probably some twenty (re)installations of Lion on two MBs, GA-X58A-UD3R and GA-X58A-UD7, with some four versions of Chameleon?

 

Regards,

Crna Brada

[digital_dreamer]

Crna Brada,

 

RE: UseKernelCache

 

Are you installing the kexts into S/L/E? That's the only way the system is going to see the kexts and build that kernelcache, for now. Additionally, a kernelcache has to be in the S/L/C/c.a.k.c/Startup folder (and RAID helper partitions at c.a.b.X/S/L/C/etc.) for the system to even boot in that mode. I'm not sure it would boot without one.

 

Sometimes the system will not boot properly because the existing kernelcache does not contain the modified kexts. In these cases, it requires manually loading the kexts via kextload command. You probably have seen that mentioned in some threads.

 

So, it requires booting into Lion with the kexts in S/L/E. Then, the system will build a kernelcache based on the existing S/L/E installation (after a few seconds). After that a normal boot can be done with UseKernelCache.

 

Actually, Crna Brada, I haven't even tested this, yet. So, don't even know if the bootloader will work correctly using the kernelcache in RAID mode, if the kext cache issue on RAID is any indication.

 

best of wishes,

MAJ

 

P.S. I'll find out if the kernelcache method works in RAID after I get back from work tonight.

 

Okay, I just tried it and you're right. It doesn't work.

I installed all kexts into /System and added UseKernelCache=Yes key/string.

No dice. It comes up with the same KP we had when we tried a standard non-combo boot cache.

I still believe this is a Chameleon issue.

[Crna Brada]

Crna Brada,

 

RE: UseKernelCache

 

Are you installing the kexts into S/L/E? That's the only way the system is going to see the kexts and build that kernelcache, for now. Additionally, a kernelcache has to be in the S/L/C/c.a.k.c/Startup folder (and RAID helper partitions at c.a.b.X/S/L/C/etc.) for the system to even boot in that mode. I'm not sure it would boot without one.

 

Sometimes the system will not boot properly because the existing kernelcache does not contain the modified kexts. In these cases, it requires manually loading the kexts via kextload command. You probably have seen that mentioned in some threads.

 

So, it requires booting into Lion with the kexts in S/L/E. Then, the system will build a kernelcache based on the existing S/L/E installation (after a few seconds). After that a normal boot can be done with UseKernelCache.

 

Actually, Crna Brada, I haven't even tested this, yet. So, don't even know if the bootloader will work correctly using the kernelcache in RAID mode, if the kext cache issue on RAID is any indication.

 

best of wishes,

MAJ

 

P.S. I'll find out if the kernelcache method works in RAID after I get back from work tonight.

 

Okay, I just tried it and you're right. It doesn't work.

I installed all kexts into /System and added UseKernelCache=Yes key/string.

No dice. It comes up with the same KP we had when we tried a standard non-combo boot cache.

I still believe this is a Chameleon issue.

 

 

I am quite convinced you are right about Chameleon being a culprit in RAID KP case!

 

My interpretation of what is happening in the scenario that works reinforces validity of that assumption. Unfortunately I have to use the word 'assumption' here since the results of numerous tests point to that direction but I have to admit that they are not entirely conclusive.

 

So here is the more detailed description of my setup (on both UD3R and UD7 MB)

 

1. Lion installed on USB (or any other media) works - no RAID. Everything done by the book all OSx86 kexts on /E/E except for network Realtek.. kext which is in /SL/E. DSTD, symbios and boot.plist in /Extra.

2. Chameleon 'boot' is in / - root directory.

3. Creation of kernelcache initiated by "touch /S/L/E", after fixing ownership.

4. If redirection to RAID is dropped from boot.plist, system boots from USB (or whatever media Lion happens to be installed on) - fully functional!

 

Now very same installation is transferred to RAID:

 

4. mash_kernel + Chameleon 'boot' + '/Extra' are copied to Boot - s3 partition of every disk included in RAID.

5. After ownership of all kexts is revised to root (wheel:root), 'touch /RAID_HD/S/L/E' is used again to initiate kernel cache creation.

 

In case of SL, you would now set the default partition, boot from RAID directly, and everything would work perfectly! In Lion, however, that causes KP!

 

But if you boot from USB and set boot-uiid to point to RAID (RAID UIID), everything works perfectly!

 

Based on possibly biased opinion, tainted by your suggestion that Chameleon is at fault, my interpretation is that attempt to boot directly from RAID fails since Chameleon has an issue dealing with RAID. If booted from USB, however, Chameleon passes control to Darwin somewhere along the way. OS, that knows how to deal with RAID, and not Chameleon, then gets redirected to RAID and everything woks just fine.

 

Another interpretation, that just came to my mind while I was writing this, would be that there still might be a minor Lion problem with SW RAID. Booted through USB, the system goes through regular non-RAID procedure, passes all the checks, figures out that it can work with the platform etc, and then passes control to RAID who happily runs Lion. Going directly to RAID, some formal tests fail as the platform is not recognized properly and KP happens stating that platform is not supported while in reality Lion can work from RAID!? Unfortunately, I haven't heard of anybody who tested SW RAID on a genuine Mac. That test could help understand if Lion is at fault.

 

But let's forget RAID problem altogether for a moment now. The other issue that is bothering me happens without any RAID in the system. When I put Use KernelCache=Yes, perfectly functional non-RAID system (configured using steps 1 to 4 from above) never finishes boot sequence - ends up with endless rotating "wheel of death"!

I am quite puzzled what happens here. No RAID present in the system at all, still the system fails to boot! No KP however.

 

Thanks for help MAJ!

[ronsega]

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.

 

Finally had time to do a 10.6.8 (from 10.6.7) update on my backup hard drive. Only problem was audio as well and just replaced AppleHDA.kext from 10.6.7 back into /S/L/E after updating to 10.6.8 and so far seem to be working as expected.

 

10.6.8 apparently broke audio on some real macs as well https://discussions.apple.com/thread/3139275

[jhrfc]

Finally had time to do a 10.6.8 (from 10.6.7) update on my backup hard drive. Only problem was audio as well and just replaced AppleHDA.kext from 10.6.7 back into /S/L/E after updating to 10.6.8 and so far seem to be working as expected.

 

10.6.8 apparently broke audio on some real macs as well https://discussions.apple.com/thread/3139275

 

I also upgraded and had no audio, if fixed it by making DSDT changes as detailed by d00d to not need any third party kext for stereo only audio. (I was using ALC889a_v2.kext)

All works fine now.

Jon

[LocusOfControl]

For future posterity, In case anyone is wondering about SATA III and USB 3

 

I have an Asus card plugged in connected to an OCZ Sata Agility III HD running 10.6.8 on an old EX58 board

 

works fine booting from EFI but I had to install manually, DD script didn't work with this drive (error message, mount fail), I had to explicitly format the EFI partition manually (mount_hfs doesn't work) and do a full manual install followed by a carbon copy clone of my SL drive, I loaded boot1 to EFI following some annoying boot hangs (and remember re-formatting changes UUID string that goes in com.apple.boot.plist)

 

hope this helps someone

[ronsega]

I also upgraded and had no audio, if fixed it by making DSDT changes as detailed by d00d to not need any third party kext for stereo only audio. (I was using ALC889a_v2.kext)

All works fine now.

Jon

 

Just did this too and now have 2 less 3rd party kext, HDAEnabler.kext/LegacyHDA.kext removed!

[digital_dreamer]

For future posterity, In case anyone is wondering about SATA III and USB 3

 

I have an Asus card plugged in connected to an OCZ Sata Agility III HD running 10.6.8 on an old EX58 board

 

works fine booting from EFI but I had to install manually, DD script didn't work with this drive (error message, mount fail), I had to explicitly format the EFI partition manually (mount_hfs doesn't work) and do a full manual install followed by a carbon copy clone of my SL drive, I loaded boot1 to EFI following some annoying boot hangs (and remember re-formatting changes UUID string that goes in com.apple.boot.plist)

 

hope this helps someone

 

That's interesting to know.

Were you able to format via newfs_hfs command or something else?

 

I may have to put in some checks in the script to monitor this and resort to a working alternative.

How did you mount the EFI partition? Does mount /dev/diskXsX or diskutil mount /dev/diskXsX work?

 

And, was this only a problem with the EFI partition?

 

MAJ

[LocusOfControl]

That's interesting to know.

Were you able to format via newfs_hfs command or something else?

 

I may have to put in some checks in the script to monitor this and resort to a working alternative.

How did you mount the EFI partition? Does mount /dev/diskXsX or diskutil mount /dev/diskXsX work?

 

And, was this only a problem with the EFI partition?

 

MAJ

 

 

Hi MAJ

 

In the past I always preferred to do things manually so I knew what was happening

This time I wanted an easy life so I thought I'd just run your script, but it didn't work (i.e couldn't get it to boot, but the chameleon 2 installer didn't work either due to problem below)

 

I noticed that when I tried to do a manual mount_hfs I got the invalid argument message, (yes only EFI gave me trouble)

 

I searched this site for possible clues (which is why I always report my findings in case I forget in 2 years time ;-)

 

Turns out for this drive the EFI isn't formatted and you have to do it yourself manually

 

newfs_hfs -v EFI /dev/diskXsY

 

where X and Y are your disk/partition

 

I also found that I had to put boot1h in disk2s1 in my case

 

474 fdisk -f boot0 -u -y /dev/rdisk2

475 dd if=boot1h of=/dev/rdisk2s1

476 cp boot /volumes/lion

477 diskutil list

478 mkdir EFI

479 mount_hfs /dev/disk2s1 /volumes/efi

 

I was getting a hang with no error at BSD when I tried the documented dd if=boot1h of=/dev/rdiskXs2

(other errors around this area are the boot0 and boot1 hangs)

 

(also remember if you screw up and decide to reformat, you need to update the uuid string in boot.plist)

 

So now my boot and Extra is in the EFI

Make sure your DSDT is up to date and make sure that you have no unnecessary kexts in Extra otherwise you can get strange boot errors/hangs

 

I previously used carbon cloner to copy my System stuff across (don't forget mach_kernel)

 

The hard drive was the OCZ Agility 3 SATA III 2.5" 60GB Solid State Hard Drive (doesn't have mounting adapters inc)

The adapter card was the Asus 2 Port PCIe USB 3.0 / SATA III Adapter (has 2 free cables) The drive works the same when connected to the mobo or the Asus card

 

I now have a working 10.6.8 (and hopefully) Lion ready disk with OS and Applications on a sata III SSD (plus a couple of backups)

 

 

hope this helps

Steve

 

PS Mounting the EFI isn't possible until you format the EFI explicitly (I had used the graphical diskutility to format and partition previously)

[Crna Brada]

For future posterity, In case anyone is wondering about SATA III and USB 3

 

I have an Asus card plugged in connected to an OCZ Sata Agility III HD running 10.6.8 on an old EX58 board

 

works fine booting from EFI but I had to install manually, DD script didn't work with this drive (error message, mount fail), I had to explicitly format the EFI partition manually (mount_hfs doesn't work) and do a full manual install followed by a carbon copy clone of my SL drive, I loaded boot1 to EFI following some annoying boot hangs (and remember re-formatting changes UUID string that goes in com.apple.boot.plist)

 

hope this helps someone

 

Thanks for the info! I was just thinking about OCZ SATA 3 drives.

There is one thing I am not sure about from your messages. I understand that you managed to get it going running SL, but does it run at SATA 3 speed or in SATA 2 compatible mode?

 

Cheers

[seanmcgpa]

Tried using the combo updater to 10.6.8 and before reboot using the Hackinstaller update caches : immediate KP on reboot. Doh!

 

Should I restore my backup and try the normal software update to 10.6.8?

[LocusOfControl]

Thanks for the info! I was just thinking about OCZ SATA 3 drives.

There is one thing I am not sure about from your messages. I understand that you managed to get it going running SL, but does it run at SATA 3 speed or in SATA 2 compatible mode?

 

Cheers

 

I don't think it runs at SATA 3 yet, the Asus card came with Windows drivers but no Mac.

(any advice on how I could measure it?)

 

So I suspect we will have to wait till Lion for Sata 3 either natively or by 3rd party kext, but at least I'll be ready when available (likewise the same Asus card also supports USB 3)

[@ROBASEFR]

Tried using the combo updater to 10.6.8 and before reboot using the Hackinstaller update caches : immediate KP on reboot. Doh!

 

Should I restore my backup and try the normal software update to 10.6.8?

 

I used the combo updater 10.6.8 from my "Scratch" hdisk (10.6.4) to update my "work hdisk "(10.6.7) ;

Then install with Hackinstaller 5.54 script: bootloader CH2CR5 rev.841 and update /Extra

the Kext/cache on 10.6.8 hdisk.

Then reboot 10.6.8 hdisk with option -f

 

Good luck

[Crna Brada]

I don't think it runs at SATA 3 yet, the Asus card came with Windows drivers but no Mac.

(any advice on how I could measure it?)

 

So I suspect we will have to wait till Lion for Sata 3 either natively or by 3rd party kext, but at least I'll be ready when available (likewise the same Asus card also supports USB 3)

 

I guess it would be unlikely that it runs at SATA 3 speed under Mac OS and neither Asus nor OCZ advertise that.

I believe Xbench can measure disk speed.

[digital_dreamer]

Tried using the combo updater to 10.6.8 and before reboot using the Hackinstaller update caches : immediate KP on reboot. Doh!

 

Should I restore my backup and try the normal software update to 10.6.8?

 

Did you remove the SleepEnabler.kext, if installed?

If not, you can use pmVersion=Yes flag at boot to get in.

 

Rumor has it that using pmVersion=23 will get you in with this update. Can anyone confirm?

 

MAJ

[LocusOfControl]

I guess it would be unlikely that it runs at SATA 3 speed under Mac OS and neither Asus nor OCZ advertise that.

I believe Xbench can measure disk speed.

 

 

Ta, I'll give Xbench a go tonight

[LocusOfControl]

Ta, I'll give Xbench a go tonight

 

 

Here are two results run from my SL partition (which is running on a normal WD HD)

[seanmcgpa]

Thank you guys - I did get 10.6.8 finally installed after a harrowing few hours.

 

CPU temps on my Xeon 3520 are definitely running hotter : 10.6.7 they averaged 39 degrees C, in 10.6.8 they are averaging 47! Eeep!

[digital_dreamer]

Ah, pmVersion is 23 for 10.6.8

 

See the sources just released:

#define PM_DISPATCH_VERSION	23

MAJ

[Cosmin Petre]

Just wanted to add some info re: 10.6.8 on Cruisar Method

 

Tested on maintenance drive - agreed with earlier posters that 10.6.8 kills network.

 

kerneltask running at ~40% in activity monitor makes a lot of basic tasks beachball.

 

Anyone have any further info? Is is due to a change in Cruisar's DSDT?

[LocusOfControl]

What's wrong with your network?

 

Haven't noticed any increase in beach ball activity here, kernel_task currently at 0.4% to 1.5%

 

(I had 4 photography RAW editors open yesterday plus other stuff without issue, just opened 3 of them simultaneously and it stayed at 1.4%)

 

apart from the initial hiccup due to my old DSDT (which was a really cut down version so my fault) it seems OK