Many have expressed a desire to have the Retail DVD Install and Boot from EFI Partition Retail DVD Install tutorials moved from the growing Upcoming Intel X58 Mobos & Core i7 CPUs thread to this Tutorials forum for easy access. They have been getting buried in the numerous posts and hard to monitor for updates. Many, perhaps, don't know they were even there.

This Retail DVD Install thread is divided into two parts:
1. DIGITAL_DREAMER'S STANDARD RETAIL DVD INSTALL (included in this post)
The introduction of Mac OS 10.5.7 has simplified a number of things for us Core i7 users. We not longer need to concern ourselves with the kernel and supporting System.kext, as the vanilla version is finely tuned for our systems.
This portion will begin by outlining the basic steps performed for the install and what kexts are needed. This method entails installing your Mac OS X Retail DVD and a small bootloader (Chameleon 2.0 RC1 or the older Chameleon v1012 with the Voodoo-based 9.6.0 kernel). I prefer the Retail DVD install method over the common distros from a legal point of view, as it allows one to purchase a current OS X Retail DVD and, therefore, support Apple. This is a full vanilla install with a handful of modified kexts that are added to a special folder (/Extra/Stored_Kexts) for full functionality. This setup now supports full Apple Software Updates without issues. An added bonus is a fully-featured script that provides a comprehensive set of options and features, such as:

� Installing the new Chameleon v2.0 RC1 or older Chameleon v1012 bootloader �
� Set partition as active � Run OS X installer � Install modified kexts � Update boot caches �
� Run DSDT patcher � Modify Mac model name � Modify processor info � Modify "About This Mac" graphics �
� Select various bootloader themes � Choose from a selection of 27 boot pictures �
� Powerful plist editor that allows you to edit any boot.plist or smbios.plist in various locations �
� Plist editor allows you to select from a list of useful keys, create a custom key, or modify kernel flags �
� Automatically add a UUID as a kernel flag from any of your installed drives �

2. WOLFIENUKE'S BOOT FROM EFI PARTITION RETAIL DVD INSTALL (see next post)
The Boot from EFI partition method is a slightly different method in that the modified kexts are copied to a hidden partition (EFI), leaving your boot drive untouched with no visible evidence of patches. This method also allows you to run Apple's Software Update without any problems. The walk-through script, written by wolfienuke, is fast and allows you to simply answer a few options and confirm your choices. Although the script runs in the Terminal, no Terminal background is necessary.

STANDARD RETAIL DVD INSTALL:
UPDATE: 7/5/2009

• Minor script update to 3.91 - removed a misleading EFI setup option. Script does not support EFI partition boot, yet. The next update will.

UPDATE: 6/25/2009

• Script version 3.9 is released.
• Added multi-language support for changing "About This Mac" processor info.
  

  � This feature utilizes the Preferred Languages as indicated in System Preferences/International/Language.
  � Starting at the first preferred language, the script will look for the proper Systeminfo.strings file for that language and set your processor info for that language.
  � If the script finds the language, it will check if the processor info is "Unknown" in that particular language and, if so, change the info based on the hardware gather data.
  � Although there are over 130 languages to install for OS X, there are only 18 languages that come with the corresponding SystemInfo.strings files.
  � If you are using a language that does not include a appropriate SystemInfo.strings file to modify, the script will skip to the next preferred language on the list until it finds one.
  � The 18 default languages are as follows: English, Japanese, French, German, Spanish, Italian, Brazilian Portuguese, European Portuguese, Dutch, Swedish, Norwegian, Danish, Finnish, Russian, Polish, Traditional Chinese, Simplified Chinese, and Korean.

• Added Time Machine Restore From Backup feature. Requires Retail DVD.
• Added EFI-string.txt file in /Plist folder for importing device-properties string into boot.plist.
• Changed DSDT.aml file handling so that it gets copied to root directory of boot volume for Chameleon 1012 install in preparation for Snow Leopard.
• Fixed various minor bugs in plist editor.

UPDATE: 6/18/2009

• Script version 3.8 is released.
• Fixed a serious file permissions bug affecting the bootloader.
• Added ability to copy kernels with .voodoo or other extensions. The "mach_kernel" suffix must be maintained, however, for proper script operation.
• Added ability to restore original kernel and system.kext.
• Added ability to unpack and examine contents of current mkext file.
• When installing a kernel and matching System.kext, the System.kext will install into S/L/E by default.
• Fixed a bug so that the System.kext in the _For_System folder will be preserved when that kext is removed from Script's Kernels folder.
• Added the new Voodoo2 alpha3 9.7.0 kernel.

UPDATE: 5/30/2009

• Script version 3.7 is released.
• Fine-tuned the handling of kexts in /Stored_Kexts folder and, if present, the /_For_System folder.
• You can now edit the smbios.plist in the Plist editor.
• Added "Universal" graphics injector, ATY_Init.kext.

UPDATE: 5/16/2009

• Script version 3.6 is released.
• Script includes option to install individual kexts into S/L/E, instead of /Extra/Stored_Kexts. Script keeps track of what's installed into S/L/E and, with a simple selection, they can be restored back to /Extra.
• You have the option to include a "_For_System" folder inside /Extra/Stored_Kexts. This folder offers the following features:
  

  � Any kexts dragged into this folder will get installed into S/L/E via "Update boot caches" script routine. Script will also use this folder if it's present for the "Kext/kernel installer" routine.
  � Kexts removed from this folder or transfered to /Extra will be deleted from S/L/E after the "Update boot caches" script routine.
  � For the curious and concerned, original kexts with equivalent names in S/L/E are not replaced, but renamed with ".original" tacked on the filename. Other installed kexts get a duplicate file with ".duplicate" added to filename for script to keep track of.

• The "_to_install" folders have been removed from the Kexts directory to help clean it up. Kexts simply need to be outside their "_repository" folders.
• Natit.kext updated
• VoodooHDA v0.2.2 audio kext and prefPane are included for those who wish to use it. This is an Open Source audio driver for our boards.
• Reworked the DSDT routine. Hopefully, the patch will enable all cores without any additional modifications on ASUS and similar boards.

UPDATE: 5/10/2009

• Script version 3.5 is released.
• The LAN driver (RTLR1000) was missing from the IONetworkingFamily.kext that was uploaded a couple hours ago. Now included. One of the pitfalls of doing lots of tests...but also the advantage of doing more tests is finding the culprit.
• A LegacyJMicronATASATAIDE.kext has been added for IDE or PATA support. This replaces the original LegacyAppleIntelPIIXATA.kext.
• Added logging to installer script. You can now view Installer or DSDT log, or copy logs to desktop for transport.
• Script now sets boot file and kernel files as invisible, leaving less clutter in your root folder.
• Script now deletes all the previous kexts in the Stored_Kexts directory prior to installing from the script repositories. This is a more reliable method, as otherwise a stray or modified kext may remain and be included in the new install.

