Jump to content

[GUIDE] Retail OS X Install (10.5.8) on Gigabyte GA-EX58-UD5 (Core i7) Mobo

digital_dreamer

By digital_dreamer,
in OSx86 10.5 (Leopard)

 Share
3,054 posts in this topic

Recommended Posts

fuma
fuma
Posted
Posted

Just wondering if anyone with the right skills could look into building a utility to change out the gigabyte BIOS picture... there are a lot of us that use gigabyte boards here, and we have the option to use their (ugly) boot up screen or the default non graphic boot before Darwin kicks in.... may be nice to swap it out on our rigs!

 

I found this utility (for windows) on gigybytes website, maybe someone could port it over or build something from the ground up?

 

http://www.gigabyte.com.tw/FileList/NewTec..._facewizard.htm

 

I guess I could throw in a spare hard drive, install windows, (or if you have dual boot system already) then run the utility to change the boot logo and then there u go... but it would be cool to have as a mac app!

Link to comment
Share on other sites
mangopeach
mangopeach
Posted
Posted
Just wondering if anyone with the right skills could look into building a utility to change out the gigabyte BIOS picture... there are a lot of us that use gigabyte boards here, and we have the option to use their (ugly) boot up screen or the default non graphic boot before Darwin kicks in.... may be nice to swap it out on our rigs!

 

I found this utility (for windows) on gigybytes website, maybe someone could port it over or build something from the ground up?

 

http://www.gigabyte.com.tw/FileList/NewTec..._facewizard.htm

 

I guess I could throw in a spare hard drive, install windows, (or if you have dual boot system already) then run the utility to change the boot logo and then there u go... but it would be cool to have as a mac app!

 

what about running windows via virtualization...? might seem less dirty :)

 

-------------

 

 

yeah, dreamer it is trippy. I kinda like the snappiness of the gui in some ways but its all an illusion of speed since the geekbench numbers are {censored} poor.

Link to comment
Share on other sites
bernito
bernito
Posted
Posted

Heads up for those with HD4870 and Entourage. If you have this combination in your machine, I can save you a ton of brain damage. Do not enable QE in OSX86 tools, otherwise Microsoft Entourage will slow to a crawl and also slow down other applications that are opened simultaneously. For some reason enabling QE creates a bizarre font issue which could only be resolved by countless hours of troubleshooting and then subsequently reinstalling everything from scratch.

 

Another weird issue for me was using the kernal contained in Digital Dreamer's Gigabyte GA-EX58-UD5 kexts for boot from EFI partition package. If I use it, I get a kernal panic everytime I try to install Firefox. The panic disappears when I switch back to Wolfienuke's stock voodoo kernal.

 

Just trying to give back to all those, especially DD and Wolfie, that helped me with my second hack on the EX-58.

 

Would love to know if anyone has installed the latestest release of Chameleon bootloader on the EFI partition and got it to work. Specifics as to kexts and kernal would be appreciated as I have tried endlessly to get it to work, with little success. I would ultimately like to combine Chameleon, the 9.6.3 kernal and vmware fusion (I have Vista on its own HD), but haven't managed to get there yet.

 

RUNNING OS X (10.5.6) ON THE

GIGABYTE GA-EX58-UD5 (Core i7) MOTHERBOARD:

 

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)

This portion will begin by outlining the basic steps performed for the install and what kexts are needed, replaced or deleted. This method entails installing your Mac OS X Retail DVD and a small bootloader (PC-EFIv9 Chameleon). 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 vanilla install with a handful of kexts removed/replaced for full functionality. See these threads for further information: Retail DVD Guide and New modified BOOT-132 allows you to boot retail DVDs, Use Mac OS X Retail DVD on hackintoshes!

 

2. WOLFIENUKE'S BOOT FROM EFI PARTITION RETAIL DVD INSTALL (see next post)

The Boot from EFI partition method is basically an extension to the Boot-132 method, where the modified kexts are copied to a hidden partition (EFI), leaving your vanilla Retail DVD install untouched on your main drive. This method allows you to run Apple's Software Update without any problems whatsoever. This is arguably the best install method, and one I'm currently using, if you want to keep your system up-to-date with few problems. Making this method even more appealing is the walk-through script written by wolfienuke, where you 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: 4/2/2009

  • Natit.kext for ATI 46x0 and 48x0 series cards has been updated. It's now backward compatible, so only one version is needed.
  • I've included my updated package of kexts for the boot from EFI partition setup. They are below in the downloads section.

