[GUIDE] Scripted Yosemite/Mavericks Install on Gigabyte Mobos

[Sidewinder33]

MAJ

I'm on pins and needles waiting for the new script, not that I need it to make any changes or setup modifications but just for seeing what other magic you've offered us in the form of an amazingly simple to use script.

 

I also had a question for you CruiSAr, does your setup support a higher blk speed? I want to turn my blk up to 200 but when I do I seem to loose apple power management booting verbose I dont see the turbo 1112 or the usual power management initialized lines.

 

Now a message to anyone does anyone know if there is a specific setup that is required to run the blk speed at 200?

[luh3417]

Has anyone had trouble with hot-swap hard disks? I insert a drive and it doesn't mount. Maybe, few of us use hot-swap. But if you have any tips about hot swap I am interested. Even if you use a different install (I am using CruiSAr method).

 

OK, inserting disk, no message in the log under Console. It does NOT show up under /dev/disk*. I'm sure I've got AHCI turned on. Strange.

 

Its hard to argue with CruiSAr's post above. And the last thing we want to do is annoy the trailblazers in this thread. I think the solution is to have a wiki. I tried setting that up here once but it didn't get much use. Anyway the fact is it takes less than 15 minutes to install with CruiSAr. You really need to 1. download the thread into a word file and search through it and 2. be willing (or get yourself a spare hard disk) to try things before begging for help. The fact that it works for everyone else means you have to figure out if you are doing anything different from the well worn path.

[dewby]

Ok so I really don't know where to post this question, I did a search and wasn't able to find any results. I am trying to decide between two mobo's and I think that newegg made the choice for me. The gigabyte ga-ex58-ud5 or the evga 141-bl-e757. I like the look of the evga more then the gigabyte but I can't find ANY hackintosh info about it. Is there a reason to use one over the other? Can I get away with using the evga as far as kexts are concerned? Any info will be hella appreciated.

[Gadensgaard]

Hi,

 

I am all new in this world of OSx86, however i succesfully managed to install SL on my DELL Latitude E6500 (it is back in Ubuntu however, since i couldnt get shutdown or graphics working).

 

So now i want to install SL on my Desktop, and i found all my hardware in the wiki to be supported (Hurray).

 

Unfortunately i have no access to a mac of any kind.

 

I have a retail SL DVD (original, no worries) my laptop (ubuntu) and my desktop (win 7).

 

Is it not possible to install manually with the charmeleon boot DVD as i did with my laptop, and then load all kexts and extras in afterwards?

 

If so, i would really appreciate aa quick step by step guide, i am all new in this EFI/kernel/kexts/extras/vanilla?

 

I have a GigaByte GA-EX68-UD5 with an Intel i7 CPU, and an NVidia GeForce GTX 285 GPU.

 

 

 

If you cant provide a guide for this particular hardware, could you at least point me in the direction of how to start creating a hackintosh with my hardware already purchased?

[luh3417]

Ok so I really don't know where to post this question, I did a search and wasn't able to find any results. I am trying to decide between two mobo's and I think that newegg made the choice for me. The gigabyte ga-ex58-ud5 or the evga 141-bl-e757. I like the look of the evga more then the gigabyte but I can't find ANY hackintosh info about it. Is there a reason to use one over the other? Can I get away with using the evga as far as kexts are concerned? Any info will be hella appreciated.

Particularly for newbies, it only makes sense to pick a well worn path. It depends a bit on how much free time and how much free money you have. Personally I end up using the more expensive board or trying a few different graphics cards, but its still a vast savings over a real Mac Pro, and faster and more flexible too.

[Sidewinder33]

Hi,

 

I am all new in this world of OSx86, however i succesfully managed to install SL on my DELL Latitude E6500 (it is back in Ubuntu however, since i couldnt get shutdown or graphics working).

 

So now i want to install SL on my Desktop, and i found all my hardware in the wiki to be supported (Hurray).

 

Unfortunately i have no access to a mac of any kind.

 

I have a retail SL DVD (original, no worries) my laptop (ubuntu) and my desktop (win 7).

 

Is it not possible to install manually with the charmeleon boot DVD as i did with my laptop, and then load all kexts and extras in afterwards?

 

If so, i would really appreciate aa quick step by step guide, i am all new in this EFI/kernel/kexts/extras/vanilla?

 

I have a GigaByte GA-EX68-UD5 with an Intel i7 CPU, and an NVidia GeForce GTX 285 GPU.

 

 

 