UPDATE: 5/7/2009

• Script version 3.4 is released.
• Bug fix in boot cache updater. If you're having trouble updating the boot cache, this update will fix that issue.

UPDATE: 5/3/2009

• Version 3.3 is out. All kexts are gathered from their various locations in the script's directories and copied to Stored_Kexts in /Extra. From there a boot cache is automatically created to boot from.
• This Stored_Kexts folder is simply a repository and does not contain the live kexts the system is actually booting from. It's the boot cache created from these stored kexts that boot the system. That being so, the script changes the permissions of the Stored_Kext folder to a user editable stage, so you can delete/add other kexts at will. After having done that, you can simply select Update boot cache from the script to update the boot cache (mkext) file and be ready for reboot.
• Support is now added for the new MacPro4,1 Model Identifier. If you have your system setup to use this Identifier, whether by a kernel flag in Chameleon v1012 or via smbios.plist in Chameleon 2.0 RC1, the script will add this new key and allow you to provide a custom Model Name.

UPDATE: 5/2/2009

• Script has been updated to include the older Chameleon v1012 bootloader for those who wish to use something more stable. If you wish to revert from Chameleon 2.0 RC1 to the older v1012, simply installing/overwriting the newer bootloader (pre-patch) may create serious issues, leading to a unmountable partition. It's recommended to do a backup, erase, install, and restore. This older bootloader still uses the /Extra directory, but does not includes Themes or a boot.plist. Rather, the boot.plist is in it's conventional location. The script automatically copies the boot.plist to the proper location, depending on the bootloader in use.
• IMPORTANT: Those wishing to use the older bootloader (any older version, actually), will need to use the Voodoo-based 9.6.0 kernel and include the busratio=20 kernel flag in the boot.plist if they want to avoid the system clock speed-up issue, until a future time this issue is resolved.
• Regardless of bootloader in use, the kernel's matching System.kext is copied to S/L/E, with the original renamed, thereby improving system behavior. This action makes this kext the only file copied into the vanilla OS install. No longer the case, as everything is in /Extra.
• The Natit.kext has been updated.