UPDATE: 3/14/2009

  • The script has been updated with the PC-EFI v9 Chameleon (v1.0.11) Bootloader and supports boot graphics. In the future, I'll be adding some samples that the user can select, just like the About This Mac graphics.
  • Pulled the new Natit.kext, as it's creating issues for others on older video cards. Doesn't work on my ATI 2600 XT card. I'll be looking into it. (Strangely, the new Natit.kext has NVIDIA flags and strings in it.) It is now colored "Red" and in the "_repository" folder. The usual Natit.kext is colored "green" and is in the "_to_install" folder. Now fixed and updated.
  • The DSDT portion of the script has been updated to properly delete the CPU "alias" lines and ignore the other "alias" lines that occur in ASUS and similar boards.

UPDATE: 3/7/2009

  • Another script update to remove the clutter. Now, you can select a Full Install Sequence or the individual options.
  • Added updated Natit.kext for the ATI 48x0 series cards.

UPDATE: 2/28/2009

  • New walk-through script is introduced. No Terminal experience or external instructions necessary. Features are as follows:
  • • Both the pre-patch and post-patch routines are combined and can be run at your choosing.
  • • Automatically detect if the "Mac OS X Install DVD" (or ISO) is mounted and run the installer when prompted.
  • • Option is provided to make target drive active.
  • • Ability to change your Mac Model Name, CPU type, and custom About This Mac graphic (several graphic files are included).
  • • If your current CPU type is "Unknown", script will grab your CPU name and incorporate the correct CPU type (920, 940, 965, etc.) automatically.
  • • Automatic removal of "Alias" CPU lines in the DSDT patcher for those who wish to use it for other motherboards, like ASUS.
  • • Added flexibility to incorporate any number of kexts of various names. The folder structure allows support for various setups. There are basically 5 categories (ATA, Audio, Graphics, Networking, and Misc. Patches), and two folders for each category: The _repository folder to store your collection of support files and the _to_install folder, where you place files to be installed by the script.
  • • Safeguards incorporated to check for unmounted drives, incorrectly partitioned drives, duplicate mount points, etc.
  • • Activate drive feature works with user to unmount all drive partitions, including listing open files/running processes that prevent them from unmounting.
  • • Modifying Boot plist hasn't been implemented, yet.

UPDATE: 2/6/2009

  • Provided helpful information on running virtual machines, including Vista, in VMware Fusion 2.
  • Renamed Voodoo-based kernel to include the .voodoo suffix so that it doesn't get replaced by any Apple updates. The boot.plist is updated to reflect that change.
  • A symlink is created linking to this kernel so that VMware Fusion, which expects to see the default name, "mach_kernel", may function.
  • Installer script now replaces AppleSystemInfo.strings with a user-modified version, so that the About This Mac box displays proper CPU info.
  • Installer script also replaces SPMachineTypes.plist with a user-modified version, so that the Model Name under Hardware Overview in System Profiler can display the name of choice, depending on the Model Identifier.

UPDATE: 2/5/2009

  • Simplified script handling and instructions.
  • Updated script to correctly set permissions on all installed kexts, even non-Apple versions that don't come with permissions data.

UPDATE: 1/25/2009

  • Updated audio with the latest AppleHDA.kext: Version 1.6.2a37 3outs3ins digital with HDA headphone setup. 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.
  • Added DSDT patcher. An updated dsdt.aml file will be created and copied to your root directory. For more information on this patcher and why it's needed, see DSDT Patcher, a tool to fix your DSDT.

UPDATE: 1/17/2009

  • Tutorial has been updated for 10.5.6
  • Standalone kext package and installer package now includes the Voodoo-based 9.6.0 kernel.

PREVIOUS UPDATES:

  • Added further instructions for those who may have more than one partition on their drive.
  • Updated the Realtek LAN driver with version 1.8.1 from Psystar, which offers dual-gigabit support and enhanced interrupt handling for improved throughput and link detection. This driver fixes the connection loss after wake issue when using DHCP. Turn "Green LAN" on OFF in BIOS so ports can activate automatically when cable is plugged in. (Latest BIOS update must have toggled the "Green LAN" behavior.)
  • Simplified script and clarified some instructions.
  • Updated AppleAHCIPort.kext to support the Intel ICH10-R Chipset. Now shows proper info in System Profiler.
  • Modified instructions for those who need ejecting drives, i.e. eSATA. Option is available to not include "internal fix." Until a real fix is made, all drives would be flagged as "external" and will have yellow icons.
  • Fixed stupid paths error in post-patch script.
  • If you need any of the vanilla kexts that are removed from OS X 10.5.5 by the script, they are here.

DOWNLOADS:

Gigabyte GA-EX58-UD5 motherboard kexts (4.9MB) - includes Voodoo-based 9.6.0 kernel.

Gigabyte X58 Mobo Boot-132 Installer (10MB) - includes Voodoo-based 9.6.0 kernel.

NEW! Gigabyte GA-EX58-UD5 kexts for boot from EFI partition (2.65MB) - for wolfienuke's script - includes Voodoo-based 9.6.0 kernel.

 

All that's really needed to boot into OS X on this board is the Voodoo kernel, its matching System.kext, a boot.plist with the "busratio=20" kernel flag, 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 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, be absolutely sure the permissions are correct for these non-Apple kexts, or your system won't boot. Either use the Terminal to do a "sudo chmod -R 755" and "sudo chown -R root:wheel" to the file or use software like OSx86 Tools Utility to install kexts automatically.

 

After performing a Retail Mac OS X Leopard DVD install, our modified post-patch script, used in the Gigabyte GA-EX58-UD5 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:

 

BASIC RUNDOWN:

Install Mac OS X Leopard Retail DVD

 

Backup 10 vanilla files from original install: (This is not absolutely necessary, but a good practice.)

  • AppleACPIPlatform.kext
  • AppleAHCIPort.kext
  • AppleEFIRuntime.kext
  • AppleHDA.kext
  • AppleSMBIOS.kext
  • IOAHCIFamily.kext
  • IOATAFamily.kext
  • JMicronATA.kext
  • System.kext
  • com.apple.boot.plist (from Library/Preferences/SystemConfiguration directory)

Remove 7 incompatible kexts from install:

  • AppleACPIPlatform.kext
  • AppleAHCIPort.kext
  • AppleHDA.kext
  • AppleSMBIOS.kext
  • IOAHCIFamily.kext
  • IOATAFamily.kext
  • JMicronATA.kext

Install kernel and supporting files (ABSOLUTELY NECESSARY TO BOOT!):

  • Voodoo-based 9.6.0 kernel by Andy Vandijck (named "mach_kernel")
  • Voodoo-based System.kext
  • com.apple.boot.plist -(updated with device properties string and busratio=20 flag for Voodoo kernel)