If you cant provide a guide for this particular hardware, could you at least point me in the direction of how to start creating a hackintosh with my hardware already purchased?

 

Hey Gadensgaard,

DD suggest using an easy to use distro like Kalyway to get osx up and running to start the process off if you don't have access to a mac. In the first post he has a little link where you can find more info on how and what to do to get that up and running. After that (or technically even including that) you should be able to follow DD's procedure to get SL up and running.

 

One thing, that happened to me during my install after it was all said and done I wasn't getting any video signal after moving through the bootloader. What I ended up needing to do was add a device property string to my boot.plist and everything worked perfectly. I'm only saying this as you have the same card and may experience a similar problem, not all do many people don't need to add the string and graphics enabler works flawlessly.

 

I'd just suggest really reading DD's procedure to make sure you understand what each step is trying to accomplish (took me awhile of reading it to finally get it all).

 

Hopefully that gets you started keep us posted.

[CruiSAr]

I also had a question for you CruiSAr, does your setup support a higher blk speed? I want to turn my blk up to 200 but when I do I seem to loose apple power management booting verbose I dont see the turbo 1112 or the usual power management initialized lines.

Yes my setup supports a higher BLCK, that is over 200. I have been able to run upto 4.2 Ghz using an overclocking template you can find in d00d's DSDT patching guide. Once you go above 200, certain stuff have to enabled and disabled and his template will walk you through it. Give it a shot and let me know how it goes.

[Sidewinder33]

Yes my setup supports a higher BLCK, that is over 200. I have been able to run upto 4.2 Ghz using an overclocking template you can find in d00d's DSDT patching guide. Once you go above 200, certain stuff have to enabled and disabled and his template will walk you through it. Give it a shot and let me know how it goes.

 

Worked like a champ, set up all the voltages d00d outlines and got it booting solid now, thanks for the direction CruiSAr

[CruiSAr]

Worked like a champ, set up all the voltages d00d outlines and got it booting solid now, thanks for the direction CruiSAr

No Worries, always glad to be of help.

[Gadensgaard]

Thanks i will give it a try.

[epitaphic]

I had posted earlier about a high frequency noise that comes out of the computer then I do certain things like flip through albums in iTune's coverflow.

 

After many, many BIOS config edits and reboots, I'm happy to report that the issue goes away when you change the CPU vcore from auto to the number displayed. In my case that's 1.29375. I did try with a lower number (1.23) and it also worked. C1E is off, haven't gotten around to testing with it on.

 

Hope it helps some of you guys also afflicted by this nuisance.

[digital_dreamer]

BETA RELEASE FOR RAID TESTING:

version 4.5b

• Full Apple RAID support for vanilla or custom kernels! Although you can install via RAID EFI partition, EFI boot requires the kernels be installed in the RAID helper partitions (at least, that was true in my case). If the kernel name is the standard vanilla name, "mach_kernel," it appears the system will boot the kernel installed by the OS installer (/Volumes/Boot OSX/com.apple.Boot.S/ or equiv.). However, if you change this name in the boot.plist, you can boot a custom kernel installed at root (/Volumes/Boot OSX/). I haven't been able to get a kernel recognized in the EFI partition, even with rd(0,0)/mach_kernel in the boot.plist. Don't know if this is a bootloader or OS limitation. In any case, the script will do the entire installation, which includes installing the kernels in the RAID helper partitions for EFI installs.)
  
• Updated script to include many recent bootloader updates:
  
  • PC-EFI v10.6
    
  • Chameleon 2.0 RC5 pre12 - rekursor mods
    
  • Chameleon 2.0 RC4 AsereBLN v1.1.9 - Asere mods
    

  [*] Rewrote the bootloader installer so that bootloaders can be easily added and recognized by dropping them into the /~extra/Bootloaders directory. Bootloaders can be removed from the script by simply removing the folder or removing the underscore prefix (_) in its folder name. For proper handling, the bootloader will need, at minimum, the boot, boot0, and boot1h files in a /i386 directory, along with a /Extra directory, if you wish to include a Themes folder, etc. If there are any questions, simply view the existing versions for answers.

  [*] Added a more robust test for failed bootloader installs, particularly for EFI install methods.

  [*] Added an additional method of formatting EFI partitions, if the initial formatting failed.

  [*] Updated the Single-User 'buildcache' script to properly update boot cache in EFI partition.

  [*] Improved handling of modified kexts containing Apple names (IONetworkingFamily.kext, AppleHDA.kext, etc.) after a Software Update is performed:

  • When installing modified kexts in S/L/E with Apple names, the originals are renamed (i.e. IONetworkingFamily.kext.original). The newly installed kexts, are then tagged (via Info.plist) and monitored by script. If the tag is missing during a future kext install, it is assumed the kext was replaced via Apple Software Update. This kext will now replace the current "original" file to reflect the latest update. This procedure will ensure that, upon a restore, the "original" kext is always the latest version supplied by Apple.
    

  [*] Improved parsing of kernel flags in plist editor.

  [*] Improved handling of kernel installation and restoration.

  [*] Implemented check to have script abort if there are over nine drives and/or partitions on the system, as the script will exhibit unpredictable behavior.

  [*] Updated iasl compiler version 2010_03_09 (March 9, 2010) for DSDT patcher.