(All previous updates are included in script's change log.)

DOWNLOADS:
Gigabyte GA-EX58-UD5 motherboard kexts NEW!
(10MB) - kernels included: Vanilla 9.7.0 (for Mac OS 10.5.6), Voodoo2 alpha3 9.7.0, and Voodoo-based 9.6.0 (older bootloaders).
X58 Mobo Patch Installer UPDATED! - 7/5/2009 v3.91
(21.8MB) - kernels included: Vanilla 9.7.0 (for Mac OS 10.5.6), Voodoo2 alpha3 9.7.0, and Voodoo-based 9.6.0 (older bootloaders).
Selection of 27 boot pictures EXTRA
(26.6MB) - for use with the X58 Mobo Patch Installer.

All that's really needed to boot into OS X 10.5.7 on this board is the Disabler.kext and dsmos.kext. That's it. Everything else are little fixes for hardware reporting, updated device IDs, audio, LAN, etc. In my case, I also needed the Natit.kext for ATI graphic card support, as without it I just got video corruption and couldn't see the desktop.

One important issue to keep in mind when installing kexts manually is that non-Apple kexts, like dsmos.kext, and injectors, like HDAEnabler.kext, Natit.kext, etc. are not installed with permissions data regarding them. So, Repairing Permissions via Disk Utility or Terminal will do absolutely nothing in fixing them. With the exception of commercial software that come with their own installers, only Apple-supplied OS software will get their permissions repaired. So, if you are installing manually, be absolutely sure the permissions and ownership information are correct for these non-Apple kexts or your system won't boot. Use the Terminal to do a "sudo chmod -R 755" and "sudo chown -R root:wheel" to the file.

After performing a Retail Mac OS X Leopard DVD install, our script, used in the X58 Mobo Patch Installer mentioned later in this thread, will be performing the following basic steps for this board. If you desire to perform the kext install manually, these are the steps you would want to accomplish for fully operational subsystems. The following assumes you are using a Chameleon bootloader that supports the /Extra directory:

BASIC RUNDOWN:
Install Mac OS X Leopard Retail DVD and combo updater, if needed.

Install kernel and supporting files: Mostly needed if using the older bootloaders (i.e. Chameleon v1012).

• Vanilla 9.7.0 kernel Included as part of the 10.5.7 install.
  If using the older bootloader, you must install the Voodoo-based 9.6.0 kernel (included), instead.
• Matching System.kext in /Extra/Stored_Kexts Included as part of the 10.5.7 install.
• com.apple.boot.plist in /Extra. This is necessary with the new Chameleon 2.0 bootloader.

Install updated/modified kexts in /Extra/Stored_Kexts on your boot drive:

• LegacyHDAController.kext
  (pre-patched for the ALC889a chipset)
• LegacyHDAPlatformDriver.kext
  (pre-patched for the ALC889a chipset)
• HDAEnabler.kext
  (goes with the included HDA kext above)
• LegacyJMicronATASATAIDE.kext
  (support for ATA devices on JMicron controller with over 4GB RAM fix)
• LegacyJMicronJMB36xSATA.kext
  (JMicron SATA suppport with over 4GB RAM fix)
• LegacyIOAHCIBlockStorage.kext
  (display drives as "internal" fix. NOTE: If you have removable drives, this kext should not be used.)
• LegacyAppleAHCIPort.kext
  (no longer needed with native Intel ICH10R support in 10.5.7.)
• IONetworkingFamily.kext
  (on-board LAN support from Psystar's version (1.8.1) of the Realtek R1000 driver and support for Time Machine)
• ATY_Init.kext
  (Universal graphics card injector, with support for the ATI Radeon 2x00, 3x00, 4870, 4850, plus NVIDIA cards.)
• Disabler.kext
  (disabler for AppleIntelCPUPowerManagement.kext and others - ABSOLUTELY NECESSARY TO BOOT!)
• dsmos.kext
  (page decryption EFI module - ABSOLUTELY NECESSARY TO BOOT!)

Repair permissions:
chmod -R 755 "/Volumes/YOUR_BOOT_DRIVE/Extra/Stored_Kexts/"
chown -R root:wheel "/Volumes/YOUR_BOOT_DRIVE/Extra/Stored_Kexts/"

Update boot cache:
mv "/Volumes/YOUR_BOOT_DRIVE/Extra/Extensions.mkext" "/Volumes/YOUR_BOOT_DRIVE/Extra/Extensions.mkext.previous"
kextcache -a i386 -m "/Volumes/YOUR_BOOT_DRIVE/Extra/Extensions.mkext" "/Volumes/YOUR_BOOT_DRIVE/Extra/Stored_Kexts"

DONE!

NOTES:

• My installer/patcher does not come with graphics card drivers. The included injectors (Natit.kext, NVinject.kext, and NVkush.kext) can only extract the graphics card hardware info for the OS to use, and they can take the place of EFI strings. So, if you have a graphics card that is not currently supported in the vanilla OS X install, you are still responsible for installing those drivers, as well as EFI strings, if you choose not to use the injectors.

USING THE SCRIPT:
INSTALLING OS X LEOPARD RETAIL DVD AND BOOTLOADER:
Download X58 Mobo Patch Installer (21.8MB without boot pictures)
These files include the Chameleon v2.0 RC1 and v1012 bootloaders, kexts, vanilla 9.7.0 kernel (for those still on Mac OS X 10.5.6), Voodoo-based 9.6.0 kernel (for those using an older bootloader), com.apple.boot.plist, and patch/installer script. Some have asked for a Boot-132 image, such as created from the Slimbuild CD Creator. The problem is that it works best when you include the UUID of your Install DVD in the boot.plist, which I wouldn't know first hand. I can still make it available, but don't know how successful it may be, as not even I can get it to work reliably.

INSTRUCTIONS:
Much credit and many thanks go to LTL, dfe (David Eliott), Kabyl, Munky, Turbo, Dense, zef and many, many other talented individuals that make these projects possible. The following is the basic objective:

PREPARATION

1. It is ideal to have two physical drives (not two partitions on the same drive) or, at least, another Mac system to work from.
2. One drive must already have OS X installed and running.
   This may mean using another Mac or installing a easy-to-use distro like Kalyway on the smaller/slower drive. (I only mention Kalyway, because it is the only distro I'm familiar with and know works well with this board. There may be more recent distros that can achieve equal success.)
3. Partition your target drive in Disk Utility using the GUID Partition Table (in Options button).
4. Make an ISO of your Retail DVD and download the Combo update, if needed.
   (The ISO of your DVD is not really needed, but it will shorten your install times dramatically. Trust me, when things go wrong (and they will) and you have to do an emergency install, more time spent waiting is directly proportional to higher blood pressure.)

RUNNING THE SCRIPT

1. Double-click RUN-PATCHER and enter your password.
2. You will be prompted with a selection of valid HFS drives to work with.
3. Default choices are highlighted in bold type.
4. Confirmed target drive name is saved for future use.
5. Install your choice of bootloader or pre-patch (option #2).
6. An option is provided to set target partition as active (option #3). The activate drive feature works with user to unmount all drive partitions (this is necessary for activation), including listing open files/running processes that prevent them from unmounting.
7. The script will check for the presence of a mounted "Mac OS X Install DVD" (or ISO) and prompt you if you wish to run that installer (option #4). Install from your Retail DVD and, immediately following that, the lastest combo updater. (There is NO need to boot into your new install first, before installing the combo updater.)
8. Run the kext/kernel installer (option #5). This is preconfigured to install the required kexts for the Gigabyte EX58-UD5 motherboard, or any motherboard with the same chipsets. The kext/kernel installer automatically updates the boot caches for you.
9. Run the DSDT patcher (option #7) and the patched DSDT file will be installed in the appropriate location.
10. Your system is ready for reboot!
11. After booting into your system, you have the option to change your Mac model name (option #9), CPU type (option #10), custom About This Mac graphic (option #11), as well as custom boot picture (option #13), bootloader theme (option #12), and boot plist (option #8).
12. The script's folders has basically 5 categories for the kexts - ATA, Audio, Graphics, Networking, and Misc. Patches. There is a _repository folder in each to store your collection of files. Kexts outside this _repository folder will get installed by the kext/kernel installer.
13. After your initial install, you can continue to use the script folders (ATA, Audio, Graphics, Networking, and Misc. Patches) to install kexts or you can simply drag and drop kexts in the /Extra/Store_Kexts (and _For_System folder, if included) and run the script's Update boot caches.
14. If you create a _For_System folder inside /Extra/Stored_Kexts, kexts that get copied to it will get installed to S/L/E when you Update boot caches. If you delete kexts from _For_System or transfer them to /Stored_Kexts, they will get uninstalled from S/L/E after updating boot caches. Basically, if the _For_System folder is present, the contents of S/L/E will stay in sync with the contents of _For_System. This method is an easy way to keep track of patched kexts that have been installed into S/L/E.
    If, however, you decide not to use the _For_System folder, you can simply delete it and the script will still keep track of kexts installed in S/L/E. In either case, the script will "flag" any kexts installed into S/L/E so that their presence is easily seen.
15. The script is pretty much fool-proof (I hope I don't have to eat my words on that), so if anything goes wrong, it should inform you gracefully.
16. If you have any questions or issues, please post to this thread.

Script features:


smbios.plist contents:
If using the Chameleon 2 bootloader, this picture shows just what to include in the smbios.plist for best results.


Being human, I may have goofed somewhere, so provide feedback in this thread if there are issues.
Disclaimer: I will not be held responsible for any damages, non-working systems, explosions, dead kittens, screaming monkeys, etc. that may result from following these instructions.

MODIFYING SYSTEM INFORMATION (The following are extras and only affect system information reporting)
The boot.plist
The com.apple.boot.plist and smbios.plist (used by Chameleon 2) that is installed is located in the script's "Plists" directory. It may contains extra flags that you may want to modify based on your specifications. This data is used and reported by System Profiler and does not affect system performance in any way. The string may be set as follows (this is only an example and may not be current):

Your Mac Model Name (i.e. "Mac Pro") is derived from the Model Identifier (i.e. "MacPro4,1"). See your Hardware Overview in System Profiler for an example. The list of valid Mac Model Identifiers and their corresponding marketing name is found in the SPMachineTypes.plist file, located in the SPPlatformReporter.spreporter bundle. Although I'm sure you can add your own custom model identifiers, keep in mind that Software Update uses this info for updates that apply to certain models. So, if you want to be alerted to software updates that apply to Mac Pros, use a Mac Pro identifier. Likewise, if you don't want to be alerted to updates that apply only to Macbooks, don't use a Macbook identifier. Given that this board is a Mac Pro ranking board, I've kept the Identifer as "MacPro4,1".
(NOTE: macmodel flag is no longer supported in Chameleon v2.0. Please use the included smbios.plist in /Extra to set this information.)

RUNNING VIRTUAL MACHINES IN VMWARE FUSION
If you are attempting to run Vista in VMware Fusion 2 and receive a blue screen with a "STOP 0x0000007B" message during launch, try applying the MS Hotfix for multicore-processor computer running Vista in a VM. You can get the hotfix for x64-based versions of Windows Vista here. Usual disclaimers apply.

HELPFUL LINKS AND SCREENSHOTS:
� Marcel Bresink's Temperature Monitor
� Great Internet Mersenne Prime Search (GIMPS) - Prime95 CPU torture test in OS X binaries.
� Great Internet Mersenne Prime Search forum
� Gigabyte GA-EX58-UD5 product page
� Gigabyte X58 BIOS Features
� Virtual BIOS
� TweakTown: Gigabyte Technical Support Forum
� BIOS F4 binary update
� BIOS F5 binary update
� BIOS F6 binary update
� BIOS F7 binary update

Current Integrated Peripherals settings in the BIOS:


Working hardware devices: (CLICK FOR ACTUAL SIZE)


Crunching Prime95 for 5 hours @ 3.8GHz: (CLICK FOR ACTUAL SIZE)


Running Vista 64 in VMware Fusion 2 (CLICK FOR ACTUAL SIZE)


kind regards,
MAJ

Gigabyte GA-EX58-UD5 EFI Partition Boot Install Script
Anyway, here is my EFI Boot Install Scripts for the Gigabyte GA-EX58-UD5.
I have included the kexts that I have used on my Install. The only issue I am having right now is my RAM show 400MHz... If anyone has a fix, let me know...

WARNING: This script will format/modify some of the partitions on the selected disk. I have written some safeguards to prevent accidental formatting, but it's ultimately your responsibility. Always have a backup!

What it does:
I have made a script to automate:
1. Formatting of the EFI Partition
2. Activating the EFI Partition
3. Installing the boot loader to the EFI Partition
4. Mounting the EFI Partition
5. Copying the Kernel/Kexts/boot.plist/DSDT and any other required files
6. Running the update.sh script
7. Unmounting the EFI partition
8. Restarting

The whole process takes a few minutes when done manually in terminal (Maybe more depending on how fast you can type). With the script it only takes a few seconds. You also don't have to worry about typo's (which are a BIG deal when modifying partitions). If you do this often enough (like when trying to find a working kext) it's a huge time saver!

Requirements:
1. A working install on a GUID Partitioned disk

Instructions:
1. Get the UUID of your disk. Place the UUID in the com.apple.boot.plist - Your install WILL NOT boot if this is not done. You can also edit the boot.plist kernel flags to your liking at this time, and include your EFI Strings. The UUID is set automatically. It will be added to the boot flags when the script generates the com.apple.boot.plist.
2. Edit the install.sh for your disk number. (Usually 0) You will select the disk from the script. The selection is saved to diskid.txt...
3. Place any kexts you which to install to the EFI Partition into the Extensions folder.
4. Be sure to edit the info.plist of any kexts to ensure it's version is higher than any vanilla kexts. Also "touch" them and verify the new version. I have pre-set the included kexts to v9.9.9 No longer required... These features are now built in to the install.sh script. This needs some modification, so don't increase version numbers yet.
3. Open Terminal and type:

or
Double-click install.command

Feel free to edit the script or post any kext that you feel may be better. My Install is not perfect, and I will repost any fixes to the script/kexts as it get's better.

You can also use this script to update your EFI Partition. Just throw in some kexts, change the boot.plist, add a new kernel, or whatever you want.

WARNING: I am still having issues with 10.5.6 with EFI Partition Boot. I get kernel panics when mounting a disk image. I would wait to upgrade with this motherboard unless you are experienced. Fixed (Thanks mattrb!)

Note: The Audio is not working with Mac OS X 10.5... Update to 10.5.3 or above for audio.

Download: EFI Partition Boot Installer (Update 3) (4.2MB)

Update: Updated script to fix some errors, removed IOAHCIFamily.kext which caused waiting for root errors, and added 10.5.5 Seatbelt (Disk Image Mount kernel panic fix).

Update 2: Added DSDT Patcher, boot.plist creator, and kext version editor functions to script. Simplified user input.

Update 3: Fixed issue where boot files were not copied properly. Fixed other script issues. Added kexts from Digital Dreamer (Thanks!).

Details/Credit:
EFI Boot Files: Munky/DFE/Chameleon
Kernel/System.kext: Voodoo XNU 9.5.0
DSDT: Patched DSDT for GA-EX58-UD5 (BIOS v3F)
System Management: Modified AppleSMBIOS.kext and SMBIOSEnabler.kext
Disabler: Disables AppleEFIRuntime.kext, AppleIntelCPUPowerManagement.kext, ACPI_SMC_PlatformPlugin.
Audio: Legacy AppleHDA for Boot-132
Ethernet: Modified IONetworkingFamily.kext with open-source RealtekR1000.kext
Serial-ATA: Modified IOAHCIFamily.kext from OS X v10.5.6 (Internal Disk Icon Fix)
Video: Included current NVInject.kext and Netkas Natit.kext

NEW July 2009 NOTICE RELATED TO wolfienuke's script,

Wolfienuke gave up on his EFIv8 script and you should read more to understand the game plan as to what to do in response to that.

DD's script is better for us i7 people because Chameleon 2 made it easier to deal with kexts. The kexts are easily changeable in a folder that is accessible without terminal. Whereas munky/wolfienukes EFI bootloader needs commands from the terminal.

Munky, the creator of EFI bootloader method (the basis of wolfienuke's script), expects people to go to the Chameleon 2 platform. Chameleon 2 fixes bugs from EFIv9, wolfienuke's script is dated. If you still love EFI bootloader, it is still very much possible and easy to perform.
If you still dead set on EFI Boot Partition then there is a more in depth EFI Partition script called EPOS (features a auto kext updater and Cham2). I have tested it but I just like DD's script better. Link to EPOS. Unfortunately the script is generic, maybe someone can make a complete package for i7 because I have not used the newer EPOS yet.

Enjoy your hackintosh and have a good day.

I have the GA-EX58-EXTREME on the way - Hopefully this guide will be my bible

I hope you don't mind but is it alright if I post some of the logs that I have been receiving here instead of the old thread?

If it is alright I will keep adding, but for now this is what I have been seeing today.



If anyone has idea if they are normal or can be fixed let me know. thanks again, and this is a great thread and am glad you put it together.

Thanks again Digital and wolfie for helping me get to where I am, couldn't have dont it without your guys help.

Oh, yes, don't forget those cool overvoltage and overclock lights that are all over the board! You can tell what the BIOS settings are at a glance.
For those that don't know, these are the LEDs available:

OVERVOLTAGE LED indicators for CPU, Northbridge, Southbridge, and Memory - 4 levels

Off: normal
Slight: green
Moderate: yellow
High: red

OVERCLOCK LED indicators for CPU - 6 levels

Off: normal
LED --1: •
LED 1-2: ••
LED 1-3: •••
LED 1-4: ••••
LED 1-5: •••••
LED 1-6: ••••••

TEMPERATURE LED indicators for CPU and Northbridge- 3 levels

Off: normal
61-80°C: green
Over 80°C: red

Cool and fancy.
MAJ

Digital Dreamer, you are the man!
It takes a lot for this kind of work. I just appreciate you for doing this.
Especially, the bios was so kind.
I'm going to retry with my Giga Board.

I just let other guys know on the record that Digital Dreamers Retail works with EVGA X58 SLI MOBO too, except Sound.
If other people has EVGA X58 board, you guys can just follow DD's guide, then OSX will be successfully installed although sound has to be figured out on your own. I'm using one of cheap USB sound card. Other than that, my system works perfect.

Thanks DD

I don't see anything unusual in that log. This is just occurring during bootup and is not recurring, correct?
Dashboard has checked for update.
Printing via CUPS is starting (whether you have printers installed, or not).

kernel[0]: hi mem tramps at 0xffe00000 message: There are scattered reports that this can indicate bad RAM, but is not conclusive. Have you been experiencing random shutdowns or restarts? If not, don't worry about it.

Skipping duplicate extension message is expected, as you're running a Boot from EFI partition setup. You have a System.kext that is loaded from the EFI partition at boot that has the same version # as the System.kext in the main install. So, the second one is skipped.

The mdworker message is from Spotlight and is typical.

Keep in mind that these logs are just that, logs. They exist as a FYI to programmers and others who want to determine what has happened. They don't always indicate a real problem, at least not a unrecoverable or fatal one. There are always going to be issues, but programming is about working around those issues, dumping a FYI message, and moving to the next task.

regards,
MAJ

Nevermind!

And an other success Story !
Thank you very very much to all of you and specially to Digital_Dreamer and Wolfienuke

Finally I succeeded this weekend (after 4 weeks of strugling) with a iPC 10.5.6 PPF4 disk to install and get to work my config.
In fact this was due to my ATI HD4850 card. I replaced it temporarely (while waiting for support !) by an Nvidia7900GS card from my son.
I followed the installing guides and have now one disk iPC-OSX (security) and second disk by the retail OSX DVD method.The third disk is for Time machine or RAID 1 and the 4th I have Vista64 Ultimate.

My Config:

Mobo:GA-EX58-UD5
RAM:3x2GB GSkill NQ (F3-10666CL9T-6GBNQ) (8-8-8-20)
Proc:Core i7 920 with original fan
GPU: Nvidia7900GS-256Mo ( Gainward HD4850-512Mo GS )
Case:Lian Li PC-7F
Power:Corsair HX620 mod
Monitor:Dell SP2309W (Webcam working !)
Burner:Optiarc AD-7200S
HD:Maxtor 320Gb SATA1;2x Samsung 1Tb Spinpoint F1 SATA2;Seagate 80Gb SATA1

Specs:
(I pushed the proc to 3Ghz in the Bios.)
Geekbench (64bit) :10686 (mentions 0 proc and 8 Core !)
iBench: 246 (with HD)

Some problems : On my iPC disk I have an KP when I open a dmg ! and my USB 8Gb dongle (Fat32) is detected but invisible !

I will follow very closely this "new" Topic !

When you make updates to your install guides the best is to post -patch with the new files or kext per kext with Kext helper?

arobasefr

Hi nice guide,

Your guide:
Nice guide, could you only make an extra option @ the kexts, so you can see which one are cosmatic, or extra, so the people will know the!!!minimal number of kexts to boot!!!a lot of people on the forum do get trouble with the ahci kexts, maybe in efi partition / dependencies wrong rights... you might get a higher score for you guide if you just add them later to a already working install.

Cooler did you use for the overclock? 80 degrees celcius seems to be the most save, i reached 99 with stock cooler, so didn't do the stress test before new cooler.

Hey digital_dreamer or wolfienuke, how did you guys get your memory to show up as ddr3 in the profiler? My processor is also detected as running at 0MHz lol. But my geekbench still reflects proper speeds.


*EDIT* fixed 0MHz processor by restoring original AppleACPIPlatform.kext. Memory issue, still remains detected as DDR2

Gigabyte GA-EX58-UD5 feedback

Below is my experience with this board. I'll detail a brief install method, problems/quirks and any outstanding issues I have. I'm definitely no expert and I have progressed with a lot of trial and error but hopefully my experience might help others.

I'm afraid there is little science here... These are problems I've come across and worked around. As with all this stuff YMMV.

I'd also like to take this opportunity to thank everyone on the forum who has helped me out, with big thanks to wolf and digital_dreamer for their time and efforts.

Brief install procedure

1. Firstly I installed kalyway 10.5.2 using kabyl kernel on an empty GUID USB drive. This was to be my maintenance drive.
2. Once booted in Kalyway I installed OS X using a legit retail .iso onto a clean GUID drive with no other partitions. I updated this with the 10.5.6 Combo updater and then ran Wolfs script to install EFI and the bundled kexts.
3. Once booted into OS X (i7) I added an efi string for my graphics card and removed the Natit.kext from wolfs originals.
4. I also updated to the latest voodoo and system.kext and removed the seatbelt.kext. I also added a different IONetworkingFamily.kext from digital_dreamer which enabled Time Machine to work correctly and had the latest RealtekR1000.kext in plugins - this fixes DHCP wake errors.
5. Recently I added the updated HDA kexts to get rid of the audio Sound assertion errors.

Problems/Issues


Airport/Wireless Not Working on EFI i7 install

Immediately I noticed I had no airport card showing. Looking at the -v screen on start up showed the following error:

There is also a similar error for Firewire networks which doesn't effect me


I removed the EFI IONetworkingFamily.kext and I got Airport back. Great!! I thought... But without IONetworkingFamily.kext LAN and Time Machine won't work.

Fix/Workaround
I added IO80211Family.kext to the EFI partition and Airport and Time Machine both function at the cost of working LAN. If you leave the LAN port connected, Airport will show up in the Network list but will not turn on and console reports the following error and System prefs hangs.


Hang on startup at ERROR: FireWire unable to determine security-mode; defaulting to full-secure - Green LAN!
Now this one was bit of a mystery (and still is). I was getting random hangs on boot at this message. What made it more tricky was that it seemed completely random - sometimes it happened, sometimes not. After a lot of BIOS tweaking I noticed it didn't happen when Green LAN was disabled. It also seemed to happen more when IO80211Family.kext was in the EFI partition.

Fix/Workaround
Disable Green LAN. (I've read that this needs to be on for LAN to work after sleep, but in my experience this wasn't true. I was able to sleep and the DHCP LAN came back on wake. I was also able to swap between ports). Again, YMMV


Outstanding issues.


Network - would like to figure out how to run Airport and Ethernet in tandem without having to swap out kexts.
If any of the more technical heads can offer any help with this I'd really appreciate it. Is there a way to work around the link/load error? There is obviously some sort of conflict between the IONetworkingFamily.kext in the EFI partition and the IO80211Family.kext in S/L/E.

Any ideas/input appreciated.

3rd Memory DIMM not showing in System Profiler and incorrect speed
No idea with this - just cosmetic.

The speed seems to have jumped up to 1600 (mine is 1333) after a recent .kext change - I'm not sure which.

Static Noise from PSU when disks are running
Another weird one here... No biggie, but mentioning here to see if anyone else has experienced it with this board. As the title says I get audible static noise from the PSU when the machine is running. It is loudest when the disks are working and bizarrely when I scroll up with the mighty mouse scroll ball!! My previous hack was using a P5w board with exactly the same hardware (drives,case,monitor,psu etc) and it was completely silent. I'll look into grounding etc when I get a chance.

Congratulations! I know you struggled with this for a while, so I'm glad you're on board.
Do you know what kernel the iPC install is using? To solve the KP with the dmgs, exchange your seatbelt.kext. If you're running 10.5.6 with the Voodoo 9.5 kernel, you need to use the earlier 10.5.5 seatbelt.kext.
The USB drive mounting issue is a common issue with 10.5.6. The only current solution (until the official Voodoo kernel release) is to use Andy's Voodoo-based 9.6 kernel. If you do that, you'll need to go back to the 10.5.6 seatbelt.kext to prevent KP. Simple stuff, eh?

As for your kext updates, it doesn't really matter. Whatever is simpler or quicker, but needs to be accomplished correctly with the right permissions. I like to run the post-patch, so that the script's kext folder is always current. Otherwise I may get confused regarding which version of that particular kext got installed and that can happen a lot. I also label them with various colors to keep track of them.


I'll see about doing a update regarding what kexts are needed just to boot, what are needed for device services, and what are just superficial. I did explain what the kexts are for, but I can give them a "need for boot" flag.

I'm currently using the ThermalRight Ultra-120 Extreme cooler with a quiet 1600RPM fan. I may go with an extra fan for better cooling sometime.


The kext download for my Retail DVD install has a AppleSMBIOS.kext that allows you to type in some of those strings. I was able to add "DDR3" and "1600MHz", among other things, but still only have two banks detected. That's more a issue of the way the code is implemented. 0MHz clock, eh. That's pretty fast! LOL!


I'll look into those issues you reported.


Check my previous comment to JaE-V above this one.

That's mildly amusing, as those issues were the same Apple had to contend with in the PowerMac G5 and Mac Pro PSUs, except they were mostly the infamous chirps. The iMacs also had the audible sound during scrolling, as this moves a lot of video data. Those onboard inductors can really emit a irritating high frequency sound when there are load changes on the PSU.
As for what to do? Take it in to the Apple Store.. oh, wait!
I remember some of the suggestions offered was to change the performance settings in the Energy Saver preferences, but that isn't available to us. What PSU do you have and what wattage?

regards,
MAJ

@ Cosmin Petre

You have to disable "CPU Enhanced Halt (C1E)" in the Advanced CPU Features.
This will solve this issue!

@ digital_dreamer

Thanks a lot for your hard work!

I had luck with your script. Thanks

But there is an issue with sleep. I can get it to sleep but it didn't come back!!!
How did you solve this issue?

Thanks for your help

Best regards
masterlen

I am getting KPs with the new kernel when I wake from sleep sometimes now. I can't seem to find the log for it either, I might try to cause the KP again to find the log.

Thanks - I've done a lot of testing so please let me know if I can help in any way.


Thank you so much masterlen - all is now quiet!!

Are you able to reboot okay?
Let me know, because the replaced AppleCPIPlatform.kext is supposed to contain a reboot fix. However, it just may not be necessary on your system.

The processor type and speed is read from the "Unknown" flag in the AppleSystemInfo.strings file in System/Library/CoreServices/Resources/English.lproj

Search for this text block:

and replace "Unknown" with whatever you want.

I don't know of any other way to change the Memory text other than with the OSx86 Tools Utility and use the "Modify About this Mac" option.

regards,
MAJ






Sounds like the same issue. Are you both on the Standard Retail Install or Boot from EFI?

regards,
MAJ

I am on Standard Retail!

best regards
masterlen

Awesome guide!

Looks ill be going to microcenter to pick up the UD5 and the 920

Is there anywhere to look up Debug LED codes?

When running, my board LED says "dC" but I can't find any reference to it in the manual.

Any ideas?

umm to be honest your going to help me out on that one. I would think boot from efi, I am using wolfies script so would that be from efi?

I am thinking about starting over and doing it the way you did it, but are there any benefits of doing it one way or the other? (bascially what are the big differences?)

Thanks

Craig

If you're using wolfienduke's script, then yes, you're on the Boot from EFI Partition setup.

The difference is this:
The Standard Retail DVD install puts all the patches/kexts in with the rest of the kexts on the main drive (System/Library/Extensions directory). The Boot from EFI Partition method puts the kexts in a separate and hidden partition (EFI partition), forces the bootloader to load them first or with greater priority (via higher version numbers) so that they supersede the other like-named kexts on the main partition (S/L/E directory).

Which is better?
Whichever one achieves the greatest compatibility for your system. Or, the one that is easier for you to implement. YMMV.
I like the Boot from EFI Partition approach, because you end up with a perfectly vanilla install on your main drive and can use Software Update without worrying about it overwriting your patches, as is sometimes the case in the Standard Retail DVD install. I use both: Boot from EFI partition on my main work drive and standard Retail install on my test/experiment/doctor drive.

Although you can use the same kexts in both approaches, there are slight differences in the EFI partition boot setup:

• Version numbers need to be increased to provide loading priority (over the same-named kexts on the main drive). This is why wolfienuke's script offers the option to increase the version numbers of the kexts to be installed (usually to 9.9.9 or 999.9.9, depending on which version number you're looking at). This is also why you'll see these messages in your system.log: kernel Skipping duplicate extension...
  Other changes related to loading is that the OSBundleRequired key in the plist needs to have the Root flag or string.
• "Fake" kexts that only contain the updated plists can be used (no binaries). These plists can just contain the updated device IDs and other information necessary for your board to work, but the OS will still use the actual binaries/drivers located on the main partition (if available), because they can't be found in the "fake" kext. Not only does this result in a much smaller file on the EFI partition, this has the added benefit of staying up-to-date each time Apple releases an OS update, as the "fake" kext will always use the latest binaries/drivers located on the main partition. These kexts are usually referred to as Legacy kexts.

Hope that all makes sense.

regards,
MAJ

@digital

Yeah I was thinking right about the difference between EFI boot and Standard boot. I just didn't fully understand that the kexts superseded the ones on the vanilla install. I am just confused to why I am getting this KP when my computer wakes up from sleep now. Is it possible that any of the HDA kexts could have caused this? I am thinking about trying to go back to 9.5 kernel and testing if it is that or not. Also is it possible that the kexts don't have the right version number as you stated they need a certain number to supersede correct?

thanks,

Craig

Yea, i'm rebooting fine, i actually chose that Openhaltrestart.kext durring my installation and thats taken care of everything. Restoring that original platform kext fixed my speed issue. Processor is detected at 3.2 as it should and identifying the processor correctly. I then did adjustments to applesystem info string you know and all is fine. My geekbench jumped over the thousands when i restored that original kext. I then edited my plist and added an extra flag beside the busratio=20 flag as macmodel=MacPro3,1 and that got rid of the macbook pro issue. My memory is detected at the right speed, it just says ddr2 instead of 3 lol, i'm gonna give up on it and play happy for now.

I've booted into my install and, unfortunately, do not experience the wake from sleep issues reported here. So, there must be something different in your BIOS settings or, more likely, some devices you have hooked up that's not responding properly.

I'd start with USB devices and unplug everything except for just keyboard and mouse. Make sure your keyboard and mouse are not connected to a USB hub.

Other issues could be external drives (USB, FireWire or eSATA) that don't wake up properly, PCI(e) cards that don't support sleep, or older IDE drives connected via SATA-to-IDE adapter.

Hope you find the culprit.
MAJ



Good move. Way to go.
Unfortunately, that doesn't seem to get rid of the repeating kernel messages: "Let's set the macmodel as MacPro over and over again just to be safe!" LOL!

MAJ

@ digital_dreamer

I already tried EFI Partition Boot Install Script.
It works great but I have the same issue with sleep!

Would you please tell me your bios settings?

that would be great!

Thanks!

regards
masterlen

I thought I might repeat this tip from the previous thread:

For all those using the Boot from EFI Partition method and are getting the following recurring sound assertion errors:


tmongkol has provided a fix for that from this 889A thread. (Solved by adding Digital Input's NodeID in pathmap.)
Download and install this AppleHDA update for Boot from EFI Partition setup: Legacy 3outs3ins digital HDA headphone update

This particular bundle includes the HDAEnabler.kext, LegacyHDAController.kext, and LegacyHDAPlatformDriver.kext. Also included is the latest AppleSMBIOS.kext published by karrakeha1, to get Digital Output working. This update supports HDA front audio: When you plug headphones in, the front speakers will be automatically muted. Also, in System Preferences' Sound, the name Internal Speakers will be changed to Headphones. Additionally, the Microphone inputs include the "Use ambient noise reduction" option.
I've already updated the version numbers so that they receive loading priority.


Thanks for the heads-up on the Green LAN issue. I swear it used to work with it ON, but can confirm, like you said, that it behaves in the reverse manner now. Must have been the F4 BIOS update.

UPDATE:
As for the Airport and LAN issue, have you tried installing just the RealtekR1000.kext onto the EFI partition (instead of the IONetworkingFamily.kext, which includes the whole assortment of LAN drivers), along with the IO80211Family.kext? Let me know your results.

masterlen,
I'll try to provide the pertinent BIOS settings later tonight.

regards,
MAJ

P.S. It's a slow day at work today. 98% of the company's workforce is attending a funeral for a receptionist, who was also the wife of my supervisor and mother of a fellow worker in my dept. Plus, we've had some rather icy road conditions, prompting some to take a leave from work. All of that appears to lead to some odd situations, like increasing post counts.

Condolences for the lost..

Any luck with virtual machines with the i7's yet? I havent dived into installing one yet and finding out what happens. Any issues with Time Machine?

ILife09 works great

Hey MAJ,
Right - I'm pretty sure I tried this during my testing but just tried again now to confirm.

Results/Observations
Firewire network shows up in Network System Preferences. Both Ethernet services are missing as is Airport. A quick trawl of console shows these messages - different to the link/load errors observed when loading both IONetworkFamily and IO80211.






Completely unrelated to this but does any one else get a blinking power light on sleep? This case used to blink when sleeping with old P5W board but doesn't with this board. No biggie, just curious.

Thanks

I am new to Hackintosh.

I am also very new to PC. I have been a mac guy for 20 years. Assuming the EVGA mobo is a good option, there is a system builder I found online that can build and ship the following i7 920 config for $1002. I already own the Griffin iMic, so I can solve the sound problems. Purchasing the parts at newegg comes real close to this cost, and they integrate it for me, ship it and guarantee it..

Does anyone have experience with CyberPowerPC.com? Would you go this way? Is it worth spending $100 more and hours integrating to get the Gigabyte mobo?

I am just not sure of getting the PC integrated correctly..

Thanks (details follow)

• CASE: Apevia X-Supra Gaming Mid-Tower 420W Case (G Type Black Color with Side-Window)
• CPU: Intel® Core™ i7-920 2.66 GHz 8M L3 Cache LGA1366
• COOLING FAN : CoolerMaster V8 Gaming CPU Cooling Fan (Extreme Silent Operation at only 22dBA + Overclock Proof)
• MOTHERBOARD: (3-Way SLI Support) EVGA X58 3X SLI Intel X58 Chipset SLI/CrossFireX Mainboard Triple-Channel DDR3/1600 SATA RAID w/ eSATA, Dual GbLAN, USB2.0, Dual IEEE1394& 7.1Audio
• MEMORY: 3GB (1GBx3) PC1333 DDR3 PC3 10666 Triple Channel Memory (Corsair or Major Brand)
• FREEBIES: None
• VIDEO CARD: NVIDIA GeForce 7200 GS TurboCache supporting 256MB PCI-E (EVGA Powered by NVIDIA)
• HARD DRIVE: Single Hard Drive (500GB SATA-II 3.0Gb/s 16MB Cache 7200RPM HDD)
• Optical Drive: (Special Price) LG 20X DVD±R/±RW + CD-R/RW DRIVE DUAL LAYER (BLACK COLOR)
• SOUND: HIGH DEFINITION ON-BOARD 7.1 AUDIO
• NETWORK: ONBOARD 10/100 NETWORK CARD
• KEYBOARD: Logitech Deluxe 250 USB Keyboard (Black Color)
• MOUSE: XtremeGear Optical USB 3 Buttons Gaming Mouse
• OS: NONE - FORMAT HARD DRIVE ONLY
• SERVICE: STANDARD WARRANTY: 3-YEAR LIMITED WARRANTY PLUS LIFE-TIME TECHNICAL SUPPORT

Thanks for that log. Obviously, the RealtekR1000.kext is not loading and in its place is the non-working vanilla AppleRTL8169Ethernet driver inside the IONetworkingFamily.kext from the S/L/E directory. Hmmmm.

I believe the blinking light only works when you have the S1(POS) (Power On Suspend) option selected in the BIOS for ACPI Suspend Type. This is the low-power sleep state that produces the blinking light. Default is S3(STR) (Suspend To RAM), where the system actually appears off, so no blinking light.

You may have better results and no KP with the S1(POS) sleep mode.

regards,
MAJ

Go for it, got my install just about perfect. All that doesnt work onboard is audio. *using adapter* Leo also reports memory as ddr2 but its operating correctly.

Tried it, makes no difference with the light on my board. It's really not a problem though I was just interested to hear if others had the same issue.

Thanks but I wasn't having any KPs - I think that was masterlen.

Any more ideas on what I can try on the Airport/LAN conflict issue? I'm running out of things to try. The only thing I haven't experimeted with is switching kexts in S/L/E (purely for evaluation purposes). Would this be worth trying? - say maybe replace Original S/L/E IONEtworkFamily and see if I still get link/load error?

Also, I'm in the market for a new graphics card and would appreciate some buying advice. Would it be worth holding off to see if any of the rumored new Macs include support for the new NVidia 200 Series cards or would I be better off getting something like a 9800GTX. All opinions welcomed

thanks

Interesting. I'd like the blinking light, too, but no worky for me, either.



I'd say go for it! Worth a try.
If it works, it'll probably be because of dependency issues with the EFI partition setup. Some kexts really require/depend on supporting kexts being in the same directory and may just fail if they're not.

You could also try just dropping the RealtekR1000.kext into S/L/E. I know the LAN will work that way, as that's the way the standard Retail install is done. But, I wouldn't know about wireless. Sorry I don't have any way to test, as I don't use an Airport/wireless card. I just have a Airport base station plugged into the LAN.

Are you still getting the "dC" error code? What symptoms does that board have in that code? Failed boot?
I did a search and cannot find that code anywhere. That number is far away from the last codes recorded in the manual.

masterlen,
After looking at the BOIS settings, I can't really see what setting you would need to resolve the sleep issue. You could try the BIOS profiles I have saved from my system and see if they work for you. If they don't, then the problem is elsewhere.

regards,
MAJ

Cool - I'll keep tinkering.

Yep, still have it when the machine is running but there are no symptoms as nothing is wrong.

Again I was just curious and a little confused as I couldn't find any mention of it. Sometimes is displayes FF and sometimes dC but it's completely stable. See (crappy) pic below.

No issues aside from Networking ones which I'm working on.

iPC is running 10.5.6 with the Voodoo 9.5 kernel ! so i changed it for seatbelt 10.5.5 version. Thats Ok now !

I have now also a EFI bootloader OSX (built with wolfienuke script) 10.5.6 disk, but is has the same dmg KP error so where can i get seatbelt 10.5.6 ,from combo update 10.5.6 ?
How can I get info for version N° ? Do I have to change the version n° when i put it in the EFI partition to force it to load before S/L/E ?

A question: Did you try de latest Bios for this card F5g ? or is it to risky ?
http://forums.tweaktown.com/f69/gigabyte-latest-bios-28441/

Here's the Seatbelt.kext for 10.5.6.

Wolfienuke's script has an option to update the version numbers of the kexts.
I prefer to do it manually via text editor. The relevant areas that need changes are in the info.plist and version.plist, if present:



Some kexts don't have the short version string, so it must be added.

I haven't updated to F5g, as Gigabyte seldom tells you what has been changed in that version. That's been a complaint noted even on that forum. I make it a practice to only update for known fixes/improvements that affect me and when those fixes are released to the general public (out of beta). I've subscribed to the RSS feed for various driver and BIOS updates on Gigabyte's site.

best regards,
MAJ

For those of you who want to increase version numbers via terminal, you can use the defaults command:

Your spec looks good! Only thing different is that your choice of VGA card. I happend to use ATI HD3870 which is also used by DD and Wolfienuke who guided us to have successful installation. So, if you are going to go with the nvidia VGA, you need to get that VGA driver correctly by you.

Oooo. Thanks for that!

I haven't tried, but I suppose it'll just say "no file or directory found" if there's no Version.plist present?

MAJ

JaE-V,
Have you tried the following kernel flags in the boot.plist for the RAM type, using whatever specs you have?:



I haven't tried recently, but don't plan to until the official release of the Voodoo 9.6 kernel.
Time Machine works fine if you use the updated IONetworking.kext in the GA-EX58-UD5 kexts download.
regards,
MAJ

Has anyone had luck with the Extreme version of this board? I can load iDeneb with cpus=1 but once it is installed I cant boot into the new install - even with cpus=1, -f, -v, -x, my bios settings match the settings on the 1st page - anyone?

What kernel are you using?
If using the Voodoo kernel, you need to add the "busratio=20" flag.

regards,
MAJ

Thanks for the HDA update... Works flawlessly now!

Also, you can try Kalyway distro with Kabyl kernel. That's the first kernel that I tried that worked well. I would recommend Vanilla install with Voodoo-based 9.6.0 kernel, but whatever gets your rig up and running is a step in the right direction.

Downloading now Will let you know - Just build the ultimate system Win 7 etc runs great of course but would rather OS X



running to try now



busratio=20 got me booting - I am now hanging once it gets to BSD - Shows disk0s2 minor=14 major=(Cant remember) tried using -x

Thats the end result I am after - I need to have a functioning osx install first though correct?

ok - am I being stupid Using either of the scripts to make the new GUID Disk bootable - no problem - Go to install from Retail DVD and get "Alert - For Mac OS X system requirements, see the "Read Before You Install" document on your Mac OS X installation disc. " I have done retail installs before honest I have tried my reg retail DVD as well as a unibody Aluminum MBP restore dvd - I am having to boot into my iDeneb install with busratio=20 -x -v I have installed retail from safe mode before so I dont think thats it??

Is it hanging in the iDeneb installer? Not much we can do, but it would help if you can post a picture of that log on screen.

That definitely makes things easier and less painful, because (speaking from experience here) you're going to mess up your main install a few times. So, always having a working install to go back to to fix things up is a no-brainer.


Is the install drive a fresh partition, with HFS+ and Journaling enabled? Using the Options, were you able to discern it is, indeed, a GUID partition, and not Apple Partition Map (APM) or Master Boot Record (MBR)?

regards,
MAJ

*****THIS GUIDE IS A WORK IN PROGRESS, I JUST GOT MY SYSTEM WORKING, GIVE ME A DAY OR TWO*****

My system specs:

Motherboard: GA-EX58-UD4P
Video: Zotac Geforce 7300GT
Other: Sata DVD drive, Sata II Harddrive

These are the steps I have personally taken to obtain a stable and successful install on my system.

-Bios Settings-

1. Press delete to load Bios

2. Select Integrated Peripherals

-Sata Mode: AHCI
-Sata0 - 3 Native Mode: Enabled

-Install iPC 10.5.6-

1. Boot from disc, press f8, type 'busratio=20'

2. Upon loading of install disc, use disk utility to partition and format your harddrive as GUID

3. Customize the installation by selecting the following:

Kernels: Voodoo 9.5.0
Drivers> Chipset Drivers> Intel ICH10 Sata Support

4. Install and Reboot

5. At Darwin Bootloader, press f8, type 'busratio=20'

6. Follow the onscreen instructions to setup the keyboard, user account, and whatnot. ***Be sure to create a password***

Run SlimbuildGUI-1.0

I have a quick question for you overclocking guys. I tried overclocking my system just a little to 3.2ghz, but the temp shoots up to 80 on all of the cores as soon as I start doing anything even mildy taxing. I saw a lot of people saying I shouldn't let the temp get over 70, but I just saw digital dreamers pics, and his cores are at 89 or so after 5 hours of crunching. Am I missing something? Thanks in advance for any info. ALEX