Install updated/modified kexts:

  • AppleHDA.kext
    (pre-patched for the ALC889a chipset with Targas patcher)
  • HDAEnabler.kext
    (goes with the included AppleHDA.kext)
  • AppleACPIPlatform.kext
    (w/reboot fix)
  • IOATAFamily.kext
    (over 4GB RAM fix)
  • JMicronATA.kext
    (over 4GB RAM fix)
  • IOAHCIFamily.kext
    (display drives as "internal" fix. NOTE: If you have removable drives, this kext should not be used.)
  • AppleAHCIPort.kext
    (ICH10R ATA driver
  • RealtekR1000.kext
    (on-board LAN support from Psystar's version (1.8.1) of the Realtek R1000 driver)
  • Natit.kext
    (support for the ATI 24XX to 38XXx2; a separate Natit.kext from netkas is available for the new 48x0 GPU series.)
  • NVinject.kext
    (support for the NVIDIA GPUs. The NVkush.kext is included for those who wish to use it instead.)
  • AppleSMBIOS.kext
    (for PC EFI compatibility)
  • dsmos.kext
    (page decryption EFI module - ABSOLUTELY NECESSARY TO BOOT!)

Remove kext cache on new install:

sudo rm -r /Volumes/YOUR_HDD_NAME/System/Library/Extensions.mkext

 

Repair permissions:

sudo diskutil repairpermissions /Volumes/YOUR_HDD_NAME

 

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 .
  • Because I have a ATI GPU, the script includes support for it. If you have a NVIDIA GPU, you may need to install a separate kext. If you have the NVIDIA 8800GT 512, try the included NVinject.kext in the downloaded kexts folder.] FIXED - Now included.
  • If you are using DHCP in your Ethernet settings, the RealtekR1000 LAN driver will only grab an IP during boot time, and after wake from sleep will not connect again. Until a fix is made, it is suggested that we use a fixed/manual IP address for your Ethernet connection. This includes inputing your Subnet Mask and Router IP, as well. FIXED - Replaced with Psystar's version of the Realtek R1000 driver.

You may install these kexts/files via:

INSTALLING OS X LEOPARD RETAIL DVD AND BOOTLOADER:

Download Gigabyte X58 Mobo Boot-132 Installer (10MB)

These files include the EFI v9.0 bootloader, kexts, Voodoo-based 9.6.0 kernel, com.apple.boot.plist, and patcher 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, from whom the scripts and instructions are based on, dfe (David Eliott), who created the boot-132 bootloader, Kabyl, Munky, and many, many other talented individuals that make these projects possible. If you are already familiar with this method, you don't need to read any further here. The following is the basic objective:

 

PREPARATION

  1. It is ideal to have two physical drives (not two partitions on the same drive).
  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. 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 SCRIPT

  1. Double-click RUN-PATCHER and enter your password.
  2. You will be prompted to enter the name of your target drive. This name will be checked against what's available on your system, even if unmounted.
  3. Default choices are highlighted in bold type.
  4. Confirmed target drive name is saved for future use.
  5. After pre-patch selection, an option is provided to set target partition as active. 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.
  6. Prior to post-patch routine, 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.
  7. An option is available for you to change your Mac Model Name, CPU type, and custom About This Mac graphic.
  8. There are basically 5 categories (ATA, Audio, Graphics, Networking, and Misc. Patches), and two folders for each category: The _repository folder to store your collection of files and the _to_install folder, where you place files to be installed by the script.
  9. 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.
  10. If you have any questions or issues, please post to this thread.

Main list:

Installer-Main.png

Modifying Info Strings:

Installer_Info_Strings.png

Running Post Patch:

Installer_Post_Patch.png

 

UPDATES:

Most of the time, you can run Software Update without any issues. However, sometimes the updates modify the custom-installed kexts and even the kernel, which may result in a non-booting Mac. In those cases, all you need to do is boot into the other drive and double-click the RUN-PATCHER script again and you should be all set up.

 

Again, follow the directions in the scripts very carefully. Being human, I may have goofed somewhere, so provide feedback 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 that will be installed is located in the "plists" directory. It contains extra flags identifying your Mac model and memory speed 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 current string is set as follows (my settings):

<string>busratio=20 -v macmodel=MacPro3,1 MemSpeed=1600 MemType=DDR3</string>

Your Mac Model Name (i.e. "Mac Pro") is based on the Model Identifier (i.e. "MacPro3,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 "MacPro3,1".

Currently, the name "Hackintosh Pro" is used where the "Mac Pro" model name was originally. With this change, anytime the model identifier "MacPro3,1" is called up (i.e. in System Profiler), the name "Hackintosh Pro" will be used. Feel free to change this name to your liking in the script.

 

RUNNING VIRTUAL MACHINES IN VMWARE FUSION

If you get the following message upon starting a VM, "VMware Fusion cannot connect to the virtual machine. Make sure you have rights to run the program and to access all directories it uses and rights to access all directories for temporary files," you need to reboot the VMware daemon using this command in Terminal:

sudo /Library/Application\ Support/VMware\ Fusion/boot.sh --restart

Or, you can simply download this Start_VMware_Fusion script that will take care of that task and launch VMware Fusion for you. This script assumes Fusion is in the main Applications folder.

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:

• 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

• Preconfigured BIOS profiles (Load CMOS from BIOS <F12>)

Contains default 2.66GHz settings (start with this!), 3.2GHz overclock, and 3.8GHz overclock. These are my working profiles. They likely will work for you if you have set up your system similarly, but that is not guaranteed. The most likely area of change is the RAM speed and timings, so pay attention to that, as I run 1600MHz RAM with 9-9-9-24 timings. Additionally, keep in mind the overclock profiles are for
my
board. Although the 3.2GHz overclock settings required no voltage changes, the 3.8GHz settings required a CPU Vcore (1.4v) and QPI/Vtt (1.34v) voltage change, but still well within the maximum allowed for the CPU and chipset. Although these settings are safe, they may be more than your board needs or less than it needs. Only you can determine that through tests. I will not take responsibility for any harm done from overclocking your board.

NOTE:
I use the Extreme Memory Profile (X.M.P.) for my Corsair XMS3 RAM. Your RAM may not have a XMP profile or one under the same name, so double-check this setting. For the absolute best in stability, use the XMP profile (if available) or key in your memory timings manually (Your BIOS can only guess your timings with the AUTO setting.)

 

Current Integrated Peripherals settings in the BIOS:

Integrated-Peripherals.gif

 

Working hardware devices: (CLICK FOR ACTUAL SIZE)

Hardware-Profile_SMALL.gif

 

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

OC-Screenshot_SMALL.gif

 

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

VMware-Fusion-Vista_SMALL.gif

 

kind regards,

MAJ

Link to comment
Share on other sites
scfp
scfp
Posted
Posted
what about running windows via virtualization...? might seem less dirty :)

 

-------------

yeah, dreamer it is trippy. I kinda like the snappiness of the gui in some ways but its all an illusion of speed since the geekbench numbers are {censored} poor.

 

just thinking if the system clock was running fast bench marks would be low because of the time distortion between system time and real time

system time x2 = benchmarks /2 Just a thought ;)