DOWNLOAD: HackInstaller v4.5b

 

I'd like to hear from others regarding any bugs, quirks, etc. and particularly regarding RAID support.

I've removed kexts for Leopard and custom kernels to cut the size down on this download.

The bootCD and USB boot portion of the script is coded out for now, as I still have some work to do for EFI strings support.

 

best of wishes,

MAJ

[seanmcgpa]

Holy {censored}, digital_dreamer - you are the BEST!

[Windows04]

Mmm... I always had an installation based on only fakesmc/legacyHDA/orangefix kexts in extra and a patched DSDT, based on the instructions from the GA-EX58 DSDT power management topic in tutorials. With this, I can activate speedstep on this computer.

 

Now, when the script patches the DSDT (and I change nothing to it), the system boots with only these kexts and intelcpupowermanagement is loaded . I also see that the P-states are in the DSDT... But just to be sure, does the DSDT that the new beta script makes, support Speedstep + Turbo Boost?

[Sidewinder33]

Hey DD,

One thing i liked about the old installer that you seem to have removed from the beta.

 

Option 8 View efi partition, the new installer doesn't let me look at the raid member partitions any more, or mount the two partitions separately to make any mods manually if needed. The only reason I'm saying this is because it was in the old installer and thats actually how I got my raid up and running, plus its nice to see what needs to be where.

 

Good script for me so far still figurin stuff out with it

[knightprozac]

Hey DD.

 

Great work on the updated RAID version.

 

I decided to test it out with a fresh install since after playing around with things on my normal RAID I lost my sound output.

 

I've installed a /Extra on a Apple Software RAID 0 and it seems to work fine. When I was installing Exotic for 10.6.3 after doing my system update I had a crash. My boot.plist is being ignored for some reason. This may be related to the crash I had or something else I'm not sure yet. I've checked it manually and it's definitely there on both Boot OSX volumes but it doesn't seem to be recognised for some reason.

 

Anyway great job.

[Windows04]

Hi Digital_Dreamer,

 

So i've used your beta and it's very well-written (especially the RAID part, it just works like magic!), but there is one problem:

 

Why can you only build a normal cache on a RAID? When i create a normal cache, my system can't boot because it only loads, from some strange reason, the extensions cache from Extra. And because that cache only holds fakesmc/orangeiconfix/legacyhda.kext, my hard drive is not found.

 

Furthermore: I immediately get a kernel panic, saying that no ACPI device was found...

 

So it would be nice if we could create a super combo build cache in a RAID .

 

But on all the other parts, there is not a single complaint against this script .

[Dalgar]

Hey everyone. So I have been struggling with getting SL installed on my Core i7 and I need help.

I am not a experienced MAC user as I converted to mac back in Oct '09 from a PC to a mac mini. God I love that thing. I have

ga-ex58-ud5

nVidia 9400GT video

380GiB Sata drive

20x Sata DVD drive

Snow Leopard 10.6 Retail DVD

EmpireEFI 1085

 

Using EmpireEFI I was able to actually get the install running. Everything would go well until the very end and then INSTALL FAILED. When I attempt to boot the HD via the EmpireEFI boot disk, I get a CPU Halted and seems like kext.appleIO.... is failing to load.

 

I don't know where to go from here. I REALLY want to put Mac OSX on this beastie. It would be a shame to give it to Micro sloth.

 

So, any help would be wonderful.

 

Thanks guys.

[digital_dreamer]

Mmm... I always had an installation based on only fakesmc/legacyHDA/orangefix kexts in extra and a patched DSDT, based on the instructions from the GA-EX58 DSDT power management topic in tutorials. With this, I can activate speedstep on this computer.

 

Now, when the script patches the DSDT (and I change nothing to it), the system boots with only these kexts and intelcpupowermanagement is loaded . I also see that the P-states are in the DSDT... But just to be sure, does the DSDT that the new beta script makes, support Speedstep + Turbo Boost?

The script won't tamper with anything other than the CPU alias and RTC (CMOS reset) issues. It should leave your changes intact. But, I'd keep the original in a safe place, just in case.

 

Hey DD,

One thing i liked about the old installer that you seem to have removed from the beta.

 

Option 8 View efi partition, the new installer doesn't let me look at the raid member partitions any more, or mount the two partitions separately to make any mods manually if needed. The only reason I'm saying this is because it was in the old installer and thats actually how I got my raid up and running, plus its nice to see what needs to be where.

 

Good script for me so far still figurin stuff out with it

The view partitions portion is context sensitive. If you have RAID - Extra as your install target, you should be allowed to view the RAID helper partitions. On the other hand, if you have a EFI install target, it you allow to view those partitions. It should changes based on your install target.

 

Hi Digital_Dreamer,

 

So i've used your beta and it's very well-written (especially the RAID part, it just works like magic!), but there is one problem:

 

Why can you only build a normal cache on a RAID? When i create a normal cache, my system can't boot because it only loads, from some strange reason, the extensions cache from Extra. And because that cache only holds fakesmc/orangeiconfix/legacyhda.kext, my hard drive is not found.

 

Furthermore: I immediately get a kernel panic, saying that no ACPI device was found...

 

So it would be nice if we could create a super combo build cache in a RAID .

 

But on all the other parts, there is not a single complaint against this script .

I cut out the combo cache builds due to some concerns that the system may run out of drive space on the RAID partitions. When I had a mirrored RAID setup, I noticed I only had 15MB of free space on one of the RAID helper partitions. This included the copied over kernel and the typical support files installed by the OS installer. That's certainly not enough space for a "super" combo. But, a regular combo should work.

 

I can include those options back in, but with a warning. I'll play around with it and see what it actually does in that situation. Hopefully, a cache will not be created at all (if no space) and the script will revert to the previous cache and informs the user.

 

Only loading the kexts from /Extra is certainly a problem. Have you noticed that the boot-uuid kernel flag is present in the boot.plist? Does it read any other flags, like -v, if used?

 

I can release for you a modified version with the combos included.

 

MAJ

 

Hey DD.

 

Great work on the updated RAID version.

 

I decided to test it out with a fresh install since after playing around with things on my normal RAID I lost my sound output.

 

I've installed a /Extra on a Apple Software RAID 0 and it seems to work fine. When I was installing Exotic for 10.6.3 after doing my system update I had a crash. My boot.plist is being ignored for some reason. This may be related to the crash I had or something else I'm not sure yet. I've checked it manually and it's definitely there on both Boot OSX volumes but it doesn't seem to be recognised for some reason.

 

Anyway great job.

Are you talking about the QE_CI for Exotic cards?

 

Make sure you are actually booting from the RAID slices in the BIOS drive selector (F12). If you have another OS install that has loading priority in the BIOS, the bootloader is going to load only those kexts and boot.plist, even if you select and boot the RAID drive in the bootloader screen.

 

You probably already know this, but just in case, and for the benefit of others that may not know.

Here's my conclusion of what's going on based on how the BIOS and the bootloader functions:

 

1. The BIOS is going to read the first drive in the drive sequence, based on the BIOS drive priority settings (all configurable).

2. From there, it will attempt to load a bootloader on the active partition, wherever that is. The "active" partition tells the BIOS THIS is the partition that contains the bootloader and we want to boot from it.

3. Here's the important part: The chameleon bootloader will always load the boot.plist and kexts from that active partition, regardless of whether you decide to select a different bootable OS X install from another drive/partition.

 

As an example, if one were to have OS X 10.6.0 on the first bootable drive (BIOS wise), then were to select a 10.6.3 install from a different drive in the bootloader screen, you will experience a KP and some boot failure due to the fact that the 10.6.0 kexts in /Extra were already loaded from the first bootable drive (or drive selected from BIOS). In other words, although the bootloader screen may show several OS X installs to choose from (installed on different drives), only the kexts and boot.plist from the first bootable drive (or drive selected from BIOS) are used during the actual boot.

 

So, if one wished to boot a different install (different from the first bootable install), he would need to use the BIOS drive selector (F12), to explicitly boot from that particular drive, thus guaranteeing that the proper kexts for that install are loaded.

 