Link to comment
Share on other sites
tgintheworld
tgintheworld
Posted
Posted

Gigabyte GA-EX58-UD5 motherboard kexts (4.9MB) - includes Voodoo-based 9.6.0 kernel.

Gigabyte X58 Mobo Boot-132 Installer (10MB) - includes Voodoo-based 9.6.0 kernel.

NEW! Gigabyte GA-EX58-UD5 kexts for boot from EFI partition (2.65MB) - for wolfienuke's script - includes Voodoo-based 9.6.0 kernel.

 

Hi all,

 

I've been reading this thread for a couple weeks now, and I started building my machine this weekend. Specs:

 

GIGABYTE GA-EX58-UD5

Intel i7 920, 2.66GHz

6GB OCZ Platinum DDR3 1600

SATA2 HDs

Zotac 8800GT 512MB

Dual displays

Microsoft Bluetooth Mouse and Keyboard

 

I've been successful with both DD's install script as well as Wolfienuke's. However, with DD's, I get support for pretty much everything: sleep works, bluetooth keyboard and mouse connect and work, video and sound work (I use EFI studio to generate the EFI string for my video card), firewire and USB seem to work fine, and of course VMware works.

 

My EFI Partition install works well too, with most of those things working, except:

 

1.My bluetooth mouse is detected, and while it attempts to connect to it, it fails every time. What kext should I be using for Wolfienuke's script to give me the same bluetooth functionality that works in DD's? (Edit: I got this working, explained below)

 

2. Firewire doesn't show up in my network preferences panel at all. Again, can someone recommend a firewire kext that works with the EFI Partition method?

 

3. VMWare: I'm aware that the issue seems to stem from the mach_kernel filename -- I just haven't gotten around to playing with this to get it to work properly (maybe using OSX86tools as someone else in this thread suggested).

 

 

Here's my question to Digital Dreamer: the set of boot kexts you provided to use with Wolfienuke's script, are those meant to be the only kexts in the Extensions folder on the EFI Partition? Or should I add those on top of the kexts that Wolfienuke has in his set of files, replacing the ones with the same names? (Edit: I think I figured this out for myself)

 

The reason I ask is that I haven't been able to use those scripts you provided successfully yet, whether I add them to Wolfie's Extenions, or delete the kexts he has in there and adding yours instead. Either way, it doesn't boot up for me (I don't recall the message, if you're interested I can try it again and get the message). However, I was able to take the "_to_install" kexts from your Boot 132 installer package, dump them in Wolfie's Extensions folder (after deleting the kexts already in there) and boot successfully. I had Firewire in that case, but still no bluetooth.

 

I'd also like to thank you (DD) and Wolfienuke and all the others who have helped out here by asking good questions (and eventually posting the answers :unsure:

 

Thanks!

 

-----------------------------------------

Edit: I managed to get the EFI Partition method to give me everything I needed to work besides Firewire. I did this by using

 

Wolfienuke's EFI script

Digital Dreamer's System.kext and 9.6.0 Voodoo kernel

Digital Dreamer's boot kexts for EFI Partition (removed the kexts wolfienuke's zip had in it first) + 10.5.6 seatbelt.kext