This scenario is the root cause of a lot of misunderstandings and booting issues.

Some may wonder why the Chameleon bootloader insists on only loading the boot.plist and kexts from the drive selected from the BIOS. Well, that feature is what makes preboot CDs possible. You can load a preboot_CD with its kexts and support files, eject it, and then boot a Retail OS X Install disk. And, all through the booting process those kexts are still loaded, in spite of the fact you may be running a different OS install.

 

Hope that helps.

MAJ

[Windows04]

I cut out the combo cache builds due to some concerns that the system may run out of drive space on the RAID partitions. When I had a mirrored RAID setup, I noticed I only had 15MB of free space on one of the RAID helper partitions. This included the copied over kernel and the typical support files installed by the OS installer. That's certainly not enough space for a "super" combo. But, a regular combo should work.

 

I can include those options back in, but with a warning. I'll play around with it and see what it actually does in that situation. Hopefully, a cache will not be created at all (if no space) and the script will revert to the previous cache and informs the user.

 

Only loading the kexts from /Extra is certainly a problem. Have you noticed that the boot-uuid kernel flag is present in the boot.plist? Does it read any other flags, like -v, if used?

 

I can release for you a modified version with the combos included.

 

MAJ

 

Well, i made a super combo build cache using your previous script and just copied it over to the raid helper partitions and it works just fine . What you do need to do is REPLACE the extensions.mkext, because for some odd reason, when you delete something on a raid helper partition, the space can't be reused (don't know why that is :s). But no problems here when I do that, typing this from my raid install with everything working . Ofcourse it could be a little bit easier if i just had a "one-button-option" to do that instead of making it in another version of the script and copying it over . Don't know however how the script will react if it wants to replace extensions.mkext... When you copy it in Finder, it gives you an error (not enough available space) but when you click ok, it just copies over...

 

But you can give me a modified version and I will play around with it . Just know that there is enough place on the helper partition for an extensions.mkext from around 35,5 mb size...

 

Yeah, it's weird that I have that problem with the kernel panic, always have had it since the day I installed Mac OS X on a striped RAID... I used -v arch=x86_64 as kernel flags, but even when I delete them or replace them, the error remains... I do use an extensively patched DSDT with only 3 kexts as my install method, maybe it has something to do with that... I could try to boot with a normal "kext install"...

 

The boot-uuid is inserted correctly (otherwise i couldn't boot at all even with a "big" extensions.mkext...).

 

About the DSDT: do you know an utility that can test if speedstep/turbo boost is enabled? The problem is that I can't use MSR-Tools because it gives me a kernel panic at boot :s...

[Sidewinder33]

The view partitions portion is context sensitive. If you have RAID - Extra as your install target, you should be allowed to view the RAID helper partitions. On the other hand, if you have a EFI install target, it you allow to view those partitions. It should changes based on your install target.

 

Weird now it is letting me view them, must have selected the wrong drive.

 

Although I haven't used the script to actually setup my Raid I see now how much easier it would be to setup with all the new little tweaks, very nice work as always DD.

 

I'm almost torn just to reset the RAID just to se all the files your installer uses and puts into place vs the manual method I have, heck I may have a bunch of extra stuff I don't need in the helper partitions.

[digital_dreamer]

DOWNLOAD: HackInstaller v4.5b1 shell script

 

• Returned combo cache builds for RAID and improved handling of failed boot cache builds due to lack of storage space, as may happen on RAID partitions when a large "Super Combo" cache build is executed.

This is just the shell script, which replaces the previous one. Goes in /~extra/Resources.

 

Question for some of you RAID users out there:

I'm trying to figure out which RAID helper partition is generally chosen for the support files (/com.apple.Boot.S/ and /System) by the OS installer. I'm assuming, based on my experience, that the OS installer picks the last helper partition for this role, which would be at #1 (disk3s2) as indicated below from 'diskutil listRAID'

 

-------------------------------------------------------------------------------
#   Device Node	   UUID								   Status
-------------------------------------------------------------------------------
0   disk4s2		   C1FE847C-AAA2-43A6-8D0D-8C1B0AD5E607   Online
1   disk3s2		   C8920A62-0AF5-466D-B5B4-3798DFAF7268   Online
===============================================================================

 

Note that disk3s2 is actually the RAID slice, but disk3s3 (not shown above) is the helper partition. Anyhow, it would still be drive 3, or the last drive on the RAID list. Is that the case for all of you?

Here's my 'diskutil list' output:

(The last helper partition is disk3s3 or "Boot_1")

 

/dev/disk0
  #:					   TYPE NAME					SIZE	   IDENTIFIER
  0:	  GUID_partition_scheme						*640.1 GB   disk0
  1:				  Apple_HFS EFI					 209.7 MB   disk0s1
  2:				  Apple_HFS Doctor_Mac			  20.0 GB	disk0s2
  3:				  Apple_HFS Time Machine			619.7 GB   disk0s3
/dev/disk1
  #:					   TYPE NAME					SIZE	   IDENTIFIER
  0:	  GUID_partition_scheme						*1.0 TB	 disk1
  1:						EFI						 209.7 MB   disk1s1
  2:				  Apple_HFS Macalem_i7			  999.9 GB   disk1s2
/dev/disk2
  #:					   TYPE NAME					SIZE	   IDENTIFIER
  0:	 FDisk_partition_scheme						*250.1 GB   disk2
  1:			   Windows_NTFS WIN_7				  250.1 GB   disk2s1
/dev/disk3
  #:					   TYPE NAME					SIZE	   IDENTIFIER
  0:	  GUID_partition_scheme						*500.1 GB   disk3
  1:				 Apple_Free						 209.7 MB   disk3s1
  2:				 Apple_RAID						 499.8 GB   disk3s2
  3:				 Apple_Boot Boot_2				  134.2 MB   disk3s3
/dev/disk4
  #:					   TYPE NAME					SIZE	   IDENTIFIER
  0:	  GUID_partition_scheme						*1.0 TB	 disk4
  1:				 Apple_Free						 209.7 MB   disk4s1
  2:				 Apple_RAID						 999.9 GB   disk4s2
  3:				 Apple_Boot Boot_1				  134.2 MB   disk4s3
/dev/disk5
  #:					   TYPE NAME					SIZE	   IDENTIFIER
  0:				  Apple_HFS MacRAID				*999.5 GB   disk5

 

So, again, my question is do you guys have the support files (assuming you did a install, not a clone) at this last RAID drive identifier?

 

My reasons are that I'm trying to make sure I don't run into issues where the script is copying the files from one RAID helper to another and runs out of space. The script always works from the last RAID helper partition first, then does a copy to the others. So, if the OS support files are always on this last partition, the one the script works from and the one that likely to run out of space, then my file copy checks would be okay. But, if that's not the case, the script may build everything just fine on the working partition, but copies to the other partitions may fail if it runs out of space there instead.

Hope that makes sense.

 

regards,

MAJ

[knightprozac]

Are you talking about the QE_CI for Exotic cards?

Yes

Make sure you are actually booting from the RAID slices in the BIOS drive selector (F12). If you have another OS install that has loading priority in the BIOS, the bootloader is going to load only those kexts and boot.plist, even if you select and boot the RAID drive in the bootloader screen.

Yep. I'm switching my boot disks through the the bios (Running F13b). Something is definitely going on. I did a fresh install and still had the same problem after installing 10.6.3 and the exotic pkg. I tried reinstalling the bootloader (PCEFI 10.6) selecting no for preserving current files but it didn't fix the problem. I'm going to attempt to install the bootloader after doing my OS install and updates to see if this works, although this might be worrying for me to perform future updates.

As an example, if one were to have OS X 10.6.0 on the first bootable drive (BIOS wise), then were to select a 10.6.3 install from a different drive in the bootloader screen, you will experience a KP and some boot failure due to the fact that the 10.6.0 kexts in /Extra were already loaded from the first bootable drive (or drive selected from BIOS). In other words, although the bootloader screen may show several OS X installs to choose from (installed on different drives), only the kexts and boot.plist from the first bootable drive (or drive selected from BIOS) are used during the actual boot.

If i set my first bootable drive (in Bios) to my RAID but then choose my Non-RAID backup drive in the bootloader then my machine will boot and use all of the user settings and setup from my RAID drive. I'm running 10.6.3 on both of these with the same kexts. This isn't optimal for me as I always like to have to completely independant bootable volumes to allow me to fix any problems that might come up.

 

I will report back on any progress.

[knightprozac]

Looks like I've been barking up the wrong tree. My boot.plist is being recognised after all. It's only the Countdown Timer that isn't being recognised.

[CruiSAr]

Thumbs up on the new script DD, just used it to install SL on a buddy's machine. I am really being tempted to wipe my raid and test the script...hehehe.

 

Regards

Charles