EFI string from EFI studio (I've only done this for one video card, but I plan on using 2 for SLI on my windows drive)

 

Thanks again for everyone's help, and I'll be glad to assist anyone with questions about my set up too.

Link to comment
Share on other sites
joeblough
joeblough
Posted
Posted
also is deep sleep working on the UD5? its not working on the UD4P (goes to sleep, but then does not wake up properly (don't see any kernel panic logs either.) i'd like to get it working - are there particular kexts that are usually the source of sleep problems?

 

if anyone cares - i upgraded my bios to F6 (it was way down at F2). that didn't help by itself, but switching to the kernel from 10.5.7 did. sleep now works, and i think i've got a 100% working system now. i assume the dsdt in the new bios is different, but i'm still running a patched dsdt from F2, i have to re-do the patch now.

 

edit: ha, i take it back. it won't mount and USB drives anymore with the new kernel. perhaps some kexts did not load, i have to check.

 

edit edit: duh, i forgot to put back the vanilla system.kext. now its working again.

 

edit^3: that's interesting. with the right system.kext in there it won't wake up from sleep anymore. there must be some kext that didnt load due to the bad system.kext, and that's causing the hang after wake??

Link to comment
Share on other sites
digital_dreamer
digital_dreamer
Posted
  • Author
Posted
thanks guys.. phat and matt - appreciate ya' chiming in.

 

I will just keep fiddling. On a side note my machine is running at completely stock voltages and overclocked to 3.6ghz with turbo and all the cpu stuff enabled. I did a 3 hour prime test and none of my core got above 81celsius and my geekbench is 12828. That was literally my first "quick" overclock i first set when i built the system two weeks ago. But now i'm wondering if i should just leave well enough alone. 81 degrees full load is "safe" right?

 

---

 

update : now running 3.75ghz at stock voltage. geekbench 13500 cinebench 20k

havent stress tested it yet.

That's an incredible OC on stock voltage. Should run cool, compared to other OCed boards with upped voltages. I forget, is stock Vcore at 1.375?

 

@digital_dreamer

 

thanks for the script, it worked well for me on a UD4P motherboard.

 

i dont know if you are planning any more development on this script, but it would be nice if the dsdt patching stage could be broken out separately, or if you can have the dsdt patching stage take a dsdt from disk rather than dumping it from the bios. this would let you run the script from a totally different machine. in my case i ran the script on my badaxe2 and of course the dsdt that ended up on the target disk was completely wrong. i had to delete it, then boot the UD4P on the new disk, and dump/patch the dsdt. luckily it would boot without the patched dsdt.

 

also is deep sleep working on the UD5? its not working on the UD4P (goes to sleep, but then does not wake up properly (don't see any kernel panic logs either.) i'd like to get it working - are there particular kexts that are usually the source of sleep problems?

 

thanks again for your efforts, this is great.

Thanks for your feedback. Appreciated.

Yes, I'm still working on updating the script. Lots of stuff going in, now.

 

Those suggestions regarding separating the DSDT stage from the rest of the post-patch will be considered, as you're not the only one who requested that. There have been a few who have installed just as you described. As for creating a patch from a prebuilt file rather than the on-board BIOS, that sounds like a cool workaround, but don't know if that's possible with the current software. I might mention that suggestion in the DSDT thread, as there have been quite a few needing to create a DSDT patch, but not able to run it on the actual board.

The thing is, if you have to run the software to create a digital file (from the BIOS) to be patched elsewhere, you might as well run the entire sequence and finish the job right there.

 

regards,

MAJ

Link to comment
Share on other sites
mangopeach
mangopeach
Posted
Posted
I forget, is stock Vcore at 1.375?

MAJ

 

Well... another possibility is i'm a complete noob and [auto]actually means the motherboard sets some mysterious voltage. Basically I never touched my voltage. Here is a photo. School me please if [auto] means something other than the voltage shown to the left of [auto] (lower right of image below).

biosfotos.jpg

 

 

btw - i have been really happy with my hardware build. Let me share my system specs for those still in the hardware phase. System seems happy and stable with the settings in the photo above.. geekbench 13500 cinebench(multicore) 20,250. I haven't really done major tuning q/c-ing with the graph paper yet (wonder if i'll get around to it)

 

- gigabyte UD5

- noctua NH-U12P (cooler - both fans exhausting out back)

- intel i7 920

- GSkill ddr3 1600 6gb (9-9-9-24)

- COOLER MASTER RC-690 Case (kinda ugly an pc-ish but really well laid out)

- COOLER MASTER UCP RS700 (really nice power supply)

- 5 additional Noctua 120mm fans

- EVga GeForce 9800 GTX+ 512MB

- 300 gb velociraptor

- some cheap craptastic dvd burner

Link to comment
Share on other sites
fuma
fuma
Posted
Posted
Just trying to give back to all those, especially DD and Wolfie, that helped me with my second hack on the EX-58.

 

 

Wooooo yah that was fun to scroll through... had to quote the WHOLE tutorial over again huh? You can selectively edit your quotes you know... just a heads up!

 

I just swaped out the voodoo kernel with 9.6.3 and my sys identifier now says its a MacPro2,1 ?

 

I only noticed after I used geekbench, and the "hackintosh" identifier was gone.

 

I know this is something I can change, but what I'm wondering is, was this from the kernel itself or is my system seeing an older kext now that I'm not using the voodoo kernel?

 

Just bumping my own post here...

 

and got to thinking... did anyone get the corresponding vanilla system.kext to go with the 9.6.3 kernel? It would be nice to have as well!

 

System seems happy and stable with the settings in the photo above.. geekbench 13500 cinebench(multicore) 20,250. I haven't really done major tuning q/c-ing with the graph paper yet (wonder if i'll get around to it)

 

Is your CPU using a different stepping than everyone elses? I know they were going (or maybe have already) release a newer version of the 920.

 

My i7 says it's c0, if netkas's cpu-x is reporting correctly... I can't get it above 3.4 with stock voltage and not above 3.6 at all.

Link to comment
Share on other sites
mangopeach
mangopeach
Posted
Posted
Is your CPU using a different stepping than everyone elses? I know they were going (or maybe have already) release a newer version of the 920.

 

My i7 says it's c0, if netkas's cpu-x is reporting correctly... I can't get it above 3.4 with stock voltage and not above 3.6 at all.

 

i dont know... here this will help.

stepping.jpg

Link to comment
Share on other sites
joeblough
joeblough
Posted
Posted
Thanks for your feedback. Appreciated.

Yes, I'm still working on updating the script. Lots of stuff going in, now.

 

...

 

The thing is, if you have to run the software to create a digital file (from the BIOS) to be patched elsewhere, you might as well run the entire sequence and finish the job right there.

 

regards,

MAJ

 

sure, i understand what you mean. if its a separate step that can be skipped that would probably be good enough.

Link to comment
Share on other sites
digital_dreamer
digital_dreamer
Posted
  • Author
Posted
i dont know... here this will help.

stepping.jpg

Hmmmmm. You got the same stepping as I have. The only difference I see is that CPU-X is reporting 7 cores for you, but 4 cores on mine (but, still 16 threads). Interesting.

 

You got a lucky pick. :hysterical:

 

EDIT: and very low Vcore voltage for that OC. 1.26875v Wow. Nice.

But, I bet you aren't prime95 stable with those settings. :D

 

regards,

MAJ

Link to comment
Share on other sites
digital_dreamer
digital_dreamer
Posted
  • Author
Posted
pssh. probably not. I tested 3.6ghz at stock, though for 3.5 hours.

 

Still when I leave it on [auto] for voltage is it really the number shown to the left or some random voltage the bios decides?

I'm sure it's really using that quoted number. I believe the BIOS will determine the working minimum voltage for each installed CPU and that's where the "Auto" comes in. That's why the stock voltage may be different from board to board.

My stock is 1.375v

 

ANNOUNCEMENT

Script has been updated with the new GUI Chameleon bootloader, vanilla 9.6.3 kernel and other goodies. Grab it and give it a try.

 

regards,

MAJ

Link to comment
Share on other sites
L3B3R
L3B3R
Posted
Posted
ANNOUNCEMENT

Script has been updated with the new GUI Chameleon bootloader, vanilla 9.6.3 kernel and other goodies. Grab it and give it a try.

Thanks DD! Everything seems to have updated perfectly.

 

The only thing that I see that may need changing is that your update in the first post says that there are boot pictures to choose from and so on. There is nothing in the "boot_pictures" folder and when the option is chosen in your script it says, "Nothing in source directory to install!" Thought I would mention it.

Link to comment
Share on other sites
mangopeach
mangopeach
Posted
Posted
I'm sure it's really using that quoted number. I believe the BIOS will determine the working minimum voltage for each installed CPU and that's where the "Auto" comes in. That's why the stock voltage may be different from board to board.

My stock is 1.375v

 

ANNOUNCEMENT

Script has been updated with the new GUI Chameleon bootloader, vanilla 9.6.3 kernel and other goodies. Grab it and give it a try.

 

regards,

MAJ

 

w00tage!

Link to comment
Share on other sites
digital_dreamer
digital_dreamer
Posted
  • Author
Posted
Thanks DD! Everything seems to have updated perfectly.

 

The only thing that I see that may need changing is that your update in the first post says that there are boot pictures to choose from and so on. There is nothing in the "boot_pictures" folder and when the option is chosen in your script it says, "Nothing in source directory to install!" Thought I would mention it.

L3B3R,

There are two different versions: One with all the boot pictures and one without. I did it that way so that those not interested in the boot pictures wouldn't be forced to download the entire 48MB, but just the 22MB version.

 

Sorry I didn't clarify that earlier.

 

regards,

MAJ

 

Is the new vanilla kernel tested with the installer? I only just got my system perfect yesterday!

 

Got to decide whether I want to switch off voodoo.... :)

The vanilla kernel works alright. But, given the time, I haven't really put it through all its paces.

 

If one decides to go back to the Voodoo kernel, it's still there in the folder. Just put it and the System.kext back into its folder and pull the Voodoo version back out and run the post-patch and you're good to go. (Both kernels are under the same name, so the script will handle them the same way.)

 

best regards,

MAJ

Link to comment
Share on other sites
digital_dreamer
digital_dreamer
Posted
  • Author
Posted
Installer seemed to work fine, but I no longer have working USB ports...

Hmmm. I haven't experienced this issue. USB only works when plugged in at boot time? Have you done another restart?

 

The script should be installing a matching System.kext, which, I'm told, is just the vanilla kext from 10.5.6. If the required System.kext for that kernel is actually an updated one, I'll need to get a copy.

 

Can anyone else chime in as regards USB hotplugging with the updated script? I'm at work now.

 

regards,

MAJ

 

Hi all,

 

I've been reading this thread for a couple weeks now, and I started building my machine this weekend. Specs:

 

GIGABYTE GA-EX58-UD5

Intel i7 920, 2.66GHz

6GB OCZ Platinum DDR3 1600

SATA2 HDs

Zotac 8800GT 512MB

Dual displays

Microsoft Bluetooth Mouse and Keyboard

 

<snip>

Here's my question to Digital Dreamer: the set of boot kexts you provided to use with Wolfienuke's script, are those meant to be the only kexts in the Extensions folder on the EFI Partition? Or should I add those on top of the kexts that Wolfienuke has in his set of files, replacing the ones with the same names? (Edit: I think I figured this out for myself)

 

The reason I ask is that I haven't been able to use those scripts you provided successfully yet, whether I add them to Wolfie's Extenions, or delete the kexts he has in there and adding yours instead. Either way, it doesn't boot up for me (I don't recall the message, if you're interested I can try it again and get the message). However, I was able to take the "_to_install" kexts from your Boot 132 installer package, dump them in Wolfie's Extensions folder (after deleting the kexts already in there) and boot successfully. I had Firewire in that case, but still no bluetooth.

 

I'd also like to thank you (DD) and Wolfienuke and all the others who have helped out here by asking good questions (and eventually posting the answers :)

 

Thanks!

 

-----------------------------------------

Edit: I managed to get the EFI Partition method to give me everything I needed to work besides Firewire. I did this by using

 

Wolfienuke's EFI script

Digital Dreamer's System.kext and 9.6.0 Voodoo kernel

Digital Dreamer's boot kexts for EFI Partition (removed the kexts wolfienuke's zip had in it first) + 10.5.6 seatbelt.kext

EFI string from EFI studio (I've only done this for one video card, but I plan on using 2 for SLI on my windows drive)

 

Thanks again for everyone's help, and I'll be glad to assist anyone with questions about my set up too.

Congrats!

Sorry, I hadn't responded earlier, but it looks like you were able to answer your own question regarding the included kexts. Good work!

 

Does Firewire not work at all, or does it just not show up in the Network panel? That particular feature is for IP over Firewire and some ports don't show up until they are actually used.

 

regards,

MAJ

Link to comment
Share on other sites
joeblough
joeblough
Posted
Posted

i am experiencing the 'double-time' fast clock/time weirdness with an EFI install using wolfienuke's script as well.

 

at first i thought maybe wolfie's kexts were different since they have slightly different names. so i instead moved digital_dreamer's kexts over to the efi partition and rebuilt Extensions.mkext. but i had the same problem.

 

it seems to me like boot.plist isnt actually getting parsed, because the model number and dram are no longer set. i thought maybe i needed chameleon 2.0 for this to work right, so i upgraded but still no joy. also it does not seem to be taking my EFI strings so that's further evidence.

 

interestingly after upgrading to chameleon 2.0, the 2x clock problem was not there. however it does seem like some kexts did not load - for instance my USB flash drive stopped mounting. so that may have 'fixed' the clock issue but the system still is not working right.

 

does anyone know who picks up those boot flag strings? is it the kernel itself or the hacked AppleSMBIOS.kext? i know that some kexts don't load properly from the EFI partition... i have however removed the vanilla versions from /S/L/E so there should be only one place to get the new kexts.

 

i put my boot.plist both in the root of the EFI partition and in the Extras folder. i even fixed the boot.plist in /Library/Preferences/SystemConfiguration, but still no joy.

 

hmm.

 

edit: i just realized that i forgot to change the osbundlerequired string in the info.plists to 'root'... i think this will prevent the kexts from loading right. this is something that wolfienuke's script does (right??) but since i moved the other kexts in it was necessary to do it by hand. i'll try this tonight, or maybe just start over and edit the script to use chameleon.

 

also my thinking here is that if busratio=20 is not properly parsed, the timebase for the internal clock will be wrong. i realize that some kernels will not boot at all unless this flag is passed, but i am using the kernel from 10.5.7, which i assume can figure out the multiplier on its own (?)

Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...